Data centre networking at the University of Bristol - Networkshop44
•Download as PPTX, PDF•
1 like•2,372 views
The document summarizes the modernization of the University of Bristol's existing data center and plans for a new second data center. It discusses how the existing data center was upgraded from legacy switches to Cisco Nexus switches with copper and fiber connectivity. It also addresses challenges in configuring the legacy switches and moving from Fibre Channel storage to iSCSI. Plans for the new data center include geographic diversity, sub-2ms connectivity between sites to allow for synchronous storage, and architecting services to work across multiple data centers. The future plans include using Nexus 9k switches with APIC and integrating F5 load balancers and Hyper-V into the network architecture.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Data centre networking at the University of Bristol - Networkshop44
Similar to Data centre networking at the University of Bristol - Networkshop44 (20)
More from Jisc
More from Jisc (20)
Recently uploaded
Recently uploaded (20)
Data centre networking at the University of Bristol - Networkshop44
- 1. Data Centre at The University of Bristol Oliver Elliott
- 2. Data Centre at University of Bristol »How we modernized our existing Data Centre »Plans for a new second Data Centre »How to make them work together »The future! Introduction 22/03/2016 Data Centre at The University of Bristol
- 3. Data Centre at University of Bristol »Cisco Cat6500 DC Routers »Brocade FCX TOR Switches »Brocade SX HPC Routers »Brocade FC fabrics The Past 22/03/2016 Data Centre at The University of Bristol Configuring the legacy DC switches
- 4. Data Centre at University of Bristol »Problems: › No campus to DC FW › Difficult and expensive 10GbE –Copper or SFP+ or both? › EOL load balancers › Cross rack stacks increasing failure domain › SpanningTree convergence and interop Is this hacking? 22/03/2016 Data Centre at The University of Bristol
- 5. Data Centre at University of Bristol »The Current – How did we get here? › FC SAN -> iSCSI › 6500/Brocade SX -> Cisco Nexus –Copper FEX and 5k for SFP+ › Cisco ACE -> F5 › Fabricpath › SeparateVRF for out of band management network ("Pink" networks) 22/03/2016 Data Centre at The University of Bristol
- 6. Data Centre at University of Bristol »Topology design of our current DC 22/03/2016 Data Centre at The University of Bristol
- 7. Data Centre at University of Bristol »Load balancing 22/03/2016 Data Centre at The University of Bristol
- 8. Data Centre at University of Bristol »Bugs! »Physical faults during migration – MyFiles »Discovering just how many hosts didn't have any usable switch failover What went wrong? 22/03/2016 Data Centre at The University of Bristol
- 9. Data Centre at University of Bristol »Cultural change in the DC › From just a room with servers in to a proper managed DC »M&E upgrade in progress 22/03/2016 Data Centre at The University of Bristol
- 10. Data Centre at University of Bristol DC Requirements 22/03/2016 Data Centre at The University of Bristol »We need a 2nd Data Centre
- 11. Data Centre at University of Bristol »Geographically diverse »L2 between sites? No? (Not yet?) »Sub 2ms between sites to allow for synchronous storage? › Async vs Sync storage »Architecting services for multiple DC is different 22/03/2016 Data Centre at The University of Bristol
- 12. Data Centre at University of Bristol »Linking the Data Centres together
- 13. Data Centre at University of Bristol »JANET Diverse L2VPN 22/03/2016 Data Centre at The University of Bristol
- 14. Data Centre at University of Bristol »Nexus 9k and SDN › APIC › Integration of F5 and Hyper-V into the network The Future 22/03/2016 Data Centre at The University of Bristol
- 15. Data Centre at University of Bristol »Questions? 22/03/2016 Data Centre at The University of Bristol
- 16. jisc.ac.uk Thank you University of Bristol Oliver Elliott Senior Network Specialist oliver.elliott@bristol.ac.uk
Editor's Notes
- This student is presumably attempting to hack our DC
- Crocodile represents the dangers of migrating an entire DC network: You might lose a leg.
- Bugs on Nexus5k Fibre faults meant some switch stacks didn't come back properly Migrating a single TOR stack at a time to ensure hosts always had at least one working TOR switch. Unfortunately loads of hosts Solving failover makes future software upgrades easier to arrange
- Mechanical & Electrical - expensive! Might mean we need to vacate even sooner!
- Either accidentally nuked by Donald Trump or intentionally nuked by Hilary Clinton? Has taken a long time to get recognition from the University that this is a risk. Changing attitudes towards IT a big factor.
- Explain the multiple JANET links