<?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 c-class blades and NLB for terminal servers in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/c-class-blades-and-nlb-for-terminal-servers/m-p/4082628#M1205</link>
    <description>Does anyone have any experiance with c-class blades and network load balancing with windows terminal servers. I think we have a problem with the mac address that is designated by the virtual connect domain en the mac address that is overridden by the NLB config. Ill elaborate if anyone thinks the might be able to help..&lt;BR /&gt;Thanks&lt;BR /&gt;Gary</description>
    <pubDate>Mon, 08 Oct 2007 05:07:42 GMT</pubDate>
    <dc:creator>Gary Witham</dc:creator>
    <dc:date>2007-10-08T05:07:42Z</dc:date>
    <item>
      <title>c-class blades and NLB for terminal servers</title>
      <link>https://community.hpe.com/t5/bladesystem-general/c-class-blades-and-nlb-for-terminal-servers/m-p/4082628#M1205</link>
      <description>Does anyone have any experiance with c-class blades and network load balancing with windows terminal servers. I think we have a problem with the mac address that is designated by the virtual connect domain en the mac address that is overridden by the NLB config. Ill elaborate if anyone thinks the might be able to help..&lt;BR /&gt;Thanks&lt;BR /&gt;Gary</description>
      <pubDate>Mon, 08 Oct 2007 05:07:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/c-class-blades-and-nlb-for-terminal-servers/m-p/4082628#M1205</guid>
      <dc:creator>Gary Witham</dc:creator>
      <dc:date>2007-10-08T05:07:42Z</dc:date>
    </item>
    <item>
      <title>Re: c-class blades and NLB for terminal servers</title>
      <link>https://community.hpe.com/t5/bladesystem-general/c-class-blades-and-nlb-for-terminal-servers/m-p/4082629#M1206</link>
      <description>This should work OK.  I assume you are using unicast NLB as that is the only version that needs to overwrite the MAC address of the NIC.&lt;BR /&gt;&lt;BR /&gt;Essentially, VC overwrites the MAC addresses of the NICs in the BIOS.  So in the OS the VC MACs look like the burned-in-addresses (and for all intents and purposes they are).  Then NLB Unicast overwrites the MAC in the OS.  No problem there.  Virtual Connect can handle the logically administered NLB MACs.&lt;BR /&gt;&lt;BR /&gt;It's other things you might have to look out for - Are you running NIC Teaming?  Running NIC Teaming with NLB can be tricky and there are some definitel caveats.&lt;BR /&gt;&lt;BR /&gt;What kind of problems are you experiencing?</description>
      <pubDate>Tue, 09 Oct 2007 08:02:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/c-class-blades-and-nlb-for-terminal-servers/m-p/4082629#M1206</guid>
      <dc:creator>HEM_2</dc:creator>
      <dc:date>2007-10-09T08:02:05Z</dc:date>
    </item>
  </channel>
</rss>

