- Implementing IPv6 Addressing and Basic Connectivity
- Implementing ADSL for IPv6
- Implementing Bidirectional Forwarding Detection for IPv6
- Implementing DHCP for IPv6
- Implementing EIGRP for IPv6
- Configuring First Hop Redundancy Protocols in IPv6
- Implementing IPsec in IPv6 Security
- Implementing IS-IS for IPv6
- Implementing IPv6 for Network Management
- Implementing IPv6 over MPLS
- Implementing IPv6 VPN over MPLS
- Implementing IPv6 Multicast
- PIMv6 Anycast RP Solution
- Implementing Multiprotocol BGP for IPv6
- Implementing NAT-PT for IPv6
- Implementing OSPFv3
- Implementing Policy-Based Routing for IPv6
- Implementing QoS for IPv6
- Implementing RIP for IPv6
- Implementing Selective Packet Discard in IPv6
- Implementing Static Routes for IPv6
- Implementing Traffic Filters for IPv6 Security
- IPv6 ACL Extensions for Hop by Hop Filtering
- Implementing Tunneling for IPv6
- IPv6 Virtual Fragmentation Reassembly
- IPv6 RFCs
- Finding Feature Information
- Information About Implementing IPv6 for Network Management
Implementing IPv6 for Network Management
This document describes the concepts and commands used to manage Cisco applications over IPv6 and to implement IPv6 for network management.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and 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 table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Information About Implementing IPv6 for Network Management
- Telnet Access over IPv6
- TFTP IPv6 Support
- ping and traceroute Commands in IPv6
- SSH over an IPv6 Transport
- SNMP over an IPv6 Transport
- Cisco IOS XE IPv6 Embedded Management Components
Telnet Access over IPv6
The Telnet client and server in Cisco software support IPv6 connections. A user can establish a Telnet session directly to the device using an IPv6 Telnet client, or an IPv6 Telnet connection can be initiated from the device. A vty interface and password must be created in order to enable Telnet access to an IPv6 device.
TFTP IPv6 Support
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 it 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 device to an IPv6 TFTP server, as follows:
Device# copy running-config tftp://[3ffe:xxxx:c18:1:290:27ff:fe3a:9e9a]/running-config
ping 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
Secure shell (SSH) 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 device, and the SSH client feature enables a Cisco device to make a secure, encrypted connection to another Cisco device or to any other device running an SSH server. IPv6 enhancements to SSH consist of support for IPv6 addresses that enable a Cisco device 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 IPv6 software. The SNMP agent and related MIBs have been enhanced to support IPv6 addressing. This feature uses the data encryption standard (3DES) and advanced encryption standard (AES) 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:
- The upgrade is backward-compatible; all IP-MIB and IP-FORWARD-MIB objects and tables still appear.
- IP-MIB and IP-FORWARD-MIB include new IPv6-only, IPv4-only, and protocol-version independent (PVI) objects and tables. However, IPv6 supports IPv6-only and the new IPv6 part of the PVI objects and tables in these MIBs.
MIBs Supported for IPv6
The following MIBs are supported for IPv6:
- CISCO-CONFIG-COPY-MIB
- CISCO-CONFIG-MAN-MIB
- CISCO-DATA-COLLECTION-MIB
- CISCO-FLASH-MIB
- CISCO-SNMP-TARGET-EXT-MIB
- ENTITY-MIB
- IP-FORWARD-MIB
- IP-MIB
- NOTIFICATION-LOG-MIB
- SNMP-TARGET-MIB
CISCO-CONFIG-COPY-MIB and CISCO-FLASH-MIB support IPv6 addressing when TFTP, remote copy protocol (rcp), or FTP is used.
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 dual-stack IPv6 and IPv4 networks.
Syslog
The Cisco 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 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 it 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. 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 device. The configuration agent uses a CNS configuration engine to provide methods for automating initial Cisco 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 device by the configuration engine until the CNS event agent is operational and has successfully built a connection between the configuration engine and the device.
The event agent uses a CNS configuration engine to provide methods for automating initial Cisco 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 device by sending an event message that contains the command.
CNS Image Agent
Administrators maintaining large networks of Cisco 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:
IP SLAs for IPv6
Cisco IP Service Level Agreements (SLAs) are a portfolio of technology embedded in most devices that run Cisco software that allows Cisco customers to analyze IPv6 service levels for IPv6 applications and services, increase productivity, lower operational costs, and 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 IP SLAs are supported for IPv6:
- Internet Control Message Protocol (ICMP) echo operation--Used to monitor end-to-end response time between a Cisco device and other devices using IPv4 or IPv6. ICMP echo is useful for troubleshooting network connectivity issues.
- TCP connect operation--Used to measure the response time taken to perform a TCP Connect operation between a Cisco device and other devices using IPv4 or IPv6.
- User Datagram Protocol (UDP) echo operation--Used to monitor end-to-end response time between a Cisco router and devices using IPv4 or IPv6 .
- UDP jitter operation--Used to analyze round-trip delay, one-way delay, one-way jitter, one-way packet loss, and connectivity in networks that carry UDP traffic in IPv4 or IPv6 networks.
-
UDP jitter operation--Used to 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 Device 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
Enabling Telnet Access to an IPv6 Device and Establishing a Telnet Session
DETAILED STEPS
Enabling SSH on an IPv6 Router
If you do not configure SSH parameters, then the default values will be used.
Prior to configuring SSH over an IPv6 transport, ensure that the following conditions exist:
- An IPsec (Data Encryption Standard [DES] or 3DES) encryption software image is loaded on your router. IPv6 transport for the SSH server and SSH client requires an IPsec encryption software image.
- A hostname and host domain are configured for your router. Refer to the "Mapping Hostnames to IPv6 Addresses" section of Implementing IPv6 Addressing and Basic Connectivity for information on assigning hostnames to IPv6 addresses and specifying default domain names that can be used by both IPv4 and IPv6.
- A Rivest, Shamir, and Adelman (RSA) key pair, which automatically enables SSH, is generated for your router. RSA is the public key cryptographic system developed by Ron Rivest, Adi Shamir, and Leonard Adelman. RSA keys come in pairs: one public key and one private key.
- A user authentication mechanism for local or remote access is configured on your router.
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
|
Example: Router# configure terminal |
Enters global configuration mode. |
|
Example: Router(config)# ip ssh timeout 100 authentication-retries 2 |
Configures SSH control variables on your router.
By default, five vty lines are defined (0-4); therefore, five terminal sessions are possible. After the SSH executes a shell, the vty timeout starts. The vty timeout defaults to 10 minutes. |
|
Example: Router(config)# exit |
Exits configuration mode, and returns the router to privileged EXEC mode. |
|
Example: Router# ssh |
Starts an encrypted session with a remote networking device. |
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:
- An access list of IP addresses of the SNMP managers that are permitted to use the community string to gain access to the agent.
- A MIB view, which defines the subset of all MIB objects accessible to the given community.
- Read and write or read-only permission for the MIB objects accessible to the community.
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).
DETAILED STEPS
Command or Action | Purpose | |||
---|---|---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode.
|
||
|
Example: Router# configure terminal |
Enters global configuration mode. |
||
|
Example: Router(config)# snmp-server community mgr view restricted rw ipv6 mgr2 |
Defines the community access string. |
||
|
Example: Router(config)# snmp-server engineID remote 3ffe:b00:c18:1::3/127 remotev6 |
(Optional) Specifies the name of the remote SNMP engine (or copy of SNMP). |
||
|
Example: Router(config)# snmp-server group public v2c access ipv6 public2 |
(Optional) Configures a new SNMP group, or a table that maps SNMP users to SNMP views. |
||
|
Example: Router(config)# snmp-server host host1.com 2c vrf trap-vrf |
Specifies the recipient of an SNMP notification operation. Specifies whether you want the SNMP notifications sent as traps or informs, the version of SNMP to use, the security level of the notifications (for SNMPv3), and the recipient (host) of the notifications. |
||
|
Example: Router(config)# snmp-server user user1 bldg1 remote 3ffe:b00:c18:1::3/127 v2c access ipv6 public2 |
(Optional) Configures a new user to an existing SNMP group.
|
||
|
Example: Router(config)# snmp-server enable traps bgp |
Enables sending of traps or informs, and specifies the type of notifications to be sent.
|
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
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Device> enable |
Enables privileged EXEC mode. |
|
Example: Device# configure terminal |
Enters global configuration mode. |
|
Example: Device(config)# logging host ipv6 AAAA:BBBB:CCCC:DDDD::FFFF |
Logs system messages and debug output to a remote host. |
Disabling HTTP Access to an IPv6 Device
HTTP access over IPv6 is automatically enabled if an HTTP server is enabled and the device has an IPv6 address. If the HTTP server is not required, it should be disabled.
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Device> enable |
Enables privileged EXEC mode. |
|
Example: Device# configure terminal |
Enters global configuration mode. |
|
Example: Device(config)# no ip http server |
Disables HTTP access. |
Configuration Examples for Implementing IPv6 for Network Management
- Examples: Enabling Telnet Access to an IPv6 Device
- Examples: Configuring an SNMP Notification Server over IPv6
Examples: Enabling Telnet Access to an IPv6 Device
The following examples provide information on how to enable Telnet and start a session to or from an IPv6 device. 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.
Device# configure terminal Device(config)# ipv6 host cisco-sj 2001:DB8:20:1::12 Device(config)# end Device# show host Default domain is not set Name/address lookup uses static mappings Codes:UN - unknown, EX - expired, OK - OK, ?? - revalidate temp - temporary, perm - permanent NA - Not Applicable None - Not defined Host Port Flags Age Type Address(es) cisco-sj None (perm, OK) 0 IPv6 2001:DB8:20:1::12
To enable Telnet access to a device, create a vty interface and password:
Device(config)# line vty 0 4 password lab login
To use Telnet to access the device, you must enter the password:
Device# telnet cisco-sj
Trying cisco-sj (2001:DB8:20:1::12)... Open
User Access Verification
Password:
cisco-sj
.
.
.
verification
It is not necessary to use the telnet command. Specifying either the hostname or the address is sufficient, as shown in the following examples:
Device# cisco-sj
or
Device# 2001:DB8:20:1::12
To display the IPv6 connected user (line 130) on the device to which you are connected, use the show users command:
Device# show users
Line User Host(s) Idle Location
* 0 con 0 idle 00:00:00
130 vty 0 idle 00:00:22 8800::3
Note 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:
Device# show users
Line User Host(s) Idle Location
* 0 con 0 idle 00:00:00
130 vty 0 idle 00:02:47 cisco-sj
If the user at the connecting device suspends the session with ^6x and then enters the show sessions command, the IPv6 connection is displayed:
Device# show sessions
Conn Host Address Byte Idle Conn Name
* 1 cisco-sj 2001:DB8:20:1::12 0 0 cisco-sj
The 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:
Device# show sessions
Conn Host Address Byte Idle Conn Name
* 1 2001:DB8:20:1::12 2001:DB8:20:1::12 0 0 2001:DB8:20:1::12
Examples: 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 device also will send Border Gateway Protocol (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 will be sent with the traps.
Device(config)# snmp-server community public Device(config)# snmp-server enable traps bgp Device(config)# snmp-server host 172.16.1.27 version 2c public Device(config)# snmp-server host 172.16.1.111 version 1 public Device(config)# snmp-server host 3ffe:b00:c18:1::3/127 public
Example: Associate an SNMP Server Group with Specified Views
In the following example, the SNMP context A is associated with the views in SNMPv2c group GROUP1 and the IPv6 named access list public2:
Device(config)# snmp-server context A Device(config)# snmp mib community-map commA context A target-list commAVpn Device(config)# snmp mib target list commAVpn vrf CustomerA Device(config)# snmp-server view viewA ciscoPingMIB included Device(config)# snmp-server view viewA ipForward included Device(config)# snmp-server group GROUP1 v2c context A read viewA write viewA notify access ipv6 public2
Example: Create an SNMP Notification Server
The following example configures the IPv6 host as the notification server:
Device> enable Device# configure terminal Device(config)# snmp-server community mgr view restricted rw ipv6 mgr2 Device(config)# snmp-server engineID remote 3ffe:b00:c18:1::3/127 remotev6 Device(config)# snmp-server group public v2c access ipv6 public2 Device(config)# snmp-server host host1.com 2c vrf trap-vrf Device(config)# snmp-server user user1 bldg1 remote 3ffe:b00:c18:1::3/127 v2c access ipv6 public2 Device(config)# snmp-server enable traps bgp Device(config)# exit
Additional References
Related Documents
Related Topic |
Document Title |
---|---|
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 |
Cisco IOS IPv6 Command Reference |
SSH configuration information |
Cisco IOS Security Command Reference |
Cisco IOS master command list, all releases |
|
IP SLAs for IPv6 |
|
Standards
Standards |
Title |
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
-- |
MIBs
MIBs |
MIBs Link |
---|---|
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
RFCs |
Title |
---|---|
RFC 1350 |
The TFTP Protocol (Revision 2) |
RFC 2732 |
Format for Literal IPv6 Addresses in URLs |
RFC 3414 |
User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) |
RFC 3484 |
Default Address Selection for Internet Protocol version 6 (IPv6) |
RFC 4292 |
IP Forwarding Table MIB |
RFC 4293 |
Management Information Base for the Internet Protocol (IP) |
Technical Assistance
Description |
Link |
---|---|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
http://www.cisco.com/cisco/web/support/index.html |
Feature Information for Implementing IPv6 for Network Management
The following table provides release information about the feature or features described in this module. This table 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.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1 | Feature Information for Managing Cisco IOS XE Applications over IPv6 |
Feature Name |
Releases |
Feature Information |
---|---|---|
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. |
IP SLAs for IPv6 |
Cisco IOS XE Release 2.1
|
IP SLAs are supported for IPv6. |
IPv6 for Config Logger |
Cisco IOS XE Release 2.1 |
Config logger tracks and reports configuration changes. |
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 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. |
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. |
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. |
IPv6 Support for TCL |
Cisco IOS XE Release 2.1 |
IPv6 supports TCL. |
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 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 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 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. |
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. |
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: 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)
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.