Page 1
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
First Published: 2016-08-12
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Page 2
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version
of the UNIX operating system. All rights reserved. Copyright©1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://
www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
©
2017 Cisco Systems, Inc. All rights reserved.
Page 3
CONTENTS
Preface
CHAPTER 1
CHAPTER 2
CHAPTER 3
Preface ix
Changes to This Document ix
Obtaining Documentation and Submitting a Service Request ix
New and Changed Feature Information 1
New and Changed Information 1
Preconfiguring Physical Interfaces 3
Physical Interface Preconfiguration Overview 3
Prerequisites for Preconfiguring Physical Interfaces 4
Benefits of Interface Preconfiguration 4
How to Preconfigure Physical Interfaces 4
Information About Preconfiguring Physical Interfaces 6
Use of the Interface Preconfigure Command 6
Advanced Configuration and Modification of the Management Ethernet Interface 9
CHAPTER 4
Prerequisites for Configuring Management Ethernet Interfaces 9
Performing Advanced Management Ethernet Interface Configuration 10
Configuring a Management Ethernet Interface 10
IPv6 Stateless Address Auto Configuration on Management Interface 12
Modifying the MAC Address for a Management Ethernet Interface 14
Verifying Management Ethernet Interface Configuration 15
Information About Configuring Management Ethernet Interfaces 16
Configuring Ethernet Interfaces 17
Configuring Gigabit Ethernet Interfaces 17
Information About Configuring Ethernet 21
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
iii
Page 4
Contents
Default Configuration Values for 100-Gigabit Ethernet 21
Ethernet MTU 21
CHAPTER 5
Configuring Ethernet OAM 23
Configuring Ethernet OAM 23
Information About Configuring Ethernet OAM 24
Ethernet Link OAM 24
Neighbor Discovery 24
Link Monitoring 25
MIB Retrieval 25
Miswiring Detection (Cisco-Proprietary) 25
SNMP Traps 25
Ethernet CFM 25
Maintenance Domains 26
Services 28
Maintenance Points 28
MIP Creation 28
MEP and CFM Processing Overview 29
CFM Protocol Messages 31
Continuity Check (IEEE 802.1ag and ITU-T Y.1731) 31
Loopback (IEEE 802.1ag and ITU-T Y.1731) 34
Linktrace (IEEE 802.1ag and ITU-T Y.1731) 34
Configurable Logging 36
Flexible VLAN Tagging for CFM 36
How to Configure Ethernet OAM 37
Configuring Ethernet Link OAM 37
Configuring an Ethernet OAM Profile 38
Attaching an Ethernet OAM Profile to an Interface 43
Configuring Ethernet OAM at an Interface and Overriding the Profile
Configuration 45
Verifying the Ethernet OAM Configuration 46
Configuring Ethernet CFM 47
Configuring a CFM Maintenance Domain 47
Configuring Services for a CFM Maintenance Domain 48
Enabling and Configuring Continuity Check for a CFM Service 50
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
iv
Page 5
Contents
Configuring Automatic MIP Creation for a CFM Service 52
Configuring Cross-Check on a MEP for a CFM Service 53
Configuring Other Options for a CFM Service 55
Configuring CFM MEPs 58
Configuring Y.1731 AIS 60
Configuring AIS in a CFM Domain Service 60
Configuring AIS on a CFM Interface 62
Configuring Flexible VLAN Tagging for CFM 63
Verifying the CFM Configuration 64
Troubleshooting Tips 65
Configuration Examples for Ethernet OAM 66
Configuration Examples for EOAM Interfaces 66
Configuring an Ethernet OAM Profile Globally: Example 66
Configuring Ethernet OAM Features on an Individual Interface: Example 67
Configuring Ethernet OAM Features to Override the Profile on an Individual Interface:
Example 67
Clearing Ethernet OAM Statistics on an Interface: Example 68
Enabling SNMP Server Traps on a Router: Example 68
Configuration Examples for Ethernet CFM 68
Ethernet CFM Domain Configuration: Example 68
Ethernet CFM Service Configuration: Example 68
Flexible Tagging for an Ethernet CFM Service Configuration: Example 69
Continuity Check for an Ethernet CFM Service Configuration: Example 69
MIP Creation for an Ethernet CFM Service Configuration: Example 69
Cross-check for an Ethernet CFM Service Configuration: Example 69
Other Ethernet CFM Service Parameter Configuration: Example 69
MEP Configuration: Example 69
Ethernet CFM Show Command: Examples 70
AIS for CFM Configuration: Examples 72
CHAPTER 6
AIS for CFM Show Commands: Examples 73
show ethernet cfm interfaces ais Command: Example 73
show ethernet cfm local meps Command: Examples 74
show ethernet cfm local meps detail Command: Example 75
Integrated Routing and Bridging 77
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
v
Page 6
Contents
Bridge-Group Virtual Interface 78
Supported Features on a BVI 78
BVI Interface and Line Protocol States 78
Prerequisites for Configuring IRB 79
Restrictions for Configuring IRB 79
How to Configure IRB 80
Configuring the Bridge Group Virtual Interface 80
Configuration Guidelines 80
Configuring the Layer 2 AC Interfaces 82
Configuring a Bridge Group and Assigning Interfaces to a Bridge Domain 83
Associating the BVI as the Routed Interface on a Bridge Domain 85
Displaying Information About a BVI 86
Additional Information on IRB 87
CHAPTER 7
Packet Flows Using IRB 87
Packet Flows When Host A Sends to Host B on the Bridge Domain 88
Packet Flows When Host A Sends to Host C From the Bridge Domain to a Routed
Interface 88
Packet Flows When Host C Sends to Host B From a Routed Interface to the Bridge
Domain 88
Configuration Examples for IRB 89
Basic IRB Configuration: Example 89
IPv4 Addressing on a BVI Supporting Multiple IP Networks: Example 89
IRB With BVI and VRRP Configuration: Example 89
Configuring Link Bundling 91
Features and Compatible Characteristics of Ethernet Link Bundles 92
Configuring Ethernet Link Bundles 93
Configuring LACP Fallback 97
Configuring EFP Load Balancing on an Ethernet Link Bundle 98
VLANs on an Ethernet Link Bundle 100
Configuring VLAN over Bundles 101
102
LACP Short Period Time Intervals 105
Configuring the Default LACP Short Period Time Interval 106
Configuring Custom LACP Short Period Time Intervals 108
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
vi
Page 7
Contents
Configuring VPWS Cross-Connects in MC-LAG 114
Configuring VPLS in MC-LAG 116
Information About Configuring Link Bundling 119
IEEE 802.3ad Standard 119
Link Bundle Configuration Overview 120
Link Switchover 120
LACP Fallback 120
Failure Cases 121
CHAPTER 8
Configuring Traffic Mirroring 123
Introduction to Traffic Mirroring 123
Traffic Mirroring Types 124
Restrictions 124
How to Configure Traffic Mirroring 125
Configuring Remote Traffic Mirroring 125
Attaching the Configurable Source Interface 127
Configuring UDF-Based ACL for Traffic Mirroring 129
Additional Information on Traffic Mirroring 131
Traffic Mirroring Terminology 131
Characteristics of the Source Port 131
Characteristics of the Monitor Session 132
Characteristics of the Destination Port 133
Traffic Mirroring Configuration Examples 133
Traffic Mirroring with Physical Interfaces (Local): Example 133
Viewing Monitor Session Status: Example 134
CHAPTER 9
Troubleshooting Traffic Mirroring 135
Verifying UDF-based ACL 137
Configuring Virtual Loopback and Null Interfaces 139
Information About Configuring Virtual Interfaces 139
Virtual Loopback Interface Overview 139
Prerequisites for Configuring Virtual Interfaces 140
Configuring Virtual Loopback Interfaces 140
Null Interface Overview 142
Configuring Null Interfaces 142
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
vii
Page 8
Contents
Configuring Virtual IPv4 Interfaces 144
CHAPTER 10
CHAPTER 11
Configuring 802.1Q VLAN Interfaces 147
How to Configure 802.1Q VLAN Interfaces 147
Configuring 802.1Q VLAN Subinterfaces 148
Verification 150
Configuring an Attachment Circuit on a VLAN 150
Removing an 802.1Q VLAN Subinterface 152
Information About Configuring 802.1Q VLAN Interfaces 153
Subinterfaces 153
Subinterface MTU 154
EFPs 154
Layer 2 VPN on VLANs 154
Configuring GRE Tunnels 155
Configuring GRE Tunnels 155
IP-in-IP De-capsulation 156
viii
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
Page 9
Preface
The Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers provides
information and procedures related to router interface and hardware configuration.
The preface contains the following sections:
Changes to This Document, page ix
•
Obtaining Documentation and Submitting a Service Request, page ix
•
Changes to This Document
This table lists the technical changes made to this document since it was first released.
Table 1: Changes to This Document
SummaryDate
Added ERSPAN and LACP Fallback features.May 2017
February 2017
Added IP-in-IP De-capsulation feature for Release
6.1.3
Initial release of this document.November 2016
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information,
see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco
technical documentation, at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical
documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The
RSS feeds are a free service.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
ix
Page 10
Obtaining Documentation and Submitting a Service Request
Preface
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
x
Page 11
New and Changed Feature Information
This table summarizes the new and changed feature information for the Interface and Hardware Component
Configuration Guide for Cisco NCS 5500 Series Routers , and tells you where they are documented.
New and Changed Information, page 1
•
New and Changed Information
Table 2: New and Changed Features
CHAPTER 1
Where DocumentedChanged in ReleaseDescriptionFeature
Release 6.1.3This feature was introduced.Integrated Routing and Bridging
Release 6.1.31This feature was introduced.ERSPAN
Release 6.1.31This feature was introduced.LACP Fallback
Configuring Integrated and
Bridging chapter
Configuring Traffic Monitoring
chapter
Configuring Link Bundling
chapter
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
1
Page 12
New and Changed Information
New and Changed Feature Information
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
2
Page 13
CHAPTER 2
Preconfiguring Physical Interfaces
This module describes the preconfiguration of physical interfaces.
Preconfiguration is supported for these types of interfaces and controllers:
100-Gigabit Ethernet
•
Management Ethernet
•
Preconfiguration allows you to configure line cards before they are inserted into the router. When the cards
are inserted, they are instantly configured. The preconfiguration information is created in a different system
database tree (known as the preconfiguration directory on the route processor), rather than with the regularly
configured interfaces.
There may be some preconfiguration data that cannot be verified unless the line card is present, because the
verifiers themselves run only on the line card. Such preconfiguration data is verified when the line card is
inserted and the verifiers are initiated. A configuration is rejected if errors are found when the configuration
is copied from the preconfiguration area to the active area.
One Gigabit Ethernet interface is not supported. Only physical interfaces can be preconfigured.Note
Physical Interface Preconfiguration Overview, page 3
•
Prerequisites for Preconfiguring Physical Interfaces, page 4
•
Benefits of Interface Preconfiguration, page 4
•
How to Preconfigure Physical Interfaces, page 4
•
Information About Preconfiguring Physical Interfaces, page 6
•
Physical Interface Preconfiguration Overview
Preconfiguration is the process of configuring interfaces before they are present in the system. Preconfigured
interfaces are not verified or applied until the actual interface with the matching location (rack/slot/module)
is inserted into the router. When the anticipated line card is inserted and the interfaces are created, the precreated
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
3
Page 14
Prerequisites for Preconfiguring Physical Interfaces
configuration information is verified and, if successful, immediately applied to the running configuration of
the router.
Preconfiguring Physical Interfaces
Note
Note
When you plug the anticipated line card in, make sure to verify any preconfiguration with the appropriate
show commands.
Use the show run command to see interfaces that are in the preconfigured state.
We recommend filling out preconfiguration information in your site planning guide, so that you can
compare that anticipated configuration with the actual preconfigured interfaces when that card is installed
and the interfaces are up.
Tip Use the commit best-effort command to save the preconfiguration to the running configuration file.
Tip
The commit best-effort command merges the target configuration with the running configuration and
commits only valid configuration (best effort). Some configuration might fail due to semantic errors, but
the valid configuration still comes up.
Prerequisites for Preconfiguring Physical Interfaces
Before preconfiguring physical interfaces, ensure that this condition is met:
Preconfiguration drivers and files are installed. Although it may be possible to preconfigure physical
•
interfaces without a preconfiguration driver installed, the preconfiguration files are required to set the
interface definition file on the router that supplies the strings for valid interface names.
Benefits of Interface Preconfiguration
Preconfigurations reduce downtime when you add new cards to the system. With preconfiguration, the new
line card can be instantly configured and actively running during line card bootup.
Another advantage of performing a preconfiguration is that during a card replacement, when the line card is
removed, you can still see the previous configuration and make modifications.
How to Preconfigure Physical Interfaces
This task describes only the most basic preconfiguration of an interface.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
4
Page 15
Preconfiguring Physical Interfaces
SUMMARY STEPS
DETAILED STEPS
How to Preconfigure Physical Interfaces
configure
1.
interface preconfigure type interface-path-id
2.
Use one of the following commands:
3.
ipv4 address ip-address subnet-mask
•
ipv4 address ip-address/prefix
•
Configure additional interface parameters, as described in this manual in the configuration chapter that
4.
applies to the type of interface that you are configuring.
end or commit best-effort
5.
show running-config
6.
Step 1
Step 2
Step 3
configure
Example:
RP/0/RP0/CPU0:router#configure
Enters global configuration mode.
interface preconfigure type interface-path-id
Example:
RP/0/RP0/CPU0:router(config)# interface preconfigure HundredGigE 0/3/0/2
Enters interface preconfiguration mode for an interface, where type specifies the supported interface type that you want
to configure and interface-path-id specifies the location where the interface will be located in rack/slot/module/port
notation.
Use one of the following commands:
ipv4 address ip-address subnet-mask
•
ipv4 address ip-address/prefix
•
Example:
RP/0/RP0/CPU0:router(config-if-pre)# ipv4 address 192.168.1.2/31
Assigns an IP address and mask to the interface.
Step 4
Step 5
Configure additional interface parameters, as described in this manual in the configuration chapter that applies to the
type of interface that you are configuring.
end or commit best-effort
Example:
RP/0/RP0/CPU0:router(config-if-pre)# end
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
5
Page 16
Information About Preconfiguring Physical Interfaces
or
RP/0/RP0/CPU0:router(config-if-pre)# commit
Saves configuration changes.
• When you issue the end command, the system prompts you to commit changes: Uncommitted changes found,
commit them before exiting (yes/no/cancel)?
Entering yes saves configuration changes to the running configuration file, exits the configuration session, and
•
returns the router to EXEC mode.
Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration
•
changes.
Entering cancel leaves the router in the current configuration session without exiting or committing the configuration
•
changes.
Use the commit best-effort command to save the configuration changes to the running configuration file and
•
remain within the configuration session. The commit best-effort command merges the target configuration with
the running configuration and commits only valid changes (best effort). Some configuration changes might fail
due to semantic errors.
Preconfiguring Physical Interfaces
Step 6
show running-config
Example:
RP/0/RP0/CPU0:router# show running-config
(Optional) Displays the configuration information currently running on the router.
This example shows how to preconfigure a basic Ethernet interface:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface preconfigure HundredGigE 0/3/0/24
RP/0/RP0/CPU0:router(config-if)# ipv4 address 192.168.1.2/31
RP/0/RP0/CPU0:router(config-if-pre)# commit
Information About Preconfiguring Physical Interfaces
To preconfigure interfaces, you must understand these concepts:
Use of the Interface Preconfigure Command
Interfaces that are not yet present in the system can be preconfigured with the interface preconfigure command
in global configuration mode.
The interface preconfigure command places the router in interface configuration mode. Users should be able
to add any possible interface commands. The verifiers registered for the preconfigured interfaces verify the
configuration. The preconfiguration is complete when the user enters the end command, or any matching exit
or global configuration mode command.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
6
Page 17
Preconfiguring Physical Interfaces
Use of the Interface Preconfigure Command
Note
Note
It is possible that some configurations cannot be verified until the line card is inserted.
Do not enter the no shutdown command for new preconfigured interfaces, because the no form of this
command removes the existing configuration, and there is no existing configuration.
Users are expected to provide names during preconfiguration that will match the name of the interface that
will be created. If the interface names do not match, the preconfiguration cannot be applied when the interface
is created. The interface names must begin with the interface type that is supported by the router and for which
drivers have been installed. However, the slot, port, subinterface number, and channel interface number
information cannot be validated.
Specifying an interface name that already exists and is configured (or an abbreviated name like Hu0/3/0/0)
is not permitted.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
7
Page 18
Use of the Interface Preconfigure Command
Preconfiguring Physical Interfaces
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
8
Page 19
CHAPTER 3
Advanced Configuration and Modification of the Management Ethernet Interface
This module describes the configuration of Management Ethernet interfaces.
Before you can use Telnet to access the router through the LAN IP address, you must set up a Management
Ethernet interface and enable Telnet servers.
Note
Although the Management Ethernet interfaces on the system are present by default, the user must configure
these interfaces to use them for accessing the router, using protocols and applications such as Simple
Network Management Protocol (SNMP), HTTP, extensible markup language (XML), TFTP, Telnet, and
command-line interface (CLI).
Prerequisites for Configuring Management Ethernet Interfaces, page 9
•
Performing Advanced Management Ethernet Interface Configuration, page 10
•
Information About Configuring Management Ethernet Interfaces, page 16
•
Prerequisites for Configuring Management Ethernet Interfaces
Before performing the Management Ethernet interface configuration procedures that are described in this
chapter, be sure that the following tasks and conditions are met:
You have performed the initial configuration of the Management Ethernet interface.
•
You know how to apply the generalized interface name specification rack/slot/module/port.
•
Note
For transparent switchover, both active and standby Management Ethernet interfaces are expected to be
physically connected to the same LAN or switch.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
9
Page 20
Advanced Configuration and Modification of the Management Ethernet Interface
Performing Advanced Management Ethernet Interface Configuration
Performing Advanced Management Ethernet Interface
Configuration
This section contains these procedures:
Configuring a Management Ethernet Interface
Perform this task to configure a Management Ethernet interface. This procedure provides the minimal
configuration required for the Management Ethernet interface.
SUMMARY STEPS
configure
1.
interface MgmtEth interface-path-id
2.
ipv4 address ip-address mask
3.
mtu bytes
4.
no shutdown
5.
end or commit
6.
show interfaces MgmtEth interface-path-id
7.
DETAILED STEPS
Step 1
Step 2
Step 3
configure
Example:
RP/0/RP0/CPU0:router# configure
Enters global configuration mode.
interface MgmtEth interface-path-id
Example:
RP/0/RP0/CPU0:router(config)# interface MgmtEth 0/RP0/CPU0/0
Enters interface configuration mode and specifies the Ethernet interface name and notation rack/slot/module/port.
The example indicates port 0 on the RP card that is installed in slot 0.
ipv4 address ip-address mask
Example:
RP/0/RP0/CPU0:router(config-if)# ipv4 address 1.76.18.150/16 (or)
ipv4 address 1.76.18.150 255.255.0.0
Assigns an IP address and subnet mask to the interface.
Replace ip-address with the primary IPv4 address for the interface.
•
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
10
Page 21
Advanced Configuration and Modification of the Management Ethernet Interface
Replace mask with the mask for the associated IP subnet. The network mask can be specified in either of two ways:
•
The network mask can be a four-part dotted decimal address. For example, 255.255.0.0 indicates that each bit equal
•
to 1 means that the corresponding address bit belongs to the network address.
The network mask can be indicated as a slash (/) and number. For example, /16 indicates that the first 16 bits of
•
the mask are ones, and the corresponding bits of the address are network address.
Configuring a Management Ethernet Interface
Step 4
Step 5
Step 6
mtu bytes
Example:
RP/0/RP0/CPU0:router(config-if# mtu 1488
(Optional) Sets the maximum transmission unit (MTU) byte value for the interface. The default is 1514.
The default is 1514 bytes.
•
The range for the Management Ethernet interface Interface mtu values is 64 to 1514 bytes.
•
no shutdown
Example:
RP/0/RP0/CPU0:router(config-if)# no shutdown
Removes the shutdown configuration, which removes the forced administrative down on the interface, enabling it to
move to an up or down state.
end or commit
Example:
RP/0/RP0/CPU0:router(config-if)# end
or
RP/0/RP0/CPU0:router(config-if)# commit
Saves configuration changes.
Step 7
When you issue the end command, the system prompts you to commit changes:
•
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
Entering yes saves configuration changes to the running configuration file, exits the configuration session, and
•
returns the router to EXEC mode.
Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration
•
changes.
Entering cancel leaves the router in the current configuration session without exiting or committing the configuration
•
changes.
Use the commit command to save the configuration changes to the running configuration file and remain within
•
the configuration session.
show interfaces MgmtEth interface-path-id
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
11
Page 22
Advanced Configuration and Modification of the Management Ethernet Interface
IPv6 Stateless Address Auto Configuration on Management Interface
Example:
RP/0/RP0/CPU0:router# show interfaces MgmtEth 0/RP0/CPU0/0
(Optional) Displays statistics for interfaces on the router.
This example displays advanced configuration and verification of the Management Ethernet interface on the
RP:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface MgmtEth 0/RP0/CPU0/0
RP/0/RP0/CPU0:router(config)# ipv4 address 1.76.18.150/16
RP/0/RP0/CPU0:router(config-if)# speed 100
RP/0/RP0/CPU0:router(config-if)# duplex full
RP/0/RP0/CPU0:router(config-if)# no shutdown
RP/0/RP0/CPU0:router(config-if)# commit
RP/0/RP0/CPU0:router:Mar 26 01:09:28.685 :ifmgr[190]:%LINK-3-UPDOWN :Interface
MgmtEth0/RP0/CPU0/0, changed state to Up
RP/0/RP0/CPU0:router(config-if)# end
RP/0/RP0/CPU0:router# show interfaces MgmtEth 0/RP0/CPU0/0
MgmtEth0/RP0/CPU0/0 is up, line protocol is up
Interface state transitions: 3
Hardware is Management Ethernet, address is 1005.cad8.4354 (bia 1005.cad8.4354)
Internet address is 1.76.18.150/16
MTU 1488 bytes, BW 1000000 Kbit (Max: 1000000 Kbit)
reliability 255/255, txload 0/255, rxload 0/255
Encapsulation ARPA,
Full-duplex, 1000Mb/s, 1000BASE-T, link type is autonegotiation
loopback not set,
Last link flapped 00:00:59
ARP type ARPA, ARP timeout 04:00:00
Last input 00:00:00, output 00:00:02
Last clearing of "show interface" counters never
5 minute input rate 4000 bits/sec, 3 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
21826 packets input, 4987886 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 12450 broadcast packets, 8800 multicast packets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
1192 packets output, 217483 bytes, 0 total output drops
Output 0 broadcast packets, 0 multicast packets
0 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
3 carrier transitions
RP/0/RP0/CPU0:router# show running-config interface MgmtEth 0/RP0/CPU0/0
interface MgmtEth0/RP0/CPU0/0
mtu 1488
ipv4 address 1.76.18.150/16
ipv6 address 2002::14c:125a/64
ipv6 enable
!
0 runts, 0 giants, 0 throttles, 0 parity
IPv6 Stateless Address Auto Configuration on Management Interface
Perform this task to enable IPv6 stateless auto configuration on Management interface.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
12
Page 23
Advanced Configuration and Modification of the Management Ethernet Interface
SUMMARY STEPS
configure
1.
interface MgmtEth interface-path-id
2.
ipv6 address autoconfig
3.
show ipv6 interfaces interface-path-id
4.
DETAILED STEPS
IPv6 Stateless Address Auto Configuration on Management Interface
Step 1
Step 2
Step 3
Step 4
configure
Example:
RP/0/RP0/CPU0:router# configure
Enters global configuration mode.
interface MgmtEth interface-path-id
Example:
RP/0/RP0/CPU0:router(config)# interface MgmtEth 0/RP0/CPU0/0
Enters interface configuration mode and specifies the Ethernet interface name and notation rack/slot/module/port.
The example indicates port 0 on the RP card that is installed in slot 0.
ipv6 address autoconfig
Example:
RP/0/RP0/CPU0:router(config-if)# ipv6 address autoconfig
Enable IPv6 stateless address auto configuration on the management port.
show ipv6 interfaces interface-path-id
Example:
RP/0/RP0/CPU0:router# show ipv6 interfaces gigabitEthernet 0/2/0/0
(Optional) Displays statistics for interfaces on the router.
This example displays :
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface MgmtEth 0/RP0/CPU0/0
RP/0/RP0/CPU0:router(config)# ipv6 address autoconfig
RP/0/RP0/CPU0:router# show ipv6 interfaces gigabitEthernet 0/2/0/0
Fri Nov 4 16:48:14.372 IST
GigabitEthernet0/2/0/0 is Up, ipv6 protocol is Up, Vrfid is default (0x60000000)
IPv6 is enabled, link-local address is fe80::d1:1eff:fe2b:baf
Global unicast address(es):
5::d1:1eff:fe2b:baf [AUTO CONFIGURED], subnet is 5::/64 <<<<<< auto configured address
Joined group address(es): ff02::1:ff2b:baf ff02::2 ff02::1
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
13
Page 24
Advanced Configuration and Modification of the Management Ethernet Interface
Modifying the MAC Address for a Management Ethernet Interface
MTU is 1514 (1500 is available to IPv6)
ICMP redirects are disabled
ICMP unreachables are enabled
ND DAD is enabled, number of DAD attempts 1
ND reachable time is 0 milliseconds
ND cache entry limit is 1000000000
ND advertised retransmit interval is 0 milliseconds
Hosts use stateless autoconfig for addresses.
Outgoing access list is not set
Inbound common access list is not set, access list is not set
Table Id is 0xe0800000
Complete protocol adjacency: 0
Complete glean adjacency: 0
Incomplete protocol adjacency: 0
Incomplete glean adjacency: 0
Dropped protocol request: 0
Dropped glean request: 0
Modifying the MAC Address for a Management Ethernet Interface
Perform this task to configure the MAC layer address of the Management Ethernet interfaces for the RPs.
SUMMARY STEPS
DETAILED STEPS
Step 1
configure
Example:
RP/0/RP0/CPU0:router# configure
Enters global configuration mode.
Step 2
interface MgmtEth interface-path-id
Example:
RP/0/RP0/CPU0:router(config)# interface MgmtEth 0/RP0/CPU0/0
Enters interface configuration mode and specifies the Management Ethernet interface name and instance.
Step 3
mac-address address
configure
1.
interface MgmtEth interface-path-id
2.
mac-address address
3.
end or commit
4.
Step 4
14
Example:
RP/0/RP0/CPU0:router(config-if)# mac-address 0001.2468.ABCD
Configures the MAC layer address of the Management Ethernet interface.
Note
To return the device to its default MAC address, use the no mac-address address
•
command.
end or commit
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
Page 25
Advanced Configuration and Modification of the Management Ethernet Interface
Example:
RP/0/RP0/CPU0:router(config-if)# end
or
RP/0/RP0/CPU0:router(config-if)# commit
Saves configuration changes.
When you issue the end command, the system prompts you to commit changes:
•
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
Entering yes saves configuration changes to the running configuration file, exits the configuration session, and
•
returns the router to EXEC mode.
Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration
•
changes.
Verifying Management Ethernet Interface Configuration
Entering cancel leaves the router in the current configuration session without exiting or committing the configuration
•
changes.
Use the commit command to save the configuration changes to the running configuration file and remain within
•
the configuration session.
Verifying Management Ethernet Interface Configuration
Perform this task to verify configuration modifications on the Management Ethernet interfaces.
SUMMARY STEPS
show interfaces MgmtEth interface-path-id
1.
show running-config interface MgmtEth interface-path-id
2.
DETAILED STEPS
Step 1
show interfaces MgmtEth interface-path-id
Step 2
Example:
RP/0/RP0/CPU0:router# show interfaces MgmtEth 0/RP0/CPU0/0
Displays the Management Ethernet interface configuration.
show running-config interface MgmtEth interface-path-id
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
15
Page 26
Advanced Configuration and Modification of the Management Ethernet Interface
Information About Configuring Management Ethernet Interfaces
Example:
RP/0/RP0/CPU0:router# show running-config interface MgmtEth 0/RP0/CPU0/0
Displays the running configuration.
Information About Configuring Management Ethernet Interfaces
To configure Management Ethernet interfaces, you must understand the following concept:
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
16
Page 27
CHAPTER 4
Configuring Ethernet Interfaces
This module describes the configuration of Ethernet interfaces.
The distributed 10-Gigabit, 40-Gigabit, 100-Gigabit Ethernet architecture delivers network scalability and
performance, while enabling service providers to offer high-density, high-bandwidth networking solutions.
These solutions are designed to interconnect the router with other systems in POPs, including core and edge
routers and Layer 2 and Layer 3 switches.
Configuring Gigabit Ethernet Interfaces, page 17
•
Information About Configuring Ethernet, page 21
•
Configuring Gigabit Ethernet Interfaces
Use this procedure to create a basic Ethernet interface configuration.
SUMMARY STEPS
DETAILED STEPS
Step 1
show version
show version
1.
show interfaces [HundredGigE | ] interface-path-id
2.
configure
3.
interface [HundredGigE| TenGigE] interface-path-id
4.
ipv4 address ip-address mask
5.
mtu bytes
6.
mac-address value1.value2.value3
7.
no shutdown
8.
end or commit
9.
show interfaces [HundredGigE | TenGigE] interface-path-id
10.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
17
Page 28
Configuring Ethernet Interfaces
Configuring Gigabit Ethernet Interfaces
Example:
RP/0/RP0/CPU0:router# show version
(Optional) Displays the current software version, and can also be used to confirm that the router recognizes the line card.
Step 2
Step 3
Step 4
show interfaces [HundredGigE | ] interface-path-id
Example:
RP/0/RP0/CPU0:router# show interface HundredGigE 0/1/0/1
(Optional) Displays the configured interface and checks the status of each interface port.
configure
Example:
RP/0/RP0/CPU0:router# configure terminal
Enters global configuration mode.
interface [HundredGigE| TenGigE] interface-path-id
Example:
RP/0/RP0/CPU0:router(config)# interface HundredGigE 0/1/0/1
Enters interface configuration mode and specifies the Ethernet interface name and notation rack/slot/module/port. Possible
interface types for this procedure are:
HundredGigE
•
TenGigE
•
Note
The example indicates a 100-Gigabit Ethernet interface in the line card
•
in slot 1.
Step 5
Step 6
18
ipv4 address ip-address mask
Example:
RP/0/RP0/CPU0:router(config-if)# ipv4 address 172.18.189.38 255.255.255.224
Assigns an IP address and subnet mask to the interface.
Replace ip-address with the primary IPv4 address for the interface.
•
Replace mask with the mask for the associated IP subnet. The network mask can be specified in either of two ways:
•
The network mask can be a four-part dotted decimal address. For example, 255.0.0.0 indicates that each bit equal
•
to 1 means that the corresponding address bit belongs to the network address.
The network mask can be indicated as a slash (/) and number. For example, /8 indicates that the first 8 bits of the
•
mask are ones, and the corresponding bits of the address are network address.
mtu bytes
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
Page 29
Configuring Ethernet Interfaces
Example:
RP/0/RP0/CPU0:router(config-if)# mtu 1448
(Optional) Sets the MTU value for the interface.
The default is 1514 bytes for normal frames and 1518 bytes for 802.1Q tagged frames.
•
The range for 100-Gigabit Ethernet mtu values is 64 bytes to 65535 bytes.
•
Configuring Gigabit Ethernet Interfaces
Step 7
Step 8
Step 9
mac-address value1.value2.value3
Example:
RP/0/RP0/CPU0:router(config-if)# mac address 0001.2468.ABCD
(Optional) Sets the MAC layer address of the Management Ethernet interface.
The values are the high, middle, and low 2 bytes, respectively, of the MAC address in hexadecimal. The range of
•
each 2-byte value is 0 to ffff.
no shutdown
Example:
RP/0/RP0/CPU0:router(config-if)# no shutdown
Removes the shutdown configuration, which forces an interface administratively down.
end or commit
Example:
RP/0/RP0/CPU0:router(config-if)# end
or
RP/0/RP0/CPU0:router(config-if)# commit
Saves configuration changes.
Step 10
When you issue the end command, the system prompts you to commit changes:
•
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
Entering yes saves configuration changes to the running configuration file, exits the configuration session, and
•
returns the router to EXEC mode.
Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration
•
changes.
Entering cancel leaves the router in the current configuration session without exiting or committing the configuration
•
changes.
Use the commit command to save the configuration changes to the running configuration file and remain within
•
the configuration session.
show interfaces [HundredGigE | TenGigE] interface-path-id
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
19
Page 30
Configuring Gigabit Ethernet Interfaces
Example:
RP/0/RP0/CPU0:router# show interfaces HundredGigE 0/1/0/1
(Optional) Displays statistics for interfaces on the router.
This example shows how to configure an interface for a 100-Gigabit Ethernet line card:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface HundredGigE 0/1/0/1
RP/0/RP0/CPU0:router(config-if)# ipv4 address 172.18.189.38 255.255.255.224
RP/0/RP0/CPU0:router(config-if)# mtu 1448
RP/0/RP0/CPU0:router(config-if)# mac-address 0001.2468.ABCD
RP/0/RP0/CPU0:router(config-if)# no shutdown
RP/0/RP0/CPU0:router(config-if)# end
Uncommitted changes found, commit them? [yes]: yes
Configuring Ethernet Interfaces
RP/0/RP0/CPU0:router# show interfaces HundredGigE 0/5/0/24
HundredGigE0/5/0/24 is up, line protocol is up
Interface state transitions: 1
Hardware is HundredGigE, address is 6219.8864.e330 (bia 6219.8864.e330)
Internet address is 3.24.1.1/24
MTU 9216 bytes, BW 100000000 Kbit (Max: 100000000 Kbit)
reliability 255/255, txload 3/255, rxload 3/255
Encapsulation ARPA,
Full-duplex, 100000Mb/s, link type is force-up
output flow control is off, input flow control is off
Carrier delay (up) is 10 msec
loopback not set,
Last link flapped 10:05:07
ARP type ARPA, ARP timeout 04:00:00
Last input 00:08:56, output 00:00:00
Last clearing of "show interface" counters never
5 minute input rate 1258567000 bits/sec, 1484160 packets/sec
5 minute output rate 1258584000 bits/sec, 1484160 packets/sec
228290765840 packets input, 27293508436038 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 15 broadcast packets, 45 multicast packets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
212467849449 packets output, 25733664696650 bytes, 0 total output drops
Output 23 broadcast packets, 15732 multicast packets
39 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
RP/0/RP0/CPU0:router# show running-config interface HundredGigE 0/5/0/24
interface HundredGigE0/5/0/24
mtu 9216
service-policy input linerate
service-policy output elinerate
ipv4 address 3.24.1.1 255.255.255.0
ipv6 address 3:24:1::1/64
flow ipv4 monitor perfv4 sampler fsm ingress
!
0 runts, 0 giants, 0 throttles, 0 parity
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
20
Page 31
Configuring Ethernet Interfaces
Information About Configuring Ethernet
This section provides the following information sections:
Default Configuration Values for 100-Gigabit Ethernet
This table describes the default interface configuration parameters that are present when an interface is enabled
on a 100-Gigabit Ethernet line card.
Information About Configuring Ethernet
Note
You must use the shutdown command to bring an interface administratively down. The interface default
is no shutdown. When a line card is first inserted into the router, if there is no established preconfiguration
for it, the configuration manager adds a shutdown item to its configuration. This shutdown can be removed
only be entering the no shutdown command.
Table 3: 100-Gigabit Ethernet Line Card Default Configuration Values
Default ValueConfiguration File EntryParameter
mtuMTU
mac addressMAC address
1514 bytes for normal
•
frames
1518 bytes for 802.1Q
•
tagged frames.
1522 bytes for Q-in-Q
•
frames.
Hardware burned-in address
(BIA)
Ethernet MTU
The Ethernet maximum transmission unit (MTU) is the size of the largest frame, minus the 4-byte frame check
sequence (FCS), that can be transmitted on the Ethernet network. Every physical network along the destination
of a packet can have a different MTU.
Cisco IOS XR software supports two types of frame forwarding processes:
• Fragmentation for IPV4 packets–In this process, IPv4 packets are fragmented as necessary to fit within
the MTU of the next-hop physical network.
IPv6 does not support fragmentation.Note
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
21
Page 32
Ethernet MTU
Configuring Ethernet Interfaces
• MTU discovery process determines largest packet size–This process is available for all IPV6 devices,
and for originating IPv4 devices. In this process, the originating IP device determines the size of the
largest IPv6 or IPV4 packet that can be sent without being fragmented. The largest packet is equal to
the smallest MTU of any network between the IP source and the IP destination devices. If a packet is
larger than the smallest MTU of all the networks in its path, that packet will be fragmented as necessary.
This process ensures that the originating device does not send an IP packet that is too large.
Jumbo frame support is automatically enable for frames that exceed the standard frame size. The default value
is 1514 for standard frames and 1518 for 802.1Q tagged frames. These numbers exclude the 4-byte frame
check sequence (FCS).
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
22
Page 33
CHAPTER 5
Configuring Ethernet OAM
This module describes the configuration of Ethernet Operations, Administration, and Maintenance (OAM)
.
Feature History for Configuring Ethernet OAM
ModificationRelease
Release 6.1.1
Release 6.3.1
Configuring Ethernet OAM, page 23
•
Information About Configuring Ethernet OAM, page 24
•
How to Configure Ethernet OAM, page 37
•
Configuration Examples for Ethernet OAM, page 66
•
Support for the following features was introduced:
Support for the following feature was introduced:
Configuring Ethernet OAM
This module describes the configuration of Ethernet Operations, Administration, and Maintenance (OAM) .
Feature History for Configuring Ethernet OAM
Ethernet Link OAM
•
Ethernet CFM
•
Unidirectional Link Detection Protocol
•
ModificationRelease
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
23
Page 34
Information About Configuring Ethernet OAM
Configuring Ethernet OAM
Release 6.1.1
Release 6.3.1
Support for the following features was introduced:
Ethernet Link OAM
•
Ethernet CFM
•
Support for the following feature was introduced:
Unidirectional Link Detection Protocol
•
Information About Configuring Ethernet OAM
To configure Ethernet OAM, you should understand the following concepts:
Ethernet Link OAM
Ethernet as a Metro Area Network (MAN) or a Wide Area Network (WAN) technology benefits greatly from
the implementation of Operations, Administration and Maintenance (OAM) features. Ethernet link OAM
features allow Service Providers to monitor the quality of the connections on a MAN or WAN. Service
providers can monitor specific events, . Ethernet link OAM operates on a single, physical link and it can be
configured to monitor either side or both sides of that link.
Ethernet link OAM can be configured in the following ways:
A Link OAM profile can be configured, and this profile can be used to set the parameters for multiple
•
interfaces.
Link OAM can be configured directly on an interface.
•
When an interface is also using a link OAM profile, specific parameters that are set in the profile can
be overridden by configuring a different value directly on the interface.
An EOAM profile simplifies the process of configuring EOAM features on multiple interfaces. An Ethernet
OAM profile, and all of its features, can be referenced by other interfaces, allowing other interfaces to inherit
the features of that Ethernet OAM profile.
Individual Ethernet link OAM features can be configured on individual interfaces without being part of a
profile. In these cases, the individually configured features always override the features in the profile.
The preferred method of configuring custom EOAM settings is to create an EOAM profile in Ethernet
configuration mode and then attach it to an individual interface or to multiple interfaces.
These standard Ethernet Link OAM features are supported on the router:
Neighbor Discovery
Neighbor discovery enables each end of a link to learn the OAM capabilities of the other end and establish
an OAM peer relationship. Each end also can require that the peer have certain capabilities before it will
establish a session. You can configure certain actions to be taken if there is a capabilities conflict or if a
discovery process times out, using the action capabilities-conflict or action discovery-timeout commands.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
24
Page 35
Configuring Ethernet OAM
Link Monitoring
Link monitoring enables an OAM peer to monitor faults that cause the quality of a link to deteriorate over
time. When link monitoring is enabled, an OAM peer can be configured to take action when the configured
thresholds are exceeded.
MIB Retrieval
MIB retrieval enables an OAM peer on one side of an interface to get the MIB variables from the remote side
of the link. The MIB variables that are retrieved from the remote OAM peer are READ ONLY.
Miswiring Detection (Cisco-Proprietary)
Miswiring Detection is a Cisco-proprietary feature that uses the 32-bit vendor field in every Information
OAMPDU to identify potential miswiring cases.
Ethernet CFM
SNMP Traps
Ethernet CFM
SNMP traps can be enabled or disabled on an Ethernet OAM interface.
Ethernet Connectivity Fault Management (CFM) is a service-level OAM protocol that provides tools for
monitoring and troubleshooting end-to-end Ethernet services per VLAN. This includes proactive connectivity
monitoring, fault verification, and fault isolation. CFM uses standard Ethernet frames and can be run on any
physical media that is capable of transporting Ethernet service frames. Unlike most other Ethernet protocols
which are restricted to a single physical link, CFM frames can transmit across the entire end-to-end Ethernet
network.
CFM is defined in two standards:
• IEEE 802.1ag—Defines the core features of the CFM protocol.
• ITU-T Y.1731—Redefines, but maintains compatibility with the features of IEEE 802.1ag, and defines
some additional features.
Ethernet CFM supports these functions of ITU-T Y.1731:
• ETH-CC, ETH-RDI, ETH-LB, ETH-LT—These are equivalent to the corresponding features defined
in IEEE 802.1ag.
Note
• ETH-AIS—The reception of ETH-LCK messages is also supported.
To understand how the CFM maintenance model works, you need to understand these concepts and features:
The Linktrace responder procedures defined in IEEE 802.1ag are used rather than the
procedures defined in Y.1731; however, these are interoperable.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
25
Page 36
Ethernet CFM
Maintenance Domains
A maintenance domain describes 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 interfaces internal to it
and at its boundary, as shown in this figure.
Figure 1: CFM Maintenance Domain
Configuring Ethernet OAM
A maintenance domain is defined by the bridge ports that are provisioned within it. Domains are assigned
maintenance levels, in the range of 0 to 7, by the administrator. The level of the domain is useful in defining
the hierarchical relationships of multiple domains.
CFM maintenance domains allow different organizations to use CFM in the same network, but independently.
For example, consider a service provider who offers a service to a customer, and to provide that service, they
use two other operators in segments of the network. In this environment, CFM can be used in the following
ways:
The customer can use CFM between their CE devices, to verify and manage connectivity across the
•
whole network.
The service provider can use CFM between their PE devices, to verify and manage the services they are
•
providing.
Each operator can use CFM within their operator network, to verify and manage connectivity within
•
their network.
Each organization uses a different CFM maintenance domain.
This figure shows an example of the different levels of maintenance domains in a network.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
26
Page 37
Configuring Ethernet OAM
Ethernet CFM
Note
In CFM diagrams, the conventions are that triangles represent MEPs, pointing in the direction that the
MEP sends CFM frames, and circles represent MIPs. For more information about MEPs and MIPs, see
the “Maintenance Points” section on page 71.
Figure 2: Different CFM Maintenance Domains Across a Network
To ensure that the CFM frames for each domain do not interfere with each other, each domain is assigned a
maintenance level, between 0 and 7. Where domains are nested, as in this example, the encompassing domain
must have a higher level than the domain it encloses. In this case, the domain levels must be negotiated between
the organizations involved. The maintenance level is carried in all CFM frames that relate to that domain.
CFM maintenance domains may touch or nest, but cannot intersect. This figure illustrates the supported
structure for touching and nested domains, and the unsupported intersection of domains.
Supported CFM Maintenance Domain
Structure
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
27
Page 38
Ethernet CFM
Services
Configuring Ethernet OAM
A CFM service allows an organization to partition its CFM maintenance domain, according to the connectivity
within the network. For example, if the network is divided into a number of virtual LANs (VLANs), a CFM
service is created for each of these. CFM can then operate independently in each service. It is important that
the CFM services match the network topology, so that CFM frames relating to one service cannot be received
in a different service. For example, a service provider may use a separate CFM service for each of their
customers, to verify and manage connectivity between that customer's end points.
A CFM service is always associated with the maintenance domain that it operates within, and therefore with
that domain's maintenance level. All CFM frames relating to the service carry the maintenance level of the
corresponding domain.
Note
CFM Services are referred to as Maintenance Associations in IEEE 802.1ag and as Maintenance Entity
Groups in ITU-T Y.1731.
Maintenance Points
A CFM Maintenance Point (MP) is an instance of a particular CFM service on a specific interface. CFM only
operates on an interface if there is a CFM maintenance point on the interface; otherwise, CFM frames are
forwarded transparently through the interface.
A maintenance point is always associated with a particular CFM service, and therefore with a particular
maintenance domain at a particular level. Maintenance points generally only process CFM frames at the same
level as their associated maintenance domain. Frames at a higher maintenance level are always forwarded
transparently, while frames at a lower maintenance level are normally dropped. This helps enforce the
maintenance domain hierarchy described in the “Maintenance Domains” section on page 69, and ensures that
CFM frames for a particular domain cannot leak out beyond the boundary of the domain.
There are two types of MP:
• Maintenance End Points (MEPs)—Created at the edge of the domain. Maintenance end points (MEPs)
are members of a particular service within a domain and are responsible for sourcing and sinking CFM
frames. They periodically transmit continuity check messages and receive similar messages from other
MEPs within their domain. They also transmit traceroute and loopback messages at the request of the
administrator. MEPs are responsible for confining CFM messages within the domain.
• Maintenance Intermediate Points (MIPs)—Created in the middle of the domain. Unlike MEPS, MIPs
do allow CFM frames at their own level to be forwarded.
MIP Creation
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
28
Unlike MEPs, MIPs are not explicitly configured on each interface. MIPs are created automatically according
to the algorithm specified in the CFM 802.1ag standard. The algorithm, in brief, operates as follows for each
interface:
The bridge-domain or cross-connect for the interface is found, and all services associated with that
•
bridge-domain or cross-connect are considered for MIP auto-creation.
Page 39
Configuring Ethernet OAM
Ethernet CFM
The level of the highest-level MEP on the interface is found. From among the services considered above,
•
the service in the domain with the lowest level that is higher than the highest MEP level is selected. If
there are no MEPs on the interface, the service in the domain with the lowest level is selected.
The MIP auto-creation configuration (mip auto-create command) for the selected service is examined
•
to determine whether a MIP should be created.
Note
Configuring a MIP auto-creation policy for a service does not guarantee that a MIP will
automatically be created for that service. The policy is only considered if that service
is selected by the algorithm first.
MEP and CFM Processing Overview
The boundary of a domain is an interface, rather than a bridge or host. Therefore, MEPs can be sub-divided
into two categories:
• Down MEPs—Send CFM frames from the interface where they are configured, and process CFM frames
received on that interface. Down MEPs transmit AIS messages upward (toward the cross-connect).
• Up MEPs—Send frames into the bridge relay function, as if they had been received on the interface
where the MEP is configured. They process CFM frames that have been received on other interfaces,
and have been switched through the bridge relay function as if they are going to be sent out of the
interface where the MEP is configured. Up MEPs transmit AIS messages downward (toward the wire).
However, AIS packets are only sent when there is a MIP configured on the same interface as the MEP
and at the level of the MIP.
Note
The terms Down MEP and Up MEP are defined in the IEEE 802.1ag and ITU-T Y.1731 standards, and
refer to the direction that CFM frames are sent from the MEP. The terms should not be confused with the
operational status of the MEP.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
29
Page 40
Ethernet CFM
Configuring Ethernet OAM
This figure illustrates the monitored areas for Down and Up MEPs.
Figure 3: Monitored Areas for Down and Up MEPs
This figure shows maintenance points at different levels. Because domains are allowed to nest but not intersect
(see Figure 3), a MEP at a low level always corresponds with a MEP or MIP at a higher level. In addition,
only a single MIP is allowed on any interface—this is generally created in the lowest domain that exists at
the interface and that does not have a MEP.
CFM Maintenance Points at Different
Levels
MIPs and Up MEPs can only exist on switched (Layer 2) interfaces, because they send and receive frames
from the bridge relay function. Down MEPs can be created on switched (Layer 2) or routed (Layer 3) interfaces.
MEPs continue to operate normally if the interface they are created on is blocked by the Spanning Tree Protocol
(STP); that is, CFM frames at the level of the MEP continue to be sent and received, according to the direction
of the MEP. MEPs never allow CFM frames at the level of the MEP to be forwarded, so the STP block is
maintained.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
30
Page 41
Configuring Ethernet OAM
Ethernet CFM
MIPs also continue to receive CFM frames at their level if the interface is STP blocked, and can respond to
any received frames. However, MIPs do not allow CFM frames at the level of the MIP to be forwarded if the
interface is blocked.
Note
A separate set of CFM maintenance levels is created every time a VLAN tag is pushed onto the frame.
Therefore, if CFM frames are received on an interface which pushes an additional tag, so as to “tunnel”
the frames over part of the network, the CFM frames will not be processed by any MPs within the tunnel,
even if they are at the same level. For example, if a CFM MP is created on an interface with an encapsulation
that matches a single VLAN tag, any CFM frames that are received at the interface that have two VLAN
tags will be forwarded transparently, regardless of the CFM level.
CFM Protocol Messages
The CFM protocol consists of a number of different message types, with different purposes. All CFM messages
use the CFM EtherType, and carry the CFM maintenance level for the domain to which they apply.
This section describes the following CFM messages:
Continuity Check (IEEE 802.1ag and ITU-T Y.1731)
Continuity Check Messages (CCMs) are “heartbeat” messages exchanged periodically between all the MEPs
in a service. Each MEP sends out multicast CCMs, and receives CCMs from all the other MEPs in the
service—these are referred to as peer MEPs. This allows each MEP to discover its peer MEPs, and to verify
that there is connectivity between them.
MIPs also receive CCMs. MIPs use the information to build a MAC learning database that is used when
responding to Linktrace. For more information about Linktrace, see the Linktrace (IEEE 802.1ag and ITU-T
Y.1731).
Figure 4: Continuity Check Message Flow
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
31
Page 42
Ethernet CFM
Configuring Ethernet OAM
All the MEPs in a service must transmit CCMs at the same interval. IEEE 802.1ag defines 7 possible intervals
that can be used:
3.3ms
•
10ms
•
100ms
•
1s
•
10s
•
1 minute
•
10 minutes
•
A MEP detects a loss of connectivity with one of its peer MEPs when some number of CCMs have been
missed. This occurs when sufficient time has passed during which a certain number of CCMs were expected,
given the CCM interval. This number is called the loss threshold, and is usually set to 3.
CFM is supported only on interfaces which have Layer 2 transport feature enabled.
CCM messages carry a variety of information that allows different defects to be detected in the service. This
information includes:
A configured identifier for the domain of the transmitting MEP. This is referred to as the Maintenance
•
Domain Identifier (MDID).
A configured identifier for the service of the transmitting MEP. This is referred to as the Short MA
•
Name (SMAN). Together, the MDID and the SMAN make up the Maintenance Association Identifier
(MAID). The MAID must be configured identically on every MEP in the service.
These are restrictions on the type of MAID that are supported for sessions with time interval of less than
•
1 minute. The MAID supports two types of formats on offloaded MEPs:
No Domain Name Format
•
MD Name Format = 1-NoDomainName
◦
Short MA Name Format = 3 - 2 bytes integer value
◦
Short MA NAme Length = 2 - fixed length
◦
Short MA Name = 2 bytes of integer
◦
1731 Maid Format
•
MD Name Format = 1-NoDomainName
◦
MA Name Format(MEGID Format) = 32
◦
MEGID Length = 13 - fixed length
◦
MEGID(ICCCode) = 6 Bytes
◦
MEGID(UMC) = 7 Bytes
◦
ITU Carrier Code (ICC) - Number of different configurable ICC code - 15 (for each NPU)
◦
Unique MEG ID Code (UMC) - 4
◦
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
32
Page 43
Configuring Ethernet OAM
Ethernet CFM
A configured numeric identifier for the MEP (the MEP ID). Each MEP in the service must be configured
•
with a different MEP ID.
Dynamic Remote MEPs are not supported for MEPs with less than 1min interval. You must configure
•
MEP CrossCheck for all such MEPS.
Sequence numbering is not supported for MEPs with less than 1 minute interval.
•
A Remote Defect Indication (RDI). Each MEP includes this in the CCMs it is sending, if it has detected
•
a defect relating to the CCMs it is receiving. This notifies all the MEPs in the service that a defect has
been detected somewhere in the service.
The interval at which CCMs are being transmitted.
•
CCM Tx/Rx statistics counters are not supported for MEPs with less than1 minute intervals.
•
Sender TLV and Cisco Proprietary TLVs are not supported for MEPs with less than 1min intervals.
•
• The status of the interface where the MEP is operating—for example, whether the interface is up, down,
STP blocked, and so on.
Note
The status of the interface (up/down) should not be confused with the direction of any
MEPs on the interface (Up MEPs/Down MEPs).
These defects can be detected from received CCMs:
• Interval mismatch—The CCM interval in the received CCM does not match the interval that the MEP
is sending CCMs.
• Level mismatch—A MEP has received a CCM carrying a lower maintenance level than the MEPs own
level.
• Loop—A CCM is received with the source MAC address equal to the MAC address of the interface
where the MEP is operating.
• Configuration error—A CCM is received with the same MEP ID as the MEP ID configured for the
receiving MEP.
• Cross-connect—A CCM is received with an MAID that does not match the locally configured MAID.
This generally indicates a VLAN misconfiguration within the network, such that CCMs from one service
are leaking into a different service.
• Peer interface down—A CCM is received that indicates the interface on the peer is down.
• Remote defect indication—A CCM is received carrying a remote defect indication.
Note
This defect does not cause the MEP to include a remote defect indication in the CCMs
that it is sending.
Out-of-sequence CCMs can also be detected by monitoring the sequence number in the received CCMs from
each peer MEP. However, this is not considered a CCM defect.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
33
Page 44
Ethernet CFM
Loopback (IEEE 802.1ag and ITU-T Y.1731)
Loopback Messages (LBM) and Loopback Replies (LBR) are used to verify connectivity between a local
MEP and a particular remote MP. At the request of the administrator, a local MEP sends unicast LBMs to the
remote MP. On receiving each LBM, the target maintenance point sends an LBR back to the originating MEP.
Loopback indicates whether the destination is reachable or not—it does not allow hop-by-hop discovery of
the path. It is similar in concept to an ICMP Echo (ping). Since loopback messages are destined for unicast
addresses, they are forwarded like normal data traffic, while observing the maintenance levels. At each device
that the loopback reaches, if the outgoing interface is known (in the bridge's forwarding database), then the
frame is sent out on that interface. If the outgoing interface is not known, then the message is flooded on all
interfaces.
This figure shows an example of CFM loopback message flow between a MEP and MIP.
Figure 5: Loopback Messages
Configuring Ethernet OAM
Loopback messages can be padded with user-specified data. This allows data corruption to be detected in the
network. They also carry a sequence number which allows for out-of-order frames to be detected.
Linktrace (IEEE 802.1ag and ITU-T Y.1731)
Linktrace Messages (LTM) and Linktrace Replies (LTR) are used to track the path (hop-by-hop) to a unicast
destination MAC address. At the request of the operator, a local MEP sends an LTM. Each hop where there
is a maintenance point sends an LTR back to the originating MEP. This allows the administrator to discover
connectivity data about the path. It is similar in concept to IP traceroute, although the mechanism is different.
In IP traceroute, successive probes are sent, whereas CFM Linktrace uses a single LTM which is forwarded
by each MP in the path. LTMs are multicast, and carry the unicast target MAC address as data within the
frame. They are intercepted at each hop where there is a maintenance point, and either retransmitted or dropped
to discover the unicast path to the target MAC address.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
34
Page 45
Configuring Ethernet OAM
Ethernet CFM
This figure shows an example of CFM linktrace message flow between MEPs and MIPs.
Figure 6: Linktrace Message Flow
Note
The linktrace mechanism is designed to provide useful information even after a network failure. This allows
it to be used to locate failures, for example after a loss of continuity is detected. To achieve this, each MP
maintains a CCM Learning Database. This maps the source MAC address for each received CCM to the
interface through which the CCM was received. It is similar to a typical bridge MAC learning database, except
that it is based only on CCMs and it times out much more slowly—on the order of days rather than minutes.
In IEEE 802.1ag, the CCM Learning Database is referred to as the MIP CCM Database. However, it
applies to both MIPs and MEPs.
In IEEE 802.1ag, when an MP receives an LTM message, it determines whether to send a reply using the
following steps:
1
The target MAC address in the LTM is looked up in the bridge MAC learning table. If the MAC address
is known, and therefore the egress interface is known, then an LTR is sent.
2
If the MAC address is not found in the bridge MAC learning table, then it is looked up in the CCM learning
database. If it is found, then an LTR is sent.
3
If the MAC address is not found, then no LTR is sent (and the LTM is not forwarded).
If the target MAC has never been seen previously in the network, the linktrace operation will not produce any
results.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
35
Page 46
Ethernet CFM
Configuring Ethernet OAM
Note
IEEE 802.1ag and ITU-T Y.1731 define slightly different linktrace mechanisms. In particular, the use of
the CCM learning database and the algorithm described above for responding to LTM messages are
specific to IEEE 802.1ag. IEEE 802.1ag also specifies additional information that can be included in
LTRs. Regardless of the differences, the two mechanisms are interoperable.
Configurable Logging
CFM supports logging of various conditions to syslog. Logging can be enabled independently for each service,
and when the following conditions occur:
New peer MEPs are detected, or loss of continuity with a peer MEP occurs.
•
Changes to the CCM defect conditions are detected.
•
• Cross-check “missing” or “unexpected” conditions are detected.
AIS condition detected (AIS messages received) or cleared (AIS messages no longer received).
•
EFD used to shut down an interface, or bring it back up.
•
Flexible VLAN Tagging for CFM
The Flexible VLAN Tagging for CFM feature ensures that CFM packets are sent with the right VLAN tags
so that they are appropriately handled as a CFM packet by the remote device. When packets are received by
an edge router, they are treated as either CFM packets or data packets, depending on the number of tags in
the header. The system differentiates between CFM packets and data packets based on the number of tags in
the packet, and forwards the packets to the appropriate paths based on the number of tags in the packet.
CFM frames are normally sent with the same VLAN tags as the corresponding customer data traffic on the
interface, as defined by the configured encapsulation and tag rewrite operations. Likewise, received frames
are treated as CFM frames if they have the correct number of tags as defined by the configured encapsulation
and tag rewrite configuration, and are treated as data frames (that is, they are forwarded transparently) if they
have more than this number of tags.
In most cases, this behavior is as desired, since the CFM frames are then treated in exactly the same way as
the data traffic flowing through the same service. However, in a scenario where multiple customer VLANs
are multiplexed over a single multipoint provider service (for example, N:1 bundling), a different behavior
might be desirable.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
36
Page 47
Configuring Ethernet OAM
How to Configure Ethernet OAM
This figure shows an example of a network with multiple VLANS using CFM.
Figure 7: Service Provider Network With Multiple VLANs and CFM
This figure shows a provider's access network, where the S-VLAN tag is used as the service delimiter. PE1
faces the customer, and PE2 is at the edge of the access network facing the core. N:1 bundling is used, so the
interface encapsulation matches a range of C-VLAN tags. This could potentially be the full range, resulting
in all:1 bundling. There is also a use case where only a single C-VLAN is matched, but the S-VLAN is
nevertheless used as the service delimiter—this is more in keeping with the IEEE model, but limits the provider
to 4094 services.
CFM is used in this network with a MEP at each end of the access network, and MIPs on the boxes within
the network (if it is native Ethernet). In the normal case, CFM frames are sent by the up MEP on PE1 with
two VLAN tags, matching the customer data traffic. This means that at the core interfaces and at the MEP on
PE2, the CFM frames are forwarded as if they were customer data traffic, since these interfaces match only
on the S-VLAN tag. So, the CFM frames sent by the MEP on PE1 are not seen by any of the other MPs.
Flexible VLAN tagging changes the encapsulation for CFM frames that are sent and received at Up MEPs.
Flexible VLAN tagging allows the frames to be sent from the MEP on PE1 with just the S-VLAN tag that
represents the provider service. If this is done, the core interfaces will treat the frames as CFM frames and
they will be seen by the MIPs and by the MEP on PE2. Likewise, the MEP on PE1 should handle received
frames with only one tag, as this is what it will receive from the MEP on PE2.
To ensure that CFM packets from Up MEPs are routed to the appropriate paths successfully, tags may be set
to a specific number in a domain service, using the tags command. Currently, tags can only be set to one (1).
How to Configure Ethernet OAM
This section provides these configuration procedures:
Configuring Ethernet Link OAM
Custom EOAM settings can be configured and shared on multiple interfaces by creating an EOAM profile in
Ethernet configuration mode and then attaching the profile to individual interfaces. The profile configuration
does not take effect until the profile is attached to an interface. After an EOAM profile is attached to an
interface, individual EOAM features can be configured separately on the interface to override the profile
settings when desired.
This section describes how to configure an EOAM profile and attach it to an interface in these procedures:
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
37
Page 48
Configuring Ethernet Link OAM
Configuring an Ethernet OAM Profile
Perform these steps to configure an Ethernet OAM profile.
SUMMARY STEPS
configure
1.
ethernet oam profile profile-name
2.
link-monitor
3.
symbol-period window { milliseconds window | symbols window [ thousand | million | billion ]}
4.
symbol-period threshold { ppm [ low threshold ] [ high threshold ] | symbols [ low threshold [ thousand
5.
| million | billion ]] [ high threshold [ thousand | million | billion ]]}
frame window milliseconds window
6.
frame threshold [ low threshold ] [ high threshold ]
7.
frame-period window { milliseconds window | frames window [ thousand | million | billion ]}
8.
frame-period threshold { ppm [ low threshold ] [ high threshold ] | frames [ low threshold [ thousand
9.
| million | billion ]] [ high threshold [ thousand | million | billion ]]}
frame-seconds window milliseconds window
10.
frame-seconds threshold [ low threshold ] [ high threshold ]
11.
exit
12.
mib-retrieval
13.
connection timeout <timeout>
14.
hello-interval {100ms|1s}
15.
mode {active|passive}
16.
require-remote mode {active|passive}
17.
require-remote link-monitoring
18.
require-remote mib-retrieval
19.
action capabilities-conflict {disable | efd | error-disable-interface | log}
20.
action critical-event {disable | error-disable-interface | log}
21.
action discovery-timeout {disable | efd | error-disable-interface | log}
22.
action dying-gasp {disable | error-disable-interface | log}
23.
action high-threshold {disable | error-disable-interface | log}
24.
action remote-loopback { disable | log }
25.
action session-down {disable | efd | error-disable-interface | log}
26.
action session-up { disable | log }
27.
action uni-directional link-fault {disable | efd | error-disable-interface | log}
28.
action wiring-conflict {disable | efd | error-disable-interface | log}
29.
uni-directional link-fault detection
30.
commit
31.
end
32.
Configuring Ethernet OAM
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
38
Page 49
Configuring Ethernet OAM
DETAILED STEPS
Configuring Ethernet Link OAM
PurposeCommand or Action
Step 1
Step 2
Step 3
Step 4
Example:
RP/0/RP0/CPU0:router# configure terminal
ethernet oam profile profile-name
Example:
RP/0/RP0/CPU0:router(config)# ethernet oam
profile Profile_1
Example:
RP/0/RP0/CPU0:router(config-eoam)#
link-monitor
symbol-period window { milliseconds window
| symbols window [ thousand | million | billion
]}
Example:
RP/0/RP0/CPU0:router(config-eoam-lm)#
symbol-period window 60000
Enters global configuration mode.configure
Creates a new Ethernet Operations, Administration and Maintenance
(OAM) profile and enters Ethernet OAM configuration mode.
Enters the Ethernet OAM link monitor configuration mode.link-monitor
(Optional) Configures the window size for an Ethernet OAM
symbol-period error event.
If specified in milliseconds, the range is 1000 to 60000. If not
specified as a multiple of 1 second, the actual window used will be
rounded up to the nearest second, with thresholds scaled accordingly.
If specified in symbols, the range is interface speed dependent (must
be between the maximum number of symbols that could be received
in 1 second and the maximum number of symbols that could be
received in 1 minute). Again the actual window used is rounded up
to the nearest second, with thresholds scaled accordingly.
The default value is 1000 milliseconds.
Step 5
Step 6
symbol-period threshold { ppm [ low threshold
] [ high threshold ] | symbols [ low threshold [
thousand | million | billion ]] [ high threshold [
thousand | million | billion ]]}
Example:
RP/0/RP0/CPU0:router(config-eoam-lm)#
symbol-period threshold symbols low
10000000 high 60000000
frame window milliseconds window
Example:
RP/0/RP0/CPU0:router(config-eoam-lm)#
frame window milliseconds 60
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
(Optional) Configures the thresholds that trigger an Ethernet OAM
symbol-period error event, in symbols or ppm (errors per million
symbols). When using this command at least one of the high and low
thresholds must be specified. If the low threshold is not specified, the
default value is used. If the high threshold is not specified, no action
is performed in response to an event. The high threshold must not be
smaller than the low threshold.
If specified in ppm, the range (for both thresholds) is 1 to 1000000.
If specified in symbols, the range (for both thresholds) is 1 to the
maximum window size in symbols, see Step symbol-period window.
The default low threshold is 1 symbol.
(Optional) Configures the frame window size (in milliseconds) of an
OAM frame error event.
The range is from 1000 to 60000.
The default value is 1000.
39
Page 50
Configuring Ethernet Link OAM
Configuring Ethernet OAM
PurposeCommand or Action
Step 7
Step 8
frame threshold [ low threshold ] [ high
threshold ]
Example:
RP/0/RP0/CPU0:router(config-eoam-lm)#
frame threshold low 10000000 high 60000000
frame-period window { milliseconds window |
frames window [ thousand | million | billion ]}
Example:
RP/0/RP0/CPU0:router(config-eoam-lm)#
frame-period window milliseconds 60000
(Optional) Configures the thresholds (in symbols) that triggers an
Ethernet OAM frame error event. When using this command at least
one of the high and low thresholds must be specified. If the low
threshold is not specified, the default value is used. If the high
threshold is not specified, no action is performed in response to an
event. The high threshold must not be smaller than the low threshold.
The range is from 1 to 60000000.
The default low threshold is 1.
(Optional) Configures the window size for an Ethernet OAM
frame-period error event.
The range is from 100 to 60000, if defined in milliseconds. If the
window is defined as say, 200ms, and the interface could receive at
most say 10000 minimum size frames in 200ms, then the actual
window size used will be the time taken to receive 10000 frames,
rounded up to the nearest second. The thresholds will be scaled
accordingly.
If specified in frames, the range is interface speed dependent, but
must be between the number of minimum size frames that could be
received in 100ms and the number of minimum size frames that could
be received in 1 minute. If the window is defined as 20000 frames,
the actual window size used will be the time taken to receive 20000
frames, rounded up to the nearest second. The thresholds will be
scaled accordingly.
The default value is 1000 milliseconds.
Step 9
Step 10
Step 11
frame-period threshold { ppm [ low threshold
] [ high threshold ] | frames [ low threshold [
thousand | million | billion ]] [ high threshold [
thousand | million | billion ]]}
Example:
RP/0/RP0/CPU0:router(config-eoam-lm)#
frame-period threshold ppm low 100
high 1000000
frame-seconds window milliseconds window
Example:
RP/0/RP0/CPU0:router(config-eoam-lm)#
frame-seconds window milliseconds 900000
frame-seconds threshold [ low threshold ] [ high
threshold ]
(Optional) Configures the thresholds (either in frames or in ppm errors per million frames) that trigger an Ethernet OAM frame-period
error event. When using this command at least one of the high and
low thresholds must be specified. If the low threshold is not specified,
the default value is used. If the high threshold is not specified, no
action is performed in response to an event. The high threshold must
not be smaller than the low threshold.
The range for both thresholds is from 1 to 1000000 if specified in
ppm. If specified in frames, the range is from 1 to the maximum
frame-period window size in frames, see Step frame-period window.
The default low threshold is 1 ppm.
(Optional) Configures the window size (in milliseconds) for the OAM
frame-seconds error event.
The range is 10000 to 900000.
The default value is 6000.
(Optional) Configures the thresholds (in seconds) that trigger a
frame-seconds error event. When using this command at least one of
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
40
Page 51
Configuring Ethernet OAM
Example:
RP/0/RP0/CPU0:router(config-eoam-lm)#
frame-seconds threshold low 3 threshold
high 900
Configuring Ethernet Link OAM
PurposeCommand or Action
the high and low thresholds must be specified. If the low threshold
is not specified, the default value is used. If the high threshold is not
specified, no action is performed in response to an event. The high
threshold must not be smaller than the low threshold.
The range is 1 to 900
The default value is 1.
Step 12
Step 13
Step 14
Step 15
Step 16
Example:
RP/0/RP0/CPU0:router(config-eoam-lm)# exit
mib-retrieval
Example:
RP/0/RP0/CPU0:router(config-eoam)#
mib-retrieval
connection timeout <timeout>
Example:
RP/0/RP0/CPU0:router(config-eoam)#
connection timeout 30
hello-interval {100ms|1s}
Example:
RP/0/RP0/CPU0:router(config-eoam)#
hello-interval 100ms
Exits back to Ethernet OAM mode.exit
Enables MIB retrieval in an Ethernet OAM profile or on an Ethernet
OAM interface.
Configures the connection timeout period for an Ethernet OAM
session. as a multiple of the hello interval.
The range is 2 to 30.
The default value is 5.
Configures the time interval between hello packets for an Ethernet
OAM session. The default is 1 second (1s).
Configures the Ethernet OAM mode. The default is active.mode {active|passive}
Step 17
Step 18
Example:
RP/0/RP0/CPU0:router(config-eoam)# mode
passive
require-remote mode {active|passive}
Example:
RP/0/RP0/CPU0:router(config-eoam)#
require-remote mode active
require-remote link-monitoring
Example:
RP/0/RP0/CPU0:router(config-eoam)#
require-remote link-monitoring
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
Requires that active mode or passive mode is configured on the remote
end before the OAM session becomes active.
Requires that link-monitoring is configured on the remote end before
the OAM session becomes active.
41
Page 52
Configuring Ethernet Link OAM
Configuring Ethernet OAM
PurposeCommand or Action
Step 19
Step 20
Step 21
Step 22
Step 23
require-remote mib-retrieval
Example:
RP/0/RP0/CPU0:router(config-eoam)#
require-remote mib-retrieval
action capabilities-conflict {disable | efd |
error-disable-interface | log}
Example:
RP/0/RP0/CPU0:router(config-eoam)# action
capabilities-conflict efd
action critical-event {disable |
error-disable-interface | log}
Example:
RP/0/RP0/CPU0:router(config-eoam)# action
critical-event error-disable-interface
action discovery-timeout {disable | efd |
error-disable-interface | log}
Example:
RP/0/RP0/CPU0:router(config-eoam)# action
discovery-timeout efd
action dying-gasp {disable |
error-disable-interface | log}
Example:
Requires that MIB-retrieval is configured on the remote end before
the OAM session becomes active.
Specifies the action that is taken on an interface when a
capabilities-conflict event occurs. The default action is to create a
syslog entry.
Specifies the action that is taken on an interface when a critical-event
notification is received from the remote Ethernet OAM peer. The
default action is to create a syslog entry.
Specifies the action that is taken on an interface when a connection
timeout occurs. The default action is to create a syslog entry.
Specifies the action that is taken on an interface when a dying-gasp
notification is received from the remote Ethernet OAM peer. The
default action is to create a syslog entry.
Step 24
Step 25
42
RP/0/RP0/CPU0:router(config-eoam)# action
dying-gasp error-disable-interface
action high-threshold {disable |
error-disable-interface | log}
Specifies the action that is taken on an interface when a high threshold
is exceeded. The default is to take no action when a high threshold
is exceeded.
Example:
RP/0/RP0/CPU0:router(config-eoam)# action
high-threshold error-disable-interface
action remote-loopback { disable | log }
Specifies that no action is taken on an interface when a
remote-loopback event occurs. The default action is to create a syslog
Example:
RP/0/RP0/CPU0:router(config-eoam)# action
remote-loopback disable
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
entry.
Page 53
Configuring Ethernet OAM
Configuring Ethernet Link OAM
PurposeCommand or Action
Step 26
Step 27
Step 28
Step 29
Step 30
action session-down {disable | efd |
error-disable-interface | log}
Example:
RP/0/RP0/CPU0:router(config-eoam)# action
session-down efd
action session-up { disable | log }
Example:
RP/0/RP0/CPU0:router(config-eoam)# action
session-up disable
action uni-directional link-fault {disable | efd |
error-disable-interface | log}
action wiring-conflict {disable | efd |
error-disable-interface | log}
Example:
RP/0/RP0/CPU0:router(config-eoam)# action
session-down efd
uni-directional link-fault detection
Example:
Specifies the action that is taken on an interface when an Ethernet
OAM session goes down.
Specifies that no action is taken on an interface when an Ethernet
OAM session is established. The default action is to create a syslog
entry.
Specifies the action that is taken on an interface when a link-fault
notification is received from the remote Ethernet OAM peer. The
default action is to create a syslog entry.
Note
In Cisco IOS XR Release 4.x, this command replaces the
action link-fault command.
Specifies the action that is taken on an interface when a wiring-conflict
event occurs. The default is to put the interface into error-disable
state.
Enables detection of a local, unidirectional link fault and sends
notification of that fault to an Ethernet OAM peer.
RP/0/RP0/CPU0:router(config-eoam)#
uni-directional link-fault detection
Step 31
commit
Example:
RP/0/RP0/CPU0:router(config-if)# commit
Step 32
Example:
RP/0/RP0/CPU0:router(config-if)# end
Attaching an Ethernet OAM Profile to an Interface
Perform these steps to attach an Ethernet OAM profile to an interface:
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
Saves the configuration changes to the running configuration file and
remains within the configuration session.
Ends the configuration session and exits to the EXEC mode.end
43
Page 54
Configuring Ethernet Link OAM
SUMMARY STEPS
DETAILED STEPS
configure
1.
interface [FastEthernet | HundredGigE| TenGigE] interface-path-id
2.
ethernet oam
3.
profile profile-name
4.
commit
5.
end
6.
PurposeCommand or Action
Configuring Ethernet OAM
Step 1
Step 2
Step 3
Step 4
Step 5
Example:
RP/0/RP0/CPU0:router# configure terminal
interface [FastEthernet | HundredGigE| TenGigE]
interface-path-id
Example:
RP/0/RP0/CPU0:router(config)# interface
TenGigE 0/1/0/0
ethernet oam
Example:
RP/0/RP0/CPU0:router(config-if)# ethernet
oam
profile profile-name
Example:
RP/0/RP0/CPU0:router(config-if-eoam)# profile
Profile_1
commit
Example:
Enters global configuration mode.configure
Enters interface configuration mode and specifies the Ethernet
interface name and notation rack/slot/module/port.
Note
The example indicates an 8-port 10-Gigabit
•
Ethernet interface in modular services card slot
1.
Enables Ethernet OAM and enters interface Ethernet OAM
configuration mode.
Attaches the specified Ethernet OAM profile (profile-name),
and all of its configuration, to the interface.
Saves the configuration changes to the running configuration
file and remains within the configuration session.
Step 6
44
RP/0/RP0/CPU0:router(config-if)# commit
Ends the configuration session and exits to the EXEC mode.end
Example:
RP/0/RP0/CPU0:router(config-if)# end
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
Page 55
Configuring Ethernet OAM
Configuring Ethernet Link OAM
Configuring Ethernet OAM at an Interface and Overriding the Profile Configuration
Using an EOAM profile is an efficient way of configuring multiple interfaces with a common EOAM
configuration. However, if you want to use a profile but also change the behavior of certain functions for a
particular interface, then you can override the profile configuration. To override certain profile settings that
are applied to an interface, you can configure that command in interface Ethernet OAM configuration mode
to change the behavior for that interface.
In some cases, only certain keyword options are available in interface Ethernet OAM configuration due to
the default settings for the command. For example, without any configuration of the action commands, several
forms of the command have a default behavior of creating a syslog entry when a profile is created and applied
to an interface. Therefore, the log keyword is not available in Ethernet OAM configuration for these commands
in the profile because it is the default behavior. However, the log keyword is available in Interface Ethernet
OAM configuration if the default is changed in the profile configuration so you can retain the action of creating
a syslog entry for a particular interface.
To see all of the default Ethernet OAM configuration settings, see the Verifying the Ethernet OAM
Configuration.
To configure Ethernet OAM settings at an interface and override the profile configuration, perform these
steps:
SUMMARY STEPS
DETAILED STEPS
Step 1
Example:
RP/0/RP0/CPU0:router# configure terminal
Step 2
interface [HundredGigE | TenGigE]
interface-path-id
Example:
RP/0/RP0/CPU0:router(config)# interface
TenGigE 0/1/0/0
configure
1.
interface [HundredGigE | TenGigE] interface-path-id
2.
ethernet oam
3.
interface-Ethernet-OAM-command RP/0/RP0/CPU0:router(config-if-eoam)# action capabilities-conflict
4.
error-disable-interface
commit
5.
end
6.
PurposeCommand or Action
Enters global configuration mode.configure
Enters interface configuration mode and specifies the Ethernet
interface name and notation rack/slot/module/port.
Note
The example indicates an 8-port 10-Gigabit Ethernet
•
interface in modular services card slot 1.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
45
Page 56
Configuring Ethernet Link OAM
Configuring Ethernet OAM
PurposeCommand or Action
Step 3
Step 4
Step 5
Step 6
ethernet oam
Example:
RP/0/RP0/CPU0:router(config-if)# ethernet
oam
interface-Ethernet-OAM-command
RP/0/RP0/CPU0:router(config-if-eoam)# action
capabilities-conflict error-disable-interface
commit
Example:
RP/0/RP0/CPU0:router(config-if)# commit
Example:
RP/0/RP0/CPU0:router(config-if)# end
Enables Ethernet OAM and enters interface Ethernet OAM
configuration mode.
Configures a setting for an Ethernet OAM configuration command
and overrides the setting for the profile configuration, where
interface-Ethernet-OAM-command is one of the supported
commands on the platform in interface Ethernet OAM
configuration mode.
Saves the configuration changes to the running configuration file
and remains within the configuration session.
Ends the configuration session and exits to the EXEC mode.end
Verifying the Ethernet OAM Configuration
Use the show ethernet oam configuration command to display the values for the Ethernet OAM configuration
for a particular interface, or for all interfaces. The following example shows the default values for Ethernet
OAM settings:
RP/0/RP0/CPU0:router# show ethernet oam configuration
Thu Aug 5 22:07:06.870 DST
GigabitEthernet0/4/0/0:
Hello interval: 1s
Link monitoring enabled: Y
Remote loopback enabled: N
Mib retrieval enabled: N
Uni-directional link-fault detection enabled: N
Configured mode: Active
Connection timeout: 5
Symbol period window: 0
Symbol period low threshold: 1
Symbol period high threshold: None
Frame window: 1000
Frame low threshold: 1
Frame high threshold: None
Frame period window: 1000
Frame period low threshold: 1
Frame period high threshold: None
Frame seconds window: 60000
Frame seconds low threshold: 1
Frame seconds high threshold: None
High threshold action: None
Link fault action: Log
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
46
Page 57
Configuring Ethernet OAM
Dying gasp action: Log
Critical event action: Log
Discovery timeout action: Log
Capabilities conflict action: Log
Wiring conflict action: Error-Disable
Session up action: Log
Session down action: Log
Remote loopback action: Log
Require remote mode: Ignore
Require remote MIB retrieval: N
Require remote loopback support: N
Require remote link monitoring: N
Configuring Ethernet CFM
To configure Ethernet CFM, perform the following tasks:
Configuring a CFM Maintenance Domain
To configure a CFM maintenance domain, perform the following steps:
Configuring Ethernet CFM
SUMMARY STEPS
DETAILED STEPS
Step 1
Example:
RP/0/RP0/CPU0:router# configure
Step 2
Example:
RP/0/RP0/CPU0:router(config)#
ethernet cfm
Step 3
domain domain-name level level-value [id
[null] [dns DNS-name] [mac H.H.H] [string
string] ]
Example:
RP/0/RP0/CPU0:router(config-cfm)#
configure
1.
ethernet cfm
2.
domain domain-name level level-value [id [null] [dns DNS-name] [mac H.H.H] [string string] ]
3.
traceroute cache hold-time minutes size entries
4.
end or commit
5.
PurposeCommand or Action
Enters global configuration mode.configure
Enters Ethernet Connectivity Fault Management (CFM) configuration mode.ethernet cfm
Creates and names a container for all domain configurations and enters CFM
domain configuration mode.
The level must be specified.
The id is the maintenance domain identifier (MDID) and is used as the first
part of the maintenance association identifier (MAID) in CFM frames. If
the MDID is not specified, the domain name is used as the MDID by default.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
47
Page 58
Configuring Ethernet CFM
Step 4
Step 5
domain Domain_One level 1 id string
D1
traceroute cache hold-time minutes size
entries
Example:
RP/0/RP0/CPU0:router(config-cfm)#
traceroute cache hold-time 1 size
3000
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn)#
commit
Configuring Ethernet OAM
PurposeCommand or Action
(Optional) Sets the maximum limit of traceroute cache entries or the
maximum time limit to hold the traceroute cache entries. The default is 100
minutes and 100 entries.
Saves configuration changes.end or commit
When you use the end command, the system prompts you to commit
•
changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
Entering yes saves configuration changes to the running configuration
•
file, exits the configuration session, and returns the router to EXEC
mode.
Entering no exits the configuration session and returns the router to
•
EXEC mode without committing the configuration changes.
Entering cancel leaves the router in the current configuration session
•
without exiting or committing the configuration changes.
Use the commit command to save the configuration changes to the
•
running configuration file and remain within the configuration session.
Configuring Services for a CFM Maintenance Domain
You can configure up to 32000 CFM services for a maintenance domain. To configure services for a CFM
maintenance domain, perform the following steps:
SUMMARY STEPS
configure
1.
ethernet cfm
2.
domain domain-name level level-value [id [null] [dns DNS-name] [mac H.H.H] [string string] ]
3.
service service-name {down-meps | xconnect group xconnect-group-name p2p xconnect-name}[id
4.
[icc-based icc-string umc-string] | [ [number number]
end or commit
5.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
48
Page 59
Configuring Ethernet OAM
DETAILED STEPS
Configuring Ethernet CFM
PurposeCommand or Action
Step 1
Step 2
Step 3
Step 4
Example:
RP/0/RP0/CPU0:router# configure
Example:
RP/0/RP0/CPU0:router(config)# ethernet
cfm
domain domain-name level level-value [id [null]
[dns DNS-name] [mac H.H.H] [string string] ]
Example:
RP/0/RP0/CPU0:router(config-cfm)# domain
Domain_One level 1 id string D1
service service-name {down-meps | xconnect
group xconnect-group-name
p2p xconnect-name}[id [icc-based icc-string
umc-string] | [ [number number]
Example:
Enters global configuration mode.configure
Enters Ethernet CFM configuration mode.ethernet cfm
Creates and names a container for all domain configurations at a specified
maintenance level, and enters CFM domain configuration mode.
The id is the maintenance domain identifier (MDID) and is used as the
first part of the maintenance association identifier (MAID) in CFM
frames. If the MDID is not specified, the domain name is used as the
MDID by default.
Configures and associates a service with the domain and enters CFM
domain service configuration mode. You can specify that the service is
used only for down MEPs, or associate the service with a bridge domain
where MIPs and up MEPs will be created.
The id sets the short MA name.
Step 5
RP/0/RP0/CPU0:router(config-cfm-dmn)#
service xconnect group X1
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)#
commit
Saves configuration changes.end or commit
When you use the end command, the system prompts you to
•
commit changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
Entering yes saves configuration changes to the running
•
configuration file, exits the configuration session, and returns the
router to EXEC mode.
Entering no exits the configuration session and returns the router
•
to EXEC mode without committing the configuration changes.
Entering cancel leaves the router in the current configuration
•
session without exiting or committing the configuration changes.
Use the commit command to save the configuration changes to
•
the running configuration file and remain within the configuration
session.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
49
Page 60
Configuring Ethernet CFM
PurposeCommand or Action
Enabling and Configuring Continuity Check for a CFM Service
To configure Continuity Check for a CFM service, complete the following steps:
SUMMARY STEPS
configure
1.
ethernet cfm
2.
domain domain-name level level-value [id [null] [dns DNS-name] [mac H.H.H] [string string] ]
3.
service service-name {down-meps | xconnect group xconnect-group-name p2p xconnect-name}[id
4.
[icc-based icc-string umc-string] | [ [number number]
continuity-check interval time [loss-threshold threshold]
5.
continuity-check archive hold-time minutes
6.
continuity-check loss auto-traceroute
7.
end or commit
8.
Configuring Ethernet OAM
DETAILED STEPS
Step 1
Example:
RP/0/RP0/CPU0:router# configure
Step 2
Step 3
ethernet cfm
Example:
RP/0/RP0/CPU0:router(config)# ethernet cfm
domain domain-name level level-value [id [null]
[dns DNS-name] [mac H.H.H] [string string] ]
Example:
RP/0/RP0/CPU0:router(config-cfm)# domain
Domain_One level 1 id string D1
Step 4
service service-name {down-meps | xconnect
group xconnect-group-name
PurposeCommand or Action
Enters global configuration mode.configure
Enters Ethernet Connectivity Fault Management (CFM) configuration
mode.
Creates and names a container for all domain configurations and enters
the CFM domain configuration mode.
The level must be specified.
The id is the maintenance domain identifier (MDID) and is used as
the first part of the maintenance association identifier (MAID) in CFM
frames. If the MDID is not specified, the domain name is used as the
MDID by default.
Configures and associates a service with the domain and enters CFM
domain service configuration mode. You can specify that the service
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
50
Page 61
Configuring Ethernet OAM
p2p xconnect-name}[id [icc-based icc-string
umc-string] | [ [number number]
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn)#
service xconnect group X1
Step 5
continuity-check interval time [loss-threshold
threshold]
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)#
continuity-check interval 100m
loss-threshold 10
Step 6
continuity-check archive hold-time minutes
Example:
Configuring Ethernet CFM
PurposeCommand or Action
is used only for down MEPs, or associate the service with a bridge
domain or xconnect where MIPs and up MEPs will be created.
The id sets the short MA name.
(Optional) Enables Continuity Check and specifies the time interval
at which CCMs are transmitted or to set the threshold limit for when
a MEP is declared down.
(Optional) Configures how long information about peer MEPs is stored
after they have timed out.
Step 7
Step 8
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)#
continuity-check archive hold-time 100
continuity-check loss auto-traceroute
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)#
continuity-check loss auto-traceroute
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)#
commit
(Optional) Configures automatic triggering of a traceroute when a
MEP is declared down.
Saves configuration changes.end or commit
When you use the end command, the system prompts you to
•
commit changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
Entering yes saves configuration changes to the running
•
configuration file, exits the configuration session, and returns
the router to EXEC mode.
Entering no exits the configuration session and returns the router
•
to EXEC mode without committing the configuration changes.
Entering cancel leaves the router in the current configuration
•
session without exiting or committing the configuration changes.
Use the commit command to save the configuration changes to
•
the running configuration file and remain within the configuration
session.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
51
Page 62
Configuring Ethernet CFM
Configuring Automatic MIP Creation for a CFM Service
For more information about the algorithm for creating MIPs, see the MIP Creation section.
To configure automatic MIP creation for a CFM service, complete the following steps:
SUMMARY STEPS
configure
1.
ethernet cfm
2.
domain domain-name level level-value [id [null] [dns DNS-name] [mac H.H.H] [string string] ]
3.
service service-name {down-meps | xconnect group xconnect-group-name p2p xconnect-name}[id
4.
[icc-basedicc-string umc-string] | [number number]
mip auto-create {all | lower-mep-only} {ccm-learning}
5.
end or commit
6.
DETAILED STEPS
Configuring Ethernet OAM
Step 1
Step 2
Step 3
Step 4
Example:
RP/0/RP0/CPU0:router# configure
ethernet cfm
Example:
RP/0/RP0/CPU0:router# ethernet cfm
domain domain-name level level-value [id [null]
[dns DNS-name] [mac H.H.H] [string string] ]
Example:
RP/0/RP0/CPU0:router(config-cfm)# domain
Domain_One level 1 id string D1
service service-name {down-meps | xconnect
group xconnect-group-name
p2p xconnect-name}[id [icc-basedicc-string
umc-string] | [number number]
Example:
PurposeCommand or Action
Enters global configuration mode.configure
Enters the Ethernet Connectivity Fault Management (CFM) configuration
mode.
Creates and names a container for all domain configurations and enters
the CFM domain configuration mode.
The level must be specified. The only supported option is id [null] for
less than 1min interval MEPS.
The id is the maintenance domain identifier (MDID) and is used as the
first part of the maintenance association identifier (MAID) in CFM
frames. If the MDID is not specified, the domain name is used as the
MDID by default.
Configures and associates a service with the domain and enters CFM
domain service configuration mode. You can specify that the service is
used only for down MEPs, or associate the service with a bridge domain
where MIPs and up MEPs will be created.
The id sets the short MA name.
RP/0/RP0/CPU0:router(config-cfm-dmn)#
service xconnect group X1
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
52
Page 63
Configuring Ethernet OAM
Configuring Ethernet CFM
PurposeCommand or Action
Step 5
Step 6
mip auto-create {all | lower-mep-only}
{ccm-learning}
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)#
mip auto-create all ccm-learning
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)#
commit
(Optional) Enables the automatic creation of MIPs in a bridge domain.
ccm-learning option enables CCM learning for MIPs created in this
service. This must be used only in services with a relatively long CCM
interval of at least 100 ms. CCM learning at MIPs is disabled by default.
Saves configuration changes.end or commit
When you use the end command, the system prompts you to
•
commit changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
Entering yes saves configuration changes to the running
•
configuration file, exits the configuration session, and returns the
router to EXEC mode.
Entering no exits the configuration session and returns the router
•
to EXEC mode without committing the configuration changes.
Entering cancel leaves the router in the current configuration
•
session without exiting or committing the configuration changes.
Use the commit command to save the configuration changes to
•
the running configuration file and remain within the configuration
session.
Configuring Cross-Check on a MEP for a CFM Service
To configure cross-check on a MEP for a CFM service and specify the expected set of MEPs, complete the
following steps:
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
53
Page 64
Configuring Ethernet CFM
SUMMARY STEPS
DETAILED STEPS
Configuring Ethernet OAM
configure
1.
ethernet cfm
2.
domain domain-name level level-value [id [null] [dns DNS-name] [mac H.H.H] [string string] ]
3.
service service-name {bridge group bridge-domain-group bridge-domain bridge-domain-name |
4.
down-meps | xconnect group xconnect-group-name p2p xconnect-name}[id [icc-based icc-string
umc-string] | [string text] | [number number] | [vlan-id id-number] | [vpn-id oui-vpnid]]
mep crosscheck
5.
mep-id mep-id-number [mac-address mac-address]
6.
end or commit
7.
PurposeCommand or Action
Step 1
Step 2
Step 3
Step 4
Example:
RP/0/RP0/CPU0:router# configure
ethernet cfm
Example:
RP/0/RP0/CPU0:router# ethernet cfm
domain domain-name level level-value [id [null]
[dns DNS-name] [mac H.H.H] [string string] ]
Example:
RP/0/RP0/CPU0:router(config-cfm)# domain
Domain_One level 1 id string D1
service service-name {bridge group
bridge-domain-group bridge-domain
bridge-domain-name | down-meps | xconnect
group xconnect-group-name
p2p xconnect-name}[id [icc-based icc-string
umc-string] | [string text] | [number number] |
[vlan-id id-number] | [vpn-id oui-vpnid]]
Enters global configuration mode.configure
Enters the Ethernet Connectivity Fault Management (CFM)
configuration mode.
Creates and names a container for all domain configurations and enters
the CFM domain configuration mode.
The level must be specified.
The id is the maintenance domain identifier (MDID) and is used as
the first part of the maintenance association identifier (MAID) in CFM
frames. If the MDID is not specified, the domain name is used as the
MDID by default.
Configures and associates a service with the domain and enters CFM
domain service configuration mode. You can specify that the service
is used only for down MEPs, or associate the service with a bridge
domain or xconnect where MIPs and up MEPs will be created.
The id sets the short MA name.
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn)#
service Bridge_Service bridge group BD1
bridge-domain B1
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
54
Page 65
Configuring Ethernet OAM
Configuring Ethernet CFM
PurposeCommand or Action
Step 5
Step 6
Step 7
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)#
mep crosscheck mep-id 10
mep-id mep-id-number [mac-address
mac-address]
Example:
RP/0/RP0/CPU0:router(config-cfm-xcheck)#
mep-id 10
Example:
RP/0/RP0/CPU0:router(config-cfm-xcheck)#
commit
Enters CFM MEP crosscheck configuration mode.mep crosscheck
Enables cross-check on a MEP.
Note
Repeat this command for every MEP that you want
•
included in the expected set of MEPs for cross-check.
Saves configuration changes.end or commit
When you use the end command, the system prompts you to
•
commit changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
Entering yes saves configuration changes to the running
•
configuration file, exits the configuration session, and returns
the router to EXEC mode.
Configuring Other Options for a CFM Service
To configure other options for a CFM service, complete the following steps:
Entering no exits the configuration session and returns the router
•
to EXEC mode without committing the configuration changes.
Entering cancel leaves the router in the current configuration
•
session without exiting or committing the configuration changes.
Use the commit command to save the configuration changes to
•
the running configuration file and remain within the
configuration session.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
55
Page 66
Configuring Ethernet CFM
SUMMARY STEPS
DETAILED STEPS
Configuring Ethernet OAM
configure
1.
ethernet cfm
2.
domain domain-name level level-value [id [null] [dns DNS-name] [mac H.H.H] [string string] ]
3.
service service-name {bridge group bridge-domain-group bridge-domain bridge-domain-name |
4.
down-meps | xconnect group xconnect-group-name p2p xconnect-name}[id [icc-based icc-string
umc-string] | [string text] | [number number] | [vlan-id id-number] | [vpn-id oui-vpnid]]
maximum-meps number
5.
log {ais|continuity-check errors|continuity-check mep changes|crosscheck errors|efd}
6.
end or commit
7.
PurposeCommand or Action
Step 1
Step 2
Step 3
Step 4
Example:
RP/0/RP0/CPU0:router# configure
ethernet cfm
Example:
RP/0/RP0/CPU0:router# ethernet cfm
domain domain-name level level-value [id [null]
[dns DNS-name] [mac H.H.H] [string string] ]
Example:
RP/0/RP0/CPU0:router(config-cfm)# domain
Domain_One level 1 id string D1
service service-name {bridge group
bridge-domain-group bridge-domain
bridge-domain-name | down-meps | xconnect
group xconnect-group-name
p2p xconnect-name}[id [icc-based icc-string
umc-string] | [string text] | [number number] |
[vlan-id id-number] | [vpn-id oui-vpnid]]
Enters global configuration mode.configure
Enters the Ethernet Connectivity Fault Management (CFM)
configuration mode.
Creates and names a container for all domain configurations and
enters the CFM domain configuration mode.
The level must be specified.
The id is the maintenance domain identifier (MDID) and is used as
the first part of the maintenance association identifier (MAID) in
CFM frames. If the MDID is not specified, the domain name is used
as the MDID by default.
Configures and associates a service with the domain and enters CFM
domain service configuration mode. You can specify that the service
is used only for down MEPs, or associate the service with a bridge
domain or xconnect where MIPs and up MEPs will be created.
The id sets the short MA name.
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn)#
service Bridge_Service bridge group BD1
bridge-domain B1
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
56
Page 67
Configuring Ethernet OAM
Configuring Ethernet CFM
PurposeCommand or Action
Step 5
Step 6
Step 7
maximum-meps number
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)#
maximum-meps 1000
mep changes|crosscheck errors|efd}
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)#
log continuity-check errors
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)#
commit
(Optional) Configures the maximum number (2 to 8190) of MEPs
across the network, which limits the number of peer MEPs recorded
in the database.
(Optional) Enables logging of certain types of events.log {ais|continuity-check errors|continuity-check
Saves configuration changes.end or commit
When you use the end command, the system prompts you to
•
commit changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
Entering yes saves configuration changes to the running
•
configuration file, exits the configuration session, and returns
the router to EXEC mode.
Entering no exits the configuration session and returns the router
•
to EXEC mode without committing the configuration changes.
Entering cancel leaves the router in the current configuration
•
session without exiting or committing the configuration changes.
Use the commit command to save the configuration changes
•
to the running configuration file and remain within the
configuration session.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
57
Page 68
Configuring Ethernet CFM
Configuring CFM MEPs
SUMMARY STEPS
configure
1.
interface {HundredGigE | TenGigE} interface-path-id
2.
interface {HundredGigE | TenGigE | Bundle-Ether} interface-path-id.subinterface
3.
vrf vrf-name
4.
interface {HundredGigE | TenGigE} interface-path-id
5.
ethernet cfm
6.
mep domain domain-name service service-name mep-id id-number
7.
cos cos
8.
end or commit
9.
Configuring Ethernet OAM
DETAILED STEPS
Step 1
Example:
RP/0/RP0/CPU0:router# configure
Step 2
interface {HundredGigE | TenGigE}
interface-path-id
Example:
RP/0/RP0/CPU0:router(config)# interface
TenGigE 0/0/0/1
Step 3
interface {HundredGigE | TenGigE |
Bundle-Ether} interface-path-id.subinterface
Example:
RP/0/RP0/CPU0:router(config)# interface
TenGigE 0/0/0/1
PurposeCommand or Action
Enters global configuration mode.configure
Type of Ethernet interface on which you want to create a MEP. Enter
HundredGigE or TenGigE and the physical interface or virtual interface.
Note
Use the show interfaces command to see a list of all
•
interfaces currently configured on the router.
For more information about the syntax for the router, use the question
mark (?) online help function.
Type of Ethernet interface on which you want to create a MEP. Enter
HundredGigE, TenGigE, or Bundle-Ether and the physical interface
or virtual interface followed by the subinterface path ID.
Naming notation is interface-path-id.subinterface. The period in front
of the subinterface value is required as part of the notation.
For more information about the syntax for the router, use the question
mark (?) online help function.
Step 4
Step 5
58
Configures a VRF instance and enters VRF configuration mode.vrf vrf-name
Example:
RP/0/RP0/CPU0:router(config-if)# vrf
vrf_A
interface {HundredGigE | TenGigE}
interface-path-id
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
Type of Ethernet interface on which you want to create a MEP. Enter
HundredGigE or TenGigE and the physical interface or virtual interface.
Page 69
Configuring Ethernet OAM
Example:
RP/0/RP0/CPU0:router(config)# interface
TenGigE 0/0/0/1
Configuring Ethernet CFM
PurposeCommand or Action
Note
Use the show interfaces command to see a list of all
•
interfaces currently configured on the router.
For more information about the syntax for the router, use the question
mark (?) online help function.
Step 6
Step 7
Step 8
Step 9
Example:
RP/0/RP0/CPU0:router(config-if)# ethernet
cfm
mep domain domain-name service
service-name mep-id id-number
Example:
RP/0/RP0/CPU0:router(config-if-cfm)# mep
domain Dm1 service Sv1 mep-id 1
cos cos
Example:
RP/0/RP0/CPU0:router(config-if-cfm-mep)#
cos 7
Example:
RP/0/RP0/CPU0:router(config-if-cfm-mep)#
commit
Enters interface Ethernet CFM configuration mode.ethernet cfm
Creates a maintenance end point (MEP) on an interface and enters
interface CFM MEP configuration mode.
(Optional) Configures the class of service (CoS) (from 0 to 7) for all
CFM packets generated by the MEP on an interface. If not configured,
the CoS is inherited from the Ethernet interface.
Note
For Ethernet interfaces, the CoS is carried as a field in the VLAN
tag. Therefore, CoS only applies to interfaces where packets are
sent with VLAN tags. If the cos (CFM) command is executed
for a MEP on an interface that does not have a VLAN
encapsulation configured, it will be ignored.
Saves configuration changes.end or commit
When you use the end command, the system prompts you to commit
•
changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
Entering yes saves configuration changes to the running
•
configuration file, exits the configuration session, and returns the
router to EXEC mode.
Entering no exits the configuration session and returns the router
•
to EXEC mode without committing the configuration changes.
Entering cancel leaves the router in the current configuration session
•
without exiting or committing the configuration changes.
Use the commit command to save the configuration changes to the
•
running configuration file and remain within the configuration
session.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
59
Page 70
Configuring Ethernet CFM
Configuring Y.1731 AIS
This section has the following step procedures:
Configuring AIS in a CFM Domain Service
Use the following procedure to configure Alarm Indication Signal (AIS) transmission for a CFM domain
service and configure AIS logging.
SUMMARY STEPS
configure
1.
ethernet cfm
2.
domain name level level
3.
service name bridge group name bridge-domain name
4.
service name xconnect group xconnect-group-name p2p xconnect-name
5.
ais transmission [interval {1s|1m}][cos cos]
6.
log ais
7.
end or commit
8.
Configuring Ethernet OAM
DETAILED STEPS
Step 1
Example:
RP/0/RP0/CPU0:router# configure
Step 2
Example:
RP/0/RP0/CPU0:router(config)# ethernet cfm
Step 3
domain name level level
Example:
RP/0/RP0/CPU0:router(config-cfm)# domain D1
level 1
PurposeCommand or Action
Enters global configuration mode.configure
Enters Ethernet CFM global configuration mode.ethernet cfm
Specifies the domain and domain level.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
60
Page 71
Configuring Ethernet OAM
Configuring Ethernet CFM
PurposeCommand or Action
Step 4
Step 5
Step 6
Step 7
Step 8
service name bridge group name bridge-domain name
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn)# service
S1 bridge group BG1 bridge-domain BD2
service name xconnect group xconnect-group-name
p2p xconnect-name
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn)# service
S1 bridge group BG1 bridge-domain BD2
ais transmission [interval {1s|1m}][cos cos]
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)# ais
transmission interval 1m cos 7
log ais
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)# log
ais
Specifies the service, bridge group, and bridge domain.
Specifies the service and cross-connect group and name.
Configures Alarm Indication Signal (AIS) transmission for a
Connectivity Fault Management (CFM) domain service.
Configures AIS logging for a Connectivity Fault Management
(CFM) domain service to indicate when AIS or LCK packets
are received.
Saves configuration changes.end or commit
Example:
RP/0/RP0/CPU0:router(config-sla-prof-stat-cfg)#
commit
When you issue the end command, the system prompts
•
you to commit changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
Entering yes saves configuration changes to the running
•
configuration file, exits the configuration session, and
returns the router to EXEC mode.
Entering no exits the configuration session and returns
•
the router to EXEC mode without committing the
configuration changes.
Entering cancel leaves the router in the current
•
configuration session without exiting or committing the
configuration changes.
Use the commit command to save the configuration
•
changes to the running configuration file and remain
within the configuration session.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
61
Page 72
Configuring Ethernet CFM
Configuring AIS on a CFM Interface
To configure AIS on a CFM interface, perform the following steps:
SUMMARY STEPS
configure
1.
interface gigabitethernet interface-path-id
2.
ethernet cfm
3.
ais transmission up interval 1m cos cos
4.
end or commit
5.
DETAILED STEPS
Configuring Ethernet OAM
Step 1
Step 2
Step 3
Step 4
Step 5
Example:
RP/0/RP0/CPU0:router# configure
interface gigabitethernet interface-path-id
Example:
RP/0/RP0/CPU0:router# interface TenGigE 0/0/0/2
Example:
RP/0/RP0/CPU0:router(config)# ethernet cfm
ais transmission up interval 1m cos cos
Example:
RP/0/RP0/CPU0:router(config-if-cfm)# ais
transmission up interval 1m cos 7
PurposeCommand or Action
Enters global configuration mode.configure
Enters interface configuration mode.
Enters Ethernet CFM interface configuration mode.ethernet cfm
Configures Alarm Indication Signal (AIS) transmission on a
Connectivity Fault Management (CFM) interface.
Saves configuration changes.end or commit
When you issue the end command, the system prompts
Example:
RP/0/RP0/CPU0:router(config-sla-prof-stat-cfg)#
commit
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
62
•
you to commit changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
Page 73
Configuring Ethernet OAM
Configuring Ethernet CFM
PurposeCommand or Action
Entering yes saves configuration changes to the running
•
configuration file, exits the configuration session, and
returns the router to EXEC mode.
Entering no exits the configuration session and returns the
•
router to EXEC mode without committing the
configuration changes.
Entering cancel leaves the router in the current
•
configuration session without exiting or committing the
configuration changes.
Use the commit command to save the configuration
•
changes to the running configuration file and remain within
the configuration session.
Configuring Flexible VLAN Tagging for CFM
Use this procedure to set the number of tags in CFM packets in a CFM domain service.
SUMMARY STEPS
configure
1.
ethernet cfm
2.
domain name level level
3.
service name bridge group name bridge-domain name
4.
tags number
5.
end or commit
6.
DETAILED STEPS
Step 1
Example:
RP/0/RP0/CPU0:router# configure
Step 2
PurposeCommand or Action
Enters global configuration mode.configure
Enters Ethernet CFM global configuration mode.ethernet cfm
Example:
RP/0/RP0/CPU0:router(config)# ethernet
cfm
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
63
Page 74
Configuring Ethernet CFM
Configuring Ethernet OAM
PurposeCommand or Action
Step 3
Step 4
Step 5
Step 6
domain name level level
Example:
RP/0/RP0/CPU0:router(config-cfm)# domain
D1 level 1
service name bridge group name bridge-domain
name
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn)#
service S2 bridge group BG1 bridge-domain
BD2
tags number
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)#
tags 1
Example:
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)#
commit
Specifies the domain and domain level.
Specifies the service, bridge group, and bridge domain.
Specifies the number of tags in CFM packets. Currently, the only
valid value is 1.
Saves configuration changes.end or commit
When you issue the end command, the system prompts you to
•
commit changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
Verifying the CFM Configuration
To verify the CFM configuration, use one or more of the following commands:
Entering yes saves configuration changes to the running
•
configuration file, exits the configuration session, and returns
the router to EXEC mode.
Entering no exits the configuration session and returns the router
•
to EXEC mode without committing the configuration changes.
Entering cancel leaves the router in the current configuration
•
session without exiting or committing the configuration changes.
Use the commit command to save the configuration changes
•
to the running configuration file and remain within the
configuration session.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
64
Page 75
Configuring Ethernet OAM
Configuring Ethernet CFM
Note
Troubleshooting Tips
SUMMARY STEPS
show ethernet cfm configuration-errors [domain
domain-name] [interface interface-path-id ]
Displays information about errors that are preventing
configured CFM operations from becoming active, as
well as any warnings that have occurred.
Displays a list of local maintenance points.show ethernet cfm local maintenance-points
domain name [service name] | interface type
interface-path-id] [mep | mip]
After you configure CFM, the error message, cfmd[317]: %L2-CFM-5-CCM_ERROR_CCMS_MISSED
: Some received CCMs have not been counted by the CCM error counters, may display. This error message
does not have any functional impact and does not require any action from you.
To troubleshoot problems within the CFM network, perform these steps:
To verify connectivity to a problematic MEP, use the ping ethernet cfm command as shown in this
1.
example:
If the results of the ping ethernet cfm command show a problem with connectivity to the peer MEP, use
2.
the traceroute ethernet cfm command to help further isolate the location of the problem as shown in the
following example:
DETAILED STEPS
Step 1
To verify connectivity to a problematic MEP, use the ping ethernet cfm command as shown in this example:
RP/0/RP0/CPU0:router# ping ethernet cfm domain D1 service S1 mep-id 16 source
interface TenGigE 0/0/0/1
Type escape sequence to abort.
Sending 5 CFM Loopbacks, timeout is 2 seconds -
Domain foo (level 2), Service foo
Source: MEP ID 1, interface TenGigE0/0/0/1
Target: 0001.0002.0003 (MEP ID 16):
Running (5s) ...
Success rate is 60.0 percent (3/5), round-trip min/avg/max = 1251/1349/1402 ms
Out-of-sequence: 0.0 percent (0/3)
Bad data: 0.0 percent (0/3)
Received packet rate: 1.4 pps
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
65
Page 76
Configuration Examples for Ethernet OAM
Configuring Ethernet OAM
Step 2
If the results of the ping ethernet cfm command show a problem with connectivity to the peer MEP, use the traceroute
ethernet cfm command to help further isolate the location of the problem as shown in the following example:
RP/0/RP0/CPU0:router# traceroute ethernet cfm domain D1 service S1 mep-id 16 source interface TenGigE 0/0/0/2
Traceroutes in domain D1 (level 4), service S1
Source: MEP-ID 1, interface TenGigE0/0/0/2
================================================================================
Traceroute at 2009-05-18 12:09:10 to 0001.0203.0402,
TTL 64, Trans ID 2:
Hop Hostname/Last Ingress MAC/name Egress MAC/Name Relay
--- ------------------------ ---------------------- ---------------------- -----
1 ios 0001.0203.0400 [Down] FDB
0000-0001.0203.0400 TenGigE0/0/0/2
2 abc 0001.0203.0401 [Ok] FDB
ios Not present
3 bcd 0001.0203.0402 [Ok] Hit
abc TenGigE0/0
Replies dropped: 0
If the target was a MEP, verify that the last hop shows “Hit” in the Relay field to confirm connectivity to the peer MEP.
If the Relay field contains “MPDB” for any of the hops, then the target MAC address was not found in the bridge MAC
learning table at that hop, and the result is relying on CCM learning. This result can occur under normal conditions, but
it can also indicate a problem. If you used the ping ethernet cfm command before using the traceroute ethernet cfm
command, then the MAC address should have been learned. If “MPDB” is appearing in that case, then this indicates a
problem at that point in the network.
Configuration Examples for Ethernet OAM
This section provides the following configuration examples:
Configuration Examples for EOAM Interfaces
This section provides the following configuration examples:
Configuring an Ethernet OAM Profile Globally: Example
This example shows how to configure an Ethernet OAM profile globally:
configure terminal
ethernet oam profile Profile_1
link-monitor
symbol-period window 60000
symbol-period threshold low 10000000 high 60000000
frame window 60
frame threshold low 10000000 high 60000000
frame-period window 60000
frame-period threshold low 100 high 12000000
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
66
Page 77
Configuring Ethernet OAM
Configuration Examples for EOAM Interfaces
frame-seconds window 900000
frame-seconds threshold 3 threshold 900
exit
mib-retrieval
connection timeout 30
require-remote mode active
require-remote link-monitoring
require-remote mib-retrieval
action dying-gasp error-disable-interface
action critical-event error-disable-interface
action discovery-timeout error-disable-interface
action session-down error-disable-interface
action capabilities-conflict error-disable-interface
action wiring-conflict error-disable-interface
action remote-loopback error-disable-interface
commit
Configuring Ethernet OAM Features on an Individual Interface: Example
This example shows how to configure Ethernet OAM features on an individual interface:
configure terminal
interface TenGigE 0/1/0/0
ethernet oam
link-monitor
symbol-period window 60000
symbol-period threshold low 10000000 high 60000000
frame window 60
frame threshold low 10000000 high 60000000
frame-period window 60000
frame-period threshold low 100 high 12000000
frame-seconds window 900000
frame-seconds threshold 3 threshold 900
exit
mib-retrieval
connection timeout 30
require-remote mode active
require-remote link-monitoring
require-remote mib-retrieval
action link-fault error-disable-interface
action dying-gasp error-disable-interface
action critical-event error-disable-interface
action discovery-timeout error-disable-interface
action session-down error-disable-interface
action capabilities-conflict error-disable-interface
action wiring-conflict error-disable-interface
action remote-loopback error-disable-interface
commit
Configuring Ethernet OAM Features to Override the Profile on an Individual Interface: Example
This example shows the configuration of Ethernet OAM features in a profile followed by an override of that
configuration on an interface:
configure terminal
ethernet oam profile Profile_1
mode passive
action dying-gasp disable
action critical-event disable
action discovery-timeout disable
action session-up disable
action session-down disable
action capabilities-conflict disable
action wiring-conflict disable
action remote-loopback disable
action uni-directional link-fault error-disable-interface
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
67
Page 78
Configuration Examples for Ethernet CFM
commit
configure terminal
interface TenGigE 0/1/0/0
ethernet oam
profile Profile_1
mode active
action dying-gasp log
action critical-event log
action discovery-timeout log
action session-up log
action session-down log
action capabilities-conflict log
action wiring-conflict log
action remote-loopback log
action uni-directional link-fault log
uni-directional link-fault detection
commit
Clearing Ethernet OAM Statistics on an Interface: Example
This example shows how to clear Ethernet OAM statistics on an interface:
Configuring Ethernet OAM
RP/0/RP0/CPU0:router# clear ethernet oam statistics interface gigabitethernet 0/1/5/1
Enabling SNMP Server Traps on a Router: Example
This example shows how to enable SNMP server traps on a router:
configure terminal
ethernet oam profile Profile_1
snmp-server traps ethernet oam events
Configuration Examples for Ethernet CFM
This section includes the following examples:
Ethernet CFM Domain Configuration: Example
This example shows how to configure a basic domain for Ethernet CFM:
configure
ethernet cfm
traceroute cache hold-time 1 size 3000
domain Domain_One level 1 id string D1
commit
Ethernet CFM Service Configuration: Example
This example shows how to create a service for an Ethernet CFM domain:
service Bridge_Service bridge group BD1 bridge-domain B1
service Cross_Connect_1 xconnect group XG1 p2p X1
commit
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
68
Page 79
Configuring Ethernet OAM
Configuration Examples for Ethernet CFM
Flexible Tagging for an Ethernet CFM Service Configuration: Example
This example shows how to set the number of tags in CFM packets from down MEPs in a CFM domain
service:
configure
ethernet cfm
domain D1 level 1
service S2 bridge group BG1 bridge-domain BD2
tags 1
commit
Continuity Check for an Ethernet CFM Service Configuration: Example
This example shows how to configure continuity-check options for an Ethernet CFM service:
continuity-check archive hold-time 100
continuity-check loss auto-traceroute
continuity-check interval 100ms loss-threshold 10
commit
MIP Creation for an Ethernet CFM Service Configuration: Example
This example shows how to enable MIP auto-creation for an Ethernet CFM service:
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)# mip auto-create all
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)# commit
Cross-check for an Ethernet CFM Service Configuration: Example
This example shows how to configure cross-check for MEPs in an Ethernet CFM service:
mep crosscheck
mep-id 10
mep-id 20
commit
Other Ethernet CFM Service Parameter Configuration: Example
This example shows how to configure other Ethernet CFM service options:
maximum-meps 4000
log continuity-check errors
commit
exit
exit
exit
MEP Configuration: Example
This example shows how to configure a MEP for Ethernet CFM on an interface:
interface TenGigE 0/0/0/1
ethernet cfm
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
69
Page 80
Configuration Examples for Ethernet CFM
mep domain Dm1 service Sv1 mep-id 1
commit
Ethernet CFM Show Command: Examples
These examples show how to verify the configuration of Ethernet Connectivity Fault Management (CFM):
Example 1
This example shows how to display all the maintenance points that have been created on an interface:
RP/0/RP0/CPU0:router# show ethernet cfm local maintenance-points
Domain/Level Service Interface Type ID MAC
-------------------- ------------------- ----------------- ------ ---- -------fig/5 bay Gi0/10/0/12 Dn MEP 2 44:55:66
fig/5 bay Gi0/0/1/0 MIP 55:66:77
fred/3 barney Gi0/1/0/0 Dn MEP 5 66:77:88!
Example 2
This example shows how to display all the CFM configuration errors on all domains:
Configuring Ethernet OAM
RP/0/RP0/CPU0:router# show ethernet cfm configuration-errors
Domain fig (level 5), Service bay
* MIP creation configured using bridge-domain blort, but bridge-domain blort does not exist.
* An Up MEP is configured for this domain on interface TenGigE0/0/0/3 and an Up MEP is
also configured for domain blort, which is at the same level (5).
* A MEP is configured on interface TenGigE0/0/0/1 for this domain/service, which has CC
interval 100ms, but the lowest interval supported on that interface is 1s
Example 3
This example shows how to display operational state for local maintenance end points (MEPs):
RP/0/RP0/CPU0:router# show ethernet cfm local meps
A - AIS received I - Wrong interval
R - Remote Defect received V - Wrong Level
L - Loop (our MAC received) T - Timed out (archived)
C - Config (our ID received) M - Missing (cross-check)
X - Cross-connect (wrong MAID) U - Unexpected (cross-check)
P - Peer port down
Domain foo (level 6), Service bar
ID Interface (State) Dir MEPs/Err RD Defects AIS
----- ------------------------ --- -------- -- ------- --100 Gi1/1/0/1 (Up) Up 0/0 N A L7
Domain fred (level 5), Service barney
ID Interface (State) Dir MEPs/Err RD Defects AIS
----- ------------------------ --- -------- -- ------- ---
2 Gi0/1/0/0 (Up) Up 3/2 Y RPC L6
Domain foo (level 6), Service bar
ID Interface (State) Dir MEPs/Err RD Defects AIS
----- ------------------------ --- -------- -- ------- --100 Gi1/1/0/1 (Up) Up 0/0 N A
Domain fred (level 5), Service barney
ID Interface (State) Dir MEPs/Err RD Defects AIS
----- ------------------------ --- -------- -- ------- ---
2 Gi0/1/0/0 (Up) Up 3/2 Y RPC
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
70
Page 81
Configuring Ethernet OAM
Configuration Examples for Ethernet CFM
Example 4
This example shows how to display operational state of other maintenance end points (MEPs) detected by a
local MEP:
RP/0/RP0/CPU0:router# show ethernet cfm peer meps
Flags:
> - Ok I - Wrong interval
R - Remote Defect received V - Wrong level
L - Loop (our MAC received) T - Timed out
C - Config (our ID received) M - Missing (cross-check)
X - Cross-connect (wrong MAID) U - Unexpected (cross-check)
Domain fred (level 7), Service barney
Down MEP on TenGigE0/0/0/1, MEP-ID 2
================================================================================
St ID MAC address Port Up/Downtime CcmRcvd SeqErr RDI Error
-- ----- -------------- ------- ----------- --------- ------ ----- ----> 1 0011.2233.4455 Up 00:00:01 1234 0 0 0
R> 4 4455.6677.8899 Up 1d 03:04 3456 0 234 0
L 2 1122.3344.5566 Up 3w 1d 6h 3254 0 0 3254
C 2 7788.9900.1122 Test 00:13 2345 6 20 2345
X 3 2233.4455.6677 Up 00:23 30 0 0 30
I 3 3344.5566.7788 Down 00:34 12345 0 300 1234
V 3 8899.0011.2233 Blocked 00:35 45 0 0 45
T 5 5566.7788.9900 00:56 20 0 0 0
M 6 0 0 0 0
U> 7 6677.8899.0011 Up 00:02 456 0 0 0
Domain fred (level 7), Service fig
Down MEP on TenGigE0/0/0/12, MEP-ID 3
================================================================================
St ID MAC address Port Up/Downtime CcmRcvd SeqErr RDI Error
-- ----- -------------- ------- ----------- -------- ------ ----- ----> 1 9900.1122.3344 Up 03:45 4321 0 0 0
Example 5
This example shows how to display operational state of other maintenance end points (MEPs) detected by a
local MEP with details:
RP/0/RP0/CPU0:router# show ethernet cfm peer meps detail
Domain dom3 (level 5), Service ser3
Down MEP on TenGigE0/0/0/1 MEP-ID 1
================================================================================
Peer MEP-ID 10, MAC 0001.0203.0403
CFM state: Wrong level, for 00:01:34
Port state: Up
CCM defects detected: V - Wrong Level
CCMs received: 5
Out-of-sequence: 0
Remote Defect received: 5
Wrong Level: 0
Cross-connect (wrong MAID): 0
Wrong Interval: 5
Loop (our MAC received): 0
Config (our ID received): 0
Last CCM received 00:00:06 ago:
Level: 4, Version: 0, Interval: 1min
Sequence number: 5, MEP-ID: 10
MAID: String: dom3, String: ser3
Port status: Up, Interface status: Up
Domain dom4 (level 2), Service ser4
Down MEP on TenGigE0/0/0/2 MEP-ID 1
================================================================================
Peer MEP-ID 20, MAC 0001.0203.0402
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
71
Page 82
Configuration Examples for Ethernet CFM
CFM state: Ok, for 00:00:04
Port state: Up
CCMs received: 7
Out-of-sequence: 1
Remote Defect received: 0
Wrong Level: 0
Cross-connect (wrong MAID): 0
Wrong Interval: 0
Loop (our MAC received): 0
Config (our ID received): 0
Last CCM received 00:00:04 ago:
Level: 2, Version: 0, Interval: 10s
Sequence number: 1, MEP-ID: 20
MAID: String: dom4, String: ser4
Chassis ID: Local: ios; Management address: 'Not specified'
Port status: Up, Interface status: Up
Peer MEP-ID 21, MAC 0001.0203.0403
CFM state: Ok, for 00:00:05
Port state: Up
CCMs received: 6
Out-of-sequence: 0
Remote Defect received: 0
Wrong Level: 0
Cross-connect (wrong MAID): 0
Wrong Interval: 0
Loop (our MAC received): 0
Config (our ID received): 0
Last CCM received 00:00:05 ago:
Level: 2, Version: 0, Interval: 10s
Sequence number: 1, MEP-ID: 21
MAID: String: dom4, String: ser4
Port status: Up, Interface status: Up
Configuring Ethernet OAM
Peer MEP-ID 601, MAC 0001.0203.0402
CFM state: Timed Out (Standby), for 00:15:14, RDI received
Port state: Down
CCM defects detected: Defects below ignored on local standby MEP
CCMs received: 2
Out-of-sequence: 0
Remote Defect received: 2
Wrong Level: 0
Wrong Interval: 2
Loop (our MAC received): 0
Config (our ID received): 0
Last CCM received 00:15:49 ago:
Level: 2, Version: 0, Interval: 10s
Sequence number: 1, MEP-ID: 600
MAID: DNS-like: dom5, String: ser5
Chassis ID: Local: ios; Management address: 'Not specified'
Port status: Up, Interface status: Down
AIS for CFM Configuration: Examples
Example 1
This example shows how to configure Alarm Indication Signal (AIS) transmission for a CFM domain service:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ethernet cfm
RP/0/RP0/CPU0:router(config-cfm)# domain D1 level 1
RP/0/RP0/CPU0:router(config-cfm-dmn)# service S1 bridge group BG1 bridge-domain BD2
I - Wrong Interval
R - Remote Defect received
T - Timed Out
P - Peer port down
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
72
Page 83
Configuring Ethernet OAM
Configuration Examples for Ethernet CFM
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)# ais transmission interval 1m cos 7
RP/0/RP0/CPU0:routerconfigure
RP/0/RP0/CPU0:router(config)# ethernet cfm
RP/0/RP0/CPU0:router(config-cfm)# domain D1 level 1
RP/0/RP0/CPU0:router(config-cfm-dmn)# service Cross_Connect_1 xconnect group XG1 p2p
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)# ais transmission interval 1m cos 7
Example 2
This example shows how to configure AIS logging for a Connectivity Fault Management (CFM) domain
service to indicate when AIS or LCK packets are received:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ethernet cfm
RP/0/RP0/CPU0:router(config-cfm)# domain D1 level 1
RP/0/RP0/CPU0:router(config-cfm-dmn)# service S2 bridge group BG1 bridge-domain BD2
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)# log ais
RP/0/RP0/CPU0:routerconfigure
RP/0/RP0/CPU0:router(config)# ethernet cfm
RP/0/RP0/CPU0:router(config-cfm)# domain D1 level 1
RP/0/RP0/CPU0:router(config-cfm-dmn)# service Cross_Connect_1 xconnect group XG1 p2p
RP/0/RP0/CPU0:router(config-cfm-dmn-svc)# log ais
This example shows how to configure AIS transmission on a CFM interface.
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface TenGigE 0/1/0/2
RP/0/RP0/CPU0:router(config-if)# ethernet cfm
RP/0/RP0/CPU0:router(config-if-cfm)# ais transmission up interval 1m cos 7
AIS for CFM Show Commands: Examples
This section includes the following examples:
show ethernet cfm interfaces ais Command: Example
This example shows how to display the information published in the Interface AIS table:
RP/0/RP0/CPU0:router# show ethernet cfm interfaces ais
Defects (from at least one peer MEP):
A - AIS received I - Wrong interval
R - Remote Defect received V - Wrong Level
L - Loop (our MAC received) T - Timed out (archived)
C - Config (our ID received) M - Missing (cross-check)
X - Cross-connect (wrong MAID) U - Unexpected (cross-check)
P - Peer port down D - Local port down
Trigger Transmission
Interface (State) Dir L Defects Levels L Int Last started Packets
------------------------ --- - ------- ------- - --- ------------ --------
TenGigE0/0/0/0 (Up) Dn 5 RPC 6 7 1s 01:32:56 ago 5576
TenGigE0/0/0/0 (Up) Up 0 M 2,3 5 1s 00:16:23 ago 983
TenGigE0/0/0/1 (Dn) Up D 7 60s 01:02:44 ago 3764
TenGigE0/0/0/2 (Up) Dn 0 RX 1!
AIS --------- Via ---------------------------
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
73
Page 84
Configuration Examples for Ethernet CFM
show ethernet cfm local meps Command: Examples
Example 1: Default
This example shows how to display statistics for local maintenance end points (MEPs):
RP/0/RP0/CPU0:router# show ethernet cfm local meps
A - AIS received I - Wrong interval
R - Remote Defect received V - Wrong Level
L - Loop (our MAC received) T - Timed out (archived)
C - Config (our ID received) M - Missing (cross-check)
X - Cross-connect (wrong MAID) U - Unexpected (cross-check)
P - Peer port down
Domain foo (level 6), Service bar
ID Interface (State) Dir MEPs/Err RD Defects AIS
----- ------------------------ --- -------- -- ------- --100 Gi1/1/0/1 (Up) Up 0/0 N A 7
Domain fred (level 5), Service barney
ID Interface (State) Dir MEPs/Err RD Defects AIS
----- ------------------------ --- -------- -- ------- ---
2 Gi0/1/0/0 (Up) Up 3/2 Y RPC 6
Configuring Ethernet OAM
Example 2: Domain Service
This example shows how to display statistics for MEPs in a domain service:
RP/0/RP0/CPU0:router# show ethernet cfm local meps domain foo service bar detail
Domain foo (level 6), Service bar
Down MEP on TenGigE0/0/0/1, MEP-ID 100
================================================================================
Interface state: Up MAC address: 1122.3344.5566
Peer MEPs: 0 up, 0 with errors, 0 timed out (archived)
CCM generation enabled: No
AIS generation enabled: Yes (level: 7, interval: 1s)
Sending AIS: Yes (started 01:32:56 ago)
Receiving AIS: Yes (from lower MEP, started 01:32:56 ago)
Domain fred (level 5), Service barney
Down MEP on TenGigE0/0/0/1, MEP-ID 2
================================================================================
Interface state: Up MAC address: 1122.3344.5566
Peer MEPs: 3 up, 2 with errors, 0 timed out (archived)
Cross-check defects: 0 missing, 0 unexpected
CCM generation enabled: Yes (Remote Defect detected: Yes)
CCM defects detected: R - Remote Defect received
AIS generation enabled: Yes (level: 6, interval: 1s)
Sending AIS: Yes (to higher MEP, started 01:32:56 ago)
Receiving AIS: No
P - Peer port down
C - Config (our ID received)
Example 4: Detail
This example shows how to display detailed statistics for MEPs in a domain service:
RP/0/RP0/CPU0:router# show ethernet cfm local meps detail
Domain foo (level 6), Service bar
Down MEP on TenGigE0/0/0/1, MEP-ID 100
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
74
Page 85
Configuring Ethernet OAM
Configuration Examples for Ethernet CFM
================================================================================
Interface state: Up MAC address: 1122.3344.5566
Peer MEPs: 0 up, 0 with errors, 0 timed out (archived)
CCM generation enabled: No
AIS generation enabled: Yes (level: 7, interval: 1s)
Sending AIS: Yes (started 01:32:56 ago)
Receiving AIS: Yes (from lower MEP, started 01:32:56 ago)
Domain fred (level 5), Service barney
Down MEP on TenGigE0/0/0/1, MEP-ID 2
================================================================================
Interface state: Up MAC address: 1122.3344.5566
Peer MEPs: 3 up, 2 with errors, 0 timed out (archived)
Cross-check defects: 0 missing, 0 unexpected
CCM generation enabled: Yes (Remote Defect detected: Yes)
CCM defects detected: R - Remote Defect received
P - Peer port down
C - Config (our ID received)
AIS generation enabled: Yes (level: 6, interval: 1s)
Sending AIS: Yes (to higher MEP, started 01:32:56 ago)
Receiving AIS: No
show ethernet cfm local meps detail Command: Example
Use the show ethernet cfm local meps detail command to display MEP-related EFD status information. This
example shows that EFD is triggered for MEP-ID 100:
RP/0/RP0/CPU0:router# show ethernet cfm local meps detail
Domain foo (level 6), Service bar
Down MEP on TenGigE0/0/0/1, MEP-ID 100
================================================================================
Interface state: Up MAC address: 1122.3344.5566
Peer MEPs: 0 up, 0 with errors, 0 timed out (archived)
Cross-check errors: 2 missing, 0 unexpected
CCM generation enabled: No
AIS generation enabled: Yes (level: 7, interval: 1s)
Sending AIS: Yes (started 01:32:56 ago)
Receiving AIS: Yes (from lower MEP, started 01:32:56 ago)
EFD triggered: Yes
Domain fred (level 5), Service barney
Down MEP on TenGigE0/0/0/1, MEP-ID 2
================================================================================
Interface state: Up MAC address: 1122.3344.5566
Peer MEPs: 3 up, 0 with errors, 0 timed out (archived)
Cross-check errors: 0 missing, 0 unexpected
CCM generation enabled: Yes (Remote Defect detected: No)
AIS generation enabled: Yes (level: 6, interval: 1s)
Sending AIS: No
Receiving AIS: No
EFD triggered: No
Note
You can also verify that EFD has been triggered on an interface using the show interfaces and show
interfaces brief commands. When an EFD trigger has occurred, these commands will show the interface
status as up and the line protocol state as down.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
75
Page 86
Configuration Examples for Ethernet CFM
Configuring Ethernet OAM
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
76
Page 87
CHAPTER 6
Integrated Routing and Bridging
The BVI is a virtual interface within the router that acts like a normal routed interface. The BVI does not
support bridging itself, but acts as a gateway for the corresponding bridge-domain to a routed interface within
the router.
Aside from supporting a configurable MAC address, a BVI supports only Layer 3 attributes, and has the
following characteristics:
Uses a MAC address taken from the local chassis MAC address pool, unless overridden at the BVI
•
interface.
Is configured as an interface type using the interface bvi command and uses an IPv4 address that is
•
in the same subnet as the hosts on the segments of the bridged domain. The BVI also supports secondary
addresses.
The BVI identifier is independent of the bridge-domain identifier. These identifiers do not need to
•
correlate like they do in Cisco IOS software.
Is associated to a bridge group using the routed interface bvi command.
•
Bridge-Group Virtual Interface, page 78
•
Supported Features on a BVI, page 78
•
BVI Interface and Line Protocol States, page 78
•
Prerequisites for Configuring IRB, page 79
•
Restrictions for Configuring IRB, page 79
•
How to Configure IRB, page 80
•
Additional Information on IRB, page 87
•
Packet Flows Using IRB, page 87
•
Configuration Examples for IRB, page 89
•
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
77
Page 88
Bridge-Group Virtual Interface
Bridge-Group Virtual Interface
The BVI is a virtual interface within the router that acts like a normal routed interface. The BVI does not
support bridging itself, but acts as a gateway for the corresponding bridge-domain to a routed interface within
the router.
BVI supports only Layer 3 attributes, and has the following characteristics:
Uses a MAC address taken from the local chassis MAC address pool, unless overridden at the BVI
•
interface.
Is configured as an interface type using the interface bvi command and uses an IPv4 address that is in
•
the same subnet as the hosts on the segments of the bridged domain.
The BVI identifier is independent of the bridge-domain identifier. These identifiers do not need to
•
correlate like they do in Cisco IOS software.
Is associated to a bridge group using the routed interface bvi command.
•
BVI interfaces support a number range of 1 to 4294967295.
•
Integrated Routing and Bridging
Supported Features on a BVI
These interface commands are supported on a BVI:
•
arp purge-delay
◦
arp timeout
◦
bandwidth (The default is 10 Gbps and is used as the cost metric for routing protocols for the
◦
BVI)
ipv4
◦
ipv6
◦
mac-address
◦
mtu (The default is 1500 bytes)
◦
shutdown
◦
The BVI supports IP helper addressing and secondary IP addressing.
•
BVI Interface and Line Protocol States
Like typical interface states on the router, a BVI has both an Interface and Line Protocol state.
The BVI interface state is Up when the following occurs:
•
The BVI interface is created.
◦
The bridge-domain that is configured with the routed interface bvi command has at least one
◦
available active bridge port (Attachment circuit [AC] or pseudowire [PW]).
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
78
Page 89
Integrated Routing and Bridging
Prerequisites for Configuring IRB
Note
These characteristics determine when the the BVI line protocol state is up:
•
The bridge-domain is in Up state.
◦
The BVI IP address is not in conflict with any other IP address on another active interface in the
◦
router.
A BVI will be moved to the Down state if all of the bridge ports (Ethernet flow points
[EFPs]) associated with the bridge domain for that BVI are down. However, the BVI
will remain up if at least one bridgeport is up, even if all EFPs are down.
Prerequisites for Configuring IRB
You must be in a user group associated with a task group that includes the proper task IDs. The command
reference guides include the task IDs required for each command. If you suspect user group assignment is
preventing you from using a command, contact your AAA administrator for assistance.
Before configuring IRB, be sure that these tasks and conditions are met:
Know the IP addressing and other Layer 3 information to be configured on the bridge virtual interface
•
(BVI).
Complete MAC address planning if you decide to override the common global MAC address for all
•
BVIs.
Be sure that the BVI network address is being advertised by running static or dynamic routing on the
•
BVI interface.
Restrictions for Configuring IRB
Before configuring IRB, consider these restrictions:
Only one BVI can be configured in any bridge domain.
•
The same BVI can not be configured in multiple bridge domains.
•
The following areas are not supported on the Layer2 bridging (with BVI):
•
Access Control Lists (ACLs). However, Layer 2 ACLs can be configured on each Layer 2 port of
◦
the bridge domain.
Static mac entry configuration in Bridge.
◦
Mac ageing configuration at global config mode.
◦
MAC Learning Disable.
◦
Port-channel sub-interface as bridge member.
◦
Physical sub-interface as bridge member.
◦
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
79
Page 90
How to Configure IRB
Vlan rewrite.
◦
QOS configuration on BVI interface is not supported.
•
VRF on BVI interface is not supported.
•
L2 sub-interfaces are not supported.
•
How to Configure IRB
This section includes the following configuration tasks:
Configuring the Bridge Group Virtual Interface
To configure a BVI, complete the following steps.
Integrated Routing and Bridging
Configuration Guidelines
Consider the following guidelines when configuring the BVI:
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
The BVI must be assigned an IPv4 or IPv6 address that is in the same subnet as the hosts in the bridged
•
segments.
If the bridged network has multiple IP networks, then the BVI must be assigned secondary IP addresses
•
for each network.
configure
interface bvi identifier
ipv4 address ipv4-address mask [secondary] ipv6 address ipv6-prefix/prefix-length [eui-64] [route-tag
route-tag value]
arp purge-delay seconds
arp timeout seconds
bandwidth rate
mtu bytes
end or commit
Step 1
80
configure
Example:
RP/0/RP0/CPU0:router# configure
Enters the global configuration mode.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
Page 91
Integrated Routing and Bridging
Configuring the Bridge Group Virtual Interface
Step 2
Step 3
Step 4
Step 5
interface bvi identifier
Example:
RP/0/RP0/CPU0:router(config)# interface bvi 1
Specifies or creates a BVI, where identifier is a number from 1 to 65535.
ipv4 address ipv4-address mask [secondary] ipv6 address ipv6-prefix/prefix-length [eui-64] [route-tag route-tag value]
Example:
RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.10.0.4 255.255.255.0
Specifies a primary or secondary IPv4 address or an IPv6 address for an interface.
arp purge-delay seconds
Example:
RP/0/RP0/CPU0:router(config-if)#arp purge-delay 120
(Optional) Specifies the amount of time (in seconds) to delay purging of Address Resolution Protocol (ARP) table entries
when the interface goes down.
The range is 1 to 65535. By default purge delay is not configured.
arp timeout seconds
Example:
Step 6
Step 7
Step 8
RP/0/RP0/CPU0:router(config-if)# arp timeout 12200
(Optional) Specifies how long dynamic entries learned on the interface remain in the ARP cache.
The range is 30 to 2144448000 seconds. The default is 14,400 seconds (4 hours).
bandwidth rate
Example:
RP/0/RP0/CPU0:router(config-if)# bandwidth 1000000
(Optional) Specifies the amount of bandwidth (in kilobits per second) to be allocated on the interface. This number is
used as the cost metric in routing protocols for the BVI.
The range is 0 to 4294967295. The default is 10000000 (10 Gbps).
mtu bytes
Example:
RP/0/RP0/CPU0:router(config-if)# mtu 2000
(Optional) Specifies the maximum transmission unit (MTU) size for packets on the interface. The range is 64 to 65535.
The default is 1514.
end or commit
Example:
RP/0/RP0/CPU0:router(config-if)# end
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
81
Page 92
Configuring the Layer 2 AC Interfaces
or
RP/0/RP0/CPU0:router(config-if)# commit
Saves configuration changes.
When you issue the end command, the system prompts you to commit changes:
•
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
Entering yes saves configuration changes to the running configuration file, exits the configuration session, and
returns the router to EXEC mode.
Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration
changes.
Entering cancel leaves the router in the current configuration session without exiting or committing the configuration
changes.
Use the commit command to save the configuration changes to the running configuration file and remain within
•
the configuration session.
Integrated Routing and Bridging
Configuring the Layer 2 AC Interfaces
To configure the Layer 2 AC interfaces for routing by a BVI, complete the following steps.
SUMMARY STEPS
configure
1.
interface [HundredGigE | TenGigE] l2transport
2.
end or commit
3.
DETAILED STEPS
Step 1
Step 2
configure
Example:
RP/0/RP0/CPU0:router# configure
Enters global configuration mode.
interface [HundredGigE | TenGigE] l2transport
Example:
RP/0/RP0/CPU0:router(config)# interface TenGigE 0/1/0/0.1 l2transport
Enables Layer 2 transport mode on a Gigabit Ethernet or 10-Gigabit Ethernet interface or subinterface and enters interface
or subinterface configuration mode.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
82
Page 93
Integrated Routing and Bridging
Configuring a Bridge Group and Assigning Interfaces to a Bridge Domain
Step 3
end or commit
Example:
RP/0/RP0/CPU0:router(config-if)# end
or
RP/0/RP0/CPU0:router(config-if)# commit
Saves configuration changes.
When you issue the end command, the system prompts you to commit changes:
•
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
Entering yes saves configuration changes to the running configuration file, exits the configuration session, and
•
returns the router to EXEC mode.
Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration
•
changes.
Entering cancel leaves the router in the current configuration session without exiting or committing the configuration
•
changes.
Use the commit command to save the configuration changes to the running configuration file and remain within
•
the configuration session.
Configuring a Bridge Group and Assigning Interfaces to a Bridge Domain
To configure a bridge group and assign interfaces to a bridge domain, complete the following steps.
SUMMARY STEPS
configure
1.
l2vpn
2.
bridge group bridge-group-name
3.
bridge-domain bridge-domain-name
4.
interface [HundredGigE | TenGigE
5.
end or commit
6.
DETAILED STEPS
Step 1
configure
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
83
Page 94
Configuring a Bridge Group and Assigning Interfaces to a Bridge Domain
Example:
RP/0/RP0/CPU0:router# configure
Enters global configuration mode.
Integrated Routing and Bridging
Step 2
Step 3
Step 4
Step 5
l2vpn
Example:
RP/0/RP0/CPU0:router(config)# l2vpn
Enters L2VPN configuration mode.
bridge group bridge-group-name
Example:
RP/0/RP0/CPU0:router(config-l2vpn)# bridge group 10
Creates a bridge group and enters L2VPN bridge group configuration mode.
bridge-domain bridge-domain-name
Example:
RP/0/RP0/CPU0:router(config-l2vpn-bg)# bridge-domain BD_1
Creates a bridge domain and enters L2VPN bridge group bridge domain configuration mode.
interface [HundredGigE | TenGigE
Example:
RP/0/RP0/CPU0:router(config-l2vpn-bg-bd)# interface HundredGigE 0/1/0/0.1
Associates the 100-Gigabit Ethernet or 10-Gigabit Ethernet interface with the specified bridge domain and enters L2VPN
bridge group bridge domain attachment circuit configuration mode.
Repeat this step for as many interfaces as you want to associate with the bridge domain.
Step 6
84
end or commit
Example:
RP/0/RP0/CPU0:router(config-l2vpn-bg-bd-ac)# end
or
RP/0/RP0/CPU0:router(config-l2vpn-bg-bd-ac)# commit
Saves configuration changes.
When you issue the end command, the system prompts you to commit changes:
•
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
Entering yes saves configuration changes to the running configuration file, exits the configuration session, and
•
returns the router to EXEC mode.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
Page 95
Integrated Routing and Bridging
Associating the BVI as the Routed Interface on a Bridge Domain
Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration
•
changes.
Entering cancel leaves the router in the current configuration session without exiting or committing the configuration
•
changes.
Use the commit command to save the configuration changes to the running configuration file and remain within
•
the configuration session.
Associating the BVI as the Routed Interface on a Bridge Domain
To associate the BVI as the routed interface on a bridge domain, complete the following steps.
SUMMARY STEPS
DETAILED STEPS
Step 1
configure
Example:
RP/0/RP0/CPU0:router# configure
Enters global configuration mode.
Step 2
l2vpn
Example:
RP/0/RP0/CPU0:router(config)# l2vpn
Enters L2VPN configuration mode.
configure
1.
l2vpn
2.
bridge group bridge-group-name
3.
bridge-domain bridge-domain-name
4.
routed interface bvi identifier
5.
end or commit
6.
Step 3
Step 4
bridge group bridge-group-name
Example:
RP/0/RP0/CPU0:router(config-l2vpn)# bridge group BG_test
Creates a bridge group and enters L2VPN bridge group configuration mode.
bridge-domain bridge-domain-name
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
85
Page 96
Displaying Information About a BVI
Example:
RP/0/RP0/CPU0:router(config-l2vpn-bg)# bridge-domain 1
Creates a bridge domain and enters L2VPN bridge group bridge domain configuration mode.
Integrated Routing and Bridging
Step 5
Step 6
routed interface bvi identifier
Example:
RP/0/RP0/CPU0:router(config-l2vpn-bg-bd)# routed interface bvi 1
Associates the specified BVI as the routed interface for the interfaces assigned to the bridge domain.
end or commit
Example:
RP/0/RP0/CPU0:router(config-l2vpn-bg-bd)# end
or
RP/0/RP0/CPU0:router(config-l2vpn-bg-bd)# commit
Saves configuration changes.
When you issue the end command, the system prompts you to commit changes:
•
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:
Entering yes saves configuration changes to the running configuration file, exits the configuration session, and
•
returns the router to EXEC mode.
Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration
•
changes.
Entering cancel leaves the router in the current configuration session without exiting or committing the configuration
•
changes.
Use the commit command to save the configuration changes to the running configuration file and remain within
•
the configuration session.
Displaying Information About a BVI
To display information about BVI status and packet counters, use the following commands:
show interfaces bvi identifier [accounting | brief |
description | detail ]
show adjacency bvi identifier [detail | remote]
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
86
Displays interface status, line protocol state, and
packet counters for the specified BVI.
Displays packet and byte transmit counters per
adjacency to the specified BVI.
Page 97
Integrated Routing and Bridging
Additional Information on IRB
Packet Flows Using IRB
This figure shows a simplified functional diagram of an IRB implementation to describe different packet flows
between Host A, B, and C. In this example, Host C is on a network with a connection to the same router. In
reality, another router could be between Host C and the router shown.
Figure 8: IRB Packet Flows Between Hosts
Additional Information on IRB
Displays the reason that a BVI is down.show l2vpn bridge-domain detail
When IRB is configured on a router, the following processing happens:
ARP requests are resolved between the hosts and BVI that are part of the bridge domain.
•
All packets from a host on a bridged interface go to the BVI if the destination MAC address matches
•
the BVI MAC address. Otherwise, the packets are bridged.
For packets destined for a host on a routed network, the BVI forwards the packets to the routing engine
•
before sending them out a routed interface.
All packets either from or destined to a host on a bridged interface go to the BVI first (unless the packet
•
is destined for a host on the bridge domain).
For packets that are destined for a host on a segment in the bridge domain that come in to the router on
•
a routed interface, the BVI forwards the packet to the bridging engine, which forwards it through the
appropriate bridged interface.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
87
Page 98
Integrated Routing and Bridging
Packet Flows When Host A Sends to Host B on the Bridge Domain
Packet Flows When Host A Sends to Host B on the Bridge Domain
When Host A sends data to Host B in the bridge domain on the 10.10.0.0 network, no routing occurs. The
hosts are on the same subnet and the packets are bridged between their segment interfaces on the router.
Packet Flows When Host A Sends to Host C From the Bridge Domain to a Routed Interface
Using host information from this figure, the following occurs when Host A sends data to Host C from the
IRB bridging domain to the routing domain:
Host A sends the packet to the BVI (as long any ARP request the is resolved between the host and the
•
BVI). The packet has the following information:
Source MAC address of host A.
◦
Destination MAC address of the BVI.
◦
Since Host C is on another network and needs to be routed, the BVI forwards the packet to the routed
•
interface with the following information:
IP source MAC address of Host A (10.10.0.2) is changed to the MAC address of the BVI (10.10.0.4).
◦
IP destination address is the IP address of Host C (10.20.0.3).
◦
Interface 10.20.0.2 sees receipt of a packet from the routed BVI 10.10.0.4. The packet is then routed
•
through interface 10.20.0.2 to Host C.
Packet Flows When Host C Sends to Host B From a Routed Interface to the Bridge Domain
Using host information from this figure, the following occurs when Host C sends data to Host B from the IRB
routing domain to the bridging domain:
The packet comes into the routing domain with the following information:
•
◦ MAC source address—MAC of Host C.
◦ MAC destination address—MAC of the 10.20.0.2 ingress interface.
◦ IP source address—IP address of Host C (10.20.0.3).
◦ IP destination address—IP address of Host B (10.10.0.3).
When interface 10.20.0.2 receives the packet, it looks in the routing table and determines that the packet
•
needs to be forwarded to the BVI at 10.10.0.4.
• The routing engine captures the packet that is destined for the BVI and forwards it to the BVI’s
corresponding bridge domain. The packet is then bridged through the appropriate interface if the
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
88
Page 99
Integrated Routing and Bridging
destination MAC address for Host B appears in the bridging table, or is flooded on all interfaces in the
bridge group if the address is not in the bridging table.
Configuration Examples for IRB
This section provides the following configuration examples:
Basic IRB Configuration: Example
The following example shows how to perform the most basic IRB configuration:
! Configure the BVI and its IPv4 address
!
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)#interface bvi 1
RP/0/RP0/CPU0:router(config-if)#ipv4 address 10.10.0.4 255.255.255.0
RP/0/RP0/CPU0:router(config-if))# exit
!
! Configure the Layer 2 AC interface
!
RP/0/RP0/CPU0:router(config)#interface HundredGigE 0/1/0/0 l2transport
RP/0/RP0/CPU0:router(config-if))# exit
!
! Configure the L2VPN bridge group and bridge domain and assign interfaces
!
RP/0/RP0/CPU0:router(config)#l2vpn
RP/0/RP0/CPU0:router(config-l2vpn)#bridge group 10
RP/0/RP0/CPU0:router(config-l2vpn-bg)#bridge-domain 1
RP/0/RP0/CPU0:router(config-l2vpn-bg-bd)#interface HundredGigE 0/1/0/0
RP/0/RP0/CPU0:router(config-l2vpn-bg-bd-if)# exit
!
! Associate a BVI to the bridge domain
!
RP/0/RP0/CPU0:router(config-l2vpn-bg-bd)# routed interface bvi 1
RP/0/RP0/CPU0:router(config-l2vpn-bg-bd)# commit
Configuration Examples for IRB
IPv4 Addressing on a BVI Supporting Multiple IP Networks: Example
The following example shows how to configure secondary IPv4 addresses on a BVI that supports bridge
domains for the 10.10.10.0/24, 10.20.20.0/24, and 10.30.30.0/24 networks. In this example, the BVI must
have an address on each of the bridge domain networks:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)#interface bvi 1
RP/0/RP0/CPU0:router(config-if)#ipv4 address 10.10.10.4 255.255.255.0
RP/0/RP0/CPU0:router(config-if)#ipv4 address 10.20.20.4 255.255.255.0 secondary
RP/0/RP0/CPU0:router(config-if)#ipv4 address 10.30.30.4 255.255.255.0 secondary
RP/0/RP0/CPU0:router(config-if))# commit
IRB With BVI and VRRP Configuration: Example
This example shows a partial router configuration for the relevant configuration areas for IRB support of a
BVI and VRRP:
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
89
Page 100
IRB With BVI and VRRP Configuration: Example
VRRPv6 is also supported.Note
l2vpn
bridge group IRB
bridge-domain IRB-EDGE
interface TenGigE0/0/0/8
!
routed interface BVI 100
!
interface TenGigE0/0/0/8
l2transport
!
interface BVI 100
ipv4 address 10.21.1.1 255.255.255.0
!
router vrrp
interface BVI 100
vrrp 1 ipv4 10.21.1.100
vrrp 1 priority 100
!
Integrated Routing and Bridging
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
90
Loading...