ZyXEL Communications P-974H - V3.70, Manual

Page: 40 / 116

Chapter 3 Status
P-974H/HW Series User’s Guide
40
Init RANGING
Critical Ranging
Request Retries
exhausted Critical Your ZyXEL Device has sent 16 Ranging Request (RNG-REQ)
messages without receiving a Ranging Response (RNG-RSP) reply
message from your cable operator’s CMTS. Your ZyXEL Device will
reset its cable interface and restart the registration process. This
error message is typically caused by noise on the upstream channel
that causes the loss of MAC-layer messages. If your ZyXEL Device
cannot raise its upstream channel transmit power to a level that
allows successful communication within the maximum timeout
period, it resets its cable interface and restarts the registration
process.
Received
Response to
Broadcast
Maintenance
Request, But no
Unicast
Maintenance
opportunities
received - T4
timeout Critical Your ZyXEL Device did not received a station maintenance
opportunity in which to transmit a Ranging Request (RNG-REQ)
message within the required T4 timeout period (30 to 35 seconds).
Your ZyXEL Device will reset its cable interface and restart the
registration process. Typically, this indicates an occasional,
temporary loss of service, but if the problem persists, check for
possible service outages or maintenance activity on the part of your
cable operator.
No Ranging
Response
received - T3
time-out Critical Your ZyXEL Device sent a Ranging Request (RNG-REQ) message as
part of its initial ranging process, but did not receive a Ranging
Response (RNG-RSP) message from the CMTS within the required T3
timeout period. Your ZyXEL Device will adjust its upstream channel
transmit power and send another RNG-REQ message, up to the
maximum of 16 successive attempts, or until it reaches the
maximum transmit power level.
Started Unicast
Maintenance
Ranging - No
Response
received - T3
time-out Critical Your ZyXEL Device is online and has sent a periodic Ranging Request
(RNG-REQ) message to the CMTS, without receiving a Ranging
Response (RNG-RSP) message from the CMTS within the required T3
timeout period. Your ZyXEL Device will send another RNG-REQ
message, up to the maximum of 16 successive attempts.
TFTP Failed -
OUT OF ORDER
packets Critical Your ZyXEL Device attempted to download its DOCSIS compliant
configuration file from the TFTP server, but the download failed
because the ZyXEL Device received at least one packet that was out
of order.
TFTP file
complete - but
failed Message
Integrity check
MIC Critical Your ZyXEL Device successfully downloaded its configuration file, but
the Message Integrity Check (MIC) field sent with the configuration
file does not match the one that your ZyXEL Device generated
internally after checking the file’s contents. This could indicate either
that the configuration file was corrupted during file transfer, or that
the software tool that generated the configuration file was not
performing up to the DOCSIS standard. This message may also
indicate that a malicious user is attempting to download their own
configuration file as part of a theft-of-service attempt.
TFTP failed -
request sent -
No Response Critical Your ZyXEL Device attempted to download the configuration file
from the TFTP server specified by the DHCP server, but the TFTP
server has not replied.
TFTP failed -
configuration file
NOT FOUND Critical Your ZyXEL Device attempted to download its configuration file from
the TFTP server specified by the DHCP server, but the TFTP server
replied that it could not find the requested file.
Table 9 Event Log: Log Description (continued)
LOG NAME SEVERITY DESCRIPTION