50 likes | 235 Views
PowerEdge M620 . LOM Broadcom 57810-K 10GB NDC. MEZZ B Emulex LPE 1205-M 8Gbps FC I/O Card. MEZZ C Unused. Server. Chasis. Fabric A1 M-8024K. Fabric B1 Dell FC 8/4 Passthrough. Fabric C1. Fabric A2 M-8024K. Fabric B2 Dell FC 8/4 Passthrough. Fabric C2.
E N D
PowerEdge M620 LOM Broadcom 57810-K 10GB NDC MEZZ B Emulex LPE 1205-M 8Gbps FC I/O Card MEZZ C Unused Server Chasis Fabric A1 M-8024K Fabric B1 Dell FC 8/4 Passthrough Fabric C1 Fabric A2 M-8024K Fabric B2 Dell FC 8/4 Passthrough Fabric C2
Static Design Configuration with Broadcom Hardware assisted Network Partitions Dell PowerEdge M620 MGMT Dvuplink5 vMotion dvuplink6 TSM PAN dvuplink7 VM Prod dvuplink8 MGMT dvuplink1 vMotion dvuplink2 TSM PAN dvuplink3 VM Prod dvuplink4 PF# 1 PF# 3 PF# 5 PF# 7 PF# 0 PF# 2 PF# 4 PF# 6 1 Gb 7Gb 1 Gb 1 Gb 7Gb 1 Gb 1 Gb 1 Gb Physical Port 0 Physical Port 1 Broadcom 57810 – K NDC 10 Gb Ethernet Lane 10 Gb Ethernet Lane NetworkSwitch Consideration: Each Physical function within Physical Port is serving to different VLAN
Static Design Configuration with Broadcom Hardware assisted Network Partitions Pros : Bandwidth management offloaded to hardware layer Better control over bandwidth Less management overheads Traditional Network troubleshooting skills are enough for support Cons : Restricted to 4 partitions per NIC port or 8 partitions per NIC Not flexible to accommodate more traffic types if required in future for e.g. FT traffic or Not flexible to get away with existing traffic types without reconfiguration and ESX host downtime
Static Design with Vmware LBT Pros : Traffic separation using VLANs Traffic types can be mapped to different Links as Primary Configuration changes are non disruptive if traffic needs to be rerouted Cons : No protection against one traffic type dominating others Hard limits can be put in on each traffic type at port group layer but any underutilized bandwidth is waste Traffic management at hypervisor layer
Dynamic Design with Vmware NIOC & LBT Note: Enable egress traffic shaper on vMotion dVPort Group to help in situations where multiple vMotions initiated on different hosts converge to same vSphere server Pros : Traffic separation using VLANs Dynamic traffic management (greater flexibility in distribution of unused traffic) Configuration changes are non disruptive and new traffic types can easily be introduced Cons : Traffic management at hypervisor layer (but doesn’t kick off unless uplink utilization is over 75% for more than 30 seconds) Multiple NIC vMotion ??? Needs to be tested