-
Cisco IOS IPv6 Command Reference
-
Introduction
-
aaa accounting multicast default through clear ipv6 mobile home-agents
-
clear ipv6 mobile traffic through debug bgp vpnv6 unicast
-
debug crypto ipv6 ipsec through debug ipv6 pim
-
debug ipv6 pim df-election through ip http server
-
ip name-server through ipv6 general-prefix
-
ipv6 hello-interval eigrp through ipv6 mld static-group
-
ipv6 mobile home-agent (global configuration) through ipv6 ospf database-filter all out
-
ipv6 ospf dead-interval through ipv6 split-horizon eigrp
-
ipv6 summary-address eigrp through mpls ldp router-id
-
mpls traffic-eng auto-bw timers through route-map
-
router-id (IPv6) through show bgp ipv6 labels
-
show bgp ipv6 neighbors through show crypto isakmp peers
-
show crypto isakmp policy through show ipv6 eigrp neighbors
-
show ipv6 eigrp topology through show ipv6 nat statistics
-
show ipv6 nat translations through show ipv6 protocols
-
show ipv6 rip through snmp-server host
-
snmp-server user through vrf forwarding
-
Table Of Contents
clear ipv6 multicast aaa authorization
clear mls cef ipv6 accounting per-prefix
clear ipv6 mobile traffic
To clear statistics associated with Mobile IPv6 traffic, use the clear ipv6 mobile traffic command in privileged EXEC mode.
clear ipv6 mobile traffic
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The clear ipv6 mobile traffic command clears the statistics about the received binding updates and transmitted binding acknowledgments on a mobile node.
Examples
In the following example, statistics about binding updates and binding acknowledgments are cleared:
Router# clear ipv6 mobile trafficRouter# show ipv6 mobile trafficMIPv6 statistics:Rcvd: 0 total0 truncated, 0 format errors0 checksum errorsBinding Updates received:00 no HA option, 0 BU's length0 options' length, 0 invalid CoASent: 0 generatedBinding Acknowledgements sent:00 accepted (0 prefix discovery required)0 reason unspecified, 0 admin prohibited0 insufficient resources, 0 home reg not supported0 not home subnet, 0 not home agent for node0 DAD failed, 0 sequence numberBinding Errors sent:00 no binding, 0 unknown MHHome Agent Traffic:0 registrations, 0 deregistrationsunknown time since last accepted HA registrationunknown time since last failed HA registrationunknown last failed registration codeTraffic forwarded:0 tunneled, 0 reversed tunneledDynamic Home Agent Address Discovery:0 requests received, 0 replies sentMobile Prefix Discovery:0 solicitations received, 0 advertisements sentRelated Commands
binding
Configures binding options for the Mobile IPv6 home agent feature in home agent configuration mode.
show ipv6 mobile home-agent
Displays neighboring home agents.
clear ipv6 multicast aaa authorization
To clear parameters that restrict user access to an IPv6 multicast network, use the clear ipv6 multicast aaa authorization command in privileged EXEC mode.
clear ipv6 multicast aaa authorization [interface-type interface-number]
Syntax Description
interface-type interface-number
Interface type and number. For more information, use the question mark (?) online help function.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Using the clear ipv6 multicast aaa authorization command without the optional interface-type and interface-number arguments will clear all authorization parameters on a network.
Examples
The following example clears all configured authorization parameters on an IPv6 network:
Router# clear ipv6 multicast aaa authorization FastEthernet 1/0Related Commands
aaa authorization multicast default
Sets parameters that restrict user access to an IPv6 multicast network.
clear ipv6 nat translation
To clear dynamic Network Address Translation—Protocol Translation (NAT-PT) translations from the dynamic state table, use the clear ipv6 nat translation command in privileged EXEC mode.
clear ipv6 nat translation *
Syntax Description
Command Default
Entries are deleted from the dynamic translation state table when they time out.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to clear entries from the dynamic translation state table before they time out. Static translation configuration is not affected by this command.
Examples
The following example shows the NAT-PT entries before and after the dynamic translation state table is cleared. Note that all the dynamic NAT-PT mappings are cleared, but the static NAT-PT configurations remain.
Router# show ipv6 nat translationsProt IPv4 source IPv6 sourceIPv4 destination IPv6 destination--- --- ---192.168.123.2 2001::2--- --- ---192.168.122.10 2001::10tcp 192.168.124.8,11047 3002::8,11047192.168.123.2,23 2001::2,23udp 192.168.124.8,52922 3002::8,52922192.168.123.2,69 2001::2,69Router# clear ipv6 nat translation *Router# show ipv6 nat translationsProt IPv4 source IPv6 sourceIPv4 destination IPv6 destination--- --- ---192.168.123.2 2001::2--- --- ---192.168.122.10 2001::10Related Commands
ipv6 nat
Designates that traffic originating from or destined for the interface is subject to NAT-PT.
show ipv6 nat translations
Displays active NAT-PT translations.
clear ipv6 neighbors
To delete all entries in the IPv6 neighbor discovery cache, except static entries, use the clear ipv6 neighbors command in privileged EXEC mode.
clear ipv6 neighbors
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example deletes all entries, except static entries, in the neighbor discovery cache:
Router# clear ipv6 neighborsRelated Commands
ipv6 neighbor
Configures a static entry in the IPv6 neighbor discovery cache.
show ipv6 neighbors
Displays IPv6 neighbor discovery cache information.
clear ipv6 nhrp
To clear all dynamic entries from the Next Hop Resolution Protocol (NHRP) cache, use the clear ipv6 nhrp command in privileged EXEC mode.
clear ipv6 nhrp [ipv6-address | counters]
Syntax Description
ipv6-address
(Optional) The IPv6 network to delete.
counters
(Optional) Specifies NHRP counters to delete.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command does not clear any static (configured) IPv6-to-nonbroadcast multiaccess (NBMA) address mappings from the NHRP cache.
Examples
The following example shows how to clear all dynamic entries from the NHRP cache for the interface:
Router# clear ipv6 nhrpRelated Commands
clear ipv6 ospf
To clear the Open Shortest Path First (OSPF) state based on the OSPF routing process ID, use the clear ipv6 ospf command in privileged EXEC mode.
clear ipv6 ospf [process-id] {process | force-spf | redistribution}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
When the process keyword is used with the clear ipv6 ospf command, the OSPF database is cleared and repopulated, and then the shortest path first (SPF) algorithm is performed. When the force-spf keyword is used with the clear ipv6 ospf command, the OSPF database is not cleared before the SPF algorithm is performed.
Use the process-id option to clear only one OSPF process. If the process-id option is not specified, all OSPF processes are cleared.
Examples
The following example starts the SPF algorithm without clearing the OSPF database:
Router# clear ipv6 ospf force-spfclear ipv6 ospf counters
To clear the Open Shortest Path First (OSPF) state based on the OSPF routing process ID, use the clear ipv6 ospf command in privileged EXEC mode.
clear ipv6 ospf [process-id] counters [neighbor [neighbor-interface | neighbor-id]]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the neighbor neighbor-interface option to clear counters for all neighbors on a specified interface. If the neighbor neighbor-interface option is not used, all OSPF counters are cleared.
Use the neighbor neighbor-id option to clear counters at a specified neighbor. If the neighbor neighbor-id option is not used, all OSPF counters are cleared.
Examples
The following example provides detailed information on a neighbor router:
Router# show ipv6 ospf neighbor detailNeighbor 10.0.0.1In the area 1 via interface Serial19/0Neighbor:interface-id 21, link-local address FE80::A8BB:CCFF:FE00:6F00Neighbor priority is 1, State is FULL, 6 state changesOptions is 0x194AE05Dead timer due in 00:00:37Neighbor is up for 00:00:15Index 1/1/1, retransmission queue length 0, number of retransmission 1First 0x0(0)/0x0(0)/0x0(0) Next 0x0(0)/0x0(0)/0x0(0)Last retransmission scan length is 1, maximum is 1Last retransmission scan time is 0 msec, maximum is 0 msecThe following example clears all neighbors on the specified interface:
Router# clear ipv6 ospf counters neighbor s19/0The following example now shows that there have been 0 state changes since the clear ipv6 ospf counters neighbor s19/0 command was used:
Router# show ipv6 ospf neighbor detailNeighbor 10.0.0.1In the area 1 via interface Serial19/0Neighbor:interface-id 21, link-local address FE80::A8BB:CCFF:FE00:6F00Neighbor priority is 1, State is FULL, 0 state changesOptions is 0x194AE05Dead timer due in 00:00:39Neighbor is up for 00:00:43Index 1/1/1, retransmission queue length 0, number of retransmission 1First 0x0(0)/0x0(0)/0x0(0) Next 0x0(0)/0x0(0)/0x0(0)Last retransmission scan length is 1, maximum is 1Last retransmission scan time is 0 msec, maximum is 0 msecRelated Commands
show ipv6 ospf neighbor
Displays OSPF neighbor information on a per-interface basis.
clear ipv6 ospf events
To clear the Open Shortest Path First (OSPF) for IPv6 event log content based on the OSPF routing process ID, use the clear ipv6 ospf events command in privileged EXEC mode.
clear ipv6 ospf [process-id] events
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(33)SRC
This command was introduced.
12.2(33)SB
This command was integrated into Cisco IOS Release 12.2(33)SB.
Usage Guidelines
Use the optional process-id argument to clear the IPv6 event log content of a specified OSPF routing process. If the process-id argument is not used, all event log content is cleared.
Examples
The following example enables the clearing of OSPF for IPv6 event log content for routing process 1:
Router# clear ipv6 ospf 1 eventsclear ipv6 pim counters
To reset the Protocol Independent Multicast (PIM) traffic counters, use the clear ipv6 pim counters command in privileged EXEC mode.
clear ipv6 pim counters
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Using the clear ipv6 pim counters command will reset all PIM traffic counters.
Examples
The following example resets the PIM traffic counters:
Router# clear ipv6 pim countersRelated Commands
clear ipv6 pim reset
To delete all entries from the topology table and reset the Multicast Routing Information Base (MRIB) connection, use the clear ipv6 pim reset command in privileged EXEC mode.
clear ipv6 pim reset
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Using the clear ipv6 pim reset command breaks the PIM-MRIB connection, clears the topology table, and then reestablishes the PIM-MRIB connection. This procedure forces MRIB resynchronization.
CautionUse the clear ipv6 pim reset command with caution, as it clears all PIM protocol information from the PIM topology table. Use of the clear ipv6 pim reset command should be reserved for situations where PIM and MRIB communication are malfunctioning.
Examples
The following example deletes all entries from the topology table and resets the MRIB connection:
Router# clear ipv6 pim resetclear ipv6 pim topology
To clear the Protocol Independent Multicast (PIM) topology table, use the clear ipv6 pim topology command in privileged EXEC mode.
clear ipv6 pim topology [group-name | group-address]
Syntax Description
Command Default
When the command is used with no arguments, all group entries located in the PIM topology table are cleared of PIM protocol information.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command clears PIM protocol information from all group entries located in the PIM topology table. Information obtained from the MRIB table is retained. If a multicast group is specified, only those group entries are cleared.
Examples
The following example clears all group entries located in the PIM topology table:
Router# clear ipv6 pim topologyclear ipv6 prefix-list
To reset the hit count of the IPv6 prefix list entries, use the clear ipv6 prefix-list command in privileged EXEC mode.
clear ipv6 prefix-list [prefix-list-name] [ipv6-prefix/prefix-length]
Syntax Description
Command Default
The hit count is automatically cleared for all IPv6 prefix lists.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The clear ipv6 prefix-list command is similar to the clear ip prefix-list command, except that it is IPv6-specific.
The hit count is a value indicating the number of matches to a specific prefix list entry.
Examples
The following example clears the hit count from the prefix list entries for the prefix list named first_list that match the network mask 2001:0DB8::/35.
Router# clear ipv6 prefix-list first_list 2001:0DB8::/35Related Commands
clear ipv6 rip
To delete routes from the IPv6 Routing Information Protocol (RIP) routing table, use the clear ipv6 rip command in privileged EXEC mode.
clear ipv6 rip [name]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
When the name argument is specified, only routes for that process are deleted from the IPv6 RIP routing table and, if installed, from the IPv6 routing table. If no name argument is specified, all IPv6 RIP routes are deleted.
Use the show ipv6 rip command to display IPv6 RIP routes.
Examples
The following example deletes all the IPv6 routes for the RIP process called one:
Router# clear ipv6 rip oneRelated Commands
clear ipv6 route
To delete routes from the IPv6 routing table, use the clear ipv6 route command in privileged EXEC mode.
clear ipv6 route {ipv6-address | ipv6-prefix/prefix-length | *}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The clear ipv6 route command is similar to the clear ip route command, except that it is IPv6-specific.
When the ipv6-address or ipv6-prefix/prefix-length argument is specified, only that route is deleted from the IPv6 routing table. When the * keyword is specified, all routes are deleted from the routing table (the per-destination maximum transmission unit [MTU] cache is also cleared).
Examples
The following example deletes the IPv6 network 2001:0DB8::/35:
Router# clear ipv6 route 2001:0DB8::/35Related Commands
ipv6 route
Establishes static IPv6 routes.
show ipv6 route
Displays the current contents of the IPv6 routing table.
clear ipv6 traffic
To reset IPv6 traffic counters, use the clear ipv6 traffic command in privileged EXEC mode.
clear ipv6 traffic [interface-type interface-number]
Syntax Description
interface-type interface-number
Interface type and number. For more information, use the question mark (?) online help function.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Using this command resets the counters in the output from the show ipv6 traffic command.
Examples
The following example resets the IPv6 traffic counters. The output from the show ipv6 traffic command shows that the counters are reset:
Router# clear ipv6 trafficRouter# show ipv6 trafficIPv6 statistics:Rcvd: 1 total, 1 local destination0 source-routed, 0 truncated0 format errors, 0 hop count exceeded0 bad header, 0 unknown option, 0 bad source0 unknown protocol, 0 not a router0 fragments, 0 total reassembled0 reassembly timeouts, 0 reassembly failuresSent: 1 generated, 0 forwarded0 fragmented into 0 fragments, 0 failed0 encapsulation failed, 0 no route, 0 too bigMcast: 0 received, 0 sentICMP statistics:Rcvd: 1 input, 0 checksum errors, 0 too short0 unknown info type, 0 unknown error typeunreach: 0 routing, 0 admin, 0 neighbor, 0 address, 0 portparameter: 0 error, 0 header, 0 option0 hopcount expired, 0 reassembly timeout,0 too big0 echo request, 0 echo reply0 group query, 0 group report, 0 group reduce0 router solicit, 0 router advert, 0 redirects0 neighbor solicit, 1 neighbor advertSent: 1 outputunreach: 0 routing, 0 admin, 0 neighbor, 0 address, 0 portparameter: 0 error, 0 header, 0 option0 hopcount expired, 0 reassembly timeout,0 too big0 echo request, 0 echo reply0 group query, 0 group report, 0 group reduce0 router solicit, 0 router advert, 0 redirects0 neighbor solicit, 1 neighbor advertUDP statistics:Rcvd: 0 input, 0 checksum errors, 0 length errors0 no port, 0 droppedSent: 0 outputTCP statistics:Rcvd: 0 input, 0 checksum errorsSent: 0 output, 0 retransmittedRelated Commands
clear mls cef ipv6 accounting per-prefix
To clear information about the IPv6 per-prefix accounting statistics, use the clear mls cef ipv6 accounting per-prefix command in privileged EXEC mode.
clear mls cef ipv6 accounting per-prefix {all | ipv6-address/mask [instance]}
Syntax Description
Command Default
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
When entering the ipv6-address/mask arguments, use this format, X:X:X:X::X/mask, where the valid values for mask are from 0 to 128.
Examples
This example shows how to clear all information about the per-prefix accounting statistics:
Router# clear mls cef ipv6 accounting per-prefix allcontext
To associate a Simple Network Management Protocol (SNMP) context with a particular virtual private network (VPN) routing and forwarding (VRF) instance, use the context command in VRF configuration mode. To disassociate an SNMP context from a VPN, use the no form of this command.
context context-name
no context context-name
Syntax Description
Command Default
No SNMP contexts are associated with VPNs.
Command Modes
VRF configuration
Command History
Usage Guidelines
Before you use this command to associate an SNMP context with a VPN, you must do the following:
•
•
•
SNMP contexts provide VPN users with a secure way of accessing MIB data. When a VPN is associated with a context, MIB data for that VPN exists in that context. Associating a VPN with a context helps enable service providers to manage networks with multiple VPNs. Creating and associating a context with a VPN enables a provider to prevent the users of one VPN from accessing information about users of other VPNs on the same networking device.
A route distinguisher (RD) is required when you configure an SNMP context. An RD creates routing and forwarding tables and specifies the default route distinguisher for a VPN. The RD is added to the beginning of a IPv4 prefix to make it globally unique. An RD is either ASN relative, which means it is composed of an autonomous system number and an arbitrary number, or it is IP address relative and composed of an IP address and an arbitrary number.
Examples
The following example shows how to create an SNMP context named context1 and associate the context with the VRF named vrf1:
Router(config)# snmp-server context1Router(config)# ip vrf vrf1Router(config-vrf)# rd 100:120Router(config-vrf)# context context1Related Commands
copy
To copy any file from a source to a destination, use the copy command in privileged EXEC or diagnostic mode.
copy [/erase] [/verify | /noverify] source-url destination-url
Syntax Description
The exact format of the source and destination URLs varies according to the file or directory location. You may enter either an alias keyword for a particular file or a filename that follows the standard Cisco IOS file system syntax (filesystem:[/filepath][/filename]).
Table 9 shows two keyword shortcuts to URLs.
The following tables list URL prefix keywords by file system type. The available file systems will vary by platform. If you do not specify a URL prefix keyword, the router looks for a file in the current directory.
Table 10 lists URL prefix keywords for Special (opaque) file systems. Table 11 lists them for remote file systems, and Table 12 lists them for local writable storage.
