57-35
Software Configuration Guide—Release 15.0(2)SG
OL-23818-01
Chapter 57 Configuring Ethernet OAM and CFM
Enabling and Configuring Ethernet OAM
Enabling and Configuring Ethernet OAM
This section includes this information:
• Ethernet OAM Default Configuration, page 57-35
• Ethernet OAM Configuration Guidelines, page 57-35
• Enabling Ethernet OAM on an Interface, page 57-36
• Enabling Ethernet OAM Remote Loopback, page 57-37
• Configuring Ethernet OAM Link Monitoring, page 57-38
• Configuring Ethernet OAM Remote Failure Indications, page 57-42
• Configuring Ethernet OAM Templates, page 57-45
Ethernet OAM Default Configuration
The default configuration is as follows:
• Ethernet OAM is disabled on all interfaces.
• When Ethernet OAM is enabled on an interface, link monitoring is automatically turned on.
• Remote loopback is disabled.
• No Ethernet OAM templates are configured.
Ethernet OAM Configuration Guidelines
Follow these guidelines when configuring Ethernet OAM:
• The switch does not support monitoring of egress frames sent with cyclic redundancy code (CDC)
errors. The ethernet oam link-monitor transmit crc interface-configuration or
template-configuration commands are visible but are not supported on the switch. The commands
are accepted but are not applied to an interface.
• For a remote failure indication, the switch does not generate Link Fault or Critical Event OAM
PDUs. However, if these PDUs are received from a link partner, they are processed. The switch
generates and receives Dying Gasp OAM PDUs when Ethernet OAM is disabled, the interface is
shut down, the interface enters the error-disabled state, or the switch is reloading. It can respond to,
but not generate, Dying Gasp PDUs based on loss of power.
• The switch does not support Ethernet OAM loopback on ports that belong to an EtherChannel, ISL
trunk, and promiscuous trunk.
