<?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: ELRP implementation in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/elrp-implementation/m-p/54818#M15714</link>
    <description>Yes, but wouldn't it have to, in order to detect a loop?&lt;BR /&gt;
Reading &lt;A href="https://gtacknowledge.extremenetworks.com/articles/Q_A/What-is-ELRP" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/Q_A/What-is-ELRP&lt;/A&gt;, it says that the switch sends out a packet on every configured (including the uplink, in my approach) port, and sees if it gets it back on another port.&lt;BR /&gt;
If I have a switch scenario like:&lt;BR /&gt;
           Core-Switch&lt;BR /&gt;
            /        \&lt;BR /&gt;
﻿      EdgeSW-1       EdgeSW-2and have a vlan with untagged port 1 on Edge-1 and Edge-2, and tagged ports 55 on Edge-1 and Edge-2 (the uplink ports), same vlan on the Core between Edge-1 and Edge-2, and configure elrp both on Edge-1 and Edge-2, wouldn't the only way that I can detect a loop between Edge-1 and Edge-2 (let's just say 'physical cable') be because I the packet goes out port-1 Edge-1 and comes in on Edge-1 port 55 - or out Edge-1 55 and back in on Edge-1 port 1?&lt;BR /&gt;
If I wouldn't include the uplink port on the elrp port list (OK, 'all vlan ports'), I'd never detect the loop, even if it existed.&lt;BR /&gt;
&lt;BR /&gt;
Now, if you're only concerned with loops on a single Edge switch (for instance because you don't have the same vlan on another Edge switch, then you could live without the uplink port in ELRP - but I fear you'd then have to specify every port that's in the vlan, except the uplink port, and only ports that are part of that vlan.&lt;BR /&gt;
And if you add ports to the vlan, you'd probably have to add them manually to the ELRP list. And that would just drive me nuts, because I know I'd screw up sooner or later (but that's juist me  )&lt;BR /&gt;
&lt;BR /&gt;
Standard disclaimer - I may have something wrong. Also, I only have BlackDiamon/Summit 460/480/670s running EXOS 15.4 or higher.&lt;BR /&gt;</description>
    <pubDate>Wed, 30 Mar 2016 02:21:00 GMT</pubDate>
    <dc:creator>Frank</dc:creator>
    <dc:date>2016-03-30T02:21:00Z</dc:date>
    <item>
      <title>ELRP implementation</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/elrp-implementation/m-p/54813#M15709</link>
      <description>Hello everyone,&lt;BR /&gt;
I have some issues configuring ELRP and need a few clarifications &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;
&lt;BR /&gt;
So, I have several access switches called ToR that connect to the core switches.&lt;BR /&gt;
I want to enable ELRP on all ports except uplinks to the core switch.&lt;BR /&gt;
On every ToR switch I have around 70 vlans. I thought that I can copy/paste the config but it is not a solution as I'm receiving warnings that not all ports are in that VLAN.&lt;BR /&gt;
&lt;BR /&gt;
* Slot-1 ENSX670V-01.15 # configure elrp-client periodic "Backup_2" ports 1:1-48,1:50-52,1:54-64,2:1-48,2:50-52,2:54-64 log-and-trap disable-port egress duration 30WARNING: Port 1:1 does not belong to Backup_2!&lt;BR /&gt;
&lt;BR /&gt;
I ignored the message and continued with my vlans until I was stopped by:&lt;BR /&gt;
* Slot-1 ENSX670V-01.22 # configure elrp-client periodic "VDI_Provisioning_PFDC" ports 1:1-48,1:50-52,1:54-64,2:1-48,2:50-52,2:54-64 log-and-trap disable-port egress duration 30&lt;BR /&gt;
Configuration reply is too big&lt;BR /&gt;
Configuration failed on backup Node, command execution aborted!&lt;BR /&gt;
&lt;BR /&gt;
Did some tests..I am able to issue the command if I reduce the number of "port list"; is there any command to add ports to an existing elpr session for a vlan ?&lt;BR /&gt;
&lt;BR /&gt;
Another way would be to configure elrp on all ports for each vlan but do we have a command to exclude a specific port after that?&lt;BR /&gt;
&lt;BR /&gt;
 &lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Mar 2016 18:12:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/elrp-implementation/m-p/54813#M15709</guid>
      <dc:creator>Victor_Plohod</dc:creator>
      <dc:date>2016-03-29T18:12:00Z</dc:date>
    </item>
    <item>
      <title>RE: ELRP implementation</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/elrp-implementation/m-p/54814#M15710</link>
      <description>Sounds like you have the basics but are complicating it. Below is a summary of our default elrp config to protect all non uplink ports. I remember all the symantics but if you take the below information and tab your way through you should be good. The name and tag of the vlan is simply what we choose any name and tag you find relevant would work.&lt;BR /&gt;
&lt;BR /&gt;
Our standard elrp configuration is:&lt;BR /&gt;
&lt;BR /&gt;
Create vlan NO_LOOP tag 666&lt;BR /&gt;
Config NO_LOOP add ports all tagged&lt;BR /&gt;
Config elrp client ........................&lt;BR /&gt;
Config elrp disabled-ports exclude (uplink Ports)&lt;BR /&gt;
&lt;BR /&gt;
Hope this helps,</description>
      <pubDate>Tue, 29 Mar 2016 18:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/elrp-implementation/m-p/54814#M15710</guid>
      <dc:creator>davidj_cogliane</dc:creator>
      <dc:date>2016-03-29T18:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: ELRP implementation</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/elrp-implementation/m-p/54815#M15711</link>
      <description>Hi Victor,&lt;BR /&gt;
&lt;BR /&gt;
Yes the best option would be to configure ELRP on all ports, then use the below command to exclude the uplinks:&lt;BR /&gt;
"configure elrp-client disable-port exclude "&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Mar 2016 18:22:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/elrp-implementation/m-p/54815#M15711</guid>
      <dc:creator>Dorian_Perry</dc:creator>
      <dc:date>2016-03-29T18:22:00Z</dc:date>
    </item>
    <item>
      <title>RE: ELRP implementation</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/elrp-implementation/m-p/54816#M15712</link>
      <description>Call me a cheater, but I just do:&lt;BR /&gt;
&lt;BR /&gt;
enable elrp-client&lt;BR /&gt;
configure elrp-client disable-port exclude &lt;U&gt;&lt;BR /&gt;
configure elrp-client periodic &lt;VLAN-NAME&gt; ports all interval 5 log disable-port duration 300 ...&lt;BR /&gt;
&lt;BR /&gt;
I don't even care what ports are in which vlan - I just do it by vlan  "all ports".&lt;BR /&gt;
&lt;BR /&gt;&lt;/VLAN-NAME&gt;&lt;/U&gt;</description>
      <pubDate>Tue, 29 Mar 2016 21:01:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/elrp-implementation/m-p/54816#M15712</guid>
      <dc:creator>Frank</dc:creator>
      <dc:date>2016-03-29T21:01:00Z</dc:date>
    </item>
    <item>
      <title>RE: ELRP implementation</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/elrp-implementation/m-p/54817#M15713</link>
      <description>I would do the same thing if it was up to me . &lt;BR /&gt;
The only problem with this solution is that it is still sending elrp packets on the uplink ports...</description>
      <pubDate>Wed, 30 Mar 2016 02:21:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/elrp-implementation/m-p/54817#M15713</guid>
      <dc:creator>Victor_Plohod</dc:creator>
      <dc:date>2016-03-30T02:21:00Z</dc:date>
    </item>
    <item>
      <title>RE: ELRP implementation</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/elrp-implementation/m-p/54818#M15714</link>
      <description>Yes, but wouldn't it have to, in order to detect a loop?&lt;BR /&gt;
Reading &lt;A href="https://gtacknowledge.extremenetworks.com/articles/Q_A/What-is-ELRP" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/Q_A/What-is-ELRP&lt;/A&gt;, it says that the switch sends out a packet on every configured (including the uplink, in my approach) port, and sees if it gets it back on another port.&lt;BR /&gt;
If I have a switch scenario like:&lt;BR /&gt;
           Core-Switch&lt;BR /&gt;
            /        \&lt;BR /&gt;
﻿      EdgeSW-1       EdgeSW-2and have a vlan with untagged port 1 on Edge-1 and Edge-2, and tagged ports 55 on Edge-1 and Edge-2 (the uplink ports), same vlan on the Core between Edge-1 and Edge-2, and configure elrp both on Edge-1 and Edge-2, wouldn't the only way that I can detect a loop between Edge-1 and Edge-2 (let's just say 'physical cable') be because I the packet goes out port-1 Edge-1 and comes in on Edge-1 port 55 - or out Edge-1 55 and back in on Edge-1 port 1?&lt;BR /&gt;
If I wouldn't include the uplink port on the elrp port list (OK, 'all vlan ports'), I'd never detect the loop, even if it existed.&lt;BR /&gt;
&lt;BR /&gt;
Now, if you're only concerned with loops on a single Edge switch (for instance because you don't have the same vlan on another Edge switch, then you could live without the uplink port in ELRP - but I fear you'd then have to specify every port that's in the vlan, except the uplink port, and only ports that are part of that vlan.&lt;BR /&gt;
And if you add ports to the vlan, you'd probably have to add them manually to the ELRP list. And that would just drive me nuts, because I know I'd screw up sooner or later (but that's juist me  )&lt;BR /&gt;
&lt;BR /&gt;
Standard disclaimer - I may have something wrong. Also, I only have BlackDiamon/Summit 460/480/670s running EXOS 15.4 or higher.&lt;BR /&gt;</description>
      <pubDate>Wed, 30 Mar 2016 02:21:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/elrp-implementation/m-p/54818#M15714</guid>
      <dc:creator>Frank</dc:creator>
      <dc:date>2016-03-30T02:21:00Z</dc:date>
    </item>
    <item>
      <title>RE: ELRP implementation</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/elrp-implementation/m-p/54819#M15715</link>
      <description>I too do not see why the ELRP packets going out the uplinks. If the links leave the building and physical loops are not possible you could simply leave your "noloop" vlan off those ports.    The the links go to other stacks within the building I would think you would want the protection to span those ports.    Thanks</description>
      <pubDate>Wed, 30 Mar 2016 15:18:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/elrp-implementation/m-p/54819#M15715</guid>
      <dc:creator>davidj_cogliane</dc:creator>
      <dc:date>2016-03-30T15:18:00Z</dc:date>
    </item>
  </channel>
</rss>

