Page 831 / 944 Scroll up to view Page 826 - 830
Appendix A Log Descriptions
ZyWALL USG 50 User’s Guide
831
(%s MTU - 8) < %s MTU,
%s may not work
correctly.
An administrator configured ethernet, vlan or bridge and this
interface is base interface of PPP interface. PPP interface MTU
> (base interface MTU - 8), PPP interface may not run
correctly because PPP packets will be fragmented by base
interface and peer will not receive correct PPP packets.1st
%s: Ethernet interface name, 2nd %s: PPP interface name.
Interface %s links
down. Default route
will not apply until
interface %s links up.
An administrator set a static gateway in interface
but this
interface is link down. At this time the configuration will be
saved but route will not take effect until the link becomes
up.1st %s: interface name, 2nd %s: interface name.
name=%s,status=%s,TxP
kts=%u,
RxPkts=%u,Colli.=%u,T
xB/s=%u,
RxB/s=%u,UpTime=%s
Port statistics log. This log will be sent to the VRPT server.
1st %s: physical port name, 2nd %s: physical port status, 1st
%u: physical port Tx packets, 2nd %u: physical port Rx
packets, 3rd %u: physical port packets collisions, 4th %u:
physical port Tx Bytes/s, 5th %u: physical port Rx Bytes/s,
3rd %s: physical port up time.
name=%s,status=%s,TxP
kts=%u,
RxPkts=%u,Colli.=%u,T
xB/s=%u,
RxB/s=%u
Interface statistics log. This log will be sent to the VRPT
server.
1st %s: interface name, 2nd %s: interface status, 1st %u
variable: interface Tx packets, 2nd %u variable: interface Rx
packets, 3rd %u: interface packets collisions, 4th %u:
interface Tx Bytes/s, 5th %u: interface Rx Bytes/s.
Interface %s start
dailing.
A PPP interface started dialing to a server. %s: interface
name.
Interface %s connect
failed: Connect to
server failed.
A PPTP interface failed to connect to the PPTP server. %s:
interface name.
Interface %s
connection
terminated.
A PPP connection will terminate. %s: interface name.
Interface %s
connection
terminated: idle
timeout.
An idle PPP connection timed out.1%s: interface name.
Interface %s connect
failed: MS-CHAPv2
mutual authentication
failed.
MS-CHAPv2 authentication failed (the server must support
mS-CHAPv2 and verify that the authentication failed, this
does not include cases where the servers does not support
MS-CHAPv2). %s: interface name.
Interface %s connect
failed: MS-CHAP
authentication
failed.
MS-CHAP authentication failed (the server must support MS-
CHAP and verify that the authentication failed, this does not
include cases where the server does not support MS-CHAP).
%s: interface name.
Interface %s connect
failed: CHAP
authentication
failed.
CHAP authentication failed (the server must support CHAP
and
verify that the authentication failed, this does not include
cases where the server does not support CHAP). CHAP:
interface name.
Interface %s is
connected.
A PPP interface connected successfully. %s: interface name.
Table 274
Interface Logs (continued)
LOG MESSAGE
DESCRIPTION
Page 832 / 944
Appendix A Log Descriptions
ZyWALL USG 50 User’s Guide
832
Interface %s is
disconnected.
A PPP interface disconnected successfully. %s: interface
name.
Interface %s connect
failed: Peer not
responding.
The interface’s connection will be terminated because the
server did not send any LCP packets. %s: interface name.
Interface %s connect
failed: PAP
authentication
failed.
PAP authentication failed (the server must support PAP and
verify
verify that the authentication failed, this does not
include cases where the server does not support PAP). %s:
PPP interface name.
Interface %s connect
failed: Connect
timeout.
A PPPOE connection timed out due to a lack of response from
the PPPOE server. %s: PPP interface name.
Interface %s create
failed because has no
member.
A bridge interface has no member. %s: bridge interface
name.
"Interface cellular
Application Error Code
%d\n.
The listed error code (%d) was generated due to an internal
cellular interface error.
"An error [%d]
occurred while
negotiating with the
device in %s. Please
try to remove then
insert the device.
The listed error code (%d) happened when the ZyWALL
attempted to negotiate with the cellular device installed in (or
connected to) the listed slot (%s). Remove and reinstall the
device.
"Unable to negotiate
with the device in %s.
Please try to remove
then insert the
device.
The ZyWALL could not negotiate with the cellular device
installed in (or connected to) the listed slot (%s). Remove
and reinstall the device.
"Unable to configure
the selected frequency
band to the device in
%s. Please try to
remove then insert the
device.
The ZyWALL failed to set the cellular device installed in (or
connected to) the listed slot (%s) to use the frequency band
you configured. The cellular device may not support the band
or you may need to try removing and reinstalling the device.
"PIN code is required
for inteface
cellular%d. Please
check the PIN code
setting.
The PIN code configured for the listed cellular interface (%d)
is incorrect or missing.
"SIM card has been
successfully unlocked
by PUK code on
interface cellular%d.
You entered the correct PUK code and unlocked the SIM card
for the cellular device associated with the listed cellular
interface (%d).
"Incorrect PUK code of
interface cellular%d.
Please check the PUK
code setting.
You entered an incorrect PUK code so you were not able to
unlock the SIM card for the cellular device associated with the
listed cellular interface (%d).
Table 274
Interface Logs (continued)
LOG MESSAGE
DESCRIPTION
Page 833 / 944
Appendix A Log Descriptions
ZyWALL USG 50 User’s Guide
833
"SIM card of interface
cellular%d in %s is
damaged or not
inserted. Please
remove the device,
then check the SIM
card.
The SIM card for the cellular device associated with the listed
cellular interface (%d) cannot be detected. The SIM card may
be missing, not inserted properly, or damaged. Remove the
device and check its SIM card. If it does not appear to be
damaged, try re-inserting the SIM card.
"SIM card of interface
cellular%d in %s is
locked. Please enter
PUK code to unlock.
The SIM card for the cellular device associated with the listed
cellular interface (%d) is locked. This may be because the PIN
code was entered incorrectly more than three times. You need
to enter the PUK code to unlock the SIM card. .
"Incorrect PIN code of
interface cellular%d.
Please check the PIN
code setting.
The listed cellular interface (%d) does has the wrong PIN
code configured.
"Unable to query the
signal quality from
the device in %s.
Please try to remove
then insert the
device.
The ZyWALL could not check the signal strength for the listed
cellular interface (%d). This could be due to an error or being
out of range of the ISP’s cellular station.
"Interface cellular%d
cannot connect to the
service provider.
The listed cellular interface (%d) cannot connect to the ISP.
This could be due to an error or being out of range of the
ISP’s cellular station.
"Interface cellular%d
is configured with
incorrect APN.
The listed cellular interface (%d) does not have the correct
APN (Access Point Name) configured.
"Interface cellular%d
is configured with
incorrect phone
number.
The listed cellular interface (%d) does not have the correct
phone number configured.
"Interface cellular%d
is configured with
incorrect username or
password.
The listed cellular interface (%d) does not have the correct
user name and password configured.
"Interface cellular%d
is configured with
device %s, but current
inserted device is %s.
The listed cellular interface (%d) is configured for a particular
cellular device (first %s), but a different cellular device
(second %s) is inserted.
"Cellular device [%s
%s] has been inserted
into %s.
The cellular device (identified by its manufacturer and model)
has been inserted in or connected to the specified slot.
"Cellular device [%s
%s] has been removed
from %s.
The cellular device (identified by its manufacturer and model)
has been removed from the specified slot.
Table 274
Interface Logs (continued)
LOG MESSAGE
DESCRIPTION
Page 834 / 944
Appendix A Log Descriptions
ZyWALL USG 50 User’s Guide
834
Interface cellular%d
required
authentication
password.Please set
password in cellular%d
edit page.
You need to manually enter the password for the listed
cellular interface (%d).
"Cellular%d (IMSI=%s
or ESN=%s) over time
budget!(budget = %d
seconds).
The listed cellular interface (%d) with the listed SIM card
IMSI number or IMEI/ESN number went over the listed time
budget threshold value (second %d).
"Cellular%d (IMSI=%s
or ESN=%s) over time
budget %d%% (budget =
%d seconds).
The listed cellular interface (%d) with the listed SIM card
IMSI number or IMEI/ESN number went over the listed
percentage of the time budget threshold value (second %d).
"Cellular%d (IMSI=%s
or ESN=%s) over time
budget!(budget = %d
seconds).
This alert lets you know that the listed cellular interface (%d)
with the listed SIM card IMSI number or IMEI/ESN number
went over the listed time budget threshold value (second
%d).
"Cellular%d (IMSI=%s
or ESN=%s) over time
budget %d%% (budget =
%d seconds).
This alert lets you know that the listed cellular interface (%d)
with the listed SIM card IMSI number or IMEI/ESN number
went over the listed percentage of the time budget threshold
value (second %d).
"Cellular%d (IMSI=%s
or ESN=%s) over data
budget!(budget = %lld
Mbytes, used = %lld
Mbytes).
The listed cellular interface (%d) with the listed SIM card
IMSI number or IMEI/ESN number went over the listed data
budget by the listed number of MB.
"Cellular%d (IMSI=%s
or ESN=%s) over data
budget %d%% (budget =
%.2f Mbytes, used =
%.2f Mbytes).
The listed cellular interface (%d) with the listed SIM card
IMSI number or IMEI/ESN number went over the listed
percentage of the data budget threshold value.
"Cellular%d (IMSI=%s
or ESN=%s) over data
budget!(budget = %lld
Mbytes, used = %lld
Mbytes).
This alert lets you know that the listed cellular interface (%d)
with the listed SIM card IMSI number or IMEI/ESN number
went over the listed data budget by the listed number of MB.
"Cellular%d (IMSI=%s
or ESN=%s) over data
budget %d%% (budget =
%.2f Mbytes, used =
%.2f Mbytes).
This alert lets you know that the listed cellular interface (%d)
with the listed SIM card IMSI number or IMEI/ESN number
went over the listed percentage of the data budget threshold
value.
The interface name is
not accepted.
An incorrect name was not permitted for an interface.
Configured interface
name is reserved word.
A reserved word was not permitted to be used in an interface
name.
Configured interface
name match reserved
prefix.
A reserved pre-fix was not permitted to be used in an
interface name.
Table 274
Interface Logs (continued)
LOG MESSAGE
DESCRIPTION
Page 835 / 944
Appendix A Log Descriptions
ZyWALL USG 50 User’s Guide
835
Duplicated interface
name.
A duplicate name was not permitted for an interface.
This Interface can not
be renamed.
An interface’s name cannot be changed.
Virtual interface is
not supported on this
type of interface.
A virtual interface was not created on an interface because
the type of interface does not support virtual interfaces.
Virtual interface need
to be removed before
changing the interface
property.
An interface property cannot be changed because the
interface has a virtual interface on it.
Virtual interface can
not configured at
external interface.
A virtual interface cannot be configured on an external
interface.
Interface property is
not accepted.
An invalid interface property was not accepted.
The property can not
be changed at this
interface.
An interface property cannot be changed.
System default ppp
interface can not bind
with other ethernet
interface.
The system default PPP interface can only be bound with the
corresponding Ethernet interface, not any other.
Related system default
ppp interface need to
deactivate first.
The related system default PPP interface has to be
deactivated before the attempted configuration can be done.
Related system default
ppp interface can not
be activated since
interface property is
internal.
The system default PPP interface cannot be activated because
it is related to an internal interface.
System default ppp
interface can not be
removed.
A PPP interface could not be removed because it is a system
default PPP interface.
Interface property can
not change to internal
since interface is the
member of other trunk.
An interface can not be set to be an internal interface because
it is a member of a trunk.
Port-grouping is not
support
The interface does not support port grouping.
This interface type
can not set 3rd-dns.
This type of interface does not support setting a third DNS
server setting.
Table 274
Interface Logs (continued)
LOG MESSAGE
DESCRIPTION

Rate

4.5 / 5 based on 2 votes.

Bookmark Our Site

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

Share
Top