Problem with port numbering on Avaya 49xx

[netdisco-automation]

From @erics69 on January 20, 2017 8:28

The discover of new Avaya ERS49xx's stacks results in wrong port numbering: unit 1 has 1.x port number format, but unit #2 has 3.x, unit #3 has 5.x, and so on.

Your Environment

• Netdisco version used: 2.034002
• SNMP::Info version used: 3.34
• Avaya ERS4950GTS-PWR+: fw 7.2.0.5, sw 7.2.0.213

Copied from original issue: netdisco/netdisco#292

[netdisco-automation]

From @jl84 on April 21, 2017 10:6

Hi,

This is probably due to Avaya releasing the ERS 59100GTS switch model with 100 ports so the port indexing gets wierd but yeah I have the same issue which is quite annoying and I already made a config mistake because of it :)

/Johan

[zoeloe]

FYI:
Suggested intermediate fix:
It seems that a 4950 switch has a index_factor of 128.
It looks that modifying SNMP::Info::Layer2::Baystack.pm

the diff is e.g.:

----------------
232c232
<         if ( ( $model =~ /(5[56]\d\d)|VSP|(4950)/ )
---
>         if ( ( $model =~ /(5[56]\d\d)|VSP/ )
----------------

does the trick.
It would be nice if a generic catch-all fix would be available. A similar regex would catch
other devices with an index_factor of 128.
You could try: /(5[56]\d\d)|VSP|(59100)/
Not tested.

[ollyg]

fixed in 4afbd37, many thanks!