<?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: VRRP priority in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-priority/m-p/8951#M532</link>
    <description>Fabric Routing is a simpler approach, imho. During the VRRP config, this is an option you can turn on.&lt;BR /&gt;
&lt;BR /&gt;
configure vrrp {vlan vlan_name vr vr_id | all} fabric-routing [on | off]&lt;BR /&gt;
&lt;BR /&gt;
User Guide:&lt;BR /&gt;
&lt;A href="https://documentation.extremenetworks.com/exos_22.4/EXOS_21_1/VRRP/c_vrrp-fabric-routing-overview.shtml" target="_blank" rel="nofollow noreferrer noopener"&gt;https://documentation.extremenetworks.com/exos_22.4/EXOS_21_1/VRRP/c_vrrp-fabric-routing-overview.sh...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Command Guide:&lt;BR /&gt;
&lt;A href="https://documentation.extremenetworks.com/exos_commands_22.4/exos_21_1/exos_commands_all/r_configure-vrrp-group-fabric-routing.shtml" target="_blank" rel="nofollow noreferrer noopener"&gt;https://documentation.extremenetworks.com/exos_commands_22.4/exos_21_1/exos_commands_all/r_configure...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Sat, 30 Dec 2017 19:23:00 GMT</pubDate>
    <dc:creator>Stephane_Grosj1</dc:creator>
    <dc:date>2017-12-30T19:23:00Z</dc:date>
    <item>
      <title>VRRP priority</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-priority/m-p/8948#M529</link>
      <description>I have configured MLAG(X670) on two switch and want to configure VRRP active-active can we use same &lt;B&gt;priority level&lt;/B&gt; on both switches?&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;A href="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20171230-28764-1.gifpa-img-1_inline.jpg" rel="image" class="fancybox"&gt;&lt;IMG src="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20171230-28764-1.gifpa-img-1_inline.jpg" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 30 Dec 2017 09:56:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-priority/m-p/8948#M529</guid>
      <dc:creator>Alok_Shukla</dc:creator>
      <dc:date>2017-12-30T09:56:00Z</dc:date>
    </item>
    <item>
      <title>RE: VRRP priority</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-priority/m-p/8949#M530</link>
      <description>Just giving them the same priority does not give you active-active. When two VRRP routers have the same priority the one with the higher MAC wins. So only one of them will become master. You have to block the VRRP hellos via an ACL on the ISC link.&lt;BR /&gt;</description>
      <pubDate>Sat, 30 Dec 2017 16:23:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-priority/m-p/8949#M530</guid>
      <dc:creator>AnonymousM</dc:creator>
      <dc:date>2017-12-30T16:23:00Z</dc:date>
    </item>
    <item>
      <title>RE: VRRP priority</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-priority/m-p/8950#M531</link>
      <description>VRRPActive.pol&lt;BR /&gt;
&lt;BR /&gt;
    entry denyVrrpCtrl {&lt;BR /&gt;
&lt;BR /&gt;
         if match all {&lt;BR /&gt;
&lt;BR /&gt;
             destination-address 224.0.0.18/32;&lt;BR /&gt;
&lt;BR /&gt;
         } then {&lt;BR /&gt;
&lt;BR /&gt;
             deny; } }&lt;BR /&gt;
&lt;BR /&gt;
    &lt;BR /&gt;</description>
      <pubDate>Sat, 30 Dec 2017 16:28:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-priority/m-p/8950#M531</guid>
      <dc:creator>AnonymousM</dc:creator>
      <dc:date>2017-12-30T16:28:00Z</dc:date>
    </item>
    <item>
      <title>RE: VRRP priority</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-priority/m-p/8951#M532</link>
      <description>Fabric Routing is a simpler approach, imho. During the VRRP config, this is an option you can turn on.&lt;BR /&gt;
&lt;BR /&gt;
configure vrrp {vlan vlan_name vr vr_id | all} fabric-routing [on | off]&lt;BR /&gt;
&lt;BR /&gt;
User Guide:&lt;BR /&gt;
&lt;A href="https://documentation.extremenetworks.com/exos_22.4/EXOS_21_1/VRRP/c_vrrp-fabric-routing-overview.shtml" target="_blank" rel="nofollow noreferrer noopener"&gt;https://documentation.extremenetworks.com/exos_22.4/EXOS_21_1/VRRP/c_vrrp-fabric-routing-overview.sh...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Command Guide:&lt;BR /&gt;
&lt;A href="https://documentation.extremenetworks.com/exos_commands_22.4/exos_21_1/exos_commands_all/r_configure-vrrp-group-fabric-routing.shtml" target="_blank" rel="nofollow noreferrer noopener"&gt;https://documentation.extremenetworks.com/exos_commands_22.4/exos_21_1/exos_commands_all/r_configure...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Sat, 30 Dec 2017 19:23:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-priority/m-p/8951#M532</guid>
      <dc:creator>Stephane_Grosj1</dc:creator>
      <dc:date>2017-12-30T19:23:00Z</dc:date>
    </item>
    <item>
      <title>RE: VRRP priority</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-priority/m-p/8952#M533</link>
      <description>Stephane is right. With the introduction of fabric routing we have an easier approach. The ACL was the way to do it before we had fabric routing. Anyway, both ways work.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Sat, 30 Dec 2017 20:09:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-priority/m-p/8952#M533</guid>
      <dc:creator>AnonymousM</dc:creator>
      <dc:date>2017-12-30T20:09:00Z</dc:date>
    </item>
    <item>
      <title>RE: VRRP priority</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-priority/m-p/8953#M534</link>
      <description>thank's Hagemann</description>
      <pubDate>Sat, 30 Dec 2017 20:09:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-priority/m-p/8953#M534</guid>
      <dc:creator>Alok_Shukla</dc:creator>
      <dc:date>2017-12-30T20:09:00Z</dc:date>
    </item>
    <item>
      <title>RE: VRRP priority</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-priority/m-p/8954#M535</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
There is one good article which could help you to configure fabric routing.&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/An-example-of-VRRP-fabric-routing-configuration-to-achieve-active-active-forwarding-routing-on-all-VRRP-routers" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/An-example-of-VRRP-fabric-routing-configur...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Best regards,&lt;BR /&gt;
Bin</description>
      <pubDate>Sat, 30 Dec 2017 20:09:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-priority/m-p/8954#M535</guid>
      <dc:creator>Bin</dc:creator>
      <dc:date>2017-12-30T20:09:00Z</dc:date>
    </item>
  </channel>
</rss>

