Table of Contents
Advertisement
RTR Monitoring
5.2 Standard Monitor Pictures
Table 5–1 (Cont.) Standard Monitor Pictures
Picture name
Description
traffic
Displays a list of the links to other nodes. Shown for each link are: byte rate, packet
rate, message rate and congestion, in both directions. Average packets per second is
also shown.
trans
Displays transactions for a frontend, router and backend.
v2calls
Shows RTR Version 2 verb usage through the interoperability subsystem. The screen
layout is identical to the RTR Version 2 monitor calls picture.
xa
Displays XA counter information including success and failure as well as call and
readonly counters.
The following sections describe the more commonly used standard monitor
pictures in detail.
5.2.1 Monitor ACCFAIL (Link Acceptance Failures)
When configuring RTR it can happen that nodes sometimes fail to connect
up. Whilst the cause of the error can be viewed on the initiator side with the
MONITOR NETSTAT picture, it can be difficult to pinpoint the problem when
looking at the other end of the link. The monitor picture ACCFAIL can be used to
display the reason for the local node to refuse to accept connections. An example:
================================================================================
U n a c c e p t a b l e
Most recent links on which a connection attempt was declined
Node: LENGTH
--------------------------------------------------------------------------------
Link Transport Name(s)
--------------------------------------------------------------------------------
ilira
dmark.zko.dec.com
breal
DMARK DEC:.ZKO.DMARK
ilira
dmark.zko.dec.com
breal
sfranc
breal
DMARK DEC:.ZKO.DMARK
--------------------------------------------------------------------------------
List entries are reused in a cyclical fashion; the most
recent entry is highlighted.
================================================================================
Some of the errors that can be displayed by ACCFAIL are:-
•
RTR_STS_NOTRECOGNISED - "node not recognized"
The local node has received a connection request over a link that is not
configured in any facility on the local machine. If you expected the connection
to succeed as the result of having a template link defined, check carefully the
names displayed in the monitor picture. These are the names obtained from
the network transport over which the link connection attempt was received,
and it is with these that a match with a template (wildcard specification)
link must succeed. Bear in mind that the name match is performed in a case
sensitive manner. Names corresponding to TCP links may or may nor contain
5–4 RTR Monitoring
L i n k s
Wed Jan 7 1998 10:51:00
Reason for failure
node is not configured for the facility
node not recognized
facility name not matched
node not recognized
node is not configured for the facility
node not recognized
facility name not matched
node role definitions do not match for
facility name not matched
node not recognized
Advertisement
Table of Contents
