HP 6400/8400 HP Enterprise Virtual Array Updating Product Software Guide (XCS - Page 68

No storage systems found, Cause, Resolution, Reference documentation Symptom

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

Page 68 highlights

Cause HP P6000 Command View may have lost communication with the controllers. Two possible scenarios follow: • The management server HBA may have timed out commands to the controllers. See "Unknown storage system" (page 67). • The controllers are running a version of XCS that HP P6000 Command View does not recognize. See "Unknown storage system" (page 67). Resolution Unknown storage system - cause 1 If the array has a heavy I/O load, the HBA in the management server may time out commands to the controllers. If this occurs, the array appears in the Unknown state. Corrective action This scenario should correct itself in less than one minute. Alternatively, you can perform a Rediscover operation to initiate new commands to the controller. Unknown storage system- cause 2 HP P6000 Command View can only manage controllers that are running supported XCS versions. Corrective action Ensure that you are running the HP P6000 Command View version that is compatible with XCS 10000000. See the "HP P6000 Command View interoperability support" table in the HP P6000 Enterprise Virtual Array Compatibility Reference to determine which version of HP P6000 Command View you should be running. Then, upgrade HP P6000 Command View to a compatible version. See "Reference documentation" (page 6) for the link to this document. No storage systems found Symptom HP P6000 Command View does not display any arrays, even though they are in the fabric. Cause Several conditions can cause this symptom. Table 10 (page 68) lists some possible causes and corrective actions. Resolution Table 10 Possible causes and corrective actions when no array is found Possible cause Corrective action The management server may not be able to communicate with either controller. Check the connection configuration between the management server and the controller pair. The management server must have a communication path to both controllers in case one controller loses communication with the server. When HP P6000 Command View is first starting up, a password may be enabled on the controllers, but a password has not been entered in HP P6000 Command View. Enter the correct password in HP P6000 Command View or disable the password on the controller. The switches may not be zoned correctly, making an Verify that the switches are zoned correctly. array invisible to HP P6000 Command View. HP P6000 Command View may have been restarted 1. Verify that the controllers are up and running properly. while there was a communication failure between HP 2. Check the cable connections between the management P6000 Command View and the controllers. When the server and the switch. 68 Troubleshooting

  • 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
Cause
HP P6000 Command View may have lost communication with the controllers. Two possible scenarios
follow:
•
The management server HBA may have timed out commands to the controllers. See
“
Unknown
storage system
” (page 67)
.
•
The controllers are running a version of XCS that HP P6000 Command View does not
recognize. See
“
Unknown storage system
” (page 67)
.
Resolution
Unknown storage system
– cause 1
If the array has a heavy I/O load, the HBA in the management server may time out commands to
the controllers. If this occurs, the array appears in the
Unknown
state.
Corrective action
This scenario should correct itself in less than one minute. Alternatively, you can perform a Rediscover
operation to initiate new commands to the controller.
Unknown storage system
– cause 2
HP P6000 Command View can only manage controllers that are running supported XCS versions.
Corrective action
Ensure that you are running the HP P6000 Command View version that is compatible with XCS
10000000. See the “HP P6000 Command View interoperability support” table in the
HP P6000
Enterprise Virtual Array Compatibility Reference
to determine which version of HP P6000 Command
View you should be running. Then, upgrade HP P6000 Command View to a compatible version.
See
“Reference documentation” (page 6)
for the link to this document.
No storage systems found
Symptom
HP P6000 Command View does not display any arrays, even though they are in the fabric.
Cause
Several conditions can cause this symptom.
Table 10 (page 68)
lists some possible causes and
corrective actions.
Resolution
Table 10 Possible causes and corrective actions when no array is found
Corrective action
Possible cause
Check the connection configuration between the management
server and the controller pair. The management server must
The management server may not be able to
communicate with either controller.
have a communication path to both controllers in case one
controller loses communication with the server.
Enter the correct password in HP P6000 Command View or
disable the password on the controller.
When HP P6000 Command View is first starting up,
a password may be enabled on the controllers, but a
password has not been entered in HP P6000
Command View.
Verify that the switches are zoned correctly.
The switches may not be zoned correctly, making an
array invisible to HP P6000 Command View.
HP P6000 Command View may have been restarted
while there was a communication failure between HP
1.
Verify that the controllers are up and running properly.
2.
Check the cable connections between the management
server and the switch.
P6000 Command View and the controllers. When the
68
Troubleshooting