![]() |
![]() HP OpenVMS Systemsask the wizard |
![]() |
The Question is: 1) Having installed DECnet-plus on OpenVMS 7.1 this will bring up a few small problems. In the "old" days i just could add a new node by typing ncp> define node ds90l address 10.5 hardware 08-00-01-06-0a-a0 service cir ewa-0 ncp> set node ds90l all now i just can't seem to do the same anymore. I looked in the DECnet-plus manuals but there is no reference of specifing a hardware address anymore. Is this still possible. BTW i trying to install a new Dec terminal server and try to talk to it over LAT. 2) We have a Alphastation 466 and a VaxStation 4096 both running OpenVMS 7.1 and DECnet-plus. We want to make a small cluster of these two systems to share the disks. Setingup was straightforeward. But durring boot we get a strange error message stating s omething with license. We can't read the exact message because the system trying to reboot again. i found some reference that a two system cluster is diffrent to other versions but can't seem to find this in the manuals. Regards Otto Meijer The Answer is : For your specific operation around downloading via MOP, please see the LANCP tool. (Downloads via DECnet-Plus and DECnet Phase IV are also available, but starting in V6.2 LANCP can be used -- regardless of the presence of DECnet.) Using NCL: $ ncl create mop client <name> $ ncl set mop client <name> address {08-00-2b-xx-xx-xx} $ ncl set mop client <name> system image {"<full_sys_file_spec>"} $ ncl set mop client <name> mana image {"<full_bin_file_spec>"} $ ncl set mop client <name> dump file {"<full_dmp_file_spec>"} $ ncl set mop client <name> circuit <circuit_name> The Wizard tends to prefer to use LANCP, simply because it is not tied to any networking software. (If you choose to use LANCP, you generally MOP service via DECnet -- via DECnet-Plus or via DECnet Phase IV.) -- Without specifics of the license message, it is difficult to determine what the specific problem. More interesting right now than the particular license message is the reason the system reboots again, that tends to point to another problem. Please see the OpenVMS FAQ for a discussion of EXPECTED_VOTES and the OpenVMS quorum scheme, and comments on two-node cluster configurations.
|