P-971M User’s Guide

37 

Chapter 4 SNMP Event Log

Received Response to Broadcast Maintenance Request, But no Unicast 

Maintenance opportunities received - T4 timeout (Critical)

Your P-971M 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 P-971M 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 P-971M 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 P-971M 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 P-971M 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 P-971M will send another RNG-REQ message, up to the 
maximum of 16 successive attempts. 

TFTP Failed - OUT OF ORDER packets (Critical)

Your P-971M attempted to download its DOCSIS compliant configuration file from the TFTP 
server, but the download failed because the P-971M received at least one packet that was out 
of order. 

TFTP file complete - but failed Message Integrity check MIC (Critical)

Your P-971M successfully downloaded its configuration file, but the Message Integrity Check 
(MIC) field sent with the configuration file does not match the one that your P-971M 
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 P-971M 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)