<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
Cisco has a feature you can enable called “Interface Index Persistence”:
<div><br>
</div>
<div><a href="https://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/28420-ifIndex-Persistence.html">https://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/28420-ifIndex-Persistence.html</a><br>
<br>
This solves the problem, at least with Cisco gear.</div>
<div><br>
</div>
<div>
<div id="AppleMailSignature"> -mel beckman</div>
<div><br>
On Oct 12, 2018, at 1:33 PM, Naslund, Steve <<a href="mailto:SNaslund@medline.com">SNaslund@medline.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><span>I see this all the time. Especially in module chassis. It seems like sometimes it has to do with when each board goes to a ready state as the system boots. We also see renumbering due to virtual interface and board additions. While you are running
they seem to get the next ifindex available but when you reboot the seem to be in the order they come up or the order they are in the configuration. It is a real pain and some software allows us to rescan a device and other software we have no easy way other
than to delete and the re-add the device. I feel your pain on this one.</span><br>
<span></span><br>
<span>I have no idea why most NMS systems can't seem to understand this and just rescan at a set interval or after an up/down device event.</span><br>
<span></span><br>
<span>Steven Naslund</span><br>
<span>Chicago IL</span><br>
<span></span><br>
<blockquote type="cite"><span>do folk have experience with platforms where ifIndexes are not stable
</span><br>
</blockquote>
<blockquote type="cite"><span>across reboots etc? how do you deal with it? do some of those
</span><br>
</blockquote>
<blockquote type="cite"><span>platforms trap on change?</span><br>
</blockquote>
<span></span><br>
</div>
</blockquote>
</div>
</body>
</html>