![]() |
Cisco IOS Carrier Ethernet Command Reference
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ais through ethernet cfm logging
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Contents
ais through ethernet cfm logging aisTo enable the Alarm Indication Signal (AIS) function for a specific maintenance association, use the ais command in Ethernet connectivity fault management (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
Usage GuidelinesAlarms 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. alarmTo configure an alarm when fault alarms are enabled, use the alarmcommand 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
Usage GuidelinesThis command overrides the global ethernet cfm alarmcommand. 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. ExamplesThe following example shows how to set up notifications for all defects: Router(config)# ethernet cfm domain test level 5 Router(config-ecfm)# service vlan-id 17 vlan 17 Router(config-ecfm-srv)# exit Router(config-ecfm)# exit Router(config-if)# ethernet cfm mep domain test mpid 5 vlan 17 Router(config-if-ecfm-mep)# alarm notification all Router(config-if-ecfm-mep)# The 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 5 Router(config-ecfm)# service vlan-id 17 vlan 17 Router(config-ecfm-srv)# exit Router(config-ecfm)# exit Router(config-if)# ethernet cfm mep domain test mpid 5 vlan 17 Router(config-if-ecfm-mep)# alarm delay 7000 announce intervalTo 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. Command DefaultFor the IE 3000 switch, the default value is 1. For the MWR 2941 router, the default value is 2. Usage GuidelinesThe interval value defined by this command impacts the timeout value defined by the announce timeout command. announce timeoutTo 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. Usage GuidelinesThis 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. aps-channelbackbone interfaceTo 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. Usage GuidelinesUse 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). bridge-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 DescriptionUsage GuidelinesWhen 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.
ExamplesThe following example shows how to configure a bridge domain as a customer domain and place the CLI in bridge-domain configuration mode: Router> enable Router# configure terminal Router(config)# bridge-domain 100 c-mac Router(config-bdomain)# mac limit maximum addresses 10 The following example shows how to configure a bridge domain as a customer domain with an aging time of 400 minutes: Router> enable Router# configure terminal Router(config)# bridge-domain c-mac aging-time 400 Router(config)# 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 Device
bridge-domain
bridge-id
[split-horizon group group-id]
no
bridge-domain
bridge-id
[split-horizon group group-id]
Syntax DescriptionCommand ModesService instance configuration (config-if-svc) MAC-in-MAC tunnel configuration (config-tunnel-minm) Command History
Usage GuidelinesUse 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 Device does not support MAC tunnels. ExamplesThe following example shows how to bind a bridge domain to a service instance: Device> enable Device# configure terminal Device(config)# interface gigabitethernet 2/0/0 Device(config-if)# service instance 100 ethernet Device(config-if-srv)# encapsulation dot1q 100 Device(config-if-srv)# bridge-domain 200 The following example shows how to bind a MAC tunnel to a service instance: Device> enable Device# configure terminal Device(config)# ethernet mac-tunnel virtual 100 Device(config-tunnel-minm)# bridge-domain 200 bridge-domain from-encapsulationTo create a range of bridge domains on the basis of the bridge-domain IDs derived from encapsulation VLAN numbers, use the bridge-domain from-encapsulation command in Ethernet service configuration mode. To remove the bridge domains, use the no form of this command. Usage GuidelinesUse the bridge-domain from-encapsulation command in Ethernet service configuration mode (config-if-srv) to configure support for Ethernet Flow Points (EFPs) on trunk ports (interfaces). To enter Ethernet service configuration mode (config-if-srv), use the service instance ethernet command. The bridge-domain from-encapsulation command is used in conjunction with the encapsulation dot1q command. The bridge-domain from-encapsulation command uses the VLAN range specified by the encapsulation dot1q command to create the corresponding range of bridge domains. In the following example, bridge domains in the range of 12 to 1900 are created on the basis of the VLAN range specified by the encapsulation dot1q command. Router(config)# interface GigabitEthernet0/0/5 Router(config-if)# service instance trunk 4000 ethernet Router(config-if-srv)# encapsulation dot1q 12-1900 Router(config-if-srv)# bridge-domain from-encapsulation ExamplesThe following is an example of the bridge-domain from-encapsulation command in a typical configuration: Router(config)# interface gigabitethernet2/0/1 Router(config-if)# service instance trunk 1 ethernet Router(config-if-srv)# encapsulation dot1q 1 - 5, 7, 9-12 Router(config-if-srv)# bridge-domain from-encapsulation cfm encapsulationTo 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
Usage GuidelinesTo 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. ExamplesThe following example shows how to configure the cfm encapsulation command: ethernet cfm domain CUSTOMER level 7 direction outward service customer_100 evc evc_100 ethernet cfm domain MIP level 7 ethernet cfm domain PROVIDER level 4 service provider_100 evc evc_100 mep crosscheck mpid 200 evc evc_100 mac aabb.cc00.0310 ethernet evc evc_100 interface Ethernet 1/0 no ip address service instance 100 ethernet evc_100 encapsulation dot1q 100 bridge-domain 100 cfm encapsulation dot1q 1 cos 2 second-dot1q 3 cos 4 cfm mep domainTo 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
Usage GuidelinesThe cfm mep domain command defines an Ethernet flow point as an 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. ExamplesThe following example shows how to configure the cfm mep domain command: ethernet cfm domain CUSTOMER level 7 direction outward service customer_100 evc evc_100 ethernet cfm domain MIP level 7 ethernet cfm domain PROVIDER level 4 service provider_100 evc evc_100 mep crosscheck mpid 200 evc evc_100 mac aabb.cc00.0310 ethernet evc evc_100 interface Ethernet 1/0 no ip address service instance 100 ethernet evc_100 encapsulation dot1q 100 bridge-domain 100 cfm mep domain CUSTOMER outward mpid 1001 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 DescriptionCommand History
Usage GuidelinesOSMs 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 onkeyword, 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 numberdepends 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.
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 addresscommand 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. To display information about the Fast EtherChannel, use the show interfaces port-channelEXEC 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 ExamplesThis 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 on
Router(config-if)#
The 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 1 Router(config-if)# exit Router(config)# interface fastethernet 1/0 Router(config-if)# channel-group 1 Related Commands
clear bridge-domain mac-tableTo clear a bridge domain of learned MAC addresses, use the clear bridge-domain mac-tablecommand in privileged EXEC mode. Usage GuidelinesUse 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 linecards. To invoke this command use the remote command module command; for example, remote command module 10 clear bridge-domain 25 mac-table. ExamplesThe 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 table The 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.aaaa clear ethernet cfm aisTo clear a maintenance endpoint (MEP) or server maintenance endpoint (SMEP) from the Ethernet Connectivity Fault Management (CFM) Alarm Indication Signal (AIS) defect condition, use the clear ethernet cfm ais command in privileged EXEC mode. CFM Cisco Proprietary Draft 8 (CFM D8)
clear
ethernet
cfm
ais
{domain domain-name mpid mpid-id {evc name | port | 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
Usage GuidelinesIf an 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. ExamplesThe following example shows how to clear an SMEP of an AIS defect condition:
Router# clear ethernet cfm ais link-status interface ethernet 0/0
The following example shows how to clear an MEP of an AIS defect condition: Router# clear ethernet cfm ais domain ciso.com mpid 100 vlan 11 Router# clear ethernet cfm ais domain cisco.com mpid 100 evc test clear ethernet cfm errorsTo 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 {icc icc-code meg-code | maintenance-association-name | maintenance-association-number | vlan-id vlan-id | vpn-id vpn-id}]
Syntax Description
Command History
Usage GuidelinesUse 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 is more than 43 characters in length, 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. ExamplesThe following is an example from the clear ethernet cfm errors command for errors at maintenance level 3. No output is generated when this command is issued.
Device# clear ethernet cfm errors level 3
The following example shows how to clear errors for a DNS on VLAN 17. No output is generated when this command is issued.
Device# clear ethernet cfm errors domain-id dns Service10 service vlan-id 17
clear ethernet cfm maintenance-points remoteTo 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 DescriptionCommand DefaultThe continuity check database is unchanged; existing entries remain in the database. Command History
Usage GuidelinesUse 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 maintenence 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. clear ethernet cfm statisticsTo 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. Usage GuidelinesIf a MEP does not exit the AIS state when all errors are resolved, use the clear ethernet cfm ais command with the domainand mpidkeywordsto 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 interfacekeywords to clear the AIS defect condition. clear ethernet cfm traceroute-cacheTo remove the contents of the traceroute cache, use the clear ethernet cfm traceroute-cache command in privileged EXEC mode. Command History
Usage GuidelinesUse 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. clear ethernet lmi statisticsTo 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. Syntax DescriptionUsage GuidelinesThis 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 statisticscommand to reset the counter. At the end of the hour, you would issue the show ethernet lmi statisticscommand to display errors that occurred during that one-hour time period. ExamplesThe following example shows how to clear Ethernet LMI statistics counters on all interfaces: Router# clear ethernet lmi statistics Clear "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/0
Clear "show ethernet lmi" statistics counters on this interface [confirm]
Router#
clear ethernet oam statisticsTo reset Ethernet operations, maintenance, and administration (OAM) counters and event statistics on all interfaces or on a specific interface, use the clear ethernet oam statisticscommand in privileged EXEC mode. Usage GuidelinesUse 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. clear ethernet ring g8032 statisticsTo clear the statistic counters for one or more Ethernet Ring Protocol ( ERP) instances, use the clear ethernet ring g8032 statistics command in user EXEC mode. clear ethernet service instanceTo 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
Usage GuidelinesUse the clear ethernet service instancecommand to clear service instance attributes that are not needed and to purge service instance errors. clear lldpTo reset either the Link Layer Discovery Protocol (LLDP) traffic counters or the table that contains LLDP information about neighbors, use the clear lldpcommand in privileged EXEC mode. Command DefaultThe LLDP traffic counters are not reset, and the table of LLDP information is not cleared. Usage GuidelinesUse this command for informational purposes or to test a symptom of network malfunction such as packet loss. ExamplesThe 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. Device# clear lldp counters Device# show lldp traffic LLDP traffic statistics: Total frames out: 0 Total entries aged: 0 Total frames in: 0 Total frames received in error: 0 Total frames discarded: 0 Total TLVs unrecognized: 0 The 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. Device# clear lldp table Device# show lldp neighbors Capability codes: (R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device (W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other Device ID Local Intf Hold-time Capability Port ID clock destinationTo 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. Usage GuidelinesIf 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. clock-portTo 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. ExamplesThe following example shows how to configure a PTP clock port: Router# configure terminal Router# ptp clock boundary domain 0 Router(config-ptp-clk)# clock-port slave slaveport Router(config-ptp-port)# clock source 8.8.8.1 Router(config-ptp-port)# sync limit 1 Router(config-ptp-port)# announce timeout 4 Router(config-ptp-port)# delay-req interval 2 Router(config-ptp-port)# end Router# 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. ExamplesThe following example shows how to specify a clock source: Router# configure terminal Router(config)# ptp clock ordinary domain 0 Router(config-ptp-clk)# tod 3/0 ntp Router(config-ptp-clk)# output 1pps 3/0 Router(config-ptp-clk)# clock-port slaveport slave Router(config-ptp-port)# transport ipv4 unicast interface GigabitEthernet3/0/1 negotiation Router(config-ptp-port)# clock source 103.113.0.1 continuity-checkTo 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 DescriptionUsage GuidelinesThe 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. 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. Usage GuidelinesThis command is used to set the priority of messages. CoS may not be supported on all platforms. ExamplesThe following example shows how to set the CoS to 5: Router(config)# ethernet cfm domain test level 5 Router(config-ecfm)# service vlan-id 17 vlan 17 Router(config-ecfm-srv)# end Router# configure terminal Router(config)# interface gigabitethernet 0/2 Router(config-if)# ethernet cfm mep domain test mpid 5 vlan 17 Router(config-if-ecfm-mep)# cos 5 delay-req intervalTo 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. Syntax Descriptiondescription (Ethernet ring)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. Command ModesMAC-in-MAC tunnel configuration (config-tunnel-minm) MAC tunnel service configuration (config-tunnel-srv) Usage GuidelinesUse this command to identify and describe the type of service for which the MAC tunnel is used. ExamplesThe 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 100 Router(config-tunnel-minm)# description MAC-Tunnel-100 Router(config-tunnel-minm)# service instance 1 ethernet Router(config-tunnel-srv)# description ServInst-1 disable (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. Usage GuidelinesWhen the default value is configured, "no disable" is displayed when the show running all command is issued. encapsulation dot1ah isidTo 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. errdisable recovery cause mac-securityTo 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. Usage GuidelinesA 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 instancecommand to bring the service instance out of the error-disabled state. ExamplesThe 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> enable Router# configure terminal Router(config)# interface gigabitethernet 3/0/1 Router(config-if)# service instance 200 ethernet Router(config-if-srv)# encapsulation dot1Q 200 Router(config-if-srv)# bridge-domain 100 Router(config-if-srv)# mac security Router(config-if-srv)# errdisable recovery cause mac-security 30 errdisable recovery cause mlacp-minlinkTo 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. Command DefaultThis 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. Usage GuidelinesUse the errdisable recovery cause mlacp-minlinkcommand 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 intervalseconds command. ethernet cfm aisTo configure Ethernet Connectivity Fault Management (CFM) 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 an SMEP, use the no form of this command. ethernet cfm ais {domain domain-name | {evc name | vlan vlanid | {vlanid-vlanid | , vlanid-vlanid} | link-status global}}
no ethernet cfm ais {domain domain-name | {evc name | vlan vlanid | {vlanid-vlanid | , vlanid-vlanid} | link-status global}}
Syntax Description
Usage GuidelinesThe ethernet cfm ais command allows you to configure, enable, or disable AIS generation from an MEP or SMEP. To change the default values for AIS generation on an SMEP, use the link-status global keywords. To change the default values for AIS generation on an MEP, use the domain keyword. ExamplesThe following example shows how to specify AIS generation on a domain named PROVIDER and on VLAN 10:
Router(config)# ethernet cfm ais domain PROVIDER vlan 10
The following example shows how to enable AIS generation and place the CLI in Ethernet CFM AIS MEP configuration mode:
Router(config)# ethernet cfm ais link-status global
Router(config-ais-mep-cfm)#
ethernet cfm ais link-statusTo enable Alarm Indication Signal (AIS) generation from a server maintenance endpoint (SMEP), use the ethernet cfm ais link-statuscommand 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
Usage GuidelinesThis command has precedence over the ethernet cfm ais link-status globalcommand issued in global configuration mode. ethernet cfm ais link-status globalTo globally enable Alarm Indication Signal (AIS) generation and place the CLI in Ethernet Connectivity Fault Management (CFM) AIS MEP configuration mode , 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 alarmTo configure an alarm for Ethernet connectivity fault management (CFM), use the ethernet cfm alarmcommand 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 DescriptionCommand History
Usage GuidelinesIf 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. ExamplesThe following example shows how to set up notification for all defects: Router(config)# ethernet cfm alarm notification all The 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 5000 The following example shows how to set the maximum number of DefError and DefXcon fault alarm packets to 6500: Router(config)# ethernet cfm alarm packet 6500 ethernet cfm ccTo set the parameters for continuity check messages (CCMs), use the ethernet cfm cccommand 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 DefaultFor all maintenance levels and VLANs configured on a device, the interval is 30 seconds and the loss-threshold is 2. Command History
Usage GuidelinesThe ethernet cfm cccommand is used to set parameters for generating and receiving CCMs in one of the following ways:
When the ethernet cfm cccommandis 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 cccommand 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).
ExamplesThe 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.
Device(config)# ethernet cfm cc level 5 vlan any interval 30 loss-threshold 2
(NVGEN)ethernet cfm cc level 5 vlan any
The 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:
Device(config)# ethernet cfm cc level 5 vlan any interval 1000 loss-threshold 2
(NVGEN)ethernet cfm cc level 5 vlan any interval 1000
The 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):
Device(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 7
The 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): Device(config)# ethernet cfm cc level 1-5 vlan 100-200 interval 50 loss-threshold 5 Device(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 5 ethernet cfm cc level 1,4-5 vlan 100-200 interval 50 loss-threshold 5 The 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): Device(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 3 ethernet cfm cc enable level evcTo globally enable transmission of continuity check messages (CCMs), use the ethernet cfm cc enable level evccommand 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
Usage GuidelinesUse the ethernet cfm cc enable level evccommand to enable transmission of CCMs in one of the following ways: ExamplesThe following example shows how to configure the ethernet cfm cc enable level evccommand for EVC evc5:
Router (config)# ethernet cfm cc enable level 5 evc evc5
How you enter the ethernet cfm cc enable level evccommand 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 evc1
The configuration shows the following: ethernet cfm cc enable level 1-5 evc evc1 To 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 evc1
ethernet cfm cc enable level vlanTo globally enable transmission of continuity check messages (CCMs), use the ethernet cfm cc enable level vlancommand 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}
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
Usage GuidelinesUse the ethernet cfm cc enable level vlancommand to enable transmission of CCMs in one of the following ways:
How you enter the ethernet cfm cc enable level vlancommand and the format you see in the configuration may be different. For example, if you enter:
Device(config)# ethernet cfm cc enable level 1,2,3,4,5 vlan 100,101,102,103,105
The configuration shows the following: ethernet cfm cc enable level 1-5 vlan 100-103,105 To shorten the length of the command, you also can enter it this way. ExamplesThe following examples show how this command functions: ethernet cfm cc enable level 1-5 vlan 100-200 Device(config)# no ethernet cfm cc enable level 2-3 vlan 50-150
ethernet cfm cc enable level 1,4-5 vlan 100-200 ethernet cfm cc enable level 2-3 vlan 151-200 ethernet cfm distribution enableTo enable Ethernet connectivity fault management (CFM) distribution, use the ethernetcfmdistributionenable command in the global configuration mode. To disable distribution, use the no form of this command. Usage GuidelinesOn the Cisco 7600 series router, this command must be configured before Ethernet performance monitoring (EPM) sessions are configured. When you issue the noethernetcfmdistributionenable 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 ipslareset command to clear all the IP SLA configurations, or you can clear each one individually. ethernet cfm domain levelTo define a connectivity fault management (CFM) maintenance domain at a particular maintenance level and enter Ethernet CFM configuration mode, use the ethernet cfm domain levelcommand 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 DescriptionCommand DefaultNo maintenance domains are assigned to maintenance levels if this command is not issued. Command History
Usage GuidelinesWhen a device 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." ExamplesThe 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:
Device(config)# ethernet cfm domain domain1 level 6 direction outward
Device(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:
Device(config)# ethernet cfm domain cust10 level 5
Device(config-ecfm)#
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. Usage GuidelinesEthernet 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. ethernet cfm enableTo 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 globalTo enable Ethernet connectivity fault management (CFM) globally on a device, use the ethernet cfm globalcommand in global configuration mode. To disable CFM globally on a device, use the no form of this command. ethernet cfm ieeeTo enable the Ethernet Connectivity Fault Management 802.1ag Standard (CFM IEEE) version of CFM, use the ethernet cfm ieeecommand in global configuration mode. To disable the CFM IEEE version, use the no form of this command. ethernet cfm interfaceTo enable Ethernet connectivity fault management (CFM) processing on a port, use the ethernet cfm interfacecommand in interface configuration mode. To disable Ethernet CFM processing, use the no form of this command. Usage GuidelinesThis 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. ethernet cfm loggingTo 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
ExamplesThe following example shows how to enable all Ethernet CFM syslog messages:
Router(config)# ethernet cfm logging
The following example shows how to enable all alarm syslog messages for Cisco MIBs:
Router(config)# ethernet cfm logging alarm cisco
The following example shows how to enable syslog messages specific to the CFM AIS feature:
Router(config)# ethernet cfm logging ais
© 2012 Cisco Systems, Inc. All rights reserved.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|