<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Only 1 target address in use on Nimble array after switching to Nimble PSP in Array Setup and Networking</title>
    <link>https://community.hpe.com/t5/array-setup-and-networking/only-1-target-address-in-use-on-nimble-array-after-switching-to/m-p/6985780#M1852</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;resolved.. i rebooted the hosts again and now everything shows correct.. i have all 4 target addresses again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 19 Jul 2014 00:00:55 GMT</pubDate>
    <dc:creator>chillware28</dc:creator>
    <dc:date>2014-07-19T00:00:55Z</dc:date>
    <item>
      <title>Only 1 target address in use on Nimble array after switching to Nimble PSP</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/only-1-target-address-in-use-on-nimble-array-after-switching-to/m-p/6985779#M1851</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just finished upgrading my CS-220 array to FW 2.08. I've followed the guides and created my new group IP (which I set to the same as the iSCSI discovery IP, I didn't see anything that I couldn't/shouldn't do this). I also installed NCM on all 6 of my ESXi hosts, rebooted them, and went though all of my datastores and changed the from VMware Round Robin to the new Nimble PSP Directed path policy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My CS220 has 4 iscsi data NICs configured, and when the Round Robin policy was selected on the datastores, I could see each data store had connected to each iSCSI IP on the Nimble as expected - i.e. 4 nics per ESXi host and, 4 nics on the Nimble, each data store had 4 connections to the Nimble on each of its 4 IPs. all good.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now with the Nimble PSP selected, each datastore still makes four connections to the Nimble however all 4 all go to only one Nimble IP, the same IP for all datastores across all hosts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why is everything only using 1 IP/NIC on the Nimble now? This doesn't seem right...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Attached is a screen shot of one of the data stores, showing all connections going to one IP, all my datastores look the same. They used show all four Nimble IP's&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hopefully this makes sense, thanks for any help!&lt;IMG alt="2014-07-18_14-48-58.jpg" class="jive-image image-1" src="https://community.hpe.com/legacyfs/online/1781_2014-07-18_14-48-58.jpg" style="height: auto;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jul 2014 21:50:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/only-1-target-address-in-use-on-nimble-array-after-switching-to/m-p/6985779#M1851</guid>
      <dc:creator>chillware28</dc:creator>
      <dc:date>2014-07-18T21:50:55Z</dc:date>
    </item>
    <item>
      <title>Re: Only 1 target address in use on Nimble array after switching to Nimble PSP</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/only-1-target-address-in-use-on-nimble-array-after-switching-to/m-p/6985780#M1852</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;resolved.. i rebooted the hosts again and now everything shows correct.. i have all 4 target addresses again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Jul 2014 00:00:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/only-1-target-address-in-use-on-nimble-array-after-switching-to/m-p/6985780#M1852</guid>
      <dc:creator>chillware28</dc:creator>
      <dc:date>2014-07-19T00:00:55Z</dc:date>
    </item>
  </channel>
</rss>

