crashdump

crashdump

Provides for configuration of crashdump per router platform.

Syntax: crashdump {server serverID | module bay/slot | bay bay/slot} [address address] [context context] [directory directory] [event event] [filename filename] [gateway gateway] [host host] [password password] [retry retry] [sequence sequence] [user user] [restrict]

serverID

Specifies the ID number of the route-controller. Valid Values: 1 - 64. Default: None

bay/slot

Specifies the bay and slot number of the module or bay-controller delineated by a forward-slash "/".

address

Specifies an IP address and mask on this module or router to use for the crashdump. Valid Values: any IP address with mask in the format A.B.C.D/XX. Default: IP address for ETH0. None for module and bay.

context

Specifies a crashdump context of task, interrupt, or both.

Valid Values: task for task context, interrupt for interrupt context, all for both task and interrupt context. Default: all.

directory

Specifies the host directory to receive the crashdump. Default: b:\CRASH for route-controller. Must be specified for module and bay.

event

Specifies the event type to enable. Valid Values: exception, fatal, panic, or all. Default: all.

filename

Specifies the filename generated for the crashdump. Default: SERV_ for route controller. The sequence number is appended to the filename. The filename must be specified for Module and Bay.

gateway

Specifies the gateway address to the host receiving the crashdump. Default: None.

host

Specifies the IP address of the host receiving the crashdump. Default: None.

password

Specifies an FTP password if required. Default: None.

retry

Specifies the number of seconds to wait before retrying transmission of the crashdump should transmission links not be available at the time of the failure. Default: 0.

sequence

Specifies a beginning sequence number to be appended to the filename. Valid Values: 0 - 255. Default: 0 if no file exists, next number in sequence if files exist.

user

Specifies an FTP user name if required. Default: None.

A crashdump provides a complete snapshot of route-controller or module state at the time of a failure within a task or interrupt context for each platform. A crashdump can be configured to trigger on exceptions, fatal, and panic conditions, or all three conditions. Crashdump configuration provides for the specification of filename and sequence number, IP address on this router for the crashdump to access the receiving location, receiving file location including IP address, host, gateway, directory, FTP user name and password, and a retry period in seconds should a crashdump fail to occur because of temporary link conditions.

By default, a route-controller crashdump resides on the b:\crash directory on the route-controller flash. The receiving location for module crashdumps must be specified.

NOTE Crashdumps create large files. Route-controller flash memory is limited to no more than two crashdumps.

The Avici crashdump implementation has a restrict feature that defaults to enabled (crashdump must be enabled for restrict to have any affect). In an NSR® system with restrict crashdump enabled, a primary route controller will initiate a crashdump only if another route controller is operational in a hot backup, warm backup or redundant state. This feature protects the system against an NSR® scenario where the primary goes down and crashdumps, and the backup becomes primary and subsequently goes down and crashdumps without an operational route controller to take over.

In a non-NSR® system with restrict crashdump enabled, a route controller will never auto initiate a crashdump. Enter the no crashdump server serverID restrict command after enabling crashdump in a non-NSR® system to disable the restrict feature.

NOTE The Restrict feature has changed the default behavior for crashdump in a non-NSR® system or an NSR® system that should find itself with no operational route controller. Under either of these conditions, enabling crashdump leaves crashdump in a disabled state until the restrict feature is disabled using the no crashdump server serverID restrict command.

Crashdump defaults to disabled for all platforms. When crashdump is enabled, the restrict feature defaults to enabled.

WARNING A crashdump takes a platform out of service for the entire period of the dump. Though the period of time is variable, in all cases it would constitute an excessive period within the operations of a live network. In a live network context, assure that the restrict feature is enabled using the show crashdump server command. The crashdump restrict feature assures that an operational route controller is currently available before allowing this route controller to crashdump. The restrict feature is enabled by default when entering a crashdump configuration. Usage of crashdump without the direct assistance of Avici customer support is not supported under any circumstances. Only trained technical personnel are capable of using the output of a crashdump.

Use the crashdump command in configuration command mode to configure and enable crashdump for this Avici router. The restrict feature is enabled by default when crashdump is configured.

Use the no crashdump command in configuration command mode to disable an existing crashdump configuration for this Avici router. Entering this command while only specifying the affected platform disable context for all events but has no affect on all other specific configuration. To disable or set to default all other values, the affected keyword must be specified in a separate command line.

Use the crashdump force command in privileged command mode specifying the platform and platform ID to force a previously configured and enabled crashdump for that platform.

Use the crashdump server serverID restrict command to enable the crashdump restrict feature on this route controller. This feature is enabled by default once a crashdump configuration is enabled.

Use the no crashdump server serverID restrict command to disable the crashdump restrict feature on this route controller. This command does not affect any other crashdump configuration for this route controller. To disable crashdump for a route controller use the no crashdump server serverID command specifying the context to disable.

Use the show crashdump command to display current configuration settings by specified platform.

Factory Default: Disabled.

Command Mode: Configuration.

Example 1: In the following example crashdump is configured and enabled on route-controller 1 to use ETH0 to write a crashdump to the FLASH directory b:\CRASH for all contexts and events.

router#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

router(config)#crashdump server 1

router(config)#exit

router#show crashdump server 1

Crash dump settings:

Exception from interrupt context - enabled

Exception from task context - enabled

Fatal call from interrupt context - enabled

Fatal call from task context - enabled

Panic call from interrupt context - enabled

Panic call from task context - enabled

host inet:

inet on ethernet: 192.168.1.51 255.255.255.0

gateway inet:

user:

ftp password: (none)

crashdump directory:

retry: 0

sequence number: 0

filename:

crashdump restrict feature: ON

crashdump file writing: ENABLED

router#

Example 2: In the following example:

Enter configuration mode using the configure terminal command.

Configure crashdump on route-controller 1 to send the crashdump to host 192.168.1.61 and for the crashdump to reside in the c:\crash directory.

Use the no crashdump command to clear any current context and event configuration to assure the interrupt and fatal only configuration.

Use the context keyword to set the interrupt and the event keyword to set the fatal settings.

Display the current configuration using the show crashdump server command.

router#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

router(config)#crashdump server 1 host 192.168.1.61 directory c:\crash

router(config)#no crashdump server 1 context all event all

router(config)#crashdump server 1 context interrupt event fatal

router(config)#exit

router#show crashdump server 1

Crash dump settings:

Exception from interrupt context - disabled

Exception from task context - disabled

Fatal call from interrupt context - enabled

Fatal call from task context - disabled

Panic call from interrupt context - disabled

Panic call from task context - disabled

host inet: 192.168.1.61

inet on ethernet: 192.168.1.51 255.255.255.0

gateway inet:

user:

ftp password: (none)

crashdump directory: c:\crash

retry: 0

sequence number: 0

filename:

crashdump restrict feature: ON

crashdump file writing: ENABLED

router#

Example 3: In the following example the crashdump force server command is used to force a crashdump on route-controller 1 based upon the current configuration of crashdump for that route-controller

router#crashdump force server 1

router#

Example 4: In the following example, crashdump is first enabled on the route controller 1. Secondly, crashdump restrict is disabled on route-controller 1 allowing crashdump to auto-initiate when the primary goes down and no other operational route controller exists:

router#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

router(config)#crashdump server 1

router(config)#no crashdump server 1 restrict

router(config)#exit

router#show crashdump 1

Crash dump settings:

Exception from interrupt context - enabled

Exception from task context - enabled

Fatal call from interrupt context - enabled

Fatal call from task context - enabled

Panic call from interrupt context - enabled

Panic call from task context - enabled

host inet: 10.2.21.116

inet on ethernet: 10.200.161.41 255.255.0.0

gateway inet: 10.200.0.1

user: labman1

ftp password: (none)

crashdump directory:

retry: 0

sequence number: 16

filename: ha161s1

crashdump restrict feature: OFF

crashdump file writing: ENABLED

router#

Related Commands: crashdump force
show crashdump

serverID	Specifies the ID number of the route-controller. Valid Values: 1 - 64. Default: None
bay/slot	Specifies the bay and slot number of the module or bay-controller delineated by a forward-slash "/".
address	Specifies an IP address and mask on this module or router to use for the crashdump. Valid Values: any IP address with mask in the format A.B.C.D/XX. Default: IP address for ETH0. None for module and bay.
context	Specifies a crashdump context of task, interrupt, or both. Valid Values: task for task context, interrupt for interrupt context, all for both task and interrupt context. Default: all.
directory	Specifies the host directory to receive the crashdump. Default: b:\CRASH for route-controller. Must be specified for module and bay.
event	Specifies the event type to enable. Valid Values: exception, fatal, panic, or all. Default: all.
filename	Specifies the filename generated for the crashdump. Default: SERV_ for route controller. The sequence number is appended to the filename. The filename must be specified for Module and Bay.
gateway	Specifies the gateway address to the host receiving the crashdump. Default: None.
host	Specifies the IP address of the host receiving the crashdump. Default: None.
password	Specifies an FTP password if required. Default: None.
retry	Specifies the number of seconds to wait before retrying transmission of the crashdump should transmission links not be available at the time of the failure. Default: 0.
sequence	Specifies a beginning sequence number to be appended to the filename. Valid Values: 0 - 255. Default: 0 if no file exists, next number in sequence if files exist.
user	Specifies an FTP user name if required. Default: None.

router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#crashdump server 1 router(config)#exit router#show crashdump server 1 Crash dump settings: Exception from interrupt context - enabled Exception from task context - enabled Fatal call from interrupt context - enabled Fatal call from task context - enabled Panic call from interrupt context - enabled Panic call from task context - enabled host inet: inet on ethernet: 192.168.1.51 255.255.255.0 gateway inet: user: ftp password: (none) crashdump directory: retry: 0 sequence number: 0 filename: crashdump restrict feature: ON crashdump file writing: ENABLED router#

router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#crashdump server 1 host 192.168.1.61 directory c:\crash router(config)#no crashdump server 1 context all event all router(config)#crashdump server 1 context interrupt event fatal router(config)#exit router#show crashdump server 1 Crash dump settings: Exception from interrupt context - disabled Exception from task context - disabled Fatal call from interrupt context - enabled Fatal call from task context - disabled Panic call from interrupt context - disabled Panic call from task context - disabled host inet: 192.168.1.61 inet on ethernet: 192.168.1.51 255.255.255.0 gateway inet: user: ftp password: (none) crashdump directory: c:\crash retry: 0 sequence number: 0 filename: crashdump restrict feature: ON crashdump file writing: ENABLED router#

router#crashdump force server 1 router#

router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#crashdump server 1 router(config)#no crashdump server 1 restrict router(config)#exit router#show crashdump 1 Crash dump settings: Exception from interrupt context - enabled Exception from task context - enabled Fatal call from interrupt context - enabled Fatal call from task context - enabled Panic call from interrupt context - enabled Panic call from task context - enabled host inet: 10.2.21.116 inet on ethernet: 10.200.161.41 255.255.0.0 gateway inet: 10.200.0.1 user: labman1 ftp password: (none) crashdump directory: retry: 0 sequence number: 16 filename: ha161s1 crashdump restrict feature: OFF crashdump file writing: ENABLED router#

   Source File Name: sys_mgmt.fm
    HTML File Name: sys_mgmt15.html
    Last Updated: 02/25/05 at 14:26:49

crashdump

Please email suggestions and comments to: doc@avici.com