- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - OpenVMS
- >
- Reboot from dka0: to ewa0:
-
- Forums
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- Infrastructure Solutions German
- L’Avenir de l’IT
- IT e Trasformazione Digitale
- Enterprise Topics
- ИТ для нового стиля бизнеса
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Forums
-
Blogs
-
InformationEnglish
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-15-2005 12:57 AM
10-15-2005 12:57 AM
Reboot from dka0: to ewa0:
Now, i will reboot the machine into the ewa0-device (diskless NetBSD) from OpenVMS. But i dont now how.
At the moment i shutdown the system manually and on the SRM-console i enter the comands:
> boot dka0 (for OpenVMS)
or
> boot ewa0 (for diskless NetBSD)
How can i reboot from dka0: to ewa0: ?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-15-2005 01:27 AM
10-15-2005 01:27 AM
Re: Reboot from dka0: to ewa0:
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-15-2005 02:59 AM
10-15-2005 02:59 AM
Re: Reboot from dka0: to ewa0:
as Kalle said, there is no 'supported' way of rebooting from a device other than BOOT_DEV, i.e. the last device the system has booted from (typically same as BOOTDEF_DEV).
I've found an unsupported program called DEFAULT_BOOT.C at:
http://wwwvms.mppmu.mpg.de/vmssig/src/C/default_boot.c
This example program seems to come from Steve H. from OpenVMS engineering.
With appropriate modifications, this UNSUPPORTED program might do want you want to do.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-15-2005 05:06 AM
10-15-2005 05:06 AM
Re: Reboot from dka0: to ewa0:
A word of caution regarding the UNSUPPORTED stuff by Steven H.
It has crashed a dual CPU DS25.
I'm still investigating why. On a single CPU system it seems to work.
Regards,
Kris (aka Qkcl)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-15-2005 09:49 PM
10-15-2005 09:49 PM
Re: Reboot from dka0: to ewa0:
Joseph
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-15-2005 10:28 PM
10-15-2005 10:28 PM
Re: Reboot from dka0: to ewa0:
feel free to mail me the CLUE file from the crash.
According to the Alpha ARM, some console callback routines must only be invoked from the primary CPU, but GET_ENV and SET_ENV do not seem to be affected by this restriction.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-16-2005 06:34 PM
10-16-2005 06:34 PM
Re: Reboot from dka0: to ewa0:
feel free to mail me the CLUE file from the crash.
Unfortunately, shortly after the crash we experienced another one (in DECnet) that has overwritten the one caused by default_boot.
According to the Alpha ARM, some console callback routines must only be invoked from the primary CPU, but GET_ENV and SET_ENV do not seem to be affected by this restriction.
I'm currently adapting the program so it can run on the primary CPU only. Still have to find a window for testing it (do not want to crash that system again in the middle of the day (development system)).
Regards,
Kris (aka Qkcl)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-16-2005 06:42 PM
10-16-2005 06:42 PM
Re: Reboot from dka0: to ewa0:
CLUE files won't be overwritten, you'll find the most recent of them in CLUE$COLLECT:CLUE$*.LIS. As the CLUE file is automatically created from the dump during startup, the crash information will only be lost, if there is a crash during startup before the CLUE$SDA detached process created by @SYS$STARTUP:CLUE$STARTUP has completed.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-16-2005 08:44 PM
10-16-2005 08:44 PM
Re: Reboot from dka0: to ewa0:
CLUE files won't be overwritten, you'll find the most recent of them in CLUE$COLLECT:CLUE$*.LIS
Somehow that particular CLUE file got lost. Don't know why yet. So sorry.
Kris (aka Qkcl)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-17-2005 03:50 AM
10-17-2005 03:50 AM
Re: Reboot from dka0: to ewa0:
I'm thinking about a totally other way:
If the console is plugged into a Terminalserverport, you can use Kermit or a console manager (like PCM) to give the instructions!
Like:
SHUTDOWN
(Wait until "shutdown completed")
CTRL/P (If necessary)
BOOT EWA0:
Hope that helps!
Bye Kuddel
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-17-2005 01:53 PM
10-17-2005 01:53 PM
Re: Reboot from dka0: to ewa0:
But i am not a developer and i dont have a c-compiler. Can any body manipulate and compile the "default_boot.c" for me, so that i can reboot temporarely like the src-command: "boot -fl a ewa0" (this boots my NetBSD-System)?
My default-boot-device and flag (dka0: -fl 0,1) must be untouched, so when i power ON the maschine she boots like the src-command: "boot -fl 0,1 dka0:".
Thats my problem. On my Sparc-machines its very simple, i can reboot with options, ex. "reboot -- net".
A portserver for all 84 Alphas is not a good option.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-17-2005 08:48 PM
10-17-2005 08:48 PM
Re: Reboot from dka0: to ewa0:
making modifications to the example program and testing these modifications may be a non-trivial task.
Temporarily changing BOOT_OSFLAGS without affecting the nonvolatile value may be impossible, as this environment variable is both Nonvolatile and Warm nonvolatile (according to the Alpha Architecture Reference Manual).
Volker.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-18-2005 12:46 AM
10-18-2005 12:46 AM
Re: Reboot from dka0: to ewa0:
initial tests have shown, that this could be done:
- re-write BOOT_DEV with 'EWA0' string
- reboot
If you need BOOT_OSFLAGS to be set to 'A' for your NetBSD system and you still want your OpenVMS Alpha system to automatically boot into OpenVMS after power-up, you'll have to change your system root from [SYS0] to [SYSA] (just use SET FILE/ENTER).
If you're interested, send me mail (look at my ITRC profile).
Viele Gruesse nach Rostock ;-)
Volker.
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP