What do you think is wrong?

Started by psp83, May 08, 2008, 09:57:37

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Sebby

I know it must be frustrating to have a 135k profile, but stability is more important. The profile will shift is sync is maintained. Still, if IDNet can get it reset manually, it saves the annoyance of poor throughput.

psp83

Well the line didnt drop last night but i have been alerted by routerstats that it drop this afternoon.

I will know more when i get home and look at the logs, cant access the router/pc from work today for some reason :( all i know is that the line is showing alot of noise today again.


[attachment deleted by admin]

psp83

With it still dropping the profile will never get higher :( as BT wont nudge it up until the line is stable  :rant2:

Rik

IDNet might be able to intervene manually to get a 'halfway house' profile. That spike doesn't look bad enough to force a re-sync though - I wonder what the error count was doing at the time?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

psp83

Quote from: Rik on May 13, 2008, 14:28:57
IDNet might be able to intervene manually to get a 'halfway house' profile. That spike doesn't look bad enough to force a re-sync though - I wonder what the error count was doing at the time?

When i checked before work, the CRC was at 100 that was from 7pm till 8:30am..

IDnet have already said BT wont move the profile manually.

Rik

Quote from: psp83 on May 13, 2008, 14:32:26
IDnet have already said BT wont move the profile manually.

Ouch. :( It might be worth moving to a fixed rate service for a while then.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

psp83

Quote from: Rik on May 13, 2008, 14:39:03
Ouch. :( It might be worth moving to a fixed rate service for a while then.
Dont see why i should though, i've been on adsl max since the trials. its never been this bad and when i was with tiscali i never got this problem on a 15 margin and i always sync'd over 5500 kbps, something is wrong somewhere and BT dont want to own up :( i've only had this problem since the warmer weather, the builders next door and tiscali installing there LLU in the exchange.

I dont like BT and i'm going to keep bugging them till they own up!  >:D

Rik

My thinking was that a fixed rate switch might change things somewhere, but if you can live with the speed and the nagging, go get BT. ;)

An email to Uncle Ben might help, of course...
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

psp83

Just been on the phone to support and they say i haven't re sync'd since last night at 7pm, but my router and routerstats clearly show i have resync'd today.

So whats going on  ???

We've (support and I) agree'd to leave it till the end of the week and see how it goes once the builders pack up. They are also going to do a check on my account tomorrow morning to see if anything has changed.

Rik

One possibility could be that routerstats isn't showing a re-sync but an inability to access the router and obtain the data at that point, Paul. It will be interesting to see what the router logs show. Is anything running, eg email, besides RS?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby


psp83

Quote from: Rik on May 13, 2008, 15:01:12
One possibility could be that routerstats isn't showing a re-sync but an inability to access the router and obtain the data at that point, Paul. It will be interesting to see what the router logs show. Is anything running, eg email, besides RS?

The sync pic above shows it connected at just under 6000kbps and then after the spike, connected at just under 5000kbps so i dont know if thats a resync or the exchange dropping the sync rate. I'll be home at 6pm tonight so i will check the logs and post here.

Only routerstats is running on the pc.

Rik

True, I wasn't remembering the change in sync rate, but I have seen RS unable to access a router briefly and showing an apparent drop. For you to have had a sync rate change means there must have been a re-sync, wherever it was triggered, so I'm puzzled why support can't see one, Paul. :(
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

psp83

Quote from: Rik on May 13, 2008, 15:20:44
True, I wasn't remembering the change in sync rate, but I have seen RS unable to access a router briefly and showing an apparent drop. For you to have had a sync rate change means there must have been a re-sync, wherever it was triggered, so I'm puzzled why support can't see one, Paul. :(

Any chance the equipment in the exchange stayed connected to IDnet but i lost connection to the equipment in the exchange  ??? hence why IDnet didnt see the drop?

Rik

AFAIK, Paul, if your line drops your PPP session drops - which is the bit that IDNet see. I suppose it's possible that it happened so fast that PPP was unaffected. It will be interesting to see what the router shows and whether you have a stale session.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

That's my understanding, too. You can't lose the sync and not the PPP, but you can lose the PPP and not the sync.

psp83

Well. i've just checked the logs and theres nothing there but sync has lowered today.

Connection Speed     4896 kbps     448 kbps
Line Attenuation    40 db    13 db
Noise Margin    11 db    25 db

Theres nearly a 1000 kbps drop from this morning.
Attenuation has gone up on both down/up stream.

Routerstats:-

Tue 13 May 2008  13:29:52 **.***.**.** Rx-Noise= 10 Tx-Noise= 26 Rx-Sync= 5856 Tx-Sync= 448 Downstream Att= 39 Upstream Att= 12.5
Tue 13 May 2008  13:30:12 **.***.**.** Rx-Noise= 8 Tx-Noise= 26 Rx-Sync= 5856 Tx-Sync= 448 Downstream Att= 39 Upstream Att= 12.5
Tue 13 May 2008  13:30:32 **.***.**.** Rx-Noise= 9 Tx-Noise= 26 Rx-Sync= 5856 Tx-Sync= 448 Downstream Att= 39 Upstream Att= 12.5
Tue 13 May 2008  13:30:52 **.***.**.** Rx-Noise= 8 Tx-Noise= 26 Rx-Sync= 5856 Tx-Sync= 448 Downstream Att= 39 Upstream Att= 12.5
Tue 13 May 2008  13:31:12 **.***.**.** Rx-Noise= 8 Tx-Noise= 26 Rx-Sync= 5856 Tx-Sync= 448 Downstream Att= 39 Upstream Att= 12.5
Tue 13 May 2008  13:31:32 **.***.**.** Rx-Noise= 6 Tx-Noise= 26 Rx-Sync= 5856 Tx-Sync= 448 Downstream Att= 39 Upstream Att= 12.5
Tue 13 May 2008  13:31:52 **.***.**.** Rx-Noise= 2 Tx-Noise= 26 Rx-Sync= 0 Tx-Sync= 0 Downstream Att= 39 Upstream Att= 12.5
Tue 13 May 2008  13:32:12 **.***.**.** Rx-Noise= 0 Tx-Noise= 0 Rx-Sync= 0 Tx-Sync= 0 Downstream Att= 0 Upstream Att= 0
Tue 13 May 2008  13:32:32 **.***.**.** Rx-Noise= 10 Tx-Noise= 25 Rx-Sync= 4896 Tx-Sync= 448 Downstream Att= 40 Upstream Att= 13
Tue 13 May 2008  13:32:52 **.***.**.** Rx-Noise= 11 Tx-Noise= 25 Rx-Sync= 4896 Tx-Sync= 448 Downstream Att= 40 Upstream Att= 13
Tue 13 May 2008  13:33:12 **.***.**.** Rx-Noise= 11 Tx-Noise= 25 Rx-Sync= 4896 Tx-Sync= 448 Downstream Att= 40 Upstream Att= 13
Tue 13 May 2008  13:33:32 **.***.**.** Rx-Noise= 11 Tx-Noise= 25 Rx-Sync= 4896 Tx-Sync= 448 Downstream Att= 40 Upstream Att= 13


This part shows the loss of sync, margin drop.

Rik

How about the router's logs, Paul?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

psp83

Sun, 2002-09-08 13:00:21 - Initialize LCP.
Sun, 2002-09-08 13:00:21 - LCP is allowed to come up.
Sun, 2002-09-08 13:00:26 - CHAP authentication success
Sun, 2002-09-08 13:00:36 - Send out NTP request to time-g.netgear.com
Mon, 2008-05-12 19:05:50 - Receive NTP Reply from time-g.netgear.com
Mon, 2008-05-12 19:06:58 - Administrator login successful - IP:192.168.0.2
Mon, 2008-05-12 19:05:14 - Router start up
Tue, 2008-05-13 08:34:52 - Administrator login successful - IP:192.168.0.2
Tue, 2008-05-13 13:17:30 - TCP Packet - Source:**.**.**.**,**** Destination:**.**.**.**,**** - [VNC3 rule match]
Tue, 2008-05-13 13:17:31 - TCP Packet - Source:**.**.**.**,**** Destination:**.**.**.**,**** - [VNC3 rule match]
Tue, 2008-05-13 13:17:34 - TCP Packet - Source:**.**.**.**,**** Destination:**.**.**.**,**** - [VNC3 rule match]
Tue, 2008-05-13 17:54:28 - Administrator login successful - IP:192.168.0.2

Some of the log seems missing, it seems broke since the firmware update last night.

Rik

They did break the reporting of loss of sync, but I can't remember which version it was. The answer has to be to get a 2700. ;D
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

psp83

Quote from: Rik on May 13, 2008, 18:17:31
The answer has to be to get a 2700. ;D

I had one, my line didnt even like that one  :rant2:

psp83

Here's some more stats since 7pm last night:-

Connection Rate:  4896 Kbps
Line Attenuation: 40 dB
Noise Margin:     11 dB

Interleave CRC:   0
Interleave FEC:   0
Interleave HEC:   0

Fast path CRC:    132
Fast path FEC:    0
Fast path HEC:    0

Upstream (Tx):
  Good Cells: 36053
  Idle Cells: 18082968

Downstream (Rx):
  Good Cells: 323702
  Idle Cells: 197690699
  Bad HEC Cells: 585
  Overflow Dropped: 0

Bytes Transferred (PPP):
  Tx: 11630516 (11.0 Mb)
  Rx: 109212739 (104.1 Mb)

Rik

It's not even a big error count.  :shake:
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

psp83

Quote from: Rik on May 13, 2008, 18:22:54
It's not even a big error count.  :shake:

So i dont know whats going on with my line at the mo and it seems like no one else does aswell  :bawl:

Rik

About the only thing we can be certain of is that it's between you and the exchange. :(
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.