1 – circuit
Initiates a downline load from the system specified by node-id to
a target system specified by the arguments or by a client.
Circuit-name specifies the name of the circuit over which the load
operation is to occur.
load [node node-id] mop circuit circuit-name -
address lan-address, -
system image filespec [,optional arguments...]
The Address and System Image arguments are required for LAN circuits.
If those arguments are not supplied in the command, then the Client
argument must be specified so the required information can be
obtained from the MOP Client database.
load [node node-id] mop circuit circuit-name -
client client-name [,optional arguments...]
Optional arguments for the load mop circuit command are: management
image, script file, secondary loader, tertiary loader, and
verification.
1.1 – address
Address is the LAN address of the remote system on that circuit.
The Address and System Image arguments are required for LAN
circuits. If you do not supply this information in the command,
you must specify a Client in the MOP Client database which can
provide that information.
load [node node-id] mop circuit circuit-name -
address lan-address, -
system image filespec [,optional arguments...]
Optional arguments for the load mop circuit command are:
management image, script file, secondary loader, tertiary
loader, and verification.
Examples:
load mop circ csmacd-1 address 08-00-2B-13-FD-0A, -
system image SH1601ENG.SYS
load mop circ fddi-1 address 08-00-2b-0f-a8-dc, -
system image "@net$niscs_laa($1$dua0:<sys16.>)"
1.2 – client
Client-name is the client entity to be used for this load
operation. The default information for this client is obtained
from the MOP Client database. Address and System Image
information for this client must be present in the database if
it is not provided on the command line.
load [node node-id] mop circuit circuit-name -
client client-name [,optional arguments...]
Optional arguments for the load mop circuit command are:
management image, script file, secondary loader, tertiary
loader, and verification.
Example:
load mop circuit csmacd-1 client lamchp
1.3 – management_image
Management Image is an optional argument which can be used if
a file containing initialization data for the node is required by
the target system. Data is encoded in a product-specific format.
Address and System Image information is required for the load mop
circuit command; that information must be obtainable either from
the command line or from the MOP Client database.
To override any default Management Image information for this
Client in the MOP Client database:
load [node node-id] mop circuit circuit-name -
client client-name, -
management image filespec
Example:
load mop circuit csmacd-1 client lamchp, -
management image MGMT.IMAGE
1.4 – script_file
The optional Script File argument specifies a file containing
initialization data for the node; data is encoded as a sequence
of network management commands in CMIP form. This argument may be
required by the target system.
Address and System Image information is required for the load mop
circuit command; that information must be obtainable either from
the command line or from the MOP Client database.
To override any default Script File information for this
Client in the MOP Client database:
load [node node-id] mop circuit circuit-name -
client client-name, -
script file filespec
Example:
load mop circuit csmacd-1 client lamchp, script file SCRIPT.FILE
1.5 – secondary_loader
The optional Secondary Loader argument specifies the name of a
second file containing the software to be downline loaded. This
argument may be required by the target system.
Address and System Image information is required for the load mop
circuit command; that information must be obtainable either from
the command line or from the MOP Client database.
To override any default Secondary Loader information for this
Client in the MOP Client database:
load [node node-id] mop circuit circuit-name -
client client-name, -
secondary loader filespec
Example:
load mop circuit csmacd-1 client lamchp, -
secondary loader sys$system:secondary_vmb.exe
1.6 – system_image
System Image specifies the file containing the system image to be
downline loaded. The System Image and Address arguments are
required for LAN circuits. If you do not supply this information
in the command, you must specify a Client in the MOP Client
database which can provide that information.
load [node node-id] mop circuit circuit-name -
system image filespec, -
address lan-address [,optional arguments...]
Optional arguments for the load mop circuit command are:
management image, script file, secondary loader, tertiary
loader, and verification.
Examples:
load mop circ csmacd-1 system image SH1601ENG.SYS, -
address 08-00-2B-13-FD-0A
load mop circ fddi-1 -
system image "@net$niscs_laa($1$dua0:<sys16.>)", -
address 08-00-2b-0f-a8-dc
1.7 – tertiary_loader
The optional Tertiary Loader argument specifies the name of a
third file containing the software to be downline loaded. This
argument may be required by the target system.
Address and System Image information is required for the load
mop circuit command; that information must be obtainable either
from the command line or from the MOP Client database.
To override any default Tertiary Loader information for this
Client in the MOP Client database:
load [node node-id] mop circuit circuit-name -
client client-name, -
tertiary loader filespec
Example:
load mop circuit csmacd-1 client lamchp, -
tertiary loader sys$system:tertiary_vmb.exe
1.8 – verification
The optional Verification argument specifies the string that must
match a verification code at the receiving system in order for the
load to be performed. The value must be an even number of digits
from 2 to 16. The default verification is '0000000000000000'H.
Address and System Image information is required for the load mop
circuit command; that information must be obtainable either from
the command line or from the MOP Client database.
To override any default Verification information for this Client
in the MOP Client database:
load [node node-id] mop circuit circuit-name -
client client-name, -
verification hex-string
Example:
load mop circuit csmacd-1 client lamchp, -
verification %x0000000000000011
1.9 – Exception Messages
o data link error
An error was reported by the Data Link layer on the load command.
o unrecognized client
There is no client with the specified identification.
o unrecognized circuit
There is no circuit with the specified identification.
o required argument omitted
Both the Address and System Image arguments are required. If
they are not present in the command line, then a Client must be
specified which can provide that information.
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.
2 – client
Initiates a downline load from the system specified by node-id to
a target system specified by the arguments or by a client.
Client-name is the client entity to be used for this load operation.
The default information for this client is obtained from the MOP
Client database.
load [node node-id] mop client client-name [optional arguments...]
Circuit information for this client must be present in the database
if it is not provided on the command line. The Address and System
Image arguments are also required for LAN circuits. If those
arguments are not supplied in the command, then they must be
obtainable from the MOP Client database.
Optional arguments for the load mop client command are: management
image, script file, secondary loader, tertiary loader, and
verification.
2.1 – address
Address is the LAN address of the remote system on that circuit.
The Address and System Image arguments are required for LAN
circuits. If you do not supply this information in the command,
this information must be present for the specified client in the
MOP Client database. The Circuit argument must also either be
provided on the command line or obtainable from the MOP Client
database.
load [node node-id] mop client client-name -
address lan-address [,optional arguments...]
Optional arguments for the load mop client command are:
management image, script file, secondary loader, tertiary
loader, and verification.
Example:
load mop client lamchp - ! Client provides default Circuit
address 08-00-2B-13-FD-0A ! and System Image
2.2 – circuit
Circuit information is required either on the command line or
from the MOP Client database for the specified client.
Circuit-name specifies the circuit over which the load
operation is to be performed.
The Address and System Image arguments are also required for
LAN circuits. If you do not supply this information in the
command, this information must be present for the specified
client in the MOP Client database.
load [node node-id] mop client client-name -
circuit circuit-name [,optional arguments...]
Optional arguments for the load mop client command are:
management image, script file, secondary loader, tertiary
loader, and verification.
Example:
load mop client lamchp - ! Client provides default Address
circuit csmacd-1 ! and System Image
2.3 – management_image
Management Image is an optional argument which can be used if
a file containing initialization data for the node is required by
the target system. Data is encoded in a product-specific format.
Circuit, Address, and System Image information is required for
the load mop client command; that information must be obtainable
either from the command line or from the MOP Client database.
To override any default Management Image information for this
Client in the MOP Client database:
load [node node-id] mop client client-name -
management image filespec [,optional arguments...]
Example:
load mop client lamchp - ! Client gives default Address,
management image MGMT.IMAGE ! System Image and Circuit
2.4 – script_file
The optional Script File argument specifies a file containing
initialization data for the node; data is encoded as a
sequence of network management commands in CMIP form. This
argument may be required by the target system.
Circuit, Address, and System Image information is required
for the load mop client command; that information must be
obtainable either from the command line or from the MOP Client
database.
To override any default Script File information for this
Client in the MOP Client database:
load [node node-id] mop client client-name -
script file filespec
Example:
load mop client lamchp - ! Client gives default Address,
script file SCRIPT.FILE ! Circuit, and System Image
2.5 – secondary_loader
The optional Secondary Loader argument specifies the name of a
second file containing the software to be downline loaded. This
argument may be required by the target system.
Circuit, Address, and System Image information is required for
the load mop client command; that information must be obtainable
either from the command line or from the MOP Client database.
To override any default Secondary Loader information for this
Client in the MOP Client database:
load [node node-id] mop client client-name -
secondary loader filespec [,optional arguments...]
Example:
load mop client lamchp - ! Client gives Addr, Circ and Sys Image
secondary loader sys$system:secondary_vmb.exe
2.6 – system_image
System Image specifies the file containing the system image to be
downline loaded. The System Image and Address arguments are
required for LAN circuits. If you do not supply this information
in the command, you must specify a Client in the MOP Client
database which can provide that information. The Circuit
argument must also be specified on the command line if that
information is not obtainable from the MOP Client database.
load [node node-id] mop client client-name -
system image filespec [,optional arguments...]
Optional arguments for the load mop client command are:
management image, script file, secondary loader, tertiary
loader, and verification.
Example:
load mop client lamchp - ! Client gives default Address
system image SH1601ENG.SYS ! and Circuit
2.7 – tertiary_loader
The optional Tertiary Loader argument specifies the name of a
third file containing the software to be downline loaded. This
argument may be required by the target system.
Circuit, Address, and System Image information is required for
the load mop client command; that information must be obtainable
either from the command line or from the MOP Client database.
To override any default Tertiary Loader information for this
Client in the MOP Client database:
load [node node-id] mop client client-name -
tertiary loader filespec
Example:
load mop client lamchp - ! Client gives Addr, Circ and Sys Image
tertiary loader sys$system:tertiary_vmb.exe
2.8 – verification
The optional Verification argument specifies the string that must
match a verification code at the receiving system in order for the
load to be performed. The value must be an even number of digits
from 2 to 16. The default verification is '0000000000000000'H.
Circuit, Address, and System Image information is required for
the load mop client command; that information must be obtainable
either from the command line or from the MOP Client database.
To override any default Verification information for this Client
in the MOP Client database:
load [node node-id] mop client client-name -
verification hex-string
Example:
load mop client lamchp - ! Client gives default Address,
verification %x0000000000000011 ! Circuit and System Image
2.9 – Exception Messages
o data link error
An error was reported by the Data Link layer on the load command.
o unrecognized client
There is no client with the specified identification.
o unrecognized circuit
There is no circuit with the specified identification.
o required argument omitted
The Address and System Image arguments are required for LAN
circuits. If they are not present in the command line, then
the MOP Client database entry must provide that information.
Circuit information must also be provided on the command
line or it must be obtainable from the specified MOP Client
entry.
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.