General
eWLC should not be crashed as per the scenario explained in the Summary.
Symptom
Steps to Reproduce:
1) Load the above image on to 9800-L controller
2) Have Maui AP and associate the Intel AX210 clients. In my case I am using Octoscope STAPALs.
3) Configure UDO or TCP traffic targetting more than 1200 Mbps which is greater than the thoeretical max of 1200 Mbps.
4) Controller will crash and generates the below message
*Dec 1 02:48:49.698: %WEBSERVER-5-SESS_LOGOUT: Chassis 1 Successfully logged out from host 10.21.123.66 by user 'admin' using crypto cipher 'TLS_AES_256_GCM_SHA384'Dec 1 02:54:05.013: %PMAN-3-PROCHOLDDOWN: F0/0: cpp_ha_top_level_server: The process cpp_ha_top_level_server has been helddown (rc 69)
Chassis 1 reloading, reason - Non participant detected
DeDec 1 02:54:27.526: %PMAN-3-PROCHOLDDOWN: F0/0: qfp-ucode-wlc: The process qfp-ucode-wlc has been helddown (rc 134)
Dec 1 02:54:28.448: %PMAN-5-EXITACTION: F0/0: pvp: Process manager is exiting: process exit with reload fru code
DDec 1 02:55:55.352: %PMAN-3-PROCESS_NOTIFICATION: R0/0: pvp: System report bootflash:core/Octo-Katar-2_1_RP_0-system-report_20221201-025529-Pacific.tar.gz (size: 78614 KB) generated and System report info at bootflash:core/Octo-Katar-2_1_RP_0-system-report_20221201-025529-Pacific-info.txt
Initializing Hardware ..
Conditions
eWLC with Maui AP and 8 AX210 Intel clients are used.