Efm oam critical-link-event – Brocade Communications Systems Brocate Ethernet Access Switch 6910 User Manual

Page 614

Advertising
background image

564

Brocade 6910 Ethernet Access Switch Configuration Guide

53-1002581-01

OAM Commands

26

Default Setting

Disabled

Command Mode

Interface Configuration

Command Usage

If the remote device also supports OAM, both exchange Information OAMPDUs to establish an
OAM link.

Not all CPEs support OAM functions, and OAM is therefore disabled by default. If the CPE
attached to a port supports OAM, then this functionality must first be enabled by the efm oam
command to gain access to other remote configuration functions.

Example

Console(config)#interface ethernet 1/1

Console(config-if)#efm oam

Console(config-if)#

efm oam critical-link-event

This command enables reporting of critical event or dying gasp. Use the no form to disable this
function.

Syntax

[no] efm oam critical-link-event {critical-event | dying-gasp}

critical-event - If a critical event occurs, the local OAM entity (this switch) indicates this to
its peer by setting the appropriate flag in the next OAMPDU to be sent and stores this
information in its OAM event log.

dying-gasp - If an unrecoverable condition occurs, the local OAM entity indicates this by
immediately sending a trap message.

Default Setting

Enabled

Command Mode

Interface Configuration

Command Usage

Critical events are vendor-specific and may include various failures, such as abnormal voltage
fluctuations, out-of-range temperature detected, fan failure, CRC error in flash memory,
insufficient memory, or other hardware faults.

Dying gasp events are caused by an unrecoverable failure, such as a power failure or device
reset.

NOTE

When system power fails, the switch will always send a dying gasp trap message prior to power
down.

Advertising