S2600GZ and S2600GL

Intel® Server Board S2600GZ/GL TPS Platform Management Functional Overview
6.10.3.3
IPV6 Support
In addition to IPv4, the server board has support for IPv6 for manageability channels. Configuration of IPv6 is
provided by extensions to the IPMI Set & Get LAN Configuration Parameters commands as well as through a
Web Console IPv6 configuration web page.
The BMC supports IPv4 and IPv6 simultaneously so they are both configured separately and completely
independently. For example, IPv4 can be DHCP configured while IPv6 is statically configured or vice versa.
The parameters for IPv6 are similar to the parameters for IPv4 with the following differences:
 An IPv6 address is 16 bytes vs. 4 bytes for IPv4.
 An IPv6 prefix is 0 to 128 bits whereas IPv4 has a 4 byte subnet mask.
 The IPv6 Enable parameter must be set before any IPv6 packets will be sent or received on that channel.
 There are two variants of automatic IP Address Source configuration vs. just DHCP for IPv4.
The three possible IPv6 IP Address Sources for configuring the BMC are:
Static (Manual): The IP, Prefix, and Gateway parameters are manually configured by the user. The BMC
ignores any Router Advertisement messages received over the network.
DHCPv6: The IP comes from running a DHCPv6 client on the BMC and receiving the IP from a DHCPv6
server somewhere on the network. The Prefix and Gateway are configured by Router Advertisements from the
local router. The IP, Prefix, and Gateway are read-only parameters to the BMC user in this mode.
Stateless auto-config: The Prefix and Gateway are configured by the router through Router Advertisements.
The BMC derives its IP in two parts: the upper network portion comes from the router and the lower unique
portion comes from the BMC’s channel MAC address. The 6-byte MAC address is converted into an 8-byte
value per the EUI-64* standard. For example, a MAC value of 00:15:17:FE:2F:62 converts into a EUI-64 value
of 215:17ff:fefe:2f62. If the BMC receives a Router Advertisement from a router at IP 1:2:3:4::1 with a prefix of
64, it would then generate for itself an IP of 1:2:3:4:215:17ff:fefe:2f62. The IP, Prefix, and Gateway are read-
only parameters to the BMC user in this mode.
IPv6 can be used with the BMC’s Web Console, JViewer (remote KVM and Media), and Systems Management
Architecture for Server Hardware – Command Line Protocol (SMASH-CLP) interface (ssh). There is no
standard yet on how IPMI RMCP or RMCP+ should operate over IPv6 so that is not currently supported.
6.10.3.4
LAN Failover
The BMC FW provides a LAN failover capability such that the failure of the system HW associated with one
LAN link will result in traffic being rerouted to an alternate link. This functionality is configurable from IPMI
methods as well as from the BMC’s Embedded UI, allowing for user to specify the physical LAN links constitute
the redundant network paths or physical LAN links constitute different network paths. BMC will support only a
all or nothing” approach – that is, all interfaces bonded together, or none are bonded together.
The LAN Failover feature applies only to BMC LAN traffic. It bonds all available Ethernet devices but only one
is active at a time. When enabled, If the active connection’s leash is lost, one of the secondary connections is
automatically configured so that it has the same IP address (the next active LAN link will be chosen randomly
from the pool of backup LAN links with link status as “UP”). Traffic immediately resumes on the new active
connection.
The LAN Failover enable/disable command may be sent at any time. After it has been enabled, standard IPMI
commands for setting channel configuration that specify a LAN channel other than the first will return an error
code.
6.10.3.5
BMC IP Address Configuration
Enabling the BMC’s network interfaces requires using the Set LAN Configuration Parameter command to
configure LAN configuration parameter 4, IP Address Source. The BMC supports this parameter as follows:
Revision 2.4
67