18.3.2 ICMPv6

The format and settings of ICMPv6 messages sent by the Switch conforms to RFC 2463. The following table describes the supported ICMPv6 message types.

Table 18-6 ICMPv6 messaging support spec
ICMPv6 message				Supported
Type	Code (decimal)	Detailed type	Code (decimal)	Supported
Destination Unreachable	1	no route to destination	0	OK
		communication with destination administratively prohibited	1	OK
		beyond scope of source address	2	OK
		address unreachable	3	OK
		port unreachable	4	OK
Packet Too Big	2	-	0	OK
Time Exceeded	3	hop limit exceeded in transit	0	OK
Time Exceeded	3	fragment reassembly time exceeded	1	OK
Parameter Problem	4	erroneous header field encountered	0	OK
		unrecognized Next Header type encountered	1	OK
		unrecognized IPv6 option encountered	2	OK
Echo Request	128	-	0	OK
Echo Reply	129	-	0	OK
Multicast Listener Query	130	-	0	OK
Multicast Listener Report	131	-	0	OK
Multicast Listener Done	132	-	0	OK
Router Solicitation	133	-	0	OK
Router Advertisement	134	-	0	OK
Neighbor Solicitation	135	-	0	OK
Neighbor Advertisement	136	-	0	OK
Redirect	137	-	0	OK
ICMP Node Information Response	140	A successful reply. The Reply Data field may or may not be empty	0	OK

(Legend) OK: Supported-: Not applicable

<Structure of this section>

(1) ICMPv6 Redirect Send Specifications

If the receiving interface and the sending interface are the same for a forwarded packet, the hardware determines that a decision about whether an ICMPv6 Redirect message can be sent is required, and the software determines whether an ICMPv6 Redirect message can be sent. The software sends an ICMPv6 Redirect message when the following conditions are satisfied:

The packet source and the next hop router belong to the same link.
The received IPv6 packet is not an ICMPv6 packet.

(2) ICMPv6 Time Exceeded transmit specifications

The Switch sends an ICMPv6 Time Exceeded message if the following conditions are satisfied:

The hop limit is 1 in the received IPv6 packet to be forwarded.
The received IPv6 packet is not an ICMPv6 packet.