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
95Command Console V2.5 User Guide
8. Click the WINS Address tab. If your computer uses DNS, you do not need to
have Enable LMHOSTS Lookup selected.
Note: If WINS servers are available on the network, the LMHOST file can be used.
SWCC does not support WINS.
9. Check the General tab in the Internet Protocol (TCP/IP) Properties
window to determine the IP address for the system,.
10. Click the DNS tab in the Advanced TCP/IP Settings window to determine
the full name of the system.
For other operating systems
Generally, the entry for an Agent in the Client authorization list must match what
gethostbyaddr(<client IP address>) returns in the hosts agent h_name field if
gethostbyaddr(<client IP address>) is executed on the Agent system. If the hosts
files names on all systems are not identical, the
h_name returned may vary on
different Agent systems. For example,
xxx.xxx.xxx.xxx client.somewhere.com client
returns client.somewhere.com in the h_name field, but
xxx.xxx.xxx.xxx client client.somewhere.com
returns client in the h_name field.
The best way to determine what to use for a Client name in the Client
authorization list is to write a program that runs on the Agent system and prints
the
h_name field returned by gethostbyaddr(<client IP address>).
Multiple Agents
If the Agent system is running multiple SWCC Agents (for example, to support
different controller types), the client system must be authorized for all Agents. If
the client system is missing from any authorized Client list of an Agent, that
Agent cannot be added to the Navigation tree.