The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Ethernet Connectivity Fault Management (CFM) is an end-to-end per-service-instance Ethernet layer operations, administration, and maintenance (OAM) protocol. It includes proactive connectivity monitoring, fault verification, and fault isolation for large Ethernet metropolitan-area networks (MANs) and WANs.
The advent of Ethernet as a MAN and WAN technology imposes a new set of OAM requirements on Ethernet’s traditional operations, which were centered on enterprise networks only. The expansion of Ethernet technology into the domain of service providers, where networks are substantially larger and more complex than enterprise networks and the user base is wider, makes operational management of link uptime crucial. More importantly, the timeliness in isolating and responding to a failure becomes mandatory for normal day-to-day operations, and OAM translates directly to the competitiveness of the service provider.
Network topology and network administration have been evaluated.
Business and service policies have been established.
CFM loopback messages will not be confined within a maintenance domain according to their maintenance level. The impact of not having CFM loopback messages confined to their maintenance levels occurs at these levels:
Architecture—CFM layering is violated for loopback messages.
Deployment—A user may potentially misconfigure a network and have loopback messages succeed.
Security—A malicious device that recognizes devices’ MAC addresses and levels may potentially explore a network topology that should be transparent.
CFM is not fully supported on a Multiprotocol Label Switching (MPLS) provider edge (PE) device. There is no interaction between CFM and an Ethernet over MPLS (EoMPLS) pseudowire.
CFM configuration is not supported on an EtherChannel in FastEthernet Channel (FEC) mode.
QinQ encapsulation is not supported on the Cisco ASR 1000 Series Aggregation Services Router for CFM for routed subinterfaces.
Ethernet CFM is an end-to-end per-service-instance Ethernet layer OAM protocol that includes proactive connectivity monitoring, fault verification, and fault isolation. End to end can be PE to PE or CE to CE. A service can be identified as a service provider VLAN (S-VLAN) or an EVC service.
Being an end-to-end technology is the distinction between CFM and other metro-Ethernet OAM protocols. For example, MPLS, ATM, and SONET OAM help in debugging Ethernet wires but are not always end-to-end. 802.3ah OAM is a single-hop and per-physical-wire protocol. It is not end to end or service aware.
Troubleshooting carrier networks offering Ethernet Layer 2 services is challenging. Customers contract with service providers for end-to-end Ethernet service and service providers may subcontract with operators to provide equipment and networks. Compared to enterprise networks, where Ethernet traditionally has been implemented, these constituent networks belong to distinct organizations or departments, are substantially larger and more complex, and have a wider user base. Ethernet CFM provides a competitive advantage to service providers for which the operational management of link uptime and timeliness in isolating and responding to failures is crucial to daily operations.
End-to-end service-level OAM technology
Reduced operating expense for service provider Ethernet networks
Competitive advantage for service providers
Supports both distribution and access network environments with the outward facing MEPs enhancement
A customer service instance is an Ethernet virtual connection (EVC), which is identified by an S-VLAN within an Ethernet island, and is identified by a globally unique service ID. A customer service instance can be point-to-point or multipoint-to-multipoint. The figure below shows two customer service instances. Service Instance Green is point to point; Service Instance Blue is multipoint to multipoint.
A maintenance domain is a management space for the purpose of managing and administering a network. A domain is owned and operated by a single entity and defined by the set of ports internal to it and at its boundary. The figure below illustrates a typical maintenance domain.
A unique maintenance level in the range of 0 to 7 is assigned to each domain by a network administrator. Levels and domain names are useful for defining the hierarchical relationship that exists among domains. The hierarchical relationship of domains parallels the structure of customer, service provider, and operator. The larger the domain, the higher the level value. For example, a customer domain would be larger than an operator domain. The customer domain may have a maintenance level of 7 and the operator domain may have a maintenance level of 0. Typically, operators would have the smallest domains and customers the largest domains, with service provider domains between them in size. All levels of the hierarchy must operate together.
Domains should not intersect because intersecting would mean management by more than one entity, which is not allowed. Domains may nest or touch but when two domains nest, the outer domain must have a higher maintenance level than the domain nested within it. Nesting maintenance domains is useful in the business model where a service provider contracts with one or more operators to provide Ethernet service to a customer. Each operator would have its own maintenance domain and the service provider would define its domain—a superset of the operator domains. Furthermore, the customer has its own end-to-end domain which is in turn a superset of the service provider domain. Maintenance levels of various nesting domains should be communicated among the administering organizations. For example, one approach would be to have the service provider assign maintenance levels to operators.
CFM exchanges messages and performs operations on a per-domain basis. For example, running CFM at the operator level does not allow discovery of the network by the higher provider and customer levels.
Network designers decide on domains and configurations. The figure below illustrates a hierarchy of operator, service provider, and customer domains and also illustrates touching, intersecting, and nested domains.
A maintenance point is a demarcation point on an interface (port) that participates in CFM within a maintenance domain. Maintenance points on device ports act as filters that confine CFM frames within the bounds of a domain by dropping frames that do not belong to the correct level. Maintenance points must be explicitly configured on Cisco devices. Two classes of maintenance points exist, MEPs and MIPs.
Maintenance endpoints (MEPs) have the following characteristics:
Per maintenance domain (level) and service (S-VLAN or EVC)
At the edge of a domain, define the boundary
Within the bounds of a maintenance domain, confine CFM messages
When configured to do so, proactively transmit Connectivity Fault Management (CFM) continuity check messages (CCMs)
At the request of an administrator, transmit traceroute and loopback messages
Inward facing means the MEP communicates through the Bridge Relay function and uses the Bridge-Brain MAC address. An inward facing MEP performs the following functions:
Sends and receives CFM frames at its level through the relay function, not via the wire connected to the port on which the MEP is configured.
Drops all CFM frames at its level (or lower level) that come from the direction of the wire.
Processes all CFM frames at its level coming from the direction of the relay function.
Drops all CFM frames at a lower level coming from the direction of the relay function.
Transparently forwards all CFM frames at its level or a higher level, independent of whether they come in from the relay function side or the wire side.
 Note |
A MEP of level L (where L is less than 7) requires a MIP of level M > L on the same port; hence, CFM frames at a level higher than the level of the MEP will be catalogued by this MIP. |
If the port on which the inward MEP is configured is blocked by Spanning-Tree Protocol, the MEP can no longer transmit or receive CFM messages.
Outward facing means that the MEP communicates through the wire. Outward facing MEPs can be configured on port channels (using cross connect functionality). A MIP configuration at a level higher than the level of the outward facing MEP is not required.
Outward facing MEPs on port channels use the Bridge-Brain MAC address of the first member link. When port channel members change, the identities of outward facing MEPs do not have to change.
An outward facing MEP performs the following functions:
Sends and receives CFM frames at its level via the wire connected to the port where the MEP is configured.
Drops all CFM frames at its level (or at a lower level) that come from the direction of the relay function.
Processes all CFM frames at its level coming from the direction of the wire.
Drops all CFM frames at a lower level coming from the direction of the wire.
Transparently forwards all CFM frames at levels higher than the level of the outward facing MEP, independent of whether they come in from the relay function side or the wire side.
If the port on which the outward MEP is configured is blocked by the Spanning-Tree Protocol, the MEP can still transmit and receive CFM messages via the wire.
MIPs have the following characteristics:
Per maintenance domain (level) and for all S-VLANs enabled or allowed on a port.
Internal to a domain, not at the boundary.
CFM frames received from MEPs and other MIPs are cataloged and forwarded, using both the wire and the relay function.
All CFM frames at a lower level are stopped and dropped, independent of whether they originate from the wire or relay function.
All CFM frames at a higher level are forwarded, independent of whether they arrive from the wire or relay function.
MIPs respond only when triggered by CFM traceroute and loopback messages.
Bridge-Brain MAC addresses are used.
If the port on which a MIP is configured is blocked by Spanning-Tree Protocol, the MIP cannot receive CFM messages or relay them toward the relay function side. The MIP can, however, receive and respond to CFM messages from the wire.
A MIP has only one level associated with it and the command-line interface (CLI) does not allow you to configure a MIP for a domain that does not exist.
The figure below illustrates MEPs and MIPs at the operator, service provider, and customer levels.
CFM uses standard Ethernet frames. CFM frames are distinguishable by EtherType and for multicast messages by MAC address. CFM frames are sourced, terminated, processed, and relayed by bridges. Routers can support only limited CFM functions.
Bridges that cannot interpret CFM messages forward them as normal data frames. All CFM messages are confined to a maintenance domain and to an S-VLAN (PE-VLAN or Provider-VLAN). Three types of messages are supported:
Continuity Check
Loopback
Traceroute
CFM CCMs are multicast heartbeat messages exchanged periodically among MEPs. They allow MEPs to discover other MEPs within a domain and allow MIPs to discover MEPs. CCMs are confined to a domain and S-VLAN.
CFM CCMs have the following characteristics:
Transmitted at a configurable periodic interval by MEPs. The interval can be from 10 seconds to 65535 seconds, the default is 30.
Contain a configurable hold-time value to indicate to the receiver the validity of the message. The default is 2.5 times the transmit interval.
Catalogued by MIPs at the same maintenance level.
Terminated by remote MEPs at the same maintenance level.
Unidirectional and do not solicit a response.
Carry the status of the port on which the MEP is configured.
CFM loopback messages are unicast frames that a MEP transmits, at the request of an administrator, to verify connectivity to a particular maintenance point. A reply to a loopback message indicates whether a destination is reachable but does not allow hop-by-hop discovery of the path. A loopback message is similar in concept to an Internet Control Message Protocol (ICMP) Echo (ping) message.
A CFM loopback message can be generated on demand using the CLI. The source of a loopback message must be a MEP; the destination may be a MEP or a MIP. CFM loopback messages are unicast; replies to loopback messages also are unicast. CFM loopback messages specify the destination MAC address, VLAN, and maintenance domain.
CFM traceroute messages are multicast frames that a MEP transmits, at the request of an administrator, to track the path (hop-by-hop) to a destination MEP. They allow the transmitting node to discover vital connectivity data about the path, and allow the discovery of all MIPs along the path that belong to the same maintenance domain. For each visible MIP, traceroute messages indicate ingress action, relay action, and egress action. Traceroute messages are similar in concept to User Datagram Protocol (UDP) traceroute messages.
Traceroute messages include the destination MAC address, VLAN, and maintenance domain and they have Time To Live (TTL) to limit propagation within the network. They can be generated on demand using the CLI. Traceroute messages are multicast; reply messages are unicast.
The cross-check function is a timer-driven post-provisioning service verification between dynamically discovered MEPs (via CCMs) and expected MEPs (via configuration) for a service. The cross-check function verifies that all endpoints of a multipoint or point-to-point service are operational. The function supports notifications when the service is operational; otherwise it provides alarms and notifications for unexpected endpoints or missing endpoints.
The cross-check function is performed one time. You must initiate the cross-check function from the CLI every time you want a service verification.
The support provided by the Cisco software implementation of CFM traps is Cisco proprietary information. MEPs generate two types of Simple Network Management Protocol (SNMP) traps, continuity check (CC) traps and cross-check traps.
MEP up—Sent when a new MEP is discovered, the status of a remote port changes, or connectivity from a previously discovered MEP is restored after interruption.
MEP down—Sent when a timeout or last gasp event occurs.
Cross-connect—Sent when a service ID does not match the VLAN.
Loop—Sent when a MEP receives its own CCMs.
Configuration error—Sent when a MEP receives a continuity check with an overlapping MPID.
Service up—Sent when all expected remote MEPs are up in time.
MEP missing—Sent when an expected MEP is down.
Unknown MEP—Sent when a CCM is received from an unexpected MEP.
To understand how CFM and OAM interact, you should understand the following concepts:
An EVC as defined by the Metro Ethernet Forum is a port-level point-to-point or multipoint-to-multipoint Layer 2 circuit. EVC status can be used by a CE device either to find an alternative path in to the service provider network or in some cases, to fall back to a backup path over Ethernet or over another alternative service such as ATM.
The OAM manager is an infrastructure element that streamlines interaction between OAM protocols. The OAM manager requires two interworking OAM protocols, in this case Ethernet CFM and Ethernet OAM. Interaction is unidirectional from the OAM manager to the CFM protocol and the only information exchanged is the user network interface (UNI) port status. Additional port status values available include
REMOTE_EE—Remote excessive errors
LOCAL_EE—Local excessive errors
TEST—Either remote or local loopback
After CFM receives the port status, it communicates that status across the CFM domain.
Connectivity Fault Management (CFM) over bridge domains allows untagged CFM packets to be associated with a maintenance end point (MEP). An incoming untagged customer CFM packet has an EtherType of CFM and is mapped to an Ethernet virtual circuit (EVC) or bridge domain based on the encapsulation configured on the Ethernet flow point (EFP). The EFP is configured specifically to recognize these untagged packets.
An EFP is a logical demarcation point of an EVC on an interface and can be associated with a bridge domain. The VLAN ID is used to match and map traffic to the EFP. VLAN IDs have local significance per port similar to an ATM virtual circuit. CFM is supported on a bridge domain associated with an EFP. The association between the bridge domain and the EFP allows CFM to use the encapsulation on the EFP. All EFPs in the same bridge domain form a broadcast domain. The bridge domain ID determines the broadcast domain.
The distinction between a VLAN port and the EFP is the encapsulation. VLAN ports use a default dot1q encapsulation. For EFPs, untagged, single tagged, and double tagged encapsulation exists with dot1q and IEEE dot1ad EtherTypes. Different EFPs belonging to the same bridge domain can use different encapsulations.
Both up MEP, down MEP and MIP are supported. If an up MEP is configured under an EFP within a bridge domain, CFM messages would be routed into the bridge, and the rest members of the same bridge domain would be able to receive messages from this MEP. If a down MEP is configured, the messages will not goes into the bridge domain.
In access and service provider networks using Ethernet technology, High Availability (H)A is a requirement, especially on Ethernet OAM components that manage EVC connectivity. End-to-end connectivity status information is critical and must be maintained on a hot standby Route Switch Processor (RSP).
Note |
A hot standby Route Switch Processor (RSP) has the same software image as the active RSP and supports synchronization of protocol and application state information between RSPs for supported features and protocols. |
End-to-end connectivity status is maintained on the customer edge (CE), provider edge (PE), and access aggregation PE (uPE) network nodes based on information received by protocols such as Connectivity Fault Management (CFM) and 802.3ah. This status information is used to either stop traffic or switch to backup paths when an EVC is down.
Every transaction involves either accessing or updating data among various databases. If the database is synchronized across active and standby modules, the modules are transparent to clients.
The Cisco infrastructure provides various component application program interfaces (APIs) that help to maintain a hot standby RSP. Metro Ethernet HA clients HA/ISSU, CFM HA/ISSU, and 802.3ah HA/ISSU interact with these components, update the database, and trigger necessary events to other components.
Elimination of network downtime for Cisco software image upgrades, allowing for faster upgrades.
Elimination of resource scheduling challenges associated with planned outages and late night maintenance windows.
Accelerated deployment of new services and applications and facilitation of faster implementation of new features.
Reduced operating costs due to outages while delivering higher service levels.
CFM updates its databases and controls its own HA messaging and versioning, and this control facilitates maintenance.
A standalone Connectivity Fault Management (CFM) implementation does not have explicit high availability (HA) requirements. When CFM is implemented on a customer edge (CE) or provider edge (PE), CFM must maintain the Ethernet virtual circuit (EVC) state, which requires HA because the EVC state is critical in maintaining end-to-end connectivity. CFM configures the platform with maintenance level, domain, and maintenance point, learns the remote maintenance point information, and maps it to the appropriate EVC. CFM then aggregates data received from all remote ports; consequently HA requirements vary for CE and PE.
The CE receives the EVC ID, associated customer VLANs, UNI information, EVC state, and remote UNI ID and state from the MEN. The CE relies on the EVC state to send or stop traffic to the MEN.
The PE has EVC configuration and associated customer VLAN information and derives the EVC state and remote UNI from CFM.
Note |
PEs and CEs running 802.3ah OAM must maintain the port state so peers are not affected by a switchover. This information is also sent to remote nodes in CFM CC messages. |
The redundancy configurations Stateful Switchover (SSO) and Nonstop Forwarding (NSF) are both supported in Ethernet Connectivity Fault Management (CFM) and are automatically enabled. A switchover from an active to a standby Route Switch Processor (RSP) occurs when the active RSP fails, is removed from the networking device, or is manually taken down for maintenance. NSF interoperates with the SSO feature to minimize network downtime following a switchover. The primary function of Cisco NSF is to continue forwarding IP packets following an RSP switchover.
For detailed information about SSO, see the “Configuring Stateful Switchover” module of the High Availability Configuration Guide. For detailed information about the NSF feature, see the “Configuring Cisco Nonstop Forwarding” module of the High Availability Configuration Guide.
In Service Upgrades (ISSUs) allow you to perform a Cisco software upgrade or downgrade without disrupting packet flow. Connectivity Fault Management (CFM) performs a bulk update and a runtime update of the continuity check database to the standby Route Switch Processor (RSP), including adding, deleting, or updating a row. This checkpoint data requires ISSU capability to transform messages from one release to another. All the components that perform active RSP to standby RSP updates using messages require ISSU support.
ISSU is automatically enabled in CFM and lowers the impact that planned maintenance activities have on network availability by allowing software changes while the system is in service. For detailed information about ISSU, see the “Performing an In Service Software Upgrade ” module of the High Availability Configuration Guide.
Note |
To have an operator, service provider, or customer domain is optional. A network may have a single domain or multiple domains. The steps listed here show the sequence when all three types of domains will be assigned. |
Knowledge and understanding of the network topology.
Understanding of organizational entities involved in managing the network; for example, operators, service providers, network operations centers (NOCs), and customer service centers.
Understanding of the type and scale of services to be offered.
Agreement by all organizational entities on the responsibilities, roles, and restrictions for each organizational entity.
Determination of the number of maintenance domains in the network.
Determination of the nesting and disjoint maintenance domains.
Assignment of maintenance levels and names to domains based on agreement between the service provider and operator or operators.
Determination of whether the domain should be inward or outward.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
Determine operator level MIPs. |
Follow these steps:
|
| Step 2 |
Determine operator level MEPs. |
Follow these steps:
|
| Step 3 |
Determine service provider MIPs. |
Follow these steps:
|
| Step 4 |
Determine service provider MEPs. |
Follow these steps:
|
| Step 5 |
Determine customer MIPs. |
Customer MIPs are allowed only on the UNIs at the uPEs if the service provider allows the customer to run CFM. Otherwise, the service provider can configure Cisco devices to block CFM frames.
|
| Step 6 |
Determine customer MEPs. |
Customer MEPs are on customer equipment. Assign an outward facing MEP within an outward domain at the appropriate customer level at the handoff between the service provider and the customer. |
The figure below shows an example of a network with a service provider and two operators, A and B. Three domains are to be established to map to each operator and the service provider. In this example, for simplicity we assume that the network uses Ethernet transport end to end. CFM, however, can be used with other transports.
After you have defined the Ethernet CFM domains, configure Ethernet CFM functionality by first provisioning the network and then provisioning service.
Configuring Ethernet CFM consists of the following tasks:
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ethernet cfm domain domain-name level level-id Example: |
Defines a CFM maintenance domain at a particular maintenance level and enters Ethernet CFM configuration mode. |
| Step 4 |
service short-ma-name evc evc-name vlan vlanid direction down Example: |
Configures a maintenance association within a maintenance domain and enters Ethernet connectivity fault management (CFM) service configuration mode. |
| Step 5 |
continuity-check Example: |
Configures the transmission of continuity check messages (CCMs). |
| Step 6 |
continuity-check [interval cc-interval] Example: |
Configures the per-service parameters and sets the interval at which CCMs are transmitted. |
| Step 7 |
exit Example: |
Returns to Ethernet connectivity fault management configuration mode. |
| Step 8 |
mep archive-hold-time minutes Example: |
Sets the amount of time that data from a missing MEP is kept in the continuity check database or that entries are held in the error database before they are purged. |
| Step 9 |
exit Example: |
Returns to global configuration mode. |
| Step 10 |
ethernet cfm global Example: |
Enables CFM processing globally on the device. |
| Step 11 |
ethernet cfm traceroute cache Example: |
Enables caching of CFM data learned through traceroute messages. |
| Step 12 |
ethernet cfm traceroute cache size entries Example: |
Sets the maximum size for the CFM traceroute cache table. |
| Step 13 |
ethernet cfm traceroute cache hold-time minutes Example: |
Sets the amount of time that CFM traceroute cache entries are retained. |
| Step 14 |
snmp-server enable traps ethernet cfm cc [mep-up ] [mep-down ] [config ] [loop ] [cross-connect ] Example: |
Enables SNMP trap generation for Ethernet CFM continuity check events. |
| Step 15 |
snmp-server enable traps ethernet cfm crosscheck [mep-unknown | mep-missing | service-up ] Example: |
Enables SNMP trap generation for Ethernet CFM continuity check events in relation to the cross-check operation between statically configured MEPS and those learned via CCMs. |
| Step 16 |
end Example: |
Returns to privileged EXEC mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ethernet cfm domain domain-name level level-id Example: |
Defines a CFM maintenance domain at a particular maintenance level and enters Ethernet CFM configuration mode. |
| Step 4 |
service short-ma-name evc evc-name vlan vlanid direction down Example: |
Configures a maintenance association within a maintenance domain and enters Ethernet connectivity fault management (CFM) service configuration mode. |
| Step 5 |
continuity-check Example: |
Configures the transmission of continuity check messages (CCMs). |
| Step 6 |
continuity-check [interval cc-interval] Example: |
Configures the per-service parameters and sets the interval at which CCMs are transmitted. |
| Step 7 |
exit Example: |
Returns to Ethernet connectivity fault management configuration mode. |
| Step 8 |
mep archive-hold-time minutes Example: |
Sets the amount of time that data from a missing MEP is kept in the continuity check database or that entries are held in the error database before they are purged. |
| Step 9 |
exit Example: |
Returns to global configuration mode. |
| Step 10 |
ethernet cfm global Example: |
Enables CFM processing globally on the device. |
| Step 11 |
ethernet cfm traceroute cache Example: |
Enables caching of CFM data learned through traceroute messages. |
| Step 12 |
ethernet cfm traceroute cache size entries Example: |
Sets the maximum size for the CFM traceroute cache table. |
| Step 13 |
ethernet cfm traceroute cache hold-time minutes Example: |
Sets the amount of time that CFM traceroute cache entries are retained. |
| Step 14 |
interface type number Example: |
Specifies an interface and enters interface configuration mode. |
| Step 15 |
service instance id ethernet [evc-name] Example: |
Configures an Ethernet service instance on an interface and enters Ethernet service configuration mode. |
| Step 16 |
encapsulation encapsulation-type Example: |
Sets the encapsulation method used by the interface. |
| Step 17 |
bridge-domain bridge-id Example: |
Binds a service instance to a bridge domain instance. |
| Step 18 |
cfm mip level { level } Example: |
Creates a MIP and sets the maintenance level number. |
| Step 19 |
exit Example: |
Returns to interface configuration mode. |
| Step 20 |
exit Example: |
Returns to global configuration mode. |
| Step 21 |
snmp-server enable traps ethernet cfm cc [mep-up ] [mep-down ] [config ] [loop ] [cross-connect ] Example: |
Enables SNMP trap generation for Ethernet CFM mep-up, mep-down, config, loop, and cross-connect events. |
| Step 22 |
snmp-server enable traps ethernet cfm crosscheck [mep-unknown | mep-missing | service-up ] Example: |
Enables SNMP trap generation for Ethernet CFM mep-unknown, mep-missing, and service-up continuity check events in relation to the cross-check operation between statically configured MEPs and those learned via CCMs. |
| Step 23 |
end Example: |
Returns to privileged EXEC mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ethernet cfm domain domain-name level level-id Example: |
Defines a CFM maintenance domain at a particular maintenance level and enters Ethernet CFM configuration mode. |
| Step 4 |
service short-ma-name evc evc-name vlan vlanid direction down Example: |
Configures a maintenance association within a maintenance domain and enters Ethernet connectivity fault management (CFM) service configuration mode. |
| Step 5 |
continuity-check Example: |
Configures the transmission of continuity check messages (CCMs). |
| Step 6 |
continuity-check [ interval cc-interval] Example: |
Configures the per-service parameters and sets the interval at which CCMs are transmitted. |
| Step 7 |
exit Example: |
Returns to Ethernet connectivity fault management configuration mode. |
| Step 8 |
mep archive-hold-time minutes Example: |
Sets the amount of time that data from a missing MEP is kept in the continuity check database or that entries are held in the error database before they are purged. |
| Step 9 |
exit Example: |
Returns the CLI to global configuration mode. |
| Step 10 |
ethernet cfm global Example: |
Enables CFM processing globally on the device. |
| Step 11 |
interface type number Example: |
Specifies an interface and enters interface configuration mode. |
| Step 12 |
service instance id ethernet [evc-name] Example: |
Configures an Ethernet service instance on an interface and enters Ethernet service configuration mode. |
| Step 13 |
encapsulation encapsulation-type Example: |
Sets the encapsulation method used by the interface. |
| Step 14 |
bridge-domain bridge-id Example: |
Binds a service instance to a bridge domain instance. |
| Step 15 |
cfm mip level level Example: |
Creates a MIP and sets the maintenance level number. |
| Step 16 |
end Example: |
Returns to privileged EXEC mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ethernet cfm domain domain-name level level-id Example: |
Defines a CFM maintenance domain at a particular maintenance level and enters Ethernet CFM configuration mode. |
| Step 4 |
service short-ma-name evc evc-name vlan vlanid direction down Example: |
Configures a maintenance association within a maintenance domain and enters Ethernet connectivity fault management (CFM) service configuration mode. |
| Step 5 |
continuity-check Example: |
Configures the transmission of continuity check messages (CCMs). |
| Step 6 |
continuity-check [interval cc-interval] Example: |
Configures the per-service parameters and sets the interval at which CCMs are transmitted. |
| Step 7 |
exit Example: |
Returns to Ethernet connectivity fault management configuration mode. |
| Step 8 |
ethernet cfm global Example: |
Enables CFM processing globally on the device. |
| Step 9 |
ethernet cfm traceroute cache Example: |
Enables caching of CFM data learned through traceroute messages. |
| Step 10 |
ethernet cfm traceroute cache size entries Example: |
Sets the maximum size for the CFM traceroute cache table. |
| Step 11 |
ethernet cfm traceroute cache hold-time minutes Example: |
Sets the amount of time that CFM traceroute cache entries are retained. |
| Step 12 |
interface type number Example: |
Specifies an interface and enters interface configuration mode. |
| Step 13 |
service instance id ethernet [evc-name] Example: |
Configures an Ethernet service instance on an interface and enters Ethernet service configuration mode. |
| Step 14 |
encapsulation encapsulation-type Example: |
Sets the encapsulation method used by the interface. |
| Step 15 |
bridge-domain bridge-id Example: |
Binds a service instance to a bridge domain instance. |
| Step 16 |
cfm mip level level Example: |
Creates a MIP and sets the maintenance level number. |
| Step 17 |
exit Example: |
Returns to interface configuration mode. |
| Step 18 |
exit Example: |
Returns to global configuration mode. |
| Step 19 |
snmp-server enable traps ethernet cfm cc [mep-up ] [mep-down ] [config ] [loop ] [cross-connect ] Example: |
Enables SNMP trap generation for Ethernet CFM mep-up, mep-down, config, loop, and cross-connect events. |
| Step 20 |
snmp-server enable traps ethernet cfm crosscheck [mep-unknown | mep-missing | service-up ] Example: |
Enables SNMP trap generation for Ethernet CFM mep-unknown, mep-missing, and service-up continuity check events in relation to the cross-check operation between statically configured MEPs and those learned via CCMs. |
| Step 21 |
end Example: |
Returns to privileged EXEC mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ethernet cfm domain domain-name level level-id Example: |
Defines a CFM maintenance domain at a particular maintenance level and enters Ethernet CFM configuration mode. |
| Step 4 |
service short-ma-name evc evc-name vlan vlanid direction down Example: |
Configures a maintenance association within a maintenance domain and enters Ethernet connectivity fault management (CFM) service configuration mode. |
| Step 5 |
continuity-check Example: |
Configures the transmission of continuity check messages (CCMs). |
| Step 6 |
continuity-check [interval cc-interval] Example: |
Configures the per-service parameters and sets the interval at which CCMs are transmitted. |
| Step 7 |
exit Example: |
Returns to Ethernet connectivity fault management configuration mode. |
| Step 8 |
mep archive-hold-time minutes Example: |
Sets the amount of time that data from a missing MEP is kept in the continuity check database or that entries are held in the error database before they are purged. |
| Step 9 |
exit Example: |
Returns to global configuration mode. |
| Step 10 |
ethernet cfm global Example: |
Enables CFM processing globally on the device. |
| Step 11 |
ethernet cfm traceroute cache Example: |
Enables caching of CFM data learned through traceroute messages. |
| Step 12 |
ethernet cfm traceroute cache size entries Example: |
Sets the maximum size for the CFM traceroute cache table. |
| Step 13 |
ethernet cfm traceroute cache hold-time minutes Example: |
Sets the amount of time that CFM traceroute cache entries are retained. |
| Step 14 |
snmp-server enable traps ethernet cfm cc [mep-up ] [mep-down ] [config ] [loop ] [cross-connect ] Example: |
Enables SNMP trap generation for Ethernet CFM mep-up, mep-down, config, loop, and cross-connect events. |
| Step 15 |
snmp-server enable traps ethernet cfm crosscheck [mep-unknown | mep-missing | service-up ] Example: |
Enables SNMP trap generation for Ethernet CFM mep-unknown, mep-missing, and service-up continuity check events in relation to the cross-check operation between statically configured MEPs and those learned via CCMs. |
| Step 16 |
end Example: |
Returns to privileged EXEC mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ethernet cfm domain domain-name level level-id Example: |
Defines a CFM maintenance domain at a particular maintenance level and enters Ethernet CFM configuration mode. |
| Step 4 |
service short-ma-name evc evc-name vlan vlanid direction down Example: |
Configures a maintenance association within a maintenance domain and enters Ethernet connectivity fault management (CFM) service configuration mode. |
| Step 5 |
continuity-check Example: |
Configures the transmission of continuity check messages (CCMs). |
| Step 6 |
continuity-check [interval cc-interval] Example: |
Configures the per-service parameters and sets the interval at which CCMs are transmitted. |
| Step 7 |
exit Example: |
Returns to Ethernet connectivity fault management configuration mode. |
| Step 8 |
mep archive-hold-time minutes Example: |
Sets the amount of time that data from a missing MEP is kept in the continuity check database or that entries are held in the error database before they are purged. |
| Step 9 |
exit Example: |
Returns to global configuration mode. |
| Step 10 |
ethernet cfm global Example: |
Enables CFM processing globally on the device. |
| Step 11 |
ethernet cfm traceroute cache Example: |
Enables caching of CFM data learned through traceroute messages. |
| Step 12 |
ethernet cfm traceroute cache size entries Example: |
Sets the maximum size for the CFM traceroute cache table. |
| Step 13 |
ethernet cfm traceroute cache hold-time minutes Example: |
Sets the amount of time that CFM traceroute cache entries are retained. |
| Step 14 |
interface type number Example: |
Specifies an interface and enters interface configuration mode. |
| Step 15 |
service instance id ethernet [evc-name] Example: |
Configures an Ethernet service instance on an interface and enters Ethernet service configuration mode. |
| Step 16 |
encapsulation encapsulation-type Example: |
Sets the encapsulation method used by the interface. |
| Step 17 |
bridge-domain bridge-id Example: |
Binds a service instance to a bridge domain instance. |
| Step 18 |
cfm mip level level Example: |
Creates a MIP and sets the maintenance level number. |
| Step 19 |
exit Example: |
Returns to interface configuration mode. |
| Step 20 |
exit Example: |
Returns to global configuration mode. |
| Step 21 |
snmp-server enable traps ethernet cfm cc [mep-up ] [mep-down ] [config ] [loop ] [cross-connect ] Example: |
Enables SNMP trap generation for Ethernet CFM mep-up, mep-down, config, loop, and cross-connect events. |
| Step 22 |
snmp-server enable traps ethernet cfm crosscheck [mep-unknown | mep-missing | service-up ] Example: |
Enables SNMP trap generation for Ethernet CFM mep-unknown, mep-missing, and service-up continuity check events in relation to the cross-check operation between statically configured MEPs and those learned via CCMs. |
| Step 23 |
end Example: |
Returns to privileged EXEC mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ethernet cfm domain domain-name level level-id Example: |
Defines a CFM maintenance domain at a particular maintenance level and enters Ethernet CFM configuration mode. |
| Step 4 |
service short-ma-name evc evc-name vlan vlanid direction down Example: |
Configures a maintenance association within a maintenance domain and enters Ethernet connectivity fault management (CFM) service configuration mode. |
| Step 5 |
continuity-check Example: |
Configures the transmission of continuity check messages (CCMs). |
| Step 6 |
continuity-check [interval cc-interval] Example: |
Configures the per-service parameters and sets the interval at which CCMs are transmitted. |
| Step 7 |
exit Example: |
Returns to Ethernet connectivity fault management configuration mode. |
| Step 8 |
mep archive-hold-time minutes Example: |
Sets the amount of time that data from a missing MEP is kept in the continuity check database or that entries are held in the error database before they are purged. |
| Step 9 |
exit Example: |
Returns to global configuration mode. |
| Step 10 |
ethernet cfm global Example: |
Enables CFM processing globally on the device. |
| Step 11 |
interface type number Example: |
Specifies an interface and enters interface configuration mode. |
| Step 12 |
service instance id ethernet [evc-name] Example: |
Configures an Ethernet service instance on an interface and enters Ethernet service configuration mode. |
| Step 13 |
encapsulation encapsulation-type Example: |
Sets the encapsulation method used by the interface. |
| Step 14 |
bridge-domain bridge-id Example: |
Binds a service instance to a bridge domain instance. |
| Step 15 |
cfm mip level level Example: |
Creates a MIP and sets the maintenance level number. |
| Step 16 |
end Example: |
Returns to privileged EXEC mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ethernet cfm domain domain-name level level-id Example: |
Defines a CFM maintenance domain at a particular maintenance level and enters Ethernet CFM configuration mode. |
| Step 4 |
service short-ma-name evc evc-name vlan vlanid direction down Example: |
Configures a maintenance association within a maintenance domain and enters Ethernet connectivity fault management (CFM) service configuration mode. |
| Step 5 |
continuity-check Example: |
Configures the transmission of continuity check messages (CCMs). |
| Step 6 |
continuity-check [interval cc-interval] Example: |
Configures the per-service parameters and sets the interval at which CCMs are transmitted. |
| Step 7 |
exit Example: |
Returns to Ethernet connectivity fault management configuration mode. |
| Step 8 |
mep archive-hold-time minutes Example: |
Sets the amount of time that data from a missing MEP is kept in the continuity check database or that entries are held in the error database before they are purged. |
| Step 9 |
exit Example: |
Returns to global configuration mode. |
| Step 10 |
ethernet cfm global Example: |
Enables CFM processing globally on the device. |
| Step 11 |
ethernet cfm traceroute cache Example: |
Enables caching of CFM data learned through traceroute messages. |
| Step 12 |
ethernet cfm traceroute cache size entries Example: |
Sets the maximum size for the CFM traceroute cache table. |
| Step 13 |
ethernet cfm traceroute cache hold-time minutes Example: |
Sets the amount of time that CFM traceroute cache entries are retained. |
| Step 14 |
interface type number Example: |
Specifies an interface and enters interface configuration mode. |
| Step 15 |
service instance id ethernet [evc-name] Example: |
Configures an Ethernet service instance on an interface and enters Ethernet service configuration mode. |
| Step 16 |
encapsulation encapsulation-type Example: |
Sets the encapsulation method used by the interface. |
| Step 17 |
bridge-domain bridge-id Example: |
Binds a service instance to a bridge domain instance. |
| Step 18 |
cfm mip level level Example: |
Creates a MIP and sets the maintenance level number. |
| Step 19 |
exit Example: |
Returns to interface configuration mode. |
| Step 20 |
exit Example: |
Returns to global configuration mode. |
| Step 21 |
snmp-server enable traps ethernet cfm cc [mep-up ] [mep-down ] [config ] [loop ] [cross-connect ] Example: |
Enables SNMP trap generation for Ethernet CFM mep-up, mep-down, config, loop, and cross-connect events. |
| Step 22 |
snmp-server enable traps ethernet cfm crosscheck [mep-unknown | mep-missing | service-up ] Example: |
Enables SNMP trap generation for Ethernet CFM mep-unknown, mep-missing, and service-up continuity check events in relation to the cross-check operation between statically configured MEPs and those learned via CCMs. |
| Step 23 |
end Example: |
Returns to privileged EXEC mode. |
Perform this task to set up service for Ethernet CFM. Optionally, when this task is completed, you may configure and enable the cross-check function. To perform this optional task, see “Configuring and Enabling Cross-Checking for an Inward Facing MEP on the U PE-A”.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ethernet cfm domain domain-name level level-id Example: |
Defines a CFM maintenance domain at a particular maintenance level and enters Ethernet CFM configuration mode. |
| Step 4 |
service short-ma-name evc evc-name vlan vlanid direction down Example: |
Configures a maintenance association within a maintenance domain and enters Ethernet connectivity fault management (CFM) service configuration mode. |
| Step 5 |
continuity-check Example: |
Configures the transmission of continuity check messages (CCMs). |
| Step 6 |
continuity-check [interval cc-interval] Example: |
Configures the per-service parameters and sets the interval at which CCMs are transmitted. |
| Step 7 |
exit Example: |
Returns to Ethernet connectivity fault management configuration mode. |
| Step 8 |
mep archive-hold-time minutes Example: |
Sets the amount of time that data from a missing MEP is kept in the continuity check database or that entries are held in the error database before they are purged. |
| Step 9 |
exit Example: |
Returns to global configuration mode. |
| Step 10 |
ethernet cfm global Example: |
Enables CFM processing globally on the device. |
| Step 11 |
ethernet cfm traceroute cache Example: |
Enables caching of CFM data learned through traceroute messages. |
| Step 12 |
ethernet cfm traceroute cache size entries Example: |
Sets the maximum size for the CFM traceroute cache table. |
| Step 13 |
ethernet cfm traceroute cache hold-time minutes Example: |
Sets the amount of time that CFM traceroute cache entries are retained. |
| Step 14 |
interface type number Example: |
Specifies an interface and enters interface configuration mode. |
| Step 15 |
service instance id ethernet [evc-name] Example: |
Configures an Ethernet service instance on an interface and enters Ethernet service configuration mode. |
| Step 16 |
encapsulation encapsulation-type Example: |
Sets the encapsulation method used by the interface. |
| Step 17 |
bridge-domain bridge-id Example: |
Binds a service instance to a bridge domain instance. |
| Step 18 |
cfm mep domain domain-name mpid id Example: |
Configures the MEP domain and the ID. |
| Step 19 |
end Example: |
Returns to privileged EXEC mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ethernet cfm domain domain-name level level-id Example: |
Defines a CFM maintenance domain at a particular maintenance level and enters Ethernet CFM configuration mode. |
| Step 4 |
service short-ma-name evc evc-name vlan vlanid direction down Example: |
Configures a maintenance association within a maintenance domain and enters Ethernet connectivity fault management (CFM) service configuration mode. |
| Step 5 |
continuity-check Example: |
Configures the transmission of continuity check messages (CCMs). |
| Step 6 |
continuity-check [interval cc-interval] Example: |
Configures the per-service parameters and sets the interval at which CCMs are transmitted. |
| Step 7 |
exit Example: |
Returns to Ethernet connectivity fault management configuration mode. |
| Step 8 |
mep archive-hold-time minutes Example: |
Sets the amount of time that data from a missing MEP is kept in the continuity check database or that entries are held in the error database before they are purged. |
| Step 9 |
exit Example: |
Returns to global configuration mode. |
| Step 10 |
ethernet cfm global Example: |
Enables CFM processing globally on the device. |
| Step 11 |
ethernet cfm traceroute cache Example: |
Enables caching of CFM data learned through traceroute messages. |
| Step 12 |
ethernet cfm traceroute cache size entries Example: |
Sets the maximum size for the CFM traceroute cache table. |
| Step 13 |
ethernet cfm traceroute cache hold-time minutes Example: |
Sets the amount of time that CFM traceroute cache entries are retained. |
| Step 14 |
interface type number Example: |
Specifies an interface and enters interface configuration mode. |
| Step 15 |
service instance id ethernet [evc-name] Example: |
Configures an Ethernet service instance on an interface and enters Ethernet service configuration mode. |
| Step 16 |
encapsulation encapsulation-type Example: |
Sets the encapsulation method used by the interface. |
| Step 17 |
bridge-domain bridge-id Example: |
Binds a service instance to a bridge domain instance. |
| Step 18 |
cfm mep domain domain-name mpid id Example: |
Configures the MEP domain and the ID. |
| Step 19 |
exit Example: |
Returns to interface configuration mode. |
| Step 20 |
exit Example: |
Returns to global configuration mode. |
| Step 21 |
interface type number Example: |
Specifies an interface and enters interface configuration mode. |
| Step 22 |
service instance id ethernet [evc-name] Example: |
Configures an Ethernet service instance on an interface and enters Ethernet service configuration mode. |
| Step 23 |
encapsulation encapsulation-type Example: |
Sets the encapsulation method used by the interface. |
| Step 24 |
bridge-domain bridge-id Example: |
Binds a service instance to a bridge domain instance. |
| Step 25 |
cfm mip level level Example: |
Creates a MIP and sets the maintenance level number. |
| Step 26 |
end Example: |
Returns to privileged EXEC mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ethernet cfm domain domain-name level level-id Example: |
Defines a CFM maintenance domain at a particular maintenance level and enters Ethernet CFM configuration mode. |
| Step 4 |
service short-ma-name evc evc-name vlan vlanid direction down Example: |
Configures a maintenance association within a maintenance domain and enters Ethernet connectivity fault management (CFM) service configuration mode. |
| Step 5 |
continuity-check Example: |
Configures the transmission of continuity check messages (CCMs). |
| Step 6 |
continuity-check [interval cc-interval] Example: |
Configures the per-service parameters and sets the interval at which CCMs are transmitted. |
| Step 7 |
exit Example: |
Returns to Ethernet connectivity fault management configuration mode. |
| Step 8 |
mep archive-hold-time minutes Example: |
Sets the amount of time that data from a missing MEP is kept in the continuity check database or that entries are held in the error database before they are purged. |
| Step 9 |
exit Example: |
Returns to global configuration mode. |
| Step 10 |
ethernet cfm global Example: |
Enables CFM processing globally on the device. |
| Step 11 |
interface type number Example: |
Specifies an interface and enters interface configuration mode. |
| Step 12 |
service instance id ethernet [evc-name] Example: |
Configures an Ethernet service instance on an interface and enters Ethernet service configuration mode. |
| Step 13 |
encapsulation encapsulation-type Example: |
Sets the encapsulation method used by the interface. |
| Step 14 |
bridge-domain bridge-id Example: |
Binds a service instance to a bridge domain instance. |
| Step 15 |
cfm mip level level Example: |
Creates a MIP and sets the maintenance level number. |
| Step 16 |
end Example: |
Returns to privileged EXEC mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ethernet cfm domain domain-name level level-id Example: |
Defines a CFM maintenance domain at a particular maintenance level and enters Ethernet CFM configuration mode. |
| Step 4 |
service short-ma-name evc evc-name vlan vlanid direction down Example: |
Configures a maintenance association within a maintenance domain and enters Ethernet connectivity fault management (CFM) service configuration mode. |
| Step 5 |
continuity-check Example: |
Configures the transmission of continuity check messages (CCMs). |
| Step 6 |
continuity-check [interval cc-interval] Example: |
Configures the per-service parameters and sets the interval at which CCMs are transmitted. |
| Step 7 |
exit Example: |
Returns to Ethernet connectivity fault management configuration mode. |
| Step 8 |
mep archive-hold-time minutes Example: |
Sets the amount of time that data from a missing MEP is kept in the continuity check database or that entries are held in the error database before they are purged. |
| Step 9 |
exit Example: |
Returns to global configuration mode. |
| Step 10 |
ethernet cfm global Example: |
Enables CFM processing globally on the device. |
| Step 11 |
ethernet cfm traceroute cache Example: |
Enables caching of CFM data learned through traceroute messages. |
| Step 12 |
ethernet cfm traceroute cache size entries Example: |
Sets the maximum size for the CFM traceroute cache table. |
| Step 13 |
ethernet cfm traceroute cache hold-time minutes Example: |
Sets the amount of time that CFM traceroute cache entries are retained. |
| Step 14 |
interface type number Example: |
Specifies an interface and enters interface configuration mode. |
| Step 15 |
service instance id ethernet [evc-name] Example: |
Configures an Ethernet service instance on an interface and enters Ethernet service configuration mode. |
| Step 16 |
encapsulation encapsulation-type Example: |
Sets the encapsulation method used by the interface. |
| Step 17 |
bridge-domain bridge-id Example: |
Binds a service instance to a bridge domain instance. |
| Step 18 |
cfm mip level level Example: |
Creates a MIP and sets the maintenance level number. |
| Step 19 |
exit Example: |
Returns to interface configuration mode. |
| Step 20 |
exit Example: |
Returns to global configuration mode. |
| Step 21 |
interface type number Example: |
Specifies an interface. |
| Step 22 |
service instance id ethernet [evc-name ] Example: |
Configures an Ethernet service instance on an interface and enters Ethernet service configuration mode. |
| Step 23 |
encapsulation encapsulation-type Example: |
Sets the encapsulation method used by the interface. |
| Step 24 |
bridge-domain bridge-id Example: |
Binds a service instance to a bridge domain instance. |
| Step 25 |
cfm mep domain domain-name mpid id Example: |
Configures the MEP domain and the ID. |
| Step 26 |
end Example: |
Returns to privileged EXEC mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ethernet cfm domain domain-name level level-id Example: |
Defines a CFM maintenance domain at a particular maintenance level and enters Ethernet CFM configuration mode. |
| Step 4 |
service short-ma-name evc evc-name vlan vlanid direction down Example: |
Configures a maintenance association within a maintenance domain and enters Ethernet connectivity fault management (CFM) service configuration mode. |
| Step 5 |
continuity-check Example: |
Configures the transmission of continuity check messages (CCMs). |
| Step 6 |
continuity-check [interval cc-interval] Example: |
Configures the per-service parameters and sets the interval at which CCMs are transmitted. |
| Step 7 |
exit Example: |
Returns to Ethernet connectivity fault management configuration mode. |
| Step 8 |
mep archive-hold-time minutes Example: |
Sets the amount of time that data from a missing MEP is kept in the continuity check database or that entries are held in the error database before they are purged. |
| Step 9 |
exit Example: |
Returns to global configuration mode. |
| Step 10 |
ethernet cfm global Example: |
Enables CFM processing globally on the device. |
| Step 11 |
ethernet cfm traceroute cache Example: |
Enables caching of CFM data learned through traceroute messages. |
| Step 12 |
ethernet cfm traceroute cache size entries Example: |
Sets the maximum size for the CFM traceroute cache table. |
| Step 13 |
ethernet cfm traceroute cache hold-time minutes Example: |
Sets the amount of time that CFM traceroute cache entries are retained. |
| Step 14 |
interface type number Example: |
Specifies an interface and enters interface configuration mode. |
| Step 15 |
service instance id ethernet [evc-name] Example: |
Configures an Ethernet service instance on an interface and enters Ethernet service configuration mode. |
| Step 16 |
encapsulation encapsulation-type Example: |
Sets the encapsulation method used by the interface. |
| Step 17 |
bridge-domain bridge-id Example: |
Binds a service instance to a bridge domain instance. |
| Step 18 |
cfm mep domain domain-name mpid id Example: |
Configures the MEP domain and the ID. |
| Step 19 |
end Example: |
Returns to privileged EXEC mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ethernet cfm domain domain-name level level-id Example: |
Defines a CFM maintenance domain at a particular maintenance level and enters Ethernet CFM configuration mode. |
| Step 4 |
service short-ma-name evc evc-name vlan vlanid direction down Example: |
Configures a maintenance association within a maintenance domain and enters Ethernet connectivity fault management (CFM) service configuration mode. |
| Step 5 |
continuity-check Example: |
Configures the transmission of continuity check messages (CCMs). |
| Step 6 |
continuity-check [interval cc-interval] Example: |
Configures the per-service parameters and sets the interval at which CCMs are transmitted. |
| Step 7 |
exit Example: |
Returns to Ethernet connectivity fault management configuration mode. |
| Step 8 |
mep archive-hold-time minutes Example: |
Sets the amount of time that data from a missing MEP is kept in the continuity check database or that entries are held in the error database before they are purged. |
| Step 9 |
exit Example: |
Returns to global configuration mode. |
| Step 10 |
ethernet cfm global Example: |
Enables CFM processing globally on the device. |