Reference Guide
PERQ_BYTE(0).cpu0 : 79,696 +79,696
PERQ_BYTE(41).cpu0 : 35,871,020 +35,871,020
PERQ_DROP_PKT(0).cpu0 : 217,930 +217,930
PERQ_DROP_PKT(41).cpu0 : 2,186,107,010 +2,186,107,010
PERQ_DROP_BYTE(0).cpu0 : 14,819,240 +14,819,240
PERQ_DROP_BYTE(41).cpu0 : 148,655,276,680 +148,655,276,680
QUEUE_PEAK(0).cpu0 : 224
QUEUE_PEAK(41).cpu0 : 236
RUC.xe0 : 2,756,973,184 +2,756,973,184
RDBGC0.xe0 : 2,186,634,525 +2,186,634,525
RDBGC5.xe0 : 2,186,634,525 +2,186,634,525
ING_NIV_RX_FRAMES.xe0 : 2,756,973,184 +2,756,973,184
TDBGC3.xe0 : 2,881,121 +2,881,121
TDBGC6.xe0 : 190,692,963,094 +190,692,963,094 12,017,817/s
TDBGC10.xe0 : 2,881,121 +2,881,121
R127.xe0 : 2,756,973,184 +2,756,973,184
RPKT.xe0 : 2,756,973,184 +2,756,973,184
Accessing Application Core Dumps
Core dumps for an application crash are enabled by default. On the Z9500, core dumps are generated and stored in the local
flash of the Z9500 Control Processor CPU. To access an application core-dump file, you must perform an FTP to the Control
Processor CPU flash directory where the application core dump is stored in the format: /flash/
CORE_DUMP_DIR
/
f10
cpu
_
application
_
timestamp
.acore.gz:
Where cpu specifies a Z9500 CPU and is one of the following values: cp (Control Processor), rp (Route Processor), lp0 (line-
card processor 0), lp1 (line-card processor 1), or lp2 (line-card processor 2);
application specifies the name of the executable that has crashed;
timestamp is a text string in the format: yymmddhhmmss (YearMonthDayHourMinuteSecond).
You can also configure the system to automatically move (upload) an application core dump to an external FTP server. Use the
logging coredump server server-ip-address username ftp-username password ftp-password
command in global configuration mode to configure an FTP server.
When you enter the logging coredump server command, you are required to enter a password. Use the password of the
FTP server where the core files are to be copied. The password can be up to 15 characters; special characters are allowed. After
you enter the password, an FTP URL is created with the credentials in the operating system. The CLI monitors application core
dumps in the unit.
NOTE:
On the Z9500, when you enable core dumps of application crashes to be uploaded to an FTP server, only core
dumps from the Control Processor are uploaded to the server. Application core-dump files from the Route Processor and
line-card CPUs are moved to flash memory on the Control Processor CPU and can be accessed by performing an FTP to
the Control Processor (CP) core-dump directory:
● The application core-dump file for the Route Processor is stored at: flash:/
CORE_DUMP_DIR
/
f10rp_
application
_
timestamp
.acore.gz
● The application core-dump file for a line-card processor is stored at:flash:/
CORE_DUMP_DIR
/f10lp
slot-
number
_
application
_
timestamp
.acore.gz
To disable the automatic uploading of application core dumps, enter the no logging coredump server command.
Mini Core Dumps
The system supports mini core dumps for kernel crashes. The mini core dump applies to all Z9500 CPUs.
Kernel mini core dumps are always enabled. Mini core dumps contain the stack space and some other very minimal information
that can be used to debug a crash. A mini core dump is a small file that is written into flash until space is exhausted. When the
flash is full, the write process is stopped.
A mini core dump contains critical information in the event of a crash. Mini core dump files are located in the flash://
CORE_DUMP_DIR directory. The kernel mini core filename format is f10_cpu_timestamp.kcore.mini.tx, where:
Where cpu specifies a Z9500 CPU and is one of the following values: cp (Control Processor), cp (Route Processor), lp0 (line-
card processor 0), lp1 (line-card processor 1), or lp2 (line-card processor 2);
Debugging and Diagnostics
263