Strange behaviour while adding port to sharing group

[Valur_Hjartarso]

Hello.
I have a ring of 4 X670-48x running exos "15.5.3.4 patch1-6". Each switch are connected to its neighbour with 4x10gig sharing group links, and also to 4 cisco cat6509 with similar 4x10gig sharing group links - like this http://i.imgur.com/wC0vLYd.jpg
So last night i've tried to add empty enabled port to one sharing group between cisco and extreme.
This is the existing sharing group:
enable sharing 17 grouping 17-20 algorithm address-based L3_L4 lacpAnd this was the command
conf sharing 17 add ports 21and the whole ring crashed. I've lost access to all network and was saved only by rebooting that switch.
What did I do wrong?

[Valur_Hjartarso]

I had like this experience with sharing group between extreme and juniper. But in my case the ring crashed after plugging the new port. That was a juniper problem for mode negotiation not related to extreme. I think your case is related to xos image. try to get it upgraded to recent one.

[BrandonC]

Hi Valur,

One more question in addition to the ones Prashanth asked. Was the switch where the LAG changes were made the EAPS master? Or was it just a transit node?

-Brandon

[Prashanth_KG]

Hi Valur,

Before we could jump into any conclusions about what could have happened, please clarify the following:
- On the ports connecting to the CISCO, are you using STP to prevent the loop? If so, are those ports untagged or tagged in the STP VLANs?
- When the problem happened, you had mentioned that the ring crashed. Can you elaborate on that? Did you experience a situation where the secondary port was open and the loop occurred within the ring?

In my opinion, EAPS should not break for any changes that are made outside the ring ports.
Awaiting your response!

[Husam_Abu_Hasan]

I had like this experience with sharing group between extreme and juniper. But in my case the ring crashed after plugging the new port. That was a juniper problem for mode negotiation not related to extreme. I think your case is related to xos image. try to get it upgraded to recent one.