Cisco NCS 5500 Series User manual

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: [phone]
800 553-NETS (6387)
Fax: [phone]

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.

CONTENTS
Preface Preface ix
Changes to This Document ix
Obtaining Documentation and Submitting a Service Request ix
CHAPTER 1 New and Changed Feature Information 1
New and Changed Information 1
CHAPTER 2 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
CHAPTER 3 Advanced Configuration and Modification of the Management Ethernet Interface 9
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
CHAPTER 4 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

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
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
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
CHAPTER 6 Integrated Routing and Bridging 77
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
v
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
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
CHAPTER 7 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
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
Troubleshooting Traffic Mirroring 135
Verifying UDF-based ACL 137
CHAPTER 9 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
Contents

Configuring Virtual IPv4 Interfaces 144
CHAPTER 10 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
CHAPTER 11 Configuring GRE Tunnels 155
Configuring GRE Tunnels 155
IP-in-IP De-capsulation 156
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
viii
Contents

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
Added IP-in-IP De-capsulation feature for Release
6.1.3
February 2017
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

Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
x
Preface
Obtaining Documentation and Submitting a Service Request

CHAPTER 1
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
Where DocumentedChanged in ReleaseDescriptionFeature
Configuring Integrated and
Bridging chapter
Release 6.1.3This feature was introduced.Integrated Routing and Bridging
Configuring Traffic Monitoring
chapter
Release 6.1.31This feature was introduced.ERSPAN
Configuring Link Bundling
chapter
Release 6.1.31This feature was introduced.LACP Fallback
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
1

Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
2
New and Changed Feature Information
New and Changed Information

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

configuration information is verified and, if successful, immediately applied to the running configuration of
the router.
When you plug the anticipated line card in, make sure to verify any preconfiguration with the appropriate
show commands.
Note
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.
Note
Tip Use the commit best-effort command to save the preconfiguration to the running configuration file.
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.
Tip
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
Preconfiguring Physical Interfaces
Prerequisites for Preconfiguring Physical Interfaces

SUMMARY STEPS
1. configure
2. interface preconfigure type interface-path-id
3. Use one of the following commands:
•ipv4 address ip-address subnet-mask
•ipv4 address ip-address/prefix
4. Configure additional interface parameters, as described in this manual in the configuration chapter that
applies to the type of interface that you are configuring.
5. end or commit best-effort
6. show running-config
DETAILED STEPS
Step 1 configure
Example:
RP/0/RP0/CPU0:router#configure
Enters global configuration mode.
Step 2 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.
Step 3 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 Configure additional interface parameters, as described in this manual in the configuration chapter that applies to the
type of interface that you are configuring.
Step 5 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
Preconfiguring Physical Interfaces
How to Preconfigure 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.
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
Preconfiguring Physical Interfaces
Information About Preconfiguring Physical Interfaces

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.
Note
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.
Note
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
7
Preconfiguring Physical Interfaces
Use of the Interface Preconfigure Command

Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release
6.1.x
8
Preconfiguring Physical Interfaces
Use of the Interface Preconfigure Command

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.
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).
Note
•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.
For transparent switchover, both active and standby Management Ethernet interfaces are expected to be
physically connected to the same LAN or switch.
Note
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
9

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
1. configure
2. interface MgmtEth interface-path-id
3. ipv4 address ip-address mask
4. mtu bytes
5. no shutdown
6. end or commit
7. show interfaces MgmtEth interface-path-id
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 Ethernet interface name and notation rack/slot/module/port.
The example indicates port 0 on the RP card that is installed in slot 0.
Step 3 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
Advanced Configuration and Modification of the Management Ethernet Interface
Performing Advanced Management Ethernet Interface Configuration