Changes between Version 1 and Version 2 of URNConsolidation


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

--

Legend:

Unmodified
Added
Removed
Modified

  • URNConsolidation

    v1 v2  
    4242}}}
    4343
    44 From 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 
    46 Note: 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 
    52 This 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 
    54 The 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 
    58 Make 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 
    60 Note 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 
    62 Internet2 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 
    64 If 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 
    66 If 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 
    70 The aggregate advertisement includes a ''stitching'' section which defines how VLANs are to be connected and which VLANs are associated with that stitching endpoint.
    71 
    72 Get the AL2S advertisement:
    73 {{{
    74    omni -a al2s listresources -o
    75 }}}
    76 Review 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 }}}
    90 Note, from the above we will only request the "<stitch:link id" transition, the "<stitch:port id" transitions are implicit.
    91 
    92 NB. 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.
     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, 1 network aggregate(iMinds) and 1 fixed endpoint (host-gpolab). 
     45
     46In Stitching a fixed endpoint is a resource that is not a GENI aggregate but still supports stitching.  Fixed endpoint and are statically configured in the SCS servers to capture stitching information and are generally set up for specific demonstrations.
     47
    9648
    9749== 2. Define Stitching Configuration Changes ==
    9850
    99 These are the consolidations to update AL2S NEWY, according to email from Eric Boyd of Internet2:
     51Review announced changes to define expected changed. Using details from the consolidation email from Eric Boyd of Internet2 for the New York Switch:
    10052
    10153{{{
    … …  
    10658 100GigabitEthernet1/2   100GE                   et-3/3/0.0
    10759 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)
     60 100GigabitEthernet5/2   100GE                   et-7/3/0.0
    11061 100GigabitEthernet7/1   100GE                   et-4/1/0.0
    11162 100GigabitEthernet7/2   100GE                   et-4/3/0.0
    … …  
    11566 10GigabitEthernet15/7   10GE                    xe-3/0/3.0
    11667}}}
    117 Hence, there are seven sites impacted by this URN transition. The table below highlights each of the transitions:
     68From the check of the AL2S stitching Advertisement, we know that there are seven stitching sites impacted by this URN transition. Define a list of each of the exacted changes. The table below highlights each of the transitions:
    11869||'''Old URN                                             || ''' New URN ''' ||
    11970|| sdn-sw.newy32aoa.net.internet2.edu:eth1/1:iminds      || rtsw.newy32aoa.net.internet2.edu:et-3/1/0.0:iminds ||
    … …  
    12879== 3. Request Stitching Changes from GENI Aggregate Operations Teams ==
    12980
    130 This 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)
     81URN transition require co-ordination with the appropriate team. Following are the teams/contributors that handle the transition:
     82  * InstaGENI: (geni-ops@googlegroups.com) Request is handled by Hussam Nasir (nasir@netlab.uky.edu)
     83  * ExoGENI: (exogeni-ops@renci.org) Request is handled by Mert Cevik (mcevik@renci.org) or Ilya Baldin (ilbadin@renci.org)
    13384  * OpenGENI: Marshall Brinn (Mbrinn@bbn.com) and Regina Rosales-Hain (rrhain@bbn.com)
    13485  * 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.
    13586  * Test SCS - Xi Yang (xyang@maxgigapop.net)
    13687  * iMinds - Brecht Vermeulen (brecht.vermeulen@iminds.be>
     88  * host-gpolab - was configured by Ali and he updates the local definitions.
    13789
    13890=== 3a. Define Change Request Details ===
    139 
    140 GPO IG and NYSERNet URNs Changes Request to InstaGENI Team:
     91Based on the existing Stitching information and the announced changes, generate a list of new link ids to be used at each site.
     92 
     93Following is an example from the New York transition, where GPO IG and NYSERNet URNs changes were request to InstaGENI Team:
    14194{{{
    14295Link ID:          urnpublicid:IDN+instageni.gpolab.bbn.com+interface+procurve2:5.24.al2s
    … …  
    149102}}}
    150103
    151 GPO EG URNs Change Request for ExoGENI Team:
     104GPO EG URNs change were request for ExoGENI Team:
    152105{{{
    153106Link ID:          urnpublicid:IDN+exogeni.net:bbnNet+interface+BbnNet:IBM:G8052:GigabitEthernet:1:2:ethernet
    … …  
    156109}}}
    157110
    158 GPO OG URNs Change Request for OpenGENI Team:
     111GPO OG URNs change request for OpenGENI Team:
    159112{{{
    160113Link ID:          urnpublicid:IDN+bbn-cam-ctrl-1.gpolab.bbn.com+interface+force10:3:al2s
    … …  
    163116}}}
    164117
    165 Wall2 iMinds URN Change Request to Imind Team:
     118Wall2 iMinds URN changes were request to Imind Team:
    166119{{{
    167120Link ID:          urnpublicid:IDN+wall2.ilabt.iminds.be+interface+c300b:0.12
    … …  
    170123}}}
    171124
    172 AL2S Aggregate URN Change Request for GMOC/GRNOC:
     125AL2S Aggregate URN Change Request for GMOC:
    173126{{{
    174127Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-3/1/0.0:iminds
    … …  
    211164  - Internet2
    212165
    213 As 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 
    215 Also 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.
     166As a courtesy, copy the rack admin contact(s) or email list from the [http://groups.geni.net/geni/wiki/GENIRacksHome/Operators 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.
     167
     168Also copy the GENI Monitoring team (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.
    216169 
    217170
    … …  
    224177You can now review all output files to verify that the correct URN is in place for each advertisement.
    225178
    226 ==== InstaGENI Update Alternatives ====
    227 
    228 InstaGENI 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.
     179==== InstaGENI Update Details ====
     180
     181InstaGENI updates follow the following approach:
     182
     183  1. Ask geni-ops@googlgroups.com, which maps to Hussam (nasir@netlab.uky.edu) running the commands below on the rack boss node.
     184  2. Or, a site contact may asked to log into boss node and run these commands.
     185  3. Or, 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.
    232186   
    233 Below is an old example for the commands issued on the uwashington-ig boss node:
     187''Note: Options 2 and 3 are not likely to happen, as option 1 has always taken place as expected. '' 
     188
     189The InstaGENI changes that will made to the external network definition for AL2S will be used for the stitching configuration. Below is an old example of the commands used to modify the URN for the uwashington-ig external network.  These commands are executed on the InstaGENI '' '''boss''' '' node:
    234190{{{
    235191 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"'
    236192
    237193 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 
    239194}}}
    240195
    … …  
    248203  - 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).
    249204
    250 To find out which SCS knows about which aggregates, issue the following:
     205The Production and Test SCS include stitching information for different sets of aggregates, to find out which SCS knows about which aggregates, issue the following:
    251206
    252207For the Production SCS:
    … …  
    260215python gcf/gcf-current/src/gcf/omnilib/stitch/scs.py --listaggregates --scs_url http://nutshell.maxgigapop.net:8081/geni/xmlrpc > scs-test
    261216}}}
    262 The above shows that the GPO IG, GPO EG, GPO OG, NYSERnet IG, iMinds, and Umass site are known to the Production SCS.
    263 
    264 
    265 Both Production and Test SCS are impacted by the updates. Send a request to:
     217The listaggregates function shows that sites from the example New York update are GPO IG, GPO EG, GPO OG, NYSERnet IG, iMinds, and Umass. Both Production and Test SCS are impacted by the example New York update. Send a request to:
    266218 - the GMOC to the Production SCS
    267219 - to Xi to update the Test SCS.
    … …  
    270222== 5. Validate Updated Stitching ==
    271223
    272 When the updates are completed for all Aggregates and for SCS servers, ask Luisa to conduct stitching tests.
     224When the updates are completed for all Aggregates and for the SCS servers, testing takes place to verify the URN changes. Validation includes:
     225
     226 a. Verify Advertisement for AL2s and utah-stitch aggregate. If the new URN is missing from the '' '''stitching''' '' section, contact the appropriate aggregate team. [[BR]]
     227 b. Create stitched slivers with the production SCS that uses the utah-stitch network aggregate by selecting a University of Utah endpoint and any other remote GENI site that supports stitching (ex. utahddc-ig to nysernet-ig; pg-utah to nps-ig)(RSpecs are attached for this step).  Login in to one node for each sliver and leave some ping traffic running.  _DO NOT_ delete these slivers used later in monitoring verification. If Production SCS reports unknown path contact Luke about updating production SCS. [[BR]]
     228 c. Create stitched slivers with the test SCS, which can be done by using the omni/stitcher option '' "--scsURL https://nutshell.maxgigapop.net:8443/geni/xmlrpc" '' . Create a stitched sliver that uses any University of Utah site endpoint and any other remote GENI site that supports stitching (ex. utahddc-ig to gatech-ig)(Rspecs are attached for this step). Login in to one node for each sliver and leave some ping traffic running.  _DO NOT_ delete these slivers used later in monitoring verification. If Test SCS reports unknown path contact Xi about updating Test SCS. [[BR]]
     229 d. Update the GENI aggregate page for utah-stitch (http://groups.geni.net/geni/wiki/GeniAggregate/UtahStitch) to capture the new stitching ''' ''link'' ''' details. [[BR]]
     230 e. Normally the operator page should be reviewed to replace any instances of URN, but there is no such information for the utah-stitch operator page (http://groups.geni.net/geni/wiki/GENIRacksHome/InstageniRacks/Operators/UtahStitch).[[BR]]
     231 f. Update http://groups.geni.net/geni/wiki/GeniNetworkStitchingSites#GENIStitchingAL2SPathMappings to replace: [[BR]] 
     232   
     233    ||''' Router'''           ||''' Interface''' ||''' Site ''' ||''' VLAN Range''' ||
     234    ||salt.net.internet2.edu  || eth7/1          || utah-stitch || 2100-3499        ||
     235
     236    With the new switch details:
     237 
     238    ||''' Router'''           ||''' Interface''' ||''' Site ''' ||''' VLAN Range''' ||
     239    ||salt.net.internet2.edu  || et-4/3/0        || utah-stitch || 2100-3499      ||[[BR]]
     240 
     241 g. GENI Monitoring URN Validation. Login into https://genimondev.uky.edu and use the '' '''search''' '' feature to find all data relating to the new AL2S switch "rtsw.salt.net.internet2.edu" and make sure the following are returned:
     242  * a switch is listed with the new name "rtsw.salt.net.internet2.edu",
     243  * interface statistics are available for the new switch
     244  * VLAN are being reported for the new switch[[BR]]     
     245 h. Report back about test finding or any outstanding/unresolved issues.
     246
    273247
    274248== 6. Update and close all tickets ==
    … …  
    276250Assuming 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.
    277251
    278 
    279 
    280 
    281 Note:  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 
    288 These 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 }}}
    306 Hence, 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 
    319 This 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 
    329 GPO IG and NYSERNet URNs Changes Request to InstaGENI Team:
    330 {{{
    331 Link ID:          urnpublicid:IDN+instageni.gpolab.bbn.com+interface+procurve2:5.24.al2s
    332 Remote Link ID:   urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-ig
    333 VLAN Range:       3596-3600,3706-3732,3746-3749
    334 
    335 Link ID:          urnpublicid:IDN+instageni.nysernet.org+interface+procurve2:1.19.al2s
    336 Remote Link ID:   urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-4/3/0.0:nysernet-ig
    337 VLAN Range:       1700-1719
    338 }}}
    339 
    340 GPO EG URNs Change Request for ExoGENI Team:
    341 {{{
    342 Link ID:          urnpublicid:IDN+exogeni.net:bbnNet+interface+BbnNet:IBM:G8052:GigabitEthernet:1:2:ethernet
    343 Remote Link ID:   urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-eg
    344 VLAN Range:       3741,3736-3739
    345 }}}
    346 
    347 GPO OG URNs Change Request for OpenGENI Team:
    348 {{{
    349 Link ID:          urnpublicid:IDN+bbn-cam-ctrl-1.gpolab.bbn.com+interface+force10:3:al2s
    350 Remote Link ID:   urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-og
    351 VLAN Range:       2611-2630
    352 }}}
    353 
    354 Wall2 iMinds URN Change Request to Imind Team:
    355 {{{
    356 Link ID:          urnpublicid:IDN+wall2.ilabt.iminds.be+interface+c300b:0.12
    357 Remote Link ID:   urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-3/1/0.0:iminds
    358 VLAN Range:       1125-1164
    359 }}}
    360 
    361 AL2S Aggregate URN Change Request for GMOC/GRNOC:
    362 {{{
    363 Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-3/1/0.0:iminds
    364 Remote Link ID:   urnpublicid:IDN+wall2.ilabt.iminds.be+interface+c300b:0.12
    365 VLAN Range:       1125-1164
    366 
    367 Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-og
    368 Remote Link ID:   urnpublicid:IDN+bbn-cam-ctrl-1.gpolab.bbn.com+interface+force10:3:al2s
    369 VLAN Range:       2611-2630
    370 
    371 Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-eg
    372 Remote Link ID:   urnpublicid:IDN+exogeni.net:bbnNet+interface+BbnNet:IBM:G8052:GigabitEthernet:1:2:ethernet
    373 VLAN Range:       3741,3736-3739
    374 
    375 Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:gpo-ig
    376 Remote Link ID:   urnpublicid:IDN+instageni.gpolab.bbn.com+interface+procurve2:5.24.al2s
    377 VLAN Range:       3596-3600,3706-3732,3746-3749
    378 
    379 Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-4/3/0.0:nysernet-ig
    380 Remote Link ID:   urnpublicid:IDN+instageni.nysernet.org+interface+procurve2:1.19.al2s
    381 VLAN Range:       1700-1719
    382 
    383 Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:host-gpolab
    384 Remote Link ID:   urnpublicid:IDN+gpolab.bbn.com+interface+switch:port:al2s
    385 VLAN Range:       2646
    386 
    387 Link ID:          urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.newy32aoa.net.internet2.edu:et-7/3/0.0:umass-eg
    388 Remote Link ID:   urnpublicid:IDN+exogeni.net:umassNet+interface+umassNet:IBM:G8264:TenGigabitEthernet:1:1:ethernet
    389 VLAN Range:       3581-3595
    390 
    391 }}}
    392 
    393 === 3b. Make Requests for Aggregate Updates ===
    394 
    395 Send Email to each of the teams to request the above changes:
    396   - IG
    397   - EG
    398   - OG
    399   - iMinds
    400   - Internet2
    401 
    402 As 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 
    404 Also 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 
    413 You can now review all output files to verify that the correct URN is in place for each advertisement.
    414 
    415 ==== InstaGENI Update Alternatives ====
    416 
    417 InstaGENI 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    
    422 Below 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 
    435 In 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 
    439 To find out which SCS knows about which aggregates, issue the following:
    440 
    441 For 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 }}}
    445 The above shows that the GPO IG, GPO EG, and NYSERnet IG sites are known to the Production SCS.
    446 
    447 For the Test SCS:
    448 {{{
    449 python gcf/gcf-current/src/gcf/omnilib/stitch/scs.py --listaggregates --scs_url http://nutshell.maxgigapop.net:8081/geni/xmlrpc > scs-test
    450 }}}
    451 The above shows that the GPO IG, GPO EG, GPO OG, NYSERnet IG, iMinds, and Umass site are known to the Production SCS.
    452 
    453 
    454 Both 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 
    461 When 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 
    465 Assuming 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