A "What-if" analysis
Andrea Dainese - Data Center Engineer
Designing an Hybrid Data
Center Infrastructure
Data Center topology (8 years ago)
Devices
● Cisco Catalyst 6500 (core)
● Cisco Catalyst 3560 (access)
● Physical servers
...
Data Center topology (8 years ago)
What-if
● a core switch power down? ←
● an access switch power down?
● a fiber became u...
Data Center topology (8 years ago)
What-if
● a core switch power down?
● an access switch power down?
● a fiber became uni...
Data Center topology (8 years ago)
What-if
● a core switch power down?
● an access switch power down?
● a fiber became uni...
Data Center topology (8 years ago)
What-if
● a core switch power down?
● an access switch power down?
● a fiber became uni...
Data Center topology (4 years ago)
Evolutions
● needing a cheaper/easier storage network
● needing a faster Ethernet netwo...
Data Center topology (4 years ago)
What-if
● a SCSI transmission is lost/delayed?
● a cluster heartbeat is lost/delayed?
P...
Data Center topology (today)
Evolutions
● needing an unified cabling
● 10% physical - 90% virtual servers
Devices
● Blade ...
Data Center topology (today)
What-if
● a Cisco Nexus 5000 reboots?
● a BPDU is transmitted by a VM? ←
Problems
● Failover ...
Data Center topology (today)
What-if
● a Cisco Nexus 5000 reboots?
● a BPDU is transmitted by a VM? ←
Problems
● Failover ...
Data Center topology (today)
What-if
● a Cisco Nexus 5000 reboots?
● a BPDU is transmitted by a VM? ←
Problems
● Failover ...
Data Center topology (today)
What-if
● a Cisco Nexus 5000 reboots?
● a BPDU is transmitted by a VM? ←
Problems
● Failover ...
Conclusions
I. Ethernet is a lossy network
Be sure your software can tolerate connection reset,
packet loss/delay.
II. Sof...
Thanks
andrea.dainese@gmail.com
http://www.routereflector.com/
http://www.linkedin.com/in/adainese
@adainese
Andrea Dainese
Upcoming SlideShare
Loading in …5
×

festival ICT 2013: Designing an Hybrid Data Center Infrastructure

498 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
498
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
34
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

festival ICT 2013: Designing an Hybrid Data Center Infrastructure

  1. 1. A "What-if" analysis Andrea Dainese - Data Center Engineer Designing an Hybrid Data Center Infrastructure
  2. 2. Data Center topology (8 years ago) Devices ● Cisco Catalyst 6500 (core) ● Cisco Catalyst 3560 (access) ● Physical servers ● FC Storage
  3. 3. Data Center topology (8 years ago) What-if ● a core switch power down? ← ● an access switch power down? ● a fiber became unidirectional? Problems ● L2 Loops ● NHRP ← ● black hole caused by STP convergence ← Solutions ● HSRP/GLBP ← ● UDLD ● RPVST ← ● Storm Control ● VSS + PortChannel ← Conclusions ● lossy network ←
  4. 4. Data Center topology (8 years ago) What-if ● a core switch power down? ● an access switch power down? ● a fiber became unidirectional? ← Problems ● L2 Loops ← ● NHRP ● black hole caused by STP convergence Solutions ● HSRP/GLBP ● UDLD ← ● RPVST ● Storm Control ← ● VSS + PortChannel ← Conclusions ● lossy network ←
  5. 5. Data Center topology (8 years ago) What-if ● a core switch power down? ● an access switch power down? ● a fiber became unidirectional? ← Problems ● L2 Loops ← ● NHRP ● black hole caused by STP convergence Solutions ● HSRP/GLBP ● UDLD ← ● RPVST ● Storm Control ← ● VSS + PortChannel ← Conclusions ● lossy network ←
  6. 6. Data Center topology (8 years ago) What-if ● a core switch power down? ● an access switch power down? ● a fiber became unidirectional? ← Problems ● L2 Loops ← ● NHRP ● black hole caused by STP convergence Solutions ● HSRP/GLBP ● UDLD ← ● RPVST ● Storm Control ← ● VSS + PortChannel ← Conclusions ● lossy network ←
  7. 7. Data Center topology (4 years ago) Evolutions ● needing a cheaper/easier storage network ● needing a faster Ethernet network ● 50% physical - 50% virtual servers Devices ● Cisco Nexus 5000 (10 GbE core) ● Cisco Nexus 2000 (10 GbE access) ● Virtual servers ● NetApp storage (iSCSI/NFS)
  8. 8. Data Center topology (4 years ago) What-if ● a SCSI transmission is lost/delayed? ● a cluster heartbeat is lost/delayed? Problems ● SCSI over a lossy network ● Cluster heartbeat over a lossy network Solutions ● VMware Tools ● Timeouts Conclusions ● SCSI doesn't like lossy networks
  9. 9. Data Center topology (today) Evolutions ● needing an unified cabling ● 10% physical - 90% virtual servers Devices ● Blade Servers ● Virtual Appliance ● Unified Cabling (2 fibers bring everything)
  10. 10. Data Center topology (today) What-if ● a Cisco Nexus 5000 reboots? ● a BPDU is transmitted by a VM? ← Problems ● Failover does not work anymore ● BPDUs shut down all VMware servers ← Solutions ● Knows your devices ← Conclusions ● Hybrid devices behave unexpectedly ← Notes ● Nexus 1000v or vSphere 5.1 can filter BPDUs ● Reject “Forged Transmit” is not a solution
  11. 11. Data Center topology (today) What-if ● a Cisco Nexus 5000 reboots? ● a BPDU is transmitted by a VM? ← Problems ● Failover does not work anymore ● BPDUs shut down all VMware servers ← Solutions ● Knows your devices ← Conclusions ● Hybrid devices behave unexpectedly ← Notes ● Nexus 1000v or vSphere 5.1 can filter BPDUs ● Reject “Forged Transmit” is not a solution
  12. 12. Data Center topology (today) What-if ● a Cisco Nexus 5000 reboots? ● a BPDU is transmitted by a VM? ← Problems ● Failover does not work anymore ● BPDUs shut down all VMware servers ← Solutions ● Knows your devices ← Conclusions ● Hybrid devices behave unexpectedly ← Notes ● Nexus 1000v or vSphere 5.1 can filter BPDUs ● Reject “Forged Transmit” is not a solution
  13. 13. Data Center topology (today) What-if ● a Cisco Nexus 5000 reboots? ● a BPDU is transmitted by a VM? ← Problems ● Failover does not work anymore ● BPDUs shut down all VMware servers ← Solutions ● Knows your devices ← Conclusions ● Hybrid devices behave unexpectedly ← Notes ● Nexus 1000v or vSphere 5.1 can filter BPDUs ● Reject “Forged Transmit” is not a solution
  14. 14. Conclusions I. Ethernet is a lossy network Be sure your software can tolerate connection reset, packet loss/delay. II. Software/Hardware integration can behave unexpectedly Be aware of what your are including in your data-center and how to best configure it.
  15. 15. Thanks andrea.dainese@gmail.com http://www.routereflector.com/ http://www.linkedin.com/in/adainese @adainese Andrea Dainese

×