EtherNation ExtremeNetworks

Signup   |  Login
 
EtherNation ForumsEtherNation ForumsDiscussionsDiscussionsExtensibility E...Extensibility E...ELRP with UPM ScriptELRP with UPM Script
Previous Previous
 
Next
 Disabled
New Post
 4/15/2010 12:33 PM
 

Hello All,

A powerful tool on Extreme EXOS to protect L2 loops is ELRP (Extreme Loop recovery protocol). UPM script is triggered when ELRP protocol logs a message in EMS log, when it detects a L2 loop on a switch. This is a powerful mechanism to prevert l2 loops in network.

Unable to attach the files and pasting it below:

Step 1) Enable ELRP on all ports on all VLANs

enable elrp

conf elrp-client periodic [vlan name] ports all interval 5 log

Step 2) Create a UPM Profile UPM-loopdetect

Example:

create upm profile upm-loopdetect

#disable log target upm upm-loopdetect

#########################################################################

#Set variables (These variables must be set to your uplink ports)

#########################################################################

set var trunk1 1:23

set var trunk2 1:24

#########################################################################

# Create user friendly log entries

#########################################################################

create log entry UPM-EMS-EVENT-NAME:Loop-Detected

create log entry UPM-EMS-LOG-SEVERITY:WARNING

create log entry UPM-EMS-LOG-MESSAGE:A_LOOP_HAS_BEEN_DETECTED!

create log entry UPM-EMS-LOG-PARAM6:$EVENT.LOG_PARAM_6

create log entry UPM-EMS-LOG-PARAM7:$EVENT.LOG_PARAM_7

#########################################################################

# Script Actions

#########################################################################

if (!$match($trunk1,$EVENT.LOG_PARAM_7)) then

create log entry UPM-EMS:TRUNK_PORT_LOOPED-$EVENT.LOG_PARAM_7

create log entry TRUNKPORT_CANNOT_BE_DISABLED!

Enable log target upm upm-loopdetect

else

if (!$match($trunk2,$EVENT.LOG_PARAM_7)) then

create log entry UPM-EMS:TRUNK_PORT_LOOPED-$EVENT.LOG_PARAM_7

create log entry TRUNKPORT_$trunk2_CANNOT_BE_DISABLED!

enable log target upm upm-loopdetect

else

create log entry UPM-EMS:PORT_DISABLED-$EVENT.LOG_PARAM_7

disable port $EVENT.LOG_PARAM_7

enable log target upm upm-loopdect

endif

endif

.

Step 3) Configure UPM as the ELRP log target

create log filter UPMLoopfilter

config log filter UPMLoopfilter add event ELRP.Report.Message

create log target upm upm-loopdetect

enable log target upm upm-loopdetect

config log target upm upm-loopdetect filter UPMLoopfilter severity Warning only

####SAMPLE LOG FOR ELRP

* Slot-1 Stack.24 # sh log
11/21/2008 15:24:16.37 <Erro:UPM.Msg.upmMsgExshLaunchStsFail> Slot-1: Profile execution returned FAIL on event log-message, profile upm-loopdetect
11/21/2008 15:24:16.33 <Info:System.userComment> Slot-1: UPM-EMS:PORT_DISABLED-1:5
11/21/2008 15:24:16.32 <Info:System.userComment> Slot-1: UPM-EMS-LOG-PARAM7:1:5
11/21/2008 15:24:16.31 <Info:System.userComment> Slot-1: UPM-EMS-LOG-PARAM6:1:3
11/21/2008 15:24:16.31 <Info:System.userComment> Slot-1: UPM-EMS-LOG-MESSAGE:A_LOOP_HAS_BEEN_DETECTED!
11/21/2008 15:24:16.30 <Info:System.userComment> Slot-1: UPM-EMS-LOG-SEVERITY:WARNING
11/21/2008 15:24:16.30 <Info:System.userComment> Slot-1: UPM-EMS-EVENT-NAME:Loop-Detected
11/21/2008 15:24:15.24 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 1:5 link down
11/21/2008 15:24:15.16 <Noti:UPM.Msg.upmMsgExshLaunch> Slot-1: Launched profile upm-loopdetect for the event log-message
11/21/2008 15:24:14.54 <Erro:UPM.Msg.upmMsgExshLaunchStsFail> Slot-1: Profile execution returned FAIL on event log-message, profile upm-loopdetect
11/21/2008 15:24:14.51 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 1:3 link down
11/21/2008 15:24:14.47 <Info:System.userComment> Slot-1: UPM-EMS:PORT_DISABLED-1:3
11/21/2008 15:24:14.43 <Info:System.userComment> Slot-1: UPM-EMS-LOG-PARAM7:1:3
11/21/2008 15:24:14.42 <Info:System.userComment> Slot-1: UPM-EMS-LOG-PARAM6:1:5
11/21/2008 15:24:14.42 <Info:System.userComment> Slot-1: UPM-EMS-LOG-MESSAGE:A_LOOP_HAS_BEEN_DETECTED!
11/21/2008 15:24:14.42 <Info:System.userComment> Slot-1: UPM-EMS-LOG-SEVERITY:WARNING
11/21/2008 15:24:14.41 <Info:System.userComment> Slot-1: UPM-EMS-EVENT-NAME:Loop-Detected
11/21/2008 15:24:13.00 <Noti:UPM.Msg.upmMsgExshLaunch> Slot-1: Launched profile upm-loopdetect for the event log-message
11/21/2008 15:24:12.88 <Warn:ELRP.Report.Message> Slot-1: [CLI:data:1] LOOP DETECTED : 27 transmited, 1599 received, ingress slot:port (1:3) egress slot:port (1:5)
11/21/2008 15:24:12.88 <Warn:ELRP.Report.Message> Slot-1: [CLI:data:1] LOOP DETECTED : 27 transmited, 1598 received, ingress slot:port (1:5) egress slot:port (1:3)
11/21/2008 15:24:04.42 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 1:5 link UP at speed 1 Gbps and full-duplex
11/21/2008 15:24:04.39 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 1:3 link UP at speed 1 Gbps and full-duplex

A total of 22 log messages were displayed.

New Post
 4/22/2010 1:49 AM
 

Is there any way of letting the script instead snmp trap a detected loop ? And also is there anyway of configuring this globally. And not have to be able to activate it on every vlan ?

New Post
 4/22/2010 4:14 PM
 

As of 12.4.1 This feature is in Hardware. I will post more on it when time permits (e.g. After Interop)

New Post
 5/18/2010 2:28 AM
 

How about this feature. Is there some undocumented commands

I have 12.4.1.7 and summit 150

I need command something like "Elrp port shut down"

Previous Previous
 
Next
 Disabled
EtherNation ForumsEtherNation ForumsDiscussionsDiscussionsExtensibility E...Extensibility E...ELRP with UPM ScriptELRP with UPM Script