clariion cx series

8/11/2019 CLARiiON CX Series

1/39

EMC Global Education 2004 EMC Corporation. All rights reserved.

CLARiiON CX-SeriesAdvanced Hardware and Software Details


2/39


2

Topics

ATA Drive Enclosure (DAE2-ATA)

Array Software ConfigurationInitialization of ArraysNon Disruptive UpgradeNavisphere User Security Domains Portals


3/39


DAE2-ATAATA Drive Enclosure for CX Arrays

This module introduces a new DAE2 to the CX family called DAE2-ATA. It consistsof a standard DAE2 enclosure and power supply/fan assemblies. New LCC cardsreplace the old LCC cards and all disk drives in the enclosure are commodity ATAdisks. Drives in the enclosure must be the same type. ATA enclosures can bemixed in an array with existing FC enclosures. Upon completion of this module thestudent will be able to:


4/39


4

ATA-DAE Enclosure - Overview

High-Capacity, LowerPerformance, Lower Cost DAEUtilizing Serial-ATA TechnologyLeverages Components fromexisting DAE2 Chassis

Chassis Power Supplies / Blowers

Product Components Maxtor DiamondMax 16 250 GB

(Tomcat) ATA Disk Drive Disk Drive Paddle Card LCC 2Gb Fibre Channel to Serial ATA

Bridge Adapter

The DAE2-ATA is a Lower Performance DAE that uses Serial-ATA Technology.The chassis is the same as its counterpart the Fibre Channel DAE2. TheComponents that populate this new offering are: a Maxtor DiamondMax 16 250 GB(Tomcat) ATA Drive, a disk drive paddle card mounted on the disk carrier and anew LCC 2Gb Fibre Channel to Serial ATA Bridge Adapter card.


5/39


5

Disk Drive Characteristics

Parallel ATA Interface (512-byte Blocks Only)

5400 RPM MaxtorDiamondMax 16 250GB ATADisk DriveSpindle Speed / 12 ms SeekTimeZone Density RecordingUltra ATA/133 InterfaceController

Read-Ahead Mode

Automatic Write Defect Reallocation

The ATA disk drives used provide data in 512 byte blocks on a parallel interface.Using 5400 RPMs for a spindle speed yields an average seek time of 12ms.

The drives use zone density recording which provide fewer sectors on inside tracks

and more sectors on succeeding tracks as the heads move towards the outer trackson the disk.

An Ultra ATA/133 interface controller can provide read-ahead mode based on aprevious read history algorithm. Also, Automatic Write Defect Reallocation (badblock detection) is provided so bad sectors can be remapped to another place onthe disk.


6/39


6

DAE2-ATA Rear View

ATA Controller

(LCC B)

ATA Controller

(LCC B)

Power/Cooling APower/Cooling B

ATA Controller(LCC A)

ATA Controller(LCC A)

Enclosure Address Switch

Enclosure

ATA Ctlr ATA Ctlr

The DAE2-ATA includes the following components:

A sheet-metal enclosure with a mid-plane and front bezel, two Bridge ControlCards (LCC) cards. Both LCC cards have the same form factor as original LCC

cards that are used in the Fibre Channel version. The DAE2 can be populated withas many as 15 disk modules, although the DAE2-ATA can be ordered with no disksand two power supplies with system cooling modules.


7/39


7

Disk Drive Paddle Card

Provides Dual-Port Capability to ATA Disks

Performs Serial-to-Parallel Signal Conversion

A Micro Processor Chip Controls : Disk Environmental Functions LED Disk Drive Power-Up Sequence, etc.)

The paddle card sits on the drive carrier between the ATA drive and theDAE2 mid-plane. The paddle card controls power to the ATA drive. Thepaddle card converts the standard ATA interface into Serial and dual portedfor use in the DAE2 for high availability. The paddle card is not a FRU, it is apart of the disk module.

The paddle card on the disk drive carrier performs several functions. Itprovides Dual-port capability so drives can be accessed by either of the twoFibre loops this is the same capability as in the Fibre channel enclosureusing Fibre channel drives. Since the interface to the disk from the paddlecard is parallel, conversion to serial is required when providing information tothe DAE2 enclosure. Also provided on the paddle card is a microprocessor.It causes the disks to spin up in sequence starting with disk 0, then 1, etc.The microprocessor also monitors environmental conditions and signals theserver when a problem occurs, Also the micro is responsible for illuminatingthe LED on the front of the drive.


8/39


8

Bridge Controller Card (LCC)

Fibre-Channel (SCSI) to ATACommand & ErrorTranslationCommand Queuing of FCRequestsData Buffering Provides 520-Byte Sector Emulation ontop of 512-byte PhysicalSectorsFull FRUMON Command SetEmulation

LED Control for Enclosureand Disk Drives

Environmental Monitoring

One purpose of the Bridge Controller Card (LCC) is to convert all signaling (control anddata) from the ATA interface from the disk drive into the Fibre Channel interface for theDAE2 that can be used by the other components in the array (other DPE2s and StorageProcessors).

A LCC supports and controls one Fibre Channel loop and monitors the DAE2. The LCCs ina DAE2 are connected to other Fibre Channel devices (hosts and DAE2s) using twin-axialcopper cables. The cabling is not explicitly configured as a loop, but instead, as a set of full-duplex, point-to-point connections with the last disk enclosure in the chain closing the loopon its LCC.

The LCC passes the input signal to the disk drives in the enclosure then sends the outputsignal, via cables, to the next DAE2 in the loop. ATA link control cards (LCCs) provide thesame Fibre channel input and output, but convert those signals to and from the ATA 6protocol used by their disk drives. Each LCC independently monitors the environmentalstatus of the entire enclosure, using a microcomputer-controlled FRU (field-replaceable unit)monitor. The FRU monitor (FRUMON) communicates status to the server.

Each LCC independently monitors the environmental status of the entire enclosure, using amicrocomputer FRU monitor. The FRU monitor communicates status to the server. Theprotocols let the server poll DAE2 status and send commands that control the LCC portbypass circuits and the disk-module status lights. The protocols do not let the LCCscommunicate with or control each other. Each LCC has four status lights.


9/39


9

ATA-DAE Mixing FC & ATA Enclosures in an Array

ATA-DAE

DAE2DAE2DAE2

ATA-DAE

DAE2DAE2

ATA-DAE

ATA-DAE

DAE2

DAE2ATA-DAE

DAE2ATA-DAEATA-DAE

DAE2DAE2

ATA-DAE

ATA-DAE

DAE2

DAE2ATA-DAE

DAE2DAE2

ATA-DAE

ATA-DAE

DAE2

DAE2ATA-DAE

DAE2DAE2

ATA-DAE

ATA-DAE

DAE2

15 sATA Drives: ~4TB*15 Fibre Drives: ~1TB**depends on drive size

First enclosure must be FC

As shown in the drawing, ATA and Fibre Channel enclosures can be mixed in thesame array. The only rule that cannot be broken is the first enclosure MUST beFibre Channel and contain a minimum of five disks. Notice that the amount of totalstorage in an enclosure varies with the drive size. The example chosen was using73Gb FC drives and 250GB ATA disks.


10/39


10

GUI Interface changes

In order to manage the DAE2-ATA enclosure Navisphere 6.4 is required. For allitems associated with an ATA enclosure notice that Navisphere 6.4 identifies thoseitems with the letters ATA. Under Physical, the second enclosure is identified asBus 0 Enclosure 1 (DAE2-ATA). Notice also that the Icon for that enclosure alsocontains the letter E which stands for Empty. This means that at least one diskslot is empty. Each empty slot must be occupied with a blank carrier for coolingpurposes.

Under the RAID Groups icon, RAID group 2 is identified as a RAID 1 (mirrored pair)and is using ATA disks. When RAID group 2 is expanded you can see that disks 0and 1 are being used to form the RAID group and they are ATA disks.

A further breakdown, shows that LUN0 is a part of RAID group 0 and again isshown using ATA disks.


11/39


Array Based SoftwarePrivate Space Configuration


12/39


12

DPE2 & DAE2-OS Structure

0 1 2 3 4 5 6 7 8 9 10 11 12 13 140 1 2 3 4 5 6 7 8 9 10 11 12 13 14

6GB 6GB 6GB 6GB 6GB

32MB 32MB 32MB 32MB 32MB 32MB 32MB 32MB 32MB 32MB

Private Space is white, user space is blueNot to scale

The CX-Series array sets aside roughly 32MB per disk aside for Private Space, foruse by the array. Except for the first 5 Disks on the Array, known as the VAULTDRIVES. For a CX600, these are located on the DAE2-OS, drives 0-4. On theCX400 & CX200, these are located on the DPE2, drives 0-4.

Roughly 6 GB per disk is set aside on the Vault Drives for the functionality of thearray. The next slide will provide the detail on this space


13/39


13

Vault Drive Private Space Structure

Data Directory Boot Service (2MB/disk)

Flare Db (28.3MB/disk)Data Directory (2MB/disk)

SPANT Boot

Primary(2826.2MB)

SPBNT Boot

Primary(2826.2MB)

SPANT Boot

Secondary(2826.2MB)

SPBUtility Pr (200MB) SPAUtility Pr (200MB) SPBUtility Pr (200MB)

Reserve Area (100MB/disk)

NAS Core DumpArea (1GB)

0 1 2 3 4

6GB

Not in use

Not in use

Not in use

SPBNT Boot

Secondary(2826.2MB)

Vault Area (2176MB/disk)

PSM (1024MB/disk)

SPAUtility Pr (200MB)

FRU Signature (28.3MB/disk)

External Db (35MB/disk)

Image Repository(1GB)

Data Directory Boot Service 2 MB All disks in array Fixed space for boot serviceData Directory 2 MB All disks in array - Each disk contains a data directory that maintains a map ofthe database entries for that diskFlare Database 28.3 MB All disks in array The traditional database is triple-mirrored on drives 0,1 & 2. This area is used in other drives for FRU signature, clean/dirty flags, HW/FRU verify, etc. and

a large reserved for future use areaExternal Database 35 MB drives 0, 1, & 2 Contains persistent information outside the purview ofFlare such as: BIOS code image, PROM code image, Chameleon Kernel software, Chameleonvolume manager, Chameleon filesystem database.NT Boot Partitions 2826.2 MB drives 0, 1, 2, & 3 - Each SP will have a mirrored NT boot partition.SPA will use drives 0 & 2, SPB will use drives 1 & 3.Reserved Space 300 MB Set aside for future NT growth.PSM 1024 MB drives 0, 1 & 2 Triple mirrored private LUN for storage of persistent SP data.Vault 2176 MB drives 0 through 4 RAID 4+1 area used for vaulting cache data in power failemergencyCore Dump Partition 1 GB disk 4 reserved for Chameleon II NAS software core dumpsTotal private space drives 0 4 = 6393.5 MB

Arrays shipped with at least release 11 and Utility Partition installed include the following areas:SPA and SPB Utility Boot Partitions The SPA utility partitions are on SPB s boot drives and the SPButility partitions are on SPA s boot drives. This will allow SPA to be booted to the utility partition ondrives 1 and 3 in the event of failure of both drives 0 and 2. SPB has the same arrangement withdrives 0 and 2 in the event both drives 1 and 3 fail.Image Repository A separate 1gigabyte partition has been created on previously unused space ondrive 4 for the storage of raw image metafiles.


14/39


14

Private Space Details

SP Boot Images: Contain NT 4.0 SP 5 Operating System

Base code, Navi Code and Layered Drivers (eg. SnapView) All Software loads from Boot images

Persistent Storage Manager (PSM) Contains most settings (eg. IP Addresses, Navi Settings, SP settings,

Layered Driver Settings)

Flare Database Contains record of all RAID Groups, LUNs, cache settings

Optional SP Utility Partitions Contains some NT and Base code, and a menu driven OS. For recovery of failed boot images.

The Vault Location of cache dumps during failures.


15/39


15

Initializing the Array

Purpose : To prepare a brand-new array for managementand to upgrade to the customers specification.Configure Management Station PPP Dial-up Networking Session Navisphere

Off-Array Management UI Java Runtime Environment Navisphere CLI

Initialize the Array Set the IP Addresses of the SPs Launch Navisphere / Set security Commit Base Software Upgrade the Array Software

All instructions can be found in the Procedure Generator.


16/39


Initializing an Array


17/39


17

Module Objectives

Upon completion of this module, the student will be

able to: Configure a newly shipped CLARiiON for connectivity andoperation

Cable a CLARiiON environment for management Connect to a CLARiiON using a serial cable


18/39


18

Configure Management Station / Laptop

Install the following from the Service Tools CD:

JRE version x.xx_xx (version compatible with UI) Navisphere Windows Management UI (off-array) Navisphere CLI

Configure PPP Dial-up Networking: Run the Windows 2000/XP New Network Connection

Wizard Choose the settings relating to Direction connection

between 2 PCs with Serial Cable Be a Guest when asked. Set the Speed to 115,200 baud.


19/39


19

Using PPP to Connect to a CLARiiON SP

Connect a NULL Modem

cable between your serialport and SPA on the array.Launch the PPP connectionyou created.Logon with:User name: clariionPassword: clariion!Click on Connect


20/39


20

Alternate Management Topology

ManagementStation

Connection from serial port on management station to the serial porton a Storage Processor

Using a NULL MODEM CABLE

Using a PPP Connection at 115,200 baud (Dial-Up Networking)

DHCPIP: 192.168.1.10

IP: 192.168.1.1

Reasons for using CLARiiONs PPP option

On a new array, there is no Ethernet / TCP-IP connectivity, so this is the methodfor configuring the array (initialization)

There are problems with the tpc/ip network or settings.Customer security issues prohibit maintainers to operate on the customers tcp/ipnetwork.

Means of establishing this connection

Using a Null Modem serial cable, connect from a serial port on the workstation tothe serial port (marked |0|0|) on the Storage Processor

Configure a Dial-Up Networking Session on the workstation (see ProcedureGenerator for details)

Connect to the array using Dial-Up Networking session, using user: clariion, pw:clariion! (include !)

The array will auto-assign an IP to the workstation and present the StorageProcessor as 192.168.1.1.

This will allow use of the Management UI, though it will be limited to the singlestorage processor, and will be far slower than the ethernet topology

This allows for access to navicli commands to that storage processor

Finally, this method can be used as back door method for lost domain passwords

etc.


21/39


21

Configure SP Network Parameters

Enter in the following URL into your browser window:http: 192 168 1 1 setup

IP Address of SPA

Hostname (unique, 15 chars or less)

Subnet Mask

Gateway (cannot leave blank)

Peer IP Address (IP Address of SPB)

TCP/IP Ports (other choice = 2162/2163)

Click Apply Settings which will reboot the SP


22/39


22

Finish Network Parameters

While SPA reboots, connect NULL Modem to SPB

Run PPP Session to SPBConfigure Network settings for SPB and rebootWhen SPB reboots, connect NULL Modem back toSPA.Log into SPA, and Restart Management server fromhttp: 192 168 1 1 setup page

After setting the parameters for both Storage Processors, you need to restart themanagement server on SPA in order for SPA to be able to reach SPB via theEthernet Peer connection.


23/39


23

Launch the Off-Array UI

1. Browse to the folder where the GUI is installed and double-click on the start.htmlfile.

2. When the browser launched it will prompt you for the Connection Type. In this

case, select LAN Connection, and type in the IP Address of one of the SPs.Click OK.

3. When it first launches, it will prompt you to initialize Security. If you say no, thearray will not be secure, but can be added to another Domaina if desired.

4. If you say Yes, the next screen will prompt you to create a Global Admin User.


24/39


24

Other Array Settings

On a new system, you will need to COMMIT the BaseSoftware before proceeding with any other settings.Set the Date and Time on the SPs.Give the array a Unique nameChange the speed of one or more of the SP FE Ports.Enable Cache and Statistics Logging

All of these steps will be practiced in the CLARiiON HostIntegration Workshop

Until the Base or array software is committed, the array will not be fullyfunctional. This step also needs to be completed after each Base Softwareupgrade

It is important to set the date and time on the array so that the event logs oneach Storage Processor are accurate. You only need to configure the timeon a single Storage Processor and it will propagate to the other.

The name given to an array by default in the Navisphere interface is theSerial Number. While this is ok in some circumstances, it may provecumbersome in an environment with multiple arrays. Giving a logical nameto the array may ease identification.

The default speed of the Front-End ports is 2Gbit. If these ports are beingcabled to a legacy environment, such as a host with a 1Gbit HBA or 1Gbit

switch, you will need to change the speed on all ports involved. It has to bedone to each individual port and is a live, real-time software operation inNavisphere.

Cache is not enabled by default. You will need to enable it to thecustomers specification before the end of the configuration.

The workshop will cover all the necessary software steps to complete theinitialization.


25/39


Upgrading Array SoftwareThe Non-Disruptive Upgrade (NDU)


26/39


26

Software Options CX400, CX600

CX400 / CX600 ship with the following software:

Base Code : without Access Logix, Needs to be Committed, mayneed to be upgraded Navisphere Array Agent : may need to be upgraded Navisphere Management Server : may need to be upgraded

May need to Upgrade array to: Latest Versions of above Access Logix : Alternate Base Code Navisphere UIs : Main, Snap, Mirror, SAN Copy, Analyzer SnapView : SnapView, Clone Provider, CLI Provider MirrorView SAN Copy


27/39


27

Software Options CX200

CX200 ships with the following software:

Base Code : without Access Logix, Needs to be Committed, mayneed to be upgraded Navisphere Array Agent : may need to be upgraded Navisphere Management Server Base : may need to be upgraded Navisphere Management UI Base : may need to be upgraded

May need to Upgrade Array, to: Latest Versions of above Access Logix : Alternate Base Code Navisphere Management Server Full Navisphere UI Full : Main, Analyzer


28/39


28

Non Disruptive Upgrade

Means by which a CX-Series array can have features

added or upgraded without disrupting host access.Requirements to be non-disruptive: Hosts must have an active connection to both Storage

Processors. Hosts must have PowerPath software running and properly

configured. Cache settings should be recorded.

Requirements for successful upgrade: If upgrading software currently on an array, all software must

be upgraded at once. If adding software to an array, all pre-requisites must be met. See Software Compatibility Matrix for details


29/39


29

NDU Functionality

SPBBoot Image

SPABoot Image

PSM

Host RunningPowerPath

SPA

SPB

Management StationRunning Navisphere

1. Through the software Installation Wizard, the admin chooses the .ndu files tobe upgraded.

2. The array then checks for the validity of the files and whether all the pre-reqs and

dependencies will be met.3. The .ndu files are then copied to the PSM area of the array.

4. The PSM then extracts the Driver files from the .ndu files

5. It will then update the Storage Processor it determines is the Secondary StorageProcessor (usually SPB), with the new software.

6. It will then de-active the old software and activate the new software.

7. That Storage processor will reboot. It is up to the host to failover to the other SPby having PowerPath installed and a valid path to the other Storage Processor.

8. When the SP, is done booting, it will repeat steps 5-7 for the other SP.


30/39


30

The Software Installation Wizard

To start the Wizard, right-click on the array and select Software Operations thenSoftware Installation Wizard.


31/39


31

The Software Installation Wizard (contd)

Base 02.05.1.60.4.004; MirrorView 0 Non-Disruptiv

On the Package Selection Screen, first look at the Currently Installed SoftwareScreen to exam whats there and what version.

Select the appropriate .ndu files from your management station, using the Browse

button. Click Next. On the Summary Screen which follows, you will find out if yourupgrade is valid or not. If all appears ok (usually signified by a non-disruptivecomment next to the list of Packages, click OK then finish.


32/39


32

Finishing the Installation

Active (Commit Required)

Commit

Dont forget to re-enable cache !

After you get the Operation Completed Successfully message, proceed to theStorage System Properties window and click on the Software tab. When Basesoftware is upgraded, a Commit is required. Until the commit is performed, not allfeatures are available, but you may have the option to Revert to the pre-existingversion. After the Commit is performed, all features should be available, and youwill not be able to revert to a previous version. The commit is instantaneous andnon-disruptive.

Also, you will need to re-enable and reconfigure cache in order to consider theoperation complete.


33/39


Navisphere Advanced TopicsArchitecture, Domains, Portals, Security


34/39


34

Navisphere 6.x Domain - TCP/IP Topology

SPB

SPA

S P B

S P A

S P B

S P A

Ethernet TCP/IPNetwork

NavisphereManagement

UI

NavisphereMgt Server



CX600Domain Master CX500

Domain Member CX200

Domain Member

ManagementStation

CLARiiON management topology is designed to be out-of-band, using aethernet/tcpip network for management. A management station and all of thearrays you wish to manage need to all be on the same tcp/ip network. This doesnot mean they need to be on the same subnet. The need to be reachable to eachother over tcp ports 80, and 443 (or alternatively, if these are not an option 2162and 2163). Also, both Storage Processors on each managed system need to be onthe network.

The Management Workstation is where we run the Navisphere interface. If youwish to manage all arrays within a single UI, one needs to be selected as theDomain MASTER. In this diagram, the CX600 has been chosen to be theMASTER. But any array running Navi Mgt Server can be a MASTER. The other

arrays are MEMBERS of the domain. When we wish to manage this environmentwith our UI, we enter the IP Address of one of the storage processors on theMASTER (or any system in the Domain), and it will automatically bring up all thearrays in this Domain. This will be discussed and configured in the CLARiiON HostIntegration Workshop.\

Because setting up this network is critical for configuring and managing the arrays,our first order of business with a new array will be to configure its IP addresses.


35/39


35

Navisphere UI Options

BrowserwithJRE

ManagementStation

Windows-based

ManagemtUI(OFF ARRAY)

SPB


Array-basedManagemtUI(ON ARRAY)

TCP/IPNETWORKSPA

There are two topologies supported for the Navisphere Management User Interface(ManagementUI). One is called On Array. You can install, via NDU, the UIsdirectly onto an array. When a supported client browser, running the proper versionof Java, enters the IP address of an array which has ON-ARRAY UI installed, the UIwill be pushed into the browser/java session and then open communication with theManagement Server running on that array.

The other option is to directly install the Windows-based version directly onto theManagement Station. This allows you to directly manage all arrays regardless ofwhether they have the ON-ARRAY installed. Arrays ship by default without the UI,since this is a revenue item.


36/39


36

Navisphere Security

USERS Username Password

ROLES Administrator Manager Monitor

SCOPE Global Local


37/39


37

Navisphere Users Defined

NothingLocal storage-system settings andaccounts

Local Monitor

Nothing All storage-system settings and

accounts

Global Monitor

Local storage systeminformation

Local storage system informationLocal Manager

All storage systeminformation

All storage-system settingsGlobal Manager

Local storage system settingsand local user accounts

Local storage system settings andlocal user accounts

Local administrator

All storage-system settingsand global and local accounts(but cannot delete the lastglobal administrator account)

All storage-system settings andglobal and local accountsNote that local accounts on astorage system can be viewed onlywhen one is logged into thatstorage system.

Global administrator

Can Add, Modify, or DeleteCan ViewAnyone Logged in as


38/39


39/39


39

Summary

ATA-DAE Uses IDE drives and advanced hardware to provide low-cost, high

capacity storage addition to CX Series Array Software

CLARiiON uses intricate Private Area on first 5 drives to boot,operate, and protect the array

Initialization CX Series require some steps in order to prepare them for useUpgrading the array The NDU procedure upgrades the array without interrupting accessNavisphere Architecture

Domains and Portals allow for management of multiple objects. User security provides a variety of options

clariion cx series

Documents