Management network properties

The management network has the properties listed below.

IP mode (either IPv4 or IPv6)

By default, the management network for a new S Series Node has an IP mode of IPv4.

IPv4-specific properties:

IPv4 gateway address

This is the address from which communications initiated by the S Series Node are sent when the management network is the selected network for the particular type of communication and IPv4 addressing is selected.

By default, the management network has an IPv4 gateway address of 10.2.2.254.

IPv4 subnet

With the Management Console, you use the IPv4 gateway address and a four-octet subnet mask to specify the IPv4 subnet. With the management API, you use CIDR notation to specify the IPv4 subnet.

By default, the management network has an IPv4 subnet of 10.2.2.0/24 and a four-octet subnet mask of 255.255.255.0.

On an S11 or S31 Node, the management network IPv4 subnet cannot start with 192.168. On and S32 Node, the management network IPv4 subnet cannot be 192.168.255.0/24.

IPv4 address for each server module

By default, the management network has IPv4 addresses of 10.2.2.1 for server module 1 and 10.2.2.2 for server module 2.

Note: Do not use 10 as the fourth octet for the IPv4 gateway address or server module IPv4 addresses. This value is reserved for use by authorized service providers.

IPv6-specific properties:

Primary IPv6 gateway address

This is the address from which communications initiated by the S Series Node are sent when the management network is the selected network for the particular type of communication and primary IPv6 addressing is selected.

Primary IPv6 subnet

With the Management Console, you use the primary IPv6 gateway address and an IPv6 prefix length to specify the primary IPv6 subnet. With the management API, you use CIDR notation to specify the primary IPv6 subnet.

Primary IPv6 address for each server module

Optionally, secondary IPv6 settings

Gateway address, subnet, and address for each server module.

With the Management Console, you use the secondary IPv6 gateway address and an IPv6 prefix length to specify the secondary IPv6 subnet. With the management API, you use CIDR notation to specify the secondary IPv6 subnet.

Note: Do not use 000A as the last segment for the primary or secondary IPv6 gateway address or primary or secondary server module IPv6 addresses. This value is reserved for use by authorized service providers.

Combined speed and duplex setting

By default, the management network has a speed and duplex setting of auto. This setting cannot be changed.

With a setting of auto, the S Series Node detects the speed and duplex settings of the device with which it’s communicating. The S Series Node then adjusts its own setting to provide the highest possible data rate.

Maximum transmission unit (MTU)

The MTU is the largest packet size supported for data sent on the network.

The MTU for a network can be 1,500 or 9,000. The larger MTU reduces overhead and increases network throughput. An MTU of 9,000 is possible only if it is supported by the networking infrastructure.

By default, the management network has an MTU of 1,500.

VLAN ID

If the networking infrastructure supports virtual networking, valid values for the VLAN ID are integers in the range 0 through 4,094. If the networking infrastructure doesn't support virtual networking, the VLAN ID must be 0.

If the management network has a nonzero VLAN ID, the management network switches must be configured to support that ID. Additionally, the networking infrastructure must be configured to allow client requests to be routed to the S Series Node through the management network.

By default, the management network has a VLAN ID of 0.

Note: S32 Nodes use different internal VLAN IDs from the internal VLAN IDs used by S11 and S31 Nodes:

• For internal purposes, an S11 or S31 Node uses VLAN IDs of either 700 and 800 or 701 and 801. You cannot use the HCP S Series Management Console or management API to change the management network VLAN ID to a VLAN ID that's being used internally. If the management network requires the use of a VLAN ID that's being used internally, contact your authorized service provider to have the internal VLAN ID changed. In this case, changing the VLAN ID entails rebooting the S11 or S31 Node. While the S11 or S31 Node reboots, it is unavailable for both management and data access purposes.
• For internal purposes, an S32 Node uses VLAN IDs 1, 2, and 3. Therefore, these VLAN IDs cannot be used for the management network on an S32 Node.

Management network monitoring

If you don't physically connect the management network to the your networking infrastructure, you should disable monitoring for the network. If monitoring is enabled without the physical connections present, the S Series Node reports that the network is not functioning properly, and the HCP S Series Management Console displays alerts to that effect. By default, management network monitoring is enabled.