Cisco ASR 14000 Series, Management Command Reference

Page: 508 / 782

C i s c o C o n f i d e n t i a l - B e t a R e v i e w R 3 . 7. 1
Process and Memory Management Commands on Cisco IOS XR Software
exception filepath
SMR-506
Cisco ASR 14000 Series Router System Management Command Reference
OL-17231-01
Note
The Cisco IOS XR software does not save a core file on a local storage device if the size of the core dump
file creates a low-memory condition.
By default, the Cisco IOS XR software assigns filenames to core dump files according to the following
format:
process [.by. requester |.abort][.sparse]. date-time . node . processor-type [.Z]
For example:
packet.by.dumper_gen.20040921-024800.node0_RP0_CPU0.ppc.Z
Table 55 describes the default core dump filenaming convention.
You can modify the default naming convention by specifying a filename to be appended to core dump
files with the optional
filename keyword and filename argument and by specifying a lower and higher
limit ranges of values to be appended to core dump filenames with the lower-limit and higher-limit
arguments, respectively. The filename that you specify for the filename argument is appended to the core
dump file and the lower and higher limit ranges of core dump files to be sent to a specified destination
before the filenames are recycled. Valid values for the
lower-limit argument are 0 to 4. Valid values for
the higher-limit argument are 5 to 64. A hyphen ( - ) must immediately follow the lower-limit argument.
In addition, to uniquely identify each core dump file, a value is appended to each core dump file,
beginning with the lower-limit value specified with the
lower-limit argument and continuing until the
higher-limit value specified with the higher-limit keyword has been reached. When the configured
higher-limit value has been reached, the Cisco IOS XR software begins to recycle the values appended
to core dump files, beginning with the lower-limit value.
Table 55 Default Core Dump Filenaming Convention Description
Field Description
process Name of the process that generated the core dump.
.by. requester | .abort If the core dump was generated because of a request by a
process (requester), the core filename contains the string
“.by.
requester ” where the requester variable is the name or
process ID (pid) of the process that requested the core dump.
If the core dump was due to a self-generated abort call
request, the core filename contains the string “.abort” instead
of the name of the requester.
.sparse If a sparse core dump was generated instead of a full core
dump, “.sparse” appears in the core dump filename.
.date-time Date and time the dumper process was called by the process
manager to generate the core dump. The
.date-time
time-stamp variable is expressed in the
yyyy.mm.dd-hh.mm.ss format. Including the time stamp in
the filename uniquely identifies the core dump filename.
. node Node ID, expressed in the rack/slot/modul e notation, where
the process that generated the core dump was running.
.processor-type Type of processor (mips or ppc).
.Z If the core dump was sent compressed, the filename contains
the .Z suffix.