Re: OpenVMs Cluster
From: Keith A. Lewis (lewis_at_spyder.mitre.org)
Date: 05/19/04
- Next message: Bob Koehler: "Re: LAT & Hobbiest VMS questions"
- Previous message: GreyCloud: "Re: [OT]: Maybe SCO is (partially) right"
- In reply to: jutta: "OpenVMs Cluster"
- Next in thread: jutta: "Re: OpenVMs Cluster"
- Reply: jutta: "Re: OpenVMs Cluster"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 19 May 2004 17:31:53 +0000 (UTC)
jutta.reichel@gmx.de (jutta) writes in article <ec7e473.0405190622.77145268@posting.google.com> dated 19 May 2004 07:22:55 -0700:
>We have a OpenVMS (Alpha) Cluster with 4 Satellites.
>One of them is defect. We took another Client with Operating System
>DEC UNIX. We changed the Hardware Address on the Server with
>Cluster_config.
>The boot parameter on the new Client:
>>>> os_type OpenVMS
>>>> ew0_protocols MOP
>>>> boot_dev ewa0.0.0.14.0
>>>> boot_osflags 0,0
>>>> ewa0_inet_init bootp
>>>> pal VMS PALcode V1.20-14
>>>> version V6-9-7
>
>We try to boot the new Client and we got the message:
>>>> b
>boot ewa0.0.0.3.0 -flags 0,0
>Trying MOP boot
>..... bootstrap failure
That's the message I get if the server is down, or ignoring me.
Are you running DECnet IV or V? I know the commands for phase IV, to
double-check the hardware address:
$ MC NCP SHOW NODE (node) CHAR
Also, you can narrow down the problem by doing a "REPLY/ENABLE" on the
server, then trying to boot again. If the server gets the request there
will be an OPCOM message to that effect.
Check ewa0_mode and make sure it's compatible with your hub/switch.
--Keith Lewis klewis {at} mitre.org
The above may not (yet) represent the opinions of my employer.
- Next message: Bob Koehler: "Re: LAT & Hobbiest VMS questions"
- Previous message: GreyCloud: "Re: [OT]: Maybe SCO is (partially) right"
- In reply to: jutta: "OpenVMs Cluster"
- Next in thread: jutta: "Re: OpenVMs Cluster"
- Reply: jutta: "Re: OpenVMs Cluster"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|