Causes the system specified by node-id to send a boot message to
an adjacent system. Circuit-name specifies the name of the circuit
over which the boot operation is to occur.
boot [node node-id] mop circuit circuit-name -
address lan-address [,optional arguments...]
If an Address is not supplied in the command on a LAN circuit, then
the Client argument must be specified so the address information
can be obtained from the MOP Client database.
boot [node node-id] mop circuit circuit-name -
client client-name [,optional arguments...]
Optional arguments for this boot mop circuit command are: device,
script id, software id, and verification.
The NCL boot mop circuit and boot mop client commands are similar
to the NCP trigger command.
1 – address
Address is the LAN address of the remote system on that circuit.
This argument is required for LAN circuits. If you do not supply
this information as an argument for this command, you must
specify a Client in the MOP Client database which can provide
default Address information.
boot [node node-id] mop circuit circuit-name -
address lan-address [,optional arguments...]
Optional arguments for this boot mop circuit command are: device,
script id, software id, and verification.
Example:
boot mop circ csmacd-1 address 08-00-2B-00-33-44
2 – client
Client-name is the client entity to be used for this boot
operation. The default information for this client is obtained
from the MOP Client database. Address information for this
client must be present in the database if it is not provided
on the command line.
boot [node node-id] mop circuit circuit-name -
client client-name [,optional arguments...]
Optional arguments for this boot mop circuit command are:
device, script id, software id, and verification.
Example:
boot mop circuit csmacd-1 client lamchp
3 – device
Device is an optional argument which can be used if the target
system requires device information for the boot operation.
Address information is required for the boot mop circuit command;
it must be obtainable either from the command line or from the
MOP Client database.
boot [node node-id] mop circuit circuit-name -
address lan-address, device device-string
Or, to override any default Device Types information for this
Client in the MOP Client database:
boot [node node-id] mop circuit circuit-name -
client client-name, device device-string
Examples:
boot mop circuit fddi-1 address 08-00-2b-00-33-44, device "sva"
boot mop circuit csmacd-1 client lamchp, device "sva"
4 – script_id
Script Id is an optional argument which can be used if a Script
File is required by the target system for the boot operation.
Address information is required for the boot mop circuit command;
it must be obtainable either from the command line or from the
MOP Client database.
boot [node node-id] mop circuit circuit-name -
address lan-address, script id string
Or, to override any default Script File information for this
Client in the MOP Client database:
boot [node node-id] mop circuit circuit-name -
client client-name, script id string
Examples:
boot mop circuit fddi-1 address 08-00-2b-00-33-44, script id "-1"
boot mop circuit csmacd-1 client test, script id "-1"
5 – software_id
Software Id is an optional argument which can be used if a
System Image is required by the target system for the boot
operation. Address information is required for the boot mop
circuit command; it must be obtainable either from the command
line or from the MOP Client database.
boot [node node-id] mop circuit circuit-name -
address lan-address, software id string
Or, to override any default System Image information for this
Client in the MOP Client database:
boot [node node-id] mop circuit circuit-name -
client client-name, software id string
Examples:
boot mop circuit fddi-1 address 08-00-2b-00-33-44, software id "-1"
boot mop circuit csmacd-1 client lamchp, software id "-1"
6 – verification
Verfication is a string that must match a verification code at
the receiving system in order to trigger the bootstrap mechanism.
The default verification is '0000000000000000'H. Verification is
an optional argument, but Address information is required, either
from the command line or from the MOP Client database.
boot [node node-id] mop circuit circuit-name -
address lan-address, verification hex-string
Or, to override any default Verification information for this
Client in the MOP Client database:
boot [node node-id] mop circuit circuit-name -
client client-name, verification hex-string
Examples:
boot mop circuit fddi-1 address 08-00-2b-00-33-44, -
verification %x0000000000000011
boot mop circuit csmacd-1 client lamchp, -
verification %x0000000000000011
7 – Exception Messages
o data link error
An error was reported by the Data Link layer.
o unrecognized client
There is no client with the specified identification in the MOP
Client database. Run net$configure to add that client entity
to the MOP Client database.
o unrecognized circuit
There is no circuit with the specified identification.
o required argument omitted
An Address must be provided either in the command line or the
MOP Client database.
o entity class not supported (OpenVMS)
MOP is not registered with EMAA. The NET$MOP process is probably
not started. For instructions on how to restart the MOP process,
refer to HELP NETWORK_MANAGEMENT MOP.