Filter
Top Products
RTR Monitoring
5.2 Standard Monitor Pictures
5.2.6 Monitor Calls
RTR api calls, Node: nodea.zuo.dec.com , PID: 2162 , Process name: -ALL-
Image: -ALL- Fri Feb 12 1999 16:38:05
CALLS client server fail MESSAGES client server pend
open_channel 1 1 0 mt_opened 1 1 0
close_channel 0 0 0 mt_closed 0 0 0
start_tx 0 0 mt_msg1 0 1
send_to_server 1 0 mt_msg1_uncertain 0 0
mt_msgn 0 0
reply_to_client 0 0 mt_reply 0 0
mt_rettosend 0 0
prepare_tx 0 0 mt_prepared 0 0
accept_tx 0 0 0 mt_accepted 0 0 0
reject_tx 0 0 0 mt_rejected 0 0 0
broadcast_event 0 0 0 mt_user_event 0 0 0
set_user_handle 0 0 0 mt_rtr_event 0 0 0
get_tid 0 0 0 mt_prepare 0 0
other other
request_info 3 0 mt_request_info 2 0
set_info 0 0 mt_set_info 0 0
error_text 2 mt_closed 2
set_wakeup 0
calls active fail timeout
receive_message 9 1 2 2
user wakeup 0 0
Displays the total number of RTR API calls and their outcome for the processes
on all the nodes being monitored. Use the
/IDENTIFICATION=process-id
qualifier
to display the values for one specific process, otherwise the total values for all
processes are displayed.
5.2.7 Monitor Channel
RTR CHANNELS BY TYPE PER PROCESS Fri Feb 12 1999 16:41:13
Client Server Call-out
Node ID Process Image Pri. Sby. Router Backend
nodea 2162 2162 1 0 0 0 0
Displays the channels opened by RTR CALL RTR_OPEN_CHANNEL comands.
5.2.8 Monitor Connects
Connection Status Summary
Node: nodea.zuo.dec.com Tue Feb 16 1999 13:02:18
-Executive summary----------------------------------------
Number of links up: 3 (100.%)
Number of links down: 0 (0.0 %)
----------------------------------------------------------
-Detail-------------------------------------------------------------------------
Node -> Link State Arch T’port Fail-reason
--------------:-----:-----:------:----------------------------------------------
nodea->nodea up alpha -
nodea->nodeb up alpha TCP
nodea->nodec up i386 TCP
RTR Monitoring 5–7