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
99Command Console V2.5 User Guide
Invalid or Missing Fault Displays and Event Logs
Invalid or lost notifications may occur when the client system loses connection
with a subsystem. The client system receives notification about most of the
changing subsystem faults at monitored intervals. If the client system no longer
receives notification about subsystem faults, then changes to that subsystem will
not appear in the client system’s Navigation tree, Storage window (if applicable),
Fabric window (if applicable), and Event Viewer.
For example, while client system’s connection with a subsystem is broken, you
will not receive event logs about that subsystem, except the lost connection
notification.
The following list describes common causes for lost connections. After you fix
the physical and/or software problem that is listed below, you need to close and
reopen the Storage window for that subsystem to get its latest status.
■ RAS connections—Remote Access Service (RAS) connections are not
full-time. If no RAS connection exists, events are not logged to the Event
Viewer Application Log.
■ Serial controller connections—There may be a bad or missing serial cable. To
correct this situation, replace or plug in the cable.
■ Network connections—Agent may be missing or not running.
■ Network connections—There may be network discontinuity.
■ The Agent may not be properly configured for a client system.
■ If your setup includes a controller, the controller may have halted, reset, or
hung. To repair the situation, restart or replace the controller.
■ If your setup includes virtual disks, the virtual disk used for communicating
with the subsystem is no longer available.
Pager Notification Continues After Exiting the Command Console Client
You may have noticed continuous pager notification in response to subsystem
faults, even though you have exited the Command Console Client. This behavior
is normal.
AES runs as a service under Windows NT, Windows 2000, and Windows Server
2003. It continues to run after you exit the Command Console Client. AES
communicates with Agents and activates paging when a subsystem event occurs.
To stop pager notification, stop AES. For information about stopping AES, see
Chapter 2.