Step 1 |
enable
Example:
|
Enables privileged EXEC mode.
- Enter your password if prompted.
|
Step 2 |
configure
terminal
Example:
Device# configure terminal
|
Enters global configuration mode.
|
Step 3 |
monitor event-trace voip ccsip trace-type [size number]
Example:
Device(config)# monitor event-trace voip ccsip api size 50
|
Enables event tracing for various Voice Over IP (VoIP) CCSIP API events.
Event tracing for other events, such as Finite State Machine (FSM), Communicating Nested FSM (CNFSM), miscellaneous, message, and global events can be enabled in a similar way.
|
Step 4 |
monitor event-trace voip ccsip dump dump-type
Example:
Device(config)# monitor event-trace voip ccsip dump marked
|
(Optional) Specifies the automatic dump policy for VoIP CCSIP events. Available options are marked, all, or none (default).
|
Step 5 |
monitor event-trace voip ccsip dump-file file-name
Example:
Device(config)# monitor event-trace voip ccsip
dump-file slot0:ccsip-dump-file
OR
Device(config)#monitor event-trace voip ccsip dump-file ftp://username:password@server_ip//path/ccsip-dump-file
OR
Device(config)#monitor event-trace voip ccsip dump-file tftp://server_ip//path/ccsip-dump-file.txt
|
(Optional) Specifies the file where event trace messages are written from memory to permanent storage.
You can also configure the folder for the dump-file using the
monitor event-trace voip ccsip dump-file folder_path command. The folder path can be flash:folder_name
or bootflash:folder_name, usb0:folder_name, or harddisk:folder_name.- If there is a failure in configuring the dump file, then a syslog is generated as follows: %SIP-5-EVENT_TRACE_PATH_ERR: Event Trace Dump PATH "tftp://223.255.254.254/eventtrace" not accesible. Verify credentials, directory path and network connectivity.
|
Step 6 |
monitor event-trace voip ccsip limit connections max-connections
Example:
Device(config)# monitor event-trace voip ccsip limit connections 500
|
(Optional) Limits the resources used by the event tracing mechanism based on the number of connections or call legs.
The default limit is 1000 connections.
|
Step 7 |
monitor event-trace voip ccsip limit memory size
Example:
Device(config)# monitor event-trace voip ccsip limit memory 50
|
(Optional) Limits the resources used by the event tracing mechanism to 50 MBytes.
|
Step 8 |
monitor event-trace voip ccsip stacktrace number
Example:
Device(config)# monitor event-trace voip ccsip stacktrace 9
|
(Optional) Enables the stack trace at tracepoints and specifies the depth of
the stack trace stored.
|
Step 9 |
monitor event-trace voip ccsip dump-folder size size
Example:
Device(config)# monitor event-trace voip ccsip dump-folder size 20
OR
Device(config)# monitor event-trace voip ccsip dump-folder time 500
|
(Optional) Configures the dump-folder size (or time) based on the storage available for the rotation of files. You can also configure the dump-folder time using the
monitor event-trace voip ccsip dump-folder timetime command.
- Sub-folders are created by CUBE under the user-created folder based on timestamp. When one of the above conditions (size or time) is met, folder rotation happens creating a new folder, and CUBE continues to dump the new event trace files to the new folder.
- Each folder contains a file
et_fold_size,
which captures the size of the folder that is used
for folder rotation.
|
Step 10 |
monitor event-trace voip ccsip max-dump-limit size_in_MB
Example:
Device(config)# monitor event-trace voip ccsip max-dump-limit 1000
|
(Optional) Sets the limit of the maximum size of event traces.
- This command creates a file in flash with the name et_fold_size, which is used to store the current size used by event traces.
- Once the event trace size reaches the configured maximum dump limit, then the event trace folder is automatically purged. The folder created first (oldest) is purged first. All files under a folder are deleted in a purge.
- Select the maximum-dump-limit based on the space available in storage.
|
Step 11 |
monitor event-trace voip ccsip dump all periodic
Example:
Device(config)# monitor event-trace voip ccsip dump all periodic
|
(Optional) Dumps the buffer content to file when the buffer is full.
- When the buffer is full, the content is written or appended to same file so that all event traces for a particular leg is available in a single file.
- Periodic dump is applicable for all and marked dumping.
- Periodic dump can be configured for binary or pretty format.
|
Step 12 |
monitor event-trace voip ccsip dump marked
Example:
Device(config)# monitor event-trace voip ccsip dump marked
|
(Optional) Configures dumping of marked traces.
- There are certain conditions, which handle fatal and unexpected events; the call will be disconnected abnormally in such cases. Trace-marks are added to capture these details in event trace. These trace-marks are pre-defined in CUBE and you can configure to dump these traces.
|
Step 13 |
exit
Example:
|
Exits global configuration mode.
|