Statistic logs

Print version

19. Statistic logs

From MORSE main menu select d(i)ag stat (l)ogs.

Type il Enter.

Logs:
(l)inks c(a)lls
SCC p(o)rts
net(u)ser
RF (m)edium
(e)thernet
pu(s)h into history list
clea(r)
(q)uit
>>

Menu commands common for all statistic logs:

pu(s)h into history list

— All currently active logs (period 0) are closed, saved to the flash memory and cleared. The oldest logs history record (period 3) is overwritten, so the result of the pu(s)h command is that period 2 becomes period 3, 1 becomes 2, 0 becomes 1 and a new, empty record for period 0 is started.

clea(r)

— Clears all currently active logs, i.e. period 0. The above commands should only be used in exceptional situations. When statistic information from the very last minute is needed, then use the commands (d)isplay with (r)ef, reference (w)rite see bellow.

Menu items (l),(a),(o),(u),(m),(e) enable selection of the desired log. To give an example, the (l)inks log has been chosen here:

Type l Enter

(0) (1) (2) (3)
(f)ilter
(d)isplay with (r)ef
reference (w)rite
(q)uit
>>

The above submenu is identical for all log types. The time period from which we want to see the statistics is chosen here. (0, 1, 2, 3) For logs consisting of list (Link list a Call list) a filter can be configured. Only list items with addresses meeting conditions set in the filter are then reported and displayed.

(f)ilter

— For filter setting

Type f Enter

  Log report filter:
  (a)ddress:690F0300
  (m)ask:FFFF0000
  (o)ut:OFF
  (c)nt:1 
  (q)uit
  >>
(a)ddress: 690F0300

— comparative address (base)

(m)ask: FFFF0000

FFFF0000 — “1” bits indicate the part of the list item address which must be equal to the comparative address

00000000 — displays all items

(o)ut: OFF

OFF — items where the masked address is equal to the base address are listed in the report

ON — items where the masked address does not equal to base are listed

(c)nt: 1

– only this items are displayed, which have higher number of records than this parameter. Then (c)nt:0 displays the the singly packet also.

Following commands can be used to get the latest (incremental) information from any statistic log:

(d)isplay with (r)ef
reference (w)rite

First it is necessary to get the reference log data. Type (0) to obtain the current log information, then use the reference (w)rite command to save it. After next typing of (0) you can display the increment of log data by issuing the (r)ef command. The (d)isplay command displays the current content of Setr buffers. Thus alternating the (d)isplay and (r)ef commands, you can have both, the incremental and the last received log data display.

(0),(1),(2),(3)

— Choose the time period from which the log statistic is to be displayed

  • (0) is the running period

  • (1) is the last history period saved in the flash memory

  • (2) the period before

  • (3) the oldest history period available

The typical history period length is 86400 seconds, i.e. one day. The log period length can be configured within the Unit menu. The shift occurs also when you restarted CU, see pu(s)h into history list

Type 0 Enter

The running period of the links log has been chosen – see the following chapter for the report.

19.1. LINKS LIST

Updated for version 8.04

This provides comprehensive information about the retranslation packets exchange. Contains the packets transmitted (TX) via the net N and link L node outputs and the packet received (RX). The log contains the communication of all nodes in CU.

From MORSE main menu select: d(i)ag stat (l)ogs (l)inks (0) i.e.

Type ill0 Enter

The log list starts with a header containing:

Log from unit

serial number of a tracked CU, decimal

history period

record period according to the menu ill

opened:

the time, when the log counters were cleared and the counting began

closed:

the time, when the counters were closed (for past periods) or the time, when the counters were read (for current period)

total

total counting time of displayed log in seconds
for the choice (0) it is (closed – opened)
for (d)isplay it is (closed – opened) in moment of reading by command (0)
for (r)ef it si the time pertinent to the interval displayed

LINK LIST

distinguishing of the log type LINK LIST, CALL LIST,….

The remote address of a link listed in the report has to meet conditions set in the (f)ilter menu (see the (f)ilter menu)

>>
Log from unit 4833383  history period 0
  opened: 2007-02-05 13:29:59
  closed: 2007-02-05 13:44:33

total 874 s  LINK LIST
690F0001 690F0002
TX:  16/.018  byte:  3000/100  rep:  14/.467  lost:  8/.500  busy:  9/.360
RX:   8/.009  byte:   800/100  rep:   5/.385  misc:  0/ -    
Total:
packs     bytes     packs/sec bytes/sec
24        3800      0.03      4.3 
>>

Items of LINK LIST report

690F0001

node address of the link end in the observed CU, each node pair has a individual record in the log

690F0002

node address of the link end in the counterpart CU, in case of the wires retranslation the addresses are equal

Transmitting reports TX

TX:424/0.01

number of data packets sent into retransmission channel
more precisely:
packets entered in the RFC input buffer,
most 9 positions for MR400, next incoming packets are refused and registered in the busy item,
the TX packets are processed in some of next method:

  • if sec OFF – packet is sent without requirement for ACK

  • if sec ON – packet is sent and the ACK returned

  • if sec ON – packet is ent and the ACK didn’t come, the repeat follows and it is registered in the item rep

  • if the ACK does not come after specified number of repeats, then the packet is discarded and registered once in TX and once more in the item lost

  • if the ACK does not come until the store timeout in node expired (Ne1T15), then the packet is discarded and registered in the item lost

  • if the store timeout expired and the packet did not start be transmitted, then the packet is discarded and it is not registered, neither in the TX item number of

TX: …/.018

TX/total — number of TX / total time of opened log, [packets/sec]

byte: 3000/…

data byte number in TX + number of repeatedly transmitted bytes

byte: …/100

byte/(TX+rep) — average data lenght of packets transmitted

rep: 14/…

number of repeatedly transmitted packets

rep: …/.467

rep/(TX+rep) — relative part of packet repeated

lost: 8/…

number of packets which did not be acknowledged by ACK or which were discarded after store timeout,
the repeated packets (rep) are not counted
the unsecured packets are not counted

lost: …/.500

lost/TX — relative part of unacknowledged packets

busy: 9/…

packets, which did not fit into buffer and were discarded

busy: …/.360

busy/(TX+busy) — relative number of refused packets

Receiving reports RX

RX: 8/…

number of data packets received for the first time (the state of repeat bit in the header is not important here)

RX: …/.009

RX/total — number of packets received for the first time/sec

byte: 800/…

number of data bytes received for the first time

byte: …/100

byte/RX — average data length in the firstly received packets

rep: 5/…

repeatedly received packets, it is not added in the RX

rep: …/.385

rep/(RX+rep) — relative number of repeats

misc:

the meaning differs according to RF channel access mode:

  • NORMAL – number of received packets having the data integrity mistakes (corrupted packets), this packets have the head crc OK but data crc wrong

  • R-CTRL – number of tx req

Total – summary records for the all CU

packs 24

TX+RX — number of packets passed through CU, without repeats

bytes: 3800

byte(TX)+byte(RX) — general data flow, including repeatedly transmitted bytes, the bytes received repeatedly are not counted in

packs/sec: 0.03

packs/total — number of packets (TX+RX) / total time opening of log

bytes/sec: 4.3

bytes/total — number of bytes / total time opening of log

19.2. CALLS LIST

Offers a review of all the calls (MORSE addresses) which were detected on any of the RF Channels during the log period, together with average DQ and RSS values.

Fromn the MORSE main menu select: d(i)ag stat (l)ogs c(a)lls (0), i.e.

Type ila0 Enter

Every address listed in the report has to meet conditions set in the (f)ilter menu.

Log from unit 4943628  history period 0
  opened: Thu Sep 30 12:29:59 2005
  closed: Thu Sep 30 19:03:03 2005
total 23584 s RF CALL LIST
addr.    count DQ RSS    addr.    count DQ RSS    addr.    count DQ RSS
69509001   766 18 109    690F0400   130 24  72    69501500    97 26  72
008A003A    77 23  72    690F8100    19 28  63    690F8606   185 28  90
690F8601    20 25  90    69509002     1  0 119
Total:
packs    rate
1295     0.05
>>

Items of an address record in the RF CALL LIST:

adr 69509001

— MORSE address

count 766

— number of transmissions detected

DQ 18

— average data quality

RSS 109

— average RF signal strength

packs 1295

— sum of all detected packet transmissions on the RF channel

rate 0.05

— packets per second average rate

19.3. SCC PORTS LOG

provides statistics of received and transmitted frames on the RS232 interface of SCCs (to and from a connected remote terminal device).

From the MORSE main menu select: d(i)ag stat (l)ogs SCC (p)orts (0), i.e.

Type ilo0 Enter

Log from unit 5711764  history period 0
  opened: Mon Sep 20 23:08:42 2005
  closed: Tue Sep 21 05:34:05 2005
total 23123 s COM PORTS LOG
Port  TX   bytes  size  RX   bytes  size
  0      no TX data         no RX data
  1      no TX data         no RX data
  2   293  16180  55    287   3368  12
>>
Log from unit 5863503  history period 0
  opened: Tue Sep 13 14:09:04 2005
  closed: Tue Sep 13 14:31:21 2005
total 23123 s  COM PORTS LOG
Port  TX   bytes  size  RX   bytes  size
  0   293  16180  55    287   3368  12
  1      no TX data         no RX data
  2      no TX data         no RX data
  3      no TX data         no RX data 
>>

Items of COM PORTS LOG report:

Port 2

— number of SCC

Port 0

— number of SCC

TX 293

— direction SCC → terminal, count of frames

  • bytes 16180 – count of bytes

  • size 55 – average length of frame

RX 287

— direction terminal → SCC, count of frames

  • bytes 3368 – count of bytes

  • size 12 – average length of frame

19.4. NET USER LOG

Gives information of packets passing through the user part of the Channel to Node interface, thus enabling evaluation of the network load generated by the user connected via the respective channel.

The SCC, Ethernet or Network Agent channels can be used fot user access in the MORSE network.

From MORSE main menu select: d(i)ag stat (l)ogs net (u)ser (0) i.e.

Type ilu0 Enter

Log from unit 4611616  history period 0
  opened: Tue Sep 13 14:09:04 2005
  closed: Tue Sep 13 15:26:14 2005
total 4630 s  USER INTERFACE LOG
Port  TX/period  bytes  size  RX/period  bytes  size
S00       no TX data              no RX data
S01       no TX data            20/231      80    4
S02       no TX data              no RX data
E00       no TX data              no RX data
G00       no TX data              no RX data
G01       no TX data              no RX data 
>>
Log from unit 5863503  history period 0
  opened: Tue Sep 13 14:09:04 2005
  closed: Tue Sep 13 15:26:14 2005
total 4630 s  USER INTERFACE LOG
Port  TX/period  bytes  size  RX/period  bytes  size
S00       no TX data              no RX data
S01       no TX data            20/231      80    4
S02       no TX data              no RX data
S03       no TX data              no RX data
E00       no TX data              no RX data
G00       no TX data              no RX data
G01       no TX data              no RX data 
>>

Items of USER INTERFACE LOG report

opened:

— time when log counters were cleared and counting started

closed:

— time when counters were closed and saved (for history periods) or time when log counters were read (for running period)

total 4630 s

— entire time of counting (closed – opened)

Port S01

— channel identification

TX

— direction Channel → Node, count of packets

RX 20

— direction Node → Channel, count of packets

period

— the average time interval between packets (sec)

bytes 80

— count of data bytes

size 4

— average length of packet data (bytes / packets)

19.5. RF MEDIUM LOG

Gives indications about time occupancy of the RF channel. Based on periodical sampling of the RF channel status and RSS level every 8 milliseconds, percentages of time consumed by data communication and by interference are calculated and displayed. If more detailed information is needed, RF medium monitoring can be used.

From MORSE main menu select: d(i)ag stat (l)ogs RF(m)edium (0), i.e.

Type ilm0 Enter

Log from unit 4340141  history period 1
  opened: Wed Jan 23 21:13:14 2002
  closed: Thu Jan 24 21:13:14 2002
total 86400 s  RF MEDIUM LOG
comms total  7.97%  free 87.57%
noise:        comms:
 112  2.47%   101-    2.20%
 104  0.90%   85-100  1.71%
  96  0.96%   69-84   0.21%
  88  0.03%     -68   0.10%
  80  0.07%
  72  0.00%   **TX**  3.74%
  64  0.00%
  56  0.00%
  48  0.02%
No RSS info  0.00%
FDI 95.37%  CI 35.05%
>>

Items of RF MEDIUM LOG menu:

comms total 7.97%

— sum of comms and TX

free 87.57%

— free capacity of RF medium (noise below -116 dBm)

noise: 112 2.47% ….

— percentages of time when noise signals with different RSS levels are received

comms: 101- 2.20% ….

— percentages of time when MORSE data communication is received, sorted according the RSS level

**TX** 3.74%

— percentage of time when RF modem was transmitting

No RSS info 0.00%

— percentage of time when RSS measurement failed

FDI 95.37%

— Free Data Index – percentage of the receiving time, when the channel is free, i.e. without comms nor noise (related to the time without transmitting)

CI 35.05%

— Collision Index – it is meaningful at heavy traffic only (for **TX** 10 and more percent) – proportion of noise time to comms time with omission of the weak signals. This number illustrated, for which part of signals received the time collision occurs, i.e. they are evaluated like the noise

19.6. ETHERNET LOG

Information about traffic in Ethernet channel.

From MORSE main menu type ile0 Enter.

Log from unit 5863503  history period 0
  opened: Tue Sep 13 14:09:04 2005
  closed: Tue Sep 13 15:44:33 2005
total 5729 s  ETHERNET LOG
RX:
packs    :  0         packs/s :  0.00     
bytes    :  0         bytes/s :  0.0      
busy     :  0         packs/s :  0.0      
collision:  0         packs/s :  0.0      
overrun  :  0         packs/s :  0.0      
crc error:  0         packs/s :  0.0      
short fr.:  0         packs/s :  0.0      
align err:  0         packs/s :  0.0      
long fr. :  0         packs/s :  0.0      
mcast    :  0         packs/s :  0.0      
bcast    :  0         packs/s :  0.0      
TX:
packs    :  0         packs/s :  0.00     
bytes    :  0         bytes/s :  0.0      
busy     :  0         packs/s :  0.0      
carrier  :  0         packs/s :  0.0      
underrun :  0         packs/s :  0.0      
retry    :  0         packs/s :  0.0      
tot. retr:  0         packs/s :  0.0      
retr. lim:  0         packs/s :  0.0      
late col.:  0         packs/s :  0.0      
heart b. :  0         packs/s :  0.0      
collision:  0         packs/s :  0.0       
>>

The informations concerning the Ethernet channel traffic are available here.

  • packs — the number of packets passed through Eth channel

  • bytes — the number of bytes passed through Eth channel

  • ostatní — next records serves for productions purposes