Table Of Contents
ethernet oam link-monitor frame
ethernet oam link-monitor frame-period
ethernet oam link-monitor frame-seconds
ethernet oam link-monitor high-threshold action
ethernet oam link-monitor receive-crc
ethernet oam link-monitor supported
ethernet oam link-monitor symbol-period
ethernet oam link-monitor transmit-crc
ethernet oam remote-loopback (interface)
mac tunnel address destination default
mac tunnel address destination map
service instance ethernet (mac-tunnel)
ethernet mac-tunnel virtual
To configure a virtual MAC-in-MAC tunnel and place the command-line interface (CLI) into MAC-in-MAC tunnel configuration mode, use the ethernet mac-tunnel virtual command in global configuration mode. To remove the configured virtual MAC-in-MAC tunnel, use the no form of this command.
ethernet mac-tunnel virtual tunnel-id
no ethernet mac-tunnel virtual tunnel-id
Syntax Description
tunnel-id
Integer from 1 to 2147483647 that identifies the MAC-in-MAC tunnel.
•
The upper limit may vary based on the platform.
Command Default
No virtual MAC-in-MAC tunnels are configured.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Multiple MAC tunnels with the same identifier cannot coexist on a single bridge.
In Cisco IOS Release 12.2(33)SRE, the platform upper limit for tunnel IDs is 4094.
Examples
The following example shows how to configure a virtual MAC-in-MAC tunnel and place the CLI into MAC-in-MAC tunnel configuration mode:
Router> enableRouter# configure terminalRouter(config)# ethernet mac-tunnel virtual 100Router(config-tunnel-minm)#ethernet oam
To enable Ethernet operations, maintenance, and administration (OAM) on an interface, use the ethernet oam command in interface configuration mode. To disable Ethernet OAM on an interface, use the no form of this command.
ethernet oam [max-rate oampdus | min-rate num-seconds | mode {active | passive} | timeout seconds]
no ethernet oam [max-rate | min-rate | mode {active | passive} | timeout]
Syntax Description
Command Default
Ethernet OAM is disabled.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
When Ethernet OAM is configured on an interface, the default mode of the OAM client is active. When the Ethernet OAM mode is enabled on two interfaces passing traffic, both interfaces cannot be in passive mode. Both interfaces can be in active mode, and one can be in active mode and the other in passive mode. You can toggle between Ethernet OAM modes without disabling OAM.
The min-rate num-seconds keyword and argument pair controls the minimum rate at which OAM PDUs can be sent on an interface, in seconds. A value of n, where 1 is less than or equal to n and n is less than or equal to 10, indicates that an OAM PDU must be sent at least once per n seconds. If no other OAM PDU is to be sent within an n-second window, an information OAM PDU must be sent.
Examples
The following example shows how to activate an Ethernet OAM interface that was previously configured to be in passive mode:
Router(config)# interface gigabitethernet 0/1Router(config-if)# ethernet oam mode activeThe following example shows how to set the maximum transmission rate of OAM PDUs on interface GigabitEthernet 0/1 to 5 transmissions per second:
Router(config)# interface gigabitethernet 0/1Router(config-if)# ethernet oam max-rate 5The following example shows how to set the timeout period to 25 seconds on interface GigabitEthernet 0/1:
Router(config)# interface gigabitethernet 0/1Router(config-if)# ethernet oam timeout 25ethernet oam link-monitor frame
To configure an error frame threshold or window on an Ethernet operations, maintenance, and administration (OAM) interface, use the ethernet oam link-monitor frame command in configuration template mode or interface configuration mode. To remove the threshold or window, use the no form of this command.
ethernet oam link-monitor frame {threshold {high {none | high-frames} | low low-frames} | window milliseconds}
no ethernet oam link-monitor frame {threshold {high | low} | window}
Syntax Description
Command Default
The ethernet oam link-monitor frame command is not configured.
Command Modes
Configuration template (config-template)
Interface configuration (config-if)Command History
Usage Guidelines
The ethernet oam link-monitor frame command configures a number of error frames that triggers an action or a period of time in which error frames are counted.
Examples
The following example shows how to configure an Ethernet OAM link-monitor frame window of 3000 milliseconds:
Router(config-template)# ethernet oam link-monitor frame window 300Related Commands
ethernet oam link-monitor frame-period
To configure an error frame period on an Ethernet operations, maintenance, and administration (OAM) interface, use the ethernet oam link-monitor frame-period command in configuration template or interface configuration mode. To remove the frame period, use the no form of this command.
ethernet oam link-monitor frame-period {threshold {high {none | high-frames} | low low-frames} | window frames}
no ethernet oam link-monitor frame-period {threshold {high | low} | window}
Syntax Description
Command Default
The ethernet oam link-monitor frame-period command is not configured.
Command Modes
Configuration template (config-template)
Interface configuration (config-if)Command History
Usage Guidelines
The ethernet oam link-monitor frame-period command configures an error frame period in number of frames. When a high threshold is configured, it must be at least as great as the low threshold for frame errors.
The number of frames polled is user defined. Note that the system can poll only by time, not by frames. The number of frames you specify is converted internally to seconds using a formula that includes interface speed.
Examples
The following example shows how to configure an Ethernet OAM link-monitor frame-period window of 20000 frames:
Router(config-template)# ethernet oam link-monitor frame-period window 2The following example shows how to configure an Ethernet OAM link-monitor frame-period low threshold of 500 frames:
Router(config-template)# ethernet oam link-monitor frame-period threshold low 500Related Commands
ethernet oam link-monitor frame-seconds
To configure a frame-seconds period on an Ethernet operations, maintenance, and administration (OAM) interface, use the ethernet oam link-monitor frame-seconds command in configuration template and interface configuration mode. To remove the threshold or window, use the no form of this command.
ethernet oam link-monitor frame-seconds {threshold {high {none | high-frames} | low low-frames} | window milliseconds}
no ethernet oam link-monitor frame-seconds {threshold {high | low} | window}
Syntax Description
Command Default
The ethernet oam link-monitor frame-seconds command is not configured.
Command Modes
Configuration template (config-template)
Interface configuration (config-if)Command History
Usage Guidelines
The ethernet oam link-monitor frame-seconds command configures a number of error frames that triggers an action or a period of time in which error frames are counted.
Examples
The following example shows how to configure an Ethernet OAM link-monitor frame-seconds window of 30000 milliseconds (30 seconds):
Router(config-template)# ethernet oam link-monitor frame-seconds window 300Related Commands
ethernet oam link-monitor high-threshold action
To configure a specific action to occur when a high threshold for an error is exceeded on an Ethernet operations, maintenance, and administration (OAM) interface, use the ethernet oam link-monitor high-threshold action command in configuration template mode. To remove the high-threshold action, use the no form of this command.
ethernet oam link-monitor high-threshold action {error-disable-interface | failover}
no ethernet oam link-monitor high-threshold action
Syntax Description
error-disable-interface
Performs an error-disable function on the interface.
failover
Performs a failover to another port in the same PortChannel.
Command Default
A high-threshold action is not configured.
Command Modes
Configuration template (config-template)
Command History
Usage Guidelines
The failover action is applicable only to EtherChannel interfaces. It provides an automatic failover of traffic from one port in an EtherChannel to another port in the same EtherChannel when one of the ports in the channel exceeds the high threshold for an error within the specified interval. The port failover occurs only if at least one operational port is in the EtherChannel. The failed port is put into an error-disable state. If the failed port is the last port in the EtherChannel, the port will not be put into the error-disable state and will continue to pass traffic regardless of the types of errors received.
Single, nonchanneling ports go into the error-disable state when the error high threshold is exceeded within the specified interval.
Examples
The following example shows how to configure an error-disable-interface action to occur when the high threshold for an error is exceeded:
Router(config-template)# ethernet oam link-monitor high-threshold action error-disable-interfaceRelated Commands
ethernet oam link-monitor on
To enable link monitoring on an Ethernet operations, maintenance, and administration (OAM) interface, use the ethernet oam link-monitor on command in interface configuration mode. To disable link monitoring, use the no form of this command.
ethernet oam link-monitor on
no ethernet oam link-monitor on
Syntax Description
This command has no arguments or keywords.
Command Default
Link monitoring is turned on when Ethernet OAM is enabled.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
When link monitoring is enabled, the interface sends event OAM protocol data units (PDUs) when errors occur and interprets event OAM PDUs from the remote peer. Link monitoring can be effective only if both the local client and remote peer agree to support it.
The ethernet oam link-monitor on command is enabled by default when Ethernet OAM is enabled and does not display in the configuration when the show running-config command is issued.
When link monitoring is enabled by default, to turn it off you must explicitly disable it by issuing the no form of this command.
Examples
The following example shows how to disable link monitoring on Ethernet OAM interface Ethernet 0/1:
Router(config)# interface ethernet 0/1Router(config-if)# no ethernet oam link-monitor onRelated Commands
ethernet oam link-monitor supported
Enables support for link monitoring on an Ethernet OAM interface.
ethernet oam link-monitor receive-crc
To configure an Ethernet operations, maintenance, and administration (OAM) interface to monitor ingress frames received with cyclic redundancy code (CRC) errors for a period of time, use the ethernet oam link-monitor receive-crc command in configuration template or interface configuration mode. To disable monitoring, use the no form of this command.
ethernet oam link-monitor receive-crc {threshold {high {high-frames | none} | low low-frames} | window milliseconds}
no ethernet oam link-monitor receive-crc {threshold {high | low} | window}
Syntax Description
Command Default
The ethernet oam link-monitor receive-crc command is not configured.
Command Modes
Configuration template (config-template)
Interface configuration (config-if)Command History
Usage Guidelines
OAM must be operational on the interface before you issue this command.
Examples
The following example shows how to configure a receive-crc period with a low threshold of 3000:
Router(config-if)# ethernet oam link-monitor receive-crc threshold low 3000Related Commands
ethernet oam link-monitor supported
To enable support for link monitoring on an Ethernet operations, maintenance, and administration (OAM) interface, use the ethernet oam link-monitor supported command in interface configuration mode. To disable link monitoring support, use the no form of this command.
ethernet oam link-monitor supported
no ethernet oam link-monitor supported
Syntax Description
This command has no arguments or keywords.
Command Default
Link monitoring is supported when Ethernet OAM is enabled.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Use this command to help establish an OAM session for performing OAM functions, such as remote loopback. For example, if your device is connected to a third-party device that does not support link monitoring, you must disable link monitoring support on your device to establish an OAM session with the third-party device.
When the ethernet oam link-monitor supported command has been issued, remote loopback will not function, whether or not an interface has been configured to support it.
The ethernet oam link-monitor supported command is enabled by default when Ethernet OAM is enabled and does not display in the configuration when the show running-config command is issued.
When support for link monitoring is enabled by default, to turn it off you must explicitly disable it by issuing the no form of this command.
Examples
The following example shows how to disable support for link monitoring on the GigabitEthernet 0/1 OAM interface:
Router(config)# interface gigabitethernet 0/1Router(config-if)# no ethernet oam link-monitor supportedThe following example shows how to reenable support for link monitoring on the GigabitEthernet 0/1 OAM interface after support has been disabled:
Router(config)# interface gigabitethernet 0/1Router(config-if)# ethernet oam link-monitor supportedRelated Commands
ethernet oam link-monitor symbol-period
To configure an error symbol period on an Ethernet operations, maintenance, and administration (OAM) interface, use the ethernet oam link-monitor symbol-period command in configuration template or interface configuration mode. To remove the symbol period, use the no form of this command.
ethernet oam link-monitor symbol-period {threshold {high {none | high-symbols} | low low-symbols} | window symbols}
no ethernet oam link-monitor symbol-period {threshold {high | low} | window}
Syntax Description
Command Default
The ethernet oam link-monitor symbol-period command is not configured.
Command Modes
Configuration template (config-template)
Interface configuration (config-if)Command History
Usage Guidelines
The ethernet oam link-monitor symbol-period command configures an error symbol threshold or error symbol window in number of symbols. When a high threshold is configured, it must be at least as great as the low threshold for symbol errors.
This command can be applied to an Ethernet OAM template and to an interface. The value configured on an interface takes precedence over the value configured by this command for the template.
This command is prefixed with "ether oam" in interface configuration mode.
Examples
The following example shows how to configure a symbol-period window of 500 million error symbols:
Router(config-template)# ethernet oam link-monitor symbol-period window 500The following example shows how to configure a symbol-period low threshold of 500 error symbols:
Router(config-template)# ethernet oam link-monitor symbol-period threshold low 500Related Commands
ethernet oam link-monitor transmit-crc
To configure an Ethernet operations, maintenance, and administration (OAM) interface to monitor egress frames transmitted with cyclic redundancy code (CRC) errors for a period of time, use the ethernet oam link-monitor transmit-crc command in configuration template or interface configuration mode. To disable monitoring, use the no form of this command.
ethernet oam link-monitor transmit-crc {threshold {high {high-frames | none} | low low-frames} | window milliseconds}
no ethernet oam link-monitor transmit-crc {threshold {high | low} | window}
Syntax Description
Command Default
The ethernet oam link-monitor transmit-crc command is not configured.
Command Modes
Configuration template (config-template)
Interface configuration (config-if)Command History
Usage Guidelines
OAM must be operational on the interface before you issue this command.
Examples
The following example shows how to configure a transmit CRC window of 2500 milliseconds:
Router(config-if)# ethernet oam link-monitor transmit-crc window 25Related Commands
ethernet oam mib log size
To set the size of the Ethernet Operations, Administration, and Maintenance (OAM) event log table, use the ethernet oam mib log size command in global configuration mode. To remove the event log table, use the no form of this command.
ethernet oam mib log size entries
no ethernet oam mib log size
Syntax Description
entries
Number of entries that the event log table will hold. Integer from 0 to 200. The minimum is 0, the maximum is 200, and the default is 50.
Command Default
An event log table is not configured.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use this command to configure an OAM event log table.
Examples
The following example shows how to set the size of an event log table to 100 entries:
Router# configure terminal Router(config)# ethernet oam mib log size 100ethernet oam remote-loopback
To turn on or off Ethernet operations, maintenance, and administration (OAM) remote loopback functionality on an interface, use the ethernet oam remote-loopback command in privileged EXEC mode. This command does not have a no form.
ethernet oam remote-loopback {start | stop} {interface type number}
Syntax Description
Command Default
Remote loopback functionality is turned off.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
A no form of this command is not available.
When Ethernet OAM remote loopback functionality is enabled on an interface, traffic sent out on this interface will be discarded or sent back (and dropped locally) by the remote interface.
Remote loopback will not function, whether or not an interface has been configured to support it, when the no ethernet oam link-monitor supported command has been issued.
Note
Examples
The following example shows how to start a remote loopback session on interface GigabitEthernet 2/1:
Router# ethernet oam remote-loopback start interface gigabitethernet2/1Related Commands
ethernet oam remote-loopback (interface)
To enable the support of Ethernet operations, maintenance, and administration (OAM) remote loopback operations on an interface or set a remote loopback timeout period, use the ethernet oam remote-loopback (interface) command in interface configuration mode. To disable support or remove the timeout setting, use the no form of this command.
ethernet oam remote-loopback {supported | timeout seconds}
no ethernet oam remote-loopback {supported | timeout}
Syntax Description
supported
Supports the remote loopback functionality.
timeout
Sets a master loopback timeout setting.
seconds
Integer from 1 to 10 that is the number of seconds of the timeout period.
Command Default
Remote loopback is not supported.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
This command enables the support of OAM remote-loopback on an interface. Only after this functionality is enabled can the local OAM client initiate the OAM remote loopback operation. Changing this setting causes the local OAM client to exchange configuration information with its remote peer.
The no form of the command is rejected if the interface is in the loopback mode.
Note
Examples
The following example shows how to enable remote loopback support on interface GigabitEthernet 2/1:
Router(config)# interface gigabitethernet 2/1Router(config-if)# ethernet oam remote-loopback supportedRelated Commands
ethernet uni
To set user-network interface (UNI) bundling attributes, use the ethernet uni command in interface configuration mode. To return to the default bundling configuration, use the no form of this command.
ethernet uni [bundle [all-to-one] | id uni-id | multiplex]
no ethernet uni
Syntax Description
Command Default
If bundling or multiplexing attributes are not configured, the default is bundling with multiplexing. The UNI then has one or more EVCs with one or more CE VLANs mapped to each EVC.
Command Modes
Interface configuration (config-if)
Command History
12.2(25)SEG
This command was introduced.
12.2(33)SRB
This command was implemented on the Cisco 7600 series routers.
Usage Guidelines
UNI options determine the functionality that the interface has regarding bundling VLANs and multiplexing EVCs.
If you want only the bundling or only the multiplexing service, you must configure the service appropriately. Bundling supports only one EVC at the UNI with one or multiple customer edge (CE)-VLAN IDs mapped to the EVC.
When multiplexing is configured, the UNI can have one or more EVCs with a single CE-VLAN ID mapped to each EVC.
When you configure a UNI ID on a port, that ID is used as the default name for all maintenance end points (MEPs) configured on the port.
You must enter the ethernet uni command with the id keyword and id argument on all ports that are directly connected to CE devices. When the specified ID is not unique on a device, an error message is displayed.
When you configure, change, or remove a UNI service type, the EVC and CE-VLAN ID configurations are checked to ensure that the configurations and the UNI service types match. If the configurations do not match, the command is rejected.
Examples
The following example shows how to configure bundling without multiplexing:
Router(config)# interface ethernet 2/1Router(config-if)# ethernet uni bundleThis example shows how to identify a UNI as test2:
Router(config)# interface ethernet 2/1Router(config-if)# ethernet uni id test2Related Commands
show ethernet service interface
Displays information about Ethernet service instances on an interface, including service type.
id (CFM)
To configure a maintenance domain identifier (MDID), use the id command in Ethernet connectivity fault management (CFM) configuration mode. To remove a MDID, use the no form of this command.
id {mac-address domain-number | dns dns-name | null}
no id
Syntax Description
Command Default
A MDID is not configured.
Command Modes
Ethernet CFM configuration (config-ecfm)
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 the MDID is not specified, the domain name in string format is used as the default. If a DNS name exceeds 43 characters, the MDID is only the first 43 characters of that DNS name.
If the MDID is explicitly null, the maintenance association ID (MAID) is constructed from the short maintenance association name. The short maintenance association name needs to be unique globally if the MDID is null.
Examples
The following example shows how to configure a MDID with a MAC address and a domain number:
Router(config)# ethernet cfm domain customerA level 5Router(config-ecfm)# id aaaa.bbbb.cccc 1017lacp direct-loadswap
To enable Link Aggregation Control Protocol (LACP) direct load swapping on a port channel, use the lacp direct-loadswap command in interface port-channel configuration mode. To return to the default setting, use the no form of this command.
lacp direct-loadswap
no lacp direct-loadswap
Syntax Description
This command has no arguments or keywords.
Command Default
Direct loadswapping is disabled.
Command Modes
Interface port-channel configuration (config-if)
Command History
Usage Guidelines
Use this command to enable the LACP Single Fault Direct Load Balance Swapping feature on a port channel. This command can be used for only a single bundled port failure. If a second failure occurs before the first failure recovers, the loadshare bits for member links are recomputed.
Examples
This example shows how to enable LACP single fault direct load swapping on port channel 1:
Router(config)# interface port-channel 1
Router(config-if)# lacp direct-loadswapRouter(config-if)#Related Commands
lacp fast-switchover
To enable Link Aggregation Control Protocol (LACP) 1:1 link redundancy, use the lacp fast-switchover command in interface configuration mode. To disable LACP 1:1 link redundancy, use the no form of this command.
lacp fast-switchover
no lacp fast-switchover
Syntax Description
This command has no arguments or keywords.
Command Default
LACP 1:1 link redundancy is disabled by default.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Prior to entering the lacp fast-switchover command, you must ensure the following:
•
•
When you enable LACP 1:1 link redundancy, based on the system priority and port priority, the port with the higher system priority chooses the link as the active link and the other link as the standby link. When the active link fails, the standby link is selected as the new active link without taking down the port channel. When the original active link recovers, it reverts to its active link status. During this change-over, the port channel is also up.
Note
You can enter this command on any port channels with different EtherChannel protocol types of LACP, Port Aggregation Protocol (PAgP), or Fast EtherChannel (FEC).
Examples
This example shows how to enable LACP 1:1 link redundancy:
Router(config-if)# lacp fast-switchoverThis example shows how to disable LACP 1:1 link redundancy:
Router(config-if)# no lacp fast-switchoverRelated Commands
lacp max-bundle
Assigns and configures an EtherChannel interface to an EtherChannel group.
show etherchannel
Displays the EtherChannel information for a channel.
lacp max-bundle
To define the maximum number of active bundled Link Aggregation Control Protocol (LACP) ports allowed in a port channel, use the lacp max-bundle command in interface configuration mode. To return to the default settings, use the no form of this command.
lacp max-bundle max-bundles
no lacp max-bundle
Syntax Description
Command Default
A maximum number of active bundled ports is not configured.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
The value specified in the max-bundles argument determines the number of active links that are bundled in the port channel. The remaining links are in hot-standby mode.
On the Cisco 10000 series router, this command requires a Performance Routing Engine 2 (PRE2) or PRE3.
Examples
This example shows how to set 3 ports to bundle in port channel 2:
Router(config)# interface port-channel 2Router(config-if)# lacp max-bundle 3Router(config-if)#Related Commands
lacp min-bundle
To set the minimum number of active links in a Link Aggregation Control Protocol (LACP) bundle, use the lacp min-bundle command in interface configuration mode. To return to the default settings, use the no form of this command.
lacp min-bundle min-bundle
no lacp min-bundle
Syntax Description
min-bundle
Minimum number of bundled ports allowed in the port channel. Valid values are from 1 to 8. The default is 1.
Command Default
The port-channel operational state will be "Down" only when there are no active links in the channel. If there are one or more active links, the port-channel state will be "Up."
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Use the lacp min-bundle command to configure the minimum number of active links allowed in an LACP bundle. When the number of active links falls below this minimum threshold, the port channel shuts down.
Note
Cisco 10000 Series Router
This command requires a Performance Routing Engine 2 (PRE2) or PRE3.
Examples
This example shows how to set the minimum number of active links to 5 ports:
Router(config-if)# lacp min-bundle 5Router(config-if)#Related Commands
lacp port-priority
To set the priority for a physical interface, use the lacp port-priority command in interface configuration mode. To return to the default setting, use the no form of this command.
lacp port-priority priority
no lacp port-priority
Syntax Description
priority
Integer from 1 to 65535 that indicates the priority for the physical interface. The default is 32768.
•
Command Default
The default port priority is set.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
You may assign a port priority to each port on a device running Link Aggregation Control Protocol (LACP). You can specify the port priority by using the lacp port-priority command at the command-line interface (CLI) or use the default port priority (32768) that is carried as part of the LACP protocol data unit (PDU) exchanged with the partner. Port priority is used to decide which ports should be put in standby mode when a hardware limitation or the lacp max-bundle command configuration prevents all compatible ports from aggregating. Priority is supported only on port channels with LACP-enabled physical interfaces.
Note
Port priority together with port number form a port identifier.
To verify the configured port priority, issue the show lacp internal command.
Examples
This example shows how to set a priority of 23700 for an interface:
Router(config-if)# lacp port-priority 23700Router(config-if)#Related Commands
lacp rate
To set the rate at which Link Aggregation Control Protocol (LACP) control packets are ingressed to an LACP-supported interface, use the lacp rate command in interface configuration mode. To return to the default settings, use the no form of this command.
lacp rate {normal | fast}
no lacp rate
Syntax Description
Defaults
The default ingressed rate for control packets is 30 seconds after the link is bundled.
Command Modes
Interface configuration (config-if)
Command History
12.2(18)SXF2
This command was introduced on the Catalyst 6500 series switch.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
Usage Guidelines
Use this command to modify the duration of a LACP timeout. The LACP timeout value is set on Cisco switches to a value of 90 seconds. Using the lacp rate command, you can select the LACP timeout value for a switch to be either 30 seconds or 1 second.
This command is supported only on LACP-enabled interfaces.
Examples
This example shows how to specify the fast (1-second) ingress rate on interface Ethernet 0/1:
Router(config)# interface ethernet 0/1Router(config-if)# lacp rate fastRelated Commands
lacp system-priority
To set the priority for a system, use the lacp system-priority command in global configuration mode. To return to the default setting, use the no form of this command.
lacp system-priority priority
no lacp system-priority
Syntax Description
priority
Integer from 1 to 65535 that indicates the priority for the system. The default is 32768.
•
Command Default
The default system priority is set.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
You can assign a system priority to each device running Link Aggregation Control Protocol (LACP). You can specify the system priority by using the lacp system-priority command at the command-line interface (CLI) or use the default system priority (32768) that is carried as part of the LACP protocol data unit (PDU) exchanged with the partner. System priority is used with the MAC address of the device to form the system ID and also is used during negotiation with other systems. Priority is supported only on port channels with LACP-enabled physical interfaces.
Note
To verify the configured system priority, issue the show lacp internal command.
Examples
The following example shows how to set a system priority of 25500 for a device:
Router(config)# lacp system-priority 25500Related Commands
level (CFM-AIS-link)
To configure a maintenance level to receive Alarm Indication Signal (AIS) frames transmitted by a link-status change (server maintenance endpoint [SMEP]), use the level command in Ethernet connectivity fault management (CFM) SMEP AIS configuration mode (config-ais-link-cfm). To remove the maintenance level, use the no form of this command.
level level-id
no level
Syntax Description
Command Default
A maintenance level is not configured.
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
This command allows you to transmit AIS messages to a higher level maintenance association without configuring a maintenance intermediate point (MIP) for the service.
Examples
The following example shows how to configure maintenance level 5 as the level to receive AIS frames transmitted by a link-status change:
Router(config)# ethernet cfm ais link-status globalRouter(config-ais-link-cfm)# level 5lldp
To enable Link Layer Discovery Protocol (LLDP), use the lldp command in global configuration mode. To revert to the default settings, use the no form of this command.
lldp {holdtime seconds | reinit delay | run | timer rate | tlv-select tlv}
no lldp {holdtime | reinit | run | timer | tlv-select tlv}
Syntax Description
Command Default
LLDP will be globally disabled by default. No LLDP advertisements will be sent.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
To enable LLDP, use this command with the run keyword.
LLDP packets are sent with a hold-time value. The receiving device ages the LLDP information about the neighbor after the hold time has elapsed.
Examples
The following example shows how to configure a hold time of 100 seconds:
Router(config)# lldp holdtime 100The following example shows how to set the timer to send LLDP updates every 75 seconds:
Router(config)# lldp timer 75Related Commands
lldp (interface)
To enable Link Layer Discovery Protocol (LLDP) on an interface, use the lldp command in interface configuration mode. To disable LLDP on an interface, use the no form of this command.
lldp {med-tlv-select tlv | receive | transmit}
no lldp {med-tlv-select tlv | receive | transmit}
Syntax Description
Command Default
LLDP is enabled on supported interfaces.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
This command is supported on 802.1 media types.
Examples
The following example shows how to disable LLDP transmission on interface Ethernet 0/1:
Router# configure terminalRouter(config)# interface ethernet 0/1Router(config-if)# no lldp transmitThe following example shows how to enable LLDP transmission on interface Ethernet 0/1:
Router# configure terminalRouter(config)# interface ethernet 0/1Router(config-if)# lldp transmitRelated Commands
mac access-group in
To use a MAC access control list (ACL) to control inbound traffic on an Ethernet service instance, use the mac access-group in command in service instance configuration mode. To remove a MAC ACL, use the no form of this command.
mac access-group access-list-name in
no mac access-group access-list-name in
Syntax Description
access-list-name
Name of a MAC ACL to apply to an interface or subinterface (as specified by the mac access-list extended command).
Defaults
A MAC ACL is not applied to the Ethernet service instance.
Command Modes
Service instance configuration (config-if-srv)
Command History
Usage Guidelines
The mac access-group in command is used to apply MAC ACLs on Ethernet service instances. After a networking device receives a packet, the Cisco IOS software checks the source MAC address of the packet against the ACL. If the MAC ACL permits the address, the software continues to process the packet.
If a MAC ACL does not exist on the Ethernet service instance, all packets are passed.
Examples
The following example shows how to apply a MAC ACL called mac_layer on inbound traffic to service instance 100:
Router> enableRouter# configure terminalRouter(config)# mac access-list extended mac_layerRouter(config-ext-macl)# permit 00aa.bbcc.ddee 0.0.0 anyRouter(config-ext-macl)# exitRouter(config)# interface gigabitethernet 2/0/0Router(config-if)# service instance 100 ethernetRouter(config-if-srv)# encapsulation dot1q 100Router(config-if-srv)# mac access-group mac_layer inRelated Commands
mac access-list extended
Defines a MAC ACL.
show ethernet service instance
Displays information about Ethernet service instances.
mac limit maximum addresses
To configure the maximum number of MAC addresses allowed on a bridge domain, use the mac limit maximum addresses command in bridge domain configuration mode. To return to the default state, use the no form of this command.
mac limit maximum addresses maximum-addresses
no mac limit maximum addresses maximum-addresses
Syntax Description
maximum-addresses
Integer in the range 1 to Platform_Upper_Bound that specifies the maximum number of MAC addresses allowed. Platform_Upper_Bound is a platform-specific upper limit.
Command Default
The maximum number of MAC addresses allowed by the platform.
Command Modes
Bridge domain configuration (config-bdomain)
Command History
Examples
The following example shows how to set the maximum number of MAC addresses on a specific bridge domain to 1000:
Router> enableRouter# configure terminalRouter(config)# bridge-domain 100Router(config-bdomain)# mac limit maximum addresses 1000Related Commands
mac security maximum addresses
Specifies the maximum number of MAC addresses allowed on an Ethernet service instance.
mac security
To configure MAC security and the various MAC security elements on an Ethernet service instance, use the mac security command in service instance configuration mode. To return to the default MAC security setup on the service instance, use the no form of this command.
mac security [address {permit | deny} mac-address | aging {static | sticky | time aging-time [inactivity]} | maximum addresses maximum-addresses | sticky [address mac-address] | violation {protect | restrict}]
no mac security [address {permit | deny} mac-address | aging {static | sticky | time aging-time [inactivity]} | maximum addresses maximum-addresses | sticky [address mac-address] | violation {protect | restrict}]
Syntax Description
Command Default
MAC security is disabled.
Command Modes
Service instance configuration (config-if-srv)
Command History
Usage Guidelines
The MAC security operation is enabled on an Ethernet service instance by the mac security command.
Configuring or removing MAC security elements is permitted irrespective of whether MAC security is enabled. Configured elements become operational only when the mac security command is issued and MAC security is enabled.
Examples
The following example shows how to enable MAC security on Ethernet service instance 100:
Router> enableRouter# configure terminalRouter(config)# interface gigabitethernet 2/0/1Router(config-if)# service instance 100 ethernetRouter(config-if-srv)# encapsulation dot1q 100Router(config-if-srv)# bridge-domain 200Router(config-if-srv)# mac securityThe following example shows how to configure a MAC address permit with three addresses:
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 security maximum addresses 3Router(config-if-srv)# mac security address permit a2aa.aaaa.aaaaRouter(config-if-srv)# mac security address permit a2aa.aaaa.aaabRouter(config-if-srv)# mac security address permit a2aa.aaaa.aaacRouter(config-if-srv)# mac securityThe following example shows how to enable a MAC address violation protect response on 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 200Router(config-if-srv)# mac security address permit a2aa.aaaa.aaaaRouter(config-if-srv)# mac security address permit a2aa.aaaa.aaabRouter(config-if-srv)# mac security address permit a2aa.aaaa.aaacRouter(config-if-srv)# mac security violation protectRouter(config-if-srv)# mac securityThe following example shows how to enable MAC address security aging on a service instance, with the aging time set to 100 minutes:
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 security aging time 100Router(config-if-srv)# mac securityThe following example shows how to configure a MAC address limit of 1000 on a service instance.
Router> enableRouter# configure terminalRouter(config)# interface gigabitethernet 2/0/0Router(config-if)# service instance 150 ethernetRouter(config-if-srv)# encapsulation dot1Q 150Router(config-if-srv)# bridge-domain 100Router(config-if-srv)# mac security maximum addresses 1000Router(config-if-srv)# mac securityThe following example shows how to configure sticky MAC addressing on an Ethernet service instance:
Router> enableRouter# configure terminalRouter(config)# interface gigabitethernet 2/0/1Router(config-if)# service instance 100 ethernetRouter(config-if-srv)# encapsulation dot1Q 100Router(config-if-srv)# bridge-domain 150Router(config-if-srv)# mac security stickyRouter(config-if-srv)# mac securityRelated Commands
mac static address
To configure a MAC static address, use the mac static address command either in interface service instance configuration mode or in virtual forwarding instance (VFI) neighbor configuration mode. To remove a MAC static address, use the no form of this command.
mac static address mac-addr [auto-learn] [disable-snooping]
no mac static address mac-addr
Syntax Description
Command Default
MAC static addresses are not configured.
Command Modes
Interface service instance configuration (config-if-srv)
VFI neighbor configuration (config-vfi-neighbor)Command History
Usage Guidelines
Static MAC addresses are related to a Layer 2 bridge domain table; therefore, only bridged services are supported.
Static MAC address configuration is supported only on Ethernet virtual circuit (EVC) bridge domain interfaces and VFI pseudowires.
A unicast static MAC address and MAC security cannot be simultaneously configured on the same Ethernet flow point (EFP). A static MAC multicast address and MAC security can be simultaneously supported on the same EFP.
The number of MAC addresses (unicast and multicast) is limited to 1024 per bridge domain, pseudowire, VFI, or system.
Examples
The following example shows how to configure a MAC static address in service instance configuration mode:
Router(config)# interface ethernet 1/0Router(config-if)# service instance 123 ethernetRouter(config-if-srv)# encapsulation dot1q 100Router(config-if-srv)# bridge-domain 100Router(config-if-srv)# mac static address 3333.1111.1111The following example shows how to configure a MAC static address in VFI neighbor configuration mode:
Router(config)# l2 vfi foo-core manualRouter(config-vfi)# vpn id 100Router(config-vfi)# bridge-domain 10Router(config-vfi)# neighbor 11.0.0.1 pw-class hubclassRouter(config-vfi-neighbor)# mac static address 1111.2222.3333mac tunnel address destination default
To specify a B-component destination address (B-DA) for a group of service instance IDs (I-SIDs), use the mac tunnel address destination default command in MAC-in-MAC tunnel configuration mode. To remove a MAC tunnel address, use the no form of this command.
mac tunnel address destination default mac-addr
no mac tunnel address destination default mac-addr
Syntax Description
Command Default
B-DAs are not configured.
Command Modes
MAC-in-MAC tunnel configuration (config-tunnel-minm)
Command History
Usage Guidelines
The MAC address specified can be either a unicast or a multicast address.
Examples
The following example shows how to specify a B-DA using MAC address 3333.1111.1111:
Router(config)# ethernet mac-tunnel virtual 1Router(config-tunnel-mimn)# mac tunnel address destination default 3333.1111.1111mac tunnel address destination map
To map a service provider backbone bridge MAC address to a customer MAC address, use the mac tunnel address destination map command in MAC tunnel service configuration mode. To remove a bridge mapping, use the no form of this command.
mac tunnel address destination map c-mac-addr b-mac-addr
no mac tunnel address destination map c-mac-addr b-mac-addr
Syntax Description
c-mac-addr
48-bit MAC address of the customer bridge.
b-mac-addr
48-bit MAC address of the service provider bridge.
Command Default
Service provider and customer bridges are not mapped.
Command Modes
MAC tunnel service configuration (config-tunnel-srv)
Command History
Usage Guidelines
The MAC address specified can be either a unicast or a multicast address. If a packet's destination is a backbone edge bridge, the MAC address must be a unicast address.
Examples
The following example shows how to map a customer bridge to a service provider backbone bridge:
Router(config)# ethernet mac-tunnel virtual 1Router(config-tunnel-mimn)# service instance 1 ethernetRouter(config-tunnel-srv)# mac tunnel address destination map 3333.1111.1111 5555.2222.2222maximum meps
To specify the number of maintenance endpoints (MEPs) across the network in a maintenance association, use the maximum meps command in Ethernet CFM service configuration mode. To restore the default value, use the no form of this command.
maximum meps max-num
no maximum meps
Syntax Description
Command Default
A maximum number of MEPs is not configured.
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
When the configured maximum is reached, continuity check messages (CCMs) from other remote MEPs are ignored and a warning message is displayed.
Output of the show running all command displays "maximum meps 100" when the default value is configured.
Examples
The following example shows how to configure a maximum of 50 MEPs:
Router(config)# ethernet cfm domain operatorA level 5Router(config-ecfm)# service vlan-id 5 portRouter(config-ecfm-srv)# maximum meps 50Related Commands
mep archive-hold-time
To set the amount of time, in minutes, that data from a missing maintenance end point (MEP) is kept in the continuity check database or that entries are held in the error database before they are purged, use the mep archive-hold-time command in Ethernet connectivity fault management (CFM) configuration mode. To restore the default number of minutes, use the no form of this command.
mep archive-hold-time minutes
no mep archive-hold-time minutes
Syntax Description
Syntax DescriptionCommand Syntax]
minutes
Integer from 1 to 65535 that specifies the number of minutes that data from a missing MEP is kept before it is purged. The default is 100.
Command Default
The command is enabled, and the archive hold time is set to 100 minutes.
Command Modes
Cisco pre-Standard CFM Draft 1 (CFM D1)
Ethernet CFM configuration (config-ether-cfm)
CFM IEEE 802.1ag Standard (CFM IEEE)
Ethernet CFM configuration (config-ecfm)
Command History
Usage Guidelines
When you reset the archive hold time, the new hold time applies only to entries in the database that occur after the reset. Entries made before the hold time was reset are not affected by the change.
Different archive hold times can be set for MEPs in different domains.
Note
In CFM IEEE, output of the show running all command displays "mep archive hold-time 100" when the default value is configured.
Examples
The following example shows how to set a timeout period of 1000 minutes in CFM D1:
Router(config-ether-cfm)# mep archive-hold-time 1000The following example shows how to set a timeout period of 1000 minutes in CFM IEEE:
Router(config-ecfm)# mep archive-hold-time 1000Related Commands
mep crosscheck mpid evc
To statically define a remote maintenance endpoint (MEP) within a maintenance domain, use the mep crosscheck mpid evc command in Ethernet CFM configuration mode. To delete a remote MEP, use the no form of this command.
mep crosscheck mpid id evc evc-name [mac mac-address]
no mep crosscheck mpid id evc evc-name [mac mac-address]
Syntax Description
Command Default
Remote MEPs are not configured.
Command Modes
Ethernet CFM configuration (config-ether-cfm)
Command History
Usage Guidelines
The mep crosscheck mpid evc command is available on the Cisco 7600 Series Route Switch Processor 720 (RSP 720) and the Cisco 7600 Series Supervisor Engine 720.
Use the mep crosscheck mpid evc command to statically configure remote MEPs that are part of a domain. These remote MEPs can be used in the cross-check operation. The cross-check operation works only when local MEPs are configured that correspond to the statically configured remote MEPs.
Examples
The following example shows how to define a MEP within a maintenance domain with an ID of 20, in EVC evc5, and with MAC address a5a1.a5a1.a5a1:
Router(config-ether-cfm)# mep crosscheck mpid 20 evc evc5 mac a5a1.a5a1.a5a1Related Commands
mep crosscheck mpid vlan
To statically define a remote maintenance endpoint (MEP) within a maintenance domain, use the mep crosscheck mpid vlan command in Ethernet connectivity fault management (CFM) configuration mode. To delete a remote MEP, use the no form of this command.
mep crosscheck mpid id {evc evc-name | vlan vlan-id} [mac mac-address]
no mep crosscheck mpid id {evc evc-name | vlan vlan-id} [mac mac-address]
Syntax Description
Command Default
No remote MEPs are configured.
Command Modes
Ethernet CFM configuration (config-ether-cfm)
Command History
Usage Guidelines
Use the mep crosscheck mpid vlan command to statically configure remote MEPs that are part of a domain. These remote MEPs can be used in the cross-check operation. The mep crosscheck mpid vlan command can be used only if the device has MEPs at the same level and in the same VLAN.
Examples
The following example shows how to define a MEP within a maintenance domain with an ID of 20, in VLAN 5, and with MAC address a5a1.a5a1.a5a1:
Router(config-ether-cfm)# mep crosscheck mpid 20 vlan 5 mac a5a1.a5a1.a5a1The following example shows how to define a MEP within a maintenance domain with an ID of 20, in EVC evc5, and with MAC address a5a1.a5a1.a5a1:
Router(config-ether-cfm)# mep crosscheck mpid 20 evc evc5 mac a5a1.a5a1.a5a1
Related Commands
mep mpid
To statically define the maintenance endpoints (MEPs) within a maintenance association, use the mep mpid command in Ethernet connectivity fault management (CFM) service configuration mode. To remove MEP definitions, use the no form of this command.
mep mpid mpid
no mep mpid
Syntax Description
Command Default
No MEPs are statically defined.
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
Use this command to manually configure a list of MEPs in a maintenance association. The device logs a warning when a discovered MPID is not on the list of configured MPIDs.
Examples
The following example shows how to configure a MEP with an ID of 25:
Router(config)# ethernet cfm domain operatorA level 5Router(config-ecfm)# service vlan-id 5 portRouter(config-ecfm-srv)# mep mpid 25mip auto-create
To enable the automatic creation of a maintenance intermediate point (MIP) at a maintenance domain level, use the mip auto-create command in Ethernet connectivity fault management (CFM) configuration mode. To disable the automatic creation of a MIP, use the no form of this command.
mip auto-create [lower-mep-only]
no mip auto-create [lower-mep-only]
Syntax Description
lower-mep-only
(Optional) Creates a MIP only if there is a MEP for the service in another domain at the next lower active maintenance domain level.
Command Default
MIPs will not be created.
Command Modes
Ethernet CFM configuration (config-ecfm)
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 configures the MIP creation policy for members of a maintenance domain to apply for automatically creating a MIP at the domain maintenance level.
If you manually configure a MIP for the maintenance association, it will override the mip auto-create command for the MIP for that maintenance association. The mip auto-create command also has lower precedence than the MIP creation policy at the maintenance association.
Examples
The following example shows how to enable the automatic creation of a MIP in the customerA domain at maintenance level 5:
Router(config)# ethernet cfm domain customerA level 5Router(config-ecfm)# mip auto-createmip auto-create (cfm-srv)
To configure the policy for a maintenance association to dynamically create maintenance intermediate points (MIPs) at the enclosing maintenance domain level, use the mip auto-create command in Ethernet connectivity fault management (CFM) service configuration mode. To disable the dynamic creation of a MIP, use the no form of this command.
mip auto-create [lower-mep-only | none]
no mip auto-create [lower-mep-only | none]
Syntax Description
Command Default
The default behavior is to defer to the MIP configuration policy of the enclosing maintenance domain.
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
If the lower-mep-only or none options are not configured, a MIP is created at the maintenance association.
This command has lower precedence than the manual configuration of a MIP for a maintenance association. For example, if you manually configure a MIP for a maintenance association, that manual configuration overrides the dynamic configuration from this mip auto-create command.
Examples
The following example shows how to configure the policy for a maintenance association to dynamically create MIPs at the enclosing maintenance domain level:
Router(config)# ethernet cfm domain Domain_L5 level 5Router(config-ecfm)# service cust_500_l5 vlan 9Router(config-ecfm-srv)# mip auto-createoam protocol
To specify an operations, maintenance, and administration (OAM) protocol for an Ethernet virtual connection (EVC), use the oam protocol command in EVC configuration mode. To remove an OAM protocol configuration for an EVC, use the no form of this command.
oam protocol {cfm svlan svlan-id domain domain-name | ldp}
no oam protocol
Syntax Description
Command Default
An OAM protocol is not specified.
Command Modes
EVC configuration (config-evc)
Command History
Usage Guidelines
Use this command to specify the OAM protocol to use for communicating link status in an Ethernet over Multiprotocol Label Switching (EoMPLS) network.
Examples
The following example shows how to specify CFM as the OAM protocol:
Router(config)# ethernet evc evc10Router(config-evc)# oam protocol cfm svlan 10 domain cstmrperiod (CFM-AIS-link)
To configure a specific Alarm Indication Signal (AIS) transmission interval on a server maintenance endpoint (SMEP), use the period command in Ethernet connectivity fault management (CFM) SMEP AIS configuration mode (config-ais-link-cfm). To remove the interval configuration, use the no form of this command.
period seconds
no period
Syntax Description
seconds
Integers 1 or 60 that specify the time interval, in seconds, between AIS transmissions. The default is 60.
Command Default
AIS frames are transmitted every 60 seconds.
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, "period 60" is displayed when the show running all command is issued.
Examples
The following example shows how to configure an AIS transmission interval of 1 second:
Router(config)# ethernet cfm ais link-status globalRouter(config-ais-link-cfm)# period 1Related Commands
ping ethernet
To send Ethernet connectivity fault management (CFM) loopback messages to a destination maintenance endpoint (MEP), use the ping ethernet command in privileged EXEC mode.
ping ethernet {mac-address | mpid mpid | multicast} {domain domain-name {port | vlan vlan-id}} [cos cos-value | source source-mpid [cos cos-value]] [de]
Syntax Description
Command Default
A CFM ping operation to the specified MEP is performed.
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
Use this command to test connectivity between MEPs.
If the continuity check database does not have entries for the specified MPID, an error message is displayed notifying you to use the ping ethernet mac-address command instead.
If a domain name has more than 43 characters, a warning message is displayed notifying you that the maintenance domain ID (MDID) will be truncated to 43 characters in continuity check messages (CCMs) if "id <fmt> <MDID>" is not configured.
This command can be issued by specifying keywords and arguments as one command or as an "extended" command in which you specify options line by line.
Examples
The following examples show how to send an Ethernet CFM loopback message to a destination MEP using the "extended ping" format:
Router# pingProtocol [ip]: ethernetMulticast [n] :Mac Address : aabb.cc03.bb99Maintenance Domain : Domain_L5VLAN [9]:Source MPID [220]:Repeat Count [5]:Datagram Size [100]:Timeout in seconds [5]:Interval in seconds [0]:Extended commands [n]:Type escape sequence to abort.Sending 5 Ethernet CFM loopback messages to aabb.cc03.bb99, timeout is 5 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 msRouter# pingProtocol [ip]: ethernetMulticast [n] : yMaintenance Domain : Domain_L5VLAN [9]:Source MPID [220]:Datagram Size [100]:Timeout in seconds [5]:Interval in seconds [0]:Extended commands [n]:Type escape sequence to abort.Sending 5 Ethernet CFM loopback messages to 0180.c200.0035, timeout is 5 seconds:Reply to Multicast request from aabb.cc03.bb99, 0 msTotal Remote MEPs replied: 1ping ethernet evc
To send Ethernet connectivity fault management (CFM) loopback messages to a maintenance endpoint (MEP) or maintenance intermediate point (MIP) destination, use the ping ethernet evc command in privileged EXEC mode.
ping ethernet {mac-address | mpid} {domain domain-name | level level-id}
evc evc-name [source mpid]Syntax Description
Command Default
A basic CFM ping operation to the specified MAC address (MEP or MIP) is performed.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
A local MEP must be configured for the same level and EVC before you can use this command.
The optional source keyword is available only when you enter a domain name. The source keyword is useful when there are multiple local MEPs in the same domain, level, and EVC as the ping target. For outward facing MEPs, choosing the source MPID implicitly selects the interface from which the ping will be sent.
Examples
The following example shows how to send an Ethernet CFM loopback message to MAC address 1010.pcef.1010 at maintenance level 2 on evc5:
Router# ping ethernet 1010.pcef.1010 level 2 evc evc5Related Commands
ping ethernet mpid vlan
Note
To send Ethernet connectivity fault management (CFM) loopback messages to a maintenance end point (MEP) destination, use the ping ethernet mpid vlan command in privileged EXEC mode.
ping ethernet mpid mpid {domain domain-name | level level-id} vlan vlan-id
Syntax Description
Command Default
A basic CFM ping operation to the specified maintenance end point ID (MPID) is performed.
Command Modes
Privileged EXEC (#)
Command History
12.2(33)SRA
This command was introduced.
12.4(11)T
This command was replaced by the ping ethernet vlan command.
Usage Guidelines
Use this command to test connectivity between MEPs.
If the continuity check database does not have entries for the specified MPID, an error message displays indicating that the command cannot be used.
Examples
The following example shows how to send an Ethernet CFM loopback message to MPID 3075, maintenance domain operatorv, maintenance level 3, VLAN ID 4325:
Router# ping ethernet mpid 3075 domain operatorv level 3 vlan 4325Type escape sequence to abort. Sending 5 Ethernet CFM loopback messages, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 60/62/72 msRelated Commands
ping ethernet vlan
To send Ethernet connectivity fault management (CFM) loopback messages to a maintenance endpoint (MEP) or maintenance intermediate point (MIP) destination, use the ping ethernet vlan command in privileged EXEC command mode.
ping ethernet {mac-address | mpid} {domain domain-name | level level-id} vlan vlan-id [source mpid]
Syntax Description
Command Default
A basic CFM ping operation to the specified MAC address (MEP or MIP) is performed.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
A local MEP must be configured for the same level and VLAN before you can use this command.
The optional source keyword is available only when you enter a domain name. The source keyword is useful when there are multiple local MEPs in the same domain, level, and VLAN as the ping target. For outward facing MEPs, choosing the source MPID implicitly selects the interface from which the ping will be sent.
Examples
The following example shows how to send an Ethernet CFM loopback message to MAC address 4123.pcef.9879 at maintenance level 3, VLAN ID 4325:
Router# ping ethernet 4123.pcef.9879 level 3 vlan 4325Related Commands
ping
Sends an echo request packet to an address, and then awaits a reply to determine whether a device can be reached or is functioning.
sender-id
To indicate the contents of the Sender ID TLV field transmitted in Ethernet connectivity fault management (CFM) messages for members of a maintenance domain, use the sender-id command in Ethernet CFM configuration mode. To send no sender ID information, use the no form of this command.
sender-id {chassis}
no sender-id {chassis}
Syntax Description
Command Default
The Sender ID TLV is not included in messages.
Command Modes
Ethernet CFM configuration (config-ecfm)
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 has lower precedence than the sender-id command issued at the maintenance association. To override the configuration at the maintenance association, configure the service ID as "none."
Examples
The following example shows how to include only the chassis ID information in the Sender ID TLV:
Router(config)# ethernet cfm domain customerA level 5Router(config-ecfm)# sender-id chassissender-id (CFM-srv)
To indicate the contents of the Sender ID TLV field transmitted in Ethernet connectivity fault management (CFM) messages for the maintenance association, use the sender-id command in Ethernet CFM service configuration mode. To send no sender ID information, use the no form of this command.
sender-id {chassis | none}
no sender-id {chassis | none}
Syntax Description
Command Default
The Sender ID TLV is not included in messages.
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
This command has higher precedence than the sender-id command issued for the maintenance domain.
The default is that the enclosing maintenance domain determines the Sender ID.
Examples
The following example shows how to include only the chassis ID information in the Sender ID TLV:
Router(config)# ethernet cfm domain customerA level 5Router(config-ecfm)# service vlan-id 17 portRouter(config-ecfm-srv)# sender-id chassisservice (CFM-srv)
To configure a maintenance association within a maintenance domain and place the command-line interface (CLI) into Ethernet connectivity fault management (CFM) service configuration mode (config-ecfm-srv), use the service command in Ethernet CFM configuration mode. To remove the configuration, use the no form of this command.
service {ma-name | ma-num | vlan-id vlan-id | vpn-id vpn-id} [port | vlan vlan-id [direction down]]
no service {ma-name | ma-num | vlan-id vlan-id | vpn-id vpn-id} [port | vlan vlan-id [direction down]]
Syntax Description
Command Default
No maintenance associations are configured.
Command Modes
Ethernet CFM configuration (config-ecfm)
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 maintenance association ID (MAID) is a combination of a maintenance domain ID and the short maintenance association name, and the length of the MAID TLV should not exceed 48 characters.
If you configure the same short maintenance association name for two VLANs in the same domain, an error message is displayed and the command is rejected.
If you specify the service direction as down (outward to the LAN), you can create multiple outward services at the same level containing an overlapping set of VLANs. The set of VLANs in an outward service can also overlap with inward services. A set of VLANs between inward services at the same level must be unique.
Examples
The following example shows how to configure a maintenance association with the ID 10, VLAN 17, and service direction toward the LAN within the customerA maintenance domain:
Router(config)# ethernet cfm domain customerA level 5Router(config-ecfm)# service 10 vlan-id 17 direction downRouter(config-ecfm-srv)#service evc
To set a universally unique ID for a customer service instance (CSI) within a maintenance domain, use the service evc command in Ethernet CFM configuration mode. To remove a universally unique ID for a service within a maintenance domain, use the no form of this command.
service csi-id evc evc-name
no service csi-id evc evc-name
Syntax Description
csi-id
String of a maximum of 100 characters that identifies the CSI.
evc-name
String that identifies the Ethernet virtual circuit (EVC).
Command Default
No universally unique ID is set for the CSI.
Command Modes
Ethernet CFM configuration (config-ether-cfm)
Command History
Usage Guidelines
A fully qualified service ID consists of a service ID plus a domain name. Service IDs identify customers within a domain. Ethernet connectivity fault management (CFM) requires that service IDs are unique in a network.
You must configure a service EVC before you can configure a maintenance endpoint (MEP) for a domain.
The following restrictions apply when you issue the service evc command:
•
•
•
For two domains at the same maintenance level, the same service ID can be used for two different EVCs. If you try to configure the same service ID for two EVCs in the same domain, the command is rejected and an error message is displayed.
Specifying a domain as outward allows you to create multiple outward domains at the same level with a set of services that overlap. These EVCs also can overlap with inward domains. Note that a set of EVCs overlapping inward domains at only the same level must be unique.
You can use the same service ID in the same EVC or different EVCs if the service IDs are in different levels.
Before you remove a service ID, all MEPs corresponding to the service must be removed.
On Cisco 7600 series routers, a VLAN service and an EVC service may have the same service ID if the bridge domain is associated with an EVC and the bridge-domain ID equals the VLAN service ID. This situation occurs because the bridge domain and the VLAN of the same number form a single broadcast domain representing the same CFM service.
Examples
The following example shows how to configure an Ethernet CFM service with EVC evc100:
ethernet cfm domain PROVIDER level 4service provider_100 evc evc100The following example shows how to configure Ethernet CFM service on a Cisco Route Switch Processor 720. You must configure the VLAN and EVC services with the same name because VLAN 100 and bridge domain 100, which is associated with EVC 100, represent a single broadcast domain.
ethernet cfm domain CUSTOMER level 7service customer_100 vlan 100service customer_100 evc evc100!ethernet evc evc100!interface Ethernet0/0service instance 100 ethernet evc100encapsulation dot1q 100bridge-domain 100Related Commands
service instance ethernet
To configure an Ethernet service instance on an interface and to enter Ethernet service configuration mode, use the service instance ethernet command in interface configuration mode. To delete a service instance, use the no form of this command.
service instance id ethernet [evc-name]
no service instance id
Syntax Description
Command Default
No Ethernet service instances are defined.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
A service instance is a configuration object (container) that holds all management and control-plane attributes and parameters that apply to that service instance on a per-port basis. Different service instances that correspond to the same EVC must share the same name. Service instances are associated with a global EVC object through their shared name.
After you enter the service instance ethernet command, the device enters Ethernet service configuration mode, and these configuration commands are available:
•
•
•
•
•
Examples
The following example shows how to define an Ethernet service instance and enter Ethernet service configuration mode for an EVC:
Router(config-if)# service instance 333 ethernet testRouter(config-if-srv)#Related Commands
service instance ethernet (mac-tunnel)
To define an Ethernet flow point (EFP) that corresponds to a specific service instance ID (I-SID) encapsulation and to place the command-line interface (CLI) into MAC tunnel service configuration mode, use the service instance ethernet command in MAC-in-MAC tunnel configuration mode. To delete an EFP, use the no form of this command.
service instance id ethernet
no service instance id
Syntax Description
Command Default
EFPs are not defined.
Command Modes
MAC-in-MAC tunnel configuration (config-tunnel-minm)
Command History
Usage Guidelines
Use this command to define an EFP and map it to a specific I-SID encapsulation.
When this command is issued, the CLI enters MAC tunnel service configuration mode.
Examples
The following example shows how to define an EFP and place the CLI into MAC tunnel service configuration mode:
Router(config)# ethernet mac-tunnel virtual 100Router(config-tunnel-minm)# service instance 5 ethernetRouter(config-tunnel-srv)#service vlan
To set a universally unique ID for a customer service instance (CSI) within a maintenance domain, use the service vlan command in Ethernet connectivity fault management (CFM) configuration mode. To remove a universally unique ID for a service within a maintenance domain, use the no form of this command.
service csi-id {evc evc-name | vlan vlan-id}
no service csi-id {evc evc-name | vlan vlan-id}
Syntax Description
Syntax DescriptionCommand Syntax]
Command Default
No universally unique ID is set for the CSI.
Command Modes
Ethernet CFM configuration (config-ether-cfm)
Command History
Usage Guidelines
A fully qualified service ID consists of a service ID plus a domain name. Service IDs identify customers within a domain. Ethernet CFM requires that service IDs are unique in a network.
You must configure a service VLAN before you can configure a MEP for a domain.
The following restrictions apply when you issue the service vlan command:
•
•
•
For two domains at the same maintenance level, the same service ID can be used for two different VLANs. If you try to configure the same service ID for two VLANs in the same domain, the command is rejected and an error message displays.
Specifying a domain as outward allows you to create multiple outward domains at the same level with a set of services that overlap. These VLANs also can overlap with inward domains. Note that a set of VLANs overlapping inward domains at only the same level must be unique.
You can use the same service ID in the same VLAN or different VLANs if the service IDs are in different levels.
Before you remove a service ID, all MEPs corresponding to the service must be removed.
On Cisco 7600 series devices, a VLAN service and an EVC service may have the same service ID if the bridge domain is associated with the EVC. The reason for this shared ID is that the bridge domain and the VLAN with the same ID form a single broadcast domain representing the same CFM service.
Examples
The following example shows how to configure a CFM service on a Cisco 7600 Series RSP 720 device. You must configure the VLAN and EVC services with the same name because VLAN 100 and bridge domain 100, which are associated with evc100, represent a single broadcast domain.
ethernet cfm domain CUSTOMER level 7service customer_100 vlan 100service customer_100 evc evc100!ethernet evc evc100!interface Ethernet0/0service instance 100 ethernet evc100encapsulation dot1q 100bridge-domain 100The following example shows how to set a unique service ID within a maintenance domain:
Router(config-ether-cfm)# service firstinstance vlan 35
