<?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: cluster management lif is not at home port in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/cluster-management-lif-is-not-at-home-port/m-p/436357#M11279</link>
    <description>&lt;P&gt;The node management LIF and SP use e0m so you can attempt to ping or connect to those IP addresses.&lt;/P&gt;</description>
    <pubDate>Fri, 01 Jul 2022 06:13:44 GMT</pubDate>
    <dc:creator>NetApp_SR</dc:creator>
    <dc:date>2022-07-01T06:13:44Z</dc:date>
    <item>
      <title>cluster management lif is not at home port</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/cluster-management-lif-is-not-at-home-port/m-p/436252#M11269</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hello Team,&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;W&lt;/SPAN&gt;&lt;SPAN&gt;e had&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;manually moved&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;LIF&lt;/SPAN&gt;&amp;nbsp;cluster_mgmt&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;from not&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;working port (&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;S1D1NNFBKP8020-01_mgmt1&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;10.189.187.170) to working port (&lt;/SPAN&gt;&lt;SPAN&gt;S1D1NNFBKP8020-02_mgmt1&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;10.189.187.171) to access storage and performed down/up port on&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;S1D1NNFBKP001 port e0M for troubleshooting purpose&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Fri Jun 24 09:48:42 IST [S1D1NNFBKP001: vifmgr: vifmgr.&lt;SPAN class=""&gt;lif&lt;/SPAN&gt;BeingRemoved:notice]:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;LIF&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;cluster_mgmt (on virtual server 4294967295), IP address 10.189.187.174, is being removed from node S1D1NNFBKP001, port e0M.&lt;/P&gt;&lt;P&gt;Fri Jun 24 09:48:42 IST [S1D1NNFBKP001: vifmgr: vifmgr.&lt;SPAN class=""&gt;lif&lt;/SPAN&gt;moved.byadmin:notice]:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;LIF&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;cluster_mgmt (on virtual server 4294967295), IP address 10.189.187.174, is being moved to node S1D1NNFBKP002, port e0M.&lt;/P&gt;&lt;P&gt;Fri Jun 24 09:52:46 IST [S1D1NNFBKP001: vifmgr: vifmgr.portdown:notice]: A link down event was received on node S1D1NNFBKP001, port e0M.&lt;/P&gt;&lt;P&gt;Fri Jun 24 09:52:46 IST [S1D1NNFBKP001: vifmgr: vifmgr.&lt;SPAN class=""&gt;lif&lt;/SPAN&gt;down.noports:alert]:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;LIF&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;S1D1NNFBKP8020-01_mgmt1 (on virtual server 4294967295), IP address 10.189.187.170, currently cannot be hosted on node S1D1NNFBKP001, port e0M, or any of its failover targets, and is being marked as down.&lt;/P&gt;&lt;P&gt;Fri Jun 24 09:52:46 IST [S1D1NNFBKP001: vifmgr: vifmgr.&lt;SPAN class=""&gt;lif&lt;/SPAN&gt;BeingRemoved:notice]:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;LIF&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;S1D1NNFBKP8020-01_mgmt1 (on virtual server 4294967295), IP address 10.189.187.170, is being removed from node S1D1NNFBKP001, port e0M.&lt;/P&gt;&lt;P&gt;Fri Jun 24 09:53:05 IST [S1D1NNFBKP001: vifmgr: vifmgr.portup:notice]: A link up event was received on node S1D1NNFBKP001, port e0M.&lt;/P&gt;&lt;P&gt;Fri Jun 24 09:53:05 IST [S1D1NNFBKP001: vifmgr: vifmgr.&lt;SPAN class=""&gt;lif&lt;/SPAN&gt;beinghosted:notice]:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;LIF&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;S1D1NNFBKP8020-01_mgmt1 (on virtual server 4294967295), IP address 10.189.187.170, previously marked as down, is now up and serving data on node S1D1NNFBKP001, port e0M.&lt;/P&gt;&lt;P&gt;Fri Jun 24 09:53:05 IST [S1D1NNFBKP001: vifmgr: vifmgr.&lt;SPAN class=""&gt;lif&lt;/SPAN&gt;successfullymoved:notice]:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;LIF&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;S1D1NNFBKP8020-01_mgmt1 (on virtual server 4294967295), IP address 10.189.187.170, is now hosted on node S1D1NNFBKP001, port e0M.&lt;/P&gt;&lt;P&gt;Fri Jun 24 10:50:08 IST [S1D1NNFBKP001: vifmgr: vifmgr.&lt;SPAN class=""&gt;lif&lt;/SPAN&gt;BeingRemoved:notice]:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;LIF&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;S1D1NNFBKP8020-01_mgmt1 (on virtual server 4294967295), IP address 10.189.187.170, is being removed from node S1D1NNFBKP001, port e0M.&lt;/P&gt;&lt;P&gt;Fri Jun 24 10:51:05 IST [S1D1NNFBKP001: vifmgr: vifmgr.&lt;SPAN class=""&gt;lif&lt;/SPAN&gt;successfullymoved:notice]:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;LIF&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;S1D1NNFBKP8020-01_mgmt1 (on virtual server 4294967295), IP address 10.189.187.170, is now hosted on node S1D1NNFBKP001, port e0M.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As now we are trying to check at hardware aspect but i need to know how to get check lif availability before migrating to home port and what can be reason for more history refer case&amp;nbsp;&lt;SPAN&gt;2009217608&amp;nbsp;, anymore suggestion to bring up the lif back to normalize until then we will check the hardware aspect&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jun 2022 07:24:36 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/cluster-management-lif-is-not-at-home-port/m-p/436252#M11269</guid>
      <dc:creator>backupstorageCRM</dc:creator>
      <dc:date>2022-06-28T07:24:36Z</dc:date>
    </item>
    <item>
      <title>Re: cluster management lif is not at home port</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/cluster-management-lif-is-not-at-home-port/m-p/436357#M11279</link>
      <description>&lt;P&gt;The node management LIF and SP use e0m so you can attempt to ping or connect to those IP addresses.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Jul 2022 06:13:44 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/cluster-management-lif-is-not-at-home-port/m-p/436357#M11279</guid>
      <dc:creator>NetApp_SR</dc:creator>
      <dc:date>2022-07-01T06:13:44Z</dc:date>
    </item>
    <item>
      <title>Re: cluster management lif is not at home port</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/cluster-management-lif-is-not-at-home-port/m-p/455425#M11896</link>
      <description>&lt;P&gt;1. Run the network interface failover-groups show command to view your failover group and check whether the e0m of the node has a proper failover group.&lt;BR /&gt;"network interface failover-groups show "&lt;BR /&gt;2, you can use the following command to return your port to the master node.&lt;BR /&gt;“network interface revert -vserver vserver_name -lif lif_name”&lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2024 08:43:52 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/cluster-management-lif-is-not-at-home-port/m-p/455425#M11896</guid>
      <dc:creator>weiliu</dc:creator>
      <dc:date>2024-09-26T08:43:52Z</dc:date>
    </item>
  </channel>
</rss>

