Cisco IOS XE 3S Configuration Guide

Add to My manuals
218 Pages

advertisement

Cisco IOS XE 3S Configuration Guide | Manualzz

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE

Everest 3.18SP

First Published: 2016-07-30

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

© 2016 Cisco Systems, Inc. All rights reserved.

C O N T E N T S

C H A P T E R 1

Using Cisco IOS XE Software 1

Understanding Command Modes 1

Understanding Diagnostic Mode 3

Accessing the CLI Using a Console 4

Accessing the CLI Using a Directly-Connected Console 4

Connecting to the Console Port 4

Using the Console Interface 4

Accessing the CLI from a Remote Console Using Telnet 5

Preparing to Connect to the Router Console Using Telnet 5

Using Telnet to Access a Console Interface 6

Accessing the CLI from a Remote Console Using a Modem 7

Using the Auxiliary Port 7

Using Keyboard Shortcuts 7

Using the History Buffer to Recall Commands 8

Getting Help 8

Finding Command Options Example 9

Using the no and default Forms of Commands 12

Saving Configuration Changes 12

Managing Configuration Files 12

Filtering Output from the show and more Commands 14

Powering Off the Router 14

Finding Support Information for Platforms and Cisco Software Images 14

Using Cisco Feature Navigator 15

Using Software Advisor 15

Using Software Release Notes 15

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

iii

Contents

C H A P T E R 2

C H A P T E R 3

Console Port Telnet and SSH Handling 17

Important Notes and Restrictions 17

Console Port Overview 17

Connecting Console Cables 18

Installing USB Device Drivers 18

Console Port Handling Overview 18

Telnet and SSH Overview 18

Persistent Telnet and Persistent SSH Overview 18

Configuring a Console Port Transport Map 19

Examples 20

Configuring Persistent Telnet 21

Examples 23

Configuring Persistent SSH 23

Examples 26

Viewing Console Port, SSH, and Telnet Handling Configurations 27

Configuring Clocking and Timing 31

Clocking and Timing Restrictions 31

Restrictions on RSP3 Module 33

Clocking and Timing Overview 33

Understanding PTP 34

Telecom Profiles 35

PTP Redundancy 35

PTP Asymmetry Readjustment 35

PTP Redundancy Using Hop-By-Hop Topology Design 35

BMCA 41

Hybrid Clocking 42

Transparent Clocking 42

Time of Day (TOD) 43

Timing Port Specifications 43

BITS Framing Support 43

Understanding Synchronous Ethernet ESMC and SSM 44

Clock Selection Modes 44

iv

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Contents

C H A P T E R 4

Managing Clock Selection 45

Configuring Clocking and Timing 45

Configuring an Ordinary Clock 45

Configuring a Server Ordinary Clock 45

Configuring a Client Ordinary Clock 50

Configuring a Boundary Clock 53

Configuring a Transparent Clock 55

Configuring a Hybrid Clock 57

Configuring a Hybrid Boundary Clock 57

Configuring a Hybrid Ordinary Clock 61

Configuring PTP Redundancy 65

Configuring PTP Redundancy in Client Clock Mode 65

Configuring PTP Redundancy in Boundary Clock Mode 67

Synchronizing the System Time to a Time-of-Day Source 70

Synchronizing the System Time to a Time-of-Day Source (Server Mode) 70

Synchronizing the System Time to a Time-of-Day Source (Client Mode) 71

Configuring Synchronous Ethernet ESMC and SSM 72

Configuring Synchronous Ethernet ESMC and SSM 72

Managing Clock Source Selection 76

Verifying the Configuration 78

Troubleshooting 79

Configuration Examples 80

Using the Management Ethernet Interface 87

Gigabit Ethernet Management Interface Overview 87

Gigabit Ethernet Port Numbering 87

IP Address Handling in ROMmon and the Management Ethernet Port 88

Gigabit Ethernet Management Interface VRF 88

Common Ethernet Management Tasks 89

Viewing the VRF Configuration 89

Viewing Detailed VRF Information for the Management Ethernet VRF 89

Setting a Default Route in the Management Ethernet Interface VRF 90

Setting the Management Ethernet IP Address 90

Telnetting over the Management Ethernet Interface 90

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

v

Contents

C H A P T E R 5

Pinging over the Management Ethernet Interface 90

Copy Using TFTP or FTP 90

NTP Server 91

SYSLOG Server 91

SNMP-related services 91

Domain Name Assignment 91

DNS service 92

RADIUS or TACACS+ Server 92

VTY lines with ACL 92

Configuring Ethernet Interfaces 93

Configuring Ethernet Interfaces 93

Limitations and Restrictions 93

Configuring an Interface 94

Specifying the Interface Address on an Interface Module 97

Configuring Hot Standby Router Protocol 97

Verifying HSRP 98

Modifying the Interface MTU Size 98

Interface MTU Configuration Guidelines 99

Configuring Interface MTU 99

Verifying the MTU Size 100

Configuring the Encapsulation Type 100

Configuring Autonegotiation on an Interface 100

Enabling Autonegotiation 100

Disabling Autonegotiation 101

Configuring Carrier Ethernet Features 101

Saving the Configuration 101

Shutting Down and Restarting an Interface 102

Verifying the Interface Configuration 102

Verifying Per-Port Interface Status 102

Verifying Interface Module Status 103

Configuring LAN/WAN-PHY Controllers 104

Restrictions for LAN/WAN-PHY Mode 104

Configuring LAN-PHY Mode 105

vi

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Contents

C H A P T E R 6

C H A P T E R 7

Configuring WAN-PHY Mode 106

Configuring WAN-PHY Error Thresholds 108

Configuration Examples 109

Example: Basic Interface Configuration 109

Example: MTU Configuration 110

Example: VLAN Encapsulation 111

Configuring the Global Navigation Satellite System 113

Information About the GNSS 113

Overview of the GNSS Module 113

Operation of the GNSS Module 114

Anti-Jamming 115

High Availability for GNSS 115

Prerequisites for GNSS 115

Restrictions for GNSS 115

How to Configure the GNSS 115

Enabling the GNSS License 115

Enabling the GNSS on the Cisco Router 116

Configuring the Satellite Constellation for GNSS 116

Configuring Pulse Polarity 116

Configuring Cable Delay 116

Disabling Anti-Jam Configuration 117

Verifying the Configuration of the GNSS 117

Swapping the GNSS Module 118

Configuration Example For Configuring GNSS 118

Additional References 119

G.8275.1 Telecom Profile 121

Why G.8275.1?

121

More About G.8275.1

121

PTP Domain 122

PTP Messages and Transport 122

PTP Modes 123

PTP Clocks 123

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

vii

Contents

C H A P T E R 8

C H A P T E R 9

PTP Ports 124

Virtual Port Support on T-BC 124

Alternate BMCA 124

Benefits 125

Prerequisites for Using the G.8275.1 Profile 125

Restrictions for Using the G.8275.1 Profile 125

Configuring the G.8275.1 Profile 125

Configuring Physical Frequency Source 125

Creating a Server-Only Ordinary Clock 126

Associated Commands 126

Creating an Ordinary Slave 126

Creating Dynamic Ports 126

Configuring Virtual Ports 127

Restrictions for Configuring Virtual Ports 127

Associated Commands 127

Verifying the Local Priority of the PTP Clock 127

Verifying the Port Parameters 127

Verifying the Foreign Master Information 128

Verifying Current PTP Time 128

Verifying the Virtual Port Status 128

G.8275.1 Deployment Scenario 129

Additional References 130

Feature Information for G.8275.1

130

Tracing and Trace Management 133

Tracing Overview 133

How Tracing Works 134

Tracing Levels 134

Viewing a Tracing Level 135

Setting a Tracing Level 137

Viewing the Content of the Trace Buffer 137

OTN Wrapper Overview 139

Advantages of OTN 141

viii

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

ODU and OTU 141

OTU1e and OTU 2e Support on 8x10GE Interface Module 141

Deriving OTU1e and OTU2e Rates 142

OTU3 Support in 2x40GE Interface Module 143

Supported Transceivers 143

OTN Specific Functions 143

Standard MIBS 144

Restrictions for OTN 144

DWDM Provisioning 145

Prerequisites for DWDM Provisioning 145

Configuring DWDM Provisioning 145

Configuring Transport Mode in 8x10GE and 2x40GE Interface Modules 145

Verification of LAN Transport Mode Configuration 146

Verification of OTN Transport Mode Configuration in 8x10GE Interface Modules 146

Verification of OTN Transport Mode Configuration in 2x40GE Interface Modules 147

Changing from OTN to LAN Mode 147

Verification of Enabled Ports for Controller Configuration 148

OTN Alarms 148

Configuring OTN Alarm Reports 149

Configuring OTU Alarm Reports 149

Configuring ODU Alarm Report 151

OTN Threshold 151

Configuring OTU Threshold 151

Configuring ODU Threshold 152

Verification of OTU and ODU Threshold Configuration 152

Configuring OTU Alerts 153

Configuring ODU Alerts 153

Configuring ODU Alerts 153

Verifying Alerts Configuration 154

Loopback 155

Configuring Loopback 155

Forward Error Connection 155

Benefits of FEC 155

Configuring FEC 156

Contents

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

ix

Contents

C H A P T E R 1 0

Trail Trace Identifier 157

Verifying Loopback Configuration 158

SNMP Support 159

Performance Monitoring 160

OTUk Section Monitoring 162

ODUk Path Monitoring 163

Configuring PM Parameters for FEC 163

Configuring PM Parameters for OTN 164

Verifying PM Parameters Configuration 164

Troubleshooting Scenarios 167

Associated Commands 167

Configuring the SDM Template 171

Prerequisites for the SDM Template 171

Restrictions for the SDM Template 171

Information About the SDM Template 173

Selecting the SDM Template 184

Verifying the SDM Template 186

SDM Template Supported Features on RSP3 Module 186

VPLS Statistics 187

Split Horizon Enhancements on the RSP3 Module 188

Prerequisites for Split-Horizon Groups on the RSP3 Module 188

Restrictions for Split-Horizon Groups on the RSP3 Module 188

Split-Horizon Supported Scale 189

Configuring Split-Horizon Group on the RSP3 Module 189

8K EFP (4 Queue Model) 190

Information About 8000 (8K) EFP 190

Prerequisites for 8000 (8K) EFP 190

Restrictions for 8000 (8K) EFP 190

Configuring 8K Model 190

16K EFP Support on Port Channel 193

Restrictions for 16K EFP on Port Channel 194

Configuring 16K EFP on Port Channel 194

Verifying 16k EFP on Port Channel 194

x

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Control Plane Policing 195

Restrictions for Control Plane Policing 195

Restrictions for CoPP on the RSP3 195

Supported Protocols 196

Input Rate-Limiting and Silent Mode Operation 198

How to Use Control Plane Policing 198

Configuration Examples for Control Plane Policing 200

Verification Examples for CoPP 200

QoS Support on Port Channel LACP Active Active 201

Benefits of QoS Support on Port Channel LACP Active Active 201

Restrictions for QoS Support on Port Channel Active Active 201

Configuring QoS Support on Port Channel Active Active 201

Verification of QoS Support on Port Channel LACP Active Active 202

Match Inner DSCP on RSP3 Module 204

Restrictions for Match Inner DSCP on RSP3 Module 204

Configuring Match Inner DSCP on RSP3 Module 204

Verifying Match Inner DSCP on RSP3 Module 204

Contents

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

xi

Contents xii

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

C H A P T E R

1

Using Cisco IOS XE Software

Understanding Command Modes, on page 1

Understanding Diagnostic Mode, on page 3

Accessing the CLI Using a Console, on page 4

Using the Auxiliary Port, on page 7

Using Keyboard Shortcuts, on page 7

Using the History Buffer to Recall Commands, on page 8

Getting Help, on page 8

Using the no and default Forms of Commands, on page 12

Saving Configuration Changes, on page 12

Managing Configuration Files, on page 12

Filtering Output from the show and more Commands, on page 14

Powering Off the Router, on page 14

Finding Support Information for Platforms and Cisco Software Images, on page 14

Understanding Command Modes

The command modes available in the traditional Cisco IOS CLI are exactly the same as the command modes available in Cisco IOS XE.

You use the CLI to access Cisco IOS XE software. Because the CLI is divided into many different modes, the commands available to you at any given time depend on the mode that you are currently in. Entering a question mark ( ?

) at the CLI prompt allows you to obtain a list of commands available for each command mode.

When you log in to the CLI, you are in user EXEC mode. User EXEC mode contains only a limited subset of commands. To have access to all commands, you must enter privileged EXEC mode, normally by using a password. From privileged EXEC mode, you can issue any EXEC command—user or privileged mode—or you can enter global configuration mode. Most EXEC commands are one-time commands. For example, show commands show important status information, and clear commands clear counters or interfaces. The EXEC commands are not saved when the software reboots.

Configuration modes allow you to make changes to the running configuration. If you later save the running configuration to the startup configuration, these changed commands are stored when the software is rebooted.

To enter specific configuration modes, you must start at global configuration mode. From global configuration mode, you can enter interface configuration mode and a variety of other modes, such as protocol-specific modes.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

1

Using Cisco IOS XE Software

Understanding Command Modes

ROM monitor mode is a separate mode used when the Cisco IOS XE software cannot load properly. If a valid software image is not found when the software boots or if the configuration file is corrupted at startup, the software might enter ROM monitor mode.

Table 1: Accessing and Exiting Command Modes , on page 2

describes how to access and exit various common command modes of the Cisco IOS XE software. It also shows examples of the prompts displayed for each mode.

Table 1: Accessing and Exiting Command Modes

Command

Mode

User EXEC

Access Method

Log in.

Prompt Exit Method

Use the logout command.

Router>

Privileged

EXEC

Global configuration

From user EXEC mode, use the enable EXEC command.

From privileged EXEC mode, use the configure terminal privileged EXEC command.

Router#

Router(config)#

To return to user EXEC mode, use the disable command.

To return to privileged EXEC mode from global configuration mode, use the exit or end command.

Interface configuration

Diagnostic

From global configuration mode, specify an interface using an interface command.

The router boots up or accesses diagnostic mode in the following scenarios:

Router(diag)#

• In some cases, diagnostic mode will be reached when the IOS process or processes fail. In most scenarios, however, the router will reload.

• A user-configured access policy was configured using the transport-map command that directed the user into diagnostic mode. See the

Using Cisco IOS

XE Software, on page 1

chapter of this book for information on configuring access policies.

• The router was accessed using a Route

Switch Processor auxiliary port.

• A break signal ( Ctrl-C , Ctrl-Shift-6 , or the send break command ) was entered and the router was configured to go into diagnostic mode when the break signal was received.

Router(config-if)#

To return to global configuration mode, use the exit command.

To return to privileged EXEC mode, use the end command.

If the IOS process failing is the reason for entering diagnostic mode, the IOS problem must be resolved and the router rebooted to get out of diagnostic mode.

If the router is in diagnostic mode because of a transport-map configuration, access the router through another port or using a method that is configured to connect to the

Cisco IOS CLI.

If the router is accessed through the Route

Switch Processor auxiliary port, access the router through another port. Accessing the router through the auxiliary port is not useful for customer purposes anyway.

2

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Using Cisco IOS XE Software

Understanding Diagnostic Mode

Command

Mode

Access Method Prompt

ROM monitor From privileged EXEC mode, use the reload

EXEC command. Press the Break key during the first 60 seconds while the system is booting.

>

Exit Method

To exit ROM monitor mode, use the continue command.

Universal IOS Image

Starting with XE318SP, there are two flavors of universal images supported on Cisco ASR900 series routers:

• Universal images with the "universalk9" designation in the image name: This universal image offers the strong payload cryptography Cisco IOS feature, the IPSec VPN feature.

• Universal images with the universalk9_npe" designation in the image name: The strong enforcement of encryption capabilities provided by Cisco Software Activation satisfies requirements for the export of encryption capabilities. However, some countries have import requirements that require that the platform does not support any strong crypto functionality such as payload cryptography. To satisfy the import requirements of those countries, the `npe' universal image does not support any strong payload encryption.

Starting with Cisco IOS XE Release 3.18SP, IPsec tunnel is supported only on the Cisco ASR903 and ASR907 routers with payload encryption (PE) images. IPSec requires an IPsec license to function.

Note • IPsec license must be acquired and installed in the router for IPsec functionality to work. When you enable or disable the IPsec license, reboot is mandatory for the system to function properly. IPsec is not supported on Cisco IOS XE Everest 16.5.1.

• NPE images shipped for Cisco ASR 900 routers do not support data plane encryptions. However, control plane encryption is supported with NPE images, with processing done in software, without the crypto engine.

Understanding Diagnostic Mode

Diagnostic mode is supported.

The router boots up or accesses diagnostic mode in the following scenarios:

• The IOS process or processes fail, in some scenarios. In other scenarios, the RSP will simply reset when the IOS process or processes fail.

• A user-configured access policy was configured using the transport-map command that directs the user into diagnostic mode.

• A send break signal ( Ctrl-C or Ctrl-Shift-6 ) was entered while accessing the router, and the router was configured to enter diagnostic mode when a break signal was sent.

In diagnostic mode, a subset of the commands that are also available in User EXEC mode are made available to users. Among other things, these commands can be used to:

• Inspect various states on the router, including the IOS state.

• Replace or roll back the configuration.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

3

Using Cisco IOS XE Software

Accessing the CLI Using a Console

• Provide methods of restarting the IOS or other processes.

• Reboot hardware, such as the entire router, an RSP, an IM, or possibly other hardware components.

• Transfer files into or off of the router using remote access methods such as FTP, TFTP, SCP, and so on.

The diagnostic mode provides a more comprehensive user interface for troubleshooting than previous routers, which relied on limited access methods during failures, such as ROMmon, to diagnose and troubleshoot IOS problems.

The diagnostic mode commands are stored in the non-IOS packages on the chassis, which is why the commands are available even if the IOS process is not working properly. Importantly, all the commands available in diagnostic mode are also available in privileged EXEC mode on the router even during normal router operation.

The commands are entered like any other commands in the privileged EXEC command prompts when used in privileged EXEC mode.

Accessing the CLI Using a Console

The following sections describe how to access the command-line interface (CLI) using a directly-connected console or by using Telnet or a modem to obtain a remote console:

Accessing the CLI Using a Directly-Connected Console

This section describes how to connect to the console port on the router and use the console interface to access the CLI. The console port is located on the front panel of each Route Switch Processor (RSP).

Connecting to the Console Port

Before you can use the console interface on the router using a terminal or PC, you must perform the following steps:

Procedure

Step 1

Step 2

Configure your terminal emulation software with the following settings:

• 9600 bits per second (bps)

• 8 data bits

• No parity

• 1 stop bit

• No flow control

Connect to the port using the RJ-45-to-RJ-45 cable and RJ-45-to-DB-25 DTE adapter or using the

RJ-45-to-DB-9 DTE adapter (labeled “Terminal”).

Using the Console Interface

Every RSP has a console interface. Notably, a standby RSP can be accessed using the console port in addition to the active RSP in a dual RSP configuration.

To access the CLI using the console interface, complete the following steps:

4

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Using Cisco IOS XE Software

Accessing the CLI from a Remote Console Using Telnet

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

After you attach the terminal hardware to the console port on the router and you configure your terminal emulation software with the proper settings, the following prompt appears:

Example:

Press RETURN to get started.

Press Return to enter user EXEC mode. The following prompt appears:

Example:

Router>

From user EXEC mode, enter the enable command as shown in the following example:

Example:

Router> enable

At the password prompt, enter your system password. If an enable password has not been set on your system, this step may be skipped.The following example shows entry of the password called “enablepass”:

Example:

Password: enablepass

When your enable password is accepted, the privileged EXEC mode prompt appears:

Example:

Router#

You now have access to the CLI in privileged EXEC mode and you can enter the necessary commands to complete your desired tasks.

To exit the console session, enter the exit command as shown in the following example:

Example:

Router# exit

Accessing the CLI from a Remote Console Using Telnet

This section describes how to connect to the console interface on a router using Telnet to access the CLI.

Preparing to Connect to the Router Console Using Telnet

Before you can access the router remotely using Telnet from a TCP/IP network, you need to configure the router to support virtual terminal lines (vtys) using the line vty global configuration command. You also should configure the vtys to require login and specify a password.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

5

Using Cisco IOS XE Software

Using Telnet to Access a Console Interface

Note To prevent disabling login on the line, be careful that you specify a password with the password command when you configure the login line configuration command. If you are using authentication, authorization, and accounting (AAA), you should configure the login authentication line configuration command. To prevent disabling login on the line for AAA authentication when you configure a list with the login authentication command, you must also configure that list using the aaa authentication login global configuration command.

For more information about AAA services, refer to the Cisco IOS XE Security Configuration Guide, Release

2 and Cisco IOS Security Command Reference publications.

In addition, before you can make a Telnet connection to the router, you must have a valid host name for the router or have an IP address configured on the router. For more information about requirements for connecting to the router using Telnet, information about customizing your Telnet services, and using Telnet key sequences, refer to the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2SR

.

Using Telnet to Access a Console Interface

To access a console interface using Telnet, complete the following steps:

Procedure

Step 1

Step 2

Step 3

From your terminal or PC, enter one of the following commands:

connect host [ port ] [ keyword ]

telnet host [ port ] [ keyword ]

In this syntax, host is the router hostname or an IP address, port is a decimal port number (23 is the default), and keyword is a supported keyword. For more information, refer to the Cisco IOS Configuration Fundamentals

Command Reference .

Note If you are using an access server, then you will need to specify a valid port number such as telnet

172.20.52.40 2004 , in addition to the hostname or IP address.

The following example shows the telnet command to connect to the router named “router”:

Example: unix_host% telnet router

Trying 172.20.52.40...

Connected to 172.20.52.40.

Escape character is '^]'.

unix_host% connect

At the password prompt, enter your login password. The following example shows entry of the password called “mypass”:

Example:

User Access Verification

Password: mypass

Note If no password has been configured, press Return .

From user EXEC mode, enter the enable command as shown in the following example:

6

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Using Cisco IOS XE Software

Accessing the CLI from a Remote Console Using a Modem

Step 4

Step 5

Step 6

Step 7

Example:

Router> enable

At the password prompt, enter your system password. The following example shows entry of the password called “enablepass”:

Example:

Password: enablepass

When the enable password is accepted, the privileged EXEC mode prompt appears:

Example:

Router#

You now have access to the CLI in privileged EXEC mode and you can enter the necessary commands to complete your desired tasks.

To exit the Telnet session, use the exit or logout command as shown in the following example:

Example:

Router# logout

Accessing the CLI from a Remote Console Using a Modem

To access the router remotely using a modem through an asynchronous connection, connect the modem to the console port.

The console port on a chassis is an EIA/TIA-232 asynchronous, serial connection with no flow control and an RJ-45 connector. The console port is located on the front panel of the RSP.

To connect a modem to the console port, place the console port mode switch in the in position. Connect to the port using the RJ-45-to-RJ-45 cable and the RJ-45-to-DB-25 DCE adapter (labeled “Modem”).

To connect to the router using the USB console port, connect to the port using a USB Type A-to-Type A cable.

Using the Auxiliary Port

The auxiliary port on the Route Switch Processor does not serve any useful purpose for customers.

This port should only be accessed under the advisement of a customer support representative.

Using Keyboard Shortcuts

Commands are not case sensitive. You can abbreviate commands and parameters if the abbreviations contain enough letters to be different from any other currently available commands or parameters.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

7

Using Cisco IOS XE Software

Using the History Buffer to Recall Commands

Table 2: Keyboard Shortcuts , on page 8

lists the keyboard shortcuts for entering and editing commands.

Table 2: Keyboard Shortcuts

Keystrokes Purpose

Ctrl-B or the Left Arrow key

1

Move the cursor back one character

Ctrl-F orthe Right Arrow key1 Move the cursor forward one character

Ctrl-A Move the cursor to the beginning of the command line

Ctrl-E

Esc B

Esc F

Move the cursor to the end of the command line

Move the cursor back one word

Move the cursor forward one word

1

The arrow keys function only on ANSI-compatible terminals such as VT100s.

Using the History Buffer to Recall Commands

The history buffer stores the last 20 commands you entered. History substitution allows you to access these commands without retyping them, by using special abbreviated commands.

Table 3: History Substitution Commands, on page 8

lists the history substitution commands.

Table 3: History Substitution Commands

Command

Ctrl-P or the Up Arrow key

2

Purpose

Recall commands in the history buffer, beginning with the most recent command. Repeat the key sequence to recall successively older commands.

Ctrl-N or the Down Arrow key1 Return to more recent commands in the history buffer after recalling commands with Ctrl-P or the Up Arrow key.

While in EXEC mode, list the last several commands you have just entered.

Router# show history

2

The arrow keys function only on ANSI-compatible terminals such as VT100s.

Getting Help

Entering a question mark ( ?

) at the CLI prompt displays a list of commands available for each command mode. You can also get a list of keywords and arguments associated with any command by using the context-sensitive help feature.

To get help specific to a command mode, a command, a keyword, or an argument, use one of the following commands:

8

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Using Cisco IOS XE Software

Finding Command Options Example

Table 4: Help Commands and Purpose

Command Purpose

Provides a brief description of the help system in any command mode.

help abbreviated-command-entry

?

Provides a list of commands that begin with a particular character string. (No space between command and question mark.) abbreviated-command-entry

< Tab

>

Completes a partial command name.

Lists all commands available for a particular command mode.

?

command

?

Lists the keywords or arguments that you must enter next on the command line. (Space between command and question mark.)

Finding Command Options Example

This section provides an example of how to display syntax for a command. The syntax can consist of optional or required keywords and arguments. To display keywords and arguments for a command, enter a question mark ( ?

) at the configuration prompt or after entering part of a command followed by a space. The Cisco IOS

XE software displays a list and brief description of available keywords and arguments. For example, if you were in global configuration mode and wanted to see all the keywords or arguments for the rep command, you would type rep ?

.

The <cr> symbol in command help output stands for “carriage return.” On older keyboards, the carriage return key is the Return key. On most modern keyboards, the carriage return key is the Enter key. The <cr> symbol at the end of command help output indicates that you have the option to press Enter to complete the command and that the arguments and keywords in the list preceding the <cr> symbol are optional. The <cr> symbol by itself indicates that no more arguments or keywords are available and that you must press Enter to complete the command.

Table 5: Finding Command Options , on page 9

shows examples of how you can use the question mark ( ?

) to assist you in entering commands.

Table 5: Finding Command Options

Command

Router> enable

Password: <password>

Router#

Comment

Enter the enable command and password to access privileged

EXEC commands. You are in privileged EXEC mode when the prompt changes to a “ # ” from the “ > ”; for example, Router> to Router# .

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

9

Using Cisco IOS XE Software

Finding Command Options Example

Command

Router# configure terminal

Enter configuration commands, one per line. End with

CNTL/Z.

Router(config)#

Comment

Enter the configure terminal privileged EXEC command to enter global configuration mode. You are in global configuration mode when the prompt changes to Router(config)# .

Router(config)# interface gigabitEthernet ?

<0-0> GigabitEthernet interface number

<0-1> GigabitEthernet interface number

Router(config)# interface gigabitEthernet 0?

.

/ <0-0>

Router(config)# interface gigabitEthernet 0/?

<0-5> Port Adapter number

Router(config)# interface gigabitEthernet 0/0?

/

Router(config)# interface gigabitEthernet 0/0/?

<0-15> GigabitEthernet interface number

Router(config)# interface gigabitEthernet 0/0/0?

.

<0-23>

Router(config)# interface gigabitEthernet 0/0/0

Enter interface configuration mode by specifying the serial interface that you want to configure using the global configuration command.

Enter ?

When the <cr> symbol is displayed, you can press Enter to complete the command.

You are in interface configuration mode when the prompt changes to Router(config-if)# .

interface serial to display what you must enter next on the command line. In this example, you must enter the serial interface slot number and port number, separated by a forward slash.

Router(config-if)# ?

Interface configuration commands:

.

.

.

ip Interface Internet Protocol config commands keepalive lan-name llc2 load-interval calculation for an

Enable keepalive

LAN Name command

LLC2 Interface Subcommands

Specify interval for load locaddr-priority logging loopback interface mac-address interface

Assign a priority group

Configure logging for interface

Configure internal loopback on an

Manually set interface MAC address

Enter ?

to display a list of all the interface configuration commands available for the serial interface. This example shows only some of the available interface configuration commands.

mls mls router sub/interface commands mpoa commands mtu

MPOA interface configuration

Set the interface Maximum

Transmission Unit (MTU) netbios Use a defined NETBIOS access list or enable no name-caching

Negate a command or set its defaults nrzi-encoding ntp

.

.

.

Router(config-if)#

Enable use of NRZI encoding

Configure NTP

10

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Using Cisco IOS XE Software

Finding Command Options Example

Command Comment

Router(config-if)# ip ?

Interface IP configuration subcommands: access-group Specify access control for packets accounting interface address

Enable IP accounting on this

Set the IP address of an interface

Enter the command that you want to configure for the interface.

This example uses the ip command.

Enter ?

to display what you must enter next on the command line. This example shows only some of the available interface IP configuration commands.

authentication authentication subcommands bandwidth-percent Set EIGRP bandwidth limit broadcast-address Set the broadcast address of an interface cgmp Enable/disable CGMP directed-broadcast Enable forwarding of directed broadcasts dvmrp DVMRP interface commands hello-interval Configures IP-EIGRP hello interval helper-address

UDP broadcasts hold-time

.

.

.

Router(config-if)# ip

Specify a destination address for

Configures IP-EIGRP hold time

Router(config-if)# ip address ?

A.B.C.D

IP address negotiated IP Address negotiated over PPP

Router(config-if)# ip address

Router(config-if)# ip address 172.16.0.1 ?

A.B.C.D

IP subnet mask

Router(config-if)# ip address 172.16.0.1

Enter the command that you want to configure for the interface.

This example uses the ip address command.

Enter ?

to display what you must enter next on the command line. In this example, you must enter an IP address or the negotiated keyword.

A carriage return (<cr>) is not displayed; therefore, you must enter additional keywords or arguments to complete the command.

Enter the keyword or argument that you want to use. This example uses the 172.16.0.1 IP address.

Enter ?

to display what you must enter next on the command line. In this example, you must enter an IP subnet mask.

A <cr> is not displayed; therefore, you must enter additional keywords or arguments to complete the command.

Router(config-if)# ip address 172.16.0.1 255.255.255.0

?

secondary Make this IP address a secondary address

<cr>

Router(config-if)# ip address 172.16.0.1 255.255.255.0

Enter the IP subnet mask. This example uses the 255.255.255.0

IP subnet mask.

Enter ?

to display what you must enter next on the command line. In this example, you can enter the secondary keyword, or you can press Enter .

A <cr> is displayed; you can press Enter to complete the command, or you can enter another keyword.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

11

Using Cisco IOS XE Software

Using the no and default Forms of Commands

Command Comment

Router(config-if)# ip address 172.16.0.1 255.255.255.0

Router(config-if)#

In this example, Enter is pressed to complete the command.

Using the no and default Forms of Commands

Almost every configuration command has a no form. In general, use the no form to disable a function. Use the command without the no keyword to re-enable a disabled function or to enable a function that is disabled by default. For example, IP routing is enabled by default. To disable IP routing, use the no ip routing command; to re-enable IP routing, use the ip routing command. The Cisco IOS software command reference publications provide the complete syntax for the configuration commands and describe what the no form of a command does.

Many CLI commands also have a default form. By issuing the command default command-name , you can configure the command to its default setting. The Cisco IOS software command reference publications describe the function of the default form of the command when the default form performs a different function than the plain and no forms of the command. To see what default commands are available on your system, enter default ?

in the appropriate command mode.

Saving Configuration Changes

Use the copy running-config startup-config command to save your configuration changes to the startup configuration so that the changes will not be lost if the software reloads or a power outage occurs. For example:

Router# copy running-config startup-config

Building configuration...

It might take a minute or two to save the configuration. After the configuration has been saved, the following output appears:

[OK]

Router#

This task saves the configuration to NVRAM.

Managing Configuration Files

On the chassis, the startup configuration file is stored in the nvram: file system and the running-configuration files are stored in the system: file system. This configuration file storage setup is not unique to the chassis and is used on several Cisco router platforms.

As a matter of routine maintenance on any Cisco router, users should backup the startup configuration file by copying the startup configuration file from NVRAM onto one of the router’s other file systems and, additionally, onto a network server. Backing up the startup configuration file provides an easy method of recovering the startup configuration file in the event the startup configuration file in NVRAM becomes unusable for any reason.

12

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Using Cisco IOS XE Software

Managing Configuration Files

The copy command can be used to backup startup configuration files. Below are some examples showing the startup configuration file in NVRAM being backed up:

Example 1: Copying Startup Configuration File to Bootflash

Router# dir bootflash:

Directory of bootflash:/

11 drwx

15105 drwx

16384

4096

Feb 2 2000 13:33:40 +05:30

Feb 2 2000 13:35:07 +05:30 lost+found

.ssh

45313 drwx

75521 drwx

90625 drwx

4096 Nov 17 2011 17:36:12 +05:30 core

4096 Feb 2 2000 13:35:11 +05:30 .prst_sync

4096 Feb 2 2000 13:35:22 +05:30 .rollback_timer

105729 drwx

30209 drwx

8192 Nov 21 2011 22:57:55 +05:30 tracelogs

4096 Feb 2 2000 13:36:17 +05:30 .installer

1339412480 bytes total (1199448064 bytes free)

Router# copy nvram:startup-config bootflash:

Destination filename [startup-config]?

3517 bytes copied in 0.647 secs (5436 bytes/sec)

Router# dir bootflash:

Directory of bootflash:/

11 drwx 16384 Feb 2 2000 13:33:40 +05:30 lost+found

15105 drwx 4096 Feb 2 2000 13:35:07 +05:30 .ssh

45313 drwx

75521 drwx

4096 Nov 17 2011 17:36:12 +05:30 core

4096 Feb 2 2000 13:35:11 +05:30 .prst_sync

90625 drwx

12 -rw-

105729 drwx

4096 Feb 2 2000 13:35:22 +05:30 .rollback_timer

0 Feb 2 2000 13:36:03 +05:30 tracelogs.878

8192 Nov 21 2011 23:02:13 +05:30 tracelogs

30209 drwx

13 -rw-

4096

1888

Feb 2 2000 13:36:17 +05:30

Nov 21 2011 23:03:17 +05:30

1339412480 bytes total (1199439872 bytes free)

.installer

startup-config

Example 2: Copying Startup Configuration File to USB Flash Disk

Router# dir usb0:

Directory of usb0:/

43261 -rwx 208904396 May 27 2008 14:10:20 -07:00 ncs4200rsp3-adventerprisek9.02.01.00.122-33.XNA.bin

255497216 bytes total (40190464 bytes free)

Router# copy nvram:startup-config usb0:

Destination filename [startup-config]?

3172 bytes copied in 0.214 secs (14822 bytes/sec)

Router# dir usb0:

Directory of usb0:/

43261 -rwx 208904396 May 27 2008 14:10:20 -07:00 ncs4200rsp3-adventerprisek9.02.01.00.122-33.XNA.bin

43262 -rwx

3172 Jul 2 2008 15:40:45 -07:00 startup-config 255497216 bytes total (40186880 bytes free)

Example 3: Copying Startup Configuration File to a TFTP Server

Router# copy bootflash:startup-config tftp:

Address or name of remote host []?

172.17.16.81

Destination filename [pe24_confg]?

/auto/tftp-users/user/startup-config

!!

3517 bytes copied in 0.122 secs (28828 bytes/sec)

For more detailed information on managing configuration files, see the Configuration Fundamentals

Configuration Guide, Cisco IOS XE Release 3S .

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

13

Using Cisco IOS XE Software

Filtering Output from the show and more Commands

Filtering Output from the show and more Commands

You can search and filter the output of show and more commands. This functionality is useful if you need to sort through large amounts of output or if you want to exclude output that you need not see.

To use this functionality, enter a show or more command followed by the “pipe” character ( | ); one of the keywords begin , include , or exclude ; and a regular expression on which you want to search or filter (the expression is case sensitive):

show command | { append | begin | exclude | include | redirect | section | tee | count } regular-expression

The output matches certain lines of information in the configuration file. The following example illustrates how to use output modifiers with the show interface command when you want the output to include only lines in which the expression “protocol” appears:

Router# show interface | include protocol

GigabitEthernet0/0/0 is up, line protocol is up

Serial4/0/0 is up, line protocol is up

Serial4/1/0 is up, line protocol is up

Serial4/2/0 is administratively down, line protocol is down

Serial4/3/0 is administratively down, line protocol is down

Powering Off the Router

Before you turn off a power supply, make certain the chassis is grounded and you perform a soft shutdown on the power supply. Not performing a soft shutdown will often not harm the router, but may cause problems in certain scenarios.

To perform a soft shutdown before powering off the router, enter the reload command to halt the system and then wait for ROM Monitor to execute before proceeding to the next step.

The following screenshot shows an example of this process:

Router# reload

Proceed with reload? [confirm]

*Jun 18 19:38:21.870: %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload command.

Place the power supply switch in the Off position after seeing this message.

Finding Support Information for Platforms and Cisco Software

Images

Cisco software is packaged in feature sets consisting of software images that support specific platforms. The feature sets available for a specific platform depend on which Cisco software images are included in a release.

To identify the set of software images available in a specific release or to find out if a feature is available in a given Cisco IOS XE software image, you can use Cisco Feature Navigator or the software release notes.

14

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Using Cisco IOS XE Software

Using Cisco Feature Navigator

Using Cisco Feature Navigator

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco

Feature Navigator enables you to determine which Cisco IOS XE software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn . An account on Cisco.com is not required.

Using Software Advisor

To see if a feature is supported by a Cisco IOS XE release, to locate the software document for that feature, or to check the minimum software requirements of Cisco IOS XE software with the hardware installed on your router, Cisco maintains the Software Advisor tool on Cisco.com at http://www.cisco.com/cgi-bin/Support/CompNav/Index.pl.

You must be a registered user on Cisco.com to access this tool.

Using Software Release Notes

Cisco IOS XE software releases include release notes that provide the following information:

• Platform support information

• Memory recommendations

• New feature information

• Open and resolved severity 1 and 2 caveats for all platforms

Release notes are intended to be release-specific for the most current release, and the information provided in these documents may not be cumulative in providing information about features that first appeared in previous releases. Refer to Cisco Feature Navigator for cumulative feature information.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

15

Using Software Release Notes

Using Cisco IOS XE Software

16

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

C H A P T E R

2

Console Port Telnet and SSH Handling

This chapter covers the following topics:

Important Notes and Restrictions, on page 17

Console Port Overview, on page 17

Connecting Console Cables, on page 18

Installing USB Device Drivers, on page 18

Console Port Handling Overview, on page 18

Telnet and SSH Overview, on page 18

Persistent Telnet and Persistent SSH Overview, on page 18

Configuring a Console Port Transport Map, on page 19

Configuring Persistent Telnet, on page 21

Configuring Persistent SSH, on page 23

Viewing Console Port, SSH, and Telnet Handling Configurations, on page 27

Important Notes and Restrictions

• The Telnet and SSH settings made in the transport map override any other Telnet or SSH settings when the transport map is applied to the Management Ethernet interface.

• Only local usernames and passwords can be used to authenticate users entering a Management Ethernet interface. AAA authentication is not available for users accessing the router through a Management

Ethernet interface using persistent Telnet or persistent SSH.

• Applying a transport map to a Management Ethernet interface with active Telnet or SSH sessions can disconnect the active sessions. Removing a transport map from an interface, however, does not disconnect any active Telnet or SSH sessions.

• Configuring the diagnostic and wait banners i s optional but recommended. The banners are especially useful as indicators to users of the status of their Telnet or SSH attempts.

Console Port Overview

The console port on the chassis is an EIA/TIA-232 asynchronous, serial connection with no flow control and an RJ-45 connector. The console port is used to access the chassis and is located on the front panel of the

Route Switch Processor (RSP).

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

17

Console Port Telnet and SSH Handling

Connecting Console Cables

For information on accessing the chassis using the console port, see the “Accessing the CLI Using a Console” section on page 1-4 .

Connecting Console Cables

For information about connecting console cables to the chassis, see the NCS 4200 Hardware Installation

Guides.

Installing USB Device Drivers

For instructions on how to install device drivers in order to use the USB console port, see the NCS 4200

Hardware Installation Guides.

Console Port Handling Overview

Users using the console port to access the chassis are automatically directed to the IOS command-line interface, by default.

If a user is trying to access the router through the console port and sends a break signal (a break signal can be sent by entering Ctrl-C or Ctrl-Shift-6 , or by entering the send break command at the Telnet prompt ) before connecting to the IOS command-line interface, the user is directed into diagnostic mode by default if the non-RPIOS sub-packages can be accessed.

These settings can be changed by configuring a transport map for the console port and applying that transport map to the console interface.

Telnet and SSH Overview

Telnet and Secure Shell (SSH) can be configured and handled like Telnet and SSH on other Cisco platforms.

For information on traditional Telnet, see the line command in the Cisco IOS Terminal Services Command

Reference guide located at http://www.cisco.com/en/US/docs/ios/12_2/termserv/command/reference/trflosho.html#wp1029818.

For information on configuring traditional SSH, see the Secure Shell Configuration Guide, Cisco IOS XE

Release 3S

The chassis also supports persistent Telnet and persistent SSH. Persistent Telnet and persistent SSH allow network administrators to more clearly define the treatment of incoming traffic when users access the router through the Management Ethernet port using Telnet or SSH. Notably, persistent Telnet and persistent SSH provide more robust network access by allowing the router to be configured to be accessible through the

Ethernet Management port using Telnet or SSH even when the IOS process has failed.

Persistent Telnet and Persistent SSH Overview

In traditional Cisco routers, accessing the router using Telnet or SSH is not possible in the event of an IOS failure. When Cisco IOS fails on a traditional Cisco router, the only method of accessing the router is through

18

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Console Port Telnet and SSH Handling

Configuring a Console Port Transport Map the console port. Similarly, if all active IOS processes have failed on a chassis that is not using persistent

Telnet or persistent SSH, the only method of accessing the router is through the console port.

With persistent Telnet and persistent SSH, however, users can configure a transport map that defines the treatment of incoming Telnet or SSH traffic on the Management Ethernet interface. Among the many configuration options, a transport map can be configured to direct all traffic to the IOS command-line interface, diagnostic mode, or to wait for an IOS vty line to become available and then direct users into diagnostic mode when the user sends a break signal while waiting for the IOS vty line to become available. If a user uses Telnet or SSH to access diagnostic mode, that Telnet or SSH connection will be usable even in scenarios when no

IOS process is active. Therefore, persistent Telnet and persistent SSH introduce the ability to access the router via diagnostic mode when the IOS process is not active. For information on diagnostic mode, see the

“Understanding Diagnostic Mode” section on page 1-3 .

For more information on the various other options that are configurable using persistent Telnet or persistent

SSH transport map see the

Configuring Persistent Telnet, on page 21

and the

Configuring Persistent SSH, on page 23

.

Configuring a Console Port Transport Map

This task describes how to configure a transport map for a console port interface.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action enable

Example:

Router> enable configure terminal

Example:

Purpose

Enables privileged EXEC mode.

• Enter your password if prompted.

Enters global configuration mode.

Router# configure terminal transport-map type console transport-map-name

Example:

Creates and names a transport map for handling console connections, and enter transport map configuration mode.

Router(config)# transport-map type console consolehandler connection wait [ allow interruptible | none ] Specifies how a console connection will be handled using this transport map:

Example:

Router(config-tmap)# connection wait none

Example:

• allow interruptible —The console connection waits for an IOS vty line to become available, and also allows user to enter diagnostic mode by interrupting a console connection waiting for the IOS vty

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

19

Console Port Telnet and SSH Handling

Examples

Step 5

Command or Action banner [

Example:

Enter TEXT message.

End with the character 'X'.

Example:

--Welcome to Diagnostic Mode--

Example: diagnostic | wait ] banner-message

Router(config-tmap)# banner diagnostic

X

Example:

(Optional) Creates a banner message that will be seen by users entering diagnostic mode or waiting for the IOS vty line as a result of the console transport map configuration.

• diagnostic —Creates a banner message seen by users directed into diagnostic mode as a result of the console transport map configuration.

• wait —Creates a banner message seen by users waiting for the IOS vty to become available.

• banner-message —The banner message, which begins and ends with the same delimiting character.

X

Example:

Purpose line to become available. This is the default setting.

Note Users can interrupt a waiting connection by entering Ctrl-C or

Ctrl-Shift-6 .

• none —The console connection immediately enters diagnostic mode.

Router(config-tmap)#

Example:

Step 6

Step 7 exit

Example:

Exits transport map configuration mode to re-enter global configuration mode.

Router(config-tmap)# exit

transport type console console-line-number

input transport-map-name

Example:

Router(config)# transport type console

0 input consolehandler

Applies the settings defined in the transport map to the console interface.

The transport-map-name for this command must match the transport-map-name defined in the transport-map type console comm and.

Examples

In the following example, a transport map to set console port access policies is created and attached to console port 0:

20

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Console Port Telnet and SSH Handling

Configuring Persistent Telnet

Router(config)# transport-map type console consolehandler

Router(config-tmap)# connection wait allow interruptible

Router(config-tmap)# banner diagnostic X

Enter TEXT message.

End with the character 'X'.

Welcome to diagnostic mode

X

Router(config-tmap)# banner wait X

Enter TEXT message.

End with the character 'X'.

Waiting for IOS vty line

X

Router(config-tmap)# exit

Router(config)# transport type console 0 input consolehandler

Configuring Persistent Telnet

Before you begin

For a persistent Telnet connection to access an IOS vty line on the chassis, local login authentication must be configured for the vty line (the login command in line configuration mode). If local login authentication is not configured, users will not be able to access IOS using a Telnet connection into the Management Ethernet interface with an applied transport map. Diagnostic mode will still be accessible in this scenario.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action enable

Example:

Router> enable configure terminal

Example:

Purpose

Enables privileged EXEC mode.

• Enter your password if prompted.

Enters global configuration mode.

Router# configure terminal transport-map type persistent telnet transport-map-name

Example:

Creates and names a transport map for handling persistent Telnet connections, and enters transport map configuration mode.

Router(config)# transport-map type persistent telnet telnethandler connection wait [ allow { interruptible }| none

{ disconnect }]

Specifies how a persistent Telnet connection will be handled using this transport map:

Example:

Router(config-tmap)# connection wait none

Example:

• allow —The Telnet connection waits for an IOS vty line to become available, and exits the router if interrupted.

• allow interruptible —The Telnet connection waits for the IOS vty line to

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

21

Console Port Telnet and SSH Handling

Configuring Persistent Telnet

Step 5

Command or Action banner [

Example:

Enter TEXT message.

End with the character 'X'.

Example:

--Welcome to Diagnostic Mode--

Example: diagnostic | wait ] banner-message

Router(config-tmap)# banner diagnostic

X

Example:

(Optional) Creates a banner message that will be seen by users entering diagnostic mode or waiting for the IOS vty line as a result of the persistent Telnet configuration.

• diagnostic —creates a banner message seen by users directed into diagnostic mode as a result of the persistent Telnet configuration.

• wait —creates a banner message seen by users waiting for the vty line to become available.

• banner-message —the banner message, which begins and ends with the same delimiting character.

X

Example:

Purpose become available, and also allows user to enter diagnostic mode by interrupting a

Telnet connection waiting for the IOS vty line to become available. This is the default setting.

Note Users can interrupt a waiting connection by entering Ctrl-C or

Ctrl-Shift-6 .

• none —The Telnet connection immediately enters diagnostic mode.

• none disconnect —The Telnet connection does not wait for the IOS vty line and does not enter diagnostic mode, so all Telnet connections are rejected if no vty line is immediately available in IOS.

Router(config-tmap)#

Example:

Step 6 transport interface type num

Example:

Applies the transport map settings to the

Management Ethernet interface (interface gigabitethernet 0).

Router(config-tmap)# transport interface gigabitethernet 0

Persistent Telnet can only be applied to the

Management Ethernet interface on the chassis.

This step must be taken before applying the transport map to the Management Ethernet interface.

22

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Console Port Telnet and SSH Handling

Examples

Step 7

Step 8

Command or Action exit

Example:

Purpose

Exits transport map configuration mode to re-enter global configuration mode.

Router(config-tmap)# exit transport type persistent telnet input transport-map-name

Applies the settings defined in the transport map to the Management Ethernet interface.

Example:

Router(config)# transport type persistent telnet input telnethandler

The transport-map-name for this command must match the transport-map-name defined in the transport-map type persistent telnet comm and.

Examples

In the following example, a transport map that will make all Telnet connections wait for an IOS vty line to become available before connecting to the router, while also allowing the user to interrupt the process and enter diagnostic mode, is configured and applied to the Management Ethernet interface (interface gigabitethernet

0).

A diagnostic and a wait banner are also configured.

The transport map is then applied to the interface when the transport type persistent telnet input command is entered to enable persistent Telnet.

Router(config)# transport-map type persistent telnet telnethandler

Router(config-tmap)# connection wait allow interruptible

Router(config-tmap)# banner diagnostic X

Enter TEXT message.

End with the character 'X'.

--Welcome to Diagnostic Mode--

X

Router(config-tmap)# banner wait X

Enter TEXT message.

End with the character 'X'.

--Waiting for IOS Process--

X

Router(config-tmap)# transport interface gigabitethernet 0

Router(config-tmap)# exit

Router(config)# transport type persistent telnet input telnethandler

Configuring Persistent SSH

This task describes how to configure persistent SSH.

Procedure

Step 1

Command or Action enable

Example:

Purpose

Enables privileged EXEC mode.

• Enter your password if prompted.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

23

Console Port Telnet and SSH Handling

Configuring Persistent SSH

Step 2

Step 3

Step 4

Step 5

Command or Action

Router> enable configure terminal

Example:

Purpose

Enters global configuration mode.

Router# configure terminal transport-map type persistent ssh transport-map-name

Example:

Creates and names a transport map for handling persistent SSH connections, and enters transport map configuration mode.

Router(config)# transport-map type persistent ssh sshhandler connection wait [ allow { interruptible }| none

{ disconnect }]

Specifies how a persistent SSH connection will be handled using this transport map:

Example:

Router(config-tmap)# connection wait allow interruptible

Example:

• allow —The SSH connection waits for the vty line to become available, and exits the router if interrupted.

• allow interruptible —The SSH connection waits for the vty line to become available, and also allows users to enter diagnostic mode by interrupting a SSH connection waiting for the vty line to become available. This is the default setting.

Note Users can interrupt a waiting connection by entering Ctrl-C or

Ctrl-Shift-6 .

• none —The SSH connection immediately enters diagnostic mode.

• none disconnect —The SSH connection does not wait for the vty line from IOS and does not enter diagnostic mode, so all SSH connections are rejected if no vty line is immediately available.

rsa keypair-name rsa-keypair-name

Example:

Router(config-tmap)# rsa keypair-name sshkeys

Names the RSA keypair to be used for persistent SSH connections.

For persistent SSH connections, the RSA keypair name must be defined using this command in transport map configuration mode. The RSA keypair definitions defined elsewhere on the router, such as through the use of the ip ssh rsa keypair-name command, do not apply to persistent SSH connections.

24

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Console Port Telnet and SSH Handling

Configuring Persistent SSH

Step 6

Step 7

Step 8

Step 9

Step 10

Step 11

Command or Action Purpose

No rsa-keypair-name is defined by default.

authentication-retriesnumber-of-retries

Example:

(Optional) Specifies the number of authentication retries before dropping the connection.

The default number-of-retries is 3.

Router(config-tmap)# authentication-retries 4 banner [

Example: diagnostic | wait ] banner-message

Router(config-tmap)# banner diagnostic

X

(Optional) Creates a banner message that will be seen by users entering diagnostic mode or waiting for the vty line as a result of the persistent SSH configuration.

Example:

Enter TEXT message.

End with the character 'X'.

Example:

--Welcome to Diagnostic Mode--

Example:

• diagnostic —Creates a banner message seen by users directed into diagnostic mode as a result of the persistent SSH configuration.

• wait —Creates a banner message seen by users waiting for the vty line to become active.

• banner-message —The banner message, which begins and ends with the same delimiting character.

X

Example:

Router(config-tmap)#

time-outtimeout-interval

Example:

(Optional) Specifies the SSH time-out interval in seconds.

The default timeout-interval is 120 seconds.

Router(config-tmap)# time-out 30

transport interface type num

Example:

Applies the transport map settings to the

Management Ethernet interface (interface gigabitethernet 0).

Router(config-tmap)# transport interface gigabitethernet 0

Persistent SSH can only be applied to the

Management Ethernet interface on the chassis.

exit

Example:

Exits transport map configuration mode to re-enter global configuration mode.

Router(config-tmap)# exit transport type persistent ssh input transport-map-name

Example:

Applies the settings defined in the transport map to the Management Ethernet interface.

The transport-map-name for this command must match the transport-map-name defined

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

25

Console Port Telnet and SSH Handling

Examples

Command or Action

Router(config)# transport type persistent ssh input sshhandler

Purpose in the transport-map type persistent ssh command .

Examples

In the following example, a transport map that will make all SSH connections wait for the vty line to become active before connecting to the router is configured and applied to the Management Ethernet interface (interface gigabitethernet 0). The RSA keypair is named sshkeys.

This example only uses the commands required to configure persistent SSH.

Router(config)# transport-map type persistent ssh sshhandler

Router(config-tmap)# connection wait allow

Router(config-tmap)# rsa keypair-name sshkeys

Router(config-tmap)# transport interface gigabitethernet 0

In the following example, a transport map is configured that will apply the following settings to any users attempting to access the Management Ethernet port via SSH:

• Users using SSH will wait for the vty line to become active, but will enter diagnostic mode if the attempt to access IOS through the vty line is interrupted.

• The RSA keypair name is “sshkeys”

• The connection allows one authentication retry.

• The banner “--Welcome to Diagnostic Mode--” will appear if diagnostic mode is entered as a result of

SSH handling through this transport map.

• The banner “--Waiting for vty line--” will appear if the connection is waiting for the vty line to become active.

The transport map is then applied to the interface when the transport type persistent ssh input command is entered to enable persistent SSH.

Router(config)# transport-map type persistent ssh sshhandler

Router(config-tmap)# connection wait allow interruptible

Router(config-tmap)# rsa keypair-name sshkeys

Router(config-tmap)# authentication-retries 1

Router(config-tmap)# banner diagnostic X

Enter TEXT message.

End with the character 'X'.

--Welcome to Diagnostic Mode--

X

Router(config-tmap)#banner wait X

Enter TEXT message.

End with the character 'X'.

--Waiting for vty line--

X

Router(config-tmap)# time-out 30

Router(config-tmap)# transport interface gigabitethernet 0

26

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Console Port Telnet and SSH Handling

Viewing Console Port, SSH, and Telnet Handling Configurations

Router(config-tmap)# exit

Router(config)# transport type persistent ssh input sshhandler

Viewing Console Port, SSH, and Telnet Handling Configurations

Use the show transport-map all name transport-map-name | type console persistent ssh telnet ]]] EXEC or privileged EXEC command to view the transport map configurations.

In the following example, a console port, persistent SSH, and persistent Telnet transport are configured on the router and various forms of the show transport-map command are entered to illustrate the various ways the show transport-map command can be entered to gather transport map configuration information.

Router# show transport-map all

Transport Map:

Name: consolehandler

Type: Console Transport

Connection:

Wait option: Wait Allow Interruptable

Wait banner:

Waiting for the IOS CLI bshell banner:

Welcome to Diagnostic Mode

Transport Map:

Name: sshhandler

Type: Persistent SSH Transport

Interface:

GigabitEthernet0

Connection:

Wait option: Wait Allow Interruptable

Wait banner:

Waiting for IOS prompt

Bshell banner:

Welcome to Diagnostic Mode

SSH:

Timeout: 120

Authentication retries: 5

RSA keypair: sshkeys

Transport Map:

Name: telnethandler

Type: Persistent Telnet Transport

Interface:

GigabitEthernet0

Connection:

Wait option: Wait Allow Interruptable

Wait banner:

Waiting for IOS process

Bshell banner:

Welcome to Diagnostic Mode

Transport Map:

Name: telnethandling1

Type: Persistent Telnet Transport

Connection:

Wait option: Wait Allow

Router# show transport-map type console

Transport Map:

Name: consolehandler

Type: Console Transport

Connection:

Wait option: Wait Allow Interruptable

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

27

Viewing Console Port, SSH, and Telnet Handling Configurations

Wait banner:

Waiting for the IOS CLI

Bshell banner:

Welcome to Diagnostic Mode

Router# show transport-map type persistent ssh

Transport Map:

Name: sshhandler

Type: Persistent SSH Transport

Interface:

GigabitEthernet0

Connection:

Wait option: Wait Allow Interruptable

Wait banner:

Waiting for IOS prompt

Bshell banner:

Welcome to Diagnostic Mode

SSH:

Timeout: 120

Authentication retries: 5

RSA keypair: sshkeys

Router# show transport-map type persistent telnet

Transport Map:

Name: telnethandler

Type: Persistent Telnet Transport

Interface:

GigabitEthernet0

Connection:

Wait option: Wait Allow Interruptable

Wait banner:

Waiting for IOS process

Bshell banner:

Welcome to Diagnostic Mode

Transport Map:

Name: telnethandling1

Type: Persistent Telnet Transport

Connection:

Wait option: Wait Allow

Router# show transport-map name telnethandler

Transport Map:

Name: telnethandler

Type: Persistent Telnet Transport

Interface:

GigabitEthernet0

Connection:

Wait option: Wait Allow Interruptable

Wait banner:

Waiting for IOS process

Bshell banner:

Welcome to Diagnostic Mode

Router# show transport-map name consolehandler

Transport Map:

Name: consolehandler

Type: Console Transport

Connection:

Wait option: Wait Allow Interruptable

Wait banner:

Waiting for the IOS CLI

Bshell banner:

Welcome to Diagnostic Mode

Router# show transport-map name sshhandler

Transport Map:

Name: sshhandler

Type: Persistent SSH Transport

28

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Console Port Telnet and SSH Handling

Console Port Telnet and SSH Handling

Viewing Console Port, SSH, and Telnet Handling Configurations

Interface:

GigabitEthernet0

Connection:

Wait option: Wait Allow Interruptable

Wait banner:

Waiting for IOS prompt

Bshell banner:

Welcome to Diagnostic Mode

SSH:

Timeout: 120

Authentication retries: 5

RSA keypair: sshkeys

Router#

The show platform software configuration access policy command can be used to view the current configurations for the handling of incoming console port, SSH, and Telnet connections. The output of this command provides the current wait policy for each type of connection, as well as any information on the currently configured banners. Unlike show transport-map , this command is available in diagnostic mode so it can be entered in cases when you need transport map configuration information but cannot access the IOS

CLI.

Router# show platform software configuration access policy

The current access-policies

Method : telnet

Rule : wait

Shell banner:

Wait banner :

Method

Rule

: ssh

: wait

Shell banner:

Wait banner :

Method : console

Rule : wait with interrupt

Shell banner:

Wait banner :

In the following example, the connection policy and banners are set for a persistent SSH transport map, and the transport map is enabled.

The show platform software configuration access policy output is given both before the new transport map is enabled and after the transport map is enabled so the changes to the SSH configuration are illustrated in the output.

Router# show platform software configuration access policy

The current access-policies

Method : telnet

Rule : wait with interrupt

Shell banner:

Welcome to Diagnostic Mode

Wait banner :

Waiting for IOS Process

Method : ssh

Rule : wait

Shell banner:

Wait banner :

Method : console

Rule : wait with interrupt

Shell banner:

Wait banner :

Router# configure terminal

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

29

Viewing Console Port, SSH, and Telnet Handling Configurations

Enter configuration commands, one per line.

End with CNTL/Z.

Router(config)# transport-map type persistent ssh sshhandler

Router(config-tmap)# connection wait allow interruptible

Router(config-tmap)# banner diagnostic X

Enter TEXT message.

End with the character 'X'.

Welcome to Diag Mode

X

Router(config-tmap)# banner wait X

Enter TEXT message.

End with the character 'X'.

Waiting for IOS

X

Router(config-tmap)# rsa keypair-name sshkeys

Router(config-tmap)# transport interface gigabitethernet 0

Router(config-tmap)# exit

Router(config)# transport type persistent ssh input sshhandler

Router(config)# exit

Router# show platform software configuration access policy

The current access-policies

Method : telnet

Rule : wait with interrupt

Shell banner:

Welcome to Diagnostic Mode

Wait banner :

Waiting for IOS process

Method : ssh

Rule : wait with interrupt

Shell banner:

Welcome to Diag Mode

Wait banner :

Waiting for IOS

Method

Rule

Shell banner:

Wait banner :

: console

: wait with interrupt

Console Port Telnet and SSH Handling

30

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

C H A P T E R

3

Configuring Clocking and Timing

This chapter explains how to configure timing ports on the Route Switch Processor (RSP) modules and includes the following sections:

Clocking and Timing Restrictions, on page 31

Clocking and Timing Overview, on page 33

Configuring Clocking and Timing, on page 45

Verifying the Configuration, on page 78

Troubleshooting, on page 79

Configuration Examples, on page 80

Clocking and Timing Restrictions

The following clocking and timing restrictions apply to the chassis:

• Interfaces carrying PTP traffic must be under the same VPN Routing and Forwarding (VRF).

Misconfiguration will cause PTP packet loss.

Use the 10 Gigabit Links to configure VRF on two Cisco RSP3 Routers.

• You can configure only a single clocking input source within each group of eight ports (0–7 and 8–15) on the T1/E1 interface module using the network-clock input-source command.

• Multicast timing is not supported.

• Out-of-band clocking and the recovered-clock command are not supported.

• Precision Time Protocol (PTP) is supported only on loopback interfaces.

• Synchronous Ethernet clock sources are not supported with PTP. Conversely, PTP clock sources are not supported with synchronous Ethernet except when configured as hybrid clock. However, you can use hybrid clocking to allow the chassis to obtain frequency using Synchronous Ethernet, and phase using

PTP.

• Time of Day (ToD) and 1 Pulse per Second (1PPS) input is not supported when the chassis is in boundary clock mode.

• Multiple ToD clock sources are not supported.

• PTP redundancy is supported only on unicast negotiation mode; you can configure up to three server clocks in redundancy mode.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

31

Configuring Clocking and Timing

Clocking and Timing Restrictions

• In order to configure time of day input, you must configure both an input 10 Mhz and an input 1 PPS source.

• PTP over IPv6 is not supported.

• SyncE Rx and Tx is supported on uplink interfaces when using 8 x 1 GE Gigabit Ethernet SFP Interface

Module.

• When PTP is configured, changing the configuration mode from LAN to WAN or WAN to LAN is not supported for following IMs:

• 2x10G

• 8x1G_1x10G_SFP

• 8x1G_1x10G_CU

• PTP functionality is restricted by license type.

Note If you install the IEEE 1588-2008 BC/MC licenseIEEE 1588-2008 BC/MC license (available by default), you must reload the chassis to use the full PTP functionality.

Note By default, all timing licenses are already included on the Cisco NCS 4200 routers.

• End-to-end Transparent Clock is not supported for PTP over Ethernet.

• Transparent clock is not supported on the Cisco RSP3 Module.

• G.8265.1 telecom profiles are not supported with PTP over Ethernet.

• The chassis does not support a mix of IPv4 and Ethernet clock ports when acting as a transparent clock or boundary clock.

The following restrictions apply when configuring synchronous Ethernet SSM and ESMC:

• To use the network-clock synchronization ssm option command, ensure that the chassis configuration does not include the following:

• Input clock source

• Network clock quality level

• Network clock source quality source (synchronous Ethernet interfaces)

• The network-clock synchronization ssm option command must be compatible with the network-clock eec command in the configuration.

• To use the network-clock synchronization ssm option command, ensure that there is not a network clocking configuration applied to synchronous Ethernet interfaces, BITS interfaces, and timing port interfaces.

32

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Restrictions on RSP3 Module

• SSM and ESMC are SSO-coexistent, but not SSO-compliant. The chassis goes into hold-over mode during switchover and restarts clock selection when the switchover is complete.

• The chassis does not support ESMC messages on the S1 byte on SONET/SDH and T1/E1 interface modules.

• It is recommended that you do not configure multiple input sources with the same priority as this impacts the TSM (Switching message delay).

• You can configure a maximum of 4 clock sources on interface modules, with a maximum of 2 per interface module. This limitation applies to both synchronous Ethernet and TDM interfaces.

• When you configure the ports using the synchronous mode command on a copper interface, the port attempts to auto-negotiate with the peer-node copper port and hence the auto negotiation is incomplete as both the ports try to act as server clock, which in turn makes the port down. Hence, for a successful clock sync to happen, you should configure the ports using network-clock input-source 1 interface interface id command prior to the configuration using the synchronous mode command under the interfaces to ensure that one of the ports behaves as a server clock.

It is not recommended to configure the copper ports using the synchronous mode command.

Restrictions on RSP3 Module

The following clocking and timing restrictions are supported on the RSP3 Module:

• Precision Time Protocol (PTP) is supported only on the routed interfaces.

• Transparent Clock over 1 Gigabit Ethernet port performance is not good.

• PTP is supported for LAN for the following IMs. WAN is not supported.

• 2x40

• 1x100 GE

• 8x10 GE

• To shift from non hybrid clock configuration to hybrid clock configuration, you must first unconfigure

PTP, unconfigure netsync, reconfigure netsync and configure hybrid PTP.

Clocking and Timing Overview

The chassis have the following timing ports:

• 1 PPS Input/Output

• 10 Mhz Input/Output

• ToD

• Building Integrated Timing Supply (BITS)

You can use the timing ports on the chassis to perform the following tasks:

• Provide or receive 1 PPS messages

• Provide or receive time of day (ToD) messages

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

33

Configuring Clocking and Timing

Understanding PTP

• Provide output clocking at 10 Mhz, 2.048 Mhz, and 1.544 Mhz

• Receive input clocking at 10 Mhz, 2.048 Mhz, and 1.544 Mhz

Note Timing input and output is handled by the active RSP.

Note For timing redundancy, you can use a Y cable to connect a GPS timing source to multiple RSPs. For information, see the Cisco NCS 4206 Series Hardware Installation Guide .

SyncE is supported in both LAN and WAN mode on a 10 Gigabit Ethernet interface.

The following sections describe how to configure clocking and timing features on the chassis.

Understanding PTP

The Precision Time Protocol (PTP), as defined in the IEEE 1588 standard, synchronizes with nanosecond accuracy the real-time clocks of the devices in a network. The clocks in are organized into a server-member hierarchy. PTP identifies the switch port that is connected to a device with the most precise clock. This clock is referred to as the server clock. All the other devices on the network synchronize their clocks with the server and are referred to as members. Constantly exchanged timing messages ensure continued synchronization.

PTP is particularly useful for industrial automation systems and process control networks, where motion and precision control of instrumentation and test equipment are important.

Table 6: Nodes within a PTP Network

Network Element

Grandmaster (GM)

Ordinary Clock (OC)

Description

A network device physically attached to the server time source. All clocks are synchronized to the grandmaster clock.

An ordinary clock is a 1588 clock with a single PTP port that can operate in one of the following modes:

• Server mode—Distributes timing information over the network to one or more client clocks, thus allowing the client to synchronize its clock to the server.

• Client mode—Synchronizes its clock to a server clock. You can enable the client mode on up to two interfaces simultaneously in order to connect to two different server clocks.

Boundary Clock (BC) The device participates in selecting the best server clock and can act as the server clock if no better clocks are detected.

Boundary clock starts its own PTP session with a number of downstream clients. The boundary clock mitigates the number of network hops and results in packet delay variations in the packet network between the Grandmaster and Client clock.

Transparent Clock (TC) A transparent clock is a device or a switch that calculates the time it requires to forward traffic and updates the PTP time correction field to account for the delay, making the device transparent in terms of time calculations.

34

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Telecom Profiles

Telecom Profiles

Cisco IOS XE Release 3.8 introduces support for telecom profiles, which allow you to configure a clock to use the G.8265.1 recommendations for establishing PTP sessions, determining the best server clock, handling

SSM, and mapping PTP classes. For information about how to configure telecom profiles, see

Configuring

Clocking and Timing, on page 45 .

Effective Cisco IOS-XE Release 3.18, the G.8275.1 telecom profile is also supported on the Cisco NCS 4206

Series with RSP2 module. For more information, see G.8275.1 Telecom Profile .

PTP Redundancy

PTP redundancy is an implementation on different clock nodes. This helps the PTP subordinate clock node achieve the following:

• Interact with multiple server ports such as grand server clocks and boundary clock nodes.

• Open PTP sessions.

• Select the best server from the existing list of server clocks (referred to as the primary PTP server port or server clock source).

• Switch to the next best server available in case the primary server clock fails, or the connectivity to the primary server fails.

Note The Cisco NCS 4206 Series chassis supports unicast-based timing as specified in the 1588-2008 standard.

For instructions on how to configure PTP redundancy, see

Configuring PTP Redundancy, on page 65 .

PTP Asymmetry Readjustment

Each PTP node can introduce delay asymmetry that affects the adequate time and phase accuracy over the networks. Asymmetry in a network occurs when one-way-delay of forward path (also referred as forward path delay or ingress delay) and reverse path (referred as reverse path delay or egress delay) is different. The magnitude of asymmetry can be either positive or negative depending on the difference of the forward and reverse path delays.

Effective Cisco IOS XE Gibraltar 16.10.1, PTP asymmetry readjustment can be performed on each PTP node to compensate for the delay in the network.

Restriction

In default profile configuration, delay-asymmetry value is provided along with the clock source command.

This restricts it to change the delay-asymmetry value with a complete reconfiguration of clock source command.

The delay-asymmetry value should be considered as static and cannot be changed at run-time.

PTP Redundancy Using Hop-By-Hop Topology Design

Real world deployments for IEEE-1588v2 for mobile backhaul requires the network elements to provide synchronization and phase accuracy over IP or MPLS networks along with redundancy.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

35

Configuring Clocking and Timing

PTP Redundancy Using Hop-By-Hop Topology Design

In a ring topology, a ring of PTP boundary clock nodes are provisioned such that each boundary clock node provides synchronization to a number of PTP client clocks connected to it. Each such ring includes at least two PTP server clocks with a PRC traceable clock.

However, with this topology the following issues may occur:

• Node asymmetry and delay variation—In a ring topology, each boundary clock uses the same server, and the PTP traffic is forwarded through intermediate boundary clock nodes. As intermediate nodes do not correct the timestamps, variable delay and asymmetry for PTP are introduced based on the other traffic passing through such nodes, thereby leading to incorrect results.

• Clock redundancy—Clock redundancy provides redundant network path when a node goes down. In a ring topology with PTP, for each unicast PTP solution, the roles of each node is configured. The PTP clock path may not be able to reverse without causing timing loops in the ring.

No On-Path Support Topology

The topology (see

Figure 1: Deployment in a Ring - No On-Path Support with IPv4, on page 36 ) describes

a ring with no on-path support. S1 to S5 are the boundary clocks that use the same server clocks. GM1 and

GM2 are the grandmaster clocks. In this design, the following issues are observed:

• Timestamps are not corrected by the intermediate nodes.

• Difficult to configure the reverse clocking path for redundancy.

• Formation of timings loops.

Figure 1: Deployment in a Ring - No On-Path Support with IPv4

Table 7: PTP Ring Topology—No On-Path Support

Clock Nodes Behavior in the PTP Ring

GM1

GM2

Grandmaster Clock

Grandmaster Clock

S1 Server Clocks: M1 (1st), M2 (2nd)

36

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Hop-By-Hop Topology in a PTP Ring

Clock Nodes Behavior in the PTP Ring

S2

S3

Server Clocks: M1 (1st), M2 (2nd)

Server Clocks: M1 (1st), M2 (2nd)

S4

S5

Server Clocks: M2 (1st), M1 (2nd)

Server Clocks: M2 (1st), M1 (2nd)

A solution to the above issue is addressed by using Hop-by-Hop topology configuration.

Hop-By-Hop Topology in a PTP Ring

PTP Ring topology is designed by using Hop-By-Hop configuration of PTP boundary clocks. In this topology, each BC selects its adjacent nodes as PTP Server clocks, instead of using the same GM as the PTP server.

These PTP BC server clocks are traceable to the GM in the network. Timing loop are not formed between adjacent BC nodes. The hot Standby BMCA configuration is used for switching to next the best server during failure.

Prerequisites

• PTP boundary clock configuration is required on all clock nodes in the ring, except the server clock nodes (GM), which provide the clock timing to ring. In the above example (see Figure 5-1) nodes S1 ...

S5 must be configured as BC.

• The server clock (GM1 and GM2 in Figure 5-1) nodes in the ring can be either a OC server or BC server.

• Instead of each BC using same the GM as a PTP server, each BC selects its adjacent nodes as PTP server clocks. These PTP BC-server clocks are traceable to the GM in the network.

• Boundary clock nodes must be configured with the single-hop keyword in the PTP configuration to ensure that a PTP node can communicate with it’s adjacent nodes only.

Restrictions

• Timing loops should not exist in the topology. For example, if for a node there are two paths to get the same clock back, then the topology is not valid. Consider the following topology and configuration.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

37

Configuring Clocking and Timing

On-Path Support Topology Scenario

The paths with double arrows (>>) are the currently active clock paths and paths with single arrow (>) are redundant clock path. This configuration results in a timing loop if the link between the BC-1 and GM fails.

• In a BC configuration, the same loopback interface should never be used for both Server and Client port configuration.

• Single-hop keyword is not supported for PTP over MPLS with explicit null configuration. The Single-hop keyword is not supported when PTP packets are sent out with a MPLS tag.

On-Path Support Topology Scenario

Consider the topology as shown in Figure 5-1.

38

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Figure 2: PTP Ring Topology—On-Path Support

On-Path Support Topology Scenario

Table 8: PTP Ring Topology—On-Path Support

Clock Node Behavior in the PTP Ring

GM1

GM2

BC1

BC2

Grandmaster Clock

Grandmaster Clock

Server Clocks: M1 (1st), BC2 (2nd)

Client Clocks: BC2

Server Clocks: BC1(1st), BC3 (2nd)

Client Clocks: BC1, BC3

BC3

BC4

BC5

Server Clocks: BC2 (1st), BC4 (2nd)

Client Clocks: BC2, BC4

Server Clocks: BC5 (1st), BC3 (2nd)

Client Clocks: BC3, BC5

Server Clocks: M2(1st), BC4 (2nd)

Client Clocks: BC4

Now consider there is a failure between BC1 and BC2 (see Figure 5-3). In this case, the BC2 cannot communicate with GM1. Node BC2 receives the clock from BC3, which in turn receives the clock from GM2.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

39

On-Path Support Topology Scenario

Figure 3: Deployment in a Ring—On-Path Support (Failure)

Configuring Clocking and Timing

Table 9: PTP Ring Topology—On-Path Support (Failure)

Clock Node Behavior in the PTP Ring

3

GM1 Grandmaster Clock

GM2

BC1

BC2

BC3

Grandmaster Clock

Server Clocks: M1 (1st), BC2 (2nd)

Client Clocks: BC2

Server Clocks: BC1(1st), BC3 (2nd)

Client Clocks: BC1, BC3

Server Clocks: BC2 (1st), BC4 (2nd)

Client Clocks: BC2, BC4

BC4 Server Clocks: BC5 (1st), BC3 (2nd)

Client Clocks: BC3, BC5

40

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Configuration Example

Clock Node Behavior in the PTP Ring

3

BC5 Server Clocks: M2(1st), BC4 (2nd)

Client Clocks: BC4

3

Red indicates that GM is not traceable and there is no path to the client.

Configuration Example

PTP Ring boundary clocks must be configured with single-hop keyword in PTP configuration. The PTP node can communicate with its adjacent nodes only. This is required for PTP hop-by-hop ring topology.

.

.

ptp clock boundary domain 0 clock-port client-port slave transport ipv4 unicast interface Lo0 negotiation single-hop clock source 1.1.1.1

clock source 2.2.2.2 1 clock-port server-port master transport ipv4 unicast interface Lo1 negotiation single-hop

Note The single-hop keyword is not supported for PTP over MPLS with explicit NULL configurations. The single-hop keyword is not supported when PTP packets are sent out with a MPLS tag.

For information on configuring PTP redundancy, see

Configuring PTP Redundancy, on page 65

.

BMCA

Starting Cisco IOS XE Release 3.15, BMCA is supported on the chassis.

The BMCA is used to select the server clock on each link, and ultimately, select the grandmaster clock for the entire Precision Time Protocol (PTP) domain. BCMA runs locally on each port of the ordinary and boundary clocks, and selects the best clock.

The best server clock is selected based on the following parameters:

• Priority—User-configurable value ranging from 0 to 255; lower value takes precedence

• Clock Class—Defines the traceability of time or frequency from the grandmaster clock

• Alarm Status—Defines the alarm status of a clock; lower value takes precedence

By changing the user-configurable values, network administrators can influence the way the grandmaster clock is selected.

BMCA provides the mechanism that allows all PTP clocks to dynamically select the best server clock

(grandmaster) in an administration-free, fault-tolerant way, especially when the grandmaster clocks changes.

For information on configuring BMCA, see

Configuring an Ordinary Clock, on page 45

and

Configuring a

Boundary Clock, on page 53 .

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

41

Configuring Clocking and Timing

Hybrid BMCA

Hybrid BMCA

Configuration Example

In hybrid BMCA implementation, the phase is derived from a PTP source and frequency is derived from a physical lock source. More than one server clock is configured in this model and the best server clock is selected. If the physical clock goes down, then PTP is affected.

Hybrid BMCA on Ordinary Clock ptp clock ordinary domain 0 hybrid clock-port client-port slave transport ipv4 unicast interface Lo0 negotiation clock source 133.133.133.133

clock source 144.144.144.144 1 clock source 155.155.155.155 2

Network-clock input-source 10 interface gigabitEthernet 0/4/0

Hybrid BMCA on Boundary Clock ptp clock boundary domain 0 hybrid clock-port client-port slave transport ipv4 unicast interface Lo0 negotiation clock source 133.133.133.133

clock source 144.144.144.144 1 clock source 155.155.155.155 2 clock-port server-port master transport ipv4 unicast interface Lo1 negotiation

Network-clock input-source 10 interface gigabitEthernet 0/4/0

Hybrid Clocking

The Cisco NCS 4206 Series Chassis support a hybrid clocking mode that uses clock frequency obtained from the synchronous Ethernet port while using the phase (ToD or 1 PPS) obtained using PTP. The combination of using physical source for frequency and PTP for time and phase improves the performance as opposed to using only PTP.

Note When configuring a hybrid clock, ensure that the frequency and phase sources are traceable to the same server clock.

For more information on how to configure hybrid clocking, see

Configuring a Hybrid Clock, on page 57 .

Transparent Clocking

A transparent clock is a network device such as a switch that calculates the time it requires to forward traffic and updates the PTP time correction field to account for the delay, making the device transparent in terms of timing calculations. The transparent clock ports have no state because the transparent clock does not need to synchronize to the grandmaster clock.

There are two kinds of transparent clocks:

• End-to-end transparent clock—Measures the residence time of a PTP message and accumulates the times in the correction field of the PTP message or an associated follow-up message.

42

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Time of Day (TOD)

• Peer-to-peer transparent clock— Measures the residence time of a PTP message and computes the link delay between each port and a similarly equipped port on another node that shares the link. For a packet, this incoming link delay is added to the residence time in the correction field of the PTP message or an associated follow-up message.

Note The Cisco NCS 4206 Series Chassis does not currently support peer-to-peer transparent clock mode.

For information on how to configure the Cisco NCS 4206 Series Chassis as a transparent clock, see

Configuring a Transparent Clock, on page 55

.

Time of Day (TOD)

You can use the time of day (ToD) and 1PPS ports on the Cisco NCS 4206 Series Chassis to exchange ToD clocking. In server mode, the chassis can receive time of day (ToD) clocking from an external GPS unit; the chassis requires a ToD, 1PPS, and 10MHZ connection to the GPS unit.

In client mode, the chassis can recover ToD from a PTP session and repeat the signal on ToD and 1PPS interfaces.

For instructions on how to configure ToD on the Cisco NCS 4206 Series Chassis, see the

Configuring an

Ordinary Clock, on page 45 .

Synchronizing the System Clock to Time of Day

You can set the chassis system time to synchronize with the time of day retrieved from an external GPS device.

For information on how to configure this feature, see

Synchronizing the System Time to a Time-of-Day

Source, on page 70 .

Timing Port Specifications

The following sections provide specifications for the timing ports on the Cisco NCS 4206 Series Chassis.

BITS Framing Support

The following table lists the supported framing modes for a BITS port.

Table 10: Framing Modes for a BITS Port on a Cisco NCS 4206 Chassis

T1

T1

E1

BITS or SSU Port Support Matrix Framing Modes Supported SSM or QL Support Tx

Port

E1

2048 kHz

T1 ESF

T1 SF

E1 CRC4

E1 FAS

2048 kHz

Yes

No

Yes

No

No

Yes

Yes

Yes

Yes

Yes

Rx

Port

Yes

Yes

Yes

Yes

Yes

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

43

Configuring Clocking and Timing

Understanding Synchronous Ethernet ESMC and SSM

The BITS port behaves similarly to the T1/E1 ports on the T1/E1 interface module; for more information about configuring T1/E1 interfaces, see the Configuring T1/E1 Interfaces document.

Understanding Synchronous Ethernet ESMC and SSM

Synchronous Ethernet incorporates the Synchronization Status Message (SSM) used in Synchronous Optical

Networking (SONET) and Synchronous Digital Hierarchy (SDH) networks. While SONET and SDH transmit the SSM in a fixed location within the frame, Ethernet Synchronization Message Channel (ESMC) transmits the SSM using a protocol: the IEEE 802.3 Organization-Specific Slow Protocol (OSSP) standard.

The ESMC carries a Quality Level (QL) value identifying the clock quality of a given synchronous Ethernet timing source. Clock quality values help a synchronous Ethernet node derive timing from the most reliable source and prevent timing loops.

When configured to use synchronous Ethernet, the chassis synchronizes to the best available clock source. If no better clock sources are available, the chassis remains synchronized to the current clock source.

The chassis supports two clock selection modes: QL-enabled and QL-disabled. Each mode uses different criteria to select the best available clock source.

For more information about Ethernet ESMC and SSM, see

Configuring Synchronous Ethernet ESMC and

SSM, on page 72 .

Note The chassis can only operate in one clock selection mode at a time.

Note PTP clock sources are not supported with synchronous Ethernet.

Clock Selection Modes

The chassis supports two clock selection modes, which are described in the following sections.

QL-Enabled Mode

In QL-enabled mode, the chassis considers the following parameters when selecting a clock source:

• Clock quality level (QL)

• Clock availability

• Priority

QL-Disabled Mode

In QL-disabled mode, the chassis considers the following parameters when selecting a clock source:

• Clock availability

• Priority

Note You can use override the default clock selection using the commands described in the

Managing Clock Source

Selection, on page 76

.

44

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Managing Clock Selection

Note 8275.1 profile does not support QL-disabled mode on RSP3.

Managing Clock Selection

You can manage clock selection by changing the priority of the clock sources; you can also influence clock selection by modifying modify the following clock properties:

• Hold-Off Time: If a clock source goes down, the chassis waits for a specific hold-off time before removing the clock source from the clock selection process. By default, the value of hold-off time is 300 ms.

• Wait to Restore: The amount of time that the chassis waits before including a newly active synchronous

Ethernet clock source in clock selection. The default value is 300 seconds.

• Force Switch: Forces a switch to a clock source regardless of clock availability or quality.

• Manual Switch: Manually selects a clock source, provided the clock source has a equal or higher quality level than the current source.

For more information about how to use these features, see

Managing Clock Source Selection, on page 76

.

Configuring Clocking and Timing

The following sections describe how to configure clocking and timing features on the chassis:

Configuring an Ordinary Clock

The following sections describe how to configure the chassis as an ordinary clock.

Configuring a Server Ordinary Clock

Follow these steps to configure the chassis to act as a Server ordinary clock.

Procedure

Step 1

Step 2 enable

Example:

Router> enable

Enables privileged EXEC mode.

• Enter your password if prompted.

configure terminal

Example:

Router# configure terminal

Enters configuration mode.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

45

Configuring Clocking and Timing

Configuring a Server Ordinary Clock

Step 3

Step 4

Step 5

Step 6

Step 7 platformptp masterprtc-only-enable

Example:

Router(config)# platform ptp master prtc-only-enable

(Optional) Enable port deletion of the server clock.

ptp clock { ordinary | boundary | e2e-transparent } domain domain-number

Example:

Router(config)# ptp clock ordinary domain 0

Example:

Router(config-ptp-clk)#

Configures the PTP clock. You can create the following clock types:

• ordinary—A 1588 clock with a single PTP port that can operate in Server or Client mode.

• boundary—Terminates PTP session from Grandmaster and acts as PTP Server or Client clocks downstream.

• e2e-transparent—Updates the PTP time correction field to account for the delay in forwarding the traffic.

This helps improve the accuracy of 1588 clock at client.

priority1 priorityvalue

Example:

Router(config-ptp-clk)# priority1 priorityvalue

Sets the preference level for a clock. client devices use the priority1 value when selecting a server clock: a lower priority1 value indicates a preferred clock. The priority1 value is considered above all other clock attributes.

Valid values are from 0-255. The default value is 128.

priority2 priorityvalue

Example:

Router(config-ptp-clk)# priority2 priorityvalue

Sets a secondary preference level for a clock. client devices use the priority2 value when selecting a server clock: a lower priority2 value indicates a preferred clock. The priority2 value is considered only when the chassis is unable to use priority1 and other clock attributes to select a clock.

Valid values are from 0-255. The default value is 128.

utc-offset value leap-second “date time” offset { -1 | 1 }

Example:

Router(config-ptp-clk)# utc-offset 45 leap-second “01-01-2017 00:00:00” offset 1

(Optional) Starting with Cisco IOS-XE Release 3.18SP, the new utc-offset CLI is used to set the UTC offset value.

Valid values are from 0-255. The default value is 36.

46

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Configuring a Server Ordinary Clock

Step 8

Step 9

Step 10

Step 11

(Optional) Starting with Cisco IOS-XE Release 3.18.1SP, you can configure the current UTC offset, leap second event date and Offset value (+1 or -1). Leap second configuration will work only when the frequency source is locked and ToD was up before.

• “date time” —Leap second effective date in dd-mm-yyyy hh:mm:ss format.

input [1pps] {R0 | R1}

Example:

Router(config-ptp-clk)# input 1pps R0

Enables Precision Time Protocol input 1PPS using a 1PPS input port.

Use R0 or R1 to specify the active RSP slot.

tod { R0 | R1} { ubx | nmea | cisco | ntp | cmcc }

Example:

Router(config-ptp-clk)# tod R0 ntp

Configures the time of day message format used by the ToD interface.

Note It is mandatory that when electrical ToD is used, the utc-offset command is configured before configuring the tod R0 , otherwise there will be a time difference of approximately 37 seconds between the server and client clocks.

Note The ToD port acts as an input port in case of server clock and as an output port in case of client clock.

clock-port port-name { master | slave } [ profile { g8265.1

}]

Example:

Router(config-ptp-clk)# clock-port server-port master

Defines a new clock port and sets the port to PTP Server or Client mode; in server mode, the port exchanges timing packets with PTP client devices.

The profile keyword configures the clock to use the G.8265.1 recommendations for establishing PTP sessions, determining the best server clock, handling SSM, and mapping PTP classes.

Note Using a telecom profile requires that the clock have a domain number of 4–23.

Do one of the following:

transport ipv4 unicast interface interface-type interface-number [negotiation]

• transport ethernet unicast [ negotiation ]

Example:

Router(config-ptp-port)# transport ipv4 unicast interface loopback 0 negotiation

Specifies the transport mechanism for clocking traffic; you can use IPv4 or Ethernet transport.

The negotiation keyword configures the chassis to discover a PTP server clock from all available PTP clock sources.

Note PTP redundancy is supported only on unicast negotiation mode.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

47

Configuring Clocking and Timing

Configuring a Server Ordinary Clock

Step 12

Step 13

Step 14

Step 15

Step 16 exit

Exits clock-port configuration.

network-clock synchronization automatic

Example:

Router(config)# network-clock synchronization automatic

Enables automatic selection of a clock source.

Note This command must be configured before any input source.

network-clock synchronization mode ql-enabled

Example:

Router(config)# network-clock synchronization mode ql-enabled

Enables automatic selection of a clock source based on quality level (QL).

Note This command is disabled by default.

Use one of the following options:

network-clock input-source priority controller { SONET | wanphy }

network-clock input-source priority external { R0 | R1 } [ 10m | 2m ]

network-clock input-source priority external { R0 | R1 } [ 2048k | e1 { cas { 120ohms | 75ohms | crc4 }}]

network-clock input-source priority external { R0 | R1 } [ 2048k | e1 { crc4 | fas ] { 120ohms | 75ohms }

{ linecode { ami | hdb3 }}

network-clock input-source priority external { R0 | R1 } [ t1 { d4 | esf | sf } { linecode { ami | b8zs }}]

network-clock input-source priority interface type/slot/port

Example:

Router(config)# network-clock input-source 1 external R0 10m

• (Optional) To nominate SDH or SONET controller as network clock input source.

• (Optional) To nominate 10Mhz port as network clock input source.

• (Optional) To nominate BITS port as network clock input source in e1 mode.

• (Optional) To nominate BITS port as network clock input source in e1 mode.

• (Optional) To nominate BITS port as network clock input source in t1 mode.

• (Optional) To nominate Ethernet interface as network clock input source.

clock destination source-address | mac-address { bridge-domain bridge-domain-id} | interface interface-name }

Example:

Router(config-ptp-port)# clock-source 8.8.8.1

Specifies the IP address or MAC address of a clock destination when the chassis is in PTP server mode.

48

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Configuring a Server Ordinary Clock

Step 17

Step 18

Step 19

Step 20

sync interval interval

Example:

Router(config-ptp-port)# sync interval -4

Specifies the interval used to send PTP synchronization messages. The intervals are set using log base 2 values, as follows:

• 1—1 packet every 2 seconds

• 0—1 packet every second

• -1—1 packet every 1/2 second, or 2 packets per second

• -2—1 packet every 1/4 second, or 4 packets per second

• -3—1 packet every 1/8 second, or 8 packets per second

• -4—1 packet every 1/16 seconds, or 16 packets per second.

• -5—1 packet every 1/32 seconds, or 32 packets per second.

• -6—1 packet every 1/64 seconds, or 64 packets per second.

• -7—1 packet every 1/128 seconds, or 128 packets per second.

announce interval interval

Example:

Router(config-ptp-port)# announce interval 2

Specifies the interval for PTP announce messages. The intervals are set using log base 2 values, as follows:

• 3—1 packet every 8 seconds

• 2—1 packet every 4 seconds

• 1—1 packet every 2 seconds

• 0—1 packet every second

• -1—1 packet every 1/2 second, or 2 packets per second

• -2—1 packet every 1/4 second, or 4 packets per second

• -3—1 packet every 1/8 second, or 8 packets per second end

Example:

Router(config-ptp-port)# end

Exit configuration mode.

linecode {ami | b8zs | hdb3}

Example:

Router(config-controller)# linecode ami

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

49

Configuring Clocking and Timing

Configuring a Client Ordinary Clock

Selects the linecode type.

• ami—Specifies Alternate Mark Inversion (AMI) as the linecode type. Valid for T1 and E1 controllers.

• b8zs—Specifies binary 8-zero substitution (B8ZS) as the linecode type. Valid for sonet controller only.

This is the default for T1 lines.

• hdb3—Specifies high-density binary 3 (hdb3) as the linecode type. Valid for E1 controller only. This is the default for E1 lines.

Example

The following example shows that the utc-offset is configured before configuring the ToD to avoid a delay of 37 seconds between the Server or Client clocks: ptp clock ordinary domain 24 local-priority 1 priority2 128 utc-offset 37 tod R0 cisco clock-port server-port-1 master profile g8275.1 local-priority 1 transport ethernet multicast interface Gig 0/0/1

Configuring a Client Ordinary Clock

Follow these steps to configure the chassis to act as a client ordinary clock.

Procedure

Step 1

Step 2

Step 3 enable

Example:

Router> enable

Enables privileged EXEC mode.

• Enter your password if prompted.

configure terminal

Example:

Router# configure terminal

Enter configuration mode.

ptp clock { ordinary | boundary | e2e-transparent } domain domain-number [ hybrid ]

Example:

Router(config)# ptp clock ordinary domain 0

50

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Configuring a Client Ordinary Clock

Step 4

Step 5

Step 6

Step 7

Configures the PTP clock. You can create the following clock types:

• ordinary—A 1588 clock with a single PTP port that can operate in Server or Client mode.

• boundary—Terminates PTP session from Grandmaster and acts as PTP Server to Client downstream.

• e2e-ransparent—Updates the PTP time correction field to account for the delay in forwarding the traffic.

This helps improve the acuracy of 1588 clock at client.

output [1pps] {R0 | R1} [ offset offset-value ] [ pulse-width value ]

Example:

Router(config-ptp-clk)# output 1pps R0 offset 200 pulse-width 20 μsec

Enables Precision Time Protocol input 1PPS using a 1PPS input port.

Use R0 or R1 to specify the active RSP slot.

Note Effective Cisco IOS XE Everest 16.6.1, the 1pps pulse bandwith can be changed from the default value of 500 milliseconds to up to 20 microseconds.

tod { R0 | R1} { ubx | nmea | cisco | ntp | cmcc }

Example:

Router(config-ptp-clk)# tod R0 ntp

Configures the time of day message format used by the ToD interface.

Note The ToD port acts as an input port in case of server clock and as an output port in case of client clock.

clock-port port-name { master | slave } [ profile { g8265.1

}]

Example:

Router(config-ptp-clk)# clock-port client-port slave

Sets the clock port to PTP Server or Client mode; in client mode, the port exchanges timing packets with a

PTP server clock.

The profile keyword configures the clock to use the G.8265.1 recommendations for establishing PTP sessions, determining the best server clock, handling SSM, and mapping PTP classes.

Note Using a telecom profile requires that the clock have a domain number of 4–23.

Do one of the following:

transport ipv4 unicast interface interface-type interface-number [negotiation]

• transport ethernet unicast [ negotiation ]

Example:

Router(config-ptp-port)# transport ipv4 unicast interface loopback 0 negotiation

Specifies the transport mechanism for clocking traffic; you can use IPv4 or Ethernet transport.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

51

Configuring Clocking and Timing

Configuring a Client Ordinary Clock

Step 8

Step 9

Step 10

Step 11

The negotiation keyword configures the chassis to discover a PTP server clock from all available PTP clock sources.

Note PTP redundancy is supported only on unicast negotiation mode.

clock source source-address | mac-address { bridge-domain bridge-domain-id } | interface interface-name }

[ priority ] [ delay-asymmetry delay asymmetry value nanoseconds ]

Example:

Router(config-ptp-port)# clock-source 8.8.8.1

Specifies the IP or MAC address of a PTP server clock.

• priority —Sets the preference level for a PTP clock.

• delay asymmetry value —Performs the PTP asymmetry readjustment on a PTP node to compensate for the delay in the network.

announce timeout value

Example:

Router(config-ptp-port)# announce timeout 8

Specifies the number of PTP announcement intervals before the session times out. Valid values are 1-10.

delay-req interval interval

Example:

Router(config-ptp-port)# delay-req interval 1

Configures the minimum interval allowed between PTP delay-request messages when the port is in the server state.

The intervals are set using log base 2 values, as follows:

• 3—1 packet every 8 seconds

• 2—1 packet every 4 seconds

• 1—1 packet every 2 seconds

• 0—1 packet every second

• -1—1 packet every 1/2 second, or 2 packets per second

• -2—1 packet every 1/4 second, or 4 packets per second

• -3—1 packet every 1/8 second, or 8 packets per second

• -4—1 packet every 1/16 seconds, or 16 packets per second.

• -5—1 packet every 1/32 seconds, or 32 packets per second.

• -6—1 packet every 1/64 seconds, or 64 packets per second.

• -7—1 packet every 1/128 seconds, or 128 packets per second.

end

52

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Configuring a Boundary Clock

Step 12

Example:

Router(config-ptp-port)# end

Exit configuration mode.

Router(config-controller)# linecode {ami | b8zs | hdb3}

Selects the linecode type.

• ami—Specifies Alternate Mark Inversion (AMI) as the linecode type. Valid for T1 and E1 controllers.

• b8zs—Specifies binary 8-zero substitution (B8ZS) as the linecode type. Valid for sonet controller only.

This is the default for T1 lines.

• hdb3—Specifies high-density binary 3 (hdb3) as the linecode type. Valid for E1 controller only. This is the default for E1 lines.

Configuring a Boundary Clock

Follow these steps to configure the chassis to act as a boundary clock.

Procedure

Step 1

Step 2

Step 3 enable

Example:

Router> enable

Enables privileged EXEC mode.

• Enter your password if prompted.

configure terminal

Example:

Router# configure terminal

Enter configuration mode.

Router(config)# ptp clock { ordinary | boundary | e2e-transparent } domain domain-number [ hybrid ]

Example:

Router(config)# ptp clock boundary domain 0

Configures the PTP clock. You can create the following clock types:

• ordinary—A 1588 clock with a single PTP port that can operate in Server or Client mode.

• boundary—Terminates PTP session from Grandmaster and acts as PTP server to client clocks downstream.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

53

Configuring Clocking and Timing

Configuring a Boundary Clock

Step 4

Step 5

Step 6

Step 7

• e2e-ransparent—Updates the PTP time correction field to account for the delay in forwarding the traffic.

This helps improve the acuracy of 1588 clock at client.

time-properties persist value

Example:

Router(config-ptp-clk)# time-properties persist 600

(Optional) Starting with Cisco IOS-XE Release 3.18.1SP, you can configure time properties holdover time.

Valid values are from 0 to 10000 seconds. The default value is 300 seconds.

When a server clock is lost, the time properties holdover timer starts. During this period, the time properties flags (currentUtcOffset, currentUtcOffsetValid, leap61, leap59) persist for the holdover timeout period. Once the holdover timer expires, currentUtcOffsetValid, leap59, and leap61 flags are set to false and the currentUtcOffset remains unchanged. In case leap second midnight occurs when holdover timer is running, utc-offset value is updated based on leap59 or leap61 flags. This value is used as long as there are no PTP packets being received from the selected server clock. In case the selected server clock is sending announce packets, the time-properties advertised by server clock is used.

clock-port port-name { master | slave } [ profile { g8265.1

}]

Example:

Router(config-ptp-clk)# clock-port client-port slave

Sets the clock port to PTP Server or Client mode; in client mode, the port exchanges timing packets with a

PTP server clock.

The profile keyword configures the clock to use the G.8265.1 recommendations for establishing PTP sessions, determining the best server clock, handling SSM, and mapping PTP classes.

Note Using a telecom profile requires that the clock have a domain number of 4–23.

transport ipv4 unicast interface interface-type interface-number [negotiation]

Example:

Router(config-ptp-port)# transport ipv4 unicast interface Loopback 0 negotiation

Specifies the transport mechanism for clocking traffic.

The negotiation keyword configures the chassis to discover a PTP server clock from all available PTP clock sources.

Note PTP redundancy is supported only on unicast negotiation mode.

clock-source source-address [priority]

Example:

Router(config-ptp-port)# clock source 133.133.133.133

Specifies the address of a PTP server clock. You can specify a priority value as follows:

• No priority value—Assigns a priority value of 0.

• 1—Assigns a priority value of 1.

• 2—Assigns a priority value of 2, the highest priority.

54

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Configuring a Transparent Clock

Step 8

Step 9

Step 10

Step 11

clock-port port-name { master | slave } [ profile { g8265.1

}]

Example:

Router(config-ptp-port)# clock-port server-port master

Sets the clock port to PTP Server or Client mode; in server mode, the port exchanges timing packets with

PTP client devices.

Note The server clock-port does not establish a clocking session until the client clock-port is phase aligned.

The profile keyword configures the clock to use the G.8265.1 recommendations for establishing PTP sessions, determining the best server clock, handling SSM, and mapping PTP classes.

Note Using a telecom profile requires that the clock have a domain number of 4–23.

transport ipv4 unicast interface interface-type interface-number [negotiation]

Example:

Router(config-ptp-port)# transport ipv4 unicast interface Loopback 1 negotiation

Specifies the transport mechanism for clocking traffic.

The negotiation keyword configures the chassis to discover a PTP server clock from all available PTP clock sources.

Note PTP redundancy is supported only on unicast negotiation mode.

end

Example:

Router(config-ptp-port)# end

Exit configuration mode.

Router(config-controller)# linecode {ami | b8zs | hdb3}

Selects the linecode type.

• ami—Specifies Alternate Mark Inversion (AMI) as the linecode type. Valid for T1 and E1 controllers.

• b8zs—Specifies binary 8-zero substitution (B8ZS) as the linecode type. Valid for sonet controller only.

This is the default for T1 lines.

• hdb3—Specifies high-density binary 3 (hdb3) as the linecode type. Valid for E1 controller only. This is the default for E1 lines.

What to do next

Configuring a Transparent Clock

Follow these steps to configure the chassis as an end-to-end transparent clock.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

55

Configuring Clocking and Timing

Configuring a Transparent Clock

Note The Cisco NCS 4206 Series Chassis does not support peer-to-peer transparent clock mode.

Note The transparent clock ignores the domain number.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5 enable

Example:

Router> enable

Enables privileged EXEC mode.

• Enter your password if prompted.

configure terminal

Example:

Router# configure terminal

Enter configuration mode.

ptp clock { ordinary | boundary | e2e-transparent } domain domain-number [ hybrid ]

Example:

Router(config)# ptp clock e2e-transparent domain

4

Configures the chassis as an end-to-end transparent clock.

exit

Example:

Router(config)# exit

Exit configuration mode.

Router(config-controller)# linecode {ami | b8zs | hdb3}

Selects the linecode type.

• ami—Specifies Alternate Mark Inversion (AMI) as the linecode type. Valid for T1 and E1 controllers.

• b8zs—Specifies binary 8-zero substitution (B8ZS) as the linecode type. Valid for sonet controller only.

This is the default for T1 lines.

• hdb3—Specifies high-density binary 3 (hdb3) as the linecode type. Valid for E1 controller only. This is the default for E1 lines.

56

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Configuring a Hybrid Clock

Configuring a Hybrid Clock

The following sections describe how to configure the chassis to act as a hybrid clock.

Configuring a Hybrid Boundary Clock

Follow these steps to configure a hybrid clocking in boundary clock mode.

Step 1

Step 2

Step 3

Step 4

Note When configuring a hybrid clock, ensure that the frequency and phase sources are traceable to the same server clock.

Procedure enable

Example:

Router> enable

Enables privileged EXEC mode.

• Enter your password if prompted.

configure terminal

Example:

Router# configure terminal

Enter configuration mode.

ptp clock { boundary } domain domain-number [ hybrid ]

Example:

Router(config)# ptp clock boundary domain 0 hybrid

Configures the PTP clock. You can create the following clock types:

Note Hybrid mode is only supported with client clock-ports; server mode is not supported.

• boundary—Terminates PTP session from Grandmaster and acts as PTP Server to Client downstream.

time-properties persist value

Example:

Router(config-ptp-clk)# time-properties persist 600

(Optional) Starting with Cisco IOS-XE Release 3.18.1SP, you can configure time properties holdover time.

Valid values are from 0 to 10000 seconds. The default value is 300 seconds.

When a server clock is lost, the time properties holdover timer starts. During this period, the time properties flags (currentUtcOffset, currentUtcOffsetValid, leap61, leap59) persist for the holdover timeout period. Once

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

57

Configuring Clocking and Timing

Configuring a Hybrid Boundary Clock

Step 5

Step 6

Step 7

Step 8 the holdover timer expires, currentUtcOffsetValid, leap59, and leap61 flags are set to false and the currentUtcOffset remains unchanged. In case leap second midnight occurs when holdover timer is running, utc-offset value is updated based on leap59 or leap61 flags. This value is used as long as there are no PTP packets being received from the selected server clock. In case the selected server clock is sending announce packets, the time-properties advertised by server is used.

utc-offset value leap-second "date time" offset { -1 | 1 }

Example:

Router(config-ptp-clk)# utc-offset 45 leap-second "01-01-2017 00:00:00" offset 1

(Optional) Starting with Cisco IOS XE Release 3.18SP, the new utc-offset CLI is used to set the UTC offset value.

Valid values are from 0-255. The default value is 36.

(Optional) Starting with Cisco IOS-XE Release 3.18.1SP, you can configure the current UTC offset, leap second event date and Offset value (+1 or -1). Leap second configuration will work only when the frequency source is locked and ToD was up before.

• "date time" —Leap second effective date in dd-mm-yyyy hh:mm:ss format.

min-clock-classvalue

Example:

Router(config-ptp-clk)# min-clock-class 157

Sets the threshold clock-class value. This allows the PTP algorithm to use the time stamps from a upstream server clock, only if the clock-class sent by the server clock is less than or equal to the configured threshold clock-class.

Valid values are from 0-255.

Note Min-clock-class value is supported only for PTP with single server clock source configuration.

clock-port port-name { master | slave } [ profile { g8265.1

}]

Example:

Router(config-ptp-clk)# clock-port client-port slave

Sets the clock port to PTP server or client mode; in client mode, the port exchanges timing packets with a

PTP server clock.

Note Hybrid mode is only supported with client clock-ports; server mode is not supported.

The profile keyword configures the clock to use the G.8265.1 recommendations for establishing PTP sessions, determining the best server clock, handling SSM, and mapping PTP classes.

Note Using a telecom profile requires that the clock have a domain number of 4–23.

transport ipv4 unicast interface interface-type interface-number [negotiationsingle-hop]

Example:

Router(config-ptp-port)# transport ipv4 unicast interface Loopback 0 negotiation or

Router(config-ptp-port)# transport ipv4 unicast interface Loopback 0 negotiation single-hop

58

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Configuring a Hybrid Boundary Clock

Step 9

Step 10

Step 11

Step 12

Step 13

Specifies the transport mechanism for clocking traffic.

negotiation —(Optional) configures the chassis to discover a PTP server clock from all available PTP clock sources.

Note PTP redundancy is supported only on unicast negotiation mode.

single-hop —(Optional)Must be configured, if Hop-by-Hop PTP ring topology is used. It ensures that the PTP node communicates only with the adjacent nodes.

clock-source source-address [priority]

Example:

Router(config-ptp-port)# clock source 133.133.133.133

Specifies the address of a PTP server clock. You can specify a priority value as follows:

• No priority value—Assigns a priority value of 0.

• 1—Assigns a priority value of 1.

• 2—Assigns a priority value of 2, the highest priority.

clock-port port-name { master | slave } [ profile { g8265.1

}]

Example:

Router(config-ptp-port)# clock-port server-port master

Sets the clock port to PTP server or client mode; in server mode, the port exchanges timing packets with PTP client devices.

The profile keyword configures the clock to use the G.8265.1 recommendations for establishing PTP sessions, determining the best server clock, handling SSM, and mapping PTP classes.

Note Using a telecom profile requires that the clock have a domain number of 4–23.

transport ipv4 unicast interface interface-type interface-number [negotiation] [single-hop]

Example:

Router(config-ptp-port)# transport ipv4 unicast interface Lo1 negotiation or

Router(config-ptp-port)# transport ipv4 unicast interface Lo1 negotiation single-hop

Specifies the transport mechanism for clocking traffic.

negotiation —(Optional)configures the chassis to discover a PTP server clock from all available PTP clock sources.

Note PTP redundancy is supported only on unicast negotiation mode.

single-hop —(Optional) Must be configured, if Hop-by-Hop PTP ring topology is used. It ensures that the

PTP node communicates only with the adjacent nodes.

exit

Exit clock-port configuration.

network-clock synchronization automatic

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

59

Configuring Clocking and Timing

Configuring a Hybrid Boundary Clock

Step 14

Step 15

Step 16

Step 17

Example:

Router(config)# network-clock synchronization automatic

Enables automatic selection of a clock source.

Note This command must be configured before any input source.

network-clock synchronization mode ql-enabled

Example:

Router(config)# network-clock synchronization mode ql-enabled

Enables automatic selection of a clock source based on quality level (QL).

Note This command is disabled by default.

Use one of the following options:

network-clock input-source priority controller { SONET | wanphy }

network-clock input-source priority external { R0 | R1 } [ 10m | 2m ]

network-clock input-source priority external { R0 | R1 } [ 2048k | e1 { cas { 120ohms | 75ohms | crc4 }}]

network-clock input-source priority external { R0 | R1 } [ 2048k | e1 { crc4 | fas ] { 120ohms | 75ohms }

{ linecode { ami | hdb3 }}

network-clock input-source priority external { R0 | R1 } [ t1 { d4 | esf | sf } { linecode { ami | b8zs }}]

network-clock input-source priority interface type/slot/port

Example:

Router(config)# network-clock input-source 1 external R0 10m

• (Optional) To nominate SDH or SONET controller as network clock input source.

• (Optional) To nominate 10Mhz port as network clock input source.

• (Optional) To nominate BITS port as network clock input source in e1 mode.

• (Optional) To nominate BITS port as network clock input source in e1 mode.

• (Optional) To nominate BITS port as network clock input source in t1 mode.

• (Optional) To nominate Ethernet interface as network clock input source.

network-clock synchronization input-threshold ql value

Example:

Router(config)# network-clock synchronization input-threshold <ql value>

(Optional) Starting with Cisco IOS-XE Release 3.18SP, this new CLI is used to set the threshold QL value for the input frequency source. The input frequency source, which is better than or equal to the configured threshold QL value, will be selected to recover the frequency. Otherwise, internal clock is selected.

network-clock hold-off { 0 | milliseconds }

Example:

Router(config)# network-clock hold-off 0

60

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Configuring a Hybrid Ordinary Clock

Step 18

Step 19

Step 20

Step 21

(Optional) Configures a global hold-off timer specifying the amount of time that the chassis waits when a synchronous Ethernet clock source fails before taking action.

Note You can also specify a hold-off value for an individual interface using the command in interface mode.

network-clock hold-off

For more information about this command, see

Configuring Clocking and Timing, on page 31

platformptpmasteralways-on

Example:

Router(config)# platform ptp master always-on

(Optional) Keeps the server port up all the time. So, when the frequency source has acceptable QL, the egress packets are sent to the downstream clients even when the server port is not phase aligned.

platformptphybrid-bcdownstream-enable

Example:

Router(config)# platform ptp hybrid-bc downstream-enable

(Optional) Enables bust mode. When the difference between the forward timestamp of the previous packet and current packet is greater than 100ns, such timestamps are not provided to the APR. Due to this setting, the APR does not see unexpected and random time jumps in two sequential timestamps of the same PTP message-types. The same applies for the reverse path timestamps as well.

end

Example:

Router(config)# end

Exit configuration mode.

Router(config-controller)# linecode {ami | b8zs | hdb3}

Selects the linecode type.

• ami—Specifies Alternate Mark Inversion (AMI) as the linecode type. Valid for T1 and E1 controllers.

• b8zs—Specifies binary 8-zero substitution (B8ZS) as the linecode type. Valid for sonet controller only.

This is the default for T1 lines.

• hdb3—Specifies high-density binary 3 (hdb3) as the linecode type. Valid for E1 controller only. This is the default for E1 lines.

Configuring a Hybrid Ordinary Clock

Follow these steps to configure a hybrid clocking in ordinary clock client mode.

Note When configuring a hybrid clock, ensure that the frequency and phase sources are traceable to the same server clock.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

61

Configuring Clocking and Timing

Configuring a Hybrid Ordinary Clock

Step 1

Step 2

Step 3

Step 4

Step 5

Procedure enable

Example:

Router> enable

Enables privileged EXEC mode.

• Enter your password if prompted.

configure terminal

Example:

Router# configure terminal

Enter configuration mode.

ptp clock { ordinary | boundary | e2e-transparent } domain domain-number [ hybrid ]

Example:

Router(config)# ptp clock ordinary domain 0 hybrid

Configures the PTP clock. You can create the following clock types:

• ordinary—A 1588 clock with a single PTP port that can operate in Server or Client mode.

Note Hybrid mode is only supported with client clock-ports; server mode is not supported.

• boundary—Terminates PTP session from Grandmaster and acts as PTP Server to Client downstream.

• e2e-ransparent—Updates the PTP time correction field to account for the delay in forwarding the traffic.

This helps improve the acuracy of 1588 clock at client.

output [1pps] {R0 | R1} [ offset offset-value ] [ pulse-width value ]

Example:

Router(config-ptp-clk)# output 1pps R0 offset 200 pulse-width 20 μsec

Enables Precision Time Protocol input 1PPS using a 1PPS input port.

Use R0 or R1 to specify the active RSP slot.

Note Effective Cisco IOS XE Everest 16.6.1, the 1pps pulse bandwith can be changed from the default value of 500 milliseconds to up to 20 microseconds.

tod { R0 | R1} { ubx | nmea | cisco | ntp | cmcc }

Example:

Router(config-ptp-clk)# tod R0 ntp

Configures the time of day message format used by the ToD interface.

62

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Configuring a Hybrid Ordinary Clock

Step 6

Step 7

Step 8

Step 9

Step 10

Note The ToD port acts as an input port in case of server clock and as an output port in case of client clock.

clock-port port-name { master | slave } [ profile { g8265.1

}]

Example:

Router(config-ptp-clk)# clock-port client-port slave

Sets the clock port to PTP Server or Client mode; in client mode, the port exchanges timing packets with a

PTP server clock.

Note Hybrid mode is only supported with client clock-ports; server mode is not supported.

The profile keyword configures the clock to use the G.8265.1 recommendations for establishing PTP sessions, determining the best server clock, handling SSM, and mapping PTP classes.

Note Using a telecom profile requires that the clock have a domain number of 4–23.

transport ipv4 unicast interface interface-type interface-number [negotiation]

Example:

Router(config-ptp-port)# transport ipv4 unicast interface Loopback 0 negotiation

Specifies the transport mechanism for clocking traffic.

The negotiation keyword configures the router to discover a PTP server clock from all available PTP clock sources.

Note PTP redundancy is supported only on unicast negotiation mode.

clock-source source-address [priority]

Example:

Router(config-ptp-port)# clock source 133.133.133.133

Specifies the address of a PTP server clock. You can specify a priority value as follows:

• No priority value—Assigns a priority value of 0.

• 1—Assigns a priority value of 1.

• 2—Assigns a priority value of 2, the highest priority.

exit

Example:

Router(config-ptp-port)# exit

Exit clock-port configuration.

network-clock synchronization automatic

Example:

Router(config-ptp-clk)# network-clock synchronization automatic

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

63

Configuring Clocking and Timing

Configuring a Hybrid Ordinary Clock

Step 11

Step 12

Step 13

Step 14

Enables automatic selection of a clock source.

Note This command must be configured before any input source.

network-clock synchronization mode ql-enabled

Example:

Router(config-ptp-clk)# network-clock synchronization mode ql-enabled

Enables automatic selection of a clock source based on quality level (QL).

Note This command is disabled by default.

For more information about this command, see

Configuring Clocking and Timing, on page 31

Use one of the following options:

• network-clock input-source <priority> controller {SONET | wanphy}

• network-clock input-source <priority> external {R0 | R1} [10m | 2m]

• network-clock input-source <priority> external {R0 | R1} [2048k | e1 {cas {120ohms | 75ohms | crc4}}]

• network-clock input-source <priority> external {R0 | R1} [2048k | e1 {crc4 | fas] {120ohms | 75ohms}

{linecode {ami | hdb3}}

• network-clock input-source <priority> external {R0 | R1} [t1 {d4 | esf | sf} {linecode {ami | b8zs}}]

• network-clock input-source <priority> interface <type/slot/port>

Example:

Router(config)# network-clock input-source 1 external R0 10m

• (Optional) To nominate SDH or SONET controller as network clock input source.

• (Optional) To nominate 10Mhz port as network clock input source.

• (Optional) To nominate BITS port as network clock input source in e1 mode.

• (Optional) To nominate BITS port as network clock input source in e1 mode.

• (Optional) To nominate BITS port as network clock input source in t1 mode.

• (Optional) To nominate Ethernet interface as network clock input source.

network-clock hold-off { 0 | milliseconds }

Example:

Router(config-ptp-clk)# network-clock hold-off 0

(Optional) Configures a global hold-off timer specifying the amount of time that the router waits when a synchronous Ethernet clock source fails before taking action.

Note You can also specify a hold-off value for an individual interface using the command in interface mode.

network-clock hold-off

For more information about this command, see

Configuring Clocking and Timing, on page 31

end

64

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Configuring PTP Redundancy

Step 15

Example:

Router(config-ptp-clk)# end

Exit configuration mode.

Router(config-controller)# linecode {ami | b8zs | hdb3}

Selects the linecode type.

• ami—Specifies Alternate Mark Inversion (AMI) as the linecode type. Valid for T1 and E1 controllers.

• b8zs—Specifies binary 8-zero substitution (B8ZS) as the linecode type. Valid for sonet controller only.

This is the default for T1 lines.

• hdb3—Specifies high-density binary 3 (hdb3) as the linecode type. Valid for E1 controller only. This is the default for E1 lines.

Configuring PTP Redundancy

The following sections describe how to configure PTP redundancy on the chassis:

Configuring PTP Redundancy in Client Clock Mode

Follow these steps to configure clocking redundancy in client clock mode:

Procedure

Step 1

Step 2

Step 3 enable

Example:

Router> enable

Enables privileged EXEC mode.

• Enter your password if prompted.

configure terminal

Example:

Router# configure terminal

Enter configuration mode.

ptp clock { ordinary | boundary | e2e-transparent } domain domain-number [ hybrid ]

Example:

Router(config#) ptp clock ordinary domain 0

Configures the PTP clock. You can create the following clock types:

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

65

Configuring Clocking and Timing

Configuring PTP Redundancy in Client Clock Mode

Step 4

Step 5

Step 6

Step 7

• ordinary—A 1588 clock with a single PTP port that can operate in Server or Client mode.

• boundary—Terminates PTP session from Grandmaster and acts as PTP Server to Client clocks downstream.

• e2e-ransparent—Updates the PTP time correction field to account for the delay in forwarding the traffic.

This helps improve the acuracy of 1588 clock at client.

clock-port port-name { master | slave } [ profile { g8265.1

}]

Example:

Router(config-ptp-clk)# clock-port client-port slave

Sets the clock port to PTP server or client mode; in client mode, the port exchanges timing packets with a

PTP server clock.

The profile keyword configures the clock to use the G.8265.1 recommendations for establishing PTP sessions, determining the best server clock, handling SSM, and mapping PTP classes.

Note Using a telecom profile requires that the clock have a domain number of 4–23.

transport ipv4 unicast interface interface-type interface-number [negotiation] [single-hop]

Example:

Router(config-ptp-port)# transport ipv4 unicast interface Loopback 0 negotiation

Example:

Router(config-ptp-port)# transport ipv4 unicast interface Loopback 0 negotiation single-hop

Specifies the transport mechanism for clocking traffic.

• negotiation —(Optional) Configures the chassis to discover a PTP server clock from all available PTP clock sources.

Note PTP redundancy is supported only on unicast negotiation mode.

• single-hop— (Optional) It ensures that the PTP node communicates only with the adjacent nodes.

clock-source source-address [priority]

Example:

Router(config-ptp-port)# clock source 133.133.133.133 1

Specifies the address of a PTP server clock. You can specify a priority value as follows:

• No priority value—Assigns a priority value of 0.

• 1—Assigns a priority value of 1.

• 2—Assigns a priority value of 2, the highest priority.

clock-source source-address [priority]

Example:

66

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Configuring PTP Redundancy in Boundary Clock Mode

Step 8

Step 9

Step 10

Router(config-ptp-port)# clock source 133.133.133.134 2

Specifies the address of an additional PTP server clock; repeat this step for each additional server clock. You can configure up to three server clocks.

clock-source source-address [priority]

Example:

Router(config-ptp-port)# clock source 133.133.133.135

Specifies the address of an additional PTP server clock; repeat this step for each additional server clock. You can configure up to three server clocks.

end

Example:

Router(config-ptp-port)# end

Exit configuration mode.

Router(config-controller)# linecode {ami | b8zs | hdb3}

Selects the linecode type.

• ami—Specifies Alternate Mark Inversion (AMI) as the linecode type. Valid for T1 and E1 controllers.

• b8zs—Specifies binary 8-zero substitution (B8ZS) as the linecode type. Valid for sonet controller only.

This is the default for T1 lines.

• hdb3—Specifies high-density binary 3 (hdb3) as the linecode type. Valid for E1 controller only. This is the default for E1 lines.

Configuring PTP Redundancy in Boundary Clock Mode

Follow these steps to configure clocking redundancy in boundary clock mode:

Procedure

Step 1

Step 2 enable

Example:

Router> enable

Enables privileged EXEC mode.

• Enter your password if prompted.

configure terminal

Example:

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

67

Configuring Clocking and Timing

Configuring PTP Redundancy in Boundary Clock Mode

Step 3

Step 4

Step 5

Step 6

Router# configure terminal

Enter configuration mode.

ptp clock { ordinary | boundary | e2e-transparent } domain domain-number

Example:

Router(config)# ptp clock boundary domain 0

Configures the PTP clock. You can create the following clock types:

• ordinary—A 1588 clock with a single PTP port that can operate in Server or Client mode.

• boundary—Terminates PTP session from Grandmaster and acts as PTP Server to Client clocks downstream.

• e2e-ransparent—Updates the PTP time correction field to account for the delay in forwarding the traffic.

This helps improve the acuracy of 1588 clock at client.

clock-port port-name { master | slave } [ profile { g8265.1

}]

Example:

Router(config-ptp-clk)# clock-port client-port slave

Sets the clock port to PTP Server or Client mode; in client mode, the port exchanges timing packets with a

PTP server clock.

The profile keyword configures the clock to use the G.8265.1 recommendations for establishing PTP sessions, determining the best server clock, handling SSM, and mapping PTP classes.

Note Using a telecom profile requires that the clock have a domain number of 4–23.

transport ipv4 unicast interface interface-type interface-number [negotiation] [single-hop]

Example:

Router(config-ptp-port)# transport ipv4 unicast interface Loopback 0 negotiation

Example:

Router(config-ptp-port)# transport ipv4 unicast interface Loopback 0 negotiation single-hop

Specifies the transport mechanism for clocking traffic.

• negotiation —(Optional) Configures the chassis to discover a PTP server clock from all available PTP clock sources.

Note PTP redundancy is supported only on unicast negotiation mode.

• single-hop— (Optional) Must beconfigured, if Hop-by-Hop PTP ring topology is used. It ensures that the PTP node communicates only with the adjacent nodes.

clock-source source-address [priority]

Example:

Router(config-ptp-port)# clock source 133.133.133.133 1

68

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Configuring PTP Redundancy in Boundary Clock Mode

Step 7

Step 8

Step 9

Step 10

Step 11

Specifies the address of a PTP server clock. You can specify a priority value as follows:

• No priority value—Assigns a priority value of 0.

• 1—Assigns a priority value of 1.

• 2—Assigns a priority value of 2, the highest priority.

clock-source source-address [priority]

Example:

Router(config-ptp-port)# clock source 133.133.133.134 2

Specifies the address of an additional PTP server clock; repeat this step for each additional server clock. You can configure up to three server clocks.

clock-source source-address [priority]

Example:

Router(config-ptp-port)# clock source 133.133.133.135

Specifies the address of an additional PTP server clock; repeat this step for each additional server clock. You can configure up to three server clocks.

clock-port port-name { master | slave } [ profile { g8265.1

}]

Example:

Router(config-ptp-port)# clock-port server-port master

Specifies the address of a PTP server clock.

The profile keyword configures the clock to use the G.8265.1 recommendations for establishing PTP sessions, determining the best server clock, handling SSM, and mapping PTP classes.

Note Using a telecom profile requires that the clock have a domain number of 4–23.

transport ipv4 unicast interface interface-type interface-number [negotiation] [single-hop]

Example:

Router(config-ptp-port)# transport ipv4 unicast interface Loopback 1 negotiation single-hop

Specifies the transport mechanism for clocking traffic.

• negotiation —(Optional) Configures the chassis to discover a PTP server clock from all available PTP clock sources.

Note PTP redundancy is supported only on unicast negotiation mode.

• single-hop— (Optional) Must be configured if Hop-by-Hop PTP ring topology is used. It ensures that the PTP node communicates only with the adjacent nodes.

end

Example:

Router(config-ptp-port)# end

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

69

Configuring Clocking and Timing

Synchronizing the System Time to a Time-of-Day Source

Step 12

Exit configuration mode.

Router(config-controller)# linecode {ami | b8zs | hdb3}

Selects the linecode type.

• ami—Specifies Alternate Mark Inversion (AMI) as the linecode type. Valid for T1 and E1 controllers.

• b8zs—Specifies binary 8-zero substitution (B8ZS) as the linecode type. Valid for sonet controller only.

This is the default for T1 lines.

• hdb3—Specifies high-density binary 3 (hdb3) as the linecode type. Valid for E1 controller only. This is the default for E1 lines.

Synchronizing the System Time to a Time-of-Day Source

The following sections describe how to synchronize the system time to a time of day (ToD) clock source.

Synchronizing the System Time to a Time-of-Day Source (Server Mode)

Note

System time to a ToD source (Server Mode) can be configured only when PTP server is configured. See

Configuring a Server Ordinary Clock, on page 45

. Select any one of the four available ToD format; cisco, nmea, ntp or ubx.10m must be configured as network clock input source.

Follow these steps to configure the system clock to a ToD source in server mode.

Procedure

Step 1

Step 2

Step 3 enable

Example:

Router> enable

Enables privileged EXEC mode.

• Enter your password if prompted.

configure terminal

Example:

Router# configure terminal

Enter configuration mode.

tod-clock input-source priority { gps { R0 | R1 } | ptp domain domain }

Example:

70

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Synchronizing the System Time to a Time-of-Day Source (Client Mode)

Step 4

Step 5

Router(config)# TOD-clock 2 gps R0/R1

In server mode, specify a GPS port connected to a ToD source.

exit

Example:

Router(config)# exit

Exit configuration mode.

Router(config-controller)# linecode {ami | b8zs | hdb3}

Selects the linecode type.

• ami—Specifies Alternate Mark Inversion (AMI) as the linecode type. Valid for T1 and E1 controllers.

• b8zs—Specifies binary 8-zero substitution (B8ZS) as the linecode type. Valid for sonet controller only.

This is the default for T1 lines.

• hdb3—Specifies high-density binary 3 (hdb3) as the linecode type. Valid for E1 controller only. This is the default for E1 lines.

Synchronizing the System Time to a Time-of-Day Source (Client Mode)

Note System time to a ToD source (Client Mode) can be configured only when PTP client is configured. See

Configuring a Client Ordinary Clock, on page 50

.

Follow these steps to configure the system clock to a ToD source in client mode. In client mode, specify a

PTP domain as a ToD input source.

Procedure

Step 1

Step 2 enable

Example:

Router> enable

Enables privileged EXEC mode.

• Enter your password if prompted.

configure terminal

Example:

Router# configure terminal

Enter configuration mode.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

71

Configuring Clocking and Timing

Configuring Synchronous Ethernet ESMC and SSM

Step 3

Step 4

Step 5

tod-clock input-source priority { gps { R0 | R1 } | ptp domain domain }

Example:

Router(config)# TOD-clock 10 ptp domain 0

In client mode, specify a PTP domain as a ToD input source.

Router(config)# end

Exit configuration mode.

Router(config-controller)# linecode {ami | b8zs | hdb3}

Selects the linecode type.

• ami—Specifies Alternate Mark Inversion (AMI) as the linecode type. Valid for T1 and E1 controllers.

• b8zs—Specifies binary 8-zero substitution (B8ZS) as the linecode type. Valid for sonet controller only.

This is the default for T1 lines.

• hdb3—Specifies high-density binary 3 (hdb3) as the linecode type. Valid for E1 controller only. This is the default for E1 lines.

Configuring Synchronous Ethernet ESMC and SSM

Synchronous Ethernet is an extension of Ethernet designed to provide the reliability found in traditional

SONET/SDH and T1/E1 networks to Ethernet packet networks by incorporating clock synchronization features.

The supports the Synchronization Status Message (SSM) and Ethernet Synchronization Message Channel

(ESMC) for synchronous Ethernet clock synchronization.

The following sections describe ESMC and SSM support on the router.

Configuring Synchronous Ethernet ESMC and SSM

Follow these steps to configure ESMC and SSM on the router.

Procedure

Step 1

Step 2 enable

Example:

Router> enable

Enables privileged EXEC mode.

• Enter your password if prompted.

configure terminal

Example:

Router# configure terminal

72

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Configuring Synchronous Ethernet ESMC and SSM

Step 3

Step 4

Step 5

Step 6

Enters global configuration mode.

network-clock synchronization automatic

Example:

Router(config)# network-clock synchronization automatic

Enables the network clock selection algorithm. This command disables the Cisco-specific network clock process and turns on the G.781-based automatic clock selection process.

Note This command must be configured before any input source.

network-clock eec { 1 | 2 }

Example:

Router(config)# network-clock eec 1

Specifies the Ethernet Equipment Clock (EEC) type. Valid values are

• 1—ITU-T G.8262 option 1 (2048)

• 2—ITU-T G.8262 option 2 and Telcordia GR-1244 (1544) network-clock synchronization ssm option { 1 | 2 { GEN1 | GEN2 }}

Example:

Router(config)# network-clock synchronization ssm option 2 GEN2

Configures the G.781 synchronization option used to send synchronization messages. The following guidelines apply for this command:

• Option 1 refers to G.781 synchronization option 1, which is designed for Europe. This is the default value.

• Option 2 refers to G.781 synchronization option 2, which is designed for the United States.

• GEN1 specifies option 2 Generation 1 synchronization.

• GEN2 specifies option 2 Generation 2 synchronization.

Use one of the following options:

network-clock input-source priority controller { SONET | wanphy }

network-clock input-source priority external { R0 | R1 } [ 10m | 2m ]

network-clock input-source priority external { R0 | R1 } [ 2048k | e1 { cas { 120ohms | 75ohms | crc4 }}]

network-clock input-source priority external { R0 | R1 } [ 2048k | e1 { crc4 | fas ] { 120ohms | 75ohms }

{ linecode { ami | hdb3 }}

network-clock input-source priority external { R0 | R1 } [ t1 { d4 | esf | sf } { linecode { ami | b8zs }}]

network-clock input-source priority interface type/slot/port

Example:

Router(config)# network-clock input-source 1 external R0 10m

• (Optional) To nominate SDH or SONET controller as network clock input source.

• (Optional) To nominate 10Mhz port as network clock input source.

• (Optional) To nominate BITS port as network clock input source in e1 mode.

• (Optional) To nominate BITS port as network clock input source in e1 mode.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

73

Configuring Clocking and Timing

Configuring Synchronous Ethernet ESMC and SSM

Step 7

Step 8

Step 9

Step 10

Step 11

Step 12

• (Optional) To nominate BITS port as network clock input source in t1 mode.

• (Optional) To nominate Ethernet interface as network clock input source.

• (Optional) To nominate PTP as network clock input source.

network-clock synchronization mode ql-enabled

Example:

Router(config)# network-clock synchronization mode ql-enabled

Enables automatic selection of a clock source based on quality level (QL).

Note This command is disabled by default.

network-clock hold-off { 0 | milliseconds }

Example:

Router(config)# network-clock hold-off 0

(Optional) Configures a global hold-off timer specifying the amount of time that the router waits when a synchronous Ethernet clock source fails before taking action.

Note You can also specify a hold-off value for an individual interface using the network-clock hold-off command in interface mode.

network-clock wait-to-restore seconds

Example:

Router(config)# network-clock wait-to-restore 70

(Optional) Configures a global wait-to-restore timer for synchronous Ethernet clock sources. The timer specifies how long the router waits before including a restored clock source in the clock selection process.

Valid values are 0 to 86400 seconds. The default value is 300 seconds.

Note You can also specify a wait-to-restore value for an individual interface using the network-clock wait-to-restore command in interface mode.

network-clock revertive

Example:

Router(config)# network-clock revertive

(Optional) Sets the router in revertive switching mode when recovering from a failure. To disable revertive mode, use the no form of this command.

esmc process

Example:

Router(config)# esmc process

Enables the ESMC process globally.

network-clock external slot/card/port hold-off { 0 | milliseconds }

Example:

74

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Configuring Synchronous Ethernet ESMC and SSM

Step 13

Step 14

Step 15

Step 16

Step 17

Router(config)# network-clock external 0/1/0 hold-off 0

Overrides the hold-off timer value for the external interface.

network-clock quality-level { tx | rx } value { controller [ E1 | BITS ] slot/card/port | external [ 2m | 10m |

2048k | t1 | e1 ] }

Example:

Router(config)# network-clock quality-level rx qL-pRC external R0 e1 cas crc4

Specifies a quality level for a line or external clock source.

The available quality values depend on the G.781 synchronization settings specified by the network-clock synchronization ssm option command:

• Option 1—Available values are QL-PRC, QL-SSU-A, QL-SSU-B, QL-SEC, and QL-DNU.

• Option 2, GEN1—Available values are QL-PRS, QL-STU, QL-ST2, QL-SMC, QL-ST4, and QL-DUS.

• Option 2, GEN 2—Available values are QL-PRS, QL-STU, QL-ST2, QL-TNC, QL-ST3, QL-SMC,

QL-ST4, and QL-DUS.

interface type number

Example:

Router(config)# interface GigabitEthernet 0/0/1

Example:

Router(config-if)#

Enters interface configuration mode.

synchronous mode

Example:

Router(config-if)# synchronous mode

Configures the Ethernet interface to synchronous mode and automatically enables the ESMC and QL process on the interface.

network-clock source quality-level value { tx | rx }

Example:

Router(config-if)# network-clock source quality-level QL-PrC tx

Applies quality level on sync E interface.

The available quality values depend on the G.781 synchronization settings specified by the network-clock synchronization ssm option command:

• Option 1—Available values are QL-PRC, QL-SSU-A, QL-SSU-B, QL-SEC, and QL-DNU.

• Option 2, GEN1—Available values are QL-PRS, QL-STU, QL-ST2, QL-SMC, QL-ST4, and QL-DUS.

• Option 2, GEN 2—Available values are QL-PRS, QL-STU, QL-ST2, QL-TNC, QL-ST3, QL-SMC,

QL-ST4, and QL-DUS.

esmc mode [ ql-disabled | tx | rx ] value

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

75

Configuring Clocking and Timing

Managing Clock Source Selection

Step 18

Step 19

Step 20

Example:

Router(config-if)# esmc mode rx QL-STU

Enables the ESMC process at the interface level. The no form of the command disables the ESMC process.

network-clock hold-off { 0 | milliseconds }

Example:

Router(config-if)# network-clock hold-off 0

(Optional) Configures an interface-specific hold-off timer specifying the amount of time that the router waits when a synchronous Ethernet clock source fails before taking action.

You can configure the hold-off time to either 0 or any value between 50 to 10000 ms. The default value is

300 ms.

network-clock wait-to-restore seconds

Example:

Router(config-if)# network-clock wait-to-restore 70

(Optional) Configures the wait-to-restore timer for an individual synchronous Ethernet interface.

end

Example:

Router(config-if)# end

Exits interface configuration mode and returns to privileged EXEC mode.

What to do next

You can use the show network-clocks command to verify your configuration.

Managing Clock Source Selection

The following sections describe how to manage the selection on the chassis:

Specifying a Clock Source

The following sections describe how to specify a synchronous Ethernet clock source during the clock selection process:

Selecting a Specific Clock Source

To select a specific interface as a synchronous Ethernet clock source, use the network-clock switch manual command in global configuration mode.

Note The new clock source must be of higher quality than the current clock source; otherwise the chassis does not select the new clock source.

76

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Specifying a Clock Source

Command Purpose network-clock switch manual external R0 |

R1 {{ E1 { crc4 | cas | fas }} { T1 { d4 | sf | esf }}

}

Manually selects a synchronization source, provided the source is available and is within the range.

Router# network-clock switch manual external r0 e1 crc4 network-clock clear switch { t0 | external slot/card/port [ 10m

| 2m ]}

Disable a clock source selection.

Router# network-clock clear switch t0

Forcing a Clock Source Selection

To force the chassis to use a specific synchronous Ethernet clock source, use the network-clock switch force command in global configuration mode.

Note This command selects the new clock regardless of availability or quality.

Note Forcing a clock source selection overrides a clock selection using the network-clock switch manual command.

Command Purpose network-clock switch force external R0 | R1 {{ E1 { crc4

| cas | fas }} { T1 { d4 | sf | esf }} }

Forces the chassis to use a specific synchronous

Ethernet clock source, regardless of clock quality or availability.

Router# network-clock switch force r0 e1 crc4 network-clock clear switch { t0 | external slot/card/port

[ 10m | 2m ]}

Disable a clock source selection.

Router# network-clock clear switch t0

Disabling Clock Source Specification Commands

To disable a network-clock switch manual or network-clock switch force configuration and revert to the default clock source selection process, use the network-clock clear switch command.

Command Purpose network-clock clear switch { t0 | external slot/card/port [ 10m | 2m ]} Disable a clock source selection.

Router# network-clock clear switch t0

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

77

Configuring Clocking and Timing

Disabling a Clock Source

Disabling a Clock Source

The following sections describe how to manage the synchronous Ethernet clock sources that are available for clock selection:

Locking Out a Clock Source

To prevent the chassis from selecting a specific synchronous Ethernet clock source, use the network-clock set lockout command in global configuration mode.

Command Purpose network-clock set lockout { interface interface_name slot/card/port | external { R0 | R1 [ { t1 { sf | esf } linecode { ami | b8zs }} | e1 [ crc4

| fas ] linecode [ hdb3 | ami ]}

Prevents the chassis from selecting a specific synchronous Ethernet clock source.

Router# network-clock set lockout interface GigabitEthernet

0/0/0 network-clock clear lockout { interface interface_name slot/card/port | external { R0 | R1 [ { t1 { sf | esf } linecode { ami | b8zs }} | e1 [ crc4 | fas ] linecode [ hdb3 | ami ] }

Disable a lockout configuration on a synchronous Ethernet clock source.

Router# network-clock clear lockout interface

GigabitEthernet 0/0/0

Restoring a Clock Source

To restore a clock in a lockout condition to the pool of available clock sources, use the network-clock clear lockout command in global configuration mode.

Command Purpose network-clock clear lockout { interface interface_name slot/card/port | external external

{ R0 | R1 [ { t1 { sf | esf } linecode { ami | b8zs }} | e1 [ crc4 | fas ] linecode [ hdb3 | ami ]

}

Forces the chassis to use a specific synchronous Ethernet clock source, regardless of clock quality or availability.

Router# network-clock clear lockout interface

GigabitEthernet 0/0/0

Verifying the Configuration

You can use the following commands to verify a clocking configuration:

• show esmc—Displays the ESMC configuration.

• show esmc detail —Displays the details of the ESMC parameters at the global and interface levels.

• show network-clock synchronization—Displays the chassis clock synchronization state.

78

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Troubleshooting

• show network-clock synchronization detail—Displays the details of network clock synchronization parameters at the global and interface levels.

• show ptp clock dataset

• show ptp port dataset

• show ptp clock running

• show platform software ptpd statistics

• show platform ptp all

• show platform ptp tod all

Troubleshooting

Table 11: SyncE Debug Commands , on page 79

list the debug commands that are available for troubleshooting the SyncE configuration on the chassis:

Caution We recommend that you do not use debug commands without TAC supervision.

Table 11: SyncE Debug Commands

Debug Command debug platform network-clock

Purpose

Debugs issues related to the network clock including active-standby selection, alarms, and OOR messages.

debug network-clock Debugs issues related to network clock selection.

debug esmc error debug esmc event debug esmc packet [interface interface-name ] debug esmc packet rx [interface interface-name ] debug esmc packet tx [interface interface-name ]

These commands verify whether the ESMC packets are transmitted and received with proper quality-level values.

Table 12: Troubleshooting Scenarios , on page 79

provides the information about troubleshooting your configuration

Table 12: Troubleshooting Scenarios

Problem

Clock selection

Solution

• Verify that there are no alarms on the interfaces using the show network-clock synchronization detail command.

• Ensure that the nonrevertive configurations are in place.

• Reproduce the issue and collect the logs using the debug network-clock errors, debug network-clock event, and debug network-clock sm commands. Contact Cisco Technical Support if the issue persists.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

79

Configuring Clocking and Timing

Configuration Examples

Problem

Incorrect QL values

Alarms

Incorrect clock limit set or queue limit disabled mode

Incorrect QL values you use the show network-clock when synchronization detail command.

Solution

• Ensure that there is no framing mismatch with the SSM option.

• Reproduce the issue using the debug network-clock errors and debug network-clock event commands.

• Reproduce the issue using the debug platform network-clock command enabled in the RSP. Alternatively, enable the debug network-clock event and debug network-clock errors commands.

• Verify that there are no alarms on the interfaces using the show network-clock synchronization detail command.

• Use the show network-clock synchronization command to confirm if the system is in revertive mode or nonrevertive mode and verify the non-revertive configurations.

• Reproduce the current issue and collect the logs using the debug network-clock errors, debug network-clock event, and debug network-clock sm RSP commands.

• Use the network clock synchronization SSM ( option 1 |option 2 ) command to confirm that there is no framing mismatch. Use the show run interface command to validate the framing for a specific interface.

For the SSM option 1, framing should be SDH or E1, and for SSM option

2, it should be T1.

• Reproduce the issue using the debug network-clock errors and debug network-clock event RSP commands.

Note Effective from Cisco IOS XE Everest 16.6.1, on RSP3 module, alarm notification is enabled on 900 watts

DC power supply. There are 2 input feeds for 900 watts DC power supply, if one of the input voltage is lesser than the operating voltage, critical alarm is generated for that particular feed and clears (stops) once the voltage is restored but the power supply state remains in OK state as the other power supply is operationally up.

Configuration Examples

This section contains sample configurations for clocking features on the chassis.

Note This section contains partial chassis configurations intended to demonstrate a specific feature.

80

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Ordinary Clock—Client ptp clock ordinary domain 0 clock-port Client slave transport ipv4 unicast interface loopback 0 negotiation clock-source 8.8.8.1

announce timeout 7 delay-req interval 100

Ordinary Clock —Client Mode (Ethernet) ptp clock ordinary domain 0 clock-port Client slave transport ethernet unicast clock-source 1234.5678.90ab bridge-domain 2 5

Ordinary Clock—Server ptp clock ordinary domain 0 clock-port Server master transport ipv4 unicast interface loopback 0 negotiation

Ordinary Clock—Server (Ethernet) ptp clock ordinary domain 0 clock-port Server master transport ethernet unicast clock destination interface GigabitEthernet0/0/1

Unicast Configuration—Client Mode ptp clock ordinary domain 0 clock-port Client slave transport ipv4 unicast interface loopback 0 clock-source 8.8.8.1

Unicast Configuration—Client Mode (Ethernet) ptp clock ordinary domain 0 clock-port Client slave transport ethernet unicast clock source 1234.5678.90ab bridge-domain 5 2

Unicast Configuration—Server Mode ptp clock ordinary domain 0 clock-port Server master transport ipv4 unicast interface loopback 0 clock-destination 8.8.8.2

sync interval 1 announce interval 2

Configuration Examples

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

81

Configuring Clocking and Timing

Configuration Examples

Unicast Configuration—Server Mode (Ethernet) ptp clock ordinary domain 0 clock-port Server master transport ethernet unicast clock destination 1234.5678.90ab bridge-domain 5

Unicast Negotiation—Client ptp clock ordinary domain 0 clock-port Client slave transport ipv4 unicast interface loopback 0 negotiation clock-source 8.8.8.1

Unicast Negotiation—Client (Ethernet) ptp clock ordinary domain 0 clock-port Client slave transport ethernet unicast negotiation clock source 1234.5678.90ab bridge-domain 5 5 clock-port Client1 slave transport ethernet unicast negotiation clock source 1234.9876.90ab interface gigabitethernet 0/0/4 2

Unicast Negotiation—Server ptp clock ordinary domain 0 clock-port Server master transport ipv4 unicast interface loopback 0 negotiation sync interval 1 announce interval 2

Unicast Negotiation—Server (Ethernet) ptp clock ordinary domain 0 clock-port Server master transport ethernet unicast negotiation

Boundary Clock ptp clock boundary domain 0 clock-port Client slave transport ipv4 unicast interface Loopback 0 negotiation clock source 133.133.133.133

clock-port Server master transport ipv4 unicast interface Loopback 1 negotiation

Transparent Clock ptp clock e2e-transparent domain 0

Hybrid Clock—Boundary ptp clock boundary domain 0 hybrid

82

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing clock-port Client slave transport ipv4 unicast interface Loopback0 negotiation clock source 133.133.133.133

clock-port Server master transport ipv4 unicast interface Loopback1 negotiation

Network-clock input-source 10 interface gigabitEthernet 0/4/0

Hybrid Clock—Client ptp clock ordinary domain 0 hybrid clock-port Client slave transport ipv4 unicast interface Loopback 0 negotiation clock source 133.133.133.133

Network-clock input-source 10 interface gigabitEthernet 0/4/0

PTP Redundancy—Client ptp clock ordinary domain 0 clock-port Client slave transport ipv4 unicast interface Loopback 0 negotiation clock source 133.133.133.133 1 clock source 55.55.55.55 2 clock source 5.5.5.5

PTP Redundancy—Boundary ptp clock boundary domain 0 clock-port Client slave transport ipv4 unicast interface Loopback 0 negotiation clock source 133.133.133.133 1 clock source 55.55.55.55 2 clock source 5.5.5.5

clock-port Server master transport ipv4 unicast interface Lo1 negotiation

Hop-By-Hop PTP Redundancy—Client ptp clock ordinary domain 0 clock-port Client slave transport ipv4 unicast interface Loopback 0 negotiation single-hop clock source 133.133.133.133 1 clock source 55.55.55.55 2 clock source 5.5.5.5

Hop-By-Hop PTP Redundancy—Boundary ptp clock boundary domain 0 clock-port Client slave transport ipv4 unicast interface Loopback 0 negotiation single-hop clock source 133.133.133.133 1 clock source 55.55.55.55 2 clock source 5.5.5.5

Configuration Examples

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

83

Configuring Clocking and Timing

Configuration Examples clock-port Server master transport ipv4 unicast interface Lo1 negotiation single-hop

Time of Day Source—Server

TOD-clock 10 gps R0/R1

Time of Day Source—Client

TOD-clock 10 ptp domain 0

Clock Selection Parameters network-clock synchronization automatic network-clock synchronization mode QL-enabled network-clock input-source 1 ptp domain 3

ToD/1PPS Configuration—Server network-clock input-source 1 external R010m ptp clock ordinary domain 1 tod R0 ntp input 1pps R0 clock-port Server master transport ipv4 unicast interface loopback 0

ToD/1PPS Configuration—Client ptp clock ordinary domain 1 tod R0 ntp output 1pps R0 offset 200 pulse-width 20 μsec clock-port Client slave transport ipv4 unicast interface loopback 0 negotiation clock source 33.1.1.

Show Commands

Router# show ptp clock dataset ?

current currentDS dataset default parent defaultDS dataset parentDS dataset time-properties timePropertiesDS dataset

Router# show ptp port dataset ?

foreign-master foreignMasterDS dataset port portDS dataset

Router# show ptp clock running domain 0

State

ACQUIRING

PTP Ordinary Clock [Domain 0]

Ports Pkts sent

1 98405

PORT SUMMARY

PTP Master

Name

Addr

Client

8.8.8.8

Tx Mode unicast slave

Role Transport

Lo0

Pkts rcvd

296399

State

Slave

SESSION INFORMATION

Redundancy Mode

Track one

Port Sessions

1

84

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Clocking and Timing

Configuration Examples

SLAVE [Lo0] [Sessions 1]

Peer addr Pkts in

8.8.8.8

Router#

296399

Pkts out

98405

In Errs

0

Router# show platform software ptpd stat stream 0

LOCK STATUS : PHASE LOCKED

SYNC Packet Stats

Time elapsed since last packet: 0.0

Configured Interval : 0, Acting Interval 0

Tx packets : 0, Rx Packets : 169681

Last Seq Number : 0, Error Packets : 1272

Delay Req Packet Stats

Time elapsed since last packet: 0.0

Configured Interval : 0, Acting Interval : 0

Tx packets : 84595, Rx Packets : 0

Last Seq Number : 19059, Error Packets : 0

!output omitted for brevity

Current Data Set

Offset from master : 0.4230440

Out Errs

0

Mean Path Delay : 0.0

Steps Removed 1

General Stats about this stream

Packet rate : 0, Packet Delta (ns) : 0

Clock Stream handle : 0, Index : 0

Oper State : 6, Sub oper State : 7

Log mean sync Interval : -5, log mean delay req int : -4

Router# show platform ptp all

Slave info : [Loopback0][0x38A4766C]

-------------------------------clock role

Slave Port hdl

Tx Mode

Slave IP

Max Clk Srcs

: SLAVE

: 486539266

: Unicast-Negotiation

: 4.4.4.4

: 1

Boundary Clock

Lock status

Refcnt

: FALSE

: HOLDOVER

: 1

Configured-Flags : 0x7F - Clock Port Stream

Config-Ready-Flags : Port Stream

-----------

PTP Engine Handle : 0

Master IP : 8.8.8.8

Local Priority

Set Master IP

: 0

: 8.8.8.8

Router#show platform ptp tod all

--------------------------------

ToD/1PPS Info for 0/0

--------------------------------

ToD CONFIGURED : YES

ToD FORMAT

ToD DELAY

1PPS MODE

: NMEA

: 0

: OUTPUT

OFFSET

PULSE WIDTH

: 0

: 0

ToD CLOCK : Mon Jan 1 00:00:00 UTC 1900

Router# show ptp clock running domain 0

State Ports

PHASE_ALIGNED 2

PORT SUMMARY

PTP Boundary Clock [Domain 0]

Pkts sent Pkts rcvd

32355 159516

Redundancy Mode

Hot standby

PTP Master

Name Tx Mode Role Transport State Sessions Port Addr

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

85

Configuring Clocking and Timing

Configuration Examples

SLAVE

9.9.9.1

MASTER unicast unicast slave Ethernet master Ethernet -

SESSION INFORMATION

SLAVE [Ethernet] [Sessions 1]

Peer addr Pkts in Pkts out In Errs

0 9.9.9.1

159083

MASTER [Ethernet] [Sessions 2]

Peer addr aabb.ccdd.ee01 [Gig0/2/3] aabb.ccdd.ee02 [BD 1000]

31054

Pkts in

223

210

Out Errs

0

Pkts out In Errs

667

634

0

0

2

1

-

Out Errs

0

0

Input Synchronous Ethernet Clocking

The following example shows how to configure the chassis to use the BITS interface and two Gigabit Ethernet interfaces as input synchronous Ethernet timing sources. The configuration enables SSM on the BITS port.

!

Interface GigabitEthernet0/0 synchronous mode network-clock wait-to-restore 720

!

Interface GigabitEthernet0/1 synchronous mode

!

!

network-clock synchronization automatic network-clock input-source 1 External R0 e1 crc4 network-clock input-source 1 gigabitethernet 0/0 network-clock input-source 2 gigabitethernet 0/1 network-clock synchronization mode QL-enabled no network-clock revertive

86

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

C H A P T E R

4

Using the Management Ethernet Interface

This chapter covers the following topics:

Gigabit Ethernet Management Interface Overview, on page 87

Gigabit Ethernet Port Numbering, on page 87

IP Address Handling in ROMmon and the Management Ethernet Port, on page 88

Gigabit Ethernet Management Interface VRF, on page 88

Common Ethernet Management Tasks, on page 89

Gigabit Ethernet Management Interface Overview

The chassis has one Gigabit Ethernet Management Ethernet interface on each Route Switch Processor.

The purpose of this interface is to allow users to perform management tasks on the router; it is basically an interface that should not and often cannot forward network traffic but can otherwise access the router, often via Telnet and SSH, and perform most management tasks on the router. The interface is most useful before a router has begun routing, or in troubleshooting scenarios when the interfaces are inactive.

The following aspects of the Management Ethernet interface should be noted:

• Each RSP has a Management Ethernet interface, but only the active RSP has an accessible Management

Ethernet interface (the standby RSP can be accessed using the console port, however).

• IPv4, IPv6, and ARP are the only routed protocols supported for the interface.

• The interface provides a method of access to the router even if the interfaces or the IOS processes are down.

• The Management Ethernet interface is part of its own VRF. For more information, see the

Gigabit Ethernet

Management Interface VRF, on page 88

.

Gigabit Ethernet Port Numbering

The Gigabit Ethernet Management port is always GigabitEthernet0.

In a dual RSP configuration, the Management Ethernet interface on the active RSP will always be Gigabit

Ethernet 0, while the Management Ethernet interface on the standby RSP will not be accessible using the

Cisco IOS CLI in the same telnet session. The standby RSP can be accessed via console port using telnet.

The port can be accessed in configuration mode like any other port on the chassis.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

87

Using the Management Ethernet Interface

IP Address Handling in ROMmon and the Management Ethernet Port

Router# config t

Enter configuration commands, one per line.

End with CNTL/Z.

Router(config)# interface gigabitethernet0

Router(config-if)#

IP Address Handling in ROMmon and the Management Ethernet

Port

IP addresses can be configured using ROMmon ( IP_ADDRESS= and IP_SUBNET_MASK= commands) and the IOS command-line interface (the ip address command in interface configuration mode).

Assuming the IOS process has not begun running on the chassis, the IP address that was set in ROMmon acts as the IP address of the Management Ethernet interface. In cases where the IOS process is running and has taken control of the Management Ethernet interface, the IP address specified when configuring the Gigabit

Ethernet 0 interface in the IOS CLI becomes the IP address of the Management Ethernet interface. The

ROMmon-defined IP address is only used as the interface address when the IOS process is inactive.

For this reason, the IP addresses specified in ROMmon and in the IOS CLI can be identical and the Management

Ethernet interface will function properly in single RSP configurations.

In dual RSP configurations, however, users should never configure the IP address in the ROMmon on either

RP0 or RP1 to match each other or the IP address as defined by the IOS CLI. Configuring matching IP addresses introduces the possibility for an active and standby Management Ethernet interface having the same

IP address with different MAC addresses, which will lead to unpredictable traffic treatment or possibility of an RSP boot failure.

Gigabit Ethernet Management Interface VRF

The Gigabit Ethernet Management interface is automatically part of its own VRF. This VRF, which is named

“Mgmt-intf,” is automatically configured on the chassis and is dedicated to the Management Ethernet interface; no other interfaces can join this VRF. Therefore, this VRF does not participate in the MPLS VPN VRF or any other network-wide VRF.

Placing the management ethernet interface in its own VRF has the following effects on the Management

Ethernet interface:

• Many features must be configured or used inside the VRF, so the CLI may be different for certain

Management Ethernet functions on the chassis than on Management Ethernet interfaces on other routers.

• Prevents transit traffic from traversing the router. Because all of the interfaces and the Management

Ethernet interface are automatically in different VRFs, no transit traffic can enter the Management

Ethernet interface and leave an interface, or vice versa.

• Improved security of the interface. Because the Mgmt-intf VRF has its own routing table as a result of being in its own VRF, routes can only be added to the routing table of the Management Ethernet interface if explicitly entered by a user.

The Management Ethernet interface VRF supports both IPv4 and IPv6 address families.

88

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Using the Management Ethernet Interface

Common Ethernet Management Tasks

Common Ethernet Management Tasks

Because users can perform most tasks on a router through the Management Ethernet interface, many tasks can be done by accessing the router through the Management Ethernet interface.

This section documents common configurations on the Management Ethernet interface and includes the following sections:

Viewing the VRF Configuration

The VRF configuration for the Management Ethernet interface is viewable using the show running-config vrf command.

This example shows the default VRF configuration:

Router# show running-config vrf

Building configuration...

Current configuration : 351 bytes vrf definition Mgmt-intf

!

address-family ipv4 exit-address-family

!

address-family ipv6 exit-address-family

!

(some output removed for brevity)

Viewing Detailed VRF Information for the Management Ethernet VRF

To see detailed information about the Management Ethernet VRF, enter the show vrf detail Mgmt-intf command.

Router# show vrf detail Mgmt-intf

VRF Mgmt-intf (VRF Id = 4085); default RD <not set>; default VPNID <not set>

Interfaces:

Gi0

Address family ipv4 (Table ID = 4085 (0xFF5)):

No Export VPN route-target communities

No Import VPN route-target communities

No import route-map

No export route-map

VRF label distribution protocol: not configured

VRF label allocation mode: per-prefix

Address family ipv6 (Table ID = 503316481 (0x1E000001)):

No Export VPN route-target communities

No Import VPN route-target communities

No import route-map

No export route-map

VRF label distribution protocol: not configured

VRF label allocation mode: per-prefix

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

89

Using the Management Ethernet Interface

Setting a Default Route in the Management Ethernet Interface VRF

Setting a Default Route in the Management Ethernet Interface VRF

To set a default route in the Management Ethernet Interface VRF, enter the following command

ip route vrf Mgmt-intf 0.0.0.0 0.0.0.0 next-hop-IP-address

Setting the Management Ethernet IP Address

The IP address of the Management Ethernet port is set like the IP address on any other interface.

Below are two simple examples of configuring an IPv4 address and an IPv6 address on the Management

Ethernet interface.

IPv4 Example

Router(config)# interface GigabitEthernet 0

Router(config-if)# ip address A.B.C.D A.B.C.D

IPv6 Example

Router(config)# interface GigabitEthernet 0

Router(config-if)# ipv6 address X:X:X:X::X

Telnetting over the Management Ethernet Interface

Telnetting can be done through the VRF using the Management Ethernet interface.

In the following example, the router telnets to 172.17.1.1 through the Management Ethernet interface VRF:

Router# telnet 172.17.1.1 /vrf Mgmt-intf

Pinging over the Management Ethernet Interface

Pinging other interfaces using the Management Ethernet interface is done through the VRF.

In the following example, the router pings the interface with the IP address of 172.17.1.1 through the

Management Ethernet interface.

Router# ping vrf Mgmt-intf 172.17.1.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 172.17.1.1, timeout is 2 seconds:

.!!!!

Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/1 ms

Copy Using TFTP or FTP

To copy a file using TFTP through the Management Ethernet interface, the ip tftp source-interface

GigabitEthernet 0 command must be entered before entering the copy tftp command because the copy tftp command has no option of specifying a VRF name.

90

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Using the Management Ethernet Interface

NTP Server

Similarly, to copy a file using FTP through the Management Ethernet interface, the ip ftp source-interface

GigabitEthernet 0 command must be entered before entering the copy ftp command because the copy ftp command has no option of specifying a VRF name.

TFTP Example

Router(config)# ip tftp source-interface gigabitethernet 0

FTP Example

Router(config)# ip ftp source-interface gigabitethernet 0

NTP Server

To allow the software clock to be synchronized by a Network Time Protocol (NTP) time server over the

Management Ethernet interface, enter the ntp server vrf Mgmt-intf command and specify the IP address of the device providing the update.

The following CLI provides an example of this procedure.

Router(config)# ntp server vrf Mgmt-intf 172.17.1.1

SYSLOG Server

To specify the Management Ethernet interface as the source IPv4 or IPv6 address for logging purposes, enter the logging host ip-address vrf Mgmt-intf command.

The following CLI provides an example of this procedure.

Router(config)# logging host <ip-address> vrf Mgmt-intf

SNMP-related services

To specify the Management Ethernet interface as the source of all SNMP trap messages, enter the snmp-server source-interface traps gigabitEthernet 0 command.

The following CLI provides an example of this procedure:

Router(config)# snmp-server source-interface traps gigabitEthernet 0

Domain Name Assignment

The IP domain name assignment for the Management Ethernet interface is done through the VRF.

To define the default domain name as the Management Ethernet VRF interface, enter the ip domain-name

vrf Mgmt-intf domain command.

Router(config)# ip domain-name vrf Mgmt-intf cisco.com

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

91

Using the Management Ethernet Interface

DNS service

DNS service

To specify the Management Ethernet interface VRF as a name server, enter the ip name-server vrf Mgmt-intf

IPv4-or-IPv6-address command.

Router(config)# ip name-server vrf Mgmt-intf

IPv4-or-IPv6-address

RADIUS or TACACS+ Server

To group the Management VRF as part of a AAA server group, enter the ip vrf forward Mgmt-intf command when configuring the AAA server group.

The same concept is true for configuring a TACACS+ server group. To group the Management VRF as part of a TACACS+ server group, enter the ip vrf forwarding Mgmt-intf command when configuring the

TACACS+ server group.

Radius Server Group Configuration

Router(config)# aaa group server radius hello

Router(config-sg-radius)# ip vrf forwarding Mgmt-intf

Tacacs+ Server Group Example outer(config)# aaa group server tacacs+ hello

Router(config-sg-tacacs+)# ip vrf forwarding Mgmt-intf

VTY lines with ACL

To ensure an access control list (ACL) is attached to vty lines that are and are not using VRF, use the vrf-also option when attaching the ACL to the vty lines.

Router(config)# line vty 0 4

Router(config-line)# access-class 90 in vrf-also

92

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

C H A P T E R

5

Configuring Ethernet Interfaces

This chapter provides information about configuring the Gigabit Ethernet interface modules.

For more information about the commands used in this chapter, see the Cisco IOS XE 3S Command References .

Configuring Ethernet Interfaces, on page 93

Verifying the Interface Configuration, on page 102

Verifying Interface Module Status, on page 103

Configuring LAN/WAN-PHY Controllers, on page 104

Configuration Examples, on page 109

Configuring Ethernet Interfaces

This section describes how to configure the Gigabit and Ten Gigabit Ethernet interface modules and includes information about verifying the configuration.

Limitations and Restrictions

• Interface module A900-IMA8Z in slot 0 with A900-RSP3C-200-S supports a maximum of 6 ports at

10GE speed and needs explicit enablement using the hw-module subslot 0/0 A900-IMA8Z mode 6-port command.

• VRF-Aware Software Infrastructure (VASI) interface commnads interface vasileft and interface vasiright are not supported .

• Interface modules have slot restrictions, see NCS 4200 Hardware Installation Guides.

• MPLS MTU is not supported.

• On the RSP3 module, MTU value configured for a BDI interface should match with the MTU configuration for all the physical interfaces, which have a service instance associated with this BDI.

• To replace the configured interface module with a different interface module in a particular slot, run the hw-module subslot slot-num default command.

• Giant counters are not supported.

• Mixed configurations of features are not supported on the same port. For example, one OC-3 port can have only CEM (CESoP or SAToP), ATM, IMA or DS3 configurations, but not a combination of these features on a single port.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

93

Configuring Ethernet Interfaces

Configuring an Interface

• Ingress counters are not incremented for packets of the below packet format on the RSP3 module for the

10 Gigabit Ethernet interfaces, 100 Gigabit Ethernet interfaces, and 40 Gigabit Ethernet interfaces:

MAC header---->Vlan header---->Length/Type

When these packets are received on the RSP3 module, the packets are not dropped, but the counters are not incremented.

• If the IM is shutdown using hw-module subslot shutdown command, then the IM goes out-of-service.

You should perform a Stateful Switchover (SSO) in the interim, as the IM needs to be re-inserted for successful reactivation.

• Following are some of the IMs that are not supported on certain slots when IPsec license is enabled:

• The below IMs are not supported on the Slot 11 on the Cisco ASR 907 router:

• SPA_TYPE_ETHER_IM_8x10GE

• SPA_TYPE_ETHER_IM_2x40GE

• The below IMs are not supported on the Slot 2 on the Cisco ASR 903 router for RSP3-200 and

RSP3-400:

• SPA_TYPE_ETHER_IM_8xGE_SFP_1x10GE

• SPA_TYPE_ETHER_IM_8xGE_CU_1x10GE

• SPA_TYPE_ETHER_IM_1x10GE

• SPA_TYPE_ETHER_IM_8x10GE

• SPA_TYPE_OCX_IM_OC3OC12

• SPA_TYPE_ETHER_IM_8xGE_SFP

• SPA_TYPE_ETHER_IM_8xGE_CU

• CTS signal goes down, when control signal frequency is configured more than 5000 ms and timeout setting is more than 20,000 ms (4x control_frequency), which is greater than the OIR time (~20s) for a selected subordinate to complete an OIR cycle. This results in the primary being unaware that the subordinate is down and CTS of all subordinates are down too. To avoid this situation, ensure that the timeout is shorter than the OIR time of the subordinate. Set the control frequency to less than or equal to 5000 ms and the timeout setting to less than or equal to 20,000 ms before you perform OIR.

Configuring an Interface

This section lists the required configuration steps to configure Gigabit and Ten Gigabit Ethernet interface modules.

Procedure

Step 1

Command or Action configure terminal

Example:

Purpose

Enters global configuration mode.

94

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Ethernet Interfaces

Configuring an Interface

Step 2

Step 3

Step 4

Command or Action Purpose

Router# configure terminal

Do one of the following:

interface gigabitethernet slot/subslot/port

• interface tengigabitethernet slot/subslot/port

Specifies the Gigabit Ethernet or Ten Gigabit

Ethernet interface to configure and enters interface configuration mode, where:

Note The slot number is always 0.

Example:

Router(config)# interface gigabitethernet

0/0/1

Example:

Example:

Router(config)# interface tengigabitethernet 0/0/1

ip address ip-address mask { secondary } | dhcp { client-id interface-name }{ hostname host-name

Example:

}]

Router(config-if)# ip address 192.168.1.1

255.255.255.255 dhcp hostname host1

Sets a primary or secondary IP address for an interface that is using IPv4, where:

• ip-address —The IP address for the interface.

• mask —The mask for the associated IP subnet.

• secondary —(Optional) Specifies that the configured address is a secondary IP address. If this keyword is omitted, the configured address is the primary IP address.

• dhcp —Specifies that IP addresses will be assigned dynamically using DHCP.

client-id interface-name —Specifies the client identifier. The interface-name sets the client identifier to the hexadecimal

MAC address of the named interface.

hostname host-name —Specifies the hostname for the DHCP purposes. The host-name is the name of the host to be placed in the DHCP option 12 field.

no negotiation auto

Example:

Router(config-if)# no negotiation auto

(Optional) Disables automatic negotitation.

Note Use the speed command only when the mode is set to no negotiation auto.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

95

Configuring Ethernet Interfaces

Configuring an Interface

Step 5

Step 6

Command or Action speed { 10 | 100 | 1000 }

Example:

Router(config-if)# speed 1000

mtu bytes

Example:

Router(config-if)# mtu 1500

Step 7 standby [ group-number ] ip [ ip-address

[ secondary ]]

Example:

Router(config-if)# standby 250 ip

192.168.10.1

Step 8 no shutdown

Example:

Router(config-if)# no shutdown

Purpose

(Optional) Specifies the speed for an interface to transmit at 10, 100, and 1000 Mbps (1 Gbps), where the default is 1000 Mbps.

(As Required) Specifies the maximum packet size for an interface, where:

• bytes— The maximum number of bytes for a packet.

The default is 1500 bytes; the range is from

1500 to 9216.

Creates or enables the Hot Standby Router

Protocol (HSRP) group using its number and virtual IP address, where:

• (Optional) group-number —The group number on the interface for which HSRP is being enabled. The range is from 0 to

255; the default is 0. If there is only one

HSRP group, you do not need to enter a group number.

• ( Optional on all but one interface if configuring HSRP ) ip-address —The virtual IP address of the hot standby router interface. You must enter the virtual IP address for at least one of the interfaces; it can be learned on the other interfaces.

• (Optional) secondary —Specifies that the

IP address is a secondary hot standby router interface. If neither router is designated as a secondary or standby router and no priorities are set, the primary

IP addresses are compared and the higher

IP address is the active router, with the next highest as the standby router.

Note

Note

This command is required only for configurations that use HSRP.

This command enables HSRP but does not configure it further.

Enables the interface.

96

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Ethernet Interfaces

Specifying the Interface Address on an Interface Module

Specifying the Interface Address on an Interface Module

To configure or monitor Ethernet interfaces, you need to specify the physical location of the interface module and interface in the CLI. The interface address format is slot/subslot/port, where:

• slot—The chassis slot number in the chassis where the interface module is installed.

Note The interface module slot number is always 0.

• subslot—The subslot where the interface module is installed. Interface module subslots are numbered from 0 to 5 for ASR 903 and from 0 to 15 for ASR 907, from bottom to top.

• port—The number of the individual interface port on an interface module.

The following example shows how to specify the first interface (0) on an interface module installed in the first interface module slot:

Router(config)# interface GigabitEthernet 0/0/0 no ip address shutdown negotiation auto no cdp enable

Configuring Hot Standby Router Protocol

Hot Standby Router Protocol (HSRP) provides high network availability because it routes IP traffic from hosts without relying on the availability of any single router. You can deploy HSRP in a group of routers to select an active router and a standby router. (An active router is the router of choice for routing packets; a standby router is a router that takes over the routing duties when an active router fails, or when preset conditions are met).

HSRP is enabled on an interface by entering the standby [ group-number ] ip [ ip-address [ secondary ]] command. The standby command is also used to configure various HSRP elements. This document does not discuss more complex HSRP configurations. For additional information on configuring HSRP, see to the

HSRP section of the Cisco IP Configuration Guide publication that corresponds to your Cisco IOS XE software release. In the following HSRP configuration, standby group 2 on Gigabit Ethernet port 0/1/0 is configured at a priority of 110 and is also configured to have a preemptive delay should a switchover to this port occur:

Router(config)# interface GigabitEthernet 0/1/0

Router(config-if)# standby 2 ip 192.168.1.200

Router(config-if)# standby 2 priority 110

Router(config-if)# standby 2 preempt

The maximum number of different HSRP groups that can be created on one physical interface is 4. If additional groups are required, create 4 groups on the physical interface, and the remaining groups on the BDI or on another physical interface.

Note TCAM space utilization changes when HSRP groups are configured on the router. If HSRP groups are configured the TCAM space is utilized. Each HSRP group takes 1 TCAM entry. The “Out of TCAM” message may be displayed if total number of TCAM space used by HSRP groups and prefixes on the router exceeds scale limit.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

97

Configuring Ethernet Interfaces

Verifying HSRP

Note HSRP state flaps with sub-second “Hello” or “Dead” timers.

Restrictions

HSRPv2 is not supported.

Verifying HSRP

To verify the HSRP information, use the show standby command in EXEC mode:

Router# show standby

Ethernet0 - Group 0

Local state is Active, priority 100, may preempt

Hellotime 3 holdtime 10

Next hello sent in 0:00:00

Hot standby IP address is 198.92.72.29 configured

Active router is local

Standby router is 198.92.72.21 expires in 0:00:07

Standby virtual mac address is 0000.0c07.ac00

Tracking interface states for 2 interfaces, 2 up:

UpSerial0

UpSerial1

Modifying the Interface MTU Size

Note The maximum number of unique MTU values that can be configured on the physical interfaces on the chassis is 8. Use the show platform hardware pp active interface mtu command to check the number of values currently configured on the router. This is not applicable on Cisco ASR 900 RSP3 Module.

The Cisco IOS software supports three different types of configurable maximum transmission unit (MTU) options at different levels of the protocol stack:

• Interface MTU—The interface module checks the MTU value of incoming traffic. Different interface types support different interface MTU sizes and defaults. The interface MTU defines the maximum packet size allowable (in bytes) for an interface before drops occur. If the frame is smaller than the interface MTU size, but is not smaller than the minimum frame size for the interface type (such as 64 bytes for Ethernet), then the frame continues to process.

• MPLS MTU—If the MPLS MTU is set to a value, for example, 1500 bytes, the value is programmed as

1504 bytes at the hardware level to allow the addition of one label. Consider the case of pseudowire. If the packet size of Layer 2 traffic sent with four bytes of Frame Check Sequence (FCS) to the pseudowire is 1500 bytes, then and four bytes of pseudowire control word and one pseudowire label (label size is four bytes) is added to the packet, the packet size is now 1508 bytes with FCS. However, note that while calculating the packet size, FCS is not considered. So the calculated packet size is 1504 bytes, which is equal to the MPLS MTU programmed in the hardware. This packet is forwarded as expected.

However, if another label is added to this packet, the packet size becomes 1508 bytes without FCS. This value is greater than programmed MTU value, so this packet is dropped. This restriction applies not only to pseudowire, but to the entire MPLS network.

98

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Ethernet Interfaces

Interface MTU Configuration Guidelines

To ensure that packets are not dropped, MPLS MTUs should be set considering the maximum size of the label stack that is added to the packet in the network.

For the Gigabit Ethernet interface module on the chassis, the default MTU size is 1500 bytes. The maximum configurable MTU is 9216 bytes. The interface module automatically adds an additional 22 bytes to the configured MTU size to accommodate some of the additional overhead.

Limitations

In EtherLike-MIB, the dot3StatsFrameTooLongs frames count in SNMP increases when the frame packet size is more than the default MTU.

Interface MTU Configuration Guidelines

When configuring the interface MTU size, consider the following guidelines:

• The default interface MTU size accommodates a 1500-byte packet, plus 22 additional bytes to cover the following additional overhead:

• Layer 2 header—14 bytes

• Dot1q header—4 bytes

• CRC—4 bytes

• Interface MTU is not supported on BDI Interface

Configuring Interface MTU

To modify the MTU size on an interface, use the following command in interface configuration mode:

Command

mtu bytes

Router(config-if)# mtu bytes

Purpose

Configures the maximum packet size for an interface, where:

• bytes— Specifies the maximum number of bytes for a packet.

The default is 1500 bytes and the maximum configurable MTU is 9216 bytes.

To return to the default MTU size, use the no form of the command.

Note When IP FRR over BDI is configured, the maximum allowed packet size is 1504 bytes.

When the BGP-PIC core is enabled, a packet destined to a prefix that is learnt through eBGP, is dropped if the packet size is greater than 1504 bytes. To work around this limitation, do one of the following:

• Disable the BGP-PIC core,

• Use the static route, or

• Use routed-port instead of BDI.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

99

Configuring Ethernet Interfaces

Verifying the MTU Size

Verifying the MTU Size

To verify the MTU size for an interface, use the show interfaces gigabitethernet privileged EXEC command and observe the value shown in the “MTU” field.

The following example shows an MTU size of 1500 bytes for interface port 0 (the second port) on the Gigabit

Ethernet interface module installed in slot 1:

Router# show interfaces gigabitethernet 0/1/0

GigabitEthernet0/1/0 is up, line protocol is up

Hardware is NCS4200-1T8LR-PS, address is d0c2.8216.0590 (bia d0c2.8216.0590)

MTU 1500 bytes

, BW 1000000 Kbit/sec, DLY 10 usec, reliability 255/255, txload 1/255, rxload 22/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Configuring the Encapsulation Type

The only encapsulation supported by the interface modules is IEEE 802.1Q encapsulation for virtual LANs

(VLANs).

Note VLANs are only supported on Ethernet Virtual Connection (EVC) service instances and Trunk Ethernet Flow

Point (EFP) interfaces.

Configuring Autonegotiation on an Interface

Gigabit Ethernet interfaces use a connection-setup algorithm called autonegotiation.

Autonegotiation allows the local and remote devices to configure compatible settings for communication over the link. Using autonegotiation, each device advertises its transmission capabilities and then agrees upon the settings to be used for the link.

For the Gigabit Ethernet interfaces on the chassis, flow control is autonegotiated when autonegotiation is enabled. Autonegotiation is enabled by default.

When enabling autonegotiation, consider these guidelines:

• If autonegotiation is disabled on one end of a link, it must be disabled on the other end of the link. If one end of a link has autonegotiation disabled while the other end of the link does not, the link will not come up properly on both ends.

• Flow control is enabled by default.

• Flow control will be on if autonegotiation is disabled on both ends of the link.

Enabling Autonegotiation

To enable autonegotiation on a Gigabit Ethernet interface, use the following command in interface configuration mode:

100

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Ethernet Interfaces

Disabling Autonegotiation

Command negotiation auto

Router(config-if)# negotiation auto

Purpose

Enables autonegotiation on a Gigabit Ethernet interface. Advertisement of flow control occurs.

Disabling Autonegotiation

Autonegotiation is automatically enabled and can be disabled on Gigabit Ethernet interfaces . During autonegotiation, advertisement for flow control, speed, and duplex occurs, depending on the media (fiber or copper) in use.

Speed and duplex configurations can be advertised using autonegotiation. The values that are negotiated are:

• For Gigabit Ethernet interfaces using RJ-45 ports and for Copper (Cu) SFP ports—10, 100, and 1000

Mbps for speed and full-duplex mode. Link speed is not negotiated when using fiber interfaces.

To disable autonegotiation, use the following command in interface configuration mode:

Command Purpose no negotiation auto

Router(config-if)# no negotiation auto

Disables autonegotiation on Gigabit Ethernet interfaces. No advertisement of flow control occurs.

Configuring Carrier Ethernet Features

For information about configuring an Ethernet interface as a layer 2 Ethernet virtual circuit (EVC) or Ethernet flow point (EFP), see the Ethernet Virtual Connections.

Saving the Configuration

To save your running configuration to NVRAM, use the following command in privileged EXEC configuration mode:

Command Purpose copy running-config startup-config Writes the new configuration to NVRAM.

Router# copy running-config startup-config

For information about managing your system image and configuration files, refer to the Cisco IOS Configuration

Fundamentals Configuration Guide and Cisco IOS Configuration Fundamentals Command Reference publications that correspond to your Cisco IOS software release.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

101

Configuring Ethernet Interfaces

Shutting Down and Restarting an Interface

Shutting Down and Restarting an Interface

You can shut down and restart any of the interface ports on an interface module independently of each other.

Shutting down an interface stops traffic and enters the interface into an “administratively down” state.

If you are preparing for an OIR of an interface module, it is not necessary to independently shut down each of the interfaces prior to deactivation of the module.

Command Purpose shutdown router#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

router(config) router(config)#interface GigabitEthernet 0/1/0 router(config-if)#shutdown

Restarts, stops, or starts an interface.

no shutdown router#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

router(config) router(config)#interface GigabitEthernet 0/1/0 router(config-if)#no shutdown

Verifying the Interface Configuration

Besides using the show running-configuration command to display the configuration settings, you can use the show interfaces gigabitethernet command to get detailed information on a per-port basis for your Gigabit

Ethernet interface module.

Verifying Per-Port Interface Status

To find detailed interface information on a per-port basis for the Gigabit Ethernet interface module, use the show interfaces gigabitethernet command.

The following example provides sample output for interface port 0 on the interface module located in slot 1:

Router# show interfaces GigabitEthernet0/1/0

GigabitEthernet0/1/0 is up, line protocol is up

Hardware is NCS4200-1T8LR-PS, address is d0c2.8216.0590 (bia d0c2.8216.0590)

MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full Duplex, 1000Mbps, link type is auto, media type is RJ45 output flow-control is off, input flow-control is off

ARP type: ARPA, ARP Timeout 04:00:00

Last input never, output 08:59:45, output hang never

Last clearing of show interface counters 09:00:18

Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

102

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Ethernet Interfaces

Verifying Interface Module Status

Output queue: 0/40 (size/max)

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

11 packets input, 704 bytes, 0 no buffer

Received 11 broadcasts (0 IP multicasts)

0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog, 0 multicast, 0 pause input

0 packets output, 0 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 unknown protocol drops

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 0 pause output

0 output buffer failures, 0 output buffers swapped out

Verifying Interface Module Status

You can use various show commands to view information specific to SFP, XFP, CWDM, and DWDM optical transceiver modules.

Note The show interface transceiver command is not supported on the router.

To check or verify the status of an SFP Module or XFP Module, use the following show commands:

Use show hw-module slot/subslot transceiver port status or show interfaces interface transceiver detail to view the threshold values for temperature, voltage and so on.

For example, show hw-module subslot 0/5 transceiver 1 status or show interfaces tenGigabitEthernet

0/5/1 transceiver detail .

Command Purpose

show hw-module slot/subslot

transceiver port idprom

show hw-module slot/subslot

transceiver port idprom status

show hw-module slot/subslot

transceiver port idprom dump

Displays information for the transceiver identification programmable read only memory (idprom).

Note Transceiver types must match for a connection between two interfaces to become active.

Displays information for the transceiver initialization status.

Note The transmit and receive optical power displayed by this command is useful for troubleshooting Digital Optical

Monitoring (DOM). For interfaces to become active, optical power must be within required thresholds.

Displays a dump of all EEPROM content stored in the transceiver.

The following show hw-module subslot command sample output is for 1000BASE BX10-U:

Router#show hw-module subslot 0/2 transceiver 0 idprom brief

IDPROM for transceiver GigabitEthernet0/2/0:

Description = SFP or SFP+ optics (type 3)

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

103

Configuring Ethernet Interfaces

Configuring LAN/WAN-PHY Controllers

Transceiver Type:

Product Identifier (PID)

Vendor Revision

Serial Number (SN)

Vendor Name

Vendor OUI (IEEE company ID)

CLEI code

Cisco part number

Device State

= 1000BASE BX10-U (259)

= GLC-BX-U

= 1.0

= NPH20441771

= CISCO-NEO

= 00.15.06 (5382)

= IPUIAG5RAC

= 10-2094-03

= Enabled.

Date code (yy/mm/dd)

Connector type

Encoding

= 16/11/12

= LC.

= 8B10B (1)

Nominal bitrate = GE (1300 Mbits/s)

Minimum bit rate as % of nominal bit rate = not specified

Maximum bit rate as % of nominal bit rate = not specified

Router#

The following show hw-module subslot command sample output is for an SFP+ 10GBASE-SR:

Router#show hw-module subslot 0/2 transceiver 8 idprom brief

IDPROM for transceiver TenGigabitEthernet0/2/8:

Description = SFP or SFP+ optics (type 3)

Transceiver Type:

Product Identifier (PID)

= SFP+ 10GBASE-SR (273)

= SFP-10G-SR

Vendor Revision

Serial Number (SN)

Vendor Name

Vendor OUI (IEEE company ID)

CLEI code

= 2

= JUR2052G19W

= CISCO-LUMENTUM

= 00.01.9C (412)

= COUIA8NCAA

Cisco part number

Device State

Date code (yy/mm/dd)

Connector type

Encoding

= 10-2415-03

= Enabled.

= 16/12/21

= LC.

= 64B/66B (6)

Nominal bitrate = (10300 Mbits/s)

Minimum bit rate as % of nominal bit rate = not specified

Maximum bit rate as % of nominal bit rate = not specified

Router#

Note VID for optics displayed in show inventory command and vendor revision shown in idprom detail command output are stored in diffrent places in Idprom.

Configuring LAN/WAN-PHY Controllers

The LAN/WAN-PHY controllers are configured in the physical layer control element of the Cisco IOS XE software.

Restrictions for LAN/WAN-PHY Mode

• Effective with Cisco IOS XE Release 3.18.1SP, A900-IMA8Z Interface Modules (IM) support

LAN/WAN-PHY mode.

• The following A900-IMA8Z IM alarms are not supported:

104

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Ethernet Interfaces

Configuring LAN-PHY Mode

• NEWPTR

• PSE

• NSE

• FELCDP

• FEAISP

Configuring LAN-PHY Mode

This section describes how to configure LAN-PHY mode on the Gigabit Ethernet interface modules.

Procedure

Step 1

Step 2

Command or Action Purpose

show controllers wanphy slot/subslot/port

Example:

Displays the configuration mode of the

LAN/WAN-PHY controller. Default configuration mode is LAN.

Router# show controllers wanphy 0/1/0

TenGigabitEthernet0/1/0

Mode of Operation: WAN Mode

SECTION

LOF = 0 LOS = 0

BIP(B1) = 0

LINE

AIS = 0

FEBE = 0

RDI = 0

BIP(B2) = 0

PATH

AIS = 0

FEBE = 0

LOP = 0

PSE = 0

RDI = 0

BIP(B3) = 0

NEWPTR = 0

NSE = 0

WIS ALARMS

SER = 0

FEAISP = 0

WLOS = 0

LFEBIP = 0

FELCDP = 0

PLCD = 0

PBEC = 0

Active Alarms[All defects]: SWLOF LAIS

PAIS SER

Active Alarms[Highest Alarms]: SWLOF

Alarm reporting enabled for: SF SWLOF

B1-TCA B2-TCA PLOP WLOS

Rx(K1/K2): 00/00 Tx(K1/K2): 00/00

S1S0 = 00, C2 = 0x1A

PATH TRACE BUFFER: UNSTABLE

Remote J1 Byte :

BER thresholds: SD = 10e-6 SF = 10e-3

TCA thresholds: B1 = 10e-6 B2 = 10e-6

B3 = 10e-6

If the configuration mode is WAN, complete the rest of the procedure to change the configuration mode to LAN.

• slot / subslot interface.

/ port —The location of the configure terminal

Example:

Enters global configuration mode.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

105

Configuring Ethernet Interfaces

Configuring WAN-PHY Mode

Step 3

Step 4

Step 5

Command or Action Purpose

Router# configure terminal

Do the following:

hw-module subslot slot/subslot interface

port enable LAN

Configures LAN-PHY mode for the Ethernet interface module.

• slot / subslot interface.

/ port —The location of the

Example:

Router(config)# hw-module subslot 0/1 enable LAN

Example:

Use the hw-module subslot slot/subslot

interface port enable LAN command to configure the LAN-PHY mode for the Ethernet interface module.

Router(config)# hw-module subslot 0/1 interface 1 enable LAN exit

Example:

Exits global configuration mode and enters privileged EXEC mode.

Router(config)# exit

show controllers wanphy slot/subslot/port

Example:

Router# show controllers wanphy 0/1/2

TenGigabitEthernet0/1/2

Mode of Operation: LAN Mode

Displays configuration mode for the

LAN/WAN-PHY controller. The example shows the mode of operation as LAN mode for the Cisco 8-Port 10 Gigabit Ethernet

LAN/WAN-PHY Controller.

Configuring WAN-PHY Mode

This section describes how to configure WAN-PHY mode on the Gigabit Ethernet interface modules.

Procedure

Step 1

Step 2

Command or Action

show controllers wanphy slot/subslot/port

Example:

Router# show controllers wanphy 0/1/0

TenGigabitEthernet0/1/0

Mode of Operation: LAN Mode configure terminal

Example:

Purpose

Displays the configuration mode of the

WAN-PHY controller. Default configuration mode is LAN.

• slot / subslot / port —The location of the interface.

Enters global configuration mode.

Router# configure terminal

106

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Ethernet Interfaces

Configuring WAN-PHY Mode

Step 3

Step 4

Step 5

Command or Action Purpose

Do the following:

hw-module subslot slot/subslotinterface port enable WAN

Configures WAN-PHY mode for the Ethernet interface module.

• slot / subslot interface.

/ port —The location of the

Example:

Router(config)# hw-module subslot 0/1 enable WAN

Example:

Use the hw-module subslot slot/subslot

interface port enable WAN command to configure the WAN-PHY mode for the Ethernet interface module.

Router(config)# hw-module subslot 0/1 interface 1 enable WAN exit

Example:

Exits global configuration mode and enters privileged EXEC mode.

Router(config)# exit

show controllers wanphy slot/subslot/port

Example:

Router# show controllers wanphy 0/1/5

TenGigabitEthernet0/1/5

Mode of Operation: WAN Mode

SECTION

LOF = 0 LOS = 0

BIP(B1) = 0

LINE

AIS = 0

FEBE = 0

PATH

RDI = 0

BIP(B2) = 0

AIS = 0

FEBE = 0

LOP = 0

PSE = 0

WIS ALARMS

SER = 0

FEAISP = 0

WLOS = 0

RDI

NSE

= 0

BIP(B3) = 0

NEWPTR = 0

= 0

FELCDP = 0

PLCD = 0

LFEBIP = 0 PBEC = 0

Active Alarms[All defects]: SWLOF LAIS

PAIS SER

Active Alarms[Highest Alarms]: SWLOF

Alarm reporting enabled for: SF SWLOF

B1-TCA B2-TCA PLOP WLOS

Rx(K1/K2): 00/00 Tx(K1/K2): 00/00

S1S0 = 00, C2 = 0x1A

PATH TRACE BUFFER: UNSTABLE

Remote J1 Byte :

BER thresholds: SD = 10e-6 SF = 10e-3

TCA thresholds: B1 = 10e-6 B2 = 10e-6

B3 = 10e-6

Displays configuration mode for the

LAN/WAN-PHY controller. The example shows the mode of operation as WAN mode for the Cisco 8-Port 10 Gigabit Ethernet

LAN/WAN-PHY Controller.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

107

Configuring Ethernet Interfaces

Configuring WAN-PHY Error Thresholds

Configuring WAN-PHY Error Thresholds

This section describes how to configure WAN-PHY Signal Failure (SF) and Signal Degrade (SD) Bit Error

Rate (BER) reporting and thresholds.

An SF alarm is triggered if the line bit error (B2) rate exceeds a user-provisioned threshold range (over the range of 10e-3 to 10e-9).

An SD alarm is declared if the line bit error (B2) rate exceeds a user-provisioned threshold range (over the range of 10e-3 to 10e-9). If the B2 errors cross the SD threshold, a warning about link quality degradation is triggered. The WAN-PHY alarms are useful for some users who are upgrading their Layer 2 core network from a SONET ring to a 10-Gigabit Ethernet ring.

Before you begin

The controller must be in the WAN-PHY mode before configuring the SF and SD BER reporting and thresholds.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action configure terminal

Example:

Purpose

Enters global configuration mode.

Router# configure terminal

controller wanphy slot/subslot/port

Example:

Enters WAN physical controller configuration mode in which you can configure a 10-Gigabit

Ethernet WAN-PHY controller.

Router(config)# controller wanphy 0/3/0 slot / subslot / port —The location of the interface.

wanphy { delay | flag | report-alarm | threshold { b1-tca | b2-tca | sd-ber | sf-ber [ bit error rate ]}}

Example:

Router(config-controller)# wanphy threshold b1-tca 6

Configures WAN-PHY controller processing.

• delay—Delays WAN-PHY alarm triggers.

• flag—Specifies byte values.

• report-alarm—Configures WAN-PHY alarm reporting.

• threshold—Sets BER threshold values.

• b1-tca—Sets B1 alarm BER threshold.

• b2-tca—Sets B2 alarm BER threshold.

• sd-ber—Sets Signal Degrade BER threshold.

• sf-ber—Sets Signal Fail BER threshold.

• bit error rate— Specifies bit error rate.

end

Example:

Exits controller configuration mode and enters privileged EXEC mode.

108

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Ethernet Interfaces

Configuration Examples

Command or Action

Router(config-controller)# end

Purpose

Configuration Examples

Example: Basic Interface Configuration

The following example shows how to enter the global configuration mode to configure an interface, configure an IP address for the interface, and save the configuration:

! Enter global configuration mode.

!

Router# configure terminal

! Enter configuration commands, one per line. End with CNTL/Z.

!

! Specify the interface address.

!

Router(config)# interface gigabitethernet 0/0/1

!

! Configure an IP address.

!

Router(config-if)# ip address 192.168.50.1 255.255.255.0

!

! Start the interface.

!

Router(config-if)# no shut

!

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

109

Configuring Ethernet Interfaces

Example: MTU Configuration

! Save the configuration to NVRAM.

!

Router(config-if)# exit

Router# copy running-config startup-config

Example: MTU Configuration

Note The maximum number of unique MTU values that can be configured on the physical interfaces on the chassis is eight. Use the show platform hardware pp active interface mtu command to check the number of values currently configured on the router.

The following example shows how to set the MTU interface to 9216 bytes.

Note The interface module automatically adds an additional 38 bytes to the configured MTU interface size.

! Enter global configuration mode.

!

Router# configure terminal

! Enter configuration commands, one per line. End with CNTL/Z.

!

! Specify the interface address

!

Router(config)# interface gigabitethernet 0/0/1

!

! Configure the interface MTU.

!

Router(config-if)# mtu 9216

110

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring Ethernet Interfaces

Example: VLAN Encapsulation

Example: VLAN Encapsulation

The following example shows how to configure interface module port 2 (the third port) and configure the first interface on the VLAN with the ID number 268 using IEEE 802.1Q encapsulation:

! Enter global configuration mode.

!

Router# configure terminal

! Enter configuration commands, one per line. End with CNTL/Z.

!

! Enter configuration commands, one per line. End with CNTL/Z.

!

Router(config)# service instance 10 ethernet

!

! Configure dot1q encapsulation and specify the VLAN ID.

Router(config-subif)# encapsulation dot1q 268

!

Note VLANs are supported only on EVC service instances and Trunk EFP interfaces.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

111

Example: VLAN Encapsulation

Configuring Ethernet Interfaces

112

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

C H A P T E R

6

Configuring the Global Navigation Satellite

System

The chassis uses a satellite receiver, also called the global navigation satellite system (GNSS), as a new timing interface.

In typical telecom networks, synchronization works in a hierarchal manner where the core network is connected to a stratum-1 clock and this clock is then distributed along the network in a tree-like structure. However, with a GNSS receiver, clocking is changed to a flat architecture where access networks can directly take clock from satellites in sky using an on-board GPS chips.

This capability simplifies network synchronization planning, provides flexibility and resilience in resolving network synchronization issues in the hierarchical network.

Information About the GNSS, on page 113

How to Configure the GNSS, on page 115

Configuration Example For Configuring GNSS, on page 118

Additional References, on page 119

Information About the GNSS

Overview of the GNSS Module

The GNSS module is present on the front panel of the RSP3 module and can be ordered separately with PID=.

However, there is no license required to enable the GNSS module.

The GNSS LED on the RSP3 front panel indicates the status of the module. The following table explains the different LED status.

Description LED

Status

Green GNSS Normal State. Self survey is complete.

Amber All other states

When connected to an external antenna, the module can acquire satellite signals and track up to 32 GNSS satellites, and compute location, speed, heading, and time. GNSS provides an accurate one pulse-per-second

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

113

Configuring the Global Navigation Satellite System

Operation of the GNSS Module

(PPS), a stable 10 MHz frequency output to synchronize broadband wireless, aggregation and pre-aggregation routers, and an accurate time-of-day (ToD).

Note The RSP3 module can also receive 1PPS, 10 MHz, and ToD signals from an external clocking and timing source. However, the timing signals from the GNSS module (when enabled) take precedence over those of the external source.

By default, anti-jamming is enabled on the GNSS module.

Operation of the GNSS Module

The GNSS module has the following stages of acquiring and providing timing signals to the Cisco router:

• Self-Survey Mode—When the router is reset, the GNSS module comes up in self-survey mode. It tries to lock on to minimum four different satellites and computes approximately 2000 different positions of the satellites to obtain a 3-D location (Latitude, Longitude, and Height) of it current position. This operation takes about 35-to-40 minutes. During this stage also, the module is able to generate accurate timing signals and achieve a Normal or Phase-locked state.

When GNSS moves into Normal state, you can start using the 1PPS, 10 MHz, and ToD inputs from GNSS.

The quality of the signal in Self-Survey mode with Normal state is considered good enough to lock to GNSS.

• Over determined clock mode—The router switches to over determined (OD) mode when the self-survey mode is complete and the position information is stored in non-volatile memory on the router. In this mode, the module only processes the timing information based on satellite positions captured in self-survey mode.

The router saves the tracking data, which is retained even when the router is reloaded. If you want to change the tracking data, use the no shutdown command to set the GNSS interface to its default value.

The GNSS module stays in the OD mode unless one of the following conditions occur:

• A position relocation of the antenna of more than 100 meters is detected. This detection causes an automatic restart of the self-survey mode.

• A manual restart of the self-survey mode or when the stored reference position is deleted.

• A worst-case recovery option after a jamming-detection condition that cannot be resolved with other methods.

You can configure the GNSS module to automatically track any satellite or configure it to explicitly use a specific constellation. However, the module uses configured satellites only in the OD mode.

Note GLONASS and BeiDou satellites cannot be enabled simultaneously. GALILEO is not supported.

When the router is reloaded, it always comes up in the OD mode unless:

• the router is reloaded when the Self-Survey mode is in progress

• the physical location of the router is changed to more than 100 m from it’s pre-reloaded condition.

114

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the Global Navigation Satellite System

Anti-Jamming

When the GNSS self-survey is restarted using the default gnss slot R0/R1 command in config mode, the

10MHz, 1PPS, and ToD signals are not changed and remain up.

Anti-Jamming

By default, anti-jamming is enabled on the GNSS module.

High Availability for GNSS

The chassis has two GNSS modules, one each on the active and standby RSP3 modules. Each GNSS module must have a separate connection to the antenna in case of an RSP3 switchover.

Prerequisites for GNSS

To use GNSS:

• 1PPS, 10 MHz, and ToD must be configured for netsync and PTP. For more information see the

Configuring Clocking and Timing chapter .

• The antenna must have a clear view of the sky. For proper timing, minimum of four satellites should be locked. For information, see the Cisco NCS 4206 Series Hardware Installation Guide .

Restrictions for GNSS

• The GNSS module is not supported through SNMP; all configurations are performed through commands.

• On HA system, the traps from the standby system are logged to the console as the SNMP infra does not get enabled on standby RSP module.

• GNSS objects or performance counters are updated every 5 seconds locally and acknowledge the MIB object request accordingly.

• GNSS traps generation is delayed for 300 seconds for the first time after system startes to avoid any drop of GNSS traps.

How to Configure the GNSS

Note To know more about the commands referenced in this document, see the Cisco IOS Master Command List .

Enabling the GNSS License

enable configure terminal license feature gnss exit

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

115

Configuring the Global Navigation Satellite System

Enabling the GNSS on the Cisco Router

Enabling the GNSS on the Cisco Router

enable configure terminal

gnss slot r0 no shutdown exit

Note After the GNSS module is enabled, GNSS will be the source for 1PPS, ToD, and 10MHz clocking functions.

Configuring the Satellite Constellation for GNSS

enable configure terminal

gnss slot r0 constellation [ auto | gps | galelio | beidou | qzss exit

Configuring Pulse Polarity

enable configure terminal

gnss slot r0

1pps polarity negative exit

Note The no 1pps polarity negative command returns the GNSS to default mode (positive is the default value).

Configuring Cable Delay

enable configure terminal

gnss slot r0

1pps offset 5 exit

Note It is recommended to compensate 5 nanosecond per meter of the cable.

The no 1pps offset command sets cable delay offset to zero.

116

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the Global Navigation Satellite System

Disabling Anti-Jam Configuration

Disabling Anti-Jam Configuration

enable configure terminal gnss slot ro anti-jam disable exit

Verifying the Configuration of the GNSS

Use the show gnss status command to display status of GNSS.

Router# show gnss status

GNSS status:

GNSS device: detected

Lock status: Normal

Receiver Status: Auto

Clock Progress: Phase Locking

Survey progress: 100

Satellite count: 22

Holdover Duration: 0

PDOP: 1.04

TDOP: 1.00

HDOP: 0.73

VDOP: 0.74

Minor Alarm: NONE

Major Alarm: None

Use the show gnss satellite command to display the status of all satellite vehicles that are tracked by the

GNSS module.

Router# show gnss satellite all

All Satellites Info:

31

24

79

78

SV PRN No Channel No Acq Flg Ephemeris Flg SV Type Sig Strength

----------------------------------------------------------------------------------

14

21

0

2

1

1

1

1

0

0

47

47

22

18

27

3

4

6

1

1

1

1

1

1

0

0

0

46

47

44

8

10

12

13

0

1

1

1

1

1

1

1

1

1

0

0

49

42

18

26

Router# show gnss satellite 21

Selected Satellite Info:

SV PRN No: 21

Channel No: 2

Acquisition Flag: 1

Ephemeris Flag: 1

SV Type: 0

Signal Strength: 47

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

117

Configuring the Global Navigation Satellite System

Swapping the GNSS Module

Router# show gnss time

Current GNSS Time:

Time: 2015/10/14 12:31:01 UTC Offset: 17

Router# show gnss location

Current GNSS Location:

LOC: 12:56.184000 N 77:41.768000 E 814.20 m

Use the show gnss device to displays the hardware information of the active GNSS module.

Router# show gnss device

GNSS device:

Serial number: FOC2130ND5X

Firmware version: 1.4

Firmware update progress: NA

Authentication: Passed

Swapping the GNSS Module

Hot swap is supported on the RSP3 module of the GNSS.

1.

Remove the standby RSP module.

2.

Replace the GNSS module on the standby RSP slot.

3.

Reinsert the RSP into the chassis and wait for the RSP to boot with standby ready.

4.

Check for GNSS Lock Status of the standby RSP. Use command show platform hardware slot < R0/R1 >

[ network-clocks | sec GNSS ] to verify.

5.

Trigger SSO after the GNSS on standby RSP is locked.

6.

Repeat steps 1–3 for the other RSP.

Configuration Example For Configuring GNSS

gnss slot R0 no shutdown anti-jam disable constellation glonass

1pps polarity negative

1pps offset 1000 negative

118

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the Global Navigation Satellite System

Additional References

Additional References

Standards

Standard Title

— There are no associated standards for this feature,

MIBs

MIB MIBs Link

• There are no MIBs for this feature.

To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following

URL: http://www.cisco.com/go/mibs

RFCs

RFC Title

— There are no associated RFCs for this feature.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

119

Additional References

Configuring the Global Navigation Satellite System

120

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

C H A P T E R

7

G.8275.1 Telecom Profile

First Published: March 29, 2016

Precision Time Protocol (PTP) is a protocol for distributing precise time and frequency over packet networks.

PTP is defined in the IEEE Standard 1588. It defines an exchange of timed messages

PTP allows for separate profiles to be defined in order to adapt PTP for use in different scenarios. A profile is a specific selection of PTP configuration options that are selected to meet the requirements of a particular application.

This recommendation allows for proper network operation for phase and time synchronization distribution when network equipment embedding a telecom boundary clock (T-BC) and a telecom time subordinate clock

(T-TSC) is timed from another T-BC or a telecom grandmaster clock (T-GM). This recommendation addresses only the distribution of phase and time synchronization with the full timing support architecture as defined in ITU-T G.8275.

Why G.8275.1?, on page 121

Configuring the G.8275.1 Profile, on page 125

Additional References, on page 130

Feature Information for G.8275.1, on page 130

Why G.8275.1?

The G.8275.1 profile is used in mobile cellular systems that require accurate synchronization of time and phase. For example, the fourth generation (4G) of mobile telecommunications technology.

The G.8275.1 profile is also used in telecom networks where phase or time-of-day synchronization is required and where each network device participates in the PTP protocol.

Because a boundary clock is used at every node in the chain between PTP Grandmaster and PTP Subordinate, there is reduction in time error accumulation through the network.

More About G.8275.1

The G.8275.1 must meet the following requirements:

• Non-participant devices, that is, devices that only forward PTP packets, and PTP transparent clocks are not allowed.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

121

PTP Domain

G.8275.1 Telecom Profile

• The telecom grandmaster (T-GM) provides timing to all other devices on the network. It does not synchronize its local clock with any other network element other than the Primary Reference Time Clock

(PRTC).

• The telecom time subordinate clock (T-TSC) synchronizes its local clock to another PTP clock (in most cases, the T-BC), and does not provide synchronization through PTP to any other device.

• The telecom boundary clock (T-BC) synchronizes its local clock to a T-GM or an upstream T-BC, and provides timing information to downstream T-BCs or T-TSCs. If at a given point in time there are no higher-quality clocks available to a T-BC to synchronize to, it may act as a grandmaster.

The following figure describes a sample G.8275.1 topology.

Figure 4: A Sample G.8275.1 Topology

PTP Domain

A PTP domain is a logical grouping of clocks that communicate with each other using the PTP protocol.

A single computer network can have multiple PTP domains operating separately, for example, one set of clocks synchronized to one time scale and another set of clocks synchronized to another time scale. PTP can run over either Ethernet or IP, so a domain can correspond to a local area network or it can extend across a wide area network.

The allowed domain numbers of PTP domains within a G.8275.1 network are between 24 and 43 (both inclusive).

PTP Messages and Transport

The following PTP transport parameters are defined:

• For transmitting PTP packets, either the forwardable multicast MAC address (01-1B-19-00-00-00) or the non-forwardable multicast MAC address (01-80-C2-00-00-0E) must be used as the destination MAC address. The MAC address in use is selected on a per-port basis through the configuration. However, the non-forwardable multicast MAC address (01-80-C2-00-00-0E) will be used if no destination MAC is configured.

The source MAC address is the interface MAC address.

• For receiving PTP packets, both multicast MAC addresses (01-80-C2-00-00-0E and 01-1B-19-00-00-00) are supported.

• The packet rate for Announce messages is 8 packets-per-second. For Sync, Delay-Req, and Delay-Resp messages, the rate is 16 packets-per-second.

• Signaling and management messages are not used.

122

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

G.8275.1 Telecom Profile

PTP Modes

PTP Modes

Two-Way Operation

To transport phase and time synchronization and to measure propagation delay, PTP operation must be two-way in this profile. Therefore, only two-way operation is allowed in this profile.

One-Step and Two-Step Clock Mode

Both one-step and two-step clock modes are supported in the G.8275.1 profile.

A client port must be capable of receiving and processing messages from both one-step clocks and two-step clocks, without any particular configuration. However, the server clock supports only one-step mode.

PTP Clocks

Two types of ordinary clocks and boundary clocks are used in this profile:

Ordinary Clock (OC)

• OC that can only be a grandmaster clock (T-GM). In this case, one PTP port will be used as a server port.

The T-GM uses the frequency, 1PPS, and ToD input from an upstream grandmaster clock.

Note The T-GM server port is a fixed server port.

Figure 5: Ordinary Clock As T-GM

• OC that can only be a subordinate/client clock (T-TSC). In this case, only one PTP port is used for T-TSC, which in turn will have only one PTP server associated with it.

Figure 6: Ordinary Clock As Subordinate/Client Clock (T-TSC)

Boundary Clock (T-BC)

1.

T-BC that can only be a grandmaster clock (T-GM).

2.

T-BC that can become a server clock and can also be a client clock to another PTP clock.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

123

PTP Ports

G.8275.1 Telecom Profile

If the BMCA selects a port on the T-BC to be a client port, all other ports are moved into the server role or a passive state.

Figure 7: Boundary Clock

PTP Ports

A port can be configured to perform either fixed primary or subordinate role or can be configured to change its role dynamically. If no role is assigned to a port, it can dynamically assume a primary, passive, or subordinate role based on the BMCA.

A primary port provides the clock to its downstream peers.

A subordinate port receives clock from an upstream peer.

A dynamic port can work either as a primary or a subordinate based on the BMCA decision.

In Cisco’s implementation of the G.8275.1:

• OC clocks can support only fixed primary or subordinate port.

• One PTP port can communicate with only one PTP peer.

• BC can have a maximum of 64 ports. Fixed subordinate ports are not supported on the BC.

Virtual Port Support on T-BC

G.8275.1 introduces the concept of a virtual port on the T-BC. A virtual port is an external frequency, phase and time input interface on a T-BC, which can participate in the source selection.

Alternate BMCA

The BMCA implementation in G.8275.1 is different from that in the default PTP profile. The G.8275.1

implementation is called the Alternate BMCA. Each device uses the alternate BMCA to select a clock to synchronize to, and to decide the port states of its local ports.

124

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

G.8275.1 Telecom Profile

Benefits

Benefits

With upcoming technologies like LTE-TDD, LTE-A CoMP, LTE-MBSFN and Location-based services, eNodeBs (base station devices) are required to be accurately synchronized in phase and time. Having GNSS systems at each node is not only expensive, but also introduces vulnerabilities. The G.8275.1 profile meets the synchronization requirements of these new technologies.

Prerequisites for Using the G.8275.1 Profile

• PTP over Multicast Ethernet must be used.

• Every node in the network must be PTP aware.

• It is mandatory to have a stable physical layer frequency whilst using PTP to define the phase.

• Multiple active grandmasters are recommended for redundancy.

Restrictions for Using the G.8275.1 Profile

• PTP Transparent clocks are not permitted in this profile.

• Changing PTP profile under an existing clock configuration is not allowed. Different ports under the same clock cannot have different profiles. You must remove clock configuration before changing the

PTP profile. Only removing all the ports under a clock is not sufficient.

• One PTP port is associated with only one physical port in this profile.

• There is no support for BDI and VLAN.

• Signaling and management messages are not used.

• PTP message rates are not configurable.

• Non-hybrid T-TSC and T-BC clock configurations are not supported.

Configuring the G.8275.1 Profile

Note To know more about the commands referenced in this module, see the Cisco IOS Interface and Hardware

Component Command Reference or the Cisco IOS Master Command List .

Configuring Physical Frequency Source

For more information, see the Configuring Synchronous Ethernet ESMC and SSM section in the Clocking and Timing chapter of this book.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

125

G.8275.1 Telecom Profile

Creating a Server-Only Ordinary Clock

Creating a Server-Only Ordinary Clock

ptp clock ordinary domain 24 local-priority 1 priority2 128 clock-port server-port-1 master profile g8275.1

local-priority 1 transport ethernet multicast interface Gig 0/0/1 clock-port server-port-2 master profile g8275.1

Note It is mandatory that when electrical ToD is used, the utc-offset command is configured before configuring the tod R0 , otherwise there will be a time difference of approximately 37 seconds between the server and client clocks.

The following example shows that the utc-offset is configured before configuring the ToD to avoid a delay of 37 seconds between the server and client clocks: ptp clock ordinary domain 0 utc-offset 37 tod R0 cisco input 1pps R0 clock-port server-port master transport ipv4 unicast interface Loopback0 negotiation

Associated Commands

• ptp clock

• local-priority

• priority2

Creating an Ordinary Slave

ptp clock ordinary domain 24 hybrid clock-port slave-port slave profile g8275.1

transport ethernet multicast interface Gig 0/0/0 delay-asymmetry 1000

Creating Dynamic Ports

Note Dynamic ports can be created when you do not specify whether a port is Server or Client. In such cases, the

BMCA dynamically choses the role of the port.

ptp clock boundary domain 24 hybrid time-properties persist 600

126

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

G.8275.1 Telecom Profile

Configuring Virtual Ports utc-offset 45 leap-second “01-01-2017 00:00:00” offset 1 clock-port bc-port-1 profile g8275.1

local-priority 1 transport ethernet multicast interface Gig 0/0/0 delay-asymmetry 500 clock-port bc-port-2 profile g8275.1

local-priority 2 transport ethernet multicast interface Gig 0/0/1 delay-asymmetry -800

Configuring Virtual Ports

ptp clock boundary domain 24 hybrid utc-offset 45 leap-second “01-01-2017 00:00:00” offset 1 virtual-port virtual-port-1 profile g8275.1 local-priority 1 input 1pps R0 input tod R0 ntp

Note It is mandatory that when electrical ToD is used, the utc-offset command is configured before configuring the tod R0 , otherwise there will be a time difference of approximately 37 seconds between the primary and subordinate clocks.

Restrictions for Configuring Virtual Ports

• Virtual port configuration is not allowed under Ordinary Clocks.

• Virtual port configuration is not supported under non-hybrid T-BC cases.

Associated Commands

• input

Verifying the Local Priority of the PTP Clock

Router# show ptp clock dataset default

CLOCK [Boundary Clock, domain 24]

Two Step Flag: No

Clock Identity: 0x2A:0:0:0:58:67:F3:4

Number Of Ports: 1

Priority1: 128

Priority2: 90

Local Priority: 200

Domain Number: 24

Slave Only: No

Clock Quality:

Class: 224

Accuracy: Unknown

Offset (log variance): 4252

Verifying the Port Parameters

Router# show ptp port dataset port

PORT [SERVER]

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

127

Verifying the Foreign Master Information

Clock Identity: 0x49:BD:D1:0:0:0:0:0

Port Number: 0

Port State: Unknown

Min Delay Req Interval (log base 2): 42

Peer Mean Path Delay: 648518346341351424

Announce interval (log base 2): 0

Announce Receipt Timeout: 2

Sync Interval (log base 2): 0

Delay Mechanism: End to End

Peer Delay Request Interval (log base 2): 0

PTP version: 2

Local Priority: 1

Not-slave: True

Verifying the Foreign Master Information

Router# show platform software ptp foreign-master domain 24

PTPd Foreign Master Information:

Current Master: SLA

Port: SLA

Clock Identity: 0x74:A2:E6:FF:FE:5D:CE:3F

Clock Stream Id: 0

Priority1: 128

Priority2: 128

Local Priority: 128

Clock Quality:

Class: 6

Accuracy: Within 100ns

Offset (Log Variance): 0x4E5D

Steps Removed: 1

Not-Slave: FALSE

Verifying Current PTP Time

Router# show platform software ptpd tod

PTPd ToD information:

Time: 01/05/70 06:40:59

Verifying the Virtual Port Status

Router# show ptp port virtual domain 24

VIRTUAL PORT [vp]

Status: down

Clock Identity: 0x74:A2:E6:FF:FE:5D:CE:3F

Port Number: 1

Clock Quality:

Class: 6

Accuracy: 0x21

Offset (log variance): 0x4E5D

Steps Removed: 0

Priority1: 128

Priority2: 128

Local Priority: 128

Not-slave: False

128

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

G.8275.1 Telecom Profile

G.8275.1 Telecom Profile

G.8275.1 Deployment Scenario

G.8275.1 Deployment Scenario

The following example illustrates a possible configuration for a G.8275.1 network with two server clocks, a boundary clock and a client. Let’s assume that server A is the main server and B is the backup server.

Figure 8: Topology for a Configuration Example

The configuration on server clock A is: ptp clock ordinary domain 24 clock-port server-port profile g8275.1

transport ethernet multicast interface GigabitEthernet 0/0/0

The configuration on server clock B is: ptp clock ordinary domain 25 clock-port server-port profile g8275.1

transport ethernet multicast interface GigabitEthernet 0/1/0

The configuration on the boundary clock is: ptp clock boundary domain 24 hybrid local-priority 3 clock-port client-port-a profile g8275.1 local-priority 1 transport ethernet multicast interface Gig 0/0/1 clock-port client-port-b profile g8275.1 local-priority 2 transport ethernet multicast interface Gig 0/1/1 clock-port server-port profile g8275.1

transport Ethernet multicast interface Gig 0/2/1

The configuration on the client clock is: ptp clock ordinary domain 24 hybrid clock-port client-port slave profile g8275.1

transport Ethernet multicast interface Gig 0/0/0

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

129

G.8275.1 Telecom Profile

Additional References

Additional References

Related Documents

Related Topic

Cisco IOS commands

Document Title

Cisco IOS Master Commands List, All Releases

Interface and Hardware Component commands Cisco IOS Interface and Hardware Component Command

Reference

Clocking and Timing Clocking and Timing

Standards

Standard Title

G.8275.1/Y.1369.1 (07/14) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS

AND NETWORKS

G.8273.2/Y.1368.2 (05/14)

Packet over Transport aspects – Synchronization, quality and availability targets

MIBs

MIB MIBs Link

— To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use

Cisco MIB Locator found at the following URL: http://www.cisco.com/go/mibs

RFCs

RFC Title

— There are no new RFCs for this feature.

Feature Information for G.8275.1

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco

Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn . An account on

Cisco.com is not required.

130

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

G.8275.1 Telecom Profile

Feature Information for G.8275.1

Note

Table 13: Feature Information for G.8275.1 , on page 131

lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

Table 13: Feature Information for G.8275.1

Feature Name Releases Feature Information

G.8275.1–Support for

1588 profile

XE 3.18

This PTP telecom profile introduces phase and time synchronization with full timing support from the network.

The following commands were introduced

• local-priority

The following commands were modified:

• clock-port

• show ptp clock dataset default

• show ptp port dataset port

The following command is deprecated for the G.8275.1 profile clocks:

• show ptp port running

The alternate command is show platform software ptp foreign-master

[domain-number].

Note This command is applicable only for the G.8275.1 profile clocks.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

131

Feature Information for G.8275.1

G.8275.1 Telecom Profile

132

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

C H A P T E R

8

Tracing and Trace Management

This chapter contains the following sections:

Tracing Overview, on page 133

How Tracing Works, on page 134

Tracing Levels, on page 134

Viewing a Tracing Level, on page 135

Setting a Tracing Level, on page 137

Viewing the Content of the Trace Buffer, on page 137

Tracing Overview

Tracing is a function that logs internal events. Trace files are automatically created and saved to the tracelogs directory on the harddisk: file system on the chassis, which stores tracing files in bootflash:. Trace files are used to store tracing data.

Note The logs in the bootflash are stored in compressed format with .gz file extension. Use the archiving tools such as gunzip, gzip, 7-zip to extract the files.

• If the sytem reloads unexpectedly, some of the files may not be in compressed format.

• Extraction of log files may lead to time hogs or CPU logs. We recommend to perform this by copying the files to the PC.

• Extraction of files cannot be performed at the IOS prompt.

• Log files not handled by the bootflash trace are not stored in the compressed format (for example, system_shell_R*.log ).

The contents of trace files are useful for the following purposes:

• Troubleshooting—If a chassis is having an issue, the trace file output may provide information that is useful for locating and solving the problem. Trace files can almost always be accessed through diagnostic mode even if other system issues are occurring.

• Debugging—The trace file outputs can help users get a more detailed view of system actions and operations.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

133

Tracing and Trace Management

How Tracing Works

How Tracing Works

The tracing function logs the contents of internal events on the chassis. Trace files with all trace output for a module are periodically created and updated and are stored in the tracelog directory. Trace files can be erased from this directory to recover space on the file system without impacting system performance.

The most recent trace information for a specific module can be viewed using the show platform software trace message privileged EXEC and diagnostic mode command. This command can be entered to gather trace log information even during an IOS failure because it is available in diagnostic mode.

Trace files can be copied to other destinations using most file transfer functions (such as FTP, TFTP, and so on) and opened using a plaintext editor.

Tracing cannot be disabled on the chassis. Trace levels, however, which set the message types that generate trace output, are user-configurable and can be set using the set platform software trace command. If a user wants to modify the trace level to increase or decrease the amount of trace message output, the user should set a new tracing level using the set platform software trace command. Trace levels can be set by process using the all-modules keyword within the set platform software trace command, or by module within a process. See the set platform software trace command reference for more information on this command, and the

Tracing Levels, on page 134

of this document for additional information on tracing levels.

Tracing Levels

Tracing levels determine how much information about a module should be stored in the trace buffer or file.

Table 14: Tracing Levels and Descriptions, on page 134

shows all of the trace levels that are available and provides descriptions of what types of messages are displayed with each tracing level.

Table 14: Tracing Levels and Descriptions

Trace Level

Emergency

Alert

Critical

Error

Warning

Notice

Informational 6

Debug

Verbose

7

8

3

4

1

2

Level Number Description

0 The message is regarding an issue that makes the system unusable.

The message is regarding an action that must be taken immediately.

The message is regarding a critical condition. This is the default setting.

The message is regarding a system error.

The message is regarding a system warning

5 The message is regarding a significant issue, but the router is still working normally.

The message is useful for informational purposes only.

The message provides debug-level output.

All possible tracing messages are sent.

134

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Tracing and Trace Management

Viewing a Tracing Level

Trace Level

Noise -

Level Number Description

All possible trace messages for the module are logged.

The noise level is always equal to the highest possible tracing level. Even if a future enhancement to tracing introduces a higher tracing level, the noise level will become equal to the level of that new enhancement.

Trace level settings are leveled, meaning that every setting will contain all messages from the lower setting plus the messages from its own setting. For instance, setting the trace level to 3(error) ensures that the trace file will contain all output for the 0 (emergencies), 1 (alerts), 2 (critical), and 3 (error) settings. Setting the trace level to 4 (warning) will ensure that all trace output for the specific module will be included in that trace file.

The default tracing level for every module on the chassis is notice.

All trace levels are not user-configurable. Specifically, the alert, critical, and notice tracing levels cannot be set by users. If you wish to trace these messages, set the trace level to a higher level that will collect these messages.

When setting trace levels, it is also important to remember that the setting is not done in a configuration mode, so trace level settings are returned to their defaults after every router reload.

Caution Setting tracing of a module to the debug level or higher can have a negative performance impact. Setting tracing to this level or higher should be done with discretion.

Caution Setting a large number of modules to high tracing levels can severely degrade performance. If a high level of tracing is needed in a specific context, it is almost always preferable to set a single module on a higher tracing level rather than setting multiple modules to high tracing levels.

Viewing a Tracing Level

By default, all modules on the chassis are set to notice. This setting will be maintained unless changed by a user.

To see the tracing level for any module on the chassis, enter the show platform software trace level command in privileged EXEC or diagnostic mode.

In the following example, the show platform software trace level command is used to view the tracing levels of the Forwarding Manager processes on the active RSP:

Router# show platform software trace level forwarding-manager rp active

Module Name Trace Level

----------------------------------------------acl Notice binos Notice binos/brand bipc bsignal btrace

Notice

Notice

Notice

Notice

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

135

Viewing a Tracing Level cce cdllib cef chasfs chasutil erspan ess ether-channel evlib evutil file_alloc fman_rp fpm fw icmp interfaces iosd ipc ipclog iphc ipsec mgmte-acl mlp mqipc nat nbar netflow om peer qos route-map sbc services sw_wdog tdl_acl_config_type tdl_acl_db_type tdl_cdlcore_message tdl_cef_config_common_type tdl_cef_config_type tdl_dpidb_config_type tdl_fman_rp_comm_type tdl_fman_rp_message tdl_fw_config_type tdl_hapi_tdl_type tdl_icmp_type tdl_ip_options_type tdl_ipc_ack_type tdl_ipsec_db_type tdl_mcp_comm_type tdl_mlp_config_type tdl_mlp_db_type tdl_om_type tdl_ui_message tdl_ui_type tdl_urpf_config_type tdllib trans_avl uihandler uipeer uistatus urpf vista wccp

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

Notice

136

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Tracing and Trace Management

Tracing and Trace Management

Setting a Tracing Level

Setting a Tracing Level

To set a tracing level for any module on the chassis, or for all modules within a process, enter the set platform software trace privileged EXEC and diagnostic mode command.

In the following example, the trace level for the ACL module in the Forwarding Manager of the ESP processor in slot 0 is set to info.

set platform software trace forwarding-manager F0 acl info

See the set platform software trace command reference for additional information about the options for this command.

Viewing the Content of the Trace Buffer

To view the trace messages in the trace buffer or file, enter the show platform software trace message privileged EXEC and diagnostic mode command.

In the following example, the trace messages for the Host Manager process in Route Switch Processor slot 0 are viewed using the show platform software trace message command:

Router# show platform software trace message host-manager R0

08/23 12:09:14.408 [uipeer]: (info): Looking for a ui_req msg

08/23 12:09:14.408 [uipeer]: (info): Start of request handling for con 0x100a61c8

08/23 12:09:14.399 [uipeer]: (info): Accepted connection for 14 as 0x100a61c8

08/23 12:09:14.399 [uipeer]: (info): Received new connection 0x100a61c8 on descriptor 14

08/23 12:09:14.398 [uipeer]: (info): Accepting command connection on listen fd 7

08/23 11:53:57.440 [uipeer]: (info): Going to send a status update to the shell manager in slot 0

08/23 11:53:47.417 [uipeer]: (info): Going to send a status update to the shell manager in slot 0

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

137

Viewing the Content of the Trace Buffer

Tracing and Trace Management

138

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

C H A P T E R

9

OTN Wrapper Overview

Optical Transport Network (OTN) Wrapper feature provides robust transport services that leverage many of the benefits such as resiliency and performance monitoring, while adding enhanced multi-rate capabilities in support of packet traffic, plus the transparency required by Dense Wavelength Division Multiplexing (DWDM) networks. OTN is the ideal technology to bridge the gap between next generation IP and legacy Time Division

Multiplexing (TDM) networks by acting as a converged transport layer for newer packet-based and existing

TDM services. OTN is defined in ITU G.709 and allows network operators to converge networks through seamless transport of the numerous types of legacy protocols, while providing the flexibility required to support future client protocols.

OTN Wrapper feature is supported on the following interface modules:

• 8-port 10 Gigabit Ethernet Interface Module (8x10GE) (A900-IMA8Z) (NCS4200-8T-PS) - The encapsulation type is OTU1e and OTU2e.

• 2-port 40 Gigabit Ethernet QSFP Interface Module (2x40GE) (A900-IMA2F) (NCS4200-2Q-P) - The encapsulation type is OTU3.

• 1-port 100 Gigabit Ethernet Interface Module (1X100GE) (NCS4200-1H-PK) (A900-IMA1C) - The encapsulation type is OTU4.

The chassis acts as an aggregator for ethernet, TDM, and SONET traffic to connect to an OTN network and vice versa. The ports on the interface modules are capable of OTN functionality. The OTN controller mode enables the IPoDWDM technology in the interface modules. The OTN Wrapper encapsulates 10G LAN, 40G

LAN, into the corresponding OTU1e or OTU2e, OTU3 containers, respectively. This enables the ports of the interface modules to work in layer 1 optical mode in conformance with standard G.709.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

139

OTN Wrapper Overview

Figure 9: OTN Signal Structure

OTN Frame

The key sections of the OTN frame are the Optical Channel Transport Unit (OTU) overhead section, Optical

Channel Data Unit (ODU) overhead section, Optical Channel Payload Unit (OPU) overhead section, OPU payload section, and Forward Error Correction (FEC) overhead section . The network routes these OTN frames across the network in a connection-oriented way. The Overhead carries the information required to identify, control and manage the payload, which maintains the deterministic quality. The Payload is simply the data transported across the network, while the FEC corrects errors when they arrive at the receiver. The number of correctable errors depends on the FEC type.

Advantages of OTN, on page 141

ODU and OTU, on page 141

OTU1e and OTU 2e Support on 8x10GE Interface Module, on page 141

Deriving OTU1e and OTU2e Rates, on page 142

OTU3 Support in 2x40GE Interface Module, on page 143

Supported Transceivers, on page 143

OTN Specific Functions, on page 143

Standard MIBS, on page 144

Restrictions for OTN, on page 144

DWDM Provisioning, on page 145

Configuring Transport Mode in 8x10GE and 2x40GE Interface Modules, on page 145

OTN Alarms, on page 148

OTN Threshold, on page 151

Configuring OTU Alerts, on page 153

Configuring ODU Alerts, on page 153

Configuring ODU Alerts, on page 153

Loopback, on page 155

Configuring Loopback, on page 155

SNMP Support, on page 159

Performance Monitoring, on page 160

Troubleshooting Scenarios, on page 167

Associated Commands, on page 167

140

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

OTN Wrapper Overview

Advantages of OTN

Advantages of OTN

The following are the advantages of OTN:

• Provides multi-layer performance monitoring and enhanced maintenance capability for signals traversing multi-operator networks.

• Allows Forward Error Correction (FEC) to improve the system performance.

• Provides enhanced alarm handling capability.

• Insulates the network against uncertain service mix by providing transparent native transport of signals encapsulating all client-management information.

• Performs multiplexing for optimum capacity utilization, thereby improving network efficiency.

• Enables network scalability as well as support for dedicated Ethernet services with service definitions.

ODU and OTU

Optical Channel Transport Unit (OTU) and Optical Channel Data Unit (ODU) are the two digital layer networks. All client signals are mapped into the optical channel via the ODU and OTU layer networks.

OTU

The OTU section is composed of two main sections: the Frame Alignment section and the Section Monitoring

(SM) section. The OTU Overhead (OH) provides the error detection correction as well as section-layer connection and monitoring functions on the section span. The OTU OH also includes framing bytes, enabling receivers to identify frame boundaries. For more information, see G.709 document .

ODU

The ODU section is an internal element allowing mapping or switching between different rates, which is important in allowing operators the ability to understand how the end user pipe is transferred through to the higher network rates. The ODU OH contains path overhead bytes allowing the ability to monitor the performance, fault type and location, generic communication, and six levels of channel protection based on

Tandem Connection Monitoring (TCM). For more information, see G.709 document .

OTU1e and OTU 2e Support on 8x10GE Interface Module

The OTU1e and OTU2e are mapping mechanisms to map a client 10G Base-R signal to OTN frames transparently as per ITU-T G series Supplement 43 specification. Both these modes are over-clocked OTN modes. These mechanisms provide real bit transparency of 10 GbE LAN signals and are useful for deployment of 10G services.

The OTU1e and OTU2e are inherently intra-domain interfaces (IaDI) and are generally applicable only to a single vendor island within an operator's network to enable the use of unique optical technology. The OTU1e and OTU2e are not standard G.709 bit-rate signals and they do not interwork with the standard mappings of

Ethernet using GFP-F. These two over-clocked mechanisms do not interwork with each other. As a result, such signals are only deployed in a point-to-point configuration between equipment that implements the same mapping.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

141

OTN Wrapper Overview

Deriving OTU1e and OTU2e Rates

The standard 10 GbE LAN has a data rate of 10.3125 Gbps. In the OTU1e and OTU2e mapping schemes, the full 10.3125 Gbit/s is transported including the 64B/66B coded information, IPG, MAC FCS, preamble, start-of-frame delimiter (SFD) and the ordered sets (to convey fault information). So, the effective OTU2e and OTU1e rates are:

• OTU1e: 11.0491 Gbits/s +/- 100ppm

• OTU2e: 11.0957 Gbits/s +/- 100ppm

The 10GBase-R client signal with fixed stuff bytes is accommodated into an OPU-like signal, then into an

ODU-like signal, and further into an OTU-like signal. These signals are denoted as OPU2e, ODU2e and

OTU2e, respectively . The OTU1e does not add 16 columns of fixed stuff bytes and hence overall data rate is relatively lesser at 11.0491 Gbps as compared to OTU2e which is 11.0957 Gbps.

The following table shows the standard OTU rates:

Table 15: Standard OTU Rates

G.709 Interface

OTU-1e

Line Rate Corresponding Ethernet

Rate

10 Gig E-LAN

Line Rate

10.3125 Gbit/s

OTU-2e

OTU-3

11.0491 Gbit/s without stuffing bits

11.0957 Gbit/s without stuffing bits

43.018 Gbit/s

10 Gig E-LAN

STM-256 or OC-768

10.3125 Gbit/s

39.813 Gbit/s

Deriving OTU1e and OTU2e Rates

A standard OTN frame consists of 255 16-column blocks and the payload rate is 9953280 Kbit/s. This is because the overhead and stuffing in the OTN frames happen at a granularity of 16-column blocks. Thus,

OPU payload occupies (3824-16)/16=238 blocks. The ODU occupies 239 blocks and the OTU (including

FEC) occupies 255 blocks. Hence, the multiplication factor in the G.709 spec is specified using numbers like

237, 238, 255.

Since OPU2e uses 16 columns that are reserved for stuffing and also for payload, the effective OPU2e frequency is:

• OPU2e = 238/237 x 10312500 Kbit/s = 10.356012 Gbit/s

• ODU2e = 239/237 x 10312500 Kbit/s = 10.399525 Gbit/s

• OTU2e = 255/237 x 10312500 Kbit/s = 11.095727 Gbit/s

Since OPU1e uses 16 columns that are reserved for stuffing and also for payload, the effective OPU1e frequency is:

• OPU1e = 238/238 x 10312500 Kbit/s = 10.3125 Gbit/s

• ODU1e = 239/238 x 10312500 Kbit/s = 10.355829 Gbit/s

• OTU1e = 255/238 x 10312500 Kbit/s = 11.049107 Gbit/s

142

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

OTN Wrapper Overview

OTU3 Support in 2x40GE Interface Module

OTU3 Support in 2x40GE Interface Module

When 40GbE LAN is transported over OTN, there is no drop in line rate when the LAN client is mapped into the OPU3 using the standard CBR40G mapping procedure as specified in G.709 clause 17.2.3. The 40G

Ethernet signal (41.25 Gbit/s) uses 64B/66B coding making it slightly larger than the OPU3 payload rate that is 40.15 Gbit/s. Hence, to transport 40G Ethernet service over ODU3, the 64B/66B blocks are transcoded into

1024B/1027B block code to reduce their size. The resulting 40.117 Gbit/s transcoded stream is then mapped in standard OPU3.

Supported Transceivers

The OTN wrapper feature works with the standard transceiver types that are supported for the LAN mode of

10G, 40G and 100G on the interface modules. The SFP-10G-LR-X, QSFP-40G-LR4, are used for 8x10GE,

2x40GE interface modules, respectively.

OTN Specific Functions

The following figure shows the OTN specific functions related to overhead processing, alarm handling, FEC and TTI:

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

143

Standard MIBS

Figure 10: OTN Specific Functions

OTN Wrapper Overview

Standard MIBS

The following are the standard MIBS:

• RFC2665

• RFC1213

• RFC2907

• RFC2233

• RFC3591

Restrictions for OTN

The following are the restrictions for OTN:

144

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

OTN Wrapper Overview

DWDM Provisioning

• OTL alarms are not supported.

• FECMISMATCH alarm is not supported.

• Enhanced FEC is not supported.

• Alarm and error counters are visible when the controller is in shutdown state.

DWDM Provisioning

All DWDM provisioning configurations take place on the controller. To configure a DWDM controller, use the controller dwdm command in global configuration mode.

Prerequisites for DWDM Provisioning

The g709 configuration commands can be used only when the controller is in the shutdown state. Use the no shutdown command after configuring the parameters, to remove the controller from shutdown state and to enable the controller to move to up state.

Configuring DWDM Provisioning

Use the following commands to configure DWDM provisioning: enable configure terminal

controller dwdm 0/1/0

Configuring Transport Mode in 8x10GE and 2x40GE Interface

Modules

Use the transport-mode command in interface configuration mode to configure LAN and OTN transport modes in 8x10GE and 2x40GE interface modules. The transport-mode command otn option has the bit-transparent sub-option, using which bit transparent mapping into OPU1e or OPU2e can be configured.

Use the following commands to configure LAN and OTN transport modes: enable configure terminal

controller dwdm 0/0/0

transport-mode otn bit-transparent opu1e

Note LAN transport mode is the default mode.

To configure the transport administration state on a DWDM port, use the admin-state command in DWDM configuration mode. To return the administration state from a DWDM port to the default, use the no form of this command.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

145

OTN Wrapper Overview

Verification of LAN Transport Mode Configuration

Verification of LAN Transport Mode Configuration

Use the show interfaces command to verify the configuration of LAN transport mode:

Router#sh int te0/1/0

TenGigabitEthernet0/1/0 is up, line protocol is up

MTU 1500 bytes, BW 10000000 Kbit/sec, DLY 10 usec, reliability 255/255, txload 8/255, rxload 193/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full Duplex, 10000Mbps, link type is force-up, media type is SFP-SR output flow-control is unsupported, input flow-control is on

Transport mode LAN

ARP type: ARPA, ARP Timeout 04:00:00

Last input 04:02:09, output 04:02:09, output hang never

Last clearing of "show interface" counters 00:29:47

Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 7605807000 bits/sec, 14854906 packets/sec

5 minute output rate 335510000 bits/sec, 655427 packets/sec

26571883351 packets input, 1700600465344 bytes, 0 no buffer

Received 0 broadcasts (0 IP multicasts)

0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog, 0 multicast, 0 pause input

10766634813 packets output, 689064271464 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 unknown protocol drops

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 0 pause output

0 output buffer failures, 0 output buffers swapped out

Router#

Verification of OTN Transport Mode Configuration in 8x10GE Interface Modules

Use the show interfaces command to verify the configuration of OTN transport mode in 8x10GE interface modules:

Router#sh int te0/1/1

TenGigabitEthernet0/1/1 is up, line protocol is up

MTU 1500 bytes, BW 10000000 Kbit/sec, DLY 10 usec, reliability 255/255, txload 193/255, rxload 7/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full Duplex, 10000Mbps, link type is force-up, media type is SFP-SR output flow-control is unsupported, input flow-control is on

Transport mode OTN (10GBASE-R over OPU1e w/o fixed stuffing, 11.0491Gb/s)

ARP type: ARPA, ARP Timeout 04:00:00

Last input 03:28:14, output 03:28:14, output hang never

Last clearing of "show interface" counters 00:30:47

Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 281326000 bits/sec, 549608 packets/sec

5 minute output rate 7596663000 bits/sec, 14837094 packets/sec

10766669034 packets input, 689066159324 bytes, 0 no buffer

Received 0 broadcasts (0 IP multicasts)

0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog, 0 multicast, 0 pause input

146

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

OTN Wrapper Overview

Verification of OTN Transport Mode Configuration in 2x40GE Interface Modules

27457291925 packets output, 1757266795328 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 unknown protocol drops

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 0 pause output

0 output buffer failures, 0 output buffers swapped out

Router#

Verification of OTN Transport Mode Configuration in 2x40GE Interface Modules

Use the show interfaces command to verify the configuration of OTN transport mode in 2x40GE interface modules:

Router#show int fo0/4/0

FortyGigabitEthernet0/4/0 is up, line protocol is up

MTU 1500 bytes, BW 40000000 Kbit/sec, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full Duplex, 40000Mbps, link type is force-up, media type is QSFP_40GE_SR output flow-control is unsupported, input flow-control is on

Transport mode OTN OTU3 (43.018Gb/s)

ARP type: ARPA, ARP Timeout 04:00:00

Last input never, output never, output hang never

Last clearing of "show interface" counters never

Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

0 packets input, 0 bytes, 0 no buffer

Received 0 broadcasts (0 IP multicasts)

0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog, 0 multicast, 0 pause input

0 packets output, 0 bytes, 0 underruns

0 output errors, 0 collisions, 2 interface resets

0 unknown protocol drops

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 0 pause output

0 output buffer failures, 0 output buffers swapped out

Changing from OTN to LAN Mode

Use the following methods to change from OTN mode to LAN mode:

• Use the following commands to make the transport mode as LAN mode: enable configure terminal

controller dwdm 0/0/0

transport-mode lan

• Use the following commands to set the controller default transport mode as LAN mode: enable configure terminal

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

147

OTN Wrapper Overview

Verification of Enabled Ports for Controller Configuration

controller dwdm 0/0/0 default transport-mode

Verification of Enabled Ports for Controller Configuration

Use the show controllers command to verify the enables ports for the controller configuration:

#show controllers

TenGigabitEthernet0/0/0

TenGigabitEthernet0/0/1

TenGigabitEthernet0/0/2

TenGigabitEthernet0/0/3

TenGigabitEthernet0/0/4

TenGigabitEthernet0/0/5

TenGigabitEthernet0/0/6

TenGigabitEthernet0/0/7

TenGigabitEthernet0/1/0

TenGigabitEthernet0/1/1

FortyGigabitEthernet0/4/0

FortyGigabitEthernet0/4/1

TenGigabitEthernet0/5/0

TenGigabitEthernet0/5/1

TenGigabitEthernet0/5/2

TenGigabitEthernet0/5/3

TenGigabitEthernet0/5/4

TenGigabitEthernet0/5/5

TenGigabitEthernet0/5/6

TenGigabitEthernet0/5/7

#

OTN Alarms

OTN supports alarms in each layer of encapsulation. All the alarms follow an alarm hierarchy and the highest level of alarm is asserted and presented as a Syslog message or on the CLI.

OTU Alarms

The types of alarms enabled for reporting:

• AIS - Alarm indication signal (AIS) alarms

• BDI - Backward defect indication (BDI) alarms

• IAE - Incoming alignment error (IAE) alarms

• LOF - Loss of frame (LOF) alarms

• LOM - Loss of multiple frames (LOM) alarms

• LOS - Loss of signal (LOS) alarms

• TIM - Type identifier mismatch (TIM) alarms

• SM - TCA - SM threshold crossing alert

• SD-BER - SM BER is in excess of the SD BER threshold

• SF-BER - SM BER is in excess of the SF BER threshold

148

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

OTN Wrapper Overview

Configuring OTN Alarm Reports

ODU Alarms

The types of alarms enabled for reporting:

• AIS - Alarm indication signal (AIS) alarms

• BDI - Backward defect indication (BDI) alarms

• LCK - Upstream connection locked (LCK) error status

• OCI - Open connection indication (OCI) error status

• PM-TCA - Performance monitoring (PM) threshold crossing alert (TCA)

• PTIM - Payload TIM error status

• SD-BER - SM BER is in excess of the SD BER threshold

• SF-BER - SM BER is in excess of the SF BER threshold

• TIM - Type identifier mismatch (TIM) alarms

Configuring OTN Alarm Reports

By default, all the OTN alarm reports are enabled. To control OTN alarm reports, disable all the alarms and enable the specific alarms.

Note You need to shutdown the interface using the shut command to configure the alarms.

Configuring OTU Alarm Reports

Use the following commands to configure OTU alarm reports: enable configure terminal

controller dwdm 0/4/1 shut

g709 otu report bdi no shut end

Note Fecmismatch is not supported.

Note Use no g709 otu report command to disable the OTU alarm reports.

Verification of OTU Alarm Reports Configuration

Use the show controllers command to verify OTU alarm reports configuration:

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

149

OTN Wrapper Overview

Verification of OTU Alarm Reports Configuration

#show controllers dwdm 0/4/1

G709 Information:

Controller dwdm 0/4/1, is up (no shutdown)

Transport mode OTN OTU3

Loopback mode enabled : None

TAS state is : IS

G709 status : Enabled

( Alarms and Errors )

OTU

LOS = 3

AIS = 0

TIM = 0

ODU

AIS = 0

OCI = 0

BIP = 2

FEC Mode: FEC

Remote FEC Mode: Unknown

FECM

EC(current second)

EC

UC

LOF = 1

BDI = 0

IAE = 0

BDI = 0

LCK = 0

BEI = 0

LOM = 0

BIP = 74444

BEI = 37032

TIM = 0

PTIM = 0

= 0

= 0

= 186

= 10695

Detected Alarms: NONE

Asserted Alarms: NONE

Detected Alerts: NONE

Asserted Alerts: NONE

Alarm reporting enabled for: LOS LOF LOM OTU-AIS OTU-IAE OTU-BDI ODU-AIS ODU-OCI ODU-LCK

ODU-BDI ODU-PTIM ODU-BIP

Alert reporting enabled for: OTU-SD-BER OTU-SF-BER OTU-SM-TCA ODU-SD-BER ODU-SF-BER ODU-PM-TCA

BER thresholds: ODU-SF = 10e-3 ODU-SD = 10e-6 OTU-SF = 10e-3 OTU-SD = 10e-6

TCA thresholds: SM = 10e-3 PM = 10e-3

OTU TTI Sent

OTU TTI Sent

String SAPI ASCII

String DAPI ASCII

: Tx TTI Not Configured

: Tx TTI Not Configured

OTU TTI Sent String OPERATOR ASCII : Tx TTI Not Configured

OTU TTI Expected String SAPI ASCII : Exp TTI Not Configured

OTU TTI Expected String DAPI ASCII : Exp TTI Not Configured

OTU TTI Expected String OPERATOR ASCII : Exp TTI Not Configured

OTU TTI Received String HEX : 0000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000

000000000000000000000000000000

ODU TTI Sent

ODU TTI Sent

String SAPI ASCII

String DAPI ASCII

: Tx TTI Not Configured

: Tx TTI Not Configured

ODU TTI Sent String OPERATOR ASCII : Tx TTI Not Configured

ODU TTI Expected String SAPI ASCII : Exp TTI Not Configured

ODU TTI Expected String DAPI ASCII : Exp TTI Not Configured

ODU TTI Expected String OPERATOR ASCII : Exp TTI Not Configured

ODU TTI Received String HEX : 0000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000

000000000000000000000000000000

150

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

OTN Wrapper Overview

Syslog Generation for LOS Alarm

Syslog Generation for LOS Alarm

The following example shows the syslog generation for LOS alarm:

(config-if)#

*Jan 16 06:32:50.487 IST: %DWDM-4-G709ALARM: dwdm-0/4/1: LOS declared

*Jan 16 06:32:51.048 IST: %LINK-3-UPDOWN: Interface FortyGigabitEthernet0/4/1, changed state to down

*Jan 16 06:32:51.489 IST: %DWDM-4-G709ALARM: dwdm-0/4/1: LOF declared

*Jan 16 06:32:51.495 IST: %DWDM-4-G709ALARM: dwdm-0/4/1: LOS cleared

Configuring ODU Alarm Report

Use the following commands to configure ODU alarm reports: enable configure terminal

controller dwdm 0/4/1 shut

g709 odu report ais no shut end

Note Use no g709 odu report command to disable the ODU alarm reports.

OTN Threshold

The signal degrade and signal failure thresholds are configured for alerts.

The following types of thresholds are configured for alerts for OTU and ODU layers:

• SD-BER—Section Monitoring (SM) bit error rate (BER) is in excess of the signal degradation (SD) BER threshold.

• SF-BER—SM BER is in excess of the signal failure (SF) BER threshold.

• PM-TCA—Performance monitoring (PM) threshold crossing alert (TCA).

• SM-TCA—SM threshold crossing alert.

Configuring OTU Threshold

To configure OTU threshold: enable configure terminal

controller dwdm 0/4/1 shut

g709 otu threshold sm-tca 3 no shut end

Note Use no g709 otu threshold command to disable OTU threshold.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

151

OTN Wrapper Overview

Configuring ODU Threshold

Configuring ODU Threshold

To configure ODU threshold: enable configure terminal

controller dwdm 0/4/1 shut

g709 odu threshold sd-ber 3 no shut end

Note Use no g709 odu threshold command to disable configuration of ODU threshold.

Verification of OTU and ODU Threshold Configuration

Use the show controllers command to verify OTU and ODU threshold configuration:

Router#show controllers dwdm 0/1/2

G709 Information:

Controller dwdm 0/1/2, is up (no shutdown)

Transport mode OTN (10GBASE-R over OPU1e w/o fixed stuffing, 11.0491Gb/s)

Loopback mode enabled : None

TAS state is : UNKNWN

G709 status : Enabled

OTU

LOS = 0

AIS = 0

TIM = 0

LOF = 0

BDI = 0

IAE = 0

LOM = 0

BIP = 0

BEI = 0

ODU

AIS = 0

OCI = 0

BIP = 0

FEC Mode: FEC

Remote FEC Mode: Unknown

FECM

EC(current second)

EC

UC

BDI = 0

LCK = 0

BEI = 0

= 0

= 0

= 0

= 0

TIM = 0

PTIM = 0

Detected Alarms: NONE

Asserted Alarms: NONE

Detected Alerts: NONE

Asserted Alerts: NONE

Alarm reporting enabled for: LOS LOF LOM OTU-AIS OTU-IAE OTU-BDI OTU-TIM ODU-AIS ODU-OCI

ODU-LCK ODU-BDI ODU-PTIM ODU-TIM ODU-BIP

Alert reporting enabled for: OTU-SD-BER OTU-SF-BER OTU-SM-TCA ODU-SD-BER ODU-SF-BER ODU-PM-TCA

BER thresholds: ODU-SF = 10e-3 ODU-SD = 10e-6 OTU-SF = 10e-3 OTU-SD = 10e-6

TCA thresholds: SM = 10e-3 PM = 10e-3

152

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

OTN Wrapper Overview

Configuring OTU Alerts

OTU TTI Sent

OTU TTI Sent

String SAPI ASCII

String DAPI ASCII

: AABBCCDD

: AABBCCDD

OTU TTI Sent String OPERATOR ASCII : AABBCCDD

OTU TTI Expected String SAPI ASCII : AABBCCDD

OTU TTI Expected String DAPI ASCII

OTU TTI Expected String OPERATOR HEX

: AABBCCDD

: AABBCCDD

OTU TTI Received String HEX : 0052414D4553480000000000000000000052414D455348000

0000000000000004141424243434444000000000000000000

000000000000000000000000000000

ODU TTI Sent

ODU TTI Sent

String SAPI ASCII

String DAPI ASCII

ODU TTI Sent String OPERATOR HEX

ODU TTI Expected String SAPI ASCII

: AABBCCDD

: AABBCCDD

: 11223344

: AABBCCDD

ODU TTI Expected String DAPI ASCII

ODU TTI Expected String OPERATOR HEX

: AABBCCDD

: 11223344

ODU TTI Received String HEX : 0052414D4553480000000000000000000052414D455348000

0000000000000001122334400000000000000000000000000

000000000000000000000000000000

Router#

Configuring OTU Alerts

To configure OTU alerts: enable configure terminal

controller dwdm 0/4/1 shutdown

g709 otu

g709 otu threshold

g709 otu threshold sd-ber no shutdown end

Configuring ODU Alerts

To configure ODU alerts: enable configure terminal

controller dwdm 0/4/1 shutdown

g709 otu

g709 otu threshold

g709 otu threshold pm-tca no shutdown end

Configuring ODU Alerts

To configure ODU alerts: enable configure terminal

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

153

OTN Wrapper Overview

Verifying Alerts Configuration

controller dwdm 0/4/1 shutdown

g709 otu

g709 otu threshold

g709 otu threshold pm-tca no shutdown end

Verifying Alerts Configuration

Use the show controllers command to verify the alerts configuration:

#show controllers dwdm 0/4/1

G709 Information:

Controller dwdm 0/4/1, is down (shutdown)

Transport mode OTN OTU3

Loopback mode enabled : Line

TAS state is : IS

G709 status : Enabled

OTU

LOS = 5

AIS = 0

TIM = 0

LOF = 1

BDI = 0

IAE = 0

ODU

AIS = 0

OCI = 0

BIP = 2

FEC Mode: FEC

Remote FEC Mode: Unknown

FECM

EC(current second)

EC

UC

BDI = 0

LCK = 0

BEI = 0

LOM = 0

BIP = 149549

BEI = 74685

TIM = 0

PTIM = 0

= 0

= 0

= 856

= 23165

Detected Alarms: NONE

Asserted Alarms: NONE

Detected Alerts: NONE

Asserted Alerts: NONE

Alarm reporting enabled for: LOS LOF LOM OTU-AIS OTU-IAE OTU-BDI ODU-AIS ODU-OCI ODU-LCK

ODU-BDI ODU-PTIM ODU-BIP

Alert reporting enabled for: OTU-SD-BER OTU-SF-BER OTU-SM-TCA ODU-SD-BER ODU-SF-BER ODU-PM-TCA

BER thresholds: ODU-SF = 10e-3 ODU-SD = 10e-6 OTU-SF = 10e-3 OTU-SD = 10e-5

TCA thresholds: SM = 10e-3 PM = 10e-4

OTU TTI Sent

OTU TTI Sent

String SAPI ASCII

String DAPI ASCII

: Tx TTI Not Configured

: Tx TTI Not Configured

OTU TTI Sent String OPERATOR ASCII : Tx TTI Not Configured

OTU TTI Expected String SAPI ASCII : Exp TTI Not Configured

OTU TTI Expected String DAPI ASCII : Exp TTI Not Configured

OTU TTI Expected String OPERATOR ASCII : Exp TTI Not Configured

OTU TTI Received String HEX : 0000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000

000000000000000000000000000000

154

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

OTN Wrapper Overview

Loopback

ODU TTI Sent

ODU TTI Sent

ODU TTI Sent

String SAPI ASCII

String DAPI ASCII

: Tx TTI Not Configured

: Tx TTI Not Configured

String OPERATOR ASCII : Tx TTI Not Configured

ODU TTI Expected String SAPI ASCII

ODU TTI Expected String DAPI ASCII

: Exp TTI Not Configured

: Exp TTI Not Configured

ODU TTI Expected String OPERATOR ASCII : Exp TTI Not Configured

ODU TTI Received String HEX : 0000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000

000000000000000000000000000000

Loopback

Loopback provides a means for remotely testing the throughput of an Ethernet port on the router. You can verify the maximum rate of frame transmission with no frame loss. Two types of loopback is supported:

• Internal Loopback - All packets are looped back internally within the router before reaching an external cable. It tests the internal Rx to Tx path and stops the traffic to egress out from the Physical port.

• Line Loopback - Incoming network packets are looped back through the external cable.

Configuring Loopback

To configure loopback: enable configure terminal

controller dwdm 0/4/1 shutdown

loopback line no shutdown end

Forward Error Connection

Forward error correction (FEC) is a method of obtaining error control in data transmission in which the source

(transmitter) sends redundant data and the destination (receiver) recognizes only the portion of the data that contains no apparent errors. FEC groups source packets into blocks and applies protection to generate a desired number of repair packets. These repair packets may be sent on demand or independently of any receiver feedback.

Standard FEC is supported on 8x10GE and 2x40GE interface modules.

The packets that can be corrected by FEC are known as Error Corrected Packets. The packets that cannot be corrected by FEC due to enhanced bit errors are known as Uncorrected Packets.

Benefits of FEC

The following are the benefits of FEC:

• FEC reduces the number of transmission errors, extends the operating range, and reduces the power requirements for communications systems.

• FEC increases the effective systems throughput.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

155

OTN Wrapper Overview

Configuring FEC

• FEC supports correction of bit errors occurring due to impairments in the transmission medium.

Configuring FEC

To configure FEC: enable configure terminal

controller dwdm 0/4/1 shutdown g709 fec standard no shutdown end

Verifying FEC Configuration

Use the show controllers command to verify FEC configuration:

G709 Information:

Controller dwdm 0/4/1, is up (no shutdown)

Transport mode OTN OTU3

Loopback mode enabled : Line

TAS state is : IS

G709 status : Enabled

OTU

LOS = 5

AIS = 0

TIM = 0

LOF = 1

BDI = 0

IAE = 0

LOM = 0

BIP = 149549

BEI = 74685

ODU

AIS = 0

OCI = 0

BIP = 2

BDI = 0

LCK = 0

BEI = 0

TIM = 0

PTIM = 0

FEC Mode: FEC

Remote FEC Mode: Unknown <— This is a limitation by which we do not show the remote FEC mode

FECM = 0

EC(current second)

EC corrected bits .

UC alarms .

= 0

= 856

= 23165

< — This is the counter for Error

<- this is the counter for Uncorrected

Detected Alarms: NONE

Asserted Alarms: NONE

Detected Alerts: NONE

Asserted Alerts: NONE

Alarm reporting enabled for: LOS LOF LOM OTU-AIS OTU-IAE OTU-BDI ODU-AIS ODU-OCI ODU-LCK

ODU-BDI ODU-PTIM ODU-BIP

Alert reporting enabled for: OTU-SD-BER OTU-SF-BER OTU-SM-TCA ODU-SD-BER ODU-SF-BER ODU-PM-TCA

BER thresholds: ODU-SF = 10e-3 ODU-SD = 10e-6 OTU-SF = 10e-3 OTU-SD = 10e-5

TCA thresholds: SM = 10e-3 PM = 10e-4

OTU TTI Sent String SAPI ASCII : Tx TTI Not Configured

156

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

OTN Wrapper Overview

Trail Trace Identifier

OTU TTI Sent

OTU TTI Sent

String DAPI ASCII : Tx TTI Not Configured

String OPERATOR ASCII : Tx TTI Not Configured

OTU TTI Expected String SAPI ASCII

OTU TTI Expected String DAPI ASCII

: Exp TTI Not Configured

: Exp TTI Not Configured

OTU TTI Expected String OPERATOR ASCII : Exp TTI Not Configured

OTU TTI Received String HEX : 0000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000

000000000000000000000000000000

ODU TTI Sent

ODU TTI Sent

ODU TTI Sent

String SAPI ASCII

String DAPI ASCII

ODU TTI Expected String SAPI ASCII

ODU TTI Expected String DAPI ASCII

: Tx TTI Not Configured

: Tx TTI Not Configured

String OPERATOR ASCII : Tx TTI Not Configured

: Exp TTI Not Configured

: Exp TTI Not Configured

ODU TTI Expected String OPERATOR ASCII : Exp TTI Not Configured

ODU TTI Received String HEX : 0000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000

Trail Trace Identifier

The Trail Trace Identifier (TTI) is a 64-Byte signal that occupies one byte of the frame and is aligned with the OTUk multiframe. It is transmitted four times per multiframe. TTI is defined as a 64-byte string with the following structure:

• TTI [0] contains the Source Access Point Identifier (SAPI) [0] character, which is fixed to all-0s.

• TTI [1] to TTI [15] contain the 15-character source access point identifier (SAPI[1] to SAPI[15]).

• TTI [16] contains the Destination Access Point Identifier (DAPI) [0] character, which is fixed to all-0s.

• TTI [17] to TTI [31] contain the 15-character destination access point identifier (DAPI [1] to DAPI [15]).

• TTI [32] to TTI [63] are operator specific.

TTI Mismatch

TTI mismatch occurs when you have enabled path trace and the "received string" is different from the "expected string". This alarm condition stops traffic.

When TTI mismatch occurs, the interface is brought to down state. This is only supported for SAPI and DAPI and is not supported for User Operator Data field.

Configuring TTI

To configure TTI: enable configure terminal

controller dwdm 0/1/1 shutdown

g709 tti-processing enable no shutdown end

Trace Identifier Mismatch (TIM) is reported in the Detected Alarms where there is a mismatch in the expected and received string. Action on detection of TIM can be configured in ODU and OTU layers as follows: enable configure terminal

controller dwdm 0/1/1 shutdown

g709 tti-processing enable otu

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

157

OTN Wrapper Overview

Configuring TTI for SAPI DAPI Operator Specific Fields no shutdown end

Configuring TTI for SAPI DAPI Operator Specific Fields

To configure TTI SAPI, DAPI, and operator specific fields for OTU and ODU layers: enable configure terminal

controller dwdm 0/1/1

g709 fec standard

g709 otu overhead tti sent ascii sapi AABBCCDD end

Verification of TTI SAPI DAPI Operator Specific Fields Configuration

Use the show controller command to verify TTI SAPI, DAPI, Operator Specific fields configuration:

Router#show controllers dwdm 0/1/1

G709 Information:

Controller dwdm 0/1/1, is up (no shutdown)

Transport mode OTN (10GBASE-R over OPU1e w/o fixed stuffing, 11.0491Gb/s)

<<truncated other output >>

OTU TTI Sent String SAPI ASCII : AABBCCDD

OTU TTI Sent String DAPI ASCII : AABBCCDD

OTU TTI Sent String OPERATOR ASCII : AABBCCDD

OTU TTI Expected String SAPI ASCII : AABBCCDD

OTU TTI Expected String DAPI ASCII : AABBCCDD

OTU TTI Expected String OPERATOR HEX : AABBCCDD

OTU TTI Received String HEX : 0052414D4553480000000000000000000052414D455348000

0000000000000004141424243434444000000000000000000

000000000000000000000000000000

ODU TTI Sent String SAPI ASCII : AABBCCDD

ODU TTI Sent String DAPI ASCII : AABBCCDD

ODU TTI Sent String OPERATOR HEX : 11223344

ODU TTI Expected String SAPI ASCII : AABBCCDD

Verifying Loopback Configuration

Use the show controllers command to verify the loopback configuration:

#show controllers dwdm 0/4/1

G709 Information:

Controller dwdm 0/4/1, is up (no shutdown)

Transport mode OTN OTU3

Loopback mode enabled : Line

TAS state is : IS

G709 status : Enabled

OTU

LOS = 5

AIS = 0

TIM = 0

ODU

LOF = 1

BDI = 0

IAE = 0

AIS = 0 BDI = 0

LOM = 0

BIP = 149549

BEI = 74685

TIM = 0

158

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

OTN Wrapper Overview

SNMP Support

OCI = 0

BIP = 2

FEC Mode: FEC

Remote FEC Mode: Unknown

FECM

EC(current second)

EC

UC

LCK = 0

BEI = 0

PTIM = 0

= 0

= 0

= 856

= 23165

Detected Alarms: NONE

Asserted Alarms: NONE

Detected Alerts: NONE

Asserted Alerts: NONE

Alarm reporting enabled for: LOS LOF LOM OTU-AIS OTU-IAE OTU-BDI ODU-AIS ODU-OCI ODU-LCK

ODU-BDI ODU-PTIM ODU-BIP

Alert reporting enabled for: OTU-SD-BER OTU-SF-BER OTU-SM-TCA ODU-SD-BER ODU-SF-BER ODU-PM-TCA

BER thresholds: ODU-SF = 10e-3 ODU-SD = 10e-6 OTU-SF = 10e-3 OTU-SD = 10e-4

TCA thresholds: SM = 10e-3 PM = 10e-3

OTU TTI Sent

OTU TTI Sent

String SAPI ASCII

String DAPI ASCII

: Tx TTI Not Configured

: Tx TTI Not Configured

OTU TTI Sent String OPERATOR ASCII : Tx TTI Not Configured

OTU TTI Expected String SAPI ASCII : Exp TTI Not Configured

OTU TTI Expected String DAPI ASCII : Exp TTI Not Configured

OTU TTI Expected String OPERATOR ASCII : Exp TTI Not Configured

OTU TTI Received String HEX : 0000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000

000000000000000000000000000000

ODU TTI Sent

ODU TTI Sent

String SAPI ASCII

String DAPI ASCII

: Tx TTI Not Configured

: Tx TTI Not Configured

ODU TTI Sent String OPERATOR ASCII : Tx TTI Not Configured

ODU TTI Expected String SAPI ASCII : Exp TTI Not Configured

ODU TTI Expected String DAPI ASCII : Exp TTI Not Configured

ODU TTI Expected String OPERATOR ASCII : Exp TTI Not Configured

ODU TTI Received String HEX : 0000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000

000000000000000000000000000000

#

SNMP Support

Simple Network Management Protocol (SNMP) is an application-layer protocol that provides a message format for communication between SNMP managers and agents. SNMP provides a standardized framework and a common language that is used for monitoring and managing devices in a network.

SNMP sets are not supported for the following tables:

• coiIfControllerTable

• coiOtnNearEndThresholdsTable

• coiOtnFarEndThresholdsTable

• coiFECThresholdsTable

Refer to CISCO-OTN-IF-MIB and SNMP Configuration Guide for SNMP support.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

159

OTN Wrapper Overview

Performance Monitoring

Performance Monitoring

Performance monitoring (PM) parameters are used by service providers to gather, store, set thresholds for, and report performance data for early detection of problems. Thresholds are used to set error levels for each

PM parameter. During the accumulation cycle, if the current value of a performance monitoring parameter reaches or exceeds its corresponding threshold value, a threshold crossing alert (TCA) is generated. The TCAs provide early detection of performance degradation. PM statistics are accumulated on a 15-minute basis, synchronized to the start of each quarter-hour. Historical counts are maintained for 33 15-minutes intervals and 2 daily intervals. PM parameters are collected for OTN and FEC.

Calculation and accumulation of the performance-monitoring data is in 15-minute and 24-hour intervals.

PM parameters require the errored ratio to be less than the standard reference that is dependent on the encapsulation. If any loss or error event does not happen within a second, it is called an error free second. If some error in transmission or alarm happens in a second, the second is called Errored Second. The error is termed as Errored Second or Severely Errored Second or Unavailable Second depending upon the nature of error. The error calculation depends on the Errored Blocks. Errored second is a second where one BIP error or BEI error occurs. Severely Errored Second occurs when the errored frames crosses a threshold or there is an alarm is generated. Unavaliable Second occurs when there are 10 consecutive severely errored seconds.

Figure 11: Performance Monitoring

PM occurs in near end and far end for both encapsulations for ODUk and OTUk. ODU is referred as Path

Monitoring (PM) and OTU is referred to as Section Monitoring (SM).

The following table shows the details of each type of PM parameter for OTN:

Table 16: PM Parameters for OTN

Parameter

BBE-PM

BBE-SM

Definition

Path Monitoring Background Block Errors (BBE-PM) indicates the number of background block errors recorded in the optical transport network (OTN) path during the PM time interval.

Section Monitoring Background Block Errors

(BBE-SM) indicates the number of background block errors recorded in the OTN section during the PM time interval.

160

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

OTN Wrapper Overview

Parameter

BBER-PM

BBER-SM

FC-PM

FC-SM

SES-PM

SES-SM

ES-PM

ESR-PM

ESR-SM

ES-SM

SESR-PM

Performance Monitoring

Definition

Path Monitoring Background Block Errors Ratio

(BBER-PM) indicates the background block errors ratio recorded in the OTN path during the PM time interval.

Section Monitoring Background Block Errors Ratio

(BBER-SM) indicates the background block errors ratio recorded in the OTN section during the PM time interval.

Path Monitoring Errored Seconds (ES-PM) indicates the errored seconds recorded in the OTN path during the PM time interval.

Path Monitoring Errored Seconds Ratio (ESR-PM) indicates the errored seconds ratio recorded in the

OTN path during the PM time interval.

Section Monitoring Errored Seconds Ratio (ESR-SM) indicates the errored seconds ratio recorded in the

OTN section during the PM time interval.

Section Monitoring Errored Seconds (ES-SM) indicates the errored seconds recorded in the OTN section during the PM time interval.

Path Monitoring Failure Counts (FC-PM) indicates the failure counts recorded in the OTN path during the PM time interval.

Section Monitoring Failure Counts (FC-SM) indicates the failure counts recorded in the OTN section during the PM time interval.

Path Monitoring Severely Errored Seconds (SES-PM) indicates the severely errored seconds recorded in the

OTN path during the PM time interval.

Section Monitoring Severely Errored Seconds

(SES-SM) indicates the severely errored seconds recorded in the OTN section during the PM time interval.

Path Monitoring Severely Errored Seconds Ratio

(SESR-PM) indicates the severely errored seconds ratio recorded in the OTN path during the PM time interval.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

161

OTN Wrapper Overview

OTUk Section Monitoring

Parameter

SESR-SM

UAS-PM

UAS-SM

Definition

Section Monitoring Severely Errored Seconds Ratio

(SESR-SM) indicates the severely errored seconds ratio recorded in the OTN section during the PM time interval.

Path Monitoring Unavailable Seconds (UAS-PM) indicates the unavailable seconds recorded in the OTN path during the PM time interval.

Section Monitoring Unavailable Seconds (UAS-SM) indicates the unavailable seconds recorded in the OTN section during the PM time interval.

The following table shows the details of each type of PM parameter for FEC:

Table 17: PM Parameters for FEC

Parameter

EC

UC-WORDS

Definition

Bit Errors Corrected (BIEC) indicated the number of bit errors corrected in the DWDM trunk line during the PM time interval.

Uncorrectable Words (UC-WORDS) is the number of uncorrectable words detected in the DWDM trunk line during the PM time interval.

OTUk Section Monitoring

Section Monitoring (SM) overhead for OTUk is terminated as follows:

• TTI

• BIP

• BEI

• BDI

• IAE

• BIAE

BIP and BEI counters are block error counters (block size equal to OTUk frame size). The counters can be read periodically by a PM thread to derive one second performance counts. They are sufficiently wide for software to identify a wrap-around with up to 1.5 sec between successive readings.

The following OTUk level defects are detected:

• dAIS

• dTIM

• dBDI

162

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

OTN Wrapper Overview

ODUk Path Monitoring

• dIAE

• dBIAE

Status of the defects is available through CPU readable registers, and a change of status of dLOF, dLOM, and dAIS will generate an interruption.

ODUk Path Monitoring

Path Monitoring (PM) overhead for higher order ODUk and lower order ODUk is processed as follows:

• TTI

• BIP

• BEI

• BDI

• STAT including ODU LCK/OCI/AIS

The following ODUk defects are detected:

• dTIM

• dLCK and dAIS (from STAT field)

• dBDI

LOS, OTU LOF, OOF and ODU-AIS alarms bring down the interface in system.

Configuring PM Parameters for FEC

To set TCA report status on FEC layer in 15-minute interval: enable configure terminal

controller dwdm 0/1/0

pm 15-min fec report ec-bits enable

pm 15-min fec report uc-words enable end

To set TCA report status on FEC layer in 24-hour interval: enable configure terminal

controller dwdm 0/1/0

pm 24-hr fec report ec-bits enable

pm 24-hr fec report uc-words enable end

To set threshold on FEC layer in 15-minute interval: enable configure terminal

controller dwdm 0/1/0

pm 15-min fec threshold ec-bits

pm 15-min fec threshold uc-words end

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

163

OTN Wrapper Overview

Configuring PM Parameters for OTN

To set threshold on FEC layer in 24-hour interval: enable configure terminal

controller dwdm 0/1/0

pm 24-hr fec threshold ec-bits

pm 24-hr fec threshold uc-words end

Configuring PM Parameters for OTN

To set OTN report status in 15-minute interval: enable configure terminal

controller dwdm 0/1/0

pm 15-min otn report es-pm-ne enable end

To set OTN report status in 24-hour interval: enable configure terminal controller dwdm slot/bay/port

pm 24-hr otn report es-pm-ne enable end

To set OTN threshold in 15-minute interval: enable configure terminal

controller dwdm 0/1/0

pm 15-min otn threshold es-pm-ne end

To set OTN threshold in 24-hour interval: enable configure terminal

controller dwdm 0/1/0

pm 24-hr otn threshold es-pm-ne end

Verifying PM Parameters Configuration

Use the show controllers command to verify PM parameters configuration for FEC in 15-minute interval:

Router#show controllers dwdm 0/1/0 pm interval 15-min fec 0 g709 FEC in the current interval [9 :15:00 - 09:16:40 Thu Jun 9 2016]

FEC current bucket type : INVALID

EC-BITS : 0 Threshold :

UC-WORDS : 0 Threshold :

200 TCA(enable) : YES

23 TCA(enable) : YES

Router#show controllers dwdm 0/1/0 pm interval 15-min fec 1 g709 FEC in interval 1 [9 :00:00 - 9 :15:00 Thu Jun 9 2016]

FEC current bucket type : VALID

EC-BITS : 0 UC-WORDS : 0

Use the show controllers command to verify PM parameters configuration for FEC in 24-hour interval:

164

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

OTN Wrapper Overview

Verifying PM Parameters Configuration

Router#show controllers dwdm 0/1/0 pm interval 24 fec 0 g709 FEC in the current interval [00:00:00 - 09:17:01 Thu Jun 9 2016]

FEC current bucket type : INVALID

EC-BITS :

UC-WORDS :

0

0

Threshold :

Threshold :

0

0

TCA(enable)

TCA(enable)

: NO

: NO

Router#show controllers dwdm 0/1/0 pm interval 24 fec 1 g709 FEC in interval 1 [00:00:00 - 24:00:00 Wed Jun 8 2016]

FEC current bucket type : VALID

EC-BITS : 717 UC-WORDS : 1188574

Use the show controllers command to verify PM parameters configuration for OTN in 15-minute interval:

Router#show controllers dwdm 0/1/0 pm interval 15-min otn 0 g709 OTN in the current interval [9 :15:00 - 09:15:51 Thu Jun 9 2016]

OTN current bucket type: INVALID

OTN Near-End Valid : YES

ES-SM-NE : 0

ESR-SM-NE : 0.00000

SES-SM-NE : 0

SESR-SM-NE : 0.00000

UAS-SM-NE :

BBE-SM-NE :

BBER-SM-NE : 0.00000

0

0

FC-SM-NE

ES-PM-NE

:

:

0

0

ESR-PM-NE : 0.00000

SES-PM-NE : 0

SESR-PM-NE : 0.00000

UAS-PM-NE :

BBE-PM-NE :

BBER-PM-NE : 0.00000

FC-PM-NE : 0

0

0

Threshold : 0 TCA(enable) : NO

Threshold : 0.00010

TCA(enable) : YES

Threshold : 0 TCA(enable) : NO

Threshold : 0.02300

TCA(enable) : NO

Threshold :

Threshold :

0

0

TCA(enable)

TCA(enable)

: NO

: NO

Threshold : 0.02300

TCA(enable) : NO

Threshold :

Threshold :

0 TCA(enable) : NO

200 TCA(enable) : YES

Threshold : 1.00000

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0.02300

TCA(enable) : NO

Threshold :

Threshold :

0 TCA(enable) : NO

0 TCA(enable) : NO

Threshold : 0.02300

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

OTN Far-End Valid : YES

ES-SM-FE : 0

ESR-SM-FE : 0.00000

SES-SM-FE : 0

SESR-SM-FE : 0.00000

UAS-SM-FE : 0

BBE-SM-FE : 0

BBER-SM-FE : 0.00000

FC-SM-FE : 0

ES-PM-FE : 0

ESR-PM-FE : 0.00000

SES-PM-FE : 0

SESR-PM-FE : 0.00000

UAS-PM-FE : 0

BBE-PM-FE : 0

BBER-PM-FE : 0.00000

FC-PM-FE : 0

Threshold : 0 TCA(enable) : NO

Threshold : 1.00000

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0.02300

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0.02300

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 1.00000

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0.02300

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0.02300

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Router#show controllers dwdm 0/1/0 pm interval 15-min otn 1 g709 OTN in interval 1 [9 :00:00 - 9 :15:00 Thu Jun 9 2016]

OTN current bucket type: VALID

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

165

OTN Wrapper Overview

Verifying PM Parameters Configuration

OTN Near-End Valid : YES

ES-SM-NE : 0

ESR-SM-NE : 0.00000

SES-SM-NE : 0

SESR-SM-NE : 0.00000

UAS-SM-NE : 0

BBE-SM-NE : 0

BBER-SM-NE : 0.00000

FC-SM-NE : 0

ES-PM-NE : 0

ESR-PM-NE : 0.00000

SES-PM-NE : 0

SESR-PM-NE : 0.00000

UAS-PM-NE : 0

BBE-PM-NE : 0

BBER-PM-NE : 0.00000

FC-PM-NE : 0

OTN Far-End Valid : YES

ES-SM-FE : 0

ESR-SM-FE : 0.00000

SES-SM-FE : 0

SESR-SM-FE : 0.00000

UAS-SM-FE : 0

BBE-SM-FE : 0

BBER-SM-FE : 0.00000

FC-SM-FE : 0

ES-PM-FE : 0

ESR-PM-FE : 0.00000

SES-PM-FE : 0

SESR-PM-FE : 0.00000

UAS-PM-FE : 0

BBE-PM-FE : 0

BBER-PM-FE : 0.00000

FC-PM-FE : 0

Use the show controllers command to verify PM parameters configuration for OTN in 24-hour interval:

Router#show controllers dwdm 0/1/0 pm interval 24-hour otn 0 g709 OTN in the current interval [00:00:00 - 09:16:10 Thu Jun 9 2016]

OTN current bucket type: INVALID

OTN Near-End Valid : YES

ES-SM-NE : 0

ESR-SM-NE : 0.00000

SES-SM-NE : 0

SESR-SM-NE : 0.00000

UAS-SM-NE :

BBE-SM-NE :

BBER-SM-NE : 0.00000

0

0

FC-SM-NE

ES-PM-NE

:

:

0

0

ESR-PM-NE : 0.00000

SES-PM-NE : 0

SESR-PM-NE : 0.00000

UAS-PM-NE :

BBE-PM-NE :

BBER-PM-NE : 0.00000

FC-PM-NE : 0

0

0

Threshold : 0 TCA(enable) : NO

Threshold : 0.00000

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0.00000

TCA(enable) : NO

Threshold :

Threshold :

0

0

TCA(enable)

TCA(enable)

: NO

: NO

Threshold : 0.00000

TCA(enable) : NO

Threshold :

Threshold :

0 TCA(enable) : NO

0 TCA(enable) : NO

Threshold : 0.00000

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0.00000

TCA(enable) : NO

Threshold :

Threshold :

0 TCA(enable) : NO

0 TCA(enable) : NO

Threshold : 0.00000

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

OTN Far-End Valid : YES

ES-SM-FE : 0

ESR-SM-FE : 0.00000

SES-SM-FE : 0

SESR-SM-FE : 0.00000

UAS-SM-FE : 0

BBE-SM-FE : 0

BBER-SM-FE : 0.00000

FC-SM-FE : 0

ES-PM-FE : 0

ESR-PM-FE : 0.00000

SES-PM-FE : 0

SESR-PM-FE : 0.00000

UAS-PM-FE : 0

BBE-PM-FE : 0

BBER-PM-FE : 0.00000

FC-PM-FE : 0

Threshold : 0 TCA(enable) : NO

Threshold : 0.00000

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0.00000

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0.00000

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0.00000

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0.00000

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

Threshold : 0.00000

TCA(enable) : NO

Threshold : 0 TCA(enable) : NO

166

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

OTN Wrapper Overview

Troubleshooting Scenarios

Router#show controllers dwdm 0/1/0 pm interval 24-hour otn 1 g709 OTN in interval 1 [00:00:00 - 24:00:00 Wed Jun 8 2016]

OTN current bucket type: INVALID

OTN Near-End Valid : YES

ES-SM-NE : 7

ESR-SM-NE : 0.00000

SES-SM-NE : 7

SESR-SM-NE : 0.00000

UAS-SM-NE : 41

BBE-SM-NE : 0

BBER-SM-NE : 0.00000

FC-SM-NE : 3

ES-PM-NE : 2

ESR-PM-NE : 0.00000

SES-PM-NE : 0

SESR-PM-NE : 0.00000

UAS-PM-NE : 0

BBE-PM-NE : 3

BBER-PM-NE : 0.00000

FC-PM-NE : 0

OTN Far-End Valid : NO

ES-SM-FE : 0

ESR-SM-FE : 0.00000

SES-SM-FE : 0

SESR-SM-FE : 0.00000

UAS-SM-FE : 0

BBE-SM-FE : 0

BBER-SM-FE : 0.00000

FC-SM-FE : 0

ES-PM-FE : 1

ESR-PM-FE : 0.00000

SES-PM-FE : 0

SESR-PM-FE : 0.00000

UAS-PM-FE : 0

BBE-PM-FE : 1

BBER-PM-FE : 0.00000

FC-PM-FE : 0

If TCA is enabled for OTN or FEC alarm, a syslog message is displayed for the 15-minute or 24-hour interval as follows:

*Jun 9 09:18:02.274: %PMDWDM-4-TCA: dwdm-0/1/0: G709 ESR-SM NE value (540) threshold (10)

15-min

Troubleshooting Scenarios

The following table shows the troubleshooting solutions for the feature.

Problem

Link is not coming up

Incrementing BIP Error

Solution

Perform shut and no shut actions of the interface.

Check for TTI Mismatch.

Verify the major alarms.

Verify the FEC mode.

Verify that Cisco supported transreceiver list is only used on both sides .

Verify FEC Mismatch.

FEC contains UC and EC errors and link is not coming up

Verify the FEC Mismatch.

Associated Commands

The following commands are used to configure OTN Wrapper:

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

167

Associated Commands

Commands controller dwdm g709 disable g709 fec g709 odu report g709 odu threshold g709 otu report g709 otu threshold g709 overhead g709 tti processing pm fec threshold pm otn report pm otn threshold show controller dwdm

OTN Wrapper Overview

Links http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-c2.html#wp1680149833 http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-f1.html#wp7175256270 http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-f1.html#wp3986227580 http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-f1.html#wp3893551740 http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-f1.html#wp3365653610 http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-f1.html#wp3306168000 http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-f1.html#wp2500217585 http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-f1.html#wp6997702360 http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-f1.html#wp3679037909 http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-o1.html#wp8624772760 http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-o1.html#wp2518071708 http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-o1.html#wp1512678519 http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-s2.html#wp7346292950

168

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

OTN Wrapper Overview

Commands show interfaces transport-mode

Associated Commands

Links http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-s4.html#wp2987586133 http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-t1.html#wp3012872075

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

169

Associated Commands

OTN Wrapper Overview

170

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

C H A P T E R

10

Configuring the SDM Template

This section details the approximate number of resources supported in each templates for a router running the license.

Prerequisites for the SDM Template, on page 171

Restrictions for the SDM Template, on page 171

Information About the SDM Template, on page 173

Selecting the SDM Template, on page 184

Verifying the SDM Template, on page 186

SDM Template Supported Features on RSP3 Module, on page 186

Prerequisites for the SDM Template

Before using an SDM template, you must set the license boot level.

For IPv6 QoS template, the license to use should be metroipaccess . You can view the license level using the show version | in License Level command

Note If you use advancedmetroipaccess , then your options may vary.

Restrictions for the SDM Template

• Do not configure CoPP and BDI-MTU SDM templates together, as it is not supported.

• If you do not enable the EFP feature template, then there is no traffic flow between EFP and VFI (when

EFP is with Split Horizon group and VFI is default). But when you enable the EFP feature template, then there is traffic flow between EFP and VFI because of design limitations.

• You cannot edit individual values in a template category as all templates are predefined.

• You cannot use a new SDM template without reloading the router.

• SDM templates are supported only by the Metro Aggregation Services license. Use the help option of the sdm prefer command to display the supported SDM templates.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

171

Configuring the SDM Template

Restrictions for the SDM Template

• A mismatch in an SDM template between an active RSP and standby RSP results in a reload of the standby RSP. During reload, SDM template of the standby RSP synchronizes with the SDM template of the active RSP.

• To revert to the current SDM template after using the sdm prefer command (which initiates reload of a new SDM template), you must wait for the reload to complete.

• Using the configure replace command which results in changes in the current SDM template is not supported.

• The supported group numbers are for scaling in uni-dimension. When scaling in multidimension, the numbers can vary as certain features may share resources.

• When scaling, features using Multiprotocol Label Switching (MPLS) are limited by the number of MPLS labels.

• Internal TCAM usage that is reserved for IPv6 is 133-135 entries. TCAM space that is allotted for SDM template is 135 entries on the router.

• EAID Exhaust occurs when two paths are MPLS and two are IP. It does not occur if all the four paths are IP.

• The following restrictions apply to the maximum IPv6 QoS ACL SDM template:

• The number of QoS ACL class maps and policy maps that are supported depends on the maximum

TCAM entries available.

• The software solution with expansion is applicable only for maximum QoS SDM template and more than eight Layer 4-port matches are supported for the maximum QoS SDM template. For other templates, due to hardware restriction, a maximum of eight Layer 4-port operators is supported per interface.

• Ethernet CFM, Ethernet OAM, and Y.1731 protocols are not supported. Features dependent on these protocols are impacted.

• Layer 2 monitoring features are not supported.

• The S-TAG based fields are not supported for classification, if IPv6 address match exists in the policy-map.

• Only eight Layer 4 operations are supported in templates other than maximum IPv6 QoS ACL template.

172

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

Information About the SDM Template

Note

Release Time

16.6.1

49-50 mins

16.7.1

50 mins

16.8.1

-

16.9.1

75 mins

Activity

Reload to SSO bulk Sync state

-

Reload to SSO bulk Sync state

Reload to SSO bulk Sync state

Information About the SDM Template

The SDM templates are used to optimize system resources in the router to support specific features, depending on how the router is used in the network. The SDM templates allocate Ternary Content Addressable Memory

(TCAM) resources to support different features. You can select the default template to balance system resources or select specific templates to support the required features.

The following table shows the approximate number of each resource supported in each of the templates for a router running the Metro Aggregation Services license on RSP3.

Table 18: Approximate Number of Feature Resources Allowed by Each SDM Template (RSP3)

Functionality

MAC table

IPv4/VPNv4 Routes

IPv6/VPNv6 Routes uRPF IPv4 routes

IPv4 mcast routes

(mroutes)

IPv6 mcast routes

(mroutes)

Default Template (RPF )

200K

IPv4 Template (No RPF)

200K

IPv6 Template

200K

Without MPLS Without MPLS Without MPLS

32k urpf ipv4 routes +

160k ipv4 routes

192k ipv4 routes 76k ipv4 routes

With MPLS With MPLS

With MPLS

32k urpf ipv4 routes +

160k (ipv4 routes + mpls labels )

192k (ipv4 routes + mpls labels)

MPLS Labels = 32000

76k (ipv4 routes + mpls labels )

MPLS Labels = 32000

MPLS Labels = 32000

8192

32768

4000

8192

32768

4000

36864

32768

4000

1000 1000 1000

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

173

Configuring the SDM Template

Information About the SDM Template

Functionality

Bridge Domains

EoMPLS Tunnels

MPLS VPN

VRF Lite

VPLS Instances

4

IPv4 ACL entries

Default Template (RPF )

4094

4000

1000

1000

3500

1000 (984 user configurable)

IPv6 ACL entries v4 QOS Classifications v6 QoS Classifications

128 (124 user configurable)

16000

NS

Egress policers per ASIC NS

OAM sessions

IPSLA sessions

EFP

Maximum VLANs per port

1000

1000

16000

4,000 per ASIC

Maximum VPLS neighbors

Maximum attachment circuit per BD

STP Instances

Maximum Etherchannel groups

64

64

16

48

Maximum Interfaces per

Etherchannel groups

Maximum VRRP per system

8

255

Maximum HSRP per system

255

Maximum Ingress MPLS labels

32000

64

64

16

48

8

255

255

32000

IPv4 Template (No RPF)

4094

4000

1000

1000

3500

1000 (984 user configurable)

128 (124 user configurable)

16000

NS

NS

1000

1000

16000

4,000 per ASIC

IPv6 Template

4094

4000

1000

1000

3500

1000 (984 user configurable)

128 (124 user configurable)

16000

NS

NS

1000

1000

16000

4,000 per ASIC

64

64

16

48

8

255

255

32000

174

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

Information About the SDM Template

Functionality

Maximum FRR/TE

Headend

Maximum FRR/TE

Midpoints

Default Template (RPF )

500

5000

Maximum E-LMI sessions

128

Maximum BFD sessions 1023

Maximum SPAN/RSPAN sessions

10

Maximum Queue counters per ASIC/system

40000/48000

Maximum Policer counters per ASIC/system

12000/24000

Max BDI for L3 1000

Multicast OIF per group for VF Lite or mVPN

255

Multicast OIF per group for native multicast

255

Queues per ASIC/system 40000/48000

Max Queues per EFP

Ingress Classifications

Egress Classifications

8

16000

48000

Max Ingress Policers per

ASIC/system

12000/24000

Max Egress Policers per

ASIC/system

NS

Maximum EFPs per BD 256

Maximum number of BDI for PW

128

Maximum Layer 3 interfaces

Max REP segments

Maximum class-maps

1000

NS

1000

IPv4 Template (No RPF)

500

5000

128

1023

10

40000/48000

12000/24000

1000

255

255

40000/48000

8

16000

48000

12000/24000

NS

256

128

1000

NS

1000

IPv6 Template

500

5000

128

1023

10

40000/48000

12000/24000

1000

255

255

40000/48000

8

16000

48000

12000/24000

NS

256

128

1000

NS

1000

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

175

Configuring the SDM Template

Information About the SDM Template

Functionality

Maximum policy maps

Max number of OSPF

Neighbors

Max number of ISIS neighbors

Max number of ISIS instances

Max number of BGP neighbors

Max number IEEE

802.1ag/Y.1731(CFM) instances at 1sec for xconnect

Default Template (RPF )

1000

400

400

30

250

1000

Max number IEEE

802.1ag/Y.1731(CFM) instances at 3.3 ms for BD

& xconenct

1000

Max number IEEE

802.1ag/Y.1731(CFM) instances at 100 ms for

BD & xconnect

1000

Max number IEEE

802.1ag/Y.1731(CFM) instances at 1Sec for BD

1000

Max number of Y.1731

instances

1000

Maximum Class-maps in policy-map

512

Max number of match statements per class-map

16

1023 Max number of BFD sessions at 3.3ms

Max number of BFD sessions at 100ms

1023

Max number of BFD sessions at 1S

1023

IPv4 Template (No RPF)

1000

400

400

30

250

1000

1000

1000

1000

1000

512

16

1023

1023

1023

IPv6 Template

1000

400

400

30

250

1000

1000

1000

1000

1000

512

16

1023

1023

1023

176

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

Information About the SDM Template

Functionality

Max number of IGP

Prefixes protected via

LFA-FRR

Default Template (RPF )

1500

Max number of L3VPN

Prefixes protected via

LFA-FRR

4000

IPv4 Template (No RPF)

1500

4000

IPv6 Template

1500

4000

Max number of L2VPN sessions protected via

LFA-FRR

2000 2000 2000

4

From release 16.7.x the VPLS backup PW feature is supported, so if VPLS instance is configured then the maximum VPLS session is limited to 1000 instead of 3500.

The following table shows the approximate number of each resource supported in each of the templates for a router running the Metro Aggregation Services license on RSP2.

Table 19: Approximate Number of Feature Resources Allowed by Each SDM Template (RSP2)

Resource Default Template Video Template

16000

4000

IP Template

16000

65536

Maximum IPv6

QoS Template

16000

4000

MAC table

Virtual local area network (VLAN) mapping

IPv4 routes

5

16000

4000

20000

3962 IPv6 routes

VPNv4 routes

6

VPNv6 routes

20000

3962

IPv4 multicast routes (mroutes)

Layer 2 multicast groups

7

Bridge Domains

(BD)

MAC-in-MAC

1000

NA

4000

0

Ethernet over

MPLS (EoMPLS) tunnels

2000

12000

3962

12000

3962

2000

NA

4000

0

2000

24000

1914

24000

1914

1000

NA

4000

0

2000

20000

3962

20000

3962

1000

NA

4000

0

2000

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

177

Information About the SDM Template

Resource Default Template

MPLS Virtual

Private Network

(VPN)

128

Virtual Routing and

Forwarding (VRF) lite

128

Virtual Private

LAN Services

(VPLS) instances

2000

Access Control List

(ACL) entries

8

2000

Queues per

Application-Specific

Integrated Circuit

(ASIC)

9

4095

4096 IPv4 Quality of

Service (QoS) classifications

Policers 4096

Ethernet

Operations,

Administration, and

Maintenance

(OAM) sessions

1000

1000 IP Service Level

Agreements

(IPSLA) sessions

Ethernet Flow

Point (EFP)

8000

Maximum VLANs per port

4094

Maximum I-TAG per system

500

64 Maximum VPLS neighbors

Maximum attachment circuit per BD

STP Instances

128

16

Video Template

128

128

2000

4000

4095

2048

4096

1000

1000

8000

4094

500

64

128

16

IP Template

128

128

2000

2000

4095

4096

4096

1000

1000

8000

4094

500

64

128

16

Configuring the SDM Template

1000

8000

4094

500

64

128

16

4096

4096

0

2000

2000

4095

Maximum IPv6

QoS Template

128

128

178

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

Information About the SDM Template

Resource Default Template Video Template IP Template Maximum IPv6

QoS Template

64 Maximum

Etherchannel groups

Maximum

Interfaces per

Etherchannel groups

Maximum Hot

Standby Router

Protocol (HSRP)

64

8

128 (For Cisco

IOS-XE Release

3.14 and earlier)

256 (For Cisco

IOS-XE Release

3.15 and later)

Maximum Virtual

Router Redundancy

Protocol (VRRP)

128 (For Cisco

IOS-XE Release

3.14 and earlier)

255 (For Cisco

IOS-XE Release

3.15 and later)

Maximum Ingress

MPLS labels

32000

Maximum Egress

MPLS labels

28500

Maximum Fast

Reroute

(FRR)/Traffic

Engineering (TE) headend

500

Maximum FRR/TE midpoints

5000

Maximum

Enhanced Local

Management

Interface (E-LMI) sessions

1000

Maximum

Bidirectional

Forwarding

Detection (BFD) sessions

1023

64

8

28500

500

5000

1000

1023

64

8

1023

8

128 (For Cisco

IOS-XE Release

3.14 and earlier)

256 (For Cisco

IOS-XE Release

3.15 and later)

128 (For Cisco

IOS-XE Release

3.14 and earlier)

255 (For Cisco

IOS-XE Release

3.15 and later)

32000

128 (For Cisco IOS-XE

Release 3.14 and earlier)

256 (For Cisco IOS-XE

Release 3.15 and later)

128 (For Cisco

IOS-XE Release

3.14 and earlier)

256 (For Cisco

IOS-XE Release

3.15 and later)

128 (For Cisco IOS-XE

Release 3.14 and earlier)

255 (For Cisco IOS-XE

Release 3.15 and later)

128 (For Cisco

IOS-XE Release

3.14 and earlier)

255 (For Cisco

IOS-XE Release

3.15 and later)

32000 32000

28500

500

5000

1000

28500

500

5000

1000

1023

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

179

Configuring the SDM Template

Information About the SDM Template

Resource Default Template Video Template IP Template Maximum IPv6

QoS Template

32 Maximum

Switched Port

Analyzer

(SPAN)/Remote

SPAN (RSPAN) sessions

32

Maximum Queue counters (packet & byte)

65536

Maximum Policer counters (packet & byte)

49152

Maximum number of BDI for Layer 3

1000

IPv6 ACL 1000

IPv6 QoS classification

4096

Maximum Number of Layer 4

Source/Destination matches per interface

10

8

32

65536

49152

1000

1000

4096

8

32

65536

49152

1000

1000

4096

8

65536

49152

1000

2000

4096

NA

9

10

7

8

5

6

Using IPv4 and VPNv4 routes concurrently reduces the maximum scaled value as both the routes use the same TCAM space.

Due to label space limitation of 16000 VPNv4 routes, to achieve 24000 VPNv4 routes in IP template use per VRF mode.

Using Layer 2 and Layer 3 multicast groups concurrently reduces the scale number to 1947.

ACLs contend for TCAM resources with Multicast Virtual Private Network (MVPN).

User available queues are 1920.

TCAM consumption for IPv6 Qos ACL Layer 4 port match operations increase with Maximum IPv6

Qos SDM template.

The following table shows the approximate number of each resource supported in each of the templates for a router running the Metro Aggregation Services license on RSP1A.

Table 20: Approximate Number of Feature Resources Allowed by Each SDM Template (RSP1A)

Resource IP template

MAC table 16000

Virtual local area network (VLAN) mapping

4000

IPv4 routes

11

24000

Video template

16000

4000

12000

180

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

Resource

IPv6 routes

12

VPNv4 routes

13

VPNv6 routes

IPv4 multicast routes (mroutes)

Layer 2 multicast groups

14

Bridge Domains (BD)

MAC-in-MAC

Ethernet over MPLS (EoMPLS) tunnels

MPLS Virtual Private Network

(VPN)

Virtual Routing and Forwarding

(VRF) lite

Virtual Private LAN Services

(VPLS) instances

Access Control List (ACL) entries

15

Queues per Application-Specific

Integrated Circuit (ASIC)

16

IPv4 Quality of Service (QoS) classifications

Policers

Ethernet Operations,

Administration, and Maintenance

(OAM) sessions

IP Service Level Agreements

(IPSLA) sessions

Ethernet Flow Point (EFP)

Maximum VLANs per port

Maximum I-TAG per system

Maximum VPLS neighbors

Maximum attachment circuit per

BD

STP Instances

Maximum Etherchannel groups

IP template

4000

24000

4000

1000

1000

4094

0

512

128

128

26

2000

2048

4096

1024

1000

1000

4000

4094

500

62

62

16

26

Information About the SDM Template

1000

4000

4094

500

62

62

16

26

2048

2048

1024

1000

Video template

4000

12000

4000

2000

2000

4094

0

512

128

128

26

4000

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

181

Configuring the SDM Template

Information About the SDM Template

Resource

Maximum Interfaces per

Etherchannel groups

Maximum Hot Standby Router

Protocol (HSRP)/Virtual Router

Redundancy Protocol (VRRP)

IP template

8

128

Maximum Ingress MPLS labels

Maximum Egress MPLS labels

Maximum Fast Reroute

(FRR)/Traffic Engineering (TE) headend

Maximum FRR/TE midpoints

16000

28500

512

Maximum Enhanced Local

Management Interface (E-LMI) sessions

Maximum Bidirectional

Forwarding Detection (BFD) sessions

5000

1000

511

Maximum Switched Port Analyzer

(SPAN)/Remote SPAN (RSPAN) sessions

32

Maximum Queue counters (packet

& byte)

65536

Video template

8

128

16000

28500

512

5000

1000

511

32

65536

Maximum Policer counters (packet

& byte)

49152

Maximum number of BDI for

Layer 3

256

49152

256

IPv6 ACL

IPv6 QoS classification

1000

4096

1000

2048

14

15

16

11

12

13

Using IPv4 and VPNv4 routes concurrently reduces the maximum scaled value as both the routes use the same TCAM space.

User available routes are 3967.

Due to label space limitation of 16000 VPNv4 routes, to achieve 24000 VPNv4 routes in IP template use per VRF mode.

Using Layer 2 and Layer 3 multicast groups concurrently reduces the scale number to 1947.

ACLs contend for TCAM resources with Multicast Virtual Private Network (MVPN).

User available queues are 1920.

The following table shows the approximate number of each resource supported in each of the templates for a router running the Metro Aggregation Services license on RSP1B.

182

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

Information About the SDM Template

Table 21: Approximate Number of Feature Resources Allowed by Each SDM Template (RSP1B)

Resource

MAC table

IVLAN mapping

EVLAN mapping

Maximum VLANS per port

Maximum security addresses per

EFP

Maximum security addresses per

BD

Maximum security addresses

Maximum security configuration addresses

EFPs per BD

IPv4 routes

IPv6 routes

Maximum BD interfaces

Maximum ITAG per system

IPv4 routing groups

17

IPv6 routing groups

18

IPv4 multicast groups

19

IPv6 multicast groups

20

BDs

MAC-in-MAC

EoMPLS tunnels

MPLS VPN

Virtual Routing and Forwarding

Scale (VRFS)

VPLS instances

Maximum VPLS neighbors

ACL entries

IPv6 ACL entries

Queues per ASIC

Classifications

Ingress policers per ASIC

VPNv4/v6 template

256000

4000

4000

4094

1000

10000

256000

256000

2000

62

4000

1000

16384

12288

8192

2000

4000

0

8000

1000

1000

62

80000

40000

1000

500

2000

2000

2000

Video template

256000

4000

4000

4094

1000

10000

256000

256000

2000

62

4000

1000

16384

12288

8192

10000

4000

0

8000

1000

1000

62

80000

8000

1000

500

8000

8000

10000

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

183

Configuring the SDM Template

Selecting the SDM Template

Resource

Egress policers per ASIC

Maximum class maps

Maximum policy maps

Maximum queue counters

Maximum policer counters

OAM sessions

ELMI sessions

SLA sessions

EFPs

MPLS ingress labels

MPLS egress labels

FRR TE headend

FRR TE midpoints

STP instances

VPNv4/v6 template

4096

4096

1024

65536

48152

4000

1000

1000

8000

64000

80000

1000

7000

128

1000

1000

8000

64000

80000

1000

7000

128

Video template

4096

4096

1024

65536

48152

4000

BFD sessions

HSRP VRRP sessions

511

256

Maximum EC groups 16

Maximum interfaces per EC groups 8

Maximum SPAN RSPAN sessions 32

511

256

16

8

IPv4 tunnel entries

Maximum VPNv4 and VPNv6 pre-fixes

21

1000

64000

32

1000

64000

18

19

20

21

17

Overall multicast groups in video template can be scaled to 8000 individually or in combination with other multicast features. For example: IPv4 routing groups can be scaled to 8000 or IPv4 routing groups and IPv6 routing groups together can be scaled to 8000.

See footnote 7.

See footnote 7.

See footnote 7.

VPNv4 and VPNv6 together can be scaled up to 64000 in per-prefix mode.

Selecting the SDM Template

To select an SDM template, complete the following steps:

184

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

Selecting the SDM Template

Procedure

Step 1

Step 2

Step 3

Command or Action enable

Example:

Router> enable

Purpose

Enables privileged EXEC mode.

• Enter your password if prompted.

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

sdm prefer { default | video | ip | mvpn_rsp1a

| VPNv4/v6 | max-ipv6-acl | enable_8k_efp | enable_copp | ipv4 | ipv6 | efp_feat_ext | enable_8k_efp | enable_copp | enable_l3vpn_cm | enable_l3vpn_cm | enable_match_inner_dscp | enable_portchannel_qos_multiple_active

| vpls_stats_enable }

Specifies the SDM template to be used on the router.

• default—Balances all functions.

• video—Increases multicast routes and

ACLs.

• ip—Increases IPv4/VPNv4 routes. This option is available only on RSP1A.

Example:

Router(config)# sdm prefer default

• mvpn_rsp1a—Supports MVPN. This option is available only on RSP1A.

• VPNv4/v6—Increases IPv4/VPNv4 routes.

This option is available only on RSP1B.

• max-ipv6-acl—Supports IPv6 QoS ACL routes. The NEQ Layer 4 operation is supported in maximum IPv6 QoS ACL template.

• ipv4—Enables the IPv4 template. This is supported on the RSP3 module.

• ipv6—Enables the IPv6 feature template.

This is supported on the RSP3 module.

• efp_feat_ext—Enables the EFP feature template. This is supported on the RSP3 module.

• enable_8k_efp—Enables the 8K EFP feature template. This is supported on the

RSP3 module.

• enable_copp—Enables the COPP feature template. This is supported on the RSP3 module.

• enable_l3vpn_cm—Enables the L3VPN conditional marking feature template. This is supported on the RSP3 module.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

185

Configuring the SDM Template

Verifying the SDM Template

Command or Action Purpose

• enable_match_inner_dscp—Enables the match inner dscp feature template. This is supported on the RSP3 module.

• enable_portchannel_qos_multiple_active—Enables the port channel QoS multiple active feature template. This is supported on the

RSP3 module.

• vpls_stats_enable—Enables the VPLS statistics feature template. This is supported on the RSP3 module.

Note

Note

When changing the SDM template, the router waits for two minutes before reloading. Do not perform any operation till the router reloads.

For the new SDM template to take effect, you must save and reload the new configuration, otherwise the current SDM template is retained.

Verifying the SDM Template

You can use the following show commands to verify configuration of your SDM template:

• show sdm prefer —Displays the resource numbers supported by the specified SDM template.

SDM Template Supported Features on RSP3 Module

This section details the supported SDM template features on the RSP3 module. The sdm prefer command provides the follwing templates

Table 22: SDM Templates and Supported Features

SDM Template sdm prefer vpls_stats_enable sdm prefer efp_feat_ext sdm prefer enable_8k_efp sdm prefer enable_match_inner_dscp sdm prefer enable_copp

Supported Feature

VPLS Statistics

Split-Horizon Groups

8K EFP (4 Queue Model)

Match Inner DSCP

Control Plane Policing

186

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

VPLS Statistics

SDM Template sdm prefer ipv4_ipv6

Supported Feature sdm prefer enable_portchannel_qos_multiple_active QoS Support on Port Channel LACP Active Active

16K EFP Support on Port Channel

Enhance uRPF scale to 32K

VPLS Statistics

VPLS statistic feature supports packet and byte count in ingress and egress directions. The following are the required criteria to enable this feature:

• Metro Aggregation services license

• Special SDM template

Use the following commands to enable or disable VPLS statistics feature: sdm prefer vpls_stats_enable sdm prefer vpls_stats_disable

After template configuration, the node is auto reloaded.

Restrictions

• EFP statistics is not supported when VPLS statistics is enabled.

• Transit packet drops data is not supported.

• There is a sync time of 10 seconds between the software and the hardware for fetching the statistics.

• If access rewrite is configured (pop 1), VC statistics show 4 bytes less than the actual size (in both imposition and disposition node) because pop 1 removes the VLAN header.

• VC statistics do not account LDP and VC label. It displays what is received from access in both imposition and disposition node.

Example

The following example shows a sample VPLS Statics counter output: router# show mpls l2transport vc 2200 detail

Local interface: Gi0/14/2 up, line protocol up, Ethernet:100 up

Destination address: 10.163.123.218, VC ID: 2200, VC status: up

Output interface: Te0/7/2, imposed label stack {24022 24025}

Preferred path: not configured

Default path: active

Next hop: 10.163.122.74

Create time: 20:31:49, last status change time: 16:27:32

Last label FSM state change time: 16:27:44

Signaling protocol: LDP, peer 10.163.123.218:0 up

Targeted Hello: 10.163.123.215(LDP Id) -> 10.163.123.218, LDP is UP

Graceful restart: configured and enabled

Non stop routing: configured and enabled

Status TLV support (local/remote) : enabled/supported

LDP route watch

Label/status state machine

: enabled

: established, LruRru

Last local dataplane status rcvd: No fault

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

187

Configuring the SDM Template

Split Horizon Enhancements on the RSP3 Module

Last BFD dataplane status rcvd: Not sent

Last BFD peer monitor status rcvd: No fault

Last local AC circuit status rcvd: No fault

Last local AC circuit status sent: No fault

Last local PW i/f circ status rcvd: No fault

Last local LDP TLV status sent: No fault

Last remote LDP TLV status rcvd: No fault

Last remote LDP ADJ status rcvd: No fault

MPLS VC labels: local 110, remote 24025

Group ID: local 40, remote 67109248

MTU: local 9000, remote 9000

Remote interface description: TenGigE0_0_2_3.2200

Sequencing: receive disabled, send disabled

Control Word: Off (configured: autosense)

SSO Descriptor: 10.163.123.218/2200, local label: 110

Dataplane:

SSM segment/switch IDs: 16911/90633 (used), PWID: 71

VC statistics: transit packet totals: receive 100, send 200 transit byte totals: receive 12800, send 25600 transit packet drops: receive 0, seq error 0, send 0

Split Horizon Enhancements on the RSP3 Module

Starting with Cisco IOS XE Release 16.6.1, the efp_feat_ext template is introduced. This template when enabled allows configuration of two split-horizon groups on the EVC bridge-domain.

• Two Split-horizon groups—Group 0 and Group 1 are configured through using the bridge-domain bd

number split-horizon group 0-1 command.

Prerequisites for Split-Horizon Groups on the RSP3 Module

• The efp_feat_ext template must be configured to enable the feature.

• Metro services license must be enabled; LICENSE_ACTIVE_LEVEL=metroaggrservices,all:ASR-903;

Restrictions for Split-Horizon Groups on the RSP3 Module

• The overall scale of EFPs is 8K, only if the split-horizon groups are configured. For information, see supported scale.

Note If split-horizon based-EFPs are not configured, the total EFPs supported are 4K.

• EFPs configured on the same bridge domain and same split-horizon group, cannot forward to or recieve traffic from each other.

• We do not recommned configuration of Y.1564 and split-horizon grpup on the same EFP.

• We do not recommend configuring MAC security with split-horizon group.

• Split-horizon group is not supported for CFM on this template. Configuing split-horizon groups on CFM based MEPs may result in MEPs being unlearnt, and unexpected behavior may be observed.

188

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

Split-Horizon Supported Scale

• If ethernet loopback is configured, and if a dynamic change in split-horizon group occurs on the EFP-BD, the ELB session must be restarted.

• A change in the split-horizon group configuration on a regular EFP results in hardware programming update and may impact L2 traffic. This results in a MAC-flush and re-learn of traffic with new MAC address.

Following are known behavoir of split-horizon groups:

• Changing the split-horizon group on any EFP, results in traffic flooding back to same EFP for few milliseconds.

• A small traffic leak may be observed on defaulting an interface with higher number of EFP with split-horizon configured.

• BFD flaps and underlying IGP flaps may be observed upon changing split-horizon groups, if BFD is hardware based.

Split-Horizon Supported Scale

8K EFPs are supported across RSP3-400 and 4K EFPs on RSP3-200.

Note If Split-horizon configuration does not exist, number of EFPs supported are reduced to 4K EFPs.

Table 23: Split-Horizon Supported Template

Split-Horizon Group

Default (No config)

Group 0

Group 1

RSP3-400

4K EFP

2K EFP

2K EFP

RSP3-200

2K EFP

1K EFP

1K EFP

Note Port-channel scale is half the regular scale of the EFP.

Configuring Split-Horizon Group on the RSP3 Module

interface GigabitEthernet0/2/2 service instance 1 ethernet encapsulation dot1q 100 bridge-domain 100 split-horizon group 0 is optional)

When you configure split-horizon group 0,(0 interface GigabitEthernet0/2/2 service instance 2 ethernet encapsulation dot1q 102 bridge-domain 102 split-horizon group 1 When you configure split-horizon group 1

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

189

Configuring the SDM Template

8K EFP (4 Queue Model)

8K EFP (4 Queue Model)

In Cisco IOS XE Release 3.18SP, the 8K EFP (4 Queue Model) support allows up to 8000 EFPs at the system level. EFP scale implementation follows the static model, that is, eight queues are created per EFP by default.

Information About 8000 (8K) EFP

• In default model, 5000 EFPs can be configured on Cisco ASR 903 RSP3 module.

• The Switch Database Management (SDM) template feature can be used to configure 8000 EFPs across

ASIC( 4000 EFPs per ASIC interfaces).

• In 8K EFP model, each EFP consumes four Egress queues. If 8K EFP SDM template is not enabled, each EFP consumes eight Egress queues.

• Ingress policy map can specify more than eight traffic classes based on PHB matches, which remains the same. However, Egress policy map can have three user defined class and class-default class.

• Each Egress class-maps can be mapped to a single or multiple traffic classes and each class-map mapped to a single queue.

• Maximum of two queues are set to Priority according to policy configuration.

• All the existing QOS restrictions that apply in default model are also applicable to 8K EFP model.

Prerequisites for 8000 (8K) EFP

• Activate the Metro Aggregation Services license on the device.

• To configure 8000 EFPs, enable the SDM template using CLI sdm prefer enable_8k_efp .

• Reset the SDM template using the CLI sdm prefer disable_8k_efp .

Restrictions for 8000 (8K) EFP

• Traffic class to Queue mapping is done per interface and not per EVC.

• Four traffic classes including class-default can be supported in Egress policy.

• Same three traffic classes or subset of three traffic classes match is supported on EVCs of an interface.

• Traffic classes to queue mapping profiles are limited to four in global, hence excluding class-default, only three mode unique combinations can be supported across interfaces.

• TRTCM always operates with conform-action transmit, exceed-action transmit and violate-action drop.

• By default, 1R2C Policer will behave as 1R3C Policer in 4 Queue model.

• All the QOS restrictions that is applicable in default mode is also applicable in 8k EFP mode

Configuring 8K Model

Configuring 8K EFP Template

Below is the sample configuration to enable 8K EFP or 4 Queue mode template. On enabling sdm prefer enable_8k_efp , the router reloads and boots up with 8K EFP template.

190

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

Verifying 8K EFP Template

RSP3-903(config)#sdm prefer enable_8k_efp

Template configuration has been modified. Save config and Reload? [yes/no]: yes

Building configuration...

Jul 22 05:58:30.774 IST: Changes to the EFP template preferences have been stored[OK]

Proceeding with system reload...

Reload scheduled for 06:00:38 IST Fri Jul 22 2016 (in 2 minutes) by console

Reload reason: EFP template change

Verifying 8K EFP Template

You can verify the current template as below.

Device#sh sdm prefer current

The current sdm template is "default" template and efp template is "enable_8k_efp" template

Configuring QOS in 8K EFP Model

Below is sample configuration to configure egress policy map when 4Q mode is enabled.

Device#enable

Device#configure terminal

Device(config)#interface GigabitEthernet0/3/0

Device(config-if)#service instance 10 e

Device(config-if-srv)#service-policy output egress

Current configuration : 193 bytes

!

policy-map egress class qos2 shape average 2000000 class qos3 shape average 3000000 class qos4 shape average 4000000

!

class class-default shape average 5000000 end

Device#sh run class-map qos2

Building configuration...

Current configuration : 54 bytes

!

class-map match-all qos2 match qos-group 2

!

end

Device#sh run class-map qos3

Building configuration...

Current configuration : 54 bytes

!

class-map match-all qos3 match qos-group 3

!

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

191

Configuring the SDM Template

Verifying QOS in 8K EFP Model end

Device#sh run class-map qos4

Building configuration...

Current configuration : 54 bytes

!

class-map match-all qos4 match qos-group 4

!

end

Verifying QOS in 8K EFP Model

You need to verify the interface and policy-map details to check 8K model queue is working.

Device# show run interface g0/3/0

Building configuration...

Current configuration : 217 bytes

!

interface GigabitEthernet0/3/0 no ip address negotiation auto service instance 10 ethernet encapsulation dot1q 10 rewrite ingress tag pop 1 symmetric service-policy output egress bridge-domain 10

!

end

Router#show running-config policy-map egress

Building configuration...

Current configuration : 193 bytes

!

policy-map egress class qos2 shape average 2000000 class qos3 shape average 3000000 class qos4 shape average 4000000 class class-default shape average 5000000

!

end

Device#sh policy-map int g0/3/0 serv inst 10

Port-channel10: EFP 10

Service-policy output: egress

Class-map: qos2 (match-all)

122566 packets, 125262452 bytes

30 second offered rate 0000 bps, drop rate 0000 bps

Match: qos-group 2

Queueing queue limit 4096000 us/ 1024000 bytes

(queue depth/total drops/no-buffer drops) 1032720/119746/0

(pkts output/bytes output) 2820/2882040 shape (average) cir 2000000, bc 8000, be 8000

192

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

16K EFP Support on Port Channel target shape rate 2000000

Class-map: qos3 (match-all)

122566 packets, 125262452 bytes

30 second offered rate 0000 bps, drop rate 0000 bps

Match: qos-group 3

Queueing queue limit 2730666 us/ 1024000 bytes

(queue depth/total drops/no-buffer drops) 1032720/118806/0

(pkts output/bytes output) 3760/3842720 shape (average) cir 3000000, bc 12000, be 12000 target shape rate 3000000

Class-map: qos4 (match-all)

245131 packets, 250523882 bytes

30 second offered rate 0000 bps, drop rate 0000 bps

Match: qos-group 4

Queueing queue limit 2048000 us/ 1024000 bytes

(queue depth/total drops/no-buffer drops) 1032720/239961/0

(pkts output/bytes output) 5170/5283740 shape (average) cir 4000000, bc 16000, be 16000 target shape rate 4000000

Class-map: class-default (match-any)

245131 packets, 250523882 bytes

30 second offered rate 0000 bps, drop rate 0000 bps

Match: any

Queueing queue limit 1638400 us/ 1024000 bytes

(queue depth/total drops/no-buffer drops) 1032720/239961/0

(pkts output/bytes output) 5170/5283740 shape (average) cir 5000000, bc 20000, be 20000 target shape rate 5000000

Device#

16K EFP Support on Port Channel

Starting with Cisco IOS XE 16.8.1 release, 16K EFPs on port channel are supported on the RSP3 module.

The following are the key features supported:

• In order to enable 16K EFP over a port channel, you need to enable the following template: enable_portchannel_qos_multiple_active

• 16000 EFPs are supported on the RSP3 module (8K EFPs are supported per ASIC). Each port can have a maximum of 8K EFPs configured.

• 8K bridge domains are supported.

• On the RSP3 module, 1024 BDI interfaces that include physical interface, port channel interface, and

BDI are available, and these interfaces can be configured upto 4096 BDI interfaces.

Note If a port channel is configured on an application-specific integrated circuit (ASIC), for example ASIC 0 , then ensure that physical members to be added to port channel also should be in the same ASIC.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

193

Configuring the SDM Template

Restrictions for 16K EFP on Port Channel

Restrictions for 16K EFP on Port Channel

• G.8032, SADT, CFM, and TEFP are not supported on the port channel.

• 16k EFP scale is not supported if SDM template is enabled for split horizon scale.

• Minimal traffic outage (for example, in milliseconds) is observed, when a policy map is applied or removed.

• In a complete scale environment, the EFP statistics update requires more than 1 minute to complete.

Configuring 16K EFP on Port Channel

To configure 16K EFP on port channel, use the following commands: router> enable router# configure terminal router(config)# sdm prefer enable_portchannel_qos_multiple_active router(config)# platform port-channel 10 members-asic-id 1 router(config)# platform qos-port-channel_multiple_active port-channel 10 router(config)# interface port-channel 10 router(config-if)# end

After the SDM template update, the device reloads automatically and you need to enter yes to save the configuration.

Verifying 16k EFP on Port Channel

The following are examples to verify for 16K EFP configuration on port channel.

show etherchannel summary

Router# show etherchannel summary

Flags: D - down P/bndl - bundled in port-channel

I - stand-alone s/susp - suspended

H - Hot-standby (LACP only)

R - Layer3

U - in use

S - Layer2 f - failed to allocate aggregator

M - not in use, minimum links not met u - unsuitable for bundling w - waiting to be aggregated d - default port

Number of channel-groups in use: 1

Number of aggregators: 1

Group Port-channel Protocol Ports

------+-------------+-----------+-----------------------------------------------

10 Po10(RU) LACP Te0/5/0(bndl) Te0/5/1(bndl)

RU - L3 port-channel UP State

SU - L2 port-channel UP state

P/bndl Bundled

S/susp - Suspended show ethernet service instance id interface stats

Router# show ethernet service instance id 12000 interface port-channel 10 stats

Port maximum number of service instances: 16000

Service Instance 12000, Interface port-channel 10

194

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

Control Plane Policing

Pkts In Bytes In Pkts Out Bytes Out

252 359352 252 359352 show ethernet service instance summary

Router# show ethernet service instance summary

System summary

Total Up AdminDo Down ErrorDi Unknown Deleted BdAdmDo bdomain xconnect local sw other all

16000

0

0

0

16000

16000

0

0

0

16000

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

Associated interface: port-channel 10

Total Up AdminDo bdomain 8000 8000 0 xconnect local sw

0

0

0

0

0

0 other all

0

8000

0

8000

0

0

Associated interface: port-channel 11 bdomain

Total

8000

Up AdminDo

8000 0 xconnect local sw other all

0

0

0

8000

0

0

0

8000

0

0

0

0

Down ErrorDi Unknown Deleted BdAdmDo

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

Down ErrorDi Unknown Deleted BdAdmDo

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

Control Plane Policing

The Control Plane Policing feature allows you to configure a quality of service (QoS) filter that manages the traffic flow of control plane packets to protect the control plane of routers and switches against reconnaissance and denial-of-service (DoS) attacks. In this way, the control plane (CP) can help maintain packet forwarding and protocol states despite an attack or heavy traffic load on the router or switch.

Restrictions for Control Plane Policing

Input Rate-Limiting Support

Input rate-limiting is performed in silent (packet discard) mode. Silent mode enables a router to silently discard packets using policy maps applied to input control plane traffic with the service-policy input command. For more information, see the “Input Rate-Limiting and Silent Mode Operation” section.

MQC Restrictions

The Control Plane Policing feature requires the Modular QoS CLI (MQC) to configure packet classification and traffic policing. All restrictions that apply when you use the MQC to configure traffic policing also apply when you configure control plane policing.

Match Criteria Support

Only the extended IP access control lists (ACLs) classification (match) criteria is supported.

Restrictions for CoPP on the RSP3

• sdm prefer enable_copp template must be enabled on the the RSP3 module to activate COPP.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

195

Configuring the SDM Template

Supported Protocols

• Ingress and Egress marking are not supported.

• Egress COPP is not supported. COPP with marking is not supported.

• CPU bound traffic (punted traffic) flows is supported via the same queue with or without CoPP.

• Only match on access group is supported on a CoPP policy.

• Hierarchical policy is not supported with CoPP.

• Class-default is not supported on CoPP policy.

• User defined ACLs are not subjected to CoPP classified traffic.

• A CoPP policy map applied on a physical interface is functional.

• When COPP template is enabled, classification on outer Vlan, inner Vlan, Inner Vlan Cos, destination

MAC address, source IP address, and destination IP address are not supported.

The template-based model is used to enable COPP features and disable some of the above mentioned

QOS classifications.

• When sdm prefer enable_copp template is enabled, sdm prefer enable_match_inner_dscp template is not supported.

• Only IP ACLs based class-maps are supported. MAC ACLs are not supported.

• Multicast protocols like PIM, IGMP are not supported.

• Only CPU destined Unicast Layer3 protocols packets are matched as part of COPP classification.

Restrictions on Firmware

• Port ranges are not supported.

• Only exact matches are supported, greater than, less than and not equal are not supported.

• Internet Control Message Protocol (ICMP) inner type’s classification not supported.

• Match any is only supported at class-map level.

• Policing action is supported on a CoPP policy map.

Supported Protocols

The following table lists the protocols supported on Control Plane Policing feature.

Supported Protocols

TFTP - Trivial FTP

TELNET

Criteria

Port Match

Port Match

Match Queue#

IP access list ext copp-system-acl-tftp permit udp any any eq 69

NQ_CPU_HOST_Q

NQ_CPU_CONTROL_Q IP access list ext copp-system-acl-telnet permit tcp any any eq telnet

196

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

Supported Protocols

Supported Protocols

NTP - Network Time

Protocol

Criteria

Port Match

FTP - File Transfer

Protocol

Port Match

SNMP - Simple Network

Management Protocol

Port Match

TACACS - Terminal

Access Controller

Access-Control System

Port Match

FTP-DATA Port Match

HTTP - Hypertext

Transfer Protocol

Port Match

WCCP - Web Cache

Communication Protocol

Port Match

SSH - Secure Shell Port Match

ICMP - Internet Control

Message Protocol

Protocol Match

DHCP - Dynamic Host

Configuration Protocol

Port Match

Match Queue#

IP access list ext copp-system-acl-ntp permit udp any any eq ntp

NQ_CPU_HOST_Q

IP access list ext copp-system-acl-ftp permit tcp host any any eq ftp

NQ_CPU_HOST_Q

IP access list ext copp-system-acl-snmp permit udp any any eq snmp

NQ_CPU_HOST_Q

IP access list ext copp-system-acl-tacacs permit tcp any any tacacs

NQ_CPU_HOST_Q

IP access list ext copp-system-acl-ftpdata permit tcp any any eq 20

NQ_CPU_HOST_Q

IP access list ext copp-system-acl-http permit tcp any any eq www

NQ_CPU_HOST_Q

IP access list ext copp-system-acl-wccp permit udp any eq 2048 any eq 2048

NQ_CPU_HOST_Q

IP access list ext copp-system-acl-ssh permit tcp any any eq 22

NQ_CPU_HOST_Q

NQ_CPU_HOST_Q IP access list copp-system-acl-icmp permit icmp any any

IP access list copp-system-acl-dhcp permit udp any any eq bootps

NQ_CPU_HOST_Q

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

197

Configuring the SDM Template

Input Rate-Limiting and Silent Mode Operation

Supported Protocols

MPLS- OAM

Criteria

Port Match

LDP - Label Distribution

Protocol

Port Match

RADIUS - Remote

Authentication Dial In

User Service

Port Match

Match Queue#

IP access list copp-system-acl-mplsoam

NQ_CPU_HOST_Q permit udp any eq 3503 any

IP access list copp-system-acl-ldp permit udp any eq 646 any eq 646 permit tcp any any eq 646

NQ_CPU_CFM_Q

IP access list copp-system-radius permit udp any any eq

1812 permit udp any any eq

1813 permit udp any any eq

1645 permit udp any any eq

1646 permit udp any eq 1812 any permit udp any eq 1813 any permit udp any eq 1645 any

NQ_CPU_HOST_Q

Input Rate-Limiting and Silent Mode Operation

A router is automatically enabled to silently discard packets when you configure input policing on control plane traffic using the service-policy input policy-map-name command.

Rate-limiting (policing) of input traffic from the control plane is performed in silent mode. In silent mode, a router that is running Cisco IOS XE software operates without receiving any system messages. If a packet that is entering the control plane is discarded for input policing, you do not receive an error message.

How to Use Control Plane Policing

Defining Control Plane Services

Perform this task to define control plane services, such as packet rate control and silent packet discard for the

RP.

198

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

Defining Control Plane Services

Before you begin

Before you enter control-plane configuration mode to attach an existing QoS policy to the control plane, you must first create the policy using MQC to define a class map and policy map for control plane traffic.

• Platform-specific restrictions, if any, are checked when the service policy is applied to the control plane interface.

• Input policing does not provide any performance benefits. It simply controls the information that is entering the device.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5 enable

Example:

Device> enable

Enables privileged EXEC mode.

• Enter your password if prompted.

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

control-plane

Example:

Device(config)# control-plane

Enters control-plane configuration mode (which is a prerequisite for defining control plane services).

service-policy [ input | output ] policy-map-name

Example:

Device(config-cp)# service-policy input control-plane-policy

Attaches a QoS service policy to the control plane.

• input —Applies the specified service policy to packets received on the control plane.

• policy-map-name —Name of a service policy map (created using the policy-map command) to be attached.

end

Example:

Device(config-cp)# end

(Optional) Returns to privileged EXEC mode.

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

199

Configuring the SDM Template

Configuration Examples for Control Plane Policing

Configuration Examples for Control Plane Policing

Example: Configuring Control Plane Policing on Input Telnet Traffic

! Rate-limit all other Telnet traffic.

Device(config)# access-list 140 permit tcp any any eq telnet

! Define class-map "telnet-class."

Device(config)# class-map telnet-class

Device(config-cmap)# match access-group 140

Device(config-cmap)# exit

Device(config)# policy-map control-plane-in

Device(config-pmap)# class telnet-class

Device(config-pmap-c)# police 80000 conform transmit exceed drop

Device(config-pmap-c)# exit

Device(config-pmap)# exit

! Define aggregate control plane service for the active route processor.

Device(config)# control-plane

Device(config-cp)# service-policy input control-plane-in

Device(config-cp)# end

Verification Examples for CoPP

The following example shows how to verify control plane policing on a policy map.

Router# show policy-map control-plane

Control Plane

Service-policy input: control-plane-in

Class-map: telnet-class (match-all)

10521 packets, 673344 bytes

5 minute offered rate 18000 bps, drop rate 15000 bps

Match: access-group 102 police: cir 64000 bps, bc 8000 bytes conformed 1430 packets, 91520 bytes; actions: transmit exceeded 9091 packets, 581824 bytes; actions: drop conformed 2000 bps, exceeded 15000 bps

Class-map: class-default (match-any)

0 packets, 0 bytes

5 minute offered rate 0000 bps, drop rate 0000 bps

Match: any

The following command is used to verify the TCAM usage on the router.

Router# show platform hardware pp active feature qos resource-summary 0

RSP3 QoS Resource Summary

Type Total Used Free

----------------------------------------------------------------------------

QoS TCAM 2048 2 2046

VOQs 49152 808 48344

QoS Policers 32768 2 32766

QoS Policer Profiles 1023 1 1022

Ingress CoS Marking Profiles 16 1 15

Egress CoS Marking Profiles 16 1 15

Ingress Exp & QoS-Group Marking Profiles 64 3 61

Ingress QOS LPM Entries 32768 0 32768

200

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

QoS Support on Port Channel LACP Active Active

QoS Support on Port Channel LACP Active Active

Link Aggregation Control Protocol (LACP) supports the automatic creation of ether channels by exchanging

LACP packets between LAN ports. Cisco IOS XE Everest 16.6.1 release introduces the support of QoS on port channel LACP active active mode. A maximum of eight member links form a port channel and thus the traffic is transported through the port channel. This feature is supported on Cisco RSP3 Module.

Benefits of QoS Support on Port Channel LACP Active Active

• This feature facilitates increased bandwidth.

• The feature supports load balancing.

• This features allows support on QoS on Port Channel with one or more active member links.

Restrictions for QoS Support on Port Channel Active Active

• Policy-map on member links is not supported.

• 100G ports and 40G ports cannot be a part of the port channel.

• Total number of port channel bandwidth supported on a given ASIC should not exceed 80G.

• This feature is not supported on multicast traffic.

• Only 3k service instance (EFP) scale is supported on port channel active active.

• Ensure that 2-3 seconds of delay is maintained before and after unconfiguring and re-configuring the port channel with the platform qos-port-channel_multiple_active command.

Note This delay increases when you have scaled EVC configurations on the port channel.

Configuring QoS Support on Port Channel Active Active

Enabling Port Channel Active/Active

Use the following commands to enable port channel active active: enable configure terminal sdm prefer enable_portchannel_qos_multiple_active end

Note The device restarts after enabling the sdm prefer enable_portchannel_qos_multiple_active command. After a successful reboot, verify the configuration using the command show sdm prefer current

Disabling Port Channel Active/Active

Use the following commands to disable port channel active active:

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

201

Configuring the SDM Template

Verification of QoS Support on Port Channel LACP Active Active enable configure terminal sdm prefer disable_portchannel_qos_multiple_active end

Configuring Active Active Port Channel per bundle

Use the following commands to configure active active port channel per bundle: enable configure terminal

platform qos-port-channel_multiple_active 10 end

Creating Port Channel Interface

Use the following commands to configure the port channel interface: enable configure terminal

interface port-channel 10 no shutdown end

Attaching member link to port channel

Use the following commands to attach a member link to the port channel: enable configure terminal

interface Te0/4/0

channel-group 10 mode active end

Configuring QoS Class Map and Policy Map

Use the following commands to configure QoS class map and policy map: enable configure terminal

class-map match-any qos1

match qos-group 1

class-map match-any qos2

match qos-group 2

policy-map policymapqos

class qos1

shape average 10000 k

class qos2

shape average 20000 k end

Attaching Configured Policy Map (policymapqos) on Port Channel Interface on Egress Direction

Use the following commands to attach the configured policy map (policymapqos) on the port channel interface on egress direction: enable configure terminal

interface port-channel 10

service-policy output policymapqos end

Verification of QoS Support on Port Channel LACP Active Active

Use the commands below to verify the port channel summary details:

202

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

Verification of QoS Support on Port Channel LACP Active Active

Device# show etherchannel summary

Flags: D - down P/bndl - bundled in port-channel

I - stand-alone s/susp - suspended

H - Hot-standby (LACP only)

R - Layer3 S - Layer2

U - in use f - failed to allocate aggregator

M - not in use, minimum links not met u - unsuitable for bundling w - waiting to be aggregated d - default port

Number of channel-groups in use: 1

Number of aggregators: 1

Group Port-channel Protocol Ports

------+-------------+-----------+-----------------------------------------------

10 Po10(RU) LACP Te0/4/0(bndl)

Use the commands below to verify the attached policy map on the port channel interface:

Device# show policy-map interface brief

Service-policy input: ingress

TenGigabitEthernet0/4/0

Service-policy output: policymapqos

Port-channel10

Device# show policy-map interface po10

Port-channel10

Service-policy output: policymapqos

Class-map: qos1 (match-any)

1027951 packets, 1564541422 bytes

30 second offered rate 50063000 bps, drop rate 40020000 bps

Match: qos-group 1

Queueing queue limit 819200 us/ 1024000 bytes

(queue depth/total drops/no-buffer drops) 0/821727/0

(pkts output/bytes output) 206224/313872928 shape (average) cir 10000000, bc 40000, be 40000 target shape rate 10000000

Class-map: qos2 (match-any)

852818 packets, 1297988996 bytes

30 second offered rate 41534000 bps, drop rate 21447000 bps

Match: qos-group 2

Queueing queue limit 409600 us/ 1024000 bytes

(queue depth/total drops/no-buffer drops) 0/440370/0

(pkts output/bytes output) 412448/627745856 shape (average) cir 20000000, bc 80000, be 80000 target shape rate 20000000

Class-map: class-default (match-any)

1565 packets, 118342 bytes

30 second offered rate 3000 bps, drop rate 0000 bps

Match: any queue limit 102 us/ 1024000 bytes

(queue depth/total drops/no-buffer drops) 0/0/0

(pkts output/bytes output) 1565/118342

Use the commands below to verify the configuration after enabling port channel active/active mode:

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

203

Configuring the SDM Template

Match Inner DSCP on RSP3 Module

#show sdm prefer current

The current sdm template is "default"

The current portchannel template is "enable_portchannel_qos_multiple_active"

Match Inner DSCP on RSP3 Module

Starting with Cisco IOS XE Release 16.6.1, the match_inner_dscp template is introduced. This template allows

DSCP policy map configuration on the RSP3 module for MPLS and tunnel terminated traffic.

Restrictions for Match Inner DSCP on RSP3 Module

• The IPv4 DSCP policy map configuration is not preserved in case of protection scenarios, where either primary or backup path is plane IP path and backup or primary is MPLS label path.

• Match on Inner DSCP for IPv6 is not supported.

• Only 1024 entries IPv4 TCAM entries are available. Hence, optimized usage of classes is recommended for configuration when policy map is applied on port channel or port or EFP.

• To support match on Inner DSCP for IPv4 when packets have MPLS forwarding type, three TCAM entries are added whenever there is a class map with match DSCP is configured.

One match is for normal DSCP scenario, one entry for Inner DSCP when outer header is MPLS header and other entry is when there is tunnel termination.

In Split Horizon template, each match DSCP class consumes 3 TCAM entries. For non-Split Horizon template, TCAM entries are one. For Class default, number of entries consumed is one. For TEFP, six entries are required for each match DSCP Class Map and two for class default.

Note Some of the IPv4 qualifiers are not supported when Split Horizon template is configured as there are limitation of Copy Engines in IPv4 Resource database.

Whenever Split Horizon template is enabled, four new qualifiers are added in

IPV4 QoS Field Group.

Configuring Match Inner DSCP on RSP3 Module

Class-map match-any dscp

Match dscp af13 exit policy-map matchdscp

Class dscp

Police cir 1000000end

Verifying Match Inner DSCP on RSP3 Module

Router# show platform hardware pp active feature qos resource-summary 0

PE1#res

RSP3 QoS Resource Summary

Type Total Used Free

----------------------------------------------------------------------------

QoS TCAM

VOQs

QoS Policers

1024

49152

32768

0

408

0

1024

48744

32768

204

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

Configuring the SDM Template

QoS Policer Profiles

Ingress CoS Marking Profiles

1023

16

Egress CoS Marking Profiles 16

Ingress Exp & QoS-Group Marking Profiles 64

Ingress QOS LPM Entries 32768

1

3

0

1

0

Verifying Match Inner DSCP on RSP3 Module

1023

15

15

61

32768

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

205

Verifying Match Inner DSCP on RSP3 Module

Configuring the SDM Template

206

Cisco NCS 4200 Series Software Configuration Guide, Cisco IOS XE Everest 3.18SP

advertisement

Related manuals

Download PDF

advertisement

Table of contents