- Audience
- Getting Started with Cisco ME 2600X
- Ethernet Virtual Circuit
- Quality of Service
- Resilient Ethernet Protocol
- Link Aggregation Group and Link Aggregation Control Protocol
- MAC Learning
- Multicast VLAN Registration
- IGMP Snooping
- Remote Network Monitoring and Alarm Troubleshooting
- Authentication, Authorization, and Accounting (AAA)
- Cisco Discovery Protocol
- SNMP
- IP Source Guard for Service Instance
- DHCP Snooping
- Dynamic ARP Inspection
- MAC Address Security
- Layer 2 Access Control Lists on EVCs
- Layer 3 Access Control Lists on EVCs
- Storm Control over EVC
- Control Plane Policing
- ICMP Unreachable Rate Limiting User Feedback
- IP Version 6 Support for the Management Port
- SSH
- PPPoE Intermediate Agent
- CFM over EVC
- Index
Cisco ME 2600X Series Ethernet Access Switch Software Configuration Guide
- Updated:
- September 3, 2014
Chapter: CFM over EVC
- Enabling or Disabling CFM Globally
- Enabling or Disabling CFM on an Interface
- Enabling Caching of CFM Data
- Creating a Maintenance Domain
- Creating a Maintenance Association
- Configuring CFM Encapsulation
- Creating a Port MEP
- Creating an MEP for an EFP
- Defining MEPs Statically within a Maintenance Association
- Specifying the Number of MEPs in a Maintenance Association
- Creating an MIP Dynamically
- Configuring an MIP on a Service Instance in CFM Manually
- Enabling the Transmission of Continuity Check Messages
- Sending CFM Loopback and Linktrace Messages
CFM over EVC
This chapter describes CFM and procedures to configure CFM.
- CFM over EVC
- Restrictions for CFM
- Information About CFM
- How to Configure CFM
- Configuration Examples for CFM
- Verifying the CFM Configuration
- Additional References for CFM
CFM over EVC
Ethernet Connectivity Fault Management (CFM) is an end-to-end per-service 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.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see the Bug Toolkit and release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
Use the Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Restrictions for CFM
- CFM over the point–to–point bridge domain is not supported.
- CFM over Virtual Private LAN Service (VPLS) is not supported.
- Depending on the Continuity Check (CC) interval, more than 16000 Maintenance End Points (MEPs) are not supported.
- More than 16000 Maintenance Intermediate Points (MIPs) are not supported.
- CFM alarms is not supported.
- CFM over VLAN based forwarding is not supported.
- CFM is not supported on a bridge domain that has the split horizon configured.
- CFM handles blocked ports only for tagged packets as REP operates only on tagged packets.
The following table specifies the number of supported remote and local MEPs depending on the configured CC interval.
|
CC Interval |
Number of Remote MEPS |
Number of Local MEPs |
| 100 milliseconds | 100 | 100 |
| 1 second | 1000 | 1000 |
| 10 seconds | 8000 | 8000 |
| 1 minute | 16000 | 16000 |
| 10 minutes | 16000 | 16000 |
Information About CFM
IEEE CFM is an end-to-end per-service Ethernet layer OAM protocol that supports provider edge-to-provider edge (PE-to-PE) and customer edge-to-customer edge (CE-to-CE) services. A service is identified as an Ethernet virtual circuit (EVC) service.
Benefits of IEEE CFM
Maintenance Domain
A maintenance domain is an administrative domain for managing and administering a network. The maintenance domain allows CFM to support multiple independent operators, each supporting service instances from multiple independent customers.
A unique maintenance level in the range of 0 to 7 is assigned to each maintenance domain by a network administrator. Maintenance 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 higher the domain level, the broader the scope of the domain. 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 in between these domains, varying in size. All levels of the hierarchy must operate together.
Domains must 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 that is a superset of the operator domains. Furthermore, the customer has its own end-to-end domain, which is in turn is a superset of the service provider domain. Maintenance levels of various nesting domains must be communicated among the administering organizations. For example, one approach would be to have the service provider assign maintenance levels to operators.
- Maintenance domains are identified by a unique domain name that can be up to 154 characters.
- The domain name as null is supported; the maintenance association name is used as the identifier.
- Domain configuration is not required for devices that have only Maintenance Intermediate Points (MIPs).
- Mix of Up (toward the bridge) and Down (toward the wire) Maintenance Association End Points (MEPs)is supported.
A domain can be removed when all the maintenance points within the domain have been removed and all the remote MEPs entries in the continuity check database (CCDB) for the domain have been purged.
The following figure illustrates a hierarchy of operator, service provider, and customer domains and also illustrates touching, intersecting, and nested domains.
Maintenance Association
There can be any number of maintenance associations (MA) within a maintenance domain. A maintenance association identifies a service that can be uniquely identified within the maintenance domains. The CFM protocol runs within a specific maintenance association.
The MA direction is specified when the MA is configured. The MA name must be configured on a domain before MEPs can be configured. Configuring an MA is not required for devices that have only MIPs.
Maintenance Point
Any port of a bridge is referred to as a Maintenance Point. A maintenance point is a demarcation point on an interface or port that participates in CFM within a maintenance domain. Maintenance points must be explicitly configured on Cisco devices.
Maintenance End Points
MEPs reside at the edge of a maintenance domain and are active elements of CFM. They confine CFM messages within the domain through the maintenance domain level. MEPs periodically transmit and receive continuity check messages (CCMs) from other MEPs within the domain. MEPs also transmit linktrace and loopback messages at the request of the administrator.
MEP ID uniquely identifies each MEP along with those configured on a single MA. The MEP IDs range from 1 to 8191.
MEP supports multicast loopbacks and pings. When a multicast ping is initiated for a particular domain or service, all the related remote MEPs reply to the ping.
MEP configurations can be removed after all pending loopback and linktrace replies are removed and the service on the interface is set to transparent mode. To set the service to transparent mode, MIP filtering must not be configured.
Up MEPs
An Up MEP is an MEP that resides in a bridge and transmits to and receives CFM messages from the direction of the bridge relay entity.
- Sends and receives CFM frames at its level through the bridge relay and not through 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 bridge.
- Drops all CFM frames at a lower level coming from the direction of the bridge.
- Forwards all CFM frames transparently at a higher level, independent of whether they came in from the bridge or wire.
Down MEPs
A Down MEP is an MEP that resides in a bridge and transmits to and receives CFM messages from the direction of the wire.
- Sends and receives CFM frames at its level through 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 bridge.
- 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.
- Forwards all CFM frames transparently at a higher level, independent of whether they came in from the bridge or wire.
Port MEPs
Cisco ME 2600X also supports Port MEP at the physical port. A port MEP can be created either on the physical port or on the port of a channel group. The port MEP takes higher precedence if both the port MEP and the Down MEP on untagged EFP is created on the same port.
Maintenance Intermediate Points
Maintenance intermediate points (MIPs) are internal to the maintenance domain and are passive elements of CFM. They store information received from MEPs and other MIPs and respond only to CFM linktrace and loopback messages. An MIP has only one level associated with it. MIPs forward CFM messages within a maintenance domain.
- Can be created manually or dynamically (auto MIPs).
- Dynamically created depending on configured policies at managed objects (MA, maintenance domain, or the default domain level).
- Manual MIPs can be created under a service instance within an interface.
- Auto MIP commands can be issued globally or under a domain or service.
- Can be created per MA, which means that an MIP in the MA can be lower level than an MEP in another MA.
- CFM frames received from MEPs and other MIPs are cataloged and forwarded, using both the wire and the bridge relay.
- When MIP filtering is enabled, all CFM frames at a lower level are stopped and dropped, independent of whether they originate from the wire or the bridge relay.
- All CFM frames at a higher level are forwarded, independent of whether they arrive from the wire or from the bridge relay.
- Passive points respond only when triggered by CFM linktrace and loopback messages.
The following figure illustrates MEPs and MIPs at the operator, service provider, and customer levels.
CFM Messages
CFM uses standard Ethernet frames that can be distinguished by their EtherType and for multicast messages by their MAC address. CFM frames are sourced, terminated, processed, and relayed by bridges.
Continuity Check Messages
CFM continuity check messages (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.
- Transmitted at a periodic interval by MEPs. The interval can be one of the following configurable values. The default is 10 seconds.
- Cataloged by MIPs at the same maintenance level.
- Terminated by remote MEPs at the same maintenance level.
- Unidirectional and do not solicit a response.
- Indicate the status of the bridge port on which the MEP is configured.
Loopback Messages
CFM loopback messages (LBMs) are unicast frames that an MEP transmits, at the request of an administrator, to verify connectivity to a specific maintenance point. A loopback message reply (LBR) 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.
Since LBMs are unicast messages, they are forwarded like normal data frames except with the maintenance level restriction. If the outgoing port is known in the forwarding database of the bridge and allows CFM frames at the maintenance level of the image to pass through, the frame is sent out on that port. If the outgoing port is unknown, the message is broadcast on all the ports in that domain.
A CFM LBM can be generated on demand using the CLI. The source of a loopback message must be an MEP; the destination may be an MEP or MIP. Both CFM LBMs and LBRs are unicast. CFM LBMs specify the destination MAC address or MPID, VLAN, and maintenance domain.
Linktrace Messages
CFM linktrace messages (LTMs) are multicast frames that an MEP transmits, at the request of an administrator, to track the path (hop-by-hop) to a destination MEP. They are similar to Layer 3 traceroute messages. LTMs 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. LTMs are intercepted by maintenance points along the path and processed, transmitted, or dropped. At each hop where there is a maintenance point at the same level, a linktrace message reply (LTR) is transmitted back to the originating MEP. For each visible MIP, linktrace messages indicate ingress action, relay action, and egress action. LTMs are multicast and LTRs are unicast.
How to Configure CFM
The following tasks describe how to configure CFM on the Cisco ME 2600X device:
- Enabling or Disabling CFM Globally
- Enabling or Disabling CFM on an Interface
- Enabling Caching of CFM Data
- Creating a Maintenance Domain
- Creating a Maintenance Association
- Configuring CFM Encapsulation
- Creating a Port MEP
- Creating an MEP for an EFP
- Defining MEPs Statically within a Maintenance Association
- Specifying the Number of MEPs in a Maintenance Association
- Creating an MIP Dynamically
- Configuring an MIP on a Service Instance in CFM Manually
- Enabling the Transmission of Continuity Check Messages
- Sending CFM Loopback and Linktrace Messages
Enabling or Disabling CFM Globally
To enable or disable CFM globally, complete the following steps:
1.
enable
2.
configure terminal
3.
ethernet cfm global
4.
end
DETAILED STEPS
Enabling or Disabling CFM on an Interface
To enable or disable CFM on an interface, complete the following steps:
1.
enable
2.
configure terminal
3.
interface
type
4.
ethernet cfm interface
5.
end
DETAILED STEPS
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 | enable
Example: Switch> enable
|
Enables privileged EXEC mode. | ||
| Step 2 | configure terminal
Example: Switch# configure terminal
|
Enters global configuration mode. | ||
| Step 3 | interface
type
Example: Switch(config)# interface GigabitEthernet 1/1
|
Enters global configuration mode. | ||
| Step 4 | ethernet cfm interface
Example: Switch(config-if)# ethernet cfm interface
|
Enables the Ethernet CFM processing on the interface.
| ||
| Step 5 | end
Example: Switch(config-if)# end
|
Returns to privileged EXEC mode. |
Enabling Caching of CFM Data
To enable caching of CFM data, complete the following steps:
1.
enable
2.
configure terminal
3.
ethernet cfm traceroute cache
4.
ethernet cfm traceroute cache size
entries
5.
ethernet cfm traceroute cache hold-time
minutes
6.
end
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | enable
Example: Switch> enable
|
Enables privileged EXEC mode. |
| Step 2 | configure terminal
Example: Switch# configure terminal
|
Enters global configuration mode. |
| Step 3 | ethernet cfm traceroute cache
Example: Switch(config)# ethernet cfm traceroute cache
|
Enables caching of CFM data learned through traceroute messages. |
| Step 4 | ethernet cfm traceroute cache size
entries
Example: Switch(config)# ethernet cfm traceroute cache size 200
|
Sets the size for the CFM traceroute cache table. The default value is 100 entries. The range is from 1 to 4095 entries. |
| Step 5 | ethernet cfm traceroute cache hold-time
minutes
Example: Switch(config)# ethernet cfm traceroute cache holdtime 60
|
Sets the amount of time (in minutes) that CFM traceroute cache entries are retained. The hold-time default value is 100 minutes. The range is from Example: 1 to 65535 minutes. |
| Step 6 | end
Example: Switch(config)# end
|
Returns to privileged EXEC mode. |
Creating a Maintenance Domain
To create a maintenance domain, complete the following steps:
1.
enable
2.
configure terminal
3.
ethernet cfm domain
domain-name
level
level-id
4.
end
DETAILED STEPS
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 | enable
Example: Switch> enable
|
Enables privileged EXEC mode. | ||
| Step 2 | configure terminal
Example: Switch# configure terminal
|
Enters global configuration mode. | ||
| Step 3 | ethernet cfm domain
domain-name
level
level-id
Example: Switch(config)# ethernet cfm domain customer level 7
|
Creates a CFM maintenance domain at a specific maintenance level and enters Ethernet CFM configuration mode. The range of the maintenance domain level is from 0 to 7.
| ||
| Step 4 | end
Example: Switch(config)# end
|
Returns to privileged EXEC mode. |
Creating a Maintenance Association
To create a maintenance association, complete the following steps:
1.
enable
2.
configure terminal
3.
ethernet cfm domain
domain-name
level
level-id
4.
service {ma-name
|
number
ma-name} {evc
evc-name
|
port} [
direction down]
5.
end
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | enable
Example: Switch> enable
|
Enables privileged EXEC mode. |
| Step 2 | configure terminal
Example: Switch# configure terminal
|
Enters global configuration mode. |
| Step 3 | ethernet cfm domain
domain-name
level
level-id
Example: Switch(config)# ethernet cfm domain Customer level 7
|
Creates a maintenance domain at a specified level and enters Ethernet CFM configuration mode. |
| Step 4 | service {ma-name
|
number
ma-name} {evc
evc-name
|
port} [
direction down]
Example: Switch(config-ecfm)# service Customer1 port
|
Creates a maintenance association within a maintenance domain and enters CFM service configuration mode. |
| Step 5 | end
Example: Switch(config-ecfm)# end
|
Returns to privileged EXEC mode. |
Configuring CFM Encapsulation
To configure CFM encapsulation, complete the following steps:
1.
enable
2.
configure terminal
3.
interface
type
4.
service instance
id
ethernet [evc-id]
5.
encapsulation dot1q
{any
|
vlan-id [vlan-id [-vlan-id]]}
second-dot1q {any
|
vlan-id [vlan-id [-vlan-id]]}
6.
bridge-domain
bridge-id [split-horizon]
7.
cfm encapsulation dot1q
{dot1ad
vlan-id
|
dot1q
vlan-id} [dot1q
vlan-id |
second-dot1q
vlan-id]
8.
end
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | enable
Example: Switch> enable
|
Enables privileged EXEC mode. |
| Step 2 | configure terminal
Example: Switch# configure terminal
|
Enters global configuration mode. |
| Step 3 | interface
type
Example: Switch(config)# interface GigabitEthernet 1/1
|
Enters global configuration mode. |
| Step 4 | service instance
id
ethernet [evc-id]
Example: Switch(config-if)# service instance 101 ethernet
|
Configures an Ethernet service instance on an interface and enters service instance configuration mode. |
| Step 5 | encapsulation dot1q
{any
|
vlan-id [vlan-id [-vlan-id]]}
second-dot1q {any
|
vlan-id [vlan-id [-vlan-id]]}
Example: Switch(config-if-srv)# encapsulation dot1q 100-110 second-dot1q 200
|
Defines the matching criteria that maps the ingress dot1q, QinQ, or untagged frames on an interface to the appropriate service instance. |
| Step 6 | bridge-domain
bridge-id [split-horizon]
Example: Switch(config-if-srv)# bridge-domain 12
|
Binds the Ethernet service instance to a bridge domain instance where bridge-id is the identifier for the bridge domain instance. |
| Step 7 | cfm encapsulation dot1q
{dot1ad
vlan-id
|
dot1q
vlan-id} [dot1q
vlan-id |
second-dot1q
vlan-id]
Example: Switch(config-if-srv)# cfm encapsulation dot1q 105 second dot1q 200
|
Defines the matching criteria that maps the ingress dot1q, QinQ, or untagged frames on an interface to the appropriate service instance. |
| Step 8 | end
Example: Switch(config-if-srv)# end
|
Returns to privileged EXEC mode. |
Creating a Port MEP
To create a port MEP, complete the following steps:
1.
enable
2.
configure terminal
3.
interface
type
4.
ethernet cfm mep domain
domain-name
mpid
mpid {port}
5.
end
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | enable
Example: Switch> enable
|
Enables privileged EXEC mode. |
| Step 2 | configure terminal
Example: Switch# configure terminal
|
Enters global configuration mode. |
| Step 3 | interface
type
Example: Switch(config)# interface GigabitEthernet 1/1
|
Enters global configuration mode. |
| Step 4 | ethernet cfm mep domain
domain-name
mpid
mpid {port}
Example: Switch(config-if)# ethernet cfm mep domain Customer mpid 701 port
|
Sets a port as internal to a maintenance domain and creates a port MEP. A port MEP can be created only on a physical port or on a port of a channel group. |
| Step 5 | end
Example: Switch(config-if)# end
|
Returns to privileged EXEC mode. |
Creating an MEP for an EFP
To create an MEP for an EFP, complete the following steps:
1.
enable
2.
configure terminal
3.
interface
type
4.
service instance
id
ethernet [evc-id]
5.
encapsulation dot1q
{any
|
vlan-id [vlan-id [-vlan-id]]}
second-dot1q {any
|
vlan-id [vlan-id [-vlan-id]]}
6.
bridge-domain
bridge-id [split-horizon]
7.
cfm mep domain
domain-name
mpid
mpid-value
8.
end
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | enable
Example: Switch> enable
|
Enables privileged EXEC mode. |
| Step 2 | configure terminal
Example: Switch# configure terminal
|
Enters global configuration mode. |
| Step 3 | interface
type
Example: Switch(config)# interface GigabitEthernet 1/1
|
Enters global configuration mode. |
| Step 4 | service instance
id
ethernet [evc-id]
Example: Switch(config-if)# service instance 101 ethernet
|
Configures an Ethernet service instance on an interface and enters service instance configuration mode. |
| Step 5 | encapsulation dot1q
{any
|
vlan-id [vlan-id [-vlan-id]]}
second-dot1q {any
|
vlan-id [vlan-id [-vlan-id]]}
Example: Switch(config-if-srv)# encapsulation dot1q 100 second-dot1q 200
|
Defines the matching criteria that maps the ingress dot1q, QinQ, or untagged frames on an interface to the appropriate service instance. |
| Step 6 | bridge-domain
bridge-id [split-horizon]
Example: Switch(config-if-srv)# bridge-domain 12
|
Binds the Ethernet service instance to a bridge domain instance where bridge-id is the identifier for the bridge domain instance. |
| Step 7 | cfm mep domain
domain-name
mpid
mpid-value
Example: Switch(config-if-srv)# cfm mep domain Customer mpid 701
|
Creates an MEP under the Ethernet service instance. |
| Step 8 | end
Example: Switch(config-if-srv)# end
|
Returns to privileged EXEC mode. |
Defining MEPs Statically within a Maintenance Association
To define MEPs statically within a maintenance association, complete the following steps:
1.
enable
2.
configure terminal
3.
ethernet cfm domain
domain-name
level
level-id
4.
service {ma-name
|
number
ma-num} {evc
evc-name
|
port }
[direction
down]
5.
mep
mpid
mpid
6.
end
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | enable
Example: Switch> enable
|
Enables privileged EXEC mode. |
| Step 2 | configure terminal
Example: Switch# configure terminal
|
Enters global configuration mode. |
| Step 3 | ethernet cfm domain
domain-name
level
level-id
Example: Switch(config)# ethernet cfm domain customer level 7
|
Creates a CFM maintenance domain at a specific maintenance level and enters Ethernet CFM configuration mode. The range of the maintenance domain level is from 0 to 7. |
| Step 4 | service {ma-name
|
number
ma-num} {evc
evc-name
|
port }
[direction
down]
Example: Switch(config-ecfm)# service Customer1 port
|
Configures a maintenance association within a maintenance domain for a port MEP or MEP for an EFP and enters CFM service configuration mode. |
| Step 5 | mep
mpid
mpid
Example: Switch(config-ecfm-srv)# mep mpid 702
|
Statically defines the MEPs within a maintenance association. |
| Step 6 | end
Example: Switch(config-ecfm-srv)# end
|
Returns to privileged EXEC mode. |
Specifying the Number of MEPs in a Maintenance Association
To specify the number of MEPs in a maintenance association, complete the following steps:
1.
enable
2.
configure terminal
3.
ethernet cfm domain
domain-name
level
level-id
4.
service {ma-name
|
number
ma-num} {evc
evc-name
|
port }
[direction
down]
5.
maximum
meps
max-num
6.
end
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | enable
Example: Switch> enable
|
Enables privileged EXEC mode. |
| Step 2 | configure terminal
Example: Switch# configure terminal
|
Enters global configuration mode. |
| Step 3 | ethernet cfm domain
domain-name
level
level-id
Example: Switch(config)# ethernet cfm domain customer level 7
|
Creates a CFM maintenance domain at a specific maintenance level and enters Ethernet CFM configuration mode. The range of the maintenance domain level is from 0 to 7. |
| Step 4 | service {ma-name
|
number
ma-num} {evc
evc-name
|
port }
[direction
down]
Example: Switch(config-ecfm)# service Customer1 port
|
Configures a maintenance association within a maintenance domain for a port MEP or MEP for an EFP and enters CFM service configuration mode. |
| Step 5 | maximum
meps
max-num
Example: Switch(config-ecfm-srv)# maximum meps 50
|
Specifies the maximum number of MEPs in a maintenance association. The default is 100. The range is from 1 to 65535. |
| Step 6 | end
Example: Switch(config-ecfm-srv)# end
|
Returns to privileged EXEC mode. |
Creating an MIP Dynamically
 Note | ethernet cfm mip auto-create command has lower precedence than the ethernet cfm mip level manual MIP command. For example, if you manually configure an MIP for a particular maintenance association, that configuration overrides the MIP created by the global ethernet cfm mip auto-create command for that maintenance association. |
To create an MIP dynamically, complete the following steps:
1.
enable
2.
configure terminal
3.
ethernet cfm mip {auto-create level
level-id [lower-mep-only] [sender-id chassis] |
filter}
4.
end
DETAILED STEPS
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 | enable
Example: Switch> enable
|
Enables privileged EXEC mode. | ||
| Step 2 | configure terminal
Example: Switch# configure terminal
|
Enters global configuration mode. | ||
| Step 3 | ethernet cfm mip {auto-create level
level-id [lower-mep-only] [sender-id chassis] |
filter}
Example: Switch(config)# ethernet cfm mip auto-create level 1
|
Dynamically creates an MIP and provisions it globally at a specified maintenance level and enables level filtering.
| ||
| Step 4 | end
Example: Switch(config)# end
|
Returns to privileged EXEC mode. |
Configuring an MIP on a Service Instance in CFM Manually
Note | You cannot configure an MIP at a level lower than the level of already configured maintenance endpoints (MEPs) on an interface. Configuring an MIP using this command is known as a manual MIP and has precedence over the ethernet cfm mip auto-create command. |
To create an MIP manually, complete the following steps:
1.
enable
2.
configure terminal
3.
interface
type
4.
service instance
id
ethernet [evc-name]
5.
encapsulation dot1ad
vlan-id
dot1q
vlan-id
6.
bridge-domain
bridge-id
7.
cfm mip level
level-id
8.
end
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | enable
Example: Switch> enable
|
Enables privileged EXEC mode. |
| Step 2 | configure terminal
Example: Switch# configure terminal
|
Enters global configuration mode. |
| Step 3 | interface
type
Example: Switch(config)# interface GigabitEthernet 0/10
|
Specifies the interface to configure and enters interface configuration mode. |
| Step 4 | service instance
id
ethernet [evc-name]
Example: Switch(config-if)# service instance 1 ethernet evc1
|
|
| Step 5 | encapsulation dot1ad
vlan-id
dot1q
vlan-id
Example: Switch(config-if-srv)# encapsulation dot1ad 430 dot1q 431
|
|
| Step 6 | bridge-domain
bridge-id
Example: Switch(config-if-srv)# bridge-domain 340
|
|
| Step 7 | cfm mip level
level-id
Example: Switch(config-if-srv)# cfm mip level 7
|
|
| Step 8 | end
Example: Switch(config-if-srv)# end
|
Returns to privileged EXEC mode. |
Enabling the Transmission of Continuity Check Messages
To enable the transmission of continuity check messages, complete the following steps:
1.
enable
2.
configure terminal
3.
ethernet cfm domain
domain-name
level
level-id
4.
service {ma-name
|
number
ma-name} {evc
evc-name
|
port}
[
direction
down]
5.
continuity-check [interval
time |
loss-threshold
threshold |
static rmep]
6.
continuity-check [interval
time |
loss-threshold
threshold |
static rmep]
7.
continuity-check [interval
time |
loss-threshold
threshold |
static rmep]
8.
exit
9.
mep archive-hold-time
minutes
10.
end
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | enable
Example: Switch> enable
|
Enables privileged EXEC mode. |
| Step 2 | configure terminal
Example: Switch# configure terminal
|
Enters global configuration mode. |
| Step 3 | ethernet cfm domain
domain-name
level
level-id
Example: Switch(config)# ethernet cfm domain Customer level 7
|
Creates a maintenance domain at a specified level and enters Ethernet CFM configuration mode. |
| Step 4 | service {ma-name
|
number
ma-name} {evc
evc-name
|
port}
[
direction
down]
Example: Switch(config-ecfm)# service Customer1 port
|
Creates a maintenance association within a maintenance domain and enters CFM service configuration mode. |
| Step 5 | continuity-check [interval
time |
loss-threshold
threshold |
static rmep]
Example: Switch(config-ecfm-srv)# continuity-check
|
Enables the transmission of CCMs. |
| Step 6 | continuity-check [interval
time |
loss-threshold
threshold |
static rmep]
Example: Switch(config-ecfm-srv)# continuity-check interval 10s
|
Configures the time period between CCM transmissions. |
| Step 7 | continuity-check [interval
time |
loss-threshold
threshold |
static rmep]
Example: Switch(config-ecfm-srv)# continuity-check lossthreshold 10
|
Sets the number of CCMs that must be missed before declaring that a remote MEP is down. |
| Step 8 | exit
Example: Switch(config-ecfm-srv)# end
|
Returns to Ethernet CFM configuration mode. |
| Step 9 | mep archive-hold-time
minutes
Example: Switch(config-ecfm)# mep archive-hold-time 60
|
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. The default value is 100 minutes. The range is from 1 to 65535 minutes. |
| Step 10 | end
Example: Switch(config-ecfm)# end
|
Returns to privileged EXEC mode. |
Sending CFM Loopback and Linktrace Messages
To send CFM loopback and linktrace messages, complete the following steps:
1.
enable
2.
configure terminal
3.
ping ethernet {mpid
mpid
|
mac-address} {domain
domain-name} {port
|
evc
evc-name} [source
source-mpid] [cos
cos-value]
4.
traceroute ethernet {mpid
mpid
|
mac-address} {domain
domain-name} {port
|
evc
evc-name} [cos
cos-value] [fdb-only]
5.
end
DETAILED STEPS
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 | enable
Example: Switch> enable
|
Enables privileged EXEC mode. | ||
| Step 2 | configure terminal
Example: Switch# configure terminal
|
Enters global configuration mode. | ||
| Step 3 | ping ethernet {mpid
mpid
|
mac-address} {domain
domain-name} {port
|
evc
evc-name} [source
source-mpid] [cos
cos-value]
Example: Switch(config)# ping ethernet 1010.pcef.1010 level 2 evc evc5
|
Sends CFM loopback messages to the destination MEP through MAC address or MPID.
| ||
| Step 4 | traceroute ethernet {mpid
mpid
|
mac-address} {domain
domain-name} {port
|
evc
evc-name} [cos
cos-value] [fdb-only]
Example: Switch(config)# traceroute ethernet aabb.cc00.1010 level 4 evc evc_100
|
Sends CFM traceroute messages to the destination MEP through MAC address or MPID.
| ||
| Step 5 | end
Example: Switch(config)# end
|
Returns to privileged EXEC mode. |
Configuration Examples for CFM
Enabling or Disabling CFM Globally
The following example shows how to enable Ethernet Connectivity Fault Management (CFM):
Switch > enable Switch # configure terminal Switch(config) # ethernet cfm global
The following example shows how to disable CFM:
Switch > enable Switch # configure terminal Switch(config) # no ethernet cfm global
Enabling or Disabling CFM on an Interface
The following example shows how to enable CFM on an Interface:
Switch > enable Switch # configure terminal Switch(config) # interface GigabitEthernet 1/1 Switch(config-if) # ethernet cfm interface
The following example shows how to disable CFM on an Interface:
Switch > enable Switch # configure terminal Switch(config) # interface GigabitEthernet 1/1 Switch(config-if) # no ethernet cfm interface
Enabling Caching of CFM Data
The following example shows how to set the maximum number of entries in the CFM traceroute cache table to 2500:
Switch > enable Switch # configure terminal Switch(config) # ethernet cfm traceroute cache size 2500
The following example shows how to set the retention time for entries in the CFM traceroute cache table to 5 minutes:
Switch > enable Switch # configure terminal Switch(config) # ethernet cfm traceroute cache hold-time 5
Creating a Maintenance Domain
The following example shows how to define a domain named domain1 at level 6 and enters Ethernet CFM configuration mode:
Switch > enable Switch # configure terminal Switch(config) # ethernet cfm domain domain1 level 6
Creating a Maintenance Association
The following example shows how to create a maintenance association:
Switch > enable Switch # configure terminal Switch(config) # ethernet cfm domain operator level 5 Switch(config-ecfm) # service operatorA port Switch(config-ecfm) # exit
Creating a Port MEP
The following example shows how to set a port as internal to a maintenance domain and creates a port Maintenance End Points (MEP):
Switch > enable Switch # configure terminal Switch(config) # interface GigabitEthernet 4/1 Switch(config-if) # ethernet cfm mep domain CustomerB mpid 5 port
Creating an MEP for an EFP (Global)
The following example shows how to create an MEP for an Ethernet Flow Point (EFP) (global):
Switch > enable Switch # configure terminal Switch(config) # ethernet cfm global Switch(config) # ethernet cfm domain D7 level 7 Switch(config-ether-cfm) # service S1 evc evc1 Switch(config-ether-cfm) # continuity-check Switch(config-cfm-dmn-svc) # continuity-check interval 1m Switch(config-cfm-dmn-svc) # exit
Creating an MEP for an EFP (Interface)
The following example shows how to create an MEP for an EFP (interface):
Switch > enable Switch # configure terminal Switch(config) # interface GigabitEthernet 1/1 Switch(config-if) # service instance 1 ethernet evc1 Switch(config-if-srv) # service S1 evc evc1 Switch(config-if-srv) # encapsulation dot1ad 430 dot1q 431 Switch(config-if-srv) # bridge-domain 340 Switch(config-if-srv) # cfm mep domain D7 mpid 3400 Switch(config-if-srv) # exit
Defining the MEPs Statically within a Maintenance Association
The following example shows how to configure an MEP with an ID of 25:
Switch > enable Switch # configure terminal Switch(config) # ethernet cfm domain operator level 5 Switch(config-ecfm) # service operatorA port Switch(config-ecfm-srv) # mep mpid 25 Switch(config-ecfm-srv) # exit Switch(config-ecfm) # exit
Specifying the Number of MEPs in a Maintenance Association
The following example shows how to configure a maximum of 50 MEPs:
Switch > enable Switch # configure terminal Switch(config) # ethernet cfm domain operator level 5 Switch(config-ecfm) # service operatorA port Switch(config-ecfm-srv) # maximum meps 50 Switch(config-ecfm-srv) # exit Switch(config-ecfm) # exit
Creating an MIP Dynamically
The following example shows how to dynamically create a Maintenance Intermediate Point (MIP) at maintenance level 6:
Switch > enable Switch # configure terminal Switch(config) # ethernet cfm mip auto-create level 6
Configuring MIP on a Service Instance in CFM Manually
The following example shows how to manually configure MIP on a service instance in CFM:
Switch > enable Switch # configure terminal Switch(config) # interface GigabitEthernet 0/10 Switch(config-if) # service instance 1 ethernet evc1 Switch(config-if-srv) # encapsulation dot1ad 430 dot1q 431 Switch(config-if-srv) # bridge-domain 340 Switch(config-if-srv) # cfm mip level 7 Switch(config-if-srv) # end
Enabling the Transmission of Continuity Check Messages
The following example shows how to configure a loss threshold of 50 Continuity Check Messages (CCMs):
Switch > enable Switch # configure terminal Switch(config) # ethernet cfm domain operator level 5 Switch(config-ecfm) # service operatorA port Switch(config-ecfm-srv) # continuity-check loss-threshold 50 Switch(config-ecfm-srv) # exit Switch(config-ecfm) # exit
Sending CFM Loopback and Traceroute Messages
The following example shows how to send an Ethernet CFM loopback message to MAC address 1010.pcef.1010 on evc5:
Switch > enable Switch # ping ethernet 1010.pcef.1010 domain domain1 evc evc5
The following example shows how to send an Ethernet CFM traceroute message to MAC address aabb.cc00.1010 at maintenance level 4 on evc_100:
Switch > enable Switch # traceroute ethernet aabb.cc00.1010 domain domain1 evc evc_100
Verifying the CFM Configuration
CFM Platform Capabilities
Use the following command to display information about the CFM platform capabilities:
Switch# show ethernet cfm capabilities
Global CFM PD Capabilities: (0x001011F3) BD does not equal VLAN Value Flag Description ---------- -------------------- --------------------------------------------- 0x00000001 INWARD_MEP Up MEPs are supported 0x00000002 OUTWARD_MEP Down MEPs are supported 0x00000010 AIS AIS is supported 0x00000020 OOS LCK is supported 0x00000040 EVC EVC-based CFM config is permitted 0x00000080 PORTMEP Port MEPs are supported 0x00000100 DE DE bit is set in Loopback packets 0x00001000 XCONNECT CFM is supported on xconnects 0x00100000 HYBRID_MODE The router is running in hybrid mode, with active-active RPs
CFM Domain
Use the following command to display information about maintenance domain:
Switch# show ethernet cfm domain
Domain Name: D7 Level: 7 Total Services: 1 Services: Type Id Dir CC CC-int Static-rmep Crosscheck MaxMEP MA-Name BD 340 Up Y 1m Disabled Disabled 100 S1
CFM Maintenance-Points Local
Use the following command to display information about local CFM maintenance points that are configured on a device:
Switch# show ethernet cfm maintenance-points local
Local MEPs:
--------------------------------------------------------------------------------
MPID Domain Name Lvl MacAddress Type CC
Ofld Domain Id Dir Port Id
MA Name SrvcInst Source
EVC name
--------------------------------------------------------------------------------
3400 D7 7 0000.3148.3379 BD Y
No D7 Up Gi0/10 340
S1 1 Static
evc1
Total Local MEPs: 1
Local MIPs: None
CFM Maintenance-Points Remote
Use the following command to display information about about remote CFM maintenance endpoints (RMEPs) that are configured statically in the MEP list and their status in the continuity check database (CCDB):
Switch# show ethernet cfm maintenance-points remote
--------------------------------------------------------------------------------
MPID Domain Name MacAddress IfSt PtSt
Lvl Domain ID Ingress
RDI MA Name Type Id SrvcInst
EVC Name Age
Local MEP Info
--------------------------------------------------------------------------------
4300 D7 0000.3148.3377 Up Up
7 D7 Gi0/20
- S1 BD 340 1
evc1 58s
MPID: 3400 Domain: D7 MA: S1
Total Remote MEPs: 1
CFM MIP Database
Use the following command to display information about the contents of a MIP CCDB:
Switch# show ethernet cfm mpdb
* = Can Ping/Traceroute to MEP
--------------------------------------------------------------------------------
MPID Domain Name MacAddress Version
Lvl Domain ID Ingress
Expd MA Name Type Id SrvcInst
EVC Name Age
--------------------------------------------------------------------------------
4300* D7 0000.3148.3377 IEEE-CFM
7 D7 Gi0/20
- S1 BD 340 1
evc1 45s
Total Remote MEPs: 1
CFM Runtime
Use the following command to display available sub-options for CFM runtime:
Switch# show ethernet cfm runtime ?
lmep Local MEP specific runtime information ma-info MA queue info mcl-info MCL queue info smep Server MEP specific runtime information snmp SNMP DB specific runtime information
CFM Runtime Local MEPs
Use the following command to display information about CFM runtime for local MEPs:
Switch# show ethernet cfm runtime lmep
Local MEPs: ---------- MPID: 3400 DomainName: D7 MA Name: S1 Level: 7 Direction: Up EVC: evc1 Bridge Domain: 340 Service Instance: 1 Interface: Gi0/10 CC Offload: No CC-Status: Enabled CC Loss Threshold: 3 MAC: 0000.3148.3379 LCK-Status: Enabled LCK Period: 60000(ms) LCK Expiry Threshold: 3.5 Level to transmit LCK: Default Defect Condition: 0x0 Defect: EFD nfn: Not Sent lck_mep_timer: Stopped
CFM Runtime MA
Use the following command to display information about CFM runtime for maintenance association (MA):
Switch# show ethernet cfm runtime ma-info
Display Maintenance Association info:
IDB = GigabitEthernet0/10
BD=340: Up:7 7 Down:-1 -1 MCL:7 MIP:-1
CFM Runtime MCL
Use the following command to display information about maximum configured level (MCL) service for Up MEPs, Down MEPs, or a MIP. This value is kept per service, either VLAN or bridge domain.
Switch# show ethernet cfm runtime mcl-info
BD=340 MCL=7
Server MEP Specific Runtime Information
Use the following command to display information about server MEP specific runtime information for CFM:
Switch# show ethernet cfm runtime smep
SMEP Settings: -------------- Interface: GigabitEthernet0/5 LCK-Status: Enabled LCK Period: 60000 (ms) Level to transmit LCK: Default AIS-Status: Enabled AIS Period: 60000 (ms) Level to transmit AIS: Default Defect Condition: 0x1 LCK up timer: Stopped LCK down timer: Stopped AIS periodic timer: Running Interface: GigabitEthernet0/10 LCK-Status: Enabled LCK Period: 60000 (ms) Level to transmit LCK: Default AIS-Status: Enabled AIS Period: 60000 (ms) Level to transmit AIS: Default Defect Condition: 0x0
CFM SNMP
Use the following command to display information about Simple Network Management Protocol (SNMP) for CFM:
Switch# show ethernet cfm runtime snmp
SNMP Settings: CFM DB is in sync with CFM-SNMP DB CFM-SNMP DB is sync with CFM DB Stack :49154 MEP :3400
CFM SMEP
Use the following command to display the output contents of Ethernet CFM SMEP:
Switch# show ethernet cfm smep
SMEP Settings: -------------- Interface: GigabitEthernet0/5 LCK-Status: Enabled LCK Period: 60000 (ms) Level to transmit LCK: Default AIS-Status: Enabled AIS Period: 60000 (ms) Level to transmit AIS: Default Defect Condition: AIS Interface: GigabitEthernet0/10 LCK-Status: Enabled LCK Period: 60000 (ms) Level to transmit LCK: Default AIS-Status: Enabled AIS Period: 60000 (ms) Level to transmit AIS: Default Defect Condition: No Defect Interface: GigabitEthernet0/11 LCK-Status: Enabled LCK Period: 60000 (ms) Level to transmit LCK: Default AIS-Status: Enabled AIS Period: 60000 (ms) Level to transmit AIS: Default Defect Condition: AIS Interface: GigabitEthernet0/20 LCK-Status: Enabled LCK Period: 60000 (ms) Level to transmit LCK: Default AIS-Status: Enabled AIS Period: 60000 (ms) Level to transmit AIS: Default Defect Condition: No Defect
CFM Statistics
Use the following command to display CFM information:
Switch# show ethernet cfm statistics
BRAIN MAC: 0000.3148.3379
DomainName: D7
MA Name: S1
MPID: 3400
Last clearing of counters: never
CCMs:
Transmitted: 1133 Rcvd Seq Errors: 0
LTRs:
Unexpected Rcvd: 0
LBRs:
Transmitted: 5 Rcvd Seq Errors: 0
Rcvd in order: 5 Rcvd Bad MSDU: 0
CFM Traceroute-Cache
Note | You must enable traceroute cache globally before using this command. |
Use the following command to display information about the contents of the traceroute cache:
Switch# show ethernet cfm traceroute-cache
Current Cache-size: 5 Hops
Max Cache-size: 100 Hops
Hold-time: 100 Minutes
Traceroute to 0000.3148.3377 on Domain D7, Level 7, service S1, evc evc1 issued at *13:29:52.125 UTC Sat Mar 8 1902
path found via MPDB
B = Intermediary Bridge
! = Target Destination
* = Per hop Timeout
--------------------------------------------------------------------------------
MAC Ingress Ingr Action Relay Action
Hops Host Forwarded Egress Egr Action Previous Hop
--------------------------------------------------------------------------------
B 1 0000.3148.3379 Gi0/10 IngOk RlyMPDB
Forwarded
B 2 4044.444e.4000 RlyMPDB
Forwarded Gi0/25 EgrOK 0000.3148.3379
B 3 108c.cf17.2005 RlyMPDB
Forwarded Gi0/15 EgrOK 4044.444e.4000
B 4 2222.2222.2222 RlyMPDB
Forwarded Gi0/20 EgrOK 108c.cf17.2005
! 5 0000.3148.3377 RlyHit:MEP
Not Forwarded 2222.2222.2222
Additional References for CFM
The following sections provide references related to the CFM feature.
Related Documents
| Related Topic | Document Title |
|---|---|
|
Cisco IOS commands |
Standards
| Standard | Title |
|---|---|
|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
— |
MIBs
| MIB | MIBs link |
|---|---|
|
None. |
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFCs
| RFC | Title |
|---|---|
|
No new or modified RFCs are supported, and support for existing RFCs has not been modified. |
— |
Technical Assistance
| Description | Link |
|---|---|
|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
http://www.cisco.com/cisco/web/support/index.html |
Feedback