<?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 Shared SAN IP LIF in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Shared-SAN-IP-LIF/m-p/446376#M42607</link>
    <description>&lt;P&gt;Starting ONTAP 9.13.1 , iSCSI and NVMe-TCP Services can be part of the same IP LIF and by doing it we have both the protocols exercised on the same IP.&amp;nbsp; This can be done as when a new lif is created or modify an existing LIF. This capability can be exercised by having custom service policy with both data-iscsi and data-nvme-tcp and then creating/modifying the LIF to the custom service policy.&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 09:46:47 GMT</pubDate>
    <dc:creator>jaikumar</dc:creator>
    <dc:date>2025-06-04T09:46:47Z</dc:date>
    <item>
      <title>Shared SAN IP LIF</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Shared-SAN-IP-LIF/m-p/446376#M42607</link>
      <description>&lt;P&gt;Starting ONTAP 9.13.1 , iSCSI and NVMe-TCP Services can be part of the same IP LIF and by doing it we have both the protocols exercised on the same IP.&amp;nbsp; This can be done as when a new lif is created or modify an existing LIF. This capability can be exercised by having custom service policy with both data-iscsi and data-nvme-tcp and then creating/modifying the LIF to the custom service policy.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 09:46:47 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Shared-SAN-IP-LIF/m-p/446376#M42607</guid>
      <dc:creator>jaikumar</dc:creator>
      <dc:date>2025-06-04T09:46:47Z</dc:date>
    </item>
  </channel>
</rss>

