1. Thoughts on TEIN2 Operation and Collaboration Xing Li <2005-08-23>

2. Outline  Background  Experience  TEIN2 NOC  Challenges  Remarks

3. Background

7. Dear All Following careful evaluation of the TEIN2 NOC Services tender offers, DANTE is pleased to announce that it has accepted in principle Tsinghua University's offer to provide the TEIN2 NOC service. A contractual agreement is now being drawn up between DANTE and Tsinghua University for providing the service, based in Hong Kong, for the duration of the TEIN2 project, to end December 2007. As well as directly managing the planned TEIN2 PoPs in Beijing, Hong Kong and Singapore, Tsinghua University will establish a close operational relationship with APAN- JP and the Japanese networks providing the Tokyo TEIN2 PoP, and also with other partners or third parties providing capacity available for use by the TEIN2 project. While there is much work still to do to finalise the contract and develop the NOC service, this announcement marks an important step towards establishing the TEIN2 network. Regards David West 20050815

8. Experience

9. NOC

10. CERNET/CERNET2/DRAGONTAP CERNET JANET STARLIGHT HARNET TANET DRAGONLIGHT CNGI-BJIX DRAGONTAP CERNET 2 Internet Domestic Peering CNGI Peering APAN KOREN 1.4G 10G 155M 100M 1G 155M 45M 10G

11. TEIN2 NOC

12.  Connectivity management implementation implementation incident and problem management incident and problem management  IP management Pro-active and reactive monitoring Pro-active and reactive monitoring Problem management Problem management  Inventory Control Hardware, software and configuration Hardware, software and configuration  Provide online information trouble ticket and statistics trouble ticket and statistics  Collaboration with other NOCs APAN-JP,... APAN-JP,...

13. Procedures  Configuration  Performance monitoring  Problem handling  Security  Online access of the operation information

14. Fault Management Procedure  Problem alert  Tracking  Problem identification and isolation  Trouble ticket assignment and engineer contact  Trouble shooting  Problem notification initial status report initial status report identification identification updates updates closure closure

15. IP Monitoring Procedure  Pro-active monitoring link statistics link statistics packet statistics packet statistics routing statistics routing statistics loss and delay statistics loss and delay statistics network equipment statistics network equipment statistics advanced application monitoring advanced application monitoring  Reactive monitoring taking fault reports around the clock taking fault reports around the clock

16. Advanced Management  IPv6 fault monitoring fault monitoring traffic and performance monitoring traffic and performance monitoring  IP Multicast multicast beacon multicast beacon traffic monitoring traffic monitoring  VPN management Ethernet over MPLS management Ethernet over MPLS management  QoS CoS statistics CoS statistics flow ranking flow ranking  Security IDS IDS host flaw scanner and the database host flaw scanner and the database

17. Challenges

18. Challenges  Connectivity problem management  BGP policy  Open access of the NOC information  Shared trouble system  Security  Level 2 services  Advanced services

19. Possible Paths policy based routing and politics based routing

20. The Real World Routing

21. Meet requirement by user AS network  Policy Under the framework of TEIN2 Under the framework of TEIN2  Database IRR (who) IRR (who)  Configuration AS-path prepend AS-path prepend Predefined community Predefined community  Fine tune Traffic and flow monitoring Traffic and flow monitoring End-to-end performance tools End-to-end performance tools AS AAS BAS C AS D

22. BGP Routing  Under the framework of TEIN2 Try to provide the BGP routing as more flexible as possible to the connected networks Try to provide the BGP routing as more flexible as possible to the connected networks Provide the online access to the routing, traffic and flow information Provide the online access to the routing, traffic and flow information

23. BGP Implementation (draft)   Implement BOGON filters   Implement prefix length filtering   Implement authenticated BGP sessions   Implement maximum prefixes   Implement route dampening   Implement route filtering (prefix-list or access-list or/and filter-list)   Accept community tag   Accept MED   Accept aggregated prefixes, except for the policy based routing

24. Open Access of the NOC Information  Access policy Under the framework of TEIN2 Under the framework of TEIN2  Tools and user interface Open software tools Open software tools APAN NOCAPAN NOC Abilene ObservatoryAbilene Observatory etc.etc. In-house developed tools In-house developed tools status/performance/routing/traffic/flow/equipmentstatus/performance/routing/traffic/flow/equipment

25. Status

26. Performance

27. Routing

28. Traffic

29. Flow

30. Equipment

31. Trouble Ticket System

32. Remarks

33. Remarks  Under the framework of the TEIN2, we welcome suggestions and comments for the TEIN2 NOC operation SLA SLA BGP routing BGP routing Monitoring and measurement Monitoring and measurement

34. Thoughts  Global Academic NOC meeting NANOG, APRICOT, RIPE NANOG, APRICOT, RIPE  Video phone no time zone problem no time zone problem  Shared trouble ticket system trouble shooting trouble shooting  Shared end-to-end measurement data optimize routing optimize routing