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
Troubleshooting
102 Command Console V2.5 User Guide
Cluster Integration for the HS-Series Agents
This section describes how to integrate a Windows NT cluster with SWCC.
How to Integrate SWCC with Windows NT
When you integrate a Windows NT cluster with SWCC, you can configure and
monitor a subsystem within the cluster environment. You need the following to
perform cluster integration:
■ A valid, working stable cluster
■ An Agent installed on a disk that is on a non-shared SCSI bus
■ An Agent on each cluster node of the cluster
To integrate a Windows NT cluster with SWCC:
1. Click Settings under the Start menu, and then click Control Panel.
Double-click Services.
The Services window opens.
2. Choose Steam from the drop-down list for the Service field, and then click
the Stop button. Steam, which stands for StorageWorks Enterprise Array
Manager, is the name for the HS-Series Agent service. This action stops
Steam, and its status no longer displays as Started in the Services window.
3. Click Startup. A smaller Services window opens.
4. Choose Manual, and then click OK to disable the automatic start of the
service.
You are returned to the main Services window.
5. Click Close to exit the Services window.
6. Repeat steps 1-5 for each cluster node.
7. Click the Cluster Administrator Utility entry under the Administrative
Tools group.
The program’s main screen opens.
Note: Microsoft develops Cluster Administrator Utility. For further information about
the software, see the appropriate documentation.