Config Router

You are here: Home / Juniper / MIB2D_SNMP_INDEX_ASSIGN

MIB2D_SNMP_INDEX_ASSIGN

by

The MIB2D_SNMP_INDEX_ASSIGN message is logged to the system message file whenever the Management Information Base 2 (MIB2D) process cannot assign a Simple Network Management Protocol(SNMP) index for an interface. This article documents an approach to troubleshoot this problem.

When the MIB2D process is unable to assign an SNMP index for an interface it will generate these messages.

For each interface on the system, the MIB2D process assigns an SNMP index to be used in identifying the interface within SNMP. If there is an error assigning the index, an error message is logged. Below are some examples of the message. The SNMP index that the process was trying to assign and the interface where the error occurred are listed.

MIB2D_SNMP_INDEX_ASSIGN: mib2d_iflm_snmp_pointchange: Warning: SNMP Pointchange failed snmpid(73) ifname(lo0.2)
MIB2D_SNMP_INDEX_ASSIGN: mib2d_iflm_snmp_pointchange: Warning: SNMP Pointchange failed snmpid(74) ifname(t3-0/0/1.0)

%DAEMON-3-MIB2D_SNMP_INDEX_ASSIGN: mib2d_iflm_snmp_pointchange: Warning: SNMP Pointchange failed snmpid(1949) ifname(lsi.1050368)

The failure to assign an SNMP index to an interface can be due to memory issues, an invalid configuration, or a software defect.

Perform these steps to determine the cause and resolve the problem (if any):

1. Collect the show command output to help determine the cause of this message.

Capture the output to a file (in case you have to open a technical support case). To do this, configure each SSH client/terminal emulator to log your session.

show log messages
show log mib2d
show log snmpd

2. Analyze the show command output. Look for any related events that occurred at or just before the MIB2D_SNMP_INDEX_ASSIGN message.

  • If the error messages are accompanied by messages indicating memory issues, then these messages are likely due to memory problems.
  • If the error messages are accompanied by kernel errors relating to DFW or by PFE errors, then these messages are likely due to an invalid configuration.
  • Otherwise the message is likely due to a software defect.