Details
-
Vendor Bug
-
Resolution: Fixed
-
Major
-
None
-
Professional Edition
Description
After changing OSPF neighbours observium does not poll new information about neighbours. Tried manually use poller.php, but no improve.
On the screenshot you can see that ports view gives info about 4 neighbours (not fully), but neighbours view showes only 3. Also port state view gives false info. Device cli shows "designatedRouter", but observium showes "backupDesignatedRouter".
Only deleting and adding device fixes this issue.
Attachments
Activity
there other reason, device not report correct ifIndex, but IP addresses:
ospfIfIpAddress.10.140.130.7.0 = 10.140.130.7
|
ospfIfIpAddress.10.140.154.24.0 = 10.140.154.24
|
ospfIfIpAddress.10.140.154.26.0 = 10.140.154.26
|
ospfIfIpAddress.10.140.154.103.0 = 10.140.154.103
|
ospfIfIpAddress.10.140.154.136.0 = 10.140.154.136
|
ospfAddressLessIf.10.140.130.7.0 = 0
|
ospfAddressLessIf.10.140.154.24.0 = 0
|
ospfAddressLessIf.10.140.154.26.0 = 0
|
ospfAddressLessIf.10.140.154.103.0 = 0
|
ospfAddressLessIf.10.140.154.136.0 = 0
|
in this case we trying detect correct interface by IP address, but seems one of this addresses not discovered.
For check this send me additionally discovery debug:
./discovery.php -d -h <device>
|
I meant port list is not full, one position in port list is blank 
It should be TenGigabitEthernet0/0/26
Wat? I see exactly four neighbours on your last screenshot. (3 on previous)
We controlled that OSPF neighbours shows correctly, but ports list still not showing all 4 neghbours.
Adding new neighbours fixed in r12528.
About interface states, it's how device report it in snmp. From your debug:
ospfIfState.10.140.130.7.0 = loopback
|
ospfIfState.10.140.154.24.0 = backupDesignatedRouter
|
ospfIfState.10.140.154.26.0 = backupDesignatedRouter
|
ospfIfState.10.140.154.103.0 = backupDesignatedRouter
|
ospfIfState.10.140.154.136.0 = backupDesignatedRouter
|
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 -ObentxU <hostname> .1 > myagent.snmpwalksnmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -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.
Sent e-mail to you.