1. FS/ILG House Managers IAP 2005 Oliver Thomas Information Services & Technology IAP 2005 Oliver Thomas Information Services & Technology

2. Agenda Networking (Data) General network architecture Problem reporting and escalation chain Useful e-mail addresses and contacts Upcoming bandwidth upgrades Demise of Service Level Agreements  Telephones Networking (Data) General network architecture Problem reporting and escalation chain Useful e-mail addresses and contacts Upcoming bandwidth upgrades Demise of Service Level Agreements  Telephones

3. General Network Architecture  On-campus ILG’s and ILG’s on Mass Ave have (MIT) fiber to the building  Off-campus ILG’s currently have Verizon T1’s from one of MIT’s routers to the ILG  Bandwidth is 1.54 M-bits/sec  Planned upgrades  Line conditioner, router  On-campus ILG’s and ILG’s on Mass Ave have (MIT) fiber to the building  Off-campus ILG’s currently have Verizon T1’s from one of MIT’s routers to the ILG  Bandwidth is 1.54 M-bits/sec  Planned upgrades  Line conditioner, router

4. Cisco Router (2000 series)

5. MITnet Map (Overview)

6. MITnet Map (Detail)

7. Network Internal to House

8. Hubs, Switches and Routers  Each ILG has a large address space (don’t use back-end networks)  Home routers generally don’t work well in this context (look for “bridging mode” in documentation)  Want access points, switches, or hubs to extend networks  Each ILG has a large address space (don’t use back-end networks)  Home routers generally don’t work well in this context (look for “bridging mode” in documentation)  Want access points, switches, or hubs to extend networks

9. General Service Model  MIT maintains the entry equipment  Verizon maintains the T1’s  ILG’s maintain everything inside the entry router  Most MITnet services are available inside ILG subnets  DHCP registration service  Moira host database  Security scans and notifications  MIT maintains the entry equipment  Verizon maintains the T1’s  ILG’s maintain everything inside the entry router  Most MITnet services are available inside ILG subnets  DHCP registration service  Moira host database  Security scans and notifications

10. Problem Reporting and Escalation Chain  Tiered model  Tier 1: ILG Network Contacts  Tier 2: ILG Coordinators (ilg-net-help@mit.edu)  Tier 3: MIT Network Operations / Verizon  Generally problem reporting should start with the ILG Network Contacts  If ILG Net Contacts cannot be reached HM’s should use ilg-net-help list directly (please make sure to identify yourself and say that you tried to reach the Net Contact)  Tiered model  Tier 1: ILG Network Contacts  Tier 2: ILG Coordinators (ilg-net-help@mit.edu)  Tier 3: MIT Network Operations / Verizon  Generally problem reporting should start with the ILG Network Contacts  If ILG Net Contacts cannot be reached HM’s should use ilg-net-help list directly (please make sure to identify yourself and say that you tried to reach the Net Contact)

11. Net Contact Responsibilities  Help residents connect to MITnet  Create proper hostname entries and keep them current  Cooperate with IS&T staff to resolve problems  Adhere to MITnet rules of use and the rules in the Quick Guide  Keep ilg-net-help@mit.edu updated with changes to network contacts  Help residents connect to MITnet  Create proper hostname entries and keep them current  Cooperate with IS&T staff to resolve problems  Adhere to MITnet rules of use and the rules in the Quick Guide  Keep ilg-net-help@mit.edu updated with changes to network contacts

12. Outages  Equipment beyond the MIT router is the responsibility of the ILG  Attempt to debug the problem  Ping other hosts on your subnet  Ping your router  Ping some other host on MITnet that isn’t on your subnet  Connect one machine to the networking equipment and see if that machine can reach your router and other hosts on MITnet  If the problem isn’t internal, follow the contact instructions in the QuickGuide  Equipment beyond the MIT router is the responsibility of the ILG  Attempt to debug the problem  Ping other hosts on your subnet  Ping your router  Ping some other host on MITnet that isn’t on your subnet  Connect one machine to the networking equipment and see if that machine can reach your router and other hosts on MITnet  If the problem isn’t internal, follow the contact instructions in the QuickGuide

13. DHCP Registration  Active in all FSILG’s  Set “obtain IP address automatically”  Set “obtain DNS servers automatically”  Browse to any web address  Active in all FSILG’s  Set “obtain IP address automatically”  Set “obtain DNS servers automatically”  Browse to any web address

14. Maintaining Connectivity  Highly cooperative effort between MIT, Verizon, and ILG  Because of the number of players involved we occasionally run into “passing the buck” problems  Open and reliable communication is critical  Important to keep Net Contacts up to date  Highly cooperative effort between MIT, Verizon, and ILG  Because of the number of players involved we occasionally run into “passing the buck” problems  Open and reliable communication is critical  Important to keep Net Contacts up to date

15. Useful Contact Information  Your ILG Network Contacts  Designate one primary Network Contact  https://web.mit.edu/rescomp/ILG/ilg-contacts.txt  Keep address records current  ilg-net-help@mit.edu list  Adam D’Amico  Angie Kelic  Oliver Thomas  Your ILG Network Contacts  Designate one primary Network Contact  https://web.mit.edu/rescomp/ILG/ilg-contacts.txt  Keep address records current  ilg-net-help@mit.edu list  Adam D’Amico  Angie Kelic  Oliver Thomas

16. Upcoming Bandwidth Upgrades (Spring 2005)

17. Demise of Service-Level Agreements Transition to a more cooperative and less segregated approach (Risks and opportunities) Transition to a more cooperative and less segregated approach (Risks and opportunities)

18. Telephones

19. Discussion and Q&A Contact info: Oliver Thomas othomas@mit.edu Contact info: Oliver Thomas othomas@mit.edu