No relevant resource is found in the selected language.
Enterprise
Worldwide
Search
Support Documentation
S1700, S2720, S5700, and S6700 V200R019C10 Alarm Handling

This document provides the explanations, causes, and recommended actions of alarms on the product.

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).
BFD

BFD

BFD_1.3.6.1.4.1.2011.5.25.38.3.1 hwBfdSessDown

Description

BFD/2/BFD_DOWN_TRAP:OID [oid] Session changes to DOWN. (Index=[integer], ConfigurationName=[octet], PeerIp=[ipaddr], BindIfIndex=[integer], BindIfName=[octet], Diagnosis=[integer], BindVrfIndex=[integer], BindVpnName=[octet], SessionType=[integer], DefaultIp=[integer], BindType=[integer], StaticLspName=[octet], PwSecondary=[integer], NextHop=[ipaddr], VcId=[integer], VsiName=[octet], VsiPeerAddress=[ipaddr], DiscrAuto=[integer], PeerIpv6=[ipv6addr], Ipv6NextHop=[ipv6addr])

The trap was generated when the BFD session changed from another state to the Down state.

The statuses of the BFD session include: Up, Init, Down, and AdmDown.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.38.3.1

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Index

Indicates the index of the BFD session.

ConfigurationName

Indicates the configuration name of the BFD session.

PeerIP

Indicates the bound destination IP address.

BindIfIndex

Indicates the index of the bound interface.

BindIfName

Indicates the name of the bound interface.

Diagnosis

Indicates information about session diagnostic characters.

BindVrfIndex

Indicates the index of the bound VPN.

BindVpnName

Indicates the name of the bound VPN.

SessionType

Indicates the type of the BFD session.

  • 1: Static, indicates the statically configured BFD session.

  • 2: Dynamic, indicates the dynamically established BFD session.

  • 3: Entire_Dynamic, indicates that the establishment of a BFD session is triggered entirely dynamically. This type of BFD session is created only after the function of passively creating BFD sessions is enabled on the egress switch of the LSP.

  • 4: Static_Auto, indicates the static BFD session that is established with automatically negotiated discriminators.

DefaultIP

Indicates the default multicast IP address.

BindType

Indicates the binding type.

  • 1: interfaceIp, detects the Interface, and peer IP address, the single hop IP link.
  • 2: peerIp, detects the peer IP, the multi-hop IP link.
  • 3: sourceIp, detects the peer IP source address.
  • 4: ifAndSourceIp, detects the Interface, peer IP and source IP address.
  • 7: ospf, detects the OSPF.
  • 8: isis, detects the ISIS.
  • 9: ldpLsp, detects the LDP LSP.
  • 10: staticLsp, detects the static LSP.
  • 11: teLsp, detects the LSP bound to the TE tunnel.
  • 12: teTunnel, detects the TE tunnel.
  • 13: pw, detects the PW.
  • 15: vsiPw, detects the VSI PW.
  • 21: ldpTunnel, detects the LDP tunnel.
  • 22: bgpTunnel, detects BGP tunnel.

StaticLspName

Indicates the name of the static LSP.

PwSecondary

Indicates the ID of the secondary PW.

NextHop

Indicates the IP address of the next hop.

VcId

Indicates the ID of the VC.

VsiName

Indicates the name of the VSI.

VsiPeerAddress

Indicates the destination address of the VSI.

DiscrAuto

Indicates the static auto-negotiation identifier.

PeerIpv6

Indicates the bound destination IPv6 address.

Ipv6NextHop

Indicates the next-hop IPv6 address.

Impact on the System

If the alarm function is enabled and a large number of BFD sessions flap, more CPU resources are consumed. Except for this, no service will be affected.

Possible Causes

Cause 1:

The session-bound interface goes down.

Cause 2:

The peer BFD session is deleted or shut down.

Cause 3:

The link went Down or was congested. Consequently, it failed to forward packets.

Procedure

  1. Run the display interface command to check whether the physical status of the interface where the session resides is Up.

    • If so, go to Step 2.
    • If not, go to Step 6.

  2. Check whether a message reporting alarm recovery is received.

    • If so, go to Step 6.
    • If not, go to Step 3.

  3. Run the display bfd session all command to check whether the BFD sessions on the local end and on the remote end are deleted.

    • If so, go to Step 6.
    • If not, go to Step 4.

  4. Run the ping ip-address command to check whether the link detected by the BFD session fails to forward packets.

    • If so, go to Step 6.
    • If not, go to Step 5.

  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.

Related Information

BFD_1.3.6.1.4.1.2011.5.25.38.3.2 hwBfdSessUp

BFD_1.3.6.1.4.1.2011.5.25.38.3.2 hwBfdSessUp

Description

BFD/2/BFD_UP_TRAP:OID [oid] Session changes to UP. (Index=[integer], ConfigurationName=[octet], PeerIp=[ipaddr], BindIfIndex=[integer], BindIfName=[octet], Diagnosis=[integer], BindVrfIndex=[integer], BindVpnName=[octet], SessionType=[integer], DefaultIp=[integer], BindType=[integer], StaticLspName=[octet], PwSecondary=[integer], NextHop=[ipaddr], VcId=[integer], VsiName=[octet], VsiPeerAddress=[ipaddr], DiscrAuto=[integer], PeerIpv6=[ipv6addr], Ipv6NextHop=[ipv6addr])

The trap was generated when the BFD session changed from another state to the Up state. The statuses of the BFD session include: Up, Init, Down, and AdmDown.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.38.3.2

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Index

Indicates the index of the BFD session.

ConfigurationName

Indicates the configuration name of the BFD session.

PeerIP

Indicates the bound destination IP address.

BindIfIndex

Indicates the index of the bound interface.

BindIfName

Indicates the name of the bound interface.

Diagnosis

Indicates information about the session diagnostic characters.

BindVrfIndex

Indicates the index of the bound VPN.

BindVpnName

Indicates the name of the bound VPN.

SessionType
Indicates the type of the BFD session.

  • 1: Static, indicates the statically configured BFD session.

  • 2: Dynamic, indicates the dynamically established BFD session.

  • 3: Entire_Dynamic, indicates that the establishment of a BFD session is triggered entirely dynamically. This type of BFD session is created only after the function of passively creating BFD sessions is enabled on the egress switch of the LSP.

  • 4: Static_Auto, indicates the static BFD session that is established with automatically negotiated discriminators.

DefaultIP

Indicates the default multicast IP address.

BindType
Indicates the binding type.
  • 1: interfaceIp, detects the Interface, and peer IP address, the single hop IP link.
  • 2: peerIp, detects the peer IP, the multi-hop IP link.
  • 3: sourceIp, detects the peer IP source address.
  • 4: ifAndSourceIp, detects the Interface, peer IP and source IP address.
  • 7: ospf, detects the OSPF.
  • 8: isis, detects the ISIS.
  • 9: ldpLsp, detects the LDP LSP.
  • 10: staticLsp, detects the static LSP.
  • 11: teLsp, detects the LSP bound to the TE tunnel.
  • 12: teTunnel, detects the TE tunnel.
  • 13: pw, detects the PW.
  • 15: vsiPw, detects the VSI PW.
  • 21: ldpTunnel, detects the LDP tunnel.
  • 22: bgpTunnel, detects BGP tunnel.

StaticLspName

Indicates the name of the static LSP.

PwSecondary

Indicates the ID of the secondary PW.

NextHop

Indicates the IP address of the next hop.

VcId

Indicates the ID of the VC.

VsiName

Indicates the name of the VSI.

VsiPeerAddress

Indicates the destination address of the VSI.

DiscrAuto

Indicates the static auto-negotiation identifier.

PeerIpv6

Indicates the bound destination IPv6 address.

Ipv6NextHop

Indicates the next-hop IPv6 address.

Impact on the System

After the trap function is enabled, if a large number of BFD sessions flap, high CPU will be utilized. Except for this, no service will be affected.

Possible Causes

Cause 1:

A BFD session was created. That is, the BFD session changed from Init to Up.

Cause 2:

The undo shutdown command was run to restore the BFD session. That is, the BFD session changed from AdmDown to Up.

Cause 3:

The BFD session changed from Down to Up.

Procedure

  1. This alarm message is informational only, and no action is required.

Related Information

BFD_1.3.6.1.4.1.2011.5.25.38.3.1 hwBfdSessDown

BFD_1.3.6.1.4.1.2011.5.25.38.3.3 hwBfdSessReachLimit

Description

BFD/4/BFD_SESSLMT_TRAP:OID [oid] The session number in all the IO boards has reached the limit, the new session can not be created. (TotalSessionLimit=[integer])

The trap was generated when the number of all the BFD sessions set up on interface boards reached the PAF upper limit and no more session can be set up. You can run the display bfd statistics command to view information about BFD_SESSION_NUM and know the upper limit.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.38.3.3 Warning qualityOfServiceAlarm (3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

TotalSessionLimit

Indicates the upper limit of global BFD sessions.

Impact on the System

Services will not be affected.

Possible Causes

New BFD configurations were still committed when the number of global BFD sessions reached the upper limit

Procedure

  1. Run the display bfd statistics command to check whether the number of BFD sessions displayed below the PAF/LCS Name field has reached the upper limit.

    • If so, go to Step 2.
    • If not, go to Step 3.

  2. Run the undo bfd session-name command to delete useless BFD sessions. The configurations of committed BFD sessions are automatically created. In this case, go to Step 4.
  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

None

BFD_1.3.6.1.4.1.2011.5.25.38.3.4 hwBfdSessReachLimitBindIf

Description

BFD/4/BFD_IFSESSLMT_TRAP:OID [oid] Try to build session, but the session number in the IO board with interface has reached the limit, the new session binding with interface can not be created. (ConfigurationName=[octet], InterfaceName=[octet], SessionLimitPerBoard=[integer])

The trap was generated when the number of BFD sessions bound to the interface on the interface board reached the PAF upper limit and no more BFD session bound to the interface can be set up. You can run the display bfd statistics command to view the value of BFD_IO_SESSION_NUM corresponding to the upper limit.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.38.3.4 Warning qualityOfServiceAlarm (3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

ConfigurationName

Indicates the configuration name.

InterfaceName

Indicates the interface name.

SessionLimitPerBoard

Indicates the allowable maximum number of BFD sessions on each board.

Impact on the System

Services will not be affected.

Possible Causes

New BFD sessions bound to the interface were still set up when the number of BFD sessions bound to the interface have reached the upper limit.

Procedure

  1. Run the display bfd statistics command to check whether the BFD_IO_SESSION_NUM on the board has reached the upper limit.

    • If so, go to Step 2.
    • If not, go to Step 3.

  2. Run the undo bfd bfd-name command in the system view to delete the useless BFD session bound to this interface. Then the BFD session about committed configuration will be set up automatically. Go to Step 4.
  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

None

Translation
日本語 简体中文
Download
Updated: 2022-05-25

Document ID: EDOC1100127008

Views: 81380

Downloads: 336

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Digital Signature File

Digital Signature Authentication Mode
Share
Previous Next

Copyright © 2023 Huawei Technologies Co., Ltd. All rights reserved.

You are going to visit :