Product manual

VTrak E-Class Product Manual
322
Connection Problems
Connection problems include:
• Serial Connections (page 322)
• Network Connections (page 323)
• Fibre Channel Connections (page 323)
• SAS Connections (page 324)
• Browser Does Not Connect to WebPAM PROe (page 325)
Connection problems cause a majority of failures in almost any electrical system.
While the installation of the cables and components was correct, they don't
function properly, or at all, because:
• A connector is dirty or corroded
• A connector is loose or damaged
• A cable looks OK outside but has an open circuit inside
• The wrong cable was used
VTraks ship with a full set of new cables, as required for each specific model. Be
sure to use these components because: 1.) They are the proper ones for your
RAID subsystem, 2.) They are in brand-new condition, and 3.) You paid for them
with the purchase of your subsystem.
Serial Connections
VTrak uses a serial connection for the command line interface (CLI) and the
command line utility (CLU). After you set the IP address, you can access the CLI
and CLU through a network connection, also. Normally, users prefer WebPAM
PROe because of its graphic user interface. But the CLI and CLU can do the
same jobs. And they work when your network connection is down.
For VTrak, you must use the CLI or CLU to set the Management Port IP address
in order for WebPAM PROe to connect with it. See “Setting up the Serial
Connection” on page 39. This issue is discussed further under Network
Connections, below. See “Setting Up Serial Cable Connections” on page 36 for
more information on making the connection.
The CLI and CLU control and manage but they do not move data. They
communicates through a null-modem cable, supplied with the VTrak. A straight-
through serial cable does not work for this purpose. You may choose not use the
CLI or CLU often and want to disconnect and store the cable. Consider leaving it
connected, so you know where it is the next time you need it.