HCP nodes

Installing an HCP system

Version
9.4.x
Audience
anonymous
Part Number
MK-99ARC026-23

For a fresh installation of the OS, you need to know which servers at your site are supposed to be nodes in the HCP system. For each server, you need to know:

  • The physical location.
  • The back-end IP address (see Back-end IP addresses). The back-end network information that you specify during the OS installation is for the [hcp_backend] network.
  • The front-end network IP mode (IPv4, IPv6, or Dual). The front-end network IP mode that you specify during the OS installation is used to set both the system-level IP mode and the [hcp_system] network IP mode. The front-end network IP mode must be the same on all nodes.

    The system-level IP mode setting determines whether HCP supports the use of only IPv4 addresses, only IPv6 addresses, or both types of IP addresses for all front-end networks defined on the HCP system, including the [hcp_system] network and any user-defined networks.

    The [hcp_system] network IP mode setting determines whether during the installation, the [hcp_system] network is configured to use IPv4 addresses, IPv6 addresses, or both types of IP addresses.

    Note: A user-defined network can be configured to use a specific type of IP address ONLY if the [hcp_system] network is also configured to use that type of IP address.

    For more information about the effects of the system-level IP mode setting and the [hcp_system] network IP mode setting, see Administering HCP.

  • The front-end network IP configuration settings. The front-end network IP configuration information that you specify during the OS installation is for the [hcp_system] network:
    • If the front-end network IP mode is IPv4 or Dual:
      • The front-end network IPv4 gateway IP address and subnet mask. These settings must be the same for all nodes.
      • The IPv4 address to assign to the node for the front-end network. This address must be on the same subnet as the IPv4 gateway.
    • If the front-end network IP mode is IPv6 or Dual:
      • The primary IPv6 gateway IP address and prefix length for the front-end network. These settings must be the same for all nodes.
      • The primary IPv6 address to assign to the node for the front-end network. This address must be on the same subnet as the primary IPv6 gateway.
      • If a secondary IPv6 gateway is defined for the [hcp_system] network:
        • The secondary IPv6 gateway IP address and prefix length for the front-end network. These settings must be the same for all nodes.
          Note: The primary and secondary IPv6 gateways must be on separate, non-overlapping subnets.
        • The secondary IPv6 address to assign to the node for the front-end network. This address must be on the same subnet as the secondary IPv6 gateway.
  • The bonding mode for the front-end network. With two front-end switches, HCP supports a bonding mode of active-backup. With a single front-end switch, HCP supports a bonding mode of active-active (802.3ad) for link aggregation or active-backup. The front-end network bonding mode must be the same on all nodes.
  • The interface type for the front-end network. The interface type can either be 10BaseT or SFP+ and must be the same on all nodes.
  • Whether to make the [hcp_system] network a tagged network by providing a VLAN ID for it and, if so, what VLAN ID to use. You might choose to do this if the networking infrastructure is VLAN capable. If specified, the VLAN ID must be the same on all nodes.

For information about the [hcp_system] and [hcp_backend] networks and VLAN IDs, see Administering HCP.