HP StorageWorks Command Console V2.5 User Guide (AA-RV1UA-TE, March 2005)
Table Of Contents
- Contents
- About this Guide
- About SWCC
- Using Command Console
- Setting Up Notification
- Required Components for Notification
- Setting Up Pager Notification
- Using SWCC with a Third-Party Storage Management Program
- Using Event Logging on the Client System to Monitor Your Subsystem
- Interpreting Agent Email Messages
- About Event Information Fields
- Mapping State Change Digits to RAID System Components
- Table 11: State Change Digit Position and Corresponding RAID system Component
- The First Digit of the State Change Field (Overall RAID System)
- The Second Digit of the State Change Field (Disks)
- The Third Digit of the State Change Field (Power Supply)
- The Fourth Digit of the State Change Field (Fans)
- The Fifth Digit of the State Change Field (Battery)
- The Sixth Digit of the State Change Field (Temperature)
- The Seventh Digit of the State Change Field (This_Controller)
- The Eighth Digit of the State Change Field (Communications LUN)
- The Ninth Digit of the State Change Field (Other_Controller)
- The 10th Digit of the State Change Field (External Factors)
- The 11th Digit of the State Change Field (Logical Units)
- Using the Storage Window
- Why Use the Storage Window?
- Configuring a Controller
- Creating Virtual Disks
- Deleting Virtual Disks
- Modifying Virtual Disks
- Configuring the Operating System to Recognize Virtual Disk Changes
- Setting Passwords and Security Options (Network Only)
- Managing and Creating Spare Devices
- Using Configuration Files
- Understanding the Icons
- CLI Window
- Integrating SWCC with Insight Manager
- Troubleshooting
- Troubleshooting Connection Problems
- Invalid Network Port Numbers During Installation
- Network Port Assignments for UNIX-Client/Server Systems
- DHCP and WINS
- Connecting Via the Host SCSI Port
- “Access Denied” Message
- Adding New System by Using Internet Protocol Address May Cause Client to Stop Responding
- “No Agent Running” Message When Adding System to the Navigation Tree
- Troubleshooting the Client
- Authorization Error When Adding an Agent System
- Cannot Open Storage Window
- Client Hangs When LUN Is Deleted
- CLI RUN Commands
- Event Notification for Subsystems Connected to a Client System
- Invalid or Missing Fault Displays and Event Logs
- Pager Notification Continues After Exiting the Command Console Client
- Reconfiguration After Controller Replacement
- Some Graphics Do Not Scale Well with Large Fonts
- Starting Client from the Command Prompt
- Warning Message Windows
- Virtual Disk Recovery from a Configuration File
- Troubleshooting the HS-Series Agents
- Cluster Integration for the HS-Series Agents
- Troubleshooting Connection Problems
- Using the Command Console LUN
- Interpreting SNMP Traps
- Glossary
- Index
Using the Storage Window
78 Command Console V2.5 User Guide
8. Click Next until you can exit the configurator.
9. Choose the Services option in the Windows Control Panel for Windows NT,
or Computer Management in Administrative Tools for Windows 2000 and
Windows Server 2003.
10. Scroll down to highlight the Steam entry.
11. Click Stop and wait for a prompt indicating that the service is halted.
12. Click Start and wait for a prompt indicating that the service is started.
13. Exit Control Panel.
Windows NT, Windows 2000, and Windows Server 2003 now recognizes any
changes you made in your virtual disk configuration.
UNIX-Based Configuration
On a UNIX-based host, after you create or delete a virtual disk using the Client or
CLI, you must perform the following steps to properly configure the UNIX file
system to recognize your changes:
1. Restart the host system. This action has the effect of forcing the file system to
recognize added virtual disks as raw disks available for use. Deleted virtual
disks are no longer present.
2. (Optional) Create file system partitions on your disks. When you create a
virtual disk in the controller, you have the option to partition it at the
controller level in any way you wish. Each of the controller-level partitions
you create becomes a virtual disk, visible to the host.
3. Afterward, if you desire, you can partition these newly added virtual disks at
UNIX's file system level. Use the appropriate commands for your operating
system version to perform this task. Once you have partitioned your drives in
UNIX, the file system assigns each drive a unique drive identifier.
4. Stop and Restart the Agent. Using the Agent configuration script, you must
stop and restart the Agent running on your UNIX host, using the configuration
program. In the program, you must choose the option to create a new
storage.ini file. This action updates the Agent to recognize any virtual disk
changes you have made.