Changes between Initial Version and Version 1 of URNConsolidation


Ignore:
Timestamp:
07/12/16 17:00:37 (8 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • URNConsolidation

    v1 v1  
     1[[PageOutline(1-3)]]
     2
     3= GENI Switch Consolidation Procedure =
     4
     5This page defines the steps required to update stitching to handle PoP device consolidation that is taking place in Internet2 AL2S. This consolidation will replace existing AL2S Brocade devices with Juniper devices, and will converge the two distinct devices that currently provide L2 and L3 services into a single converged Juniper device in locations where AL2S services exist.  These steps outline the actions required at the GENI rack, AL2S AM, and SCS servers to incorporate URN changes (due to port changes) resulting from the consolidation.
     6
     7The steps show examples based on details from previous switch consolidation and its effect on GENI stitching sites connected to this switch.
     8
     9== 0. Generate Tickets and check for conflicts with any upcoming ticketed GENI events ==
     10
     11Make sure tickets are opened at GMOC for the events listing all affected GENI resources.  Also make sure that GMOC generates corresponding requests to Internet2 Engineering (GRNOC).  Tickets should notify operators and experimenters.  Adam Williams will coordinate efforts for GMOC, but initial requests should go to the usual GMOC email for ticket requests.  (This has already been done for NYC maintenance.)
     12
     13Note that Internet2 schedules both an IP and an AL2S outage (usually on different days) for each PoP consolidation.  The IP event has no related GENI URN work needed, and will simply result in the GENI resources being unreachable (because the entire device is disconnected).  The GMOC should create tickets for both events, since they both have GENI impact, and the rack admins should see the tickets if they read their GENI operators email.
     14
     15Internet2 won't change their schedule, but you should notify any conflicting events about the maintenance and work with them to avoid any impact as much as possible.
     16
     17If the event goes longer than the scheduled tickets, be sure to email updates to the GMOC when you know that will happen, and every 2 hours thereafter.  If the event will continues to the next day, say so in your last ticket update, and tell them when you'll check in again the next day.  (You don't have to update in between).
     18
     19If there are any significant problems during the event, be sure to escalate to Heidi Dempsey (hdempsey@bbn.com) while you work on them (in addition to noting them in the ticket).
     20
     21== 1. Find Current Stitching Configuration ==
     22
     23The aggregate advertisement includes a ''stitching'' section which defines how VLANs are to be connected and which VLANs are associated with that stitching endpoint.  To determine the impact of a consolidation on stitching you must start by collecting the the AL2S advertisement:
     24{{{
     25   omni -a al2s listresources -o
     26}}}
     27Review the content of the stitching section in the output file rspec-al2s-internet2-edu.xml and see that there any site affected.
     28
     29For example there were several stitching endpoints for sdn-sw.newy32aoa.net.internet2.edu.  Here is the list from an AL2S Advertisement:
     30{{{
     31 <stitch:node id="urn:publicid:IDN+al2s.internet2.edu+node+sdn-sw.newy32aoa.net.internet2.edu">
     32 <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.newy32aoa.net.internet2.edu:eth1/1">
     33 <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.newy32aoa.net.internet2.edu:eth1/1:iminds">
     34 <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.newy32aoa.net.internet2.edu:eth5/2">
     35 <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.newy32aoa.net.internet2.edu:eth5/2:gpo-og">
     36 <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.newy32aoa.net.internet2.edu:eth5/2:gpo-eg">
     37 <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.newy32aoa.net.internet2.edu:eth5/2:gpo-ig">
     38 <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.newy32aoa.net.internet2.edu:eth5/2:host-gpolab">
     39 <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.newy32aoa.net.internet2.edu:eth5/2:umass-eg">
     40 <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.newy32aoa.net.internet2.edu:eth7/2">
     41 <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.newy32aoa.net.internet2.edu:eth7/2:nysernet-ig">
     42}}}
     43
     44From the above we will only request the "<stitch:link id" transition, the "<stitch:port id" transitions are implicit. From the above list there are 6 aggregates (2 InstaGENI, 2 ExoGENI, 1 OpenGENI and 1 iMinds) and 1 fixed endpoint (host-gpolab. 
     45
     46Note: In Stitching a fixed endpoint is a resource that is not a GENI aggregate but still supports stitching.  Fixed endpoint are statically configured in the SCS servers to capture stitching information and are generally set up for specific demonstrations. Some example fixed-endpoints are:
     47{{{
     48[[PageOutline(1-3)]]
     49
     50= GENI Consolidation - New York =
     51
     52This page defines the steps required to update stitching to handle PoP device consolidation that is taking place in Internet2 AL2S. This consolidation will replace existing AL2S Brocade devices with Juniper devices, and will converge the two distinct devices that currently provide L2 and L3 services into a single converged Juniper device in locations where AL2S services exist.  These steps outline the actions required at the GENI rack, AL2S AM, and SCS servers to incorporate URN changes (due to port changes) resulting from the consolidation.
     53
     54The steps shown below detail how the AL2S sdn-sw.newy32aoa.net transition will affect the GENI stitching sites connected to this switch.
     55
     56== 0. Generate Tickets and check for conflicts with any upcoming ticketed GENI events ==
     57
     58Make sure tickets are opened at GMOC for the events listing all affected GENI resources.  Also make sure that GMOC generates corresponding requests to Internet2 Engineering (GRNOC).  Tickets should notify operators and experimenters.  Adam Williams will coordinate efforts for GMOC, but initial requests should go to the usual GMOC email for ticket requests.  (This has already been done for NYC maintenance.)
     59
     60Note that Internet2 schedules both an IP and an AL2S outage (usually on different days) for each PoP consolidation.  The IP event has no related GENI URN work needed, and will simply result in the GENI resources being unreachable (because the entire device is disconnected).  The GMOC should create tickets for both events, since they both have GENI impact, and the rack admins should see the tickets if they read their GENI operators email.
     61
     62Internet2 won't change their schedule, but you should notify any conflicting events about the maintenance and work with them to avoid any impact as much as possible.
     63
     64If the event goes longer than the scheduled tickets, be sure to email updates to the GMOC when you know that will happen, and every 2 hours thereafter.  If the event will continues to the next day, say so in your last ticket update, and tell them when you'll check in again the next day.  (You don't have to update in between).
     65
     66If there are any significant problems during the event, be sure to escalate to Heidi while you work on them (in addition to noting them in the ticket).
     67
     68== 1. Find Current Stitching Configuration ==
     69
     70The aggregate advertisement includes a ''stitching'' section which defines how VLANs are to be connected and which VLANs are associated with that stitching endpoint.
     71
     72Get the AL2S advertisement:
     73{{{
     74   omni -a al2s listresources -o
     75}}}
     76Review the content of the stitching section in the output file rspec-al2s-internet2-edu.xml and see that there are several stitching endpoints for sdn-sw.newy32aoa.net.internet2.edu.  Here is the list:
     77{{{
     78 <stitch:node id="urn:publicid:IDN+al2s.internet2.edu+node+sdn-sw.newy32aoa.net.internet2.edu">
     79 <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.newy32aoa.net.internet2.edu:eth1/1">
     80 <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.newy32aoa.net.internet2.edu:eth1/1:iminds">
     81 <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.newy32aoa.net.internet2.edu:eth5/2">
     82 <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.newy32aoa.net.internet2.edu:eth5/2:gpo-og">
     83 <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.newy32aoa.net.internet2.edu:eth5/2:gpo-eg">
     84 <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.newy32aoa.net.internet2.edu:eth5/2:gpo-ig">
     85 <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.newy32aoa.net.internet2.edu:eth5/2:host-gpolab">
     86 <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.newy32aoa.net.internet2.edu:eth5/2:umass-eg">
     87 <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.newy32aoa.net.internet2.edu:eth7/2">
     88 <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.newy32aoa.net.internet2.edu:eth7/2:nysernet-ig">
     89}}}
     90Note, from the above we will only request the "<stitch:link id" transition, the "<stitch:port id" transitions are implicit.
     91
     92NB. If a site is listed (such as "sdn-sw.tuls.net.internet2.edu") but there no racks attached and the new URN is different from the old (In this particular case, the new URN "sdn-sw.tuls.net.internet2.edu" was the same as the old, so no changes were necessary), only the following is necessary:
     93
     94 a. Ask the GMOC to update the URN at the AL2S and the production SCS.
     95 b. Ask Xi to update the URN at the test SCS.
     96
     97== 2. Define Stitching Configuration Changes ==
     98
     99These are the consolidations to update AL2S NEWY, according to email from Eric Boyd of Internet2:
     100
     101{{{
     102 Old Hostname: sdn-sw.newy32aoa.net.internet2.edu
     103 New Hostname: rtsw.newy32aoa.net.internet2.edu
     104        'Old Interface'                       'New Interface'
     105 100GigabitEthernet1/1   100GE                   et-3/1/0.0
     106 100GigabitEthernet1/2   100GE                   et-3/3/0.0
     107 100GigabitEthernet3/1   100GE                   et-7/1/0.0
     108 100GigabitEthernet5/2   100GE                   et-7/2/0.0 (INCORRECT)
     109 100GigabitEthernet5/2   100GE                   et-7/3/0.0 (according to AJ Ragusa)
     110 100GigabitEthernet7/1   100GE                   et-4/1/0.0
     111 100GigabitEthernet7/2   100GE                   et-4/3/0.0
     112 10GigabitEthernet15/1   10GE                    xe-3/0/0.0
     113 10GigabitEthernet15/4   10GE                    xe-3/0/1.0
     114 10GigabitEthernet15/5   10GE                    xe-3/0/2.0
     115 10GigabitEthernet15/7   10GE                    xe-3/0/3.0
     116}}}
     117Hence, there are seven sites impacted by this URN transition. The table below highlights each of the transitions:
     118||'''Old URN                                             || ''' New URN ''' ||
     119|| sdn-sw.newy32aoa.net.internet2.edu:eth1/1:iminds      || rtsw.newy32aoa.net.internet2.edu:et-3/1/0.0:iminds ||
     120|| sdn-sw.newy32aoa.net.internet2.edu:eth5/2:gpo-og      || rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-og ||
     121|| sdn-sw.newy32aoa.net.internet2.edu:eth5/2:gpo-eg      || rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-eg ||
     122|| sdn-sw.newy32aoa.net.internet2.edu:eth5/2:gpo-ig      || rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-ig ||
     123|| sdn-sw.newy32aoa.net.internet2.edu:eth5/2:host-gpolab || rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:host-gpolab ||
     124|| sdn-sw.newy32aoa.net.internet2.edu:eth5/2:umass-eg    || rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:umass-eg ||
     125|| sdn-sw.newy32aoa.net.internet2.edu:eth7/2:nysernet-ig || rtsw.newy32aoa.net.internet2.edu:et-4/3/0.0:nysernet-ig ||
     126
     127
     128== 3. Request Stitching Changes from GENI Aggregate Operations Teams ==
     129
     130This URN transition will require co-ordination with the following teams:
     131  * InstaGENI: (geni-ops@googlegroups.com) Request will be handled by Hussam Nasir (nasir@netlab.uky.edu)
     132  * ExoGENI: (exogeni-ops@renci.org) Request will be handled by Mert Cevik (mcevik@renci.org) or Ilya Baldin (ilbadin@renci.org)
     133  * OpenGENI: Marshall Brinn (Mbrinn@bbn.com) and Regina Rosales-Hain (rrhain@bbn.com)
     134  * AL2S Aggregate and Production SCS: GMOC requests(gmoc@grnoc.iu.edu). Updates handled by Luke Fowler (luke@grnoc.iu.edu) or AJ Ragusa (aragusa@grnoc.iu.edu), cc: both on initial request.
     135  * Test SCS - Xi Yang (xyang@maxgigapop.net)
     136  * iMinds - Brecht Vermeulen (brecht.vermeulen@iminds.be>
     137
     138=== 3a. Define Change Request Details ===
     139
     140GPO IG and NYSERNet URNs Changes Request to InstaGENI Team:
     141{{{
     142Link ID:          urnpublicid:IDN+instageni.gpolab.bbn.com+interface+procurve2:5.24.al2s
     143Remote Link ID:   urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-ig
     144VLAN Range:       3596-3600,3706-3732,3746-3749
     145
     146Link ID:          urnpublicid:IDN+instageni.nysernet.org+interface+procurve2:1.19.al2s
     147Remote Link ID:   urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-4/3/0.0:nysernet-ig
     148VLAN Range:       1700-1719
     149}}}
     150
     151GPO EG URNs Change Request for ExoGENI Team:
     152{{{
     153Link ID:          urnpublicid:IDN+exogeni.net:bbnNet+interface+BbnNet:IBM:G8052:GigabitEthernet:1:2:ethernet
     154Remote Link ID:   urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-eg
     155VLAN Range:       3741,3736-3739
     156}}}
     157
     158GPO OG URNs Change Request for OpenGENI Team:
     159{{{
     160Link ID:          urnpublicid:IDN+bbn-cam-ctrl-1.gpolab.bbn.com+interface+force10:3:al2s
     161Remote Link ID:   urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-og
     162VLAN Range:       2611-2630
     163}}}
     164
     165Wall2 iMinds URN Change Request to Imind Team:
     166{{{
     167Link ID:          urnpublicid:IDN+wall2.ilabt.iminds.be+interface+c300b:0.12
     168Remote Link ID:   urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-3/1/0.0:iminds
     169VLAN Range:       1125-1164
     170}}}
     171
     172AL2S Aggregate URN Change Request for GMOC/GRNOC:
     173{{{
     174Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-3/1/0.0:iminds
     175Remote Link ID:   urnpublicid:IDN+wall2.ilabt.iminds.be+interface+c300b:0.12
     176VLAN Range:       1125-1164
     177
     178Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-og
     179Remote Link ID:   urnpublicid:IDN+bbn-cam-ctrl-1.gpolab.bbn.com+interface+force10:3:al2s
     180VLAN Range:       2611-2630
     181
     182Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-eg
     183Remote Link ID:   urnpublicid:IDN+exogeni.net:bbnNet+interface+BbnNet:IBM:G8052:GigabitEthernet:1:2:ethernet
     184VLAN Range:       3741,3736-3739
     185
     186Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-ig
     187Remote Link ID:   urnpublicid:IDN+instageni.gpolab.bbn.com+interface+procurve2:5.24.al2s
     188VLAN Range:       3596-3600,3706-3732,3746-3749
     189
     190Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-4/3/0.0:nysernet-ig
     191Remote Link ID:   urnpublicid:IDN+instageni.nysernet.org+interface+procurve2:1.19.al2s
     192VLAN Range:       1700-1719
     193
     194Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:host-gpolab
     195Remote Link ID:   urnpublicid:IDN+gpolab.bbn.com+interface+switch:port:al2s
     196VLAN Range:       2646
     197
     198Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:umass-eg
     199Remote Link ID:   urnpublicid:IDN+exogeni.net:umassNet+interface+umassNet:IBM:G8264:TenGigabitEthernet:1:1:ethernet
     200VLAN Range:       3581-3595
     201
     202}}}
     203
     204=== 3b. Make Requests for Aggregate Updates ===
     205
     206Send Email to each of the teams to request the above changes:
     207  - IG
     208  - EG
     209  - OG
     210  - iMinds
     211  - Internet2
     212
     213As a courtesy, copy the rack admin contact(s) or email list from the operators page on these requests.  They don't have to take any action, but they may want to know that their racks will be potentially unable to stitch for a period of time during the scheduled outage.
     214
     215Also copy kathryn.wong1@uky.edu, cody@uky.edu and caylin@uky.edu, With the exception of the ATLA consolidation, this work should not require any immediate action for monitoring, but the folks at UKY may want to note the "retired" URNs in their database, and to pay extra attention to their monitoring site during these transitions.
     216 
     217
     218''' ''Once the requested changes are completed, verify that the requested changes appear in the rack aggregate advertisement.''' ''
     219{{{
     220$ for i in gpo-ig gpo-og gpo-eg nysernet-ig al2s wall2 ; do stitcher listresources -a $i -o; done
     221}}}
     222
     223
     224You can now review all output files to verify that the correct URN is in place for each advertisement.
     225
     226==== InstaGENI Update Alternatives ====
     227
     228InstaGENI may be slow to respond, so you may do any of the following:
     229  1. Ask Hussam (nasir@netlab.uky.edu) to run the commands below on the boss node.
     230  2. Or contact the site admin and have them log into boss node and run these commands.
     231  3. You can create an admin account on the boss node (via the web UI for the site, e.g. http://instageni.gpolab.bbn.com/ for gpo-ig) and once it is approved, you can run the commands.
     232   
     233Below is an old example for the commands issued on the uwashington-ig boss node:
     234{{{
     235 mysql tbdb -e 'update external_networks set external_interface="urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.seat.net.internet2.edu:et-4/3/0.0:uwashington-ig" where network_id="al2s"'
     236
     237 mysql tbdb -e 'update external_networks set external_wire="urn:publicid:IDN+al2s.internet2.edu+link+rtsw.seat.net.internet2.edu:et-4/3/0.0:uwashington-ig" where network_id="al2s"'
     238
     239}}}
     240
     241''Note: Be aware of potential line wrapping pitfalls.''
     242   
     243
     244== 4. Request SCS Update ==
     245
     246In order for GENI Network Stitching to pick up these path configuration changes, an SCS Update must be run.  There are two SCS systems:
     247  - Test SCS maintained by Xi Yang (xyang@maxgigapop.net)
     248  - Production SCS mainted by the Internet2 (gmoc@grnoc.iu.edu). Updates handled by Luke Fowler (luke@grnoc.iu.edu) or AJ Ragusa (aragusa@grnoc.iu.edu).
     249
     250To find out which SCS knows about which aggregates, issue the following:
     251
     252For the Production SCS:
     253{{{
     254$ python ~/gcf/src/gcf/omnilib/stitch/scs.py --listaggregates --scs_url http://geni-scs.net.internet2.edu:8081/geni/xmlrpc >scs-prod
     255}}}
     256The above shows that the GPO IG, GPO EG, and NYSERnet IG sites are known to the Production SCS.
     257
     258For the Test SCS:
     259{{{
     260python gcf/gcf-current/src/gcf/omnilib/stitch/scs.py --listaggregates --scs_url http://nutshell.maxgigapop.net:8081/geni/xmlrpc > scs-test
     261}}}
     262The above shows that the GPO IG, GPO EG, GPO OG, NYSERnet IG, iMinds, and Umass site are known to the Production SCS.
     263
     264
     265Both Production and Test SCS are impacted by the updates. Send a request to:
     266 - the GMOC to the Production SCS
     267 - to Xi to update the Test SCS.
     268
     269
     270== 5. Validate Updated Stitching ==
     271
     272When the updates are completed for all Aggregates and for SCS servers, ask Luisa to conduct stitching tests.
     273
     274== 6. Update and close all tickets ==
     275
     276Assuming all tests are successful, update and close all tickets by emailing the GMOC.  If there are outstanding issues that are significant, leave the ticket open until they are resolved.  If there are smaller outstanding issues, close the maintenance tickets, and open new tickets with the appropriate owners to track and resolve, ideally before the next maintenance.
     277
     278
     279
     280
     281Note:  If a site is listed (such as "sdn-sw.tuls.net.internet2.edu") but there no racks attached and the new URN is different from the old (In this particular case, the new URN "sdn-sw.tuls.net.internet2.edu" was the same as the old, so no changes were necessary), only the following is necessary:
     282
     283 a. Ask the GMOC to update the URN at the AL2S and the production SCS.
     284 b. Ask Xi to update the URN at the test SCS.
     285
     286== 2. Define Stitching Configuration Changes ==
     287
     288These are the consolidations to update AL2S NEWY, according to email from Eric Boyd of Internet2:
     289
     290{{{
     291 Old Hostname: sdn-sw.newy32aoa.net.internet2.edu
     292 New Hostname: rtsw.newy32aoa.net.internet2.edu
     293        'Old Interface'                       'New Interface'
     294 100GigabitEthernet1/1   100GE                   et-3/1/0.0
     295 100GigabitEthernet1/2   100GE                   et-3/3/0.0
     296 100GigabitEthernet3/1   100GE                   et-7/1/0.0
     297 100GigabitEthernet5/2   100GE                   et-7/2/0.0 (INCORRECT)
     298 100GigabitEthernet5/2   100GE                   et-7/3/0.0 (according to AJ Ragusa)
     299 100GigabitEthernet7/1   100GE                   et-4/1/0.0
     300 100GigabitEthernet7/2   100GE                   et-4/3/0.0
     301 10GigabitEthernet15/1   10GE                    xe-3/0/0.0
     302 10GigabitEthernet15/4   10GE                    xe-3/0/1.0
     303 10GigabitEthernet15/5   10GE                    xe-3/0/2.0
     304 10GigabitEthernet15/7   10GE                    xe-3/0/3.0
     305}}}
     306Hence, there are seven sites impacted by this URN transition. The table below highlights each of the transitions:
     307||'''Old URN                                             || ''' New URN ''' ||
     308|| sdn-sw.newy32aoa.net.internet2.edu:eth1/1:iminds      || rtsw.newy32aoa.net.internet2.edu:et-3/1/0.0:iminds ||
     309|| sdn-sw.newy32aoa.net.internet2.edu:eth5/2:gpo-og      || rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-og ||
     310|| sdn-sw.newy32aoa.net.internet2.edu:eth5/2:gpo-eg      || rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-eg ||
     311|| sdn-sw.newy32aoa.net.internet2.edu:eth5/2:gpo-ig      || rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-ig ||
     312|| sdn-sw.newy32aoa.net.internet2.edu:eth5/2:host-gpolab || rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:host-gpolab ||
     313|| sdn-sw.newy32aoa.net.internet2.edu:eth5/2:umass-eg    || rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:umass-eg ||
     314|| sdn-sw.newy32aoa.net.internet2.edu:eth7/2:nysernet-ig || rtsw.newy32aoa.net.internet2.edu:et-4/3/0.0:nysernet-ig ||
     315
     316
     317== 3. Request Stitching Changes from GENI Aggregate Operations Teams ==
     318
     319This URN transition will require co-ordination with the following teams:
     320  * InstaGENI: (geni-ops@googlegroups.com) Request will be handled by Hussam Nasir (nasir@netlab.uky.edu)
     321  * ExoGENI: (exogeni-ops@renci.org) Request will be handled by Mert Cevik (mcevik@renci.org) or Ilya Baldin (ilbadin@renci.org)
     322  * OpenGENI: Marshall Brinn (Mbrinn@bbn.com) and Regina Rosales-Hain (rrhain@bbn.com)
     323  * AL2S Aggregate and Production SCS: GMOC requests(gmoc@grnoc.iu.edu). Updates handled by Luke Fowler (luke@grnoc.iu.edu) or AJ Ragusa (aragusa@grnoc.iu.edu), cc: both on initial request.
     324  * Test SCS - Xi Yang (xyang@maxgigapop.net)
     325  * iMinds - Brecht Vermeulen (brecht.vermeulen@iminds.be>
     326
     327=== 3a. Define Change Request Details ===
     328
     329GPO IG and NYSERNet URNs Changes Request to InstaGENI Team:
     330{{{
     331Link ID:          urnpublicid:IDN+instageni.gpolab.bbn.com+interface+procurve2:5.24.al2s
     332Remote Link ID:   urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-ig
     333VLAN Range:       3596-3600,3706-3732,3746-3749
     334
     335Link ID:          urnpublicid:IDN+instageni.nysernet.org+interface+procurve2:1.19.al2s
     336Remote Link ID:   urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-4/3/0.0:nysernet-ig
     337VLAN Range:       1700-1719
     338}}}
     339
     340GPO EG URNs Change Request for ExoGENI Team:
     341{{{
     342Link ID:          urnpublicid:IDN+exogeni.net:bbnNet+interface+BbnNet:IBM:G8052:GigabitEthernet:1:2:ethernet
     343Remote Link ID:   urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-eg
     344VLAN Range:       3741,3736-3739
     345}}}
     346
     347GPO OG URNs Change Request for OpenGENI Team:
     348{{{
     349Link ID:          urnpublicid:IDN+bbn-cam-ctrl-1.gpolab.bbn.com+interface+force10:3:al2s
     350Remote Link ID:   urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-og
     351VLAN Range:       2611-2630
     352}}}
     353
     354Wall2 iMinds URN Change Request to Imind Team:
     355{{{
     356Link ID:          urnpublicid:IDN+wall2.ilabt.iminds.be+interface+c300b:0.12
     357Remote Link ID:   urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-3/1/0.0:iminds
     358VLAN Range:       1125-1164
     359}}}
     360
     361AL2S Aggregate URN Change Request for GMOC/GRNOC:
     362{{{
     363Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-3/1/0.0:iminds
     364Remote Link ID:   urnpublicid:IDN+wall2.ilabt.iminds.be+interface+c300b:0.12
     365VLAN Range:       1125-1164
     366
     367Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-og
     368Remote Link ID:   urnpublicid:IDN+bbn-cam-ctrl-1.gpolab.bbn.com+interface+force10:3:al2s
     369VLAN Range:       2611-2630
     370
     371Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-eg
     372Remote Link ID:   urnpublicid:IDN+exogeni.net:bbnNet+interface+BbnNet:IBM:G8052:GigabitEthernet:1:2:ethernet
     373VLAN Range:       3741,3736-3739
     374
     375Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-ig
     376Remote Link ID:   urnpublicid:IDN+instageni.gpolab.bbn.com+interface+procurve2:5.24.al2s
     377VLAN Range:       3596-3600,3706-3732,3746-3749
     378
     379Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-4/3/0.0:nysernet-ig
     380Remote Link ID:   urnpublicid:IDN+instageni.nysernet.org+interface+procurve2:1.19.al2s
     381VLAN Range:       1700-1719
     382
     383Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:host-gpolab
     384Remote Link ID:   urnpublicid:IDN+gpolab.bbn.com+interface+switch:port:al2s
     385VLAN Range:       2646
     386
     387Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:umass-eg
     388Remote Link ID:   urnpublicid:IDN+exogeni.net:umassNet+interface+umassNet:IBM:G8264:TenGigabitEthernet:1:1:ethernet
     389VLAN Range:       3581-3595
     390
     391}}}
     392
     393=== 3b. Make Requests for Aggregate Updates ===
     394
     395Send Email to each of the teams to request the above changes:
     396  - IG
     397  - EG
     398  - OG
     399  - iMinds
     400  - Internet2
     401
     402As a courtesy, copy the rack admin contact(s) or email list from the operators page on these requests.  They don't have to take any action, but they may want to know that their racks will be potentially unable to stitch for a period of time during the scheduled outage.
     403
     404Also copy kathryn.wong1@uky.edu, cody@uky.edu and caylin@uky.edu, With the exception of the ATLA consolidation, this work should not require any immediate action for monitoring, but the folks at UKY may want to note the "retired" URNs in their database, and to pay extra attention to their monitoring site during these transitions.
     405 
     406
     407''' ''Once the requested changes are completed, verify that the requested changes appear in the rack aggregate advertisement.''' ''
     408{{{
     409$ for i in gpo-ig gpo-og gpo-eg nysernet-ig al2s wall2 ; do stitcher listresources -a $i -o; done
     410}}}
     411
     412
     413You can now review all output files to verify that the correct URN is in place for each advertisement.
     414
     415==== InstaGENI Update Alternatives ====
     416
     417InstaGENI may be slow to respond, so you may do any of the following:
     418  1. Ask Hussam (nasir@netlab.uky.edu) to run the commands below on the boss node.
     419  2. Or contact the site admin and have them log into boss node and run these commands.
     420  3. You can create an admin account on the boss node (via the web UI for the site, e.g. http://instageni.gpolab.bbn.com/ for gpo-ig) and once it is approved, you can run the commands.
     421   
     422Below is an old example for the commands issued on the uwashington-ig boss node:
     423{{{
     424 mysql tbdb -e 'update external_networks set external_interface="urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.seat.net.internet2.edu:et-4/3/0.0:uwashington-ig" where network_id="al2s"'
     425
     426 mysql tbdb -e 'update external_networks set external_wire="urn:publicid:IDN+al2s.internet2.edu+link+rtsw.seat.net.internet2.edu:et-4/3/0.0:uwashington-ig" where network_id="al2s"'
     427
     428}}}
     429
     430''Note: Be aware of potential line wrapping pitfalls.''
     431   
     432
     433== 4. Request SCS Update ==
     434
     435In order for GENI Network Stitching to pick up these path configuration changes, an SCS Update must be run.  There are two SCS systems:
     436  - Test SCS maintained by Xi Yang (xyang@maxgigapop.net)
     437  - Production SCS mainted by the Internet2 (gmoc@grnoc.iu.edu). Updates handled by Luke Fowler (luke@grnoc.iu.edu) or AJ Ragusa (aragusa@grnoc.iu.edu).
     438
     439To find out which SCS knows about which aggregates, issue the following:
     440
     441For the Production SCS:
     442{{{
     443$ python ~/gcf/src/gcf/omnilib/stitch/scs.py --listaggregates --scs_url http://geni-scs.net.internet2.edu:8081/geni/xmlrpc >scs-prod
     444}}}
     445The above shows that the GPO IG, GPO EG, and NYSERnet IG sites are known to the Production SCS.
     446
     447For the Test SCS:
     448{{{
     449python gcf/gcf-current/src/gcf/omnilib/stitch/scs.py --listaggregates --scs_url http://nutshell.maxgigapop.net:8081/geni/xmlrpc > scs-test
     450}}}
     451The above shows that the GPO IG, GPO EG, GPO OG, NYSERnet IG, iMinds, and Umass site are known to the Production SCS.
     452
     453
     454Both Production and Test SCS are impacted by the updates. Send a request to:
     455 - the GMOC to the Production SCS
     456 - to Xi to update the Test SCS.
     457
     458
     459== 5. Validate Updated Stitching ==
     460
     461When the updates are completed for all Aggregates and for SCS servers, ask Luisa to conduct stitching tests.
     462
     463== 6. Update and close all tickets ==
     464
     465Assuming all tests are successful, update and close all tickets by emailing the GMOC.  If there are outstanding issues that are significant, leave the ticket open until they are resolved.  If there are smaller outstanding issues, close the maintenance tickets, and open new tickets with the appropriate owners to track and resolve, ideally before the next maintenance.
     466