-
Cisco IOS IPv6 Command Reference
-
Introduction
-
IPv6 Commands: aaa accounting multicast default through clear ipv6 mobile home-agents
-
IPv6 Commands: clear ipv6 mobile traffic through debug bgp vpnv6 unicast
-
IPv6 Commands: debug crypto ipv6 ipsec through debug ipv6 pim
-
IPv6 Commands: debug ipv6 pim df-election through ip http server
-
IPv6 Commands: ip name server through ipv6 general-prefix
-
IPv6 Commands: ipv6 hello-interval eigrp through ipv6 mld static-group
-
IPv6 Commands: ipv6 mobile home-agent through ipv6 ospf database-filter all out
-
IPv6 Commands: ipv6 ospf dead-interval through ipv6 split-horizon eigrp
-
IPv6 Commands: mpls traffic-eng auto-bw timers through route-map
-
IPv6 Commands: router-id (IPv6) through show bgp ipv6 labels
-
IPv6 Commands: show bgp ipv6 neighbors through show crypto isakmp peers
-
IPv6 Commands: show crypto isakmp policy through show ipv6 eigrp neighbors
-
IPv6 Commands: show ipv6 eigrp topology through show ipv6 nat statistics
-
IPv6 Commands: show ipv6 nat translations through show ipv6 protocols
-
IPv6 Commands: show ipv6 rip through snmp-server host
-
IPv6 Commands: snmp-server user through variance (EIGRP)
-
Table Of Contents
debug crypto ipv6 ipsec
To display IP Security (IPSec) events for IPv6 networks, use the debug crypto ipv6 ipsec command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug crypto ipv6 ipsec
no debug crypto ipv6 ipsec
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging for IPv6 IPSec events is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display IPSec events while setting up or removing policy definitions during OSPF configuration.
Examples
The following example enables the display of IPSec events for IPv6 networks:
Router# debug crypto ipv6 ipsecRelated Commands
debug crypto ipv6 packet
To display the contents of IPv6 packets, use the debug crypto ipv6 packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug crypto ipv6 packet
no debug crypto ipv6 packet
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging for IPv6 IPSec packets is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Consult Cisco Technical Support before using this command.
Use this command to display the contents of IPv6 packets. This command is useful when the remote node is not a Cisco device and communication between the Cisco and non-Cisco router cannot be established. This command enables you to look at the contents of the packets outbound from the Cisco router.
This command examines the content of every IPv6 packet and may slow network performance.
Examples
This example shows the ouptut of each packet when the debug crypto ipv6 packet command is enabled:
Router# debug crypto ipv6 packetCrypto IPv6 IPSEC packet debugging is onRouter#*Oct 30 16:57:06.330:IPSECv6:before Encapsulation of IPv6 packet:0E37A7C0: 6E000000 00285901 n....(Y.0E37A7D0:FE800000 00000000 020A8BFF FED42C1D ~...........~T,.0E37A7E0:FF020000 00000000 00000000 00000005 ................0E37A7F0:03010028 01010104 00000001 8AD80000 ...(.........X..0E37A800:00000006 01000013 000A0028 0A0250CF ...........(..PO0E37A810:01010104 0A0250CF ......PO*Oct 30 16:57:06.330:IPSECv6:Encapsulated IPv6 packet:0E37A7B0:6E000000 00403301 FE800000 00000000 n....@3.~.......0E37A7C0:020A8BFF FED42C1D FF020000 00000000 ....~T,.........0E37A7D0:00000000 00000005 59040000 000022B8 ........Y....."80E37A7E0:0000001A 38AB1ED8 04C1C6FB FF1248CF ....8+.X.AF{..HO0E37A7F0:03010028 01010104 00000001 8AD80000 ...(.........X..0E37A800:00000006 01000013 000A0028 0A0250CF ...........(..PO0E37A810:01010104 0A0250CF ......PO*Oct 30 16:57:11.914:IPSECv6:Before Decapsulation of IPv6 packet:0E004A50: 6E000000 00403301 n....@3.0E004A60:FE800000 00000000 023071FF FE7FE81D ~........0q.~.h.0E004A70:FF020000 00000000 00000000 00000005 ................0E004A80:59040000 000022B8 00001D88 F5AC68EE Y....."8....u,hn0E004A90:1AC00088 947C6BF2 03010028 0A0250CF .@...|kr...(..PO0E004AA0:00000001 E9080000 00000004 01000013 ....i...........0E004AB0:000A0028 0A0250CF 01010104 01010104 ...(..PO........0E004AC0:*Oct 30 16:57:11.914:IPSECv6:Decapsulated IPv6 packet:0E004A70:6E000000 00285901 FE800000 00000000 n....(Y.~.......0E004A80:023071FF FE7FE81D FF020000 00000000 .0q.~.h.........0E004A90:00000000 00000005 03010028 0A0250CF ...........(..PO0E004AA0:00000001 E9080000 00000004 01000013 ....i...........0E004AB0:000A0028 0A0250CF 01010104 01010104 ...(..PO........0E004AC0:*Oct 30 16:57:16.330:IPSECv6:before Encapsulation of IPv6 packet:0E003DC0: 6E000000 00285901 n....(Y.0E003DD0:FE800000 00000000 020A8BFF FED42C1D ~...........~T,.0E003DE0:FF020000 00000000 00000000 00000005 ................0E003DF0:03010028 01010104 00000001 8AD80000 ...(.........X..0E003E00:00000006 01000013 000A0028 0A0250CF ...........(..PO0E003E10:01010104 0A0250CF ......PO*Oct 30 16:57:16.330:IPSECv6:Encapsulated IPv6 packet:0E003DB0:6E000000 00403301 FE800000 00000000 n....@3.~.......0E003DC0:020A8BFF FED42C1D FF020000 00000000 ....~T,.........0E003DD0:00000000 00000005 59040000 000022B8 ........Y....."80E003DE0:0000001B F8E3C4E2 4CC4B690 DDF32B5C ....xcDbLD6.]s+\0E003DF0:03010028 01010104 00000001 8AD80000 ...(.........X..0E003E00:00000006 01000013 000A0028 0A0250CF ...........(..PO0E003E10:01010104 0A0250CF ......PORelated Commands
debug eigrp fsm
To display debugging information about Enhanced Interior Gateway Routing Protocol (EIGRP) feasible successor metrics (FSMs), use the debug eigrp fsm command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eigrp fsm
no debug eigrp fsm
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command helps you observe EIGRP feasible successor activity and to determine whether route updates are being installed and deleted by the routing process.
Examples
The following is sample output from the debug eigrp fsm command:
Router# debug eigrp fsmDUAL: dual_rcvupdate(): 172.25.166.0 255.255.255.0 via 0.0.0.0 metric 750080/0DUAL: Find FS for dest 172.25.166.0 255.255.255.0. FD is 4294967295, RD is 4294967295 foundDUAL: RT installed 172.25.166.0 255.255.255.0 via 0.0.0.0DUAL: dual_rcvupdate(): 192.168.4.0 255.255.255.0 via 0.0.0.0 metric 4294967295/4294967295DUAL: Find FS for dest 192.168.4.0 255.255.255.0. FD is 2249216, RD is 2249216DUAL: 0.0.0.0 metric 4294967295/4294967295not found Dmin is 4294967295DUAL: Dest 192.168.4.0 255.255.255.0 not entering active state.DUAL: Removing dest 192.168.4.0 255.255.255.0, nexthop 0.0.0.0DUAL: No routes. Flushing dest 192.168.4.0 255.255.255.0In the first line, DUAL stands for diffusing update algorithm. It is the basic mechanism within EIGRP that makes the routing decisions. The next three fields are the Internet address and mask of the destination network and the address through which the update was received. The metric field shows the metric stored in the routing table and the metric advertised by the neighbor sending the information. If shown, the term "Metric... inaccessible" usually means that the neighbor router no longer has a route to the destination, or the destination is in a hold-down state.
In the following output, EIGRP is attempting to find a feasible successor for the destination. Feasible successors are part of the DUAL loop avoidance methods. The FD field contains more loop avoidance state information. The RD field is the reported distance, which is the metric used in update, query, or reply packets.
The indented line with the "not found" message means a feasible successor (FS) was not found for 192.168.4.0 and EIGRP must start a diffusing computation. This means it begins to actively probe (sends query packets about destination 192.168.4.0) the network looking for alternate paths to 192.164.4.0.
DUAL: Find FS for dest 192.168.4.0 255.255.255.0. FD is 2249216, RD is 2249216DUAL: 0.0.0.0 metric 4294967295/4294967295not found Dmin is 4294967295The following output indicates the route DUAL successfully installed into the routing table:
DUAL: RT installed 172.25.166.0 255.255.255.0 via 0.0.0.0The following output shows that no routes to the destination were discovered and that the route information is being removed from the topology table:
DUAL: Dest 192.168.4.0 255.255.255.0 not entering active state.DUAL: Removing dest 192.168.4.0 255.255.255.0, nexthop 0.0.0.0DUAL: No routes. Flushing dest 192.168.4.0 255.255.255.0debug eigrp neighbor
To display neighbors discovered by the Enhanced Interior Gateway Routing Protocol (EIGRP), use the debug eigrp neighbor command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eigrp neighbor [siatimer] [static]
no debug eigrp neighbor [siatimer] [static]
Syntax Description
Command Default
Debugging for EIGRP neighbors is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug eigrp neighbor command:
Router# debug eigrp neighbor staticEIGRP Static Neighbors debugging is onRouter# configure terminalRouter(config)# router eigrp 100Router(config-router)# neighbor 10.1.1.1 e3/1Router(config-router)#22:40:07:EIGRP:Multicast Hello is disabled on Ethernet3/1!22:40:07:EIGRP:Add new static nbr 10.1.1.1 to AS 100 Ethernet3/1Router(config-router)# no neighbor 10.1.1.1 e3/1Router(config-router)#22:41:23:EIGRP:Static nbr 10.1.1.1 not in AS 100 Ethernet3/1 dynamic list22:41:23:EIGRP:Delete static nbr 10.1.1.1 from AS 100 Ethernet3/122:41:23:EIGRP:Multicast Hello is enabled on Ethernet3/1!Related Commands
debug eigrp packet
To display debugging information for Enhanced Interior Gateway Routing Protocol (EIGRP) for IPv6 packets, use the debug eigrp packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eigrp packet [SIAquery | SIAreply | ack | hello | ipxsap | probe | query | reply | request | retry | stub | terse | update | verbose]
no debug eigrp packet
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If a communication session is closing when it should not be, an end-to-end connection problem can be the cause. The debug eigrp packet command is useful for analyzing the messages traveling between the local and remote hosts.
Note
Although this command accepts a number of keywords, we don't recommend their use unless directed by TAC.
Examples
The following is sample output from the debug eigrp packet command:
Router# debug eigrp packetEIGRP: Sending HELLO on Ethernet0/1AS 109, Flags 0x0, Seq 0, Ack 0EIGRP: Sending HELLO on Ethernet0/1AS 109, Flags 0x0, Seq 0, Ack 0EIGRP: Sending HELLO on Ethernet0/1AS 109, Flags 0x0, Seq 0, Ack 0EIGRP: Received UPDATE on Ethernet0/1 from 192.195.78.24,AS 109, Flags 0x1, Seq 1, Ack 0EIGRP: Sending HELLO/ACK on Ethernet0/1 to 192.195.78.24,AS 109, Flags 0x0, Seq 0, Ack 1EIGRP: Sending HELLO/ACK on Ethernet0/1 to 192.195.78.24,AS 109, Flags 0x0, Seq 0, Ack 1EIGRP: Received UPDATE on Ethernet0/1 from 192.195.78.24,AS 109, Flags 0x0, Seq 2, Ack 0The output shows transmission and receipt of EIGRP packets. These packet types may be hello, update, request, query, or reply packets. The sequence and acknowledgment numbers used by the EIGRP reliable transport algorithm are shown in the output. Where applicable, the network-layer address of the neighboring router is also included.
Table 9 describes the significant fields shown in the display.
debug eigrp transmit
To display transmittal messages sent by the Enhanced Interior Gateway Routing Protocol (EIGRP), use the debug eigrp transmit command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eigrp transmit [ack] [build] [detail] [link] [packetize] [peerdown] [sia] [startup] [strange]
no debug eigrp transmit [ack] [build] [detail] [link] [packetize] [peerdown] [sia] [startup] [strange]
Syntax Description
Command Default
Debugging for EIGRP transmittal messages is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug eigrp transmit command:
Router# debug eigrp transmitEIGRP Transmission Events debugging is on(ACK, PACKETIZE, STARTUP, PEERDOWN, LINK, BUILD, STRANGE, SIA, DETAIL)Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router#(config)# router eigrp 100Router#(config-router)# network 10.4.9.0 0.0.0.255Router#(config-router)#5d22h: DNDB UPDATE 10.0.0.0/8, serno 0 to 1, refcount 0Router#(config-router)#debug ip flow cache
To enable debugging output for NetFlow cache, use the debug ip flow cache command in user EXEC or privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip flow cache
no debug ip flow cache
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging output for NetFlow data export is disabled.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the debug ip flow export command:
Router# debug ip flow cacheIP Flow cache allocation debugging is onRouter# show ipv6 flowIP packet size distribution (0 total packets):1-32 64 96 128 160 192 224 256 288 320 352 384 416 448 480.000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000512 544 576 1024 1536 2048 2560 3072 3584 4096 4608.000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000IP Flow Switching Cache, 0 bytes0 active, 0 inactive, 0 added0 ager polls, 0 flow alloc failuresActive flows timeout in 30 minutesInactive flows timeout in 15 secondsSrcAddress InpIf DstAddressOutIf Prot SrcPrt DstPrt Packetsc7200-vxr-2#000037: 01:56:26: IPFLOW: Allocating Sub-Flow cache, without hash flags.000038: 01:56:26: IPFLOW: Sub-Flow table enabled.000039: 01:56:26: IPFLOW: Sub-Flow numbers are:24 sub-flows per chunk, 0 hashflag len,1 chunks allocated, 12 max chunks,24 allocated records, 24 free records, 960 bytes allocated000040: 01:56:26: IPFLOW: Sub-Flow cache removedRelated Commands
debug ip flow export
To enable debugging output for NetFlow data export, use the debug ip flow export command in user EXEC or privileged EXEC mode. To disable debugging output for NetFlow data export, use the no form of this command.
debug ip flow export
no debug ip flow export
Syntax Description
This command has no keywords or arguments.
Command Default
Debugging output for NetFlow data export is disabled.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the debug ip flow export command:
Router# debug ip flow exportIP Flow export mechanism debugging is on*Mar 6 22:56:21.627:IPFLOW:Sending export pak to 2001::FFFE/64 port 9999*Mar 6 22:56:21.627:IPFLOW:Error sending export packet:Adjacency failureRelated Commands
debug ipv6 cef drop
To display debug messages for Cisco Express Forwarding for IPv6 (CEFv6) and distributed CEFv6 (dCEFv6) dropped packets, use the debug ipv6 cef drop command in privileged EXEC mode. To disable debug messages for CEFv6 and dCEFv6 dropped packets, use the no form of this command.
debug ipv6 cef drop [rpf]
no debug ipv6 cef drop
Syntax Description
rpf
(Optional) Displays packets dropped by the IPv6 CEF Unicast Reverse-Path Forwarding (Unicast RPF) feature.
Command Default
Debugging for CEFv6 and dCEFv6 dropped packets is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ipv6 cef drop command is similar to the debug ip cef drops command, except that it is IPv6-specific.
Note
Examples
The following is sample output from the debug ipv6 cef drop command:
Router# debug ipv6 cef drop*Aug 30 08:20:51.169: IPv6-CEF: received packet on Serial6/0/2*Aug 30 08:20:51.169: IPv6-CEF: found no adjacency for 2001:0DB8::1 reason 2*Aug 30 08:20:51.169: IPv6-CEF: packet not switched: code 0x1Table 10 describes the significant fields shown in the display.
Related Commands
debug ipv6 cef events
Displays debug messages for CEFv6 and dCEFv6 general events.
debug ipv6 cef table
Displays debug messages for CEFv6 and dCEFv6 table modification events.
debug ipv6 cef events
To display debug messages for Cisco Express Forwarding for IPv6 (CEFv6) and distributed CEFv6 (dCEFv6) general events, use the debug ipv6 cef events command in privileged EXEC mode. To disable debug messages for CEFv6 and dCEFv6 general events, use the no form of this command.
debug ipv6 cef events
no debug ipv6 cef events
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging for CEFv6 and dCEFv6 general events is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ipv6 cef events command is similar to the debug ip cef events command, except that it is IPv6-specific.
Note
Examples
The following is sample output from the debug ipv6 cef events command:
Router# debug ipv6 cef eventsIPv6 CEF packet events debugging is onRouter#*Aug 30 08:22:57.809: %LINK-3-UPDOWN: Interface Serial6/0/2, changed state to up*Aug 30 08:22:58.809: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0/2, changed state to up*Aug 30 08:23:00.821: CEFv6-IDB: Serial6/0/2 address 2001:0DB8::248 add download succeededTable 11 describes the significant fields shown in the display.
Related Commands
debug ipv6 cef table
Displays debug messages for CEFv6 and dCEFv6 table modification events.
debug ipv6 cef hash
To display debug messages for Cisco Express Forwarding for IPv6 (CEFv6) and distributed CEFv6 (dCEFv6) load-sharing hash algorithm events, use the debug ipv6 cef hash command in privileged EXEC mode. To disable debug messages for CEFv6 and dCEFv6 load-sharing hash algorithm events, use the no form of this command.
debug ipv6 cef hash
no debug ipv6 cef hash
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging for CEFv6 and dCEFv6 load-sharing hash algorithm events is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ipv6 cef hash command is similar to the debug ip cef hash command, except that it is IPv6-specific.
Use this command when changing the load-sharing algorithm to display IPv6 hash table details.
Note
Related Commands
debug ipv6 cef events
Displays debug messages for CEFv6 and dCEFv6 general events.
debug ipv6 cef table
Displays debug messages for CEFv6 and dCEFv6 table modification events.
debug ipv6 cef receive
To display debug messages for Cisco Express Forwarding for IPv6 (CEFv6) and distributed CEFv6 (dCEFv6) packets that are process-switched on the router, use the debug ipv6 cef receive command in privileged EXEC mode. To disable debug messages for CEFv6 and dCEFv6 packets that are process-switched on the router, use the no form of this command.
debug ipv6 cef receive
no debug ipv6 cef receive
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging for CEFv6 and dCEFv6 packets that are process-switched on the router is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ipv6 cef receive command is similar to the debug ip cef receive command, except that it is IPv6-specific.
Note
Examples
The following is sample output from the debug ipv6 cef receive command when another router in the network pings 2001:0DB8::2 which is a local address on this box:
Router# debug ipv6 cef receiveIPv6 CEF packet receives debugging is onrouter#*Aug 30 08:25:14.869: IPv6CEF-receive: Receive packet for 2001:0DB8::2*Aug 30 08:25:14.897: IPv6CEF-receive: Receive packet for 2001:0DB8::2*Aug 30 08:25:14.925: IPv6CEF-receive: Receive packet for 2001:0DB8::2*Aug 30 08:25:14.953: IPv6CEF-receive: Receive packet for 2001:0DB8::2*Aug 30 08:25:14.981: IPv6CEF-receive: Receive packet for 2001:0DB8::2Table 12 describes the significant fields shown in the display.
Table 12 debug ipv6 cef receive Field Descriptions
IPv6CEF-receive: Receive packet for 2001:0DB8::2
Cisco Express Forwarding has received a packet addressed to the router.
Related Commands
debug ipv6 cef events
Displays debug messages for CEFv6 and dCEFv6 general events.
debug ipv6 cef table
Displays debug messages for CEFv6 and dCEFv6 table modification events.
debug ipv6 cef table
To display debug messages for Cisco Express Forwarding for IPv6 (CEFv6) and distributed CEFv6 (dCEFv6) table modification events, use the debug ipv6 cef table command in privileged EXEC mode. To disable debug messages for CEFv6 and dCEFv6 table modification events, use the no form of this command.
debug ipv6 cef table [background]
no debug ipv6 cef table [background]
Syntax Description
Command Default
Debugging for CEFv6 and dCEFv6 table modification events is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ipv6 cef table command is similar to the debug ip cef table command, except that it is IPv6-specific.
This command is used to record CEFv6 and dCEFv6 table events related to the Forwarding Information Base (FIB) tables. Types of events include the following:
•
•
•
•
Note
Examples
The following is sample output from the debug ipv6 cef table command when a static route is added:
Router# debug ipv6 cef tableIPv6 CEF table debugging is onrouter(config)# ipv6 route 5555::/64 serial 2/0 3000::2router(config)#*Feb 24 08:46:09.187: IPv6CEF-Table: Event add, 5555::/64*Feb 24 08:46:09.187: IPv6 CEF table: Created path_list 01184570*Feb 24 08:46:09.187: IPv6 CEF table: Adding path 01181A80 to path_list 01184570 old path count=0*Feb 24 08:46:09.187: IPv6 CEF table: No matching list for path list 01184570*Feb 24 08:46:09.187: IPv6 CEF table: Adding fib entry 0117EE80 to path_list 01184570 old refcount=0*Feb 24 08:46:09.187: IPv6 CEF table: Added path_list 01184570 to hash 50*Feb 24 08:46:09.187: IPv6 CEF: Linking path 01181A80 to adjacency 01138E28*Feb 24 08:46:09.187: IPv6 CEF table: Created 0 loadinfos for path_list 01184570*Feb 24 08:46:09.187: IPv6CEF-Table: Validated 5555::/64The following is sample output when the static route is removed:
router(config)# no ipv6 route 5555::/64 serial 2/0 3000::2router(config)#*Feb 24 08:46:43.871: IPv6CEF-Table: Event delete, 5555::/64*Feb 24 08:46:43.871: IPv6CEF-Table: Invalidated 5555::/64*Feb 24 08:46:43.871: IPv6CEF-Table: Deleted 5555::/64*Feb 24 08:46:43.871: IPv6 CEF table: Removing fib entry 0117EE80 from path_list 01184570 old refcount=1*Feb 24 08:46:43.871: IPv6 CEF table: Removed path_list 01184570 from hash 50*Feb 24 08:46:43.871: IPv6 CEF table: Freeing path_list 01184570 refcount=0*Feb 24 08:46:43.871: IPv6 CEF table: Freeing all 1 paths in path_list 01184570*Feb 24 08:46:43.871: IPv6 CEF: deleting path 01181A80Related Commands
debug ipv6 cef events
Displays debug messages for CEFv6 and dCEFv6 general events.
debug ipv6 dhcp
To enable debugging for Dynamic Host Configuration Protocol (DHCP) for IPv6, use the debug ipv6 dhcp command in privileged EXEC mode. To disable debugging for DHCP for IPv6, use the no form of this command.
debug ipv6 dhcp [detail]
no debug ipv6 dhcp [detail]
Syntax Description
Command Default
Debugging for the DHCP for IPv6 is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The detail keyword used with the debug ipv6 dhcp command reports detailed DHCP for IPv6 message decoding.
Examples
The following example enables debugging for the DHCP for IPv6:
Router# debug ipv6 dhcpRelated Commands
debug ipv6 dhcp database
Enables debugging for the DHCP for IPv6 binding database agent.
debug ipv6 dhcp database
To enable debugging for the Dynamic Host Configuration Protocol (DHCP) for IPv6 binding database agent, use the debug ipv6 dhcp database command in privileged EXEC mode. To disable the display of debug messages for the DHCP for IPv6 binding database agent, use the no form of this command.
debug ipv6 dhcp database
no debug ipv6 dhcp database
Syntax Description
This command has no keywords or arguments.
Command Default
Debugging for the DHCP for IPv6 binding database agent is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ipv6 dhcp database command enables debugging for DHCP
