<?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 issue on VSP-8284 in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-issue-on-vsp-8284/m-p/69602#M881</link>
    <description>Hello,&lt;BR /&gt;
&lt;BR /&gt;
it might be the duplicate address as Dilraj mentioned.  But if you are sure there is no duplicity it is rather caused by a loop.  Some device probably takes the vrrp packets and resends them back to the same vlan.</description>
    <pubDate>Fri, 01 Feb 2019 20:54:46 GMT</pubDate>
    <dc:creator>Martin_Sebek</dc:creator>
    <dc:date>2019-02-01T20:54:46Z</dc:date>
    <item>
      <title>VRRP issue on VSP-8284</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-issue-on-vsp-8284/m-p/69600#M879</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
We are experience issue with one VRID, which disrupts the network and we see the message below in the syslog:-&lt;BR /&gt;
&lt;BR /&gt;
GlobalRouter&lt;B&gt; &lt;/B&gt;IP&lt;B&gt; &lt;/B&gt;WARNING&lt;B&gt; &lt;/B&gt;rcIpVrrpIn:&lt;B&gt; &lt;/B&gt;Invalid&lt;B&gt; &lt;/B&gt;VRRP&lt;B&gt; &lt;/B&gt;source&lt;B&gt; &lt;/B&gt;IP&lt;B&gt; &lt;/B&gt;10.112.8.3&lt;B&gt; &lt;/B&gt;received&lt;B&gt; &lt;/B&gt;for&lt;B&gt; &lt;/B&gt;Vrid&lt;B&gt; &lt;/B&gt;202&lt;B&gt; &lt;/B&gt;on&lt;B&gt; &lt;/B&gt;IfIndex&lt;B&gt; &lt;/B&gt;3349,&lt;B&gt; &lt;/B&gt;same&lt;B&gt; &lt;/B&gt;as&lt;B&gt; &lt;/B&gt;local&lt;B&gt; &lt;/B&gt;primary&lt;B&gt; &lt;/B&gt;IP&lt;BR /&gt;
&lt;BR /&gt;
We have change priority to swap the master but we still suffered an outage with the following syslog:-&lt;BR /&gt;
&lt;BR /&gt;
GlobalRouter IP WARNING rcIpVrrpIn: Invalid VRRP source IP 10.112.8.2 received for Vrid 202 on IfIndex 3349, same as local primary IP.</description>
      <pubDate>Fri, 01 Feb 2019 19:46:33 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-issue-on-vsp-8284/m-p/69600#M879</guid>
      <dc:creator>WindyMiller</dc:creator>
      <dc:date>2019-02-01T19:46:33Z</dc:date>
    </item>
    <item>
      <title>Re: VRRP issue on VSP-8284</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-issue-on-vsp-8284/m-p/69601#M880</link>
      <description>Hi Windy,&lt;BR /&gt;
&lt;BR /&gt;
You might want to find out the duplicate address in the network (VLAN 202) and change it.&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
DILRAJ</description>
      <pubDate>Fri, 01 Feb 2019 20:32:57 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-issue-on-vsp-8284/m-p/69601#M880</guid>
      <dc:creator>Dilraj_Singh_Kh</dc:creator>
      <dc:date>2019-02-01T20:32:57Z</dc:date>
    </item>
    <item>
      <title>Re: VRRP issue on VSP-8284</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-issue-on-vsp-8284/m-p/69602#M881</link>
      <description>Hello,&lt;BR /&gt;
&lt;BR /&gt;
it might be the duplicate address as Dilraj mentioned.  But if you are sure there is no duplicity it is rather caused by a loop.  Some device probably takes the vrrp packets and resends them back to the same vlan.</description>
      <pubDate>Fri, 01 Feb 2019 20:54:46 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vrrp-issue-on-vsp-8284/m-p/69602#M881</guid>
      <dc:creator>Martin_Sebek</dc:creator>
      <dc:date>2019-02-01T20:54:46Z</dc:date>
    </item>
  </channel>
</rss>

