This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Extreme Networks
- Community List
- Switching & Routing
- ExtremeSwitching (EXOS/Switch Engine)
- Re: Will "configure elrp-client one-shot" actually...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Will "configure elrp-client one-shot" actually disable ports or just log them?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
01-31-2019 08:51 PM
Assuming we used "configure elrp-client one-shot ports all print-and-log" as described in https://extremeportal.force.com/ExtrArticleDetail?an=000090973, will that command actually disable any ports or just print/log them so that they can be resolved before enabling ELRP?
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
02-01-2019 07:54 PM
I'd not configure ELRP on a Core switch (or just for logs to see the loops happening). This is a Edge protection. You should configure it at the edge, excluding the uplinks, and use egress for optimisation if you also do not configure ELRP on uplinks (not sending ELRP PDUs to the Core).
Egress is just defining what port to shutdown when a loop is detected : is it the one that generates it, or the one that received it?
Egress is just defining what port to shutdown when a loop is detected : is it the one that generates it, or the one that received it?
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
02-01-2019 08:23 PM
Thanks. I set the core switch in each location to just log and trap so that we will get the notification but no action is taken. The switches that the desktops and phones connect to are set to log, trap, and disable for 60 seconds excluding the ports that uplink to the core.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
02-01-2019 07:54 PM
I'd not configure ELRP on a Core switch (or just for logs to see the loops happening). This is a Edge protection. You should configure it at the edge, excluding the uplinks, and use egress for optimisation if you also do not configure ELRP on uplinks (not sending ELRP PDUs to the Core).
Egress is just defining what port to shutdown when a loop is detected : is it the one that generates it, or the one that received it?
Egress is just defining what port to shutdown when a loop is detected : is it the one that generates it, or the one that received it?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
02-01-2019 01:57 PM
The "one-shot" worked as expected, but enabling ELRP didn't quite go as planned (or I am just misunderstanding how to configure it).
I enabled ELRP on egress for all ports on all VLANs using the command:
configure elrp-client periodic Desktops ports all log-and-trap disable-port egress duration 60
This was performed on our core switch and the desktop switch stack connected to it. I connected a cable between two ports on the desktop stack and both of those ports were disabled by ELRP. However, the core switch detected that loop on an attached stack and then disabled the uplink port to that stack. I thought that the "egress" method was meant to avoid that? Or is that only if we connect a device between the core switch and the desktop switch, and what we still need to do is exclude the uplink ports from ELRP?
I enabled ELRP on egress for all ports on all VLANs using the command:
configure elrp-client periodic Desktops ports all log-and-trap disable-port egress duration 60
This was performed on our core switch and the desktop switch stack connected to it. I connected a cable between two ports on the desktop stack and both of those ports were disabled by ELRP. However, the core switch detected that loop on an attached stack and then disabled the uplink port to that stack. I thought that the "egress" method was meant to avoid that? Or is that only if we connect a device between the core switch and the desktop switch, and what we still need to do is exclude the uplink ports from ELRP?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
02-01-2019 01:36 AM
Hi Stephen,
By the provided command the switch will print the logs if loop is detected.
By the provided command the switch will print the logs if loop is detected.
