show [node node-id] mop attribute [,attribute...]
all [attributes]
all characteristics
all status
Example:
show mop all
show mop state, supported functions
1 – Characteristics
o supported functions
MOP components supported on the system. This is a read-only
attribute.
configuration monitor load server
console requester loop requester
dump server query requester
load requester (Tru64 UNIX) test requester
o version
Default: Current version number
Version number of the Maintenance Operations Protocol
specification to which the implementation conforms. This is a
read-only attribute.
2 – Status
o state
State of the mop entity. This is a read-only attribute.
off The mop entity is disabled.
on The mop entity is enabled.
3 – circuit
show [node node-id] mop -
circuit circuit-name attribute [,attribute...]
all [attributes]
all characteristics
all counters
all identifiers
all status
Example:
show mop circuit * name, functions
show mop circuit fddi-1 all
3.1 – Identifiers
o name
Simple name assigned to the mop circuit when it was created.
3.2 – Characteristics
o known clients only
Default: False Value: True or False
Specifies whether MOP attempts to service load requests from
remote systems which do not have a corresponding client entity.
Some network servers are designed to request specific software
by name, and in such a case there is no need for a client entity
to exist. By default, MOP tries to process requests for named
software from unknown clients. Set this attribute to true if you
wish MOP to ignore such requests.
o link name
Default: No name Value: Data Link entity name
Name of a station entity in the Data Link layer module indicated
by the type characteristic. This name is passed to the Data Link
layer module when MOP opens a portal for the circuit.
o retransmit timer
Default: 4 Value: 1-30
Time (in seconds) to wait for a response before retransmitting a
MOP protocol message.
o type
Specifies the circuit type. This characteristic is set when the
circuit is created (see the create command). The possible types
are CSMA-CD, FDDI, HDLC (Tru64 UNIX loop only), DDCMP (OpenVMS VAX
only), and LAPB (OpenVMS only). You cannot modify this
characteristic.
3.3 – Counters
o creation time
Time this entity was created.
o dump requests completed
Number of dump service requests that completed successfully.
o failed dump requests
Number of dump service requests that could not be completed.
o failed load requests
Number of load service requests that could not be completed.
o load requests completed
Number of load service requests that completed successfully.
o unrecognized dump clients
Number of dump service requests that could not be processed
because a required client database entry could not be found.
o unrecognized load clients
Number of load service requests that could not be processed
because a required client database entry could not be found.
3.4 – Status
o functions
Which optional MOP functions are currently enabled for this
circuit.
configuration monitor load server
console requester loop requester
dump server query requester
load requester (Tru64 UNIX) test requester
To enable mop circuit functions, see the enable mop circuit
command.
o uid
Entity's unique identifier, which is generated when the entity is
created.
3.5 – operation
show [node node-id] mop -
circuit circuit-name -
operation operation-name attribute [,attribute...]
all [attributes]
all identifiers
all status
Example:
show mop circuit csmacd-1 operation * all
Displays mop circuit operation entities which are created
automatically by MOP for all operations, including those
initiated by NCL commands and those initiated by automatic
load and dump service. These entities are deleted when the
corresponding operation is commplete.
3.5.1 – Identifier
o name
Simple name of the operation entity that is generated
automatically by MOP. The simple name is derived from the
operation being performed (load or dump) and a numeric
suffix added to ensure uniqueness.
3.5.2 – Status
o address
For LANs only, specifies the address of the client system.
o client
Client name of the client entity associated with the operation,
if such an entity exists.
o operation
The operation being performed (boot, dump, load, loop, query, or
test).
3.6 – station
show [node node-id] mop -
circuit circuit-name -
station station-name attribute [,attribute...]
all [attributes]
all identifiers
all status
Example:
show mop circuit csmacd-1 station * all
Displays mop circuit station entities which are created
automatically by the Configuration Monitor. They are
deleted when the circuit entity is deleted.
NOTE
The Configuration Monitor function must be enabled on the
mop circuit to obtain the status information used by the
show mop circuit station command. Refer to the enable
mop circuit command for more information.
3.6.1 – Identifier
o name
Name of the station entity, generated automatically by the
Configuration Monitor. The name is identical to the source LAN
address for the System ID message.
3.6.2 – Status
o command size
Maximum acceptable console command size. A zero value means it is
not applicable.
o console user
LAN address of the system which currently has the console
reserved; all zeroes if the console is not in use.
o data link
Data Link protocol used by the remote station.
o device
Type of communication device used by the remote station.
o dsdu size
Maximum allowed size for a MOP message, not including data link
protocol overhead.
o functions
The set of functions supported: loop server, dump requester,
primary loader, secondary loader, boot, console carrier, and
counters.
o hardware address
Default data link address for the circuit on which the system ID
was transmitted by the remote station.
o last report
Time at which the most recent system ID message was received.
o mop version
Highest version of the MOP protocol supported by the remote
station.
o node id
Node ID for the remote station. If not reported, the null ID
(00-00-00-00-00-00) is displayed.
o node name
Node name for the remote station, as a DECdns full name. If not
reported by the remote station, the null name is used; this is
displayed as "0:.".
o reservation timer
Console reservation timer, in seconds. A zero values means it is
not applicable.
o response size
Maximum acceptable console response size. A zero value means it
is not applicable.
4 – client
show [node node-id] mop -
client client-name attribute [,attribute...]
all [attributes]
all characteristics
all identifiers
4.1 – Identifiers
o name
Simplename assigned to the MOP Client entity when it was created.
4.2 – Characteristics
o addresses
Default: Empty set Value: Set of LAN addresses
Set of LAN addresses for this client on the circuit specified by
the circuit characteristic.
For OpenVMS, Phase IV nodes can use an extended DECnet LAN address in
addition to their hardware address, so you must include both of these
addresses in the addresses set. To calculate the extended DECnet
address, express the Phase IV node address as a four-digit hex
integer, then add the prefix AA-00-04-00.
For example, if the Phase IV node address is 4.260:
4.260
o circuit
Default: No circuit Value: Circuit-id
Name of the MOP circuit that corresponds to the Data Link circuit
that is to be used for communicating with this client.
o device types (OpenVMS)
Default: No device types Value: Set of device types
Specifies one or more device types associated with this client.
Use device types and omit addresses if you want to set up a
generic client entity; the entity will be used for any incoming
load or dump requests that specify a matching communications
device type.
To determine the communications device type for a particular
network server, consult the server documentation, or use the
Configuration Monitor Function of MOP.
o diagnostic image
Default: No file Value: Sequence of file specifications
Files to be loaded when the client requests a diagnostic image
during a downline load operation. File identifications are
interpreted according to the file system of the local system.
o dump address
Default: 1 Value: 0 to 232 -1
Memory address at which to begin an upline dump.
o dump file
Default: No file Value: Sequence of file specifications
Files to write to when the client is upline dumped. File
identifications are interpreted according to the file system
of the local system.
o management image
Default: No file Value: Sequence of file specifications
Files to be loaded when the client requests a management image
during a downline load operation. File identifications are
interpreted according to the file system of the local system.
o phase iv client address
Default: 0.0 Value: Phase IV address
Phase IV node address given to the client system when it is
downline loaded. This address is passed in a load parameters
message; whether it is needed depends on the software being
loaded.
o phase iv client name
Default: No name Value: Phase IV name
Phase IV node name given to the client system when it is downline
loaded. This name is passed in a load parameters message; whether
it is needed depends on the software being loaded.
o phase iv host address
Default: 0.0 Value: Phase IV address
Phase IV node address to be passed as the host node address when
a client is downline loaded. This address is passed in a load
parameters message; whether it is needed depends on the software
being loaded.
o phase iv host name
Default: No name Value: Phase IV name
Phase IV node name that is passed as the host name when the
client is downline loaded. This name is passed in a load
parameters message; whether it is needed depends on the software
being loaded.
o script file
Default: No file Value: Sequence of file specifications
Files to be loaded when the client requests a CMIP initialization
script during a downline load operation. File identifications are
interpreted according to the file system of the local system.
o secondary loader
Default: No file Value: Sequence of file specifications
Files to be loaded when the client requests a secondary loader
during a downline load operation. File identifications are
interpreted according to the file system of the local system.
o system image
Default: No file Value: Sequence of file specifications
Files to be loaded when the client requests an operating system
image during a downline load operation. File identifications are
interpreted according to the file system of the local system.
o tertiary loader
Default: No file Value: Sequence of file specifications
Files to be loaded when the client requests a tertiary loader
during a downline load operation. File identifications are
interpreted according to the file system of the local system.
o verification
Default: %x00-00-00-00-00-00 Hex string
Verification string to be sent in a boot message to this client.
The value must have an even number of digits from 2 to 16.