We will be shutting down our Frontier interconnect in preparation of moving the circuit from our current legacy access device to CORE01 as part of our ongoing network upgrade works. The circuit will be physically moved on the 27/03/2015 while and engineer is on site and bought back in to service that evening outside of hours.
Call traffic will be routed away from this interconnect several hours prior to the works, However any calls still active on this link will drop once disconnected. Routing to Frontier will then be via one of our indirect peers after the disconnection. No further impact is expected after this.
UPDATE 01 – 20:30
The subject maintenance this evening has been postponed. New dates will be announced in due course.
Apologies for any inconvenience caused.
UPDATE 02 – 05/04/2015
This work has been re-booked for Tuesday the 07th April 2015 at the same time. A new maintenance window will be created.
In order to allow for extra IPv4 capacity in Rack03 to accommodate our new ESXi platform for VoIP we will be merging both Vlan30 & Vlan40 in to a single /25 subnet.
Customers who have unmanaged co-location with us in the 18.104.22.168/26 range will need to update the following on there devices on the day:
New gateway: 22.214.171.124
New subnet: 255.255.255.128
Once these changes are made, customers will loose access to there devices until we finalize the amended VLAN. We will be making these changes at 20:05 so would suggest customers make these changes as close to 20:00 as possible.
Please remember to commit these changes to memory once access has been re-gained as we will be moving power feeds / racks to reflect this around 21:00
We will be relocating both our ROOT name servers in the above window to another rack within our suite. This is to enable us to remove an old 10/100 line card and replace with a Fiber GBIC line card in our current Cisco Core in preparation for other upgrade works.
Each server will be migrated in turn to avoid any serious disruption, however there may be a few moments where both forwarding and reverse query’s are refused while the servers switch between primary and backup modes as they are taken on and offline.