Changes between Version 32 and Version 33 of SiteNlr


Ignore:
Timestamp:
07/07/10 18:13:48 (9 years ago)
Author:
jwilliams@bbn.com
Comment:

clarified Shared FrameNet endpoints requir provisioning via Region IT staff on behalf of a campus.

Legend:

Unmodified
Added
Removed
Modified
  • SiteNlr

    v32 v33  
    6060This section outlines provisioning within Sherpa. For the complete procedure of provisioning a VLAN between two sites see ConnectivityGuidelines.
    6161
    62 Once you have an Sherpa account you will be able to provision VLANs between site's endpoints using the [https://sherpa.nlr.net/add/a_end.html  !FrameNet VLAN provisioning webpage].
     62It is important to work with your Campus and Regional Netowrk (as well as your partner Campus and regional network) to negotiate a common VLAN ID.
     63
     64=== in sherpa ===
     65 '''If your campus has their own dedicated NLR !FrameNet port'''::
     66 You can directly ask NLR for Sherpa access to provision VLANs on that port. 
     67 '''If the campus connects through a regional and a shared !FrameNet port'''::
     68 It would be up to the regional whether the regional chooses to grant access to the campus to do Sherpa provisioning on the FN port.
     69
     70Once you (or your IT contact at your regional) have an Sherpa account you will be able to provision VLANs between site's endpoints using the [https://sherpa.nlr.net/add/a_end.html  !FrameNet VLAN provisioning webpage].
    6371
    6472There only needs to be one organization with Sherpa access with permission to provision VLANs on both endpoints.