I had 12 hours downtime last night, constantly receiving "LCP is allowed to come up." in my router log. Anyone else having this issue or is it just me? Was there any known problems in the Lincolnshire area last night?
Thanks.
The Peterborough problem is ongoing and could be affecting you. Are you losing sync (flashing lights) or PPP?
Quote from: A&AISP blogAt 19:10:12 all 21CN lines on the "PE" metronode, which is BRAS 21CN-BRAS-RED1-PE went off having suffered packet loss for around 15 minutes before.
We have seen this pattern a couple of times before although later in the evening and previously it lasted until 6am.
We are chasing with BT [again] as this is clearly a major issue.
Update: Debugging suggests this is an issue where specific IP to IP links within BT are not working. This means that by allocating our LNSs an alternative IP address we have been able to get most of the affected lines back on-line. This is clearly a BT core routing issue that needs to be fixed, and is not the first time we have seen something incredibly strange like this.
Update: We have everyone on-line but seeing packet loss on most lines.
Update: OK, only some lines have loss, most are clear, but bouncing the lines is not helping.
Update: Once again fixed before 6am.
Were they the timings for the problem yesterday?
@Rik, My router remained synced, that is to say the DSL indicator was solid green, and up/down streams on my router info were giving normal reading. The problem would occur in the actual connection process.
@Glenn, downtime started at 7:30pm last night, lasting until 7:30am this morning. There were a couple of occasions last night where connection would be re-established for a minute or 2 at a time but then quickly lost again.
This is the second time this week that this has happened. The first time also coincided with reports of problems with Peterborough.
Is there a way I can check if I am connected to Peterborough metronode? Certainly when I was with my previous ISP (Entanet) they talked about me being on Peterborough node.
LCP (Link Control Protocol) is part of the PPP protocol suite. If there's no PPP activity from the DSLAM, you'll see LCP errors.
Quote from: klipp on Dec 19, 2009, 13:20:52
Is there a way I can check if I am connected to Peterborough metronode? Certainly when I was with my previous ISP (Entanet) they talked about me being on Peterborough node.
You can, but it's not the easiest thing to do - give support a call, they will be able to check for you.
Support says they're closed for the weekend. I found a website with a list of the 21cn nodes, and Peterborough is indeed the only one that is in anyway close to me.
You can't rely on how close it is, though I think you do connect through there. Support is available for emergencies, ie no connection, so you can leave a message or email support@idnet.com if you have further problems. Someone will get back to you, usually within 24 hours.
Support have told me my connection goes through the Peterborough node and I'm in Ipswich.
My line was down on Tues evening, and approx 10 hours last night.
Fingers crossed it's sorted now.
:fingers: :fingers:
Oh for God Sake it's starting to do it again!!
What's your router doing, any flashing lights?
DSL (sync) light is solid green as per normal. The internet activity light is not flickering as much as it should normal do. Eventually the internet activity light will turn red and then the LCP errors will start appearing. My downtime matches Punch's.
Sorry for delay in replying, my connection is a complete mess at the moment lol.
So it's a PPP issue? Let support know.
Mines been off again this evening.
Currently back on (hence this post!) but it's a bit slow. All along I've stayed sync'd to my exchange.
Oh...and I've left 3 messages for support (2 last night) and as yet I've had no response.
No offense Punch, but I'm glad it's not just me!! ;D
It's not just IDNet either. While you have a connection email support with the problems.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\JoCa>ping www.idnet.net
Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=17ms TTL=59
Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 21ms, Average = 18ms
C:\Users\JoCa>tracert www.idnet.net
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.0.1
2 17 ms 17 ms 17 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 17 ms 17 ms 17 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 41 ms 20 ms 144 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 17 ms 18 ms 18 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 17 ms 18 ms 17 ms www.idnet.net [212.69.36.10]
Trace complete.
Done a quick ping and tracert. Everything is excellent except hop 4 on the tracert.
I wouldn't worry too much about that, Jonathan, the routers give low priority to pings, the overall ping is fine.