Edge-Core ES3528MV2 - Page 1370

C HAPTER 42 | OAM Commands
– 1370 –
EXAMPLE
Console#show efm oam event-log interface 1/1
OAM event log of Eth 1/1:
00:24:07 2001/01/01
"Unit 1, Port 1: Dying Gasp at Remote"
Console#
This command can show OAM link status changes for link partner as shown
in this example.
Console#show efm oam event-log interface 1/1
OAM event log of Eth 1/1:
10:22:55 2013/09/13
"Unit 1, Port 1: Connection to remote device is up at Local"
10:22:44 2013/09/13
"Unit 1, Port 1: Connection to remote device is down at Local"
<--- When the link is down,this event will be written to OAM event-log
10:20:02 2013/09/13
"Unit 1, Port 1: Connection to remote device is up at Local"
<--- When the link is up,this event will be written to OAM event-log,
Console#clear efm oam event-log
<--- Use he "clear efm oam event-log” command to clear the event-log.
Console#show efm oam event-log interface 1/1
Console#
This command can show OAM dying gasp changes for link partner as
shown in this example.
Console#show efm oam event-log interface 1/1
<--- When dying gasp happens and the switch get these packets, it will log
this event in OAM event-log.
OAM event log of Eth 1/1:
10:27:21 2013/09/13
"Unit 1, Port 1: Connection to remote device is down at Local"
10:27:20 2013/09/13
"Unit 1, Port 1: Dying Gasp occurred at Remote"
Console#show efm oam event-log interface 1/1
OAM event log of Eth 1/1:
10:28:31 2013/09/13
"Unit 1, Port 1: Connection to remote device is up at Local"
10:28:28 2013/09/13
"Unit 1, Port 1: Dying Gasp clear occurred at Remote"
<--- When the remote device comes up, the switch will get OAM packets
without the dying gasp bit and display "dying gasp event clear".
Console#