<?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: DHCP Relay Bug? in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234696#M14940</link>
    <description>hi jason &lt;BR /&gt;as for me your problem cause routing&lt;BR /&gt;&lt;BR /&gt;you can return k12xx software &lt;BR /&gt;if continue issue plese talk to me&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;not:&lt;BR /&gt;vlan 1 not managemet vlan on your switch &lt;BR /&gt;only name managemet vlan &lt;BR /&gt;&lt;BR /&gt;managemet vlan for security manage&lt;BR /&gt;managemet vlan declare on switch with &lt;BR /&gt; &amp;lt;(config)#managemet-vlan 1 &amp;gt;command and unable routing managemet vlan &lt;BR /&gt;&lt;BR /&gt;I pass over in sh tech management-vlan 1 command</description>
    <pubDate>Thu, 17 Jul 2008 11:24:47 GMT</pubDate>
    <dc:creator>cenk sasmaztin</dc:creator>
    <dc:date>2008-07-17T11:24:47Z</dc:date>
    <item>
      <title>DHCP Relay Bug?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234687#M14931</link>
      <description>Are there any known issues with DHCP Relay? We're currently migrating to 8200s in our core and have started to experience some very strange issues with some vlans and clients unable to obtain DHCP addresses. Yet other vlans that use the same physical paths are working fine.&lt;BR /&gt;&lt;BR /&gt;If I issue 'show dhcp-relay' no stats are showing for client requests and server responses. All in all, very strange.</description>
      <pubDate>Wed, 16 Jul 2008 07:14:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234687#M14931</guid>
      <dc:creator>Jason Scott</dc:creator>
      <dc:date>2008-07-16T07:14:27Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Relay Bug?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234688#M14932</link>
      <description>hi Jason &lt;BR /&gt;please send me sh tech command &lt;BR /&gt;&lt;BR /&gt;cenk</description>
      <pubDate>Wed, 16 Jul 2008 12:47:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234688#M14932</guid>
      <dc:creator>cenk sasmaztin</dc:creator>
      <dc:date>2008-07-16T12:47:15Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Relay Bug?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234689#M14933</link>
      <description>Thanks, did you want show tech or show conf? The tech file is pretty big :)&lt;BR /&gt;&lt;BR /&gt;I've tried adding the dhcp relay option 82 append command and we are now seeing statistics under 'show dhcp relay'. I'm going to test client dhcp in the next hour.</description>
      <pubDate>Wed, 16 Jul 2008 13:03:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234689#M14933</guid>
      <dc:creator>Jason Scott</dc:creator>
      <dc:date>2008-07-16T13:03:08Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Relay Bug?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234690#M14934</link>
      <description>Here is show tech.</description>
      <pubDate>Wed, 16 Jul 2008 13:22:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234690#M14934</guid>
      <dc:creator>Jason Scott</dc:creator>
      <dc:date>2008-07-16T13:22:09Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Relay Bug?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234691#M14935</link>
      <description>hi Jason,&lt;BR /&gt;several interfaces have  ip-addresses, but there is none in the same subnet (10.177.20.0) as the ip-helper (10.177.20.19)!&lt;BR /&gt;so the dhcp-server has no return path!&lt;BR /&gt;&lt;BR /&gt;   ip address 10.177.25.254 255.255.255.0 &lt;BR /&gt;   ip address 10.177.12.254 255.255.255.0 &lt;BR /&gt;   ip address 10.177.10.254 255.255.255.0 &lt;BR /&gt;   ip address 10.177.11.254 255.255.255.0 &lt;BR /&gt;   ip address 10.177.17.253 255.255.255.0 &lt;BR /&gt;   ip address 10.177.13.254 255.255.255.0 &lt;BR /&gt;   ip address 10.177.14.254 255.255.255.0 &lt;BR /&gt;   ip address 10.177.19.254 255.255.255.0 &lt;BR /&gt;   ip address 10.177.15.254 255.255.255.0 &lt;BR /&gt;   ip address 10.177.16.126 255.255.255.128 &lt;BR /&gt;   ip address 10.177.18.254 255.255.255.0 &lt;BR /&gt;   ip address 10.177.7.62 255.255.255.192 &lt;BR /&gt;   ip address 10.177.27.254 255.255.255.0 &lt;BR /&gt;&lt;BR /&gt;regards , Pieter</description>
      <pubDate>Thu, 17 Jul 2008 06:07:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234691#M14935</guid>
      <dc:creator>Pieter 't Hart</dc:creator>
      <dc:date>2008-07-17T06:07:10Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Relay Bug?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234692#M14936</link>
      <description>Hi, its misleading as you're only seeing the configuration from one of our 3 core routers. The layer 3 interface for the DHCP server vlan (20) resides on another router, with vlan 20 spanned at layer 2 across the uplinks.&lt;BR /&gt;&lt;BR /&gt;If I take a client that is having dhcp issues and give it a static ip address I have full ip connectivity to the dhcp server and other subnets. This indicates routing is ok.</description>
      <pubDate>Thu, 17 Jul 2008 06:27:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234692#M14936</guid>
      <dc:creator>Jason Scott</dc:creator>
      <dc:date>2008-07-17T06:27:11Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Relay Bug?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234693#M14937</link>
      <description>try setting speed and duplex of the switchport as fixed.&lt;BR /&gt;it may be the port still negotiates this while pxe allready sent its dhcp request wich times out.</description>
      <pubDate>Thu, 17 Jul 2008 06:31:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234693#M14937</guid>
      <dc:creator>Pieter 't Hart</dc:creator>
      <dc:date>2008-07-17T06:31:42Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Relay Bug?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234694#M14938</link>
      <description>hi Jason&lt;BR /&gt;please test for me &lt;BR /&gt;&lt;BR /&gt;one pc connect on vlan 1 (port A1)and assign ip address on pc&lt;BR /&gt;&lt;BR /&gt;ip address       10.5.1.22&lt;BR /&gt;default gateway  255.255.255.0&lt;BR /&gt;subnet mask      10.5.1.2 &lt;BR /&gt;&lt;BR /&gt;after you make ping to 10.177.20.19 on pc &lt;BR /&gt;&lt;BR /&gt;if unsuccessfull pinging you can run on pc traceroute command to 10.177.20.19 &lt;BR /&gt;&lt;BR /&gt;and please say me result&lt;BR /&gt;&lt;BR /&gt;cenk &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Jul 2008 09:10:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234694#M14938</guid>
      <dc:creator>cenk sasmaztin</dc:creator>
      <dc:date>2008-07-17T09:10:03Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Relay Bug?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234695#M14939</link>
      <description>Unfortunately this is a production network so some testing is difficult in hours. Vlan 10.5.1.x is our management vlan for switch ip addresses.&lt;BR /&gt;&lt;BR /&gt;We've been speaking with our support at HP on this as well and they believe a bug in firmware 13.09 may be the cause and have advised us to revert back to v12.xx.</description>
      <pubDate>Thu, 17 Jul 2008 09:26:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234695#M14939</guid>
      <dc:creator>Jason Scott</dc:creator>
      <dc:date>2008-07-17T09:26:39Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Relay Bug?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234696#M14940</link>
      <description>hi jason &lt;BR /&gt;as for me your problem cause routing&lt;BR /&gt;&lt;BR /&gt;you can return k12xx software &lt;BR /&gt;if continue issue plese talk to me&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;not:&lt;BR /&gt;vlan 1 not managemet vlan on your switch &lt;BR /&gt;only name managemet vlan &lt;BR /&gt;&lt;BR /&gt;managemet vlan for security manage&lt;BR /&gt;managemet vlan declare on switch with &lt;BR /&gt; &amp;lt;(config)#managemet-vlan 1 &amp;gt;command and unable routing managemet vlan &lt;BR /&gt;&lt;BR /&gt;I pass over in sh tech management-vlan 1 command</description>
      <pubDate>Thu, 17 Jul 2008 11:24:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234696#M14940</guid>
      <dc:creator>cenk sasmaztin</dc:creator>
      <dc:date>2008-07-17T11:24:47Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Relay Bug?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234697#M14941</link>
      <description>Thanks Cenk. I realised this recently but I'm not unsure of the impact were we to enable the management-vlan command. OSPF utilises addresses in vlan 1 for routing.</description>
      <pubDate>Thu, 17 Jul 2008 11:36:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234697#M14941</guid>
      <dc:creator>Jason Scott</dc:creator>
      <dc:date>2008-07-17T11:36:55Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Relay Bug?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234698#M14942</link>
      <description>hi Jason &lt;BR /&gt;so please erase management-vlan 1 command on switch &lt;BR /&gt;&lt;BR /&gt;and please make my ping and tracert test&lt;BR /&gt;&lt;BR /&gt;cenk&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Jul 2008 12:05:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234698#M14942</guid>
      <dc:creator>cenk sasmaztin</dc:creator>
      <dc:date>2008-07-17T12:05:53Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Relay Bug?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234699#M14943</link>
      <description>Hiya,&lt;BR /&gt;&lt;BR /&gt;I can do this on any of our edge switches as they all have 10.5.1.x addresses. They can ping 10.177.20.19 fine. Traceroute output is:&lt;BR /&gt;&lt;BR /&gt;L5NR_2626PWR.1# trace 10.177.20.19&lt;BR /&gt;traceroute to 10.177.20.19 ,&lt;BR /&gt;              1 hop min, 30 hops max, 5 sec. timeout, 3 probes&lt;BR /&gt; 1 10.5.1.1               0 ms       0 ms       0 ms&lt;BR /&gt; 2 10.177.20.19           0 ms       0 ms       0 ms</description>
      <pubDate>Thu, 17 Jul 2008 12:27:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234699#M14943</guid>
      <dc:creator>Jason Scott</dc:creator>
      <dc:date>2008-07-17T12:27:06Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Relay Bug?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234700#M14944</link>
      <description>are continue same issue..</description>
      <pubDate>Thu, 17 Jul 2008 13:14:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234700#M14944</guid>
      <dc:creator>cenk sasmaztin</dc:creator>
      <dc:date>2008-07-17T13:14:47Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Relay Bug?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234701#M14945</link>
      <description>Just before i go further can you tell me what vlans are bugging ?</description>
      <pubDate>Fri, 18 Jul 2008 07:06:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234701#M14945</guid>
      <dc:creator>Evert Goor</dc:creator>
      <dc:date>2008-07-18T07:06:05Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP Relay Bug?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234702#M14946</link>
      <description>Well that's the strange thing about this problem. Its random and sometimes clients are ok and sometimes not. Currently we've got issues with vlan 67 and 31.&lt;BR /&gt;&lt;BR /&gt;Another development has been that some clients are having difficulty properly resolving DNS names, but testing on other clients in the same subnet works! Our of desperation I enabled ip directed broadcasts and those clients with problems immediately resolved the names. Based on what I know of this command however I'm not sure why it would fix it.&lt;BR /&gt;&lt;BR /&gt;I don't think our issues our resolved with that one change. There's something else going on that we can't track down.</description>
      <pubDate>Fri, 18 Jul 2008 14:11:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/dhcp-relay-bug/m-p/4234702#M14946</guid>
      <dc:creator>Jason Scott</dc:creator>
      <dc:date>2008-07-18T14:11:24Z</dc:date>
    </item>
  </channel>
</rss>

