Professional Documents
Culture Documents
172 2878 BFD Link Failure
172 2878 BFD Link Failure
Meaning
This alarm is set on RNC when BFD link failure is detected between monitored local and remote IP
addresses. As a result of this the connection between the IP addresses mentioned in this alarm is
not available.
Alarms are raised in the following cases:
Ingress alarm:
The alarm shall be raised when no BFD message is received at the local end during the detection
time. The alarm shall be cleared once a BFD message is received at the local end or when the BFD
function is disabled. The alarm in ingress direction is independent of the alarm in egress
direction.
Egress alarm:
The alarm shall be raised when the BFD control packet coming from the remote peer contains the
diagnostic code "Control Detection Time Expired" and no ingress alarm is present.
Socket alarm:
The alarm shall be raised in cases when the local IP interface is not working properly or
misconfigured, e.g. when an IP address used as source endpoint is not configured.
The alarm shall be cleared when the BFD message from the remote end contains a state different from
"Down", or when the BFD function is disabled, or when the IP connectivity is restored. Ingress and
Egress direction, or socket cause can be obtained in the 1st supplementary information field.
Instructions
When this alarm is raised it means that there is no communication between the peers with the
reported IP addresses. It could be a problem in the line cards of the network elements but the
problem could be in the middle if a multi-hop network is used to connect the peers. To locate the
problem the operator should look the 1st discriminator field:
01: Local timer expiration, state Down
02: Remote state Down
03: Remote state AdminDown
04: IP interface error
Error code 01 means that no incoming packet is received from the peer then problem could be in the
middle or the peer could have no connectivity or is not working anymore. As far as the connectivity
is recovered the alarm is cleared automatically.
Error code 02 means that the remote peer has gone to down state for internal reasons and has
signaled this to the local peer.
The operator could wait for this alarm to disappear. If the alarm does not disappear it has to check
that the remote peer is working.
Anyway it should not be a connectivity problem. As far as the down state is cleared by the peer the
alarm is cleared automatically on the local.
Error code 03 means that the operator has disabled BFD on the remote peer. Alarm is cleared if the
operator disables BFD on the local peer too.
Error code 04 means that the local IP interface is not working properly or it is misconfigured, for
example if the configuration of the source IP address is missing. When the IP protocol returns to
proper functionality the alarm is cleared automatically. No BFD session reconfiguration is needed.
Cancelling
Do not cancel the alarm. The system cancels the alarm automatically when the fault has been
corrected.
2015-05-08
00:01:21
01
WBTS
2
734d
3
10.225.50.45 4
10.225.49.242 5
00
6
00
48E302DE
00000000
00
the sack:
ZGA
LVE