| Previous | Contents | Index |
LINK TRAFFIC IN BYTES Fri Apr 16 1999 17:41:12, NODE: nodea
Bytes received Bytes sent
-------------------------- --------------------------
Count Rate Max Count Rate Max
Total 59201466 6776.0 - 1002579480 113857.0 -
nodea->nodea 3072248 336.0 336.0 3072248 336.0 336.0
nodea->nodeb 42569496 4974.0 4974.0 717457678 84438.0 84438.0
nodea->nodec 13559722 1466.0 1466.0 282049554 29083.0 29083.0
|
Displays a list of the links to other nodes. For each link, the total
number of bytes received and sent on that link and the number of bytes
received and sent per second are displayed. Derived from the
NIO_BYTES_RCVD and NIO_BYTES_SENT counters. The
Max
field represents the maximum rate since the link started.
6.2.22 Monitor Netstat
C o n n e c t i o n S t a t u s D e t a i l
Node: NODEA Mon March 15 1999 09:50:28
Ini Cnf Acc Abo Rej Loss Gain Ctmo Rstr State Type FailCode
Node and Link 12 0 2 12 12 1 3 0 0
NODEA ->nodeb 0 0 0 0 0 0 1 0 0 up alpha
NODEA ->nodec 6 0 0 6 6 0 0 0 0 down ? 76490676
NODEA ->noded 6 0 0 6 6 0 0 0 0 down ? 76490676
NODEA ->nodee 0 0 2 0 0 1 2 0 0 up alpha
|
Displays the link status for connected links in detail and the fail
code for any links on which a connection has failed. Unconnected links
where connections have been lost are highlighted. Link aborts, rejects,
loss, gain, restarts, state and architecture of the remote node are
also displayed. More detail is included than in the MONITOR CONNECTS
display.
6.2.23 Monitor Ortr
oRTR Transaction Controller List on node : rtrdoc
Image: -ALL- at 15:42:55
Server Controllers Client Controller
STC000 CTC000
STC001 CTC001
STC002 CTC002
STC003 CTC003
STC004 CTC004
|
Displays lists of server and client transaction controllers.
6.2.24 Monitor Partit
PARTITION DEFINITIONS Tue Apr 6 1999 10:40:31, NODE: NODEA
Partition name # # Bounds Callout
State Svrs Segs lo hi type
RTR$DEFAULT_PARTITION_16777218 active 1 1 "A" "A" -
RTR$DEFAULT_PARTITION_16777221 active 1 1 "B" "B" -
RTR$DEFAULT_PARTITION_16777217 active 1 1 0 429496 -
|
Partitions are shown in the form partition name if a partition name has been specified using the SET PARTITION command. The number of servers and key segments are shown for each partition. The least-significant byte of the partition's low and high bound is also shown, and callout type (if any). The partition state meanings are given in Table 6-3.
| State | Meaning |
|---|---|
| wt_tr_ok | Server is waiting for routers to accept it |
| wt_quorum | Server is waiting for backend to be quorate |
| lcl_rec | Local recovery |
| lcl_rec_fail | Primary server waiting for access to a restart journal |
| lcl_rec_icpl | Getting next journal to recover from |
| lcl_rec_cpl | Processed all journals for local recovery |
| shd_rec | Shadow recovery |
| shd_rec_fail | Shadow server waiting for access to a restart journal |
| shd_rec_icpl | Shadow getting next journal to recover from |
| shd_rec_cpl | Processed all journals for shadow recovery |
| catchup | Secondary is catching up with primary |
| standby | Server is declared as standby |
| active | Server is active |
| pri_act | Server is active as primary shadow |
| sec_act | Server is active as secondary shadow |
| remember | Primary is running without shadow secondary |
TRANSACTION QUEUES BY PARTITION Fri Sep 08 2000 12:42:53, NODE: NODEA
Partition name Processed Queued #
Txns Msgs Rplys Txn Msg Svrs
RTR$DEFAULT_PARTITION_16842753 5792 5794 0 2 6 3
|
Shows transaction queues on a partition basis. Uses counters from
Transaction Manager (TM) and the Requester/Server configurator (RSC).
6.2.26 Monitor Quorum
QUORUM STATUS BY NODE AND FACILITY Tue Apr 6 1999 10:50:24, NODE: NODEA (node/role counts can be inaccurate for incorrectly configured facilities) States: bad configuration,not connected,minority,uncertain,quorate Node & Facility State CNF RCH QRT NODEA RTR$DEFAULT_FACILITY TR:quorate,BE:quorate 2 2 2 NODEA shadow TR:quorate,BE:minority(node12) 4 2 1 |
Quorum states are shown for router (TR) and backend (BE) nodes and roles in the column State .
The number of roles seen as configured (CNF), reachable (RCH) and
quorate (QRT) are shown for each node, in the columns
node/roles
.
6.2.27 Monitor Recovery
RECOVERY INFORMATION at Tue Apr 6 1999 10:54:50, on NODEA
Last Restart-Recovery Shadow-Recovery
Server Recovery Journal Txns Journal Txns
Partition State Backend Scans Recovered Scans Recovered
------------ ------ ------- ------- --------- ------- ---------
RTR_PARTITA active NODEA 1 0 0 0
RTR_PARTITB active NODEA 1 0 0 0
RTR_PARTITC active NODEA 1 0 0 0
|
Shows the progress of transaction recovery. Last recovery backend is the last backend accessed to recover transactions. If the server state is lcl_rec_fail or shd_rec_fail , this entry is the name of the background that could not be accessed. Journal scans is the number of journal files searched. Transactions recovered is the number of transactions found for this partition.
Server recovery state meanings are shown in Table 6-4.
| State | Meaning |
|---|---|
| wt_tr_ok | Server is waiting for routers to accept it |
| wt_quorum | Server is waiting for backend to be quorate |
| lcl_rec | Local recovery |
| lcl_rec_fail | Primary server waiting for access to a restart journal |
| lcl_rec_icpl | Getting next journal to recover from |
| lcl_rec_cpl | Processed all journals for local recovery |
| shd_rec | Shadow recovery |
| shd_rec_fail | Shadow server waiting for access to a restart journal |
| shd_rec_icpl | Shadow getting next journal to recover from |
| shd_rec_cpl | Processed all journals for shadow recovery |
| catchup | Secondary is catching up with primary |
| standby | Server is declared as standby |
| active | Server is active |
| pri_act | Server is active as primary shadow |
| sec_act | Server is active as secondary shadow |
| remember | Primary is running without shadow secondary |
Rejected Transaction Summary
NODE: NODEA PROCESS: 20413894 Fri Apr 9 1999 10:26:14
Time Pid Chan Reason Status Text
------------------- ------ ------ -------- -----------------------------
Fri Apr 9 10:18:43 20417266 client 0 No server available to handle
Fri Apr 9 10:17:47 20417274 server 0 Client aborted tx
|
Displays the last rtr_mt_rejected message received by each running process.
| Field | Meaning |
|---|---|
| Time | Time of day that the rtr_mt_rejected message was received |
| Pid | Process ID that received the message |
| Chan | Type of channel (client or server) that received the message |
| Reason | Reason field returned in the rtr_status_data_t buffer |
| Status Text | Textual status that describes the reject reason |
Rejected Transaction History
NODE: NODEA PROCESS: 38009A8B Mon Mar 9 1999 10:26:14
Time Chan Reason Status Text
------------------- ------ ------- --------------------------------------
Mon Mar 15 18:06:06 client 0 Client aborted tx
Mon Mar 15 18:06:41 server 0 Normal successful completion
Mon Mar 15 18:06:41 client 0 Server aborted tx
------------------------------------------------------------------------------
number of reject messages: 3
number of accept messages: 0
rejected / total txns (%): 100%
This display should be invoked with the /ID qualifier.
|
Displays the last 10 rtr_mt_rejected messages received by the selected process. This picture should always be invoked with the /ID qualifier. The transaction identifier associated with the rejected transaction can be displayed with the SHOW PROCESS < id >/COUNTER= api_reject* command.
| Field | Meaning |
|---|---|
| Time | Time of day that the rtr_mt_rejected message was generated |
| Chan | Type of channel (client or server) that received the message |
| Reason | Reason field returned in the rtr_status_data_t buffer |
| Status Text | Textual status that describes the reject reason |
TRANSACTION DURATION AT 10:24:51 Fri Apr 9 1999
Process ID, Image Name Client Response Time Server Response Time
seconds 0---1---2---3---4 seconds 0---1---2---3---4
20413894 SERVER.EXE;4 0.000 3.670
20417266 RTR.EXE;75 2.200 3.440
20417274 SERVER.EXE;4 0.000 1.160
|
Displays the elapsed time that a transaction has been active on the
opened channels of a process. On the client, transaction duration is
measured between the
rtr_start_tx
or
rtr_send_tx
call and the receipt of the final
rtr_mt_accepted
or
rtr_mt_rejected
message. A call to
rtr_reject_tx
also marks the end of a transaction. On the server, transaction
duration is measured between receipt of an
rtr_mt_msg1
or
rtr_mt_msg1_uncertain
message and the receipt of the final
rtr_mt_rejected
message or
rtr_reject_tx
call. Accepted transaction end times are recorded when the server
issues an
rtr_receive_message
call to request a new transaction for processing.
6.2.31 Monitor Rolequor
QUORUM COUNTS BY FACILITY Fri Sep 08 2000 14:32:48, NODE: -ALL-
Facility name Router View of Backend View of
Backends Routers Backend Routers
CNF RCH QRT CNF RCH QRT CNF RCH QRT CNF RCH QRT
RTR$DEFAULT_FACILITY 1 1 1 1 1 1 1 1 1 1 1 1
|
Displays detail by facility of data from the Monitor Quorum screen.
6.2.32 Monitor Routers
ROUTER TRANSACTION COUNTERS AT 14:33:29 Fri Sep 08 2000
Node: -ALL-
Facility: -ALL-
Count Rate 10 20 30 40 50 60 70 80 90 100
Starts: 116641 25.7
Enqueues: 116641 25.7
Commits: 116641 25.6
Aborts: 0 0.0
|
Displays information on a router node. It gives an indication of the
utilization of the router in terms of transactions and broadcasts
routed through this node. Useful to monitor performance or locate
problems. Uses counters in the Transaction Manager (TM) subsystem.
6.2.33 Monitor Routing
ROUTING STATISTICS BY FACILITY Thu Apr 15 1999 14:34:20, NODE: -ALL-
Facility name Transactions Broadcasts
Count Rate Count Rate
Total 118489 39.2 68444 994.0
RTR$DEFAULT_FACILITY 118489 39.2 68444 994.0
|
Displays statistics of transaction and broadcast traffic by facility.
Rate is the number of transactions or broadcasts per second within the
monitoring interval.
6.2.34 Monitor Rscbe
Most Recent RSC Dclsrv Calls History on Backend NODEA Thu Mar 4 1999,15:19:41
Partition name: RTR$DEFAULT Partition Start Time: THU MAR 4 15:18:22 1999
Image Name: RTR.EXE
T-delta RSC calls router state seq_nr
0 send_dcl_to_master nodez wait_for_response 0
1 recv_status_ok nodez rstart_rvy 1
1 send_dcl_to_master nodez rstart_rvy_incomp 1
1 recv_status_ok nodez rstart_rvy 1
1 send_dcl_to_master nodez rstart_rvy_incomp 1
1 recv_status_ok nodez active 1
1 send_dcl_to_other node10 active 1
1 recv_status_ok node10 active 1
|
Displays backend request to server messages and declared state for routers.
NETWORK STALLS AT Fri Sep 08 2000 15:35:03, ON NODE: TR1
Messages Bytes Link Stalls
Issued Rate Sent Drops Secs <3s <10s <30s >30s Totals
Total 5467 0.0 327148 2 33 23 1 0 0 24
TR1 -> TR1 29 0.0 3718 0 0 0 0 0 0 0
TR1 -> FE2 509 0.0 20707 0 4 4 0 0 0 4
TR1 -> BE1 303 0.0 13707 0 3 3 0 0 0 3
TR2 -> TR2 111 0.0 11682 0 0 0 0 0 0 0
TR2 -> BE1 504 0.0 22743 0 18 8 1 0 0 9
FE1 -> FE1 64 0.0 6645 0 0 0 0 0 0 0
FE1 -> FE2 373 0.0 18890 0 2 2 0 0 0 2
FE1 -> BE1 310 0.0 24487 0 0 0 0 0 0 0
FE2 -> FE2 231 0.0 18900 0 0 0 0 0 0 0
FE2 -> BE1 284 0.0 22503 1 1 1 0 0 0 1
FE2 -> TR1 536 0.0 28166 0 0 0 0 0 0 0
FE2 -> FE1 396 0.0 23643 0 0 0 0 0 0 0
BE1 -> BE1 355 0.0 28121 0 0 0 0 0 0 0
BE1 -> FE2 284 0.0 13014 1 0 0 0 0 0 0
BE1 -> TR2 515 0.0 27502 0 2 2 0 0 0 2
BE1 -> TR1 328 0.0 25698 0 1 1 0 0 0 1
BE1 -> FE1 335 0.0 17022 0 2 2 0 0 0 2
|
Displays in real time any network links that are currently stalling (that is, waiting to transmit outbound traffic) and provides a history of the stalls encountered by the various links during their lifetime. The display shows:
ORTR Call history monitor screen on node:rtrdoc PID : -ALL-
Image: -ALL- at 15:45:10 Mon Jul 16 2001
STC CurrentState : #Of Partitions : 0
PartitionName Channel #
Calls Channel #s State Msg/Event Ch. used Status
|
Displays history of calls for a specific server transaction controller.
6.2.37 Monitor System
System Status at 10:27:51 Fri Apr 9 1999
node: NODEA
Resource OK Warning
Facility QUORUM states...... x
JOURNAL free space.......... x
Link CONNECTS............... x
Link traffic STALLS......... x
FLOW control credits........ x
PARTITION states............ x
CALL Msg outstanding.......... x
Transaction QUEUES............ x
Transaction REJECTS........... x
Broadcast EVENT discards...... x
For additional detail about a resource,
monitor the appropriate subsystem. To
customize threshold values, edit
SYSTEM.MON. If viewing this page in a
browser, follow the hyperlinks above.
|
Displays the state of critical resources within the RTR environment. If a resource has exceeded a predefined threshold, a warning indicator is displayed.
The default thresholds are as follows:
| Quorum | Warns if any roles are inquorate |
| Journal | Warns if journal free space is less than 30% of total |
| Links | Warns if any link is disconnected |
| Stalls | Warns if 10 second stalls are greater than 1% of all messages sent |
| Flow | Warns if the wait is more than 1 second for 10% of the total credit requests |
| Partition | Warns if any of the partitions are not in one of the following states: Standby, Active, Pri_act, or Sec_act |
| Calls | Warns if any messages have been pending for more than 30 seconds |
| Queues | Warns if the transaction queue cannot be emptied within 10 seconds |
| Rejects | Warns if the number of rejects (non-user) is greater than 5% of the total transactions processed, or a reject (non-user) has occurred within the last 30 minutes |
| Events | Warns if the number of discards is greater than 5% of the total events sent |
Threshold values can be customized by editing the file SYSTEM.MON.
| Previous | Next | Contents | Index |