+ Reply to Thread
Results 1 to 2 of 2
  1. Senior Member sacredboy's Avatar
    Join Date
    May 2012
    Location
    Australia
    Posts
    288
    #1

    Default iSCSI and NIC Teaming in VMware

    Hi guys,

    I need your help to clarify one issue in regards to iSCSi initiator and NIC Teaming in VMware. Once I tried to configure iSCSI storage in VMware but failed on the stage of configuring iSCSi initiator. The issue was that I had two vmnics combined in NIC teaming and when trying to add adapter for VMkernel port binding I was getting this warning:

    "The selected physical network adapter is not associated with VMkernel with compliant teaming and failover policy. VMkernel network adapter must have exactly one active uplink and no standby uplinks to be eligible for binding to the iSCSI HBA."

    After several minutes of googling I found out that I have to break NIC Teaming and put one of the intefaces to "Unused" state.

    Yesterday, I was playing around with migration from svs to dvs and came across with an article about it. I was a bit surprised when I saw the screenshot where two VMkernel port groups on the same vswitch with two nics combined in NIC Teaming were added in iSCSi software adapter.

    34.jpg 110.jpg

    How it can be possible?
    Best, sacredboy!
    Reply With Quote Quote  

  2. Senior Member scott28tt's Avatar
    Join Date
    Jul 2010
    Posts
    614

    Certifications
    MCSE VCP2 VCP3 VCP4 VCP5 VCAP4-DCA VCI
    #2
    They've used 2 separate port groups, here's how they might be configured:

    "iSCSI-Initiator" configured with vmnic3 as an active adapter, but with vmnic4 as an unused adapter
    "iSCSI-Initiator2" configured with vmnic4 as an active adapter, but with vmnic3 as an unused adapter
    VCP2 / VCP3 / VCP4 / VCP5 / VCAP4-DCA / VCI / vExpert 2010-2012
    Blog - http://vmwaretraining.blogspot.com
    Twitter - http://twitter.com/vmtraining
    Email - vmtraining.blog@gmail.com
    Reply With Quote Quote  

+ Reply to Thread

Social Networking & Bookmarks