Ns 120 Server Solaris Native

7/31/2019 Ns 120 Server Solaris Native

1/55

CX4 Architecture for NS Series

Connecting a CX4-120 StorageSystem in a Fibre Channel Direct

or Switch Configuration with aSolaris Server with Sun StorEdge

Traffic ManagerDecember 4, 2008

If you want to connect the storage system in a Celerra NS-120 system in aFibre Channel direct or switch configuration with a new or existing Solarisserver with Sun StorEdge Traffic Manager, this document is for you.

The main topics are:

Terminology.................................................................................. 2

Before you start ............................................................................. 4 Determining if your server has a supported configuration.... ... ... ... ... 6 Installing HBAs in the server....... ...... ..... ...... ...... ...... ..... ...... ...... ..... 9 Installing or updating the HBA driver ..... ...... ...... ..... ...... ...... ...... .... 11 Installing the Admsnap utility. ...... ...... ..... ...... ...... ..... ...... ...... ...... ... 13 Configuring Sun StorEdge Traffic Manager on the server ... ... ... ... ... .. 16 Connecting the storage system to the server in a Fibre Channel direct

configuration............................................................................... . 18

Connecting the storage system to the server in a Fibre Channelswitch configuration ...... ..... ...... ...... ...... ..... ...... ...... ..... ...... ...... ..... . 21

Configuring Sun HBAs ...... ..... ...... ...... ..... ...... ...... ...... ...... ...... ...... .. 26 Manually registering the Solaris server with the storage

system ................................................... ...................................... 28 Verifying storage-system health..... ...... ..... ...... ...... ...... ...... ...... ...... .. 33 Setting storage-system failover values for the server initiators with

Navisphere Manager..................................................................... 35

Verifying your high-availability Fibre Channel configuration .. .. .. .. .. . 38 Configuring an existing storage system... ...... ...... ...... ..... ...... ...... ..... 39 Preparing LUNs to receive data.. ...... ...... ..... ...... ...... ..... ...... ...... ..... . 46 Sending Solaris disk information to the storage system ... ... ... ... ... ... .. 49 Verifying your Solaris server failover configuration .. ... ... ... ... ... ... ... .. 50

1


2/55

TerminologyThis document uses the following terms:

host A computer that is or will be connected to a CLARiiON storage

system. This computer is called either a management stationor a

server, depending on how it is or will be connected to the storage

system.

management station A host from which you manage CLARiiON storage systems. Itmust be on the same network as the storage-system management

ports. A management host may also be a server.

server A host that is already or wil l be connected directly or through a

switch to the Fibre Channel ports on a CLARiiON storage system.

A management host may also be a server.

existing server The server that is already configured for and connected to a

CLARiiON storage system.new server A server that is not already connected to or set up for a CLARiiON

storage system.

existing HBA The host bus adapter (HBA) that is already installed in a server.

new HBA The HBA that was notalready installed in the server.

existing storage system A storage system that is already connected to a server and

configured for storage.

field-replaceable unit

(FRU)

A storage-system component that you can add to your storage

system or replace in your storage system at your site. Examples

of FRUs are disks andpower/cooling modules.

SPE A storage processor enclosure that contains two storage

processors (SPs) with I/O modules.

DAE A disk-array enclosure that provides storage for a DAE. Each DAE

supports a maximum of 15 disks.storage processor (SP) A printed-circuit board with processors, memory modules, and

control logic that manages the I/O between the server and the

disk modules.

UltraFlex I/O module A printed-circuit board with either Fibre Channel front-end ports

for Celerra blades or host I/O and/or back-end ports for I/O to

the disks.

2Connecting a CX4-120 Storage System in a Fibre Channel Direct or Switch Configuration with aSolaris Server with Sun StorEdge Traffic Manager


3/55

LUN A grouping of physical disk parti tions into one span of disk storage

space. Each LUN you create is distributed equally across thedisks in the RAID group. A LUN looks like an individual disk to

the servers operating system.

RAID group A set of disks with the same capacity and RAID type on which

you create one or more LUNs.

storage group A group of one or more LUNs that you connect to a server

to provide the server access to the LUNs. Only the servers

connected to a storage group can access the LUNs in the storagegroup.

A CX4 series storage system has two SPs, so it is called a dual-SP system.

Connecting a CX4-120 Storage System in a Fibre Channel Direct or Switch Configurationwith a Solaris Server with Sun StorEdge Traffic Manager

3


4/55

Before you start Read the release notes for your storage system, which are available

in the Technical Documentation and Advisories section on thePowerlink website.

A Navisphere management station with a supported Internetbrowser for running Navisphere Manager and on the same networkas the storage-system management ports. This host can also bea server. For supported host and browsers, refer to the E-LabInteroperability Navigator on the Powerlink website.

A supported Windows host on the same subnet as thestorage-system management ports. You can use this host:

z As a Navisphere management station

z To run the Navisphere Service Taskbar, which runs only on

a Windows host.z As a CLARalert monitor station, which must be a Windows

host, but cannot be a server (that is, it cannot send I/O to thestorage-system data ports).

A Solaris host that is or will be a server with Fibre Channelconnections to the storage system. This server must have asupported server configuration; that is, it must have all required

updates, such as hot fixes or patches, installed. A Navisphere management station with a supported Internet

browser that is on the same network as the storage-systemmanagement ports. This host can also be the server or a Navisphereoff-array management station. For supported Internet browsers,see the Navisphere Manager release notes in the TechnicalDocumentation and Advisories section of the Powerlink website.

One or more supported Sun or QLogic Fibre Channel host busadapters (HBAs), which may already be installed in the server.These adapters must have the latest supported BIOS and driver.For information on supported HBAs, BIOS, and drivers, refer toSupported Configurations in the Technical descriptions section onthe storage-system support website.

Never mix Fibre Channel HBAs from different vendors in the same server.

http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/


5/55

An optical cable for each storage-processor (SP) Fibre Channel

port you will use on the storage system. (Each storage processorhas two ports.) These cables may already be connected for aconfiguration with an existing storage system or server. For cablespecifications, refer to the technical specifications for the storagesystem in the Technical Documentation and Advisories section ofthe Powerlink website.

For a switch configuration One or two Fibre Channel switches,which may already be installed, and an optical cable for connecting

each HBA port to a switch port, if not already connected.

A method for writing data to a LUN on the storage system thatwill test the paths from the server to the storage system. You candownload an I/O simulator (Iometer) from the following website:http://www.iometer.org/.


5
http://powerlink.emc.com/http://www.iometer.org/http://www.iometer.org/http://powerlink.emc.com/


6/55

Determining if your server has a supported configurationBefore you can determine if your server has a supported configuration,you need to know the revision and patch level of the operating systemon the server.If you have this information, go to Verifying a serversconfiguration with E-Lab Interoperability Navigator, page 7 . If you do nothave this information, you can generate a server configuration reportfor your server using the Navisphere Server Utility.

If you do not have the server utility installed, run it from the server support CD.

Starting the Navisphere Server Utility

You can run the server utility from the server or from the server

support CD.

Starting the Navisphere Server Utility on a Solaris server

1. Open a shell window.

2. Navigate to the Navisphere bin directory and run the server utility:

/opt/Navisphere/bin/naviserverutil

Starting the Navisphere Server Utility on a Solaris server from the CD

1. In the servers drive, insert the server support CD, which shippedwith the storage system.

2. Navigate to the Solaris directory:

/cdrom /cdrom0/solaris3. Run the server utility:



7/55

./naviserverutilcli

Generating a high-availability report for a server

1. In the Navisphere Server Utility select option 3 from the serverutilitys Welcome screen to generate a report of the serversenvironment.

This option detects if PowerPath or some other failover software,such as DMP, is running. It does not detect any other nativefailover software, such as Sun StorEdge Traffic Manager After theverification, the utility generates a summary report and saves itto the server.

2. In the summary report, select the Checklist tab to view theinformation about the server that you need to compare against theE-Lab Interoperability Navigator information.

Verifying a servers configuration with E-Lab Interoperability Navigator

1. From your web browser, go to the Powerlink website and log in.

2. If you are not registered with Powerlink, register and create ausername and password.

3. Select E-Lab Interoperability Navigator from the Tools menu on

the right-side of the home page.

4. From the E-Lab Interoperability Navigator page, select LaunchE-Lab Interoperability Navigator and then select the Wizards tab.

5. From the drop-down menu, select the CLARiiON Wizards.

6. In Select a wizard, select Host Attach Wizard.

7. For each step of the wizard, provide the requested informationbased on what is already installed on the server or what you intendto install on the server.

If the configuration you entered is invalid, an additional stepappears in the wizard and a Results, EMC Support Statementspane appears on the right with information to help you provide therequested information in the additional step.


7
http://powerlink.emc.com/http://powerlink.emc.com/


8/55

If the configuration you entered is valid, a Results link appears

on the right.8. When the Results link appears, click it to view a report that contains

information about the configuration you entered.

9. Print and/or save a copy of the report.

10. Close the E-Lab Interoperability Navigator.

11. Compare this report to either the information that you know about

your server software or the checklist report you generated usingthe server utility.

12. If your server software versions and/or patches or hot-fixes are notlisted in the Host Attach Wizard report, you need to upgrade to asupported version or patch before continuing.

The Host Attach Wizard only displays options that are supported by

EMC. If any of the configuration information on the server utilitys highavailability report cannot be found in the wizard, then it is not supported.



9/55

Installing HBAs in the serverRead this section for any configuration.

For the server to communicate with the storage-system Fibre Channeldata ports, the server must have one or more supported HBAs.

Before you start

To complete this procedure, you need one or more supported HBAswith the latest supported BIOS and driver.

For information on supported HBAs, BIOS, and drivers, refer to theE-Lab Interoperability Navigator on the Powerlink website.

Installing HBAs

CAUTION

HBAs are very susceptible to damage caused by static discharge andneed to be handled accordingly. Before handling HBAs, observethe following precautions:

Store HBAs in antistatic bags.

Use a ground (ESD) strap whenever you handle HBAs.

Never plug or unplug HBAs with the power on. Severecomponent damage can result.

1. If the server is powered up:

a. Shut down the servers operating system.

b. Power down the server.

c. Unplug the servers power cord from the power outlet.

2. Put on an ESD wristband, and clip its lead to bare metal on theservers chassis.

3. For each HBA that you are installing:

a. Locate an empty PCI bus slot or a slot in the server that ispreferred for PCI cards.


9


10/55

b. Install the HBA following the instructions provided by the HBA

vendor.c. If you installed a replacement HBA, reconnect the cables that

you removed in the exact same way as they were connected tothe original HBA.

4. Plug the servers power cord into the power outlet, and power upthe server.

The Sun HBA driver software is bundled with the Solaris operating system

software.



11/55

Installing or updating the HBA driverRead this section for any configuration.

The server must run a supported operating system and HBA driver.EMC recommends that you install the latest supported version of thedriver. For information on the supported HBA drivers, refer to theE-Lab Interoperability Navigator on the Powerlink website.

Before you start

To complete this procedure, you will need:

The latest version of the supported HBA driver.

You can download the latest supported version and instructionsfor installing the QLogic HBA driver from the vendors website:http://support.qlogic.com/support/oem_emc.asp .

You can download the latest supported version and instructionsfor installing the Sun HBA driver from the vendors website:http://wwws.sun.com/software/download/allproducts.html . Onthis site, find the latest supported version of the Sun StorEdge SANdriver.

The HBA driver is also on the installation CD that ships with the HBA.However, this version may not be the latest supported version.

Any updates, such as hot fixes or patches to the servers operatingsystem that are required for the HBA driver version you will install.

For information on any required updates, refer to one of thefollowing:

z E-Lab Interoperability Navigator on the Powerlink website

z The HBA vendors website

Installing the HBA driver

1. Install any updates, such as hot fixes or patches, to the serversoperating system that are required for the HBA driver version youare installing.


11
http://powerlink.emc.com/http://support.qlogic.com/support/oem_emc.asphttp://wwws.sun.com/software/download/allproducts.htmhttp://powerlink.emc.com/http://powerlink.emc.com/http://wwws.sun.com/software/download/allproducts.htmhttp://support.qlogic.com/support/oem_emc.asphttp://powerlink.emc.com/


12/55

2. If required by hot fix or patch, reboot the server.

3. Install the driver following the instructions on the HBA vendorswebsite.

4. If you installed the QLogic HBA driver, set the parameters inthe /kernel/drv/qla2xxx.conf , except for the persistent bindingparameter, to the values required for PowerPath as described in theHBA driver instructions. You will set the persistent bindings afterthe storage system is connected to the server through the switches.

Some driver updates may require you to reboot the server.

5. Reboot the server when the installation program prompts you toreboot.

6. If the installation program did not prompt you to reboot, thenreboot the server when the driver installation is complete.



13/55

Installing the Admsnap utilityIf you want the server to access snapshots of LUNs in the storagesystem, you must install the Admsnap Utility on the server. TheAdmhost Utility is supported only on the following Microsoft Windowsplatforms: Windows Server 2008, Windows Server 2003, or Windows2000.

For the supported versions of these operating systems, see the Admhost Release

Notes.

Installing the Admsnap Utility on a Solaris server

EMC recommends that you install the most recent version of the

Admsnap Utility software that is appropriate for your configuration.You can download the most recent version from the software downloadpage on the Powerlink website (CX4 series, CX3 series, CX series, andAX4-5 series) or on the storage-system support website (AX series).You can also install the software from the server support CD (anystorage system); however, the CD may not contain the most recentversion for your configuration.

1. Log in to the Solaris server as a superuser, such as root.

2. If a previous revision is installed, remove it as described in Removingthe Admsnap Utility on a Solaris server, page 15.

3. To download the software for CX4 series, CX3 series, CX series, orAX45 series storage systems with Navisphere Manager, do thefollowing:

a. From the Navigator drop-down menu at the top right of the

Powerlink website, select Software Downloads and Patches.

b. Select the appropriate Admsnap Utility version to downloadand select the option to save the zip file to your server.

c. At the command line prompt, navigate to the directory whereyou saved the zip file and unzip the file.

unzip admsnap_version.zip


13


14/55

where version is the version listed in the filename.

d. Load the admsnap package:

/usr/sbin/pkgadd -d ADMSNAP.pkg

4. To install the software from the server support CD (any storagesystem), do the following:

a. In the servers drive, insert the server support CD that shippedwith your storage system.

The CD is mounted automatically on /cdrom/admsnap, whichis linked to /cdrom/cdrom0.

If the CD does not mount automatically, then mount the CDusing the mount/dev/cdrom command.

The File Manager Admsnap window appears withADMSNAP.pkg displayed.

b. Load admsnap from the CD by typing:

/usr/sbin/pkgadd /cdrom/cdrom0/solaris/ADMSNAP.pkg

The following messages appear:The following packages are available:1 ADMSNAP Navisphere Admsnap

(sparc) X.X.X.X.XSelect package(s)...to process (or "all" to process allpackages). (default: all) [?, ??, q]:

5. When prompted, enter y to install the admsnap package and yagain to continue the installation.

The installation script executes, listing the files installed, and oncompletion, displays the message: Installation of was successful.

The information described in the admsnap help and man pages does not

apply to servers connected to an AX100 series storage system. Use only the

admsnap commands described in this document.



15/55

6. Use the pkginfo command to verify the installation. Enter/usr/sbin/pkginfo-1 ADMSNAP.

Messages similar to the following appear:

PKGINST: ADMSNAPNAME ...CATEGORY: applicationVERSION X.X.X.X.XPSTAMP: Navisphere: 2000:10:28:13:03:01INSTDATE: November 20 2000 13:03STATUS: Completely installedFILES: xxxxxxx

xxxxxxxx xxxxxx

When you see the error-free pkginfo message, admsnap softwareinstallation is complete. The software is installed in the directory/usr/admsnap.

7. Unmount the CD by entering the unmount/dev/cdrom command.

8. Remove the CD from its drive.

Removing the Admsnap Utility on a Solaris server

1. Log in to the server as a superuser, such as root.

2. Remove the existing admsnap software by entering:

pkgrm ADMSNAP (uppercase ADMSNAP)

Then confirm, if prompted, by entering y and y. If admsnap is notinstalled, you will receive a Not found error message; continue.


15


16/55

Configuring Sun StorEdge Traffic Manager on the serverRead this section if you are connecting a new server to the storagesystem.

Sun StorEdge Traffic Manager (STMS) is Suns native pathmanagement software. STMS manages the I/O paths between theserver and storage system. STMS also provides I/O load balancing.

For Solaris 10, STMS is integrated into the Solaris operating systempatches you install. For Solaris 9, STMS is found in the SunStorEdge SAN Foundation package, revision 4.4.7 or later. Forinformation on these patches or packages, refer to Suns website athttp://www.sun.com/software/download/allproducts.html.

Before you use STMS, you need to:

Enable STMS by editing the following configuration file:

Solaris 10 Edit the /kernel/drv/fp.conf file, by changing thempxio-disable option from yes to no.

Solaris 9 Edit the /kernel/drv/scsi_vhci.conf file, by changingthe mpxio-disable option from yes to no.

Enable the STMS auto-restore feature in order to restore LUNs totheir default SP after a failure has been repaired (this is recommend).

In Solaris 10, auto-restore is enabled by default. For Solaris 9, editthe /kernel/drv/scsi_vhci.conf file, by changing the auto-failbackoption from disable to enable.

Share the root file system of the target system in a way that allowsroot access over NFS to the installing system, if you want to installSTMS offline over NFS. You can use a command such as thefollowing on target_sys to share the root file system on target_sys sothat installer_sys has root access:

share -F nfs -d root on target_sys -o ro,rw= installer_sys,root=installer_sys /

If the base directory of the package (the default is /opt ) is not partof the root file system, it also needs to be shared with root access.

Optionally, configure the host to send warnings to the consoleinstead of just to the log file:

1. Add the following line to the /etc/syslog.conf file:

http://www.sun.com/software/download/allproducts.htmhttp://www.sun.com/software/download/allproducts.htm


17/55

localx.Warn /dev/sysmsg

where x is a value that is not used by any other local settingin /etc/syslog.conf.

For example:local0.Warn /dev/sysmsg

The separator between local x.Warn and /dev/sysmsg must be a tabcharacter.

2. Set the RAD_LOG_FACILITY environment variable toLOG_LOCAL x, where x is the number you used in the localsetting of the /etc/syslog.conf file.

For example:

For csh, enter:setenv RAD_LOG_FACILITY LOG_LOCAL0

For sh, enter:RAD_LOG_FACILITY=LOG_LOCAL0; exportRAD_LOG_FACILITY


17


18/55

Connecting the storage system to the server in a Fibre Channeldirect configuration

Use optical cables to connect storage-system Fibre Channel front-enddata ports to the server HBA ports.

Before you start

To complete this procedure, you need an optical cable for each FibreChannel front-end data SP port that you will use on the storage system.For cable specifications, refer to the technical specifications for yourstorage system in the Documentation and Technical Advisories sectionof the Powerlink website or on the storage-system documentation andresources CD, which shipped with the storage system.

Identifying storage-system Fibre Channel front-end ports for server connectionsYou can connect servers to any ports (0, 1, 2, 3) on the UltraFlexFibreChannel I/O modules in slot A2 for SP A and in slot B2 for SP B (Figure4):

CL4248

1

2

3

10/100/1000

0

10/100/1000

0

B0 B1 B2 B3 B4 A4A0 A1 A2 A3

00

Figure 1 I/O module slots

Handling optical cables

Optical cables are susceptible to damage, so take the followingprecautions when handling them:

Keep the covers on all optical cables until you are ready to insertthem.

Avoid tight bends. If you need to make a 90 bend, do it over 6 to12 inches.

Do not use optical cables to support weight (including their own

unsupported weight if they are long).



19/55

Do not pull long runs of cable; instead, lay the cable in place or pullonly a few feet at a time.

Place the cables where no one can step on them or roll equipmentover them.

Cabling the Fibre Channel front-end data ports to the server HBA ports

For the highest availability with a multiple-HBA server:

If the server has two HBAs, connect one HBA to a Fibre Channelfront-end port on SP A and the other HBA to a Fibre Channelfront-port on SP B.

If the server has four HBAs, connect two HBAs to separate FibreChannel front-end ports on SP A, and the other two HBAs toseparate Fibre Channel front-end ports on SP B.

If the server has more than four HBAs, connect an HBA to a Fibre

Channel front-end port on SP A and another HBA to a FibreChannel front-end port on SP B, and continue connecting an HBAto a Fibre Channel front-end port on SP A and another next HBA toa Fibre Channel front-end port on SP B until you have connected allthe HBAs or used all the available Fibre Channel front-end ports.

For each new HBA port you want to connect to a storage-system FibreChannel (FC) front-end data port:

1. Locate the FC front-end data port to which you will connect theHBA port.

For information on identifying the front-end ports using NavisphereManager, refer to the Navisphere Manager help.

Applications such as MirrorView/A, MirrorView/S, or SAN Copy software

may restrict or require the use of certain SP ports. Refer to the applicationdocumentation for specific cabling information.

2. Remove the protective covers from the optical connector on theHBA port and from one end of an optical cable and plug the cableinto the HBA connector.

3. Remove the protective covers from the free end of the optical cable

and from the FC front-end data port connector on the storage


19


20/55


21/55

Connecting the storage system to the server in a Fibre Channelswitch configuration

Use optical cables to connect switch ports to the storage-system FibreChannel front-end data ports and to Fibre Channel switch ports and toconnect the switch ports to the server HBA ports.

Applications such as MirrorView/A, MirrorView/S, or SAN Copy

software may restrict or require the use of certain SP ports. Refer to the

application documentation for specific cabling information.

Before you start

To complete this procedure, you will need an optical cable for each

switch port you will use. Specifications for the optical cables thatconnect the switch to the storage system are in the storage systemstechnical specifications in the documentation section ofPowerlink.

Identifying storage-system Fibre Channel front-end ports for server connections

You can connect servers to any ports (0, 1, 2, 3) on the UltraFlexFibreChannel I/O modules in slot A2 for SP A and in slot B2 for SP B (Figure

4):

CL4248

1

2

3

10/100/1000

0

10/100/1000

0

B0 B1 B2 B3 B4 A4A0 A1 A2 A3

00

Figure 4 I/O module slots

Handling optical cables

Optical cables are susceptible to damage, so take the followingprecautions when handling them:

Keep the covers on all optical cables until you are ready to insert

them.


21


22/55

Avoid tight bends. If you need to make a 90 bend, do it over 6 to12 inches.

Do not use optical cables to support weight (including their ownunsupported weight if they are long).

Do not pull long runs of cable; instead, lay the cable in place or pullonly a few feet at a time.

Place the cables where no one can step on them or roll equipmentover them.

Cabling the Fibre Channel front-end data ports to the switch ports (if necessary)

For highest availability, connect one or more Fibre Channel front-enddata ports on SP A to ports on the switch and connect the same numberof Fibre Channel front-end data ports on SP B to ports on same switchor on another switch, if two switches are available.

Customer-installable switches are easily configured. Some are preconfigured,

to use only ports 0 and 4 for SP connections and only ports 1-3 and 5-15

for HBA connections. With switches set up in such hard zones, you can

connect the Fibre ports only to ports 0 and 4 and HBAs only to ports 13 and

515. For highest availability with one of these hard zoned switches and a

multiple-HBA server, connect either Fibre port on SP A to switch port 0 and

either FE port on SP B to switch port 4.

For each Fibre Channel (FC) front-end data port on the storage systemthat you will use for I/O with the server:

1. Locate the FC front-end data port to which you will connect theswitch port.

For information on identifying the front-end ports using NavisphereManager, refer to the Navisphere Manager help.

Applications such as MirrorView/A, MirrorView/S, or SAN Copy software

may restrict or require the use of certain SP ports. Refer to the application

documentation for specific cabling information.



23/55

2. Remove the protective cover from the FC front-end data portconnector on the SP and from one end of the optical cable, and plug

the cable into the data port connector (Figure 5 and Figure 6).

3. Remove the protective cover from the optical connector on theswitch port that you will use and from the free end of the opticalcable, and plug the cable into the switch port (Figure 5 and Figure 6).

CL4021

Figure 5 Connecting an optical cable

1

2

3

10/100/1000

0

10/100/1000

0 00

CL4228

Figure 6 Sample cabling between a storage system and two switches

Cabling the switch ports to the server HBA ports (if necessary)

For highest availability in a multiple-HBA server, connect one or moreHBA ports to ports on the switch and connect the same number of HBAports to ports on same switch or on another switch, if two switchesare available.


23


24/55

For each server HBA port that you will use for I/O with the storagesystem:

1. Remove the protective cover from the FC switch port connectorand from one end of the optical cable, and plug the cable into theconnector.

2. Remove the protective cover from the server HBA port connectorand from the free end of the optical cable, and plug the cable intothe HBA port connector (Figure 7).

CL4229

1

2

3

10/100/1000

0

10/100/1000

0 00

Figure 7 Sample cabling for a Fibre Channel switch configuration

Zoning the switches

You must use switch management software to update switch softwareand zone switches that are not hard zoned.

1. Connect the switch management ports to the network from whichyou will manage the switches.

2. If the switches are not running the most recent supported firmwareversion, install this software from the switch vendors website.



25/55

For information on the supported switch firmware versions, see the E-Lab

Interoperability Navigator on Powerlink.

3. Locate the zoning wizard CD that shipped with the switch.

4. Using the instructions provided with the CD, run the zoning wizardand select the zone configuration that is applicable to the way thatyou connected the storage-system Fibre ports and the server HBAports to the switch.


25


26/55

Configuring Sun HBAsRead this section if the server has one or more Sun HBAs connected tothe storage system.

Configuring the Sun HBAs connected to the storage system

1. Log in to the server as superuser (root).

2. Scan the server for the Sun HBAs you installed:

devfsadm -C

3. Determine the Solaris controller number for each HBA (controller)connected to the storage system:

cfgadm -la

Solaris displays information similar to the following:

Ap_Id Type Receptacle Occupant Conditionac0:bank0 memory connected configured okac0:bank1 memory connected configured okac1:bank0 memory connected configured okac1:bank1 memory connected configured ok

c1 scsi-bus connected configured unknownc1::dsk/c1t6d0 C D-ROM connected configured unknownc3 scsi-bus connected unconfigured unknownc4 scsi-bus connected unconfigured unknownc5 fc-fabric connected unconfigured unknownc6 fc-fabric connected unconfigured unknown...

The HBAs are typefc-fabric

, and the HBA number is the numberfollowing the c in the first column.

4. Configure each HBA as follows:

cfgadm -c configure cn

where n is the HBA number.



27/55

If multiple HBAs are connected to the storage system, you mustrun the above command for each HBA. For the example above,

which lists two fc-fabric entries (c5 and c6), you need to enterthe following two commands:

cfgadm -c configure c5cfgadm -c configure c6


27


28/55

Manually registering the Solaris server with the storage system

Read this section for any configuration.

You must follow the steps below on each server connected to thestorage system to register the servers HBAs with the storage system.Use Naivsphere Manager.

Determining the world wide name of an HBA in a Solaris server

Determine the world wide name (WWN) of each HBA that you willconnect to the storage system.

1. Create the following shell script named wwnscript.shto determine the world wide names (WWN) of theFibre Channel HBAs connected to the storagesystem, and declare this script as an executable.#!/bin/shfor i in cfgadm |grep fc-fabric|awk {print $1};dodev="cfgadm -lv $i|grep devices |awk {print $NF}"wwn="luxadm -e dump_map $dev|grep Host Bus|awk{print $4}"echo "$i: $wwn"done

2. Execute the wwnscript.sh script:

The sample output from the script below showstwo HBAs connected to the storage system:

c8: 210000e08b105e35c9: 210100e08b305e35

where C8 and C9 are the HBA (controller) numbers and210000e08b105e35 and 210100e08b305e35 are the WWNs of the

HBAs.

3. For each HBA, record its controller number and WWN.

4. Execute the luxadm probe command and verify that you have adevice name with the storage system node WWN and that this devicelists each path you created in the previous section. In the followingexample, there are 8 paths from the host to the storage system:

Node WWN:50060160ba600064 Device Type:Disk device Logical



29/55

Path:/dev/rdsk/c3t500601603A600064d0s2 LogicalPath:/dev/rdsk/c3t500601613A600064d0s2 LogicalPath:/dev/rdsk/c3t500601683A600064d0s2 LogicalPath:/dev/rdsk/c3t500601693A600064d0s2 LogicalPath:/dev/rdsk/c4t500601603A600064d0s2 LogicalPath:/dev/rdsk/c4t500601613A600064d0s2 LogicalPath:/dev/rdsk/c4t500601683A600064d0s2 LogicalPath:/dev/rdsk/c4t500601693A600064d0s2

Starting Navisphere Manager

To manage a CX4 storage system running FLARE OE version 04.28.000.5.5xx,

you must use Navisphere Manager UI version 6.28.10 or later.

1. Log in to a host (which can be a server) that is connected through anetwork to the storage systems management ports and that has anInternet browser: Microsoft Internet Explorer, Netscape, or Mozilla.

2. Start the browser.

3. In the browser window, enter the IP address of one of the followingthat is in the same domain as the storage systems that you wantto manage:

A storage-system SP with the most recent version of the FLAREOperating Environment (OE) installed

This SP can be in one of the storage systems that you want to manage.

A Navisphere off-array management station with the mostrecent Navisphere management server and UIs installed

A dialog box opens that requests your username and password.

If you do not have a supported version of the JRE installed, you will be

directed to the Sun website where you can select a supported version to

download. For information on the supported JRE versions for your version

of Navisphere Manager, refer to Environment and System Requirements

in the Navisphere Manager release notes on the storage-system support

website.


29


30/55

4. Enter the username and password for the account you want to use,and leave the scope unchanged (set to global).

The Navisphere Manager main window opens with a navigation paneon the left that contains the Navisphere taskbar and an EnterpriseStorage window on the right. The Navisphere taskbar consists ofthe following tabs: Storage Management, Monitoring, Replication,Reporting, Service. When you select a tab, it displays one or more iconsfor starting the wizards. The Enterprise Storage window contains tabsfor the following trees:

Storage tree Displays a storage-system icon for every storagesystem in this domain.

Hosts tree Displays a host icon for each server connected to anystorage system in this domain.

Monitors tree Displays a monitor icon for:

z Every monitored storage system in the domain.

z Storage systems that do not belong to the domain, but arephysically connected to a storage system that does belong. Anexample is a SAN Copy destination storage system.

The NavisphereManager user interface (UI) version 6.28.10 introducethe following new storage concepts storage pool, traditional LUN,thin pool, and thin LUN to support the virtual provisioning feature.

Thin pools and thin LUNs are part of the virtual provisioning feature, which

is available only on storage systems with FLARE OE version 04.28.5.00.5xx or

later and the virtual provisioning enabler installed.

Storage poolA general term for RAID groups and thin pools. In the Storage tree, a

storage pool displays as a single node beneath the storage system icon.RAID groups and thin pools are displayed under the storage pool node.

Traditional LUN or LUN (not a thin LUN)A logical unit that groups space on the disks in a RAID group intoone span of disk storage space and looks like an individual disk to anoperating system. The capacity for each traditional LUN you create isdistributed equally across the disks in the RAID group on which you

create the LUN. The amount of physical space allocated to a LUN is the



31/55

same as the user capacity seen by the host server. The storage capacityof a LUN is set when you create the LUN; however, you can expand it

by adding one or more other LUNs to it to create a metaLUN.

Thin poolA set of disks with the same RAID type (RAID 5 or RAID 6 only) thatshares its user capacity with one or more thin LUNs. We recommendthat all disks within the thin pool have the same capacity. RAID 6 is thedefault RAID type for a thin pool. You can expand the user capacity ofa thin pool by adding disks to it.

Thin LUNA logical unit ofstorage on a thin pool that looks like an individual diskto an operating system. A thin LUN consumes storage in the thin poolonly when data is written to it. It competes with other thin LUNs in thethin pool for the pools available storage. The capacity of the thin LUNthat is visible to the host is independent of the available physical storagein the thin pool. A thin LUN behaves very much like a traditional LUN.

Verifying SP and HBA connections using Navisphere Manager

Establish a connection between the SP and the HBA:

1. From the Navisphere Manager Storage tree, right-click the iconfor the storage system for which you want to verify connections,and click Connectivity Status.

The Connectivity Status dialog box opens.

2. Verify that the server to SP port connection is logged in but notregistered.

If your storage system has booted and the zones have beenestablished, but no SP/Port Status entries are displayed as Logged

In, you may have to wait for Navisphere Manager to update itsinitiator table from the storage system. If after 60 seconds, thestorage system still does not show the HBA as being Logged In,


31


32/55

verify the zoning configuration and status using the fabric switchconfiguration tool that the switch manufacturer supplies.

Registering SP and HBA connections with Navisphere Manager

When you have established a connection between the SP and theHBA, you must register the connection. Use Navisphere ManagersConnectivity Status window for the storage system to register eachHBA connection with the storage system:

1. In the Connectivity Status window, select the connection for theWWN of the HBA, click Register.

2. In the Register Initiator Record window, select the following:

Initiator Type ofCLARiiON Open

ArrayCommPath

Unit Serial Number ofArray

Failover Mode of:

z 1 for active passive mode

z 4 for asymmetric active active (ALUA) modes

Asymmetric active active (ALUA) failover is available for CX4

series storage systems, connected to Solaris servers that support

ALUA for CLARiiON storage systems, as described in the Sun

StorEdge Traffic Manager for CLARiiON Release Notes on the

Powerlink website.

.

3. In the Host Information box, select New Host and enter the

servers IP address, and click OK.

After a few seconds, the registration status of the HBA or NICconnection, should change from No to Yes. If an HBA or NICconnection has No in the Registered column or does not list theservers name, the registration was unsuccessful, and you may havea cabling or switch zoning problem.



33/55

Verifying storage-system health


Use the storage system verification wizard that is part of the NavisphereService Taskbar to:

Validate the connectivity of the storage-system hardwarecomponents

Check back-end functionality

Check the status of all field-replaceable units

Analyze storage-system logs

You download the NST from a link on the CLARiiON Tools page of the

Powerlink website to a Windows management station that is connected to the

storage-systems management ports. If you do not have a Windowsmanagement station, your service provider may run this wizard.

To access the CLARiiON Tools page, use the Navigator drop-down menu at

the top right of the Powerlink home page.

1. If you do not have the Navisphere Service Taskbar running:

a. Download and install the Navisphere Service Taskbar from theCLARiiON Tools page on the Powerlink website to a Windowsmanagement station that is connected to the storage-systemsmanagement ports.

To access the CLARiiON Tools page, use the Navigator drop-down

menu at the top right of the Powerlink home page.

b. Start the Navisphere Service Taskbar by doing one of thefollowing:

Click the Navisphere Service Taskbar icon on your desktop,or

Select Start > Programs > EMC > Navisphere > NavisphereService Taskbar version > Navisphere Service Taskbar

version


33
http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/


34/55

2. In the taskbars navigation pane, select the Hardware Maintenancetab.

3. In the tabs navigation pane, select Verify Storage System.

4. If the Navisphere Connection screen opens:

a. Enter the IP address for an SP in the storage system.

b. Click Connect.

c. Enter your Navisphere login username, password, and scope

(global, local, or LDAP) and click OK.

Once you connect to a storage system, you do not need to reconnect to it

again during the NST session. To connect to a different storage system, you

must disconnect the current storage system by selecting File > Disconnect.

5. Review the report that the wizard generates, and if it lists any

problems try to resolve them.

For assistance in resolving any problems, see the troubleshootingflowcharts for the storage system on the CLARiiON Tools page ofthe Powerlink website.



35/55

Setting storage-system failover values for the server initiators withNavisphere Manager

Use the Navisphere Manager Failover Setup Wizard to set thestorage-sytem failover values for all HBA initiators belonging to theserver:

1. Start Navisphere Manager for the storage system.

2. In the Tools menu, click Failover Setup Wizard.3. In the Start Wizard dialog box, read the introduction, and then

click Next.

4. In the Select Host dialog box, select the server you just connected tothe storage system, and click Next.

5. In the Select Storage Systems dialog box, select the storage system,and click Next.

6. In the Specify Settings dialog box, set the following values for thetype of software running on the server:

IMPORTANT

If you enter incorrect values the storage system could becomeunmanageable and unreachable by the server, and the serversfailover software could stop operating correctly.

Solaris 9 or 10For a Solaris 9 or 10 server, set:

Unit Serial Number to Array

Failover Mode to 4 if your failover version supports ALUA.

Failover Mode to 1 if your failover version does not supportALUA.

For information on which versions of failover support ALUA for

CLARiiON storage systems, refer to the PowerPath release notes or the

Sun StorEdge Traffic Manager for CLARiiON Release Notes on the

Powerlink website.


35


36/55

Solaris 8, 7, or 2.6For a Solaris 8, 7, or 2.6 server, set:

Failover Mode to 4 if your failover version supports ALUA.

Failover Mode to 1 if your failover version does not supportALUA.

For information on which versions of failover support ALUA for

CLARiiON storage systems, refer to the PowerPath release notes or the

Sun StorEdge Traffic Manager for CLARiiON Release Notes on the

Powerlink website.

For a Solaris 8, 7, or 2.6 server with any of the following packages:

Solstice DiskSuite

Sun Cluster 3.x

VERITAS DBE/AC

SFRAC

VRTSvcs with I/O fencing

set:

Unit Serial Number to LUN

For a Solaris 8, 7, or 2.6 server without any of the above packagesor with VRTSvcs without I/O fencing, set:

Unit Serial Number to Array

7. In Configuration Summary, review the configuration and allsettings.

8. If the settings are correct, click Next , and if the settings areincorrect, click Back until return to the dialog box in which youneed to re-enter the correct values.

If you clicked Next, the wizard displays a confirmation dialog box.

9. In the confirmation dialog box, click Yes.

The wizard displays a summary of the success of the operation to

set the values for the storage system.



37/55

10. If the operation failed, rerun the Failover Setup Wizard again.

11. When the operation is successful, click Finish to close the wizard.


37


38/55

Verifying your high-availability Fibre Channel configuration

Read this section for any Fibre Channel configuration.

Use the server high-availability feature in the Navisphere ServerUtility to verify the following for each server in a high-availabilityconfiguration with the storage system:

Your Fibre Channel configuration is highly available (that is, eachFibre Channel HBA has at least one active path to each storage

processor).

Path management software is installed and running on the server.

Before you start

If the Navisphere Server Utility is not installed on the server, locate theserver support CD, which shipped with the storage system.

Starting the Navisphere Server Utility on a Solaris server

1. Open a shell window.

2. Navigate to the Navisphere bin directory and run the server utility:

/opt/Navisphere/bin/naviserverutil

Starting the Navisphere Server Utility on a Solaris server from the CD

1. In the servers drive, insert the server support CD, which shippedwith the storage system.

2. Navigate to the Solaris directory:

/cdrom /cdrom0/solaris

3. Run the server utility:

./naviserverutilcli



39/55

Configuring an existing storage system

Read this section if you are configuring an existing storage system. Anexisting storage system is one that was already connected to a serverwhen you started the installation procedure.

Configure the storage system with Navisphere Manager.

To configure a storage system with Navisphere Manager, use either theNavisphere taskbar wizards or the Storage tree options of Navisphere

Manager.

Before you start

You need the completed storage-system disk information worksheetfrom the storage-system configuration planning guide or planningworksheets document. You can generate this guide using the

user-customized documentation link from theCLARiiON Tools

pageon the Powerlink website.

To access the CLARiiON Tools page, use the Navigator drop-down menu at

the top right of the Powerlink home page.

Allocating storage to an existing storage system with the Navisphere taskbar wizardsStarting with UI version 6.28.10.xx, the Allocate wizard has beenrenamed to Provision wizard. Like the Allocate wizard, use theProvision wizard, found in the Navisphere Manager taskbar, to createstorage system storage and provide server access to this storage.

You allocate storage with the Navisphere Provision or Allocate wizardonly to additional servers, that is, servers connected to Fibre Channel

ports . You cannot use this wizard to allocate storage to a Celerra host.

1. Locate your completed storage-system disk information worksheetso you can refer to it in the steps that follow.

2. In the Navisphere taskbar, click the Storage Management tab.

3. If you need additional LUNs for the server, use the Provision orAllocate wizard on the Storage Management tab to create them.


39
http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/


40/55

4. If you want to assign existing LUNs to the server, use the Assignwizard on the Storage Management tab to assign them.

For high availability, a host can connect to only one storage group per

storage system at a time. If you connect a host that is already connected

to another storage group, the host will disconnect from the first storage

group. When you disconnect a host from a storage group, and then connect

it to a different storage group, the host can no longer perform I/O to the

first storage group.

5. Verify that a server was assigned to the storage group.

If you know the name of the storage group in which the LUNsreside In the Navisphere Manager Storage tree:

Click the icon for the storage system with the storage groupwhose server connection you want to verify.

Click the Storage Groups icon.

Click the icon for the storage group.

If the server is assigned to a storage group, an icon for thatserver appears under the storage group icon.

If you know the name of the server to which the storage group is

assigned In the Navisphere Manager Hosts tree: Click the icon for the server to which you assigned the LUNs

and whose server connections you want to verify.

Click the LUNs icon and confirm that the new LUNs are listed.

If you do not see any of the LUNs you just created, you may nothave selected the Assign LUNs to a server option in the Select

Servers page of the Provision wizard. You can use the Assignwizard to assign the LUNs to a server.

Allocating storage to an existing storage system with the storage tree options

1. Locate your completed storage-system disk information worksheetso you can refer to it in the steps that follow.

2. Create additional traditional LUNs on new or existing RAID groups.



41/55

To create traditional LUNs on RAID Groups In the NavisphereManager Storage tree, depending on the UI and FLARE version

that you identified earlier, right-click the storage-system icon anddo one of the following:

Click Storage Pools Operations > Create LUNs ; create a newRAID group or select an existing one; create new LUNs on theRAID group.

Click Bind LUN; create a new RAID group or select an existingone; bind LUNs on the RAID group

For details on creating traditional LUNs and RAID groups, usethe Navisphere Manager help.

3. Create any additional storage groups that you need for the server.

To create storage groups In the Navisphere Manager tree,right-click the icon for the storage system, and click Create Storage

Groups. For details on creating storage groups, use the NavisphereManager help

4. Add the new LUNs you created to new or existing storage groups.

Adding a LUN to a storage group makes the LUN accessible to the servers

connected to the storage group. If a LUN is placed in more than one storage

group, all servers in those storage groups must be in a cluster configuration.

To add LUNs to storage groups Right-click the icon for thestorage group to which you want to add LUNs, and click SelectLUNs. For details on adding LUNs to storage groups, use theNavisphere Manager help.

5. Assign a server to a new or existing storage group.

To assign servers to storage groups In the Navisphere Managertree, right-click the icon for the storage group to which you wantto assign a server, and then click Connect Hosts. For details onassigning servers to storage groups, use the Navisphere Managerhelp.


41


42/55

For high availability, a host can connect to only one storage group per

storage system at a time. If you connect a host that is already connectedto another storage group, the host will disconnect from the first storage

group. When you disconnect a host from a storage group, and then connect

it to a different storage group, the host can no longer perform I/O to the

first storage group.

6. Verify that the server was assigned to the storage group.

To verify that a server is assigned to a storage group In theNavisphere Manager tree:

Click the icon for the storage system with the storage groupwhose server connection you want to verify.

Click the Storage Groups icon.

Click the icon for the storage group.If the server is assigned to a storage group, an icon for thatserver appears under the storage group icon.

Verifying that each LUN is fully initialized using Navisphere Manager

Although the storage group with a new LUN is assigned to the

server, the server cannot see the new LUN until it is fully initialized(completely bound). The time to complete the initialization processvaries with the size of the LUN and other parameters. While a LUN isinitializing, it is in a transitioning state, and when the initialization iscomplete, its state becomes normal.

To determine the state of a LUN

1. In the Navisphere Manager Storage tree, navigate to the LUN you

want to verify.2. Right-click the LUN and click Properties.

Making LUNs visible to a Solaris server

To allow the Solaris server access to the LUNs that you created:

1. From the server, scan for the LUNs:

devfsadm -C.



43/55

2. Use the format command to verify that Solaris recognizes the LUNs.

If Solaris does not recognize the LUNs, reboot the server:reboot -r

Verifying that Sun StorEdge Traffic Manager sees all paths to the LUNs

For Solaris 9 or previous versions,

1. In a command window, view all disks (LUNs) this server has access

to by entering the luxadm probe command.

In the output below, there are eight paths from the host to thestorage system. Within each logical path:

C3 represents one of the HBAs and C4 is the other.

The number 006016X3A600064 is the WWPN of each SP port onthe storage processors. In this case, the X indicates the storage

system port: 60 (A0), 61 (A1), 68 (B0), or 69 (B1).

You can interpret from the output below that for the storage systemwith the World Wide Name 50060160ba600064:

Controller 3 has a path to SP A0, SP A1, SP B0, and SP B1.

Controller 4 also has a path to SP A0, SP A1, SP B0, and SP B1.

Sample fibre channel output follows:

Node WWN:50060160ba600064 Device Type:Disk deviceLogical Path:/dev/rdsk/c3t500601603A600064d0s2Logical Path:/dev/rdsk/c3t500601613A600064d0s2Logical Path:/dev/rdsk/c3t500601683A600064d0s2Logical Path:/dev/rdsk/c3t500601693A600064d0s2Logical Path:/dev/rdsk/c4t500601603A600064d0s2

Logical Path:/dev/rdsk/c4t500601613A600064d0s2Logical Path:/dev/rdsk/c4t500601683A600064d0s2Logical Path:/dev/rdsk/c4t500601693A600064d0s2

2. For each LUNs WWN, enter the following command:

luxadm display /dev/rdsk/c5tWWNd0s2

where WWNis the LUNs WWN.


43


44/55

For example:luxadm display

/dev/rdsk/c5t60060160FFA415013EBD91DECF10DA11d0s2

The output lists the following information for each fibre channelHBA (controller) path to the or LUN displayed by luxadm displaycommand:

Device address WWN of the SP port and the or LUN number.

Host controller port WWN WWN of the HBA connection.

Class Whether the path is the primary or secondary path tothe LUN. A primary path is through the SP that is the defaultowner of the or LUN; a secondary path is through the other SP.

State Whether the path is ONLINE, STANDBY, or OFFLINE.Active paths (paths that are available for I/O) are ONLINE;passive paths are STANDBY; and, failed paths are OFFLINE. Apath is working if it is ONLINE or STANDBY.

3. Under each HBA (controller), verify the state is either ONLINE, ifthe class is primary, or STANDBY, if the class is secondary.

For Solaris 10 versions:

1. In a command window, view all disks (LUNs) this server has accessto by entering the mpathadm list lu command.

Results:

/dev/rdsk/c1t60060160C3751D0010C02D6ADE8EDD11d0s2

Total Path Count: 4

Operational Path Count: 4

2. For each LUNs WWN, enter the following command:

mpathadm show lu/rdsk/c1t60060160C3751D0010C02D6ADE8EDD11d0s2

Results:

Logical Unit: /dev/rdsk/c1t60060160C3751D0010C02D6ADE8EDD11d0s2mpath-support: libmpscsi_vhci.soVendor: DGC

Product: VRAID



45/55

Revision: 0428Name Type: unknown typeName: 60060160c3751d0010c02d6ade8edd11

Asymmetric: yesCurrent Load Balance: round-robinLogical Unit Group ID: NAAuto Failback: onAuto Probing: NA

Paths:Initiator Port Name: 210000e08b0f3c57Target Port Name: 500601603b20031fOverride Path: NAPath State: OKDisabled: no

Initiator Port Name: 210000e08b0f3c57Target Port Name: 5006016a3b20031fOverride Path: NAPath State: OKDisabled: no

Initiator Port Name: 210100e08b2f3c57Target Port Name: 500601683b20031fOverride Path: NAPath State: OKDisabled: no

Initiator Port Name: 210100e08b2f3c57Target Port Name: 500601623b20031fOverride Path: NAPath State: OKDisabled: no

Target Port Groups:ID: 1Explicit Failover: yesAccess State: active optimized

Target Ports:Name: 500601603b20031fRelative ID: 1

Name: 500601603b20031fRelative ID: 2

.

.

.

ID: 2Explicit Failover: yes

Access State: active not optimizedTarget Ports:

Name: 5006016a3b20031fRelative ID: 24

Name: 5006016a3b20031fRelative ID: 25


45


46/55

Preparing LUNs to receive data

Read this section if you created LUNs on the storage system.

If you do not want to use a LUN as a raw disk or raw volume, thenbefore Solaris can send data to a LUN, you must partition the LUN andthen create and mount a file system on it.

Partitioning LUNs for a Solaris server

For each LUN:

1. On the server assigned to the LUN, enterformat disk_namewhere disk_name is the LUN device name.

For example:

format c2t0d2

If you do not know the disk name, enter format, and from theAvailable Disk Selections menu, select the disk number.

2. If you are prompted to label the disk, enter y.

3. From the main Format menu, enter partition and press Enter tomodify the partition.

4. From the main Partition menu, enter label and press Enter to labelthe disk.

5. Enter q to exit the partition menu.

6. From the main Format menu, enter verify to verify the partition.

Creating and mounting a file system for a Solaris server

To make the partition usable, you must create a file system in thepartition:

1. Create a file system:

newfs /dev/rdsk/disk_name_parition_number

where:



47/55

disk_name is the LUN device name

partition_number is the partition number

For example:

newfs /dev/rdsk/c2t0d0s0

2. When you are prompted to confirm the construction of a new file

system, enter y and press Enter.

3. Create a mount directory for the file system:

mkdir mount_ point

For example:

mkdir /temp

4. Mount the file system:

mount /dev/dsk/disk_name_partition_number_mount_point

For example:

mount /dev/dsk/c2t0d0s0 /temp

This mounts the partition /dev/dsk/c2t0d0s0 onto the mount pointtemp.

To verify that the file system was mounted, enter df -k.

This mount command is required every time the server is rebooted.If you prefer, you can have the file system mount automatically at

boot time by adding this mount command to the /etc/vfstab file.


47

h d d d d f h f l


48/55

The server can now write data to and read data from the file system.

Unmounting a file system for a Solaris server

1. Make sure you are out of the mount point directory by entering cd /.

2. Enterumount mount_point.

For example:

umount /temp



49/55

Sending Solaris disk information to the storage system


If the Navisphere Host Agent is installed on the server, start or restart(stop and then start) it to send to the storage system the operatingsystems device name and volume or file system information foreach LUN that the server sees. Navisphere Manager displays thisinformation on its LUN Properties Host page for each LUN.

The Navisphere Server Utility does not send operating system LUN mapping

information to the storage system.

Stopping the host agent

Log in as root and enter this command:

/etc/init.d/agent stop

Starting the host agent

Log in as root and enter this command:

/etc/init.d/agent start

Verifying that the storage system received the LUN information using NavisphereManager

1. Start Navisphere Manager on the storage system with the LUNs.

2. For each LUN in the storage system that is connected to the server,display its Navisphere Manager LUN Properties Hosts page:

a. In the Navisphere Manager Storage tree, navigate to the LUNyou want to verify.

b. Right-click the icon for the LUN, and click Properties.

3. Verify that the Properties page displays a physical device andlogical device name for the LUN.


49


50/55

Verifying your Solaris server failover configuration

If your server has a high-availability configuration, that is, at leastone HBA path to each SP on the storage system, your environmentis enabled for failover and you can proceed to verify your failoverconfiguration for a dual-SP storage system.

If you do not have a high-availability configuration, you have a singleSP, and an SP failure leaves the server without access to the data. If youhave a single SP with only one HBA, your environment is not enabledfor failover. An HBA failure leaves the server without access to thedata. If you have a single SP with more than one HBA, and an HBAfails, you can verify your failover configuration for HBAs.

Before you start

Before you store data on LUNs or , use the procedure in this section to

verify that: The server can send data to and receive data from the storage

system.

You can download an I/O simulator (Iometer) for writing data to the

storage system from the following website: http://www.iometer.org/.

Sun StorEdge Traffic Manager shows the paths from the server tothe LUN or that you expect for your configuration.

Verifying your dual-SP failover configuration with Sun StorEdge Traffic Manager

This test applies to a server with at least one HBA path to each SP ona dual-SP storage system.

http://www.iometer.org/http://www.iometer.org/


51/55

CAUTION

This test requires that you disconnect all optical cables from theFibre Channel ports on one of the SPs on the storage system. Whenyou disconnect the optical cables from one of the SPs, all LUNs onthat SP fail over to the other SP (trespass), which makes the other SPthe only point of data access for all servers connected to the storagesystem. Servers without failover software configured and at least oneadditional path to the other SPloses access to their data. To ensurethat all servers connected to this storage system maintain access totheir LUNs during this test, verify through your failover software oror Navisphere Manager that the servers have at least one path to eachSP. To verify that your failover software is configured to maintainaccess to data, refer to your operating system documentation forservers running native failover. For each or LUN that fails over to theother SP, you must to manually restore the or LUN to its original SP.

1. On the server, list the LUNs available to the server by entering theluxadm probe command.

The following output is displayed:

No Network Array enclosures found in /dev/esFound Fibre Channel device(s):

Node WWN:50060160ba600064 Device Type:Disk deviceLogical Path:/dev/rdsk/

c5t60060160FFA415013EBD91DECF10DA11d0s2Node WWN:50060160ba600064 Device Type:Disk device

Logical Path:/dev/rdsk/c5t60060160FFA415015C5A51A9CB10DA11d0s2

2. For each or LUNs WWN, enter the following command:


where WWN is the or LUNs WWN. For example:luxadm display/dev/rdsk/c5t60060160FFA415013EBD91DECF10DA11d0s2

The output lists the following information for each HBA (controller)path to the or LUN displayed by luxadm display command:



51



52/55


Class Whether the path is the primary or secondary path to

the or LUN. A primary path is through the SP that is the defaultowner of the or LUN; a secondary path is through the other SP.

State Whether the path is ONLINE, STANDBY, or OFFLINE.Active paths are ONLINE; passive paths are STANDBY; and,failed paths are OFFLINE. A path is working if it is ONLINEor STANDBY.

Leave the output displayed open.

3. Choose a or LUN that is currently accessed through the SP youwant to test and start writing data to the or LUN.

4. For the SP that corresponds to the active path for the or LUN,disconnect the optical cables from the Fibre Channel ports.

When you disconnect the optical cables, I/O freezes forapproximately 60 seconds until failover occurs. After failoveroccurs, I/O should resume normally.

5. After approximately 60 seconds, verify that a failover hasoccurred to the other SP by rerunning theluxadm display command. For example:luxadm display

/dev/rdsk/c5t60060160FFA415013EBD91DECF10DA11d0s26. Verify the following:

The state ofthe secondary SP is now listed as ONLINE and theprimary SP is OFFLINE. This indicates that the original activepath (primary) is no longer operational, and a failover (trespass)has occurred to the other (secondary) SP.

I/O (data) has continued to the or LUN from the server, butis now going through another HBA, indicating that the pathfailover was successful.


7. Reconnect the optical cables that you disconnected from the SP.


53/55

p yThe active path automatically reverts back to the original active

path.

Verifying your single-SP HBA failover configuration with Sun StorEdge Traffic Manager

This test applies to a server with more than one HBA connected to asingle-SP storage system. If you have a single SP with only one HBA,your environment is not enabled for failover. An HBA failure leavesthe server without access to the data.

1. On the server, list the LUNs available to the server by entering theluxadm probe command.

The following output is displayed:

No Network Array enclosures found in /dev/esFound Fibre Channel device(s):

Node WWN:50060160ba600064 Device Type:Disk deviceLogical Path:/dev/rdsk/

c5t60060160FFA415013EBD91DECF10DA11d0s2Node WWN:50060160ba600064 Device Type:Disk deviceLogical Path:/dev/rdsk/

c5t60060160FFA415015C5A51A9CB10DA11d0s2

2. For each or LUNs WWN, enter the following command:


where WWN is the or LUNs WWN. For example:luxadm display/dev/rdsk/c5t60060160FFA415013EBD91DECF10DA11d0s2

The output lists the following information for each HBA (controller)path to the or LUN displayed by luxadm display command:



Class SP path to the or LUN. In a single-SP storage system,primary is always listed as the class.

State Whether the path is ONLINE, STANDBY, or OFFLINE.Active paths (paths that are available for I/O) are ONLINE;passive paths are STANDBY; and failed paths are OFFLINE. Apath is working if it is ONLINE or STANDBY.


53

Leave the output displayed open.


54/55

3. Choose a or LUN that is currently accessed through the HBA you

want to test and start writing data to the or LUN.

4. For the HBA that corresponds to the active path for the disk,disconnect the optical cable from the Fibre Channel HBA port.

When you disconnect the optical cable, I/O freezes forapproximately 60 seconds until failover occurs. After failoveroccurs, I/O should resume normally.

5. After approximately 60 seconds, verify that a failover hasoccurred to the other SP by rerunning theluxadm display command. For example:luxadm display/dev/rdsk/c5t60060160FFA415013EBD91DECF10DA11d0s2

6. Verify the following:

The state of the uncabled HBA path is OFFLINE. I/O (data) has continued to the or LUN from the server, but

is now going through another HBA, indicating that the pathfailover was successful.

7. Reconnect the optical cable that you disconnected from the HBA.The active path automatically reverts back to the original activepath.

To configure an NS20FC or NS40FC for use with the following applications,

refer to the configuration steps in Solution Case emc165977: Domain

Connectivity, Event Monitor, MirrorView/A, MirrorView/S, Navisphere

Analyzer, or SAN Copy, or if you prefer to use Navisphere Manager instead of

Off Array Navisphere Manager.



55/55

Copyright 2008 EMC Corporation. All Rights Reserved.

EMC believes the information in this publication is accurate as of its publication date. Theinformation is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATIONMAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TOTHE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires anapplicable software license.

For the most up-to-date regulatory document for your product line, go to the TechnicalDocumentation and Advisories section on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks onEMC.com.

All other trademarks mentioned herein are the property of their respective owners.


55

Ns 120 Server Solaris Native

Documents

Transcript of Ns 120 Server Solaris Native