The number of routes received from the BGP peer exceeded the alarm number. (InstanceId=[InstanceId], Afi=[AddrFamilyAfi], Safi=[AddrFamilySafi], PeerRemoteAddrType=[PeerIPAddrType], PeerRemoteAddr=[PeerIPAddr], MaxRouteNum=[RouteLimitNum], AlarmThreshold=[RouteLimitThreshold])
The number of routes received from the BGP peer exceeded the upper limit allowed.
| Trap Attribute | Description |
|---|---|
Alarm or Event |
Alarm |
Trap Severity |
Critical |
Mnemonic Code |
hwBgpPeerRouteExceed |
Trap OID |
1.3.6.1.4.1.2011.5.25.177.1.3.6 |
MIB |
HUAWEI-BGP-VPN-MIB |
Alarm ID |
0x08790002 |
Alarm Name |
hwBgpPeerRouteExceed |
Alarm Type |
communicationsAlarm |
Raise or Clear |
Raise |
Match trap |
| Parameter | Description |
|---|---|
InstanceId |
Instance ID |
AddrFamilyAfi |
Address family |
AddrFamilySafi |
Sub-address family |
PeerIPAddrType |
Peer address type |
PeerIPAddr |
Peer address |
RouteLimitNum |
Maximum number of routes |
RouteLimitThreshold |
Alarm threshold |
| VB OID | VB Name | VB Index |
|---|---|---|
1.3.6.1.4.1.2011.5.25.177.1.1.5.1.1 |
hwBgpPeerConfigRouteLimitNum |
hwBgpPeerInstanceId hwBgpPeerAddrFamilyAfi hwBgpPeerAddrFamilySafi hwBgpPeerType hwBgpPeerIPAddr |
1.3.6.1.4.1.2011.5.25.177.1.1.5.1.2 |
hwBgpPeerConfigRouteLimitThreshold |
hwBgpPeerInstanceId hwBgpPeerAddrFamilyAfi hwBgpPeerAddrFamilySafi hwBgpPeerType hwBgpPeerIPAddr |
1. If the alarm threshold is set to 100% but alert-only is not specified in the command, the peer relationship is torn down, and all routes received by the peer are deleted.
2. If alert-only is configured, services are not affected.
After this alarm is reported, power-off or reset operations will cause resource reallocation and affect services. Therefore, power-off or reset operations are not allowed.
1. Run the display bgp peer command to check whether the number of routes received from the peer exceeds the upper threshold.
2. Check whether the routes received from the peer are necessary ones.
3. View user log information to check whether a large number of unnecessary routes are received because the local import policy is modified using commands such as peer route-policy, peer ip-prefix, and peer filter-policy.
4. Update the local import policy by using the commands such as the peer route-policy command, the peer ip-prefix command, and the peer filter-policy command to deny the unnecessary routes. Then, check whether the problem is solved. If the fault persists, go to Step 9.
5. Contact the maintenance engineer responsible for the remote device to check whether the routes sent by the remote device to the local device are necessary ones.
6. Request the maintenance engineer responsible for the remote device to modify the policy for importing routes or the policy for advertising routes to withdraw the unnecessary routes. Then, check whether the fault is rectified. If the fault persists, go to Step 9.
7. Request the maintenance engineer responsible for the remote device to configure route aggregation to reduce the number of routes to be advertised. Then, check whether the fault is rectified. If the fault persists, go to Step 9.
8. Increase the maximum number of routes that can be received from the peer. Then, check whether the fault is rectified. If the fault persists, go to Step 9.
9. Collect alarm information and configuration information, and then contact technical support personnel.