show monitor event-trace

 

 

 

 

 

 

 

 

 

 

 

Release

Modification

 

 

 

 

 

 

 

 

 

 

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB and

 

 

 

 

 

implemented on the Cisco 10000 series routers.

 

 

 

 

 

 

 

 

 

12.4(9)T

The cfd keyword was added as an entry for the component argument to

 

 

 

 

 

display trace messages relating to crypto fault detection.

 

 

 

 

 

 

 

 

 

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

 

 

 

 

 

 

 

 

 

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

 

 

 

 

 

 

 

 

 

12.2(33)SB

This command was integrated into Cisco IOS Release 12.2(33)SB.

 

 

 

 

 

 

 

 

 

12.4(20)T

This command was integrated into Cisco IOS Release 12.4(20)T.

 

 

 

 

 

 

 

Use the show monitor event-tracecommand to display trace message information.

Usage Guidelines

 

 

 

 

The trace function is not locked while information is being displayed to the console, which means that

 

 

 

new trace messages can accumulate in memory. If entries accumulate faster than they can be displayed,

 

 

 

some messages can be lost. If this happens, the show monitor event-tracecommand will generate a

 

 

 

message indicating that some messages might be lost; however, messages will continue to display on the

 

 

 

console. If the number of lost messages is excessive, the show monitor event-tracecommand will stop

 

 

 

displaying messages.

 

 

 

 

 

 

 

 

 

Use the bfd keyword for the component argument to display trace messages relating to the BFD feature.

 

 

 

Use the cfd keyword for the component argument to display trace messages relating to the crypto fault

 

 

 

detection feature. This keyword displays the contents of the error trace buffers in an encryption data path.

 

 

IPC Component Example

 

 

 

 

 

 

Examples

 

 

 

 

 

 

 

 

 

 

The following is sample output from the show monitor event-tracecomponent command for the

 

 

 

interprocess communication (IPC) component. Notice that each trace message is numbered and is

 

 

 

followed by a time stamp (derived from the device uptime). Following the time stamp is the

 

 

 

component-specific message data.

 

 

 

Router# show monitor event-trace ipc

 

 

3667:

6840.016:Message type:3 Data=0123456789

 

 

3668:

6840.016:Message type:4 Data=0123456789

 

 

3669:

6841.016:Message type:5 Data=0123456789

 

 

3670:

6841.016:Message type:6 Data=0123456

 

 

 

BFD Component for Cisco IOS Release 12.2(18)SXE, 12.0(31)S, and 12.4(4)T

 

 

 

Use the show monitor event-trace bfd all command to display logged messages for important BFD

 

 

 

events in the recent past. The following trace messages show BFD session state changes:

 

 

 

Router# show monitor event-trace bfd all

 

 

 

 

3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1], event Session

 

 

 

 

create, state Unknown -> Fail

 

 

 

 

3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1], state Fail -> Down

 

 

 

 

(from LC)

 

 

 

 

 

 

 

 

 

 

3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1], state Down -> Init

 

 

 

 

(from LC)

 

 

 

 

 

 

 

 

 

 

3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1], state Init -> Up

 

 

 

 

(from LC)

 

 

 

 

 

 

 

 

 

 

3d07h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,2], event Session

 

 

 

 

create, state Unknown -> Fail

 

 

 

 

 

Cisco IOS Configuration Fundamentals Command Reference

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

July 2008

 

 

 

 

 

CF-761

 

 

 

 

 

 

 

 

Page 85
Image 85
Cisco Systems 12000 series manual Component-specific message data, CF-761, Router# show monitor event-trace ipc