Alcatel 7750SR LAG interfaces not parsing during discovery

McDonald Richards added a comment - 2015/04/08 08:12 AM ifName could probably work. These are similar to the Ericcsson SmartEdge boxes in that you make the "ip interface" and bind it to a physical port. I will probably delete/hide/disable the logical ports and monitor physical ones only to keep it clean. ifName.1 = system ifName.2 = INTERNAL-AE_br01.sto01 ifName.3 = IP TRANSIT: Carrier1 ifName.4 = IP TRANSIT: Carrier2 ifName.136347648 = 4/1/1 ifName.136380416 = 4/1/2 ifName.136413184 = 4/1/3 ifName.136445952 = 4/1/4 ifName.136478720 = 4/1/5 ifName.136511488 = 4/1/6 ifName.136544256 = 4/1/7 ifName.138510336 = 4/2/3 ifName.138543104 = 4/2/4 ifName.138575872 = 4/2/5 ifName.138608640 = 4/2/6 ifName.138641408 = 4/2/7 ifName.138674176 = 4/2/8 ifName.138706944 = 4/2/9 Let me know if you'd like me to pinhole the ACL so you can run any direct tests on this box if it helps.

Adam Armstrong added a comment - 2015/04/07 05:03 PM What are these devices reporting for ifName? We might have to hardcode this OS to use ifName instead of ifDescr (lots of vendors put useless shit into ifDescr, windows puts the NIC's manufacturer and model in there!)

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.

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.

McDonald Richards added a comment - 2015/04/04 08:17 AM Discovery debug attached. Some details obfuscated (names).