BGP/2/hwBgpPeerRouteExceed_active

Message

BGP/2/hwBgpPeerRouteExceed_active: 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])

Description

The number of routes received from the BGP peer exceeded the upper limit allowed.

Parameters

Parameter Name	Parameter Meaning
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

Possible Causes

The number of routes received from the BGP peer who configured with route-limit, exceeds the maximum value allowed.

Procedure

1. Run the display bgp peer command to check whether the number of routes received from the peer exceeds the upper threshold.

If the number of routes received from the peer exceeds the upper threshold, go to Step 2.
If the number of routes received from a peer does not exceed the upper threshold, go to Step 9.

2. Check whether the routes received from the peer are necessary ones.

If the routes received from the peer are necessary ones, go to Step 8.
If the routes received from the peer are not necessary ones, go to Step 3.

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.

If a large number of unnecessary routes are received because the local import policy is modified, go to Step 4.
If a large number of unnecessary routes are received due to other reasons, go to Step 5.

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.

If the routes sent by the remote device to the local device are necessary ones, go to Step 7.
If the routes sent by the remote device to the local device are not necessary ones, go to Step 6.

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.