We have two very similar Aruba switch devices. For one of the devices, the VLAN information is shown directly under the physical ports, once you expand the physical interface from the interface tab you can see which VLAN that port belongs too and this is our preferred method.
For the other Aruba device, we see that the VLANs are being displayed at the same level in the interface tab, therefore we do not know which VLANs are assigned to each interface.
Why does Spectrum provide this information for 1 device but not the other?
Release : All
Spectrum Discovery and Modeling
The device that does not show the VLANs under the physical port does not support the Q-BRIDGE-MIB.
For Spectrum to understand where to place the virtual VLANs under the Physical Interface ports is that Spectrum matches the data found in the Q-BRIDGE-MIB::dot1qVlanStaticName with the interfaces.ifTable.ifEntry.ifDescr for a match and this will determine where to place the VLANs under which physical interfaces.
Since the dot1qVlanStaticName values for the non working device are empty, Spectrum places the VLANs at the same level as the physical interface models instead of underneath.
Spectrum needs the qbridge mib populated on devices to create the qbridge app which is what controls the vlans in Spectrum. Some devices do support the qbridge mib but do not populate all oids as required, so we cannot create the qbridge app and so cannot create the vlans correctly. Aruba devices show various problems related to the qbridge mib e.g. Both dot1qVlanNumDeletes and dot1qVlanVersionNumber are required by Spectrum but are not populated in the mibs of some Aruba devices so Spectrum is not able to correctly create the VLANs on this device type. There is an issue opened with the Aruba vendor to get them to fix their devices so that it does populate the qbridge mib fully to include these 2 empty oids. One Aruba has resolved their problem, we will be able to correctly see the vlans in Spectrum.