Diagnostic

Print version

8. Diagnostic

8.1. Monitoring

Monitoring is an advanced on-line diagnostic tool, which enables a detailed analysis of communication over any of the RipEX2 router interfaces. In addition to all the physical interfaces (RADIO, ETHs, COMs, TSs), some internal interfaces between software modules can be monitored when such advanced diagnostics is needed.

Monitoring output can be viewed on-line or saved to a file in the RipEX2 (e.g. a remote RipEX2) and downloaded later.

Interfaces

Fig. 8.1: Interfaces


8.1.1. Common parameters

  • Max. file size

    List box {1 kB, 10 kB, 50 kB, 100 kB, 500 kB, 1 MB, max (~2 MB)}, default = 100 kB

    When the selected “Time period” expires or the “Max. file size” has been reached, whichever event occurs first, the file is closed. The file can be downloaded later. Monitoring to the file will be implemented in future FW versions.

  • Time period

    List box {1 min, 2 min, 5 min, 10 min, 20 min, 30 min, 1 hour, 3 hours, 24 hours, Off}, default = 5 min

  • Show time difference

    List box {On, Off}, default = Off

    When On, the time difference between subsequent packets is displayed in the monitoring output.

  • Display

    List box {HEX, HEX+ASCII, ASCII}, default = HEX

  • Show output {On, Off}

    Enable/disable monitoring output on the local screen

  • Start monitoring / Stop monitoring button

    Starts / Stops monitoring according to set parameters

  • Clear button

    Clears local monitoring screen

8.1.2. Interfaces / Router

Common parameters for several interfaces:

  • Rx enabled, Tx enabled

    List boxes {On, Off}, default=On

    A packet is considered a Tx one when it comes out from the respective software module (e.g. RADIO or Terminal Server) and vice versa. When an external interface (e.g. Interface COM) is monitored, the Tx also means packets being transmitted from the RipEX2 over the respective interface (Rx means “received”). Understanding the directions over the internal interfaces may not be that straightforward, please consult Fig. 8.1, “Interfaces” above for clarification.

  • All

    List box {On, Off}, default On

    Monitoring output can also be limited by IP protocol type. Select Off to be able to enable/disable specific protocol output individually – see next parameter(s).

  • UDP / TCP / ICMP / Other / ARP

    List box {On, Off}, default Off

    Monitoring output of specific IP protocol limitation.

  • Offset [B]

    Default = 0

    Number of bytes from the beginning of packet/frame, which will not be displayed – the monitoring output is truncated by ‘Offset’ bytes at the beginning of the message.

  • Length [B]

    Default = 100

    Number of bytes to be displayed from each packet/frame.

    Example: Offset=2, Length=4 means, that bytes from the 3rd byte to the 6th (inclusive) will be displayed:

    Data (HEX):                 01AB3798A28593CD6B96

    Monitoring output:                        3798A285

  • Bandwidth

    List box {LOW, NORMAL, HIGH, UNLIMITED}, default= NORMAL

    Monitoring bandwidth limit to prevent overload of management link between client PC and the RipEX unit. LOW (up to ~300 kb/s), NORMAL (up to ~800 kb/s), HIGH (up to ~2 Mb/s), UNLIMITED (up to ~8 Mb/s)

  • Source port (from) (to)

    TCP/UDP source port to be enabled/disabled in the monitoring output. Use “… (to)” parameter to specify range of ports <from – to>.

  • Destination port (from) (to)

    TCP/UDP destination port to be enabled/disabled in the monitoring output. Use “… (to)” parameter to specify range of ports <from – to>.

  • Dropped frames

    List box {On, Off}, default Off

    When On, monitoring shows packets which are dropped (e.g. CRC is not valid, buffer overflow, …).

ETH interfaces

  • Include management traffic

    List box {On, Off}, default = Off

    Enable/disable management packets monitoring output.

  • Include ETH headers

    List box {On, Off}, default = Off

    Enable/disable ETH headers monitoring output

  • Include reverse

    List box {On, Off}, default = Off

    Enable/disable reverse traffic (e.g. TCP reply to a request) monitoring.

  • Source IP / mask, Destination IP / mask

    Monitoring output can also be limited to a specific address range – Source and Destination IP address and mask can be used to define the required range.

Radio interface

  • Corrupted frames

    List box {On, Off}, default = On

    Corrupted (“header CRC error”, “data CRC error”, etc.) received frames monitoring output can be suppressed. This can be useful when the communication in the channel is heavily disturbed by interference or noise, resulting in „garbage” messages which can make the monitoring output difficult to read.

  • Other modes

    List box {On, Off}, default = Off

    When Promiscuous mode is enabled, the unit is capable to monitor (receive) frames from the other RipEX units even if the other unit(s) is(are) working in the other Unit mode (Bridge versus Router).

    Frames transmitted under other Unit mode may not be properly ‘analyzed’. In such a case frames are displayed in raw data format.

  • Include headers

    List box {None, Packet (IP), Frame (ETH)}, Default= None

    • None – Only the payload (L4) is displayed, e.g. the data part of a UDP datagram.

    • Packet (IP) – Headers up to a Network layer (L3) are included, i.e. the full IP packet is displayed.

    • Frame (ETH) – The full Ethernet frame (L2) is displayed, i.e. including the ETH header.

  • Promiscuous mode

    List box {On, Off}, default = Off

    • Off – only frames which are normally received by this unit, i.e. frames whose Radio IP destination equals to Radio IP address of this RipEX2 unit and broadcast frames are available for the monitoring. Monitoring filters are applied afterwards.

    • On – all frames detected on the Radio channel are available for the monitoring. Monitoring filters are applied afterwards.

  • Link Control Frames

    List box { On, Off}, default = Off

    • Off – Radio Link Control Frames (e.g. ACK frames) are never displayed.

    • On – Radio Link Control Frames are processed by monitoring. Monitoring filters are applied.

  • Source IP / mask, Destination IP / mask (router)

    Monitoring output can also be limited to a specific address range – Internal (router) Source and Destination IP address and mask can be used to define the required range.

  • Source IP / mask, Destination IP / mask (radio)

    Monitoring output can also be limited to a specific address range – Radio interface Source and Destination IP address and mask can be used to define the required range.

Menu DIAGNOSTICS/Monitoring/Advanced groups together all setting across all monitoring web pages, mentioned above, in one web page.

8.2. Support

  • Reboot button

    RipEX2 unit can be rebooted on request.

  • RF Transmission Test

    Pre-defined type of RF signal can be transmitted for a specific purpose.

  • Type

    Listbox {Random data, Carrier wave, Single tone}, default = Random data

    Type of transmitted signal during the test. In case of Single tone a frequency with an offset from the central frequency is transmitted.

  • Period [s]

    Number from 1 to 1000 s

    Transmission test period.

  • Start button

    Starts the transmission test

  • Stop button

    Allows to stop the test before the pre-set time.