Posts Tagged ‘Telford’

Emergency Maintenance: telford-dc3.core.enta.net

Posted: Monday, February 1st, 2010 at 12:34 by Steve Lalonde

Tuesday 2nd Feb 2010, 03:00hrs – 04:00hrs

To resolve the intermittent packet loss issue on the Telford to Wolverhampton link it has become necessary to reload telford-dc3.core.enta.net. This emergency work should take approx 10 minutes to complete, during which all directly connected customers will lose connectivity.

  1. Steve Lalonde says:

    This work was completed successfully. Traffic is now on the preferred paths and full resilience is restored.

At-Risk: Loss of Resilience Telford

Posted: Monday, February 1st, 2010 at 11:52 by Steve Lalonde

The Circuit between Telford and Wolverhampton has been taken off-line while we investigate intermittent packet loss issues with the circuit. Traffic usually on this path is using an alternative route. Customers may experience an increase in latency to some destinations.

  1. Steve Lalonde says:

    We have isolated the cause of the intermittent packet loss on this link to a configuration error. Unfortunately to resolve the issue requires a reload of the router. An emergency maintenance notification will follow.

Planned work: telford-dc3.core.enta.net

Posted: Wednesday, January 20th, 2010 at 15:26 by Steve Lalonde

Thursday 28th Jan 2010, 03:30hrs – 04:00hrs

During the maintenance window above the IOS on the router will be upgraded to resolve some configuration issues. This software upgrade will require a reboot of the router which should take approx 10 minutes to complete, during which all directly connected customers will lose connectivity.

Traffic that would normally be routed through this equipment will route via alternate paths.

  1. Steve Lalonde says:

    This work was completed successfully.

Planned work: telford-dc1.core.enta.net

Posted: Wednesday, January 20th, 2010 at 15:22 by Steve Lalonde

Thursday 28th Jan 2010, 03:00hrs – 03:30hrs

During the maintenance window above the IOS on the router will be upgraded to resolve some configuration issues. This software upgrade will require a reboot of the router which should take approx 10 minutes to complete, during which all directly connected customers will lose connectivity.

Traffic that would normally be routed through this equipment will route via alternate paths.

  1. Steve Lalonde says:

    This work was completed successfully.