Hello everyone! I have an issue I can't figure out. I will be opening a ticket for this if the community can't point me in the right direction. We recently moved from some EOL Cisco devices to some Avaya (Nortel) 4550Ts. (Bad choice, but I will leave my Cisco experience out of this...) I managed the devices, SNMP works, configs download, have yet to find any good custom pollers (what a royal pain) so we set up interface advanced alerts to at least trigger when another managed node drops. Works like a charm for our Ciscos! Not so much in this example. So, this is the question.
When you look at this Las Vegas Avaya switch as an example, I can see that the device 'uplink' names are clearly labeled on the device (under interface name, as Avaya's use name and not interface) however, when I look at the ports I have managed, the names are not reflected in the managed element list.
Config snippet from the Avaya showing the named interface:
24 /* PBX 170.8.167.4 */
25
26
<SNIP>
46
47
48 *** Uplink to lasvnvxx-sr01 int Fa 1/0/44 ***
IN SW, this is what it reads:
Now this is where it gets weird....a site like Montreal, switch 14 as an example, has the interface names correct as well as the elements listed properly. Both are the same device type - 4550T-PWR, both running the exact same code. Both of the devices have been removed and added multiple times, and it works fine on this device.
(config from the Avaya)
43
44 *** Uplink to mtrlqcpr-sw15 int Fa1 ***
45 *** Uplink to mtrlqcpr-sw15 int Fa2 ***
46 *** Uplink to mtrlqcpr-sw23 int Fa4 ***
47 *** Uplink to mtrlqcpr-sw16 int Fa2 ***
48 *** Uplink to mtrlqcpr-sw16 int Fa1 ***
49
50 *** Uplink to mtrlqcpr-sr01 int Gi2/0/10 ***
And oddly enough, SW clearly sees this as the proper resource:
This is a real head scratcher. I have 2 exact same devices with identical configurations (less IPs, subnets, etc...) and one works just fine with discovery, the other is not. Is this a bug? Has anyone else had any insight on these Avaya/Nortels? thanks for any and all input here!
