Specifications

show critical-logging
119
+110 : AFF0F000 00000000 00000000 00000100 ................
+120 : 00000200 00000000 00000200 00010000 ................
+130 : 00000100 00000300 00003C00 00003C00 ..........<...<.
+140 : 00001E00 00001E81 16F4A881 16E7B884 ................
+150 : 19B94081 16C80084 19C06084 19BB7084 ..@.......`...p.
+160 : 19C06080 903FD880 09229C00 0000312E ..`..?..."....1.
+170 : 395F3134 20536570 20313020 32303038 9_14 Sep 10 2008
+180 : 2C203231 3A35363A 33332031 2E392028 , 21:56:33 1.x (
+190 : 4275696C 643A3134 29205468 65726D6F Build:yy) Thermo
+1A0 : 3D33302E 352C3431 2E352C35 302E3000 =30.5,41.5,50.0.
:
>
Display items
Table 10-3 Information displayed by the show critical-logging command
Item Meaning Displayed information
Total Entry Total number of acquired log
records
--
Record Num. Record number specified for
display
--
Ref-Code Log reference code --
Time Stamp Date and time the log record was
acquired
year/month/day - hour:minute:second
SysUpTime SysUpTime when the log record
was acquired
SysUpTime: The elapsed time since the device
started up.
(If it is within 24 hours) time:minute:second
(If it exceeds 24 hours)number-of-days -
hour:minute:second
*** Log Text Data *** Log information displayed as text *** No Text Data *** is displayed if there
is no text information.
*** Log Binary Data *** Log information displayed as
binary data
*** No Binary Data *** is displayed if there
is no binary information.
Impact on communication
None
Response messages
Table 10-4 List of response messages for the show critical-logging command
Message Description
Can't execute. The command could not be executed. After deleting
directories and files on the RAMDISK, execute the
command again.
No Log data. There is no log information.
Not enough space on device. Capacity at the write destination is insufficient.