> Source: [sk71600](https://support.checkpoint.com/results/sk/sk71600)

# sk71600 - The order of interfaces in the output of 'snmpwalk' changes after each reboot

| Property | Value |
|----------|-------|
| Solution ID | sk71600 |
| Date Created | 2012-04-18 |
| Last Modified | 2026-05-07 |
| Technical Level | Advanced |
| Products | Security Gateway, Security Management Server, Multi-Domain Security Management Server |
| Versions | R82.10, R82, R81.20, R81.10 (EOS), R82.10, R82, R81.20, R82.10, R81 (EOS), R81.10 (EOS), R81 (EOS), R81 (EOS), R81.10 (EOS), R81.20, R82 |
| OS | Gaia |

## Symptoms

- * The order of interfaces in the output of the "`snmpwalk`" command for IF-MIB changes after each reboot.

* Issue occurs only on a server with NICs that use different drivers (e.g., "`e1000`" and "`ixgbe`").

* Example:

  `[Expert@FW]# snmpwalk -v 2c -c public localhost IF-MIB::ifDescr`  
  `IF-MIB::ifDescr.1 = STRING: lo`  
  `IF-MIB::ifDescr.2 = STRING: Exp1-1`  
  `IF-MIB::ifDescr.3 = STRING: Exp1-2`  
  `IF-MIB::ifDescr.4 = STRING: Exp2-1`  
  `IF-MIB::ifDescr.5 = STRING: Exp2-2`  
  `IF-MIB::ifDescr.6 = STRING: Mgmt`  
  `IF-MIB::ifDescr.7 = STRING: Sync`  
  `IF-MIB::ifDescr.8 = STRING: Lan5`  
  `IF-MIB::ifDescr.9 = STRING: Lan6`  
  `IF-MIB::ifDescr.10 = STRING: Lan7`  
  `IF-MIB::ifDescr.11 = STRING: Lan8`  
  `IF-MIB::ifDescr.12 = STRING: Lan1`  
  `IF-MIB::ifDescr.13 = STRING: Lan2`  
  `IF-MIB::ifDescr.14 = STRING: Lan3`  
  `IF-MIB::ifDescr.15 = STRING: Lan4`  
  `IF-MIB::ifDescr.16 = STRING: bond0`  
  `IF-MIB::ifDescr.17 = STRING: bond1`  

  `[Expert@FW]# reboot`  

  `[Expert@FW]# snmpwalk -v 2c -c public localhost IF-MIB::ifDescr`  
  `IF-MIB::ifDescr.1 = STRING: lo`  
  `IF-MIB::ifDescr.2 = STRING: Exp1-1`  
  `IF-MIB::ifDescr.3 = STRING: Exp1-2`  
  `IF-MIB::ifDescr.4 = STRING: Mgmt`  
  `IF-MIB::ifDescr.5 = STRING: Sync`  
  `IF-MIB::ifDescr.6 = STRING: Exp2-1`  
  `IF-MIB::ifDescr.7 = STRING: Exp2-2`  
  `IF-MIB::ifDescr.8 = STRING: Lan5`  
  `IF-MIB::ifDescr.9 = STRING: Lan6`  
  `IF-MIB::ifDescr.10 = STRING: Lan7`  
  `IF-MIB::ifDescr.11 = STRING: Lan8`  
  `IF-MIB::ifDescr.12 = STRING: Lan1`  
  `IF-MIB::ifDescr.13 = STRING: Lan2`  
  `IF-MIB::ifDescr.14 = STRING: Lan3`  
  `IF-MIB::ifDescr.15 = STRING: Lan4`  
  `IF-MIB::ifDescr.16 = STRING: bond0`  
  `IF-MIB::ifDescr.17 = STRING: bond1`  
  `[Expert@FW]#`

## Cause

SNMP relies on "`ifIndex`", which is determined by the Linux kernel.

When several types of NICs are installed, which use different NIC drivers, Linux kernel loads the NIC drivers in a random order (you can see this in the `/var/log/dmesg` file, in the output of "`ip link`" command, or in the output of "`ip addr`" command).

This adversely affects SNMP monitoring by "`IfIndex`" because it will be different after each reboot.

According to [RFC 2863 - Section 3.1.5](https://tools.ietf.org/html/rfc2863#section-3.1.5) the interface numbering may change at a reinitialization of the SNMP Agent (for example during a reboot) and the SNMP management station has to accommodate the interface table whenever the value of "`sysUpTime`" is reset to zero.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content