HP 8/20q HP StorageWorks Simple SAN Connection Manager User Guide (5697-0633, - Page 141

Refresh the Storage Subsystem List, Refresh the Server List

Get HP 8/20q PDF manuals and user guides View all HP 8/20q manuals
Add to My Manuals
Save this manual to your list of manuals

Page 141 highlights

I brought a new server online and connected it to both the SAN and LAN, but Simple SAN Connection Manager does not see it. Why not? Symptoms: If Simple SAN Connection Manager has already been launched prior to a new server being turned on and connected to the LAN and SAN, Simple SAN Connection Manager does not automatically see this server. Solution: Possible solutions include: • Click Refresh the Server List (see "Refreshing the server list," page 99). • 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. Is all of the functionality provided in Simple SAN Connection Manager supported on all the OSs on which the application runs? Symptoms: Some Simple 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 Simple SAN Connection Manager/QLRemote: • Discover the host and its HBAs • Assign LUN to the host and its HBAs • Update HBA BIOS and drivers I tried to perform a Refresh Subsystem List and the application seems to have stopped. Symptoms: When you click Refresh the Storage Subsystem List (see "Refreshing the storage subsystem list," page 121), the system experiences an FC disruption to the storage subsystem. This may result in Simple 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. HP StorageWorks Simple SAN Connection Manager User Guide 141

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
HP StorageWorks Simple SAN Connection Manager User Guide
141
I brought a new server online and connected it to both the SAN and LAN, but Simple SAN Connection
Manager does not see it. Why not?
Is all of the functionality provided in Simple 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 Simple SAN Connection Manager has already been launched prior to a new server
being turned on and connected to the LAN and SAN, Simple SAN Connection
Manager does not automatically see this server.
Solution:
Possible solutions include:
•
Click
Refresh the Server List
(see
“Refreshing the server list,”
page 99).
•
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 Simple 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 Simple 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
“Refreshing the storage
subsystem list,”
page 121), the system experiences an FC disruption to the
storage subsystem. This may result in Simple 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.