dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
412
RouterRooter
join:2001-11-22
Rockville, MD

RouterRooter to Morac

Member

to Morac

Re: [Connectivity] Modem is reporting continuous T4 errors.

Morac,

Had sporadic connectivity problems over last few days here -- good RF stats (4/3 channels down/up with good levels) but either no Internet or extremely slow. Same modem as you and essentially identical log:

13 06/22/12 08:28:50 Z00.0 warning MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=0;CM-MAC=00:26:5b:4b:26:a0;CMTS-MAC=00:01:5c:22:b5:cf;CM-QOS=1.1;CM-VER=3.0;
14 06/22/12 08:29:35 R02.0 critical No Ranging Response received - T3 time-out;CM-MAC=00:26:5b:4b:26:a0;CMTS-MAC=00:01:5c:22:b5:cf;CM-QOS=1.1;CM-VER=3.0;
15 06/22/12 08:29:51 U102.0 warning TCS Partial Service;CM-MAC=00:26:5b:4b:26:a0;CMTS-MAC=00:01:5c:22:b5:cf;CM-QOS=1.1;CM-VER=3.0;
16 06/22/12 08:29:51 U103.0 warning Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=00:26:5b:4b:26:a0;CMTS-MAC=00:01:5c:22:b5:cf;CM-QOS=1.1;CM-VER=3.0;
17 06/22/12 08:29:54 R05.0 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:26:5b:4b:26:a0;CMTS-MAC=00:01:5c:22:b5:cf;CM-QOS=1.1;CM-VER=3.0;
18 06/22/12 08:33:54 R04.0 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:26:5b:4b:26:a0;CMTS-MAC=00:01:5c:22:b5:cf;CM-QOS=1.1;CM-VER=3.0;
19 06/22/12 08:34:05 E115.0 notice Added MAC address [00:26:f2:a1:57:6b]
20 06/22/12 11:43:24 R04.0 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:26:5b:4b:26:a0;CMTS-MAC=00:01:5c:22:b5:cf;CM-QOS=1.1;CM-VER=3.0;

POPOed modem a few times and took ~ 5 minutes to fully connect with several drop-backs from finding upstream back to finding downstream (based on LEDs) before success..

Problem cleared up about 9 AM today. So ... I assume this is a problem at the plant and nothing to do with our equipment or local lines.

RR

Morac
Cat god
join:2001-08-30
Riverside, NJ

2 edits

Morac

Member

The weird thing is other than jitter being a bit higher than usual (some large packet pings are slow to return, but that's been that way since upstream channel bonding was added), I'm not seeing any problems. No packet loss, no slowdowns, nothing. Despite getting the T4 errors constantly for at least 24 hours now.

From what I was told only one of my 3 channels is having problems (which is odd in itself since if there was a line problem you'd think it would affect all three). I guess the modem can work okay with 2 of the 3 channels up and running. I'm not sure how the modem decides which channel to send packets out over, but it must not being using the bad one.