Brocade Multi-Service IronWare Administration Guide (Supporting R05.6.00) - Manual (Page 212)

194 Multi-Service IronWare Administration Guide
53-1003028-02
IEEE 802.3ah EFM-OAM
6
Defining remote failure actions
By default, on receipt of a remote failure message, the device will only log the event. This can be
changed to block an interface on receipt of a remote failure message. The commands below
display the three events that the protocol supports.
Brocade(config-link-oam)#ethernet 2/1 remote-failure dying-gasp action
block-interface
Brocade(config-link-oam)#ethernet 2/1 remote-failure critical-event action
block-interface
Brocade(config-link-oam)#ethernet 2/1 remote-failure link-fault action
block-interface
Syntax: [no]ethernet slot/port remote-failure dying-gasp | link-fault | critical-event action
block-interface
The no form of the command returns to default state of logging.
Forcing the EFM-OAM remote interface into loopback
The link-oam remote-loopback ethernet slot/port start/stop command starts and stops the remote
loopback on the remote node.
Brocade# link-oam remote-loop-back ethernet 1/1 start
Syntax: [no]link-oam remote loopback ethernet slot/port start/stop
Display information
The following show commands will display OAM information.
DIsplaying OAM information
To show OAM information on all OAM enabled ports, enter a command such as the following:
Brocade#show link-oam info
Ethernet Link Status OAM Status Mode Local Stable Remote Stable
1/1 up up active satisfied satisfied
1/2 up up passive satisfied satisfied
1/3 up up active satisfied satisfied
1/4 up init passive unsatisfied unsatisfied
1/5 down down passive unsatisfied unsatisfied
1/6 down down passive unsatisfied unsatisfied
1/7 down down passive unsatisfied unsatisfied