Table Of Contents
bridge-domain (service instance)
clear ethernet cfm maintenance-points remote
clear ethernet cfm traceroute-cache
clear ethernet service instance
errdisable recovery cause mac-security
errdisable recovery cause mlacp-minlink
ethernet cfm ais link-status global
ethernet cfm cc enable level evc
ethernet cfm cc enable level vlan
ethernet cfm distribution enable
ethernet cfm enable (interface)
Carrier Ethernet Commands
ais
To enable the Alarm Indication Signal (AIS) function for a specific maintenance association, use the ais command in Ethernet CFM service configuration mode. To disable AIS configuration, use the no form of this command.
ais [expiry-threshold threshold | level level-id | period seconds | suppress-alarms]
no ais [expiry-threshold | level | period | suppress-alarms]
Syntax Description
Command Default
The AIS function is enabled on specific maintenance associations.
Command Modes
Ethernet CFM service configuration (config-ecfm-srv)
Command History
15.0(1)XA
This command was introduced.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
Alarms are suppressed when a MEP goes into an RX AIS (receipt of an AIS frame) defect condition.
When you specify the level keyword with the ais command, you can transmit AIS messages to a higher maintenance association without configuring a maintenance intermediate point (MIP) for that maintenance association.
Output of the show running all command shows "ais expiry-threshold 3.5" when the default expiry threshold is configured, "ais period 60" when the default transmission period is configured, and "no ais suppress-alarms" when the default value for the suppress-alarms option is configured.
Examples
The following example shows how to enable the AIS function at level 5 with a transmission period of one second:
Router(config)# ethernet cfm domain operatorA level 5Router(config-ecfm)# service vlan-id 10 portRouter(config-ecfm-srv)# ais period 1Router(config-ecfm-srv)# ais level 5Related Commands
alarm
To configure an alarm when fault alarms are enabled, use the alarm command in Ethernet connectivity fault management (CFM) interface configuration mode. To remove the configuration, use the no form of this command.
alarm {delay mseconds | notification {all | error-xcon | mac-remote-error-xcon | none | remote-error-xcon | xcon} | reset mseconds}
no alarm {delay | notification {all | error-xcon | mac-remote-error-xcon | none | remote-error-xcon | xcon} | reset}
Syntax Description
Syntax Description
Command Default
Alarms are disabled.
Command Modes
Ethernet CFM interface configuration (config-if-ecfm-mep)
Command History
12.2(33)SXI2
This command was introduced.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
This command overrides the global ethernet cfm alarm command.
If a higher priority defect occurs after a lower priority defect has triggered an alarm but before the alarm has reset, immediately issue another fault alarm for the higher priority defect.
Output of the show running all command displays "alarm delay 2500" when the default value for the delay option is configured, "alarm mac-remote-error-xcon" when the default value for the notification option is configured, and "alarm reset 10000" when the default value for the reset option is configured.
Examples
The following example shows how to set up notifications for all defects:
Router(config)# ethernet cfm domain test level 5Router(config-ecfm)# service vlan-id 17 vlan 17Router(config-ecfm-srv)# exitRouter(config-ecfm)# exitRouter(config-if)# ethernet cfm mep domain test mpid 5 vlan 17Router(config-if-ecfm-mep)# alarm notification allThe following example shows how to set the time during which one or more defects must be present before a fault alarm is issued to 7000 milliseconds:Router(config)# ethernet cfm domain test level 5Router(config-ecfm)# service vlan-id 17 vlan 17Router(config-ecfm-srv)# exitRouter(config-ecfm)# exitRouter(config-if)# ethernet cfm mep domain test mpid 5 vlan 17Router(config-if-ecfm-mep)# alarm delay 7000Related Commands
ethernet cfm alarm
Configures an alarm for Ethernet CFM.
show running all
Shows the running configuration with default values.
announce interval
To set an interval value for timing announcement packets, use the announce interval command in Precision Time Protocol clock port mode. To remove an announcement interval configuration, use the no form of this command.
announce interval interval-value
no announce interval interval-value
Syntax Description
Command Default
For the IE 3000 switch, the default value is 1. For the MWR 2941 router, the default value is 2.
Command Modes
PTP clock port configuration (config-ptp-port)
Command History
Usage Guidelines
The interval value defined by this command impacts the timeout value defined by the announce timeout command.
Examples
The following example shows how to configure an announcement interval:
Router# configure terminalRouter(config)# ptp clock ordinary domain 0Router(config-ptp-clk)# clock-port slave slaveportRouter(config-ptp-port)# announce interval 3Router(config-ptp-port)# endRelated Commands
announce timeout
To set a timeout value for timing announcement packets, use the announce timeout command in Precision Time Protocol clock port mode. To remove an announcement timeout configuration, use the no form of this command.
announce timeout timeout-value
no announce timeout timeout-value
Syntax Description
timeout-value
Specifies the number of announcement intervals before the session times out. The range is from 1 to 10. The default is 3.
Command Default
The default timeout value is 3.
Command Modes
PTP clock port configuration (config-ptp-port)
Command History
Usage Guidelines
This command configures the number of announcement intervals before the session times out. To define the length of the announcement intervals, use the announce interval command.
Examples
The following example shows how to configure an announcement timeout:
Router# configure terminalRouter(config)# ptp clock ordinary domain 0Router(config-ptp-clk)# clock-port slave slaveportRouter(config-ptp-port)# announce timeout 7Router(config-ptp-port)# endRelated Commands
backbone interface
To configure a backbone interface for a redundancy group, use the backbone interface command in interchassis redundancy configuration mode. To remove the configuration, use the no form of this command.
backbone interface type number
no backbone interface type number
Syntax Description
Command Default
A backbone interface is not configured.
Command Modes
Interchassis redundancy configuration (config-r-ic)
Command History
Usage Guidelines
Use this command to configure a backbone interface to monitor all interfaces in a redundancy group. For example, if all interfaces are in the DOWN state (core isolation), the backbone interface signals the redundancy group clients, and they may initiate attachment circuit (AC) failover procedures. An example client might be Multichassis Link Aggregation Control Protocol (mLACP).
Examples
The following example shows how to configure an Ethernet backbone interface:
Router> enableRouter# configure terminalRouter(config)# redundancyRouter(config-r)# interchassis group 1Router(config-r-ic)# backbone interface ethernet 0/1bridge-domain (global)
To configure components on a bridge domain, use the bridge-domain command in global configuration mode. To remove the configured components from the bridge domain and to return the components to the bridge-domain default state, use the no form of this command.
bridge-domain {bridge-id [c-mac] | c-mac aging-time minutes}
no bridge-domain {bridge-id [c-mac] | c-mac aging-time}
Syntax Description
Command Default
No components are configured on the bridge domain.
Command Modes
Global configuration (config)
Command History
12.2(33)SRD
This command was introduced.
12.2(33)SRE
This command was modified. The aging-time and c-mac keywords were added and the minutes argument was added.
Usage Guidelines
When the bridge-domain command is executed without the aging-time keyword, the command mode changes from global configuration mode (config) to bridge-domain configuration mode (config-bdomain). Issuing the bridge-domain c-mac aging-time command does not result in a command mode change.
In bridge-domain configuration mode, additional components can be configured on the bridge domain; for example, the MAC address limiting security component.
Note
In service instance configuration mode, the bridge-domain command binds a service instance to a bridge-domain instance.
Examples
The following example shows how to configure a bridge domain as a customer domain and place the CLI in bridge-domain configuration mode:
Router> enableRouter# configure terminalRouter(config)# bridge-domain 100 c-macRouter(config-bdomain)# mac limit maximum addresses 10The following example shows how to configure a bridge domain as a customer domain with an aging time of 400 minutes:
Router> enableRouter# configure terminalRouter(config)# bridge-domain c-mac aging-time 400Related Commands
bridge-domain
In service instance configuration mode, binds a service instance to a bridge domain.
mac limit maximum addresses
Specifies the MAC address limit on a bridge domain.
bridge-domain (service instance)
To bind a service instance or a MAC tunnel to a bridge domain instance, use the bridge-domain command in either service instance configuration mode or MAC-in-MAC tunnel configuration mode. To unbind a service instance or MAC tunnel from a bridge domain instance, use the no form of this command.
bridge-domain bridge-id [split-horizon [group group-id]]
no bridge-domain bridge-id [split-horizon [group group-id]]
Syntax on the Cisco ASR 1000 Series Aggregation Router
bridge-domain bridge-id [split-horizon group group-id]
no bridge-domain bridge-id [split-horizon group group-id]
Syntax Description
Command Default
Service instances and MAC tunnels are not bound to a bridge domain instance.
Command Modes
Service instance configuration (config-if-svc)
MAC-in-MAC tunnel configuration (config-tunnel-minm)Command History
Usage Guidelines
Use the bridge-domain (service instance) command to bind either a service instance or a MAC tunnel to a bridge domain.
Bridge domains cannot be configured under a service instance under a MAC tunnel without encapsulation also being configured.
The Cisco ASR 1000 router does not support MAC tunnels.
Note
Examples
The following example shows how to bind a bridge domain to a service instance:
Router> enableRouter# configure terminalRouter(config)# interface gigabitethernet 2/0/0Router(config-if)# service instance 100 ethernetRouter(config-if-srv)# encapsulation dot1q 100Router(config-if-srv)# bridge-domain 200The following example shows how to bind a MAC tunnel to a service instance:
Router> enableRouter# configure terminalRouter(config)# ethernet mac-tunnel virtual 100Router(config-tunnel-minm)# bridge-domain 200Related Commands
cfm encapsulation
To configure connectivity fault management (CFM) Ethernet frame encapsulation, use the cfm encapsulation command in service instance configuration mode. To remove the encapsulation, use the no form of this command.
cfm encapsulation {dot1ad vlan-id | dot1q vlan-id} [cos cos-value] [dot1q vlan-id | second-dot1q vlan-id] [cos cos-value]
no cfm encapsulation {dot1ad vlan-id | dot1q vlan-id} [cos cos-value] [dot1q vlan-id | second-dot1q vlan-id] [cos cos-value]
Syntax Description
Command Default
CFM Ethernet frame encapsulation is not configured.
Command Modes
Service instance configuration (config-if-srv)
Command History
12.2(33)SRD
This command was introduced.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
To use the cfm encapsulation command, you must first configure a bridge domain in Ethernet service configuration mode using the bridge-domain command.
When a range of VLANs is configured under the Ethernet flow point, the cfm encapsulation command configures the VLAN ID on which to send locally sourced CFM frames. The VLAN ID specified must be within the range configured in the encapsulation command.
The cfm encapsulation command does not support untagged service instances.
Examples
The following example shows how to configure the cfm encapsulation command:
ethernet cfm domain CUSTOMER level 7 direction outwardservice customer_100 evc evc_100ethernet cfm domain MIP level 7ethernet cfm domain PROVIDER level 4service provider_100 evc evc_100mep crosscheck mpid 200 evc evc_100 mac aabb.cc00.0310ethernet evc evc_100interface Ethernet 1/0no ip addressservice instance 100 ethernet evc_100encapsulation dot1q 100bridge-domain 100cfm encapsulation dot1q 1 cos 2 second-dot1q 3 cos 4Related Commands
cfm mep domain
To configure a maintenance endpoint (MEP) for a domain, use the cfm mep domain command in either service instance configuration mode or virtual forwarding instance (VFI) configuration mode. To remove the MEP, use the no form of this command.
cfm mep domain domain-name [inward | outward] mpid mpid-value [cos cos-value]
no cfm mep domain domain-name [inward | outward] mpid mpid-value
Syntax Description
Command Default
The direction of CFM packets is inward.
Command Modes
Service instance configuration (config-if-srv)
VFI configuration (config-vfi)Command History
12.2(33)SRD
This command was introduced.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
The cfm mep domain command defines an Ethernet flow point (EFP) as a MEP. To use the cfm mep domain command, you must first configure a bridge domain in service instance configuration mode by issuing the bridge-domain command.
Examples
The following example shows how to configure the cfm mep domain command:
ethernet cfm domain CUSTOMER level 7 direction outwardservice customer_100 evc evc_100ethernet cfm domain MIP level 7ethernet cfm domain PROVIDER level 4service provider_100 evc evc_100mep crosscheck mpid 200 evc evc_100 mac aabb.cc00.0310ethernet evc evc_100interface Ethernet 1/0no ip addressservice instance 100 ethernet evc_100encapsulation dot1q 100bridge-domain 100cfm mep domain CUSTOMER outward mpid 1001Related Commands
channel-group (interface)
To assign and configure an EtherChannel interface to an EtherChannel group, use the channel-group command in interface configuration mode. To remove the channel-group configuration from the interface, use the no form of this command.
channel-group channel-group-number mode {active | on | passive}
no channel-group channel-group-number
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
channel-group channel-group-number mode on
no channel-group channel-group-number
Cisco ASR 1000 Series Routers
channel-group channel-group-number mode {active | passive}
no channel-group
Cisco Catalyst Switches
channel-group channel-group-number mode {active | on | auto [non-silent] | desirable [non-silent] | passive}
no channel-group channel-group-number
Syntax Description
Command Default
No channel groups are assigned.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
OSMs are not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 32.
IP Address for the Physical Interface
You do not have to disable the IP address that is assigned to a physical interface that is part of a channel group, but Cisco highly recommends doing so.
Layer 2 and Layer 3 Port Channels
You can create both Layer 2 and Layer 3 port channels by entering the interface port-channel command or, when the channel-group gets its first physical interface assignment. The port channels are not created at run time, nor are they created dynamically.
You do not have to create a port-channel interface before assigning a physical interface to a channel group. A port-channel interface is automatically created when the channel group gets its first physical interface, if it is not already created.
Propagation of Configuration and Attribute Changes
Any configuration or attribute changes you make to the port-channel interface are propagated to all interfaces within the same channel group as the port channel. (for example, configuration changes are also propagated to the physical interfaces that are not part of the port-channel, but are part of the channel group.)
The on Keyword
When you use the on keyword, a usable EtherChannel exists only when a port group in on mode is connected to another port group in the on mode.
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
You do not have to create a port-channel interface before assigning a physical interface to a channel group. A port-channel interface is created automatically when the channel group gets its first physical interface, if it is not already created.
Cisco ASR 1000 Series Routers
The Cisco ASR 1000 series router has the following prerequisites and restriction:
•
•
•
Cisco Catalyst Switches
The number of valid values for number depends on the software release. For software releases prior to Cisco IOS Release 12.1(3a)E3, valid values are from 1 to 256; for Cisco IOS Release 12.1(3a)E3, 12.1(3a)E4, and 12.1(4)E1, valid values are from 1 to 64. Cisco IOS Release 12.1 E and later releases support a maximum of 64 values ranging from 1 to 256.
The channel-group number is global and is shared between all the channeling protocols. If a specific channel number is used for the PAgP-enabled interfaces of a channel group, that same channel number cannot be used for configuring a channel that has LACP-enabled interfaces or vice versa.
Entering the auto or desirable keyword enables PAgP on the specified interface; the command will be rejected if it is issued on an LACP-enabled interface.
The active and passive keywords are valid on PAgP-disabled interfaces only.
You can change the mode for an interface only if it is the only interface that is designated to the specified channel group.
The on keyword forces the bundling of the interface on the channel without any negotiation.
You can manually configure a switch with PAgP on one side and LACP on the other side in the on mode.
With the on mode, a usable EtherChannel exists only when a port group in on mode is connected to another port group in on mode.
If you enter the channel group command on an interface that is added to a channel with a different protocol than the protocol you are entering, the command is rejected.
If the interface belongs to a channel, the no form of this command is rejected.
All ports in the same channel group must use the same protocol; you cannot run two protocols on one channel group.
PAgP and LACP are not compatible; both ends of a channel must use the same protocol.
You can change the protocol at any time, but this change causes all existing EtherChannels to reset to the default channel mode for the new protocol.
Configure all ports in an EtherChannel to operate at the same speed and duplex mode (full duplex only for LACP mode).
All ports in a channel must be on the same DFC-equipped module. You cannot configure any of the ports to be on other modules.
On systems that are configured with nonfabric-enabled modules and fabric-enabled modules, you can bundle ports across all modules, but those bundles cannot include a DFC-equipped module port.
You do not have to create a port-channel interface before assigning a physical interface to a channel group. A port-channel interface is created automatically when the channel group gets its first physical interface, if it is not already created.
You do not have to disable the IP address that is assigned to a physical interface that is part of a channel group, but it is highly recommended.
You can create both Layer 2 and Layer 3 port channels by entering the interface port-channel command or when the channel group gets its first physical interface assignment. The port channels are not created at runtime or dynamically.
Any configuration or attribute changes that you make to the port-channel interface are propagated to all interfaces within the same channel group as the port channel (for example, configuration changes are also propagated to the physical interfaces that are not part of the port channel but are part of the channel group).
When configuring Layer 2 EtherChannels, you cannot put Layer 2 LAN ports into manually created port-channel logical interfaces.
Only the on mode is supported when using this command with GE-WAN ports on the OSM-2+4GE-WAN+ OSM to create QinQ link bundles for advanced QinQ translation. Also, you cannot use the channel-group command on GE-WAN interfaces if MPLS is configured. You must remove all IP, MPLS, and other Layer 3 configuration commands before using the channel-group command with GE-WAN interfaces.
Note
Caution
For a complete list of guidelines, see the "Configuring EtherChannel" section of the Cisco 7600 Series Router Cisco IOS Software Configuration Guide.
Fast EtherChannel
Before you assign a Fast Ethernet interface to a Fast EtherChannel group, you must first create a port-channel interface. To create a port-channel interface, use the interface port-channel global configuration command.
If the Fast Ethernet interface has an IP address assigned, you must disable it before adding the Fast Ethernet interface to the Fast EtherChannel. To disable an existing IP address on the Fast Ethernet interface, use the no ip address command in interface configuration mode.
The Fast EtherChannel feature allows multiple Fast Ethernet point-to-point links to be bundled into one logical link to provide bidirectional bandwidth of up to 800 Mbps. Fast EtherChannel can be configured between Cisco 7500 series routers and Cisco 7000 series routers with the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI) or between a Cisco 7500 series router or a Cisco 7000 series router with the RSP7000 and RSP700CI and a Cisco Catalyst 5000 switch.
A maximum of four Fast Ethernet interfaces can be added to a Fast EtherChannel group.
Caution
Fast Ethernet interfaces. Do not assign bridge groups on the physical Fast Ethernet interfaces
because it creates loops. Also, you must disable spanning tree.
To display information about the Fast EtherChannel, use the show interfaces port-channel EXEC command.
For more guidelines see the "Configuring EtherChannel" section of the Cisco 7600 Series Router Cisco IOS Software Configuration Guide and the "Configuring EtherChannel" section of the Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide.
Examples
This example shows how to add EtherChannel interface 1/0 to the EtherChannel group that is specified by port-channel 1:
Router(config-if)# channel-group 1 mode onThe following example shows how to add interface Fast Ethernet 1/0 to the Fast EtherChannel group specified by port-channel 1:
Router(config)# interface port-channel 1Router(config-if)# exitRouter(config)# interface fastethernet 1/0Router(config-if)# channel-group 1Related Commands
clear bridge-domain mac-table
To clear a bridge domain of learned MAC addresses, use the clear bridge-domain mac-table command in privileged EXEC mode.
clear bridge-domain bridge-id mac-table [mac-address]
Syntax Description
bridge-id
Integer from 1 to 16384 that identifies a bridge domain.
mac-address
(Optional) MAC address to be cleared.
Command Modes
Privileged EXEC (#)
Command History
12.2(33)SRD
This command was introduced.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
Use the clear bridge-domain mac table command to purge MAC addresses that have been dynamically learned by a bridge domain.
This command is available on both route processors and line cards. To invoke this command use the remote command module command; for example, remote command module 10 clear bridge-domain 25 mac-table.
Examples
The following example shows how to clear all dynamically learned MAC addresses in the MAC table of bridge domain 12:
Router# clear bridge-domain 12 mac tableThe following example shows how to clear a specific MAC address from the MAC table of bridge domain 12:
Router# clear bridge-domain 12 mac table 0001.0001.aaaaRelated Commands
clear ethernet cfm ais
To clear a maintenance endpoint (MEP) or server maintenance endpoint (SMEP) out of the Alarm Indication Signal (AIS) defect condition, use the clear ethernet cfm ais command in privileged EXEC mode.
Ethernet Connectivity Fault Management (CFM) Cisco Proprietary Draft 1 (CFM D1)
clear ethernet cfm ais {domain domain-name mpid mpid-id {evc name | vlan vlan-id} |
link-status interface Ethernet number}Ethernet CFM IEEE 802.1ag Standard (CFM IEEE)
clear ethernet cfm ais {domain domain-name mpid mpid-id vlan vlan-id |
link-status interface Ethernet number}Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.2(33)SRD
This command was introduced.
15.0(1)XA
This command was modified. The evc keyword and name argument are not supported in Cisco IOS Release 15.0(1)XA.
Usage Guidelines
If a MEP does not exit the AIS state when all errors are resolved, use the clear ethernet cfm ais command with the domain and mpid keywords to clear the AIS defect condition. If a SMEP does not exit the AIS state when all errors are resolved, use the clear ethernet cfm ais command with the link-status interface keywords to clear the AIS defect condition.
Examples
The following example shows how to clear a SMEP of an AIS defect condition:
Router# clear ethernet cfm ais link-status interface ethernet 0/0The following examples show how to clear a MEP of an AIS defect condition:
Router# clear ethernet cfm ais domain xxx mpid 100 vlan 11Router# clear ethernet cfm ais domain xxx mpid 100 evc testRelated Commands
clear ethernet cfm errors
To clear continuity check error conditions logged on a device, use the clear ethernet cfm errors command in privileged EXEC mode.
Cisco pre-Standard Connectivity Fault Management Draft 1.0 (CFM D1)
clear ethernet cfm errors [domain domain-name | level level-id]
CFM IEEE 802.1ag Standard (CFM IEEE)
clear ethernet cfm errors [domain-id {mac-address domain-number | domain-name | dns dns-name | null}] [service {ma-name | ma-num | vlan-id vlan-id | vpn-id vpn-id}]
Syntax Description
Command Default
The error database is unchanged; existing entries remain in the database.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the clear ethernet cfm errors command to purge error database entries that are not needed and when you want to work with a cleared database. Also, use this command with a specified domain if you want to clear errors for that domain.
In CFM IEEE, if a domain name has more than 43 characters, a warning message is displayed notifying that the maintenance domain ID (MDID) will be truncated to 43 characters in continuity check messages if "id <fmt> <MDID>" is not configured.
Examples
The following example shows a clear ethernet cfm errors command for errors at maintenance level 3. No output is generated when this command is issued.
Router# clear ethernet cfm errors level 3The following example shows how to clear errors for a DNS on VLAN 17. No output is generated when this command is issued.
Router# clear ethernet cfm errors domain-id dns Service10 service vlan-id 17Related Commands
show ethernet cfm errors
Displays CFM continuity check error conditions logged on a device since it was last reset or since the log was last cleared.
clear ethernet cfm maintenance-points remote
To purge the contents of the continuity check database, use the clear ethernet cfm maintenance-points remote command in privileged EXEC mode.
Cisco pre-Standard Connectivity Fault Management Draft 1.0 (CFM D1)
clear ethernet cfm maintenance-points remote [domain domain-name | level level-id]
CFM IEEE 802.1ag Standard (CFM IEEE)
clear ethernet cfm maintenance-points remote [domain domain-name]
Syntax Description
Command Default
The continuity check database is unchanged; existing entries remain in the database.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use this command to clear the entire continuity check database or clear the database for a specific domain or level. When a domain is specified, only entries for that domain are purged. When a level is specified, entries for all domains at that level are purged.
If a maintenance domain is not specified, the entire continuity check database is cleared.
In CFM IEEE, the level keyword and level-id argument are not supported. Also, if a domain name is more than 43 characters, a warning message is displayed notifying that the maintenance domain ID (MDID) will be truncated to 43 characters in continuity check messages if "id <fmt> <MDID>" is not configured.
Examples
The following example shows a clear ethernet cfm maintenance-points remote command. No output is generated when this command is issued.
Router# clear ethernet cfm maintenance-points remoteRelated Commands
show ethernet cfm maintenance-points remote
Displays information about remote maintenance points in the continuity check database.
clear ethernet cfm statistics
To clear a maintenance endpoint (MEP) or server maintenance endpoint (SMEP) out of the Alarm Indication Signal (AIS) defect condition, use the clear ethernet cfm ais command in privileged EXEC mode.
clear ethernet cfm statistics [mpid mpid-id]
Syntax Description
mpid
Indicates that a maintenance point ID (MPID) is specified.
mpid-id
An integer in the range of 1 to 8191 that identifies the MPID.
Command Modes
Privileged EXEC (#)
Command History
12.2(33)SXI2
This command was introduced.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
If a MEP does not exit the AIS state when all errors are resolved, use the clear ethernet cfm ais command with the domain and mpid keywords to clear the AIS defect condition. If a SMEP does not exit the AIS state when all errors are resolved, use the clear ethernet cfm ais command with the link-status interface keywords to clear the AIS defect condition.
Examples
The following example shows how to clear connectivity fault management (CFM) statistics from a SMEP of an AIS defect condition:
Router# clear ethernet cfm statistics mpid 800Related Commands
s
clear ethernet cfm traceroute-cache
To remove the contents of the traceroute cache, use the clear ethernet cfm traceroute-cache command in privileged EXEC mode.
clear ethernet cfm traceroute-cache
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the clear ethernet cfm traceroute-cache command to remove traceroute cache entries from previous traceroute operations issued on the device. This command also provides visibility into maintenance intermediate points and maintenance end points of a domain as they were recorded when the operation was performed.
Examples
The following example shows the clear ethernet cfm traceroute-cache command:
Router# clear ethernet cfm traceroute-cacheRelated Commands
clear ethernet lmi statistics
To clear Ethernet local management interface (LMI) statistics counters for all interfaces or for a specific interface, use the clear ethernet lmi statistics command in privileged EXEC mode.
clear ethernet lmi statistics [interface type number]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.4(9)T
This command was introduced.
12.2(33)SRB
Support for this command on the Cisco 7600 router was integrated into Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
This command resets counters and is useful when you want to monitor Ethernet LMI errors for a period of time. For example, to monitor errors for 1 hour, you would issue the clear ethernet lmi statistics command to reset the counter. At the end of the hour, you would issue the show ethernet lmi statistics command to display errors that occurred during that one-hour time period.
Examples
The following example shows how to clear Ethernet LMI statistics counters on all interfaces:
Router# clear ethernet lmi statisticsClear "show ethernet lmi" statistics counters on all interfaces [confirm]Router#The following example shows how to clear Ethernet LMI statistics counters on the Gigabit Ethernet 1/0 interface:
Router# clear ethernet lmi statistics interface gigabitethernet 1/0Clear "show ethernet lmi" statistics counters on this interface [confirm]Router#Related Commands
show ethernet lmi
Displays Ethernet LMI Ethernet virtual connections (EVCs) configured on a device.
show interface
Displays statistics for all interfaces configured on a device.
clear ethernet oam statistics
To reset Ethernet operations, maintenance, and administration (OAM) counters and event statistics on all interfaces or on a specific interface, use the clear ethernet oam statistics command in privileged EXEC mode.
clear ethernet oam statistics [interface type number]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use this command when you are debugging or testing and you want all statistics cleared. After this command is issued, the cleared statistics cannot be restored.
Examples
The following example shows how to clear counters and event statistics for all interfaces:
Router# clear ethernet oam statisticsRelated Commands
show ethernet oam statistics
Displays detailed information about Ethernet OAM packets.
clear ethernet service instance
To clear Ethernet service instance attributes such as MAC addresses and statistics or to purge Ethernet service instance errors, use the clear ethernet service instance command in privileged EXEC mode.
clear ethernet service instance {id id interface type number
{errdisable | mac table [address] | stats} | interface type number stats}Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the clear ethernet service instance command to clear service instance attributes that are not needed and to purge service instance errors.
Examples
The following example shows how to clear an error-disabled state on service instance 100 on interface Gigabit Ethernet 1/1:
Router(#) clear ethernet service instance id 100 interface GigabitEthernet 1/1 errdisableRelated Commands
show ethernet service instance
Displays information about Ethernet service instances.
clear lldp
To reset either Link Layer Discovery Protocol (LLDP) traffic counters or the table that contains LLDP information about neighbors, use the clear lldp command in privileged EXEC mode.
clear lldp {counters | table}
Syntax Description
counters
Specifies that the traffic counters are cleared.
table
Specifies that the LLDP table is cleared.
Command Default
The LLDP traffic counters are not reset, and the table of LLDP information is not cleared.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use this command for informational purposes or to test a symptom of network malfunction such as packet loss.
Examples
The following example shows how to clear the LLDP counters and display LLDP traffic. The output from the show lldp traffic command shows that all the traffic counters have been reset to zero.
Router# clear lldp countersRouter# show lldp trafficLLDP traffic statistics:Total frames out: 0Total entries aged: 0Total frames in: 0Total frames received in error: 0Total frames discarded: 0Total TLVs unrecognized: 0The following example shows how to clear the LLDP table. The output of the show lldp neighbors command shows that all information has been deleted from the table.
Router# clear lldp tableRouter# show lldp neighborsCapability codes:(R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device(W) WLAN Access Point, (P) Repeater, (S) Station, (O) OtherDevice ID Local Intf Hold-time Capability Port IDRelated Commands
clock destination
To specify the IP address of a Precision Time Protocol clock destination, use the clock destination command in interface configuration mode. To remove a clock destination configuration, use the no form of this command.
clock destination clock-ip-address
no clock destination clock-ip-address
Syntax Description
Command Default
No default behavior or values.
Command Modes
Clock port configuration (config-ptp-port)
Command History
Usage Guidelines
If the clock port is set to master mode with unicast and negotiation is disabled, you can only configure a single destination. If the clock port is set to master mode with unicast negotiation, you do not need to use this command because the router uses negotiation to determine the IP address of PTP slave devices.
Examples
The following example shows how to configure a PTP clock destination:
Router# configure terminalRouter(config)# ptp clock ordinary domain 0Router(config-ptp-clk)# clock-port masterPort masterRouter(config-ptp-port)# clock destination 192.168.1.2Router(config-ptp-port)# endRelated Commands
clock-port
To specify the clocking mode of a Precision Time Protocol clock port, enter clock port configuration mode using the clock-port command in the PTP clock configuration mode. To remove a clocking mode configuration, use the no form of this command.
clock-port name {slave | master}
no clock-port name {slave | master}
Syntax Description
Command Default
This command is disabled by default.
Command Modes
PTP clock configuration (config-ptp-clk)
Command History
Usage Guidelines
This command defines a new clock port and enters clock port configuration mode.
Examples
The following example shows how to configure a PTP clock port:
Router# configure terminalRouter# ptp clock boundary domain 0Router(config-ptp-clk)# clock-port slave slaveportRouter(config-ptp-port)# clock source 8.8.8.1Router(config-ptp-port)# sync limit 1Router(config-ptp-port)# announce timeout 4Router(config-ptp-port)# delay-req interval 2Router(config-ptp-port)# endRelated Commands
clock source (PTP)
To configure a connection to a Precision Time Protocol master device, use the clock source command in PTP clock port configuration mode. To remove a clock source configuration, use the no form of this command.
clock source source-address
no clock source source-address
Syntax Description
Command Default
No default behavior or values.
Command Modes
PTP clock port configuration (config-ptp-port)
Command History
Usage Guidelines
This command only applies to a clock port in slave mode.
Examples
The following example shows how to specify a clock source:
Router# configure terminalRouter(config)# ptp clock ordinary domain 0Router(config-ptp-clk)# tod 3/0 ntpRouter(config-ptp-clk)# output 1pps 3/0Router(config-ptp-clk)# clock-port slaveport slaveRouter(config-ptp-port)# transport ipv4 unicast interface GigabitEthernet3/0/1 negotiationRouter(config-ptp-port)# clock source 103.113.0.1Related Commands
continuity-check
To enable the transmission of continuity check messages (CCMs), use the continuity-check command in Ethernet connectivity fault management (CFM) service configuration mode. To disable message transmission, use the no form of this command.
continuity-check [interval time | loss-threshold threshold | static rmep]
no continuity-check [interval time | loss-threshold | static rmep]
Syntax Description
Command Default
CCMs are not transmitted.
Command Modes
Ethernet CFM service configuration (config-ecfm-srv)
Command History
12.2(33)SXI2
This command was introduced.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
The static MEP list configured using the mep mpid command is used to verify whether a MEP received in a CCM is valid. If the MEP in the received CCM is not configured in the MEP list, an error CCM received fault alarm is set.
Output of the show running all command displays "continuity-check interval 1s" when the default interval period is configured and "continuity-check loss-threshold 3" when the default loss threshold is configured.
Examples
The following example shows how to configure a loss threshold of 50 CCMs:
Router(config)# ethernet cfm domain operatorA level 5Router(config-ecfm)# service vlan-id 10 portRouter(config-ecfm-srv)# continuity-check loss-threshold 50Related Commands
mep mpid
Statically defines MEPs within a maintenance association.
show running all
Shows the running configuration with default values.
cos (CFM)
To set the class of service (CoS) for a maintenance endpoint (MEP) that will be sent in Ethernet connectivity fault management (CFM) messages, use the cos command in the Ethernet CFM interface configuration mode. To set the CoS to the highest priority allowed on the interface, use the no form of this command.
cos cos-value
no cos
Syntax Description
Command Default
If this command is not configured, the default CoS value is used.
Command Modes
Ethernet CFM interface configuration (config-if-ecfm-mep)
Command History
Usage Guidelines
This command is used to set the priority of messages.
CoS may not be supported on all platforms.
Examples
The following example shows how to set the CoS to 5:
Router(config)# ethernet cfm domain test level 5Router(config-ecfm)# service vlan-id 17 vlan 17Router(config-ecfm-srv)# endRouter# configure terminalRouter(config)# interface gigabitethernet 0/2Router(config-if)# ethernet cfm mep domain test mpid 5 vlan 17Router(config-if-ecfm-mep)# cos 5delay-req interval
To specify a recommended interval for Precision Time Protocol member devices to send delay request messages, use the delay-req interval command in PTP clock port configuration mode. To remove a delay request interval configuration, use the no form of this command.
delay-req interval interval-value unicast
no delay-req interval interval-value unicast
Syntax Description
Command Default
The default value is -4 (16 packets per second).
Command Modes
PTP clock-port configuration (config-ptp-port)
Command History
Usage Guidelines
This configuration is only required when an interface is in PTP slave mode.
Examples
The following example shows how to use the delay-req command:
Router# configure terminalRouter(config)# ptp clock ordinary domain 0Router(config-ptp-clk)# clock-port slaveport slaveRouter(config-ptp-port)# delay-req interval 2 unicastRouter(config-ptp-port)# endRelated Commands
description (mac-tunnel)
To describe the name and purpose of a MAC tunnel or a service instance under a MAC tunnel, use the description command in either MAC-in-MAC tunnel configuration mode or MAC tunnel service configuration mode. To remove a description, use the no form of this command.
description description
no description description
Syntax Description
Command Default
MAC tunnels or a service instances under MAC tunnels do not have descriptions.
Command Modes
MAC-in-MAC tunnel configuration (config-tunnel-minm)
MAC tunnel service configuration (config-tunnel-srv)Command History
Usage Guidelines
Use this command to identify and describe the type of service for which the MAC tunnel is used.
Examples
The following example shows how to add descriptions for both a MAC tunnel and a service instance under that MAC tunnel:
Router(config)# ethernet mac-tunnel virtual 100Router(config-tunnel-minm)# description MAC-Tunnel-100Router(config-tunnel-minm)# service instance 1 ethernetRouter(config-tunnel-srv)# description ServInst-1disable (CFM-AIS-link)
To disable the generation of Alarm Indication Signal (AIS) frames resulting from a link-status change (server maintenance endpoint [SMEP]), use the disable command in CFM SMEP AIS configuration mode (config-ais-link-cfm). To enable AIS frame generation, use the no form of this command.
disable
no disable
Syntax Description
This command has no arguments or keywords.
Command Default
AIS frames are generated.
Command Modes
CFM SMEP AIS configuration mode (config-ais-link-cfm)
Command History
12.2(33)SRD
This command was introduced.
15.0(1)XA
This command was integrated into Cisco IOS Release 15.0(1)XA.
Usage Guidelines
When the default value is configured, "no disable" is displayed when the show running all command is issued.
Examples
The following example shows how to disable AIS frame generation after a link-status change:
Router(config)# ethernet cfm ais link-status globalRouter(config-ais-link-cfm)# disableRelated Commands
encapsulation dot1ah isid
To configure dot1ah encapsulation for a specific service instance ID (I-SID), use the encapsulation dot1ah isid command in MAC tunnel service configuration mode. To remove dot1ah encapsulation for an I-SID, use the no form of this command.
encapsulation dot1ah isid isid
no encapsulation dot1ah isid isid
Syntax Description
Command Default
Encapsulation is not configured.
Command Modes
MAC tunnel service configuration (config-tunnel-srv)
Command History
Usage Guidelines
The I-SID is used to indicate a service in the provider backbone bridge (PBB) network. You can define the service, which can be a customer or a particular customer and type of data; for example, voice or video.
Examples
The following example shows how to configure dot1ah encapsulation for I-SID 500:
Router(config)# ethernet mac-tunnel virtual 1Router(config-tunnel-mimn)# service instance 1 ethernetRouter(config-tunnel-srv)# encapsulation dot1ah isid 500errdisable recovery cause mac-security
To enable automatic recovery of a service instance after a MAC security violation, use the errdisable recovery cause mac-security command in service instance configuration mode. To disable the automatic recovery mechanism, use the no form of this command.
errdisable recovery cause mac-security interval
no errdisable recovery cause mac-security interval
Syntax Description
Command Default
Automatic recovery of a service instance is disabled.
Command Modes
Service instance configuration (config-if-srv)
Command History
Usage Guidelines
A cause is the reason why the error-disabled state occurred. When a cause is detected on a service instance, the service instance is placed in the error-disabled state (an operational state that is similar to the shutdown state). When you enable automatic error recovery, the service instance is brought out of the error-disabled state and allowed to retry the operation after all the causes have timed out. If you do not enable automatic error recovery, the service instance stays in the error-disabled state until the shutdown and no shutdown commands are issued.
Alternatively, you can use the clear ethernet service instance command to bring the service instance out of the error-disabled state.
Examples
The following example shows how to enable the automatic recovery of service instance 200 after a MAC security violation and to specify a recovery time of 30 seconds.
Router> enableRouter# configure terminalRouter(config)# interface gigabitethernet 3/0/1Router(config-if)# service instance 200 ethernetRouter(config-if-srv)# encapsulation dot1Q 200Router(config-if-srv)# bridge-domain 100Router(config-if-srv)# mac securityRouter(config-if-srv)# errdisable recovery cause mac-security 30Related Commands
clear ethernet service instance
Clears the Ethernet service instance error-disable state.
show ethernet service instance
Displays information about Ethernet service instances.
errdisable recovery cause mlacp-minlink
To enable automatic recovery from a failover state of the port channel, use the errdisable recovery cause mlacp-minlink command in global configuration mode. To disable this command, use the no form of this command.
errdisable recovery cause mlacp-minlink
[no] errdisable recovery cause mlacp-minlink
Syntax Description
This command has no arguments or keywords.
Command Default
This command is disabled by default. If the errdisable recovery cause mlacp-minlink is not enabled, the links stay in the ERR_DISABLE state until a shut/no shut is entered on the links.
Command Modes
Global config (config)
Command History
Usage Guidelines
Use the errdisable recovery cause mlacp-minlink command to enable automatic recovery on the interface from the ERR_DISABLE state. This command tries to bring the port-channel interface out of the ERR_DISABLE state and retry operation after all the causes have timed out. To set the interval for recovery, configure the errdisable recovery interval command.
Examples
The following example shows how to enable recovery from the ERR_DISABLE state and set the interval to 100 seconds:
errdisable recovery cause mlacp-minlinkerrdisable recovery interval 100Related Commands
lacp failover
Sets the mLACP switchover to non-revertive or brute force.
errdisable recovery interval
Sets the interval time for recovery from the ERR_DISABLE state.
ethernet cfm ais
To configure Alarm Indication Signal (AIS) generation from a server maintenance endpoint (SMEP), use the ethernet cfm ais command in global configuration mode. To disable AIS generation from a SMEP, use the no form of this command.
ethernet cfm ais {domain domain-name {evc name | vlan {vlan-id | ,vlan-id | vlan-id-vlan-id | ,vlan-id-vlan-id} | link-status {global}}
no ethernet cfm ais {domain domain-name {evc name | vlan {vlan-id | ,vlan-id | vlan-id-vlan-id | ,vlan-id-vlan-id} | link-status {global}}
Syntax Description
Command Default
AIS generation is enabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The ethernet cfm ais command allows you to configure, enable, or disable AIS generation from a MEP or SMEP. To change default values for AIS generation on a SMEP, use the link-status global keywords. To change default values for AIS generation on a MEP, use the domain keyword.
Examples
The following example shows how to specify AIS generation on a domain named PROVIDER and VLAN 10:
Router(config)# ethernet cfm ais domain PROVIDER vlan 10The following example shows how to enable AIS generation and place the CLI in CFM SMEP AIS configuration mode:
Router(config)# ethernet cfm ais link-status globalRouter(config-ais-mep-cfm)#Related Commands
ethernet cfm ais link-status
To enable Alarm Indication Signal (AIS) generation from a server maintenance endpoint (SMEP), use the ethernet cfm ais link-status command in interface configuration mode. To disable AIS generation, use the no form of this command.
ethernet cfm ais link-status [level level-id | period seconds]
no ethernet cfm ais link-status [level | period]
Syntax Description
Command Default
AIS frames are not generated.
Command Modes
Interface configuration (config-if)
Command History
15.0(1)XA
This command was introduced.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
This command has precedence over the ethernet cfm ais link-status global command issued in global configuration mode.
Examples
The following example shows how to configure AIS generation with a transmission period of 60 seconds:
Router(config-if)# ethernet cfm ais link-status period 60Related Commands
ethernet cfm ais link-status global
Globally enables AIS generation and places the CLI in CFM SMEP AIS configuration mode.
ethernet cfm ais link-status global
To globally enable Alarm Indication Signal (AIS) generation and place the command-line interface (CLI) in CFM SMEP AIS configuration mode (config-ais-link-cfm) to configure AIS commands for a server maintenance endpoint (SMEP), use the ethernet cfm ais link-status global command in global configuration mode. To remove the global AIS configuration, use the no form of this command.
ethernet cfm ais link-status global
no ethernet cfm ais link-status global
Syntax Description
This command has no arguments or keywords.
Command Default
AIS generation is enabled.
Command Modes
Global configuration (config)
Command History
12.2(33)SRD
This command was introduced.
15.0(1)XA
This command was integrated into Cisco IOS Release 15.0(1)XA.
Usage Guidelines
The ethernet cfm ais link-status global command changes configuration modes to allow you to configure AIS commands for a SMEP.
Examples
The following example shows how to configure AIS commands for a SMEP:
Router(config)# ethernet cfm ais link-status globalRouter(config-ais-link-cfm)#ethernet cfm alarm
To configure an alarm for Ethernet connectivity fault management (CFM), use the ethernet cfm alarm command in global configuration mode. To restore the command options' default values, use the no form of this command.
ethernet cfm alarm {delay milliseconds | notification {all | error-xcon | mac-remote-error-xcon | none | remote-error-xcon | xcon} | packet max-num | reset milliseconds}
no ethernet cfm alarm {delay | notification {all | error-xcon | mac-remote-error-xcon | none | remote-error-xcon | xcon} | packet | reset}
Syntax Description
Syntax Description
Command Default
Ethernet CFM alarms are disabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
If a higher priority defect occurs after a lower priority defect has triggered an alarm but before the alarm has reset, immediately issue another fault alarm for the higher priority defect.
Output of the show running all command displays "ethernet cfm alarm delay 2500" when the default value for the delay option is configured and "ethernet cfm alarm reset 10000" when the default value for the reset option is configured.
Examples
The following example shows how to set up notification for all defects:
Router(config)# ethernet cfm alarm notification allThe following example shows how to set the time during which one or more defects must be present before a fault alarm is issued to 5000 ms:Router(config)# ethernet cfm alarm delay 5000The following example shows how to set the maximum number of DefError and DefXcon fault alarm packets to 6500:Router(config)# ethernet cfm alarm packet 6500Related Commands
ethernet cfm cc
To set parameters for continuity check messages (CCMs), use the ethernet cfm cc command in global configuration mode. To reset parameters to their default values, use the no form of this command.
ethernet cfm cc level {any | level-id | level-id-level-id | [,level-id-level-id]} {evc evc-name | vlan {vlan-id | any | vlan-id-vlan-id | [,vlan-id-vlan-id]}} [interval seconds] [loss-threshold num-msgs]
no ethernet cfm cc level {any | level-id | level-id-level-id | [,level-id-level-id]} {evc evc-name | vlan {vlan-id | any | vlan-id-vlan-id | [,vlan-id-vlan-id]}} [interval seconds] [loss-threshold num-msgs]
Syntax Description
Command Default
For all maintenance levels and VLANs configured on a device, the interval is 30 seconds and the loss-threshold is 2.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The ethernet cfm cc command is used to set parameters for generating and receiving CCMs in one of the following ways:
•
•
•
•
When the ethernet cfm cc command is issued, the system may perform optimizations by concatenating possible ranges, and the configuration may not go through nonvolatile generation (NVGEN) as it was originally entered.
If you configure the ethernet cfm cc command with the default values for interval and loss threshold, these parameters will not display after NVGEN. If you configure the command with at least one parameter not at the default value, all parameters are displayed.
An EVC is an association of two or more user network interfaces (UNIs).
Note
Examples
The following example shows how to configure an Ethernet CFM level ID of 5 for all VLANs, with messages transmitted every 30 seconds and a remote MEP declared down after two messages are missed. Note that the interval and loss-threshold parameters are configured for the default values and do not display after NVGEN.
Router(config)# ethernet cfm cc level 5 vlan any interval 30 loss-threshold 2 (NVGEN)ethernet cfm cc level 5 vlan anyThe following example shows how to configure an Ethernet CFM level ID of 5 for all VLANs, with messages transmitted every 1000 seconds and a remote MEP declared down after two messages (the default value) are missed:
Router(config)# ethernet cfm cc level 5 vlan any interval 1000 loss-threshold 2 (NVGEN)ethernet cfm cc level 5 vlan any interval 1000The following example shows how to configure an Ethernet CFM level ID of 5 for all VLANs, with messages transmitted every 1000 seconds and a remote MEP declared down after 7 messages are missed (neither value is a default value):
Router(config)# ethernet cfm cc level 5 vlan any interval 1000 loss-threshold 7 (NVGEN)ethernet cfm cc level 5 vlan any interval 1000 loss-threshold 7The following example shows how to configure Ethernet CFM for multiple levels for VLANs 100 to 200 with messages transmitted every 50 seconds and a remote MEP declared down after 5 messages are missed (neither value is a default value):
Router(config)# ethernet cfm cc level 1-5 vlan 100-200 interval 50 loss-threshold 5Router(config)# no ethernet cfm cc level 2-3 vlan 50-150 interval 50 loss-threshold 5(NVGEN)ethernet cfm cc level 2-3 vlan 151-200 interval 50 loss-threshold 5ethernet cfm cc level 1,4-5 vlan 100-200 interval 50 loss-threshold 5The following example shows how to configure Ethernet CFM level ID of 5 for EVC evc5, with messages transmitted every 50 seconds and a remote MEP declared down after 3 messages are missed (neither value is a default value):
Router(config)# ethernet cfm cc level 5 evc evc5 interval 50 loss-threshold 3(NVGEN)ethernet cfm cc level 5 evc evc5 interval 50 loss-threshold 3ethernet cfm cc enable level evc
To globally enable transmission of continuity check messages (CCMs), use the ethernet cfm cc enable level evc command in global configuration mode. To disable transmission of CCMs, use the no form of this command.
ethernet cfm cc enable level {any | level-id | ,level-id | level-id-level-id | ,level-id-level-id} evc evc-name
no ethernet cfm cc enable level {any | level-id | ,level-id | level-id-level-id | ,level-id-level-id} evc evc-name
Syntax Description
Command Default
No CCMs are transmitted.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use the ethernet cfm cc enable level evc command to enable transmission of CCMs in one of the following ways:
•
•
•
•
Examples
The following example shows how to configure the ethernet cfm cc enable level evc command for EVC evc5:
Router (config)# ethernet cfm cc enable level 5 evc evc5How you enter the ethernet cfm cc enable level evc command and the format you see in the configuration may be different. For example, if you enter:
Router(config)# ethernet cfm cc enable level 1,2,3,4,5 evc evc1The configuration shows the following:
ethernet cfm cc enable level 1-5 evc evc1To shorten the length of the command, you also can enter it as shown in the following example:
Router(config)# ethernet cfm cc enable level 1-5 evc evc1Related Commands
ethernet cfm cc enable level vlan
Use the ethernet cfm cc enable level vlan command in global configuration mode to globally enable transmission of continuity check messages (CCMs). To disable transmission of CCMs, use the no form of this command.
ethernet cfm cc enable level {any | level-id | ,level-id | level-id-level-id | ,level-id-level-id} vlan {any | vlan-id | ,vlan-id | vlan-id-vlan-id | ,vlan-id-vlan-id}
no ethernet cfm cc enable level {any | level-id | ,level-id | level-id-level-id | ,level-id-level-id} vlan {any | vlan-id | ,vlan-id | vlan-id-vlan-id | ,vlan-id-vlan-id}
Syntax Description
Syntax DescriptionCommand Syntax]
Command Default
No CCMs are transmitted.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use the ethernet cfm cc enable level vlan command to enable transmission of CCMs in one of the following ways:
•
•
•
•
How you enter the ethernet cfm cc enable level vlan command and the format you see in the configuration may be different. For example, if you enter:
Router(config)# ethernet cfm cc enable level 1,2,3,4,5 vlan 100,101,102,103,105The configuration shows the following:
ethernet cfm cc enable level 1-5 vlan 100-103,105To shorten the length of the command, you also can enter it this way.
Examples
The following examples show how this command functions:
1.
ethernet cfm cc enable level 1-5 vlan 100-2002.
Router(config)# no ethernet cfm cc enable level 2-3 vlan 50-1503.
ethernet cfm cc enable level 1,4-5 vlan 100-200ethernet cfm cc enable level 2-3 vlan 151-200ethernet cfm distribution enable
To enable the Ethernet connectivity fault management (CFM) distribution, use the ethernet cfm distribution enable command in the global configuration mode. To turn off distribution, use the no form of this command.
ethernet cfm distribution enable
no ethernet cfm distribution enable
Syntax Description
This command has no arguments or keywords.
Command Default
Ethernet CFM distribution is off when this command is not configured.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
On the Cisco 7600 router, this command must be configured before Ethernet performance monitoring (EPM) sessions are configured.
When you issue the no ethernet cfm distribution enable command, all EPM sessions on the route processor and on the line card are removed, but the IP SLA configurations remain. If you do not want any Y.1731 performance monitoring sessions, you must remove the IP SLA configurations. You can use the ip sla reset command to clear all the IP SLA configurations or you can clear each one individually.
Examples
The following example shows how to enable Ethernet CFM distribution:
Router(config)# ethernet cfm distribution enableethernet cfm domain level
To define a connectivity fault management (CFM) maintenance domain at a particular maintenance level and put the command-line interface (CLI) into Ethernet CFM configuration mode, use the ethernet cfm domain level command in global configuration mode. To remove the CFM domain at the specified level, use the no form of this command.
ethernet cfm domain domain-name level level-id [direction outward]
no ethernet cfm domain domain-name level level-id
Syntax Description
Command Default
No maintenance domains are assigned to maintenance levels if this command is not issued.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
When a router is in Ethernet CFM configuration mode, parameters specific to a maintenance domain can be set. Several domains, with different names, can be configured at the same maintenance level; however, a single domain cannot be associated with multiple levels.
In CFM IEEE, if a domain name has more than 43 characters, a warning message is displayed notifying that the maintenance domain ID (MDID) will be truncated to 43 characters in continuity check messages if "id <fmt> <MDID>" is not configured.
When this command places the CLI in Ethernet configuration mode, in CFM D1 the mode prompt is "config-ether-cfm" and in CFM IEEE the mode prompt is "config-ecfm."
Examples
The following example shows how to define an outward facing domain named domain1 at level 6 and that the CLI mode changes to Ethernet CFM configuration mode:
Router(config)# ethernet cfm domain domain1 level 6 direction outwardRouter(config-ether-cfm)#The following example shows how to define a domain named cust10 at level 5 and also shows the Ethernet CFM configuration mode prompt that is displayed in the CFM IEEE Standard implementation:
Router(config)# ethernet cfm domain cust10 level 5Router(config-ecfm)#Related Commands
ethernet cfm enable (interface)
To enable connectivity fault management (CFM) processing on an interface, use the ethernet cfm enable command in interface configuration mode. To disable CFM processing on an interface, use the no form of this command.
ethernet cfm enable
no ethernet cfm enable
Syntax Description
This command has no arguments or keywords.
Command Default
Ethernet CFM is enabled.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Ethernet CFM is enabled by default on an interface and must be disabled explicitly. When CFM is disabled on an interface, hardware resources (for example, port-ASIC match-registers) are released for that interface.
This command is mutually exclusive of maintenance intermediate point (MIP) and maintenance end point (MEP) configuration commands. The interface must be enabled before any MEPs or MIPs can be configured. Similarly, disabling a port that has MIPs or MEPs configured is not allowed. The user must first unconfigure the maintenance points.
When CFM processing is disabled on an interface, all CFM frames that arrive at that interface are forwarded as normal data traffic, and are not processed by the CPU.
Examples
The following example shows how to disable and then enable CFM processing on an interface:
Router(config-if)# no ethernet cfm enableRouter(config-if)# ethernet cfm enableethernet cfm enable
To enable connectivity fault management (CFM) processing globally on a device, use the ethernet cfm enable command in global configuration mode. To disable CFM processing globally on a device, use the no form of this command.
ethernet cfm enable
no ethernet cfm enable
Syntax Description
This command has no arguments or keywords.
Command Default
Ethernet CFM is disabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Ethernet CFM is disabled by default and must be enabled explicitly. When CFM is configured, hardware resources (for example, port-ASIC match-registers) are allocated for CFM.
Examples
The following example shows how to enable CFM processing globally on a device:
Router(config)# ethernet cfm enableethernet cfm global
To enable Ethernet connectivity fault management (CFM) globally on a device, use the ethernet cfm global command in global configuration mode. To disable CFM globally on a device, use the no form of this command.
ethernet cfm global
no ethernet cfm global
Syntax Description
This command has no arguments or keywords.
Command Default
Ethernet CFM is disabled.
Command Modes
Global configuration (config)
Command History
12.2(33)SXI2
This command was introduced.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
Ethernet CFM is disabled by default and must be enabled explicitly. When CFM is configured, hardware resources (for example, port-ASIC match registers) are allocated for CFM.
This command is supported only in the Ethernet CFM IEEE 802.1ag Standard implementation.
Examples
The following example shows how to enable CFM globally on a device:
Router(config)# ethernet cfm globalethernet cfm ieee
To enable the Ethernet Connectivity Fault Management 802.1ag Standard (CFM IEEE) version of CFM, use the ethernet cfm ieee command in global configuration mode. To disable the CFM IEEE version, use the no form of this command.
ethernet cfm ieee
no ethernet cfm ieee
Syntax Description
This command has no arguments or keywords.
Command Default
Ethernet CFM IEEE is disabled.
Command Modes
Global configuration (config)
Command History
12.2(33)SXI2
This command was introduced.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
This command is auto-generated when CFM is enabled and running IEEE CFM. In Cisco pre-Standard CFM Draft 1 (CFM D1), this command is not supported.
Examples
The following example shows how to enable Ethernet CFM IEEE:
Router(config)# ethernet cfm ieeeethernet cfm interface
To enable Ethernet connectivity fault management (CFM) processing on a port, use the ethernet cfm interface command in interface configuration mode. To disable Ethernet CFM processing, use the no form of this command.
ethernet cfm interface
no ethernet cfm interface
Syntax Description
This command has no arguments or keywords.
Command Default
CFM processing is enabled.
Command Modes
Interface configuration (config-if)
Command History
12.2(33)SXI2
This command was introduced.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
This command is mutually exclusive of the maintenance intermediate point (MIP) and maintenance endpoint (MEP) configuration commands. A port must be enabled before any MEPs or MIPs can be configured. Similarly, maintenance points must be unconfigured before a port configured with MIPs or MEPs can be disabled.
When CFM processing is disabled on a port, all CFM frames that arrive at that port are dropped and are not processed by the CPU.
CFM is enabled by default on a port and must be disabled explicitly. When CFM is disabled on a port, hardware resources such as port-ASIC match registers are released for that port.
Examples
The following example shows how to configure an Ethernet interface for CFM processing:
Router(config-if)# ethernet cfm interfaceethernet cfm logging
To enable Ethernet Connectivity Fault Management (CFM) syslog messages, use the ethernet cfm logging command in global configuration mode. To disable CFM syslog messages, use the no form of this command.
Cisco pre-Standard CFM Draft 1 (CFM D1)
ethernet cfm logging [ais | alarm {cisco | ieee}]
no ethernet cfm logging [ais | alarm {cisco | ieee}]
CFM IEEE 802.1ag Standard (CFM IEEE)
ethernet cfm logging [ais | alarm {cisco | ieee} | lck]
no ethernet cfm logging [ais | alarm {cisco | ieee} | lck]
Syntax Description
Command Default
CFM logging is not enabled.
Command Modes
Global configuration (config)
Command History
12.2(33)SRD
This command was introduced.
12.2(33)SXI2
This command was integrated into Cisco IOS Release 12.2(33)SXI2.
Examples
The following example shows how to enable all Ethernet CFM syslog messages:
Router(config)# ethernet cfm loggingThe following example shows how to enable all alarm syslog messages for Cisco MIBs:
Router(config)# ethernet cfm logging alarm ciscoThe following example shows how to enable syslog messages specific to the CFM AIS feature:
Router(config)# ethernet cfm logging ais
