<?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 Virtual storage console 2.0.1 does not prompt to enter controllers in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Virtual-storage-console-2-0-1-does-not-prompt-to-enter-controllers/m-p/49694#M4758</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi&lt;/P&gt;&lt;P&gt;Just wondered if anyone has seen this problem before.&lt;/P&gt;&lt;P&gt;after successful installation of vsc and registration vsc does not prompt for the netapp controller login, therefore it only shows the ESX hosts in the overview, storage controllers are blank&lt;/P&gt;&lt;P&gt;I have tried running the update severel times and even a reinstallation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;any pointers much appreciated&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 07:02:11 GMT</pubDate>
    <dc:creator>imarcroft</dc:creator>
    <dc:date>2025-06-05T07:02:11Z</dc:date>
    <item>
      <title>Virtual storage console 2.0.1 does not prompt to enter controllers</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Virtual-storage-console-2-0-1-does-not-prompt-to-enter-controllers/m-p/49694#M4758</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi&lt;/P&gt;&lt;P&gt;Just wondered if anyone has seen this problem before.&lt;/P&gt;&lt;P&gt;after successful installation of vsc and registration vsc does not prompt for the netapp controller login, therefore it only shows the ESX hosts in the overview, storage controllers are blank&lt;/P&gt;&lt;P&gt;I have tried running the update severel times and even a reinstallation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;any pointers much appreciated&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:02:11 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Virtual-storage-console-2-0-1-does-not-prompt-to-enter-controllers/m-p/49694#M4758</guid>
      <dc:creator>imarcroft</dc:creator>
      <dc:date>2025-06-05T07:02:11Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual storage console 2.0.1 does not prompt to enter controllers</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Virtual-storage-console-2-0-1-does-not-prompt-to-enter-controllers/m-p/49699#M4759</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;Last Monday I was at the customer site to install the new VSC 2.0.1.&lt;/P&gt;&lt;P&gt;Customer had SMVI previously but after the VMware migration to vSphere 4.1 I decided to upgrade to the latest versione of VSC.&lt;/P&gt;&lt;P&gt;On the primary site it works like a charm and the discovery worked very nice.&lt;/P&gt;&lt;P&gt;On the secondary site, instead, I spent 2 hours before understand why, like happened to you, I wasn't able to discover the 2 controllers even if I was able to connect to them from the same machine using the filerview and the telnet.&lt;/P&gt;&lt;P&gt;The solution was very simple...!&lt;/P&gt;&lt;P&gt;All the volumes were in restricted state.&lt;/P&gt;&lt;P&gt;So, now I know that in some way, at least a volume for each controller must be online to make the discover process works!&lt;/P&gt;&lt;P&gt;I hope this can help you.&lt;/P&gt;&lt;P&gt;Bye&lt;/P&gt;&lt;P&gt;Dario&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Jan 2011 20:48:15 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Virtual-storage-console-2-0-1-does-not-prompt-to-enter-controllers/m-p/49699#M4759</guid>
      <dc:creator>Dario_Bazzichetto</dc:creator>
      <dc:date>2011-01-20T20:48:15Z</dc:date>
    </item>
  </channel>
</rss>

