Ensure that you are familiar with the specific connection types for the SAN Volume Controller and the uninterruptible power supply.
Each SAN Volume Controller requires the following connections:
- Each SAN Volume Controller node
requires one Ethernet cable to connect it to an Ethernet switch or
hub. A 10/100/1000 Mb Ethernet connection is required. Both Internet
Protocol Version 4 (IPv4) and Internet Protocol Version 6 (IPv6) are
supported.Note: For increased redundancy, an optional second Ethernet connection is supported for each SAN Volume Controller node.
- To ensure cluster failover operations, Ethernet port 1 on all nodes must be connected to the same IP subnet or subnets.
- If used, Ethernet port 2 on all nodes must also be connected to the same IP subnet or subnets. However, the subnet or subnets that are connected to Ethernet port 2 do not have to be the same as the subnet or subnets that are connected to Ethernet port 1.
- Each SAN Volume Controller node has four fibre-channel ports, which are supplied fitted with LC-style optical small form-factor pluggable (SFP) gigabit interface converters (GBICs) for connection to a fibre-channel switch.
Each uninterruptible power supply requires a serial cable that connects the uninterruptible power supply to the SAN Volume Controller node. Ensure that for each node, the serial and power cables come from the same uninterruptible power supply.
TCP/IP requirements for SAN Volume Controller
To plan your installation, consider the TCP/IP address requirements of the SAN Volume Controller cluster and the requirements for the SAN Volume Controller to access other services. You must also plan address allocation and Ethernet router, gateway and firewall configuration to provide the required access and network security.
Both IPv4 and IPv6 addresses are supported. SAN Volume Controller can operate with either internet protocol or with both internet protocols concurrently.
For configuration and management, you must allocate an IP address to the cluster which is often referred to as the cluster IP address. For additional fault tolerance, you can also configure a second cluster IP address for the second ethernet port on the node. The addresses must be fixed addresses. If both IPv4 and IPv6 are operating concurrently, an address is required for each protocol.
In addition to the cluster IP addresses, the cluster is configured with one or more service IP address. Service mode addresses are used to gain access to a node that is not operating as part of the cluster for any reason. As with the cluster IP addresses, service mode IP addresses can be IPv4 addresses, IPv6 addresses, or both. You can choose a fixed IP address per ethernet port, or you can configure SAN Volume Controller to use a DHCP-allocated address.
The IBM® System Storage® Productivity Center that manages the cluster must be able to access the cluster IP addresses.
If the SAN Volume Controller console is used on a system other than the IBM System Storage Productivity Center, the system that it is run on must be able to access the IBM System Storage Productivity Center and the cluster itself.
Any system that is used to manage a node in service mode must be able to access a cluster service mode address, or a dynamically-allocated service mode address if DHCP is used.
You can configure SAN Volume Controller for event notification by SNMP, syslog or e-mail. To configure notification, you must ensure that the SNMP agent, syslog IP addresses or SMTP e-mail server IP addresses can be accessed from all SAN Volume Controller cluster addresses.
SAN Volume Controller does not use name servers to locate other devices. You must supply the numeric IP address of the device. To locate a device, the device must have a fixed IP address.
The nodes in a SAN Volume Controller cluster can receive native IPv4 or IPv6 packets. The nodes cannot operate as an endpoint of a tunnel where an IPv4 packet contains an IPv6 payload or where an IPv6 packet contains an IPv4 payload.