1 / 17

IGTMD réunion du 4 Mai 2007 CC IN2P3 Lyon

IGTMD réunion du 4 Mai 2007 CC IN2P3 Lyon. Bernard.Tuy@renater.fr. Contribution de RENATER. Mise en place du lien CC IN2P3, Lyon - Fermi Lab, Chicago Mise en place outils de supervision Gestion des erreurs et des TTs. Etat du circuit IN2P3 - FNAL. Pbs entre Géant et HOPI ?

carolyngrant
Télécharger la présentation

IGTMD réunion du 4 Mai 2007 CC IN2P3 Lyon

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IGTMDréunion du 4 Mai 2007CC IN2P3 Lyon Bernard.Tuy@renater.fr

  2. Contribution de RENATER • Mise en place du lien • CC IN2P3, Lyon - Fermi Lab, Chicago • Mise en place outils de supervision • Gestion des erreurs et des TTs

  3. Etat du circuit IN2P3 - FNAL • Pbs entre Géant et HOPI ? • 2 liens migrés sur le Paris - NY • Retour manuel sur Paris - Londres en cas de besoin • Pbs de nommage des interfaces ? • Plusieurs TTs par jour … • Statistiques • Cf graphes (débit 2 VLANs agrégés)

  4. Usage du circuit

  5. Monitoring • http://lhcopnmon1.fnal.gov:9090/FERMI-E2E/G2_E2E_index.html • http://lhcopnmon1.fnal.gov:9090/FERMI-E2E/G2_E2E_view_domain_IN2P3.html • http://lhcopnmon1.fnal.gov:9090/FERMI-E2E/G2_E2E_view_e2elink_FERMI-IN2P3-IGTMD-00X.html • X={1,2}

  6. TTs • 2007-04-25T15:35:01.0-6:00 BGP status for Neighbor: IP=198.151.133.153 • 2007-04-25T15:35:01.0-6:00 BGP status for Neighbor: IP=198.151.133.157

  7. E2E circuitsDebriefing... jerome.durand@renater.fr

  8. Building e2e circuits • This is complex • Synchronization required • Service offered has strong impact on network architecture • Monitoring not straightforward • What for ? • Provide more bandwidth ? • Provide 100% private circuit ?

  9. About setup • Several months needed • Hours of conf calls • Agreement required all over the path • VLAN IDs ... • Private addresses usage • Will we do better next time ?

  10. Provide more bandwidth ? • True for 10GE circuits • What about 1GE ? • We can set up 1 Gbps IP traffic much more easily

  11. Provide 100% private circuit ? • We have Ethernet switches on these circuits • Equipment handles other traffic too • No prioritization used (in Renater so far) • Some use EoMPLS • Some others have IP over MPLS  • And this differs in all parts of the circuit

  12. What about monitoring...and day to day operation • Very complex! • Difficult to find where the problem comes from • We had to configure private addresses on equipment on the path! • Good this was multipoint circuit  • Privacy issue ? • perfSONAR  + E2ECU + ...

  13. And about resiliency ? • Almost no resiliency available • And outages are often very long to manage • Up to 3 days !

  14. And what for ? • Customers do IP at the edge and have a BGP peering !

  15. Requirements to establish E2E circuits • Define end to end locations • Circuit type to be validated and decided by the NREN • VLAN &/or EoMPLS • PIP E2E • Lambda E2E • L3 VPN • Define services and apps which flow through the circuit • IPv4, IPv6, Unicast, Multicast … • MTU requirements • Specify IP address plans (private or not) • Define BW and SLA requirements for the E2E circuit • Jitter, OWD, BW, … • Who pays what ?

More Related