Starts a loop test between the loopback applications on the
specified source and destination nodes.
loop [node node-id] loopback application -
name fullname [,optional arguments...]
loop [node node-id] loopback application -
address tower-set [,optional arguments...]
The node keyword specifies the node from which the loop messages
are sent. If you omit this keyword, the test is performed from the
node on which you issue the loop command. The Name or Address
argument specifies the node whose loop mirror is used to reflect
the messages back to the originator. Either the Name or Address
argument is required, but not both. The MIRRO$SERVER account on
the remote end must have at least the NET$EXAMINE right.
Optional arguments are: format, length, and count.
Examples:
loop loopback application name - ! The "DOMAIN:" namespace
DOMAIN:LAMCHP.SCH.DEC.COM ! nickname is required for IP
! fullnames
loop loopback application name LOCAL:.LAMCHP, count 10
loop loopback application address = {([%x0119], -
[dna_sessioncontrolv3, number = 25], -
[dna_nsp], -
[dna_osinetwork, 49::00-04:AA-00-04-00-1A-10:20])}, -
format ff, count 10
1 – address
Address is the number of the destination for loopback messages
in the form of a protocol tower. Specify either this argument or
the Name argument.
loop [node node-id] loopback application -
address tower-set [,optional argument...]
Optional arguments are: format, length, count.
Examples:
loop loopback application address = {([%x0119], -
[dna_sessioncontrolv3, number = 25], -
[dna_nsp], -
[dna_osinetwork, 49::00-04:AA-00-04-00-1A-10:20])}
loop loopback application address = {([%x0119], -
[dna_sessioncontrolv3, number = 25 ], -
[dna_ositransportV1, %xDEC0 ] , -
[dna_osinetwork, 49::00-04:AA-00-04-00-1A-10:21])}
2 – count
The optional argument Count is the number of loop messages to be
sent to the loop mirror. The test is complete when this number of
loop messages has been reflected back by the loop mirror. The
default is 1, the value must be 0-4294967295.
loop [node node-id] loopback application name full-name, -
count integer [,optional arguments...]
loop [node node-id] loopback application address tower-set, -
count integer [,optional arguments...]
Example:
loop loopback application name DEC:.SCH.LAMCHP, count 10
3 – format
The optional Format argument is an octet (00-FF) which specifies
the value of each byte in the test data part of each loop message.
The default results in alternating 0 and 1 bits (55).
loop [node node-id] loopback application name full-name, -
format octet [,optional arguments...]
loop [node node-id] loopback application address tower-set, -
format octet [,optional arguments...]
Example:
loop loopback application name DEC:.SCH.LAMCHP, format FF
4 – length
The optional argument Length specifies the length, in octets,
of the data field in each loop message. The default is 40,
and the value must be 0-65534.
loop [node node-id] loopback application name full-name, -
length integer [,optional arguments...]
loop [node node-id] loopback application address tower-set, -
length integer [,optional arguments...]
Example:
loop loopback application name DEC:.SCH.LAMCHP, length 80
5 – name
Name is the fullname of the node to which loopback messages are
sent. Specify either this argument or the Address argument, but
not both. Optional arguments are: format, length, count.
loop [node node-id] loopback application -
name full-name [,optional arguments...]
Examples:
loop loopback application name DOMAIN:LAMCHP.SCH.DEC.COM
loop loopback application name DEC:.SCH.LAMCHP
loop loopback application name LOCAL:.LAMCHP, length 80
6 – Exception Messages
o bad data at mirror
There has been an error in the loopback protocol. The possible
errors are:
o The local node sent a loop message with a data field that was
too long.
o The first octet of the loop message was corrupted when it
arrived at the mirror module.
Arguments:
count Requested number of messages in the loopback test
(that is, the value of the count argument).
message Number of the loop messages in which the error
number occurred.
start time Time at which the loopback test began.
o both name and address specified
Both the name and address arguments have been specified. You must
specify one of these arguments, but not both.
o neither name nor address specified
Either the name or address argument must be specified, but not both.
o connection failed
The session control connection to the loop mirror failed.
Arguments:
reason Reason why the connection failed. This is the reason
code provided by session control.
start Time the loopback test began.
time
o data returned differs from data sent
The data field in a loop message reflected back by the loop
mirror is not the same as the data field in the loop message
that was sent.
Arguments:
count Requested number of messages in the loopback test (that
is, the value of the count argument).
format Value for each octet of the data field of the loop
message (that is, the value of the format argument).
length Length of the data field of the loop message, as
requested by the length argument.
message Number of the loop message in which the error occurred.
number
message Contents of the reflected loop message.
returned
start Time the loopback test began.
time
o disconnected
The link to the loop mirror was disconnected before the loopback
test was completed.
Arguments:
count Requested number of messages in the loopback test (that
is, the value of the count argument).
message Number of the loop message in which the error occurred.
number
reason Reason why the link was disconnected. This is the
reason code returned by session control.
start Time the loopback test began.
time
o length too long
The requested length of the data field is greater than the
maximum data field length that the loop mirror can handle.
Arguments:
length Data field length requested, in octets.
maximum Maximum data field length supported by the loop
data mirror.
start Time at which the loopback test began.
time
o namespace name is invalid or not in cache
The fullname provided is not valid. Use a different fullname,
or refer to HELP NETWORK_MANAGEMENT TOOLS DECNET_REGISTER for
information on how to add this node to your node database.