<?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: Setting up a secondary IP address range in Network Architecture &amp; Design</title>
    <link>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14661#M2065</link>
    <description>Hi Jeremy,&lt;BR /&gt;
working with secondary IP addresses on a router interface is possible but alway a nasty workaround.&lt;BR /&gt;
&lt;BR /&gt;
Regards&lt;BR /&gt;
André</description>
    <pubDate>Tue, 25 Oct 2016 19:57:00 GMT</pubDate>
    <dc:creator>André_Herkenrat</dc:creator>
    <dc:date>2016-10-25T19:57:00Z</dc:date>
    <item>
      <title>Setting up a secondary IP address range</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14660#M2064</link>
      <description>We are running out of IP's in our DHCP range and do not have 'room' in our IPv4 to enlarge the current scope. Can you setup a secondary IP range to use DHCP?&lt;BR /&gt;
&lt;BR /&gt;
Like so:&lt;BR /&gt;
&lt;BR /&gt;
interface vlan.0.100&lt;BR /&gt;
ip address 10.10.1.0 255.255.255.0 primary&lt;BR /&gt;
ip address 10.10.7.0 255.255.255.0 secondary&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 25 Oct 2016 19:54:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14660#M2064</guid>
      <dc:creator>Jeremy_Bullock</dc:creator>
      <dc:date>2016-10-25T19:54:00Z</dc:date>
    </item>
    <item>
      <title>RE: Setting up a secondary IP address range</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14661#M2065</link>
      <description>Hi Jeremy,&lt;BR /&gt;
working with secondary IP addresses on a router interface is possible but alway a nasty workaround.&lt;BR /&gt;
&lt;BR /&gt;
Regards&lt;BR /&gt;
André</description>
      <pubDate>Tue, 25 Oct 2016 19:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14661#M2065</guid>
      <dc:creator>André_Herkenrat</dc:creator>
      <dc:date>2016-10-25T19:57:00Z</dc:date>
    </item>
    <item>
      <title>RE: Setting up a secondary IP address range</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14662#M2066</link>
      <description>Why 'nasty'?</description>
      <pubDate>Tue, 25 Oct 2016 19:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14662#M2066</guid>
      <dc:creator>Jeremy_Bullock</dc:creator>
      <dc:date>2016-10-25T19:57:00Z</dc:date>
    </item>
    <item>
      <title>RE: Setting up a secondary IP address range</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14663#M2067</link>
      <description>Both subnets are broadcastdomains - usually broadcastdomains are separated by routers - you plan to connect them with a bridge.&lt;BR /&gt;
&lt;BR /&gt;
You better create a second vlan with its own IP range and use tagging on the uplinks.&lt;BR /&gt;
&lt;BR /&gt;
/André</description>
      <pubDate>Tue, 25 Oct 2016 19:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14663#M2067</guid>
      <dc:creator>André_Herkenrat</dc:creator>
      <dc:date>2016-10-25T19:57:00Z</dc:date>
    </item>
    <item>
      <title>RE: Setting up a secondary IP address range</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14664#M2068</link>
      <description>I am not sure I would use the adjective "nasty".  Adding the secondary address with another class c address is not much different than backing off the mask by 1 bit.  That said I understand and agree with the sentiment of keeping broadcast domains as small a possible.&lt;BR /&gt;</description>
      <pubDate>Tue, 25 Oct 2016 19:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14664#M2068</guid>
      <dc:creator>Daniel_Coughlin</dc:creator>
      <dc:date>2016-10-25T19:57:00Z</dc:date>
    </item>
    <item>
      <title>RE: Setting up a secondary IP address range</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14665#M2069</link>
      <description>When it stops with the first secondary IP - I agree. But you are opening the door to a bad style of networking (I have customers with 12 secondary IPs in a subnet). Creating a second vlan shouldn't be a problem.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 25 Oct 2016 19:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14665#M2069</guid>
      <dc:creator>André_Herkenrat</dc:creator>
      <dc:date>2016-10-25T19:57:00Z</dc:date>
    </item>
    <item>
      <title>RE: Setting up a secondary IP address range</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14666#M2070</link>
      <description>Another thing is the DHCP request - I assume DHCP relay will be used,&lt;BR /&gt;
In that case the router will send out 2 requests for the different scopes and the first reply will decide which IP (subnet) is used by the client.&lt;BR /&gt;
&lt;BR /&gt;
In my opinion it's better to configure a new VLAN instead of using a secondary IP.</description>
      <pubDate>Tue, 25 Oct 2016 19:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14666#M2070</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2016-10-25T19:57:00Z</dc:date>
    </item>
    <item>
      <title>RE: Setting up a secondary IP address range</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14667#M2071</link>
      <description>Your DHCP server will need to be configured to show the different subnets are actually a part of the same network.  Our BlueCat DHCP servers are able to do that.</description>
      <pubDate>Tue, 25 Oct 2016 19:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14667#M2071</guid>
      <dc:creator>Curtis_Parish1</dc:creator>
      <dc:date>2016-10-25T19:57:00Z</dc:date>
    </item>
    <item>
      <title>RE: Setting up a secondary IP address range</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14668#M2072</link>
      <description>Hi Jeremy,&lt;BR /&gt;
&lt;BR /&gt;
you can add a secondary IP address to a VLAN:&lt;BR /&gt;
configure vlan &amp;lt;&lt;I&gt;NAME&lt;/I&gt;&amp;gt; add secondary-ipaddress &amp;lt;&lt;I&gt;ADDRESS&lt;/I&gt;&amp;gt;  You can configure the BOOTP Relay service to include the secondary address(es):&lt;BR /&gt;
configure bootprelay ipv4 include-secondary  Br,&lt;BR /&gt;
Erik</description>
      <pubDate>Wed, 26 Oct 2016 12:42:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/setting-up-a-secondary-ip-address-range/m-p/14668#M2072</guid>
      <dc:creator>Erik_Auerswald</dc:creator>
      <dc:date>2016-10-26T12:42:00Z</dc:date>
    </item>
  </channel>
</rss>

