Table Of Contents
Performance Management Commands on Cisco IOS XR Software
monitor controller fabric
monitor controller sonet
monitor interface
performance-mgmt apply monitor
performance-mgmt apply statistics
performance-mgmt apply thresholds
performance-mgmt resources memory
performance-mgmt resources tftp-server
performance-mgmt statistics
performance-mgmt thresholds
show performance-mgmt bgp
show performance-mgmt interface
show performance-mgmt mpls
show performance-mgmt node
show running performance-mgmt
show system verify
Performance Management Commands on Cisco IOS XR Software
This chapter describes the performance management and monitoring commands on the Cisco IOS XR software used to monitor, collect, and report statistics, and to adjust statistics gathering for Border Gateway Protocol (BGP), Open Shortest Path First (OSPF) protocol, generic interfaces, and individual nodes.
For detailed information about performance management concepts, configuration tasks, and examples, see the Implementing Performance Management on Cisco IOS XR Software module in Cisco IOS XR System Monitoring Configuration Guide.
monitor controller fabric
To monitor controller fabric counters in real time, use the monitor controller fabric command in EXEC mode.
monitor controller fabric {plane-id | all}
Syntax Description
plane-id
|
Plane ID number of the fabric plane to be monitored. The range is from 0 to 7.
|
all
|
Monitors all fabric planes.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
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, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the monitor controller fabric command to display controller fabric counters. The display refreshes every 2 seconds.
The interactive commands that are available during a controller fabric monitoring session are described in Table 1.
Table 1 Interactive Commands Available for the monitor controller fabric Command
Command
|
Description
|
c
|
Resets controller fabric counters to 0.
|
f
|
Freezes the display screen, thereby suspending the display of fresh counters.
|
t
|
Thaws the display screen, thereby resuming the display of fresh counters.
|
q
|
Terminates the controller fabric monitoring session.
|
s
|
Enables you to jump to a nonsequential fabric plane. You are prompted to enter the plane ID of the fabric to be monitored.
|
Task ID
Task ID
|
Operations
|
fabric
|
read
|
basic-services
|
execute
|
monitor
|
read
|
Examples
The following is sample output from the monitor controller fabric command. The output in this example displays fabric controller counters from fabric plane 0.
RP/0/0/CPU0:router# monitor controller fabric 0
rack3-3 Monitor Time: 00:00:24 SysUptime: 03:37:57
Controller fabric for 0x0
Controller Fabric Stats: Delta
In Cells 0 ( 0 per-sec) 0
Out Cells 0 ( 0 per-sec) 0
CE Cells 0 ( 0 per-sec) 0
UCE Cells 0 ( 0 per-sec) 0
PE Cells 0 ( 0 per-sec) 0
Quit='q', Freeze='f', Thaw='t', Clear='c', Select controller='s'
monitor controller sonet
To monitor controller counters, use the monitor controller sonet command in EXEC mode.
monitor controller sonet instance
Syntax Description
instance
|
Either a physical interface instance or a virtual interface instance as follows:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the modular services card, line card, or SPA interface processor (SIP).
– module: Module or subslot number. A physical layer interface module (PLIM) is always 0. A subslot specifies the secondary slot on the SIP in which the SPA is installed.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
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, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the monitor controller sonet command to display SONET controller counters. The display refreshes every 2 seconds.
The interactive commands that are available during a controller monitoring session are described in Table 2.
Table 2 Interactive Commands Available for the monitor controller sonet Command
Command
|
Description
|
c
|
Resets controller SONET counters to 0.
|
f
|
Freezes the display screen, thereby suspending the display of fresh counters.
|
t
|
Thaws the display screen, thereby resuming the display of fresh counters.
|
q
|
Terminates the controller SONET monitoring session.
|
s
|
Enables you to jump to a nonsequential SONET interface instance. You are prompted to enter the SONET interface instance to be monitored.
|
Task ID
Task ID
|
Operations
|
fabric
|
read
|
basic-services
|
execute
|
monitor
|
read
|
Examples
The following is sample output from the monitor controller sonet command. The output in this example displays counters from SONET interface instance 0/3/0/0.
RP/0/0/CPU0:router# monitor controller sonet 0/3/0/0
rack3-3 Monitor Time: 00:00:06 SysUptime: 01:23:56
Controller for SONET0_3_0_0
Path LOP 0 ( 0 per-sec) 0
Path AIS 0 ( 0 per-sec) 0
Path RDI 0 ( 0 per-sec) 0
Path BIP 0 ( 0 per-sec) 0
Path FEBE 0 ( 0 per-sec) 0
Path NEWPTR 0 ( 0 per-sec) 0
Path PSE 0 ( 0 per-sec) 0
Path NSE 0 ( 0 per-sec) 0
Line AIS 0 ( 0 per-sec) 0
Line RDI 0 ( 0 per-sec) 0
Line BIP 0 ( 0 per-sec) 0
Line FEBE 0 ( 0 per-sec) 0
Section LOS 1 ( 0 per-sec) 1
Section LOF 0 ( 0 per-sec) 0
Section BIP 0 ( 0 per-sec) 0
Quit='q', Freeze='f', Thaw='t', Clear='c', Select controller='s'
monitor interface
To monitor interface counters in real time, use the monitor interface command in EXEC or administration EXEC mode.
monitor interface [type instance]
Syntax Description
type
|
Interface type. For more information, use the question mark (?) online help function.
|
instance
|
Either a physical interface instance or a virtual interface instance as follows:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the modular services card, line card, or SIP.
– module: Module or subslot number. A physical layer interface module (PLIM) is always 0. A subslot specifies the secondary slot on the SIP in which the SPA is installed.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Defaults
Use the monitor interface command without an argument to display statistics for all interfaces in the system.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
Support was added for multiple interface instances.
Support was added for default behavior to monitor all interfaces.
Support was added for wildcards in the interface instance syntax.
Support was added for additional display options.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
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, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the monitor interface command to display interface counters for all interfaces. The display refreshes every 2 seconds.
Use the monitor interface command with the type instance argument to display counters for a single interface. For example: monitor interface pos0/2/0/0
To display more than one selected interface, enter the monitor interface command with multiple type instance arguments. For example: monitor interface pos0/2/0/0 pos0/5/0/1 pos0/5/0/2
To display a range of interfaces, or interface types, interface, enter the monitor interface command with a wildcard. For example: monitor interface pos0/5/*
The interactive commands that are available during an interface monitoring session are described in.
Table 3 Interactive Commands Available for the monitor interface Command (Functional Summary)
Command
|
Description
|
Use the following keys to suspend or resume the counter refresh:
|
f
|
Freezes the display screen, thereby suspending the display of fresh counters.
|
t
|
Thaws the display screen, thereby resuming the display of fresh counters.
|
Use the following key to reset the counters:
|
c
|
Resets interface counters to 0.
|
Use the following keys when displaying statistics for a single interface. These keys display counters in normal or detailed view.
|
d
|
Changes the display mode for the interface monitoring session to display detailed counters. Use the b interactive command to return to the regular display mode.
|
r
|
Displays the protocol divided by IPv4 or IPv6, and multicast and unicast. When the statistics are displayed using the r option, you can also use the k, y, or o keys to display statistics in packets ("k"), bytes("y") or packets and bytes("o").
|
b
|
Returns the interface monitoring session to the regular display mode for counters. Statistics are not divided by protocol.
|
Use the following keys when displaying statistics for multiple interfaces. These keys modify the display to show statistics in bytes, packets, or bytes and packets.
|
k
|
Displays statistics in packets ("k").
|
y
|
(Default) Displays statistics in bytes ("y").
|
o
|
Displays statistics in both bytes and packets ("o").
|
Use the following keys to display statistics for a different interface:
|
i
|
Enables you to jump to a nonsequential interface instance. You are prompted to enter the interface type and instance to be monitored.
|
p
|
Displays the previous sequential interface in the list of available interfaces.
|
n
|
Displays the next sequential interface in the list of available interfaces.
|
q
|
Terminates the interface monitoring session.
|
Task ID
Task ID
|
Operations
|
basic-services
|
execute
|
monitor
|
read
|
Examples
When more than one interface is specified, the statistics for each interface are displayed on a separate line. This display format appears anytime more than one interface is specified. For example:
•
To display statistics for all interfaces, enter the command monitor interface.
•
To display all the interfaces for an interface type, such as all POS interface, enter the command and wildcard monitor interface pos *.
•
To display statistics for three specified interfaces, enter the command monitor interface pos0/2/0/0 pos0/5/0/1 pos0/5/0/2.
The following is sample output from the monitor interface command entered without an argument. This command displays statistics for all interfaces in the system.
RP/0/RP0/CPU0:router# monitor interface
Interface In(bps) Out(bps) InBytes/Delta OutBytes/Delta
MgmtEth0/RP0/CPU0/0 1142/ 0% 8057/ 0% 14.9M/300 11.5M/2115
FINT0/RP0/CPU0 0/ 0% 0/ 0% 50459/0 66906/0
MgmtEth0/RP1/CPU0/0 0/ 0% 0/ 0% 3.7M/0 1.7M/0
FINT0/RP1/CPU0 0/ 0% 0/ 0% 9180/0 0/0
GigabitEthernet0/1/5/0 0/ 0% 0/ 0% 4608/0 3024/0
POS0/1/0/0 0/ 0% 0/ 0% 7.9M/0 2.2M/0
POS0/1/0/1 0/ 0% 0/ 0% 275.6M/0 275.4M/0
GigabitEthernet0/1/5/1 0/ 0% 0/ 0% 5.9M/0 168/0
GigabitEthernet0/6/5/0 0/ 0% 0/ 0% 14.9M/0 2.4M/0
POS0/6/0/0 0/ 0% 0/ 0% 7.9M/0 2.2M/0
POS0/6/0/1 0/ 0% 0/ 0% 3.4M/0 2.2M/0
GigabitEthernet0/6/5/1 0/ 0% 0/ 0% 4608/0 3066/0
POS0/6/4/4 0/ 0% 0/ 0% 23.2M/0 2.2M/0
POS0/6/4/5 0/ 0% 0/ 0% 3.4M/0 2.2M/0
POS0/6/4/6 0/ 0% 0/ 0% 2.1M/0 2.2M/0
POS0/6/4/7 0/ 0% 0/ 0% 3.4M/0 2.2M/0
Quit='q', Clear='c', Freeze='f', Thaw='t',
Next set='n', Prev set='p', Bytes='y', Packets='k'
The following output is from the monitor interface pos *. This command displays statistics for all POS interfaces:
RP/0/RP0/CPU0:router# monitor interface pos 0/*
router Monitor Time: 00:00:02 SysUptime: 186:37:44
Interface In(bps) Out(bps) InBytes/Delta OutBytes/Delta
POS0/1/0/0 1263/ 0% 0/ 0% 5.3M/330 1.4M/0
POS0/1/0/1 84/ 0% 0/ 0% 274.8M/22 274.6M/0
POS0/6/0/0 1275/ 0% 0/ 0% 5.3M/330 1.4M/0
POS0/6/0/1 85/ 0% 0/ 0% 2.6M/22 1.4M/0
POS0/6/4/4 0/ 0% 0/ 0% 15.1M/0 1.4M/0
POS0/6/4/5 85/ 0% 0/ 0% 2.6M/22 1.4M/0
POS0/6/4/6 0/ 0% 0/ 0% 1.3M/0 1.4M/0
POS0/6/4/7 85/ 0% 0/ 0% 2.6M/22 1.4M/0
Quit='q', Clear='c', Freeze='f', Thaw='t',
Next set='n', Prev set='p', Bytes='y', Packets='k'
The following is sample output for a single interface using the monitor interface command with the type instance argument. In this example, the output displays interface counters from POS interface 0/6/4/4. By default, statistics are displayed in "Brief" state (statistics are not divided by protocol).
RP/0/RP0/CPU0:router# monitor interface pos0/6/4/4
router Monitor Time: 00:00:24 SysUptime: 186:43:04
POS0/6/4/4 is up, line protocol is up
Traffic Stats:(2 second rates) Delta
Input Kbps (rate): 0 ( 0%)
Output Kbps (rate): 0 ( 0%)
Quit='q', Freeze='f', Thaw='t', Clear='c', Interface='i',
Brief='b', Detail='d', Protocol(IPv4/IPv6)='r'
The following is sample output from the monitor interface command in the protocol state for the POS interface 0/6/4/4. Use the r key to display statics by protocol:
RP/0/RP0/CPU0:router# monitor interface pos0/6/4/4
router Monitor Time: 00:00:02 SysUptime: 186:49:15
POS0/6/4/4 is up, line protocol is up
Traffic Stats:(2 second rates) Delta
Input Kbps (rate): 0 ( 0%)
Output Kbps (rate): 0 ( 0%)
Input Kbps (rate): 0 ( 0%)
Output Kbps (rate): 0 ( 0%)
Input Kbps (rate): 0 ( 0%)
Output Kbps (rate): 0 ( 0%)
Input Kbps (rate): 0 ( 0%)
Output Kbps (rate): 0 ( 0%)
Input Kbps (rate): 0 ( 0%)
Output Kbps (rate): 0 ( 0%)
Quit='q', Freeze='f', Thaw='t', Clear='c', Interface='i',
Brief='b', Detail='d', Protocol(IPv4/IPv6)='r'
(Additional options in 'Protocol'):
Bytes='y', Packets='k', Both of bytes/packets='o'
performance-mgmt apply monitor
To apply a statistics template to gather one sampling-size set of samples for a particular instance, use the performance-mgmt apply monitor command in global configuration mode. To stop monitoring statistics, use the no form of this command.
performance-mgmt apply monitor entity {ip-address | interface-type | interface-instance |
node-id | node-id process-id | process-name} {template-name | default}
no performance-mgmt apply monitor
Syntax Description
entity
|
Specifies an entity for which you want to apply the statistics template:
• bgp—Applies a template for monitoring a Border Gateway Protocol (BGP) neighbor.
• interface data-rates—Applies a template for monitoring data rates on an interface.
• interface generic-counters—Applies a template for monitoring generic counters on an interface
• mpls ldp—Applies a template for monitoring an MPLS Label Distribution Protocol (LDP) neighbor.
• node cpu—Applies a template for monitoring the central processing unit (CPU) on a node. Use the node-id argument with this entity.
• node memory—Applies a template for monitoring memory utilization on a node. Use the node-id argument with this entity.
• node process—Applies a template for monitoring a process on a node. Use the node-id and process-id arguments with this entity.
• ospf v2protocol—Applies a template for monitoring an Open Shortest Path First v2 (OSPFv2) process instance.
• ospf v3protocol—Applies a template for monitoring an OSPFv3 process instance.
|
ip-address
|
IP or neighbor address. Used with the bgp or ldp keyword.
|
interface-type
|
Interface type. Used with the interface data-rates or interface generic-counter keyword. For more information, use the question mark (?) online help function.
|
interface-instance
|
Either a physical interface instance or a virtual interface instance. Used with the interface data-rates or interface generic-counter keyword as follows:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the modular services card, line card, or SIP.
– module: Module or subslot number. A physical layer interface module (PLIM) is always 0. A subslot specifies the secondary slot on the SIP in which the SPA is installed.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
node-id
|
Designated node. Used with the node cpu or node memory keyword. The node-id argument is entered in the rack/slot/module notation.
|
node-id process-id
|
Designated node and process ID. Used with the node process keyword. The node-id argument is entered in the rack/slot/module notation.
|
process-name
|
Process name of the OSPF instance. Used with the ospfv2protocol and ospfv3protocol keywords.
|
template-name
|
Name of a predefined template used for statistics collection. A template name can be any combination of alphanumeric characters, and may include the underscore character (_). Use the show running performance-mgmt command to display a list of available templates.
|
default
|
Applies the default template.
|
Defaults
Monitoring is disabled.
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
The enable keyword was replaced by the apply keyword. In previous releases, this command was referred to as performance-mgmt enable monitor. The disable keyword was deprecated. The ospf v2protocol and ospf v3protocol keywords were introduced to support the monitoring of OSPF entity instances.
|
Release 3.3.0
|
Removed support for MPLS interfaces.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
Command Modes
Global configuration
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, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the performance-mgmt apply monitor command to apply a statistics template and enable monitoring. This command captures one cycle of a sample to analyze an instance of an entity. Rather than collect statistics for all instances, which is the purpose of the performance-mgmt apply statistics command, the performance-mgmt apply monitor command captures statistics for a specific entity instance for one sampling period.
For information about creating templates, see the performance-mgmt statistics command.
Task ID
Task ID
|
Operations
|
monitor
|
read, write, execute
|
Examples
The following example shows how to enable the BGP protocol monitoring using the criterion set in the default template:
RP/0/RP0/CPU0:router(config)# performance-mgmt apply monitor bgp 10.0.0.0 default
The following example shows how to enable monitoring for data rates according to the criterion set in the default template:
RP/0/RP0/CPU0:router(config)# performance-mgmt apply monitor interface data-rates pos
0/2/0/0 default
The following example shows how to enable memory monitoring based on the criterion set in the default template:
RP/0/RP0/CPU0:router(config)# performance-mgmt apply monitor node memory 0/1/cpu0 default
Related Commands
performance-mgmt apply statistics
To apply a statistics template and enable statistics collection, use the performance-mgmt apply statistics command in configuration mode. To stop statistics collection, use the no form of this command.
performance-mgmt apply statistics entity [location {all | node-id}] {template-name | default}
no performance-mgmt apply statistics
Syntax Description
entity
|
Specifies an entity for which you want to apply a statistics template:
• bgp—Applies a statistics collection template for Border Gateway Protocol (BGP).
• interface data-rates—Applies a statistics collection template for data rates.
• interface generic-counters—Applies a statistics collection template for generic counters.
• mpls ldp—Applies a template for monitoring an MPLS Label Distribution Protocol (LDP) neighbor.
• node cpu—Applies a statistics collection template for the central processing unit (CPU). Use the location keyword with the all keyword or node-id argument when enabling a statistics collection template for this entity.
• node memory—Applies a statistics collection template for memory utilization. Use the location keyword with the all keyword or node-id argument when enabling a statistics collection template for this entity.
• node process—Applies a statistics collection template for processes. Use the location keyword with the all keyword or node-id argument when enabling a statistics collection template for this entity.
• ospf v2protocol—Applies a statistics collection template for Open Shortest Path First v2 (OSPFv2) process instances.
• ospf v3protocol—Applies a statistics collection template for OSPFv3 process instances.
|
location {all | node-id}
|
Specifies all nodes or a particular node.
Specify the location all keywords for all nodes, or the node-id argument to specify a particular node. The node-id argument is entered in the rack/slot/module notation. You must specify either the location all keywords or the location keyword and node-id argument with the node cpu, node memory, or node process entity.
|
template-name
|
Name of a predefined template used for statistics collection. A template name can be any combination of alphanumeric characters, and may include the underscore character (_). Use the show running performance-mgmt command to display a list of available templates.
|
default
|
Applies the default template.
|
Defaults
Statistics collection is disabled.
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
The enable keyword was replaced by the apply keyword. In previous releases, this command was referred to as performance-mgmt enable statistics. The disable keyword was deprecated. The ospf v2protocol and ospf v3protocol keywords were introduced to support the enabling of statistics collection templates for the OSPF entity. The location keyword was added. The global keyword was deprecated and replaced by the location all keywords.
|
Release 3.3.0
|
Removed support for MPLS interfaces.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification
|
Release 3.6.0
|
No modification.
|
Command Modes
Global configuration
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, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the performance-mgmt apply statistics command to apply a statistics template and enable statistics collection. Only one template for each entity can be enabled at a time. After samples are taken, the data is sent to a directory on an external TFTP server, and a new collection cycle starts. The directory where data is copied to is configured using the performance-mgmt resources tftp-server command. The statistics data in the directory contains the type of entity, parameters, instances, and samples. They are in binary format and must be viewed using a customer-supplied tool, or they can be queried as they are being collected using XML.
Use the performance-mgmt apply statistics command to collect data for all the instances on a continuous basis. To analyze a particular instance for a limited period of time, use the performance-mgmt apply monitor command.
Use the no form of the command to disable statistics collection. Because only one performance management statistics collection can be enabled for any given entity at any given time, you are not required to specify the template name with the default keyword or template keyword and template-name argument when disabling a performance management statistics collection.
For information about creating templates, see the performance-mgmt statistics command.
Caution 
Each particular collection enabled requires a certain amount of resources. These resources are allocated for as long as the collection is enabled.
Task ID
Task ID
|
Operations
|
monitor
|
read, write, execute
|
Examples
The following example shows how to start statistics collection for BGP using the template named bgp1:
RP/0/RP0/CPU0:router(config)# performance-mgmt apply statistics bgp template bgp1
The following example shows how to enable statistics collection for generic counters using the default template:
RP/0/RP0/CPU0:router(config)# performance-mgmt apply statistics interface
generic-counters default
The following example shows how to enable CPU statistics collection based on the settings set in the default template:
RP/0/RP0/CPU0:router(config)# performance-mgmt apply statistics node cpu global default
Related Commands
performance-mgmt apply thresholds
To apply a thresholds template and enable threshold collection, use the performance-mgmt apply thresholds command in global configuration mode. To stop threshold collection, use the no form of this command.
performance-mgmt apply thresholds entity [location {all | node-id] {template-name | default}
no performance-mgmt apply thresholds
Syntax Description
entity
|
Specifies an entity for which you want to apply a threshold template:
• bgp—Applies a threshold monitoring template for Border Gateway Protocol (BGP).
• interface data-rates—Applies a threshold monitoring template for data rates.
• interface generic-counters—Applies a threshold monitoring template for generic counters.
• mpls ldp—Applies a template for monitoring an MPLS Label Distribution Protocol (LDP) neighbor.
• node cpu—Applies a threshold monitoring template for central processing unit (CPU) utilization. Use the location keyword in conjugation with the all keyword or node-id argument when enabling a statistics collection template for this entity.
• node memory—Applies a threshold monitoring template for memory utilization. Use the location keyword in conjugation with the all keyword or node-id argument when enabling a statistics collection template for this entity.
• node process—Applies a threshold monitoring template for processes. Use the location keyword in conjugation with the all keyword or node-id argument when enabling a statistics collection template for this entity.
• ospf v2protocol—Applies a threshold monitoring template for OSPFv2.
• ospf v3protocol—Applies a threshold monitoring template for OSPFv3.
|
location {all | node-id}
|
Specifies all nodes or a particular node.
Specify the location all keywords for all nodes, or the node-id argument to specify a particular node. The node-id argument is entered in the rack/slot/module notation. You must specify either the location all keywords or the location keyword and node-id argument with the node cpu, node memory, or node process entity.
|
template-name
|
Name of a predefined template used for threshold collection. A template name can be any combination of alphanumeric characters, and may include the underscore character (_). Use the show running performance-mgmt command to display a list of available templates.
|
default
|
Applies the default template.
|
Defaults
Threshold collection is disabled.
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
The enable keyword was replaced by the apply keyword. In previous releases, this command was referred to as performance-mgmt enable thresholds.
The disable keyword was deprecated.
The ospf v2protocol and ospf v3protocol keywords were introduced to support the enabling of threshold monitoring templates for the OSPF entity.
The location keyword was added. The global keyword was deprecated and replaced by the location all keywords.
|
Release 3.3.0
|
Removed support for MPLS interfaces.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
Command Modes
Global configuration
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, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the performance-mgmt apply thresholds command to apply a threshold template and enable threshold collection. Several templates can be configured, but only one template for each entity can be enabled at a time.
Use the no form of the command to disable threshold collection. Because only one performance management threshold monitoring template can be enabled for any given entity at any given time, you are not required to specify the template name with the default keyword or template keyword and template-name argument when disabling a performance management statistics collection.
For information about creating threshold templates, see the performance-mgmt thresholds command.
Task ID
Task ID
|
Operations
|
monitor
|
read, write, execute
|
Examples
The following example shows how to start statistics collection for BGP using a template named stats1:
RP/0/RP0/CPU0:router(config)# performance-mgmt apply thresholds bgp stats1
The following example shows how to enable statistics collection for generic counters using a template named stats2:
RP/0/RP0/CPU0:router(config)# performance-mgmt apply thresholds interface
generic-counters stats2
The following example shows how to enable CPU statistics collection using the template named cpu12:
RP/0/RP0/CPU0:router(config)# performance-mgmt apply thresholds node cpu global cpu12
Related Commands
performance-mgmt resources memory
To configure memory consumption limits for performance management (PM), use the performance-mgmt resources memory command in global configuration mode. To restore the default memory consumption limits, use the no form of this command.
performance-mgmt resources memory max-limit kilobytes min-reserved kilobytes
no performance-mgmt resources memory
Syntax Description
max-limit kilobytes
|
Specifies the maximum amount of memory (specified with the kilobytes argument) that the PM statistics collector can use for serving data collection requests. The range is from 0 to 4294967295 kilobytes.The default is 50000 kilobytes.
|
min-reserved kilobytes
|
Specifies a minimum amount of memory (specified with the kilobytes argument) that must remain available in the system after allowing a new PM data collection request. The range is from 0 to 4294967295 kilobytes. The default is 10000 kilobytes.
|
Defaults
max-limit—50000 kilobytes
min-reserved—10000 kilobytes
Command Modes
Global configuration
Command History
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
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, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the performance-mgmt resource memory command to ensure that the total memory consumed by data buffers in PM does not exceed a maximum limit and that any new PM data request does not cause available memory in the system to fall below a certain threshold.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to ensure that the total memory consumed by PM data buffers does not exceed 30,000 kilobytes and that any new PM data request does not cause available memory in the system to fall below 5000 kilobytes:
RP/0/RP0/CPU0:router(config)# performance-mgmt resources memory max-limit 30000
min-reserved 5000
performance-mgmt resources tftp-server
To configure a destination TFTP server for PM statistics collections, use the performance-mgmt resources tftp-server command in global configuration mode. To disable the resource, use the no form of this command.
performance-mgmt resources tftp-server ip-address directory dir-name
no performance-mgmt resources tftp-server
Syntax Description
tftp-server ip-address
|
Specifies the IP address of the TFTP server.
|
directory dir-name
|
Specifies the directory where performance management statistics will be copied.
|
Defaults
A destination TFTP server is not configured and data is not copied out of the system after a collection cycle (sampling-size) ends.
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
Command Modes
Global configuration
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, see the Configuring AAA Services on Cisco IOS XR Software module of the