<?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: Modify OneView IP Range in HPE OneView</title>
    <link>https://community.hpe.com/t5/hpe-oneview/modify-oneview-ip-range/m-p/7098005#M5523</link>
    <description>&lt;P&gt;About reserved&amp;nbsp;VLAN&amp;nbsp;pools&lt;/P&gt;&lt;P&gt;A reserved&amp;nbsp;VLAN&amp;nbsp;pool is a range of&amp;nbsp;VLANs used for allocation of non-tagged networks:&lt;/P&gt;&lt;P&gt;Tunnel&lt;BR /&gt;Untagged&lt;BR /&gt;Tagged networks and FCoE networks use&amp;nbsp;VLANs outside of the reserved pool. You cannot use a reserved&amp;nbsp;VLAN&amp;nbsp;for tagged or FCoE networks.&lt;/P&gt;&lt;P&gt;The&amp;nbsp;VLAN&amp;nbsp;pool allows the number of available&amp;nbsp;VLANs to be segregated between tagged and non-tagged networks. Because non-tagged networks use&amp;nbsp;VLANs for internal translation resources, a reserved&amp;nbsp;VLAN&amp;nbsp;pool can provide a sufficient number of&amp;nbsp;VLANs available for allocation of those internal&amp;nbsp;VLANs. In addition, the reserved pool range removes the need for translation resources to be used on tagged networks.&lt;/P&gt;&lt;P&gt;For the maximum number of&amp;nbsp;VLANs per physical downlink port, see the&amp;nbsp;HPE OneView Support Matrix for HPE Synergy.&lt;/P&gt;&lt;P&gt;Creating and managing a reserved&amp;nbsp;VLAN&amp;nbsp;pool&lt;/P&gt;&lt;P&gt;A reserved&amp;nbsp;VLAN&amp;nbsp;pool is unique within a fabric, but independently allocated within each logical interconnect. The reserved range is identical across all logical interconnects within a fabric. The remaining&amp;nbsp;VLANs (outside of the pool) are shared among all the logical interconnects within the fabric.&lt;/P&gt;&lt;P&gt;For HPE OneView running embedded on a HPE Synergy 12000 Frame, the default range starts at 3967 and the size is 128. The minimum size of the pool must be 60&amp;nbsp;VLANs to ensure the pool is not exhausted.&lt;BR /&gt;The size of the pool cannot exceed 128&amp;nbsp;VLANs.&lt;/P&gt;&lt;P&gt;For more information please refer below link.&lt;/P&gt;&lt;P&gt;&lt;A href="https://techlibrary.hpe.com/docs/enterprise/servers/oneview5.0/cicf/en/index.html#s_fabrics-vlan-pool-about-cic.html&amp;nbsp;" target="_blank"&gt;https://techlibrary.hpe.com/docs/enterprise/servers/oneview5.0/cicf/en/index.html#s_fabrics-vlan-pool-about-cic.html&amp;nbsp;&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 12 Aug 2020 10:09:13 GMT</pubDate>
    <dc:creator>AmRa</dc:creator>
    <dc:date>2020-08-12T10:09:13Z</dc:date>
    <item>
      <title>Modify OneView IP Range</title>
      <link>https://community.hpe.com/t5/hpe-oneview/modify-oneview-ip-range/m-p/7097927#M5522</link>
      <description>&lt;P&gt;I've got a Synergy system with a defined IP range which is being exhausted.&amp;nbsp; Is there a way to tag vlans on Synergy in the Settings/&lt;SPAN&gt;Addresses and Identifiers area to define an IP scope on a seperate network?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Aug 2020 17:43:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-oneview/modify-oneview-ip-range/m-p/7097927#M5522</guid>
      <dc:creator>thecakeisalie</dc:creator>
      <dc:date>2020-08-11T17:43:11Z</dc:date>
    </item>
    <item>
      <title>Re: Modify OneView IP Range</title>
      <link>https://community.hpe.com/t5/hpe-oneview/modify-oneview-ip-range/m-p/7098005#M5523</link>
      <description>&lt;P&gt;About reserved&amp;nbsp;VLAN&amp;nbsp;pools&lt;/P&gt;&lt;P&gt;A reserved&amp;nbsp;VLAN&amp;nbsp;pool is a range of&amp;nbsp;VLANs used for allocation of non-tagged networks:&lt;/P&gt;&lt;P&gt;Tunnel&lt;BR /&gt;Untagged&lt;BR /&gt;Tagged networks and FCoE networks use&amp;nbsp;VLANs outside of the reserved pool. You cannot use a reserved&amp;nbsp;VLAN&amp;nbsp;for tagged or FCoE networks.&lt;/P&gt;&lt;P&gt;The&amp;nbsp;VLAN&amp;nbsp;pool allows the number of available&amp;nbsp;VLANs to be segregated between tagged and non-tagged networks. Because non-tagged networks use&amp;nbsp;VLANs for internal translation resources, a reserved&amp;nbsp;VLAN&amp;nbsp;pool can provide a sufficient number of&amp;nbsp;VLANs available for allocation of those internal&amp;nbsp;VLANs. In addition, the reserved pool range removes the need for translation resources to be used on tagged networks.&lt;/P&gt;&lt;P&gt;For the maximum number of&amp;nbsp;VLANs per physical downlink port, see the&amp;nbsp;HPE OneView Support Matrix for HPE Synergy.&lt;/P&gt;&lt;P&gt;Creating and managing a reserved&amp;nbsp;VLAN&amp;nbsp;pool&lt;/P&gt;&lt;P&gt;A reserved&amp;nbsp;VLAN&amp;nbsp;pool is unique within a fabric, but independently allocated within each logical interconnect. The reserved range is identical across all logical interconnects within a fabric. The remaining&amp;nbsp;VLANs (outside of the pool) are shared among all the logical interconnects within the fabric.&lt;/P&gt;&lt;P&gt;For HPE OneView running embedded on a HPE Synergy 12000 Frame, the default range starts at 3967 and the size is 128. The minimum size of the pool must be 60&amp;nbsp;VLANs to ensure the pool is not exhausted.&lt;BR /&gt;The size of the pool cannot exceed 128&amp;nbsp;VLANs.&lt;/P&gt;&lt;P&gt;For more information please refer below link.&lt;/P&gt;&lt;P&gt;&lt;A href="https://techlibrary.hpe.com/docs/enterprise/servers/oneview5.0/cicf/en/index.html#s_fabrics-vlan-pool-about-cic.html&amp;nbsp;" target="_blank"&gt;https://techlibrary.hpe.com/docs/enterprise/servers/oneview5.0/cicf/en/index.html#s_fabrics-vlan-pool-about-cic.html&amp;nbsp;&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Aug 2020 10:09:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-oneview/modify-oneview-ip-range/m-p/7098005#M5523</guid>
      <dc:creator>AmRa</dc:creator>
      <dc:date>2020-08-12T10:09:13Z</dc:date>
    </item>
    <item>
      <title>Re: Modify OneView IP Range</title>
      <link>https://community.hpe.com/t5/hpe-oneview/modify-oneview-ip-range/m-p/7098050#M5526</link>
      <description>&lt;P&gt;IP Address Pool Subnets are tied to a singular Ethernet Network.&amp;nbsp; It cannot be associated with multiple Ethernet Networks.&amp;nbsp; As an Ethernet Network is the same as a VLAN.&amp;nbsp; If you have run out of addresses within the defined range, you can add more ranges to the Subnet.&amp;nbsp; However, if your range consumes the entirity of the subnet, you will need to create a new subnet with a new range, and that means another Ethernet Network with a different VLAN.&amp;nbsp; Once the subnet mask has been set to the address pool subnet, it cannot be modified.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Aug 2020 14:41:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-oneview/modify-oneview-ip-range/m-p/7098050#M5526</guid>
      <dc:creator>ChrisLynch</dc:creator>
      <dc:date>2020-08-12T14:41:53Z</dc:date>
    </item>
    <item>
      <title>Re: Modify OneView IP Range</title>
      <link>https://community.hpe.com/t5/hpe-oneview/modify-oneview-ip-range/m-p/7121219#M6057</link>
      <description>&lt;P&gt;The Management network associated with the orignal IP subnet pool is tagged. Does the FLM mangement ports have to be tagged on the management switch as well?&amp;nbsp; Will that allow a new IP subnet pool to be created and associated with another new management network and also tagged on the FLM management switch ports?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Feb 2021 00:06:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-oneview/modify-oneview-ip-range/m-p/7121219#M6057</guid>
      <dc:creator>Brian Peterkin</dc:creator>
      <dc:date>2021-02-15T00:06:06Z</dc:date>
    </item>
    <item>
      <title>Re: Modify OneView IP Range</title>
      <link>https://community.hpe.com/t5/hpe-oneview/modify-oneview-ip-range/m-p/7121681#M6066</link>
      <description>&lt;P&gt;The FLM and Composer does not support customer VLAN tagging.&amp;nbsp; So the switch port must either be in Access Port mode, or the Default/Native VLAN ID for an 802.1q Trunk Port must be the management VLAN assigned to the subnet in question.&amp;nbsp; We do not support VLAN tagging like c-Class Onboard Administrator used to.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Feb 2021 23:02:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-oneview/modify-oneview-ip-range/m-p/7121681#M6066</guid>
      <dc:creator>ChrisLynch</dc:creator>
      <dc:date>2021-02-17T23:02:22Z</dc:date>
    </item>
  </channel>
</rss>

