Missing switch ports and CAM data from Aruba switches (S2500)

[jmbredal]

A customer reports that his Aruba S2500 switches seem to be poorly supported by NAV.

Among other things, NAV only sees switch ports on VLAN 1, and hence, only reads the forwarding tables of these few ports.

Some testing reveals the Aruba switches seem to employ the same brain-dead VLAN community-indexing scheme that Cisco does, even though they DO simultaneously support the Q-BRIDGE-MIB (which makes it look like the Q-BRIDGE-MIB keeps referring to non-existent bridge ports).

NAV can probably be made to use the same logic for Aruba switches as for Cisco switches with some minimal effort, so we should look into it.

---

Imported from Launchpad using lp2gh.

• date created: 2016-04-26T10:47:46Z
• owner: mbrekkevold
• assignee: mbrekkevold
• the launchpad url was https://bugs.launchpad.net/bugs/1575112

[jmbredal]

(by mbrekkevold) The Aruba switches do list their alternate BRIDGE-MIB instances in ENTITY-MIB::entLogicalTable, but for some, even weirder, reason, they list the master community string for all the logical entities, instead of the VLAN-indexed one. The only way to support this is to make a stupid workaround for any switch with an Aruba enterprise id.

[jmbredal]

(by mbrekkevold) fix committed here: https://nav.uninett.no/hg/nav/rev/d6d7a4e93e0f

[jmbredal]

Translated changeset references: https://nav.uninett.no/hg/nav/rev/d6d7a4e93e0f: 984adc06eb3876ddfd655e6da10f164903fe14d2