HPE FlexNetwork 10500 SERIES, Configuration Manual

Page: 220 / 407

209
Task Command Remarks
Display memory usage for all user
processes.
display process memory
[ chassis chassis-number slot
slot-number [ cpu cpu-number ] ]
N/A
Display heap memory usage for a
user process.
display process memory heap
job job-id [ verbose ] [ chassis
chassis-number slot slot-number
[ cpu cpu-number ] ]
N/A
Display the addresses of memory
blocks with a specified size used
by a user process.
display process memory heap
job job-id size memory-size
[ offset offset-size ] [ chassis
chassis-number
slot
slot-number
[ cpu cpu-number ] ]
N/A
Display memory content starting
from a specified memory block for
a user process.
display process memory heap
job job-i d address
starting-address length
memory-length [
chassis
chassis-number slot slot-number
[ cpu cpu-number ] ]
N/A
Display context information for
process exceptions.
display exception context
[ count value ] [ chassis
chassis-number slot slot-number
[ cpu cpu-number ] ]
N/A
Display the core file directory.
display exception filepath
[ chassis chassis-number slot
slot-number [
cpu
cpu-number ] ]
N/A
Enable or disable a process to
generate core files for exceptions
and set the maximum number of
core files (which defaults to 1).
process core { maxcore value |
off } { job job-id | name
process-name } [
chassis
chassis-number slot slot-number
[ cpu cpu-number ] ]
By default, a process generates a
core file for the first exception and
does not generate any core files
for subsequent exceptions.
Specify the directory for saving
core files (the default directory
depends on the device model).
exception filepath directory
The default directory is the root
directory of the
flash: file system
on the global active MPU.
Clear context information for
process exceptions.
reset exception context
[ chassis chassis-number slot
slot-number [ cpu cpu-number ] ]
N/A
Monitoring kernel threads
Tasks in this section help you quickly identify thread deadloop and starvation problems and their
causes.
Configuring kernel thread deadloop detection
CAUTION:
As a best practice, use the default settings. Inappropriate configuration of kernel thread deadloop
detection can cause service problems or system breakdown. Make sure you understand the impact
of this configuration on your network before you configure kernel thread deadloop detection.
Kernel threads share resources. If a kernel thread monopolizes the CPU, other threads cannot run,
resulting in a deadloop.