Re: OpenVMs Cluster

neale.hunt_at_hispeed.ch
Date: 05/25/04 

Date: Tue, 25 May 2004 22:29:43 +0200

Hi again,

additional info from the Cluster doucumentation:

Satellite’s LAN hardware
address
Address has the form xx-xx-xx-xx-xx-xx. You must include the hyphens
when you
specify a hardware address. Proceed as follows:
• ‡On Alpha systems, enter the following command at the satellite’s console:
>>> SHOW NETWORK
Note that you can also use the SHOW CONFIG command.

You can modify the address by running @sys$manager:cluster_config and
select option "3 CHANGE a cluster member’s characteristics."
  Then select option "9 Change <node> satellite’s Ethernet or
FDDI"hardware address.

enter your nodename an dthe ethernet address as shown below.

What is the node’s DECnet node name? ARIEL
What is the new hardware address [XX-XX-XX-XX-XX-XX]? 08-00-3B-05-37-78
Updating network database...
The configuration procedure has completed successfully.

That hopefully will help with the booting.

For reference:
http://h71000.www7.hp.com/doc/731FINAL/DOCUMENTATION/PDF/OVMS_731_CLUSTER_SYSTEMS.PDF

principles are same for your version of VMS

This is VMS 7.3-1 but Example 8–8 Sample Interactive CLUSTER_CONFIG.COM
Session to Change a Satellite’s Hardware Address should explain all you
need.

Long time since I did booting over LAN, so maybe the flags will be 0,0
the system root is supplied by the network database.

section 9.4.1 Booting from a Single LAN Adapter

Hope this get's you further ...

  -- Neale

__ Neale

jutta wrote:

> Hallo Neale,
>
> the os-version is : OpenVMS V.6.2.1H3
>
>
>> boot -flags 11,20000
>> or boot -flags 11,20001 (for a conversational boot)
>
> It is the same: I got the message: .... bootstrap failure.
> On the other client: boot_osflags 0,0 and it works.
>
>
>>As regards firmware version, depends on the version of VMS, later
>>versions do need a minimum level of firmware. It may be possible to
>>email you a "CD image" if you are able to burn it onto CD.
>
> I'm able to burn something onto CD
>
>
> Best of luck
> Jutta
>
>
> neale.hunt@hispeed.ch wrote in message news:<c8tgl6$ili$1@newshispeed.ch>...
>
>>The personal workstation should not present a problem, I had one running
>>VMS prior to swapping to an Alphastation 500.
>>
>>As regards firmware version, depends on the version of VMS, later
>>versions do need a minimum level of firmware. It may be possible to
>>email you a "CD image" if you are able to burn it onto CD.
>>
>>use "show sys /noproc" to determine the version.
>>
>>Part of the problem will be
>>
>> "boot_osflags 0,0",
>>
>> the hint here is
>>
>>Load Assist Parameter = POALF2$DKA0:<SYS11.>
>>
>>So the root you need to boot is "11" not "0"
>>
>>so set boot_osflags 11,0
>>
>>to see what is going on in detail try the following:
>>
>> >
>>You get a blow by blow account of the boot, but I'm not sure what you
>>will see if you get bootstrap failure.
>>
>>Best of luck
>>
>>-- Neale
>>
>> VMS System Specialist
>>
>>jutta wrote:
>>
>>>Thanks for the answer.
>>>
>>>I Think we have DECnet
>>>$ mc ncp list known node characteristics :
>>>
>>>Remote node = 2.32 (POALF4)
>>>Hardware address = 00-00-F8-75-6C-7F
>>>Load file = APB.EXE
>>>Load Assist Agent = SYS$SHARE:NISCS_LAA.EXE
>>>Load Assist Parameter = POALF2$DKA0:<SYS11.>
>>>
>>>Remote node = 2.33 (POALF5)
>>>Hardware address = 00-00-F8-21-E3-F4
>>>Load file = APB.EXE
>>>Load Assist Agent = SYS$SHARE:NISCS_LAA.EXE
>>>Load Assist Parameter = POALF2$DKA0:<SYS12.>
>>>
>>>poalf4 is the new node.
>>>
>>>$ mc lancp sho client *
>>>%LANCP-E-NORSPACP, No response from LANACP, LANACP process apparently
>>>not running
>>>%LANCP-E-CMDERROR, Error executing command
>>>
>>>The new Client is a digital personal workstation 433au . Perhaps it is
>>>not the right hardware for OpenVMS?
>>>
>>>Jutta
>>>
>>>"Hans Vlems" <hvlems.dotweg@zonnet.nl> wrote in message news:<2h1q9oF853dlU1@uni-berlin.de>...
>>>
>>>
>>>>"jutta" <jutta.reichel@gmx.de> schreef in bericht
>>>>news:ec7e473.0405190622.77145268@posting.google.com...
>>>>
>>>>
>>>>>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
>>>>>
>>>>>
>>>>>one of the other clients:
>>>>>
>>>>>>>>pal VMS PALcode V5.65.2
>>>>>>>>version V6.9-4
>>>>>
>>>>>Do we need to do somethings more on the server ?
>>>>>Is the firmware the wrong one?
>>>>>
>>>>>Who can help us?
>>>>>
>>>>>Jutta
>>>>>Jutta
>>>>
>>>>There are two ways to boot a satellite, DECnet or LANCP.
>>>>The MAC address of the satellite is used to figure out what SYS$SYSROOT is
>>>>used to boot from. The MAC address is either in LANCP:
>>>>Have a look at the output of this command:
>>>>
>>>>$ mc lancp sho client *
>>>>
>>>>or in a DECnet database, for phase IV that would be
>>>>
>>>>$ mc ncp list known node char

Relevant Pages

  • Re: What will many cores mean to future Windows releases?
    ... Obviously the hardware might be indeterminant --that would be the normal 'cross-platform' use case. ... But I would rather see an inline operation or compiler switches that would allow you to set or monitor the operations without a JIT compile each time the process ran. ... VMs have their purposes, but optimization is better determined at coding time when you know where the code is going to be deployed, rather than leaving it to be determined at runtime. ... The run time then chooses the algorithm and number of processors to devote to the task, so it's rather like an SQL 'ORDER BY' clause--the programmer specifies what the results need to look like, and the implementation details--being fairly mechanical once the business logic is understood--are handled by the compiler and runtime. ...
    (borland.public.delphi.non-technical)
  • Re: SBS on two systems
    ... If you do it on exactly the same hardware ... you cannot LEGALLY install that software on a second server. ... Go to the Microsoft Small Business Server website, and request a 180 day trial copy for your test lan ... > If a major component of the server, ie processor, hard drive, etc fails and is not under warranty from the folks who did the pre-install, means you get to buy another copy of SBS. ...
    (microsoft.public.windows.server.sbs)
  • Re: DEFCON 16 and Hacking OpenVMS
    ... But VMS cannot use the space in other ways than the hardware makes possible. ... Many of the privileged CPU registers ... All of this is hardware limitations, and VMS can't do diddly squat about it. ...
    (comp.os.vms)
  • Re: VMS Sighting
    ... no mention of VMS experience being needed or desired. ... it is working with a VAX, ... And let's not even go into all the other pieces of hardware ... classified database housed on a VMS Vaxstation 4000 computer system." ...
    (comp.os.vms)
  • Re: Limitations of VMs?
    ... Would anyone with direct experience of working with VMs like to comment on this review and/or on the limitations of other VM products? ... Memory or data Intensive applications and/or critical applications can have their own OS dedicated to that one application. ... No other applications outside applications that would normally running on a single instance server. ... Consolidation of Hardware: Instead of 5 servers, each with an OS, you can choose to buy one redundant server with multiple CPUs and lots of RAM and create VMs based upon need on that one box. ...
    (borland.public.delphi.non-technical)