ESXi

 View Only
  • 1.  Why bind FCoE nics to separate vSwitches?

    Broadcom Employee
    Posted Jan 09, 2013 09:19 AM

    If your host has multiple network adapters or multiple ports on the adapter, connect each FCoE NIC to a separate standard switch. but why this is what i do not understand?



  • 2.  RE: Why bind FCoE nics to separate vSwitches?

    Posted Jan 09, 2013 10:28 AM

    Have you considered the requirement of switch failovers?



  • 3.  RE: Why bind FCoE nics to separate vSwitches?

    Broadcom Employee
    Posted Jan 09, 2013 10:50 AM

    means what?



  • 4.  RE: Why bind FCoE nics to separate vSwitches?

    Posted Jan 09, 2013 10:56 AM

    In case one of your switch goes down due to any external or configuration changes.

    "This practice helps you to avoid an APD  condition when a  disruptive event, such as  an MTU change, occurs."



  • 5.  RE: Why bind FCoE nics to separate vSwitches?

    Posted Jan 09, 2013 10:58 AM

    I belive however that the question was about internal standard vSwitches. I of course agree that it is very good to have physical switch redundancy.



  • 6.  RE: Why bind FCoE nics to separate vSwitches?

    Posted Jan 09, 2013 11:08 AM

    I belive however that the question was about internal standard vSwitches. I of course agree that it is very good to have physical switch redundancy.

    :smileyhappy: I did believe that the reference was for vSwitch. But the word "standard switch" made me wonder for a while before typing :smileyhappy:

    great explanation btw on the target and initiator side



  • 7.  RE: Why bind FCoE nics to separate vSwitches?

    Posted Jan 09, 2013 10:52 AM

    Ranjna Aggarwal wrote:

    If your host has multiple network adapters or multiple ports on the adapter, connect each FCoE NIC to a separate standard switch. but why this is what i do not understand?

    I think the statements about FCoE in the ICM book is a bit confusing and contradictory.

    One reason for adding each FCoE nic port to a different vSwitch could be to give the software FCoE initator in the vmkernel the same "view" as for software iSCSI, that is that each path has only one "active" way, much the same as for iSCSI multipathing.

    However, from the recent manual it states clearly that you do not have to attach them to different vSwitches, so it might just be an error in the ICM guide.

    "If your host has multiple network adapters or multiple ports on the adapter, you can add all of them to a single vSphere standard switch. An alternative is to connect each FCoE NIC to a separate standard switch."

    http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc%2FGUID-93983024-33E6-455C-AA64-C937377E5D57.html



  • 8.  RE: Why bind FCoE nics to separate vSwitches?

    Posted Jan 09, 2013 10:54 AM

    * Thread title adjusted to a shorter version.

    Regards /  Rickard