Compaq StorageWorks Getting Started RAID Array 3000 for Microsoft Windows Installation Guide (AA-RACZD-TE, January 2001)

C-14 Getting Started RAID Array 3000 for Microsoft Windows Installation Guide
Compaq Confidential – Need to Know Required
Writer: Bob Young Project: Getting Started RAID Array 3000 for Microsoft Windows Installation Guide Comments:
Part Number: AA-RACZD-TE File Name: -appc Usage Notes and Troubleshooting.doc Last Saved On: 12/5/00 7:31 AM
■
The specific Client required to support the Agents, running on the agent
system, was not installed. For example, if the agent system only has a
Fibre Channel Interconnect Agent and the client system has only an
HSZ22 Client, the “No Agent Running” message will appear.
To check if Client support for an Agent had been installed, look at the following
registry key:
HKEY_LOCAL_MACHINE\Software\DigitalEquipmentCorporatio
n\
Command Console\AppletManager\HSZ22
■ Port names and numbers in the services file may be missing or may not
match between Client and Agent. This may occur if the default value for
a SWCC port was already in use. There is a list of port numbers and
their default values in “Network Port Assignments”
■ If you have entered the host name in the hosts file, verify that it is
spelled correctly and that it is in lowercase letters. The host name is not
required in this file, but TCP/IP will look here first when resolving host
names. The hosts file is on the client system in the following directory:
On Windows NT - \winnt\system32\drivers\etc
Make sure you have the correct port numbers in the client’s services file. See
the section “Network Port Assignments” Make sure the Command Console
Agent on the host system is using a correct host name to recognize the Client.
If the host system is Windows NT, run the Agent Configuration Utility
(H22AgntCfgWiz.exe) or examine the client.ini file on the host system. On
other host systems, look at the client.ini file.
■ If you are using a Windows NT Client, run netstat at the MS-DOS
prompt to check the TCP/IP active connections.
■ Check the Client name that the Agent’s host system sees is the same as
the name specified in the Agent's client.ini file. Run netstat at the MS-
DOS prompt on the Agent, if you are using a Windows NT host system,
and check the TCP/IP active connections.
■ Make sure the Agent’s host system has been configured to recognize the
Client by its assigned name rather than by an alias name. If the host
system has been configured to recognize the Client by an alias name,
remove the alias name from the system’s “hosts” file.
NOTE: Always reboot the Client system after making changes to the hosts or services file.