The syntax is an enumerated INTEGER of disabled(0) or enabled(1), and the desc confirms this is the current status of SecureXL. SecureXL offloads bulk packet forwarding from the firewall's slow path into an accelerated fast path, so seeing this flip to disabled(0) on a gateway that is supposed to have it enabled is a major performance red flag — expect a sharp rise in CPU load and latency on high-throughput links right afterward. e.g. fwSXLStatus = 1 (enabled) normally, flipping to 0 after a troubleshooting session where an admin disabled it to debug a connection issue and forgot to re-enable it.