Dell PowerConnect M6348 Configuration Guide - Page 127

IPv6, Overview, Interface Configuration, In PowerConnect M6220/M6348/M8024 switch software

Page 127 highlights

6 IPv6 This section includes the following subsections: • "Overview" on page 127 • "Interface Configuration" on page 127 • "DHCPv6" on page 130 Overview There are many conceptual similarities between IPv4 and IPv6 network operation. Addresses still have a network prefix portion (subnet) and a device interface specific portion (host). While the length of the network portion is still variable, most users have standardized on using a network prefix length of 64 bits. This leaves 64 bits for the interface specific portion, called an Interface ID in IPv6. Depending upon the underlying link addressing, the Interface ID can be automatically computed from the link (e.g., MAC address). Such an automatically computed Interface ID is called an EUI64 identifier. IPv6 packets on the network are of an entirely different format than traditional IPv4 packets and are also encapsulated in a different EtherType (contained within the L2 header to indicate which L3 protocol is used). In order to route these packets across L3 requires an infrastructure equivalent to and parallel to that provided for IPv4. NOTE: The PowerConnect M6220/M6348/M8024 switches also implement OSPFv3 for use with IPv6 networks. These configuration scenarios are included with the OSPFv2 scenarios in "OSPF" on page 74. Interface Configuration In PowerConnect M6220/M6348/M8024 switch software, IPv6 coexists with IPv4. As with IPv4, IPv6 routing can be enabled on physical and VLAN interfaces. Each L3 routing interface can be used for IPv4, IPv6, or both. Neighbor discovery is the IPv6 replacement for Address Resolution Protocol (ARP). Router advertisement is part of the neighbor discovery process and is required for IPv6. As part of router advertisement, PowerConnect M6220/M6348/M8024 switch software supports stateless auto configuration of end nodes. The switch supports both EUI-64 interface identifiers and manually configured interface IDs. IPv6 127

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158

IPv6
127
6
IPv6
This section includes the following subsections:
"Overview" on page 127
"Interface Configuration" on page 127
"DHCPv6" on page 130
Overview
There are many conceptual similarities between IPv4 and IPv6 network operation. Addresses still
have a network prefix portion (subnet) and a device interface specific portion (host). While the
length of the network portion is still variable, most users have standardized on using a network prefix
length of 64 bits. This leaves 64 bits for the interface specific portion, called an Interface ID in IPv6.
Depending upon the underlying link addressing, the Interface ID can be automatically computed
from the link (e.g., MAC address). Such an automatically computed Interface ID is called an EUI64
identifier.
IPv6 packets on the network are of an entirely different format than traditional IPv4 packets and are
also encapsulated in a different EtherType (contained within the L2 header to indicate which L3
protocol is used). In order to route these packets across L3 requires an infrastructure equivalent to
and parallel to that provided for IPv4.
NOTE:
The PowerConnect M6220/M6348/M8024 switches also implement OSPFv3 for use with IPv6 networks.
These configuration scenarios are included with the OSPFv2 scenarios in "OSPF" on page 74.
Interface Configuration
In PowerConnect M6220/M6348/M8024 switch software, IPv6 coexists with IPv4. As with IPv4, IPv6
routing can be enabled on physical and VLAN interfaces. Each L3 routing interface can be used for
IPv4, IPv6, or both.
Neighbor discovery is the IPv6 replacement for Address Resolution Protocol (ARP). Router
advertisement is part of the neighbor discovery process and is required for IPv6. As part of router
advertisement, PowerConnect M6220/M6348/M8024 switch software supports stateless auto
configuration of end nodes. The switch supports both EUI-64 interface identifiers and manually
configured interface IDs.