It is recommended that you create an IP Plan prior to installing the DSC SWe on the VMware ESXi host. The IP plan is generally created using an Excel spreadsheet and is intended to capture information such as hostname, logical IP addresses, and so on which help in configuring the DSC SWe. It is important to create the IP plan even for simple networks so that the system information is available during installation. Also, this information acts as a reference for future configuration changes.

Example IP Plan Information (IPv4)

The following example is an example IP plan for a DSC SWe VM in a redundant  High Availability (HA) configuration. In this configuration, the standby DSC SWe VM is protecting the active DSC SWe VM.

Example IP Plan for a DSC SWe VM


DSC SWe System Information

Description

Example/Recommendation
Name

The name of the DSC SWe VM.

DSC_SWe


VM 1 and VM 2 Information


Configure these details on VM 1 only (IP address information moves from VM 1 to VM 2 during a failover)

Management Ports:The configuration of the IP management interface is performed as part of the installation. Each DSC SWe VM has a redundant pair of physical ports for managing traffic.
VM 1 management IPv4 AddressSpecifies the management IPv4 address (mgt0) for VM 1.10.11.13.10
VM 2 management IPv4 AddressSpecifies the management IPv4 address (mgt1) for VM 2.10.11.13.11
Shared Management IPv4 addressSpecifies the shared management IPv4 address.10.11.13.12

Subnet Netmask

Specifies the subnet netmask.

255.255.255.0

VM management Default Gateway IP Address

Specifies the default gateway.

10.11.13.1

Packet Ports: 
VM 1 packet port IP Address (pkt0)Specifies the packet port IP address (pkt0) for VM 1.10.11.14.10
VM 1 packet port IP Address (pkt1)Specifies the packet port IP address (pkt1) for VM 1.10.11.15.10
VM 2 packet port IP Address (pkt0)Specifies the packet port IP address (pkt0) for VM 2. 10.11.14.11
VM 2 packet port IP Address (pkt1)Specifies the packet port IP address (pkt1) for VM 2.10.11.15.11

Subnet Netmask

Specifies the subnet netmask.

255.255.255.0

Caution

Each DSC SWe VM must be connected to at least two packet ports (for example, pkt0 and pkt1) for data traffic redundancy. Each packet port must be on a different subnet and cannot be on the same subnet as the management port.

Example IP Plan Information (IPv6)

The following example is an example IP plan for a DSC SWe VM in a redundant  High Availability (HA) configuration. In this configuration, the standby DSC SWe VM is protecting the active DSC SWe VM.

Example IP Plan for a DSC SWe VM


DSC SWe System Information

Description

Example/Recommendation
Name

The name of the DSC SWe VM.

DSC_SWe


VM 1 and VM 2 Information


Configure these details on VM 1 only (IP address information moves from VM 1 to VM 2 during a failover)

Management Ports:The configuration of the IP management interface is performed as part of the installation. Each DSC SWe VM has a redundant pair of physical ports for managing traffic.
VM 1 management IPv6 AddressSpecifies the management IPv4 address (mgt0) for VM 1.10:10:10:10::50
VM 2 management IPv6 AddressSpecifies the management IPv4 address (mgt1) for VM 2.10:10:10:10::51
Shared Management IPv6 addressSpecifies the shared management IPv6 address. 

Subnet Prefix

Specifies the subnet prefix

64

VM management Default Gateway IP Address

Specifies the default gateway.

 

Packet Ports: 
VM 1 packet port IP Address (pkt0)Specifies the packet port IP address (pkt0) for VM 1.20:20:20:20::60
VM 1 packet port IP Address (pkt1)Specifies the packet port IP address (pkt1) for VM 1.20:20:20:20::61
VM 2 packet port IP Address (pkt0)Specifies the packet port IP address (pkt0) for VM 2. 20:20:20:20::62
VM 2 packet port IP Address (pkt1)Specifies the packet port IP address (pkt1) for VM 2.20:20:20:20::63

Subnet Prefix

Specifies the subnet prefix.

64

Caution

Each DSC SWe VM must be connected to at least two packet ports (for example, pkt0 and pkt1) for data traffic redundancy. Each packet port must be on a different subnet and cannot be on the same subnet as the management port.