Compaq ProLiant 6500 Compaq Parallel Database Cluster Model PDC/05000 for Orac - Page 184

Using Secure Path Manager, Secure Path Manager provides a Graphical User Interface GUI utility

Get Compaq ProLiant 6500 PDF manuals and user guides View all Compaq ProLiant 6500 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 184 highlights

6-30 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8i and Windows 2000 Administrator Guide Using Secure Path Manager StorageWorks Secure Path is a high availability software product that provides continuous data access for MA8000/EMA12000 Storage Subsystems. Redundant hardware, advanced RAID technology, and automated failover capability are used to enhance fault tolerance and availability. Secure Path, in conjunction with your MA8000/EMA12000 Storage Subsystem, effectively eliminates as single points of failure in the storage system, the array controllers, disk drives, interconnect hardware, and host adapters. NOTE: This section assumes that storagesets have already been configured, using SWCC or CLI, and that the drives have been partitioned with Disk Management. Secure Path Manager is the cluster management component of Secure Path. Secure Path Manager provides a Graphical User Interface (GUI) utility that: I Reports the status of the I/O paths in each redundant FC-AL or redundant Fibre Channel Fabric. I Reports disk status (path assignment, failover, and failback activity). I Enables automatic drive failback upon path restoration. It is recommended that Secure Path Manager GUI remain active (or minimized) to provide continuous Secure Path status monitoring. IMPORTANT: If you make changes to the Secure Path Agent Configuration, the changes will not go into effect until you stop and restart the Secure Path Agent Service from the Services screen. NOTE: If Secure Path Manager shows a controller failure, be sure you match the displayed failed controller with the correct physical controller. The Secure Path Manager GUI displays the array controllers in each storage subsystem according to their serial numbers, not according to their physical order: the array controller with the lower serial number is displayed as Controller A and the array controller with the higher serial number is displayed as Controller B, regardless of their actual physical order in the controller enclosure. You can display a controller's serial number by using the show this_controller CLI command.

  • 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
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
6-30
Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8i and Windows 2000 Administrator Guide
Using Secure Path Manager
StorageWorks Secure Path is a high availability software product that provides
continuous data access for MA8000/EMA12000 Storage Subsystems.
Redundant hardware, advanced RAID technology, and automated failover
capability are used to enhance fault tolerance and availability. Secure Path, in
conjunction with your MA8000/EMA12000 Storage Subsystem, effectively
eliminates as single points of failure in the storage system, the array
controllers, disk drives, interconnect hardware, and host adapters.
NOTE:
This section assumes that storagesets have already been configured, using SWCC
or CLI, and that the drives have been partitioned with Disk Management.
Secure Path Manager is the cluster management component of Secure Path.
Secure Path Manager provides a Graphical User Interface (GUI) utility that:
■
Reports the status of the I/O paths in each redundant FC-AL or
redundant Fibre Channel Fabric.
■
Reports disk status (path assignment, failover, and failback activity).
■
Enables automatic drive failback upon path restoration.
It is recommended that Secure Path Manager GUI remain active (or
minimized) to provide continuous Secure Path status monitoring.
IMPORTANT:
If you make changes to the Secure Path Agent Configuration, the changes
will not go into effect until you stop and restart the Secure Path Agent Service from the
Services
screen.
NOTE:
If Secure Path Manager shows a controller failure, be sure you match the
displayed failed controller with the correct physical controller. The Secure Path Manager
GUI displays the array controllers in each storage subsystem according to their serial
numbers, not according to their physical order: the array controller with the lower serial
number is displayed as Controller A and the array controller with the higher serial number
is displayed as Controller B, regardless of their actual physical order in the controller
enclosure. You can display a controller
’
s serial number by using the
show
this_controller
CLI command.