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
137Command Console V2.5 User Guide
RAID 3 RAID 3 virtual disks use parity for data redundancy. A RAID 3
virtual disk is a type of striped parity virtual disk.
In a RAID 0 virtual disk, host data is divided into strips spread
in a stripe across virtual disk member devices. An additional
strip for parity information is appended to each stripe. This
technique allows much faster read and write performance than
does reading and writing to a single device. A three-device,
RAID 3 virtual disk has potentially three times the bandwidth
of a single device because three separate, small pieces of host
data move in parallel.
In addition, because each data stripe is protected by parity
information, there is a significant level of data redundancy for
high availability. Some RAID 3 configurations use a dedicated
parity device, but most controllers intersperse the parity strips
within the data strips to maximize the read performance.
RAID 3 virtual disks provide high performance and high
availability at reasonable cost. They are optimal for use in
applications requiring relatively high data transfer rates and
having relatively low I/O request rates.
RAID 3/5 RAID 3/5 sets are enhanced stripesets – they use striping to
increase I/O performance and distributed-parity data to ensure
data availability.
RAID 3/5 sets are similar to stripesets in that the I/O requests
are broken into smaller “chunks” and striped across the disk
drives. RAID sets also create chunks of parity data and stripe
them across all members of the RAIDset. This parity data is
derived mathematically from the I/O data and enables the
controller to reconstruct the I/O data if a single disk drive fails.
Thus, it becomes possible to lose a disk drive without losing its
data it contained. Data can be lost, however, if a second disk
drive fails before the controller replaces the first failed disk
drive and reconstructs the data.