<?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 Discovering new paths on Windows Server in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Discovering-new-paths-on-Windows-Server/m-p/447538#M9915</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We've added an A400 system to our cluster and need its interfaces discovered on one of our Windows Production Servers.&amp;nbsp; It's zoned correctly and I can see the interfaces are logged in.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Windows is not seeing the new paths, i've created a new lun and mapped it to a new Igroup with the new interfaces binded.&amp;nbsp; This is a production server and rebooting is currently not an option.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It was suggested through a google search to disable and re-enable MPIO - will this cause any disruptions?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What are my other options?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 09:45:09 GMT</pubDate>
    <dc:creator>Panther411</dc:creator>
    <dc:date>2025-06-04T09:45:09Z</dc:date>
    <item>
      <title>Discovering new paths on Windows Server</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Discovering-new-paths-on-Windows-Server/m-p/447538#M9915</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We've added an A400 system to our cluster and need its interfaces discovered on one of our Windows Production Servers.&amp;nbsp; It's zoned correctly and I can see the interfaces are logged in.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Windows is not seeing the new paths, i've created a new lun and mapped it to a new Igroup with the new interfaces binded.&amp;nbsp; This is a production server and rebooting is currently not an option.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It was suggested through a google search to disable and re-enable MPIO - will this cause any disruptions?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What are my other options?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 09:45:09 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Discovering-new-paths-on-Windows-Server/m-p/447538#M9915</guid>
      <dc:creator>Panther411</dc:creator>
      <dc:date>2025-06-04T09:45:09Z</dc:date>
    </item>
    <item>
      <title>Re: Discovering new paths on Windows Server</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Discovering-new-paths-on-Windows-Server/m-p/449623#M9989</link>
      <description>&lt;P&gt;Disabling MPIO may not be at device level but for all the devices , which is not recommended when there is IO to the underlying Block Storage Device.&lt;BR /&gt;But following can be tried.&lt;BR /&gt;* Check if the initiator is logged in&amp;nbsp;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;fcp initiator show&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;(vserver fcp initiator show)&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Logical&amp;nbsp; &amp;nbsp; Port&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Initiator&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Initiator&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Vserver Interface&amp;nbsp; &amp;nbsp;Address&amp;nbsp; WWNN&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;WWPN&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Igroup&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;--------- ----------------- -------- ------------ ------------ ---------------&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;vserver LifFCP1 20:00:00:10:9b:57:94:ce &lt;FONT color="#800080"&gt;&lt;FONT color="#FFCC00"&gt;10:00:00:10:9b:57:94:ce&lt;/FONT&gt;&amp;nbsp;&lt;/FONT&gt;&lt;FONT color="#FF0000"&gt;&lt;EM&gt;igroupname&amp;nbsp;&lt;/EM&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;BR /&gt;*&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#0000FF"&gt;igroup show -igroup &lt;FONT color="#FF0000"&gt;&lt;EM&gt;igroupname&lt;/EM&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#0000FF"&gt;Vserver Name: vserver&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Igroup Name: &lt;FONT color="#FF0000"&gt;&lt;EM&gt;igroupname&amp;nbsp;&lt;/EM&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Protocol: mixed&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;OS Type: vmware&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Portset Binding Igroup: -&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Initiators: &lt;FONT color="#FFCC00"&gt;10:00:00:10:9b:57:94:ce&lt;/FONT&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Child Igroups: -&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Initiator Comments: -&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Initiator Comments: -&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Igroup UUID: 3fc5b0e7-9370-11ee-b474-00a098f3e343&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;ALUA: true&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Initiators: &lt;FONT color="#FFCC00"&gt;10:00:00:10:9b:57:94:ce&lt;/FONT&gt;&amp;nbsp;(&lt;FONT color="#FF0000"&gt;logged in&lt;/FONT&gt;) &amp;lt;&amp;lt; &lt;U&gt;Check if the host initiator is logged in&amp;nbsp;&lt;/U&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Vserver UUID: 065f43a9-7ee7-11ee-86d3-00a098f3e357&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Delete on Last Unmap: -&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;New Name: -&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Igroup Comment: -&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Child Names: -&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Parent Names: -&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Replication Peer: -&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Replication Error: -&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Replication Error Igroup: -&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Peer Vserver UUID: -&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Peer Igroup UUID: -&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Replicated Igroup Contains Unreplicated LUNs: false&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;* And if the initiator is logged in then , Rescan for new Disks in the Windows Disk Management&lt;/P&gt;</description>
      <pubDate>Sat, 09 Dec 2023 20:02:59 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Discovering-new-paths-on-Windows-Server/m-p/449623#M9989</guid>
      <dc:creator>jaikumar</dc:creator>
      <dc:date>2023-12-09T20:02:59Z</dc:date>
    </item>
  </channel>
</rss>

