1. Update on GÉANT BoD/AutoBAHN LHCONE Workshop: Networking for WLCG - CERN Tangui Coulouarn, DeIC 11 February 2013

2. 2 Connect | Communicate | Collaborate AutoBAHN and the GÉANT BoD Service AutoBAHN is a provisioning system used in the GÉANT BoD Service Some NRENs co-offering the GÉANT BoD service use other provisioning systems The software provisioning circuits is one component of the service along with: Monitoring Multi-domain technical support Procedures AAI Cost-sharing and billing User outreach and support, etc.

3. 3 Connect | Communicate | Collaborate Agenda Update on AutoBAHN Update on the GÉANT BoD Service

4. 4 Connect | Communicate | Collaborate AutoBAHN basics AutoBAHN allocate network bandwidth to users/applications both immediately and in advance. 3 modules in AutoBAHN: InterDomain Manager (IDM), Domain Manager (DM) and Technology Proxy (TP) Supported networking equipment: – Equipment working under Bluenet Tool/Ans Tool (Cisco routers supporting AToM - 760x, 3750, 3500) – Brocade (Foundry) Network NetIron 8000 (EoMPLS) – Juniper MX80, EX4200 (Eth, EoMPLS) – Equipment working with Junos Space (currently used with Juniper Networks MX Series 3D Universal Routers) – Alcatel MCC 1678 (SDH) – Intune Networks Verisma iVX8000 (OPST - Optical Packet Switched Transport) – DLink 3450 (Eth)

5. 5 Connect | Communicate | Collaborate NSI v2.0 compliance AutoBAHN, apart from its native protocol, can also handle other BoD protocols. IDM in AutoBAHN was IDCP compliant and we had a translator to NSI v1.0 IDM rewritten so AutoBAHN 3.0 natively supports NSI v2.0 (r117) and no longer supports IDCP Release date of AutoBAHN 3.0 planned for 17 March 2014 Alpha2 was released yesterday Beta 17 February Early testing with different NRENs Only IDM module modified (not DM and TP)

6. 6 Connect | Communicate | Collaborate Access to AutoBAHN Web GUI API User Access Point (UAP) interface which allows sending of requests, the retrieval of available ports, the retrieval of reservations status, etc. WebGUI uses this method to communicate with IDMs Administration interface has methods for retrieving logs, services/reservations lists, configuration properties and intradomain topology information. So Administration is needed in addition to UAP for more advanced Client Platforms (for example the BoD Portal uses both interfaces) NSI CS v2.0 interface IDMs communicate via this interface as may other clients/apps

7. 7 Connect | Communicate | Collaborate API Access

8. 8 Connect | Communicate | Collaborate API Access with NSI v2

9. 9 Connect | Communicate | Collaborate JIRA to follow development process:https://issues.geant.net/jira/browse/ABAHNhttps://issues.geant.net/jira/browse/ABAHN FORGE for technical documentation:https://forge.geant.net/forge/display/autobahn/Homehttps://forge.geant.net/forge/display/autobahn/Home

10. 10 Connect | Communicate | Collaborate Update on GÉANT BoD Service Essential elements in scope for this presentation Footprint Monitoring Procedures, trouble-shooting Essential elements but not in scope for this presentation Cost-sharing AAI User outreach

11. 11 Connect | Communicate | Collaborate Footprint ESNet/Internet2 Peering up since August 2013 Need to work on procedures for trouble shooting NSI opens perspectives as shown by AutoGOLE/GLIF demos ProductionTestingWaiting for NSI2.0Static links from GÉANT PoP to end-points CARnet DeIC FUNET HEAnet GRnet PIONIER JANET DFN NORDUnet SURFnet BELNET GARR CESNET

12. 12 Connect | Communicate | Collaborate Monitoring Control plane solutions already working (NagiosPython SOAP client plugin, Nagios Service Check Acceptor (NSCA), Nagios Remote Plugin Executor (NRPE), Icinga) cMON developed as an extension of PerfSONAR to monitor circuits cMON works already for static circuitsFor dynamic circuits, it is currently being piloted by HEAnet, GRnet and GÉANT SNMP traps or polling sent by cMON agents to HQ Communication between cMON and AutoBAHN

13. 13 Connect | Communicate | Collaborate cMON D Pilot

14. 14 Connect | Communicate | Collaborate Procedures and trouble-shooting Provisioning of circuits within the framework of the service Multi-domain Service Desk for troubleshooting and procedures to follow Still very much ad hoc solutions with other services: need to progress

15. 15 Connect | Communicate | Collaborate www.geant.net www.twitter.com/GEANTnews | www.facebook.com/GEANTnetwork | www.youtube.com/GEANTtv Connect | Communicate | Collaborate Thank you!