This article describes how to generate NSPPE core dump on NetScaler.
When NetScaler, whether standalone or HA pair, has a problem that requires you to reboot, it is advisable to generate a NSPPE core dump in order to save any evidence of the problem for later analysis by technical support. This triggers the device to restart (and lose network connectivity) while dumping the core which would help us with the RCA for high memory usage.
If we discover that a NetScaler is on high memory usage then we need to go to /var/nslog and then verify the newnslog to check ConMEM to see which module/pool is taking up majority of the memory.
Then we suggest to perform a NSPPE core dump with which NetScaler would reboot and recover from the memory leak condition. While doing so it would dump a core file for each packet engine which can be investigated offline to identify the root cause for high memory condition.Complete the following steps to generate the NSPPE:
Log on to NetScaler using SSH session or serial console.
Go to shell prompt and run the command:
ns# pb_policy -o abort
Do ps and kill any of the NSPPE with the PID.
Run the following command to obtain the PID:
ps -aux | grep -i ppe
Set the default pitboss policy after the system comes back up:
pb_policy -d