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

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

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_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.1 hwBfdSessDown

Description

Session changes to DOWN. (Index=[Index], ConfigurationName=[ConfigurationName], PeerIp=[PeerIp], BindIfIndex=[BindIfIndex], BindIfName=[BindIfName], Diagnosis=[Diagnosis], BindVrfIndex=[BindVrfIndex], BindVpnName=[BindVpnName], SessionType=[SessionType], DefaultIp=[DefaultIp], BindType=[BindType], StaticLspName=[StaticLspName], PwSecondary=[PwSecondary], NextHop=[NextHop], VcId=[VcId], VsiName=[VsiName], VsiPeerAddress=[VsiPeerAddress], DiscrAuto=[DiscrAuto], PeerIpv6=[PeerIpv6], Ipv6NextHop=[Ipv6NextHop])

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.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwBfdSessDown

Trap OID

1.3.6.1.4.1.2011.5.25.38.3.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 matching trap.

Parameters

Parameter

Description

OID

Indicates the ID of the MIB object.

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 router 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.

  • 2 or 3: Peer Ip Address, detects the multi-hop IP link.

  • 1 or 4: Interface, detects the single-hop IP link.

  • 9: LDP_LSP, detects the LDP LSP.

  • 11: TE_LSP, detects the LSP bound to the TE tunnel.

  • 12: TE_TUNNEL, detects the TE tunnel.

  • 13: PW, detects the PW.

  • 15: VSI_PW, detects the VSI PW.

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.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.38.2.3.1.4

hwBfdSessCfgName

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.5

hwBfdSessPeerAddr

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.6

hwBfdSessBindIfIndex

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.7

hwBfdSessBindIfName

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.18

hwBfdSessDiag

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.20

hwBfdSessVrfIndex

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.21

hwBfdSessVPNName

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.22

hwBfdSessType

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.24

hwBfdSessDefaultIp

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.26

hwBfdSessBindType

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.28

hwBfdSessStaticLspName

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.30

hwBfdSessPWSecondaryFlag

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.27

hwBfdSessNextHop

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.32

hwBfdSessVcId

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.33

hwBfdSessVsiName

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.34

hwBfdSessVsiPeerAddr

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.35

hwBfdSessDiscrAuto

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.36

hwBfdSessPeerIpv6Addr

hwBfdSessIndex

1.3.6.1.4.1.2011.5.25.38.2.3.1.38

hwBfdSessIpv6NextHop

hwBfdSessIndex

Impact on the System

If a large number BFD session states flap that results in high CPU utilization rate. 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 configurations, trap messages, and log messages, and then contact technical support personnel.
  6. End.
Translation
Download
Updated: 2019-04-02

Document ID: EDOC1100074754

Views: 25674

Downloads: 31

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