EMC CLARiiON Server Support Products for Solaris Server Installation Guide P/N 300–002–039, Revision A10 August 17, 2007 This guide describes how to install and remove the Navisphere® Host Agent, Navisphere Storage System Initialization Utility, Navisphere Server Utility, Navisphere Command Line Interface (CLI), and admsnap software on a Sun Solaris operating system.
2 Installing and removing the Navisphere Server Utility ..................... Running the Navisphere Server Utility ........................................... Installing and removing the Admsnap Utility.................................. Running the Admsnap Utility ........................................................
About EMC Navisphere Software The following EMC® server-based software is available on the server support CD that shipped with your storage system or your upgrade kit (for AX-series systems upgrading to Navisphere Manager): Navisphere® Storage System Initialization Utility Navisphere Host Agent Navisphere Server Utility Admsnap Utility Navisphere Command Line Interface (CLI) About the Navisphere Storage System Initialization Utility For CX3-series and CX-series Fibre Channel storage syst
Note: The Navisphere Initialization Utility runs on servers attached to CX3-series, CX700, CX500-series, CX300-series, and AX-series storage systems. CX3 model 10 systems must be running FLARE® OE 03.24.010.5.xxx or later. CX3 model 20 systems, CX3 model 40 systems, and CX3 model 80 systems must be running FLARE OE 03.22.xxx.5.yyy or later. CX700, CX500-series, and CX300-series systems must be running FLARE OE 02.16.xxx.5.yyy or later. AX150-series systems must be running FLARE 02.20.xxx.5.yyy or later.
Update server information to the storage system — This option sends the server name and IP address to the storage system and, if needed later on, allows you to update or view this data. For Windows servers running Navisphere Server Utility version 6.
Note: The server utility runs on servers attached to CX3-series, CX-series, and AX-series storage systems. CX3 model 10 systems must be running FLARE OE 03.24.010.5.xxx or later. CX3 model 20 systems, CX3 model 40 systems, and CX3 model 80 systems must be running FLARE OE 03.22.xxx.5.yyy or later. CX200, CX300-series, CX400, CX500-series, CX600, and CX700 systems must be running FLARE 02.16.xxx.5.yyy or later.AX150-series systems must be running FLARE 02.20.xxx.5.yyy or later.
Note: The Admsnap Utility runs on servers attached to CX3-series and CX-series. It also runs on servers attached to AX-series storage systems that have been upgraded to Navisphere Manager, that is, that have the Navisphere Manager enabler installed. If you upgraded to Navisphere Manager and want to manage snapshots, you must use the SnapView software and the Admsnap Utility.
Finding current information The most up-to-date information about the CLARiiON® server software is posted on the EMC Powerlink® website. We recommend that you download the latest information before you install any server software. To access EMC Powerlink, use the following link: http://Powerlink.EMC.
Installing and removing the Navisphere Storage System Initialization Utility EMC recommends that you install the utility on the server; however, you can run the Navisphere Storage System Initialization Utility from the server support CD. Installation prerequisites To use the Storage System Initialization Utility on a Solaris server to initialize a storage system, the server must meet the following requirements: Run a supported version of the operating system.
3. To download the software for CX3–series or CX-series storage systems, do the following: a. On the Powerlink website, select Support > Software Downloads and Licensing and navigate to the Navisphere Storage System Initialization Utility download section, which may be in either the CLARiiON Navisphere Storage System Initialization Utility section or the CLARiiON Navisphere Host Based Agent/CLI Solaris section. b.
pkgadd -d INITTOOL.pkg 5. To install the software from the server support CD (any storage system), do the following: a. In the server’s drive, insert the server support CD, which shipped with the storage system or the upgrade kit (for AX-series systems upgrading to Navisphere Manager). b. From a console window, mount the CD: mount /mnt/cdrom c. Install the Navisphere Storage System Initialization Utility: /cdrom/cdrom0/solaris pkgadd -d ./solaris/INITTOOL.pkg 6.
Running the Navisphere Storage System Initialization Utility You can start the storage system initialization utility from the server on which it is installed or from the server support CD. The storage system initialization utility has two methods for executing commands — a command line interface that can be scripted, or a text-based utility that cannot be scripted. Before continuing make sure that the storage system is powered up completely.
cdrom /cdrom0/solaris 4. To start the text-based utility or command line utility from the CD, enter ./naviinittool and for the command line utility, include any of the command line switches in Using the command line initialization utility, page 15. Using the text-based initialization utility To use the text-based utility to initialize your storage systems, do the following: 1. Read the license agreement and enter y to accept it The utility automatically scans the subnet for supported storage systems.
Parameter Description Storage Processor B - IP ADDRESS IP address for SP B management port. For a CX3–series system, this IP address cannot be 128.221.1.250, 128.221.1.251,192.168.1.1, or 192.168.1.2 because these addresses are reserved. For an AX-series storage system, this IP address cannot be 192.168.1.1 or 192.168.1.2 because these addresses are reserved. Subnet Mask Subnet mask associated with the LAN to which the storage-system management port is connected.
Using the command line initialization utility Use the following switches, in combination with the appropriate CLI command, to set initialization values for the specified storage system.
-ipa spAipaddress |-sphosta spAhostname -configure with the –ipa switch sets the IP address of SP A, or the server name for SP A for the specified storage system. -ipb spBipaddress |-sphostb spBhostname -configure with the –ipb switch sets the IP address of SP B, or the server name for SP B for the specified storage system. -mask subnetmask -configure with the –mask switch sets the subnet mask for the specified storage system.
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. If you want to install both applications, you must install revision 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 NICs or iSCSI HBAs to the storage system.
Table 1 Differences between the host agent and the server utility Function Host agent Server utility Pushes LUN mapping and OS information to the storage system. Yes – LUN mapping information is displayed in the Manager UI next to the LUN icon or with the CLI using the -lunmapinfo command. AX-series storage systems Yes – LUN mapping information is displayed in the Manager UI next to the LUN icon, or with the CLI using the -lunmapinfo command.
Function Host agent Server utility Requires network connectivity to the storage system. Yes – Network connectivity allows LUN mapping information to be available to the storage system. AX-series storage systems No – LUN mapping information is sent through a data path to the storage system. CX3-series and CX-series storage systems No – LUN mapping information is not sent to the storage system.
Requirements for the host agent, server utility, and CLI To run the host agent, CLI, or server utility, 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 revision of a Solaris operating system. For the latest requirements see the software product release notes. Have the EMC CLARiiON supported HBA hardware and driver installed.
Note: 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 revision of the host agent, see the release notes for the host agent on the EMC Powerlink website. To access this website, see Finding current information, page 8 . Power-Cycling the storage system Note: Do not issue verify_disk_array while the SP is powering up. You must wait until the SP has completed the powerup cycle.
Installing or removing the Navisphere Host Agent and CLI You can install both the host agent and CLI package or just the CLI package. If you will install both, install the host agent first. To modify an existing host agent configuration refer to the next section. Note: 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 17.
b. Select the appropriate host agent version 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. Enter the following command to install the host agent and/or CLI package: pkgadd -d NAVIAGNT.pkg 5. To download the software for AX-series storage systems, do the following: a.
7. 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) 8. 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.
12. Verify the installation by entering the command pkginfo -l | grep 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) 13. If you have a multihomed host (multiple NIC cards installed on the host), create an agentID.txt file to ensure that the agent finds the correct NIC card.
192.111.222.3 Note: The agentID.txt file should contain only these two lines, without any formatting. The first line should contain the hostname and the second line should contain the IP address of the HBA/NIC port as described above. Both lines should end with a carriage return. As a result, the cursor will be on a third line but this line should not contain any text. c. Save the agentID.txt file. d. If you created the agentID.
3. View the paths using the echo command as follows: # echo $PATH # echo $MANPATH # echo $LD_LIBRARY_PATH 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 are finished with the upgrade. Removing the host agent and/or CLI on a Solaris server Note: To avoid losing site-specific information, copy the host agent configuration file (agent.
Configuring the Navisphere Host Agent Before you can use the Navisphere CLI navicli register command to configure a CX3-series, CX-series, or AX-series storage system connected to a host agent, you must make sure the host agent configuration file includes a privileged user, as described in Adding privileged users, page 28. Note: The pathname of the host agent configuration file is /etc/Navisphere/agent.config . If you are configuring a legacy storage system, refer to revision A09 of this guide.
2. If you are done 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.
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.
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 On a Solaris server, 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.
3. Verify that the host agent on the server can see the storage system as follows: a. Enter the following CLI command: navicli [-d device]| -h hostname port -list -hba Note: You cannot specify both the –d switch and –h switch; you must use one or the other. where: [-ddevice] is the device name for the storage system (only supported with legacy systems). -hhostname is the server name . For each HBA in the server, a listing similar to the following will be displayed.
c. In the listing, check the information for each HBA to make sure it is logged into the appropriate SP in the storage system. 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.
Installing and removing the Navisphere Server Utility This section describes how to install the Navisphere Server Utility on a server connected to a CX3-series, CX-series, or AX-series storage system. Installing the Navisphere Server Utility on a Solaris server EMC recommends that you install the most recent version of the Navisphere Server Utility software that is appropriate for your configuration.
where version is the version listed in the filename. d. Install the Navisphere Server Utility on the server: pkgadd -d HOSTUTIL.pkg 4. To download the software for AX-series storage systems, do the following: a. On the support website select Download for AX150 series or Register to Download software for AX100 series. b. Select the appropriate Navisphere Server Utility version to download and select the option to save the zip file to your server. c.
The screen displays information about the installation. 8. When installation is complete, exit the /cdrom directory (for example, cd /). 9. If you installed the server utility from the CD, remove the CD from the server’s CD drive. Removing the server utility on a Solaris server 1. At the Solaris server, log in as superuser (root). 2. Verify which version of the server utility is installed: pkginfo |grep HOST The name of the software application is displayed (HOSTUTIL or HOSTUTLA). 3.
Running the Navisphere Server Utility This section describes how to start and use the server utility. Starting the Navisphere Server Utility You can run the server utility from the server or from the server support CD. Starting the Navisphere Server Utility on a Solaris server 1. Open a shell window. 2. Navigate to the Navisphere bin directory: /opt/Navisphere/bin 3. Run the server utility: ./naviserverutil Starting the Navisphere Server Utility for a Solaris server on the CD 1.
Updating server information on the storage system The Update Server Information option allows you to send information about the server to all connected storage systems. To update server information, select option 1 from the server utility’s Welcome screen, and follow the instructions on the utility. Performing snapshot tasks For information on using the snapshot tasks option, refer to the Navisphere Express online help.
-secfilepath securityfilepath -port 443|2163 [-directory outputdirectory] where: -ip IPaddress Specifies the IP address of an SP on the storage system to which you will upload the report. You cannot use this switch in conjunction with the -h switch. -h IPaddress | network_name Specifies the IP address or the network name of an SP on the storage system to which you will upload the report. You cannot use this switch in conjunction with the -ip switch.
You cannot use this switch in conjunction with the -user|-u, -password|-p , and -scope|-s switches. -port 443|2163 Specifies the Navisphere Management Server port number. The default is 443. -directory outputdirectory Specifies the directory to which you want to deposit the report on the server. This switch is required only if you are running the server utility from the CD. Otherwise the report is automatically saved to the Navisphere Server Utility installation directory.
locate these LUNs. If they are not in the list, the server will lose access to those LUNs during the software upgrade.
Installing and removing the Admsnap Utility EMC strongly recommends that you install admsnap on all servers connected to a storage system that has the SnapView driver installed. Important: If you are upgrading your storage system to FLARE OE version 02.19.xxx.5.yyy or later, you must upgrade admsnap to version 2.9.x or later. Before you upgrade FLARE, verify that your operating system version supports admsnap version 2.9.x or later. Refer to the Admsnap Release Notes or the EMC Support Matrix on Powerlink.
a. On the Powerlink website, select Support > Software Downloads and Licensing and navigate to the Admsnap Utility download section, which may be in either the CLARiiON SnapView section or the SnapView section. b. Select the appropriate Admsnap Utility version 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 admsnap_version.
The CD is mounted automatically on /cdrom/admsnap, which is linked to /cdrom/cdrom0. The following command lines use /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 by typing: /usr/sbin/pkgadd —/cdrom/cdrom0/solaris/ADMSNAP.pkg The following messages appear: The following packages are available: 1 ADMSNAP Navisphere Admsnap (sparc) X.X.X.X.
xxxxxxxx xxxxxx When you see the error-free pkginfo message, admsnap software installation is complete. The software is installed in the directory /usr/admsnap. 8. Unmount the CD by entering the unmount/dev/cdrom command. 9. Remove the CD from its drive. Removing the Admsnap Utility on a Solaris server 1. Log in to the server as a superuser, such as root. 2. Remove the existing admsnap by entering: pkgrm ADMSNAP (uppercase ADMSNAP) Then confirm if prompted by entering y and y.
Running the Admsnap Utility Refer to the EMC SnapView Command Line Interfaces Reference for information on running admsnap commands.
Copyright© 2004–2007 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.
