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

Verifying Cluster Communications, IMPORTANT, Before

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

5-40 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8i and Windows 2000 Administrator Guide I Sets up registry entries for file location and standard registry parameters for the OSDs on all cluster nodes. From one node in the cluster, the OUI installs and configures OSDs on the other nodes in the cluster, provided that: I The servers are communicating through a local area network using a TCP/IP protocol. I The user running the OUI program has administrator privileges on every node. Verifying Cluster Communications IMPORTANT: The successful completion of the OUI program depends on TCP/IP connectivity being set up correctly. It also depends on the user running the OUI having administrator access to every node in the cluster. Before running the OUI, verify cluster communications and the administrator privileges of the user performing the installation. If the OSDs do not install successfully, the OUI will not offer the option to install Oracle8i Parallel Server Database software. The Compaq operating system dependent modules (OSDs) are installed from one node in the cluster (the installing node). The node on which you run the OUI program must be able to communicate with every other node in the cluster in order to copy information to all other cluster nodes. If you have installed an Ethernet cluster interconnect, use the ping utility to verify that each node in the cluster can communicate with every other node. Run the ping utility from each node in the cluster. Ping the client LAN name of every node in the cluster. The client LAN name and client LAN IP address were assigned to each cluster node while you were using SmartStart to install the operating system software. If you are using an Ethernet cluster interconnect, a cluster interconnect name and IP address were assigned to each cluster node. Ping the Ethernet cluster interconnect name of every node in the cluster. When using the client LAN name with the ping command, the IP address displayed by the ping utility should be the client LAN IP address. When using an Ethernet cluster interconnect name, the IP address displayed by the ping utility should be an Ethernet cluster interconnect address. If the ping utility does not return the expected IP addresses, check the entries in the hosts and lmhosts files at %SystemRoot%\system32\drivers\etc.

  • 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
5-40
Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8i and Windows 2000 Administrator Guide
■
Sets up registry entries for file location and standard registry parameters
for the OSDs on all cluster nodes.
From one node in the cluster, the OUI installs and configures OSDs on the
other nodes in the cluster, provided that:
■
The servers are communicating through a local area network using a
TCP/IP protocol.
■
The user running the OUI program has administrator privileges on every
node.
Verifying Cluster Communications
IMPORTANT:
The successful completion of the OUI program depends on TCP/IP
connectivity being set up correctly. It also depends on the user running the OUI having
administrator access to every node in the cluster.
Before
running the OUI, verify cluster
communications and the administrator privileges of the user performing the installation.
If the OSDs do not install successfully, the OUI will not offer the option to install Oracle8
i
Parallel Server Database software.
The Compaq operating system dependent modules (OSDs) are installed from
one node in the cluster (the installing node). The node on which you run the
OUI program must be able to communicate with every other node in the
cluster in order to copy information to all other cluster nodes.
If you have installed an Ethernet cluster interconnect, use the ping utility to
verify that each node in the cluster can communicate with every other node.
Run the ping utility from each node in the cluster. Ping the client LAN name
of every node in the cluster. The client LAN name and client LAN IP address
were assigned to each cluster node while you were using SmartStart to install
the operating system software.
If you are using an Ethernet cluster interconnect, a cluster interconnect name
and IP address were assigned to each cluster node. Ping the Ethernet cluster
interconnect name of every node in the cluster.
When using the client LAN name with the ping command, the IP address
displayed by the ping utility should be the client LAN IP address. When using
an Ethernet cluster interconnect name, the IP address displayed by the ping
utility should be an Ethernet cluster interconnect address. If the ping utility
does not return the expected IP addresses, check the entries in the hosts and
lmhosts files at %SystemRoot%\system32\drivers\etc.