[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference mvblab::alphaserver_4100

Title:AlphaServer 4100
Moderator:MOVMON::DAVISS
Created:Tue Apr 16 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:648
Total number of notes:3158

476.0. "Alternate boot device ?" by TAV02::ZOHAR (Zohar Fuchs @ISO , 882-3065) Mon Feb 10 1997 09:15

Hello,

What is our strategic for alternate boot device ? Can we add it to SRM/UNIX 
wish list ? We installed AlphaServer 4100 at IBM shop for critical application.
The customer is looking for high availability features.

We have 2 options:

1) Use LSM (UNIX).
2) Create second bootable system disk and update it evrey night or week.

In option (2), we need the alternate boot feature like in PC or AIX.

Zohar
T.RTitleUserPersonal
Name		DateLines
476.1LANDO::CUMMINSMon Feb 10 1997 09:2631
    The bootdef_dev environment variable takes a list of devices. If the
    first device fails, console will attempt the second one. Is this what
    you were asking for?
    
    P00>>>show bootdef_dev
    bootdef_dev          dkb100.1.0.2.1 dkb400.4.0.2.1 dkb200.2.0.2.1
    P00>>>
    P00>>>b
    (boot dkb100.1.0.2.1)
    Building FRU table
    failed to read dkb100.1.0.2.1
    bootstrap failure
    (boot dkb400.4.0.2.1)
    failed to read dkb400.4.0.2.1
    bootstrap failure
    (boot dkb200.2.0.2.1)
    block 0 of dkb200.2.0.2.1 is a valid boot block
    reading 32 blocks from dkb200.2.0.2.1
    bootstrap code read in
    base = 200000, image_start = 0, image_bytes = 4000
    initializing HWRPB at 2000
    initializing page table at 1f2000
    initializing machine state
    setting affinity to the primary CPU
    jumping to bootstrap code
    
    Digital UNIX boot - Fri Nov 15 21:24:46 EST 1996
    
    .
    .
476.2XIRTLU::schottEric R. Schott USG Product ManagementMon Feb 10 1997 09:316
Hi

 I would suggest you LSM under any senario...depending on the failures
you are concerned about having, you may also want another boot disk
476.3LANDO::CUMMINSMon Feb 10 1997 09:5610
    If fail-over is not enough for you, and you actually want to select
    alternate boot media every once in a while, you can modify console EVs
    from the operating system level.
    
    For instance, you could modify bootdef_dev, boot_osflags, and boot_file
    via operating system callbacks.
    
    Let me know if you need more info here, should you care..
    
    BC
476.4GREAT answersTAV02::ZOHARZohar Fuchs @ISO , 882-3065Mon Feb 10 1997 16:3613
Hi,

All the replies are excellents.

.1 - Thanks. Maybe we should add this to User Manaual.
.2 - Eric - Keep in mind I need to syncronise both disks only at nights.
	    I don't need LSM during working hours (System manager can delete
		by mistakes files from both disks).
.3 - Can you give me an example for bootdev_def (I looked for it) ?

Thanks,

Zohar
476.5MAY30::CUMMINSMon Feb 10 1997 17:1210
    It's already in the User's Guide and has been since Day One. Maybe not
    the easiest to fine, but described nonetheless under the bootdef_dev
    description. This is an Alpha SRM-defined environment variable used on
    all platforms running OpenVMS or Digital UNIX.
    
    For descriptions/examples of using callbacxks under UNIX to modify
    console EVs, I'll have to point you to someone in the UNIX development
    group, and will do so by sending you mail offline.
    
    BC