- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Network booting V4.7 from a V5.5 server
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2005 05:50 AM
тАО02-08-2005 05:50 AM
I can do this with LANCP in VMS 6.x with DECnet-Plus (pardon the wrap):
$ MCR LANCP
set node X /addr=08-00-02-xx-xx-xx /file=niscs_load.exe
/root=DISK2:[SYS0.]
However, I can't seem to find the corresponding incantation for VMS 5.5 with DECnet (IV, non-Plus).
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2005 06:00 AM
тАО02-08-2005 06:00 AM
Re: Network booting V4.7 from a V5.5 server
LANCP appeared in VMS V6.2. It provides an alternate MOP load mechanism when the customer does not want to run DECnet at all.
DECnet-Plus, by the way, has its own built-in MOP load mechanism that does not depend on LANCP (at least that was the case when I last played with it).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2005 07:42 AM
тАО02-08-2005 07:42 AM
Re: Network booting V4.7 from a V5.5 server
It's easy to set up a node to boot with @CLUSTER_CONFIG, and I used this as a starting point. I've had a limited success in getting it working -- it will start to boot the alternative operating system, but fail when it doesn't join the cluster.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2005 07:49 AM
тАО02-08-2005 07:49 AM
Re: Network booting V4.7 from a V5.5 server
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2005 07:56 AM
тАО02-08-2005 07:56 AM
Re: Network booting V4.7 from a V5.5 server
Have you tried with DECnet replacing LANCP:
NCP> SET NODE X HARD ADDR 08-00-02-xx-xx-xx
NCP> SET NODE X LOAD ASSIST AGENT sys$share:niscs_load.exe
NCP> SET NODE X LOAD ASSIST PARAMETER DISK2:[SYS0.]
Bojan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2005 08:31 AM
тАО02-08-2005 08:31 AM
Re: Network booting V4.7 from a V5.5 server
But I can do this with DECnet-Plus and LANCP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2005 08:36 AM
тАО02-08-2005 08:36 AM
Re: Network booting V4.7 from a V5.5 server
Node Volatile Characteristics as of 8-FEB-2005 16:27:47
Remote node = 1.499 (OFFICE)
Hardware address = 08-00-2B-2A-22-F8
Load Assist Agent = SYS$SHARE:NISCS_LOAD.EXE
Load Assist Parameter = DISK$VMS062:[SYS0.]
---------------------------------------------
Actually, I'm booting a VMS V6.2 image instead of V4.7, but the sequence should be the same.
---------------------------------------------
Here's what shows up on the console:
%%%%%%%%%%% OPCOM 8-FEB-2005 16:28:28.13 %%%%%%%%%%%
Message from user DECNET on SIMH55
DECnet event 0.7, aborted service request
From node 1.400 (SIMH55), 8-FEB-2005 16:28:28.11
Circuit QNA-0, Line open error, File open error, Load file
%SYSTEM-F-ROPRAND, reserved operand fault at PC=0001B0DC, PSL=03C00000
Node = 1.499 (OFFICE), Ethernet address = 08-00-2B-2A-22-F8
The Load Assist Agent is actually run by the boot host. And it can't run the V6.2 image in this case.
So, I tried the following:
NCP>set node office load assist agent sys$library:niscs_load.exe
But it still fails:
%%%%%%%%%%% OPCOM 8-FEB-2005 16:35:55.69 %%%%%%%%%%%
Message from user DECNET on SIMH55
DECnet event 0.7, aborted service request
From node 1.400 (SIMH55), 8-FEB-2005 16:35:55.65
Circuit QNA-0, Line open error, File open error, Load file
%SYSTEM-F-ROPRAND, reserved operand fault at PC=0001B0DC, PSL=03C00000
Node = 1.499 (OFFICE), Ethernet address = 08-00-2B-2A-22-F8
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2005 08:39 AM
тАО02-08-2005 08:39 AM
Re: Network booting V4.7 from a V5.5 server
You'll want to find yourself a copy of the DECnet Phase IV documentation and read up on how to set up a MOP loader and see if you find any further answers there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2005 09:27 AM
тАО02-08-2005 09:27 AM
Re: Network booting V4.7 from a V5.5 server
Remote node = 1.499 (OFFICE)
Hardware address = 08-00-2B-2A-22-F8
Load file = VMB.EXE
Load Assist Agent = SYS$SHARE:NISCS_LAA.EXE
Load Assist Parameter = DISK$VMS062:
Unfortunately, that fails with:
%%%%%%%%%%% OPCOM 8-FEB-2005 17:22:45.11 %%%%%%%%%%%
Message from user DECNET on SIMH55
DECnet event 0.7, aborted service request
From node 1.400 (SIMH55), 8-FEB-2005 17:22:45.09
Circuit QNA-0, Line open error, File open error, Load file
%LAA-F-RMTNOTCLS, remote node is not a VAXcluster member
Node = 1.499 (OFFICE), Ethernet address = 08-00-2B-2A-22-F8
*sigh*
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2005 09:33 AM
тАО02-08-2005 09:33 AM
Re: Network booting V4.7 from a V5.5 server
Hmmm. The V4.7 system MOP-downloads embedded MicroVAX II's in test equipment. It's quite possible that they're running VAXELN.
At this moment, I don't have access to the system to determine if the MV II's are running VMS or not.