C H A P T E R 3 |
Registering and Initially Administering the Array |
This chapter provides an overview of the management software and the steps required for first time you log in. It contains the following sections:
By default, the management host communicates with RAID arrays out-of-band over Ethernet. You can also configure in-band management to travel over the data path (using Fibre Channel, etc.) between data host and the array instead. You can configure in-band management either before beginning to configure the array or after registering the array using out-of-band management.
For information about in-band management, see Configuring In-Band Management.
This section describes the operations you need to perform the first time you open the management software after installing it. The sections include:
When you open the Common Array Manager after a first-time installation, the General Configuration page displays.
The General Configuration page contains information about the site, rather than the array, and differs from the Administration page.
1. Enter the following information for your site:
The required fields are indicated by an asterisk: (*).
2. Click Save and Continue Setup.
Once you have saved the Site Information page, the Auto Service Request page displays during initial installations.
During the initial Common Array Manager installation, the software prompts you to register with the Auto Service Request service by displaying the Auto Service Request (ASR) Setup page.
Auto Service Request (ASR) monitors the array system health and performance and automatically notifies the Sun Technical Support Center when critical events occur. Critical alarms generate an Auto Service Request case. The notifications enable Sun Service to respond faster and more accurately to critical on-site issues. You can select the Enroll Now button to enroll or the Decline button to defer enrollment.
For more information on Auto Service Request, see Setting Up Auto Service Request.
To enroll with ASR during the Common Array Manager installation, perform the following procedure on the Auto Service Request Setup page:
1. Provide the following information:
ASR is available to all customers with a current warranty or Sun Spectrum Contract:
2. To accept Auto Service Request, click OK.
There is a Test button to verify that the email address provided with the Sun Online Account and CAM are communicating. You must enroll the CAM software with ASR before using the Test button.
While ASR is enabled by default for all registered arrays, there are settings that must be configured to use ASR to monitor an array as described in Configuring Auto Service Request for an Array.
Further information regarding ASR can be found here:
http://www.sun.com/service/asr/
When you install the management software on a new workstation, the Storage System Summary page is displayed blank with no arrays listed.
On all subsequent logins to the Common Array Manager, the Storage System Summary page is displayed with the arrays you registered with the software.
To register an array, select Storage Systems in the left navigation pane and on the Storage Summary page, click Register. The Array Registration wizard starts and you can choose to either search the subnet for arrays that are not already registered or manually register an array.
Registering arrays are documented in the following sections:
The registration wizard will automatically discover arrays that are on the same subnet as the management host, or you can point the wizard to the array if it is not on the same subnet as the management host.
If searching for arrays on a subnet, the discovery process displays the percentage of completion while the array management software polls devices in the network to determine whether any new arrays are available. When complete, a list of discovered arrays is displayed.
The Storage System Summary page is displayed.
The Register Storage System wizard is displayed.
3. In the Register Storage System wizard, select the storage system discovery method you want to use and click Next.
The management software will scan the subnet it is on for unregistered arrays, or you can specify a specific IP address for the array if the array is outside of the storage system subnet. Additionally, you can have it use the default password for arrays or you can enter a password if you have already changed the password on the array.
Note - The password of the array is not a required entry. The array is shipped with a blank password by default. This field is used only if the array being registered is one that was previously managed and had a set password. To give the array a password, see Setting an Array Password. |
With the scanning discovery method, the wizard then finds the array you defined and any unregistered arrays on the subnet and adds them to the Storage System Summary page.
Note - It takes approximately 2 minutes for the software to discover each array. |
The Results page displays, showing whether the array was successfully registered with the software.
The Results page also displays a message if your firmware is not at the baseline to match this version of Common Array Manager software. To install the baseline firmware, see Installing the Baseline Firmware.
You remove an array from the management software by unregistering the array.
The Storage System Summary page is displayed.
2. Select the check box to the left of the array you want to remove from the list of registered arrays.
This enables the Remove button.
The array is unregistered and removed from the Storage System Summary.
Refer to the Sun StorageTek Common Array Manager Software Release Notes and array release notes for the latest release-specific firmware information. Array-specific firmware information can also be found here:
http://www.sun.com/storage/management_software/resource_management/cam/
As part of the installation of the Common Array Manager software, the script puts the array firmware files in a directory on the management host. When you upgrade the firmware, the software analyzes the firmware installed on the array. If the baseline firmware on the host is newer, and you choose to install, the software installs the baseline firmware on the array.
For optimal performance, Sun Microsystems recommends that the firmware on all arrays be at the level of the current firmware baseline. CAM generates a Revision Delta Alarm when any array components are not at baseline. New features are not supported with non-baseline firmware.
1. Log in to the management software.
2. From the Java Web Console page, click Sun StorageTek Common Array Manager.
3. Be sure the array is not in a degraded state.
If it is degraded, the firmware upgrade attempt might fail and damage the array. Resolve the critical alarms before continuing the upgrade. If the array is degraded only because it is not at the baseline, the upgrade can be performed.
Alarms can be checked in the Java Web Console masthead or in the Alarms Summary link in the Navigation Tree on the left. Use Service Advisor to fix any alarms.
Note - For 6xxx, FlexLine, and 25xx arrays, both controllers must be attached to the network and be accessible by the host. |
5. From the Storage System Summary page, select the array for which the firmware needs to be installed/upgraded.
6. Click Install Firmware Baseline, and follow the instructions given in the Firmware Upgrade Wizard.
The upgrade process analyzes the array to determine the current firmware versions installed. If the firmware is not at the baseline, and you choose to upgrade, the baseline firmware is installed on the array.
If you have a need to back out of a firmware upgrade, contact Service.
Firmware file location information can be found in the Sun StorageTek Common Array Manager Software Release Notes.
To set up the array for basic operation, perform the procedures outlined in the following sections:
The Administration page contains other features that you may decide to configure. See the online help for more information before you change any default settings.
Open the Administration page to perform array administration functions.
1. In the navigation pane, click on the array you want to work with to expand the navigation tree.
The navigation tree expands to display the configuration options for the selected array, including Administration.
2. Click on Administration, under the array you have selected.
The Administration page for that array is displayed.
After making any changes on the Administration page, click Save to save the changes.
A new Sun StorageTek array is shipped with a blank, or empty, password field. Sun recommends that you establish an array password during initial setup for security purposes. The password prevents other management hosts from unauthorized access to the configuration of the array.
1. On the Administration page, click Manage Passwords.
The Manage Passwords page is displayed.
2. Select Change Array Password.
3. Leave the Old Password field blank.
This is the only time you can leave this field blank, when you establish a password for a new array.
4. Enter a new password consisting of up to 30 characters for the array.
5. Enter the password again to confirm the new password.
The Administration page is redisplayed.
The management software stores an encrypted copy of the array password, known as the local password, on the management host
Each array requires a unique name to be identified on the subnet.
In the Name field on the Administration page, enter a unique name consisting of up to 30 characters.
Hot spare drives are used by a controller to replace a disk that has failed. It is a good practice to define a hot spare before initiating storage on the array.
From the drop-down menu on the Administration page, select a drive to serve as a hot spare drive to provide alternative drive space in case of a failure. Refer to the online help for information about this and other advanced configuration features.
You can also update the system time and date on the Administration page for the array in the browser interface. When you set the time and date for a selected array, the values are updated for all arrays registered with this management software.
There are two ways in which you can update the system time and date:
1. On the Administration page, scroll down to the System Time section.
2. Select the current hour and minute according to a 24-hour clock.
3. If the date is incorrect, change the month, day, and year to the current date.
4. Click Save to save your changes.
The Administration page is refreshed, and a Success message is displayed at the top of the page.
For more information about the fields and buttons on the Administration page that you can use after you set up your system, see the online help.
The fault management features of the Sun StorageTek Common Array Manager software enables you to monitor and diagnose your arrays and storage environment. Alarm notification can be provided by:
You can also set up Auto Service Request as described in Setting Up Auto Service Request.
1. In the navigation pane, under General Configuration, choose Notification.
The Notification Setup page is displayed:
FIGURE 3-1 Email Fault Notification Setup
a. Enter the name of the SMTP server.
If the host running this software has the sendmail daemon running, you can accept the default server, localhost, or the name of this host in the required field.
b. Specify the other optional parameters, as desired.
c. If you have changed or entered any parameters, click Save.
d. (Optional) Click Test Local Email to test your local email setup by sending a test email.
If you need help on any of the fields, click the Help button.
3. Set up local email notification recipients.
a. Click Administration > Notification > Email.
The Email Notification page is displayed.
The Add Email Notification page is displayed.
c. Enter an email address for local notification. At least one address is required to begin monitoring events. You can customize emails to specific severity, event type, or product type.
4. (Optional) Set up remote notifications by SNMP traps to an enterprise management application.
a. Select SNMP as the provider.
5. Perform optional fault management setup tasks:
To use the Common Array Management software, users and roles must be defined on the host and assigned in CAM. Make sure the following user names are defined on your systems:
User names must be a currently defined user on the management host.
Roles assign privileges to users. Two roles (storage and guest) are defined in CAM.
Assigns a user write permission and access to all of the software features related to array configuration and management.
Assigns a user read permission but restricts the ability to manage the array.
By default, CAM automatically assigns roles to:
For all other users, you assign roles to users in the CAM software.
TABLE 3-1 describes the user names and user role functions and the requirements for each.
Setting up users and roles is described in the following sections:
The first time that you access CAM software, you sign in as an administrative user defined on the management host:
By default, the administrative user has the storage role. The administrative user can add users in CAM and assign roles to them.
User names in CAM must be currently defined users on the host.
To add new users to hosts running Solaris or Linux OS, consult the system administration documentation.
To add new users to hosts running Windows, refer to Adding New Users in Windows.
To share a user name for storage administration, add the following user names to your hosts:
Once these user names are added to the host, by default they are assigned the storage and guest roles.
This section describes how to add new users and assign them the storage or guest role in CAM. The users must first be defined on the host. For users (other than the administrative user) to access CAM, roles must be assigned to those users in the CAM software.
You do not have to complete this step for users automatically assigned a role by CAM:
1. To view the list of defined users, choose General Configuration > User Management in the navigation pane.
The User Summary page is displayed.
2. To add a new user, click the Add button.
The Add New User page is displayed.
3. In the User Name field, enter a valid user name defined on this host.
4. From the User Role list, select the storage or guest role you want to assign to this user.
The User Summary page is displayed with a success message and the name is added to the list.
Newly added users can log into the Sun Java Web Console to access CAM with the same password that they use to log into the system.
This section provides the information you need to create users in Windows and assign them to groups for privileges.
Note - The steps are an example and may differ in your Windows software. |
This chapter contains the following section:
These instructions show you an example of how to configure an administrative user in standard Windows XP. Other versions of Windows software may vary slightly. Consult the Windows documentation.
Note - Administrative user names for Windows cannot have a space character. |
1. Click Start and select Administrative Tools -> Computer Management.
The Computer Management window displays.
2. In the Computer Management window, select Local Users and Groups -> Users.
3. Right click and select New User.
4. Complete the New User window as follows:
a. Enter a username in the User name box (root is used as an example).
b. Create a password and confirm it.
c. Uncheck the box labeled User must change password at next login.
d. Check Password never expires.
The Computer Management window displays.
f. Select Users, right click on root, and select Properties.
The Properties window for the username displays.
The Select Groups window displays.
7. In the Enter the object names box, type Administrators and click Check Names.
The system displays the computer-name\Administrator group in the box labeled “Enter the object names to select.”
The root Properties window shows that root is a member of Users and the Administrators groups. The root user now has Windows Administrator privileges and is automatically assigned the storage role in CAM.
To add non-Administrator users, follow the same steps as Adding an Administrator User, but define groups called storage and guest and add the user name to one of those groups instead of the Administrator group.
When done, check the Properties window of the user name and Member of tab to verify that the user is assigned to Users and to the storage or guest Group.
Proceed to assign the user name the storage or guest role in the CAM software, as described in Adding New Users to CAM and Assigning Roles.
Once these user names are added to the system, by default they are assigned the storage and guest roles.
Multiple instances of the same user name can be logged in concurrently. However, because users with the storage user role have write privileges, there is a risk that the changes of one logged-in user will overwrite previous changes of another logged-in user. Therefore, you should develop policies about who can make changes and how to notify others.
During the initial storage array set-up process, Common Array Manager prompts you to enroll with the Auto Service Request service by displaying the Auto Service Request (ASR) Setup page. This page continues to display until you either fill out the page and click OK, or click Decline to either decline or defer ASR service enrollment.
To set up the array for Auto Service Request, perform the procedures outlined in the following sections:
Auto Service Request (ASR) monitors the array system’s health and performance and automatically notifies the Sun Technical Support Center when critical events occur. Critical alarms generate an Auto Service Request case. The notifications enable Sun Service to respond faster and more accurately to critical on-site issues.
The Common Array Manager provides the interface to activate Auto Service Request on behalf of the devices it manages. It also provides the fault telemetry to notify the Sun service database of fault events on those devices.
To use ASR, you must provide Sun online account information to enroll this CAM software to participate in the ASR service. After you enroll CAM with ASR, you can choose which arrays you want to be monitored and enable them individually.
ASR uses SSL security and leverages Sun online account credentials to authenticate transactions. The service levels are based on contract level and response times of the connected devices.
ASR is available to all customers with a current warranty or Sun Spectrum Contract:
The service runs continuously from activation until the end of the warranty or contract period.
Only the event information listed in the following table is collected. Your stored data is not read and remains secure.
The event information is sent by secure connection to
https://cns-services.sun.com.
During the initial CAM set-up process, the Common Array Manager prompts you to enroll with the Auto Service Request service by displaying the Auto Service Request (ASR) Setup page. This page continues to display until you either fill out the page and click OK, or click Decline to either decline or defer ASR service registration.
To enroll with ASR after the initial set-up, use the following procedure.
1. Click Sun StorageTek Common Array Manager.
The navigation pane and the Storage System Summary page are displayed.
2. In the navigation pane, expand General Configuration and choose Auto Service Request.
The Auto Service Request Setup page displays (see FIGURE 3-2).
3. Provide the following information:
FIGURE 3-2 Auto Service Request Setup Page
TABLE 3-3 describes the fields and buttons on the Auto Service Request page.
You can test the Auto Service Request service connection to ensure that the email address specified in the Sun online account and CAM are communicating. The CAM software must be enrolled with the Auto Service Request service before testing.
1. Click Sun StorageTek Common Array Manager.
The navigation pane and the Storage System Summary page (see FIGURE 3-2) are displayed.
2. In the navigation pane, expand General Configuration and choose Auto Service Request.
The Auto Service Request Setup page displays.
The Sun Online Account service will send a confirmation email to the email address on record for your Sun Online Account. If you do not receive a confirmation email within approximately 30 minutes, contact the Sun Online Account personnel.
When you unregister from Auto Service Request service, ASR will stop sending telemetry data to Sun about your system.
1. Click Sun StorageTek Common Array Manager.
The navigation pane and the Storage System Summary page are displayed.
2. In the navigation pane, expand General Configuration and choose Auto Service Request.
The Auto Service Request Setup page displays.
After registering with ASR, you can choose which arrays to monitor using ASR. In order for an array to be monitored using ASR, the following settings must be in effect:
While ASR is enabled by default for all registered arrays, the following settings must be configured to use ASR to monitor an array:
1. Click Sun StorageTek Common Array Manager.
The navigation pane and the Storage System Summary page are displayed.
2. In the navigation pane, expand the array you want to monitor using ASR.
3. In the navigation pane, click on Array Health Monitoring
The Array Health Monitoring Setup page is displayed.
4. In the Health Monitoring section, ensure that the Health Monitoring Agent Active and the Device Category Monitored fields are set to Yes. If either are set to No, go to the General Health Monitoring Setup page and change the settings.
5. In the Monitoring this Array section, the checkbox next to both Health Monitoring and Auto Service Request are selected by default. If monitoring is not desired, deselect the Auto Service Request checkbox.
By default, the management host communicates with the arrays out-of-band over Ethernet. You can also configure in-band management for communication to travel over the data path (using Fibre Channel (FC), etc.) between a data host and the array.
Setting up the array for in-band management is outlined in the following sections:
In-band management uses a proxy agent running on a data host to communicate with a managed array. Sun StorageTek Common Array Manager software discovers the proxy agents on the subnet and then queries arrays registered with the software. The proxy agent receives the queries over Ethernet and passes them on to the array over the data path between the data host and the array.
New arrays can be registered with the software using the registration wizard. The wizard can auto-discover the array via the proxies or you can specify the IP address of the proxy agent. Once an array is registered, management of the array appears the same as does management with an out-of-band connection. Volume creation, deletion, and mapping are accomplished in the same manner.
In-band management uses a special access LUN mapping to facilitate communications between the management software and the storage array. You can view all mappings on the array on the Mapping Summary Page in the Sun StorageTek Common Array Manager software. For in-band communication, an access volume is mapped to LUN 31. This special access LUN (also called the UTM LUN) is mapped to the default domain. (All arrays have a default domain for volumes not registered with a storage domain.)
With new arrays, the mapping of the access LUN to the default domain is installed at the factory. If you lose this mapping, before installing in-band, use out-of-band management and the Common Array Manager software to re-map the access LUN to the default domain. See the online help in the software for more information about mapping.
This release supports Solaris Sparc and x86, Windows, and Linux for in-band management. For Red Hat Enterprise Linux AS, Release 5.1 or higher is required. Check the Sun StorageTek Common Array Manager Release Notes, v.6.2 for the latest list of packages to install from the CD.
The in-band management proxy agent is a package which is added to a host (or group of hosts) with in-band connectivity via Fibre Channel to the storage array. An external management station can then talk to this proxy host via an out-of-band connection and the management commands are then relayed to the storage device via the in-band path. This is a transparent proxy agent which simply converts the RPC request packets to UTM SCSI- specific messages. The API CAM uses to manage the arrays is identical whether the array is managed via the in-band or out-of-band path.
The proxy agent packages for each OS are located in the “Add-Ons” directory. Refer to the README file for installation instructions for your particular OS.
A proxy agent restart is required after disruptive changes to the storage configuration. This does not apply to changes in volumes exposed from a single array but it does apply if storage arrays are re-cabled differently or if the storage array configuration has changed (i.e. adding new storage arrays to the configuration).
The in-band proxy agents will start when the host boots, but they will terminate if storage is not immediately seen. A restart of the agent (instructions below) will force a re-scan for storage arrays and, if any are found, the agent will remain running.
Download CAM in-band proxy agents for Solaris from here:
http://www.sun.com/download/products.xml?id=471e7573
To verify the host sees the arrays management (UTM) LUN, do the following:
1. Start / Stop the Agent (Solaris)
If the agent is already running, this will stop and then restart it.
2. Check the status of the agent
# ps -ef | grep SMagent | grep -v grep
root 5144 1 0 11:58:24 pts/3 0:01 /opt/SMgr/agent/jre/bin/java -classpath
/opt/SMgr/agent/SMagent.jar devmgr.launch
Note - The SMagent requires Red Hat 5.1 (also known as “5 update 1”) or higher. It is not supported on Red Hat 5.0. |
Note - This information applies only to FLX240, FLX280, FLX380, 6130, 6140, 6540, 6580, 6780, 2510, 2530 and 2540 arrays. |
Download CAM in-band proxy agents for Linux from here:
http://www.sun.com/download/products.xml?id=471e7573
To verify the host sees the arrays management (UTM) LUN:
[root@nsvr-150 agent]# /opt/SMgr/agent/SMagent start
[root@nsvr-150 agent]# SANtricity Storage Array Host Agent, Version 09.17.A0.03
Built Tue Dec 05 14:52:38 CST 2006
Copyright (C) 1999-2006 LSI Logic Corporation. All rights reserved.
Checking device /dev/sda (/dev/sg0): Skipping
Checking device /dev/sdb (/dev/sg1): Skipping
Checking device /dev/sdc (/dev/sg2): Activating
[root@nsvr-150 agent]# java -classpath /opt/SMgr/agent/SMagent.jar devmgr.versioned.agent.DeviceIdentifier | grep “Volume Access” /dev/sdc
(/dev/sg2) [Storage Array fms-lca1, Volume Access, LUN 31, Volume ID <600a0b80002fc0740000000000000000>]
To verify the host sees the arrays management (UTM) LUN, do the following:
E:\Program Files (x86)\StorageManager\agent>net start “SANtricity Storage Manager Agent”
The Storage Manager Agent service is starting.
The Storage Manager Agent service was started successfully.
E:\Program Files (x86)\StorageManager\agent>C:\Java\jdk1.5.0_11\bin\java -classpath SMagent.jar devmgr.versioned.agent.DeviceIdentifier |
\\.\PHYSICALDRIVE0 [Storage Array fms-lca1, Volume Access, LUN 31, Volume ID <600a0b80002458d20000000000000000>]
\\.\PHYSICALDRIVE1 [Storage Array fms-lca1, Volume Access, LUN 31, Volume ID <600a0b80002fc074
1. Connect two in-band (FC, etc.) cables between HBAs on the data host where the proxy is to be installed and the array (one cable to each controller).
2. Install the SMruntime and SMagent packages on the proxy host, using the pkgadd command in Solaris and rpm command in Linux.
pkgadd -d <directory or disk-directory> SMruntime-SOL-xx.xx.xx.xx.pkg pkgadd -d <directory or disk-directory> SMagent-SOL-xx.xx.xx.xx.pkg
rpm -ivh SMruntime.xx.xx.xx.xx-xxxx.rpm rpm -ivh SMagent-LINUX-xx.xx.xx.xx-xxxx.rpm
3. Solaris only - to verify that the host sees the access LUN to manage the array via the in-band path, perform the following commands on the data host:
setenv LD_LIBRARY_PATH /opt/SMgr/agent java -classpath /opt/SMgr/agent/SMagent.jar devmgr.versioned.agent.DeviceIdentifier | grep "Volume Access"
The arrays with access LUNs visible to the agent will display as follows:
/dev/rdsk/c5t200600A0B82458D4d31s2 [Storage Array fms-lca1, Volume Access, LUN 31, Volume ID <600a0b80002458d20000000000000000>] /dev/rdsk/c5t200700A0B82458D3d31s2 [Storage Array fms-lca1, Volume Access, LUN 31, Volume ID <600a0b80002fc0740000000000000000>]
4. Verify that the Proxy Agent is running. If necessary, check the SMagent process and restart in /opt/SMgr/agent/SMagent.
5. To start the agent, perform this command in Solaris or its equivalent: /opt/SMgr/agent/SMagent start
If the agent was running, it will stop and then restart after a status check.
# ps -ef | grep SMagent | grep -v grep /opt/SMgr/agent/jre/bin/java -classpath /opt/SMgr/agent/SMagent.jar devmgr.launch
Sign in to the software and begin configuring as listed in Starting the Management Software. After the registration process discovers arrays, they display on the Storage System Summary page. The Network Address field displays whether the connection with each array is in-band or out-of-band. The Common Array Manager software can manage arrays with either in-band and out-of-band connections at the same time.
If you are going to copy a configuration file to a management host that will have in-band communication with the array, you need to preserve the mapping between the access LUN and the management host using the import array command with the -n (noclear) option.
import -x <XML-location> [ -L <list> ] [ -n ] array <array-name>
The import command typically applies an array configuration file to the specified array. The -n option preserves the current array configuration, including the mapping between the access LUN (LUN 31) and the default domain of the management host. This mapping is required for in-band management of the array.
-x,--xml <XML-location>
Specifies the location of the XML file to be imported. The XML location can be in the form of a URL (http://... or file:///...) or a file name.
-L,--list
Specifies that no import take place. Instead, the array is checked against the XML file to ensure that it is compatible.
-n,--noclear
Specifies that the current array configuration will not be cleared.
array <array-name>
Specifies the array to which the configuration file is applied.
Copyright © 2009 Sun Microsystems, Inc. All rights reserved.