Hi, could you elaborate on this bug, I think I might be having the same issue, my stack suddenly rebooted and this is from boot-history:
Member 1
Master -- Saved Crash Information (most recent first):
======================================================
ID: a70f63d7
Active/Commander system went down: 11/24/21 11:52:47 WC.16.09.0003 516
NMI event SW:PC=0x00000001 LR:0x034d1200 SP:0xf7 Task='mDsnoopCtrl' Task ID=0x2ab47298
ID: 65511af6
Standby system went down: 05/23/20 15:33:31 WC.16.09.0003 516
Reboot of Member ID 1, User reboot
ID: e96a2479
Active/Commander system went down: 05/23/20 15:07:17 WC.16.09.0003 516
Reboot of Member ID 1, User reboot
ID: 2fa30217
Active/Commander system went down: 05/23/20 15:06:50 WC.16.09.0003 516
Operator cold reboot from TELNET session.
------------------------------
Manny Taveroff
------------------------------
Original Message:
Sent: Feb 14, 2020 10:12 AM
From: AutoCreation
Subject: Bug enables operator user to reboot switch
Hi all,
a customer and I found a bug that enables operator privilege users to reboot AOS-S switches/stacks.
I will not include the exact procedure to replicate the bug here.
I just wanted to make sure this is not intended behavior.
Should I just open a case for this?
Regards