search

netdisco / snmp-info

Other
38 stars 32 forks source link

Problem with port numbering on Avaya(ERS5900) #393

Open t350 opened 4 years ago

t350 commented 4 years ago

Hello,

I have problems with port numbering on ERS5900. I have 7 unit, but on the tab Ports i see ports 1.x with 1.x, ports 2.x with 3.x, ports 3.x with 5.x(and i can see only 4 units).

Software version: version: 2.44.15 snmp: 3.70 db schema: 61 postgreSQL: 9.6.10 perl: 5.16.3

I have attached a printscreen. netdisco Can you help me please? Thanks.

zoeloe commented 4 years ago

There should be a routine to determine the index factor,.. I'm remembering an old routine here, but it seems NOT to be straightforward to integrate this in Baystack.pm module it seems. Different newer Avaya/Extreme devices deviate on the index factor regex rules it seems. Any ideas how this could be automated ?

rc9000 commented 4 years ago

I can not really help much since I don't have access to a single Bay/Avaya device, but here's my two cents anyways:

First, this slot.port calculation here does default to 32 as index factor, which was probably the case on ancient devices. Recently everybody is just adding in the 128 regex, so maybe reversing this logic could help for new unknown models. However we'd need somebody with a range of devices and OS versions to make sure it's really an improvement.

Secondly, in @t350's screenshot the expected value seems to be in the right column which is probably the ifXEntry.ifName or ifAlias? So couldn't we just use that on modern Avaya by converting / to . instead of doing this calculation from ifindex to slot.port? As above, wide verification would be required.