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.
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.38.3.1 | Major | qualityOfServiceAlarm(3) |
| 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.
|
| DefaultIP | Indicates the default multicast IP address. |
| BindType | Indicates the binding type.
|
| 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. |
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.
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.