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
96 Command Console V2.5 User Guide
Adding New System by Using Internet Protocol Address May Cause
Client to Stop Responding
The SWCC Client may stop responding if you attempt to add a system by using
the agent system’s IP address rather than its node name. This occurs when the
client system does not have a DNS server configured that knows the agent system,
and the agent system is not included in the client system’s hosts file. To correct
this situation, add the agent system to the hosts file on the client system.
If you receive an “Invalid host” or “Host not known” message when you attempt
to connect to an agent system, do not enter the IP address. Correct your DNS
server configuration. If it is correct, confirm that the DNS server knows the agent
system. If you are not using DNS, verify the agent system is in the client system’s
hosts file.
“No Agent Running” Message When Adding System to the Navigation
Tree
While attempting to add a new system to the Navigation tree, you may see the
message “No Agent running on specified system.” This message may appear for
several reasons. The following are the most likely:
■ The wrong system name was entered.
■ The Agent was not installed on the entered system.
■ The Agent was installed on a system that stopped functioning.
■ Client and Agent port names and numbers in the services file may not match.
This may occur if the default value for an SWCC port was already in use. See
"Invalid Network Port Numbers During Installation", page 91, for more
information.
■ The specific Client required to support an Agent is not installed. For example,
if the Agent system has only a KZPCC Agent and the client system has only
an HSZ22 Client, the “No Agent Running” message is displayed.
To verify that there is Client support for an Agent, look at the following
registry key:
HKEY_LOCAL_MACHINE\Software\DigitalEquipmentCorporation\Command
Console\AppletManager
You should see a series of keys for supported products.
■ Make sure the system names used for the Client and the Agent match exactly.
As a general rule, use lowercase letters when entering names.