1. Home
    2. /
  2. Manuals
    3. /
  3. Zyxel
    4. /
  4. ZyWALL-USG50
    5. /
  5. 161
Page 801 / 944 Scroll up to view Page 796 - 800
Appendix A Log Descriptions
ZyWALL USG 50 User’s Guide
801
Get server response
has failed.
The device sent packets to the server, but did not receive a
response. The root cause may be that the connection is
abnormal.
Expiration daily-
check has failed:%s.
The daily check for service expiration failed, an error message
returned by the MyZyXEL.com server will be appended to this
log.
%s: error message returned by myZyXEL.com server
Do expiration daily-
check has failed.
Because of lack must
fields.
The device received an incomplete response to the daily
service expiration check and the packets caused a parsing
error for the device.
Server setting error.
The device could not retrieve the server's IP address or FQDN
from local.
Do expiration daily-
check has failed.
The daily check for service expiration failed.
Do expiration daily-
check has succeeded.
The daily check for service expiration was successful.
Expiration daily-
check will trigger PPP
interface. Do self-
check.
Before the device sends an expiration day check packet, it
needs to check whether or not it will trigger a PPP connection.
System bootup. Do
expiration daily-
check.
The device processes a service expiration day check
immediately after it starts up.
After register. Do
expiration daily-
check immediately.
The device processes a service expiration day check
immediately after device registration.
Time is up. Do
expiration daily-
check.
The processes a service expiration day check every 24 hrs.
Read MyZyXEL.com
storage has failed.
Read data from EEPROM has failed.
Open /proc/MRD has
failed.
This error message is shown when getting MAC address.
IDP service has
expired.
The IDP service period has expired. The device can find this
through either a service expiration day check via
MyZyXEL.com server or by the device’s own count.
Content-Filter
service has expired.
The content filtering service period has expired. The device
can find this through either a service expiration day check via
MyZyXEL.com server or by the device’s own count.
Unknown TLS/SSL
version: %d.
The device only supports SSLv3 protocol. %d: SSL version
assigned by client.
Load trusted root
certificates has
failed.
The device needs to load the trusted root certificate before
the device can verify a server's certificate. This log displays if
the device failed to load it.
Certificate has
expired.
Verification of a server’s certificate failed because it has
expired.
Table 259
myZyXEL.com Logs (continued)
LOG MESSAGE
DESCRIPTION
Page 802 / 944
Appendix A Log Descriptions
ZyWALL USG 50 User’s Guide
802
Self signed
certificate.
Verification of a server’s certificate failed because it is self-
signed.
Self signed
certificate in
certificate chain.
Verification of a server’s certificate failed because there is a
self-signed certificate in the server’s certificate chain.
Verify peer
certificates has
succeeded.
The device verified a server’s certificate while processing an
HTTPS connection.
Certification
verification failed:
Depth: %d, Error
Number(%d):%s.
Verification of a server’s certificate failed while processing an
HTTPS connection. This log identifies the reason for the
failure.
1st %d: certificate chain level
2nd %d: error number
%s: error message
Certificate issuer
name:%s.
Verification of the specified certificate failed because the
device could not get the certificate’s issuer name. %s is the
certificate name.
The wrong format for
HTTP header.
The header format of a packet returned by a server is wrong.
Timeout for get server
response.
After the device sent packets to a server, the device did not
receive any response from the server. The root cause may be
a network delay issue.
Download file size is
wrong.
The file size downloaded for AS is not identical with content-
length
Parse HTTP header has
failed.
Device can't parse the HTTP header in a response returned by
a server. Maybe some HTTP headers are missing.
Table 260
IDP Logs
LOG MESSAGE
DESCRIPTION
System internal error.
Detect IDP engine
status failed.
There was an internal system error. The device failed in
checking whether or not IDP is activated.
System internal error.
Enable IDP failed.
There was an internal system error. The device failed in
turning on IDP.
System internal error.
Disable IDP failed.
There was an internal system error. The device failed in
turning off IDP.
Enable IDP succeeded.
The device turned on the use of the IDP signature file.
Disable IDP succeeded.
The device turned off the use of the IDP signature file.
Enable IDP engine
failed.
The device failed to turn on the IDP engine.
Disable IDP engine
failed.
The device failed to turn off the IDP engine.
Table 259
myZyXEL.com Logs (continued)
LOG MESSAGE
DESCRIPTION
Page 803 / 944
Appendix A Log Descriptions
ZyWALL USG 50 User’s Guide
803
Enable IDP engine
succeeded.
The device turned on the IDP engine.
Disable IDP engine
succeeded.
The device turned off the IDP engine.
IDP service is not
registered. IDP will
not be activated.
The IDP service could has not been turned on and the IDP
signatures will not be updated because the IDP service is
not registered.
IDP service standard
license is expired.
Update signature
failed.
The IDP standard service license expired so the device
cannot update the IDP signatures.
IDP service standard
license is not
registered. Update
signature failed.
A IDP standard service license has not been registered. The
device cannot update the IDP signatures.
IDP service trial
license is expired.
Update signature
failed.
The IDP service trial license has expired. The device cannot
update the IDP signatures.
IDP service trial
license is not
registered. Update
signature failed.
The IDP service trial license has not been registered yet.
The device cannot update the IDP signatures.
Custom signature add
error: sid <sid>,
<error_message>.
An attempt to add a custom IDP signature failed. The error
sid and message are displayed.
Custom signature import
error: line <line>, sid
<sid>, <error_message>.
An attempt to import a custom IDP signature failed. The
errored line number in the file, the error sid and error
message are displayed.
Custom signature
replace error: line
<line>, sid <sid>,
<error_message>.
Custom IDP signature replacing failed. Error line number of
file, sid and message will be shown
Custom signature edit
error: sid <sid>,
<error_message>.
An attempt to edit a custom IDP signature failed. The error
sid and message are displayed.
Custom signature more
than <num>. Replacement
custom signature number
is <num>.
An attempt to replace a custom IDP signature failed. The
maximum number of custom signatures (first num) and the
number of the replacement signature (second num) display.
Custom signature more
than <num>. Remaining
custom signature number
is <num. Adding custom
signature number is
<num>.
An attempt to add a custom IDP signature failed. The
maximum number of custom signatures (first num), the
number of remaining capacity for custom signatures
(second num), and the number of the custom signature
(third num) that was not added display.
Get custom signature
number error.
The device failed to get the custom IDP signature number.
Table 260
IDP Logs (continued)
LOG MESSAGE
DESCRIPTION
Page 804 / 944
Appendix A Log Descriptions
ZyWALL USG 50 User’s Guide
804
Add custom signature
error: signature <sid>
is over length.
An attempt to add a custom IDP signature failed because
the signature’s contents were too long.
Edit custom signature
error: signature <sid>
is over length.
An attempt to edit a custom IDP signature failed because
the signature’s contents were too long.
IDP off-line update
failed. File damaged.
An update attempt for the IDP signatures failed. The
signature file may be corrupt.
IDP signature update
failed. File crashed.
An attempt to update the IDP signature file failed because
the device could not decrypt the signature file.
IDP signature update
failed. File damaged.
An attempt to update the IDP signature file failed because
the device could not decompress the signature file.
IDP signature update
failed. File update
failed.
An attempt to update the IDP signatures failed. Updating
the signature file failed.
IDP signature update
failed. Can not update
last update time.
An attempt to update the IDP signatures failed. Updating
the time for the last signature file update failed.
IDP signature update
from version <version>
to version <version>
has succeeded.
An IDP signature update succeeded. The previous and
updated IDP signature versions are listed.
IDP system-protect
signature update from
version <version> to
version <version> has
succeeded.
An update of the IDP system-protect signatures succeeded.
The previous and updated signature versions are listed.
System-protect
error.
Create IDP debug
directory failed
The IDP system-protect function had an error. Creation of
the IDP debug directory failed.
System internal error.
Create IDP statistics
entry failed.
There was an internal system error. Creation of an IDP
statistics entry failed.
System-protect error.
Out of memory. IDP
activation unchanged.
The IDP system-protect function had an error. The device
did not have enough available memory. The setting for IDP
activation has not changed.
System-protect error.
Create IDP proc failed.
IDP activation failed.
Activation of the IDP system-protect function failed due to
an internal system error.
Table 260
IDP Logs (continued)
LOG MESSAGE
DESCRIPTION
Page 805 / 944
Appendix A Log Descriptions
ZyWALL USG 50 User’s Guide
805
from <zone> to <zone>
[type=<type>] <message>
, Action: <action>,
Severity: <severity>
The ZyWALL detected an intrusion in traffic traveling
between the specified zones.
The <type> = {scan-detection(<attack>) | flood-
detection(<attack>) | http-inspection(<attack>) | tcp-
decoder(<attack>)}.
The <message> gives details about the attack, although
the message is dropped if the log is more than 128
characters.
The <action is what the ZyWALL did with the packets.
The <severity> is the threat level (very low, low, medium,
high, or severe).
Program DFA failed.
There was an internal system error. The IDP search engine
failed.
IDP signature update
failed. Fail to extract
temporary file.
An attempt to update the IDP signatures failed because the
device could not extract the signature package’s temporary
file.
IDP signature update
failed.
An attempt to update the IDP signatures failed due to an
internal system error.
IDP signature update
failed. Invalid
signature content.
An attempt to update the IDP signatures failed due to an
internal system error.
System internal error.
Create IDP traffic
anomaly entry failed.
There was an internal system error.
Query signature version
failed.
The device could not get the signature version from the new
signature package it downloaded from the update server.
Can not get signature
version.
The device could not get the signature version from the new
signature package it downloaded from the update server.
IDP system-protect
signature update
failed. Invalid IDP
config file.
An IDP system-protect signature update failed.
IDP system-protect
signature update
failed. Invalid
signature content.
An IDP system-protect signature update failed.
Enable IDP system-
protect succeeded.
The IDP system-protect feature was successfully turned on.
Disable IDP system-
protect succeeded.
The IDP system-protect feature was successfully turned off.
Check duplicate sid
failed. Allocate memory
error.
Checking for duplicated signature IDs failed. There was an
error while allocating memory.
Check duplicate sid
failed. Open file
error.
Checking for duplicated signature IDs failed. Opening a
temporary file failed.
Table 260
IDP Logs (continued)
LOG MESSAGE
DESCRIPTION

Rate

124.8 / 5 based on 304 votes.

Popular Zyxel Models

Famous Router IPs
Famous Router Companies
Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top