Core File Exporter

Core File Exporter

Critical failures in the Cisco UCS components, such as a fabric interconnect or an I/O module, can cause the system to create a core dump file. Cisco UCS Manager uses the Core File Exporter to immediately export the core dump files to a specified location on the network through TFTP. This functionality allows you to export the tar file with the contents of the core dump file. The Core File Exporter provides system monitoring and automatic export of core dump files that need to be included in TAC cases.

Configuring the Core File Exporter

Procedure

  Command or Action Purpose

Step 1

UCS-A# scope monitoring

Enters monitoring mode.

Step 2

UCS-A /monitoring # scope sysdebug

Enters monitoring system debug mode.

Step 3

UCS-A /monitoring/sysdebug # enable core-export-target

Enables the core file exporter. When the core file exporter is enabled and an error causes the server to perform a core dump, the system exports the core file via TFTP to the specified remote server.

Step 4

UCS-A /monitoring/sysdebug # set core-export-target path path

Specifies the path to use when exporting the core file to the remote server.

Step 5

UCS-A /monitoring/sysdebug # set core-export-target port port-num

Specifies the port number to use when exporting the core file via TFTP. The range of valid values is 1 to 65,535.

Step 6

UCS-A /monitoring/sysdebug # set core-export-target server-description description

Provides a description for the remote server used to store the core file.

Step 7

UCS-A /monitoring/sysdebug # set core-export-target server-name hostname

Specifies the hostname of the remote server to connect with via TFTP.

Step 8

UCS-A /monitoring/sysdebug # commit-buffer

Commits the transaction.

Example

The following example enables the core file exporter, specifies the path and port to use when sending the core file, specifies the remote server hostname, provides a description for the remote server, and commits the transaction. 

UCS-A# scope monitoring
UCS-A /monitoring # scope sysdebug
UCS-A /monitoring/sysdebug # enable core-export-target
UCS-A /monitoring/sysdebug* # set core-export-target path /root/CoreFiles/core
UCS-A /monitoring/sysdebug* # set core-export-target port 45000
UCS-A /monitoring/sysdebug* # set core-export-target server-description CoreFile102.168.10.10
UCS-A /monitoring/sysdebug* # set core-export-target server-name 192.168.10.10
UCS-A /monitoring/sysdebug* # commit-buffer
UCS-A /monitoring/sysdebug #

Disabling the Core File Exporter

Procedure

  Command or Action Purpose

Step 1

UCS-A# scope monitoring

Enters monitoring mode.

Step 2

UCS-A /monitoring # scope sysdebug

Enters monitoring system debug mode.

Step 3

UCS-A /monitoring/sysdebug # disable core-export-target

Disables the core file exporter. When the core file exporter is disabled core files are not automatically exported.

Step 4

UCS-A /monitoring/sysdebug # commit-buffer

Commits the transaction.

Example

The following example disables the core file exporter and commits the transaction.

UCS-A# scope monitoring
UCS-A /monitoring # scope sysdebug
UCS-A /monitoring/sysdebug # disable core-export-target
UCS-A /monitoring/sysdebug* # commit-buffer
UCS-A /monitoring/sysdebug #