openVMS boot strap failure

[nipun_2]

Hi,
I have 3 node common environment cluster on ethernet lan running OpenVMS 7.3-1.

The systems were running fine and I recently rebooted the system.
So I started the main node and while it was sarting up, I started the Satellite node (Sat1)

and then when these two nodes were up I started the second satellite node (Sat2).

However Sat2 did not boot

This is how the events unfolded

>>>boot ewa0
starting MOP boot
....

bootstrap failure
^C to abort
retrying..

and this goes on

Is the order of booting a problem

I can start with Sever node then Sat2 and then Sat1

Let me know if you have any ideas

I not well versed in OpenVMS so please try to give me specific commands or an idea for where to look for the specific documentation.

Thanks in advance

[John Donovan_4]

I have always started 1 node at a time when bringing up the whole cluster. main, sat1 & sat2. Your main system should be up completely before starting the satellite nodes.

[Volker Halle]

Nipun,

please check SYS$MANAGER:OPERATOR.LOG of your boot member (main node) for any messages seen when trying to (unsuccessfully) boot SAT2 and consider to include these messages in your next reply.

Volker.

[nipun_2]

Hi Hein,
Here is the operator log file.
Today morning I tried to again boot Sat2 but in the following sequence
Main server (completely up and running)
boot Sat2 (same error as before boostrap failure)

boot Sat1 (sucessfully booted)

I am attaching the log file.

Please let me know what you guys think

Note: SC4238 is the name of the Server node

[Volker Halle]

Nipun,

nothing in the OPERATOR.LOG file from a successful or even unsuccessful boot atttempt of Sat2. This implies, that the MOP boot request did not even reach node SC4238.

Did it ever work ? How do you normally boot Sat2 ? Via DECnet MOP (MC NCL SHOW MOP CLIENT *) or LANCP MOP (MC LANCP SHOW NODE) ?

At 10:52, there are LANACP messages showing that EIA0 and EWA0 are being enabled for MOP downline loading, but this is 1 minute before shutdown of node SC4238 ?!

If you only have a DTSS server configured on your LAN; you might want to get rid of those 'Too Few Servers Detected' DECnet event messages by using the following NCL command:

$ MC NCL
BLOCK EVENT DISPATCHER OUTBOUND STREAM local_stream GLOBAL FILTER -
((NODE,DTSS), Too Few Servers Detected)

This command can be executed interactively. This supported place for this command is in SYS$MANAGER:NET$EVENT_LOCAL.NCL ( see comments in SYS$MANAGER:NET$EVENT_LOCAL.TEMPLATE)

Volker.

[Joseph Huber_1]

In Your operator.log (it dates 5-jun-2003, is it really from today ???), there is LANCP MOP services enabled, but no attempt of successfull or unsucessfull to boot.
This means the MOP boot requests from Sat2 do not arrive at the server.
Is EWA0 connected to the right LAN ?

[nipun_2]

From the discussion going on here,
I did the following changed the ethernet cable and did the boot process. It still did not work.
Then I shutdown the Sat2 node (turned off the power) and again started it (it was configured for auto boot through ewa0)

The following message first showed up.

ED.E8.E7....
ewa0: link failed: Using 100BaseTX:full duplex.

Then the it went throug some other messages and finally came to the srm consol prompt.
>>>

Also I have been using
2608 (Gigabit Ethernet switch) which has 2 green (indicating Gb data transfer) blinking leds however for the Sat 2 cable only one amber colored (indicating 100 Mb data transfer?)
So looks like this
SPD/LNK/ACT Green(blinks) Green(blinks) Amber (blinks)
FDX/HDX Green(blinks) Green(blinks) NO LIGHT

So I am thinking whether the ethernet card could be the problem. Is there anyway to test this in the SRM console.

I can boot into Sat2 as a standalone machine, If that might help in some hardware test.

[nipun_2]

I should have added this
OpenVMS 7.3-1, common system environment
The network setup is as shown below

Server -> 2608 Gigabit switch
Sat1 -> 2608 Gigabit Switch
Sat2 -> 2608 Gigabit Swtich

Thus all machines communicate over the switch.

[comarow · Accepted solution]

Assuming nothing has changed from VMS,
your network manager may have filtered out SCS or MOP traffic.

Issue the command Reply/network to see if you are getting Mop requests.

The system could also be broken. As I always say, try booting from a CD to help isolate hardware, versus disk or networks.

Bob

[Jan van den Ende]

Slight addendum, and slight correction to last Comarow answer:

you need to have OPER priv for the REPLY command, and the syntax is:
$ REPLY/ENABLE=NET
(switch off again by /DISABLE)

As always: if not exactly sure about any systax, then HELP is a real friend!!

Proost.

Have one on me.

jpe