Worksheet considerations

This section covers the considerations required for filling out the pre-install network configuration worksheet.

Take into account the following when filling out the worksheet:

Prior to installation, use the following table as a guide to the configuration details required for a successful ThinkAgile CP deployment.

Table 1. Configuration details guidelines

Network

IP Address Requirements

Assignment Details

Address Type

Data Center Uplink

1 IP address per Interconnect

1 Virtual IP Address (VRRP)

Statically configured at installation time

public1

OOB Interconnect

1 IP address per Interconnect

Statically configured at installation time

public

Hardware management network VLAN2

1 IP address per Interconnect

Statically configured at installation time

private

Hardware management network IP Range3

1 IP address per compute node's XCC

1 IP address per compute block SMM

1 IP address per storage controller

Dynamically configured by the DHCP server on the interconnects

private

Hypervisor VLAN

1 IP address per Interconnect

1 Virtual IP Address (VRRP)

Statically configured at installation time

public

Hypervisor IP Range

1 IP address per compute node

4 IP addresses per storage controller

Remaining IP addresses that can be assigned to application VMs vNICs and outside interfaces of NFV VMs only when the corresponding vNICs are configured in VLAN mode and assigned to the default VLAN

Dynamically configured by the DHCP server on the interconnects

public

MLAG Peers

1 IP address per Interconnect

Hard-coded values, which may be optionally be statically configured at installation time

private

VNET IP Ranges

Variable number of IP addresses, which are assigned application VM’s vNICs configured in VNET mode

Dynamically configured by the DHCP server on the NFV VM

public or private

VNET Outside Interface (optional)

1 IP address per NFV, assigned to the outside Interface of an NFV VM configured in VLAN mode and assigned a non-default VLAN

Dynamically configured by a DHCP server on the customer data center network or statically at VNET creation time

public

Application VM’s vNICs (optional)

1 IP address per vNIC, assigned to an application VM’s vNIC configured in VLAN mode and assigned a non-default VLAN

Dynamically configured by a DHCP server on the customer data center network

public

1 The term public means routable in the customer data center network. In other words, any host connected to this network must be able to reach these addresses.
2 These IP addresses are public in development environments and labs, as to allow access for debugging purposes and operating system resets during development. However, for customer installations, the recommendation is to use private IP addresses, which must not be accessible.
3 These IP addresses are public in development environments and labs, as to allow access for debugging purposes and operating system resets during development. However, for customer installations, the recommendation is to use private IP addresses, which must not be accessible.