5 Responses

  1. ljm
    ljm at |

    Good point, I’ve seen this too. With a NetApp, you can disable the iSCSI targets on the nics / ifgrps that aren’t on an iSCSI network so the ESX host will never learn about those targets and therefore will never attempt attach to them. Overall worth checking from all angles though!

    Reply
    1. Patrick Terlisten (@PTerlisten)
      Patrick Terlisten (@PTerlisten) at |

      I noticed today that removing the dynamic discovery IPs from the list also removes the static discovery IPs after a reboot. If I remove the discovery IP and switch to the static discovery tab, the entries show a “orphaned parent”. After a reboot the entries are gone. Can you confirm this?

      Reply
  2. Newsletter: March 8, 2015 | Notes from MWhite

    […] Caution Using Dynamic Discovery for Multi-Homed iSCSI Targets This is something I have not seen much or worked with much, but it sounds like if you use multi-homed iSCSI targets […]

  3. When To Use Multiple Subnet iSCSI Network Design - Wahl Network

    […] in to all targets that have been added manually or retrieved using the send targets request (read my other blog post for more on caveats with multiple subnets and dynamic discovery).  Assuming that the networks are […]

Share your point of view!