Changes between Version 33 and Version 34 of SiteNlr
- Timestamp:
- 07/07/10 18:17:24 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SiteNlr
v33 v34 56 56 The process for requesting Sherpa access right now is fairly informal. Currently there are no rules/regulations/procedures outlined for requestingSsherpa access. For now send a request to the globalnoc [mailto:noc@nlr.net <noc@nlr.net>]. 57 57 58 '''If your campus has their own dedicated NLR !FrameNet port''':: 59 You can directly ask NLR for Sherpa access to provision VLANs on that port. 60 '''If the campus connects through a regional and a shared !FrameNet port''':: 61 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. You may need to request your Regional IT staff to provision !FrameNet VLANs on your behalf. 58 62 59 == VLAN Provisioning Within !FrameNet ==63 == VLAN Provisioning Within !FrameNet using Sherpa == 60 64 This section outlines provisioning within Sherpa. For the complete procedure of provisioning a VLAN between two sites see ConnectivityGuidelines. 61 65 62 66 It 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 67 70 68 Once 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].