Details
Major Description
Hello,
We detected 2 issue regarding the fdb table for ios-xe devices.
First one, the mac-address showed in the web-interface for 1 port it has the same entry repeated many times (see picture attached).
The second issue is related to the way observium collects the fdb table, it only does for vlan 1 and vlan 10 but not for the rest of vlans created on the switch (we are doing the polling in v2c), attached the output for ./poller.php -d -r -m fdb-table -h cisco-iosxe-1706 and the picture as example of vlans present in the switch.
Thanks.
EM
Attachments
Activity
Hi,
I re-did the test:
<<Also in poller I see all available vlans polled for FDB entries>> @Mike
That's not completely true.
For example the switch have configured the following vlans
Vlan 1 |
Vlan 10 |
Vlan 74 |
Vlan 188 |
Vlan 666 |
Vlan 1192 |
Vlan 1501 |
Vlan 1502 |
Vlan 1504 |
Vlan 1506 |
Vlan 1508 |
Vlan 1510 |
Vlan 1512 |
Vlan 1516 |
Vlan 1518 |
Vlan 1520 |
Vlan 1524 |
Vlan 1528 |
Vlan 1627 |
Vlan 2006 |
But the poller, when doing this command:
CMD[/usr/bin/snmpbulkwalk -t '5' -v2c -c ***@1 -Pud -OQUsX -m BRIDGE-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'cisco-iosxe-1706':'161' dot1dTpFdbEntry] |
Is only polling for this Vlans:
Vlan 1 |
Vlan 10 |
Vlan 74 |
Vlan 188 |
And is not polling info for the following vlans:
Vlan 666 |
Vlan 1192 |
Vlan 1501 |
Vlan 1502 |
Vlan 1504 |
Vlan 1506 |
Vlan 1508 |
Vlan 1510 |
Vlan 1512 |
Vlan 1516 |
Vlan 1518 |
Vlan 1520 |
Vlan 1524 |
Vlan 1528 |
Vlan 1627 |
Vlan 2006 |
Is that correct?
Also, when you have a look in :
mysql> select * from vlans_fdb where device_id = 502; |
+------------+-----------+---------+---------+--------------+------------+----------+-----------------+---------+
|
| fdb_id | device_id | vlan_id | port_id | mac_address | fdb_status | fdb_port | fdb_last_change | deleted |
|
+------------+-----------+---------+---------+--------------+------------+----------+-----------------+---------+
|
|
There are no entries for the vlans that are not been polled, only for vlans 1,10,74,188
Is that correct?
Thanks
EM
Hi @mike,
No info in the update-errors.log
root@observium:~# ls -larth /opt/observium/logs/update-errors.log |
-rw-r--r-- 1 root root 1 May 9 15:02 /opt/observium/logs/update-errors.log |
root@observium:~# cat /opt/observium/logs/update-errors.log |
|
|
root@observium:~# |
Attached the output for:
./test_db.php -e > db.json |
Thanks,
EM
I can't reproduce your trouble. Also in poller I see all available vlans polled for FDB entries.
Probably you have local db schema troubles. Show me output of log: /opt/observium/logs/update-errors.log
And make db schema export:
./test_db.php -e > db.json
|
General questions and device support can be discussed in our Discord channel, click here to join.
Please make and attach additional information about the device:
- full snmp dump from device:
snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalksnmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalkIf device not support SNMP version 2c, replace -v2c with -v1.
- If you have problems with discovery or poller processes, please do and attach these debugs:
./discovery.php -d -h <device>./poller.php -d -h <device>
- additionally attach device and/or vendor specific MIB files
This comment is added automatically.
This is Cisco way for store FDB entries for each vlan in separate snmp context.
Each VLAN context accessed as <community>@<vlan_num>
I.e. in this command accessed to FDB table for Vlan1 (only).
snmpbulkwalk -t '5' -v2c -c ***@1 ...Same command run multiple times but with different Vlan context.