ZyXEL Communications NXC Series - Page 453

Appendix A Log Descriptions
NXC Series User’s Guide
453
Table 218 Interface Logs
LOG MESSAGE DESCRIPTION
Interface %s has been
deleted.
An administrator deleted an interface. %s is the interface name.
Interface %s has been
changed.
An administrator changed an interface’s configuration. %s: interface name.
Interface %s has been
added.
An administrator added a new interface. %s: interface name.
Interface %s is
enabled.
An administrator enabled an interface. %s: interface name.
Interface %s is
disabled.
An administrator disabled an interface. %s: 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 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 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).
Interface %s create
failed because has no
member.
A bridge interface has no member. %s: bridge interface name.