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

E9000 Server V100R001 HMM Alarm Handling 19

This document describes E9000 server alarms in terms of the meaning, impact on the system, possible causes, and solutions.
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

BGP

BGP_1.3.6.1.2.1.15.0.1 bgpEstablishedNotification

Description

The BGP FSM enters the Established state. (BgpPeerRemoteAddr=[BgpPeerRemoteAddrValue], BgpPeerLastError=[BgpPeerLastErrorValue], BgpPeerState=[BgpPeerStateValue])

The BGP peer relationship is established.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Critical

Mnemonic Code

bgpEstablishedNotification

Trap OID

1.3.6.1.2.1.15.0.1

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

BgpPeerRemoteAddr

Peer address

BgpPeerLastError

Value of the Error Code field in the Notification packet generated when the peer relationship is interrupted last time

BgpPeerState

Status of the BGP peer relationship

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.15.3.1.7

bgpPeerRemoteAddr

bgpPeerRemoteAddr;

1.3.6.1.2.1.15.3.1.14

bgpPeerLastError

bgpPeerRemoteAddr;

1.3.6.1.2.1.15.3.1.2

bgpPeerState

bgpPeerRemoteAddr;

Impact on the System

The BGP peer relationship is established.

Possible Causes

Cause: The BGP peer relationship is established.

Procedure
  • This trap message is informational only, and no action is required.

BGP_1.3.6.1.2.1.15.0.2 bgpBackwardTransNotification

Description

The BGP FSM moves from a higher numbered state to a lower numbered state. (BgpPeerRemoteAddr=[BgpPeerRemoteAddrValue], BgpPeerLastError=[BgpPeerLastErrorValue], BgpPeerState=[BgpPeerStateValue])

The BGP FSM moved from a higher numbered state, namely, Openconfirm or Established, to a lower numbered state.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Critical

Mnemonic Code

bgpBackwardTransNotification

Trap OID

1.3.6.1.2.1.15.0.2

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

BgpPeerRemoteAddr

Peer address

BgpPeerLastError

Value of the Error Code field in the Notification packet generated when the peer relationship is interrupted last time

BgpPeerState

Status of the BGP peer relationship

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.15.3.1.7

bgpPeerRemoteAddr

bgpPeerRemoteAddr;

1.3.6.1.2.1.15.3.1.14

bgpPeerLastError

bgpPeerRemoteAddr;

1.3.6.1.2.1.15.3.1.2

bgpPeerState

bgpPeerRemoteAddr;

Impact on the System

The BGP peer relationship is interrupted, the route from the local device to the remote device is unreachable, and BGP forwarding services are interrupted.

Possible Causes

Cause 1: Configuration lead peer down.

Cause 2: Receive notification.

Cause 3: Receive error packet.

Cause 4: Hold timer expire.

Cause 5: Remote peer not reachable.

Cause 6: Direct connect-interface down.

Cause 7: Route limit.

Procedure
  • Cause 1: Configuration lead peer down.
    1. Check whether the BGP peer relationship is interrupted because of the improper configurations of the local device.
      • If the configurations of the local device are improper, go to Step 2.
      • If the configurations of the local device are proper, go to Step 3.
    2. Delete the configurations that cause the interruption of the peer relationship.
    3. Check whether the BGP connection is reset. If the BGP connection is reset, wait for a while and then check whether the BGP connection is re-established.
    4. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
  • Cause 2: Receive notification.
    1. Run the display bgp peer ip-address log-info command to check the Notification packet sent by the local device when the BGP peer relationship is interrupted.
      • If the value of the Error Code field in the Notification packet is 4, no Keepalive packet is received after the BGP hold timer expires. Then, go to Step 3.
      • If the value of the Error Code field in the Notification packet is 5, the BGP FSM is incorrect. Then, go to Step 17.
      • If the value of the Error Code field in the Notification packet is 6, the local device initiatively closes the BGP connection. Then, go to Step 2.
    2. Run the display bgp peer ip-address log-info command to check whether the Notification packet is sent by the device that generates the alarm.
      • If the Notification packet is sent by the device that generates the alarm, go to Step 3.
      • If the Notification packet is not sent by the device that generates the alarm, go to Step 4.
    3. Run the ping command to check whether the local device can successfully ping its peer.
      • If the local device pings its peer successfully, go to Step 4.
      • If the local device fails to ping its peer, go to Step 5.
    4. Run the display cpu command to check whether the CPU usage is too high.
      • If the CPU usage is too high, go to Step 17.
      • If the CPU usage is within the normal range, go to Step 6.
    5. Run the display ip routing-table command to check whether the route from the local device to its peer exists in the routing table.
      • If the route from the local device to its peer exists in the routing table, go to Step 7.
      • If the route from the local device to its peer does exist in the routing table, go to Step 8.
    6. Run the display acl command to check whether the device is configured with an ACL used to disable TCP port 179.
      • If the device is configured with such an ACL, delete the ACL.
      • If the device is not configured with such an ACL, go to Step 9.
    7. Run the display interface command to check whether the outbound interface of the route is Up.
      • If the outbound interface of the route is Up, go to Step 17.
      • If the outbound interface of the route is not Up, go to Step 10.
    8. Check the configuration of the local device and the origin of the route from the local device to its peer.
      • If the route is imported from OSPF, go to Step 11.
      • If the route is imported from IS-IS, go to Step 12.
    9. View the BGP configuration of the local device to check whether a loopback interface is used to establish the BGP connection.
      • If a loopback interface is used to establish the BGP connection, go to Step 13.
      • If no loopback interface is used to establish the BGP connection, go to Step 14.
    10. Check whether the shutdown command is run on the directly connected interface.
      • If the shutdown command is run on the interface, run the undo shutdown command is run on the interface. If the alarm is not cleared, go to Step 13.
      • If the shutdown command is not run on the interface. go to Step 17.
    11. Run the display ospf peercommand to check whether the OSPF peer relationship is established.
      • If the OSPF peer relationship is established, go to Step 17.
      • If no OSPF peer relationship is established, see the precessing steps in OSPF_1.3.6.1.2.1.14.16.2.2 ospfNbrStateChange.
    12. Run the display isis peer command to check whether the IS-IS peer relationship is established.
      • If the IS-IS peer relationship is established, go to Step 17.
      • If no IS-IS peer relationship is established, see the precessing steps in ISIS_1.3.6.1.3.37.2.0.17 isisAdjacencyChange.
    13. Check whether the source address used for initiating the BGP connection is specified.
      • If the source address is specified, go to Step 14.
      • If no source address is specified, run the peer connect-interface command to configure a source address used for initiating the BGP connection.
    14. If the BGP peer relationship is a multi-hop EBGP peer relationship, check whether the peer ebgp-max-hop command is run.
      • If the peer ebgp-max-hop command is run, go to Step 15.
      • If the peer ebgp-max-hop command is not run, run the peer ebgp-max-hop command.
    15. If the peer valid-ttl-hops hops command is run, check whether the TTL of the packet received from the remote end is within the range [255-hops+1, 255].
      • If the TTL of the packet is within the range, go to Step 14.
      • If the TTL of the packet is beyond the range, run the peer valid-ttl-hops hops command to ensure that the TTL of the packet sent to the remote peer is within the range.
    16. Contact the maintenance engineer responsible for the peer device to check whether BGP is reset on the peer device, whether the peer enable command is run in the view of another address family view on the local device, and whether BGP connection parameters are set. If any of the operations is performed, wait for a period of time, and then check whether the alarm is cleared.
    17. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
  • Cause 3: Receive error packet.
    1. Run the display bgp peer ip-address log-info command to check the Notification packet sent by the local device when the BGP peer relationship is interrupted.
      • If the value of the Error Code field in the Notification packet is 1, a packet with an error header has been received.
      • If the value of the Error Code field in the Notification packet is 2, an error Open packet has been received.
      • If the value of the Error Code field in the Notification packet is 3, an error Update packet has been received.
    2. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
  • Cause 4: Hold timer expire.
    1. Run the ping command to check whether the local device can successfully ping its peer.
      • If the local device pings its peer successfully, go to Step 2.
      • If the local device fails to ping its peer, go to Step 3.
    2. Run the display cpu command to check whether the CPU usage is too high.
      • If the CPU usage is too high, go to Step 15.
      • If the CPU usage is within the normal range, go to Step 4.
    3. Run the display ip routing-table command to check whether the route from the local device to its peer exists in the routing table.
      • If the route from the local device to its peer exists in the routing table, go to Step 5.
      • If the route from the local device to its peer does not exist in the routing table, go to Step 6.
    4. Run the display acl command to check whether the device is configured with an ACL used to disable TCP port 179.
      • If the device is configured with such an ACL, delete the ACL.
      • If the device is not configured with such an ACL, go to Step 7.
    5. Run the display interface command to check whether the outbound interface of the route is Up.
      • If the outbound interface of the route is Up, go to Step 15.
      • If the outbound interface of the route is not Up, go to Step 8.
    6. Check the configuration of the local device and the origin of the route from the local device to its peer.
      • If the route is imported from OSPF, go to Step 9.
      • If the route is imported from IS-IS, go to Step 10.
    7. Check the BGP configuration of the local device to check whether a loopback interface is used to establish the BGP connection.
      • If a loopback interface is used to establish the BGP connection, go to Step 11.
      • If no loopback interface is used to establish the BGP connection, go to Step 12.
    8. Check whether the shutdown command is run on the directly connected interface.
      • If the shutdown command is run on the interface, run the undo shutdown command is run on the interface. If the alarm is not cleared, go to Step 11.
      • If the shutdown command is not run on the interface, go to Step 15.
    9. Run the display ospf peercommand to check whether the OSPF peer relationship is established.
      • If the OSPF peer relationship is established, go to Step 15.
      • If no OSPF peer relationship is established, see the precessing steps in OSPF_1.3.6.1.2.1.14.16.2.2 ospfNbrStateChange.
    10. Run the display isis peer command to check whether the IS-IS peer relationship is established.
      • If the IS-IS peer relationship is established, go to Step 15.
      • If no IS-IS peer relationship is established, see the precessing steps in ISIS_1.3.6.1.3.37.2.0.17 isisAdjacencyChange.
    11. Check whether the source address used for initiating the BGP connection is specified.
      • If the source address is specified, go to Step 12.
      • If no source address is specified, run the peer connect-interface command to configure a source address used for initiating the BGP connection.
    12. If the BGP peer relationship is a multi-hop EBGP peer relationship, check whether the peer ebgp-max-hop command is run.
      • If the peer ebgp-max-hop command is run, go to Step 13.
      • If the peer ebgp-max-hop command is not run, run the peer ebgp-max-hop command.
    13. If the peer valid-ttl-hops hops command is run, check whether the TTL of the packet received from the remote end is within the range [255-hops+1, 255].
      • If the TTL of the packet is within the range, go to Step 14.
      • If the TTL of the packet is beyond the range, run the peer valid-ttl-hops hops command to ensure that the TTL of the packet sent to the remote peer is within the range.
    14. Contact the maintenance engineer responsible for the peer device to check whether BGP is reset on the peer device, whether the peer enable command is run in the view of another address family view on the local device, and whether BGP connection parameters are set. If any of the operations is performed, wait for a period of time, and then check whether the alarm is cleared.
    15. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
  • Cause 5: Remote peer not reachable.
    1. Run the ping command to check whether the local device can successfully ping its peer.
      • If the local device pings its peer successfully, go to Step 2.
      • If the local device fails to ping its peer, go to Step 3.
    2. Run the display cpu command to check whether the CPU usage is too high.
      • If the CPU usage is too high, go to Step 15.
      • If the CPU usage is within the normal range, go to Step 4.
    3. Run the display ip routing-table command to check whether the route from the local device to its peer exists in the routing table.
      • If the route from the local device to its peer exists in the routing table, go to Step 5.
      • If the route from the local device to its peer does not exist in the routing table, go to Step 6.
    4. Run the display acl command to check whether the device is configured with an ACL used to disable TCP port 179.
      • If the device is configured with such an ACL, delete the ACL.
      • If the device is not configured with such an ACL, go to Step 7.
    5. Run the display interface command to check whether the outbound interface of the route is Up.
      • If the outbound interface of the route is Up, go to Step 15.
      • If the outbound interface of the route is not Up, go to Step 8.
    6. Check the configuration of the local device and the origin of the route from the local device to its peer.
      • If the route is imported from OSPF, go to Step 9.
      • If the route is imported from IS-IS, go to Step 10.
    7. Check the BGP configuration of the local device to check whether a loopback interface is used to establish the BGP connection.
      • If a loopback interface is used to establish the BGP connection, go to Step 11.
      • If no loopback interface is used to establish the BGP connection, go to Step 12.
    8. Check whether the shutdown command is run on the directly connected interface.
      • If the shutdown command is run on the interface, run the undo shutdown command is run on the interface. If the alarm is not cleared, go to Step 11.
      • If the shutdown command is not run on the interface, go to Step 15.
    9. Run the display ospf peercommand to check whether the OSPF peer relationship is established.
      • If the OSPF peer relationship is established, go to Step 15.
      • If no OSPF peer relationship is established, see the precessing steps in OSPF_1.3.6.1.2.1.14.16.2.2 ospfNbrStateChange.
    10. Run the display isis peer command to check whether the IS-IS peer relationship is established.
      • If the IS-IS peer relationship is established, go to Step 15.
      • If no IS-IS peer relationship is established, see the precessing steps in ISIS_1.3.6.1.3.37.2.0.17 isisAdjacencyChange.
    11. Check whether the source address used for initiating the BGP connection is specified.
      • If the source address is specified, go to Step 12.
      • If no source address is specified, run the peer connect-interface command to configure a source address used for initiating the BGP connection.
    12. If the BGP peer relationship is a multi-hop EBGP peer relationship, check whether the peer ebgp-max-hop command is run.
      • If the peer ebgp-max-hop command is run, go to Step 13.
      • If the peer ebgp-max-hop command is not run, run the peer ebgp-max-hop command.
    13. If the peer valid-ttl-hops hops command is run, check whether the TTL of the packet received from the remote end is within the range [255-hops+1, 255].
      • If the TTL of the packet is within the range, go to Step 14.
      • If the TTL of the packet is beyond the range, run the peer valid-ttl-hops hops command to ensure that the TTL of the packet sent to the remote peer is within the range.
    14. Contact the maintenance engineer responsible for the peer device to check whether BGP is reset on the peer device, whether the peer enable command is run in the view of another address family view on the local device, and whether BGP connection parameters are set. If any of the operations is performed, wait for a period of time, and then check whether the alarm is cleared.
    15. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
  • Cause 6: Direct connect-interface down.
    1. Check whether the shutdown command is run on the directly connected interface.
      • If the shutdown command is run on the interface, run the undo shutdown command is run on the interface.
      • If the shutdown command is not run on the interface, go to Step 2.
    2. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
  • Cause 7: Route limit.
    1. Check whether the peer route-limit command is run and whether the number of routes exceeds the upper threshold.
      • If the command is run and the number of received routes exceeds the upper threshold, go to Step 2.
      • If the command is not run or the command is run but the number of received routes does not exceed the upper threshold, go to Step 3.
    2. Check whether the peer route-limit command is necessary. If the command is necessary, reduce routes to ensure that the number of routes is smaller than the upper threshold.
    3. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.

BGP_1.3.6.1.2.1.15.7.1 bgpEstablished

Description

The BGP FSM enters the Established state. (BgpPeerRemoteAddr=[PeerIpv4Ipv6Addr], BgpPeerLastError=[PeerLastError], BgpPeerState=[PeerState], LocalIfName=[LocalIfName], Reason=[Reason])

The BGP peer relationship is established.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

ESTABLISHED

Trap OID

1.3.6.1.2.1.15.7.1

Alarm ID

0x0879000f

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

BGP_1.3.6.1.2.1.15.7.2 bgpBackwardTransition

Parameters

Parameter

Description

BgpPeerRemoteAddr

Peer address

BgpPeerLastError

Value of the Error Code field in the Notification packet generated when the peer relationship is interrupted last time

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

BgpPeerState

Status of the BGP peer relationship

LocalIfName

Local interface name

Reason

Reason why the peer relationship is interrupted

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.15.3.1.14

bgpPeerLastError

bgpPeerRemoteAddr;

1.3.6.1.2.1.15.3.1.2

bgpPeerState

bgpPeerRemoteAddr;

Impact on the System

The BGP peer relationship is established.

Possible Causes

Cause: The BGP peer relationship is established.

Procedure
  • This trap message is informational only, and no action is required.

BGP_1.3.6.1.2.1.15.7.2 bgpBackwardTransition

Description

The BGP FSM moves from a higher numbered state to a lower numbered state. (BgpPeerRemoteAddr=[PeerIpv4Ipv6Addr], BgpPeerLastError=[PeerLastError], BgpPeerState=[PeerState], LocalIfName=[LocalIfName], Reason=[Reason])

The BGP FSM moved from a higher numbered state, namely, Openconfirm or Established, to a lower numbered state.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

BACKWARD

Trap OID

1.3.6.1.2.1.15.7.2

Alarm ID

0x0879000f

Alarm Type

communicationsAlarm

Raise or Clear

Clear

Match trap

BGP_1.3.6.1.2.1.15.7.1 bgpEstablished

Parameters

Parameter

Description

BgpPeerRemoteAddr

Peer address

BgpPeerLastError

Value of the Error Code field in the Notification packet generated when the peer relationship is interrupted last time

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

BgpPeerState

Status of the BGP peer relationship

LocalIfName

Local interface name

Reason

Reason why the peer relationship is interrupted

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.15.3.1.14

bgpPeerLastError

bgpPeerRemoteAddr;

1.3.6.1.2.1.15.3.1.2

bgpPeerState

bgpPeerRemoteAddr;

Impact on the System

The BGP peer relationship is interrupted, the route from the local device to the remote device is unreachable, and BGP forwarding services are interrupted.

Possible Causes

Cause 1: Configuration lead peer down.

Cause 2: Receive notification.

Cause 3: Receive error packet.

Cause 4: Hold timer expire.

Cause 5: Remote peer not reachable.

Cause 6: Direct connect-interface down.

Cause 7: Route limit.

Procedure
  • Cause 1: Configuration lead peer down.
    1. Check whether the BGP peer relationship is interrupted because of the improper configurations of the local device.
      • If the configurations of the local device are improper, go to Step 2.
      • If the configurations of the local device are proper, go to Step 3.
    2. Delete the configurations that cause the interruption of the peer relationship.
    3. Check whether the BGP connection is reset. If the BGP connection is reset, wait for a while and then check whether the BGP connection is re-established.
      • If the BGP connection is not reset, go to Step 4.
      • If the BGP connection is reset, wait for a while and then check whether the BGP connection is re-established. If the BGP connection is not re-established, go to Step 4.
    4. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
  • Cause 2: Receive notification.
    1. Run the display bgp peer ip-address log-info command to check the Notification packet sent by the local device when the BGP peer relationship is interrupted.
      • If the value of the Error Code field in the Notification packet is 4, no Keepalive packet is received after the BGP hold timer expires. Then, go to Step 3.
      • If the value of the Error Code field in the Notification packet is 5, the BGP FSM is incorrect. Then, go to Step 17.
      • If the value of the Error Code field in the Notification packet is 6, the local device initiatively closes the BGP connection. Then, go to Step 2.
    2. Run the display bgp peer ip-address log-info command to check whether the Notification packet is sent by the router that generates the alarm.
      • If the Notification packet is sent by the router that generates the alarm, go to Step 3.
      • If the Notification packet is not sent by the router that generates the alarm, go to Step 4.
    3. Run the ping command to check whether the local device can successfully ping its peer.
      • If the local device pings its peer successfully, go to Step 4.
      • If the local device fails to ping its peer, go to Step 5.
    4. Run the display cpu command to check whether the CPU usage is too high.
      • If the CPU usage is too high, go to Step 17.
      • If the CPU usage is within the normal range, go to Step 6.
    5. Run the display ip routing-table command to check whether the route from the local device to its peer exists in the routing table.
      • If the route from the local device to its peer exists in the routing table, go to Step 7.
      • If the route from the local device to its peer does exist in the routing table, go to Step 8.
    6. Run the display acl command to check whether the router is configured with an ACL used to disable TCP port 179.
      • If the router is configured with such an ACL, delete the ACL.
      • If the router is not configured with such an ACL, go to Step 9.
    7. Run the display interface command to check whether the outbound interface of the route is Up.
      • If the outbound interface of the route is Up, go to Step 17.
      • If the outbound interface of the route is not Up, go to Step 10.
    8. Check the configuration of the local device and the origin of the route from the local device to its peer.
      • If the route is imported from OSPF, go to Step 11.
      • If the route is imported from IS-IS, go to Step 12.
    9. View the BGP configuration of the local device to check whether a loopback interface is used to establish the BGP connection.
      • If a loopback interface is used to establish the BGP connection, go to Step 13.
      • If no loopback interface is used to establish the BGP connection, go to Step 14.
    10. Check whether the shutdown command is run on the directly connected interface.
      • If the shutdown command is run on the interface, run the undo shutdown command is run on the interface. If the alarm is not cleared, go to Step 13.
      • If the shutdown command is not run on the interface. go to Step 17.
    11. Run the display ospf peercommand to check whether the OSPF peer relationship is established.
      • If the OSPF peer relationship is established, go to Step 17.
      • If no OSPF peer relationship is established, see the precessing steps in OSPF_1.3.6.1.2.1.14.16.2.2 ospfNbrStateChange.
    12. Run the display isis peer command to check whether the IS-IS peer relationship is established.
      • If the IS-IS peer relationship is established, go to Step 17.
      • If no IS-IS peer relationship is established, see the precessing steps in ISIS_1.3.6.1.3.37.2.0.17 isisAdjacencyChange.
    13. Check whether the source address used for initiating the BGP connection is specified.
      • If the source address is specified, go to Step 14.
      • If no source address is specified, run the peer connect-interface command to configure a source address used for initiating the BGP connection.
    14. If the BGP peer relationship is a multi-hop EBGP peer relationship, check whether the peer ebgp-max-hop command is run.
      • If the peer ebgp-max-hop command is run, go to Step 15.
      • If the peer ebgp-max-hop command is not run, run the peer ebgp-max-hop command.
    15. If the peer valid-ttl-hops hops command is run, check whether the TTL of the packet received from the remote end is within the range [255-hops+1, 255].
      • If the TTL of the packet is within the range, go to Step 14.
      • If the TTL of the packet is beyond the range, run the peer valid-ttl-hops hops command to ensure that the TTL of the packet sent to the remote peer is within the range.
    16. Contact the maintenance engineer responsible for the peer device to check whether BGP is reset on the peer device, whether the peer enable command is run in the view of another address family view on the local device, and whether BGP connection parameters are set. If any of the operations is performed, wait for a period of time, and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 17.
    17. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
  • Cause 3: Receive error packet.
    1. Run the display bgp peer ip-address log-info command to check the Notification packet sent by the local device when the BGP peer relationship is interrupted.
      • If the value of the Error Code field in the Notification packet is 1, a packet with an error header has been received. Go to Step 2.
      • If the value of the Error Code field in the Notification packet is 2, an error Open packet has been received. Go to Step 2.
      • If the value of the Error Code field in the Notification packet is 3, an error Update packet has been received. Go to Step 2.
    2. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
  • Cause 4: Hold timer expire.
    1. Run the ping command to check whether the local device can successfully ping its peer.
      • If the local device pings its peer successfully, go to Step 2.
      • If the local device fails to ping its peer, go to Step 3.
    2. Run the display cpu command to check whether the CPU usage is too high.
      • If the CPU usage is too high, go to Step 15.
      • If the CPU usage is within the normal range, go to Step 4.
    3. Run the display ip routing-table command to check whether the route from the local device to its peer exists in the routing table.
      • If the route from the local device to its peer exists in the routing table, go to Step 5.
      • If the route from the local device to its peer does not exist in the routing table, go to Step 6.
    4. Run the display acl command to check whether the router is configured with an ACL used to disable TCP port 179.
      • If the router is configured with such an ACL, delete the ACL.
      • If the router is not configured with such an ACL, go to Step 7.
    5. Run the display interface command to check whether the outbound interface of the route is Up.
      • If the outbound interface of the route is Up, go to Step 15.
      • If the outbound interface of the route is not Up, go to Step 8.
    6. Check the configuration of the local device and the origin of the route from the local device to its peer.
      • If the route is imported from OSPF, go to Step 9.
      • If the route is imported from IS-IS, go to Step 10.
    7. Check the BGP configuration of the local device to check whether a loopback interface is used to establish the BGP connection.
      • If a loopback interface is used to establish the BGP connection, go to Step 11.
      • If no loopback interface is used to establish the BGP connection, go to Step 12.
    8. Check whether the shutdown command is run on the directly connected interface.
      • If the shutdown command is run on the interface, run the undo shutdown command is run on the interface. If the alarm is not cleared, go to Step 11.
      • If the shutdown command is not run on the interface, go to Step 15.
    9. Run the display ospf peercommand to check whether the OSPF peer relationship is established.
      • If the OSPF peer relationship is established, go to Step 15.
      • If no OSPF peer relationship is established, see the precessing steps in OSPF_1.3.6.1.2.1.14.16.2.2 ospfNbrStateChange.
    10. Run the display isis peer command to check whether the IS-IS peer relationship is established.
      • If the IS-IS peer relationship is established, go to Step 15.
      • If no IS-IS peer relationship is established, see the precessing steps in ISIS_1.3.6.1.3.37.2.0.17 isisAdjacencyChange.
    11. Check whether the source address used for initiating the BGP connection is specified.
      • If the source address is specified, go to Step 12.
      • If no source address is specified, run the peer connect-interface command to configure a source address used for initiating the BGP connection.
    12. If the BGP peer relationship is a multi-hop EBGP peer relationship, check whether the peer ebgp-max-hop command is run.
      • If the peer ebgp-max-hop command is run, go to Step 13.
      • If the peer ebgp-max-hop command is not run, run the peer ebgp-max-hop command.
    13. If the peer valid-ttl-hops hops command is run, check whether the TTL of the packet received from the remote end is within the range [255-hops+1, 255].
      • If the TTL of the packet is within the range, go to Step 14.
      • If the TTL of the packet is beyond the range, run the peer valid-ttl-hops hops command to ensure that the TTL of the packet sent to the remote peer is within the range.
    14. Contact the maintenance engineer responsible for the peer device to check whether BGP is reset on the peer device, whether the peer enable command is run in the view of another address family view on the local device, and whether BGP connection parameters are set. If any of the operations is performed, wait for a period of time, and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 15.
    15. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
  • Cause 5: Remote peer not reachable.
    1. Run the ping command to check whether the local device can successfully ping its peer.
      • If the local device pings its peer successfully, go to Step 2.
      • If the local device fails to ping its peer, go to Step 3.
    2. Run the display cpu command to check whether the CPU usage is too high.
      • If the CPU usage is too high, go to Step 15.
      • If the CPU usage is within the normal range, go to Step 4.
    3. Run the display ip routing-table command to check whether the route from the local device to its peer exists in the routing table.
      • If the route from the local device to its peer exists in the routing table, go to Step 5.
      • If the route from the local device to its peer does not exist in the routing table, go to Step 6.
    4. Run the display acl command to check whether the router is configured with an ACL used to disable TCP port 179.
      • If the router is configured with such an ACL, delete the ACL.
      • If the router is not configured with such an ACL, go to Step 7.
    5. Run the display interface command to check whether the outbound interface of the route is Up.
      • If the outbound interface of the route is Up, go to Step 15.
      • If the outbound interface of the route is not Up, go to Step 8.
    6. Check the configuration of the local device and the origin of the route from the local device to its peer.
      • If the route is imported from OSPF, go to Step 9.
      • If the route is imported from IS-IS, go to Step 10.
    7. Check the BGP configuration of the local device to check whether a loopback interface is used to establish the BGP connection.
      • If a loopback interface is used to establish the BGP connection, go to Step 11.
      • If no loopback interface is used to establish the BGP connection, go to Step 12.
    8. Check whether the shutdown command is run on the directly connected interface.
      • If the shutdown command is run on the interface, run the undo shutdown command is run on the interface. If the alarm is not cleared, go to Step 11.
      • If the shutdown command is not run on the interface, go to Step 15.
    9. Run the display ospf peercommand to check whether the OSPF peer relationship is established.
      • If the OSPF peer relationship is established, go to Step 15.
      • If no OSPF peer relationship is established, see the precessing steps in OSPF_1.3.6.1.2.1.14.16.2.2 ospfNbrStateChange.
    10. Run the display isis peer command to check whether the IS-IS peer relationship is established.
      • If the IS-IS peer relationship is established, go to Step 15.
      • If no IS-IS peer relationship is established, see the precessing steps in ISIS_1.3.6.1.3.37.2.0.17 isisAdjacencyChange.
    11. Check whether the source address used for initiating the BGP connection is specified.
      • If the source address is specified, go to Step 12.
      • If no source address is specified, run the peer connect-interface command to configure a source address used for initiating the BGP connection.
    12. If the BGP peer relationship is a multi-hop EBGP peer relationship, check whether the peer ebgp-max-hop command is run.
      • If the peer ebgp-max-hop command is run, go to Step 13.
      • If the peer ebgp-max-hop command is not run, run the peer ebgp-max-hop command.
    13. If the peer valid-ttl-hops hops command is run, check whether the TTL of the packet received from the remote end is within the range [255-hops+1, 255].
      • If the TTL of the packet is within the range, go to Step 14.
      • If the TTL of the packet is beyond the range, run the peer valid-ttl-hops hops command to ensure that the TTL of the packet sent to the remote peer is within the range.
    14. Contact the maintenance engineer responsible for the peer device to check whether BGP is reset on the peer device, whether the peer enable command is run in the view of another address family view on the local device, and whether BGP connection parameters are set. If any of the operations is performed, wait for a period of time, and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 15.
    15. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
  • Cause 6: Direct connect-interface down.
    1. Check whether the shutdown command is run on the directly connected interface.
    2. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
  • Cause 7: Route limit.
    1. Check whether the peer route-limit command is run and whether the number of routes exceeds the upper threshold.
      • If the command is run and the number of received routes exceeds the upper threshold, go to Step 2.
      • If the command is not run or the command is run but the number of received routes does not exceed the upper threshold, go to Step 3.
    2. Check whether the peer route-limit command is necessary. If the command is necessary, reduce routes to ensure that the number of routes is smaller than the upper threshold.
    3. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.

BGP_1.3.6.1.4.1.2011.5.25.177.1.3.1 hwBgpPeerRouteNumThresholdExceed

Description

The number of routes received from the BGP peer exceeded the alarm threshold. (InstanceId=[InstanceId], Afi=[AddrFamilyAfi], Safi=[AddrFamilySafi], PeerRemoteAddrType=[PeerIPAddrType], PeerRemoteAddr=[PeerIPAddr], MaxRouteNumber=[RouteLimitNum], AlarmThreshold=[RouteLimitThreshold])

The number of routes received from the BGP peer exceeded the alarm threshold.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

ROUTETHRESHOLDEXCEED

Trap OID

1.3.6.1.4.1.2011.5.25.177.1.3.1

Alarm ID

0x08790001

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

BGP_1.3.6.1.4.1.2011.5.25.177.1.3.2 hwBgpPeerRouteNumThresholdClear

Parameters

Parameter

Description

InstanceId

Instance ID

Afi

Address family

Safi

Sub-address family

PeerRemoteAddrType

Peer address type

PeerRemoteAddr

Peer address

MaxRouteNumber

Maximum number of routes

AlarmThreshold

Alarm threshold

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.177.1.1.5.1.1

hwBgpPeerConfigRouteLimitNum

None

1.3.6.1.4.1.2011.5.25.177.1.1.5.1.2

hwBgpPeerConfigRouteLimitThreshold

None

Impact on the System
  • If the peer route-limit percentage command with percentage of 100% and without alert-only is run, the peer relationship is interrupted and the routes received from all peers are deleted.
  • If the peer route-limit percentage command with alert-only is run, services are not interrupted.
Possible Causes

Cause: The number of routes received from the BGP peer who configed with route-limit, exceeds the alarm threshold.

Procedure
  • Cause: The number of routes received from the BGP peer who configed with route-limit, exceeds the alarm threshold.
    1. Run the display bgp peer command to check whether the number of routes received from a peer exceeds the value obtained the maximum number of routes that can be received from the peer multiplied by the alarm threshold(%).
      • If the number of routes received from the peer exceeds the value, go to Step 2.
      • If the number of routes received from a peer does not exceed the value, 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 commandto 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 the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.

BGP_1.3.6.1.4.1.2011.5.25.177.1.3.2 hwBgpPeerRouteNumThresholdClear

Description

The number of routes received from the BGP peer decreased below the alarm threshold. (InstanceId=[InstanceId], Afi=[AddrFamilyAfi], Safi=[AddrFamilySafi], PeerRemoteAddrType=[PeerIPAddrType], PeerRemoteAdd=[PeerIPAddr], MaxRouteNumber=[RouteLimitNum], AlarmThreshold=[RouteLimitThreshold])

The number of routes received from a peer fell below the threshold

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

ROUTETHRESHOLDCLEAR

Trap OID

1.3.6.1.4.1.2011.5.25.177.1.3.2

Alarm ID

0x08790001

Alarm Type

communicationsAlarm

Raise or Clear

Clear

Match trap

BGP_1.3.6.1.4.1.2011.5.25.177.1.3.1 hwBgpPeerRouteNumThresholdExceed

Parameters

Parameter

Description

InstanceId

Instance ID

Afi

Address family

Safi

Sub-address family

PeerRemoteAddrType

Peer address type

PeerRemoteAddr

Peer address

MaxRouteNumber

Maximum number of routes

AlarmThreshold

Alarm threshold

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.177.1.1.5.1.1

hwBgpPeerConfigRouteLimitNum

None

1.3.6.1.4.1.2011.5.25.177.1.1.5.1.2

hwBgpPeerConfigRouteLimitThreshold

None

Impact on the System

The alarm that the number of routes received from the BGP peer exceed the configured threshold is cleared.

Possible Causes

Cause: The number of routes received from the BGP peer who configed with route-limit, fell below the alarm threshold.

Procedure
  • This trap message is informational only, and no action is required.

BGP_1.3.6.1.4.1.2011.5.25.177.1.3.6 hwBgpPeerRouteExceed

Description

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.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

ROUTEEXCEED

Trap OID

1.3.6.1.4.1.2011.5.25.177.1.3.6

Alarm ID

0x08790002

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

BGP_1.3.6.1.4.1.2011.5.25.177.1.3.7 hwBgpPeerRouteExceedClear

Parameters

Parameter

Description

InstanceId

Instance ID

Afi

Address family

Safi

Sub-address family

PeerRemoteAddrType

Peer address type

PeerRemoteAddr

Peer address

MaxRouteNum

Maximum number of routes

AlarmThreshold

Alarm threshold

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.177.1.1.5.1.1

hwBgpPeerConfigRouteLimitNum

None

1.3.6.1.4.1.2011.5.25.177.1.1.5.1.2

hwBgpPeerConfigRouteLimitThreshold

None

Impact on the System
  • If the peer route-limit percentage command with percentage of 100% and without alert-only is run, the peer relationship is interrupted and the routes received from all peers are deleted.
  • If the peer route-limit percentage command with alert-only is run, services are not interrupted.
Possible Causes

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

Procedure
  • Cause: The number of routes received from the BGP peer who configured with route-limit, exceeds the maximum value allowed.
    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 the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.

BGP_1.3.6.1.4.1.2011.5.25.177.1.3.7 hwBgpPeerRouteExceedClear

Description

The number of routes received from the BGP peer decreased below the alarm number. (InstanceId=[InstanceId], Afi=[AddrFamilyAfi], Safi=[AddrFamilySafi], PeerRemoteAddrType=[PeerRemoteAddrType], PeerRemoteAddr=[PeerRemoteAddr], MaxRouteNum=[MaxRouteNum], AlarmThreshold=[AlarmThreshold])

The number of routes received from a peer fell below the threshold

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

ROUTEEXCEEDCLEAR

Trap OID

1.3.6.1.4.1.2011.5.25.177.1.3.7

Alarm ID

0x08790002

Alarm Type

communicationsAlarm

Raise or Clear

Clear

Match trap

BGP_1.3.6.1.4.1.2011.5.25.177.1.3.6 hwBgpPeerRouteExceed

Parameters

Parameter

Description

InstanceId

Instance ID

Afi

Address family

Safi

Sub-address family

PeerRemoteAddrType

Peer address type

PeerRemoteAddr

Peer address

MaxRouteNum

Maximum number of routes

AlarmThreshold

Alarm threshold

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.177.1.1.5.1.1

hwBgpPeerConfigRouteLimitNum

None

1.3.6.1.4.1.2011.5.25.177.1.1.5.1.2

hwBgpPeerConfigRouteLimitThreshold

None

Impact on the System

The alarm that the number of routes received from the BGP peer exceed the upper threshold is cleared.

Possible Causes

Cause: The number of routes received from the BGP peer who configed with route-limit, fell below the alarm threshold.

Procedure
  • This trap message is informational only, and no action is required.
Translation
Download
Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 196202

Downloads: 1571

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