<?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 Parsing sdcli iscsi initiator list in powershell in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/Parsing-sdcli-iscsi-initiator-list-in-powershell/m-p/117925#M10759</link>
    <description>&lt;P&gt;FYI&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was in need of getting iscsi configuration data off of Windows Server 2008 r2 hosts to upload into a database, *cough* WFA *cough* .&amp;nbsp;The only decent information I found was using the sdcli to get the iscsi information remotely. &amp;nbsp;So I wrote this powershell function to parse through the raw text that "sdcli iscsi_initiator list -m $server -s" gives you back, and return a custom powershell object.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm doing this so that I can compare the target IP addresses with what the array currently has to make sure the iscsi session is configured with all the paths.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Use at your own risk. I have tested it on a couple machines. It is quite possible that I didn't code for every scenari&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 21:34:02 GMT</pubDate>
    <dc:creator>coreywanless</dc:creator>
    <dc:date>2025-06-04T21:34:02Z</dc:date>
    <item>
      <title>Parsing sdcli iscsi initiator list in powershell</title>
      <link>https://community.netapp.com/t5/Data-Protection/Parsing-sdcli-iscsi-initiator-list-in-powershell/m-p/117925#M10759</link>
      <description>&lt;P&gt;FYI&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was in need of getting iscsi configuration data off of Windows Server 2008 r2 hosts to upload into a database, *cough* WFA *cough* .&amp;nbsp;The only decent information I found was using the sdcli to get the iscsi information remotely. &amp;nbsp;So I wrote this powershell function to parse through the raw text that "sdcli iscsi_initiator list -m $server -s" gives you back, and return a custom powershell object.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm doing this so that I can compare the target IP addresses with what the array currently has to make sure the iscsi session is configured with all the paths.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Use at your own risk. I have tested it on a couple machines. It is quite possible that I didn't code for every scenari&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 21:34:02 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Parsing-sdcli-iscsi-initiator-list-in-powershell/m-p/117925#M10759</guid>
      <dc:creator>coreywanless</dc:creator>
      <dc:date>2025-06-04T21:34:02Z</dc:date>
    </item>
  </channel>
</rss>

