Problem with SNMP multiple IPs bound to an interface

Post general support questions here that do not specifically fall into the Linux or Windows categories.

Moderators: Developers, Moderators

Post Reply
User avatar
mahuani
Cacti User
Posts: 72
Joined: Tue Nov 01, 2005 2:10 pm
Location: Lafayette, LA
Contact:

Problem with SNMP multiple IPs bound to an interface

Post by mahuani »

On one of my boxes I have about half a dozen IPs bound to one NIC. The "main" IP is listed first when the it I do a verbose query against it.

Code: Select all

+ Located input field 'ifIP' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.2.1.4.20.1.2'
+ Found item [ifIP='127.0.0.1'] index: 1 [from regexp oid parse]
+ Found item [ifIP='***.***.***.**1'] index: 2 [from regexp oid parse]
+ Found item [ifIP='***.***.***.**2'] index: 2 [from regexp oid parse]
+ Found item [ifIP='***.***.***.**3'] index: 2 [from regexp oid parse]
+ Found item [ifIP='***.***.***.**4'] index: 2 [from regexp oid parse]
This would seem all fine and dandy, but... My traffic graphs are not returning the proper information.

Cacti wants to use the last IP for the index i.e ***.***.***.**4 . I can verify that the traffic being reported for that interface is incorrect as I'm also graphing the switch the server is uplinked to.

My question(s):

1. Does Cacti choose the IP it uses when there a multiple IP bound to an interface?

2. If Cacti is responsible, can I tell it to use the first IP?

3. If it Cacti isn't responsible, anyone know a workaround?
User avatar
BSOD2600
Cacti Moderator
Posts: 12171
Joined: Sat May 08, 2004 12:44 pm
Location: USA

Post by BSOD2600 »

Cacti pulls data from the specific ifIndex number. Since all of your IPs are reporting from the same Index (you can verify this with an snmpwalk), it's going to be a problem. I'm not sure if a way around this.
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest