Downloads |
 Feedback
|
Table Of Contents
Implementing IPv6 for Network Management
Prerequisites for Implementing IPv6 for Network Management
Information About Implementing IPv6 for Network Management
TFTP File Downloading for IPv6
ping and traceroute Commands in IPv6
Cisco IOS XE IPv6 Embedded Management Components
How to Implement IPv6 for Network Management
Enabling Telnet Access to an IPv6 Router and Establishing a Telnet Session
Enabling SSH on an IPv6 Router
Configuring an SNMP Notification Server over IPv6
Configuring Cisco IOS XE IPv6 Embedded Management Components
Disabling HTTP Access to an IPv6 Router
Configuration Examples for Implementing IPv6 for Network Management
Examples: Enabling Telnet Access to an IPv6 Router Configuration
Examples: Configuring an SNMP Notification Server over IPv6
Feature Information for Implementing IPv6 for Network Management
Implementing IPv6 for Network Management
First Published: May 5, 2008Last Updated: July 25, 2011This document describes the concepts and commands used to manage Cisco applications over IPv6 and to implement IPv6 for network management. The copy, ping, telnet, and traceroute commands were modified to provide IPv6 management capability. Secure Shell (SSH) has been enhanced to provide support for IPv6 addresses that enable a Cisco router to accept and establish secure, encrypted connections with remote IPv6 nodes over an IPv6 transport.
Cisco IOS IPv6 embedded management components have IPv6-compliant operability in IPv6 and hybrid IPv6 and IPv4 networks. Cisco IOS embedded management components include system message logging (syslog), Cisco Networking Services (CNS) agents, Config logger, tool command language (TCL) and IP Service Level Agreements (SLAs).
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Implementing IPv6 for Network Management" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Implementing IPv6 for Network Management
•
•
•
•
Prerequisites for Implementing IPv6 for Network Management
•
•
•
Information About Implementing IPv6 for Network Management
•
•
•
Telnet Access over IPv6
The Telnet client and server in the Cisco IOS XE software support IPv6 connections. A user can establish a Telnet session directly to the router using an IPv6 Telnet client, or an IPv6 Telnet connection can be initiated from the router. A vty interface and password must be created in order to enable Telnet access to an IPv6 router.
TFTP IPv6 Support
The Trivial File Transfer Protocol (TFTP) is designed to transfer files over the network from one host to another using the most minimal set of functionality possible. TFTP uses a client-server model in which clients can request to copy files to or from a server. TFTP uses UDP over IPv4 or IPv6 as its transport, and can work over IPv4 and IPv6 network layers.
TFTP File Downloading for IPv6
IPv6 supports TFTP file downloading and uploading using the copy command. The copy command accepts a destination IPv6 address or IPv6 hostname as an argument and saves the running configuration of the router to an IPv6 TFTP server, as follows:
Router# copy running-config tftp://[3ffe:xxxx:c18:1:290:27ff:fe3a:9e9a]/running-configping and traceroute Commands in IPv6
The ping command accepts a destination IPv6 address or IPv6 hostname as an argument and sends Internet Control Message Protocol version 6 (ICMPv6) echo request messages to the specified destination. The ICMPv6 echo reply messages are reported on the console. Extended ping functionality is also supported in IPv6.
The traceroute command accepts a destination IPv6 address or IPv6 hostname as an argument and will generate IPv6 traffic to report each IPv6 hop used to reach the destination address.
SSH over an IPv6 Transport
SSH in IPv6 functions the same and offers the same benefits as SSH in IPv4. The SSH Server feature enables an SSH client to make a secure, encrypted connection to a Cisco router, and the SSH Client feature enables a Cisco router to make a secure, encrypted connection to another Cisco router or to any other device running an SSH server. IPv6 enhancements to SSH consist of support for IPv6 addresses that enable a Cisco router to accept and establish secure, encrypted connections with remote IPv6 nodes over an IPv6 transport.
SNMP over an IPv6 Transport
Simple Network Management Protocol (SNMP) can be configured over IPv6 transport so that an IPv6 host can perform SNMP queries and receive SNMP notifications from a device running Cisco IOS XE software for IPv6. The SNMP agent and related MIBs have been enhanced to support IPv6 addressing.
SNMP for IPv6 provides 3DES and AES are provided for message encryption.
Cisco IOS XE IPv6 MIBs
Cisco has long supported IP-MIB and IP-FORWARD-MIB in IPv4. CISCO-IETF-IP-MIB and CISCO-IETF-IP-FORWARDING-MIB are IPv6 MIBs that are defined as being protocol-independent, but are implemented only for IPv6 objects and tables. IP-MIB and IP-FORWARD-MIB were updated to RFC 4293 and RFC 4292 standards, as follows:
•
•
MIBs Supported for IPv6
The following MIBs are supported for IPv6:
•
•
•
•
•
•
•
•
•
CISCO-CONFIG-COPY-MIB and CISCO-FLASH-MIB support IPv6 addressing when either TFTP, remote copy protocol (rcp), or FTP is used.
The following MIB was added for the IPv6 over SNMP support feature:
•
The following MIBs have been modified for the IPv6 over SNMP support feature:
•
•
•
Cisco IOS XE IPv6 Embedded Management Components
This section describes Cisco IOS XE software embedded management components that have IPv6-compliant operability in IPv6 and hybrid IPv6 and IPv4 networks.
•
Syslog
The Cisco IOS XE software system message logging (syslog) process in IPv6 allows users to log syslog messages to external syslog servers and hosts with IPv6 addresses. This implementation allows user to specify an IPv4-based logging host (syslog server) by providing the host's IP address in IPv4 format (for example, 192.168.0.0) or IPv6 format (for example, 2001:DB8:A00:1::1/64).
TCL
Tool command language (TCL) is used in Cisco IOS XE software for IPv6 to support features such as embedded syslog manager (ESM), embedded event manager (EEM), interactive voice response (IVR), and tclsh parser mode. TCL supports both initiating (client) and listening (server) sockets.
CNS Agents
IPv6 addressing is supported in the Cisco Networking Services (CNS) subsystem. CNS is a foundation technology for linking users to networking services and provides the infrastructure for the automated configuration of large numbers of network devices. Many IPv6 networks are complex, with many devices, and each device must be configured individually. When standard configurations do not exist or have been modified, the time involved in initial installation and subsequent upgrading is considerable. Internet service providers (ISPs) need a method for sending out partial configurations to introduce new services.
To address all these issues, CNS was designed to provide "plug-and-play" network services using a central directory service and distributed agents. CNS features include CNS agents and a flow-through provisioning structure. CNS flow-through provisioning uses the CNS configuration and event agents to provide an automated workflow, eliminating the need for an onsite technician.
IPv6 addressing supports the CNS agents described in the following sections:
CNS Configuration Agent
The CNS configuration agent is involved in the initial configuration and subsequent partial configurations on a Cisco IOS XE device. The configuration agent uses a CNS configuration engine to provide methods for automating initial Cisco IOS XE device configurations, incremental configurations, and synchronized configuration updates, and the configuration engine reports the status of the configuration load as an event to which a network monitoring or workflow application can subscribe.
CNS Event Agent
The CNS event agent provides a transport connection to the CNS event bus for all other CNS agents. No event can be sent to the router by the configuration engine until the CNS event agent is operational and has successfully built a connection between the configuration engine and the router.
The event agent uses a CNS configuration engine to provide methods for automating initial Cisco IOS XE device configurations, incremental configurations, and synchronized configuration updates.
CNS EXEC Agent
The CNS EXEC agent allows a remote application to execute a CLI command in EXEC mode on a Cisco IOS device by sending an event message that contains the command.
CNS Image Agent
Administrators maintaining large networks of Cisco IOS XE devices need an automated mechanism to load image files onto large numbers of remote devices. Network management applications are useful to determine which images to run and how to manage images received from the Cisco online software center. Other image distribution solutions do not scale to cover thousands of devices and cannot distribute images to devices behind a firewall or using Network Address Translation (NAT). The CNS image agent enables the managed device to initiate a network connection and request an image download allowing devices using NAT, or behind firewalls, to access the image server.
The CNS image agent can be configured to use the CNS event bus. To use the CNS event bus, the CNS event agent must be enabled and connected to the CNS event gateway in the CNS Configuration Engine. The CNS image agent can also use an HTTP server that understands the CNS image agent protocol. Deployment of CNS image agent operations can use both the CNS event bus and an HTTP server.
Config Logger
Config logger tracks and reports configuration changes. Config logger supports two content types:
•
XML—The config logger uses Extensible Markup Language (XML) to report the configuration change details (for example, what changed, who changed it, when changes were made, parser return code (PRC) values, and incremental NVGEN results).
IP SLAs for IPv6
Cisco IOS IP Service Level Agreements (SLAs) are a portfolio of technology embedded in most devices that run Cisco IOS XE software that allows Cisco customers to analyze IPv6 service levels for IPv6 applications and services, to increase productivity, to lower operational costs, and to reduce the frequency of network outages. IP SLAs uses active traffic monitoring—the generation of traffic in a continuous, reliable, and predictable manner—for measuring network performance.
The following Cisco IOS IP SLAs are supported for IPv6:
•
•
•
•
UDP jitter operation—Used to proactively monitor VoIP quality levels in your network, allowing you to guarantee VoIP quality levels to your users in IPv4 or IPv6 networks.
How to Implement IPv6 for Network Management
•
•
•
•
Enabling Telnet Access to an IPv6 Router and Establishing a Telnet Session
Using either IPv4 or IPv6 transport, you can use Telnet to connect from a host to a router, from a router to a router, and from a router to a host.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Enabling SSH on an IPv6 Router
If you do not configure SSH parameters, then the default values will be used.
Prerequisites
Prior to configuring SSH over an IPv6 transport, ensure that the following conditions exist:
•
•
•
•
Restrictions
The basic restrictions for SSH over an IPv4 transport listed in the "Configuring Secure Shell" chapter of Cisco IOS XE Security Configuration Guide apply to SSH over an IPv6 transport. In addition to the restrictions listed in that chapter, the use of locally stored usernames and passwords is the only user authentication mechanism supported by SSH over an IPv6 transport; the TACACS+ and RADIUS user authentication mechanisms are not supported over an IPv6 transport.
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring an SNMP Notification Server over IPv6
Use an SNMP community string to define the relationship between the SNMP manager and the agent. The community string acts like a password to regulate access to the agent on the router. Optionally, you can specify one or more of the following characteristics associated with the string:
•
•
•
You can configure one or more community strings. To remove a specific community string, use the no snmp-server community command.
The snmp-server host command specifies which hosts will receive SNMP notifications and whether you want the notifications sent as traps or inform requests. The snmp-server enable traps command globally enables the production mechanism for the specified notification types (such as Border Gateway Protocol [BGP] traps, config traps, entity traps, and Hot Standby Router Protocol [HSRP] traps).
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Configuring Cisco IOS XE IPv6 Embedded Management Components
Most IPv6 embedded management components are enabled automatically when IPv6 is enabled and do not need further configuration. To configure syslog over IPv6 or disable HTTP access to a router, refer to the tasks in the following sections:
•
Configuring Syslog over IPv6
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Disabling HTTP Access to an IPv6 Router
HTTP access over IPv6 is automatically enabled if an HTTP server is enabled and the router has an IPv6 address. Perform this task if the HTTP server is not required and it should be disabled.
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Configuration Examples for Implementing IPv6 for Network Management
•
•
Examples: Enabling Telnet Access to an IPv6 Router Configuration
The following examples provide information on how to enable Telnet and start a session to or from an IPv6 router. In the following example, the IPv6 address is specified as 2001:DB8:20:1::12, and the hostname is specified as cisco-sj. The show host command is used to verify this information.
Router# configure terminalRouter(config)# ipv6 host cisco-sj 2001:DB8:20:1::12Router(config)# endRouter# show hostDefault domain is not setName/address lookup uses static mappingsCodes:UN - unknown, EX - expired, OK - OK, ?? - revalidatetemp - temporary, perm - permanentNA - Not Applicable None - Not definedHost Port Flags Age Type Address(es)cisco-sj None (perm, OK) 0 IPv6 2001:DB8:20:1::12To enable Telnet access to a router, create a vty interface and password:
Router(config)# line vty 0 4password labloginTo use Telnet to access the router, you must enter the password:
Router# telnet cisco-sjTrying cisco-sj (2001:DB8:20:1::12)... OpenUser Access VerificationPassword:cisco-sj...verificationIt is not necessary to use the telnet command. Specifying either the hostname or the address is sufficient, as shown in the following examples:
Router# cisco-sjor
Router# 2001:DB8:20:1::12To display the IPv6 connected user (line 130) on the router to which you are connected, use the show users command:
Router# show usersLine User Host(s) Idle Location* 0 con 0 idle 00:00:00130 vty 0 idle 00:00:22 8800::3Note that the address displayed is the IPv6 address of the source of the connection. If the hostname of the source is known (either through a domain name server [DNS] or locally in the host cache), then it is displayed instead:
Router# show usersLine User Host(s) Idle Location* 0 con 0 idle 00:00:00130 vty 0 idle 00:02:47 cisco-sjIf the user at the connecting router suspends the session with ^6x and then enters the show sessions command, the IPv6 connection is displayed:
Router# show sessionsConn Host Address Byte Idle Conn Name* 1 cisco-sj 2001:DB8:20:1::12 0 0 cisco-sjThe Conn Name field shows the hostname of the destination only if it is known. If it is not known, the output might look similar to the following:
Router# show sessionsConn Host Address Byte Idle Conn Name* 1 2001:DB8:20:1::12 2001:DB8:20:1::12 0 0 2001:DB8:20:1::12Examples: Configuring an SNMP Notification Server over IPv6
The following example permits any SNMP to access all objects with read-only permission using the community string named public. The router also will send BGP traps to the IPv4 host 172.16.1.111 and IPv6 host 3ffe:b00:c18:1::3/127 using SNMPv1 and to the host 172.16.1.27 using SNMPv2c. The community string named public is sent with the traps.
Router(config)# snmp-server community publicRouter(config)# snmp-server enable traps bgpRouter(config)# snmp-server host 172.16.1.27 version 2c publicRouter(config)# snmp-server host 172.16.1.111 version 1 publicRouter(config)# snmp-server host 3ffe:b00:c18:1::3/127 publicAssociate an SNMP Server Group with Specified Views Example
In the following example, the SNMP context A is associated with the views in SNMPv2c group GROUP1 and the IPv6 named access list public2:
Router(config)# snmp-server context ARouter(config)# snmp mib community-map commA context A target-list commAVpnRouter(config)# snmp mib target list commAVpn vrf Customer_ARouter(config)# snmp-server view viewA ciscoPingMIB includedRouter(config)# snmp-server view viewA ipForward includedRouter(config)# snmp-server group GROUP1 v2c context A read viewA write viewA notify access ipv6 public2Create an SNMP Notification Server Example
The following example configures the IPv6 host as the notification server:
Router> enableRouter# configure terminalRouter(config)# snmp-server community mgr view restricted rw ipv6 mgr2Router(config)# snmp-server engineID remote 3ffe:b00:c18:1::3/127 remotev6Router(config)# snmp-server group public v2c access ipv6 public2Router(cofig)# snmp-server host host1.com 2c vrf trap-vrfRouter(cofig)# snmp-server user user1 bldg1 remote 3ffe:b00:c18:1::3/127 v2c access ipv6 public2Router(config)# snmp-server enable traps bgpRouter(config)# exitAdditional References
Related Documents
IPv6 supported features
"Start Here: Cisco IOS XE Software Release Specifics for IPv6 Features," Cisco IOS XE IPv6 Configuration Guide
Basic IPv6 configuration tasks
"Implementing IPv6 Addressing and Basic Connectivity," Cisco IOS XE IPv6 Configuration Guide
IPv6 commands: complete command syntax, command mode, defaults, usage guidelines, and examples
SSH configuration information
Cisco IOS master command list, all releases
IP SLAs for IPv6
•
•
•
•
•
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
None
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Feature Information for Implementing IPv6 for Network Management
Table 12 lists the features in this module and provides links to specific configuration information.
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.
Note
Table 12 Feature Information for Managing Cisco IOS XE Applications over IPv6
CNS Agents for IPv6
Cisco IOS XE Release 2.1
CNS configuration and event agents use a CNS configuration engine to provide methods for automating initial Cisco IOS device configurations, incremental configurations, and synchronized configuration updates, and the configuration engine reports the status of the configuration load as an event to which a network monitoring or workflow application can subscribe.
The following section provides information about this feature:
IP SLAs for IPv6
Cisco IOS XE Release 2.1
IP SLAs are supported for IPv6.
The following section provides information about this feature:
IPv6 for Config Logger
Cisco IOS XE Release 2.1
Config logger tracks and reports configuration changes.
The following section provides information about this feature:
IPv6—Syslog over IPv6
Cisco IOS XE Release 2.1
The Cisco IOS syslog process in IPv6 allows users to log syslog messages to external syslog servers and hosts with IPv6 addresses.
The following section provides information about this feature:
The following command was modified by this feature: logging host
IPv6 Services—IP-FORWARD-MIB Support
Cisco IOS XE Release 2.1
A MIB is a database of objects that can be managed on a device. The managed objects, or variables, can be set or read to provide information on the network devices and interfaces.
The following section provides information on this feature:
IPv6 Services—IP-MIB Support
Cisco IOS XE Release 2.1
A MIB is a database of objects that can be managed on a device. The managed objects, or variables, can be set or read to provide information on the network devices and interfaces.
The following section provides information on this feature:
IPv6 Services—RFC 4293 IP-MIB (IPv6 only) and RFC 4292 IP-FORWARD-MIB (IPv6 only)
Cisco IOS XE Release 2.1
IP-FORWARD-MIB and IP-MIB were updated to RFC 4292 and RFC 4293 standards, respectively.
The following section provides information about this feature:
IPv6 Support for TCL
Cisco IOS XE Release 2.1
IPv6 supports TCL.
The following section provides information about this feature:
•
SNMP over IPv6
Cisco IOS XE Release 2.1
SNMP can be configured over IPv6 transport so that an IPv6 host can perform SNMP queries and receive SNMP notifications from a device running Cisco IOS IPv6.
The following section provides information about this feature:
•
•
The following commands were modified by this feature: snmp-server community, snmp-server engineID remote, snmp-server group, snmp-server host, snmp-server user
SSH over an IPv6 Transport
Cisco IOS XE Release 2.1
SSH in IPv6 functions the same and offers the same benefits as SSH in IPv4—the SSH Server feature enables an SSH client to make a secure, encrypted connection to a Cisco router and the SSH Client feature enables a Cisco router to make a secure, encrypted connection to another Cisco router or to any other device running an SSH server.
The following section provides information about this feature:
•
The following command was modified by this feature: ssh
Telnet Access over IPv6
Cisco IOS XE Release 2.1
The Telnet client and server in the Cisco IOS software support IPv6 connections. A user can establish a Telnet session directly to the router using an IPv6 Telnet client, or an IPv6 Telnet connection can be initiated from the router.
The following sections provide information about this feature:
•
•
•
The following commands were modified by this feature: ipv6 access-class, ipv6 host, show host, show sessions, show users, telnet
TFTP File Downloading for IPv6
Cisco IOS XE Release 2.1
IPv6 supports TFTP file downloading and uploading.
The following section provides information about this feature:
TFTP IPv6 Support
Cisco IOS XE Release 3.4S
TFTP uses UDP over IPv4 or IPv6 as its transport, and can work over IPv4 and IPv6 network layers.
The following section provides information about this feature:
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)
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.
© 2001-2011 Cisco Systems, Inc. All rights reserved.
