<?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: Brocade access gateway failover problems in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/brocade-access-gateway-failover-problems/m-p/4112005#M1636</link>
    <description>We're experiencing the exact same issue.  Have you found a resolution?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Failover works great if there is only one active n-port.  When we map to multiple active n-ports, failover functionality does not work.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Allan</description>
    <pubDate>Fri, 11 Jan 2008 20:39:09 GMT</pubDate>
    <dc:creator>Allan Officer</dc:creator>
    <dc:date>2008-01-11T20:39:09Z</dc:date>
    <item>
      <title>Brocade access gateway failover problems</title>
      <link>https://community.hpe.com/t5/bladesystem-general/brocade-access-gateway-failover-problems/m-p/4112004#M1635</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have C-7000 enclosure with two Brocade 4Gb switches in access gateway mode. There is 16 F ports and just two N ports. Both of them have failover/failback enabled. Just to make it simpler, let's say first 8 F ports are mapped to one N port, and rest is mapped to another. When I simulate port failure, F ports mapped to that port DO NOT automatically fail over (as they should), but are disabled. When I reboot switch, they do fail over. What am I doing wrong? Firmware is 5.3.0c.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Denis</description>
      <pubDate>Wed, 05 Dec 2007 11:06:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/brocade-access-gateway-failover-problems/m-p/4112004#M1635</guid>
      <dc:creator>Denis Papes</dc:creator>
      <dc:date>2007-12-05T11:06:38Z</dc:date>
    </item>
    <item>
      <title>Re: Brocade access gateway failover problems</title>
      <link>https://community.hpe.com/t5/bladesystem-general/brocade-access-gateway-failover-problems/m-p/4112005#M1636</link>
      <description>We're experiencing the exact same issue.  Have you found a resolution?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Failover works great if there is only one active n-port.  When we map to multiple active n-ports, failover functionality does not work.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Allan</description>
      <pubDate>Fri, 11 Jan 2008 20:39:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/brocade-access-gateway-failover-problems/m-p/4112005#M1636</guid>
      <dc:creator>Allan Officer</dc:creator>
      <dc:date>2008-01-11T20:39:09Z</dc:date>
    </item>
    <item>
      <title>Re: Brocade access gateway failover problems</title>
      <link>https://community.hpe.com/t5/bladesystem-general/brocade-access-gateway-failover-problems/m-p/4112006#M1637</link>
      <description>I had access gateway connected to multiple switches, and this is not supported.&lt;BR /&gt;You should connect AG to just one switch, and failover/failback will work...</description>
      <pubDate>Sat, 12 Jan 2008 17:09:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/brocade-access-gateway-failover-problems/m-p/4112006#M1637</guid>
      <dc:creator>Denis Papes</dc:creator>
      <dc:date>2008-01-12T17:09:05Z</dc:date>
    </item>
  </channel>
</rss>

