Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Managing the Core Dump Files

    When a core dump occurs on a redundant SRP and you have the router configured to store network core dumps, the SRP that experiences the trouble retains the management Ethernet port to perform the core dump. This prevents the standby SRP from taking over operations until the core dump is complete.

    When a router uses local NVS to store a core dump, the SRP does not need the management Ethernet port. However, because of the immense size of local core dump files, using NVS to store core dumps is not practical.

    The SRP-120 available on the E120 router and the SRP-320 available on the E120 and E320 routers has a second NVS card which is dedicated to storing core dump files.

    The core dump monitor eliminates the impact that core dumps may have on redundant routers by allowing you to manage core dump files in NVS. The core dump monitor allows you to automatically transfer core dump files from NVS to an FTP server location for storage. The core dump monitor can also automatically delete transferred core dump files.

    The core dump monitor attempts to delete transferred files when all of the following conditions have been met:

    • The router attempts to write a core dump file to NVS.
    • NVS contains insufficient space to hold the new core dump file.
    • The core dump files have already been transferred from NVS to an FTP server location using the automatic core dump monitor transfer process.

    Only those core dump files that have already been transferred from NVS are considered for deletion. Of those, the oldest files are deleted first, and the router generates a log message for each core dump file it deletes.

    Note: If the router NVS does not contain sufficient space to hold a new core dump file even after deleting all possible core dump files, the core dump fails and the router generates a log message for this condition.

    This section describes the following:

    Enabling and Disabling the Core Dump Monitor

    The core dump monitor is disabled by default. To enable the core dump monitor, use the exception monitor command. To send the file to an FTP server, enter the IP address of the FTP server and the name of the directory on the server to which the system will transfer the file. Use the no version of this command to disable the core dump monitor.

    Enabling the core dump monitor specifies that future core dump files be saved to NVS. See exception dump command for details.

    Note: You can use exception protocol ftp command to assign a username and password to the targeted FTP server. If you choose not to define a username or password, the router uses the values of “ anonymous” and “ null,” respectively.

    To enable the router core dump monitor and specify the location to which you want the router to transfer core dump files:

    • Issue the exception monitor command in Global Configuration mode.
      host1(config)#exception monitor 192.168.56.7 CORE_DUMPS

    Configuring the Core Dump Monitor Interval

    You can use the exception monitor interval command to specify the length of time that the router waits between checking for core dump files.

    To specify the interval (in minutes) at which you want the router to check NVS for core dump files:

    • Issue the exception monitor interval command in Global Configuration mode.
      host1(config)#exception monitor interval 1000

      Use the no version to revert the core dump monitor interval to its default value of 60 minutes (1 hour).

    Published: 2014-08-12