IFNET_1.3.6.1.4.1.2011.5.25.41.4.5 hwIfMonitorInputRateRising

Description

IFNET/4/INBWRATEEXCEED: OID [oid] Interface input flow bandwidth usage exceeded the trap threshold. (Interface=[INTEGER], BandWidthUsage=[INTEGER], TrapThreshold=[INTEGER], InterfaceName=[STRING])

The trap was generated when the percentage of the rate of received traffic to the total bandwidth on an interface was greater than the threshold.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.41.4.5	Warning	other(1)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
Interface	Indicates the interface index.
BandWidthUsage	Indicates bandwidth usage.
TrapThreshold	Indicates the trap threshold of bandwidth usage.
InterfaceName	Indicates the interface name.

Impact on the System

When traffic rate is approximate to the maximum interface bandwidth, service packets may be dropped.

Possible Causes

The rate of traffic received by the interface was too large.

Procedure

Run the display this interface command on the interface to check whether the traffic threshold is too low. The threshold range is specified by users according to actual services.
- If so, go to Step 2.
- If not, go to Step 3.
Run the trap-threshold input-rate threshold_value command to reset the threshold and then check whether the alarm is cleared.
- If so, go to Step 7.
- If not, go to Step 3.
Run the display this interface command in the interface view to check the number and types of packets on the interface. Determine whether the packet sending and receiving is abnormal due to a failure such as loop.
- If so, go to Step 4.
- If not, go to Step 5.
Find out the abnormal packets and eliminate the impact of abnormal packets. Check whether the alarm is cleared.
- If so, go to Step 7.
- If not, go to Step 5.
Expand capacity in any of the following ways:
- Configure an Eth-Trunk to load balance traffic.
- Migrate some services to idle devices.
- Use the link with higher bandwidth to transmit service packets.
After the operation, check whether the alarm is cleared.
- If so, go to Step 7.
- If not, go to Step 6.
Collect trap messages, log messages, and configurations, and then contact the technical support personnel.
End.

Related Information

IFNET_1.3.6.1.4.1.2011.5.25.41.4.6 hwIfMonitorInputRateResume