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
Glossary
133Command Console V2.5 User Guide
maximum block
transfer
For HS-series controllers, the virtual disk parameter that
specifies the maximum number of data blocks to be cached
before writing data to virtual disk members. A data transfer
greater than this size is not cached and is written immediately to
disk. Valid values are 1-1024 (blocks).
member Any device used in a virtual disk based on multiple devices.
Any device in the device group on which the virtual disk is
based.
metadata Special data written to a device for the purpose of controller
administration. Metadata improves error detection and media
defect management for a device. It is also used to define device
and virtual disk configuration.
mirrored cache Some controllers offer high-performance cache hardware that
can be set to operate in mirrored mode. In this mode, the cache
data is duplicated and stored in cache memory in physically
separate locations. If one copy of the data becomes corrupted or
unavailable for some reason, the other copy is available for use.
A mirrored cache configuration provides complete protection
for cached data. However, the cache memory effectively
contains twice as much data for each host request, so the
effective size of the cache is cut in half.
mirrored virtual disk A group of storage devices organized as duplicate copies of
each other. Mirrored virtual disks provide the highest level of
data availability at the highest cost. Another name for RAID 1.
mirroring The simplest form of data redundancy. Two or more devices
form a mirrored device group. Each device is an exact copy of
the other.
For read requests, data can be read from either device therefore
increasing the throughput. Both devices can handle different
requests simultaneously.
For write requests, data is written to both devices. If one device
fails, all reads/writes are executed on the mirrored device
group’s other device. Therefore, mirroring provides excellent
availability (unless the second device fails before the first
(failing) device can be repaired or replaced).
Sometimes called shadowing.
The mirroring technique can also be applied to cache memory.