1. 1 AUGERnet definition and implementation René Bilhaut LAL-IN2P3 bilhaut@lal.in2p3.fr

2. 2 The global network infrastructure and network administration providing means of communication to the different on- site operational components : - Acquisition and detection sub-systems (FD, SD, CDAS) - CAMPUS facilities and external connection - On site voice-com facilities (VoIP ?) - Daily operations and maintenance routines What is AUGERnet ? Malargüe, April 2000 René Bilhaut LAL

3. 3 We should follow these simple rules due to the constraints of the experiment (long time scale, minimal attendance) - modular architecture (independence between components) - standard solutions (“off the shelf products”) - open implementation (possibility to integrate new technology) How to do ? Malargüe, April 2000 René Bilhaut LAL

4. 4 AUGERnet FD Ethernet 16*2Mbs R R R 2Mbs SD Ethernet LSX BSU LS Pm Fd Internet R High Speed Switch CDAS cluster Campus Ethernet gateway Non-IP traffic Non-Routable IP traffic Routable IP traffic Malargüe, April 2000 René Bilhaut LAL Private IP CLASS B 192.168.x.x official IP CLASS C Internet

5. 5 Some recommendations and initial coordination Malargüe, April 2000 René Bilhaut LAL

6. 6 passive infrastructure – within buildings --> foiled twisted pairs CAT5 (Fast Ethernet compliant) – between buildings --> fiber optic (electrical isolation) – patch panels and RJ45 plugs (common for computing and telephone connections) active infrastructure – Backbone based on a central High Speed SWITCH federating the different sub-systems (SD, FD …) and CAMPUS – In specific Ethernet segments (FD, SD, CAMPUS) SWICTH instead of HUB – Management via SNMP Agent Network infrastructure components Malargüe, April 2000 René Bilhaut LAL

7. 7 Network administration components Basic technical coordination – definition of the IP environment – naming schemes and addressing schemes – IP routing and generic IP services (DNS, Mail, NFS, accounting …) – security policy (on the site, and with the rest of the Universe) Needs to coordinate “IP administrators” – one correspondent for each sub-system to set up a working group SD ( René Bilhaut) CDAS (Xavier Bertou) FD ( Nobert Kunka ?) Campus (Noberto Fazzini ?) Malargüe, April 2000 René Bilhaut LAL

8. 8 Some technical ideas on the final configuration Malargüe, April 2000 René Bilhaut LAL

9. 9 Define for each Ethernet segment a pseudo IP CLASS C 192.168.x.x TOWER 1 192.168.1x.x FD Ethernet 192.168.11.x SD Ethernet 192.168.12.x SD Ethernet 192.168.13.x TOWER 2 192.168.2x.x FD Ethernet 192.168.21.x SD Ethernet 192.168.22.x... IP Addressing Scheme 1 2 3 4 Malargüe, April 2000 René Bilhaut LAL

10. 10 IP Addressing Scheme Malargüe, April 2000 René Bilhaut LAL R Cisco Router 1600 Ethernet FD Ethernet SD Tower 4 Tower 3 Tower 1 192.168.22.x 192.168.21.x 192.168.12.x 192.168.31.x 192.168.11.x 192.168.32.x 192.168.42.x 192.168.41.x 192.168.100.x 192.168.1.x Cisco 7200 CDAS Internet Campus interconnection subnet Official class C R gateway Tower 2 R R R R R R R

11. 11 IP Naming Scheme Malargüe, April 2000 René Bilhaut LAL Private local domain name one level (xxx.augernet ) or two level yyy.xxx.augernet ex: sd1xxx.augernet xxx.sd.augernet, fd1xxx.augernet xxx.fd.augernet, xxx-fd2.augernet xxx.cdas.augernet ? Internet official name (campus) xxx.auger.ar xxx.auger.edu.ar ?