No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Alarm Handling

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
SINDEX_1. hwNetStreamIndexUsedUp

SINDEX_1. hwNetStreamIndexUsedUp


SINDEX/3/IFINDEX: OID [oid] ShortIFIndex is used up.

When the total 65535 indexes were allocated but more indexes were needed for the creation of new interfaces, the trap was generated.


Alarm ID Alarm Severity Alarm Type Minor equipmentAlarm(5)


Name Meaning


Indicates the MIB object ID of the alarm.

Impact on the System

When the Netstream module sends flow information to the NMS, the flow information contains the 16-bit index of an interface. Then, the NMS resolutes the interface name according to the index. In normal situations, a 16-bit index is allocated to each interface, and the total 65535 interfaces will obtain indexes. If the number of interfaces is more than 65535, the traffic statistics sent to the NMS cannot carry the 16-bit index. As a result, the NMS fails to resolute the interface name according to the index and therefore cannot charge and monitor the network normally.

Possible Causes

The interfaces were more than the interface index resources that could be allocated. The index resources were used up.


  1. Run the display ip interface brief command to check the logical interface that is in the Down state. Run the undo interface command to delete the unwanted logical interface.
  2. Re-create an interface to be used, and check whether the trap is displayed.

    • If so, go to Step 3.
    • If not, go to Step 4.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information


Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 106777

Downloads: 61

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next