DYNES-Deployments

["David A. J. Ripley" <>]

The next maintenance is scheduled for tomorrow morning, 6:00 AM - 11:00 AM 
UTC. We apologize for the short notice, complete information only just became 
available.

The interface changes are:

Current         Post-maintenance
xe-0/0/0        xe-0/1/0
xe-0/0/1        xe-0/1/1
xe-0/0/2        xe-0/1/2
xe-0/0/3        xe-0/1/3
xe-0/1/0        xe-0/0/0
xe-0/1/1        xe-0/0/1
xe-0/1/2        xe-0/0/3
xe-0/1/3        xe-7/0/1
ge-6/0/0        xe-0/0/2
ge-6/1/0        xe-7/0/2
ge-6/2/0        xe-7/0/0
ge-7/0/0        ge-10/2/0
ge-7/0/1        ge-10/2/1
ge-7/0/2        ge-10/2/2
ge-7/0/3        ge-10/2/3
ge-7/0/4        ge-10/2/4
ge-7/1/0        ge-10/2/5
ge-7/1/1        ge-10/2/6
ge-7/1/2        ge-10/2/7

The approximate windows for the next maintenances are as follows:

feb 27-March 1st KANS

March 4-8th - SEAT

March 11-13th LOSA

March 17-22 - CHANGE FREEZE

March 27-29 - NEWY

Apri 3-5 - HOUS

April 10-12 - ATLA

April 17-19 - WASH 

D.

On Feb 11, 2013, at 2:46 AM, David A. J. Ripley 
<>
 wrote:

> In the upcoming weeks, new equipment is going to be installed in the
> Internet2 network. The Internet2 ION service will be unavailable during
> the maintenance windows, and configuration changes will most likely be
> required at DYNES sites and other IDC peers in order to reflect
> interface changes on the Internet2 network. In addition, circuits
> traversing the equipment involved in the maintenances will need to be
> canceled to prevent inconsistencies in network device configurations.
> 
> The first change is the insertion of a new node in Cleveland, scheduled
> for 0400-0900 UTC Feb 12;
> 
> No topology changes will be required at peer IDCs, but circuits
> traversing CHIC->NEWY or CHIC->WASH links will be canceled and the I2
> IDC will be unavailable during the maintenance window.
> 
> The I2 core node at Chicago is scheduled to be replaced at 0500-1000 UTC
> Feb 14th. Circuits involving this node will be canceled prior to the
> maintenance. Peers may need to update interface specification in remote
> link IDs in their topology specifications as follows:
> 
> current         post-maintenance
> xe-0/0/0      xe-7/1/3
> xe-0/0/1      xe-0/2/0
> xe-0/0/3      xe-0/1/3
> xe-0/1/1      xe-0/1/0
> xe-0/1/2      xe-0/2/2
> xe-0/1/3      xe-0/1/2
> xe-2/0/0      xe-0/2/3
> xe-2/0/1      xe-0/3/0
> xe-2/0/3      xe-0/3/1
> xe-2/1/0      xe-7/1/2
> xe-2/1/3      xe-0/3/3
> xe-3/2/0      xe-7/2/0
> ge-7/1/0      xe-7/2/2
> 
> Subsequent maintenances will follow at approximately weekly intervals;
> we will post the information to these lists as soon as it becomes available.
> 
> D.
> -- 
> David A. J. Ripley, Systems Engineer
> Indiana University GlobalNOC.
> <>
>  +1-812-855-5079
> http://mypage.iu.edu/~daripley/daripley.pgp

--
David A. J. Ripley, Systems Engineer
Indiana University GlobalNOC.
<>
 +1-812-855-5079
http://mypage.iu.edu/~daripley/daripley.pgp