cancel
Showing results for 
Search instead for 
Did you mean: 

ELRP + UPM = Number of UPM Events in Queue for execution

ELRP + UPM = Number of UPM Events in Queue for execution

AlexanderT
New Contributor
Hello!

I want to execute UPM after every LOOP detect without Queue.

Now, I see couple of loops , but UPM executes with Queue.

  • 07/22/2015 16:58:08.98 [CLI:v3000:4] LOOP DETECTED : 3241 transmited, 177 received, ingress slot:port (3) egress slot:port (1)07/22/2015 16:58:07.98 [CLI:v3002:6] LOOP DETECTED : 170 transmited, 97 received, ingress slot:port (3) egress slot:port (1)
  • 07/22/2015 16:58:05.98 [CLI:v3000:4] LOOP DETECTED : 3238 transmited, 171 received, ingress slot:port (1) egress slot:port (3)
  • 07/22/2015 16:58:04.98 [CLI:v3002:6] LOOP DETECTED : 167 transmited, 91 received, ingress slot:port (3) egress slot:port (1)
  • 07/22/2015 16:58:02.98 [CLI:v3000:4] LOOP DETECTED : 3235 transmited, 165 received, ingress slot:port (3) egress slot:port (1)
  • 07/22/2015 16:58:01.98 [CLI:v3002:6] LOOP DETECTED : 164 transmited, 85 received, ingress slot:port (3) egress slot:port (1)
  • 07/22/2015 16:57:59.98 [CLI:v3000:4] LOOP DETECTED : 3232 transmited, 159 received, ingress slot:port (1) egress slot:port (3)
* exos_vm_sw1.91 # show upm history--------------------------------------------------------------------------------
Exec Event/ Profile Port Status Time Launched
Id Timer/ Log filter
--------------------------------------------------------------------------------
100 Log-Message(loopdete loopdetect --- Running 2015-07-22 17:22:57
99 Log-Message(loopdete loopdetect --- Pass 2015-07-22 17:21:56
98 Log-Message(loopdete loopdetect --- Pass 2015-07-22 17:20:56
97 Log-Message(loopdete loopdetect --- Pass 2015-07-22 17:19:56
96 Log-Message(loopdete loopdetect --- Pass 2015-07-22 17:18:56
95 Log-Message(loopdete loopdetect --- Pass 2015-07-22 17:17:56
--------------------------------------------------------------------------------
Number of UPM Events in Queue for execution: 10
* exos_vm_sw1.92 #

* exos_vm_sw1.92 # show upm profile "loopdetect" Created at : 2015-07-22 10:43:41
Last edited at : 2015-07-22 16:30:09

************Profile Contents Begin************
configure vlan $EVENT.LOG_PARAM_1 delete ports $EVENT.LOG_PARAM_7
set var temp $TCL(after [expr 60*1000])
configure vlan $EVENT.LOG_PARAM_1 add ports $EVENT.LOG_PARAM_7 tagged

************Profile Contents Ends*************

Profile State: Enabled
Profile Maximimum Execution Time: 75
Events and ports configured on the profile:
===========================================================
Event Port list/Log filter
===========================================================
device-detect :
device-undetect :
user-authenticated :
user-unauthenticated :
log-message : loopdetect
identity-detect :
identity-undetect :
identity-role-associate :
identity-role-dissociate :
===========================================================
13 REPLIES 13

dflouret
Extreme Employee
Pavel,

ELRP has two configuration options that can help you.

The first one will let you exclude certain ports that you don't want disabled under any circumstance (uplinks, EAPS ports, etc.). You should add your uplink/trunk ports to this list so a loop in one vlan does not affect tens or hundreds of vlans.
configure elrp-client disable-ports [exclude | include] [ | eaps-ring-ports]
The second option will let you disable a port for a period of time and then re-enable it.
configure elrp-client periodic ports [ | all] interval [log | log-and-trap | trap] {disable-port {{duration } | permanent}In this case, ELRP will disable the offending port for the period of time you configured, and then will re-enable it. If the loop was temporary, then the port will resume its normal activity. If the loop remains, the port will be disabled/enabled again, and again, and again, until some external action is taken.

Hi, Daniel.

You dont understand what I need, reread please my posts.

1) blocking another port will not help me cause loop is on port you calling uplink, and not on port but rather on one or couple vlans.

You may call ot Downlink as well. The loop creates another device or another network, as you like.

2) 'disable port' is not what I need cause looping is only one vlan. Why must I shut port and thus shut traffic in all vlans ?

It is not discussion " why Pavel do not need what he want. Let's show him that."

It is discussion "How to create what Pavel need"

Stephane_Grosj1
Extreme Employee
Ok, that makes sense. Then, I assume this is because you have a loop between two edge switches with a direct (miss)connection, and it creates a loop through the core, right? And you don't want to shut the uplink.

If this is the case: Have you excluded the uplink from ELRP? (exclude-list parameter)

Another possibility is to look at 16.1 and the new ELRP capability to shut either ingress or egress port (where loop has been detected).

If that can't help for some specific design consideration, then your approach makes sense, but I wouldn't try to re-add the faulty port that way. Rather send a trap and let someone fix the loop before.

Edit: and if you're using Python, you could also send an email to notify the loop 

Python App (15.7 and above) can be multithreaded. Maybe that's where you want to look at. Need to figure out a way to detect the loop, maybe still through UPM. Need to validate that.
GTM-P2G8KFN