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

Verifying the Hardware and Software Installation, Cluster Communications

Page 176 highlights

Installation and Configuration 5-47 Verifying the Hardware and Software Installation Cluster Communications Use the ping utility to verify that each node in the cluster can communicate with every other node over the client LAN. Run the ping utility from the installing cluster node. Verify the installing node can communicate with all cluster nodes by pinging the client LAN name. The IP address displayed by the ping utility should be the client LAN IP address. If you are using an Ethernet cluster interconnect, ping the Ethernet cluster interconnect name. The IP address displayed by the ping utility should be the Ethernet cluster interconnect address. If this is not the case, check the entries in the hosts and lmhosts files at %SystemRoot%\system32\drivers\etc. Access to Shared Storage from All Nodes Use Disk Management to verify that the same shared disk resources are seen from this node as they are from other installed nodes in the cluster. OSDs After verifying all the nodes have access to the shared storage, start an Oracle instance. For example, at a C: command prompt start an instance by entering: net start oracleservice If the OSDs are installed correctly, a message will appear indicating that the Oracle service has started successfully. If the Oracle service did not start successfully, make sure that the OracleCMService is started and the SID is in the Oracle registry. There are two logs that can provide information about why the Oracle service did not start. These logs are: I \Compaq\OPS\cmsrvr.log I \Compaq\OPS\nm.log

  • 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

Installation and Configuration
5-47
Verifying the Hardware and Software
Installation
Cluster Communications
Use the ping utility to verify that each node in the cluster can communicate
with every other node over the client LAN. Run the ping utility from the
installing cluster node. Verify the installing node can communicate with all
cluster nodes by pinging the client LAN name. The IP address displayed by
the ping utility should be the client LAN IP address.
If you are using an Ethernet cluster interconnect, ping the Ethernet cluster
interconnect name. The IP address displayed by the ping utility should be the
Ethernet cluster interconnect address. If this is not the case, check the entries
in the hosts and lmhosts files at %SystemRoot%\system32\drivers\etc.
Access to Shared Storage from All Nodes
Use Disk Management to verify that the same shared disk resources are seen
from this node as they are from other installed nodes in the cluster.
OSDs
After verifying all the nodes have access to the shared storage, start an Oracle
instance. For example, at a C: command prompt start an instance by entering:
net start oracleservice<
SID
>
If the OSDs are installed correctly, a message will appear indicating that the
Oracle service has started successfully.
If the Oracle service did not start successfully, make sure that the
OracleCMService is started and the SID is in the Oracle registry. There are
two logs that can provide information about why the Oracle service did not
start. These logs are:
\Compaq\OPS\cmsrvr.log
\Compaq\OPS\nm.log