02.12.2012 Views

OpenVMS Cluster Systems - OpenVMS Systems - HP

OpenVMS Cluster Systems - OpenVMS Systems - HP

OpenVMS Cluster Systems - OpenVMS Systems - HP

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Step Action<br />

<strong>Cluster</strong> Troubleshooting<br />

C.3 Satellite Fails to Boot<br />

5 On Alpha and VAX systems, verify the following information in the NCP display:<br />

Step Action<br />

A Verify the DECnet address for the node.<br />

B Verify the load assist agent is SYS$SHARE:NISCS_LAA.EXE.<br />

C Verify the load assist parameter points to the satellite system disk and correct root.<br />

D Verify that the hardware address matches the satellite’s Ethernet address. At the<br />

satellite’s console prompt, use the information shown in Table 8–3 to obtain the<br />

satellite’s current LAN hardware address.<br />

Compare the hardware address values displayed by NCP and at the satellite’s<br />

console. The values should be identical and should also match the value shown in<br />

the SYS$MANAGER:NETNODE_UPDATE.COM file. If the values do not match,<br />

you must make appropriate adjustments. For example, if you have recently replaced<br />

the satellite’s LAN adapter, you must execute CLUSTER_CONFIG.COM CHANGE<br />

function to update the network database and NETNODE_UPDATE.COM on the<br />

appropriate MOP server.<br />

6 Perform a conversational boot to determine more precisely why the satellite is having<br />

trouble booting. The conversational boot procedure displays messages that can help you<br />

solve network booting problems. The messages provide information about the state of the<br />

network and the communications process between the satellite and the system disk server.<br />

Reference: Section C.3.6 describes booting messages for Alpha systems.<br />

C.3.6 Alpha Booting Messages (Alpha Only)<br />

On Alpha systems, the messages are displayed as shown in Table C–2.<br />

Table C–2 Alpha Booting Messages (Alpha Only)<br />

Message Comments<br />

%VMScluster-I-MOPSERVER, MOP server for downline load was node UTAH<br />

This message displays the name of the system providing the DECnet MOP<br />

downline load. This message acknowledges that control was properly<br />

transferred from the console performing the MOP load to the image that<br />

was loaded.<br />

%VMScluster-I-BUSONLINE, LAN adapter is now running 08-00-2B-2C-CE-E3<br />

This message displays the LAN address of the Ethernet or FDDI adapter<br />

specified in the boot command. Multiple lines can be displayed if multiple<br />

LAN devices were specified in the boot command line. The booting<br />

satellite can now attempt to locate the system disk by sending a message<br />

to the cluster multicast address.<br />

If this message is not displayed, either the<br />

MOP load failed or the wrong file was MOP<br />

downline loaded.<br />

If this message is not displayed, the LAN<br />

adapter is not initialized properly. Check<br />

the physical network connection. For<br />

FDDI, the adapter must be on the ring.<br />

(continued on next page)<br />

<strong>Cluster</strong> Troubleshooting C–11

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!