on 30-04-2010 04:09
Why are they only now finding these issues with BSR and UBRs? lol
on 30-04-2010 09:53
SouthWaleschris wrote:Why are they only now finding these issues with BSR and UBRs? lol
This is speculation, of course. But let's say there is instability in the VM network guts. When you do a tracert you see lots of hops. That's lots of routers and switches that all have to be perfectly synched all of the time and must be free from noise ingress. What if they're not? Uncorrectable FEC errors will be seen, packets re-requested and performance falls - say from 50 meg to 30 meg. This would be seen at the CMTS port but finding it in the backhaul or somewhere if it's not a CMTS situation is difficult.
If it's the CMTS, say CPU utilisation - they'd have spotted this sooner because the devices provide MIBs showing how CPU is utilised by software function. If CPU rises above 80% at peak times, then the amount of CPU used to route packets will be significant and queues will occur.
All very difficult.
on 30-04-2010 10:25
i wonder if they will actuallty get this right before the launch of 100mb.
on 30-04-2010 10:44
SouthWaleschris wrote:i wonder if they will actuallty get this right before the launch of 100mb.
Chris, they need to deliver 50mb first and sort the higher US issue people are demanding!
I'm sure this issue will be on Watchdog very soon!
on 30-04-2010 12:38
Adam this has always been the problem with Virgin unfortunately instead of sorting out current issues they push further and further and cause more and more problems.
As for Watchdog they have been on watchdog a number of times, the last time i recall was for billing dead people. Family members informing Virgin they have died and Virgin not terminating services and then charging for them.
on 04-05-2010 11:31
Seph, or others?
Any idea whay I keep getting DHCP renew in my event log?
Update I got from VM is they still have no idea what the fault is in Ipswich.
Here is my event log....
| Cable Modem Event Log | ||||||||||||||||||||||||
|
on 04-05-2010 20:58
Adamipswich wrote:Seph, or others?
Any idea whay I keep getting DHCP renew in my event log?
Update I got from VM is they still have no idea what the fault is in Ipswich.
Here is my event log....
Cable Modem Event Log
First Time Last Time Priority Description Time Not Established Time Not Established Error (4) ToD request sent- No Response received;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; Wed Apr 28 18:02:08 2010 Fri Apr 30 11:36:44 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; Fri Apr 30 19:38:01 2010 Fri Apr 30 19:38:01 2010 Notice (6) DHCP Renew - lease parameters tftp file-Pcaa1a92007a50b13.cm modifie;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; Sat May 1 03:29:52 2010 Sun May 2 14:30:44 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; Tue May 4 07:38:06 2010 Tue May 4 07:38:06 2010 Notice (6) DHCP Renew - lease parameters tftp file-Pcaa1a92007a50b13.cm modifie;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
on 04-05-2010 22:18
http://homepage.ntlworld.com/robin.d.h.walker/cmti
04-05-2010 22:20 - edited 04-05-2010 22:23
Update DCHP is not enabled on VM equipment hence that error but it has no bearing on your issue.
Hang on, got that wrong, it's updates not allowed, just go with what Seph has said.
on 10-05-2010 01:48
Adamipswich wrote:
Adamipswich wrote:Seph, or others?
Any idea whay I keep getting DHCP renew in my event log?
Update I got from VM is they still have no idea what the fault is in Ipswich.
Here is my event log....
Cable Modem Event Log
First Time Last Time Priority Description Time Not Established Time Not Established Error (4) ToD request sent- No Response received;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; Wed Apr 28 18:02:08 2010 Fri Apr 30 11:36:44 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; Fri Apr 30 19:38:01 2010 Fri Apr 30 19:38:01 2010 Notice (6) DHCP Renew - lease parameters tftp file-Pcaa1a92007a50b13.cm modifie;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; Sat May 1 03:29:52 2010 Sun May 2 14:30:44 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; Tue May 4 07:38:06 2010 Tue May 4 07:38:06 2010 Notice (6) DHCP Renew - lease parameters tftp file-Pcaa1a92007a50b13.cm modifie;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Issue is still on going, that DHCP is happening every Tue and Fri at the same time. Is that right?
Still awful speeds.
No comment from VM as to what the fault is, how long till its fixed!!!
2nd Line support please comment.
