3- Diagnostics Services Menu
...
Enter 3 at the Main Menu for the Directory Services menu.
================ Diagnostic Services ==============ElecSys(V:5.7.2017-08-24-1000) Wed Sep 6 19:31:54 2017RediGate120E : 1 @ 0.0.0.0 REDIGATE <46247-0002>-SerialNumb---------------------------------------------1) System Status 2) Network Interfaces3) Run Time and Loading 4) System Resources5) Task Status 6) Task Diags7) Channel Status 8) Channel Diags9) Rtu Status 10) Rtu Diags11) Rtu Clear 12) Slave Diags13) IP Route Table 14) Ping Service15) RTDB Status 16) RTDB Diags17) MQtt Status 18) RTDB Data Dump19) Dial Backup 510) Trend a Point535) View Custom Rpt99) Monitor Diag's
Make selection:
...
The Message Queues include message queue ID, owner and permissions of the task, and the number of used bytes and messages. For most users, this information is low-level and not too useful, but occasionally it can be informative of problems if one task is taking up a growing number of used bytes, or if the list of message queues continues to grow longer.
Make selection: 1
================ System Status ==============
ElecSys(V:5.7.2017-08-07-1200) Sun Sep 3 21:17:07 2017
UnitName : 1 @ 192.3.1.10 REDIGATE <46247-0004>-SerialNumb
---------------------------------------------
Linux UnitName 3.15.10-00073-ge03f088 #0 PREEMPT Thu Nov 20 10:42:18 CST 2014 armv5tel GNU/Linux
Press ENTER to continue
------ Message Queues --------
key msqid owner perms used-bytes messages
0x00000290 0 root 666 0 0
0x00002dc8 1409025 user 666 0 0
0x00000bed 720899 root 666 0 0
0x00000bf2 753668 root 666 0 0
0x00000bf6 786437 root 666 0 0
0x00000bfa 819206 root 666 0 0
0x00000bff 851975 root 666 0 0
0x00000c05 884744 root 666 0 0
0x00000c06 917513 root 666 0 0
0x00000c07 950282 root 666 0 0
0x00000c09 983051 root 666 0 0
0x00000c0c 1015820 root 666 0 0
0x00000c0e 1048589 root 666 0 0
0x00000c0f 1081358 root 666 0 0
0x00000c10 1114127 root 666 0 0
0x00000c12 1146896 root 666 0 0
0x00000c14 1179665 root 666 0 0
0x00000c16 1212434 root 666 0 0
0x00000c18 1245203 root 666 0 0
0x00000c19 1277972 root 666 0 0
0x00000c5f 1376277 root 666 0 0
0x00000c1a 1310742 root 666 0 0
0x00000c1b 1343511 root 666 0 0
Press ENTER to continue
...
2- Network Interfaces
Main Menu → Diagnostics Services → Network Interfaces
...
| Info |
|---|
| NOTE that in older RediGate tarballs prior to September 2017, this menu only worked if you logged in as 'root' first, then superuser to the user account. |
Make selection: 2
================ Network Interfaces ==============ElecSys(V:5.7.2017-08-07-1200) Sun Sep 3 21:17:07 2017
UnitName : 1 @ 192.3.1.10 REDIGATE <46247-0004>-SerialNumb---------------------------------------------eth0 Link encap:Ethernet HWaddr 82:49:22:2B:82:A6inet addr:10.63.191.28 Bcast:10.63.255.255 Mask:255.255.0.0inet6 addr: fe80::8049:22ff:fe2b:82a6/64 Scope:LinkUP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1RX packets:19565659 errors:0 dropped:83411 overruns:0 frame:0TX packets:77491 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:0RX bytes:1376149850 (1.2 GiB) TX bytes:6030078 (5.7 MiB)
lo Link encap:Local Loopbackinet addr:127.0.0.1 Mask:255.0.0.0inet6 addr: ::1/128 Scope:HostUP LOOPBACK RUNNING MTU:65536 Metric:1RX packets:412 errors:0 dropped:0 overruns:0 frame:0TX packets:412 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:0RX bytes:37684 (36.8 KiB) TX bytes:37684 (36.8 KiB)
ppp0 Link encap:Point-to-Point Protocol
inet addr:10.12.0.15 P-t-P:10.12.0.15 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:11 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:424 (424.0 B) TX bytes:61 (61.0 B)Do you want to see Socket Statuses (Y/N) ? y
Press SPACE to page forward...Active Internet connections (servers and established)Proto Recv-Q Send-Q Local Address Foreign Address Statetcp 0 0 0.0.0.0:22 0.0.0.0:* LISTENtcp 0 0 10.63.191.28:22 10.242.3.2:65199 ESTABLISHEDtcp 0 0 :::22 :::* LISTENActive UNIX domain sockets (servers and established)Proto RefCnt Flags Type State I-Node Pathunix 14 [ ] DGRAM 2214 /dev/log
Press ENTER to continue...
...
Enter 3 for Run Time and Loading.
Make selection: 3
================ Run Time ==============ElecSys(V:5.7.2017-08-07-1200) Sun Sep 3 21:17:07 2017
UnitName : 1 @ 192.3.1.10 REDIGATE <46247-0004>-SerialNumb---------------------------------------------
Local_Time Up_Time 0.0=IDLE => 1 min 5 min 15 min <= 1.00=BUSY---------- ------- ----- ----- ------18:47:04 up 11 days, 12:47, load average: 2.89, 3.35, 3.43
Press ENTER to continue
...
View the Debug Level for all running processes in the RediGate code. The Debug Level is used for RediGate task logging and can be set using menu option 6 and others. Real-time diagnostics can be viewed using menu option 99 - Monitor Diagnostics.
Enter 5 for Task Status.
The tasks are numbered sequentially (referred to as "slot numbers"), starting from 0. The name following each task is the mnemonic that appears in the real-time view as events occur.
The word following the task name (Status, Display, Dump, etc.) indicates the current Debug Level of the task (see Debug Levels).
Tasks are marked with All, None, or Some, to indicate whether debugging is enabled/disabled for all or part of the units associated with that task.
...
Set the Debug Level for a process. (You can also set Debug Levels by using option 8 for Master Channel diagnostics, 10 for Field Unit protocol diagnostics, 12 for Slave Channel diagnostics, or 16 for RTDB diagnostics.) Use option 99 - Monitor Diagnostics to observe the real-time diagnostics of each task after setting the Debug Levels.
...
First, enter the Task Slot Number from the numbers that are listed. Depending on the task you have selected, you will have to enter a number of other information, starting with the new Debug Level that you wish to enable. NOTE: The Debug Level is GLOBAL for this task. The Debug Level ; i.e., it applies to all units (Node Addresses) associated with this task. If you wish to enable debugging for only one (or more) Field Unit or Node Address on a task, see NOTE below for Enable/Disable.
Task DNPMST00 Status ( All)
Valid Debug Level:0 - Fatal Errors (Ending)1 - General Errors (Error)2 - Status Messages (Status)3 - Data Display (Display)4 - Data Dump (Dump)
Debug Level 0-4 or 'S'tats ?4
If prompted, enter a Node Address within the task to which the diagnostics status will be applied. For master protocol tasks, this will be the Unit Field Unit Address of the device being monitored. For other task types, other information will be prompted to identify the scope of the diagnostic level being applied.
Enter Node Address for Slot=5 (-1 for all) 1
If prompted, enter 1 to enable the diagnostics for the task, or 0 to disable diagnostics .Note that the multiple debug items for same task can in some cases have diagnostics for multiple items for the Node Address (or All).
Enter 0=Disable : 1=Enable [Default=1] ? 1
| Note | ||
|---|---|---|
| ||
NOTE: If a task controls multiple Node Addresses (such as Field Units), diagnostics for each Node Address can be enabled or disabled |
...
separately. One or more units may have debugging enabled simultaneously—enabling diagnostics for a single unit does not automatically disable diagnostics for all the others. For instance, to enable diagnostics for only 3 out of 10 Field Units on a master channel, first Disable diagnostics for "All" units; then select the Task Diagnostics menu multiple times to Enable diagnostics for only certain Field Unit node addresses. |
...
Enter 0=Disable : 1=Enable [Default=1] ? 1
The last Debug Level selected applies to ALL enabled units controlled by this task. |
After entering all information related to the task Debug Level modification, a single line output will indicate the change in status, and the list of tasks will generally be shown again.
Setting DNPMST00 to Level Dump
13 PROCESSES
0 - WATCHDOG Status ( All) 7 - CH01XDBM Status ( All)1 - CHANNL00 Status ( All) 8 - DNPMST01 Status ( All)2 - CHANNL01 Status ( All) 9 - CHN01SCN Status ( All)3 - CHANNL15 Status ( All) 10 - CH15XDBM Status ( All)4 - CH00XDBM Status ( All) 11 - VIRTMS15 Status ( All)5 - DNPMST00 Dump Dump ( All) 12 - CHN15SCN Status ( All)6 - CHN00SCN Status ( All)Task Slot Number (0 to 12)?
...
- Master Channel number from configuration
- Master Channel name from configuration
- Current channel status (see Master Channel Status Indications for a list of status values)
- Number of Field Units (RTUs) configured on the channel
- System timestamp of the last event on the channel.
...
- FieldUnit Address from configuration
- FieldUnit Name from configuration
- Status of debugging (enabled or disabled) for the FieldUnit
- Protocol enumeration as it appears in the Task List
- Status (see RTU Status for a list of these indications)
...
Enter 8 for Channel Diags. Enter the number of the Master Channel or Internal Channel for the FieldUnit that you want to change Debug Level. (See Master Channel Status Indications for a list of status values.)
Make selection: 8
================ Channel Diags ==============ElecSys(V:5.7.2017-08-07-1200) Sun Sep 3 21:17:07 2017
UnitName : 1 @ 192.3.1.10 REDIGATE <46247-0004>-SerialNumb---------------------------------------------Chan Name Status Rtus Time==== ============== ======== ==== ==================0 Channel0 w/Errors 1 Tue Dec 14 09:37:32 19991 Channel0 w/Errors 1 Tue Dec 14 09:37:31 199915 Channel15 Normal 1 Tue Nov 30 06:00:02 1999
Enter Channel (0 to 15) ?0
...
Addr Name Dbg? Protocol Status----- ---------------- ---- -------- ------1 DNP3 Field Unit ON DNPMST00 Timeout
Enter RTU Address (-1 for all) ? 1
Enter 0=Disable : 1=Enable [Default=1] ?1
After entering all information related to the task Debug Level modification, a single line output will indicate the change in status, and the list of tasks will generally be shown again.
Setting Scan-Rtu 1 to Enable Dump
================ Channel Diags ==============ElecSys(V:5.7.2017-08-07-1200) Sun Sep 3 21:17:07 2017
UnitName : 1 @ 192.3.1.10 REDIGATE <46247-0004>-SerialNumb---------------------------------------------Chan Name Status Rtus Time==== ============== ======== ==== ==================0 Channel0 w/Errors 1 Tue Dec 14 09:37:57 19991 Channel0 w/Errors 1 Tue Dec 14 09:37:56 199915 Channel15 Normal 1 Tue Nov 30 06:00:02 1999
Enter Channel (0 to 15)?
Once you have modified the Debug level for all FieldUnits that you wish to change, press Enter to return to the Diagnostics Services menu, or enter another channel number.
| Anchor | ||||
|---|---|---|---|---|
|
...
Enter 9 for RTU Status. Enter the Master Channel number to view Channel, Circuit, and Field Unit status. Or enter -1 to view the status for units on all channels.
(See Master Channel Status Indications for a list of status values.)
================ Rtu Status ==============
ElecSys(V:5.7.2017-08-07-1200) Mon Aug 14 02:10:12 2017
UnitName : 1 @ 192.3.1.10 REDIGATE <46247-0004>-SerialNumb
---------------------------------------------
Chan Name Status Rtus Time
==== ============== ======== ==== ==================
0 Channel0 Normal 3 Mon Aug 14 02:10:07 2017
2 Master Channel w/Errors 1 Mon Aug 14 02:02:14 2017
15 Channel15 Normal 1 Mon Aug 14 02:02:14 2017
Enter Channel (0 to 15, -1 for all) ? 0
-----------------RTU---------------- -----POLL------- -------ERRORS-------
Addr Name Protocol Status Time Count TimOut BadData Frame
----- ---------------- -------- -------- -------- -------- ------ ------- -----
1 Modbus01 MBMAST00 PollDone 02:10:07 9 2 0 0
2 Modbus02 MBMAST00 Timeout 02:09:15 0 9 0 0
3 Modbus03 MBMAST00 Polling 02:09:15 7 2 0 0
Redisplay (Y/N/E where E is Extended Info)?
See Channel Status for details on the Master Channel status information.
...
- Addr – FieldUnit address from configuration
- Name – FieldUnit name from configuration
- Protocol – Enumeration indicating both the protocol and Master Channel instance number. For example, MBMAST00 refers to Modbus Master protocol on Channel 0. The Protocol enumeration is also used for diagnostic messages in the Monitor Diagnostics log.
- Status – Current state of each Field Unit.
- PollDone - Device is in communication and last poll was completed successfully.
- Timeout - Last poll to device timed out with no valid response.
- BadData - Last poll received some data but it was not a correct expected response (including an exception code).
- FrameErr - Last poll received a framing error (possibly part of the message was received but not all – ?? check with John)
- Stopped - Field Unit or Channel is disabled or not being polled
- Polling - Poll has been sent but response not yet received, or a response to one poll has been received but not all polls are completed, so the device status cannot be completely confirmed yet.
- No Polls - No polls have been sent to Field Unit since last restart.
- Time – Last time the Field Unit was accessed (started, polled, command sent).
- Count – Number of polls which have successfully received a response.
- TimOut – Number of polls which have timed out after all configured retries.
- BadData – Number of polls which have received a bad data response.
- Frame – Number of polls which have received a framing error response.
If the Extended Info option is select by entering E, more information is displayed showing the configuration of the various port configurations (Async or Network Circuit).
Redisplay (Y/N/E where E is Extended Info) ? e
Attempts_Per_PollAdd Unit Dbg Circuit Last Clear Boot Type Port----- -------------- --- ------- ---- ----- ---- ----- ----1 Modbus01 ON CONNECT 1 1.0 1.0 TCP/IP 192.3.1.11:30402 Modbus02 ON CONNECT 4 4.0 4.0 DIRECT COM02 19200 NONE3 Modbus03 ON CONNECT 1 1.0 1.0 TCP/IP 192.3.1.11:3040Press ENTER...
...
Enter 10 for RTU Diags. Enter the number of the Master Channel or Internal Channel for the FieldUnit that you want to change Debug Level.
(See Master Channel Status Indications for a list of status values.)
...
Enter 11 for Rtu Clear. Enter the Master Channel number, and either clear statistics all devices or enter the unit address to clear.
Make selection: 11
================ Rtu Clear ==============ElecSys(V:5.7.2017-08-24-1000) Mon Dec 6 05:15:36 1999DNPMastTest : 1 @ 10.63.191.28 REDIGATE-400 <38258-0025>-SerialNumb---------------------------------------------Chan Name Status Rtus Time==== ============== ======== ==== ==================0 Channel0 Normal 1 Mon Dec 6 05:15:33 19991 Channel0 Normal 1 Mon Dec 6 05:15:34 199915 Channel15 Normal 1 Tue Nov 30 06:00:02 1999
Enter Channel (0 to 15) ? 0
Clear All Rtus (Y/N) ? n
-----------------RTU---------------- -----POLL------- -------ERRORS-------Addr Name Protocol Status Time Count TimOut BadData Frame----- ---------------- -------- -------- -------- -------- ------ ------- -----1 DNP3 Field Unit DNPMST00 PollDone 05:15:39 111713 30 0 0Enter Rtu to Clear ? 1
Clearing Rtu 1 Status Counters
Clear All Rtus (Y/N)?
...
- DNPSLAV0 = DNP Async Slave Channel, instance number 0
- MBNSL00d = Modbus Network Slave Channel 'daemon' (listening socket), instance number 0. This is the task that waits for incoming connections, and then spawns a separate task handling the active socket connection. If you set the Debug Level for this task, then any future connections to the socket will inherit the same Debug Level.
- MBNSL001 = Modbus Network Slave Channel (active socket connection #1), instance number 0. Many device protocol servers allow multiple simultaneous sockets to the same port. If you set the Debug Level for this task, it only applies to the current host connection to the socket. Once the socket connection is closed, the 'daemon' process controls the Debug Level of future connections.
Make selection: 12
================ Slave Status/Diagnostics ==============ElecSys(V:5.7.2017-08-30-1300) Mon Dec 6 05:18:07 1999powirv : 1 @ 10.63.191.29 ZEUS-3.12 <Use System Serv Option-123>---------------------------------------------0 - DNPSLAV0 Status ( All) 1 - DNPSLAV1 Status ( All)2 - DNPSLAV2 Status ( All) 3 - DNPSLAV3 Status ( All)4 - MBNSL00d Status ( All) 5 - MBNSL001 Status ( All)
Task Slot Number (0 to 4) ? 0
Task DNPSLAV0 Status ( All)
Valid Debug Level:0 - Fatal Errors (Ending)1 - General Errors (Error)2 - Status Messages (Status)3 - Data Display (Display)4 - Data Dump (Dump)
...
| Info |
|---|
| NOTE that in older RediGate tarballs prior to September 2017, this menu only worked if you logged in as 'root' first, then superuser to the user account. |
Make selection: 13
================ Route Table ==============ElecSys(V:5.7.2017-08-24-1000) Mon Dec 20 05:07:14 1999DNPMastTest : 1 @ 10.63.191.28 REDIGATE-400 <38258-0025>-SerialNumb---------------------------------------------Kernel IP routing tableDestination Gateway Genmask Flags Metric Ref Use Iface0.0.0.0 10.63.255.128 0.0.0.0 UG 0 0 0 eth010.53.47.0 0.0.0.0 255.255.255.0 U 0 0 0 eth310.63.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
Press ENTER to continue
...
To get a ping response, the destination address must be reachable from the RediGate using its current routing configuration and not prevented by firewall rules (RediGate or other network devices). To ping a named server instead of IP address, the RediGate must have DNS configured (explicit DNS configuration if using Ethernet, or through the DNS setting on a cellular PPP network).
Make selection: 14
================ Ping Services ==============ElecSys(V:5.7.2017-08-24-1000) Mon Dec 20 05:22:35 1999DNPMastTest : 1 @ 10.63.191.28 REDIGATE-400 <38258-0025>-SerialNumb---------------------------------------------Enter Host to Ping (IP-Addr or Name) 10.63.191.29
!!!! Press CTRL-C to stop pinging !!!!
PING 10.63.191.29 (10.63.191.29): 56 data bytes64 bytes from 10.63.191.29: seq=0 ttl=64 time=2.360 ms64 bytes from 10.63.191.29: seq=1 ttl=64 time=1.295 ms64 bytes from 10.63.191.29: seq=2 ttl=64 time=1.293 ms^C--- 10.63.191.29 ping statistics ---3 packets transmitted, 3 packets received, 0% packet lossround-trip min/avg/max = 1.293/1.649/2.360 ms
...
Enter 16 for RTDB Diags. Enter the Master Channel number of the channel containing the RTDB to diagnose.
Make selection: 16
================ RTDB Diags ==============ElecSys(V:5.7.2017-08-24-1000) Tue Dec 21 03:54:15 1999DNPMastTest : 1 @ 10.63.191.28 REDIGATE-400 <38258-0025>-SerialNumb---------------------------------------------Chan Name Status Rtus Time==== ============== ======== ==== ==================0 Channel0 w/Errors 1 Tue Dec 21 03:54:12 19991 Channel0 w/Errors 1 Tue Dec 21 03:54:15 199915 Channel15 Normal 1 Tue Nov 30 06:00:02 1999
Enter Channel (0 to 15) ?0
...
Enter 18 for RTDB Data Dump. Enter the Master Channel number and RTU Address of the RTDB to view registers.
Make selection: 18
================ RTDB Dump ==============ElecSys(V:5.7.2017-10-25-1700) Mon Nov 6 18:19:21 2017UnitName : 1 @ 192.3.1.10 REDIGATE-400 <38258-0025>-SerialNumb---------------------------------------------Chan Name Status Rtus Time==== ============== ======== ==== ==================0 Channel0 Normal 2 Mon Nov 6 18:19:19 201715 Channel15 Normal 1 Mon Nov 6 18:18:14 2017
Enter Channel Number ? 0
-----------------RTU---------------- -----POLL------- -------ERRORS-------Addr Name Protocol Status Time Count TimOut BadData Frame----- ---------------- -------- -------- -------- -------- ------ ------- -----2 Modbus02 MBMAST00 Timeout 18:19:14 0 4 0 03 Modbus03 MBMAST00 PollDone 18:19:22 384 0 0 0Enter Rtu Address3
The RTDB configuration is then shown for the Channel and RTU address. Enter the Starting Point Address and the Point Count of registers to display. Make sure that the quantity requested doesn't exceed the number of available registers.
Data Type Count Address---------- ----- -------BOOLEAN 10 1BOOLEAN 10 10001SINT16 5 30001UINT16 5 40001UINT32 5 41001REAL32 5 42001STRING-32 5 43001STRING-256 5 44001
Enter Starting Point Address 1
Enter Point Count (1 to 125 or only 16 STRING-256) 50
...
This is a legacy menu for the DialBackup task, which is currently not supported in the RediGate.
| Anchor | ||||
|---|---|---|---|---|
|
...
Enter 99 for Monitor Diagnostics.
510- Trend a Point
535- View Custom Rpt
If one or more Custom Report is configured for this RediGate, view the contents of the report. The Custom Report is a pre-defined set of RTDB registers with a tag descriptor. This is a more convenient way to view the values of registers than option 18, and it allows registers that have been defined as read/write to be written to through the user menu.
Enter 535 for View Custom Rpt.