<?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: One DHCP server for 2 VLANs scenario in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/6043005#M31567</link>
    <description>&lt;P&gt;Dear Jeff,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am having some problems with a Microsoft AD/DHCP server and a switch 3com 4800g.&lt;/P&gt;&lt;P&gt;In almost every lab I looked at in the configuration guide, it is assumed that L3 switch is going to&lt;/P&gt;&lt;P&gt;work as a dhcp server as well. But, a lot of companies use Microsoft AD which by default works as a DHCP and DNS server, that is my case.&lt;/P&gt;&lt;P&gt;So, my question to you is, do you have an idea as to how to use the relay capability of a 4800g switch&lt;/P&gt;&lt;P&gt;in order to have at least 3 vlans getting the DHCP addresses from a Microsoft AD DHCP server connected to vlan2?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I attached an image of what I am trying to set up. I have configured the IPs of the interfaces,&lt;/P&gt;&lt;P&gt;the default route and the relay on port 2. I have also set port 2 as trunk in order to have all traffic&lt;/P&gt;&lt;P&gt;from all other vlans go through it.&lt;/P&gt;&lt;P&gt;I am able to ping each individual interface with a host in the same network. Except the trunk interface (port 2).&lt;/P&gt;&lt;P&gt;I cannot reach any other interface but the one I am connected to and as a result I cannot get an IP address&lt;/P&gt;&lt;P&gt;from the AD. Anything you can share would be helpful.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Fri, 26 Apr 2013 17:41:27 GMT</pubDate>
    <dc:creator>jadielmota</dc:creator>
    <dc:date>2013-04-26T17:41:27Z</dc:date>
    <item>
      <title>One DHCP server for 2 VLANs scenario</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/4436730#M18725</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;I know that we can use the one DHCP server for VLANs using the hp network feature (dhcp relay) but if i need to assign 2 different subnets for these 2 vlans, how can the dhcp server understand what subnet to use when it receives a request for the network?&lt;BR /&gt;&lt;BR /&gt;i.e. Assume a dhcp server in vlan 1&lt;BR /&gt;configured for 2 subnets say 192.168.1.0/24 and 192.168.2.0/24&lt;BR /&gt;when a client from vlan 1 requests an ip address, then the dhcp server replies with an ip address from the first subnet e.g. 192.168.1.1/24 but when a client in the second vlan sends a request, the switch sends the request to the dhcp server in vlan 1, but how will the dhcp server know that it should reply with an ip address in the second subnet not from the first?</description>
      <pubDate>Wed, 10 Jun 2009 13:16:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/4436730#M18725</guid>
      <dc:creator>abdullah.ali</dc:creator>
      <dc:date>2009-06-10T13:16:22Z</dc:date>
    </item>
    <item>
      <title>Re: One DHCP server for 2 VLANs scenario</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/4436731#M18726</link>
      <description>&lt;BR /&gt;if the dhcp srvr is connected to vlan1, then in vlan2 you need the following:&lt;BR /&gt;&lt;BR /&gt;switch (config)# 'vlan 2'&lt;BR /&gt;switch (vlan 2)# 'ip helper-address &lt;IP-OF-DHCP-SRVR&gt;'&lt;BR /&gt;&lt;BR /&gt;then, when the dhcp broadcast is received by the switch from the client, it "relays" the dhcp broadcast over to vlan1, and sets an option to say it was sourced from network 192.168.2.0/24, and then the dhcp srvr get the dhcp request and looks in its scopes and sees that it has a scope for that subnet, and provides a client ip fro that scope/subnet, sends it back to the switch, the switch "relays" it back to vlan2 destined for the mac addr of the client...&lt;BR /&gt;&lt;BR /&gt;hth...jeff&lt;/IP-OF-DHCP-SRVR&gt;</description>
      <pubDate>Wed, 10 Jun 2009 17:23:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/4436731#M18726</guid>
      <dc:creator>Jeff Carrell</dc:creator>
      <dc:date>2009-06-10T17:23:04Z</dc:date>
    </item>
    <item>
      <title>Re: One DHCP server for 2 VLANs scenario</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/4436732#M18727</link>
      <description>hi abdullah&lt;BR /&gt;dhcp server take to client dhcp request message with broadcast &lt;BR /&gt;and dhcp server response to client with unicast &lt;BR /&gt;&lt;BR /&gt;if dhcp request message coming on same broadcast domain to dhcp server &lt;BR /&gt;&lt;BR /&gt;dhcp server assign ip address own network scobe with unicast to client  &lt;BR /&gt;&lt;BR /&gt;if dhcp request message coming other broadcast domain (other vlan ,other wide site etc.)&lt;BR /&gt;dhcp server see other side default gateway address  in request packet &lt;BR /&gt;and send that network  scobe ip address to client with unicast &lt;BR /&gt;&lt;BR /&gt;you can see with wireshark &lt;BR /&gt;</description>
      <pubDate>Wed, 10 Jun 2009 17:27:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/4436732#M18727</guid>
      <dc:creator>cenk sasmaztin</dc:creator>
      <dc:date>2009-06-10T17:27:26Z</dc:date>
    </item>
    <item>
      <title>Re: One DHCP server for 2 VLANs scenario</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/4436733#M18728</link>
      <description>&lt;A href="http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1240414" target="_blank"&gt;http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1240414&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;please read</description>
      <pubDate>Wed, 10 Jun 2009 17:30:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/4436733#M18728</guid>
      <dc:creator>cenk sasmaztin</dc:creator>
      <dc:date>2009-06-10T17:30:58Z</dc:date>
    </item>
    <item>
      <title>Re: One DHCP server for 2 VLANs scenario</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/4436734#M18729</link>
      <description>Thanks all for your reply.&lt;BR /&gt;Jeff Carrell, so is the key point here to assign an ip address for the VLAN in the same subnet I wish to have an IP Address in?&lt;BR /&gt;</description>
      <pubDate>Thu, 11 Jun 2009 04:40:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/4436734#M18729</guid>
      <dc:creator>abdullah.ali</dc:creator>
      <dc:date>2009-06-11T04:40:15Z</dc:date>
    </item>
    <item>
      <title>Re: One DHCP server for 2 VLANs scenario</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/4436735#M18730</link>
      <description>correct...example:&lt;BR /&gt;&lt;BR /&gt;vlan 1 ip address 192.168.1.1/24&lt;BR /&gt;&lt;BR /&gt;vlan 2 ip address 192.168.2.1/24&lt;BR /&gt;vlan 2 ip helper-address 192.168.1.x [dhcp srvr ip in vlan1]&lt;BR /&gt;&lt;BR /&gt;and you also need 'ip routing' enabled if you want devices on each vlan to access the other vlan...&lt;BR /&gt;&lt;BR /&gt;then the vlan ip addresses on thw switch are your default gateways...&lt;BR /&gt;&lt;BR /&gt;scopes in dhcp look like:&lt;BR /&gt;&lt;BR /&gt;name: vlan 1&lt;BR /&gt;subnet: 192.168.1.0/24&lt;BR /&gt;pool: 192.1681..100-192.168.1.200&lt;BR /&gt;def g/w: 192.168.1.1&lt;BR /&gt;dns: 192.168.1.x&lt;BR /&gt;domain: yourdomain.com&lt;BR /&gt;&lt;BR /&gt;name: vlan 2&lt;BR /&gt;subnet: 192.168.2.0/24&lt;BR /&gt;pool: 192.168.2.100-192.168.2.200&lt;BR /&gt;def g/w: 192.168.2.1&lt;BR /&gt;dns: 192.168.1.x&lt;BR /&gt;domain: yourdomain.com&lt;BR /&gt;&lt;BR /&gt;hth...jeff</description>
      <pubDate>Thu, 11 Jun 2009 12:20:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/4436735#M18730</guid>
      <dc:creator>Jeff Carrell</dc:creator>
      <dc:date>2009-06-11T12:20:35Z</dc:date>
    </item>
    <item>
      <title>Re: One DHCP server for 2 VLANs scenario</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/6043005#M31567</link>
      <description>&lt;P&gt;Dear Jeff,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am having some problems with a Microsoft AD/DHCP server and a switch 3com 4800g.&lt;/P&gt;&lt;P&gt;In almost every lab I looked at in the configuration guide, it is assumed that L3 switch is going to&lt;/P&gt;&lt;P&gt;work as a dhcp server as well. But, a lot of companies use Microsoft AD which by default works as a DHCP and DNS server, that is my case.&lt;/P&gt;&lt;P&gt;So, my question to you is, do you have an idea as to how to use the relay capability of a 4800g switch&lt;/P&gt;&lt;P&gt;in order to have at least 3 vlans getting the DHCP addresses from a Microsoft AD DHCP server connected to vlan2?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I attached an image of what I am trying to set up. I have configured the IPs of the interfaces,&lt;/P&gt;&lt;P&gt;the default route and the relay on port 2. I have also set port 2 as trunk in order to have all traffic&lt;/P&gt;&lt;P&gt;from all other vlans go through it.&lt;/P&gt;&lt;P&gt;I am able to ping each individual interface with a host in the same network. Except the trunk interface (port 2).&lt;/P&gt;&lt;P&gt;I cannot reach any other interface but the one I am connected to and as a result I cannot get an IP address&lt;/P&gt;&lt;P&gt;from the AD. Anything you can share would be helpful.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2013 17:41:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/6043005#M31567</guid>
      <dc:creator>jadielmota</dc:creator>
      <dc:date>2013-04-26T17:41:27Z</dc:date>
    </item>
    <item>
      <title>Re: One DHCP server for 2 VLANs scenario</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/6048625#M31568</link>
      <description>&lt;P&gt;Is port 2 your connection to your server?&lt;/P&gt;&lt;P&gt;That shouldn't be a trunk. It should be an access port in the VLAN the server belongs to.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To summarise: you have 4 networks:&lt;/P&gt;&lt;P&gt;SERVERNET: 10.7.1.0&amp;nbsp;&amp;nbsp; = VLAN1&lt;/P&gt;&lt;P&gt;NET_A:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.7.8.0&amp;nbsp;&amp;nbsp; = VLAN8&lt;/P&gt;&lt;P&gt;NET_B:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.7.16.0 = VLAN16&lt;/P&gt;&lt;P&gt;NET_C:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.7.32.0 &amp;nbsp; = VLAN32&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Each network is connected to an access port on the 4800 switch that is in the correct VLAN, ie,&lt;/P&gt;&lt;P&gt;Port2 is an access port in VLAN1&lt;/P&gt;&lt;P&gt;Port3 is an access port in VLAN32&lt;/P&gt;&lt;P&gt;Port4 is an access port in VLAN16&lt;/P&gt;&lt;P&gt;Port5 is an access port in VLAN8&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On the 4800 switch, you have 4 VLAN interfaces configured:&lt;/P&gt;&lt;P&gt;VLAN1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; --&amp;nbsp; 10.7.1.1&lt;/P&gt;&lt;P&gt;VLAN8&amp;nbsp;&amp;nbsp; &amp;nbsp; --&amp;nbsp; 10.7.8.1&lt;/P&gt;&lt;P&gt;VLAN16&amp;nbsp; --&amp;nbsp; 10.7.16.1&lt;/P&gt;&lt;P&gt;VLAN32&amp;nbsp; --&amp;nbsp; 10.7.32.1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On the last 3 VLAN interfaces, you have an "IP Helper" address configured, pointing at 10.7.1.6.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 May 2013 02:16:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/one-dhcp-server-for-2-vlans-scenario/m-p/6048625#M31568</guid>
      <dc:creator>Vince_Whirlwind</dc:creator>
      <dc:date>2013-05-02T02:16:47Z</dc:date>
    </item>
  </channel>
</rss>

