<?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: HP BLADE SERVER CLUSTER PROBLEM gbe2c in ProLiant Servers - Netservers</title>
    <link>https://community.hpe.com/t5/proliant-servers-netservers/hp-blade-server-cluster-problem-gbe2c/m-p/864761#M14422</link>
    <description>What makes you think it's related to arp cache?&lt;BR /&gt;&lt;BR /&gt;gbe2c is Cisco isn't it? Do you have redundant path setup? Are you running C-Class or P-Class blades?&lt;BR /&gt;&lt;BR /&gt;If you think it's arp cache related then you could add static arp entries to the switches to fix it, but that depends on how your environment is setup.&lt;BR /&gt;&lt;BR /&gt;If it's DNS related, you could make that server a caching only DNS server. I've had problems with DNS timeout's before and this solved it. You don't need to manage the DNS on that server if it's caching only, and you only need to get it to cache the domain that you need for the application.</description>
    <pubDate>Fri, 09 Nov 2007 19:16:36 GMT</pubDate>
    <dc:creator>Chris Rosan</dc:creator>
    <dc:date>2007-11-09T19:16:36Z</dc:date>
    <item>
      <title>HP BLADE SERVER CLUSTER PROBLEM gbe2c</title>
      <link>https://community.hpe.com/t5/proliant-servers-netservers/hp-blade-server-cluster-problem-gbe2c/m-p/864760#M14421</link>
      <description>Hi, &lt;BR /&gt;
&lt;BR /&gt;
We have a blade chasis connected via ethernet (gbe2c) to a cisco 3750 and the problem I am having is that when the (Microsoft windows 2003 r2) Cluster has initiated failover then we cannot contact the virtual clustered resource for a long time via dns or ip address?? does anyone have any ideas how we can fix this ,,, i have a feeling it is the arp cache on the gbe2c do you have any suggestions on how to resolve / troubleshoot this . I am a windows server techie so my networking knowledge is limited. &lt;BR /&gt;
&lt;BR /&gt;
Thanks&lt;BR /&gt;</description>
      <pubDate>Thu, 08 Nov 2007 07:31:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-netservers/hp-blade-server-cluster-problem-gbe2c/m-p/864760#M14421</guid>
      <dc:creator>darren skirvin</dc:creator>
      <dc:date>2007-11-08T07:31:56Z</dc:date>
    </item>
    <item>
      <title>Re: HP BLADE SERVER CLUSTER PROBLEM gbe2c</title>
      <link>https://community.hpe.com/t5/proliant-servers-netservers/hp-blade-server-cluster-problem-gbe2c/m-p/864761#M14422</link>
      <description>What makes you think it's related to arp cache?&lt;BR /&gt;&lt;BR /&gt;gbe2c is Cisco isn't it? Do you have redundant path setup? Are you running C-Class or P-Class blades?&lt;BR /&gt;&lt;BR /&gt;If you think it's arp cache related then you could add static arp entries to the switches to fix it, but that depends on how your environment is setup.&lt;BR /&gt;&lt;BR /&gt;If it's DNS related, you could make that server a caching only DNS server. I've had problems with DNS timeout's before and this solved it. You don't need to manage the DNS on that server if it's caching only, and you only need to get it to cache the domain that you need for the application.</description>
      <pubDate>Fri, 09 Nov 2007 19:16:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-netservers/hp-blade-server-cluster-problem-gbe2c/m-p/864761#M14422</guid>
      <dc:creator>Chris Rosan</dc:creator>
      <dc:date>2007-11-09T19:16:36Z</dc:date>
    </item>
  </channel>
</rss>

