C H A P T E R  4

Initial Array Set Up

This chapter provides an overview of the management software and the steps required for first time you log in. It contains the following sections:


Setting Up Site and Array Information

This section describes the operations you need to perform the first time you open the management software after installing it. The sections include:

Starting the Array Management Software

1. Open a supported web browser.



Note - For information about supported web browsers, see the Sun Storage Common Array Manager Release Notes.


2. Enter the IP address of the management host using this format:

https://cam-management-host:6789

cam-management-host is the IP address or host name of the host where you installed the Common Array Manager software.

3. Log in as root (Solaris) or administrator (Windows).

4. Click Log In.

The Oracle Java Web Console page is displayed.



Note - The connection closes automatically if there is no activity for approximately 15 minutes.


5. From the Oracle Java Web Console page, select Sun Storage Common Array Manager from the Storage section of the Oracle Java Web Console page.

Providing Site Information

When you open the Common Array Manager after a first-time installation, the General Configuration page displays.

1. Enter the required site and contact 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.

Subscribing to Auto Service Request

During the initial 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 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 contract:

2. To accept Auto Service Request, click OK.

The Test button enables you to verify that the email address provided with the Sun Online Account and array management software are communicating. You must enroll the array management 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 Setting Up Auto Service Request.

Further information regarding ASR can be found here:

http://www.sun.com/service/asr/


Registering Arrays

When you install the management software on a new workstation, the Storage System Summary page is displayed blank with no arrays listed.

To register an array, launch the Array Registration wizard to either search the subnet for arrays that are not already registered or manually register an array.

The registration wizard will automatically discover arrays that are on the same network as the management host, or you can point the wizard to the array if it is not on the same network as the management host.

1. From the Storage Systems Summary page, click Register.

2. Select the Discovery and Authentication Method and click Next.



Note - The discovery process can take as much as five minutes per array.


a. To scan for unregistered arrays and specify a password, select Scan the local network and Enter password for the discovery.

For J4000, F5100, and Sun Blade 6000 Array Families, use this option for a central management host and enter the proxy agent password.

If each proxy agent has a different password, only the array with a proxy agent using that password will be discovered. You may want to set up a common proxy agent password.

b. To manually register an array, select Enter IP address or hostname and Enter password for the discovery.

For the J4000, F5100, and Sun Blade 6000 Array Families, enter the IP address, host name, or localhost name of the proxy agent and the proxy agent password.

For all other arrays, enter the IP address or hostname of the array controller and the array password.

c. To scan for unregistered arrays that use a default password, select Scan the local network and Use the default password.

For other IP configured arrays, such as the Sun Storage 6000 Array series, use this method to discover arrays that use the default password set at the factory.



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 five minutes for the software to discover each array.


3. Select the arrays you want to monitor, and click Finish.

The Results page displays a message indicating one of the following:

4. Click Close.

You remove an array from the management software by unregistering the array. For information about how to unregister an array, see the Online Help.


Initial Array Administration

Use the Administration page associated with each array to perform the following tasks:

The Administration page has other properties that you can modify later for each array. See the Online Help for more information about each field.

Installing the Baseline Firmware

New arrays come with the firmware installed. As updates to the firmware are released or you add expansion trays to any 6000 series array, you need to install the new firmware. For optimal performance, the firmware on all arrays should be at the level of the current firmware baseline.



Note - Refer to the Sun Storage Common Array Manager Baseline Firmware document for the latest release-specific firmware information.


1. Check the release notes for any release-specific upgrade requirements.

Upgrades to the J4000, F5100, and Sun Blade 6000 Blade Families firmware (SAS I/O modules and disks) require an offline upgrade (stop all I/O activity to the array).

2. 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.

3. Resolve any alarms.

Alarms can be checked in the Oracle 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.


4. (Optional) If you are upgrading firmware for the F5100, determine the master expander location before you begin the upgrade.

a. Go to Storage Summary, F5100, FRUs.

The Health Details for the selected F5100 chassis lists the location, name, status, host information for each F5100 expander.

b. Note the location of the master expander listed for “Chassis Master Expander Location.”

5. From the Storage System Summary page, select the array for which the firmware needs to be installed/upgraded.



Note - You can only upgrade one array in the J4000, F5100, and Sun Blade 6000 Array Families at a time.




Note - For 6xxx, FlexLine, and 25xx arrays, both controllers must be attached to the network and be accessible by the host.


6. Click Install Firmware Baseline.

The upgrade process analyzes the selected arrays to determine the current firmware versions installed and displays a recommended action.

7. In the Action field, specify the type of upgrade, and click Next.



Note - To ensure a stable firmware installation, you can choose to select “Install baseline, no disks" to update the array controller or Expander/SIM firmware first. After verifying the baseline firmware is updated correctly, restart the Wizard to update the disk drive firmware.


8. If the array password is valid, click Next.

For the J4000, F5100, and Sun Blade 6000 Array Families, for arrays registered through a remote proxy, the registration validates the proxy agent password entered during the software installation. No password is verified for local in-band arrays.

9. Review the current installation action, and click Finish.

All management operations must be stopped before the installation begins. If you are installing disk firmware, all disk I/O must be stopped.

10. When the upgrade is complete, click Close.

11. If you chose to upgrade only the array controller or expander/SIM firmware first, repeat firmware installation for the disks.

For more information about array firmware, see the Online Help.

Setting an Array Password

A new Sun Storage 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.

6. Click OK.

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

Naming an Array

Each array requires a unique name to be identified on the subnet.

1. In the Name field on the Administration page, enter a unique name consisting of up to 30 characters.

2. Click Save.

Setting the System Time

When you set the system 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:

To set the time manually:

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.

Creating a Hot-Spare Drive

Hot spare drives are used by a controller to replace a disk that has failed. The management software can automatically assign a hot-spare drive, balance the request for spares across all trays within the array, and ensure that the hot-spare drive is of the same type as the other disks in the same tray.

1. From the Array Hot-Spares menu on the Administration page, select the number of hot-spares that you want to assign to this array.

2. Click Save.

The management software assigns the specified number of hot-spares, balancing the selection among trays within the array.

Refer to the Online Help for more information about assigning and unassigning hot-spare drives.


Adding Users And Assigning Roles

To use the Common Array Management software, users and roles must be defined on the host and assigned in the array management software. Make sure the following user names are defined on your systems:



Note - By default, the root user does not exist in OpenSolaris and is not recommended. Therefore, it is recommended to either 1) create storage and/or guest accounts on your OpenSolaris host for use with the array management software, or 2) assign roles to all existing users who will use the management software.


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 the array management software.

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, the array management software automatically assigns roles to:

For all other users, you assign roles to users in the array management software.

TABLE 4-1 describes the user names and user role functions and the requirements for each.


TABLE 4-1 User Names and User Roles

User Role/Group

Description

User Name

Required Password

storage (initial administrator)

Use the root or administrative user name to initially add other users. A storage user can use all of the software features related to array configuration and management.

Solaris - root

OpenSolaris OS - administrative

rights.

Linux - root

Windows - administrator user, including root if so set up.

Root or administrator password on the management host

storage

A storage user can use all of the software features related to array configuration and management.

Currently defined user on the management host

The same password used to log into the host

guest

A guest user has read-only privileges and can only view information. This user cannot modify any settings or features.

Currently defined user on the management host

The same password used to log into the host

 


Setting up users and roles is described in the following sections:

Using Administrative Roles to Initially Log In

The first time that you access the array management 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 and assign roles to them.

Adding New Users to Hosts

User names in the array management software 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.

Adding New Users and Assigning Roles

This section describes how to add new users and assign them the storage or guest role in Sun Storage Common Array Manager. The users must first be defined on the host. For users (other than the administrative user) to access the array management software, roles must be assigned to those users in the software.

You do not have to complete this step for users automatically assigned a role by the array management software:

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.

5. Click OK.

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 Oracle Java Web Console to access the array management software with the same password that they use to log into the system.

Adding New Users in Windows

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.


Adding an Administrator User

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.


Adding an Administrative User in Windows

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. Enter a username in the User name box (root is used as an example).

5. Create a password and confirm it.

6. Uncheck the box labeled User must change password at next login.

7. Check Password never expires.

8. Click Create.

9. From the Computer Management window, select Users, right click on root, and select Properties.

10. In the Properties windows, select the Member Of tab, and click Add.

11. In the Select Groups window, enter Administrators for the object name and click Check Names.

The system displays the computer-name\Administrator group in the box labeled “Enter the object names to select.”

12. Click OK.

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 the array management software.

Adding Non-Administrator Users in Windows

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 array management software, as described in Adding New Users and Assigning Roles.

Best Practices - User Roles and Names

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.