Quote:
|
Originally Posted by th'engineer
IGNITION
Think we should keep this out of the forum some things that you are claimimg are incorrect.
I think someone from NTL has passed you some incorrect information.
What you quote as things that have happened is totally wrong
just a question on your figures though is that not similar to my time out problem
Rochdale <-> Manchester Core A-Leg:
Success rate is 100 percent (10000/10000), round-trip min/avg/max = 1/2/328 ms
Rochdale <-> Manchester Core B-Leg:
Success rate is 100 percent (10000/10000), round-trip min/avg/max = 1/3/324 ms
|
If there were an issue with the links I've have said so, rather than posting those as proof there is no issue. If you've had the
RF levels adjusted and you and another engineer thought this had solved it I'd have thought you'd be happy that any issue is an HFC/RF one?
Incidentally, your Rochdale uBR has thousands of customers on it and I'd imagine that more than yourself would notice if there were issues on core which would indeed affect every customer on the uBR. Hell an issue with the cores would affect every uBR in that part of Manchester. There's been no abnormal call volume from the area served by your uBR or the North West at all recently.
Heat up Google... the high pings are caused by busy CPU on the cores as they are converging their routing tables and sending out update requests. This doesn't affect normal traffic which doesn't touch the CPU but instead is pumped through the switching fabrics and ASICs, but does show up on ICMP requests which do require CPU attention, and are well down the list of priorities for the CPU.
Rest of it I absolutely agree is well kept out of public forum. I imagine the people reading this from the outside are even more confused by this than I am, and I'm in the Twilight Zone. I've pulled stats on your connection for the past 10 months and it seems fine, excellent uptime and stability. Me well and truly out of this one!!!
