Win every interaction at the edge by delighting customers, empowering staff, and deflecting threats.
Create custom connections for every user and device with greater security and reduced complexity and cost.
Transform your data center with multivendor automation and management to accelerate innovation.
Benefit from flexible network fabrics that provide the automation and visibility to adapt to any application workload on any domain.
Extreme Networks enables Cloud Service Providers to fulfill the promise of digital transformation with flexible and adaptive infrastructure solutions for true business agility.
Get insights, visibility and control with advanced security and superior quality of user experience
Network switching products from Edge to Core—the foundation of a next-gen network
Lightning speed and scalable routers ideal for enterprise, data center, and service providers
Introducing the industry’s first flow-based 802.11ac Wave 2 wireless products
Network solutions consultation and implementation
Dedicated customer advocacy team to ensure that all your services needs are met
Superior, around-the-clock support for your network configuration
Fully managed, ITIL-based network services, defense & infrastructure
A wide selection of instructor-led and self-paced technical courses
A simple way for institutions to obtain Extreme software license access
Hi,"log-and-trap" vs "log" is about what info will be sent to signal the loop detection. The "disable-port" is the action taken when a loop is detected, and the "permanent" keyword means the port will not go back up automatically, an admin will have to enable it. As for the "ingress" versus "egress" options, this is a new one since 16.1. It tells what port should be disabled, either the "ingress" one (where the elrp looped packet has been received) or the "egress" one (where the elrp looped packet has been transmitted).
You may also find these articles helpful:https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-configure-ELRP-to-disable-ports/https://gtacknowledge.extremenetworks.com/articles/Q_A/What-is-ELRP/
Hi,I prefer to enable ELRP on the access ports, but not on uplinks, and then disable the egress port if a loop is detected.If e.g. a loop between two access switches is created, ELRP will see packets returning via the uplinks. The uplinks are usually exempted from being disabled by ELRP (otherwise the whole switch would be disabled, not just the access port that is part of the loop). Thus it does not help to act on the ingress port . But the egress port can (and should) be disabled in this situation.Thanks,Erik
I'm ready to enable this but just so I'm clear, I should enable ELRP blocking on egress on access ports and no ELRP on my uplinks? I have MLAG configured on all my edge and TOR switches and should have L2 loop prevention on those as well. Thanks
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address to receive an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.