Compaq ProLiant 6500 Compaq Parallel Database Cluster Model PDC/O2000 for Orac - Page 222

Secure Path Manager Cannot Start With Hosts That Use Hyphenated Host Names, Adapter - service manual

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

Troubleshooting 7-15 I The same Secure Path Manager password must be used for all of the hosts in a profile. I Before you change the Secure Path Agent's list of authorized clients or passwords, you must first manually stop the Secure Path Agent. Be sure to restart the Secure Path Agent after the changes have been completed. I Before you modify device volume labels with the Disk Management, you must first manually stop the Secure Path Agent. After the modifications are competed, restart the Secure Path Agent to view the changes. I Before you change the physical or logical configuration of your cluster's I/O path components, you must first stop the existing Secure Path Agent process (SecurePathAgent) from the Services screen. Examples of physical changes include adding, removing, or replacing a Fibre Host Adapter, Fibre Channel SAN Switch or Storage Hub, RA4000/4100 Array, RA4000 Array Controller, or shared disk drive. A logical change would include adding logical drives to your existing storageset. Be sure to verify that the Secure Path Agent is restarted after the changes have been completed. I Before you replace an RA4000 Array Controller, you must also first shut down the affected node or nodes. After the replacement array controller has been installed, reboot the affected node or nodes and make sure that the Secure Path Agent is started. Secure Path Manager Cannot Start With Hosts That Use Hyphenated Host Names Secure Path Manager (SPM) is unable to start with hosts that use hyphenated host names (for example. my-host). Any hyphen indicates a cluster profile member to Secure Path Manager, and DNS will not be able to resolve the name correctly. Hyphenated host file names must be changed to unhyphenated names on all client systems. To correct host names, add the name of the host without the hyphen to the Host file. Add this name to the client.ini file with the Agent configuration program, and use this name to log in with Secure Path Manager.

  • 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
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
Troubleshooting
7-15
■
The same Secure Path Manager password must be used for all of the
hosts in a profile.
■
Before you change the Secure Path Agent
’
s list of authorized clients or
passwords, you must first manually stop the Secure Path Agent. Be sure
to restart the Secure Path Agent after the changes have been completed.
■
Before you modify device volume labels with the Disk Management,
you must first manually stop the Secure Path Agent. After the
modifications are competed, restart the Secure Path Agent to view the
changes.
■
Before you change the physical or logical configuration of your cluster
’
s
I/O path components, you must first stop the existing Secure Path Agent
process (SecurePathAgent) from the
Services
screen. Examples of
physical changes include adding, removing, or replacing a Fibre Host
Adapter, Fibre Channel SAN Switch or Storage Hub, RA4000/4100
Array, RA4000 Array Controller, or shared disk drive. A logical change
would include adding logical drives to your existing storageset. Be sure
to verify that the Secure Path Agent is restarted after the changes have
been completed.
■
Before you replace an RA4000 Array Controller, you must also first
shut down the affected node or nodes. After the replacement array
controller has been installed, reboot the affected node or nodes and
make sure that the Secure Path Agent is started.
Secure Path Manager Cannot Start With Hosts That
Use Hyphenated Host Names
Secure Path Manager (SPM) is unable to start with hosts that use hyphenated
host names (for example.
my-host
). Any hyphen indicates a cluster profile
member to Secure Path Manager, and DNS will not be able to resolve the
name correctly. Hyphenated host file names must be changed to unhyphenated
names on all client systems.
To correct host names, add the name of the host without the hyphen to the
Host file. Add this name to the client.ini file with the Agent configuration
program, and use this name to log in with Secure Path Manager.