New traffic management hardware

[#1]

Hi Pwatson.
This is perfect.  We've got a new DPI box in, which means there could be problems with traffic identification.  We can't test every application signature to make sure it works, so it's important to get decent information about any possible issues you might be seeing.
Can you get reconnected to PCL-AG01 so we can try and see if the application is being identified properly?

[#2]

Hi Kelly,
I'll try when I get a chance.  I'm using standard SIP for Sipgate and calls worked first thing in the morning so I think it's unlikely that the new hardware is involved.  Do your systems show when I moved onto PCL-AG01?

[#3]

You are currently on ptw-ag04 and connected to it 15:34 23/May/2013. 
You were previously on pcl-ag01 and connect to it at 20:51 18/May/2013

[#4]

If I'm on pcl-ag01 should I be seeing a tracert to one of the DNS servers going to a server in ptn? I thought all four IP addresses went to the same set of load balanced DNS servers within the data centre you are connected to?

[#5]

Good spot Jelv, I'd have thought you'd be routed to the caching servers in City Lifeline. Bizarrely if you trace to the 212.159.6.9, 212.159.6.10 or 212.159.13.49 VIPs then you are routed there. The 212.159.13.50 VIP takes you to Telehouse North though
Edit: Same thing happens on other City Lifeline gateways so I don't think it's anything specific to the new DPI platform.

[#6]

I'm not on pcl-ag01 atm and all my tracerts to ntp.plus.net go to one cdns server  with one IP address on a particular day/hour/whatever. I'll start another thread as I have a few questions and it would be off-topic here.

[#7]

Thread regarding tracert's is http://community.plus.net/forum/index.php/topic,115267.0/topicseen.html.
Now on pcl-ag01 since 0647 after power cut in the early hours  
Is an extra hop involved?
Pings seem ok at present.
Edit: Well I was on pcl-ag01 until I was about to post this and something dropped the PPP - nothing this end - will have to go hopping  
Edit2: Was Plusnet kicking anyone off Gateways at 0730?

[#8]

Quote from: Anotherone

Edit2: Was Plusnet kicking anyone off Gateways at 0730?

No, not en masse. The disconnect was us though. It was in response to your IP Profile (and subsequently your Plusnet profile) changing.

[#9]

Thanks for the reply Bob, I'll make further comment in the other relevant thread. Could you please PM the relevant Delta report info & current line speed change details - thanks.

[#10]

Quote from: Anotherone

Could you please PM the relevant Delta report info & current line speed change details - thanks.

Done.

[#11]

Hi all,
Tomorrow morning we'll be enabling another one of our gateways (PCL-AG03) to use this new platform.
The switch over went fine for PCL-AG01 and we've moved PCL-AG02 onto the new platform this morning and all seems OK so we don't expect any issues, but if you think you spot any please let us know.
We've also posted a service status.

[#12]

On Monday(24th) morning we'll be bringing another one of our gateways (PCL-AG04) to use this new platform.
Again we don't expect any issues, but if you think you spot any please let us know.
We'll also be enabling PCL-AG05 on Tuesday(25th) morning and PCL-AG06 on Wednesday(26th) morning.

[#13]

Tomorrow morning(10th) we'll be bringing another two of our gateways (PCL-AG07 & PCL-AG08) to use this new platform.
Again we don't expect any issues, but if you think you spot any please let us know.

[#14]

Monday afternoon(15th) we'll be bringing another two of our gateways (PTW-AG01 and PTW-AG03) to use this new platform.
As previously we don't expect any issues, but if you think you spot any please let us know.

[#15]

Quote from: chrispurvey

Tomorrow morning(10th) we'll be bringing another two of our gateways (PCL-AG07 & PCL-AG08) to use this new platform. Again we don't expect any issues, but if you think you spot any please let us know.

I'm on this now Chris and it''s perfect, I didn't know we could switch Gateways sometimes my latency would increase and now I know why.
I am on this gateway now:

C:\Users\Alistair>ping bbc.co.uk
Pinging bbc.co.uk [212.58.251.195] with 32 bytes of data
Reply from 212.58.251.195: bytes=32 time=18ms TTL=117
Reply from 212.58.251.195: bytes=32 time=18ms TTL=117
Reply from 212.58.251.195: bytes=32 time=18ms TTL=117
Reply from 212.58.251.195: bytes=32 time=18ms TTL=117
Ping statistics for 212.58.251.195:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 18ms, Average = 18ms
C:\Users\Alistair>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.253.67]
over a maximum of 30 hops:
  1    63 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2    18 ms    18 ms    18 ms  lo0-central10.pcl-ag07.plus.net [195.166.128.188
]
  3    18 ms    17 ms    17 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.18
6]
  4    18 ms    18 ms    17 ms  218.core.access.plus.net [212.159.0.218]
  5    18 ms    18 ms    18 ms  ae1.ptw-cr02.plus.net [195.166.129.2]
  6    18 ms    17 ms    21 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
  7    28 ms    18 ms    18 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  8    *        *        *    Request timed out.
  9    19 ms    19 ms    19 ms  ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
10    19 ms    19 ms    19 ms  132.185.255.156
11    19 ms    19 ms    19 ms  www-vip.cwwtf.bbc.co.uk [212.58.253.67]
Trace complete.