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
104 Command Console V2.5 User Guide
Multiple Communication Lost Messages
On a Client system, AES monitors every agent system that is included in the
Client’s Navigation tree. If an Agent fails on a system that AES is monitoring,
AES generates a page and an event log entry for the Agent at every polling
interval indicating that communication has been lost. To stop the page and event
log entries, remove the system entry in the Command Console’s Navigation tree.
Event Updates
You must manually update any node added to the Navigation tree by using cluster
alias and any Storage window that opens from that cluster alias. If you have a
pager configured for automatic updating, you must add the individual nodes of the
cluster to the Navigation tree.
Multiple Pages
AES may send multiple pages if an Agent moves from a failing node to a working
node. When the Agent fails over, a TCP/IP peer reset error may appear in the
active Storage window that had been connected to that Agent.