Bay Networks Remote Annex 2000, Руководство по установке оборудования

Страница: 54 / 136

Remote Annex 2000 Hardware Installation Guide
Chapter 2 Installing the Remote Annex 2000
2-20
To enable your VAX VMS load host to accept crash dumps:
1 Assign a DECnet node number to your Remote Annex 2000. You can
pick any node number or name as long as it does not conflict with
any node or address already defined within NCP. For example:
$MCR NCP SET NODE 2.69 NAME BINGO
2 Assign a directory and file to receive the crash dump. For example:
$MCR NCP SET NODE 2.69 NAME BINGO DUMP FILE\
DKA200: [ZETKIN.REMOTEANNEX_CRASH]BINGO.DMP
3 Assign the Remote Annex 2000’s hardware address to the node
name. For example:
$MCR NCP SET NODE BINGO\
HARDWARE ADDRESS 00-80-2D-00-1A-DE
4 Issue the equivalent define commands so this crash dump support
continues when your VMS load host is restored.
The VMS load host now supports crash dumps.
Customizing for Multiple Remote Annex Images
The Remote Annex operational code is installed in MOM$LOAD as
OPER_56_ENET.SYS. The Remote Annex does not require that this
be the exact file name and you may want to keep multiple versions
of the Remote Annex software. You can rename Remote Annex
operational images, but they must remain in MOM$LOAD. If you do
change the operational image name from OPER_56_ENET.SYS to
some other name, the new file name plus the extension can be no
longer than 16 characters total. This is due to a MOP restriction of 16
characters in passing the load file name field.