Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

provisiond has issues with two IPs on the same ifIndex - I think

Description

Okay, we have a server with a "real" and "virtual" IP address. The ipAddrTable looks like this:

IP-MIB::ipAdEntAddr.64.49.254.23 = IpAddress: 64.49.254.23
IP-MIB::ipAdEntAddr.127.0.0.1 = IpAddress: 127.0.0.1
IP-MIB::ipAdEntAddr.209.61.128.9 = IpAddress: 209.61.128.9
IP-MIB::ipAdEntIfIndex.64.49.254.23 = INTEGER: 2
IP-MIB::ipAdEntIfIndex.127.0.0.1 = INTEGER: 1
IP-MIB::ipAdEntIfIndex.209.61.128.9 = INTEGER: 2

The ifTable looks like:

IF-MIB::ifIndex.1 = INTEGER: 1
IF-MIB::ifIndex.2 = INTEGER: 2
IF-MIB::ifIndex.3 = INTEGER: 3
IF-MIB::ifIndex.4 = INTEGER: 4
IF-MIB::ifDescr.1 = STRING: lo
IF-MIB::ifDescr.2 = STRING: eth0
IF-MIB::ifDescr.3 = STRING: eth1
IF-MIB::ifDescr.4 = STRING: sit0
IF-MIB::ifType.1 = INTEGER: softwareLoopback(24)
IF-MIB::ifType.2 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.3 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.4 = INTEGER: tunnel(131)

so everything looks cool. Unfortunately, the 64.49.254.23 address is never added to the node.

Environment

Operating System: All Platform: PC

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Seth Leger September 12, 2011 at 12:34 PM

Matt believes that this was fixed with the "upsert" pattern that he added to the provisiond code. capsd wasn't updated with the same improvements so that might explain why it appears to happen in bug https://opennms.atlassian.net/browse/NMS-1881#icft=NMS-1881.

Seth Leger August 31, 2011 at 3:25 PM

I experienced the same problem with capsd when trying to scan our AirPort Express in the office. See https://opennms.atlassian.net/browse/NMS-1881#icft=NMS-1881 for related issues.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created June 1, 2010 at 4:14 PM
Updated January 27, 2017 at 4:26 PM
Resolved September 12, 2011 at 12:34 PM

Flag notifications