Attaching Server To Storage System - Master 1073670

Here is Your Customized Document
Your Configuration is:

Action to Perform - Attach server
Storage-System Model - CX4-960
Storage-System Status - New
Connection Type - Fibre Channel Switch
Server Status - New
Server Operating System - Solaris
Path Management Software - EMC PowerPath
HBAs to Install - QLogic HBA
Reporting Problems
To send comments or report errors regarding this document, please email:
UserCustomizedDocs@emc.com. For issues not related to this document, contact
your service provider.
Refer to Document ID: 1073670
Content Creation Date 2010/3/8

CX4 Series
Attaching a Solaris Server with
EMC PowerPath to a CX4-960
Storage System in a Fibre Channel
Switch Configuration
This document explains how to attach a Solaris server with EMC®

PowerPath® to a CX4-960 storage system in a Fibre Channel switch
configuration.
The main topics are:
Before you start ............................................................................. 2
Determining if your server has a supported configuration................ 4
Installing HBAs in the server.......................................................... 7
Installing or updating the HBA driver ............................................ 9
Modifying Solaris system settings .................................................. 11
Installing PowerPath software ........................................................ 13
About EMC CLARiiON server software.......................................... 15
Installing CLARiiON server software.............................................. 18
Disabling Sun StorEdge Traffic Manager to use PowerPath .............. 39
Connecting the storage system to the server in a Fibre Channel
switch configuration ..................................................................... 40
Registering server with the storage system ...................................... 47
Verifying storage-system health...................................................... 50
Setting storage-system failover values for the server initiators........... 52
Verifying your high-availability Fibre Channel configuration ........... 54
Installing CLARalert software ........................................................ 56
Configuring a new storage system .................................................. 59
Preparing LUNs to receive data ...................................................... 70
Sending Solaris disk information to the storage system .................... 71
Verifying your failover configuration with PowerPath ..................... 72
1
Before you start
❑ Read the release notes for your storage system, which are available
in the Technical Documentation and Advisories section on the
Powerlink® website.
❑ If you have not done so already, complete the configuration
planning worksheets in the storage-system configuration planning
guide or planning worksheets document. You can generate an
up-to-date version of the planning guide customized for your
installation from the Plan link on the storage-system support
website.
❑ A supported Windows host on the same network as the
storage-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 the
storage-system data ports).
❑ A Navisphere® management station with a supported Internet
browser that is on the same network as the storage-system
management ports. This host can also be the server or a Navisphere
off-array management station. For supported Internet browsers,
see the Navisphere Manager release notes in the Technical
Documentation and Advisories section of the Powerlink website.
❑ A Solaris host that is or will be a server with Fibre Channel
connections to the storage system. This server must have a
supported server configuration; that is, it must have all required
updates, such as hot fixes or patches, installed.
❑ One or more supported QLogic Fibre Channel host bus adapters
(HBAs), which may already be installed in the server. These
adapters must have the latest supported BIOS and driver.
Never mix Fibre Channel HBAs from different vendors in the same server.
❑ An optical cable for each storage-processor (SP) Fibre Channel port

you will use on the storage system. (Each storage processor has two
Attaching a Solaris Server with EMC PowerPath to a CX4-960 Storage System in a Fibre Channel
2
ports.) These cables may already be connected for a configuration
with an existing storage system or server. We strongly recommend
you use OM3 50 µm cables. For cable specifications, refer to
storage-system’s Technical Specifications. You can generate this
document using the user customized documentation Learn about
storage system link on the storage-system support website.
❑ 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. We strongly recommend you use OM3
50 µm cables. For cable specifications, refer to storage-system’s
Technical Specifications. You can generate this document using the
user customized documentation Learn about storage system link
on the storage-system support website.
❑ A method for writing data to a LUN on the storage system that
will test the paths from the server to the storage system. You can
download an I/O simulator (Iometer) from the following website:
http://www.iometer.org/.
Attaching a Solaris Server with EMC PowerPath to a CX4-960 Storage System

3
in a Fibre Channel Switch Configuration
Determining if your server has a supported configuration
Before you can determine if your server has a supported configuration,
you need to know the revision and patch level of the operating system
on the server.If you have this information, go to Verifying a server’s
configuration with E-Lab Interoperability Navigator, page 5 . If you do not
have this information, you can generate a server configuration report
for your server using the Navisphere Server Utility.
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

If you have version 6.28 or earlier of the server utility, you can start it
from the CD as described below.
1. In the server’s drive, insert the server support CD, which shipped
with the storage system.
2. Navigate to the Solaris directory:
/cdrom /cdrom0/solaris
3. Run the server utility:
./naviserverutilcli
Generating a high-availability report for a server

1. In the Navisphere Server Utility select option 3 from the server
utility’s Welcome screen to generate a report of the server’s
environment.
This option detects if PowerPath or some other failover software,

such as DMPor Sun StorEdge Traffic Manager, is running. After the
4
verification, the utility generates a summary report and saves it
to the server.
2. In the summary report, select the Checklist tab to view the
information about the server that you need to compare against the
E-Lab™ Interoperability Navigator information.
Verifying a server’s 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 a
username 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 Launch
E-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 information
based on what is already installed on the server or what you intend
to install on the server.
If the configuration you entered is invalid, an additional step

appears in the wizard and a Results, EMC Support Statements
pane appears on the right with information to help you provide the
requested information in the additional step.
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 using
the server utility.

5
12. If your server software versions and/or patches or hot-fixes are not
listed in the Host Attach Wizard report, you need to upgrade to a
supported 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 utility’s high
availability report cannot be found in the wizard, then it is not supported.
6
Installing HBAs in the server
For the server to communicate with the storage-system Fibre Channel
data ports, it must have one or more supported HBAs.
Before you start

To complete this procedure, you will need one or more supported
HBAs with the latest supported BIOS and driver.
For information on supported HBAs, BIOS, and drivers, refer to the
E-Lab™ Interoperability Navigator on the Powerlink website.
Installing HBAs
! CAUTION
HBAs are very susceptible to damage caused by static discharge and

need to be handled accordingly. Before handling HBAs, observe
the 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. Severe
component damage can result.
1. If the server is powered up:

a. Shut down the server’s operating system.
b. Power down the server.
c. Unplug the server’s power cord from the power outlet.
2. Put on an ESD wristband, and clip its lead to bare metal on the
server’s chassis.
3. For each HBA that you are installing:
a. Locate an empty PCI bus slot or a slot in the server that is
preferred for PCI cards.

7
b. Install the HBA following the instructions provided by the HBA
vendor.
4. Plug the server’s power cord into the power outlet, and power up
the server.
8
Installing or updating the HBA driver
The server must run a supported operating system and HBA driver.
EMC recommends that you install the latest supported version of the
driver. For information on the supported HBA drivers, refer to the
E-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 instructions
for installing the QLogic HBA driver from the vendor’s website:
http://support.qlogic.com/support/oem_emc.asp.
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 server’s operating

system that are required for the HBA driver version you will install.
For information on any required updates, refer to one of the
following:
z E-Lab™ Interoperability Navigator on the Powerlink website
z The HBA vendor’s website
Installing the HBA driver

1. Install any updates, such as hot fixes or patches, to the server’s
operating system that are required for the HBA driver version you
are installing.
2. If required by hot fix or patch, reboot the server.
3. Install the driver following the instructions on the HBA vendor’s
website.
4. If you installed the QLogic HBA driver, set the parameters in
the /kernel/drv/qla2xxx.conf, except for the persistent binding
parameter, to the values required for PowerPath as described in the

9
HBA driver instructions. You will set the persistent bindings after
the 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 to

reboot.
6. If the installation program did not prompt you to reboot, then
reboot the server when the driver installation is complete.
10
Modifying Solaris system settings
This section lists the recommended Solaris environment setting changes
with a CLARiiON storage system.
Modifying the Solaris system specification file

You must modify the sd_io_time and sd_max_throttle parameters in
the /etc/system file when operating in a Solaris environment.
IMPORTANT
In Solaris, the sd_max_throttle settings are global, so all devices
including non-meta devices will also be affected.
1. Set sd_io_time to 60 seconds.

set sd:sd_io_time = 0x3C
This setting prevents the host from issuing warning messages

while non-disruptive operations are performed on the EMC storage
system.
2. Set sd_max_throttle to 20.
set sd:sd_max_throttle = 20
This setting prevents the host from over-sending tag queuing

commands which may cause scsi cmd timeout and scsi bus reset.
A maximum throttle setting of 20 means that each host device

instance will have no more than 20 commands outstanding
(incomplete I/Os from the standpoint of the operating system) at
any given time. This setting is suitable for many environments.
However, in some situations this value can be further fine-tuned for
configuration-specific optimizations. For example, in the case of
meta devices (which have more physical devices on the back-end
and can thus physically process more I/Os in parallel), it may be

11
beneficial to increase the queue depth to 32. Contact your EMC
Customer Service representative for assistance.
Configuring host warnings

You can configure the host to send warnings to the console instead of
just to the log file. This step is optional.
1. Add the following line to the /etc/syslog.conf file:
localx.Warn /dev/sysmsg
where x is a value that is not used by any other local setting in

/etc/syslog.conf.
For example:
local0.Warn /dev/sysmsg
The separator between local x.Warn and /dev/sysmsg must be a tab

character.
2. Set the RAD_LOG_FACILITY environment variable to

LOG_LOCAL x, where x is the number you used in the local setting
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;
export RAD_LOG_FACILITY
12
Installing PowerPath software
To install PowerPath, refer to the appropriate PowerPath Installation
and Administration Guide for your operating system. This guide is
available in the Technical Documentation and Advisories section on the
Powerlink website.
Before you install PowerPath

In the /etc/system file, make sure the timeout value is set
to 60 seconds. This minimizes path failover time without
compromising online storage-system microcode or base
code upgrades. The entry must be a hexadecimal number:
set ssd: ssd_io_time = 0x3C
Optionally, configure the host to send warnings to the console
instead of just to the log file:
1. Add the following line to the /etc/syslog.conf file:
localx.Warn /dev/sysmsg
where x is a value that is not used by any other local setting in

/etc/syslog.conf .
For example:
local0.Warn /dev/sysmsg.
The separator between local x.Warn and /dev/sysmsg must be a tab

character.
2. Set the RAD_LOG_FACILITY environment variable to

LOG_LOCAL x, where x is the number you used in the local
setting of the /etc/syslog.conf file.
For example:
For csh, enter:

setenv RAD_LOG_FACILITY LOG_LOCAL0

13
For sh, enter:
RAD_LOG_FACILITY=LOG_LOCAL0; export
RAD_LOG_FACILITY
Share the root file system of the target system in a way that allows
root access over NFS to the installing system, if you want to install
PowerPath offline over NFS. You can use a command such as the
following on target_sys to share the root file system on target_sys so
that 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 part
of the root file system, it also needs to be shared with root access.
If the Navisphere host agent is running on the server, stop it:
/etc/init.d/agent stop
Stop all applications that use PowerPath if you are upgrading from
PowerPath 4.0.4 or later. For example, unmount all file systems
mounted on PowerPath pseudo devices. If you do not stop these
applications, uninstalling PowerPath 4.0.2 or later in preparation for
the upgrade will abort with a message indicating that PowerPath
pseudo devices are still in use. If this happens, you must either stop
applications using PowerPath and try pkgrm again, or reboot the
server and postpone the upgrade.
Prepare for the cluster, if you are installing PowerPath for a cluster
environment, as described in PowerPath for Solaris Installation and
Administration Guide in PowerPath section of the Powerlink website.
TIP To find this document on the Powerlink website, enter PowerPath for
Solaris in the Powerlink search field.
14
About EMC CLARiiON server software
This section describes all the available CLARiiON server software.
Your operating system or configuration may not support all the
software mentioned.
As of release 6.29, the server support CD no longer ships with your storage
system.
Navisphere Storage System Initialization Utility

Navisphere Command Line Interface (CLI)
Navisphere Host Agent
Navisphere Server Utility
Admsnap Utility
About the Navisphere Storage System Initialization Utility

For Fibre Channel storage systems, use the Navisphere® initialization
utility to discover storage systems and set network parameters (IP
address, subnet mask, and default gateway). In addition, for iSCSI
storage systems with iSCSI data ports attached to Windows servers, use
the utility to set network parameters for these ports.
You can install it on a server or other host such as a Navisphere
off-array management station. The only requirement is that the host
be connected to the same network subnet as the storage-system
management ports.
About the Navisphere CLI

The CLI complements or is an alternative to Manager. It provides a
command line interface for storage-system management, including
storage provisioning, status and configuration information retrieval,
and control. You can use the CLI to automate management functions

15
through shell scripts and batch files. For more information, refer to the
EMC Navisphere Command Line Interface (CLI) Reference Guide.
About the Navisphere Host Agent

The host agent registers the server’s host bus adapter (HBA) with the
attached storage system when the host agent service starts. This action
sends the initiator records for each HBA to the storage system. Initiator
records are used to control access to storage-system data.
The agent can then retrieve information from the storage system
automatically at startup or when requested by Navisphere Manager
or the CLI.
The host agent can also:
Send operating system drive mapping information to the attached
CLARiiON® storage systems.
Monitor storage-system events and notify personnel by email, page,
or modem when any designated event occurs.
Retrieve LUN world wide name (WWN) and capacity information
from Symmetrix® storage systems.
About the Navisphere Server Utility

The server utility allows you to perform the following functions:
Update server information to the storage system — Lets you send
the server name and IP address to the storage system and, if needed
later on, allows you to update or view this data.
Verify server high availability (HA) — Lets you determine if the
server is configured for high availability (HA) by verifying that
the server has at least one connection path to each storage-system
SP, and that PowerPath® or some other failover software, such as
VMware native, DMP, PV Links, or HP native failover for 11iV3
is running. The utility does not detect any other native failover
software, such as Sun StorEdge Traffic Manager or Linux native
multipath (MPIO).
This feature is not available on iSCSI servers.
16
Use the snapshot feature (Navisphere Express only) — On storage
systems with Navisphere Express, you can start and stop a snapshot
on the source server (server assigned to the source virtual disk or
source LUN), or you can allow or remove access to the snapshot by
the secondary server (server assigned to the snapshot).
You can run the Navisphere Server Utility from the CD or you can
install it on the servers that are connected to the storage system. We
strongly recommend that you install the utility on each server that is
connected to the storage system.
About the Admsnap Utility

The Admsnap Utility is an executable program that you can run
interactively or with a script to manage SnapView® clones and
snapshots. The Admsnap Utility resides on the servers connected to
the storage system with the SnapView driver installed.
Use admsnap commands to:
Scan for new storage devices
Make storage devices inaccessible to the server operating system
Flush cached data to disk
List current snapshot devices
Map and unmap to a SnapView session
Start and stop a SnapView session
If you upgraded your storage system to Navisphere Manager and want to

manage snapshots, you must use the SnapView software and the Admsnap
Utility. For more information on SnapView and admsnap, refer to the
Navisphere Manager help and the EMC SnapView Command Line Interfaces
Reference.

17
Installing CLARiiON server software
This section describes how to install CLARiiON server software.
Before you install
Refer to the sections below to determine which application to install
for host registration and the requirements for installing each of these
applications.
To determine whether to install the Navisphere Host Agent or
Navisphere Server Utility to register your HBAs with the storage
system, refer to Determining whether to install the host agent or server
utility , page 18.
To run CLARiiON server software, your server must meet the
requirements outlined in Requirements for CLARiiON server
software, page 20.
Installing CLARiiON server software

Depending on which CLARiiON server software you are installing,
refer to the appropriate section below.
Navisphere Host Agent and/or Navisphere CLI – see Installing the
Navisphere Host Agent and/or CLI , page 21.
Navisphere Server Utility – see Installing the Navisphere Server
Utility , page 34.
Admsnap Utility – see Installing the Admsnap Utility , page 35.
Determining whether to install the host agent or server utility

Depending on your application needs, you can install the host agent,
server utility, or both on an attached server.
To register the server’s HBAs with the storage system, you must use the
Navisphere Server Utility or Navisphere Host Agent on each server
that is connected to the storage system.
18
IMPORTANT
If you want to install both applications, you must install version 6.22.20
or later of the server utility either before or after you install the host
agent. The registration feature of the server utility will be disabled
and the host agent will be used to register the server’s HBAs to the
storage system.
Prior to version 6.22.20 of the server utility, you could not install the
host agent and server utility on the same server. However, you could
install them on different servers that are connected to the same storage
system.
Table 1 describes the differences between the host agent and the server
utility on a server attached to a storage system.
Depending on the version of the server utility, some of the features listed in
Table 1 may not be available.
Table 1 Differences between the host agent and the server utility
Function Host agent Server utility

Pushes LUN mapping Yes – LUN mapping information is CX4 series, CX3 series, and CX series storage systems
and OS information to the displayed in the Manager UI next to No – LUN mapping information is not sent to the storage system. Only
storage system. the LUN icon or with the CLI using the server’s name, ID, and IP address are sent to the storage system.
the lunmapinfo command. Note: The text Manually Registered appears next to the
hostname icon in the Manager UI indicating that the host agent was
not used to register this server.
Runs automatically to Yes – No user interaction is CX4 series, CX3 series, and CX series storage systems
send information to the required. No – You must manually update the information by starting the utility
storage system. or you can create a script to run the utility. Since you run the server
utility on demand, you have more control as to how often or when the
utility is executed.
Provides high-availability No – You can run the server utility’s CX4 series, CX3 series, and CX series storage systems
(HA) validation. HA validation feature from the CD Yes – The HA validation feature verifies that failover software is
without having to install the server installed on the server and that working paths exist between the
utility. server and each SP in the storage system.

19
Function Host agent Server utility
Requires network Yes – Network connectivity allows CX4 series, CX3 series, and CX series storage systems
connectivity to the storage LUN mapping information to be No – LUN mapping information is not sent to the storage system.
system. available to the storage system. Note that if you are using the server utility to upload a high-availability
report to the storage system, you must have network connectivity.
Requires installation. Yes – You must install the host CX4 series, CX3 series, and CX series storage systems
agent on the server. No – You can run the server utility from the CD. However, we
recommend that you install it on the server.
Note: If you install the host agent and then version 6.22.20 or later of the server utility, the server utility’s registration service feature will
not be installed. Prior to version 6.22.20 of the server utility, you could not install the host agent and server utility on the same server.
Requirements for CLARiiON server software

To run CLARiiON server software, your server must meet the following
requirements:
Run a supported version of the Solaris operating system.
Be a Sun SPARCserver, SPARCstation, or Enterprise server running
a supported version of a Solaris operating system. For the latest
requirements see the software product release notes.
For Fibre Channel connections, have the EMC CLARiiON
supported HBA hardware and driver installed.
Be connected to at least one SP (two SPs for high availability) in
each storage system either directly or through a switch or hub. Each
SP must have an IP connection.
For the host agent and CLI only - Be on a TCP/IP network connected
to at least one SP (two SPs for high availability) in the storage
system. The TCP/IP network connection allows the server to send
LUN mapping information to the storage system and it allows
Navisphere Manager or the CLI to communicate with the storage
system over the network.
Have a configured TCP/IP network connection to any remote hosts
that you will use to manage the server’s storage systems, including:
z any server whose browser you will use to access Manager 6.X,
z a supported Windows server running Storage Management
Server software,
z any AIX, HP-UX, Linux, VMware ESX Server, NetWare, Solaris,
or Windows server running the CLI.
20
If you want to use the CLI on the server to manage storage systems on
a remote server, the server must be on a TCP/IP network connected
to both the remote server and each SP in the remote server’s storage
system. The remote server can be running AIX, HP-UX, Linux, Solaris,
or the Windows operating system.
For information about the specific revisions of the server operating system
and the storage-system FLARE and Access Logix™ software that are required
for your version of the host agent, see the release notes for the host agent on
the EMC Powerlink website.
Power-cycling the storage system
Do not issue verify_disk_array while the SP is powering up. You must wait
until the SP has completed the powerup cycle.
Solaris does not generally support the powering down of a storage

device while the Solaris server is running. There are, however,
occasions when we recommend power-cycling a storage system as part
of service. When power-cycling a storage system, it is important to
observe the following guidelines:
If the system is booted from the storage system, the server must be
shut down before the storage system is powered down.
If the system does not boot from the storage system, it is still
important to unmount any file systems on the storage system before
power-cycling the storage system.
We recommend that you stop all I/O, including raw I/O, before
power-cycling the storage system. However, the system will not
panic if raw I/O occurs when the storage system is powered down.
If there is any attempt at I/O while the storage system is off or
while it is going through its boot sequence, the failover software
will attempt to fail over.
Installing the Navisphere Host Agent and/or CLI

You can install both the host agent and CLI, or you can install them
separately. If you will install both, install the host agent first.

21
If you want to install the host agent and use some of the features in the server
utility, see Determining whether to install the host agent or server utility , page 18.
Installing the host agent on a Solaris server

This section applies to version 6.26 or later of the Navisphere Host
Agent software package.
Download the most recent version of the host agent from the software
downloads page on the Powerlink website. If you are installing version
6.28 or earlier, you can install the software from the server support CD;
however, the CD may not contain the most recent version for your
configuration.
1. If you are installing the host agent, make sure that each storage
system is connected to the Solaris server where you are installing
the host agent.
2. At the Solaris server, log in as superuser (root).
3. If your server is behind a firewall, open TCP/IP port 6389. This
port is used by the host agent. If this port is not opened, the host
agent will not function properly.
4. To download the software, do the following:
a. From the Powerlink website, select Support > Software
Downloads and Licensing > Downloads J-O > Navisphere
Server Software.
b. Select the host agent version you want to download and select
the option to save the zip file to your server.
c. At the command line prompt, navigate to the directory where
you saved the zip file and unzip the file.
unzip Sun-NAVIAGNT-version.zip
where version is the version listed in the filename.

d. Depending on which version you are installing, enter one of the
following commands to install the software:
Version 6.29 or later:
22
Sun Solaris – pkgadd -d NaviHostAgent-Solaris-32-sparc-
en_US-version-build.pkg
Sun Opteron – pkgadd -d NaviHostAgent-Solaris-32-x64-
where version and build are the version number and the build
number of the software.
Version 6.28 or earlier:

pkgadd -d NAVIAGNT.pkg
5. If you are installing version 6.28 or earlier, you can install the
software from the server support CD; however, the CD may not
contain the most recent version for your configuration. To install
the software from the server support CD, do the following:
a. In the server’s drive, insert the server support CD that shipped
with your storage system.
b. In a shell, enter the following command to install the software:
cd /cdrom/cdrom0/solaris pkgadd -d /solaris/NAVIAGNT.pkg

6. Press Enter and y to begin the installation.
The installation program looks for any agent configuration files

you may already have on your system. If the program finds an
existing configuration files, it displays a message like the following:
At Least 1 saved config file exists for Navisphere

Agent.
Please select 1 of the following:
[1]
Restore/etc/Navisphere/.Naviagent-config.000120:105
9
[2]
8
[3] Quit
Select number 1 - 3.
7. If the program finds any existing configuration file, select the

existing file you want to serve as the agent configuration file. The
software will retain that file and rename it with the required agent
filename, agent.config. Generally, you will want to use the most

23
recent file, as shown by the numeric date suffix. To use the default
configuration file, specify the number for the Quit option.
When the installation of the host agent is complete, a successful

message is displayed.
8. If you installed the host agent from the server support CD, when
installation is complete, exit the /cdrom directory (for example,
execute cd /), and then remove the CD from the server’s CD drive.
Any user who can access the management station can change or delete the
Navisphere files you just installed. You may want to change permissions
on these files to restrict access to them.
9. Verify the installation by entering the command pkginfo -l | grep

NAVI*.
A message similar to the following may be displayed:

NAVIAGENT: Navisphere Disk Array Management Tool (Agent)
Installing the Navisphere CLI on a Solaris server

This section applies to version 6.26 or later of the Navisphere CLI
software package.
Download the most recent version of the Navisphere CLI from the
software downloads page on the Powerlink website. If you are
installing version 6.28 or earlier, you can install the software from the
server support CD; however, the CD may not contain the most recent
version for your configuration.
1. Log in as superuser (root).
2. If your server is behind a firewall, open the TCP/IP ports listed in
Table 2. These ports are used by Navisphere CLI. If these ports are
not opened, the software will not function properly.
Table 2 TCP/IP ports
Navisphere Software TCP/IP ports

Classic CLI 6390, 6391, 6392
Secure CLI 443, 2163
24
Server Software.
b. Select the Navisphere CLI version you want to download and
select the option to save the zip file to your server.
unzip Sun-NAVICLI-version.zip


Sun Solaris – pkgadd -d NaviCLI-Solaris-32-sparc-en_US-
version-build.pkg
Sun Opteron – pkgadd -d NaviCLI-Solaris-32-x64-en_US-
version-build.pkg
pkgadd -d NAVICLI.pkg
b. In a shell, enter the following command:
cd /cdrom/cdrom0/solaris pkgadd -d /solaris/NAVICLI.pkg

25
5. Select the packages that you want to install by doing one of the
following:
Enter 1 (to install classic CLI)
Enter 2 (to install secure CLI)
Enter All (to install both)
6. When the installation of the CLI is complete, a successful message
is displayed.
7. If you installed the CLI from the server support CD, when
installation is complete, exit the /cdrom directory by entering cd /,
and then remove the CD from the server’s CD drive.

NAVI*.
Depending on what you installed, one of the following may be

displayed:
NAVICLI: Navisphere Disk Array Management Tool (CLI)
NAVISCLI: Navisphere Disk Array Management Tool
(CLI)
Installing the host agent and/or Navisphere CLI on a Solaris server

This section applies to version 6.24 or earlier of the Navisphere Host
Agent/ CLI software package.
Download the most recent version of the host agent/CLI from the
1. If you are installing the host agent, make sure that each storage
system is connected to the Solaris server where you are installing
the host agent.
2. At the Solaris server, log in as superuser (root).
26
3. If your server is behind a firewall, open the TCP/IP ports listed in
Table 3. These ports are used by the host agent and CLI. If these
ports are not opened, the software will not function properly.
Table 3 TCP/IP ports
Navisphere Software TCP/IP ports

Host Agent 6389
Classic CLI 6390, 6391, 6392
Secure CLI 443, 2163
4. To download software for your storage system, do the following:

Server Software.
b. Select the host agent/CLI version you want to download and
unzip Sun-NAVIAGNT-version.zip

d. Enter the following command to install the host agent and/or
CLI package:
pkgadd -d NAVIAGNT.pkg
b. In a shell, enter the following command:
cd /cdrom/cdrom0/solaris pkgadd -d /solaris/NAVIAGNT.pkg

27
6. Select the packages that you want to install by doing one of the
following:
Enter 1 (to install the host agent)
Enter 2 (to install CLI)
Enter All (to install both the host agent and CLI)
7. Enter y and y to begin the installation.
The installation program looks for any agent configuration files

you may already have on your system. If the program does
not find any agent configuration files, then you have finished
installing the agent; go to step 10. If the program does find any
existing configuration files, it displays a message like the following:
At Least 1 saved config file exists for Navisphere

Agent.
Please select 1 of the following:
[1]
9
[2]
8
[3] Quit
Select number 1 - 3.
8. Select the existing file you want to serve as the agent configuration
file. The software will retain that file and rename it with the required
agent filename, agent.config. Generally, you will want to use the
most recent file, as shown by the numeric date suffix. To use the
default configuration file, specify the number for the Quit option.
9. When the installation of the host agent is complete, a successful
message is displayed. If you are also installing the CLI, enter y at
the CLI installation prompt as you did for the agent.
10. If you installed the host agent/CLI from the server support CD,
when installation is complete, exit the /cdrom directory by entering
cd /, and then remove the CD from the server’s CD drive.
28
NAVI*.
Depending on what you installed, some of the following may be

displayed:
NAVIAGENT: Navisphere Disk Array Management Tool
(Agent)
NAVICLI: Navisphere Disk Array Management Tool (CLI)
NAVISCLI: Navisphere Disk Array Management Tool (CLI)
What next?
Before you can use the host agent or CLI, you must modify the user
login scripts.
Modifying user login scripts

Use a text editor to modify login scripts as described below:
1. Use a text editor, such as vi, to make the following additions to the
specified paths in $HOME/.profile or $HOME/.cshrc:
add the text /opt/Navisphere/bin to PATH
add the text /opt/Navisphere/man to MANPATH
add the text /opt/Navisphere/lib to LD_LIBRARY_PATH
2. Run the $HOME/.profile or $HOME/.cshrc file and export each
path you modified.
3. View the paths using the echo command as follows:
# echo $PATH
# echo $MANPATH
# echo $LD_LIBRARY_PATH

29
What next?
If you are setting up a new server, go to Running the Navisphere Host
Agent , page 31. If you are just upgrading the host agent or CLI on an
existing system, you have finished the upgrade.
Configuring the Navisphere Host Agent

Before you can use the Navisphere CLI navicli register command to
configure your storage system, you must make sure the host agent
configuration file includes a privileged user, as described in Adding
privileged users, page 30.
The pathname of the host agent configuration file is /etc/Navisphere/agent.con-

fig.
If you are configuring a legacy storage system, refer to revision A09 of

this guide.
A legacy system is an FC series storage system that is not running storage

management server software.
Adding privileged users

If you will use Navisphere CLI to configure any storage system, the
host agent configuration file must include an entry that defines the
person who will issue the CLI commands as a privileged user.
To define a privileged user, add a local or remote privileged user by
adding the appropriate entry below.
For a local user:
user name
For a remote user:
user name@hostname
where name is the person’s account name and hostname is the name of
the remote server the person will be using.
The default host agent configuration file includes a user root entry.
30
Saving the host agent configuration file
1. Save the host agent configuration file.
2. If you have finished adding information to the host agent
configuration file, stop and restart the host agent by entering the
following commands:
#/etc/init.d/agent stop
#/etc/init.d/agent start
Using the event monitor configuration file

The Navisphere Host Agent can monitor storage-system events and
take such action as sending email or paging you if specified events
occur. The event monitor that ships with Navisphere Manager provides
an interactive way to define these events and actions. If you do not
have event monitor, you can still define such events and actions by
editing the event monitor configuration file.
/etc/Navisphere/Navimon.cfg
The file is self-documenting; that is, text in it describes how to define
events and the actions you want taken if the events occur. You can
test the file after editing it using the Navisphere CLI command
responsetest, as explained in the Navisphere Command Line Interface
Reference.
Running the Navisphere Host Agent

This section describes how to test the host agent connections and how
to start and stop the host agent.
Starting and stopping the Navisphere Host Agent

The host agent starts automatically when you bring the server up to
init level 3. When you first start the host agent, look at the system log
for the server’s operating system to make sure the agent started and no
device errors occurred. The system log is located in /var/log/messages.

31
When a storage system experiences heavy input/output traffic (that is,
applications are using the storage system), information may not be reported
to the host agent in a timely manner, resulting in the host agent taking several
minutes to execute a storage-system management task. This behavior is most
evident when one host agent is managing multiple storage systems. Also, if the
SP event log is large and the host agent configuration file is set up to read all
events, it may take a few minutes for the host agent to start.
Starting the host agent

Log in as root and enter this command:
/etc/init.d/agent start
Stopping the host agent

Testing the host agent connections

Before continuing, you should test the host agent connections as
follows:
1. Start the host agent as described in Starting and stopping the
Navisphere Host Agent, page 31.
2. Look for any errors on the console and in the operating system log
to make sure the agent started and no device errors occurred.
3. Verify that the host agent on the server can see the storage system
as follows:
a. Enter the following CLI command:
naviseccli |navicli [-d device]| -h hostname port
-list -hba
You cannot specify both the –d switch and –h switch.
where:
32
[-d device] is the device name for the storage system (only
supported with legacy systems).
-h hostname is the IP address of the SP.
For each HBA in the server, a listing similar to the following will
be displayed. For storage systems in a SAN (shared storage)
environment, the listing includes HBAs in all connected hosts.
Information about each HBA:
HBA UID: 10:00:00:60:B0:3E:46:AC:10:00:00:60:B0:3E:46:AC
Server Name: siux134
Server IP Address: 128.221.208.134
HBA Model Description:
HBA Vendor Description:
HBA Device Driver Name:
Information about each port of this HBA:
SP Name: spa
HBA Devicename: sp0
Trusted: NO
Logged In: YES
Source ID: 1
Defined: YES
Initiator Type: 0
Storage Group Name:
Storage Group 134
b. In the listing, examine the information for each HBA installed in

the host to verify the path from the HBA to the SP.
Host agent status and error logging

While the system is running, the operating system tracks information
about host agent events and host agent errors, and places this
information in log files on the server.
The host agent error log tracks information about the host agent’s
startup, the host agent shutdown, and errors that might occur, such as
the host agent’s inability to access a device in the configuration file. If
problems occur, log files are a good place to start your troubleshooting.
Host agent events and errors are logged in /var/adm/messages.

33
Informational messages about host agent events are recorded in
/var/adm/log/agent.log.
Installing the Navisphere Server Utility

This section describes how to install the Navisphere Server Utility.
Installing the Navisphere Server Utility on a Solaris server

Download the most recent version of the server utility from the
1. Log in to the server as superuser (root).
Server Software.
b. Select the Navisphere Server Utility version you want to
download and select the option to save the zip file to your server.
unzip Sun_HOSTUTIL-version.zip


Sun Solaris – pkgadd -d NaviServerUtil-Solaris-32-sparc-
Sun Opteron – pkgadd -d NaviServerUtil-Solaris-32-x64-
34
pkgadd -d HOSTUTIL.pkg
a. In the server’s drive, insert the server support CD, which
shipped with the storage system.
b. From a console window, mount the CD:
mount /mnt/cdrom
c. Start the installation program:
cd /cdrom/cdrom0
pkgadd -d HOSTUTIL.pkg
4. At the prompt to select the packages to process, enter 1 to select
HOSTUTIL.
5. At the prompt about scripts that execute with superuser permission
during the installation, enter y.
The screen displays information about the installation.

6. When installation is complete, exit the /cdrom directory by entering
cd /.
7. If you installed the server utility from the CD, remove the CD from
the server’s CD drive.
Installing the Admsnap Utility

To access snapshots of LUNs in the storage system, install the Admsnap
Utility.

35
Installation prerequisites
Before you can install and use the Admsnap Utility, you must:
Install SnapView on a supported CLARiiON storage system. For
a list of supported storage systems, refer to the release notes for
SnapView and admsnap.
Enable data access control on the same CLARiiON storage system.
Installing the Admsnap Utility on a Solaris server

Download the most recent version of the admsnap utility from the
1. Log in as a superuser, such as root.
Downloads and Licensing > Downloads S > SnapView.
b. Select the Admsnap Utility version you want to download and
unzip admsnap_version.zip

d. Depending on which version you are installing, load the
appropriate admsnap package:

Sun Solaris – ADMSNAP-Solaris-32-sparc-en_US-version-
build.pkg
Sun Opteron – ADMSNAP-Solaris-32-i386-en_US-version-
build.pkg
36
/usr/sbin/pkgadd -d ADMSNAP.pkg
3. If you are installing admsnap version 6.28 or earlier, you can install
it from the server support CD; however, the CD may not contain the
most recent version for your configuration. To install the software
from the server support CD, do the following:
The CD is mounted automatically on /cdrom/admsnap, which

is linked to /cdrom/cdrom0.
If the CD does not mount automatically, then mount the CD

using the mount/dev/cdrom command.
The File Manager Admsnap window appears with

ADMSNAP.pkg displayed.
b. Load admsnap from the CD:
/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.X
Select package(s)...to process (or "all" to process all
packages). (default: all) [?, ??, q]:
4. When prompted, enter y to install the admsnap package and y
again to continue the installation.
The installation script runs, listing the files installed, and on

completion, displays the message: Installation of <ADMSNAP>
was successful.
5. Use the pkginfo command to verify the installation. Enter
/usr/sbin/pkginfo-1 ADMSNAP.
Messages similar to the following appear:

37
PKGINST: ADMSNAP
NAME ...
CATEGORY: application
VERSION X.X.X.X.X
PSTAMP: Navisphere: 2000:10:28:13:03:01
INSTDATE: November 20 2000 13:03
STATUS: Completely installed
FILES: xxxxxxx
xxxxxxxx xxxxxx
When you see the error-free pkginfo message, admsnap software

installation is complete. The software is installed in the directory
/usr/admsnap.
6. Unmount the CD by entering the unmount/dev/cdrom command.
7. Remove the CD from its drive.
Running the Admsnap Utility

Refer to the EMC SnapView Command Line Interfaces Reference for
information on running admsnap commands.
38
Disabling Sun StorEdge Traffic Manager to use PowerPath
If you are using PowerPath failover software, you must disable Sun
StorEdge Traffic Manager (MPxIO) as follows for your Solaris version.
Uncomment the following line in the /kernel/drv/iscsi.conf file:
mpxio-disable="yes"
In addition, if the following line appears in the iscsi.conf file:
mpxio-disable="no"
you must add the comment (#) as shown here:

matrix 5.10 (64 bit): more /kernel/drv/iscsi.conf
#
# CDDL HEADER START
.
.
.
# Global mpxio-disable property:
#
# To globally enable MPxIO on all iscsi ports set:
# mpxio-disable="no";
#
# To globally disable MPxIO on all iscsi ports set:
mpxio-disable="yes";
#
matrix 5.10 (64 bit):

39
Connecting the storage system to the server in a Fibre Channel
switch configuration
Use optical cables to connect switch ports to the storage-system Fibre
Channel front-end data ports and to Fibre Channel switch ports and to
connect 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. We strongly recommend you use OM3 50 μm
cables for all optical connections.
Specifications for the optical cables that connect the switch to the
storage system are in the storage system’s technical specifications in the
documentation section of Powerlink.
Identifying storage-system Fibre Channel front-end ports

The number and location of the SP Fibre Channel front-end ports for
the storage system depend on the UltraFlex™ Fibre Channel I/O
modules installed in the I/O module slots (Figure 1):
A0 through A5 for SP A
B0 through B5 for SP B
SP A and SP B must have the same type of I/O module in the same slots.
40
0 1 2 3
B0 B1 B2 B3
0 1 2 3
A0 A1 A2 A3
B4 B5 A4 A5
CL4126
Figure 1 I/O module slots (only standard I/O modules shown)
Standard Fibre Channel I/O modules with Fibre FE ports

Your storage system has two 4 or 8 Gb Fibre Channel I/O modules
per SP each with two Fibre back-end (BE) ports (0, 1) and two Fibre
FE ports (2, 3). These modules are either all 4 Gb modules or all 8 Gb
modules. One of these modules is always in slots A0 on SP A and in
slot B0 in SP B. The other modules can be in any available slot, unless
the storage system has the expansion option and is running a FLARE
OE version earlier than 04.28.000.5.5xx, in which case, they cannot be
in slots A5 and B5.
The 8 Gb modules require FLARE OE version 04.28.000.5.7xx or later.
Optional Fibre Channel I/O modules with Fibre FE ports

Your storage system may have the following optional Fibre Channel
I/O modules with Fibre FE ports:
For a base system without the expansion option – One or two
optional 4 or 8 Gb Fibre Channel I/O modules per SP each with
four Fibre FE ports (0, 1, 2, 3) in any available slots.
For a base system with the expansion option and running FLARE
OE version 04.28.000.5.5xx or later – One or two optional 4 or 8 Gb
Fibre Channel I/O modules per SP each with four Fibre FE ports
(0, 1, 2, 3) in any available slots.
For a base system with the expansion option and running a
FLARE OE version earlier than 04.28.000.5.5xx – One optional 4 Gb
Fibre Channel I/O module per SP each with four Fibre FE ports (0,
1, 2, 3) in any available slots except slots A5 and B5.

41
The 8 Gb modules require FLARE OE version 04.28.000.5.7xx or later.
Module labels and FE port connectors

Each Fibre Channel I/O module has a 4 GB Fibre or 8 GB Fibre
label on its handle and an optical small-form factor pluggable (SFP)
transceiver module in each of its Fibre FE ports.
FE port connectivity
The Fibre FE ports on a 4 Gb/s Fibre Channel I/O module supports
1/2/4 GB/s connectivity, and the Fibre FE ports on an 8 Gb/s Fibre
Channel I/O module supports 2/4/8 Gb/s connectivity. You cannot
use the FE ports on an 8 Gb/s Fibre Channel I/O module in a 1 Gb/s
Fibre Channel environment. You can use the FE ports on a 4 Gb/s Fibre
Channel I/O module in an 8 Gb/s FC environment if the FC switch
ports to which the module’s FE ports connect auto-adjust their speed
to 4 Gb/s.
Cabling the Fibre Channel front-end data ports to the switch ports
For highest availability, connect one or more Fibre Channel front-end
data ports on SP A to ports on the switch and connect the same number
of Fibre Channel front-end data ports on SP B to ports on same switch
or 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 1–3 and
5–15. 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 system
that you will use for I/O with the server:
1. Locate the FC front-end data port to which you will connect the
switch port.
For information on identifying the front-end ports using Navisphere

Manager, refer to the Navisphere Manager help.
42
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.
2. Remove the protective cover from the FC front-end data port

connector on the SP and from one end of the optical cable, and plug
the cable into the data port connector (Figure 2 and Figure 3).
3. Remove the protective cover from the optical connector on the
switch port that you will use and from the free end of the optical
cable, and plug the cable into the switch port (Figure 2 and Figure 3).
CL4021
Figure 2 Connecting an optical cable

43
! !
CL4186 CL4186
Figure 3 Sample cabling between a storage system and two switches
Cabling the switch ports to the server HBA ports

For the highest availability in a multiple-HBA server, connect one or
more HBA ports to ports on the switch and connect the same number
of HBA ports to ports on the same switch or on another switch, if two
switches are available.
For each server HBA port that you will use for I/O with the storage
system:
1. Remove the protective cover from the FC switch port connector
and from one end of the optical cable, and plug the cable into the
connector.
2. Remove the protective cover from the server HBA port connector
and from the free end of the optical cable, and plug the cable into
the HBA port connector (Figure 4).
44
! !
CL4044
Figure 4 Sample cabling for a Fibre Channel switch configuration
Zoning the switches

You must use switch management software to update switch software
and zone switches that are not hard zoned.
1. Connect the switch management ports to the network from which
you will manage the switches.
2. If the switches are not running the most recent supported firmware
version, install this software from the switch vendor’s website.
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.

45
4. Using the instructions provided with the CD, run the zoning wizard
and select the zone configuration that is applicable to the way that
you connected the storage-system Fibre ports and the server HBA
ports to the switch.
46
Registering server with the storage system
You must run the Navisphere Server Utility or Navisphere Host Agent
on each server connected to the storage system to register the server’s
HBAs with the storage system.
Running the Navisphere Server Utility on a Solaris server

You can run the Navisphere Server Utility for Solaris from the server, if
you installed the utility on the server, or from the server support CD,
which shipped with the storage system.


./naviserverutilcli
Registering the server using the Navisphere Server Utility

1. If the host agent is running, stop the host agent service.
2. In the server utility, enter 1 to select Update Server Information.
The utility automatically scans for connected storage systems, and

displays a list of the ones it finds.

47
3. In the server utility, enter u to register the server with each storage
system the utility found.
The utility sends the server’s name and IP address to each storage
system. Once the server has storage on the storage system, the
utility also sends the Solairs device name and volume or file system
information for each LUN (virtual disk) in the storage system that
the server sees.
4. Enter c (cancel) to stop the utility.
5. If you stopped the host agent, restart it.
Setting the Navisphere Server Utility to restart on Solaris reboot

Set the utility to restart automatically each time the Solaris server
reboots by using a text editor to modify login scripts as follows:
1. If you are running Common Desktop Environment, remove the
comment from the last line in $HOME/.dtprofile.
The line should readDTSOURCEPROFILE=true.

2. Make the following addition to PATH in $HOME/.profile or
$HOME/.cshrc, and export the path:
/opt/Navisphere/bin
Starting the Navisphere Host Agent

Starting the host agent on a server automatically registers the server’s
HBAs with the storage system.

Verifying HBA registration with Navisphere Manager

1. From the Navisphere Manager Storage tree, right-click the icon for
the storage system for which you want to verify HBA registration,
and click Connectivity Status.
48
The Connectivity Status dialog box opens.
2. Verify that the server to SP port connection is displayed as Yes
under the Registered columns.
If not, refer to the “Troubleshooting Flowcharts” section on the

CLARiiON Tools page on the Powerlink website.
To access the CLARiiON Tools page, use the Navigator drop-down menu
at the top right of the Powerlink home page.
Once all HBAs belonging to a server are registered, you can assign
the server to storage groups.

49
Verifying storage-system health
Use the storage system verification wizard that is part of the Navisphere
Service Taskbar to:
Validate the connectivity of the storage-system hardware
components
Check back-end functionality
Check the status of all field-replaceable units
Analyze storage-system logs
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-system’s management ports. If you do not have a Windows
management station, your service provider can 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 the
CLARiiON Tools page on the Powerlink website to a Windows
management station that is connected to the storage-system’s
management 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 the

following:
Click the Navisphere Service Taskbar icon on your desktop,
or
Select Start > Programs > EMC > Navisphere > Navisphere
Service Taskbar version > Navisphere Service Taskbar
version
2. In the taskbar’s navigation pane, select the Hardware Maintenance
tab.
50
3. In the tab’s 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 troubleshooting

flowcharts for the storage system on the CLARiiON Tools page of
the Powerlink website.

51
Setting storage-system failover values for the server initiators
Use the Navisphere Manager Failover Setup wizard to set the
storage-system failover values for all HBA initiators belonging to the
server:
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 to
the 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 the
type of software running on the server.
IMPORTANT
If you enter incorrect values the storage system could become
unmanageable and unreachable by the server, and the server’s
failover software could stop operating correctly.
Solaris 9 or 10
For 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 support
ALUA.
For information on which versions of failover support ALUA for

CLARiiON storage systems, refer to the PowerPath release notes on the
Powerlink website.
Solaris 8, 7, or 2.6
For a Solaris 8, 7, or 2.6 server, set:
52
Failover Mode to 4 if your failover version supports ALUA.
Failover Mode to 1 if your failover version does not support
ALUA.
For information on which versions of failover support ALUA for

CLARiiON storage systems, refer to the PowerPath 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 packages

or with VRTSvcs without I/O fencing, set:
Unit Serial Number to Array
7. In Configuration Summary, review the configuration and all
settings.
8. If the settings are correct, click Next, and if the settings are incorrect,
click Back until you return to the dialog box in which you need 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.
10. If the operation failed, rerun the Failover Setup Wizard again.
11. When the operation is successful, click Finish to close the wizard.

53
Verifying your high-availability Fibre Channel configuration
Use the server high-availability feature in the Navisphere Server
Utility to verify the following for each server in a high-availability
configuration with the storage system:
Your Fibre Channel configuration is highly available (that is, each
Fibre Channel HBA has at least one active path to each storage
processor).
Path management software is installed and running on the server.


./naviserverutilcli
Using the server utility to verify your high-availability configuration

1. In the Navisphere Server Utility select option 3 from the server
utility’s Welcome screen to generate a report of the server’s
environment.
54
The utility determines if the server is configured for high availability
by verifying that the server has at least one connection path to
each storage system SP, and that PowerPath or some other failover
software, such as DMP, is running. It does not detect native failover
software, such as, Sun StorEdge Traffic Manager.
2. Review and resolve any issues reported under the Issues tab of the
generated report before continuing with the installation process.

55
Installing CLARalert software
CLARalert® software monitors your storage system’s operation for
error events and automatically notifies your service provider of any
error events. CLARalert is available from the CLARiiON Tools page on
the Powerlink website. If the CLARiiON Tools page does not contain
a CLARalert link, it is not supported for your system or your service
provider can install the CLARalert software.
CLARalert uses a centralized monitoring environment. In a centralized

monitoring environment you designate a monitor station to monitor
the events of storage systems you specify. The centralized monitoring
environment is a monitoring environment option for Navisphere Event
Monitor, which is a feature of the Navisphere Manager application.
During the CLARalert installation, you designate the monitor station
and portal system where you want to configure your centralized
monitoring environment. The storage system that you designate as a
portal system during CLARalert installation is automatically added
to the list of monitored storage systems. You can later add storage
systems to your centralized monitoring environment using Navisphere
Manager. For more information, see the Navisphere Manager help,
which is in the Navisphere Manager UI or the Powerlink website. The
version on Powerlink is the most up to date.
56
For a new CLARalert installation, the wizard automatically installs the email
notification service, which sends event notification to your service provider
with email (SMTP). CLARalert integrates with WebEx, allowing you to initiate
real-time customer support sessions over the web. See the WebEx EMC Support
Center at https://emcsupport.webex.com for more information on WebEx.
CLARalert requirements
CLARalert installation and operation requires that TCP ports 80, 443, 25 (SMTP
server) are open. Refer to the EMC CLARalert Release Notes for the most current
CLARalert environment and system requirements.
The CLARalert version must be at or later than the version of FLARE®

Operating Environment (OE) running on each storage system being
monitored. CLARalert installation requires:
❑ A monitor station, which is a host running a supported Windows
operating system. For supported versions, refer to the EMC
CLARalert Release Notes. The monitor station cannot be a server
(host connected to storage-system data ports), and it must be on the
same network as your storage-system management ports.
CLARalert is installed on and runs on the monitor station. The
monitor station must have a static or DHCP reserved IP address.
The wizard automatically detects and supplies the IP address for
the monitor station, which is required for CLARalert installation.
You can verify the IP address in the wizard and, if required, enter
or select a different one.
❑ A portal system, which is a storage system running the required
FLARE Operating Environment (OE ) version. For required
versions, refer to the EMC CLARalert Release Notes.
You must provide the IP address for either SP of the portal system
during CLARalert installation. You must also supply global
administrator login credentials for the portal system during
installation.

57
If your CLARalert installation will use email notification, for example, for a
new installation, you will need connectivity to an outgoing SMTP server. You
must provide the IP address for the SMTP server during CLARalert installation.
You must also provide your service provider email address (to) and your local
email address (from) for email notification.
If you do not have an existing monitor station — You can create a

monitor station by installing CLARalert on a Windows host.
If you have an existing monitor station running CLARalert — You

can upgrade CLARalert on the monitor station. When you perform an
upgrade, the wizard asks if you want to preserve your existing email
configuration or if you want to reconfigure it.
If you have an existing monitor station running event monitor — You
can install CLARalert on the monitor station.
Downloading and installing CLARalert software

From the monitor station:
1. On the Powerlink website, select the Search Powerlink tab.
2. Replace the “Search Powerlink” text with “claralert” and in Filter
by content type, select Support: Downloads and click Search.
3. In the results page, select Download CLARalert and save the
software to your monitor station.
4. In the folder where you saved CLARalert, double-click the
NaviClarAlert executable (.exe) file or if necessary, right-click the
file and select Run as to run the installation wizard using a different
user’s credentials.
5. Follow the steps in the wizard, using the information from the
completed CLARalert Worksheet in the planning guide for your
storage system.
You can generate the latest version of the storage-system planning

guide from the CLARiiON Tools page on the Powerlink website.
58
Configuring a new storage system
A new storage system is one that was not already connected to a server
when you started the installation procedure.
To configure a storage system, use either the Navisphere taskbar
wizards or the Storage tree options of Navisphere Manager.
Before you start

You will need the completed LUN worksheets from the storage-system
configuration planning guide or the planning worksheets document.
You can generate an up-to-date version of this planning guide using
the user-customized documentation link from the CLARiiON Tools
page on the Powerlink website or view it on the documentation and
resources CD, which shipped with the storage system.
Starting Navisphere Manager
To manage a CX4 storage system running FLARE OE version 04.28.000.5.5xx or

later, 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 a

network to the storage system’s management ports and that has an
Internet browser: Microsoft Internet Explorer, Netscape, or Mozilla.
2. Start the browser.
3. In the browser window, enter the IP address of one of the following
that is in the same domain as the storage systems that you want
to manage:
A storage-system SP with the most recent version of the FLARE
Operating Environment (OE) installed

59
This SP can be in one of the storage systems that you want to manage.
A Navisphere off-array management station with the most

recent 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 Powerlink website.
4. Enter the username and password for the account you want to use,
and leave the scope unchanged (set to global).
5. If you are prompted to add the storage system to a domain, add
it now.
The first time that you log in to a storage system, you are prompted
to add the storage system to a Navisphere domain. If the storage
system is the first one, create a domain for it. If you already
have storage systems in a domain, you can either add the new
storage system to the existing domain or create a new domain for
it. For details on adding the storage system to a domain, use the
Navisphere Manager help.
The Navisphere Manager main window opens with a navigation pane
on the left that contains the Navisphere taskbar and an Enterprise
Storage window on the right. The Navisphere taskbar consists of
the following tabs: Storage Management, Monitoring, Replication,
Reporting, Service. When you select a tab, it displays one or more icons
for starting the wizards. The Enterprise Storage window contains tabs
for the following trees:
Storage tree – Displays a storage-system icon for every storage
system in this domain.
Hosts tree – Displays a host icon for each server connected to any
storage system in this domain.
Monitors tree – Displays a monitor icon for:
60
z Every monitored storage system in the domain.
z Storage systems that do not belong to the domain, but are
physically connected to a storage system that does belong. An
example is a SAN Copy destination storage system.
The Navisphere Manager user interface (UI) version 6.28.10 introduces

the following new storage concepts – storage pool, traditional LUN,
thin pool, and thin LUN – to support the Virtual Provisioning feature.
For more information on these concepts, refer to the Navisphere
Manager Help.
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.
Configuring the storage-system cache

1. In the Navisphere Manager storage tree, right-click the storage
system and select Properties.
2. Click the Memory tab.
3. Set the write cache memory size.
Generally, for a storage system with the maximum cache memory,

we recommend that the write cache should be 10764 MB per SP,
which is the maximum allowed size.
4. Set the read cache memory size.
5. Click Apply.
6. Click the Cache tab, and select SP A Read Cache, SP B Read Cache,
Write Cache, and Enable Watermarks.
7. Set the low watermark to 60% and the high watermark to 80%.

61
8. Click Apply.
Enabling storage groups or access control
Starting with Navisphere Manager 6.29, the term ’Access Logix" has been
replaced with "Storage Groups” and the Storage Access tab has been removed
from the storage-system Properties page.
If you want to connect multiple servers to the storage system, you must
either enable storage groups using Navisphere Manager 6.29 or later or
enable access control using Navisphere Manager 6.28 or earlier:
To enable storage groups using Navisphere Manager 6.29 or later)
1. In the Navisphere Manager Storage tree, right-click the icon for the
storage system, and click Properties.
2. Click the General tab, and select Storage Groups.
To enable access control using Navisphere Manager 6.48 or earlier
1. In the Navisphere Manager Storage tree, right-click the icon for the
storage system, and click Properties.
2. Click the Storage Access tab, and under Data Access, select Access
Control Enabled.
Allocating storage on a new storage system with the Provision or Allocate wizard
Starting with UI version 6.28.10.xx, the Allocate wizard has been
renamed to Provision wizard. Like the Allocate wizard, use the
Provision wizard, found in the Navisphere Manager taskbar, to create
storage-system storage and provide server access to this storage.
To provision storage:
1. In the Navisphere taskbar, click the Storage Management tab and
then open the Provision or Allocate wizard.
2. Select the server that will have access to the new LUNs.
3. Select the storage system in which the new LUNs will reside.
4. Create hot spares on a RAID group.
Thin pools do not support the Hot Spare RAID type.
62
A hot spare is a single global spare disk that serves as a temporary
replacement for any failed disk in the storage system. The storage
system automatically reconstructs data from the failed disk onto
the hot spare, so the data is always available. Do not use an FSSD
disk as a hot spare, and do not use a SATA disk as a spare for a
Fibre-Channel-based LUN, nor a Fibre Channel disk as a spare for
an SATA-based LUN.
a. From the Provision wizard, select the Traditional option in the
Select LUN Type page or, if you are running an older version of
the Provision wizard (Allocate wizard), click New RAID Group
in the Select RAID Group page.
b. Create a new RAID group with the Hot Spare RAID type.
c. Let the software select the disk for the RAID group (Automatic),
or select Manual to choose the disk yourself.
The software creates the Hot Spare RAID type with one LUN.
Click Help in the dialog box for more details.

5. Create traditional LUNs on a RAID group:
a. Create a new RAID group with the appropriate RAID type
(individual disk, RAID 0, RAID 1, RAID 1/0, RAID 3, RAID 5,
or RAID 6) for each type of LUN you want to create.
b. Let the software select the disks for the RAID group (Automatic)
or select Manual to choose the disks yourself.
The software creates the specified RAID group.

c. Select the number of LUNs and set the properties for the LUNs
that will reside in the new RAID group.
d. Add the LUNs to a user-defined folder or do not place them
in a folder.

6. Create thin LUNs on a thin pool storage pool.

63
To create thin pools and thin LUNs, the storage system must be running
FLARE version 04.28.000.5.5xx or later and the Virtual Provisioning enabler
must be installed on the storage system. You must use version 6.28.10.xx
or later of the Navisphere Manager UI to create thin pools and thin LUNs.
For more information about Virtual (Thin) Provisioning, refer to the
Navisphere Manager online help and the Provision wizard help.
To create thin LUNs:

a. Select the Thin option in the Select LUN Type page of the
wizard.
b. Create a new thin pool storage pool with the appropriate RAID
type (RAID 5 or RAID 6) for each type of thin LUN you need to
create.
c. Let the software select the disks for the thin pool (Automatic) or
select Manual to choose the disks yourself.
The software creates the specified thin pool.

d. Select the number of thin LUNs and set the properties for the
LUNs that will reside in the new thin pool.
e. Either add the thin LUNs to a user-defined folder or do not
place them in a folder.

7. Verify that the server was assigned to the storage group containing
the LUNs you created.
If you know the name of the storage group in which the LUNs
reside — In the Navisphere Manager Storage tree:
Click the icon for the storage system with the storage group
whose 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 that
server appears under the storage group icon.
64
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 storage
group 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 not
have selected the Assign LUNs to a server option in the Select
Servers page of the Provision wizard. You can use the Assign
wizard to assign the LUNs to a server.
Allocating storage on a new storage system with the Navisphere storage tree options
1. Locate your completed LUN worksheets so you can refer to them
in the steps that follow.
2. Create one or more hot spares on a RAID group.
A hot spare is a single global spare disk that serves as a temporary

replacement for any failed disk in the storage system. The storage
system automatically reconstructs data from the failed disk onto
the hot spare, so the data is always available. Do not use an SSD
disk as a hot spare, and do not use a SATA disk as a spare for a
Fibre-Channel based LUN, nor a Fibre Channel disk as a spare for
an SATA-based LUN.
From the Navisphere Manager Storage tree, depending on the UI

that you are using, right-click the storage-system icon and do one of
the following:
Click Storage Pools Operations > Storage Pools and, if visible
in the Create Storage Pool dialog box, select Raid Groups.
Create a hot spare RAID group with one LUN.
Click Bind LUN; create a Hot Spare RAID group and bind one
LUN on the RAID group.
For details on creating Hot Spares, use the Navisphere Manager

help.
3. Create traditional LUNs on RAID groups:

65
From the Navisphere Manager Storage tree, depending on the UI
that you are using, right-click the storage-system icon and do one of
the following:
Click Storage Pools Operations > Create LUNs ; create a new
RAID group or select an existing one; create new LUNs on the
RAID group.
Click Bind LUN; create a new RAID group or select an existing
one; bind LUNs on the RAID group
For details on creating traditional LUNs and RAID groups, use

the Navisphere Manager help.
4. Create thin LUNs on thin pools:
From the Navisphere Manager Storage tree, right-click the

storage-system icon and click Storage Pool Operations > Storage
Pools and in theCreate Storage Pool dialog box, select Thin Pools.
For details on creating thin LUNs and thin pools, use the
Navisphere Manager help.
5. Create one or more storage groups:
From the Navisphere Manager Storage tree, right-click the icon for
the storage system, and click Create Storage Groups. For details on
creating storage groups, use the Navisphere Manager help.
6. Add LUNs (traditional LUNs and thin LUNs) to the storage group.
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.
From the Navisphere Manager Storage tree, right-click the icon

for the storage group to which you want to add LUNs, and click
Select LUNs. For details on adding LUNs to storage groups, use
the Navisphere Manager help.
7. Assign a server to a storage group:
66
To send data to or receive data from the LUNs, you must assign servers
to the storage groups.
From the Navisphere Manager Storage tree, right-click the icon for
the storage group to which you want to connect a server, and then
click Connect Hosts. For details on connecting servers to storage
groups, use the Navisphere Manager help.
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.
8. Verify that the server was assigned to the storage group.
From the Navisphere Manager Storage tree:

Click the icon for the storage system with the storage group
whose server connection you want to verify.
Click the Storage Groups icon.
Click the icon for the storage group.
If the server is assigned to the storage group, an icon for that
server appears under the storage group icon.
Configuring event notification on a new storage system using Navisphere Manager

Event monitor supports monitoring of storage-system events in a
heterogeneous environment. Once configured, event monitor runs
continuously as a service or daemon, observing the state of all specified
storage systems and notifying you when selected events have occurred.
The event monitor user interface (UI) is part of Navisphere Manager
and runs on a web browser.
Event monitor supports centralized or distributed monitoring of
storage systems. With centralized monitoring, a monitoring host agent
monitors storage systems from a central location. With distributed

67
monitoring, SP agents monitor only the storage system in which they
reside, or host agents monitor all attached storage systems. All AX4-5
series, AX series, CX4 series, CX3 series, and CX series storage systems
have resident SP agents.
FLARE OE includes the SP agent.
For both configurations, the monitoring agent notifies the client of

events that occur on the monitored storage systems.
To use centralized monitoring, you must use either the Navisphere
taskbar Monitor wizard or the Monitor tree options of Navisphere
Manager to:
Have a host that is not managing any storage system and that
has the host agent installed on it. This host agent becomes the
centralized monitoring agent.
Define a portal.
Add monitored agents to the centralized monitoring configuration.
Create and apply templates to the monitoring agent.
To configure event monitor for the storage system using the

Monitor wizard
In the Navisphere taskbar, click the Monitoring tab, and use the
Configure Monitoring wizard under this tab to configure centralized
or distributed monitoring. For details on how to configure monitoring
and how to configure the storage system to send event notification,
use the Navisphere Manager help.
To configure event monitor for the storage system with the
Navisphere Monitor tree
In the Navisphere Manager Enterprise Storage window, click the
Monitors tab and configure centralized or distributed monitoring. For
details on configuring monitoring and configuring the storage system
to send event notification, use the Navisphere Manager help.
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 process
varies with the size of the LUN and other parameters. While a LUN is
68
initializing, it is in a transitioning state, and when the initialization is
complete, its state becomes normal.
To determine the state of a LUN:
1. From 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.
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 PowerPath for Solaris sees all the paths to the LUNs
1. Rescan for disks (LUNs).
2. On the server, configure PowerPath:
powermt config
3. View the LUNs available to the server with the PowerPath
command:
powermt display dev=all class=clariion

4. Using the output from the command above, verify that none of the
paths to the storage system are dead.

69
Preparing LUNs to receive data
If you do not want to use a LUN as a raw disk or raw volume, then
before Solaris can send data to a LUN, you must partition the LUN and
then create and mount a file system on it. For information on how to
perform these tasks, refer to your operating system documentation.
For information on how to perform these tasks, refer to your operating
system documentation.
70
Sending Solaris disk information to the storage system
If the Navisphere Host Agent is installed on the server, stop and then
restart it to send the storage system the operating system’s device
name and volume or file system information for each LUN that the
server sees. Navisphere Manager displays this information 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, so this procedure is not required.
Stopping the host agent


Verifying that the storage system received the LUN information using Navisphere
Manager
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 LUN
you want to verify.
b. Right-click the icon for the LUN, and click Properties.
3. Verify that the Properties page displays a physical device and
logical device name for the LUN.

71
Verifying your failover configuration with PowerPath
Before you store data on LUNs, 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/
PowerPath shows the paths from the server to the LUNs that you
expect for your configuration.
Verifying your failover configuration

1. For each HBA connected to the storage system:
a. View the LUNs available to the server:
powermt display dev=all

b. Choose one available LUN to receive data (I/O) for the test.
c. View the paths to the chosen LUN:
powermt display dev= x every=2
where x is a pseudo device that represents the chosen LUN.

d. Start sending data to a LUN by writing data to it.
e. Identify the HBA sending data to the LUN by viewing the
output of the powermt display dev= x every=2 command, and
disconnect the cable to that HBA.
f. View the output of the powermt display dev= x every=2
command, and verify that:
The state of the uncabled paths becomes “dead.”
Data continues to be sent on the remaining paths to the
LUN, indicating that the failover path was successful and
that PowerPath is working properly.
72
g. Reconnect the cable that you disconnected from the HBA.
h. If you caused any LUNs to fail over, restore them to their
original SP:
powermt restore

73
Copyright© 2009 EMC Corporation. All Rights Reserved.
EMC believes the information in this publication is accurate as of its publication date. The
information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION
MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO
THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an
applicable software license.
For the most up-to-date regulatory document for your product line, go to the Technical
Documentation and Advisories section on EMC Powerlink.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on
EMC.com.
All other trademarks mentioned herein are the property of their respective owners.
74

Attaching Server To Storage System - Master 1073670

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Attaching Server To Storage System - Master 1073670

Hochgeladen von

Copyright:

Verfügbare Formate

Here is Your Customized Document

Your Configuration is:

Content Creation Date 2010/3/8

This document explains how to attach a Solaris server with EMC®

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

Attaching a Solaris Server with EMC PowerPath to a CX4-960 Storage System

Starting the Navisphere Server Utility on a Solaris server

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

Generating a high-availability report for a server

This option detects if PowerPath or some other failover software,

Verifying a server’s configuration with E-Lab Interoperability Navigator

If the configuration you entered is invalid, an additional step

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

Attaching a Solaris Server with EMC PowerPath to a CX4-960 Storage System

Before you start

HBAs are very susceptible to damage caused by static discharge and

1. If the server is powered up:

Attaching a Solaris Server with EMC PowerPath to a CX4-960 Storage System

Before you start

❑ Any updates, such as hot fixes or patches to the server’s operating

Installing the HBA driver

Attaching a Solaris Server with EMC PowerPath to a CX4-960 Storage System

Some driver updates may require you to reboot the server.

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

Modifying the Solaris system specification file

1. Set sd_io_time to 60 seconds.

This setting prevents the host from issuing warning messages

This setting prevents the host from over-sending tag queuing

A maximum throttle setting of 20 means that each host device

Attaching a Solaris Server with EMC PowerPath to a CX4-960 Storage System

Configuring host warnings

where x is a value that is not used by any other local setting in

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

2. Set the RAD_LOG_FACILITY environment variable to

For csh, enter:

For sh, enter:

Before you install PowerPath

where x is a value that is not used by any other local setting in

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

2. Set the RAD_LOG_FACILITY environment variable to

For csh, enter:

Attaching a Solaris Server with EMC PowerPath to a CX4-960 Storage System

 Navisphere Storage System Initialization Utility

About the Navisphere Storage System Initialization Utility

About the Navisphere CLI

Attaching a Solaris Server with EMC PowerPath to a CX4-960 Storage System

About the Navisphere Host Agent

About the Navisphere Server Utility

This feature is not available on iSCSI servers.

About the Admsnap Utility

If you upgraded your storage system to Navisphere Manager and want to

Attaching a Solaris Server with EMC PowerPath to a CX4-960 Storage System

Installing CLARiiON server software

Determining whether to install the host agent or server utility

Function Host agent Server utility

Attaching a Solaris Server with EMC PowerPath to a CX4-960 Storage System

Requirements for CLARiiON server software

Power-cycling the storage system

Solaris does not generally support the powering down of a storage

Installing the Navisphere Host Agent and/or CLI

Attaching a Solaris Server with EMC PowerPath to a CX4-960 Storage System

Installing the host agent on a Solaris server

Navisphere Storage System Initialization Utility

Enter 2 (to install CLI)