35.1.4 ICMPv6
ICMPv6 messaging formats and settings supported by the Switch conform to RFC4443. The following table describes the supported ICMPv6 message types.
|
ICMPv6 message |
Supported |
|||
|---|---|---|---|---|
|
Type |
Code (decimal) |
Detailed type |
Code (decimal) |
|
|
Destination Unreachable |
1 |
no route to destination |
0 |
- |
|
communication with destination administratively prohibited |
1 |
- |
||
|
beyond scope of source address |
2 |
- |
||
|
address unreachable |
3 |
- |
||
|
port unreachable |
4 |
OK |
||
|
Packet Too Big |
2 |
- |
0 |
- |
|
Time Exceeded |
3 |
hop limit exceeded in transit |
0 |
- |
|
fragment reassembly time exceeded |
1 |
- |
||
|
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 |
- |
|
ICMP Node Information Response |
140 |
A successful reply. The Reply Data field may or may not be empty |
0 |
- |
(Legend) OK: Supported-: Not applicable