Cisco NCS 5000 Series Manual

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

First Published: 2017-03-01

Last Modified: 2017-07-01

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

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright©1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWAREOF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://

www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership

relationship between Cisco and any other company. (1110R)

Preface

CHAPTER 1

CHAPTER 2

CHAPTER 3

Preface ix

Changes to this Document ix

Obtaining Documentation and Submitting a Service Request ix

New and Changed System Management Features 1

System Management Features Added or Modified in IOS XR Release 6.2.x 1

Configuring Manageability 3

Information about XML Manageability 3

How to Configure Manageability 3

Configuring the XML Agent 3

Configuration Examples for Manageability 5

Enabling VRF on an XML Agent: Examples 5

Implementing Physical and Virtual Terminals 7

Prerequisites for Implementing Physical and Virtual Terminals 7

Information About Implementing Physical and Virtual Terminals 7

Line Templates 7

Line Template Configuration Mode 8

Line Template Guidelines 8

Terminal Identification 9

vty Pools 9

How to Implement Physical and Virtual Terminals on Cisco IOS XR Software 10

Modifying Templates 10

Creating and Modifying vty Pools 11

Monitoring Terminals and Terminal Sessions 13

Craft Panel Interface 14

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

iii

Contents

Configuration Examples for Implementing Physical and Virtual Terminals 14

Additional References 16

CHAPTER 4

Implementing SNMP 19

Prerequisites for Implementing SNMP 19

Restrictions for SNMP use on Cisco IOS XR Software 19

Information about Implementing SNMP 20

SNMP Functional Overview 20

SNMP Manager 20

SNMP Agent 20

MIB 20

SNMP Versions 21

Comparison of SNMPv1, v2c, and v3 21

Security Models and Levels for SNMPv1, v2, v3 22

SNMPv3 Benefits 24

SNMPv3 Costs 24

User-Based Security Model 24

View-Based Access Control Model 25

MIB Views 25

Access Policy 25

IP Precedence and DSCP Support for SNMP 25

Session MIB support on subscriber sessions 26

SNMP Notifications 26

Session Types 27

How to Implement SNMP on Cisco IOS XR Software 27

Configuring SNMPv3 27

Configuring SNMPv3: Examples 29

Configuring SNMP Trap Notifications 33

Configuring Trap Notifications: Example 34

Setting the Contact, Location, and Serial Number of the SNMP Agent 35

Defining the Maximum SNMP Agent Packet Size 36

Changing Notification Operation Values 37

Setting IP Precedence and DSCP Values 38

Setting an IP Precedence Value for SNMP Traffic: Example 39

Setting an IP DSCP Value for SNMP Traffic: Example 39

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

Contents

Displaying SNMP Context Mapping 39

Monitoring Packet Loss 40

Configuring MIB Data to be Persistent 41

Configuring LinkUp and LinkDown Traps for a Subset of Interfaces 42

CHAPTER 5

CHAPTER 6

Implementing Object Tracking 45

Prerequisites for Implementing Object Tracking 45

Information about Object Tracking 45

How to Implement Object Tracking 46

Tracking the Line Protocol State of an Interface 46

Tracking IP Route Reachability 48

Building a Track Based on a List of Objects 49

Building a Track Based on a List of Objects - Threshold Percentage 51

Building a Track Based on a List of Objects - Threshold Weight 53

Configuration Examples for Configuring Object Tracking 55

Implementing CDP 57

Prerequisites for Implementing CDP 57

Information About Implementing CDP 57

How to Implement CDP on Cisco IOS XR Software 59

Enabling CDP 59

CHAPTER 7

Modifying CDP Default Settings 59

Monitoring CDP 61

Examples 62

Configuration Examples for Implementing CDP 63

Additional References 64

Configuring Periodic MIB Data Collection and Transfer 67

Prerequisites for Periodic MIB Data Collection and Transfer 67

Information About Periodic MIB Data Collection and Transfer 67

SNMP Objects and Instances 67

Bulk Statistics Object Lists 68

Bulk Statistics Schemas 68

Bulk Statistics Transfer Options 68

Benefits of Periodic MIB Data Collection and Transfer 68

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

Contents

How to Configure Periodic MIB Data Collection and Transfer 69

Configuring a Bulk Statistics Object List 69

Configuring a Bulk Statistics Schema 70

Configuring Bulk Statistics Transfer Options 71

Periodic MIB Data Collection and Transfer: Example 74

CHAPTER 8

Configuring Flexible Command Line Interface 77

Flexible CLI Configuration Groups 77

Flexible Configuration Restrictions 77

Configuring a Configuration Group 79

Simple Configuration Group: Example 80

Configuration Group Applied to Different Places: Example 81

Verifying the Configuration of Configuration Groups 81

Regular Expressions in Configuration Groups 83

Configuration Examples Using Regular Expressions 89

Configuration Group with Regular Expression: Example 89

Configuration Group Inheritance with Regular Expressions: Example 90

Layer 2 Transport Configuration Group: Example 91

Configuration Group Precedence: Example 92

Changes to Configuration Group are Automatically Inherited: Example 92

Configuration Examples for Flexible CLI Configuration 93

Basic Flexible CLI Configuration: Example 93

CHAPTER 9

Interface MTU Settings for Different Interface Types: Example 94

ACL Referencing: Example 96

Local Configuration Takes Precedence: Example 97

ISIS Hierarchical Configuration: Example 98

OSPF Hierarchy: Example 101

Link Bundling Usage: Example 104

Upgrading FPD 107

Prerequisites for FPD Image Upgrades 107

Overview of FPD Image Upgrade Support 107

Automatic FPD Upgrade 108

How to Upgrade FPD Images 109

Configuration Examples for FPD Image Upgrade 112

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

Contents

show hw-module fpd Command Output: Example 112

show fpd package Command Output: Example 114

upgrade hw-module fpd Command Output: Example 144

show platform Command Output: Example 144

CHAPTER 10

Implementing NTP 145

Prerequisites for Implementing NTP on Cisco IOS XR Software 145

Information About Implementing NTP 145

NTP-PTP Interworking 146

Configuring Poll-Based Associations 147

Configuring Broadcast-Based NTP Associates 149

Configuring NTP Access Groups 151

Configuring NTP Authentication 153

Disabling NTP Services on a Specific Interface 155

Configuring the Source IP Address for NTP Packets 157

Configuring the System as an Authoritative NTP Server 158

Configuring NTP-PTP Interworking 159

Updating the Hardware Clock 161

Verifying the Status of the External Reference Clock 162

Examples 163

Configuration Examples for Implementing NTP 164

CHAPTER 11

Configuring NTP server inside VRF interface 166

Additional References 168

Frequency Synchronization 171

Using Synchronous Ethernet for Frequency Synchronization 171

Restrictions 172

Configuring Frequency Synchronization 172

Configuring Frequency Synchronization on an Interface 174

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

vii

Contents

viii

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

Preface

This guide describes the System Management configuration details for Cisco IOS XR software. This chapter contains details on the changes made to this document.

Changes to this Document, page ix

•

Obtaining Documentation and Submitting a Service Request, page ix

•

Changes to this Document

Table 1: Changes to this Document

SummaryDate

Initial release of this document.March 2017

Republished for Release 6.2.2.July 2017

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation.

To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What's

New in Cisco Product Documentation RSS feed. RSS feeds are a free service.

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

Obtaining Documentation and Submitting a Service Request

Preface

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

CHAPTER 1

New and Changed System Management Features

This chapter lists all the features that have been added or modified in this guide. The table also contains references to these feature documentation sections.

System Management Features Added or Modified in IOS XR Release 6.2.x, page 1

•

System Management Features Added or Modified in IOS XR Release 6.2.x

Where DocumentedChanged in ReleaseDescriptionFeature

Configuring Frequency Synchronization using SyncE

using SyncE in devices connected by Ethernet in a network. This chapter describes the tasks required to configure frequency synchronization.

Release 6.2.1Frequency is synchronized accurately

Using Synchronous Ethernet for Frequency Synchronization, on page 171

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

System Management Features Added or Modified in IOS XR Release 6.2.x

New and Changed System Management Features

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

CHAPTER 2

Configuring Manageability

This module describes the configuration required to enable the Extensible Markup Language (XML) agent services. The XML Parser Infrastructure provides parsing and generation of XML documents with Document Object Model (DOM), Simple Application Programming Interface (API) for XML (SAX), and Document Type Definition (DTD) validation capabilities:

DOM allows customers to programmatically create, manipulate, and generate XML documents.

•

SAX supports user-defined functions for XML tags.

•

DTD allows for validation of defined document types.

•

Information about XML Manageability, page 3

•

How to Configure Manageability, page 3

•

Configuration Examples for Manageability, page 5

•

Information about XML Manageability

The Cisco IOS XR Extensible Markup Language (XML) API provides a programmable interface to the router for use by external management applications. This interface provides a mechanism for router configuration and monitoring utilizing XML formatted request and response streams. The XML interface is built on top of the Management Data API (MDA), which provides a mechanism for Cisco IOS XR components to publish their data models through MDA schema definition files.

Cisco IOS XR software provides the ability to access the router via XML using a dedicated TCP connection, Secure Socket Layer (SSL), or a specific VPN routing and forwarding (VRF) instance.

How to Configure Manageability

Configuring the XML Agent

This explains how to configure the XML agent.

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

Configuring the XML Agent

SUMMARY STEPS

DETAILED STEPS

xml agent [ssl]

iteration on size iteration-size

session timeout timeout

throttle {memory size | process-rate tags}

vrf { vrfname | ipv4} [access-list access-list-name]

PurposeCommand or Action

Configuring Manageability

Step 1

Step 2

Step 3

Step 4

Step 5

xml agent [ssl]

Example:

RP/0/RP0/CPU0:router(config)# xml agent

iteration on size iteration-size

Example:

RP/0/RP0/CPU0:router(config-xml-agent)# iteration on size 500

session timeout timeout

Example:

RP/0/RP0/CPU0:router(config-xml-agent)# session timeout 5

throttle {memory size | process-rate tags}

Example:

RP/0/RP0/CPU0:router(config-xml-agent)# throttle memory 300

vrf { vrfname | ipv4} [access-list

access-list-name]

Example:

RP/0/RP0/CPU0:router(config-xml-agent)# vrf mgmt-vrf

Enables Extensible Markup Language (XML) requests over a dedicated TCP connection and enters XML agent configuration mode. Use the ssl keyword to enable XML requests over Secure Socket Layer (SSL).

Configures the iteration size for large XML agent responses in KBytes. The default is 48.

Configures an idle timeout for the XML agent in minutes. By default, there is no timeout.

Configures the XML agent processing capabilities.

Specify the memory size in Mbytes. Values can range from

•

100 to 600. The default is 300.

Specify the process-rate as the number of tags that the XML

•

agent can process per second. Values can range from 1000 to

30000. By default the process rate is not throttled.

Configures the dedicated agent or SSL agent to receive and send messages via the specified VPN routing and forwarding (VRF) instance.

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

Configuring Manageability

Configuration Examples for Manageability

Enabling VRF on an XML Agent: Examples

The following example illustrates how to configure the dedicated XML agent to receive and send messages via VRF1, VRF2 and the default VRF:

RP/0/RP0/CPU0:router(config)# xml agent RP/0/RP0/CPU0:router(config-xml-agent)# vrf VRF1 RP/0/RP0/CPU0:router(config-xml-agent)# vrf VRF2

The following example illustrates how to remove access to VRF2 from the dedicated agent:

RP/0/RP0/CPU0:router(config)# xml agent ssl RP/0/RP0/CPU0:router(config-xml-ssl)# vrf VRF1 RP/0/RP0/CPU0:router(config-xml-ssl-vrf)# vrf VRF2 RP/0/RP0/CPU0:router(config)# xml agent RP/0/RP0/CPU0:router(config-xml-agent)# no vrf VRF1

The following example shows how to configure the XML SSL agent to receive and send messages through VRF1, VRF2 and the default VRF:

RP/0/RP0/CPU0:router(config)# xml agent ssl RP/0/RP0/CPU0:router(config-xml-agent)# vrf VRF1 RP/0/RP0/CPU0:router(config-xml-agent)# vrf VRF2

The following example removes access for VRF2 from the dedicated XML agent:

RP/0/RP0/CPU0:router(config)# xml agent ssl RP/0/RP0/CPU0:router(config-xml-agent)# no vrf VRF2

Configuration Examples for Manageability

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

Enabling VRF on an XML Agent: Examples

Configuring Manageability

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

CHAPTER 3

Implementing Physical and Virtual Terminals

Line templates define standard attribute settings for incoming and outgoing transport over physical and virtual terminal lines (vtys). Vty pools are used to apply template settings to ranges of vtys.

This module describes the tasks you need to implement physical and virtual terminals on your Cisco IOS XR network.

Prerequisites for Implementing Physical and Virtual Terminals, page 7

•

Information About Implementing Physical and Virtual Terminals, page 7

•

How to Implement Physical and Virtual Terminals on Cisco IOS XR Software, page 10

•

Craft Panel Interface, page 14

•

Configuration Examples for Implementing Physical and Virtual Terminals, page 14

•

Additional References, page 16

•

Prerequisites for Implementing Physical and Virtual Terminals

You must be in a user group associated with a task group that includes the proper task IDs. The command reference guides include the task IDs required for each command. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Information About Implementing Physical and Virtual Terminals

To implement physical and virtual terminals, you need to understand the concepts in this section.

Line Templates

The following line templates are available in the Cisco IOS XR software.

• Default line template—The default line template that applies to a physical and virtual terminal lines.

• Console line template—The line template that applies to the console line.

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

Line Template Configuration Mode

• User-defined line templates—User-defined line templates that can be applied to a range of virtual terminal

lines.

Line Template Configuration Mode

Changes to line template attributes are made in line template configuration mode. To enter line template configuration mode, issue the line command from XR Config mode, specifying the template to be modified. These line templates can be configured with the line command:

• console—console template

• default—default template

• template—user-defined template

After you specify a template with the line command, the router enters line template configuration mode where you can set the terminal attributes for the specified line. This example shows how to specify the attributes for the console:

Implementing Physical and Virtual Terminals

RP/0/RP0/CPU0:router(config)# line console RP/0/RP0/CPU0:router(config-line)#

From line template configuration mode, use the online help feature ( ? ) to view all available options. Some useful options include:

• absolute-timeout—Specifies a timeout value for line disconnection.

• escape-character—Changes the line escape character.

• exec-timeout—Specifies the EXEC timeout.

• length—Sets the number of lines displayed on the screen.

• session-limit—Specifies the allowable number of outgoing connections.

• session-timeout—Specifies an interval for closing the connection if there is no input traffic.

• timestamp—Displays the timestamp before each command.

• width—Specifies the width of the display terminal.

Line Template Guidelines

The following guidelines apply to modifying the console template and to configuring a user-defined template:

Modify the templates for the physical terminal lines on the router (the console port) from line template

•

configuration mode. Use the line console command from XR Config mode to enter line template configuration mode for the console template.

Modify the template for virtual lines by configuring a user-defined template with the line template-name

•

command, configuring the terminal attributes for the user-defined template from line template configuration, and applying the template to a range of virtual terminal lines using the vty pool command.

Attributes not defined in the console template, or any virtual template, are taken from the default template.

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

Implementing Physical and Virtual Terminals

The default settings for the default template are described for all commands in line template configuration mode in the Terminal Services Commands on module in System Management Command Reference for Cisco NCS 5000 Series Routers.

Terminal Identification

Note

Before creating or modifying the vty pools, enable the telnet server using the telnet server command in XR Config mode. See IP Addresses and Services Configuration Guide for Cisco NCS 5000 Series Routers and IP Addresses and Services Command Reference for Cisco NCS 5000 Series Routers for more information.

Terminal Identification

The physical terminal lines for the console port is identified by its location, expressed in the format of rack/slot/module , on the active or standby route processor (RP) where the respective console port resides. For virtual terminals, physical location is not applicable; the Cisco IOS XR software assigns a vty identifier to vtys according to the order in which the vty connection has been established.

vty Pools

Each virtual line is a member of a pool of connections using a common line template configuration. Multiple vty pools may exist, each containing a defined number of vtys as configured in the vty pool. The Cisco IOS XR software supports the following vty pools by default:

• Default vty pool—The default vty pool consists of five vtys (vtys 0 through 4) that each reference the

default line template.

• Default fault manager pool—The default fault manager pool consists of six vtys (vtys 100 through 105)

that each reference the default line template.

In addition to the default vty pool and default fault manager pool, you can also configure a user-defined vty pool that can reference the default template or a user-defined template.

When configuring vty pools, follow these guidelines:

The vty range for the default vty pool must start at vty 0 and must contain a minimum of five vtys.

•

The vty range from 0 through 99 can reference the default vty pool.

•

The vty range from 5 through 99 can reference a user-defined vty pool.

•

The vty range from 100 is reserved for the fault manager vty pool.

•

The vty range for fault manager vty pools must start at vty 100 and must contain a minimum of six vtys.

•

A vty can be a member of only one vty pool. A vty pool configuration will fail if the vty pool includes

•

a vty that is already in another pool.

If you attempt to remove an active vty from the active vty pool when configuring a vty pool, the

•

configuration for that vty pool will fail.

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

Implementing Physical and Virtual Terminals

How to Implement Physical and Virtual Terminals on Cisco IOS XR Software

Modifying Templates

This task explains how to modify the terminal attributes for the console and default line templates. The terminal attributes that you set will modify the template settings for the specified template.

SUMMARY STEPS

configure

line {console | default}

Configure the terminal attribute settings for the specified template using the commands in line template

configuration mode.

Use one of the following commands:

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

configure

Example:

RP/0/RP0/CPU0:router(config)# line console

RP/0/RP0/CPU0:router(config)# line default

Configure the terminal attribute settings for the specified template using the commands in line template configuration mode.

end

•

commit

•

PurposeCommand or Action

Enters line template configuration mode for the specified line template.line {console | default}

• console —Enters line template configuration mode for the console

template.

• default —Enters line template configuration mode for the default

line template.

—

Saves configuration changes.Use one of the following commands:

end

•

commit

•

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

When you issue the end command, the system prompts you to

•

commit changes:

Uncommitted changes found, commit them

Implementing Physical and Virtual Terminals

Example:

RP/0/RP0/CPU0:router(config-line)# end

RP/0/RP0/CPU0:router(config-line)# commit

Creating and Modifying vty Pools

PurposeCommand or Action

before exiting(yes/no/cancel)?

[cancel]:

Entering yes saves configuration changes to the running

◦

configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the

◦

router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration

◦

session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to

•

the running configuration file and remain within the configuration session.

Creating and Modifying vty Pools

This task explains how to create and modify vty pools.

You can omit Step 3, on page 12 to Step 5, on page 12 if you are configuring the default line template to reference a vty pool.

SUMMARY STEPS

configure

telnet {ipv4 | ipv6} server max-servers limit

line template template-name

Configure the terminal attribute settings for the specified line template using the commands in line template

configuration mode.

exit

vty-pool {default | pool-name | eem} first-vty last-vty [line-template {default | template-name}]

commit

DETAILED STEPS

Step 1

configure

PurposeCommand or Action

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

Creating and Modifying vty Pools

Implementing Physical and Virtual Terminals

PurposeCommand or Action

Step 2

Step 3

Step 4

Step 5

Step 6

telnet {ipv4 | ipv6} server max-servers limit

Example:

RP/0/RP0/CPU0:router(config)# telnet

ipv4 server max-servers 10

line template template-name

Example:

RP/0/RP0/CPU0:router(config)# line

template 1

Configure the terminal attribute settings for the specified line template using the commands in line template configuration mode.

exit

Example:

RP/0/RP0/CPU0:router(config-line)# exit

vty-pool {default | pool-name | eem} first-vty last-vty [line-template {default | template-name}]

Specifies the number of allowable Telnet servers. Up to 100 Telnet servers are allowed.

Note

By default no Telnet servers are allowed. You must configure this command in order to enable the use of Telnet servers.

Enters line template configuration mode for a user-defined template.

—

Exits line template configuration mode and returns the router to global configuration mode.

Creates or modifies vty pools.

If you do not specify a line template with the line-template

•

keyword, a vty pool defaults to the default line template.

Example:

RP/0/RP0/CPU0:router(config)# vty-pool

default 0 5 line-template default

RP/0/RP0/CPU0:router(config)# vty-pool

pool1 5 50 line-template template1

RP/0/RP0/CPU0:router(config)# vty-pool

eem 100 105 line-template template1

• default —Configures the default vty pool.

The default vty pool must start at vty 0 and must contain a

◦

minimum of five vtys (vtys 0 through 4).

You can resize the default vty pool by increasing the range

◦

of vtys that compose the default vty pool.

• pool-name —Creates a user-defined vty pool.

A user-defined pool must start at least at vty 5, depending

◦

on whether the default vty pool has been resized.

If the range of vtys for the default vty pool has been resized,

◦

use the first range value free from the default line template. For example, if the range of vtys for the default vty pool has been configured to include 10 vtys (vty 0 through 9), the range value for the user-defined vty pool must start with vty

10.

• eem —Configures the embedded event manager pool.

The default embedded event manager vty pool must start at

◦

vty 100 and must contain a minimum of six vtys (vtys 100 through 105).

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

Implementing Physical and Virtual Terminals

Monitoring Terminals and Terminal Sessions

PurposeCommand or Action

• line-template template-name —Configures the vty pool to

reference a user-defined template.

Step 7

commit

Monitoring Terminals and Terminal Sessions

This task explains how to monitor terminals and terminal sessions using the show EXEC commands available for physical and terminal lines.

The commands can be entered in any order.Note

SUMMARY STEPS

(Optional) show line [aux location node-id | console location node-id | vty number]

(Optional) show terminal

(Optional) show users

DETAILED STEPS

PurposeCommand or Action

Step 1

show line [aux location node-id | console location node-id | vty number]

Example:

RP/0/RP0/CPU0:router# show line

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

(Optional) Displays the terminal parameters of terminal lines.

Specifying the show line aux location node-id EXEC command

•

displays the terminal parameters of the auxiliary line.

Specifying the show line console location node-id EXEC command

•

displays the terminal parameters of the console.

For the location node-id keyword and argument, enter the location

◦

of the Route Processor (RP) on which the respective auxiliary or console port resides.

The node-id argument is expressed in the format of

◦

rack/slot/module .

Specifying the show line vty number EXEC command displays the

•

terminal parameters for the specified vty.

Craft Panel Interface

Implementing Physical and Virtual Terminals

PurposeCommand or Action

Step 2

Step 3

show terminal

Example:

RP/0/RP0/CPU0:router# show terminal

show users

Example:

RP/0/RP0/CPU0:router# show users

(Optional) Displays the terminal attribute settings for the current terminal line.

(Optional) Displays information about the active lines on the router.

Craft Panel Interface

The Craft Panel is an easily-accessible and user-friendly interface which assists the field operator in troubleshooting the router. It consists of a LCD display and three LEDs. The LEDs indicate minor, major and critical alarms.

For more details of the Craft Panel Interface, refer the Hardware and System set-up guides.

Configuration Examples for Implementing Physical and Virtual Terminals

Modifying the Console Template: Example

This configuration example shows how to modify the terminal attribute settings for the console line template:

line console

exec-timeout 0 0 escape-character 0x5a session-limit 10 disconnect-character 0x59 session-timeout 100 transport input telnet transport output telnet

In this configuration example, the following terminal attributes are applied to the console line template:

The EXEC time out for terminal sessions is set to 0 minutes, 0 seconds. Setting the EXEC timeout to 0

•

minutes and 0 seconds disables the EXEC timeout function; thus, the EXEC session for the terminal session will never time out.

The escape character is set to the 0x5a hexadecimal value (the 0x5a hexadecimal value translates into

•

the “Z” character).

The session limit for outgoing terminal sessions is set to 10 connections.

•

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

Implementing Physical and Virtual Terminals

The disconnect character is set to 0x59 hexadecimal value (the 0x59 hexadecimal character translates

•

into the “Y” character).

The session time out for outgoing terminal sessions is set to 100 minutes (1 hour and 40 minutes).

•

The allowed transport protocol for incoming terminal sessions is Telnet.

•

The allowed transport protocol for outgoing terminal sessions is Telnet.

•

To verify that the terminal attributes for the console line template have been applied to the console, use the show line command:

RP/0/RP0/CPU0:router# show line console location 0/0/CPU0

Tty Speed Modem Uses Noise Overruns Acc I/O * con0/0/CPU0 9600 - - - 0/0 -/-

Line con0_0_CPU0, Location "Unknown", Type "Unknown" Length: 24 lines, Width: 80 columns Baud rate (TX/RX) is 9600, 1 parity, 2 stopbits, 8 databits Template: console Config: Allowed transports are telnet.

Configuration Examples for Implementing Physical and Virtual Terminals

Modifying the Default Template: Example

This configuration example shows how to override the terminal settings for the default line template:

line default

exec-timeout 0 0 width 512 length 512

In this example, the following terminal attributes override the default line template default terminal attribute settings:

The EXEC timeout for terminal sessions is set to 0 minutes and 0 seconds. Setting the EXEC timeout

•

to 0 minutes and 0 seconds disables the EXEC timeout function; thus, the EXEC session for the terminal session will never time out (the default EXEC timeout for the default line template is 10 minutes).

The width of the terminal screen for the terminals referencing the default template is set to 512 characters

•

(the default width for the default line template is 80 characters).

The length, the number of lines that will display at one time on the terminal referencing the default

•

template, is set to 512 lines (the default length for the default line template is 24 lines).

Configuring a User-Defined Template to Reference the Default vty Pool: Example

This configuration example shows how to configure a user-defined line template (named test in this example) for vtys and to configure the line template test to reference the default vty pool:

line template test

exec-timeout 100 0 width 100 length 100 exit

vty-pool default 0 4 line-template test

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

Additional References

Implementing Physical and Virtual Terminals

Configuring a User-Defined Template to Reference a User-Defined vty Pool: Example

This configuration example shows how to configure a user-defined line template (named test2 in this example) for vtys and to configure the line template test to reference a user-defined vty pool (named pool1 in this example):

line template test2

exec-timeout 0 0 session-limit 10 session-timeout 100 transport input all transport output all exit

vty-pool pool1 5 50 line-template test2

Configuring a User-Defined Template to Reference the Fault Manager vty Pool: Example

This configuration example shows how to configure a user-defined line template (named test3 in this example) for vtys and to configure the line template test to reference the fault manager vty pool:

line template test3

width 110 length 100 session-timeout 100 exit vty-pool eem 100 106 line-template test3

Additional References

The following sections provide references related to implementing physical and virtual terminals on Cisco IOS XR software.

Implementing SNMP

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 used for the monitoring and management of devices in a network.

This module describes the tasks you need to implement SNMP on your Cisco IOS XR network.

Prerequisites for Implementing SNMP, page 19

•

Restrictions for SNMP use on Cisco IOS XR Software, page 19

•

Information about Implementing SNMP, page 20

•

Session MIB support on subscriber sessions , page 26

•

How to Implement SNMP on Cisco IOS XR Software, page 27

•

Prerequisites for Implementing SNMP

Restrictions for SNMP use on Cisco IOS XR Software

SNMP outputs are only 32-bits wide and therefore cannot display any information greater than 232. 232is equal to 4.29 Gigabits.

Note

A10 Gigabit interface is greater than 232, so if you are trying to display speed information regarding the interface, you might see concatenated results.

To display correct speed of an interface greater than 10 Gigabit, ifHighSpeed can be used.

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

Information about Implementing SNMP

To implement SNMP, you need to understand the concepts described in this section.

SNMP Functional Overview

The SNMP framework consists of three parts:

SNMP manager

•

SNMP agent

•

Management Information Base (MIB)

•

SNMP Manager

Implementing SNMP

SNMP Agent

MIB

The SNMP manager is the system used to control and monitor the activities of network hosts using SNMP. The most common managing system is called a network management system (NMS). The term NMS can be applied to either a dedicated device used for network management, or the applications used on such a device. A variety of network management applications are available for use with SNMP. These features range from simple command-line applications to feature-rich graphical user interfaces (such as the CiscoWorks 2000 line of products).

The SNMP agent is the software component within the managed device that maintains the data for the device and reports these data, as needed, to managing systems. The agent and MIB reside on the router. To enable the SNMP agent, you must define the relationship between the manager and the agent.

The Management Information Base (MIB) is a virtual information storage area for network management information, which consists of collections of managed objects. Within the MIB there are collections of related objects, defined in MIB modules. MIB modules are written in the SNMP MIB module language, as defined in STD 58, RFC 2578, RFC 2579, and RFC 2580. Note that individual MIB modules are also referred to as MIBs; for example, the Interfaces Group MIB (IF-MIB) is a MIB module within the MIB on your system.

The SNMP agent contains MIB variables whose values the SNMP manager can request or change through Get or Set operations. A manager can get a value from an agent or store a value into that agent. The agent gathers data from the MIB, the repository for information about device parameters and network data. The agent can also respond to manager requests to get or set data.

Figure 1 illustrates the communications relationship between the SNMP manager and agent. A manager can

send the agent requests to get and set MIB values. The agent can respond to these requests. Independent of

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

+ 158 hidden pages

Cisco NCS 5000 Series Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x

CONTENTS

Preface

Changes to this Document

Obtaining Documentation and Submitting a Service Request

New and Changed System Management Features

System Management Features Added or Modified in IOS XR Release 6.2.x

Configuring Manageability

Information about XML Manageability

How to Configure Manageability

Configuring the XML Agent

Configuration Examples for Manageability

Enabling VRF on an XML Agent: Examples

Implementing Physical and Virtual Terminals

Prerequisites for Implementing Physical and Virtual Terminals

Information About Implementing Physical and Virtual Terminals

Line Templates

Line Template Configuration Mode

Line Template Guidelines

Terminal Identification

vty Pools

How to Implement Physical and Virtual Terminals on Cisco IOS XR Software

Modifying Templates

Creating and Modifying vty Pools

Monitoring Terminals and Terminal Sessions

Craft Panel Interface

Configuration Examples for Implementing Physical and Virtual Terminals

Additional References

Implementing SNMP

Prerequisites for Implementing SNMP

Restrictions for SNMP use on Cisco IOS XR Software

Information about Implementing SNMP

SNMP Functional Overview

SNMP manager

SNMP agent