Table
LOG MESSAGE | TYPE |
| DESCRIPTION |
|
|
| |
GSHDSL <port> Link | INFO | This log displays information about a G.SHDSL port’s connection. | |
Info: NM=<noise |
| <port> | - port number |
margin> ATT=<loop |
|
|
|
attenuation> |
| <noise margin> - the connection’s signal quality in dB. | |
|
| <loop attenuation> - the connection’s line loss in dB. | |
|
|
| |
GSHDSL <port> Link | WARN | A G.SHDSL port established a connection. | |
Up(SN=<seq no>): |
| <seq no> | - sequence number of the connection |
rate=<rate>Kbps |
| <rate> - the connection’s rate | |
|
| ||
|
|
| |
GSHDSL <port> Link | WARN | A G.SHDSL port lost its connection. | |
Down(SN=<seq no>) |
|
|
|
NM=<noise margin> |
|
|
|
ATT=<loop attenuation> |
|
|
|
GSHDSL <port> CRC | WARN | These are G.SHDSL port error counters. | |
crcAnomaly:<couter1> |
| <couter1>- the number of cyclic redundancy check errors | |
LOSW Defect:<couter2> |
|
|
|
LOSW Failure:<couter3> |
| <couter2> - the number of Loss of Sync Word defects | |
|
| <couter3> - the number of Loss of Sync Word failures | |
|
|
| |
GSHDSL <port> ATT | WARN | These are G.SHDSL port error counters. | |
Defect:<couter1> SNR |
| <couter1> - the number of times the loop attenuation was too | |
Defect:<couter2> |
| high |
|
|
|
| |
|
| <couter2> - SNR (Signal to Noise Ratio) the number of times the | |
|
| signal quality was too low. | |
|
|
| |
HTTPD data crash | ERROR | The network module failed in an attempt to construct an HTTP (web | |
theAllegroServerDataPt |
| configurator) session. | |
r <mem addr> |
|
|
|
File too large <file | WARN | The file size was too large with an attempted HTTP (web | |
id> <file size> |
| configurator) firmware upload. | |
Insecure HTTP From <ip | WARN | Someone tried to start an HTTP (web configurator) session from the | |
addr> |
| listed IP address and it did not match any of the configured secured | |
|
| client IP addresses. | |
Watchdog timeout | WARN | The hardware watchdog determined that the network module was | |
|
| hung or not executing the correct sequence of code and restarted the | |
|
| network module. | |
Warm Start Trap | WARN | The network module restarted as a result of a reboot command. | |
Cold Start Trap | WARN | The network module started. | |
Core Dump!!! | WARN | The error log is not kept after a restart. When the network module | |
|
| restarts due to a software level error, you can use config save in | |
|
| order to create a core file. Send the core file to customer support for | |
|
| analysis. |
|
THERMO OVER RANGE: | WARN | The temperature detected in the network module was too high. | |
dev:<device id> |
| <temp> | - temperature when the entry was logged |
value:<temp> |
|
|
|
Diagnostics |