Lost PPP

Started by .Griff., Oct 07, 2011, 16:08:41

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

.Griff.

At 16:05 PPP dropped but I'm still synced.

Anyone else?

(Posted from HTC)

esh

Nope, fine on 20CN -- though it seems to be usual that ye olde networke is more stable these days.
CompuServe 28.8k/33.6k 1994-1998, BT 56k 1998-2001, NTL Cable 512k 2001-2004, 2x F2S 1M 2004-2008, IDNet 8M 2008 - LLU 11M 2011

.Griff.

Back now. Looks like the same thing happened just after 1pm as well.  ???

zappaDPJ

No problems here Griff.
zap
--------------------

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

Rik

Or here. I think they're picking on you, Griff. ;)
Rik
--------------------

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

pctech

a temporary glitch in the BT network.


joe

Lostt PPP twice today whilst remaining synched. Explanations?


Rik

There was a loss of service at Stepney Green which might have affected you.
Rik
--------------------

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

joe

Thanks Rik.  I need to better understand how I keep DSL synch but lose PPP.

pctech

Sync is between your router and the kit at the exchange, establishment of PPP means that the router has to at least connect to the BRAS but for you to have Internet access the 3rd part needs to happen. connection to IDNet's edge gateway, RADIUS authentication and assignment of an IP, failure at Stepney Greeen would have prevented this stage.


Rik

Thanks, Mitch, saved my fingers. ;D
Rik
--------------------

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

pctech


Rik

I've just looked at the times for Stepney Green, the first set of red isn't explained by them, the second set fits very closely.
Rik
--------------------

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

pctech

Depending on the differences in time you can see it maybe that the actual device or service that failed was not actually monitored and a break in communication with said device or service was reported further up the chain or simply the monitoring system failed to receive a response.

While it is possible for devices to be proactive in raising an alarm this does not work if the device suffers a hardware, software or communication channel failure.

Therefore most network monitoring software works on a reactive basis, checks are run every predefined interval of say five minutes, the problem with this is that customers will often notice a problem before the alarm is raised by a test failure, setting the interval too short can use up resources on the monitored device and generate a great deal of network traffic.


joe

Thanks guys. Where did you find details of the failure at Stepney Green? I checked status at IDNet after the first failure and that said nothing.

Steve

Looking at my IDNet status RSS feed it was posted at 16:49. The time of the incident was 14:48.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.