HP 5500 Ei 5500 Si Switch Series Configuration Guide
Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
139 Verifying the configuration # Display the IPv6 interface settings on Switch A. All of the IPv6 global unicast addresses configured on the interface are displayed. [SwitchA] display ipv6 interface vlan-interface 2 Vlan-interface2 current state :UP Line protocol current state :UP IPv6 is enabled, link-local address is FE80::20F:E2FF:FE00:2 Global unicast address(es): 3001::1, subnet is 3001::/64 Joined group address(es): FF02::1:FF00:0 FF02::1:FF00:1 FF02::1:FF00:2 FF02::2 FF02::1 MTU is 1500 bytes ND DAD is enabled, number of DAD attempts: 1 ND reachable time is 30000 milliseconds ND retransmit interval is 1000 milliseconds Hosts use stateless autoconfig for addresses IPv6 Packet statistics: InReceives: 25829 InTooShorts: 0 InTruncatedPkts: 0 InHopLimitExceeds: 0 InBadHeaders: 0 InBadOptions: 0 ReasmReqds: 0 ReasmOKs: 0 InFragDrops: 0 InFragTimeouts: 0 OutFragFails: 0 InUnknownProtos: 0 InDelivers: 47 OutRequests: 89 OutForwDatagrams: 48 InNoRoutes: 0 InTooBigErrors: 0 OutFragOKs: 0 OutFragCreates: 0 InMcastPkts: 6 InMcastNotMembers: 25747 OutMcastPkts: 48 InAddrErrors: 0 InDiscards: 0 OutDiscards: 0
140 [SwitchA] display ipv6 interface vlan-interface 1 Vlan-interface1 current state :UP Line protocol current state :UP IPv6 is enabled, link-local address is FE80::20F:E2FF:FE00:1C0 Global unicast address(es): 2001::1, subnet is 2001::/64 Joined group address(es): FF02::1:FF00:0 FF02::1:FF00:1 FF02::1:FF00:1C0 FF02::2 FF02::1 MTU is 1500 bytes ND DAD is enabled, number of DAD attempts: 1 ND reachable time is 30000 milliseconds ND retransmit interval is 1000 milliseconds ND advertised reachable time is 0 milliseconds ND advertised retransmit interval is 0 milliseconds ND router advertisements are sent every 600 seconds ND router advertisements live for 1800 seconds Hosts use stateless autoconfig for addresses IPv6 Packet statistics: InReceives: 272 InTooShorts: 0 InTruncatedPkts: 0 InHopLimitExceeds: 0 InBadHeaders: 0 InBadOptions: 0 ReasmReqds: 0 ReasmOKs: 0 InFragDrops: 0 InFragTimeouts: 0 OutFragFails: 0 InUnknownProtos: 0 InDelivers: 159 OutRequests: 1012 OutForwDatagrams: 35 InNoRoutes: 0 InTooBigErrors: 0 OutFragOKs: 0 OutFragCreates: 0 InMcastPkts: 79 InMcastNotMembers: 65 OutMcastPkts: 938 InAddrErrors: 0 InDiscards: 0 OutDiscards: 0
141 # Display the IPv6 interface settings on Switch B. All the IPv6 global unicast addresses configured on the interface are displayed. [SwitchB] display ipv6 interface vlan-interface 2 Vlan-interface2 current state :UP Line protocol current state :UP IPv6 is enabled, link-local address is FE80::20F:E2FF:FE00:1234 Global unicast address(es): 3001::2, subnet is 3001::/64 Joined group address(es): FF02::1:FF00:0 FF02::1:FF00:2 FF02::1:FF00:1234 FF02::2 FF02::1 MTU is 1500 bytes ND DAD is enabled, number of DAD attempts: 1 ND reachable time is 30000 milliseconds ND retransmit interval is 1000 milliseconds Hosts use stateless autoconfig for addresses IPv6 Packet statistics: InReceives: 117 InTooShorts: 0 InTruncatedPkts: 0 InHopLimitExceeds: 0 InBadHeaders: 0 InBadOptions: 0 ReasmReqds: 0 ReasmOKs: 0 InFragDrops: 0 InFragTimeouts: 0 OutFragFails: 0 InUnknownProtos: 0 InDelivers: 117 OutRequests: 83 OutForwDatagrams: 0 InNoRoutes: 0 InTooBigErrors: 0 OutFragOKs: 0 OutFragCreates: 0 InMcastPkts: 28 InMcastNotMembers: 0 OutMcastPkts: 7 InAddrErrors: 0 InDiscards: 0 OutDiscards: 0 # Ping Switch A and Switch B on the host, and ping Swit ch A and the host on Switch B to verify that they are connected.
142 IMPORTANT: When you ping a link-local address, you should use the -i parameter to specify an interface for the link-local address. [SwitchB] ping ipv6 -c 1 3001::1 PING 3001::1 : 56 data bytes, press CTRL_C to break Reply from 3001::1 bytes=56 Sequence=1 hop limit=64 time = 2 ms --- 3001::1 ping statistics --- 1 packet(s) transmitted 1 packet(s) received 0.00% packet loss round-trip min/avg/max = 2/2/2 ms [SwitchB-Vlan-interface2] ping ipv6 -c 1 2001::15B:E0EA:3524:E791 PING 2001::15B:E0EA:3524:E791 : 56 data bytes, press CTRL_C to break \ Reply from 2001::15B:E0EA:3524:E791 bytes=56 Sequence=1 hop limit=63 time = 3 ms --- 2001::15B:E0EA:3524:E791 ping statistics --- 1 packet(s) transmitted 1 packet(s) received 0.00% packet loss round-trip min/avg/max = 3/3/3 ms The output shows that Switch B can ping Switch A and the host. Troubleshooting IPv6 basics configuration Symptom The peer IPv6 address cannot be pinged. Solution 1. Use the display current-configuration c o m m a n d i n a n y v i e w o r t h e display this command in system view to verify that IPv6 is enabled. 2. Use the display ipv6 interface command in any view to verify that the IPv6 address of the interface is correct and the interface is up. 3. Use the debugging ipv6 packet command in user view to enable the debugging for IPv6 packets to help locate the cause.
143 DHCPv6 overview Introduction to DHCPv6 The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) was designed based on IPv6 addressing scheme and is used for assigning IPv6 prefixes, IPv6 addresses and other configuration parameters to hosts. Compared with other IPv6 address allocation methods (such as manual configuration and stateless address autoconfiguration), DHCPv6 can: • Record addresses assigned to hosts and assign specific addresses to hosts, thus facilitating network management. • Assign prefixes to devices, facilitating automa tic configuration and management of the entire network. • Assign other configuration parameters, such as DNS server addresses and domain names. DHCPv6 address/prefix assignment A process of DHCPv6 address/prefix assignment involves two or four messages. The following describe the detailed processes. Rapid assignment involving two messages Figure 59 Rapid assignment involving two messages As shown in Figure 59, the r apid assignment involving two messages operates in the following steps. 1. The DHCPv6 client sends out a Solicit message th at contains a Rapid Commit option, requesting that rapid assignment of address/prefix and other configuration parameters should be preferred. 2. If the DHCPv6 server supports rapid assignment, it responds with a Reply message containing the assigned IPv6 address/prefix and other configuration parameters. If the DHCPv6 server does not support rapid assignment, Assignment involving four messages is i mplemented. Assignment involving four messages Figure 60 shows the process of IPv6 address/prefix assignment involving four messages.
144 Figure 60 Assignment involving four messages The assignment involving four messages operates in the following steps: 1. The DHCPv6 client sends out a Solicit message, requesting an IPv6 address/prefix and other configuration parameters. 2. If the Solicit message does not contain a Rapid Co mmit option, or if the DHCPv6 server does not support rapid assignment even though the Soli cit message contains a Rapid Commit option, the DHCPv6 server responds with an Advertise message, informing the DHCPv6 client of the assignable address/prefix and other configuration parameters. 3. The DHCPv6 client may receive multiple Advertise messages offered by diffe rent DHCPv6 servers. It then selects an offer according to the rece iving sequence and server priority, and sends a Request message to the selected server for the confirmation of assignment. 4. The DHCPv6 server sends a Reply message to the client, confirming that the address/prefix and other configuration parameters are assigned to the client. Address/prefix lease renewal The IPv6 address/prefix assigned by the DHCPv6 server has a lease time, which depends on the valid lifetime. When the valid lifetime of the IPv6 address/prefix expires, the DHCPv6 client cannot use the IPv6 address/prefix any longer. To continue using the IPv6 address/prefix, the DHCPv6 client has to renew the lease time. As shown in Figure 61, at T1, the DHCPv6 client unicasts a Renew message to the DHCPv6 server that assigned the IPv6 address/prefix to the DHCPv6 client. The recommended value of T1 is half the preferred lifetime. Then the DHCPv6 server responds with a Reply message, informing the client about whether or not the lease is renewed. Figure 61 Using the Renew message for address/prefix lease renewal As shown in Figure 62 , i f the D HC P v6 cl ient re c eives no response from the D HC P v6 ser ver af ter sendi ng out a Renew message at T1, it multicasts a Rebind message to all DHCPv6 servers at T2 (that is, when 80% preferred lifetime expires). Then the DHCPv6 server responds with a Reply message, informing the client about whether or not the lease is renewed.
145 If the DHCPv6 client receives no response from the DHCPv6 servers, the client stops using the address/prefix when the valid lifetime expires. For more information about the valid lifetime and the preferred lifetime, see Configuring IPv6 basics. Figure 62 Using the Rebind message for address/prefix lease renewal Configuring stateless DHCPv6 After obtaining an IPv6 address/prefix, a device can use stateless DHCPv6 to obtain other configuration parameters from a DHCPv6 server. This applicat ion is called stateless DHCPv6 configuration. With an IPv6 address obtained through stateless address autoconfiguration, a device automatically enables the stateless DHCPv6 function after it receives an RA message with the managed address configuration flag (M flag) set to 0 and with the ot her stateful configuration flag (O flag) set to 1. Stateless address autoconfiguration means that a no de automatically generates an IPv6 address based on the information obtained through router/prefix discovery. For more information, see Configuring IPv6 basics. Operation Figure 63 Operation of stateless DHCPv6 As shown in Figure 63, stat eless DHCPv6 operates in the following steps: 1. The DHCPv6 client multicasts an Information- request message to the multicast address of all DHCPv6 servers and DHCPv6 relay agents. The In formation-request message contains an Option Request option, specifying the configuration parameters that the client requests from the DHCPv6 server. 2. After receiving the Information-request message, the DHCPv6 server returns the client a Reply message containing the reques ted configuration parameters. 3. The client checks the Reply message. If the obtained configuration parameters match those requested in the Information-requ est message, the client performs network configuration with the
146 parameters. If not, the client ignores the configuration parameters. If multiple replies are received, the first received reply will be used. Protocols and standards • RFC 3736, Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6 • RFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6) • RFC 2462, IPv6 Stateless Address Autoconfiguration • RFC 3633, IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6
147 Configuring DHCPv6 server Overview As shown in Figure 64, the DHCPv6 server assigns the DHCPv6 client an IPv6 prefix to facilitate IPv6 address management and network configuration. After obtaining the IPv6 prefix, the DHCPv6 client sends an RA message containing the prefix information to the subnet where it resides, so that hosts on the subnet can automatically configure their IPv6 addresses by using the prefix. A device serving as a DHCPv6 server assigns DHCPv6 clients IPv6 prefixes, but not IPv6 addresses, and supports DHCPv6 stateless configuration to assign other configuration parameters. Figure 64 Typical DHCPv6 server application Concepts DHCPv6 multicast address The multicast address FF05::1:3 identifies all DHCPv6 servers on the site-local network. The multicast address FF02::1:2 identifies all DHCPv6 servers and relay agents on the link-local link. DUID A DHCP unique identifier (DUID) uniquely identifies a DHCPv6 device (DHCPv6 client, server, or relay agent). Figure 65 DUID-LL format
148 A DUID based on link-layer address (DUID-LL) defined in RFC 3315 is used to identify a DHCPv6 device. Figure 65 sh ows the DUID-LL format, where: • DUID type —The device supports DUID-LL as the DUID type with the value of 0x0003. • Hardware type —The device supports Ethernet as the hardware type with the value of 0x0001. • Link layer address —Its value is the bridge MAC address of the device. IA Identified by an IAID, an Identity Association (IA) provides a construct through which the obtained addresses, prefixes, and other configuration parameters assigned from a server to a client are managed. A client can maintain multiple IAs, each of which is configured on an interface to manage the addresses, prefixes, and other configuration parameters obtained by that interface. IAID An IAID uniquely identifies an IA. It is chosen by the client and must be unique among the IAIDs on the client. PD The Prefix Delegation (PD) is the lease record created by the DHCPv6 server for each assigned prefix. The PD contains information such as the IPv6 prefix, clie nt DUID, IAID, valid lifetime, preferred lifetime, lease expiration time, and the IPv6 address of the requesting client. Prefix selection process Upon receiving a request, the DHCPv6 server select s the prefix and other configuration parameters from the address pool that is applied to the interface receiving the request. An address pool may contain the static prefixes configured for specific clients, or have a prefix pool referenced for dynamic assignment from the specific prefix range. A DHCPv6 server selects a prefix from the address pool according to the following sequence: 1. The desired static prefix with the DUID and IAID matching those of the client 2. The static prefix with the DUID and IAID matching those of the client 3. The desired static prefix with the DUID matching th e client’s DUID and with no client IAID specified 4. The static prefix with the DUID matching the cl ient’s DUID and with no client IAID specified 5. The desired idle prefix in the prefix pool 6. An idle prefix in the prefix pool DHCPv6 server configuration task list Before you configure the DHCPv6 server, enable IPv6 by using the ipv6 command. Task Remarks Enabling the DHCPv6 server Required Creating a prefix pool Required Configuring a DHCPv6 address pool Required Applying the address pool to an interface Required Setting the DSCP value for DHCPv6 packets Optional