The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes troubleshooting ASR9k acting as Dynamic Host Configuration Protocol (DHCP) Relay by reviewing output of the debug dhcp ipv6 packets command. This is quite common when setting up the ASR9k as a DHCPv6 Relay Agent and using external DHCPv6 Server. It is useful to run debug to troubleshoot why customer is not getting IPv6 address.
Cisco recommends that you have knowledge of these topics:
This document is not restricted to specific software and hardware versions.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Here is the summary of the DHCPv6 Server and Client communication:
Note: Clients listen for DHCP messages on UDP port 546. Servers and Relay Agents listen for DHCP messages on UDP port 547.
There are many reasons why a Client can't get IPv6 address from DHCPv6 Server. It can be Client configuration, DHCPv6 Relay or DHCPv6 Server. The following discussion describes a scenario which includes ASR9k acting as a DHCPv6 Relay Agent.
In such a network, when Client is not receiving IP address, one of the troubleshooting steps is to analyze the communicated message, which is handled by DHCPv6 Relay Agent.
You can run "debug dhcp IPv6 packet" on DHCPv6 Relay Agent which shows you the content and sequence of the communicated messages in normal situation. It can assist you to find where the issue occurs by comparing a successful vs. unsuccessful transaction between Client/Server and find out the root cause and the next step for troubleshooting.
This is image shows the topology of the case study including Client, DHCPv6 Relay Agent (ASR9k) and DHCPv6 Server.
This is the basic terminology:
The Dynamic Host Configuration Protocol version 6 (DHCPv6) is a network protocol for configuring Internet Protocol version 6 (IPv6) hosts with IP addresses, IP prefixes and other configuration data required to operate in an IPv6 network. It is the IPv6 equivalent of the Dynamic Host Configuration Protocol for IPv4.
IPv6 hosts can automatically generate IP addresses internally using stateless address auto configuration, or they can be assigned configuration data with DHCPv6.
DHCPv6 Server (or Server) is a node that responds to requests from Clients, and may or may not be on the same link as the Client(s).
DHCPv6 Client (or Client) is a node that initiates requests on a link to obtain configuration parameters from one or more DHCPv6 servers.
DHCP Relay Agent (or Relay Agent) is a node that acts as an intermediary to deliver DHCP messages between Clients and Servers, and is on the same link as the Client.
Users configure DHCPv6 Relay Agents [RFC3315] to forward DHCPv6 messages between Clients and Servers when they are not on the same IPv6 link. They implement DHCPv6 alongside a routing function in a common node.
Message is a unit of data carried as the payload of a UDP datagram, exchanged among DHCPv6 Servers, Relay Agents and Clients.
DUID is a DHCP Unique Identifier for a DHCPv6 participant; each DHCPv6 Client and Server has exactly one DUID.
Identity association (IA) is a collection of addresses assigned to a Client. Each IA has an associated IAID.
A Client can have more than one IA assigned to it; for example, one for each of its interfaces.
Each IA holds one type of address; for example, an identity association for temporary addresses (IA_TA) holds temporary addresses.
Identity association identifier (IAID) is an identifier for an IA, chosen by the Client. Each IA has an IAID, which is unique among all IAIDs for IAs belonging to that Client.
Identity association for non-temporary addresses (IA_NA) is an IA that carries assigned addresses that are not temporary addresses (see "identity association for temporary addresses")
DHCPv6 uses status codes to communicate the success or failure of operations requested in messages from Clients and Servers, and to provide additional information about the specific cause of the failure of a message.
Considering the DHCPv6 Relay-Agent/Server and Client communication, you can analyze each type of message, shown in the debug output separately:
Client sends the "Solicit" message from link local to multicast address FF02::1:2 in order to find DHCP Server.
It includes:
You can find DUID of the Client by running ipconfig/all command, then look for DUID information in the debug to see if the Client is sending message or not.
This is an example of the captured information:
LC/0/0/CPU0:Sep 5 15:26:18.336 : dhcpv6d[159]: DHCPV6 PACKET: TP763: PKT IPv6 DHCP: Detailed packet contents LC/0/0/CPU0:Sep 5 15:26:18.336 : dhcpv6d[159]: DHCPV6 PACKET: TP762: PKT: src:fe80::8146:c052:79e1:c015 dest:ff02::1:2 << Src: Client's Link local IP >> Dest: To all DHCP Relay and Server LC/0/0/CPU0:Sep 5 15:26:18.336 : dhcpv6d[159]: DHCPV6 PACKET: TP758: PKT: type: SOLICIT dhcp->type:1 dhcp->xid:3882870 << DHCPv6 Message Type:Solicit LC/0/0/CPU0:Sep 5 15:26:18.336 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:ELAPSED-TIME(8) optlen:2 LC/0/0/CPU0:Sep 5 15:26:18.336 : dhcpv6d[159]: DHCPV6 PACKET: TP738: PKT: elaspsed_time:0 LC/0/0/CPU0:Sep 5 15:26:18.336 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:CLIENTID(1) optlen:14 LC/0/0/CPU0:Sep 5 15:26:18.336 : dhcpv6d[159]: DHCPV6 PACKET: TP725: PKT: duidbuf: 000100011f3c6ebb54ee75376d89 << DUID of Client (DHCP Unique Identifier, Can be verified with running ipconfig/all command at Client) LC/0/0/CPU0:Sep 5 15:26:18.336 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:IA-NA(3) optlen:12 LC/0/0/CPU0:Sep 5 15:26:18.336 : dhcpv6d[159]: DHCPV6 PACKET: TP748: PKT: IAID 0x0x354ee75 (55897717) T1:0x0 (0) T2:0x0 (0) << IAID of Client (can be verified with running ipconfig/all command at Client) LC/0/0/CPU0:Sep 5 15:26:18.336 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:CLIENT-FQDN(39) optlen:26 LC/0/0/CPU0:Sep 5 15:26:18.337 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:VENDOR-CLASS(16) optlen:14 LC/0/0/CPU0:Sep 5 15:26:18.337 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:ORO(6) optlen:8 LC/0/0/CPU0:Sep 5 15:26:18.337 : dhcpv6d[159]: DHCPV6 PACKET: TP734: PKT: option: VENDOR-OPTS LC/0/0/CPU0:Sep 5 15:26:18.337 : dhcpv6d[159]: DHCPV6 PACKET: TP734: PKT: option: DNS-SERVERS LC/0/0/CPU0:Sep 5 15:26:18.337 : dhcpv6d[159]: DHCPV6 PACKET: TP734: PKT: option: DOMAIN-LIST LC/0/0/CPU0:Sep 5 15:26:18.337 : dhcpv6d[159]: DHCPV6 PACKET: TP734: PKT: option: CLIENT-FQDN
DHCP Relay send the "Solicit" message to the DHCP Server which includes:
This is an example of the captured information:
LC/0/0/CPU0:Sep 5 15:26:18.339 : dhcpv6d[159]: DHCPV6 PACKET: TP764: PKT IPv6 DHCP: Det pkt cntents LC/0/0/CPU0:Sep 5 15:26:18.339 : dhcpv6d[159]: DHCPV6 PACKET: TP762: PKT: src:2002:172:16:70::2 dest:2002:172:16:151::2 << Src and Dst defined by Relay Agent to forward message to DHCP Server LC/0/0/CPU0:Sep 5 15:26:18.339 : dhcpv6d[159]: DHCPV6 PACKET: TP760: PKT: type:RELAY-FORWARD relay->msgtype:12 hop:0 << DHCPv6 Message Type LC/0/0/CPU0:Sep 5 15:26:18.339 : dhcpv6d[159]: DHCPV6 PACKET: TP761: PKT: link:2002:50:50:50::5 peer:fe80::8146:c052:79e1:c015 << Link: Global IP of Relay Interface toward Client & Peer : Client's Link local IP LC/0/0/CPU0:Sep 5 15:26:18.339 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:INTERFACE-ID(18) optlen:6 LC/0/0/CPU0:Sep 5 15:26:18.340 : dhcpv6d[159]: DHCPV6 PACKET: TP774: PKT: 0x LC/0/0/CPU0:Sep 5 15:26:18.340 : dhcpv6d[159]: DHCPV6 PACKET: TP743: PKT: 0x0 (0) LC/0/0/CPU0:Sep 5 15:26:18.340 : dhcpv6d[159]: DHCPV6 PACKET: TP743: PKT: 0x4 (4) LC/0/0/CPU0:Sep 5 15:26:18.340 : dhcpv6d[159]: DHCPV6 PACKET: TP743: PKT: 0x0 (0) LC/0/0/CPU0:Sep 5 15:26:18.340 : dhcpv6d[159]: DHCPV6 PACKET: TP743: PKT: 0x0 (0) LC/0/0/CPU0:Sep 5 15:26:18.341 : dhcpv6d[159]: DHCPV6 PACKET: TP743: PKT: 0x0 (0) LC/0/0/CPU0:Sep 5 15:26:18.341 : dhcpv6d[159]: DHCPV6 PACKET: TP743: PKT: 0x4 (4) LC/0/0/CPU0:Sep 5 15:26:18.341 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:REMOTEID(37) optlen:12 LC/0/0/CPU0:Sep 5 15:26:18.341 : dhcpv6d[159]: DHCPV6 PACKET: TP725: PKT: duidbuf: 0000000900068478ac36ba56 LC/0/0/CPU0:Sep 5 15:26:18.341 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:RELAY-MSG(9) optlen:104 LC/0/0/CPU0:Sep 5 15:26:18.341 : dhcpv6d[159]: DHCPV6 PACKET: TP758: PKT: type: SOLICIT dhcp->type:1 dhcp->xid:3882870 << DHCPv6 Message Type LC/0/0/CPU0:Sep 5 15:26:18.342 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:ELAPSED-TIME(8) optlen:2 LC/0/0/CPU0:Sep 5 15:26:18.342 : dhcpv6d[159]: DHCPV6 PACKET: TP738: PKT: elaspsed_time:0 LC/0/0/CPU0:Sep 5 15:26:18.342 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:CLIENTID(1) optlen:14 LC/0/0/CPU0:Sep 5 15:26:18.342 : dhcpv6d[159]: DHCPV6 PACKET: TP725: PKT: duidbuf: 000100011f3c6ebb54ee75376d89 << DUID of Client , Can be verified with ipconfig/all command at Client LC/0/0/CPU0:Sep 5 15:26:18.342 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:IA-NA(3) optlen:12 LC/0/0/CPU0:Sep 5 15:26:18.342 : dhcpv6d[159]: DHCPV6 PACKET: TP748: PKT: IAID 0x0x354ee75 (55897717) T1:0x0 (0) T2:0x0 (0) << IAID of Client , Can be verified with ipconfig/all command at Client LC/0/0/CPU0:Sep 5 15:26:18.342 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:CLIENT-FQDN(39) optlen:26 LC/0/0/CPU0:Sep 5 15:26:18.342 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:VENDOR-CLASS(16) optlen:14 LC/0/0/CPU0:Sep 5 15:26:18.343 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:ORO(6) optlen:8 LC/0/0/CPU0:Sep 5 15:26:18.343 : dhcpv6d[159]: DHCPV6 PACKET: TP734: PKT: option: VENDOR-OPTS LC/0/0/CPU0:Sep 5 15:26:18.343 : dhcpv6d[159]: DHCPV6 PACKET: TP734: PKT: option: DNS-SERVERS LC/0/0/CPU0:Sep 5 15:26:18.343 : dhcpv6d[159]: DHCPV6 PACKET: TP734: PKT: option: DOMAIN-LIST LC/0/0/CPU0:Sep 5 15:26:18.343 : dhcpv6d[159]: DHCPV6 PACKET: TP734: PKT: option: CLIENT-FQDN
DHCP Server respond with "Advertise" message and it receives as a “Relay Reply” packet by DHCP Relay Agent which includes:
This is an example of the captured information:
RP/0/RSP0/CPU0:Sep 5 15:26:18.346 : dhcpv6d[1087]: DHCPV6 PACKET: TP763: PKT IPv6 DHCP: Detailed packet contents RP/0/RSP0/CPU0:Sep 5 15:26:18.346 : dhcpv6d[1087]: DHCPV6 PACKET: TP762: PKT: src:2002:172:16:151::2 dest:2002:172:16:70::2 << Src & Dest defined by DHCP Server RP/0/RSP0/CPU0:Sep 5 15:26:18.346 : dhcpv6d[1087]: DHCPV6 PACKET: TP760: PKT: type:RELAY-REPLY relay->msgtype:13 hop:0 << DHCPv6 Message Type RP/0/RSP0/CPU0:Sep 5 15:26:18.346 : dhcpv6d[1087]: DHCPV6 PACKET: TP761: PKT: link:2002:50:50:50::5 peer:fe80::8146:c052:79e1:c015 << How to get to the Client RP/0/RSP0/CPU0:Sep 5 15:26:18.346 : dhcpv6d[1087]: DHCPV6 PACKET: TP723: PKT: optype:INTERFACE-ID(18) optlen:6 RP/0/RSP0/CPU0:Sep 5 15:26:18.347 : dhcpv6d[1087]: DHCPV6 PACKET: TP774: PKT: 0x RP/0/RSP0/CPU0:Sep 5 15:26:18.347 : dhcpv6d[1087]: DHCPV6 PACKET: TP743: PKT: 0x0 (0) RP/0/RSP0/CPU0:Sep 5 15:26:18.347 : dhcpv6d[1087]: DHCPV6 PACKET: TP743: PKT: 0x4 (4) RP/0/RSP0/CPU0:Sep 5 15:26:18.347 : dhcpv6d[1087]: DHCPV6 PACKET: TP743: PKT: 0x0 (0) RP/0/RSP0/CPU0:Sep 5 15:26:18.347 : dhcpv6d[1087]: DHCPV6 PACKET: TP743: PKT: 0x0 (0) RP/0/RSP0/CPU0:Sep 5 15:26:18.347 : dhcpv6d[1087]: DHCPV6 PACKET: TP743: PKT: 0x0 (0) RP/0/RSP0/CPU0:Sep 5 15:26:18.347 : dhcpv6d[1087]: DHCPV6 PACKET: TP743: PKT: 0x4 (4) RP/0/RSP0/CPU0:Sep 5 15:26:18.347 : dhcpv6d[1087]: DHCPV6 PACKET: TP723: PKT: optype:RELAY-MSG(9) optlen:115 RP/0/RSP0/CPU0:Sep 5 15:26:18.347 : dhcpv6d[1087]: DHCPV6 PACKET: TP758: PKT: type: ADVERTISE dhcp->type:2 dhcp->xid:3882870 << DHCP Server respond with Advertise message RP/0/RSP0/CPU0:Sep 5 15:26:18.347 : dhcpv6d[1087]: DHCPV6 PACKET: TP723: PKT: optype:SERVERID(2) optlen:10 << Server ID RP/0/RSP0/CPU0:Sep 5 15:26:18.348 : dhcpv6d[1087]: DHCPV6 PACKET: TP725: PKT: duidbuf: 00030001c8f9f98c3e80 << DUID of DHCP Server RP/0/RSP0/CPU0:Sep 5 15:26:18.348 : dhcpv6d[1087]: DHCPV6 PACKET: TP723: PKT: optype:CLIENTID(1) optlen:14 << DHCPv6 Message Type RP/0/RSP0/CPU0:Sep 5 15:26:18.348 : dhcpv6d[1087]: DHCPV6 PACKET: TP725: PKT: duidbuf: 000100011f3c6ebb54ee75376d89 << DUID of Client RP/0/RSP0/CPU0:Sep 5 15:26:18.348 : dhcpv6d[1087]: DHCPV6 PACKET: TP723: PKT: optype:IA-NA(3) optlen:40 RP/0/RSP0/CPU0:Sep 5 15:26:18.348 : dhcpv6d[1087]: DHCPV6 PACKET: TP748: PKT: IAID 0x0x354ee75 (55897717) T1:0xa8c0 (43200) T2:0x10e00 (69120) << IAID of Client RP/0/RSP0/CPU0:Sep 5 15:26:18.348 : dhcpv6d[1087]: DHCPV6 PACKET: TP723: PKT: optype:IAADDR(5) optlen:24 RP/0/RSP0/CPU0:Sep 5 15:26:18.348 : dhcpv6d[1087]: DHCPV6 PACKET: TP729: PKT: IPV6 addr:2002:50:50:50:2cdd:1975:9b64:8453 RP/0/RSP0/CPU0:Sep 5 15:26:18.348 : dhcpv6d[1087]: DHCPV6 PACKET: TP730: PKT: preferred RP/0/RSP0/CPU0:Sep 5 15:26:18.348 : dhcpv6d[1087]: DHCPV6 PACKET: TP769: PKT: 86400 RP/0/RSP0/CPU0:Sep 5 15:26:18.348 : dhcpv6d[1087]: DHCPV6 PACKET: TP731: PKT: valid RP/0/RSP0/CPU0:Sep 5 15:26:18.349 : dhcpv6d[1087]: DHCPV6 PACKET: TP733: PKT: len:172800 RP/0/RSP0/CPU0:Sep 5 15:26:18.349 : dhcpv6d[1087]: DHCPV6 PACKET: TP723: PKT: optype:DNS-SERVERS(23) optlen:16 RP/0/RSP0/CPU0:Sep 5 15:26:18.349 : dhcpv6d[1087]: DHCPV6 PACKET: TP744: PKT: ipv6_addr:2001:4860:4860::8888 RP/0/RSP0/CPU0:Sep 5 15:26:18.349 : dhcpv6d[1087]: DHCPV6 PACKET: TP723: PKT: optype:DOMAIN-LIST(24) optlen:11 RP/0/RSP0/CPU0:Sep 5 15:26:18.349 : dhcpv6d[1087]: DHCPV6 PACKET: TP746: PKT: Domain_name: cisco.com
DHCP Relay Agent send “Advertise” message to the Client which includes:
This is an example of the captured information:
LC/0/0/CPU0:Sep 5 15:26:18.351 : dhcpv6d[159]: DHCPV6 PACKET: TP765: PKT IPv6 DHCP: Det pkt cntents LC/0/0/CPU0:Sep 5 15:26:18.351 : dhcpv6d[159]: DHCPV6 PACKET: TP762: PKT: src:fe80::8678:acff:fe34:dafa dest:fe80::8146:c052:79e1:c015 << Src & Des defined by DHCP Relay Agent LC/0/0/CPU0:Sep 5 15:26:18.351 : dhcpv6d[159]: DHCPV6 PACKET: TP758: PKT: type: ADVERTISE dhcp->type:2 dhcp->xid:3882870 << DHCP Server respond with Advertise message LC/0/0/CPU0:Sep 5 15:26:18.351 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:SERVERID(2) optlen:10 LC/0/0/CPU0:Sep 5 15:26:18.351 : dhcpv6d[159]: DHCPV6 PACKET: TP725: PKT: duidbuf: 00030001c8f9f98c3e80 << DUID of the DHCP Server LC/0/0/CPU0:Sep 5 15:26:18.351 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:CLIENTID(1) optlen:14 LC/0/0/CPU0:Sep 5 15:26:18.351 : dhcpv6d[159]: DHCPV6 PACKET: TP725: PKT: duidbuf: 000100011f3c6ebb54ee75376d89 << DUID of the Client LC/0/0/CPU0:Sep 5 15:26:18.352 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:IA-NA(3) optlen:40 LC/0/0/CPU0:Sep 5 15:26:18.352 : dhcpv6d[159]: DHCPV6 PACKET: TP748: PKT: IAID 0x0x354ee75 (55897717) T1:0xa8c0 (43200) T2:0x10e00 (69120) << IAID of the Client LC/0/0/CPU0:Sep 5 15:26:18.352 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:IAADDR(5) optlen:24 LC/0/0/CPU0:Sep 5 15:26:18.352 : dhcpv6d[159]: DHCPV6 PACKET: TP729: PKT: IPV6 addr:2002:50:50:50:2cdd:1975:9b64:8453 LC/0/0/CPU0:Sep 5 15:26:18.352 : dhcpv6d[159]: DHCPV6 PACKET: TP730: PKT: preferred LC/0/0/CPU0:Sep 5 15:26:18.352 : dhcpv6d[159]: DHCPV6 PACKET: TP769: PKT: 86400 LC/0/0/CPU0:Sep 5 15:26:18.352 : dhcpv6d[159]: DHCPV6 PACKET: TP731: PKT: valid LC/0/0/CPU0:Sep 5 15:26:18.352 : dhcpv6d[159]: DHCPV6 PACKET: TP733: PKT: len:172800 LC/0/0/CPU0:Sep 5 15:26:18.353 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:DNS-SERVERS(23) optlen:16 LC/0/0/CPU0:Sep 5 15:26:18.353 : dhcpv6d[159]: DHCPV6 PACKET: TP744: PKT: ipv6_addr:2001:4860:4860::8888 LC/0/0/CPU0:Sep 5 15:26:18.353 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:DOMAIN-LIST(24) optlen:11 LC/0/0/CPU0:Sep 5 15:26:18.353 : dhcpv6d[159]: DHCPV6 PACKET: TP746: PKT: Domain_name: cisco.com
DHCP Relay Agent send “Request” message to the Server which includes:
This is an example of the captured information:
LC/0/0/CPU0:Sep 5 15:26:19.338 : dhcpv6d[159]: DHCPV6 PACKET: TP763: PKT IPv6 DHCP: Detailed packet contents LC/0/0/CPU0:Sep 5 15:26:19.338 : dhcpv6d[159]: DHCPV6 PACKET: TP762: PKT: src:fe80::8146:c052:79e1:c015 dest:ff02::1:2 << Src & Des defined by Client LC/0/0/CPU0:Sep 5 15:26:19.339 : dhcpv6d[159]: DHCPV6 PACKET: TP758: PKT: type: REQUEST dhcp->type:3 dhcp->xid:3882870 << DHCPv6 Message Type LC/0/0/CPU0:Sep 5 15:26:19.339 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:ELAPSED-TIME(8) optlen:2 LC/0/0/CPU0:Sep 5 15:26:19.339 : dhcpv6d[159]: DHCPV6 PACKET: TP738: PKT: elaspsed_time:0 LC/0/0/CPU0:Sep 5 15:26:19.339 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:CLIENTID(1) optlen:14 LC/0/0/CPU0:Sep 5 15:26:19.339 : dhcpv6d[159]: DHCPV6 PACKET: TP725: PKT: duidbuf: 000100011f3c6ebb54ee75376d89 << DUID of Client LC/0/0/CPU0:Sep 5 15:26:19.339 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:SERVERID(2) optlen:10 LC/0/0/CPU0:Sep 5 15:26:19.339 : dhcpv6d[159]: DHCPV6 PACKET: TP725: PKT: duidbuf: 00030001c8f9f98c3e80 << DUID of DHCP Server LC/0/0/CPU0:Sep 5 15:26:19.339 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:IA-NA(3) optlen:40 LC/0/0/CPU0:Sep 5 15:26:19.340 : dhcpv6d[159]: DHCPV6 PACKET: TP748: PKT: IAID 0x0x354ee75 (55897717) T1:0xa8c0 (43200) T2:0x10e00 (69120) << IAID of Client LC/0/0/CPU0:Sep 5 15:26:19.340 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:IAADDR(5) optlen:24 LC/0/0/CPU0:Sep 5 15:26:19.340 : dhcpv6d[159]: DHCPV6 PACKET: TP729: PKT: IPV6 addr:2002:50:50:50:2cdd:1975:9b64:8453 LC/0/0/CPU0:Sep 5 15:26:19.340 : dhcpv6d[159]: DHCPV6 PACKET: TP730: PKT: preferred LC/0/0/CPU0:Sep 5 15:26:19.340 : dhcpv6d[159]: DHCPV6 PACKET: TP769: PKT: 86400 LC/0/0/CPU0:Sep 5 15:26:19.340 : dhcpv6d[159]: DHCPV6 PACKET: TP731: PKT: valid LC/0/0/CPU0:Sep 5 15:26:19.340 : dhcpv6d[159]: DHCPV6 PACKET: TP733: PKT: len:172800 LC/0/0/CPU0:Sep 5 15:26:19.341 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:CLIENT-FQDN(39) optlen:26 LC/0/0/CPU0:Sep 5 15:26:19.341 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:VENDOR-CLASS(16) optlen:14 LC/0/0/CPU0:Sep 5 15:26:19.341 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:ORO(6) optlen:8 LC/0/0/CPU0:Sep 5 15:26:19.341 : dhcpv6d[159]: DHCPV6 PACKET: TP734: PKT: option: VENDOR-OPTS LC/0/0/CPU0:Sep 5 15:26:19.341 : dhcpv6d[159]: DHCPV6 PACKET: TP734: PKT: option: DNS-SERVERS LC/0/0/CPU0:Sep 5 15:26:19.341 : dhcpv6d[159]: DHCPV6 PACKET: TP734: PKT: option: DOMAIN-LIST LC/0/0/CPU0:Sep 5 15:26:19.341 : dhcpv6d[159]: DHCPV6 PACKET: TP734: PKT: option: CLIENT-FQDN
DHCP Relay Agent forward “Request” message as “ RELAY-Forward” type to the Server which includes:
This is an example of the captured information:
LC/0/0/CPU0:Sep 5 15:26:19.343 : dhcpv6d[159]: DHCPV6 PACKET: TP764: PKT IPv6 DHCP: Det pkt cntents LC/0/0/CPU0:Sep 5 15:26:19.344 : dhcpv6d[159]: DHCPV6 PACKET: TP762: PKT: src:2002:172:16:70::2 dest:2002:172:16:151::2 << Src & Des defined by DHCP Relay Agent LC/0/0/CPU0:Sep 5 15:26:19.344 : dhcpv6d[159]: DHCPV6 PACKET: TP760: PKT: type:RELAY-FORWARD relay->msgtype:12 hop:0 << DHCPv6 Message Type LC/0/0/CPU0:Sep 5 15:26:19.344 : dhcpv6d[159]: DHCPV6 PACKET: TP761: PKT: link:2002:50:50:50::5 peer:fe80::8146:c052:79e1:c015 << Link: Global IP of Relay Interface toward Client & Peer : Client's Link local IP LC/0/0/CPU0:Sep 5 15:26:19.344 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:INTERFACE-ID(18) optlen:6 LC/0/0/CPU0:Sep 5 15:26:19.344 : dhcpv6d[159]: DHCPV6 PACKET: TP774: PKT: 0x LC/0/0/CPU0:Sep 5 15:26:19.344 : dhcpv6d[159]: DHCPV6 PACKET: TP743: PKT: 0x0 (0) LC/0/0/CPU0:Sep 5 15:26:19.344 : dhcpv6d[159]: DHCPV6 PACKET: TP743: PKT: 0x4 (4) LC/0/0/CPU0:Sep 5 15:26:19.344 : dhcpv6d[159]: DHCPV6 PACKET: TP743: PKT: 0x0 (0) LC/0/0/CPU0:Sep 5 15:26:19.344 : dhcpv6d[159]: DHCPV6 PACKET: TP743: PKT: 0x0 (0) LC/0/0/CPU0:Sep 5 15:26:19.345 : dhcpv6d[159]: DHCPV6 PACKET: TP743: PKT: 0x0 (0) LC/0/0/CPU0:Sep 5 15:26:19.345 : dhcpv6d[159]: DHCPV6 PACKET: TP743: PKT: 0x4 (4) LC/0/0/CPU0:Sep 5 15:26:19.345 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:REMOTEID(37) optlen:12 LC/0/0/CPU0:Sep 5 15:26:19.345 : dhcpv6d[159]: DHCPV6 PACKET: TP725: PKT: duidbuf: 0000000900068478ac36ba56 LC/0/0/CPU0:Sep 5 15:26:19.345 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:RELAY-MSG(9) optlen:146 LC/0/0/CPU0:Sep 5 15:26:19.345 : dhcpv6d[159]: DHCPV6 PACKET: TP758: PKT: type: REQUEST dhcp->type:3 dhcp->xid:3882870 LC/0/0/CPU0:Sep 5 15:26:19.345 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:ELAPSED-TIME(8) optlen:2 LC/0/0/CPU0:Sep 5 15:26:19.346 : dhcpv6d[159]: DHCPV6 PACKET: TP738: PKT: elaspsed_time:0 LC/0/0/CPU0:Sep 5 15:26:19.346 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:CLIENTID(1) optlen:14 LC/0/0/CPU0:Sep 5 15:26:19.346 : dhcpv6d[159]: DHCPV6 PACKET: TP725: PKT: duidbuf: 000100011f3c6ebb54ee75376d89 << DUID of Client LC/0/0/CPU0:Sep 5 15:26:19.346 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:SERVERID(2) optlen:10 LC/0/0/CPU0:Sep 5 15:26:19.346 : dhcpv6d[159]: DHCPV6 PACKET: TP725: PKT: duidbuf: 00030001c8f9f98c3e80 << DUID of DHCP Server LC/0/0/CPU0:Sep 5 15:26:19.346 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:IA-NA(3) optlen:40 LC/0/0/CPU0:Sep 5 15:26:19.347 : dhcpv6d[159]: DHCPV6 PACKET: TP748: PKT: IAID 0x0x354ee75 (55897717) T1:0xa8c0 (43200) T2:0x10e00 (69120) LC/0/0/CPU0:Sep 5 15:26:19.347 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:IAADDR(5) optlen:24 LC/0/0/CPU0:Sep 5 15:26:19.347 : dhcpv6d[159]: DHCPV6 PACKET: TP729: PKT: IPV6 addr:2002:50:50:50:2cdd:1975:9b64:8453 LC/0/0/CPU0:Sep 5 15:26:19.347 : dhcpv6d[159]: DHCPV6 PACKET: TP730: PKT: preferred LC/0/0/CPU0:Sep 5 15:26:19.347 : dhcpv6d[159]: DHCPV6 PACKET: TP769: PKT: 86400 LC/0/0/CPU0:Sep 5 15:26:19.347 : dhcpv6d[159]: DHCPV6 PACKET: TP731: PKT: valid LC/0/0/CPU0:Sep 5 15:26:19.347 : dhcpv6d[159]: DHCPV6 PACKET: TP733: PKT: len:172800 LC/0/0/CPU0:Sep 5 15:26:19.347 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:CLIENT-FQDN(39) optlen:26 LC/0/0/CPU0:Sep 5 15:26:19.348 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:VENDOR-CLASS(16) optlen:14 LC/0/0/CPU0:Sep 5 15:26:19.348 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:ORO(6) optlen:8 LC/0/0/CPU0:Sep 5 15:26:19.348 : dhcpv6d[159]: DHCPV6 PACKET: TP734: PKT: option: VENDOR-OPTS LC/0/0/CPU0:Sep 5 15:26:19.348 : dhcpv6d[159]: DHCPV6 PACKET: TP734: PKT: option: DNS-SERVERS LC/0/0/CPU0:Sep 5 15:26:19.348 : dhcpv6d[159]: DHCPV6 PACKET: TP734: PKT: option: DOMAIN-LIST LC/0/0/CPU0:Sep 5 15:26:19.348 : dhcpv6d[159]: DHCPV6 PACKET: TP734: PKT: option: CLIENT-FQDN
DHCP Server respond with “Reply” message and DHCP Relay Agent receives it as a “Relay Reply” packet which includes:
This is the example of the captured information:
RP/0/RSP0/CPU0:Sep 5 15:39:21.225 : dhcpv6d[1087]: DHCPV6 PACKET: TP763: PKT IPv6 DHCP: Detailed packet contents RP/0/RSP0/CPU0:Sep 5 15:39:21.225 : dhcpv6d[1087]: DHCPV6 PACKET: TP762: PKT: src:2002:172:16:151::2 dest:2002:172:16:70::2 << Src & Dest defined by DHCP Server RP/0/RSP0/CPU0:Sep 5 15:39:21.225 : dhcpv6d[1087]: DHCPV6 PACKET: TP760: PKT: type:RELAY-REPLY relay->msgtype:13 hop:0 << DHCPv6 Message Type RP/0/RSP0/CPU0:Sep 5 15:39:21.225 : dhcpv6d[1087]: DHCPV6 PACKET: TP761: PKT: link:2002:50:50:50::5 peer:fe80::8146:c052:79e1:c015 << Link: Global IP of Relay Interface toward Client & Peer : Client's Link local IP RP/0/RSP0/CPU0:Sep 5 15:39:21.225 : dhcpv6d[1087]: DHCPV6 PACKET: TP723: PKT: optype:INTERFACE-ID(18) optlen:6 RP/0/RSP0/CPU0:Sep 5 15:39:21.225 : dhcpv6d[1087]: DHCPV6 PACKET: TP774: PKT: 0x RP/0/RSP0/CPU0:Sep 5 15:39:21.225 : dhcpv6d[1087]: DHCPV6 PACKET: TP743: PKT: 0x0 (0) RP/0/RSP0/CPU0:Sep 5 15:39:21.225 : dhcpv6d[1087]: DHCPV6 PACKET: TP743: PKT: 0x4 (4) RP/0/RSP0/CPU0:Sep 5 15:39:21.225 : dhcpv6d[1087]: DHCPV6 PACKET: TP743: PKT: 0x0 (0) RP/0/RSP0/CPU0:Sep 5 15:39:21.226 : dhcpv6d[1087]: DHCPV6 PACKET: TP743: PKT: 0x0 (0) RP/0/RSP0/CPU0:Sep 5 15:39:21.226 : dhcpv6d[1087]: DHCPV6 PACKET: TP743: PKT: 0x0 (0) RP/0/RSP0/CPU0:Sep 5 15:39:21.226 : dhcpv6d[1087]: DHCPV6 PACKET: TP743: PKT: 0x4 (4) RP/0/RSP0/CPU0:Sep 5 15:39:21.226 : dhcpv6d[1087]: DHCPV6 PACKET: TP723: PKT: optype:RELAY-MSG(9) optlen:106 RP/0/RSP0/CPU0:Sep 5 15:39:21.226 : dhcpv6d[1087]: DHCPV6 PACKET: TP758: PKT: type: REPLY dhcp->type:7 dhcp->xid:15323045 RP/0/RSP0/CPU0:Sep 5 15:39:21.226 : dhcpv6d[1087]: DHCPV6 PACKET: TP723: PKT: optype:SERVERID(2) optlen:10 RP/0/RSP0/CPU0:Sep 5 15:39:21.226 : dhcpv6d[1087]: DHCPV6 PACKET: TP725: PKT: duidbuf: 00030001c8f9f98c3e80 << DUID of DHCP Server RP/0/RSP0/CPU0:Sep 5 15:39:21.226 : dhcpv6d[1087]: DHCPV6 PACKET: TP723: PKT: optype:CLIENTID(1) optlen:14 RP/0/RSP0/CPU0:Sep 5 15:39:21.226 : dhcpv6d[1087]: DHCPV6 PACKET: TP725: PKT: duidbuf: 000100011f3c6ebb54ee75376d89 << DUID of Client RP/0/RSP0/CPU0:Sep 5 15:39:21.226 : dhcpv6d[1087]: DHCPV6 PACKET: TP723: PKT: optype:STATUS-CODE(13) optlen:9 RP/0/RSP0/CPU0:Sep 5 15:39:21.226 : dhcpv6d[1087]: DHCPV6 PACKET: TP740: PKT: status message: RP/0/RSP0/CPU0:Sep 5 15:39:21.227 : dhcpv6d[1087]: DHCPV6 PACKET: TP739: PKT: Status_code:SUCCESS << DHCP Server sends Status Message: Success RP/0/RSP0/CPU0:Sep 5 15:39:21.227 : dhcpv6d[1087]: DHCPV6 PACKET: TP723: PKT: optype:IA-NA(3) optlen:53 RP/0/RSP0/CPU0:Sep 5 15:39:21.227 : dhcpv6d[1087]: DHCPV6 PACKET: TP748: PKT: IAID 0x0x354ee75 (55897717) T1:0x0 (0) T2:0x0 (0) << DUID of Client RP/0/RSP0/CPU0:Sep 5 15:39:21.227 : dhcpv6d[1087]: DHCPV6 PACKET: TP723: PKT: optype:STATUS-CODE(13) optlen:9 RP/0/RSP0/CPU0:Sep 5 15:39:21.227 : dhcpv6d[1087]: DHCPV6 PACKET: TP740: PKT: status message: RP/0/RSP0/CPU0:Sep 5 15:39:21.227 : dhcpv6d[1087]: DHCPV6 PACKET: TP739: PKT: Status_code:SUCCESS RP/0/RSP0/CPU0:Sep 5 15:39:21.227 : dhcpv6d[1087]: DHCPV6 PACKET: TP723: PKT: optype:IAADDR(5) optlen:24 RP/0/RSP0/CPU0:Sep 5 15:39:21.227 : dhcpv6d[1087]: DHCPV6 PACKET: TP729: PKT: IPV6 addr:2002:50:50:50:2cdd:1975:9b64:8453 RP/0/RSP0/CPU0:Sep 5 15:39:21.227 : dhcpv6d[1087]: DHCPV6 PACKET: TP730: PKT: preferred RP/0/RSP0/CPU0:Sep 5 15:39:21.227 : dhcpv6d[1087]: DHCPV6 PACKET: TP769: PKT: 0 RP/0/RSP0/CPU0:Sep 5 15:39:21.227 : dhcpv6d[1087]: DHCPV6 PACKET: TP731: PKT: valid RP/0/RSP0/CPU0:Sep 5 15:39:21.228 : dhcpv6d[1087]: DHCPV6 PACKET: TP733: PKT: len:0
DHCP Relay Agent send “Reply” message to the Client which includes:
This is an example of the captured information:
LC/0/0/CPU0:Sep 5 15:39:21.229 : dhcpv6d[159]: DHCPV6 PACKET: TP765: PKT IPv6 DHCP: Det pkt cntents LC/0/0/CPU0:Sep 5 15:39:21.230 : dhcpv6d[159]: DHCPV6 PACKET: TP762: PKT: src:fe80::8678:acff:fe34:dafa dest:fe80::8146:c052:79e1:c015 < Src & Des defined by DHCP Relay Agent LC/0/0/CPU0:Sep 5 15:39:21.230 : dhcpv6d[159]: DHCPV6 PACKET: TP758: PKT: type: REPLY dhcp->type:7 dhcp->xid:15323045 << DHCPv6 Message Type LC/0/0/CPU0:Sep 5 15:39:21.230 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:SERVERID(2) optlen:10 LC/0/0/CPU0:Sep 5 15:39:21.230 : dhcpv6d[159]: DHCPV6 PACKET: TP725: PKT: duidbuf: 00030001c8f9f98c3e80 << DUID of DHCP Server LC/0/0/CPU0:Sep 5 15:39:21.230 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:CLIENTID(1) optlen:14 LC/0/0/CPU0:Sep 5 15:39:21.230 : dhcpv6d[159]: DHCPV6 PACKET: TP725: PKT: duidbuf: 000100011f3c6ebb54ee75376d89 << DUID of Client LC/0/0/CPU0:Sep 5 15:39:21.230 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:STATUS-CODE(13) optlen:9 LC/0/0/CPU0:Sep 5 15:39:21.230 : dhcpv6d[159]: DHCPV6 PACKET: TP740: PKT: status message:Status_code:SUCCESS LC/0/0/CPU0:Sep 5 15:39:21.230 : dhcpv6d[159]: DHCPV6 PACKET: TP739: PKT: LC/0/0/CPU0:Sep 5 15:39:21.230 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:IA-NA(3) optlen:53 LC/0/0/CPU0:Sep 5 15:39:21.231 : dhcpv6d[159]: DHCPV6 PACKET: TP748: PKT: IAID 0x0x354ee75 (55897717) T1:0x0 (0) T2:0x0 (0) << IAID of Client LC/0/0/CPU0:Sep 5 15:39:21.231 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:STATUS-CODE(13) optlen:9 LC/0/0/CPU0:Sep 5 15:39:21.231 : dhcpv6d[159]: DHCPV6 PACKET: TP740: PKT: status message: LC/0/0/CPU0:Sep 5 15:39:21.231 : dhcpv6d[159]: DHCPV6 PACKET: TP739: PKT: Status_code:SUCCESS << DHCP Server sends Status Message: Success LC/0/0/CPU0:Sep 5 15:39:21.231 : dhcpv6d[159]: DHCPV6 PACKET: TP723: PKT: optype:IAADDR(5) optlen:24 LC/0/0/CPU0:Sep 5 15:39:21.232 : dhcpv6d[159]: DHCPV6 PACKET: TP729: PKT: IPV6 addr:2002:50:50:50:2cdd:1975:9b64:8453 LC/0/0/CPU0:Sep 5 15:39:21.232 : dhcpv6d[159]: DHCPV6 PACKET: TP730: PKT: preferred LC/0/0/CPU0:Sep 5 15:39:21.232 : dhcpv6d[159]: DHCPV6 PACKET: TP769: PKT: 0 LC/0/0/CPU0:Sep 5 15:39:21.232 : dhcpv6d[159]: DHCPV6 PACKET: TP731: PKT: valid LC/0/0/CPU0:Sep 5 15:39:21.232 : dhcpv6d[159]: DHCPV6 PACKET: TP733: PKT: len:0
Revision | Publish Date | Comments |
---|---|---|
1.0 |
09-Apr-2017 |
Initial Release |