Page 1 of 1

06-Feb-2009 - Scheduled Network Maintenance 12:01am - 2:00am

Posted: Thu Jan 29, 2009 2:28 am
by porcupine
Hi Guys,

Please be advised of the following maintenance window:

Maintenance Window: Friday February 6th 2009, 12:01am - 2:00am EST

Affected Device: core02.tor1
Affected Customers: physically/directly connected BGP Customers
Service Impacting: Yes - BGP Customer sessions will be gracefully turned down for the duration of this maintenance. All other BGP network traffic will be re-routed around device until the maintenance has completed.

Affected Device: dist02.tor1
Affected Customers: physically/directly connected customers
Service Impacting: Yes - Several short disruptions, totaling less then 15 minutes. A reload of the IOS software (reboot) may be performed during this time.

Details:

We will be upgrading core02.tor1’s supervisor card to a Sup720-3BXL, and replacing the current gigabit blade with a high density blade to allow further network growth and capacity.

This is a repeat of our maintenance plans from 16-Jan-2009 that were cut short due to a suspected Cisco ISIS bug between dist02.tor1 and core02.tor1. We believe we have isolated the cause of this bug, we expect there to be several short disruptions in service to the dist02.tor1 distribution router, which may require a reload (reboot) of said router. Customers who are not directly connected to either device, should see no interruption in services, and should treat this maintenance window as precautionary.

06-Feb-2009 - Scheduled Network Maintenance 12:01am - 2:00am

Posted: Fri Feb 06, 2009 4:08 am
by porcupine
Hi Guys,

Just to let everyone know, the network maintenance scheduled for 06-Feb-2009 12:01am - 2:00am has concluded, as per schedule.

I am pleased to report that the maintenance was completed successfully; the routing anomaly has been found (and corrected, permanently). The core02.tor1 router is now once again fully operational, with its new SUP720-3BXL supervisor card, finalizing our core network upgrades.

Customers who were interrupted during this maintenance have my sincere apologies. While we certainly knew this was a likely occurrence, and provided the best advance notification possible, we naturally strive to avoid any and all disruptions, as often as possible.

Regards,