The log message identifies the cause directly:
Port 1/1/24 disabled - BPDU received on protected port
This is the characteristic behavior of BPDU Guard . HPE Aruba Networking documents that when BPDU Guard is enabled on an interface, receipt of an MSTP BPDU causes the interface to be disabled . The feature is intended primarily for edge ports connected to endpoints that should never participate in spanning tree. Aruba Networks
Port 1/1/24 now connects to another switch , so receiving BPDUs is legitimate and expected. The aggregation-facing connection needs to participate in spanning-tree topology calculations. BPDU Guard should therefore be removed from that interface with:
interface 1/1/24
no spanning-tree bpdu-guard
HPE Aruba ' s event documentation also defines the corresponding log event as a protected port being disabled after receiving a BPDU, exactly matching the exhibit. Aruba Networks
BPDU filter is not the problem. A BPDU-filtered interface suppresses BPDU transmission/reception but normally remains forwarding; it does not generate the displayed protected-port BPDU Guard shutdown event. Aruba Networks Loop protection addresses different Layer 2 failure conditions, while “MSTP guard” does not correspond to the explicit event shown.
Study Guide References: MSTP; BPDU Protection; spanning-tree bpdu-guard; Switch-to-Switch Links; STP Event Logging; Layer 2 Loop Prevention.