Accessing the Core Dump Files

If a module fails and saves a core dump file to NVS memory (which can take several minutes), and you have not configured the Core Dump Monitor for automatic transfer, you must transfer the file to a network host before it can be examined. You can transfer the core dump file when the module is back online or has assumed a redundant status. For information about the status of modules, see the Troubleshooting chapter in the ERX Hardware Guide. To transfer the core dump file to a network host, use the copy command.

In a system with two SRP modules, the following behavior applies if you have configured the SRP modules to save core dump files to an FTP server:

The show version command output indicates the failed SRP module state as not responding during the save process. Consequently, when the failed SRP module recovers and assumes the role of redundant module, the show version command output indicates the SRP module state as standby and displays output for the standby SRP. The standby SRP can notify the primary SRP during a core dump. Output from the show version command displays core dumping for the Standby SRP.

If the standby SRP boot image encounters a problem loading the diagnostics or operational image, the state of the standby SRP appears as disabled (image error). When standby SRP diagnostics encounter a test failure, the primary SRP is notified and the state is set to hardware error. You can now transfer the core dump file to a network host for examination.

To transfer a file from NVS of the failed SRP module to the host:

Related Documentation