50M Downstream channels - Page 3

Peter_ · 09-09-2011, 11:38

Quote:

Originally Posted by Firmsky

I can appreciate it to be annoying and I hope my comments haven't annoyed you in any way, I for one appreciate the time you and your colleagues invest in this forum in your own time.

I know that just sometimes we having sweeping statements that encompass everyone.

qasdfdsaq · 10-09-2011, 01:37

Quote:

Originally Posted by Sephiroth

On the VM forum, once it's picked up by a tech, it does get sorted, as you've observed.

The underlying cause of misconfiguration hasn't been rectified and I find that disturbing knowing some of the control procedures in force at Virgin media.

Still? This has been an ongoing issue since the rollout started almost a year ago!

Then again, so has the Superhub.

Firmsky · 10-09-2011, 10:02

Still no reply and still on mini slot size 1.

Seph I noticed yours was fixed before you got a reply, I wonder if mine will be the same.

Sephiroth · 10-09-2011, 10:17

Firmsky,

There were other cases too on the VM forum. All the peops had to do was wait for someone to get round to fixing the configuration file concerned.

It does seem to me that there is something missing from their configuration management procedures and I find that surprising.

Firmsky · 10-09-2011, 10:39

Quote:

Originally Posted by Sephiroth

Firmsky,

There were other cases too on the VM forum. All the peops had to do was wait for someone to get round to fixing the configuration file concerned.

It does seem to me that there is something missing from their configuration management procedures and I find that surprising.

Like you say it is alarming, considering this has occurred before it is surprising it is still happening. I'll keep you posted on the outcome of this.

Thanks for your continued interest in this thread.

Firmsky · 11-09-2011, 15:38

Had a reply and is as follows..

Hi Adamipswich,
*
Sorry to hear you have been having toruble with your upload speeds.
*
I have checked your part of the network and can confirm that it is able to acheive 5Mb uploads.
*
Thankyou for posting your ping test and modem information.
The ping test shows no issues, and everything looks OK with your modem re: power levels etc.
*
You are correct when you say that your minislot size should be 4.
I have passed this information to our Networks team ref: F001732648
*
thanks
Di
*
*
Diane Smith
Help & Support Forum Team

So just got to wait for the fix now, my Mrs uploads lots of photos so until it does I'll keep getting it in the neck!!

General Maximus · 11-09-2011, 22:05

nice one dude, i am well chuffed for you that they have

1) replied
2) admitted there is a problem
3) know what to do to fix the problem and are fixing it

Firmsky · 11-09-2011, 22:07

T4 error in my log now, can someone remind me what they are?

Still got mini slot size 1 and now had this....

Sun Sep 11 18:22:45 2011 Sun Sep 11 18:22:45 2011 Warning (5) Lost MDD Timeout;
Sun Sep 11 18:23:17 2011 Sun Sep 11 18:23:17 2011 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out

Think the time is out by an hour.

Sephiroth · 11-09-2011, 22:22

Was that during a reboot/reset? Partial logs don't help. I'm afraid.

T3 ( Ranging Request Retries Exhausted )
The cable modem has sent 16 Ranging Request (RNG-REQ) messages without receiving a Ranging Response (RNG-RSP) message in reply from the CMTS. The cable modem is therefore resetting its cable interface and restarting the registration process. This typically is caused by noise on the upstream that causes the loss of MAC-layer messages. Noise could also raise the signal-to-noise ratio (SNR) on the upstream to a point where the cable modem's power level is insufficient to transmit any messages. If the cable modem cannot raise its upstream transmit power level to a level that allows successful communication within the maximum timeout period, it resets its cable interface and restarts the registration process. This error message is DOCSIS event message is R03.0, Ranging Request.

T4 ( Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received )
The cable modem did not received a station maintenance opportunity in which to transmit a Ranging Request (RNG-REQ) message within the T4 timeout period (30 to 35 seconds). The cable modem is resetting its cable interface and restarting 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 this particular headend system. This error message is DOCSIS event message is R04.0, Ranging Request.

Firmsky · 11-09-2011, 22:52

Quote:

Originally Posted by Sephiroth

Was that during a reboot/reset? Partial logs don't help. I'm afraid.

T3 ( Ranging Request Retries Exhausted )
The cable modem has sent 16 Ranging Request (RNG-REQ) messages without receiving a Ranging Response (RNG-RSP) message in reply from the CMTS. The cable modem is therefore resetting its cable interface and restarting the registration process. This typically is caused by noise on the upstream that causes the loss of MAC-layer messages. Noise could also raise the signal-to-noise ratio (SNR) on the upstream to a point where the cable modem's power level is insufficient to transmit any messages. If the cable modem cannot raise its upstream transmit power level to a level that allows successful communication within the maximum timeout period, it resets its cable interface and restarts the registration process. This error message is DOCSIS event message is R03.0, Ranging Request.

T4 ( Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received )
The cable modem did not received a station maintenance opportunity in which to transmit a Ranging Request (RNG-REQ) message within the T4 timeout period (30 to 35 seconds). The cable modem is resetting its cable interface and restarting 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 this particular headend system. This error message is DOCSIS event message is R04.0, Ranging Request.

It was through neither Seph, was watching tv and when I checked my logs found it.

Since my modem reset Wed 7/9 this is the full log, not much help I'm afraid...

Still got mini slot size 1 and now had this....

Wed Sep 7 10:39:13 2011 Wed Sep 7 11:23:28 2011 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC
Sat Sep 10 07:43:54 2011 Sat Sep 10 07:43:54 2011 Notice (6) DHCP Renew
Sun Sep 11 18:22:45 2011 Sun Sep 11 18:22:45 2011 Warning (5) Lost MDD Timeout;CM-MAC=
Sun Sep 11 18:23:17 2011 Sun Sep 11 18:23:17 2011 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out

---------- Post added at 21:52 ---------- Previous post was at 21:27 ----------

Sorry was checking log on my iPad so didn't see it fully the T4 timeout was followed by a MIMO event.

Sephiroth · 11-09-2011, 23:25

From Brady Volpe:

3. MAC Domain Descriptor (MDD)MDD messages are periodically transmitted on all Downstream Channel(s) of DOCSIS 3.0 CMTSs. The MDD message contains the Downstream Channel ID of the Primary Downstream Channel for the CMTS sending the MDD message. The value of the MDD occurs when a cable modem locks onto a non-primary capable downstream channel, the cable modem will read the MDD and know immediately where to tune to in order to lock on to the Primary Downstream Channel. The MDD can also be used for load balancing cable modems in a DOCSIS 3.0 network. The MDD also contains additional information for the cable modem, such as available downstream channels, available upstream channels, upstream frequency range and more.

That's why I asked if there was a modem reset involved. You do have a downstream problem too, it seems.

Firmsky · 12-09-2011, 10:01

So is it just a case of monitoring the whole thing Seph? Obviously over on the official forums they say nothing is wrong with my connection?

This also seems to have started since the introduction of the four Downstream Channels.

Sephiroth · 12-09-2011, 10:55

I couldn't glean any negativity on VM's part in your thread over there. Do you actually have a problem apart from the still stunted upsload speed?

If you had these MDD entries coming up all the time, then you'd be having problems and your modem stats woud reflect this. Oddly, I'm going through an unusual period of surprising stability!

I say surprising - because it's always been stable and good with fairly nominal power levels and albeit slightly low SNR (with attendant consequences for correctables). Last week, my DS power plunged from -1 to -7 and my SNR from 34 - 35 to 27-31. Apart from a spate of MDD Timeouts on the day and low speeds of 1 Mbps, I now am back to 50 meg and still have the rubbish SNR and -7 dBmv downstream power. Event logs are clear.

Since we have the same modem, and your event log isn't clogged with these events, what trouble are you having now that VM is denying?

Firmsky · 12-09-2011, 11:02

Have a bit of occasional packet loss but apart from the reduced upstream nothing is wrong Seph. It was more out of curiosity and as I've suffered a awful connection in the past I suppose I'm just dreading it occurring again. With that I suppose I'm just trying to preempt any faults but by the sounds of it apart from the reduced upstream I do not have a fault as the T4 hardly ever happens and has only been since going onto 4 DS channels.

Probably just a case of me over worrying due to previous experience.

Sephiroth · 12-09-2011, 11:18

When you went to 4 channels, they put you on the latest generation line card, which increased handling capacity at the UBR. So I don't expect there to be much going wrong your way other than you seem to have the same upstream issue as I did when we switched to the new line card.

As I say, shoddy configuration management (in the ITIL sense) by VM.