Loading ...
Loading ...
Loading ...
Configuring OAM (Only for Certain Devices) Ethernet OAM
User Guide 991
Remote Failure Indication (RFI)
With Remote Failure Indication, an OAM entity can send the failure conditions of the link,
such as disruption in traffic because of the device failure, to its peer through Information
OAMPDUs. This allows the network administrator to stay informed of the link faults and
take action quickly. The switch supports two kinds of failure conditions:
Dying Gasp: An unrecoverable fault, such as power failure, occurs.
Critical Event: Unspecified critical event occurs.
Remote Loopback
With Remote Loopback, administrators can test link performance including the delay, jitter,
and frame loss rate during installation or troubleshooting.
Figure 1-2 Remote Loopback
(1) Loopback Control OAMPDU
(3) Non-OAMPDUs from A to B
(5) Loopback Control OAMPDU
(2) Information OAMPDU
(4) Non-OAMPDUs back from B to A
(6) Information OAMPDU
Switch A Switch B
Gi 1/0/1
(Active mode)
Gi 1/0/1
(Passive mode)
As the above figure shows, the OAM connection has been established between the two
entities. The OAM entity on Switch A is in active mode, and that on Switch B is in passive
mode.
The working mechanism of Remote Loopback is as follows:
1) Switch A sends a Loopback Control OAMPDU to put the peer into remote loopback
mode. Note that at least one of the two entities should be configured in active mode
because only the entity in active mode can generate Loopback Control OAMPDU.
2) After receiving the Loopback Control OAMPDU, Switch B turns into remote loopback
mode and sends an Information OAMPDU to inform its state updating.
3) Switch A sends Non-OAMPDU packets to Switch B for link testing.
4) Switch B receives the testing packets and sends back these packets along the original
path. Through these returned packets, administrators can test the link performance.
Loading ...
Loading ...
Loading ...