HP 8.20q Fibre Channel Switch User Manual
Page 146
146 Troubleshooting
When I open SAN Connection Manager, why doesn’t it discover my subsystems?
Why doesn’t SAN Connection Manager start up?
Why does the storage subsystem fail to create logical disk with maximum size?
Symptoms:
This can be caused by several factors:
•
Another application is running on the same or different system and connects to the
subsystem. Some storage subsystems only allow a single application to connect and
perform management functions on them.
•
The subsystems do not have an FC link to the SAN Connection Manager system.
SAN Connection Manager requires a direct FC link to discover and manage the
subsystem.
•
The subsystem’s hardware provider has not been installed or registered on the SAN
Connection Manager system.
Solution:
Ensure that your subsystems have a direct FC link and that the subsystem’s hardware is
registered on SAN Connection Manager.
Symptoms:
When I try to start SAN Connection Manager, it does not open and I get an error
message. This happens when multiple copies of SAN Connection Manager are trying
to be used within the SAN at the same time. On launching SAN Connection Manager,
a message box saying:
The application cannot run. No storage subsystem was
detected
.
Solution:
Close all instances of SAN Connection Manager running on other machines connected
to the SAN, and then re-launch SAN Connection Manager.
Symptoms:
When creating a logical disk with the maximum size allowed, some storage subsystems
fail the request with one of the following error messages:
Not enough space for the new logical disk.
Cannot complete the logical disk creation request.
This could be because the subsystems do not have enough space for the new logical
disk’s size. The subsystems might need space for the new logical disk overhead or
space is not available because of bad sectors on the drives.
Solution:
When this problem occurs, reduce the logical disk size and re-initiate the logical disk
creation request.