HP StorageWorks Interface Manager and Command View TL Installation Guide (March 2005)
Table Of Contents
- Title
- Contents
- About this Guide
- 1: Introduction
- 2: Hardware Installation
- Preparing the Installation
- Installing the Expansion Cage in the ESL Series Library
- Installing the Fibre Channel Interface Controllers into the Expansion Cage
- Installing the Interface Manager Card into the Expansion Cage
- Connecting the Cables
- Connecting the Interface Manager Card to the Fibre Channel Interface Controllers
- Connecting the SCSI Bus Cables
- Connecting the Fibre Channel Cables
- Connecting the Interface Manager Card to the LAN
- Connecting the PC or Laptop
- Completing the Hardware Installation
- 3: Configuration and Software Installation
- 4: Troubleshooting
- A: Serial and Ethernet Pin Assignments
- B: Regulatory Compliance Notice
- Federal Communications Commissions Notice
- Harmonics Conformance (Japan)
- German Noise Declaration
- C: Electrostatic Discharge
- D: Specifications
- Index
Troubleshooting
67Interface Manager and Command View TL Installation Guide
Command View TL
opens in browser
but returns “Not
bound in registry”
error message
Management
Station has more
than one network
interface controller
(NIC)
■ Disconnect all but one NIC. Use the Services applet
to restart the Command View TL service. Click Start >
Settings > Control Panel > Administrative
Tools > Services to access the Services applet.
■ Navigate to the config directory in the Command
View TL installation directory on the Management
Station and locate the file
wrapper_rmi.conf
. Using a
text editor, edit the file as follows:
a. Delete the pound sign (#) at the beginning of
the line that starts with
“#wrapper.java.additional.1.”
b. Change the IP address in the same line to the IP
address of the NIC card to be used with
Command View TL.
c. Save the changes and restart the Command
View TL service using the Services applet. Click
Start > Settings > Control Panel >
Administrative Tools > Services to access the
Services applet.
Note: You must edit the
wrapper_rmi.conf
file every
time the IP address of the NIC changes.
Symptom Possible Cause Solution