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
Interpreting Agent Email Messages
62 Command Console V2.5 User Guide
0—Everything is fine.
1—Battery state went from bad to good.
2—Battery state went from good to bad.
The details of the battery failure follow in parentheses, in the format:
controller_id:state
where controller_id is the SCSI ID of the reporting controller (in other words,
the cache battery failed for the other controller), and
state is one of the
following:
Good—Battery is good.
Low—Battery voltage is low.
Fail—Battery has failed.
In this example, the cache battery for the controller with SCSI ID 6 failed.
The Sixth Digit of the State Change Field (Temperature)
The sixth digit of the state change field reports temperature state changes.
Example:
WARNING: -
Suncity HSG80 10000200000 HSG80 temp(0:2:2) (SP_MONITOR:
Monitor_Subsys)
The sixth digit can have one of three values:
0—Everything is fine.
1—Temperature state went from bad to good.
2—Temperature state went from good to bad.
The details regarding the temperature change follow in parentheses, in the format:
cabinet_number:sensor_type:state
where cabinet_number is the cabinet ID from 0-1, sensor_type is the EMU
sensor (sensor 1 or sensor 2), and
state is either of the following:
1—Temperature went from bad to good.
2—Temperature went from good to bad.
In this example, an adverse temperature change is detected by sensor 2 of the
main cabinet.