IGTMD réunion du 4 Mai 2007 CC IN2P3 Lyon

Présentation au sujet: "IGTMD réunion du 4 Mai 2007 CC IN2P3 Lyon"— Transcription de la présentation:

1 IGTMD réunion du 4 Mai 2007 CC IN2P3 Lyon

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

4 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)

5 Usage du circuit

6 Monitoring http://lhcopnmon1.fnal.gov:9090/FERMI-E2E/G2_E2E_index.html
X={1,2}

7 TTs T15:35:01.0-6:00 BGP status for Neighbor: IP= T15:35:01.0-6:00 BGP status for Neighbor: IP=

8 E2E circuits Debriefing...

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

10 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 ? Utiliser les bons N° de VLAN Adresses privées dans le VLAN (par commodité pour tester les segmenst de la liaison)

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

12 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

13 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 + ... Plusieurs mails par jour ! Installation de PerfSonar sur tous les sites + développement spécifique …

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

15 And what for ? Customers do IP at the edge and have a BGP peering !
Laisser le routage en place plutot que de chercher à ignorer le niveau physique IGTMD : pas d’IGP (BGP entre Lyon et Fermi)

16 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 ?

17