Major Description
http://jira.observium.org/browse/OBSERVIUM-149 was just closed without being fixed.
When adding or removing ports from a VLAN, the VLAN tab is not updated. It appears as though the VLAN is populated the ver first time a device is discovered, and then never altered again.
This is happening on a Nexus 5548.
Attachments
Activity
There are some issues like the above in the Q-bridge-mib code that I've known about / notice regularly; I intend to fix these soonish unless Mike beats me to it.
I think I see the issue here Mike.
After running discovery and poller in debug mode and reading the output, I've discovered that the ports that are displaying incorrectly have their access VLAN set, however the port is actually a trunk port with separate set of VLANS being trunked.
So for example, port Eth1/1 might look like:
interface Ethernet1/1
switchport mode trunk
switchport access vlan 5
swithport trunk native vlan 2
switchport trunk allowed vlan 50,60,70,80
In the above config, VLAN 5 is irrelevant as the port is configured as a trunk port. However, when going to the vlans tab in Observium for the device, we will see port Et1/1 listed as part of VLAN 5. I would have expected Observium to list port Eth1/1 under VLAN 2, 50, 60, 70, and 80 but this is not the case.
Is this intended behavior? Should Observium be showing the port as being assigned to all VLANS that it trunks? I expected the vlans tab to resemble the output of show vlan on the Nexus.
If this issue still exist, please open new issue report with more detailed info and debug output for device:
./discovery.php -d -m vlans -h nexus_host
|
./poller.php -d -m ports -h nexus_host
|
149 was about Q-BRIDGE-MIB however; I'm pretty sure Nexus uses another MIB.
I close this issue because fixed today some Q-bridge-mib vlan discovery (in r6022).
If this specific issue still exist here I can reopen, but anyway someone add debug output which I wrote earlier.
But after svn up.