Manualshelf

3PAR InServ® E-Class/F-Class Storage Server Physical Planning Manual (320 - 200120 Rev F, September 2010)

ManualsBrandsHP ManualsStorageHP 3PAR F200 Field Starter Kit
919293949596979899100
6.6
3PAR InServ E-Class/F-Class Storage Server Physical Planning Manual
◆ At least one management station on the private network segment.
6.3 Adapter Connections for the E-Class/F-Class Controller Nodes
There are two different types of controller nodes: one is used on the E-Class and the other is
used on F-Class servers. See E-Class Controller Node on page 6.7 and F-Class Controller Node on
page 6.8 for details.
InServ Storage Servers support the following types of modules:
■ Gigabit Ethernet adapters. For the E-Class controller node, Remote Copy using Ethernet
requires one pair of Gigabit Ethernet adapters in the primary storage server and another
pair of Gigabit Ethernet adapters in a secondary or target storage server. When required,
Gigabit Ethernet adapters should be installed in controller slot 2 for the E-Class. If
controller slot 2 on the E-Class is already used for host connections, use slot 1. The F-Class
controller node has two built-in Gigabit Ethernet ports.
■ iSCSI adapters. A PCI Host Bus Adapter (HBA) with iSCSI ports connects controller nodes to
hosts. The F-Class supports 2, 2-port iSCSI adapters per node.
■ Fibre Channel SFPs (Adapter). These adapters are used to connect to the customer FC switch
and/or hosts and connect controller nodes to drive chassis within the system. They can also
be used for Remote Copy operations. The number of ports available for the host
connection will vary based on the model and configuration. Each InServ node contains a
minimum of four Fibre Channel SFP’s; for the E-Class, there are two in PCI slot 0 for drive
chassis connections, and two in slot 3 for host or drive connections. The F-Class nodes have
the four SFP’s in slot 2.
NOTE: It is strongly recommended that the private network segment also have a
management station to communicate with the service processor.
NOTE: When implementing Remote Copy interfaces, the service processor should
not be assigned to the same subnet.