So in getting ready to configure company wide ELRP I was doing to some testing the other day.
The test case is a Summit200-24 running Image : Extremeware Version 7.8e.4.1
Issue is when ELRP detected a loop it disables the port. FIrst I didnt think Xware supported this feature............... In the example below I removed all ELRP instances, :
/01/2015 10:26:32.97 10.227.28.8 epicenter: configure elrp-client periodic Legacy interval 1 ports 1 , 2 , 25 log-and-trap
5/01/2015 10:26:24.20 10.227.28.8 epicenter: unconfigure elrp-client Legacy
Result is this:
05/01/2015 10:07:43.42 10.227.28.8 epicenter: disable ports 1
05/01/2015 10:07:42.24 Loop detected on port 1. Disabling port.
05/01/2015 10:07:42.24 Loop detected on port 2. Disabling port.
05/01/2015 10:07:42.23 Loop Detected on VLAN Legacy port sent 2 port received 1
05/01/2015 10:07:42.22 Loop Detected on VLAN Legacy port sent 1 port received 2
05/01/2015 10:07:41.07 Port 2 link active 100Mbs FULL duplex
05/01/2015 10:07:41.06 Port 1 link active 100Mbs FULL duplex
05/01/2015 10:07:39.16 10.227.28.8 epicenter: enable ports 1
05/01/2015 10:07:03.89 10.227.28.8 epicenter: disable ports 1
05/01/2015 10:05:00.55 Port 2 link down
I had a cable run between ports 1 and 2. Nowhere did we ever say to disable the port.. Notice that legacy just has log and trap, no mention of disabling the port, ....so why does the port get disabled? I also looked at sh conf detail, but nothing stood out
ty
