<?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: VLAN issue with latest NIC Driver in HPE ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068083#M69285</link>
    <description>Hello.&lt;BR /&gt;&lt;BR /&gt;Exactly the same issue with ProLiant BL20p G3. The workaround of disable-enable the interface works fine...until you reboot the server :-(&lt;BR /&gt;&lt;BR /&gt;I have tried to disable TOE, but it seems that TOE is only availble if you have Teaming, not only VLAN's. Is it right?&lt;BR /&gt;&lt;BR /&gt;Next I will downgrade the driver.&lt;BR /&gt;&lt;BR /&gt;Regards.&lt;BR /&gt;</description>
    <pubDate>Mon, 17 Sep 2007 05:43:33 GMT</pubDate>
    <dc:creator>Carlos Hernandez Barea</dc:creator>
    <dc:date>2007-09-17T05:43:33Z</dc:date>
    <item>
      <title>VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068065#M69267</link>
      <description>We currently have multiple VLANS setup on a Cisco 6500 and a DL360 g4p. When we upgrade to the latest support pack (7.90a) with firmware some of the VLANs are not accessible. We've tried this in two different environments and we get the same issue. The NIC model is a NC7782.&lt;BR /&gt;&lt;BR /&gt;Has anyone seen this or does anyone have any documentation they could point me to on what may have changed on the latest NIC driver VLAN config wise?</description>
      <pubDate>Mon, 10 Sep 2007 09:03:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068065#M69267</guid>
      <dc:creator>Technology Helpdesk</dc:creator>
      <dc:date>2007-09-10T09:03:36Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068066#M69268</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;Try updating the NIC firmware ALONE,&lt;BR /&gt;then, upgrade the Drivers.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=PSD_CO040408_CW01" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=PSD_CO040408_CW01&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;{All this is after PSP 7.90}&lt;BR /&gt;&lt;BR /&gt;Also, Disabling TOE Helps resolve MANY issues in NIC performance/Teaming Issues.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1159651" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1159651&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;James.</description>
      <pubDate>Mon, 10 Sep 2007 10:38:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068066#M69268</guid>
      <dc:creator>James ~ Happy Dude</dc:creator>
      <dc:date>2007-09-10T10:38:46Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068067#M69269</link>
      <description>James,&lt;BR /&gt;&lt;BR /&gt;Thanks for the quick response. I don't see anywhere for me to disable the TCP Offload Engine under the NCU. Is there some place else or a command I should use?&lt;BR /&gt;&lt;BR /&gt;Thanks again,&lt;BR /&gt;&lt;BR /&gt;Travis</description>
      <pubDate>Mon, 10 Sep 2007 11:30:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068067#M69269</guid>
      <dc:creator>Technology Helpdesk</dc:creator>
      <dc:date>2007-09-10T11:30:24Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068068#M69270</link>
      <description>Hello Travis,&lt;BR /&gt;&lt;BR /&gt;use the Command :&lt;BR /&gt;&lt;BR /&gt;Netsh int ip set chimney DISABLED &lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;James.</description>
      <pubDate>Mon, 10 Sep 2007 12:22:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068068#M69270</guid>
      <dc:creator>James ~ Happy Dude</dc:creator>
      <dc:date>2007-09-10T12:22:19Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068069#M69271</link>
      <description>Also refer :&lt;BR /&gt;&lt;A href="http://support.microsoft.com/default.aspx?scid=kb;EN-US;927695" target="_blank"&gt;http://support.microsoft.com/default.aspx?scid=kb;EN-US;927695&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;For Disabling RSS;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;James.</description>
      <pubDate>Mon, 10 Sep 2007 12:24:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068069#M69271</guid>
      <dc:creator>James ~ Happy Dude</dc:creator>
      <dc:date>2007-09-10T12:24:41Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068070#M69272</link>
      <description>James,&lt;BR /&gt;&lt;BR /&gt;Is there anything else I can try? I've tried both of those and I'm still not able to access some of the vlans.&lt;BR /&gt;&lt;BR /&gt;Thanks again for the help.&lt;BR /&gt;&lt;BR /&gt;Travis</description>
      <pubDate>Mon, 10 Sep 2007 13:07:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068070#M69272</guid>
      <dc:creator>Technology Helpdesk</dc:creator>
      <dc:date>2007-09-10T13:07:27Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068071#M69273</link>
      <description>Reading this Again... "When we upgrade to the latest support pack (7.90a) with firmware some of the VLANs are not accessible." &lt;BR /&gt;&lt;BR /&gt;I hope U have Updated the FIRMWARE first, then the Latest Drivers; Then Apply the Latest NIC Teaming Software .. if any;&lt;BR /&gt;&lt;BR /&gt;Which OS R u trying this ?&lt;BR /&gt;&lt;A href="http://h18023.www1.hp.com/support/files/networking/us/download/24634.html" target="_blank"&gt;http://h18023.www1.hp.com/support/files/networking/us/download/24634.html&lt;/A&gt;&lt;BR /&gt;Or Go through the Documentation At&lt;BR /&gt;&lt;A href="http://h18023.www1.hp.com/support/files/server/us/download/19958.html" target="_blank"&gt;http://h18023.www1.hp.com/support/files/server/us/download/19958.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;James.</description>
      <pubDate>Mon, 10 Sep 2007 13:22:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068071#M69273</guid>
      <dc:creator>James ~ Happy Dude</dc:creator>
      <dc:date>2007-09-10T13:22:26Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068072#M69274</link>
      <description>James,&lt;BR /&gt;&lt;BR /&gt;I applied the firmware and then the support pack which applies the latest drivers and NCU. This is for Windows 2003 R2 SP2 and I know that HP has had issues with SP2 and their NIC drivers.</description>
      <pubDate>Mon, 10 Sep 2007 13:28:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068072#M69274</guid>
      <dc:creator>Technology Helpdesk</dc:creator>
      <dc:date>2007-09-10T13:28:26Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068073#M69275</link>
      <description>Yes Travis, PSP does installs them;&lt;BR /&gt;However, It may be worth to install them separately; I have seen cases when Applying them separately solves issue; U might wanna try it too, in case u haven't :&lt;BR /&gt;&lt;BR /&gt;NCU&lt;BR /&gt;&lt;A href="http://h18023.www1.hp.com/support/files/server/us/download/27384.html" target="_blank"&gt;http://h18023.www1.hp.com/support/files/server/us/download/27384.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Broadcom drivers&lt;BR /&gt;&lt;A href="http://h18023.www1.hp.com/support/files/networking/us/download/27387.html" target="_blank"&gt;http://h18023.www1.hp.com/support/files/networking/us/download/27387.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;James.</description>
      <pubDate>Mon, 10 Sep 2007 13:39:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068073#M69275</guid>
      <dc:creator>James ~ Happy Dude</dc:creator>
      <dc:date>2007-09-10T13:39:05Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068074#M69276</link>
      <description>Hi &lt;BR /&gt;&lt;BR /&gt;Try this old driver and hopes it works &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h18023.www1.hp.com/support/files/server/us/download/25512.html" target="_blank"&gt;http://h18023.www1.hp.com/support/files/server/us/download/25512.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers :)</description>
      <pubDate>Mon, 10 Sep 2007 16:16:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068074#M69276</guid>
      <dc:creator>HP_Sammy</dc:creator>
      <dc:date>2007-09-10T16:16:27Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068075#M69277</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;if the configuration is changed, you will be unable to connect to the VLANS with all tricks you make. I think that the driver changed the config of the NIC, not the VLAN, since it don't have acces to the VLAN(Switch). You can try to downgrade the driver and see if the problem is resolved.&lt;BR /&gt;If so , then there is 99% problem with the driver/his relation to the Cicso switch and you can open an elevation at HP suport...&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Pac</description>
      <pubDate>Tue, 11 Sep 2007 12:19:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068075#M69277</guid>
      <dc:creator>Blazhev_1</dc:creator>
      <dc:date>2007-09-11T12:19:55Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068076#M69278</link>
      <description>DL380 G4&lt;BR /&gt;&lt;BR /&gt;Windows 2003 X64 installed with latest SmartStart CD (7.90)&lt;BR /&gt;&lt;BR /&gt;When I add a Vlan to NC7782 with HP Network Utility I get an interface with:&lt;BR /&gt;&lt;BR /&gt;MAC Physical Address: 00-00-00-00-00-00&lt;BR /&gt;&lt;BR /&gt;and the server will comunicate with nobody !&lt;BR /&gt;&lt;BR /&gt;can you tell me how to resolve this ?!?!?&lt;BR /&gt;&lt;BR /&gt;thank you&lt;BR /&gt;&lt;BR /&gt;max</description>
      <pubDate>Wed, 12 Sep 2007 07:58:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068076#M69278</guid>
      <dc:creator>Massimiliano Fiorazzo</dc:creator>
      <dc:date>2007-09-12T07:58:28Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068077#M69279</link>
      <description>James,&lt;BR /&gt;&lt;BR /&gt;I'm back at the customers site and manually installing the firmware and drivers didn't fix the problem.&lt;BR /&gt;&lt;BR /&gt;Pac,&lt;BR /&gt;&lt;BR /&gt;From the looks of the config on a server still working it doesn't look like the updated driver changed the config. Obviously it changed something though. One thing I did notice is HP has separated the Large Send Offload and IPMI now with the new driver. &lt;BR /&gt;&lt;BR /&gt;I am able to go back on drivers with the latest support pack. But the NCU won't work work and the only way to uninstall it is via the NIC and then it removes the 20 vlans we've got setup. So I'm not a big fan of that.&lt;BR /&gt;&lt;BR /&gt;Also I've contacted HP and they shrug off as to just continue using your previous driver. The only problem is we've updated these servers to SP2 and now I have to get to the latest support pack to prevent random restarts and conflicts with certain drivers.&lt;BR /&gt;&lt;BR /&gt;Thanks guys for all of your help. I honestly just wanted to make sure that we didn't setup our VLANS wrong on our switch, but they worked with the previous driver so in theory they should continue to work.</description>
      <pubDate>Thu, 13 Sep 2007 08:42:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068077#M69279</guid>
      <dc:creator>Technology Helpdesk</dc:creator>
      <dc:date>2007-09-13T08:42:43Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068078#M69280</link>
      <description>Just wanted to give you the heads up that are you not alone with this issue.. IDENTICAL setup with the 6500 + DL360g4p.&lt;BR /&gt;&lt;BR /&gt;If we disable any of the virtual VLAN NICs and re-enable it, the issue is resolved.&lt;BR /&gt;&lt;BR /&gt;We're going to roll back to the v7.8 driver and see if that solves it.&lt;BR /&gt;&lt;BR /&gt;-Craig</description>
      <pubDate>Thu, 13 Sep 2007 11:01:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068078#M69280</guid>
      <dc:creator>Craig A. Liess</dc:creator>
      <dc:date>2007-09-13T11:01:08Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068079#M69281</link>
      <description>Craig,&lt;BR /&gt;&lt;BR /&gt;Thanks...I was beginning to think I was all alone. So you were able to get it working if you disabled the VLAN and brought it back up? I'm willing to try that and that's not a bad work around if it works.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Travis</description>
      <pubDate>Thu, 13 Sep 2007 11:06:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068079#M69281</guid>
      <dc:creator>Technology Helpdesk</dc:creator>
      <dc:date>2007-09-13T11:06:47Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068080#M69282</link>
      <description>Hi Travis,&lt;BR /&gt;&lt;BR /&gt;Yes, simply disabling &amp;amp; re-enabling any of the virtual VLAN interfaces seems to resolve the issue... until you reboot the server, that is.&lt;BR /&gt;&lt;BR /&gt;We're going to roll the driver back this weekend (I think..) and see what happens.&lt;BR /&gt;&lt;BR /&gt;-Craig</description>
      <pubDate>Fri, 14 Sep 2007 08:10:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068080#M69282</guid>
      <dc:creator>Craig A. Liess</dc:creator>
      <dc:date>2007-09-14T08:10:24Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068081#M69283</link>
      <description>Craig,&lt;BR /&gt;&lt;BR /&gt;When we've tried the roll back idea we've had to recreate all of our 32 VLANS after we uninstall the NCU. Have you guys found a way to export the VLAN info and then reimport it?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Travis&lt;BR /&gt;</description>
      <pubDate>Fri, 14 Sep 2007 08:35:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068081#M69283</guid>
      <dc:creator>Technology Helpdesk</dc:creator>
      <dc:date>2007-09-14T08:35:39Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068082#M69284</link>
      <description>Hey there ;)&lt;BR /&gt;&lt;BR /&gt;I think the previous idea for stopping TOE is really good and the driver works fine. Just go to network configuration utility - settings - advanced settings and remove the tick from TCP POffload engine.&lt;BR /&gt;&lt;BR /&gt;Also - if you use teaming, make the settings on "transmit load balancing". One more thing - bios version is very important, the old one didn't allocate the ram properly. And sometimes the /PAE switch causes problems. &lt;BR /&gt;&lt;BR /&gt;Greets!</description>
      <pubDate>Sat, 15 Sep 2007 03:12:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068082#M69284</guid>
      <dc:creator>Mi6t0</dc:creator>
      <dc:date>2007-09-15T03:12:34Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068083#M69285</link>
      <description>Hello.&lt;BR /&gt;&lt;BR /&gt;Exactly the same issue with ProLiant BL20p G3. The workaround of disable-enable the interface works fine...until you reboot the server :-(&lt;BR /&gt;&lt;BR /&gt;I have tried to disable TOE, but it seems that TOE is only availble if you have Teaming, not only VLAN's. Is it right?&lt;BR /&gt;&lt;BR /&gt;Next I will downgrade the driver.&lt;BR /&gt;&lt;BR /&gt;Regards.&lt;BR /&gt;</description>
      <pubDate>Mon, 17 Sep 2007 05:43:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068083#M69285</guid>
      <dc:creator>Carlos Hernandez Barea</dc:creator>
      <dc:date>2007-09-17T05:43:33Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN issue with latest NIC Driver</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068084#M69286</link>
      <description>Hello.&lt;BR /&gt;&lt;BR /&gt;The downgrade of the driver didn't fix the issue :-(&lt;BR /&gt;&lt;BR /&gt;Maybe it would be a good idea downgrade also NCU?&lt;BR /&gt;&lt;BR /&gt;Regards.&lt;BR /&gt;</description>
      <pubDate>Mon, 17 Sep 2007 06:07:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/vlan-issue-with-latest-nic-driver/m-p/4068084#M69286</guid>
      <dc:creator>Carlos Hernandez Barea</dc:creator>
      <dc:date>2007-09-17T06:07:37Z</dc:date>
    </item>
  </channel>
</rss>

