1 – event_dispatcher
The test command is used by the manager to request that an event
be logged to test the entire event logging subsystem. This
directive tests the complete event logging system from entity
to manager and causes the test requested event to be logged.
test [node node-id] event dispatcher
2 – mop
2.1 – circuit
Initiates an XID test between the node specified and the node
indicated by the address or client argument.
test [node node-id] mop circuit circuit-name -
address lan-address [,optional argument...]
The Address information is required. If Address is not specified
in the command, then a Client must be specified which can supply
the address information.
test [node node-id] mop circuit circuit-name -
client client-name [,optional argument...]
The optional arguments for the test command are: count, format,
length, and sap.
Examples:
test mop circuit csmacd-1 address 08-00-2b-45-77-ED
test mop circuit csmacd-1 -
client lamchp ! Client gives default Address
The test requester function must be enabled on the MOP Circuit
to perform the test operation. You may enable this function
using:
enable mop circuit circuit-name function {test requester}
2.1.1 – SAP
The optional SAP argument specifies the Service Access Point on
the target system to which the XID message is to be sent. SAP is
an octet (00-FF). The default SAP is 00.
test [node node-id] mop circuit circuit-name -
address lan-address, -
sap octet [,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.
test [node node-id] mop circuit circuit-name -
client client-name, -
sap octet [,optional arguments...]
Examples:
test mop circuit csmacd-1 address 08-00-2b-00-13-4F, sap ff
test mop circuit fddi-1 client mynode, sap 55
2.1.2 – address
test [node node-id] mop circuit circuit-name -
address lan-address [,optional argument...]
The Address information is required. If Address is not specified
in the command, then a Client must be specified which can supply
the address information.
2.1.3 – client
test [node node-id] mop circuit circuit-name -
client client-name [,optional argument...]
Address information is required. If Address is not specified
in the command, then the specified Client must supply the address
information.
2.1.4 – count
The optional Count argument is an integer between 0-4294967295
which specifies the number of messages to be tested. The default
count is 1.
test [node node-id] mop circuit circuit-name -
address lan-address, -
count integer [,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.
test [node node-id] mop circuit circuit-name -
client client-name, -
count integer [,optional arguments...]
Examples:
test mop circuit csmacd-1 address 08-00-2b-00-13-4F, count 50
test mop circuit fddi-1 client mynode, count 10
2.1.5 – format
The optional Format argument is an octet (00-FF) which specifies
the value of each byte in the test data. The default results in
alternating 0 and 1 bits (55).
test [node node-id] mop circuit circuit-name -
address lan-address, -
format octet [,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.
test [node node-id] mop circuit circuit-name -
client client-name, -
format octet [,optional arguments...]
Examples:
test mop circuit csmacd-1 address 08-00-2b-00-13-4F, format FF
test mop circuit fddi-1 client mynode, format 00
2.1.6 – length
The optional Length argument specifies the length of the test
data part of each message. The maximum and minimum permitted
values depend on the particular data link in use. The range is
0-4294967295. The default length is 40.
test [node node-id] mop circuit circuit-name -
address lan-address, -
length integer [,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.
test [node node-id] mop circuit circuit-name -
client client-name, -
length integer [,optional arguments...]
Examples:
test mop circuit csmacd-1 address 08-00-2b-00-13-4F, length 20
test mop circuit fddi-1 client mynode, length 45
2.1.7 – Exception Messages
o data link error
An error was reported by the Data Link layer. Ascertain that
the query requester function is enabled on the MOP circuit.
o unrecognized client
There is no client with the specified identification.
o unrecognized circuit
There is no circuit with the specified identification.
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.
o timeout
Operation has timed out.
2.2 – client
Initiates an XID test between the node specified and the node
specified by the client.
test [node node-id] mop client client-name [optional arguments...]
The Address and Circuit information is required. If that
information is not specified in the MOP client database, then it
must be supplied in the command:
test [node node-id] mop client client-name -
circuit circuit-name, -
address lan-address [,optional arguments...]
The optional arguments for the test command are: count, format,
length, and sap.
Examples:
test mop client lamchp ! Client gives the Address and Circuit
test mop client lamchp - ! Client gives default Circuit
address 08-00-2b-45-77-ED
The test requester function must be enabled on the MOP Circuit
to perform the test operation. You may enable this function
using:
enable mop circuit circuit-name function {test requester}
2.2.1 – SAP
The optional SAP argument specifies the Service Access Point on
the target system to which the XID message is to be sent. SAP is
an octet (00-FF). The default SAP is 00.
test [node node-id] mop client client-name -
sap octet [,optional arguments...]
If an Address and Circuit are not supplied by the MOP client
database, then that information must be provided in the command:
test [node node-id] mop client client-name -
circuit circuit-name, -
address lan-address, -
sap octet [,optional arguments...]
Examples:
test mop client lamchp sap ff
test mop client lamchp circuit fddi-1, -
address AA-00-04-00-34-56, sap 55
2.2.2 – address
Address of the node to receive the XID test message.
test [node node-id] mop client client-name -
address lan-address [,optional arguments...]
The Address and Circuit information is required. If they are not
specified in the MOP Client database, that information must be
included in the command.
2.2.3 – circuit
Circuit over which the XID test message is to be sent.
test [node node-id] mop client client-name -
circuit circuit-name [,optional arguments...]
The Address and Circuit information is required. If they are not
specified in the MOP Client database, that information must be
included in the command.
2.2.4 – count
The optional Count argument is an integer between
0-4294967295 which specifies the number of messages to be tested.
The default count is 1.
test [node node-id] mop client client-name -
count integer [,optional arguments...]
If an Address and Circuit are not supplied by the MOP client
database, then that information must be provided in the command:
test [node node-id] mop client client-name -
circuit circuit-name, -
address lan-address, -
count integer [,optional arguments...]
Examples:
test mop client lamchp count 50
test mop client lamchp, circuit fddi-1, -
address aa-00-04-00-34-56, count 10
2.2.5 – format
The optional Format argument is an octet (00-FF) which specifies
the value of each byte in the test data. The default results in
alternating 0 and 1 bits (55).
test [node node-id] mop client client-name -
format octet [,optional arguments...]
If an Address and Circuit are not supplied by the MOP client
database, then that information must be provided in the command:
test [node node-id] mop client client-name -
circuit circuit-name, -
address lan-address, -
format octet [,optional arguments...]
Examples:
test mop client lamchp - ! Client gives Address and Circuit
format FF
test mop client lamchp, - ! Client gives default Circuit
address aa-00-04-00-34-56, format 00
2.2.6 – length
The optional Length argument specifies the length of the test
data part of each message. The maximum and minimum permitted
values depend on the particular data link in use. The range is
0-4294967295. The default length is 40.
test [node node-id] mop client client-name -
length integer [,optional arguments...]
If an Address and Circuit are not supplied by the MOP client
database, then that information must be provided in the command:
test [node node-id] mop client client-name -
circuit circuit-name, -
address lan-address, -
length integer [,optional arguments...]
Examples:
test mop client lamchp - ! Client gives Address and Circuit
length 20
test mop client lamchp - ! Client gives default Address
circuit fddi-1, length 45
2.2.7 – Exception Messages
o data link error
An error was reported by the Data Link layer. Ascertain that
the query requester function is enabled on the MOP circuit.
o unrecognized client
There is no client with the specified identification.
o unrecognized circuit
There is no circuit with the specified identification.
o timeout
Operation has timed out on the loop command.
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.