NET$MGMT_HELP.HLB  —  mop
   The MOP module is located in the Application layer described by the
   Digital Network Architecture. MOP has a direct connection with the Data
   Link layer; thus, for certain functions, MOP can bypass the higher layers
   in the DNA protocol tower.  This is useful for nodes which do not yet have
   all the higher layers of DNA protocol towers installed.  Functions
   provided by the MOP module include down-line loading, up-line dumping,
   and communications testing.

  The hierarchy of MOP Module Entities is shown with indentation as follows:

                           MOP
                             Client
                             Circuit
                               Operation
                               Station

   The MOP entity is the top-level entity in the hierarchy of entities
   belonging to the MOP module.

1  –  character

     SUPPORTED FUNCTIONS

         MOP components supported on the system. This is a read-only
         attribute.

         DUMP SERVER
         LOAD SERVER
         LOOP REQUESTER
         QUERY REQUESTER
         CONSOLE REQUESTER
         CONFIGURATION MONITOR

     VERSION

         Version number of the Maintenance Operations Protocol specification
         to which the implementation conforms. This is a read-only attribute.

2  –  status

     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

   A MOP Circuit entity is a data link circuit on which MOP services are
   available. The status attribute functions specifies the services enabled
   on the circuit.

3.1  –  character

     KNOWN CLIENTS ONLY
         Default: False                            Value: Boolean

         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.

     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.

     RETRANSMIT TIMER
         Default: 4                               Value: 1-30

         Time, in seconds, to wait for a response before retransmitting a MOP
         protocol message.

     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 OSF/1 loop only, DDCMP OpenVMS only, and LAPB
         OpenVMS only. You cannot modify this characteristic.

3.2  –  counters

     DUMP REQUESTS COMPLETED

         Number of dump service requests that completed successfully.

     FAILED DUMP REQUESTS

         Number of dump service requests that could not be completed.

     FAILED LOAD REQUESTS

         Number of load service requests that could not be completed.

     LOAD REQUESTS COMPLETED

         Number of load service requests that completed successfully.

     UNRECOGNIZED DUMP CLIENTS

         Number of dump service requests that could not be processed because a
         required client database entry could not be found.

     UNRECOGNIZED LOAD CLIENTS

         Number of load service requests that could not be processed because a
         required client database entry could not be found.

3.3  –  status

     FUNCTIONS

         Which optional MOP functions are currently enabled for this circuit.

4  –  circ OPER

   The MOP Circuit operation entities are created automatically by MOP for
   all operations, including those initiated by NCL action directives  and
   those initiated by automatic load and dump service.  They are deleted when
   the corresponding operation is complete.

4.1  –  status

     ADDRESS

         For LANs only, specifies the address of the client system.

     CLIENT

         Client name of the client entity associated with the operation, if
         such an entity exists.

     OPERATION

         The operation being performed boot, dump, load, loop, query, or test.

5  –  cir_sta

   The MOP Circuit Station entities are created automatically by the
   Configuration Monitor. They are deleted when the circuit entity is deleted.

   The Configuration Monitor function must be enabled to obtain the status
   information used by the show MOP Circuit Station command.

5.1  –  status

     COMMAND SIZE

         Maximum acceptable console command size. A zero value means it is not
         applicable.

     CONSOLE USER

         LAN address of the system which currently has the console reserved;
         all zeroes if the console is not in use.

     DATA LINK

         Data Link protocol used by the remote station.

     DEVICE

         Type of communication device used by the remote station.

     DSDU SIZE

         Maximum allowed size for a MOP message, not including data link
         protocol overhead.

     FUNCTIONS

         The set of functions supported: loop server, dump requester, primary
         loader, secondary loader, boot, console carrier, and counters.

     HARDWARE ADDRESS

         Default data link address for the circuit on which the system ID was
         transmitted by the remote station.

     LAST REPORT

         Time at which the most recent system ID message was received.

     MOP VERSION

         Highest version of the MOP protocol supported by the remote station.

     NODE ID

         Node ID for the remote station.  If not reported, the null ID
         00-00-00-00-00-00 is displayed.

     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:.".

     RESERVATION TIMER

         Console reservation timer, in seconds.  A zero values means it is not
         applicable.

     RESPONSE SIZE

         Maximum acceptable console response size. A zero value means it is not
         applicable.

6  –  client

   A MOP Client entity is a set of default characteristics used by these MOP
   functions: dump/load server, load requester,  loop requester, and console
   requester. When a command or a request for one of these services does not
   supply all of the required arguments, the values stored by the client are
   used to perform the operation.  The client-name refers to the client managed
   by this command.

6.1  –  character

     ADDRESSES
         Default: Empty Set                    Values: Set of LAN Address

         Set of LAN addresses for this client on the circuit specified by the
         circuit characteristic.  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

     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.

     DEVICE TYPES
         Default: No device type              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.

     DIAGNOSTIC IMAGE
         Default: No File                     Value: Sequence of file specs

         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.

     DUMP ADDRESS
         Default: 1                           Value: 0 - (2 to the 23rd -1)

         Memory address at which to begin an upline dump.

     DUMP FILE
         Default: No File                     Value: Sequence of file specs

         Files to write to when the client is upline dumped.  File
         identifications are interpreted according to the file system of the
         local system.

     MANAGEMENT IMAGE
         Default: No File                     Value: Sequence of file specs

         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.

     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.

     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.

     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.

     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.

     SCRIPT FILE
         Default: No File                      Value: Sequence of file specs

         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.

     SECONDARY LOADER
         Default: No File                       Value: Sequence of file specs

         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.

     SYSTEM IMAGE
         Default: No File                       Value: Sequence of file specs

         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.

     TERTIARY LOADER
         Default: No File                        Value: Sequence of file specs

         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.

     VERIFICATION
         Default: %X00-00-00-00-00-00-00-00      Value: 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.
Close Help