OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.202.4.0.1	The number of routes received from a peer has exceeded the alarm threshold.	Error	Major	1.3.6.1.4.1.25506.2.202.4.0.2 (hh3cBgpPeerRouteNumThresholdClear)	ON

Notification triggers

This notification is generated when the number of routes received from a peer has reached the alarm threshold. The alarm threshold refers to the value specified for the percentage-value argument when you execute the peer route-limit command for the peer. The device generates an alarm message when the ratio of M to N exceeds the alarm threshold:

The M argument represents the number of routes received from the peer.

The N argument represents the maximum number of routes that can be received from the peer.

System impact

The impact on the system varies by the alarm threshold configuration of the peer route-limit command:

If the alarm threshold is set to 100% for the peer, the device will be disconnected from the peer or cannot receive new routes from the peer.

If the alarm threshold is set to a value other than 100% for the peer, this issue has no negative impact on the system. This alarm message aims at informing users of the potential impact, that is, the number of routes received from the peer is reaching the upper limit.

Status control

CLI: Use the snmp-agent trap enable bgp [ peer-routethreshold-exceed ] command.

OFF

CLI: Use the undo snmp-agent trap enable bgp [ peer-routethreshold-exceed ] command.

Object

OID (object name)

Description

Index

Type

Value range

(1.3.6.1.4.1.25506.2.202.1.1.4.1.1 (hh3cBgpPeerConfigRouteLimitNum)

Limit on the number of routes that can be received from a peer or peer group.

hh3cBgpPeerInstanceId

hh3cBgpPeerVpnIndex

hh3cBgpPeerAddrFamilyId

hh3cBgpPeerSubAddrFamilyId

hh3cBgpPeerType

hh3cBgpPeerIPAddr

Unsigned32

Standard MIB values.

1.3.6.1.4.1.25506.2.202.1.1.4.1.2 (hh3cBgpPeerConfigRouteLimitThreshold)

Threshold value for the device to generate an alarm notification.

The device generates an alarm notification when the ratio of the number of received routes to the limit on the number of received routes exceeds the threshold.

hh3cBgpPeerInstanceId

hh3cBgpPeerVpnIndex

hh3cBgpPeerAddrFamilyId

hh3cBgpPeerSubAddrFamilyId

hh3cBgpPeerType

hh3cBgpPeerIPAddr

Unsigned32

Unsigned32{(0,100)}

Recommended action

To resolve the issue:

1.Execute the display bgp peer verbose command and view the NLRI statistics and Message statistics fields in the command output to check whether the number of routes received from the peer has reached the alarm threshold:

- If the number of routes received from the peer has reached the alarm threshold, proceed to step 2.

- If the number of routes received from the peer has not reached the alarm threshold, proceed to step 10.

2.Identify whether the overflowing received routes are necessary for forwarding services.

- If the overflowing received routes are necessary, proceed to step 8.

- If the overflowing received routes are not necessary, proceed to step 3.

3.Execute the display current-configuration configuration bgp command to view the current BGP configurations. Check for configurations that cause the local device to receive too many unnecessary routes. Such configurations include peer prefix-list, peer filter-policy, peer as-path-acl, filter-policy, and peer route-policy.

- If the local device has some configurations that affect the route reception policy, proceed to step 4.

- If the local device does not have configurations that affect the route reception policy, proceed to step 5.

4.Edit those configurations to reduce the number of routes received by the local device, and then proceed to step 9.

5.Contact the administrator of the peer to check whether the number of BGP routes sent to the local device is appropriate:

- If the number of BGP routes sent to the local device is appropriate, proceed to step 6.

- If the number of BGP routes sent to the local device is not appropriate, proceed to step 7.

6.Notify the administrator of the BGP peer to reduce the number of BGP routes sent to the local device, and then proceed to step 9. To reduce the number of BGP routes sent to the local device, the administrator can use the following methods:

- Summarize the routes sent to the local device.

- Suppress the advertisement of summaried routes.

7.Notify the administrator of the BGP peer to edit the policy of route distribution to the local device, which prevents the local device from receiving unnecessary routes. Then, proceed to step 9.

8.Use the peer route-limit command to increase the maximum number of BGP routes that can be received from the peer or increase the alarm threshold. Then, proceed to step 9.

9.Check whether the hh3cBgpPeerRouteNumThresholdCleard message is generated on the device.

- If the message is generated, the issue is cleared and the troubleshooting completes.

- If the message is not generated, proceed to step 10.

10.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

hh3cBgpPeerRouteNumThresholdCleard

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.202.4.0.2	The number of routes received from a peer has dropped below the alarm threshold.	Recovery	Major	N/A (N/A)	ON

Notification triggers

This notification is generated when the number of routes received from a peer has dropped below the alarm threshold. The alarm threshold refers to the value specified for the percentage-value argument when you execute the peer route-limit command for the peer. The device generates an alarm message when the ratio of M to N exceeds the alarm threshold:

The M argument represents the number of routes received from the peer.

The N argument represents the maximum number of routes that can be received from the peer.

System impact

No negative impact on the system.

Status control

CLI: Use the snmp-agent trap enable bgp [ peer-routethreshold-clear ] command.

OFF

CLI: Use the undo snmp-agent trap enable bgp [ peer-routethreshold-clear ] command.

Object

OID (object name)

Description

Index

Type

Value range

1.3.6.1.4.1.25506.2.202.1.1.4.1.1 (hh3cBgpPeerConfigRouteLimitNum)

Limit on the number of routes that can be received from a peer or peer group.

hh3cBgpPeerInstanceId

hh3cBgpPeerVpnIndex

hh3cBgpPeerAddrFamilyId

hh3cBgpPeerSubAddrFamilyId

hh3cBgpPeerType

hh3cBgpPeerIPAddr

Unsigned32

Standard MIB values.

1.3.6.1.4.1.25506.2.202.1.1.4.1.2 (hh3cBgpPeerConfigRouteLimitThreshold)

Threshold value for the device to generate an alarm notification.

The device generates an alarm notification when the ratio of the number of received routes to the limit on the number of received routes exceeds the threshold.

hh3cBgpPeerInstanceId

hh3cBgpPeerVpnIndex

hh3cBgpPeerAddrFamilyId

hh3cBgpPeerSubAddrFamilyId

hh3cBgpPeerType

hh3cBgpPeerIPAddr

Unsigned32

Unsigned32{(0,100)}

Recommended action

No action is required.

hh3cBgpPeerRouteExceed

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.202.4.0.3	The number of routes received from a peer has exceeded the upper limit.	Error	Major	1.3.6.1.4.1.25506.2.202.4.0.4 (hh3cBgpPeerRouteExceedClear)	ON

Notification triggers

This notification is generated when the number of routes received from a peer has exceeded the upper limit. The upper limit refers to the value specified for the prefix-number argument when you execute the peer route-limit command for the peer.

System impact

The device will be disconnected from the peer or cannot receive new routes from the peer.

Status control

CLI: Use the snmp-agent trap enable bgp [ peer-routeexceed ] command.

OFF

CLI: Use the undo snmp-agent trap enable bgp [ peer-routeexceed ] command.

Object

OID (object name)

Description

Index

Type

Value range

1.3.6.1.4.1.25506.2.202.1.1.4.1.1 (hh3cBgpPeerConfigRouteLimitNum)

Limit on the number of routes that can be received from a peer or peer group.

hh3cBgpPeerInstanceId

hh3cBgpPeerVpnIndex

hh3cBgpPeerAddrFamilyId

hh3cBgpPeerSubAddrFamilyId

hh3cBgpPeerType

hh3cBgpPeerIPAddr

Unsigned32

Standard MIB values.

1.3.6.1.4.1.25506.2.202.1.1.4.1.2 (hh3cBgpPeerConfigRouteLimitThreshold)

Threshold value for the device to generate an alarm notification.

The device generates an alarm notification when the ratio of the number of received routes to the limit on the number of received routes exceeds the threshold.

hh3cBgpPeerInstanceId

hh3cBgpPeerVpnIndex

hh3cBgpPeerAddrFamilyId

hh3cBgpPeerSubAddrFamilyId

hh3cBgpPeerType

hh3cBgpPeerIPAddr

Unsigned32

Unsigned32{(0,100)}

Recommended action

To resolve this issue:

1.Identify whether the overflowing received routes are necessary for forwarding services.

- If the overflowing received routes are necessary, proceed to step 7.

- If the overflowing received routes are not necessary, proceed to step 2.

2.Execute the display current-configuration configuration bgp command to view the current BGP configurations. Check for configurations that cause the local device to receive too many unnecessary routes. Such configurations include peer prefix-list, peer filter-policy, peer as-path-acl, filter-policy, and peer route-policy.

- If the local device has some configurations that affect the route reception policy, proceed to step 3.

- If the local device does not have configurations that affect the route reception policy, proceed to step 4.

3.Edit those configurations to reduce the number of routes received by the local device, and then proceed to step 8.

4.Contact the administrator of the peer to check whether the number of BGP routes sent to the local device is appropriate:

- If the number of BGP routes sent to the local device is appropriate, proceed to step 5.

- If the number of BGP routes sent to the local device is not appropriate, proceed to step 6.

5.Notify the administrator of the BGP peer to reduce the number of BGP routes sent to the local device, and then proceed to step 8. To reduce the number of BGP routes sent to the local device, the administrator can use the following methods:

- Summarize the routes sent to the local device.

- Suppress the advertisement of summaried routes.

6.Notify the administrator of the BGP peer to edit the policy of route distribution to the local device, which prevents the local device from receiving unnecessary routes. Then, proceed to step 8.

7.Use the peer route-limit command to increase the maximum number of BGP routes that can be received from the peer. Then, proceed to step 8.

8.Check whether the hh3cBgpPeerRouteExceedClear message is generated on the device.

- If the message is generated, the issue is cleared and the troubleshooting completes.

- If the message is not generated, proceed to step 9.

9.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

hh3cBgpPeerRouteExceedClear

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.202.4.0.4	The number of routes received from a peer has dropped below the upper limit.	Recovery	Major	N/A (N/A)	ON

Notification triggers

This notification is generated when the number of routes received from a peer has dropped below the upper limit. The upper limit refers to the value specified for the prefix-number argument when you execute the peer route-limit command for the peer.

System impact

No negative impact on the system.

Status control

CLI: Use the snmp-agent trap enable bgp [ peer-routeexceed-clear ] command.

OFF

CLI: Use the undo snmp-agent trap enable bgp [ peer-routeexceed-clear ] command.

Object

OID (object name)

Description

Index

Type

Value range

1.3.6.1.4.1.25506.2.202.1.1.4.1.1 (hh3cBgpPeerConfigRouteLimitNum)

Limit on the number of routes that can be received from a peer or peer group.

hh3cBgpPeerInstanceId

hh3cBgpPeerVpnIndex

hh3cBgpPeerAddrFamilyId

hh3cBgpPeerSubAddrFamilyId

hh3cBgpPeerType

hh3cBgpPeerIPAddr

Unsigned32

Standard MIB values.

1.3.6.1.4.1.25506.2.202.1.1.4.1.2 (hh3cBgpPeerConfigRouteLimitThreshold)

Threshold value for the device to generate an alarm notification.

The device generates an alarm notification when the ratio of the number of received routes to the limit on the number of received routes exceeds the threshold.

hh3cBgpPeerInstanceId

hh3cBgpPeerVpnIndex

hh3cBgpPeerAddrFamilyId

hh3cBgpPeerSubAddrFamilyId

hh3cBgpPeerType

hh3cBgpPeerIPAddr

Unsigned32

Unsigned32{(0,100)}

Recommended action

No action is required.

hh3cBgpPeerEstablished

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.202.4.0.5	A peer session enters Established state	Recovery	Major	N/A (N/A)	ON

Notification triggers

This notification is generated when the BGP session to a BGP peer is successfully established.

System impact

The BGP session is correctly established.

Status control

CLI: Use the snmp-agent trap enable bgp [ peer-established ] command.

OFF

CLI: Use the undo snmp-agent trap enable bgp [ peer-established ] command.

Object

OID (object name)

Description

Index

Type

Value range

1.3.6.1.4.1.25506.2.202.1.1.2.1.8 (hh3cBgpPeerLastError)

Error code and subcode for the most recent peer connection error.

hh3cBgpPeerInstanceId

hh3cBgpPeerVpnIndex

hh3cBgpPeerAddrFamilyId

hh3cBgpPeerSubAddrFamilyId

hh3cBgpPeerType

hh3cBgpPeerIPAddr

DisplayString

OCTET STRING (2)

1.3.6.1.4.1.25506.2.202.1.1.2.1.4 (hh3cBgpPeerState)

Peer state.

hh3cBgpPeerInstanceId

hh3cBgpPeerVpnIndex

hh3cBgpPeerAddrFamilyId

hh3cBgpPeerSubAddrFamilyId

hh3cBgpPeerType

hh3cBgpPeerIPAddr

INTEGER

idle(1), connect(2), active(3), opensent(4), openconfirm(5), established(6)

Recommended action

No action is required.

hh3cBgpPeerBackwardTransition

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.202.4.0.6	A peer session enters a lower-level state.	Error	Major	1.3.6.1.4.1.25506.2.202.4.0.5 (hh3cBgpPeerEstablished)	ON

Notification triggers

This notification is generated when the state of a BGP peer session transitions from an upper level (for example, Established) to a lower level (for example, OpenConfirm). A typical example is that the BFD session is disconnected. Possible reasons for generating this notification are as follows:

Incorrect BGP configuration.

BGP receives a notification because an error event occurs.

BGP message receiving or sending times out.

The BGP peer IP address is unreachable.

An incorrect BGP packet is received.

The directly connected BGP interface goes down.

The number of BGP routes exceeds the maximum number of BGP routes that can be received.

System impact

The device might not have the associated BGP route to guide traffic forwarding, resulting in service interruption.

Status control

CLI: Use the snmp-agent trap enable bgp [ peer-backward-transition ] command.

OFF

CLI: Use the undo snmp-agent trap enable bgp [ peer-backward-transition ] command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.4.1.25506.2.202.1.1.2.1.8 (hh3cBgpPeerLastError)	Error code and subcode for the most recent peer connection error.	hh3cBgpPeerInstanceId hh3cBgpPeerVpnIndex hh3cBgpPeerAddrFamilyId hh3cBgpPeerSubAddrFamilyId hh3cBgpPeerType hh3cBgpPeerIPAddr	DisplayString	OCTET STRING (2)
1.3.6.1.4.1.25506.2.202.1.1.2.1.4 (hh3cBgpPeerState)	Peer state.	hh3cBgpPeerInstanceId hh3cBgpPeerVpnIndex hh3cBgpPeerAddrFamilyId hh3cBgpPeerSubAddrFamilyId hh3cBgpPeerType hh3cBgpPeerIPAddr	INTEGER	idle(1), connect(2), active(3), opensent(4), openconfirm(5), established(6)
1.3.6.1.4.1.25506.2.202.1.1.2.1.9 (hh3cBgpPeerUnAvaiReason)	Reason why the peer went down.	hh3cBgpPeerInstanceId hh3cBgpPeerVpnIndex hh3cBgpPeerAddrFamilyId hh3cBgpPeerSubAddrFamilyId hh3cBgpPeerType hh3cBgpPeerIPAddr	Unsigned32	Standard MIB values.

Recommended action

To resolve this issue:

1.Execute the display current-configuration configuration bgp command to identify the settings that affect BGP session state.

- If a setting that causes BGP session disconnection exists, execute the relevant command to cancel the setting.

- If BGP uses a loopback interface as the source interface of TCP connections, execute the peer connect-interface or peer source-address command to specify the loopback interface as the source interface for establishing TCP connections.

- To establish an EBGP session to an indirectly connected peer, make sure the peer ebgp-max-hop command is executed on both ends of the session.

- If the peer ttl-security command is configured to enable BGP GTSM on the device, the device receives the BGP packets with a TTL in the range from 255 – the configured hop count + 1 to 255.

- If no settings affect BGP session state, proceed to step 2.

2.Wait for a short period of time to exclude the cause of disconnection by BGP session reset. If the BGP session fails to restore to the Established state within a long period of time, proceed to step 3.

3.Execute the display current-configuration configuration bgp command to check for the configuration of the peer route-limit command, and the BGP/4/BGP_EXCEED_ROUTE_LIMIT log printed by the device.

- If both the configuration and the log exist, the BGP session is disconnected because excessive BGP routes are received. In this case, verify that the maximum number of routes that can be received configured with the peer route-limit command is appropriate:

If the setting is appropriate, notify the administrator of the BGP peer to reduce the number of BGP routes sent to the local end.

If the setting is inappropriate, increase the maximum number of BGP routes that can be received on the local end.

- If the configuration or the log does not exist, or neither of them exists, receiving excessive BGP routes is not the cause for the BGP session disconnection. In this case, proceed to step 4.

4.Execute the display bgp peer log-info command. From the command output, identify the BGP session disconnection cause based on the error code or subcode printed in the Notification Error/SubError field.

- If the error code (Error) is 4, the local end fails to receive any keepalive or update messages from the peer end within the BGP session hold time. This results in BGP session disconnection. If the error code is 5 or 6, the BGP session is disconnected because the TCP connection has an error or the connection is actively disconnected. You can perform troubleshooting by using the following methods:

On the local end, ping the source address used for establishing TCP connections on the BGP peer. If the ping operation fails, execute the display ip routing-table command to identify whether a route is available to the BGP peer. If no routes are available to the BGP peer, troubleshoot IGP route, static route, or direct route settings.

Execute the display memory-threshold command to identify whether the device has reached the memory usage threshold. If the memory usage threshold is reached, proceed to step 5.

Execute the display cpu-usage command to identify whether the CPU usage is too high. If the CPU usage is too high, proceed to step 5.

Execute the display acl all command to identify whether a rule exists that denies port bgp or 179. If such an ACL exists, delete the ACL.

Execute the display interface command to identify whether the output interface associated with the next hop of the route to the BGP peer is up. If the output interface is down, execute the undo shutdown command to bring up the interface in the view of the interface. If the interface fails to be brought up, or the interface is up but the notification persists, proceed to step 5.

- If the error code (Error) is 1 or 3, the device has received wrong BGP packets. Proceed to step 5.

5.If the issue persists, collect alarm information, configuration data, and the output information from the previous commands, and then contact H3C Support for help.

hh3cBgpVrfRouteNumReachThreshold

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.202.4.0.7	The number of VPN routes received from peers has exceeded the alarm threshold.	Error	Major	1.3.6.1.4.1.25506.2.202.4.0.8 (hh3cBgpVrfRouteNumReachThresholdClear)	ON

Notification triggers

This notification is generated when the number of routes received from peers in an address family of a VPN instance has exceeded the alarm threshold.

System impact

The number of routes received by the VPN instance has exceeded the alarm threshold and the VPN instance stops receiving new routes.

Status control

CLI: Use the snmp-agent trap enable bgp [ vrfroutenum-threshold ] command.

OFF

CLI: Use the undo snmp-agent trap enable bgp [ vrfroutenum-threshold ] command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.4.1.25506.2.202.1.2.1.1.1 (hh3cBgpVpnRouteType)	Route type.	hh3cBgpVpnRouteType hh3cBgpVpnInstName hh3cBgpVpnAddressFamily	Unsigned32	Standard MIB values.
1.3.6.1.4.1.25506.2.202.1.2.1.1.2 (hh3cBgpVpnInstName)	VPN instance name.	hh3cBgpVpnRouteType hh3cBgpVpnInstName hh3cBgpVpnAddressFamily	OCTET STRING	0..31
1.3.6.1.4.1.25506.2.202.1.2.1.1.3 (hh3cBgpVpnAddressFamily)	Address family.	hh3cBgpVpnRouteType hh3cBgpVpnInstName hh3cBgpVpnAddressFamily	Unsigned32	Standard MIB values.
1.3.6.1.4.1.25506.2.202.1.2.1.1.4 (hh3cBgpVpnCurrRouteNum)	Number of VPN routes in the BGP routing table.	hh3cBgpVpnRouteType hh3cBgpVpnInstName hh3cBgpVpnAddressFamily	Unsigned32	Standard MIB values.
1.3.6.1.4.1.25506.2.202.1.2.1.1.5 (hh3cBgpVpnThresholdValue)	Threshold value for the device to generate an alarm notification. The device generates an alarm notification when the ratio of the number of VPN routes to the maximum number of VPN routes exceeds the threshold.	hh3cBgpVpnRouteType hh3cBgpVpnInstName hh3cBgpVpnAddressFamily	Unsigned32	Standard MIB values.

Recommended action

To resolve this issue:

1.Use the display bgp routing-table { ipv4 | ipv6 } vpn-instace command to check whether the number of routes received from peers in the VPN instance has reached the alarm threshold.

- If the alarm threshold is reached, proceed to step 2.

- If the alarm threshold is not reached, proceed to step 10.