
Hop Limit (8 bits)
The Hop Limit field shows the number of hops remaining for packet processing. In IPv4, this is known as the Time to Live (TTL) field
and uses seconds rather than hops.
Each time the packet moves through a forwarding router, this field decrements by 1. If a router receives a packet with a Hop Limit of
1, it decrements it to 0 (zero). The router discards the packet and sends an ICMPv6 message back to the sending router indicating
that the Hop Limit was exceeded in transit.
Source Address (128 bits)
The Source Address field contains the IPv6 address for the packet originator.
Destination Address (128 bits)
The Destination Address field contains the intended recipient’s IPv6 address. This can be either the ultimate destination or the
address of the next hop router.
Extension Header Fields
Extension headers are used only when necessary. Due to the streamlined nature of the IPv6 header, adding extension headers do not
severely impact performance. Each Extension headers’s lengths vary, but they are always a multiple of 8 bytes.
Each extension header is identified by the Next Header field in the IPv6 header that precedes it. Extension headers are viewed only
by the destination router identified in the Destination Address field. If the Destination Address is a multicast address, the Extension
headers are examined by all the routers in that multicast group.
However, if the Destination Address is a Hop-by-Hop options header, the Extension header is examined by every forwarding router
along the packet’s route. The Hop-by-Hop options header must immediately follow the IPv6 header, and is noted by the value 0
(zero) in the Next Header field.
Extension headers are processed in the order in which they appear in the packet header.
Hop-by-Hop Options Header
The Hop-by-Hop options header contains information that is examined by every router along the packet’s path. It follows the IPv6
header and is designated by the Next Header value 0 (zero).
When a Hop-by-Hop Options header is not included, the router knows that it does not have to process any router specific
information and immediately processes the packet to its final destination.
When a Hop-by-Hop Options header is present, the router only needs this extension header and does not need to take the time to
view further into the packet.
The Hop-by-Hop Options header contains:
•
Next Header (1 byte)
This field identifies the type of header following the Hop-by-Hop Options header and uses the same values.
•
Header Extension Length (1 byte)
This field identifies the length of the Hop-by-Hop Options header in 8-byte units, but does not include the first 8 bytes.
Consequently, if the header is less than 8 bytes, the value is 0 (zero).
•
Options (size varies)
This field can contain one or more options. The first byte if the field identifies the Option type, and directs the router how to handle
the option.
00
Skip and continue processing.
01
Discard the packet.
IPv6 Routing
421
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...