Share group vanishes after reboot

[davidj_cogliane]

I believe I understand why the issues occurs, but am curious if it is expected behavior or a bug. See config below (I don't how how we managed to configure it)

1:17 LACP 1 L2 A 1:17 - R 2
L2 1:18 - R 0
L2 2:17 - R 0
L2 2:18 - R 2

Port: 1:17(to_Firewall):
Virtual-router: VR-Default
Type: 1000T
Random Early drop: Unsupported
Admin state: Enabled with auto-speed sensing (1G Advertised), auto-duplex
Port: 1:18(to_Firewall):
Virtual-router: VR-Default
Type: NONE
Random Early drop: Unsupported
Admin state: Enabled with 10G full-duplex
Port: 2:17(to_Firewall):
Virtual-router: VR-Default
Type: NONE
Random Early drop: Unsupported
Admin state: Enabled with 10G full-duplex
Port: 2:18(to_Firewall):
Virtual-router: VR-Default
Type: 1000T
Random Early drop: Unsupported
Admin state: Enabled with auto-speed sensing (1G Advertised), auto-duplex

Obviously you can't have an LACP share group with different speed ports but as you can see it is configured and functions. The behavior that we noted was that even though the config was saved the share group was gone after a reboot.

My theory is as follows:
The switch must load the config line by line after the reboot. The port speed loads before the share group is created so the share group line fails to load and is removed from the config.

Am I correct?
Is this expected behavior or a bug?
Or is the bug whatever loop whole allowed us to create the config?

I would argue that anything that causes or allows the config to be changed by a reboot is a bug.

Thanks,

Forgot to mention:

summitX-21.1.4.4-patch1-6.xos
Slot-1 X670G2-48x-4q X670G2-48x-4q Operational 64
Slot-2 X670G2-48x-4q X670G2-48x-4q Operational 64

[Ron_Huygens]

Interesting topic.
In my lab I was not able to replicate. I tried several scenarios and most of the times it was simply denied by EXOS.
Only inserting the 1000T will not show an error but in all cases the share will stay in the config after a reboot.

Any change that you can remember the exact order of steps?

[davidj_cogliane]

Yes,
I did wonder if we created the share group then inserted the 1G optic and that changed the advertised speed which created the conflict.

I really think that is what we did, but I guess I didn't think inserting an optic would write a line to the config.