<?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 Failover connection mode fail back in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/failover-connection-mode-fail-back/m-p/5548397#M32103</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Suppose we configure two external uplink ports in a failover connection mode, first one on VC1 (primary) and the second one on VC2 (secondary).&lt;/P&gt;&lt;P&gt;With Fast MAC Cache enable, when uplink port on VC1 fails, uplink port on VC2 switchs on active mode and sends gratuitous arp which enables the external Ethernet switches to identify the new connection (and update their MAC caches appropriately).&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;What's happen when uplink port on VC1 fail back ? Does it send a gratuitous arp again ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In case of VC1 failed, what is the behavior when VC1 fail back ?&lt;/P&gt;</description>
    <pubDate>Mon, 13 Feb 2012 08:11:37 GMT</pubDate>
    <dc:creator>jmogez</dc:creator>
    <dc:date>2012-02-13T08:11:37Z</dc:date>
    <item>
      <title>Failover connection mode fail back</title>
      <link>https://community.hpe.com/t5/bladesystem-general/failover-connection-mode-fail-back/m-p/5548397#M32103</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Suppose we configure two external uplink ports in a failover connection mode, first one on VC1 (primary) and the second one on VC2 (secondary).&lt;/P&gt;&lt;P&gt;With Fast MAC Cache enable, when uplink port on VC1 fails, uplink port on VC2 switchs on active mode and sends gratuitous arp which enables the external Ethernet switches to identify the new connection (and update their MAC caches appropriately).&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;What's happen when uplink port on VC1 fail back ? Does it send a gratuitous arp again ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In case of VC1 failed, what is the behavior when VC1 fail back ?&lt;/P&gt;</description>
      <pubDate>Mon, 13 Feb 2012 08:11:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/failover-connection-mode-fail-back/m-p/5548397#M32103</guid>
      <dc:creator>jmogez</dc:creator>
      <dc:date>2012-02-13T08:11:37Z</dc:date>
    </item>
    <item>
      <title>Re: Failover connection mode fail back</title>
      <link>https://community.hpe.com/t5/bladesystem-general/failover-connection-mode-fail-back/m-p/5552357#M32104</link>
      <description>VC will do fast mac cache refresh for both scenarios. The key thing is if there is a new ACTIVE uplink for this vnet, then VC will refresh its MAC cache.&lt;BR /&gt;&lt;BR /&gt;the packets are not strictly gratuitous arp, VC uses a heartbeat frame as defined by HP Proliant Network Adapter Teaming white paper:&lt;BR /&gt;&lt;A href="http://www.hp.com/sbso/bus_protect/teaming.pdf" target="_blank"&gt;http://www.hp.com/sbso/bus_protect/teaming.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The destination address of Heartbeat frames is 03-00-C7-00-00-EE</description>
      <pubDate>Wed, 15 Feb 2012 15:26:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/failover-connection-mode-fail-back/m-p/5552357#M32104</guid>
      <dc:creator>Hongjun Ma</dc:creator>
      <dc:date>2012-02-15T15:26:20Z</dc:date>
    </item>
  </channel>
</rss>

