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