Application Notes
Command Console Version 2.3
for HSJ80 ACS Version 8.5J-2
This document summarizes features and characteristics of the Command Console Verison 2.3 for
the HSJ80 Array Controller that are not covered elsewhere in the documentaiton.
Second Edition (July 2000)
Part Number: EKHSJANAA. B01
Compaq Computer Corporation
2 Application Notes: Command Console Version 2.3 for the HSJ80 Array Controller ACS Version 8.5J
2000 Compaq Computer Corporation.
Compaq, Compaq Proliant, the Compaq logo, and StorageWorks Registered in U.S. Patent
and Trademark Office. Microsoft Windows, and Windows NT are registered trademarks of
Microsoft Corporation in the United States and/or other countries. All other product
names mentioned herein may be trademarks and/or registered trademarks of their
respective companies.
Confidential computer software. Valid license from Compaq required for possession, use,
or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software,
Computer Software Documentation, and Technical Data for Commercial Items are
licensed to the U.S. Government under vendor's stadard commercial license.
Compaq shall not be liable for technical or editorial errors or omissions contained herein.
The information in this document is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS" WITHOUT
WARRANTY OF ANY KIND. THE ENTIRE RISK ARISING OUT OF THE USE OF
THIS INFORMATION REMAINS WITH RECIPIENT. IN NO EVENT SHALL
COMPAQ BE LIABLE FOR ANY DIRECT, CONSEQUENTIAL, INCIDENTAL,
SPECIAL, PUNITIVE OR OTHER DAMAGES WHATSOEVER (INCLUDING
WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS,
BUSINESS INTERRUPTION OR LOSS OF BUSINESS INFORMATION), EVEN IF
COMPAQ HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES AND
WHETHER IN AN ACTION OF CONTRACT OR TORT, INCLUDING NEGLIGENCE.
The limited warranties for Compaq products are exclusively set forth in the
documentation accompanying such products. Nothing herein should be construed as
constituting a further or additional warranty.
Printed in the U.S.A
Application Notes - Command Console Version 2.3 for the HSJ80 Array Controller ACS
Version 8.5J-2
Second Edition (August 2000)
Part Number EK-HSJAN-AA. B01
Application Notes 3
Application Notes Contents
These application notes for the Command Console Version 2.3 cover the following topics:
Introduction, page 3
Qualification, page 6
Clarifications, page 7
Operating Constraints, page 10
Avoiding Problem Situations, page 13
Installation, page 17
StorageWorks Command Console (Navigation Tree)-- Version 2.2, page 18
Introduction
These application notes provide application information and specific information that you
should be aware of for Version 2.3 of Command Console for the HSJ80 and version 2.2 of
the StorageWorks Command Console (Navigation Tree).
Command Console for the HSJ80 is a feature-rich graphical user interface (GUI). This
document covers both the Client and Agent program modules.
Product Description
Command Console for the HSJ80 is a plug-in or standalone GUI for the HSJ80
controller-based storage subsystems.
Command Console contains two main components--Client and Agent. For most versions
of Command Console, Client includes the following components:
s Navigation Tree--The enterprise storage management window, from which you can
open multiple Storage Windows. Client can be shipped with or without the Navigation
Tree component, depending upon the application of the product.
s Storage Window--The graphical window into a specific storage subsystem. There is a
separate Storage Window type for each controller type to be managed. You must open
a separate Storage Window from Navigation Tree for each subsystem you wish to
manage.
s CLI Window--The text-based, command-line window into a specific storage
subsystem, from which you can manage the subsystem using CLI commands.
NOTE: The Navigation Tree component of Command Console is shipped as part of
Command Console for the HSJ80.
4 Application Notes: Command Console Version 2.3 for the HSJ80 Array Controller ACS Version 8.5J
Document Issues
Command Console Version 2.3 for the HSJ80 refers to the StorageWorks Command
Console (SWCC) solution for HSJ80 controllers. The term "Client" refers to
StorageWorks Command Console (Navigation Tree), Storage Window, and CLI Window.
The term StorageWorks Command Console refers to the Navigation Tree.
More Information
For complete product information on Command Console, see the product's on-line Help.
For details on the features of the controller software, see the controller documentation.
Application Notes Contents
These application notes cover the following topics:
s Minimum system configuration
s Qualification
s Clarifications--Explanation of the behavior of Command Console in certain situations
s Operating Constraints--Limitations placed on the operation of Command Console by
the nature of its design
s Avoiding Problem Situations--Information to help you avoid and recover from
unusual behavior with Command Console in certain situations and under specific
conditions
s Installation
Release Package Contents
The software release package for Command Console consists of a CD containing an
InstallShield Kit and complete user documentation.
The files are also available at the internal and external COMPAQ Web sites:
Internal - storage.inet.cpqcorp.net
External - www.compaq.com/showroom
Intended Audience
The intended audience for this document is customers who will install and use Command
Console for the HSJ80.
Application Notes 5
Identifying Your Command Console Software Revision Level
On the Help menu, click About to identify your version of Client software. The version
number will be displayed.
6 Application Notes: Command Console Version 2.3 for the HSJ80 Array Controller ACS Version 8.5J
Minimum System Configuration for the Command Console Client
Command Console Client requires the minimum system configuration shown in Table 1 to
operate:
s
Table 1 Command Console Client Minimum System Configuration Requirements
Feature Requirement
Architecture x86-compatible, 66 MHz CPU, 16 MB memory, with 1 MB free disk space
OR
Microsoft Windows NT-compatible Alpha CPU-powered host, with 1 MB
free disk space
OS Microsoft Windows NT, Windows 95, Windows 98, or Windows 2000
Monitor 15" VGA
Input devices Keyboard, mouse
Modem Hayes-compatible
Serial port (for connection Standard PC serial port capable of at least 9600 baud
via serial port only)
Network adapter (for TCP/IP-compatible network card
connection via network
only)
Controller compatibility StorageWorks HSJ80 controller
Qualification
This section describes the software and hardware with which Command Console for the
HSJ80 has been tested.
Operating Systems
C lien t
Command Console Client, Version 2.3 for the HSJ80 has been qualified with the operating
systems, platforms, and controllers shown in Table 2.
Table 2 Client Operating System and Platform Qualification
Operating System Platform Controller
Application Notes 7
Table 2 Client Operating System and Platform Qualification
DEC Celebris XL 5166DP
Microsoft Windows NT, version 4.0
HSJ80 Controller, ACS
DEC Celebris GL 6180
(with Service Pack 3 or later)
Version 8.5J
Compaq Proliant
Windows 2000
Ag en t
Command Console Client, Version 2.3, for the HSJ80 has been qualified with the
OpenVMS Agent V2.3.
For minimum system requirements and qualified operating system versions for a
particular Agent type, see the Compaq StorageWorks Command Console Getting Started
Guide.
Clarifications
This section presents clarifications on the behavior of Command Console in certain
situations.
Cautions When Configuring from a Configuration File
When configuring a storage subsystem from a configuration file, you are prompted to
choose whether or not the program initializes your virtual disks. You must choose the
appropriate option or you risk the loss of your data when the configuration file is loaded
and your subsystem is reconfigured.
The options are:
s Do not initialize virtual disks--Choose this option when your virtual disks contain
valuable user data, and you wish to retain that data. You might, for example, need to
replace a failed subsystem component such as a controller or cache module. In this
case, your subsystem configuration must be transferred to the new hardware, but you
do not wish to change any information on your storage devices themselves.
s Initialize virtual disks--Choose this option when your virtual disks do not contain user
data, or when you do not care if the data on them is lost. You might use this option
when configuring a storage subsystem from scratch, to make it match the configuration
in your configuration file.
8 Application Notes: Command Console Version 2.3 for the HSJ80 Array Controller ACS Version 8.5J
Virtual Disk Recovery from a Configuration File
When you delete a virtual disk, its member drives are all reinitialized and any user data is
lost. You cannot restore the lost data by reconfiguring your subsystem from a
configuration file because a configuration file contains only information about the
structure of a virtual disk.
Warning Message Windows
The controller software responds to problems in parsing and executing commands from
Client and Agent by returning a "Warning" message. Such messages may contain
indications such as "Command Execution Error," along with information related to the
message.
Although these messages are passed through for display by Client and Agent, they
indicate controller problems, rather than software problems.
Virtual Disk Maximum Capacity
The maximum capacity of RAID-based virtual disks is determined by the capacity of the
smallest member, not the largest, as indicated below:
s The maximum capacity of RAID 0 virtual disks is equal to the number of members
times the capacity of the smallest member.
s The maximum capacity of RAID 1 virtual disks is equal to the capacity of the smallest
member.
s The maximum capacity of RAID 0+1 virtual disks is equal to the number of members
in one stripe times the capacity of the smallest mirrorset member.
s The maximum capacity of RAID 3/5 virtual disks is equal to the number of members
minus the capacity of the smallest member.
Editing Agent Configuration Files
To ensure the proper formatting of the Agent configuration files, use only a standard VMS
editing program such as EDT or LSE.
Case Sensitivity in Client, Host, and Storage Subsystem Names
When you configure Command Console for network operation, you must enter names for
your hosts, storage subsystems, and Clients. The names used in Client and Agent must be
consistent to allow the programs to communicate with each other. This section discusses
issues of case sensitivity associated with name entry in Client and Agent.
Application Notes 9
In Client, you are required to enter host names and have the option to enter specific storage
subsystem names. In the Agent installation and configuration programs, you are required
to enter Client and storage subsystem names.
Host and Subsystem Names in Client
Enter host and subsystem names in the Client program without regard to case. The
software converts all names internally to lower case, regardless of the way you enter them.
Subsystem Names in Agent Installation/Configuration
Programs
Enter subsystem names in the Agent installation/configuration programs without regard to
case. The software converts all names internally to lower case, regardless of the way you
enter them.
Client Names in Agent Installation/Configuration
Programs
Enter Client names in the installation/configuration programs without regard to case. The
software converts all names internally to lower case, regardless of the way you enter them.
ServerWORKS Connections
You can manually configure any Agent to send SNMP traps to a host running Digital
Equipment Corporation's ServerWORKS by editing the client.ini file. Edit the file to
include the ServerWORKS host name and SNMP notification.
Running Client Via Network Connections
You can operate Client over PPP, SLIP, or RAS network connections, although some
restrictions exist related to the features. See the Operating Constraints section.
Display in VGA Mode
There are numerous issues involving the use of Client on a system with standard VGA
resolution. The Storage window requires a minimum amount of screen space to properly
display its contents. When you use VGA display resolution 640x480, screen space
becomes more limited. Compaq highly recommends that you use Client with a minimum
of SVGA (800x600) display resolution.
10 Application Notes: Command Console Version 2.3 for the HSJ80 Array Controller ACS Version 8.5J
If you must use VGA resolution, consider the following suggestions:
s If you are running Windows 95, enable the Auto Hide feature for the Task Bar. More
screen space is available when the Task Bar is not being used.
s You may not be able to see the scroll bars on the bottom of the display. You can use the
Storage window's menu settings to remove the toolbar from the display to make room
for the bottom scroll bars.
Tuning Fault Notification
For faster fault notification, remove any unused host system names in the client.ini file for
each of your Agent programs. Inactive systems may force timeouts that slow Client
response to your commands.
Operating Parameters of Partitioned Virtual disks
Keep in mind that partitioned virtual disks on any container are all closely related. They all
share the same target and operating parameters of the container. If you change any of this
information for one partition on the container, you change it for all the partitions on that
container.
Documentation for Compaq OpenVMS and Windows NT
The Adobe Acrobat Reader is not available for the Compaq OpenVMS operating system
or the Windows NT operating system on Compaq Alpha systems. The Agent
documentation is provided in Word for Windows and Postscript formats for viewing and
printing.
Operating Constraints
This section describes the operating constraints for the Command Console software. An
operating constraint is a limitation placed on the operation of the controller by the nature
of its design. Keep these constraints in mind to avoid problems and to help you obtain the
maximum performance.
Local Host Bus Connections Not Supported
Local host bus connections are not supported in Command Console for the HSJ80.
Application Notes 11
Code Load Supported
The HSJ80 controller supports software upgrade, also known as Code Load.
Connection Limitations
Local serial connections are only available with standalone Storage Windows. You cannot
use the Navigation Tree to connect locally to a subsystem.
Client Features available with Different Connection Types
Because of the nature of the connections that you can use between Client and your
subsystems, the features available with each connection type vary slightly. Some
connection types impose limitations on Client's features, as noted in Table 3.
Table 3 Feature Limitations
Feature Create Delete virtual Fault Events: Fault Events: Fault Events:
virtual disk disk Client Visual Paging NT Event
Connection
Notification Notification Logging
Type
Local Serial Supported Supported Supported Not Supported Not Supported
Connection
(Navigation
Tree and
Agent not
used)
Supported Supported Supported Supported Supported
Remote
Network
Connection
(Client
running on a
PC remote
from Agent on
a host)
12 Application Notes: Command Console Version 2.3 for the HSJ80 Array Controller ACS Version 8.5J
Table 3 Feature Limitations (Continued)
Supported
Supported
Supported Supported Supported
Remote RAS
reliably at
reliably only
reliably only
Connection
host end only.
while RAS is
while RAS is
(Client
Some events
intact. Some
intact. Some
running on a
may be
events may
events may
remote PC
missed at
be missed
be missed
with a dialup
Client end
while dialup
while dialup
network
while dialup
connection is
connection is
connection)
connection is
broken.
broken.
broken.
Delayed Event Notification on RAS Connections
Visual fault notification, paging, and NT Event Logging may be delayed significantly in
situations where RAS connections are used for multiple Clients. An Agent with multiple
Clients in its CLIENT.INI file must poll each Client whenever a fault occurs. Any Clients
not currently network-connected significantly delay this process because Agent must wait
for their connections to time out before moving on to the other Clients.
To avoid this situation, set the notification_method parameter for each Client in the
CLIENT.INI file to "0" to defeat event fault notification.
CLI RUN Commands
Do not issue RUN commands in the CLI Window. Use only a maintenance terminal
connection to issue RUN commands.
"What's This" Feature Help not Available
The Windows Help 4.0 "What's This" feature is not available in this release of Client.
DHCP Not Supported
Client cannot use a DHCP-generated network address.
Application Notes 13
Avoiding Problem Situations
In certain situations and under specific conditions, you may experience unusual behavior
with Command Console. This section presents information to help you avoid such
situations and recover from them if they occur.
Agent Sensitive to Alpha Node Names
Agent may not accept some node name forms, particularly those with embedded
underscores. If Agent rejects a node name, try other names until Agent accepts one of
them.
Application Errors When Restarting Agent
You may experience an "application error" when attempting to restart Agent after
changing the Agent configuration files. Either of the following issues may be the cause:
s The CLIENT.INI file must end with a carriage return. If any other character is used to
terminate the file, an application error may occur.
s The STORAGE.INI file must not end with a carriage return. If a carriage return
terminates the file, an application error may occur.
Client Access Changes Not In Effect After CLIENT.INI Is Changed
After manually editing or changing the Agent client.ini file with a configurator program,
you may notice that your Clients' access has not changed. To place your changes in effect,
you must restart Agent after editing any of the Agent configuration files.
Always Restart After Controller Replacement
If you replace either of the controllers in your subsystem, you must restart the Agent. See
your Agent documentation for details on how to properly restart the application.
Storage Window Won't Open
If you cannot open a Storage Window from the Navigation Tree or in standalone mode, the
access parameter in the Agent for the subsytem you wish to connect to is probably set to
"0" disabling Storage Window access. Use the Agent configuration script or edit the
CLIENT.INI file to enable access to the subsytem.
14 Application Notes: Command Console Version 2.3 for the HSJ80 Array Controller ACS Version 8.5J
Configuration File Deleted on Reinstallation or Upgrade
Make sure to save a copy of the current SWCC2.MDB file to another directory if you
intend to reinstall or upgrade Client. If you uninstall the program, you may inadvertently
delete the SWCC2.MDB file. This file contains your configuration of host systems and
storage subsystems used in the Navigation Tree window display.
To reinstate your current Navigation Tree window configuration after installing a new
version of Command Console, copy the saved SWCC2.MDB file back to the directory in
which you installed Command Console.
Invalid Network Port Numbers During Installation
During Client or Agent installation, you may experience an error if the installation
program cannot find an acceptable pair of network port numbers.
Client uses Windows sockets (sometimes called "network ports") to communicate with its
Agents. The socket numbers for the Client and Agent must match for network
communication to occur.
In Windows NT, the socket numbers are assigned in the services file in the
\WINNT\SYSTEM32\DRIVERS\ETC subdirectory. In Windows 95 or Windows 98, the
socket numbers are assigned in the services file in the \WINDOWS directory. In
OpenVMS, the socket numbers are assigned in the SWCC_CONFIG.COM file in the
SYS$MANAGER: directory. If you experience a conflict with the socket numbers, you may
edit the file manually.
The default socket numbers for Command Console are "4998" and "4999". If you are
installing either Client or Agent and these numbers are already taken by another
application, the installation program prompts to warn you that you must choose another
pair.
To select another pair for Client, open the file containing the sockets in an ASCII editor
after you have installed Client. Pick two numbers above 1023 that are not already used in
the file and add the following two lines:
spgui number1/tcp # StorageWorks Command Console
spagent number2/tcp # StorageWorks Command Console
Note that the port numbers which you select must match the port numbers used by all of
the Clients to which you wish to connect your Agent.
See the installation guide for a particular Agent type for instructions on configuring the
services file on its associated platform.
Application Notes 15
Invalid Cache Errors
Your controller module, cache module, and subsystem devices all contain configuration
information used to keep their activity synchronized. This data is called metadata. The
controller software reports an invalid cache error on the affected controller in situations in
which there is an mismatch between the metadata in the controller module and in a cache
module that contains unwritten data. This mismatch can result in loss of the unwritten
cache data if the error is not properly cleared.
CAUTION: Use extreme care in responding to the Command Console invalid cache
error prompt. If you inappropriately instruct the program to delete unwritten cache
data, you may lose valid user data.
Client displays a message and prompt box when an invalid cache error occurs. You must
tell the program whether or not to delete unwritten cache data as the error is cleared. If you
are not familiar with the proper treatment of unwritten cache data, see the information in
the on-line Help documentation under the topic "Invalid Cache Errors."
Communications Failure on Power Up with Low Batteries
If the battery in the cache is discharged when you power up the controller, the controller
may produce an invalid cache error. If you are using Client as your controller interface at
that time, the error may prevent communication with the controller. In this case, the
controller status icon in Client changes to yellow, and the program displays a window
containing error information.
If this happens, make sure Client is set up with the proper communication parameters. If
Client is configured properly for your controller, you must exit Client and use a normal
controller maintenance terminal to clear the error with the CLEAR ERRORS
INVALID_CACHE command before you can use the controller. See your controller
documentation for instructions on use of the CLEAR ERRORS INVALID_CACHE
command.
After you have cleared the invalid cache error, you can use either a normal maintenance
terminal or Client as your controller interface.
16 Application Notes: Command Console Version 2.3 for the HSJ80 Array Controller ACS Version 8.5J
Lost Connections Cause Invalid or Missing Fault Displays and Event
Logs
Client receives notification for most types of subsystem fault conditions on the next
monitor interval after they occur. You may experience invalid or lost notifications in
situations in which the connection between Client and its subsystems is broken. Any
Windows NT Event Logs that might have occurred while the connection was broken are
also lost.
If the connection between Client and its subsystems is broken for any reason, Client may
continue to display faults that are cleared while the connection is broken. Similarly, faults
that occur while the connection is broken are not displayed at all.
To clear an invalid fault indication in Client, you must exit and restart Client once its
subsystem connections are intact. To avoid lost fault indications, make sure that Client's
connections with its subsystems are monitored and maintained.
Broken connections can occur for a variety of reasons, including the following:
s RAS connections--The RAS connection is not a full-time connection. Events that
occur during a period when the RAS connection is not made are not logged to the
Event Logging facility of Windows NT.
s Serial controller connections--Bad or missing serial cable. To correct this situation,
plug in or replace the cable.
s Network connections--Agent missing or not running, lack of network continuity, or
Agent not properly configured for your Clients.
s "This controller" halted, reset or hung--To correct this situation, restart or replace
"This controller".
No Agent Notification Causes Invalid or Missing Fault Displays
For some types of faults, Agent does not send Client notification of changes in status as
they occur. Client displays the fault information it last received. Following are three
situations in which a fault can occur without immediate display in Client:
s The "OTHER controller" fails or is shut down.
s A cache battery on either controller fails or goes low.
s A cache module fails.
When these conditions occur, you can get current status by viewing the subsystem in
question. To do this, on the View menu, click Refresh.
Application Notes 17
Incompatibility with Windows 95 Monitor Energy Saver Mode
If you are using Windows 95, do not use the "energy saver" (low power) monitor mode
which is available with some monitors and graphics adapters. Your system may lock up
with a blank screen when the energy saver mode is activated. However, you may use any
screen saver you wish with Command Console.
Installation
For complete instructions on installing Command Console for the HSJ80, see the Getting
Started guide for your version of the software.
You can install Command Console for the HSJ80 as a standalone product or under an
existing Command Console installation. The procedure for each is the same.
Version 2.3 Client and Agent components are not supported when operating with Version
1.x components. You must completely uninstall previous versions of Command Console
before installing Version 2.3.
18 Application Notes: Command Console Version 2.3 for the HSJ80 Array Controller ACS Version 8.5J
StorageWorks Command Console (Navigation Tree)--
Version 2.2
NOTE: The Navigation Tree is included with your Command Console package for the HSJ80.
Since you may have the Navigation Tree, applicable application notes are included. In this
section, Command Console Client refers to the Navigation Tree.
These application notes cover version 2.2 of the Command Console Client. They include
notes specific to the Command Console, such as installation, removal of the Client, and
troubleshooting.
Installation Notes
Client Installation Claims System Files Are Out of Date
After Installing New Files
SWCC 2.x Client software requires at least version 2.30.0.0 of the OLEAUT32.DLL file. If
the version is older a dialog box tells you that:
s Systems files are out of date.
s It will install new system files.
s Rerun the installation after the system reboots.
With some versions of OLEAUT32.DLL, the version check will fail and the installation
program will not overwrite with the newer file. This action will cause the install to always
say that the system files need to be upgraded and to never allow you to install SWCC. To
fix this, ensure that a proper version of OLEAUT32.DLL is installed by installing a clean
version of the operating system.
Invalid Network Port Numbers During Installation
During Client or Agent installation, the SWCC installation may display a message stating
that it cannot upgrade the services file. This happens if it finds an entry in the local
services file with the same number as the one it wants to add, but with a different name.
If the SWCC installation finds an entry in the local services file with the same name as the
one it wants to add, it assumes the one already in the file is correct. If the SWCC
installation does not find the name and the port is already in use, you need to add the
appropriate name. In that case, you must get port numbers that are appropriate for the
network, and manually add them to the services file.
Application Notes 19
SWCC Clients and Agents communicate by using network port numbers (sockets). The
SWCC installation procedures attempt to add entries into each system list of services (the
services file, or for UCX, the local services database). The default port number for the
Command Console Client is 4998. It appears in the services file as follows:
Spgui . . . . . . . . . . . . 4998/tcp #Command Console
Contact your network administrator if one of the following is occurring:
s The network ports or names are being used.
s The Network Information Services (NIS) are being used to provide named port lookup
services.
NOTE: Port names and numbers must be exactly the same on all systems that need to
communicate with each other on the network.
Stand-Alone Installations
After doing a stand-alone install of a device-specific Client, exit Command Console
before adding or accessing a system with that type of device. Command Console will then
recognize the installation.
"There is no disk in the drive" Message
When you install the Command Console Client, the software checks the shortcuts on the
desktop and in the Start menu. If you have Windows NT, the installation will check the
shortcuts of all users of that computer, even if they are not currently logged on. You may
receive an error message if any of these shortcuts point to empty floppy drives, empty
CD-ROM drives, or removable disks that are no longer present. If you receive an error
message, take the following actions:
1. Ignore the error message by clicking Ignore.
2. Replace the removable disks, place a disk in the floppy drive and a CD-ROM in the
CD-ROM drive, then click Retry.
Uninstall Notes
Configuration File Deleted on Reinstallation or Upgrade
If you intend to reinstall or upgrade Client, save a copy of the current SWCC2.MDB file to
another directory . If you uninstall the program, you will delete the SWCC2.MDB file.
This file contains your configuration of host systems and storage subsystems used in the
Navigation Tree window.
To reinstate your current Navigation Tree window configuration after installing a new
version of Command Console, copy your saved SWCC2.MDB file back to the directory to
which you installed Command Console.
20 Application Notes: Command Console Version 2.3 for the HSJ80 Array Controller ACS Version 8.5J
Command Console Client Uninstall Does Not Remove
AsyncEventService Entries
Before uninstalling the Command Console Client, remove the AsyncEventService entries.
This prevents the computer from sending you messages during boot time about a service
failing to start.
To remove the entries, under Windows 98 and Windows 95, click Start, then Settings, then
Control Panel, and then Async Event Service and uncheck "Automatic startup on boot ".
Under Windows NT, change to the directory where you installed the Command Console
Client, enter the "AsyncEventService remove" command, press Enter key, and then
remove the Command Console Client.
Command Console Client Troubleshooting
Authorization Error when Adding the Server to the
Navigation Tree
If you receive an authorization error when you add an agent system to the Navigation Tree,
your client system may be missing from the Agent's list of client system entries. If you
have more than one type of Agent installed on that agent system, the name of your client
system must be on each Agent's list of client system entries.
Help Files Still Appear after Uninstall
After you have uninstalled a storage subsystem Client, its help files will still appear.
Delete the CCONSOLE.GID file, which may be hidden (In Windows Explorer, click View,
then Options, and then View). This file will regenerate the next time you use the Client's
help files.
Some Graphics Do Not Scale Properly with Large Fonts
It is recommended that you set the display to small fonts when using the SWCC client
software on Windows 95 and Windows NT. Some of the graphics do not scale as well
when large fonts are used.
Windows 95 Memory Leak
When you run SWCC on Windows 95, the operating system will gradually increase its use
of memory, especially when SWCC opens and closes a large number of sockets. Microsoft
has released an upgraded version of KERNAL32.DLL that corrects this situation. This file
is available from the following website:
www.microsoft.com/windows95/downloads/contents/wuadmintools/s_wunetworkingtools/
w95kernel32/default.asp
Application Notes 21
The following is the name of the file:
kernel32.dll version 4.00.951 (7/29/97, 337016 bytes) or later
NOTE: Microsoft may not support the Kernel32 upgrades on all versions of Windows 95. Check
Microsoft's website to determine if it is supported for your operating system revision and
language kit. Do not install the kernel32 upgrade unless Microsoft supports it.
Troubleshooting Connection and Access Problems
This section documents known connection problems and suggests some solutions. SWCC
is a TCP/IP socket-based application. As a result, SWCC requires that each node running
an SWCC Client or Agent must have access to a valid hosts file or Domain Name Service
(DNS) server. The valid hosts file must include at least the system running SWCC and any
other systems running an SWCC Client or Agent that it will connect to.
Dynamic Internet Protocol Address Allocation Not Supported
SWCC will not function properly if the client systems or agent systems are obtaining an IP
address dynamically because the Dynamic Host Configuration Protocol (DHCP) is not
supported. RAS servers and IP tunneling servers are supported only if they are configured
to nondynamic IP addresses.
WINS Not Supported
Window s Internet Name Service (WINS) is a name resolution service available for
Windows NT, Windows 98, and Windows 95. SWCC does not support WINS. Each
system using SWCC must have access to either a DNS server or a valid hosts file.
Access Denied Problem
This section covers some of the most common reasons for a Client to receive an "ACCESS
DENIED" message when it attempts to add an agent system to the Navigation Tree.
Client System Not on Agent's List
The client system is probably not on the authorized client system list for the Agent. For
information on adding the client system to the list of client system entries for an Agent,
refer to the Installation Guide.
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.
22 Application Notes: Command Console Version 2.3 for the HSJ80 Array Controller ACS Version 8.5J
Aliases Are Not Checked
When SWCC Agents scan the Client authorization list, aliases are not checked. The entry
in the Client authorization list must match that returned by a gethostbyaddr call in the
hostent h_name field. SWCC will not walk the hostent alias list to check if an alias may
match the Client authorization list.
Entry in the Client Authorization List Does Not Match
Generally, the entry in the Client authorization list for an Agent must match what
gethostbyadd () will return in the hostent h_name field when executed
on the Agent system. If hosts files are not exactly the same on all systems, the h_name
returned may vary on different Agent systems.
In some situations, you can configure the way a system uses DNS and its local hosts file.
Please refer to your system documentation to find how your system is configured. Some
systems may be configured to do the following:
s Check the local hosts file first, then go to DNS.
s Go to DNS first, then check the local hosts file.
s Ignore DNS even if configured.
s Ignore the local hosts file.
The best way to verify what is needed 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 (). Remember, the dynamic IP address allocation is not
supported.
Adding a New System by Using Internet Protocol Address Crashes
The SWCC Client may crash when you attempt to add a system by using the agent
system's Internet protocol (IP) address, rather than the agent system's 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 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, the solution is not to use the IP address. Fix your DNS server
configuration, or if that is correct, confirm the DNS server knows the agent system. If you
are not using DNS, make sure the agent system is in the client system's hosts file.
Remember, WINS is not supported by SWCC.
Application Notes 23
"No Agent Running" Message Received When Adding a
System to the Navigation Tree
When trying to add a new system to the Navigation Tree, you may receive a message
stating "No Agent running on specified system." This message can appear for several
reasons. The error most likely occurred as a result of one of the following:
s Wrong system name was entered
s Agents were not installed on the system entered
s Agents were installed on a system that stopped functioning
s 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 a 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\DigitalEquipmentCorporation\Command
Console\AppletManager
You should see a series of keys for supported products.
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 an SWCC port was already in
use. A list of port numbers and their default values is contained in the "Network Port
Assignments" section of Appendix A in the Installation Guide.
If you change the network card on a computer running Windows 98 or Windows 95, your
services file may be deleted and replaced by the version on the Windows 98 or Windows
95 distribution kit. In this case, you will need to add the entries required for SWCC. For a
list of the ports and their defaults, refer to the "Add System Error" section in Appendix A
of the Installation Guide.
| EK-HSJAN-AA
|
