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
About SWCC
37Command Console V2.5 User Guide
Local Client/Agent Network Connection
You can run both the Client and Agent on the same Windows NT, Windows 2000,
or Windows Server 2003 host machine and connect them using a network
connection. By doing so, you can create a local connection to take advantage of
the Agent's event notification features. No special installation instructions are
necessary to implement this type of connection. Install each component as if the
Client were to run on a system remote from the host machine.
Because the Client runs only on Windows NT, Windows 2000, and Windows
Server 2003 systems, and the Agent runs on Windows NT, UNIX-based systems,
and OpenVMS, you can implement this type of connection only on a Windows
NT system. Also, you cannot use a Client with a local connection of either type
while an Agent is running on the local machine.
Note: SWCC is no longer supported on Novell NetWare systems with HBA
281540-B21 (3R-A3750-AA).
RAS
Connect
(Client
running on
a remote PC
with a
dialup
network
connection)
Supported
but not
recom-
mended.
Follow-up
operating
system
configura-
tion cannot
be
performed
remotely.
Supported
but not
recom-
mended.
Follow-up
operating
system
configura-
tion cannot
be
performed
remotely.
Supported
reliably
only while
RAS intact.
Some
events may
be missed
while
dialup
connec-
tion is
broken.
Supported
reliably
only while
RAS intact.
Some
events may
be missed
while
dialup
connec-
tion is
broken.
Supported
reliably at
host end
only. Some
events may
be missed
at Client
end while
dialup
connec-
tion is
broken.
Supported
Table 6: Feature Limitations (Continued)
Feature
Connection
Type
Create
Virtual
Disk
Delete
Virtual
Disk
Fault
Events:
Client
Visual
Notify
Fault
Events:
Paging
Notify
Windows
NT/
2000/
Server
2003
Fault
Events:
Event
Logging
Email
Notify
(UNIX/V
MS only)