<?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: Connectivity issue: Manager cannot reach Storage network in HPE Morpheus VM Essentials Software</title>
    <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/connectivity-issue-manager-cannot-reach-storage-network/m-p/7260517#M1682</link>
    <description>&lt;P&gt;On my hypervisors, I have bond0.100 and bond1.200. On the manager, I only have one virtual network interface. Is it necessary to add another network interface? Can the configuration you mentioned be done through the manager's GUI?&lt;/P&gt;</description>
    <pubDate>Tue, 06 Jan 2026 10:57:21 GMT</pubDate>
    <dc:creator>hlago</dc:creator>
    <dc:date>2026-01-06T10:57:21Z</dc:date>
    <item>
      <title>Connectivity issue: Manager cannot reach Storage network</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/connectivity-issue-manager-cannot-reach-storage-network/m-p/7260487#M1671</link>
      <description>&lt;P&gt;I have 2 hypervisors configured with two bonds: one for Production (VLAN 100) and another for Storage (VLAN 200). From the hypervisors, I can ping both Production and Storage networks. However, from the Manager, I cannot ping the Storage network. How can I resolve this issue?&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jan 2026 19:13:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/connectivity-issue-manager-cannot-reach-storage-network/m-p/7260487#M1671</guid>
      <dc:creator>hlago</dc:creator>
      <dc:date>2026-01-05T19:13:18Z</dc:date>
    </item>
    <item>
      <title>Re: Connectivity issue: Manager cannot reach Storage network</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/connectivity-issue-manager-cannot-reach-storage-network/m-p/7260509#M1678</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P data-unlink="true"&gt;Your Manager node is just sitting on the outside looking in because it lacks a physical or logical "foot" in that Storage network. While your hypervisors have those bonds configured to talk to both VLANs, the Manager usually only has a primary interface on the Production network (VLAN 100) by default. To fix this, you need to make sure the switch port connected to your Manager is&amp;nbsp;&lt;FONT color="#FFFFFF"&gt;c&lt;/FONT&gt;set as a trunk port allowing both VLANs, and then you’ll need to create a tagged sub-interface (like eth0.200 or bond0.200) on the Manager itself with a valid IP address from your Storage subnet. Without that specific VLAN 200 tag and a local IP in that range, the Manager doesn't have a path to route those pings, even if the hypervisors are sitting right next to it.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jan 2026 04:44:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/connectivity-issue-manager-cannot-reach-storage-network/m-p/7260509#M1678</guid>
      <dc:creator>moyali76alc</dc:creator>
      <dc:date>2026-01-06T04:44:32Z</dc:date>
    </item>
    <item>
      <title>Re: Connectivity issue: Manager cannot reach Storage network</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/connectivity-issue-manager-cannot-reach-storage-network/m-p/7260517#M1682</link>
      <description>&lt;P&gt;On my hypervisors, I have bond0.100 and bond1.200. On the manager, I only have one virtual network interface. Is it necessary to add another network interface? Can the configuration you mentioned be done through the manager's GUI?&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jan 2026 10:57:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/connectivity-issue-manager-cannot-reach-storage-network/m-p/7260517#M1682</guid>
      <dc:creator>hlago</dc:creator>
      <dc:date>2026-01-06T10:57:21Z</dc:date>
    </item>
  </channel>
</rss>

