Upstream CRC errors ??

M

Mal1ce

Well-Known Member
Joined
Feb 3, 2006
Messages
291
Reaction score
19
Location
Pinetown, KZN
/begin rant

Telkom decided that my exchange required some “planned maintenance work” this weekend and as a result my ADSL dropped on Friday night. Woke up Saturday morning to find it syncing at 2048/512 instead of the usual 384/128 but a router reboot soon cured that…

But wait.. I cannot authenticate? Strange. And what’s this? I now have a s**tload of upstream CRC errors appearing in the router status page. So, pick up the phone, 0800 375 375 and begin the seemingly eternal wait.

After about 4 attempts holding on up to an hour each time I finally got through on this afternoon, Sunday, so no ADSL since Friday night, to a (highly incompetent) BEE staff member who didn’t want to know anything about the work at the exchange and was insistent that I clear my cookies, set my router to bridge mode, create a PPPoE connection from my desktop using the Telkom guest account… blah blah blah. Long story short I hung up, redialled, managed to get a consultant who was willing to listen and reset the DSLAM port for me.

Great, I can now authenticate, but the errors in the router status page keep climbing (around 2000 now). Can anyone explain to me who/why/what these errors are and how I can go about fixing this apparent issue?

Thanks

*sigh* I feel like going and dragging the punching bag I got for my 13th birthday out the garage and giving it a good wallop, such is the pain & futility I felt after spending around 4 hours listening to that awful hold music.

/rant over
 
I only pay for a 384 connection which has been rock solid, stable, no errors since the last router reboot 2 months ago, that 2048 sync was a just a freak (something between the DSLAM and me).

All of a sudden now, after months of perfect use, they do planned work and I'm getting loads of CRC errors?
 
Well a speed upgrade and then downgrade wouldn't cause this to happen.

Either someone got into your SDC (green box) or something went screwy.

Didn't maybe have a thunderstorm in last 24-48h? line maybe get wet somewhere?

*pick up the handset, if any ,and press 0 - listen for faint humm/scratch noises.
*unplug everything except adsl.
*try another router.

if on saix - ping 41.242.128.1 -t and post a packet test here for about 1min.
 
New telephone cable from jack to router, new router, new filters already tried (in my frustration at getting it to authenticate the entire day yesterday until I had the DSLAM port reset this afternoon).

Ping results below:

Ping statistics for 41.242.128.1:
Packets: Sent = 64, Received = 63, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 122ms, Average = 27ms
Control-C
C:\Documents and Settings\Administrator>

Nope, no storms, nothing, the line went dead within 5 minutes of the time the maintenance was supposed to begin according to the telkomsa.net noticeboards.

Almost convinced something has gone pear shaped at the exchange during the course of said maintenance, getting Telkom to understand this of course is a different story..
 
Last edited:
ok..2 tests you can do:

1) if your router is supported by routerstats (google it) - give it a try..sample interval 5sec - 1000points..let it run for an hour - along with

2) same ip ping -t test 41.242.128.1 - after that hour terminate test
 
Ping statistics for 41.242.128.1:
Packets: Sent = 64, Received = 64, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 74ms, Maximum = 76ms, Average = 75ms

mine.
 
ok 100% - just to see if routerstats can confirm if your problem is verified by your SNR dipping - and the ping values equaling those problem gaps.
 
Good heavens MrNutz,

I see your avg ping is also sky high.

Here is mine:

Ping statistics for 41.242.128.1:
Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 90ms, Average = 87ms

Since last week Wednesday evening, my pings were sweet 38ms-44ms in BF2, it was a joy, then, my internet goes off, i'm still synced but my PPP light went off, came back on after 10mins, and my latency increased to 66ms-80ms in BF2.

Boy was I peeved off, on Thursday at noon, it went off again, this time for 3 hours, called them, got helped after 40min on the phone, logged a call, and there was a problem at my exchange, it got back up 2 hours later, then later on Friday also noonish, it went off again, came back on after 10min, at 16:20 went off again, came back on at 16:35.

Still after each one of these interruptions, my ping remained crap, still playable, but somewhere in the Free State, something isn't lekker with the network. Even my friends also have higher pings, bit lower than mine but highish 58ms. Has anyone experienced higher latencies than normal ?

BTW I got 3 sms's telling my that they are still working on the fault, I can prepare myself, will probably get one tomorrow stating that its resolved, but I will still have crap latencies. Do you guys think one should get a techie to go and look at our DSLAM at my exchange, because other exchanges in Bloem wasn't affected by this last week.... :mad:

PS: Soz for the mini thread highjack... :)
 
Resetting a dslam port - that can be done remotely , but i'm seriously worried about telkom.

A local tech told me that our town has got a total of 13 data techs and out of them 9 are looking for work elsewhere.

They haven't been given a raise this year , and didn't receive ANY bonus/13th cheque last year due to some telkom court case.

Some of them work damn hard , and do try to make a difference - so its very sad that upper management does this.

anyhow - yeah - i see my pings have also gone a bit high - i'll reset my router just now and ping again.

Ping statistics for 41.241.128.1:
Packets: Sent = 35, Received = 35, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 51ms, Average = 41ms
 
Last edited:
Turns out routerstats doesn't like my D-LINK.. but I've got to supply a client with a Netgear DG834 this week so I'll make use of it temporarily and post the results later.

EDIT: telkomsa.net noticeboard stated the following regarding my exchange this morning... CRC errors still climbing though...

ID NN0000691
Publish Date Wed, 26 Mar 2008 10:40:37 +0200
Category Planned Work
Title Link - Planned Maintenance will be performed on the Telkom Network at PARADISE VALLEY
Type Planned Work
TimeDown Fri, 28 Mar 2008 22:00:00 +0200
ETTR 5 Hours
Progress PLANNED MAINTENANCE SUCCESSFULLY COMPLETED
Areas Affected DSLAM Affected: PARADISE VALLEY
Status Cleared
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X