Here is Your Customized Document
Your Configuration is:
Action to Perform - Plan configuration Configuration Type - Basic
Storage-System Model - CX4-120
Connection Type - Fibre Channel Switch or Boot from SAN Server Operating System - HP-UX
Management Tool - EMC Navisphere Manager
Reporting Problems
To send comments or report errors regarding this document, please email:
[email protected]. For issues not related to this document, contact
your service provider.
CLARiiON® CX4™ Series
Planning Your Basic CX4-120
Storage-System Switch
Configuration with an HP-UX Server
This guide introduces the CLARiiON® CX4-120 storage system with UltraFlex™ technology in Fibre Channel switch configurations with an HP-UX server. You should read this guide:
If you are considering the purchase of one of these storage systems and want to understand its features, or
Before you plan the installation of one of these storage systems. This guide has worksheets for planning:
Hardware components
Management port network and security login information File systems and storage-system disks (LUNs and thin LUNs) For information on planning replication and/or data mobility software
(MirrorView™, SnapView™, SAN Copy™) configurations for your storage system, use the Plan Configuration link under Storage-system tasks on the CX4 support website.
These worksheets assume that you are familiar with the servers (hosts) that will use the storage systems and with the operating systems on these servers. For each storage system that you will configure, complete a separate copy of the worksheets included in this document.
For the most current, detailed, and complete CX4 series configuration rules and sample configurations, refer to the E-Lab™ Interoperability Navigator on the Powerlink® website (http://Powerlink.EMC.com). Be sure to read the notes for the parts relevant to the configuration that you are planning. For background information on the storage system, read the Hardware and Operational Overview and Technical Specifications for your storage system. You can generate the latest version of these documents
using the customized documentation Learn about storage system link under Storage-system tasks on the storage-system support website. Topics in this document are:
About the storage system ... 3
Storage-system Fibre Channel components ... 13
Storage-system management ... 29
Basic storage concepts... 48
About the storage system
Major topics are:
Storage-system overview, page 3 Fibre Channel overview, page 4
Storage-system connection limits and rules, page 8 Types of storage-system installations, page 9
Storage-system overview
The storage system provides terabytes of disk storage capacity in flexible configurations and highly available data at a low cost. End-to-end data transfer rates are up to:
8 Gb/s for Fibre Channel connections in any storage system 10 Gb/s for iSCSI connections in a storage system with
UltraFlex™iSCSI I/O modules
10 Gb/s for Fibre Channel over Ethernet (FCoE) connections in a storage system with UltraFlex FCoE I/O modules
The storage system consists of:
One storage processor enclosure (SPE)
One or more separate disk-array enclosures (DAEs) One or two standby power supplies (SPSs)
The storage processor enclosure does not include disks, and requires at least one disk-array enclosure (DAE) with a minimum of 5 disks. A maximum of 8 separate disk-array enclosures are supported for a total of 120 disks. A DAE connects to a back-end bus, which consists of two redundant loops – one loop associated with a back-end port on SP A and one loop associated with the corresponding back-end port on SP B. Since each SP has two back-end ports, the storage system has one back-end bus.You can connect a maximum of eight DAEs to one back-end bus.
Storage processor enclosure
Two storage processors (SP A and SP B) that provide the RAID (redundant array of independent disks) features of the storage system and control disk activity and host I/O.
Four power/cooling modules, two associated with SP A and two associated with SP B.
Disk-array enclosures
The storage system’s disk-array enclosures are 4 Gb/s
UltraPoint™ (point-to-point) enclosures (DAEs) that support either high-performance Fibre Channel disk modules or economical SATA (Serial Advanced Technology Attachment, SATA II) disk modules. The DAE also supports Enterprise Flash Drive Fibre Channel modules. These modules are solid state disk (SSD) Fibre Channel modules, also known as Flash or SSD disk modules or disks. You can mix Flash and standard FC disk modules, but not Flash and SATA disk modules, within a DAE. You cannot mix SATA and Fibre Channel disk modules within a DAE, but you can integrate and connect FC and SATA enclosures within a storage system. The enclosures operate at either a 2 or 4 Gb/s bus speed (2 Gb/s components, including disks, cannot operate on a 4 Gb/s bus).
Fibre Channel overview
Fibre Channel is a high-performance serial protocol that allows transmission of both network and I/O data. It is a low-level protocol, independent of data types, and supports such formats as SCSI and IP. The Fibre Channel standard supports two physical protocols that the storage system supports:
Arbitrated loop (FC-AL) for direct connection to a host (server) Switch fabric connection to a host (server)
A Fibre Channel arbitrated loop is a circuit consisting of nodes. Each node has a unique address, called a Fibre Channel arbitrated loop address.
A Fibre Channel switch fabric is a set of point-to-point connections between nodes; each connection is made through one or more Fibre Channel switches. Each node may have its own unique address, but the path between nodes is governed by a switch.
cables connect nodes directly to the storage system or to switches. An optical cable can transmit data over great distances for connections that span entire enterprises and can support remote disaster recovery systems. We strongly recommend the use of OM3 50 μm cables for all optical connections.
Each device in an arbitrated loop or a switch fabric is a server adapter (initiator) or a target (storage-system Fibre Channel SP data port). Figure 1 shows an initiator node and target node.
EMC1802
Server adapter (initiator)
Connection
Storage system (target) Node
Adapter
Node
Figure 1 Fibre Channel nodes - initiator and target connections (1 of up to 6 connections to an SP shown)
In addition to one or more storage systems, a Fibre Channel storage configuration has two main components:
A server component (host bus adapter driver with adapter and software)
Interconnection components (cables based on Fibre Channel standards and switches)
Fibre Channel initiator components (host bus adapter and driver)
The host bus adapter is a printed-circuit board that slides into an I/O slot in the server’s cabinet. Under the control of a driver, the adapter transfers data between server memory and one or more storage systems over a Fibre Channel connection.
Fibre Channel target components
Target components are the target portals that accept and respond to requests from an initiator. The Fibre Channel target portals are the front-end Fibre Channel data ports on the storage-system SP. Each SP has 2 or 6 Fibre Channel front-end ports per SP. The Fibre Channel front-end (data) ports communicate with Fibre Channel switches
or servers. The connectivity speeds supported by these front-end ports depends on the type of Fibre Channel UltraFlex™ I/O module that has the ports. The 4 Gb/s Fibre Channel I/O modules support 1/2/4 GB/s front-end connectivity and the 8 Gb/s Fibre Channel I/O modules support 2/4/8 Gb/s front-end connectivity. You cannot use 8 Gb/s Fibre Channel I/O modules in an 1 Gb/s Fibre Channel environment. You can use 4 Gb/s Fibre Channel I/O modules in an 8 Gb/s environment if the Fibre Channel interconnection components auto-adjust their speeds to 4 Gb/s.
Fibre Channel interconnection components
The interconnection components consist of optical cables between components and Fibre Channel switches.
The maximum length of the optical cable between a storage system and a server or switch ranges from 10 to 500 meters (11 to 550 yards), depending on the type of cable and operating speed. With extenders, connections between servers, switches, and other devices can span up to 60 kilometers (36 miles) or more. This ability to span great distances is a major advantage of using optical cables. We strongly recommend the use of OM3 50 μm cables for all optical connections. Details on cable lengths and rules for using them are in Table 9.
Fibre channel switches
A Fibre channel switch, which is required for shared storage in a storage area network (SAN), connects all the nodes cabled to it using a fabric topology. A switch adds serviceability and scalability to any installation; it allows online insertion and removal of any device on the fabric and maintains integrity if any connected device stops participating. A switch also provides server-to-storage-system access control and point-to-point connections. Figure 2 shows a Fibre channel switch.
EMC1805 A da pte r Server A da pte r Server A da pte r Server SP SP SP SP
Storage system Storage system
Figure 2 Fibre channel switch connections (1 of up to 6 connections to one SP in each storage system shown)
You can cascade switches (connect one switch port to another switch port) for additional port connections.
Fibre Channel switch zoning
Switch zoning lets an administrator define paths between connected nodes based on the node’s unique World Wide Name. Each zone includes a server adapter node and/or one or more SP nodes. We recommend single-initiator zoning, which limits each zone to a single HBA port (initiator).
In Figure 3, the dotted lines show the zone that allows server 1 has access to one SP in storage systems 1 and 2; server 1 has no access to any other SP.
Zone
Server 1 Server 2 Server 3
Storage system 1 SP Storage system 2 SP Storage system 3 SP SP Switch EMC1806 SP SP Adapter Adapter Adapter
To illustrate switch zoning, Figure 3 shows just one HBA per server and one switch. Normally, such installations include multiple HBAs per server and two or more switches. In general a server should be zoned to 2 ports on each SP in a redundant configuration. If you do not define a zone in a switch, all adapter ports connected to the switch can communicate with all SP ports connected to the switch.
Fibre Channel switches are available with 8, 16, 32, or more ports. They are compact units that fit into a rackmount cabinet.
If your servers (hosts) and storage systems will be far apart, you can place the switches closer to the servers or storage systems, as convenient.
A switch is technically a repeater, not a node, in a Fibre Channel loop. However, it is bound by the same cabling distance rules as a node.
Storage-system connection limits and rules
For an initiator to communicate with a storage-system target, it must be registered with the storage system. Table 1 lists the number of initiators that can be registered with the storage system.
Table 1 Number of initiators that can be registered with a storage system Maximum number of initiators
FLARE version Per SP Per storage system
FLARE 04.29 or later 256 512
FLARE 04.28 128 256
A CNA can run both 10 GbE iSCSI and FCoE at the same time. As a general rule, a single server cannot connect to the same storage system through both the storage system’s iSCSI data ports and FCoE data ports or through both the storage system’s iSCSI data ports and Fibre Channel data ports. The same general rule applies to servers in a cluster group connected to the storage system. For example, you must not connect one server in the cluster to the storage system’s iSCSI data ports and another server in the cluster to the storage system’s FCoE or Fibre Channel data ports. A single server with both Fibre Channel HBAs and CNAs can connect through the same FCoE switch to the same storage system through the storage’s Fibre Channel data ports and FCoE data ports.
Servers with virtual machines or virtual systems that run different instances of the Navisphere® Host Agent than the kernel system runs are the exception to this rule. The initiators on servers that the host agent registers with the storage system for the kernel system and that the host agent registers with the storage system for the virtual machines appear to be from different servers. As a result, you can connect them to different storage groups.
You can attach a single server to a CX4 series, CX3 series, or CX series storage system and an AX4-5 series or AX series storage system at the same time only if the following conditions are met:
The server is running the Unisphere Server Utility and/or the Unisphere Host Agent or version 6.26.5 or later of the Navisphere Server Utility and/or the Navisphere Host Agent.
The AX4-5 series and AX series storage systems are running Navisphere® Manager software.
The master of the domain with these storage systems is one of the following:
z A CX4 series storage system
z A CX3 series storage system running FLARE 03.26.xxx.5.014 or later
z A CX series storage system running FLARE 02.24.xxx.5.018 or later
z An AX4-5 storage system running FLARE 02.23.050.5.5xx or later
z Either a Unisphere management station or a Navisphere management station running the Navisphere UIs version 6.28 or later.
Types of storage-system installations
You can use a storage system in any of several types of installation: Unshared direct with one server is the simplest and least costly. Shared or clustered direct lets multiple servers share the storage
system.
Shared switchedwith two or more Fibre Channel switch fabrics or network switches or routers lets multiple servers share the resources of several storage systems in a storage area network
(SAN). Shared switched or network storage systems can have multiple paths to each SP, providing multipath I/O for dynamic load sharing and greater throughput.
Figure 4 shows the three types of storage-system installation.
EMC1826b Server component Interconnection component Storage component Unshared direct (one or two servers)
Shared or clustered direct (two servers)
Shared switched (multiple servers, multiple paths to SPs)
Adapter
Server Server Server Server Server Server
Path 1 Path 2
SP A SP B SP A SP B SP A SP B SP A SP B SP A SP B
Storage system Storage system Storage system Storage system Storage system
Adapter Adapter Adapter Adapter Adapter Adapter Adapter Adapter Adapter Adapter Adapter
FC or FCoE switch or LAN
FC or FCoE switch or LAN
Figure 4 Types of storage-system installation
The shared or clustered direct installation can be either shared (that is, with storage groups on the storage system enabled to control LUN access) or clustered (that is, with operating system cluster software controlling LUN access). In a clustered configuration, data access control on the storage system can be either enabled or disabled. The number of servers in the cluster varies with the operating system. About shared switched or network storage and storage area networks
A storage area network (SAN) is one or more storage devices connected to servers through switches to provide a central location for disk storage. Centralizing disk storage among multiple servers has many advantages, including:
Highly available data
Flexible association between servers and storage capacity
Easier file backup and recovery
A SAN is based on shared storage; that is, the SAN requires that storage-system storage groups are enabled to provide flexible access control to storage-system LUNs. Within the SAN, a network connection to each SP in the storage system lets you configure and manage the storage system. Figure 5 shows the components of a SAN.
EMC1810c
Server Server Server
Storage system SP A SP B Storage system SP A SP B Path 1 Path 2
Adapter Adapter Adapter Adapter Adapter Adapter
FC or FCoE switch or LAN
FC or FCoE switch or LAN
Figure 5 Components of a SAN
In a Fibre Channel environment, the switches can control data access to storage systems through the use of switch zoning. Switch zoning cannot selectively control data access to LUNs in a storage system because each SP appears as a single Fibre Channel device to the switch fabric. Switch zoning and restrictive authentication can prevent or allow communication with an SP, but not with specific disks or LUNs attached to an SP. For access control with LUNs, a different solution is required: storage groups.
Storage groups
Storage groups are the central component of shared storage; a storage system that is unshared (that is, dedicated to a single server) does not need to use storage groups. When you configure shared storage, you create a storage group and specify which server(s) can access it (read from and/or write to it).
More than one server can access the same storage group only if all the servers run cluster software. The cluster software enforces orderly access to the shared storage group LUNs.
Figure 6 shows a simple shared storage configuration consisting of one storage system with two storage groups. One storage group serves a cluster of two servers running the same operating system, and the other storage group serves a database server with a different operating system. Each server is configured with two independent paths to its data, including separate host bus adapters, switches, and SPs, so there is no single point of failure for access to its data.
EMC1811c
Highly available cluster
File server Operating system A Mail server Operatin g system A Database server Operatin g system B SP A SP B LUN LUN LUN LUN LUN LUN LUN Physical storage system Cluster storage group Database server storage group Pa th 1 Pa th 2
Adapter Adapter Adapter Adapter Adapter Adapter
FC or FCoE switch or LAN
FC or FCoE switch or LAN
Storage-system Fibre Channel components
This section helps you plan the hardware components – adapters, cables, storage system requirements, and site requirements – for each server in your installation.
Major topics are:
Storage-system hardware components, page 13 Hardware components worksheet, page 25 Cache worksheet, page 28
Storage-system hardware components
The basic storage-system hardware components are:
Storage processor enclosure (SPE) – a sheet-metal housing with a front cover (bezel), midplane, and slots for the following components:
z A pair of redundant storage processors (SP A and SP B), each with a CPU module and an I/O carrier with slots for UltraFlex™ I/O modules
z Four power supply/system cooling modules (referred to as power/cooling modules), two associated with SP A and two associated with SP B
Two separate standby power supplies (SPSs) support write caching and provide the highest data availability.
One or more disk-array enclosures (DAEs) with slots for 15 disks. One DAE with at least five disks is required.
Figure 7 and Figure 8 show the SPE components. If the enclosure provides slots for two identical components, the component in slot A is called component-name A. The second component is called component-name B. For increased clarity, the following figures depict the SPE outside of the rack cabinet. Your SPE may arrive installed in a rackmount cabinet.
CPU module A CPU module B CL4135
Power/cooling modules A0 - A1 Power/cooling modules B0 - B1
Figure 7 SPE components (front with bezel removed)
CL4134 12 3 10/100/1000 0 10/100/1000 0 Management module B Management module A SP A SP B
Figure 8 SPE components (back)
Storage processor
The storage processor (SP) provides the intelligence of the storage system. Using its own proprietary software (called FLARE® Operating Environment), the SP processes the data written to or read from the disk modules, and monitors the disk modules. An SP consists of a CPU module printed-circuit board with two central processing module and memory modules, associated UltraFlex I/O modules, and status lights. Each SP uses UltraFlex I/O modules for Fibre Channel (FC), FCoE, and iSCSI front-end port connectivity to hosts (servers) and Fibre Channel (FC) back-end port connectivity to disks with the standard configurations listed in Table 2.
Table 2 Standard SP port configurations Storage system iSCSI server ports (see note) FC server ports (see note) FCoE ports (see note) FC back-end ports CX4-120 2 2 2 1
Each SP can have one optional UltraFlex I/O module for additional iSCSI, Fibre Channel, or FCoE server ports.
Each SP also has an Ethernet connection through which the EMC Navisphere® management software lets you configure and reconfigure the LUNs and storage groups in the storage system. Since each SP connects to a network, you can still reconfigure your system, if needed, should one SP fail.
UltraFlex I/O modules
Table 3 lists the number of I/O modules the storage system supports and the slots the I/O modules can occupy. More slots are available for optional I/O modules than the maximum number of optional I/O modules supported because some slots are occupied by required I/O modules. With the exception of slots A0 and B0, the slots occupied by the required I/O modules can vary between configurations. Figure 9 shows the I/O module slot locations and the I/O modules for the standard minimum configuration with 1 GbE iSCSI modules. The 1 GbE iSCSI modules shown in this example could be 10 GbE iSCSI or FCoE I/O modules.
Table 3 Number of supported I/O modules per SP
All I/O modules Optional I/O modules
Storage system
Number
supported per SP SP A slots SP B slots
Number
supported per SP SP A slots SP B slots
CL4127 12 3 10/100/1000 0 10/100/1000 0 B0 B1 B2 B3 B4 A0 A1 A2 A3 A4
Figure 9 I/O module slot locations (1 GbE iSCSI and FC I/O modules for a standard minimum configuration shown)
The following types of modules are available: 4 or 8 Gb Fibre Channel (FC) modules with either:
z 2 back-end (BE) ports for disk bus connections and 1 front-end (FE) port for server I/O connections (connection to a switch or server HBA).
or
z 4 front-end (FE) ports for server I/O connections (connection to a switch or server HBA).
The 8 Gb FC module requires FLARE 04.28.000.5.7xx or later. 10 Gb Ethernet (10 GbE) FCoE module with 2 FCoE front-end (FE)
ports for server I/O connections (connection to a FCoE switch and from the switch to the server CNA). The 10 GbE FCoE module requires FLARE 04.30.000.5.5xx or later.
1 Gb Ethernet (1 GbE) or 10 Gb Ethernet (10 GbE) iSCSI module with 2 iSCSI front-end (FE) ports for network server iSCSI I/O connections (connection to a network switch, router, server NIC, or iSCSI HBA). The 10 GbE iSCSI module requires FLARE 04.29 or later.
Table 4 lists the I/O modules available for the storage system and the number of each module that is standard and/or optional.
Table 4 I/O modules per SP
Number of modules per SP
Module Standard Optional
4 or 8 Gb FC module: 1 BE port (0)
2 FE ports (2, 3) (port 1 not used)
1 0
4 or 8 Gb FC module: 4 FE ports (0, 1, 2, 3)
0 1
10 GbE FCoE module: 2 FE ports (0, 1)
1 or 0 (see note 1) 1 (see note 2)
1 or 10 GbE iSCSI module: 2 FE ports (0, 1)
1 or 0 (see note 1) 1 (see note 2)
Note 1: The standard system has either 1 FCoE module or 1 iSCSI module per SP, but not both types.
Note 2: The maximum number of 10 GbE FCoE modules or 10 GbE iSCSI I/O modules per SP is 1.
IMPORTANT
Always install I/O modules in pairs – one module in SP A and one module in SP B. Both SPs must have the same type of I/O modules in the same slots. Slots A0 and B0 always contain a Fibre Channel I/O module with one back-end port and two front-end ports. The other available slots can contain any type of I/O module that is supported for the storage system.
The actual number of each type of optional Fibre Channel, FCoE, and iSCSI I/O modules supported for a specific storage-system configuration is limited by the available slots and the maximum number of Fibre Channel, FCoE, and iSCSI front-end ports supported for the storage system. Table 5 lists the maximum number of Fibre Channel, FCoE, and iSCSI FE ports per SP for the storage system.
Table 5 Maximum number of front-end (FE) ports per SP Storage system Maximum Fibre Channel FE ports per SP Maximum FCoE FE ports per SP Maximum iSCSI FE ports per SP (see note) CX4-120 6 4 4
Note: The maximum number of 10 GbE iSCSI ports per SP is 2. Back-end (BE) port connectivity
Each FC back-end port has a connector for a copper SFP-HSSDC2 (small form factor pluggable to high speed serial data connector) cable. Back-end connectivity cannot exceed 4 Gb/s regardless of the I/O module’s speed. Table 6 lists the FC modules that support the back-end bus.
Table 6 FC I/O module ports supporting back-end bus
Storage system and FC modules Back-end bus (module port) CX4-120
FC module in slots A0 and B0 Bus 0 (port 0) Fibre Channel (FC) front-end connectivity
Each 4 Gb or 8 Gb FC front-end port has an SFP shielded Fibre Channel connector for an optical cable. The FC front-end ports on a 4 Gb FC module support 1, 2, or 4 Gb/s connectivity, and the FC front-end ports on an 8 Gb FC module support 2, 4, or 8 Gb/s connectivity. You cannot use the FC front-end ports on an 8 Gb FC module in a 1 Gb/s Fibre Channel environment. You can use the FC front-end ports on a 4 Gb FC module in an 8 Gb/s Fibre Channel environment if the FC switch or HBA ports to which the module’s FE ports connect auto-adjust their speed to 4 Gb/s.
Storage-system caching
The storage systems have an SP cache consisting of dynamic random access memory (DRAM) on each storage processor (SP). A standby power supply (SPS) protects data in the cache from power loss. If line power fails, the SPS provides sufficient power to let the storage system write cache contents to the vault disks. The vault disks are standard disk modules that store user data but have space reserved for outside
operating system control. When power returns, the storage system reads the cache information from the vault disks, and then writes it to the file systems on the disks. This design ensures that all write-cached information reaches its destination. During normal operation, no I/O occurs with the vault; therefore, a disk’s role as a vault disk has no effect on its performance.
Storage-system caching improves read and write performance for LUNs. Write caching, particularly, helps write performance – an inherent problem for RAID types that require writing to multiple disks. Read and write caching improve performance in two ways:
For a read request – If a read request seeks information that is already in the SP read or write cache, the storage system can deliver it immediately, much faster than a disk access can.
For a write request – The storage system writes updated information to SP write-cache memory instead of to disk, allowing the server to continue as if the write had actually completed. The write to disk from cache memory occurs later, at the most expedient time. If the request modifies information that is in the cache waiting to be written to disk, the storage system updates the information in the cache before writing it to disk; this requires just one disk access instead of two.
The FAST Cache is based on the locality of reference of the data set requested. A data set with high locality of reference and that is most frequently accessed is a good candidate for promotion to the FAST Cache. By promoting the data set to the FAST Cache the storage system services any subsequent requests for this data faster from the Flash disks that make up the FAST Cache, thus reducing the load on the disks in the LUNs that contain the data (the underlying disks). Applications such as File and OLTP (online transaction processing) have data sets that can benefit from the FAST Cache. Disks
The disks – available in different capacities – fit into slots in the DAE. The storage system supports 4 Gb/s DAEs with the high-performance Fibre Channel disks or economical serial ATA (SATA) disks. The 1 TB SATA disks operate on a 4 Gb/s back-end bus like the 4 Gb FC disks, but have a 3 Gb/s bandwidth. Since they have a Fibre Channel interface to the back-end loop, these disks are sometimes referred to as Fibre Channel disks. For information on the currently available disks and their usable capacities, refer to the EMC® CX4 Series Storage
Systems – Disk and FLARE® OE Matrix (P/N 300-007-437) on the EMC
Powerlinkwebsite.
The 1 TB, 5.4K rpm disks are available only in a DAE that is fully populated with these disks, and they cannot be mixed with or replaced by the 1 TB, 7.2 rpm disks in a DAE.
Each disk has a unique ID that you use when you create a RAID group containing the disk or when you monitor the disk’s operation. The ID is derived from the Fibre Channel loop number, enclosure address, and disk slot in the enclosure.
Enclosure 0 on bus 0 in the storage system must contain disks with IDs 000 through 004. The remaining disk slots can be empty unless they are 1 TB, 5.4K rpm disks, in which case all the disks in the DAE must be 1 TB, 5.4K rpm disks. You can mix Flash (SSD) disks and standard Fibre Channel disks, but not Flash and SATA disks, in the same enclosure.You cannot mix Fibre Channel and SATA disks in the same enclosure. Disk power savings
Some disks have a power savings (spin-down) option, which lets you assign power savings settings to a RAID group composed of these disks in a storage system running FLARE 04.29 or later. If power savings is enabled for both the storage system and the RAID group, the disks in the RAID group will transition to the low power state after being idle for at least 30 minutes. Power savings is not supported for a RAID group if any LUN in the RAID group is participating in a MirrorView/A, MirrorView/S, SnapView, or SAN Copy session. Background verification of data (sniffing) does not continue when disks are in a low power state. For the currently available disks that support power savings, refer to the EMC® CX4 Series Storage Systems – Disk and FLARE® OE Matrix (P/N 300-007-437) on the EMC Powerlink website. Basic requirements for shared storage and unshared configurations
For shared switch storage, you need the components described below. Components for shared switched storage
For shared switched storage, you must use a high-availability configuration. The minimum hardware required for shared switched storage is two servers, each with two Fibre Channel HBAs, two Fibre Channel switch fabrics with one switch per fabric, and one storage system. You can use more servers, more Fibre Channel switches per fabric, and more storage systems (up to four are allowed).
Dimensions and weight
Table 7 CX4-120 hardware dimensions and weight
Component Dimensions Vertical size Weight (see notes)
SPE Height: 8.90 cm (3.50 in) Width: 44.50 cm (17.50 in) Depth: 62.60 cm (24.25 in)
2 NEMA units 23.81 kg (52.5 lb)
DAE Height: 13.34 cm (5.25 in) Width: 45.0 cm (17.72 in) Depth: 35.56 cm (14.00 in)
3 NEMA units 30.8 kg (68 lb) with 15 disks
SPS Height: 4.02 cm (1.58 in)
Mounting tray width: 42.1 cm (16.5 in) Depth: 60.33 cm (23.75 in)
1 NEMA units 10.8 kg (23.5 lb) per SPS
Notes: Weights do not include mounting rails. Allow 2.3- 4.5 kg (5-10 lb) for a rail set. A fully configured DAE includes 15 disk drives that typically weigh 1.0 kg to 1.1 kg (2.25 to 2.4 lb) each. The weights listed in this table do not describe enclosures with Enterprise Flash Drives (solid state disk drives with Flash memory, or SSD drives). Each SSD drive module weighs 20.8 ounces (1.3 lb).
Cabinet for hardware components
The 19-inch wide cabinet, prewired with AC power strips and ready for installation, has the dimensions listed in Table 8.
Table 8 Cabinet dimensions
Dimension 40U-C cabinet
Height (internal, usable for devices) 40U (179 cm; 70 in) from floor pan to cabinet top (fan installed) Height (overall) 190 cm (75 in)
Width (usable for devices) NEMA 19 in standard; rail holes 45.78 cm (18.31 in) apart center-to-center
Width (overall) 60 cm (24 in)
Depth (front to back rail) 60 cm (24 in)
98.425 cm (39.37 in) without front door Depth (overall)
103.75 cm (41.5 in) with optional front door 177 kg (390 lb) maximum without front door Weight (empty)
200 kg (440 lb) maximum with optional front door Maximum total device weight supported 945 kg (2100 lb)
2U SPE 3U DAE 1U 1200W SPS 1U or 2U switch
The cabinet requires 200 to 240 volts AC at 50/60 Hz, and includes 2 to 4 power strips with compatible outlets. Plug options are L6-30P and IEC 309 30 A.
Filler panels of various sizes are available. Data cable and configuration guidelines
Each Fibre Channel data port that you use on the storage system requires an optical cable connected to either a server HBA port or a switch port. The cabling between the SPE and the DAEs and between the DAEs is copper. Generally, you should minimize the number of cable connections, since each connection degrades the signal slightly and shortens the maximum distance of the signal.
SP optical cabling to a switch or server
Optical cables connect the small form-factor pluggable (SFP) modules on the storage processors (SPs) to the external Fibre Channel or 10 Gb Ethernet environment. EMC strongly recommends the use of OM3 50 µm cables for all optical connections. Table 9 lists the optical cables that are available for your storage system.
Table 9 Optical cables
Cable type Operating speed Length
1.0625 Gb 2 m (6.6 ft) minimum to 500 m (1,650 ft) maximum 2.125 Gb 2 m (6.6 ft) minimum to 300 m (990 ft) maximum 4 Gb 2 m (6.6 ft) minimum to 150 m (495 ft) maximum 8 Gb OM3: 1 m (3.3 ft) minimum to 150 m (495 ft) maximum OM2: 1 m (3.3 ft) minimum to 50 m (165 ft) maximum 50µm 10 Gb OM3: 1 m (3.3 ft) minimum to 300 m (990 ft ) maximum
Cable type Operating speed Length OM2: 1 m (3.3 ft) minimum to 82 m (270 ft) maximum 1.0625 Gb 2 m (6.6 ft) minimum to 300 m (985 ft) maximum 2.125 Gb 2 m (6.6 ft) minimum to 150 m (492 ft) maximum 62.5µm 4 Gb 2 m (6.6 ft) minimum to 70 m (231 ft) maximum Notes: All cables are multi-mode, dual LC with a bend radius of 3 cm (1.2 in) minimum. The maximum length for either the 62.5 µm or 50 µm cable (noted in the table above) includes two connections or splices between source and destination.
!
CAUTIONEMC does not recommend mixing 62.5μm and 50 μm optical cables in the same link. In certain situations you can add a 50μm adapter cable to the end of an already installed 62.5μm cable plant. Contact your service representative for details.
SP-to-DAE and DAE-to-DAE copper cabling
The expansion port interface to the DAE is copper cabling. The following copper cables are available:
Cable type Length
SFP-to-HSSDC2 for SP-to-DAE 2 m (6.6 ft) 5 m (16.5 ft) HSSDC2-to-HSSDC2 for DAE-to-DAE 2 m (6.6 ft)
5 m (16.5 ft) 8 m (26.4 ft)
The cable connector can be either a direct-attach shielded SFP (small form-factor pluggable) module or an HSSDC2 (high speed serial data connector), as detailed below:
SP connector — Shielded, 150 Ω differential, shield-bonded to SFP plug connector shell (360°), SFF-8470 150 specification for SFP transceiver.
DAE connector — Shielded, 150 Ω differential, shield-bonded to plug connector shell (360°) FC-PI-2 standard, revision 13 or later for HSSDC2.
DAE enclosure addresses
Each disk enclosure in a Fibre Channel bus must have a unique enclosure address (also called an EA, or enclosure ID) that identifies the enclosure and determines disk module IDs. In many cases, the factory sets the enclosure address before shipment to coincide with the rest of the system; you will need to reset the selection if you install the enclosure into your rack independently. The enclosure address ranges from 0 through 7.
Figure 10 shows sample back-end connections for a storage system with eight DAEs on its bus. The figure shows a configuration with DAE2P or DAE3Ps as the only disk-array enclosures. Environments with a mix of DAE2s and DAE2Ps and/or DAE3Ps follow the same EA, bus balancing, and cabling conventions whenever possible and practical. Each DAE supports two completely redundant loops.
! ! ! ! ! EXP PRI EXP PRI # ! PRI EXP EXP PRI # A B ! ! ! ! ! EXP PRI EXP PRI # ! PRI EXP EXP PRI # A B ! ! ! ! ! EXP PRI EXP PRI # ! PRI EXP EXP PRI # A B ! ! ! ! ! EXPPRI EXP PRI # ! EXP PRI EXP PRI # A B ! ! ! ! ! EXPPRI EXP PRI # ! EXP PRI EXP PRI # A B ! ! ! ! ! EXP PRI EXP PRI # ! PRI EXP EXP PRI # A B ! ! ! ! ! EXPPRI EXP PRI # ! PRI EXP EXP PRI # A B ! ! ! ! ! EXPPRI EXP PRI # ! PRI EXP EXP PRI # A B SP A SP B B A EA0/Bus 0 EA1/Bus 0 EA2/Bus 0 EA3/Bus 0 EA5/Bus 0 EA6/Bus 0 EA7/Bus 0 EA4/Bus 0 10/100/1000 0 1 01 2 3 10/100/1000 01 2 3 10/100/1000 1000 Base-X 23 0 1 10/100/1000 10/100/1000 0 1 01 2 3 10/100/1000 01 2 3 10/100/1000 1000 Base-X 23 0 1 10/100/1000 CL4124
Figure 10 Sample storage-system configuration with eight DAEs
Hardware components worksheet
Use the worksheet in Table 10 and the cable planning template in Figure 11 to plan the hardware components you want. Some installation types do not have switches or multiple servers.
Table 10 Hardware components worksheet Server information
Server name: Server operating system:
Adapters in server:
Server name: Server operating system:
Adapters in server:
Server name: Server operating system:
Adapters in server:
Server name: Server operating system:
Adapters in server:
Storage-system components
SPEs: DAEs: Cabinets:
Fibre Channel switch information
32-port: 24-port: 16-port: 8-port:
Cables between server and Fibre Channel switch ports — cable A
Cable A1 number: Length (m or ft):
Cable A2 number: Length (m or ft):
Cable A3 number: Length (m or ft):
Cable A4 number: Length (m or ft):
Cables between Fibre Channel switch ports and storage-system SP Fibre Channel data ports — cable B Cable B1 (up to 6 per CX4-120 or CX4-240 SPE SP, optical) number: Length (m or ft): Cable B2 (up to 6 per CX4-120 or CX4-240 SPE SP, optical) number: Length (m or ft):
Cables between enclosures — cable C
Cable C1 (copper) number (2 per SPE): Length (m or ft):
EMC3571 Switch 1 Switch 2 Ad a pter Ad a pter Ad a pter Ad a pter Ad a pter Ad a pter B1 B2 Cable between server and switch Cable between switch and storage system Cable between enclosures LCC LCC D AE LCC LCC D AE LCC LCC D AE LCC LCC D AE LCC LCC D AE LCC LCC D AE SP B SP A SPE C1 C2 C2 C2 C2 C1 C2 C2 C2 C2 Path 1 Path 2
Other paths not cabled
A1 Am An
A4
A2 A3
C2 C2
Figure 11 Cable planning template for a shared storage system (two front-end cables per SP shown)
Cache worksheet
Use the worksheet in Table 11 to plan your cache configuration. Table 11 Cache worksheet
Cache information
Read cache size: Write cache size:
Cache page size:
Cache information
You can use SP memory for read/write caching. You can use different cache settings for different times of day. For example, for user I/O during the day, use more write cache; for sequential batch jobs at night, use more read cache. Generally, write caching improves performance far more than read caching. Read caching is nonetheless crucial for good sequential read performance, as seen in backups and table scans. The ability to specify caching on a LUN basis provides additional flexibility, since you can use caching for only the units that will benefit from it. Read and write caching is recommended for any type of RAID group or pool, particularly RAID 6 or RAID 5. You can enable caching for specific LUNs in a RAID Group and for all the LUNs in a pool, which allows you to tailor your cache resources according to priority. The maximum cache size per SP is 598 MB, and the maximum write cache size is 598 MB.
Read cache size
If you want a read cache, enter the read cache size you want. Write cache size
Enter the write cache size that you want. Generally, we recommend that the write cache should be the maximum allowed size, which is 600 MB per SP.
Cache page size
Cache page size applies to both read and write caches. It can be 2, 4, 8, or 16 KB. As a general guideline, we suggest 8 KB. The ideal cache page size depends on the server’s operating system and application.
Storage-system management
This section describes the storage-system management ports and the management applications you can use, and provides the appropriate planning worksheets.
Major topics are:
Storage-system management ports, page 29
Storage-system management ports worksheet, page 30 CLARalert® software, page 40
CLARalert worksheet, page 40
Navisphere® management software, page 41 Navisphere Analyzer, page 46
Optional Navisphere Quality of Service Manager, page 46 Navisphere management worksheet, page 47
Storage-system management ports
The storage system has two management ports, one per SP, through which you manage the storage system. For storage-system initialization, these ports must be connected to a host on the network from which the storage system will be initialized. This host must be on the same subnet as these ports. Initialization assigns network and security characteristics to each SP. After initialization, these ports are used for storage-system management, which can be done from any host with a supported browser on the same network as these ports. A storage system running FLARE 04.29 or later supports one virtual port with VLAN tagging for each management port. If a management port is connected to a switch, you can:
Create a trunk port on the switch per IEEE 802.1q standards. Configure the trunk port to pass along network traffic with the
VLAN tag for the virtual management port and for any other virtual ports that you want.
Configure the truck port to drop all other traffic.
Storage-system management ports worksheet
Record network information for the storage-system management ports in Table 12. Your network administrator should provide most of this information, except for the login information.
Table 12 Storage-system management port information Storage-system information
Storage-system serial number:
Physical network information IPv4 SP port information (default Internet protocol)
SP A IP address: Subnet mask: Gateway:
SP B IP address: Subnet mask: Gateway:
IPv6 SP port information (manual configuration only)
Global prefix: Gateway:
Virtual port network information
Storage processor Virtual port VLAN ID IP address
SP A SP B
Login information Username: Password:
Role: Monitor Manager Administrator Administrator Security Local replication Replication Replication and recovery
Storage-system information
Fill out the storage-system information section of the worksheet using the information that follows.
Storage-system serial number
The hardware serial number (TLA S/N) is on a tag that is hanging from the back middle of the storage processor enclosure (Figure 12).
CL4037 01 2 3 10 /100/1 000 01 2 3 10/100/1000 10/100/1000 10/100/100010/100 /100 0 0 1 01 2 3 01 2 3 10/100/100010 /100/100 0 0 1
Figure 12 Location of the storage-system serial number on the SPE
Physical network information
Fill out the physical network information section of the worksheet using the information that follows.
The management ports support both IPv4 and IPv6 Internet Protocols concurrently. IPv4 is the default and you must provide IPv4 addresses. If your network supports IPv6, you can choose to use IPv6 with automatic or manual configuration. For automatic configuration, you do not need to provide any information. For manual configuration, you must provide the global prefix and the gateway.
IPv4 SP port information
Fill out the IPv4 SP port information section of the worksheet using the information that follows.
IP address
Enter the static network IPv4 address (for example, 128.222.78.10) for connecting to the management port of a storage processor (SP A or
SP B). Do not use IP addresses 128.221.1.248 through 128.221.1.255, 192.168.1.1, or 192.168.1.2.
Subnet mask
Enter the subnet mask for the LAN to which the storage system is connected for management, for example, 255.255.255.0.
Gateway
Enter the gateway address if the LAN to which the storage-system management port is connected has a gateway.
IPv6 SP port information
Fill out the IPv6 SP port information section of the worksheet using the information that follows.
Global prefix
Enter the IPv6 global prefix, which is 2000::/3. Gateway
Enter the gateway address if the LAN to which the storage-system management port is connected has a gateway.
Virtual port information
The virtual port for the management port supports 802.1q VLAN tagging. FLARE 04.29 or later is required for virtual ports and VLAN tagging. Navisphere Manager always represents the management ports as virtual ports on storage systems running FLARE 04.29 or later. Fill out the virtual port information section of the worksheet using the information that follows.
Virtual port
Enter the name for the virtual port. VLAN ID
Enter a number between 1 and 4095, and the number must be unique. IP address
Enter the network IP (Internet Protocol) address (for example, 128.222.78.10) for connecting to the virtual port. Do not use IP addresses128.221.1.248 through 128.221.1.255, 192.168.1.1, or 192.168.1.2.
Login information
Fill out the Login information section of the worksheet using the information that follows.
Username
Enter a username for the management interface. It must start with a letter and may contain 1 to 32 letters and numbers. The name may not contain punctuation, spaces, or special characters. You can use uppercase and lowercase characters. Usernames are case-sensitive. For example, ABrown is a different username from abrown. Your network administrator may provide the username. If not, then you need to create one.
Password
Enter a password for connecting to the management interface. It may contain 1 to 32 characters, consisting of uppercase and lowercase letters and numbers. As with the username, passwords are case-sensitive. For example, Azure23 is a different password than azure23. The password is valid only for the username you specified. Your network administrator may provide the password. If not, then you need to create one.
User roles
Four basic user roles are available - monitor, manager, administrator, and security administrator. All users, except a security administrator, can monitor the status of a storage system. Users with the manager role can also configure a storage system. Administrators can maintain user accounts, as well as configure a storage system. Security administrators can only manage security and domain settings. Select the role you want for the user. For more information on roles, refer to Authentication, page 42.
EMC Secure Remote Support IP Client for CLARiiON
ESRS IP Client for CLARiiON software does the following: Monitors storage systems within a domain for error events.
Automatically and securely sends alerts (call homes) to your service provider about events that require service provider notification. Allows your service provider to securely connect remotely through
the monitor station into your monitored storage system to help troubleshoot storage-system issues.
Sends a notification e-mail to you (the customer) when an alert is sent to your service provider.
We recommend that you use EMC Secure Remote Support (ESRS) IP Client for CLARiiON instead of the CLAR alert software if your environment meets the requirements for the ESRS IP Client for CLARiiON software.
Figure 13 shows the communications infrastructure for Call Home feature of the ESRS IP Client for CLARiiON, and Figure 14 shows the communication infrastructure for the remote access feature of the ESRS IP Client for CLARiiON.
LAN
Centralized monitoring station running ESRS IP Client for CLARiiON
CX4-240 CX4-480 CX4-120 Event Call Home (SSL) (SSL) Service provider (SSL) (SSL) (SSL) (SSL) Event Event
Figure 13 ESRS IP Client for CLARiiON communication information infrastructure for Call Home
LAN
Centralized monitoring station running ESRS IP Client for CLARiiON
CX4-240 CX4-480 CX4-120 (SSL) (SSL) Service provider (SSL) Remote access (SSL) (SSL) (SSL)
Figure 14 ESRS IP Client for CLARiiON communications information infrastructure for remote access
The ESRS IP Client for CLARiiON:
Requires a monitor station, which is a host or virtual machine running a supported Windows operating system and the ESRS IP Client for CLARiiON software. The monitor station must:
z Must have a 1.8 GHz or higher computer with at least 2 GB of available storage for the ESRS IP Client
z Not be a server (host connected to storage-system data ports). z Must be connected to the same network as your storage-system
management ports and connected to the Internet through a proxy server.
Must be connected over the network to a portal system, which is a storage system running the required FLARE version.
ESRS IP Client for CLARiiON worksheet
If you want to use ESRS IP Client for CLARiiON to monitor your storage system, record the information in Table 13.
Table 13 ESRS IP Client for CLARiiON worksheet Monitor station network information
Host identifier: IP address:
Portal system network information
Portal identifier: IP address:
Username: Password:
Proxy server network information
Protocol: HTTPS SOCKS IP address or network name:
Username: Password:
Customer notification information
e-mail address: SMTP server name or IP address:
Powerlink credentials
Usename: Password:
Monitored system information
System name or IP address: Port:
Username: Password:
Customer contact information
Name: Phone:
e-mail address: Site:
Monitor station network information
Fill out the monitor station network information section of the worksheet using the information that follows
Host identifier
Enter the optional name or description that identifies the Windows host that will be the monitor station.
IP address
Enter the network IP (Internet Protocol) address (for example,
128.222.78.10) for connecting to the monitor station. This address must be a static or DHCP reserved IP address. The portal system uses this IP address to manage the monitor station. Since the monitor station can have multiple NICs, you must specify an IP address. This IP address cannot be 128.221.1.250, 128.221.1.251,192.168.1.1, or 192.168.1.2 because these addresses are reserved.
Portal system network information
Fill out the portal system network information section of the worksheet using the information that follows.
Portal identifier
Enter the optional identifier (such as a hostname) for the storage system that is or will be the portal system.
IP address
Enter the network IP address for connecting to the portal system. This IP address is the IP address that you assign to one of the storage system’s SPs when you initialize it.
Username
Enter the username for logging into the portal. Password
Enter the password for the username for logging into the portal. Proxy server network information
Depending on your network configuration, you may have to connect to the Internet (or services outside the local network) through a proxy server. In this situation, the server running the ESRS IP Client for CLARiiON uses the proxy server settings to access the proxy server so it can access Powerlink and send alerts to your service provider. Fill out the proxy server network information section of the worksheet using the information that follows.
Protocol
Enter the protocol (HTTPS or SOCKS) for connecting to the proxy server.
IP address or network name
Enter the network IP address or network name for connecting to the proxy server. The IP address cannot be 128.221.1.250, 128.221.1.251,192.168.1.1, or 192.168.1.2 because these addresses are reserved.
Username
Enter the username for accessing the proxy server if it requires authentication. The SOCKS protocol requires authentication, and the HTTPS protocol does not.
Password
Enter the password for the username. Customer notification information
Customer notification information is information about the person or group to be notified when ESRS sends alerts to the service provider. Fill out the customer notification information section of the worksheet using the information that follows.
e-mail address
Enter the e-mail address of the person or group to notify when ESRS sends an alert to your service provider.
SMTP server name or IP address
Enter the address of the server in your corporate network that sends e-mail over the Internet. You can choose to have ESRS use e-mail as your backup communication for the Call Home feature and to use e-mail to notify you when ESRS sends alerts (remote notification events) to your service provider. To use e-mail in these cases, you must provider your SMPT server name or IP address, in addition to your e-mail address.
Powerlink credentials
The ESRS IP Client for CLARiiON software is available from Powerlink. To use the ESRS IP Client for CLARiiON Installation wizard to install this software on the monitor station, you must provide your Powerlink credentials. Fill out the Powerlink credentials section of the worksheet using the information that follows.
Username
Enter the Powerlink username for the person who will install the ESRS IP Client for CLARiiON on the monitor station.
Password
Enter the Powerlink password for the user. Monitored system information
Fill out the monitored system information section of the worksheet using the information that follows.
System name or IP address
Enter the name or network IP address for connecting to your storage system. This IP address is the IP address that you assign to one of the storage system’s SPs when you initialize it.
Port
Enter the port on the SP for ESRS to access. Username
Enter the name of user that will monitor your storage system and will have monitoring access to your storage system.
Password
Enter the user’s password. Customer contact information
Customer contact information is the information that the service provider needs to contact the person at your storage-system site if the service provider cannot fix the problem with your storage system online. Fill out the customer contact information section of the worksheet using the information that follows.
Name
Enter the name of the person at your storage-system site to contact. e-mail
Enter the e-mail address of the contact person. Phone
Site
Enter the identifier of the site with your storage system.
CLARalert
® software
CLARalert software monitors your storage system’s operation for error events and automatically notifies your service provider of any error events. It requires:
A monitor station, which is a host running a supported Windows operating system. This monitor station cannot be a server (host connected to storage-system data ports) and must be on the same network as your storage-system management ports.
A portal system, which is a storage system running the required FLARE version.
We recommend that you use EMC Secure Remote Support (ESRS) IP Client for CLARiiON instead of the CLAR alert software if your environment meets the requirements for the ESRS IP Client for CLARiiON software.
CLARalert worksheet
Record the network information for the CLARalert monitor station and the portal system in Table 14.
Table 14 CLARalert worksheet
Monitor station network information Host identifier: IP address:
Portal system network information
Portal identifier: IP address: Username: Password:
Monitor station network information
Fill out the monitor station network information section of the worksheet using the information that follows
Host identifier
Enter the optional name or description that identifies the Windows host that will be the monitor station.
IP address
Enter the network IP (Internet Protocol) address (for example,
128.222.78.10) for connecting to the monitor station. This address must be a static or DHCP reserved IP address. The portal system uses this IP address to manage the monitor station. Since the monitor station can have multiple NICs, you must specify an IP address. This IP address cannot be 128.221.1.250, 128.221.1.251,192.168.1.1, or 192.168.1.2 because these addresses are reserved.
Portal system network information
Fill out the portal system network information section of the worksheet using the information that follows.
Portal identifier
Enter the optional identifier (such as a hostname) for the storage system that is or will be the portal system.
IP address
Enter the network IP address for connecting to the portal system. This IP address is the IP address that you assign to one of the storage system’s SPs when you initialize it.
Username
Enter the username for logging into the portal. Password
Enter the password for the username for logging into the portal.
Navisphere
® management software
The Navisphere management software consists of the following software products:
Navisphere Manager
Unisphere Server Utility for supported operating systems Unisphere Host Agent for supported operating systems
Navisphere host-based command line interface (CLI) for supported operating systems
Navisphere Manager
Navisphere Manager (called manager) lets you manage multiple storage systems on multiple servers simultaneously. It includes an
event monitor that checks storage systems for fault conditions and can notify you and/or customer service if any fault condition occurs. Some of the tasks that you can perform with Navisphere Manager are: Manage server connections to the storage system
Create RAID groups and thin pools and LUNs on the RAID groups and thin pools
Create storage groups Manipulate caches
Examine storage-system status and events recorded in the storage-system event logs
Transfer control from one SP to the other
Manager features a user interface (UI) with extensive online help. All CX4 storage systems running FLARE 04.29.000.5.xxx or earlier ship with Navisphere Manager installed and enabled.
Navisphere provides the following security functions and benefits: Authentication
Authorization Privacy Audit Authentication
Manager uses password-based authentication that is implemented by the storage management server on each storage system in the domain. You assign a username and password when you create either global or local user accounts. Global user accounts apply to all storage systems in a domain and local user accounts apply to a specific storage system. A global user account lets you manage user accounts from a single location. When you create or change a global user account or add a new storage system to a domain, Manager automatically distributes the global account information to all storage systems in the domain. Authorization
Manager bases authorization on the role associated with the authenticated user. Four roles are available — monitor, manager, administrator, security administrator. All users, except a security administrator, can monitor the status of a storage system. Users with
can maintain user accounts, as well as configure a storage system. Security administrators can only manage security and domain settings. Privacy
Manager encrypts all data that passes between the browser and storage management server, as well as the data that passes between storage-system management servers. This encryption protects the transferred data whether it is on local networks behind corporate firewalls or on the Internet.
Audit
Manager maintains an SP event log that contains a time-stamped record for each event. This record includes information such as an event code and event description. Manager also adds time-stamped audit records to the SP event log each time a user logs in or enters a request. These records include information about the request and the requestor. Unisphere Server Utility, Unisphere Host Agent, and Navisphere CLI
The Unisphere Server Utility and the Unisphere Host Agent are provided for different operating systems. The Unisphere Server Utility replaces the Navisphere Server Utility and the Unisphere Host Agent replaces the Navisphere Host Agent.
You should install the server utility on each server connected to the storage system. Depending on your application needs, you can also install the host agent on each server connected to a storage system to: Monitor storage-system events and notify personnel by e-mail,
page, or modem when any designated event occurs.
Retrieve LUN world wide name (WWN) and capacity information from Symmetrix® storage systems.
Register the server’s HBAs with the storage system. Alternatively, you can use the Unisphere Server Utility to register the server’s HBAs with the storage system. Table 15 describes the host
Table 15 Host Registration differences between the host agent and the server utility
Function Unisphere Host Agent Unisphere Server Utility Pushes LUN mapping
and OS information to the storage system.
Yes – LUN mapping information is displayed in the Manager UI next to the LUN icon or with the CLI using the lunmapinfo command.
CX4 series, CX3 series, and CX series storage systems No – LUN mapping information is not sent to the storage system. Only the server’s name, ID, and IP address are sent to the storage system. Note: The textManually Registeredappears next to the hostname icon in the Manager UI indicating that the host agent was not used to register this server.
Runs automatically to send information to the storage system.
Yes – No user interaction is required.
CX4 series, CX3 series, and CX series storage systems No – You must manually update the information by starting the utility or you can create a script to run the utility. Since you run the server utility on demand, you have more control as to how often or when the utility is executed.
Requires network connectivity to the storage system.
Yes – Network connectivity allows LUN mapping information to be available to the storage system.
CX4 series, CX3 series, and CX series storage systems No – LUN mapping information is not sent to the storage system. Note that if you are using the server utility to upload a high-availability report to the storage system, you must have network connectivity. The Navisphere CLI provides commands that implement Navisphere Manager UI functions for in addition to commands that implement the functions of the UIs for the optional data replication and data mobility software. A major benefit offered by the CLI is the ability to write command scripts to automate management operations.
Using Navisphere manager software
With Navisphere manager you can assign storage systems on an intranet or Internet to a storage domain. For any installation, you can create one or more domains, provided that each storage system is in only one domain. Each storage domain must have at least one member with Manager installed.
Each storage system in the domain is accessible from any other in the domain. Using an Internet browser, you point at a storage system that has Manager installed. The security software then prompts you to log in. After logging in, depending on the privileges of your account, you can monitor, manage, and/or define user accounts for any storage system in the domain. You cannot view storage systems outside the domain from within the domain.
You can run the Internet browser on any supported station (often a PC or laptop) with a network controller. At least one storage system – ideally at least two for higher availability – in a domain must have or Navisphere Manager installed, preferably Unisphere.
Figure 15 shows an Internet configuration that connects 9 storage systems. It shows 2 domains, a U.S. Division domain with 5 storage systems (4 systems on SANs) and a European Division with 4 storage systems. The 13 servers that use the storage system may be connected to the same or a different network, but the intranet shown is the one used to manage the storage systems.
Server Server Server Server EMC2276 Storage System Storage System Storage System Storage System Storage System Storage System Storage System Storage System Switch Fabric Switch Fabric Switch Fabric Switch Fabric
Domain 1 - U.S. Division
Domain 2 - European Division Internet
Browser
Server Server Server Server Server Server
Server
Storage System
Server Server Internet
Figure 15 Storage domains on the Internet
Navisphere Analyzer
Navisphere Analyzer lets you measure, compare, and chart the performance of SPs, LUNs, and disks to help you anticipate and find bottlenecks in your storage system.
Optional Navisphere Quality of Service Manager
The optional Navisphere Quality of Service Manager ( or Navisphere QoS Manager) lets you allocate storage-system performance resources on an application-by-application basis. You can use Navisphere QoS Manager to solve performance conflicts in consolidated environments where multiple applications share the same storage system. Within
storage-system capacity, Navisphere QoS Manager lets you meet specific performance targets for applications, and create performance thresholds to prevent applications from monopolizing storage-system performance.
Navisphere management worksheet
The worksheet in Table 16 will help you plan your Navisphere storage management configuration.
Table 16 Storage management worksheet for Navisphere software
Storage-system name: Domain name:
Navisphere Analyzer Navisphere QoS Manager
Server name: Operating system:
Server name: Operating system:
Server name: Operating system:
Server name: Operating system:
Server name: Operating system:
Server name: Operating system:
Server name: Operating system:
