ARUBA vs HPE snmp-trap

I’ve been a long-time user of HPE/Aruba switches, and I’m currently migrating from HPE 5130 / 5140 (ProVision-based) to new Aruba OS-CX. Overall, OS-CX is a solid step forward, but there’s one feature we lost that hurts more than I expected: the SNMP trap that carries syslog messages (I think it was snmp-server enable traps syslog).

This was incredibly useful for two things:

1. Instant BPDU detection – When a rogue switch appears on the network, you get an SNMP trap within seconds. In a large environment, this is the fastest way to know which port is blocking. With OS-CX, you have to poll logs or rely on slower mechanisms.
2. Live command auditing – Every CLI command entered on the switch can be sent as a syslog message. By converting that into an SNMP trap, we could feed it directly into Zabbix (or any SNMP-aware NMS) and trigger alerts on dangerous commands, or just keep a real‑time audit trail. Losing this capability creates a blind spot.

I know OS-CX has webhooks, streaming telemetry, and better logging in general. But for those of us who rely on a simple, proven, SNMP‑based workflow (and don’t want to rebuild our whole monitoring stack), the absence of the “syslog as SNMP trap” is a real regression.

I’m currently moving my Zabbix setup from HPE 5130/5140 to new Aruba switches, and I’m genuinely sad to lose this trap. It worked flawlessly for years.

So my humble request to Aruba engineers: Please consider bringing back an option to send syslog messages as SNMP traps on OS‑CX. Even as a hidden “compatibility” knob. It would make the migration path much smoother for many of us.

Has anyone else found a workaround on OS‑CX to get the same kind of real‑time command or BPDU trap? Or is there a hidden feature I missed?

Thanks for reading.