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

Why doesn't Simple SAN Connection Manager start up?, registered on Simple SAN Connection Manager.

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 136 highlights

When I open Simple SAN Connection Manager, why doesn't it discover my subsystems? 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 Simple SAN Connection Manager system. Simple 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 Simple SAN Connection Manager system. Solution: Ensure that your subsystems have a direct FC link and that the subsystem's hardware is registered on Simple SAN Connection Manager. Why doesn't Simple SAN Connection Manager start up? Symptoms: When I try to start Simple SAN Connection Manager, it does not open and I get an error message. This happens when multiple copies of Simple SAN Connection Manager are trying to be used within the SAN at the same time. On launching Simple SAN Connection Manager, a message box saying: The application cannot run. No storage subsystem was detected. Solution: Close all instances of Simple SAN Connection Manager running on other machines connected to the SAN, and then re-launch Simple SAN Connection Manager. Why does the storage subsystem fail to create logical disk with maximum size? 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. 136 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
  • 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
136
Troubleshooting
When I open Simple SAN Connection Manager, why doesn’t it discover my subsystems?
Why doesn’t Simple 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 Simple SAN Connection Manager
system. Simple 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
Simple SAN Connection Manager system.
Solution:
Ensure that your subsystems have a direct FC link and that the subsystem’s hardware is
registered on Simple SAN Connection Manager.
Symptoms:
When I try to start Simple SAN Connection Manager, it does not open and I get an
error message. This happens when multiple copies of Simple SAN Connection
Manager are trying to be used within the SAN at the same time. On launching Simple
SAN Connection Manager, a message box saying:
The application cannot run. No storage subsystem was
detected
.
Solution:
Close all instances of Simple SAN Connection Manager running on other machines
connected to the SAN, and then re-launch Simple 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.