GENI Internet2 Switch URN Renaming

Internet2 plans an effort to migrate from SDN to MPLS in the AL2S backbone. The implementation of MPLS is to be verified by the ability to exchange GENI experiment traffic both via stitching or OpenFlow Over stitching after the upgrade has taken place. (Validation covered in sections x.x.)

This effort also includes a task to rename AL2S Switches from sdn-sw to rtsw. The renaming effort impacts: 1) GENI Aggregates, 2) Stitching Computation Services and 3) GENI Monitoring 4) Numerous wiki pages capturing network connectivity details. Thus is the bulk of the effort covered in all sections below.

Impacted AL2S Switches

The renaming effort impacts 26 AL2S switches whose URN is to be changed. Only 9 AL2S switches that are to be renamed have have stitching sites and require updates to GENI Aggregates, GENI Stitching Computation Service and GENI Monitoring. The AL2S switches with GENI Stitching sites connected are:

Old URN	New URN
sdn-sw.alba.net.internet2.edu	rtsw.alba.net.internet2.edu
sdn-sw.ashb.net.internet2.edu	rtsw.ashb.net.internet2.edu
sdn-sw.bato.net.internet2.edu	rtsw.bato.net.internet2.edu
sdn-sw.houh.net.internet2.edu	rtsw.houh.net.internet2.edu
sdn-sw.jack.net.internet2.edu	rtsw.jack.net.internet2.edu
sdn-sw.loui.net.internet2.edu	rtsw.loui.net.internet2.edu
sdn-sw.phil.net.internet2.edu	rtsw.phil.net.internet2.edu
sdn-sw.pitt.net.internet2.edu	rtsw.pitt.net.internet2.edu
sdn-sw.star.net.internet2.edu	rtsw.star.net.internet2.edu

Impacted GENI Sites

The 9 AL2S switches above have 23 GENI aggregates whose advertisement is to be reconfigured (1 AL2S +22 GENI Sites) to pick up the name change. Following are the details for the AL2S switches that will be reconfigured and tested along with the number of ports configured for switching and the switching sites associated with those ports.

1. Switch sdn-sw.star.net.internet2.edu has 4 stitching ports, some with multiple sites:
   • et-1/0/0.0 -> uchicago-ig, wisconsin-ig, wisc-clab[1], umich-ig
   • et-7/0/0.0 -> northwestern-ig
   • et-8/0/0.0 -> savi
   • et-9/0/0.0 -> illinois-ig

2. Switch sdn-sw.pitt.net.internet2.edu has 1 stitching port:
   • et-4/0/0.0 -> psc-eg[1]

3. Switch sdn-sw.phil.net.internet2.edu has 1 stitching port:
   • et-3/0/0.0 -> rutgers-ig

4. Switch sdn-sw.loui.net.internet2.edu has 1 stitching port with multiple sites:
   • et-3/0/0.0 -> uky-pg, uky-ig, ukypks2-ig, ukymcv-ig

5. Switch sdn-sw.jack.net.internet2.edu has 1 stitching port with multiple sites:
   • et-4/0/0.0 -> *[2], unf-eg[1], fiu-eg[1], ufl-eg[1]

6. Switch sdn-sw.houh.net.internet2.edu has 1 stitching port with multiple sites:
   • et-0/3/0.0 -> tamu-eg, [1], uh-campus

7. Switch sdn-sw.alba.net.internet2.edu has 1 stitching port:
   • xe-5/2/2.0 -> uvm-ig

8. Switch sdn-sw.ashb.net.internet2.edu has 1 stitching port:
   • et-3/0/0.0 -> vt-ig

1. Switch sdn-sw.bato.net.internet2.edu has 1 stitching port:
   • et-8/0/0.0 -> ullafayette-ig

[1] Test SCS only. All other sites apply to both Test and Production SCS.
[2] Not sure how this stitching endpoint is used or how to test.

Remember!!! Each AL2S Switch renaming impacts the AL2S Aggregate which advertises the network topology and must always capture the correct naming for each switch in the network.

URN Renaming Procedure

This procedure assumes the following:

• Sites will be migrates in batches to streamline effort and allow for efficiency.
• A common chat tool/live messaging is used to coordinate effort when sites are transitioned to the new URN
• Representatives for the impacted aggregates and for both Test and Production SCS are available for transition.
• URN Name transition will be planned while considering upcoming events.

Following is the procedure to be followed when the URN renaming takes place.

1. Generate GMOC Ticket

GMOC tickets must be generated capturing:

• Date and duration of the URN change activity
• Impacted to GENI sites. Scheduling

2. Review Affected Stitching Endpoint

Before URN renaming takes place, collect Aggregate Advertisement for all Aggregates impacted. To determine which sites are impacted, refer to the [xxx Impacted GENI Sites] section above.