Table Of Contents
clear ipv6 mobile traffic
clear ipv6 multicast aaa authorization
clear ipv6 nat translation
clear ipv6 neighbors
clear ipv6 ospf
clear ipv6 ospf counters
clear ipv6 pim counters
clear ipv6 pim reset
clear ipv6 pim topology
clear ipv6 prefix-list
clear ipv6 rip
clear ipv6 route
clear ipv6 traffic
clear mls cef ipv6 accounting per-prefix
context
copy
crypto ipsec profile
crypto isakmp identity
crypto isakmp key
crypto isakmp peer
crypto isakmp policy
crypto isakmp profile
crypto keyring
ctunnel mode
debug adjacency
debug bgp ipv6 dampening
debug bgp ipv6 updates
debug bgp vpnv6 unicast
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
Release
|
Modification
|
12.3(14)T
|
This command was introduced.
|
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 traffic
Router# show ipv6 mobile traffic
0 truncated, 0 format errors
Binding Updates received:0
0 no HA option, 0 BU's length
0 options' length, 0 invalid CoA
Binding Acknowledgements sent:0
0 accepted (0 prefix discovery required)
0 reason unspecified, 0 admin prohibited
0 insufficient resources, 0 home reg not supported
0 not home subnet, 0 not home agent for node
0 DAD failed, 0 sequence number
0 no binding, 0 unknown MH
0 registrations, 0 deregistrations
unknown time since last accepted HA registration
unknown time since last failed HA registration
unknown last failed registration code
0 tunneled, 0 reversed tunneled
Dynamic Home Agent Address Discovery:
0 requests received, 0 replies sent
0 solicitations received, 0 advertisements sent
Related Commands
Command
|
Description
|
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
Release
|
Modification
|
12.4(4)T
|
This command was introduced.
|
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/0
Related Commands
Command
|
Description
|
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
*
|
Clears all dynamic NAT-PT translations.
|
Command Default
Entries are deleted from the dynamic translation state table when they time out.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(13)T
|
This command was introduced.
|
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 translations
Prot IPv4 source IPv6 source
IPv4 destination IPv6 destination
tcp 192.168.124.8,11047 3002::8,11047
192.168.123.2,23 2001::2,23
udp 192.168.124.8,52922 3002::8,52922
192.168.123.2,69 2001::2,69
Router# clear ipv6 nat translation *
Router# show ipv6 nat translations
Prot IPv4 source IPv6 source
IPv4 destination IPv6 destination
Related Commands
Command
|
Description
|
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 keywords or arguments.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
12.0(21)ST
|
This command was integrated into Cisco IOS Release 12.0(21)ST.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(25)SG
|
This command was integrated into Cisco IOS Release 12.2(25)SG.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
Examples
The following example deletes all entries, except static entries, in the neighbor discovery cache:
Router# clear ipv6 neighbors
Related Commands
Command
|
Description
|
ipv6 neighbor
|
Configures a static entry in the IPv6 neighbor discovery cache.
|
show ipv6 neighbors
|
Displays IPv6 neighbor discovery cache information.
|
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
process-id
|
(Optional) Internal identification. It is locally assigned and can be any positive integer. The number used here is the number assigned administratively when enabling the OSPF routing process.
|
process
|
Restarts the OSPF process.
|
force-spf
|
Starts the shortest path first (SPF) algorithm without first clearing the OSPF database.
|
redistribution
|
Clears OSPF route redistribution.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(24)S
|
This command was introduced.
|
12.2(15)T
|
This command was integrated into Cisco IOS Release 12.2(15)T.
|
12.2(18)S
|
This command was integrated into Cisco IOS Release 12.2(18)S.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
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-spf
clear 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
process-id
|
(Optional) Internal identification. It is locally assigned and can be any positive integer. The number used here is the number assigned administratively when enabling the OSPF routing process.
|
neighbor
|
(Optional) Neighbor statistics per interface or neighbor ID.
|
neighbor-interface
|
(Optional) Neighbor interface.
|
neighbor-id
|
(Optional) IPv6 or IP address of the neighbor.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(24)S
|
This command was introduced.
|
12.2(15)T
|
This command was integrated into Cisco IOS Release 12.2(15)T.
|
12.2(18)S
|
This command was integrated into Cisco IOS Release 12.2(18)S.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
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 detail
In the area 1 via interface Serial19/0
Neighbor:interface-id 21, link-local address FE80::A8BB:CCFF:FE00:6F00
Neighbor priority is 1, State is FULL, 6 state changes
Dead timer due in 00:00:37
Neighbor is up for 00:00:15
Index 1/1/1, retransmission queue length 0, number of retransmission 1
First 0x0(0)/0x0(0)/0x0(0) Next 0x0(0)/0x0(0)/0x0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0 msec
The following example clears all neighbors on the specified interface:
Router# clear ipv6 ospf counters neighbor s19/0
The 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 detail
In the area 1 via interface Serial19/0
Neighbor:interface-id 21, link-local address FE80::A8BB:CCFF:FE00:6F00
Neighbor priority is 1, State is FULL, 0 state changes
Dead timer due in 00:00:39
Neighbor is up for 00:00:43
Index 1/1/1, retransmission queue length 0, number of retransmission 1
First 0x0(0)/0x0(0)/0x0(0) Next 0x0(0)/0x0(0)/0x0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0 msec
Related Commands
Command
|
Description
|
show ipv6 ospf neighbor
|
Displays OSPF neighbor information on a per-interface basis.
|
clear 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
Release
|
Modification
|
12.0(26)S
|
This command was introduced.
|
12.2(18)S
|
This command was integrated into Cisco IOS Release 12.2(18)S.
|
12.3(4)T
|
This command was integrated into Cisco IOS Release 12.3(4)T.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(25)SG
|
This command was integrated into Cisco IOS Release 12.2(25)SG.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
Usage Guidelines
Using the clear ipv6 pim counters command will reset all PIM traffic counters.
Examples
The following example resets the PIM traffic counters:
Related Commands
Command
|
Description
|
show ipv6 pim traffic
|
Displays the PIM traffic counters.
|
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
The command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(2)T
|
This command was introduced.
|
12.2(18)S
|
This command was integrated into Cisco IOS Release 12.2(18)S.
|
12.0(26)S
|
This command was integrated into Cisco IOS Release 12.0(26)S.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
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.
Caution 
Use 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 reset
clear 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
group-name | group-address
|
(Optional) IPv6 address or name of the multicast group.
|
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
Release
|
Modification
|
12.3(2)T
|
This command was introduced.
|
12.2(18)S
|
This command was integrated into Cisco IOS Release 12.2(18)S.
|
12.0(26)S
|
This command was integrated into Cisco IOS Release 12.0(26)S.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(25)SG
|
This command was integrated into Cisco IOS Release 12.2(25)SG.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
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 topology
clear 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
prefix-list-name
|
(Optional) The name of the prefix list from which the hit count is to be cleared.
|
ipv6-prefix
|
(Optional) The IPv6 network from which the hit count is to be cleared.
This argument must be in the form documented in RFC 2373 where the address is specified in hexadecimal using 16-bit values between colons.
|
/prefix-length
|
(Optional) The length of the IPv6 prefix. A decimal value that indicates how many of the high-order contiguous bits of the address comprise the prefix (the network portion of the address). A slash mark must precede the decimal value.
|
Command Default
Clears the hit count for all IPv6 prefix lists.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
12.0(21)ST
|
This command was integrated into Cisco IOS Release 12.0(21)ST.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(25)SG
|
This command was integrated into Cisco IOS Release 12.2(25)SG.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
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::/35
Related Commands
Command
|
Description
|
ipv6 prefix-list
|
Creates an entry in an IPv6 prefix list.
|
ipv6 prefix-list sequence-number
|
Enables the generation of sequence numbers for entries in an IPv6 prefix list.
|
show ipv6 prefix-list
|
Displays information about an IPv6 prefix list or prefix list entries.
|
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
name
|
(Optional) Name of an IPv6 RIP process.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(22)S
|
This command was introduced.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(25)SG
|
This command was integrated into Cisco IOS Release 12.2(25)SG.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
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 one
Related Commands
Command
|
Description
|
show ipv6 rip
|
Displays the current contents of the IPv6 RIP routing table.
|
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
ipv6-address
|
The address of the IPv6 network to delete from the table.
This argument must be in the form documented in RFC 2373 where the address is specified in hexadecimal using 16-bit values between colons.
|
ipv6-prefix
|
The IPv6 network number to delete from the table.
This argument must be in the form documented in RFC 2373 where the address is specified in hexadecimal using 16-bit values between colons.
|
/prefix-length
|
The length of the IPv6 prefix. A decimal value that indicates how many of the high-order contiguous bits of the address comprise the prefix (the network portion of the address). A slash mark must precede the decimal value.
|
*
|
Clears all IPv6 routes.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
12.0(21)ST
|
This command was integrated into Cisco IOS Release 12.0(21)ST.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(25)SG
|
This command was integrated into Cisco IOS Release 12.2(25)SG.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
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::/35
Related Commands
Command
|
Description
|
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
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
12.0(21)ST
|
This command was integrated into Cisco IOS Release 12.0(21)ST.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S and output fields were added.
|
12.2(13)T
|
The modification to add output fields was integrated into this release.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(25)SG
|
This command was integrated into Cisco IOS Release 12.2(25)SG.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
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 traffic
Router# show ipv6 traffic
Rcvd: 1 total, 1 local destination
0 source-routed, 0 truncated
0 format errors, 0 hop count exceeded
0 bad header, 0 unknown option, 0 bad source
0 unknown protocol, 0 not a router
0 fragments, 0 total reassembled
0 reassembly timeouts, 0 reassembly failures
Sent: 1 generated, 0 forwarded
0 fragmented into 0 fragments, 0 failed
0 encapsulation failed, 0 no route, 0 too big
Mcast: 0 received, 0 sent
Rcvd: 1 input, 0 checksum errors, 0 too short
0 unknown info type, 0 unknown error type
unreach: 0 routing, 0 admin, 0 neighbor, 0 address, 0 port
parameter: 0 error, 0 header, 0 option
0 hopcount expired, 0 reassembly timeout,0 too big
0 echo request, 0 echo reply
0 group query, 0 group report, 0 group reduce
0 router solicit, 0 router advert, 0 redirects
0 neighbor solicit, 1 neighbor advert
unreach: 0 routing, 0 admin, 0 neighbor, 0 address, 0 port
parameter: 0 error, 0 header, 0 option
0 hopcount expired, 0 reassembly timeout,0 too big
0 echo request, 0 echo reply
0 group query, 0 group report, 0 group reduce
0 router solicit, 0 router advert, 0 redirects
0 neighbor solicit, 1 neighbor advert
Rcvd: 0 input, 0 checksum errors, 0 length errors
Rcvd: 0 input, 0 checksum errors
Sent: 0 output, 0 retransmitted
Related Commands
Command
|
Description
|
show ipv6 traffic
|
Displays IPv6 traffic statistics.
|
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
all
|
Clears all per-prefix accounting statistics information.
|
ipv6-address/mask
|
Entry IPv6 address and mask. The format used is X:X:X:X::X/mask, where the valid values for mask are from 0 to 128.
|
instance
|
(Optional) VPN routing and forwarding instance name.
|
Command Default
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(17a)SX
|
This command was introduced on the Supervisor Engine 720.
|
12.2(17d)SXB
|
Support for this command on the Supervisor Engine 2 was extended to Release 12.2(17d)SXB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
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 all
context
To associate a Simple Network Management Protocol (SNMP) context with a particular virtual private network (VPN) routing/forwarding instance (VRF), 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
context-name
|
Name of the SNMP VPN context, up to 32 characters.
|
Command Default
No SNMP contexts are associated with VPNs.
Command Modes
VRF configuration
Command History
Release
|
Modification
|
12.0(23)S
|
This command was introduced.
|
12.3(2)T
|
This command was integrated into Cisco IOS Release 12.3(2)T.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(31)SB2
|
This command was integrated into Cisco IOS Release 12.2(31)SB2.
|
12.2(33)SRB
|
Support for IPv6 was added.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
Before you use this command to associate an SNMP context with a VPN, you must do the following:
•
Issue the snmp-server context command to create an SNMP context
•
Associate a VPN with a context so that the specific MIB data for that VPN exists in that context.
•
Associate a VPN group with the context of the VPN using the snmp-server group command with the context context-name keyword and argument.
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 context1
Router(config)# ip vrf vrf1
Router(config-vrf)# rd 100:120
Router(config-vrf)# context context1
Related Commands
Command
|
Description
|
ip vrf
|
Enters VRF configuration mode for the configuration of a VRF.
|
snmp mib community-map
|
Associates an SNMP community with an SNMP context, engine ID, or security name.
|
snmp mib target list
|
Creates a list of target VRFs and hosts to associate with an SNMP v1 or v2c community.
|
snmp-server context
|
Creates an SNMP context.
|
snmp-server group
|
Configures a new SNMP group, or a table that maps SNMP users to SNMP views.
|
snmp-server trap authentication vrf
|
Controls VRF-specific SNMP authentication failure notifications.
|
snmp-server user
|
Configures a new user to an SNMP group.
|
copy
To copy any file from a source to a destination, use the copy command in privileged EXEC mode.
copy [/erase] [/verify | /noverify] source-url destination-url
Syntax Description
/erase
|
(Optional) Erases the destination file system before copying.
Note This option is typically provided on platforms with limited memory to allow for an easy way to clear local flash memory space.
|
/verify
|
(Optional) Verifies the digital signature of the destination file. If verification fails, the file is deleted from the destination file system. This option applies to Cisco IOS software image files only.
|
/noverify
|
(Optional) If the file being copied is an image file, this keyword disables the automatic image verification that occurs after an image is copied.
Note This keyword is often issued if the file verify auto command is enabled, which automatically verifies the digital signature of all images that are copied.
|
source-url
|
The location URL (or alias) of the source file or directory to be copied. The source can be either local or remote, depending upon whether the file is being downloaded or uploaded.
|
destination-url
|
The destination URL (or alias) of the copied file or directory. The destination can be either local or remote, depending upon whether the file is being downloaded or uploaded.
|
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 2 shows two keyword shortcuts to URLs.
Table 2 Common Keyword Aliases to URLs
Keyword
|
Source or Destination
|
running-config
|
(Optional) Keyword alias for the system:running-config URL. The system:running-config keyword represents the current running configuration file. This keyword does not work in more and show file EXEC command syntaxes.
|
startup-config
|
(Optional) Keyword alias for the nvram:startup-config URL. The nvram:startup-config keyword represents the configuration file used during initialization (startup). This file is contained in NVRAM for all platforms except the Cisco 7000 family, which uses the CONFIG_FILE environment variable to specify the startup configuration. The Cisco 4500 series cannot use the copy running-config startup-config command. This keyword does not work in more and show file EXEC command syntaxes.
|
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 3 lists URL prefix keywords for Special (opaque) file systems. Table 4 lists them for remote file systems, and Table 5 lists them for local writable storage.
Table 3 URL Prefix Keywords for Special File Systems
Keyword
|
Source or Destination
|
flh:
|
Source URL for flash load helper log files.
|
modem:
|
Destination URL for loading modem firmware on to supported networking devices.
|
null:
|
Null destination for copies or files. You can copy a remote file to null to determine its size.
|
nvram:
|
Router NVRAM. You can copy the startup configuration to NVRAM or from NVRAM.
|
system:
|
Source or destination URL for system memory, which includes the running configuration.
|
xmodem:
|
Source or destination for a file from a network machine that uses the Xmodem protocol.
|
ymodem:
|
Source or destination for a file from a network machine that uses the Ymodem protocol.
|
Table 4 URL Prefix Keywords for Remote File Systems
Keyword
|
Source or Destination
|
ftp:
|
Source or destination URL for FTP network server. The syntax for this alias is as follows: ftp:[[[//username [:password]@]location]/directory]/filename.
|
http://
|
Source or destination URL for an HTTP server (also called a web server). The syntax for this alias is as follows: http://[[username:password]@]{hostname | host-ip}[/filepath]/filename
|
https://
|
Source or destination URL for a Secure HTTP (HTTPS) server. HTTPS uses Secure Socket Layer (SSL) encryption. The syntax for this alias is as follows: https://[[username:password]@]{hostname | host-ip}[/filepath]/filename
|
rcp:
|
Source or destination URL for a remote copy protocol (rcp) network server. The syntax for this alias is as follows: rcp:[[[//username@]location]/directory]/filename
|
scp:
|
Source or destination URL for a network server that supports Secure Shell (SSH) and accepts copies of files using the secure copy protocol (scp). The syntax for this alias is as follows: scp://username@location[/directory][/filename]
|
tftp:
|
Source or destination URL for a TFTP network server. The syntax for this alias is as follows: tftp:[[//location]/directory]/filename.
|
Table 5 URL Prefix Keywords for Local Writable Storage File Systems
Alias
|
Source or Destination
|
bootflash:
|
Source or destination URL for boot flash memory.
|
disk0: and disk1:
|
Source or destination URL of disk-based media.
|
flash:
|
Source or destination URL for flash memory. This alias is available on all platforms. For platforms that lack a flash: device, note that flash: is aliased to slot0:, allowing you to refer to the main flash memory storage area on all platforms.
|
slavebootflash:
|
Source or destination URL for internal flash memory on the slave RSP card of a router configured for HSA.
|
slaveram:
|
NVRAM on a slave RSP card of a router configured for HSA.
|
slaveslot0:
|
Source or destination URL of the first Personal Computer Memory Card International Association (PCMCIA) card on a slave RSP card of a router configured for HSA.
|
slaveslot1:
|
Source or destination URL of the second PCMCIA slot on a slave RSP card of a router configured for HSA.
|
slot0:
|
Source or destination URL of the first PCMCIA flash memory card.
|
slot1:
|
Source or destination URL of the second PCMCIA flash memory card.
|
usbflash[0-9]:
|
Source or destination URL for the Universal Serial Bus (USB) flash drive that has been plugged into the router.
|
usbtoken[0-9]:
|
Source or destination URL for the USB eToken that has been plugged into the router.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.3T
|
This command was introduced.
|
12.3(2)T
|
• The http:// and https:// keywords were added as supported remote source locations (file system URL prefixes) for files.
• This command was enhanced to support copying files to servers that support SSH and the scp.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(18)S
|
The /verify and /noverify keywords were added.
|
12.0(26)S
|
The /verify and /noverify keywords were integrated into Cisco IOS Release 12.0(26)S.
|
12.3(4)T
|
The /verify and /noverify keywords were integrated into Cisco IOS Release 12.3(4)T.
|
12.3(7)T
|
|