Alcatel 7750SR LAG interfaces not parsing during discovery

McDonald Richards added a comment - 2015/04/07 12:35 PM Frustrating. They seem to stick any description into the ifDescr. Quotation marks are required for anything with a space in it and they are escaping them in the SNMP description. Are there any config knobs I can use to over-ride this inside Observium? *A:pr01.sto01>config>port# info ---------------------------------------------- description "INTERNAL: br01.sto01 || XE-4/1/1 || lag0" ethernet exit no shutdown ---------------------------------------------- *A:pr01.sto01>config>port#   ifDescr.138510336 = 4/2/3, 10-Gig Ethernet ifDescr.138543104 = 4/2/4, 10-Gig Ethernet ifDescr.138575872 = 4/2/5, 10-Gig Ethernet ifDescr.138608640 = 4/2/6, 10-Gig Ethernet ifDescr.138641408 = 4/2/7, 10-Gig Ethernet, \"INTERNAL: br01.sto01 || XE-4/1/1 || lag0\" ifDescr.138674176 = 4/2/8, 10-Gig Ethernet, \"INTERNAL: br01.sto01 || XE-4/1/2 || lag0\" ifDescr.138706944 = 4/2/9, 10-Gig Ethernet, \"INTERNAL: br01.sto01 || XE-4/1/3 || lag0\"   ifAlias.138510336 = 10-Gig Ethernet ifAlias.138543104 = 10-Gig Ethernet ifAlias.138575872 = 10-Gig Ethernet ifAlias.138608640 = 10-Gig Ethernet ifAlias.138641408 = INTERNAL: br01.sto01 || XE-4/1/1 || lag0 ifAlias.138674176 = INTERNAL: br01.sto01 || XE-4/1/2 || lag0 ifAlias.138706944 = INTERNAL: br01.sto01 || XE-4/1/3 || lag0

McDonald Richards added a comment - 2015/04/07 11:08 AM You can close this. Just saw the config on the box and they have used the description as the interface name instead of calling it something sensible and using the "description" for the description. Sigh... Thanks

McDonald Richards added a comment - 2015/04/07 08:45 AM Ah sorry – we use "INTERNAL-AE" instead of "INTERNAL" to prevent the double count of LAGs in the aggregated graphs. The pipes in the descriptions are used by some other internal tools here. We have a Juniper environment as well that we use the same syntax on. The parsing of the description for the transit/peering/core interfaces works fine. I have included a couple of screenshots that may make what I am trying to report a little clearer.

Adam Armstrong added a comment - 2015/04/05 08:27 PM - edited You probably can't have a dash in the port-type in the description. Descriptions are in ifAlias, because back when the MIBs were written, people were stupid. ifDescr is actually the name of the interface, and ifName is usually the "shortest unique name the device understands for the interface". In the output above : [ifAlias] => INTERNAL-AE: br01.sto01 || lag 100 || xxGbps Seems to be fine except for the - (and that our parsing format doesn't use ||, I assume you have some custom code to do that?)

McDonald Richards added a comment - 2015/04/04 08:20 AM Also if desired I can provide access to a pre-production device to a whitelisted IP address for testing.