<?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 The e0M cannot be connected in AFF</title>
    <link>https://community.netapp.com/t5/AFF/The-e0M-cannot-be-connected/m-p/455281#M1320</link>
    <description>&lt;P&gt;Hello, everyone.&lt;BR /&gt;I am manually obtaining autosupport logs. I configured the Ethernet port of my computer on the same network segment as the storage management port, and connected the storage e0M port with a network cable. I tried to log in to the centralized management IP/spi to obtain autosupport logs, but I found that I could not ping through the management IP address of the storage end. The computer firewall is also turned off&lt;BR /&gt;(Because in other places my computer is able to connect to storage and access graphics pages)&lt;BR /&gt;Is there any restriction made by the storage to deny my access?&lt;/P&gt;</description>
    <pubDate>Fri, 20 Sep 2024 12:51:36 GMT</pubDate>
    <dc:creator>weiliu</dc:creator>
    <dc:date>2024-09-20T12:51:36Z</dc:date>
    <item>
      <title>The e0M cannot be connected</title>
      <link>https://community.netapp.com/t5/AFF/The-e0M-cannot-be-connected/m-p/455281#M1320</link>
      <description>&lt;P&gt;Hello, everyone.&lt;BR /&gt;I am manually obtaining autosupport logs. I configured the Ethernet port of my computer on the same network segment as the storage management port, and connected the storage e0M port with a network cable. I tried to log in to the centralized management IP/spi to obtain autosupport logs, but I found that I could not ping through the management IP address of the storage end. The computer firewall is also turned off&lt;BR /&gt;(Because in other places my computer is able to connect to storage and access graphics pages)&lt;BR /&gt;Is there any restriction made by the storage to deny my access?&lt;/P&gt;</description>
      <pubDate>Fri, 20 Sep 2024 12:51:36 GMT</pubDate>
      <guid>https://community.netapp.com/t5/AFF/The-e0M-cannot-be-connected/m-p/455281#M1320</guid>
      <dc:creator>weiliu</dc:creator>
      <dc:date>2024-09-20T12:51:36Z</dc:date>
    </item>
    <item>
      <title>Re: The e0M cannot be connected</title>
      <link>https://community.netapp.com/t5/AFF/The-e0M-cannot-be-connected/m-p/455293#M1321</link>
      <description>&lt;P&gt;Typically, you have one cluster management interface (LIF) and two node management interfaces. The cluster-mgmt LIF could be mapped to any of the node’s management ports. Try using the node-mgmt LIF/IP, instead.&lt;/P&gt;</description>
      <pubDate>Sat, 21 Sep 2024 18:54:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/AFF/The-e0M-cannot-be-connected/m-p/455293#M1321</guid>
      <dc:creator>andris</dc:creator>
      <dc:date>2024-09-21T18:54:55Z</dc:date>
    </item>
  </channel>
</rss>

