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

Reminder

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

upgrade

Alarm Handling

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

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).
BGP_1.3.6.1.4.1.2011.5.25.177.1.3.10 hwBgpPeerBackwardTransition

BGP_1.3.6.1.4.1.2011.5.25.177.1.3.10 hwBgpPeerBackwardTransition

Description

BGP/2/HWBACKWARD:OID [oid] The BGP FSM moves from a higher numbered state to a lower numbered state. (InstanceId=[gauge], Afi=[integer], Safi=[integer], PeerType=[integer], PeerRemoteAddr=[binary], InterfaceIndex=[integer], PeerLastError=[octet], PeerState=[integer], PeerUnavaiReason=[gauge], InterfaceName=[octet])

Indicates that this trap was generated when the BGP state machine moved from a higher numbered state, namely, Openconfirm or Established, to a lower numbered state.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.177.1.3.10 Major communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

InstanceId

Indicates the index of the instance to which the peer belongs.

Afi

Indicates the address family:
  • 1: ipv4

  • 2: ipv6

  • 25: vpls

  • 196: l2vpn

Safi

Indicates the sub-address family:
  • 1: unicast

  • 2: multicast

  • 4: mpls

  • 5: mvpn

  • 65: vpls

  • 66: mdt

  • 70: evpn

  • 132: vpn-target

  • 128: vpn

PeerType

Indicates the address type of the peer:
  • 1: ipv4

  • 2: ipv6

PeerRemoteAddr

Indicates the address of the peer.

InterfaceIndex

Indicates the index of the interface.

PeerLastError

Indicates the error code of the BGP Notification when the neighbor relationship is disconnected for the last time.

The value is expressed in the format of [ErrorCode][ErrorSubCode]. [ErrorCode] refers to the error code and [ErrorSubCode] refers to the error subcode. Take the integer 35 as an example, figure 3 is the error code and figure 5 is the error subcode. For detailed information about the error code, refer to BGP Error Code.

If the value is 0, it indicates that no error occurs.

PeerState

Indicates the status of the BGP peer.
  • 1 Idle: indicates that BGP denies any request of entering. This is the initiatory status of BGP.

    Upon receiving a Start event, BGP initiates a TCP connection to the remote BGP peer, starts the ConnectRetry Timer with the initial value, listens for a TCP connection initiated by the remote BGP peer, and changes its state to Connect.

  • 2 Connect: indicates that BGP performs other actions after the TCP connection is set up.
    • If the TCP connection succeeds, BGP stops the ConnectRetry Timer, sends an Open message to the remote peer, and changes its state to OpenSent.

    • If the TCP connection fails, BGP restarts the ConnectRetry Timer with the initial value, continues to listen for a TCP connection initiated by the remote peer, and changes its state to Active.

    • If the ConnectRetry Timer has expired before a TCP connection is established, BGP restarts the timer with the initial value, initiates a TCP connection to the remote BGP peer, and stays in the Connect state.

  • 3 Active: indicates that BGP tries to set up TCP connection. This is the intermediate status of BGP.
    • If the TCP connection succeeds, BGP stops the ConnectRetry Timer, sends an Open message to the remote peer, and changes its state to OpenSent.

    • If the ConnectRetry Timer has expired before a TCP connection is established, BGP restarts the timer with the initial value and changes its state to Connect.

    • If BGP initiates a TCP connection with an unknown IP address, the TCP connection fails. When this occurs, BGP restarts the ConnectRetry Timer with the initial value and stays in the Active state.

  • 4 OpenSent: indicates that BGP has sent one Open message to its peer and waits for the other Open message from the peer.
    • If there are no errors in the Open message received, BGP changes its state to OpenConfirm.

    • If there are errors in the Open message received, BGP sends a Notification message to the remote peer and changes its state to Idle.

    • If the TCP connection fails, BGP restarts the ConnectRetry Timer with the initial value, continues to listen for a TCP connection initiated by the remote peer, and changes its state to Active.

  • 5 OpenConfirm: indicates that BGP waits for a Notification message or a Keepalive message.
    • If BGP receives a Notification message, or the TCP connection fails, BGP changes its state to Idle.

    • If BGP receives a Keepalive message, BGP changes its state to Established.

  • 6 Established: indicates that BGP peers can exchange Update, Notification and Keepalive packets.
    • If BGP receives an Update or a Keepalive message, its state stays in Established.

    • If BGP receives a Notification message, BGP changes its state to Idle.

PeerUnavaiReason

Indicates the reason that the BGP peer down.

  1. Configuration lead peer down: The configuration causes the peer disconnection.

  2. Receive notification: Notification packets are received.

  3. Receive error packet: Error packets are received.

  4. Hold timer expire: The Hold timer expires.

  5. Remote peer not reachable: The remote peer is unreachable.

  6. Direct connect-interface down: The directly connected interface is Down.

  7. Route limit: The number of routes exceeds the upper limit.

InterfaceName

Indicates the name of the interface.

Impact on the System

The BGP neighbor will be disconnected, and the BGP route received from the neighbor will be deleted. The packet forwarding based on the BGP route will fail.

Possible Causes

1. The BGP holdtimer timed out and did not receive the Keepalive packet.

2. BGP received incorrect BGP packets.

3. The BGP neighbor relationship was reset and the neighbor relationship was automatically interrupted.

4. BGP received Notification packets from the neighbor.

Procedure

  1. Run the display bgp peer ipv4-addresses log-info command to check the check the Error field in the command output. You can view the Error Code and Sub Error Code in the received Notification in the form of [ErrorCode][ErrorSubCode].

    • If the error code of the Notification is 1, it indicates that the BGP module receives the packet with incorrect headers. Then, go to Step 23.

    • If the error code of the Notification is 2, it indicates that the BGP module receives the incorrect Open packet. Then, go to Step 23.

    • If the error code of the Notification is 3, it indicates that the BGP module receives the incorrect Update packet. Then, go to Step 23.

    • If the error code of the Notification is 4, it indicates that till the Holdtimer times out, the BGP module does not receive the Keepalive packet. Then, go to Step 4.

    • If the error code of the Notification is 5, it indicates that the finite state machine of the BGP module is faulty. Then, go to Step 23.

    • If the error code of the Notification is 6, go to Step 2.

  2. If the error code of the Notification is 6, it indicates that BGP automatically closes the connection. Then, you need to run the display bgp peer ipv4-address log-info command to view the Notification field and check whether the Notification is sent by the router that generates the trap.

    • If "Send Notification" is displayed, it indicates that the local router actively sends the Notification. Then, go to Step 3.

    • If "Receive Notification" is displayed, it indicates that the local router receives the Notification. Then, go to Step 22.

  3. Search for the reset bgp all and reset bgp ipv4-address commands in the user logs to check whether BGP is reset on the local end; or search for the peer ipv4-address enable command to check whether the peer is enabled in other address families on the local, or parameters for the BGP connection are configured.

    • If so, it indicates that incorrect configurations cause the trap, and thus no action is required. Then, go to Step 24.

    • If not, go to Step 23.

  4. If the error code is 4, it indicates that the BGP disconnection is caused by the timeout of the Holdtimer. Then, you need to check whether the address of the BGP neighbor can be pinged successfully.

    • If so, go to Step 21.

    • If not, go to Step 5.

  5. Run the display ip routing-table command to check whether the Destination/Mask field has the route to the peer address.

    • If so, go to Step 7.

    • If not, go to Step 8.

  6. Run the display acl all command to check whether the router is configured with the ACL that disables TCP port 179.

    • If so, go to Step 9.

    • If not, go to Step 10.

  7. Run the display ip interface brief command to check whether the values of Physical and Protocol fields of the outbound interface are Up.

    • If so, go to Step 23.

    • If not, go to Step 11.

  8. Check the origin of the route with the BGP peer address.

    • If the route is originated from OSPF, go to Step 12.

    • If the route is originated from IS-IS, go to Step 13.

    • Else, go to Step 23.

  9. Delete the ACL that disables the TCP port 179, and check whether the trap BGP_1.3.6.1.4.1.2011.5.25.177.1.3.9 hwBgpPeerEstablished appears later.

    • If so, go to Step 24.

    • If not, go to Step 10.

  10. Check the BGP configuration to see whether loopback interfaces are used to establish BGP peers.

    • If so, go to Step 14.

    • If not, go to Step 15.

  11. Enter the view of the outbound interface, and run the display this command to check whether the interface is shut down.

    • If so, run the undo shutdown command to enable the interface.

    • If not, go to Step 22.

  12. Run the display ospf peer command to check whether the OSPF peer relationship is established.

  13. Run the display isis peer command to check whether the IS-IS peer relationship is established.

  14. Check whether the peer connect-interface is configured for specifying the source address.

    • If so, go to Step 15.

    • If not, go to Step 16.

  15. If BGP is the EBGP neighbor relationship and multiple hops exist between EBGP neighbors, check whether the peer ebgp-max-hop is configured.

    • If so, go to Step 17.

    • If not, go to Step 19.

  16. Configure the peer connect-interface command. The parameter in the command must be the local interface that establishes a connection with the peer. Then, check whether the trap BGP_1.3.6.1.4.1.2011.5.25.177.1.3.9 hwBgpPeerEstablished appears later.

    • If so, go to Step 24.

    • If not, go to Step 23.

  17. Check whether the peer valid-ttl-hops hops command is configured.

    • If so, go to Step 18.

    • If not, go to Step 23.

  18. If the peer valid-ttl-hops hops is configured, check whether the TTL of the packet to the peer ranges from [255-hops+1] to 255.

    • If so, go to Step 23.

    • If not, go to Step 20.

  19. Configure the peer ebgp-max-hop. Then, check whether the trap BGP_1.3.6.1.4.1.2011.5.25.177.1.3.9 hwBgpPeerEstablished appears later.

    • If so, go to Step 24.

    • If not, go to Step 23.

  20. Changed the value of the peer valid-ttl-hops hops and make it within the range from [255-hops+1] to 255. Then, check whether the trap BGP_1.3.6.1.4.1.2011.5.25.177.1.3.9 hwBgpPeerEstablished appears later.

    • If so, go to Step 24.

    • If not, go to Step 23.

  21. Run the the display cpu-usage command to check whether the CPU usage remains 100% in a period.

    • If so, go to Step 23.

    • If not, go to Step 6.

  22. Contact the maintenance personnel of the peer device to check whether BGP is reset on the peer router, the peer is enabled in other address families on the local, and parameters for BGP connection are configured. Then, check whether the trap BGP_1.3.6.1.4.1.2011.5.25.177.1.3.9 hwBgpPeerEstablished appears later.

    • If so, go to Step 24.

    • If not, go to Step 23.

  23. Collect alarm information and configuration information, and then contact technical support personnel.
  24. End.
Translation
Download
Updated: 2019-08-12

Document ID: EDOC1100034065

Views: 138615

Downloads: 42

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next