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
77Command Console V2.5 User Guide
Configuring the Operating System to Recognize Virtual Disk
Changes
The Client does not perform all of the system configuration necessary to make
your subsystem's virtual disks visible to the user in the operating system.
When you create or delete virtual disks using either the Command Line Interface
(CLI) or Client, you are adding or removing “disks” in the subsystem in a manner
similar to plugging or unplugging physical disk drives on the host bus. In either
case, there are certain operating system configuration actions you must perform to
make these “disks” visible or invisible to the operating system's file system.
Windows NT/Windows 2000/Windows Server 2003 Configuration
On a Windows NT, Windows 2000, or Windows Server 2003 host, after you
create or delete a virtual disk, you must perform the following steps to properly
configure the file system to recognize your changes:
1. Start the host system. This action has the effect of forcing the Disk
Administrator or Disk Management to recognize added virtual disks as raw
disks, available for use. Deleted virtual disks are no longer present.
2. Create file system partitions on your disks. When you create a virtual disk in
the controller, you can partition it at the controller level in any way you wish
as long as you create at least one partition per disk. Each of the
controller-level partitions you create becomes a virtual disk, visible to the
host. In Disk Administrator, you must create partitions on these newly added
virtual disks at the Windows NT file system (NTFS) level.
3. After you create partitions on your drives in Windows NT, Windows 2000, or
Windows Server 2003, the file system assigns each drive a unique drive letter.
Make a note of the drive letters assigned.
4. Format your disks. You must format each newly added disk.
5. Start the Agent Configurator by double-clicking its icon in the Command
Console Start Menu group.
6. Navigate through the menus until a popup appears, prompting you to scan
your subsystems. Click Yes to perform the scan and display a list of
subsystems.
7. Make sure that the access device you have been using for your subsystem still
exists. If you inadvertently deleted it, you must assign another device in its
place. If no access device exists, the Client cannot communicate with your
subsystem unless the CCL is used.