HP StorageWorks SN6000 HP StorageWorks Simple San Connection manager user guid - Page 135

Troubleshooting, Refresh Subsystem List support-see

Get HP StorageWorks SN6000 - Fibre Channel Switch PDF manuals and user guides View all HP StorageWorks SN6000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 135 highlights

A Troubleshooting This appendix provides answers regarding the following: • Dynamic disk support-see page 135. • Launch-time support-see page 135. • Linux server on my local SAN is not discovered-see page 136. • Lost aliases support-see page 136. • New server support-see page 137. • OS support-see page 137. • Refresh Subsystem List support-see page 137. • Simple SAN Connection Manager does not discover my subsystems-see page 138. • Simple SAN Connection Manager does not start up-see page 138. • Storage subsystem fails to create logical disk with maximum size-see page 138. • "Unknown Server" is shown-see page 139. Does Simple SAN Connection Manager support dynamic disk functionality? Symptoms: None. Solution: None. This version of Simple SAN Connection Manager does not support dynamic disk functionality. When I launch Simple SAN Connection Manager, it takes a long time to open. Symptoms: This can be caused by a several factors: • The subsystem is busy servicing I/O. • The Ethernet network is busier than normal with traffic. • There are many servers with HP HBAs and agents running. This requires more time for these systems to respond and report to the Simple SAN Connection Manager server discovery. • There are many subsystems or the subsystems have many logical and physical disks. This requires more time for the subsystems to gather and report the information to Simple SAN Connection Manager. Solution: Be patient. We recommend launching Simple SAN Connection Manager during periods of light or no I/O traffic. HP StorageWorks Simple SAN Connection Manager User Guide 135

  • 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
HP StorageWorks Simple SAN Connection Manager User Guide
135
A
Troubleshooting
This appendix provides answers regarding the following:
•
Dynamic disk support—see page 135.
•
Launch-time support—see page 135.
•
Linux server on my local SAN is not discovered—see page 136.
•
Lost aliases support—see page 136.
•
New server support—see page 137.
•
OS support—see page 137.
•
Refresh Subsystem List support—see page 137.
•
Simple SAN Connection Manager does not discover my subsystems—see page 138.
•
Simple SAN Connection Manager does not start up—see page 138.
•
Storage subsystem fails to create logical disk with maximum size—see page 138.
•
“Unknown Server” is shown—see page 139.
Does Simple SAN Connection Manager support dynamic disk functionality?
When I launch Simple SAN Connection Manager, it takes a long time to open.
Symptoms:
None.
Solution:
None. This version of Simple SAN Connection Manager does not support dynamic disk
functionality.
Symptoms:
This can be caused by a several factors:
•
The subsystem is busy servicing I/O.
•
The Ethernet network is busier than normal with traffic.
•
There are many servers with HP HBAs and agents running. This requires more time
for these systems to respond and report to the Simple SAN Connection Manager
server discovery.
•
There are many subsystems or the subsystems have many logical and physical disks.
This requires more time for the subsystems to gather and report the information to
Simple SAN Connection Manager.
Solution:
Be patient. We recommend launching Simple SAN Connection Manager during
periods of light or no I/O traffic.