HP 8.20q Fibre Channel Switch User Manual
Page 145
HP SAN Connection Manager User Guide 145
I brought a new server online and connected it to both the SAN and LAN, but SAN Connection Manager
does not see it. Why not?
Is all of the functionality provided in SAN Connection Manager supported on all the OSs on which the
application runs?
I tried to perform a Refresh Subsystem List and the application seems to have stopped.
Symptoms:
If SAN Connection Manager has already been launched prior to a new server being
turned on and connected to the LAN and SAN, SAN Connection Manager does not
automatically see this server.
Solution:
Possible solutions include:
•
Click Refresh the Server List (see
•
Re-launch the application for the new server to appear. (This also applies to a server
taken offline.)
•
Ensure that QLRemote is running:
• In Windows: From Administrative Tools, Services, check to make sure the service
named “QLManagementAgentJava” is started and running. Or, in Task
Manager, check for QLremote.exe.
• In Linux: Enter /etc/init.d/qlremote status. The system should show
QLRemote as running.
Symptoms:
Some SAN Connection Manager options are only supported on specific operating
systems.
Solution:
The following options are supported on the various OSs.
•
Linux host with QLRemote:
• Discover the host and its HBAs
• Assign LUN to the host and its HBAs
• Update HBA BIOS
•
Windows host with SAN Connection Manager/QLRemote:
• Discover the host and its HBAs
• Assign LUN to the host and its HBAs
• Update HBA BIOS and drivers
Symptoms:
When you click Refresh the Storage Subsystem List (see
page 125), the system experiences an FC disruption to the
storage subsystem. This may result in SAN Connection Manager being in a
“hung” state and not able to recover. If the FC connection is re-established, the
application should be able to communicate with the storage subsystem again.
However, some hardware providers may not be able to recover, causing the
application to exit and no longer able to discover the subsystem.
Solution:
To resolve this issue, make sure that the FC connection is back to normal, and
then try to restart the Virtual Disk Services service through either Computer
Management’s Service (services.msc command) or Command Line.