IfIndex persistence (was "IfIndex persistence across reboots on BSD box")

Amit Dor-Shifer <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
I'm referring to "IfIndex persistence across reboots on BSD box", dated 
*14 Mar 2008.

*I'm working on a similar issue. On my host, ifIndex of "lo" and "eth0" 
got swapped, assumed to be related to a kernel upgrade (2.6.22 -> 2.6.25).
I'm asked to explore alternatives for fixating ifIndex, not via the use 
of ifAlias.

I'm wondering whether the use of the 'override' directive of snmpd.conf 
can assist here. Something like this:

# override ifIndex.1 to be '2' and ifIndex.2 to be '1'
override .1.3.6.1.2.1.2.2.1.1.1 integer 2
override .1.3.6.1.2.1.2.2.1.1.2 integer 1

Is this total profanity, or can expect this to work, and in-accordance 
with the rest of the IF-MIB implementation?

Amit
*
*

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.