Table Of Contents

Performance Management Debug Commands on Cisco IOS XR Software

debug performance-mgmt pm-collector

debug performance-mgmt pm-server

Performance Management Debug Commands on Cisco IOS XR Software

---

This chapter describes the commands used to debug the Performance Management module on Cisco IOS XR software.

debug performance-mgmt pm-collector

To display the information related to performance management processes, use the debug performance-mgmt pm-collector command in EXEC mode. To disable the performance management debugging, use the no form of this command.

debug performance-mgmt pm-collector [checkpoint | messaging | scheduler | server-restart]

no debug performance-mgmt pm-collector [checkpoint | messaging | scheduler | server-restart]

Syntax Descriptions

checkpoint	Displays the checkpoint diagnostics for the PM Collector.
messaging	Displays the report messages received and sent by the PM Collector.
scheduler	Displays the task scheduling diagnostics for the PM Collector.
server-restart	Displays the diagnostics regarding the restart of PM Server.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release	Modification
Release 3.6.0	This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID	Operations
Monitor	read

Examples

The following example shows the output of the scheduler when the debug performance-mgmt pm-collector command is executed on the router:

RP/0/RP0/CPU0:router# debug performance-mgmt pm-collector scheduler

RP/0/RP0/CPU0:Jan 14 14:53:28.635 : pm_collector[390]: [ReqID 20] Data collection start 
(status:DATA_COLLECT SP=0)

RP/0/RP0/CPU0:Jan 14 14:53:28.708 : pm_collector[390]: [ReqID 20] Data collection complete

RP/0/RP0/CPU0:Jan 14 14:53:28.708 : pm_collector[390]: [ReqID 20] *** Sampling task 
complete *** (status: IDLE)

debug performance-mgmt pm-server

To display information about the performance of the server, use the debug performance-mgmt pm-server command in EXEC mode. To disable the performance management debugging, use the no form of this command.

debug performance-mgmt pm-server [checkpoint | collector-restart | messaging]

no debug performance-mgmt pm-server [checkpoint | collector-restart | messaging]

Syntax Description

checkpoint	Displays the checkpoint diagnostics for the PM server restartability.
collector-restart	Displays the report diagnostics regarding PM collector restartability. The following events and messages are included: •GSP notification events (pm_collector joins or leaves the group) •Restart messages sent from pm_collector
messaging	Displays the message contents sent by the PM server.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release	Modification
Release 3.6.0	This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID	Operations
Monitor	read

Examples

The following example shows sample output of the messaging activities using the debug performance-mgmt pm-server command on the router:

RP/0/RP0/CPU0:router# debug performance-mgmt pm-server messaging

RP/0/RP0/CPU0:Jan 14 15:13:55.041 : pm_server[391]: PM Server sending :PM_START_COLLECTION 
message of length: 32

RP/0/RP0/CPU0:Jan 14 15:13:55.042 : pm_server[391]: Header: req_code: 1, req_id: 8, 
entity_type:8, attr_count:2, memory max_limit:51200, usage:180160,min-reserved:10240

RP/0/RP0/CPU0:Jan 14 15:13:55.042 : pm_server[391]: Content: attr_id1:1, attr_val1:15, 
attr_id2:2, attr_val2:2

RP/0/RP0/CPU0:Jan 14 15:13:55.049 : pm_server[391]: Message response. Retcode:No error, 
Mem reqd:80488

RP/0/RP0/CPU0:Jan 14 15:13:55.049 : pm_server[391]: New memory usage:260648