cancel
Showing results for 
Search instead for 
Did you mean: 

Gateway checking and troubleshooting

Community Veteran
Posts: 3,789
Registered: 08-06-2007

Gateway checking and troubleshooting

I just raised a point with Jameseh that the Usertools gateway checker needs updating so that 32.core.plus.net is identified as a proper gateway.
However, this did get me thinking about how the gateways are identified.  As it stands at the moment, do all Aladdin triallists rise onto one 'real' gateway or do they rise on whichever gateway they get sent to, and are then virtualised to 32.core.plus.net?
This could have a bearing when attempting to troubleshoot connection issues (not Aladdin specific ones, just general speed queries) as any triallist is not aware of which gateway they are actually connected to.  In the case of the other night when PCL-AG02 was dropping gold traffic this could actually be useful information.
I'm assuming that the current configuration is for the trial - What is the configuration intended to be if/when the system is deployed live?
B.
2 REPLIES
Plusnet Alumni (retired) _CN_
Plusnet Alumni (retired)
Posts: 385
Registered: 11-06-2007

Re: Gateway checking and troubleshooting

The end user will always see 32.core.plus.net as the gateway (this happens to be a virtual router on PCL-AG01), but does not necessarily mean that you are on the central that terminates on PCL-AG01 as you get tunnel-switched from the central gateway your really connected to over to PCL-AG01 via our core network while on the Aladdin trial.
Our RADIUS tool internally does show which gateway you are tunnel-switched from, see the example below of my RADIUS logs -
Access Rack Last Event Event Time Message IP Assigned Service Calling From Session Started Session Ended Session Duration
Plusnet ADSL 2 MEG 195.166.128.23 active 15:44 13/Jun/2008 unknown (Interim update) 84.92.79.1 Not set ip:195.166.128.57:21 11:44 05/Jun/2008 N/A 8 Days, 4:36:30 (on going)
Plusnet ADSL 2 MEG 195.166.128.23 ended 11:44 05/Jun/2008 unknown (Administrative reset) 84.92.79.1 Not set ip:195.166.128.36:21 17:22 04/Jun/2008 11:44 05/Jun/2008   18:21:36
Plusnet ADSL 2 MEG 195.166.128.23 ended 17:22 04/Jun/2008 unknown (User request) 84.92.79.1 Not set ip:195.166.128.37:21 14:27 04/Jun/2008 17:22 04/Jun/2008   2:54:44
Plusnet ADSL 2 MEG 195.166.128.23 ended 14:27 04/Jun/2008 unknown (User request) 84.92.79.1 Not set ip:195.166.128.63:21 08:50 04/Jun/2008 14:27 04/Jun/2008   5:36:46
Plusnet ADSL 2 MEG 195.166.128.23 ended 08:50 04/Jun/2008 unknown (Administrative reset) 84.92.79.1 Not set ip:195.166.128.78:21 08:15 04/Jun/2008 08:50 04/Jun/2008   0:35:4
Plusnet ADSL 2 MEG 195.166.128.23 ended 08:15 04/Jun/2008 unknown (Administrative reset) 84.92.79.1 Not set 08:02 29/May/2008 08:15 04/Jun/2008 6 Days, 0:12:53
The 'Calling From' column is the actual gateway (central) I'm connected to and my connection is always tunnel-switched to PCL-AG01 as per the 'Access Rack' column.  Notice the entry for 08:02 29/May/2008 - 08:15 04/Jun/2008, this has no entry in the 'Calling From' column, this indicates that I was connected to the central that terminates on PCL-AG01 so did not need to be tunnel-switched.
HTH
Plusnet Alumni (retired) _CN_
Plusnet Alumni (retired)
Posts: 385
Registered: 11-06-2007

Re: Gateway checking and troubleshooting

Quote from: Barry
I'm assuming that the current configuration is for the trial - What is the configuration intended to be if/when the system is deployed live?

The design for a live product has not started yet, but it would be something similar to how it works now, only in the sense that some sort of tunneling would need to take place to switch the user across to the platform that is performing the 'clean web' and 'url filtering' functionality.  Also looking at using MPLS/VRFs will come into consideration but like I said, no work has begun on a live production design.
HTH