 Feedback
|
Table Of Contents
Process and Memory Management Commands on Cisco IOS XR Software
Process and Memory Management Commands on Cisco IOS XR Software
This chapter describes the Cisco IOS XR software commands used to manage processes and memory.
For more information about using the process and memory management commands to perform troubleshooting tasks, see Cisco IOS XR Getting Started Guide.
affinity location-set
To set the affinity of a placeable program (process) to or from a group of nodes, use the affinity location-set command in placement program configuration mode. To remove the affinity location set, use the no form of this command.
affinity location-set node-id1 [...[node-id5]] {attract strength | repulse strength | default | none}
no affinity location-set node-id1 [...[node-id5]] {attract strength | repulse strength | default | none}
Syntax Description
Defaults
There are no default location-set affinities for any placeable processes.
Specifying an affinity value of default is equivalent to specifying the attract strength argument to be 200.Command Modes
Placement program configuration
Command History
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.
The affinity location-set command assigns an affinity for a process to run on a specific node, node pair or set of up to 5 nodes.
A node pair is either an active and standby pair of nodes [hosted on route processors (RPs) or distributed RPs], or a single active node on an RP or DRP that does not have a standby.
By containing references to specific location identifiers, location-set affinities are more specific to the individual SDR in which they are used than other affinity types.
Task ID
Examples
The following example shows how to configure placement affinity for the OSPF process class on the node pair:
RP/0/RP0/CPU0:router(config)# placement program ospfRP/0/RP0/CPU0:router(config-place)# affinity location-set 0/1/cpu0 0/1/cpu1 attract 200The following example shows how to stop loading a DRP with more processes:
RP/0/RP0/CPU0:router(config)# placement program defaultRP/0/RP0/CPU0:router(config-place)# affinity location-set 0/1/cpu0 repulse 90Related Commands
Enters placement program configuration mode to set process affinities (preferences).
affinity location-type
To set the affinity of a placeable program (process) to or from a location type, use the affinity location-set command in placement program configuration mode. To remove the affinity of a location set, use the no form of this command.
affinity location-type {current | paired | primary} {attract strength | repulse strength | default | none}
no affinity location-type {current | paired | primary} {attract strength | repulse strength | default | none}`
Syntax Description
Defaults
By default, all processes have the following settings:
•
location-type current attract strength argument: 100
•
•
Specifying an affinity value of default is equivalent to specifying the attract strength argument to be 200.
Command Modes
Placement program configuration
Command History
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.
The affinity location-type command is used to place a process at a particular location. The default policy is that the location type be a node pair (active and standby nodes), and that the process does not move automatically (current = 100) unless a solo node fails and the process must be started on a different node.
You can configure the placement policy to allow certain processes to stay where they are (current) or move just by indicating so through the various affinity choices. The higher the positive value of an affinity, the stronger the requirement that the process run at a location, and so on. A low or zero point value would indicate a weaker requirement (or no preference) that a process run at a location.
The affinity location type with the paired option configures the affinity towards the nodes that are paired (active and standby nodes), and as mentioned earlier, this is the default policy. The affinity location type using the primary option configures the affinity towards the designated secure domain router system controller (DSDRSC) node.
Note
Task ID
Examples
This example shows how to place Border Gateway Protocol (BGP) in a specific location by setting it with a high attract value. The result is that BGP does not move location under any circumstances other than a node pair removal.
RP/0/RP0/CPU0:router(config)# placement program bgpRP/0/RP0/CPU0:router(config-place)# affinity location-type current attract 5000Related Commands
Enters placement program configuration mode to set process affinities (preferences).
affinity program
To set the affinity of a placeable program (process) to or from another program, use the affinity program command in placement program configuration mode. To remove the affinity of a program, use the no form of this command.
affinity program program {attract strength | repulse strength | default | none}
no affinity program program {attract strength | repulse strength | default | none}
Syntax Description
Defaults
Specifying an affinity value of default is equivalent to specifying the attract strength argument to be 200.
Command Modes
Placement program configuration
Command History
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.
The affinity program command is used to collocate processes or keep them apart. You would want to use this command because you have learned that certain processes perform better when they are running together on the same node (attract)—or on different nodes, apart from each other (repulse).
Task ID
Examples
The following example shows how to keep IPv4 and IPv6 Routing Information Bases (RIBs) apart:
RP/0/RP0/CPU0:router(config)# placement program ipv4_ribRP/0/RP0/CPU0:router(config-place)# affinity program ipv6_rib repulse 200Related Commands
Enters placement program configuration mode to set process affinities (preferences).
affinity self
To set the affinity of a placeable program (process) to or from one of its own instances, use the affinity self command in placement program configuration mode. To remove the affinity self setting, use the no form of this command.
affinity self {attract strength | repulse strength | default | none}
no affinity self {attract strength | repulse strength | default | none}
Syntax Description
Defaults
The affinity self default is initially set in system placement files.
Command Modes
Placement program configuration
Command History
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.
The affinity self command is used to adjust placement decisions when multiple instances of a process are started. An attract (positive) affinity indicates a preference to have all instances of a process run on the same node, while a repulse (negative) affinity indicates a preference to have each instance of a process run on different nodes.
Typically, you would want to monitor how a process on your system best performs, and whether instances of the same class should be collocated or not.
Task ID
Examples
The following example shows how to configure BGP speakers to run on different nodes:
RP/0/RP0/CPU0:router(config)# placement program bgpRP/0/RP0/CPU0:router(config-place)# affinity self repulse 200Related Commands
Enters placement program configuration mode to set process affinities (preferences).
clear context
To clear core dump context information, use the clear context command in administration EXEC mode or in EXEC mode.
clear context location {node-id | all}
Syntax Description
Defaults
No default behavior or values
Command Modes
Administration EXEC
EXECCommand History
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 clear context command to clear core dump context information. If you do not specify a node with the location keyword and node-id argument, this command clears core dump context information for all nodes.
Use the show context command to display core dump context information.
Task ID
Examples
The following example shows how to clear core dump context information:
RP/0/RP0/CPU0:router# clear contextRelated Commands
dumpcore
To manually generate a core dump, use the dumpcore command in administration EXEC mode or in EXEC mode.
dumpcore {running | suspended} job-id location node-id
Syntax Description
Defaults
No default behavior or values
Command Modes
Administration EXEC
EXECCommand History
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.
When a process crashes on the Cisco IOS XR software, a core dump file of the event is written to a designated destination without bringing down the router. Upon receiving notification that a process has terminated abnormally, the Cisco IOS XR software then respawns the crashed process. Core dump files are used by Cisco Technical Support Center engineers and development engineers to debug the Cisco IOS XR software.
On the Cisco IOS XR software, core dumps can be generated manually for a process, even when a process has not crashed. Two modes exist to generate a core dump manually:
•
•
Core dump files contain the following information about a crashed process:
•
•
•
•
Task ID
Examples
The following example shows how to generate a core dump in suspended mode for the process instance 52:
RP/0/RP0/CPU0:router# dumpcore suspended 52RP/0/RP0/CPU0:Sep 22 01:40:26.982 : sysmgr[71]: process in stop/continue state 4104RP/0/RP0/CPU0Sep 22 01:40:26.989 : dumper[54]: %DUMPER-4-CORE_INFO : Core for pid = 4104 (pkg/bin/devc-conaux) requested by pkg/bin/dumper_gen@node0_RP0_CPU0RP/0/RP0/CPU0Sep 22 01:40:26.993 : dumper[54]: %DUMPER-6-SPARSE_CORE_DUMP : Sparse core dump as configured dump sparse for allRP/0/RP0/CPU0Sep 22 01:40:26.995 : dumper[54]: %DUMPER-7-DLL_INFO_HEAD : DLL path Text addr. Text size Data addr. Data size VersionRP/0/RP0/CPU0Sep 22 01:40:26.996 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libplatform.dll 0xfc0d5000 0x0000a914 0xfc0e0000 0x00002000 0RP/0/RP0/CPU0Sep 22 01:40:26.996 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libsysmgr.dll 0xfc0e2000 0x0000ab48 0xfc0c295c 0x00000368 0RP/0/RP0/CPU0Sep 22 01:40:26.997 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libinfra.dll 0xfc0ed000 0x00032de0 0xfc120000 0x00000c90 0RP/0/RP0/CPU0Sep 22 01:40:26.997 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libios.dll 0xfc121000 0x0002c4bc 0xfc14e000 0x00002000 0RP/0/RP0/CPU0Sep 22 01:40:26.997 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libc.dll 0xfc150000 0x00077ae0 0xfc1c8000 0x00002000 0RP/0/RP0/CPU0Sep 22 01:40:26.998 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libsyslog.dll 0xfc1d2000 0x0000530c 0xfc120c90 0x00000308 0RP/0/RP0/CPU0Sep 22 01:40:26.998 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libbackplane.dll 0xfc1d8000 0x0000134c 0xfc0c2e4c 0x000000a8 0RP/0/RP0/CPU0Sep 22 01:40:26.999 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libnodeid.dll 0xfc1e5000 0x00009114 0xfc1e41a8 0x00000208 0RP/0/RP0/CPU0Sep 22 01:40:26.999 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libttyserver.dll 0xfc1f1000 0x0003dfcc 0xfc22f000 0x00002000 0RP/0/RP0/CPU0Sep 22 01:40:27.000 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libttytrace.dll 0xfc236000 0x00004024 0xfc1e44b8 0x000001c8 0RP/0/RP0/CPU0Sep 22 01:40:27.000 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libdebug.dll 0xfc23b000 0x0000ef64 0xfc1e4680 0x00000550 0RP/0/RP0/CPU0Sep 22 01:40:27.001 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/lib_procfs_util.dll 0xfc24a000 0x00004e2c 0xfc1e4bd0 0x000002a8 0RP/0/RP0/CPU0Sep 22 01:40:27.001 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libsysdb.dll 0xfc24f000 0x000452e0 0xfc295000 0x00000758 0RP/0/RP0/CPU0:Oakland#RP/0/RP0/CPU0Sep 22 01:40:27.001 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libsysdbutils.dll 0xfc296000 0x0000ae08 0xfc295758 0x000003ec 0RP/0/RP0/CPU0Sep 22 01:40:27.002 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/lib_tty_svr_error.dll 0xfc2a1000 0x0000172c 0xfc1e4e78 0x00000088 0RP/0/RP0/CPU0Sep 22 01:40:27.002 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/lib_tty_error.dll 0xfc2a3000 0x00001610 0xfc1e4f00 0x00000088 0RP/0/RP0/CPU0Sep 22 01:40:27.003 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libwd_evm.dll 0xfc2a5000 0x0000481c 0xfc295b44 0x00000188 0RP/0/RP0/CPU0Sep 22 01:40:27.003 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libttydb.dll 0xfc2aa000 0x000051dc 0xfc295ccc 0x00000188 0RP/0/RP0/CPU0Sep 22 01:40:27.004 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libttydb_error.dll 0xfc23a024 0x00000f0c 0xfc295e54 0x00000088 0RP/0/RP0/CPU0Sep 22 01:40:27.004 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/librs232.dll 0xfc2b0000 0x00009c28 0xfc2ba000 0x00000470 0RP/0/RP0/CPU0Sep 22 01:40:27.005 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/lib_rs232_error.dll 0xfc2bb000 0x00000f8c 0xfc295edc 0x00000088 0RP/0/RP0/CPU0Sep 22 01:40:27.005 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libst16550.dll 0xfc2bc000 0x00008ed4 0xfc2ba470 0x00000430 0RP/0/RP0/CPU0Sep 22 01:40:27.006 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libconaux.dll 0xfc2c5000 0x00001dc0 0xfc2ba8a0 0x000001a8 0RP/0/RP0/CPU0Sep 22 01:40:27.006 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/lib_conaux_error.dll 0xfc1ee114 0x00000e78 0xfc295f64 0x00000088 0RP/0/RP0/CPU0Sep 22 01:40:27.007 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libttyutil.dll 0xfc2c7000 0x00003078 0xfc2baa48 0x00000168 0RP/0/RP0/CPU0Sep 22 01:40:27.007 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libbag.dll 0xfc431000 0x0000ee98 0xfc40cc94 0x00000368 0RP/0/RP0/CPU0Sep 22 01:40:27.008 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libchkpt.dll 0xfc474000 0x0002ecf8 0xfc4a3000 0x00000950 0RP/0/RP0/CPU0Sep 22 01:40:27.008 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libsysdbbackend.dll 0xfc8ed000 0x0000997c 0xfc8d3aa8 0x0000028c 0RP/0/RP0/CPU0Sep 22 01:40:27.008 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libttymgmtconnection.dll 0xfce85000 0x00004208 0xfce8a000 0x00000468 0RP/0/RP0/CPU0Sep 22 01:40:27.009 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libttymgmt.dll 0xfcea4000 0x0000e944 0xfce8abf0 0x000003c8 0RP/0/RP0/CPU0Sep 22 01:40:27.009 : dumper[54]: %DUMPER-7-DLL_INFO : /pkg/lib/libttynmspc.dll 0xfcec7000 0x00004a70 0xfcec6644 0x000002c8 0RP/0/RP0/CPU0Sep 22 01:40:28.396 : dumper[54]: %DUMPER-5-CORE_FILE_NAME : Core for process pkg/bin/devc-conaux at harddisk:/coredump/devc-conaux.by.dumper_gen.sparse.20040922-014027.node0_RP0_CPU0.ppc.ZRP/0/RP0/CPU0Sep 22 01:40:32.309 : dumper[54]: %DUMPER-5-DUMP_SUCCESS : Core dump successexception filepath
To modify core dump settings, use the exception filepath command in administration configuration mode or in global configuration mode. To remove the configuration, use the no form of this command.
exception [choice preference] [compress {on | off}] [filename filename lower-limit-higher-limit] filepath filepath
no exception [choice preference] [compress {on | off}] [filename filename lower-limit-higher-limit] [filepath filepath]
Syntax Description
choice preference
(Optional) Configures the order of preference for the destination of core dump files. Up to the three destinations can be defined. Valid values are 1 to 3.
compress {on | off}
(Optional) Specifies whether or not the core dump file should be sent compressed. By default, core dump files are sent compressed. If you specify the compress keyword, you must specify one of the following required keywords:
•
•
filename filename lower-limit-higher-limit
(Optional) Specifies the filename to be appended to core dump files and the lower and higher limit range of core dump files to be sent to a specified destination before being recycled by the circular buffer.
See Table 65 in the "Usage Guidelines" section for a description of the default core dump file naming convention.
Valid values for the lower-limit argument are 0 to 4. Valid values for the higher-limit argument are 5 to 64. A hyphen (-) must immediately follow the lower-limit argument.
Note
filepath
Local file system or network protocol, followed by the directory path. All local file systems are supported. The following network protocols are supported: TFTP and FTP.
Defaults
If you do not specify the order of preference for the destination of core dump files using the choice keyword and preference argument, the default preference is the primary location (that is, choice 1).
Core dump files are sent compressed.The default filenaming convention used for core dump files is described in the "Usage Guidelines" section. See Table 65.
Command Modes
Administration configuration
Global configurationCommand History
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 exception filepath command to modify core dump settings, such as the destination file path to store core dump files, file compression, and the filename appended to core dumps.
Up to three user-defined locations may be configured as the preferred destinations for core dump files:
•
•
•
When specifying a destination for a core dump file, you can specify an absolute file path on a local file system or on a network server. The following network protocols are supported: TFTP and FTP.
Note
In addition to the three preferred destinations that can be configured, Cisco IOS XR software provides three default fallback destinations for core dump files in the event that user-defined locations are unavailable.
The default fallback destinations on the Cisco CRS-1 are:
•
•
•
The default fallback destinations on Cisco XR 12000 Series Routers are:
•
•
•
Note
We recommend that you configure at least one preferred destination for core dump files as a preventive measure if the default fallback paths are unavailable. Configuring at least one preferred destination also ensures that core dump files are archived because the default fallback destinations store only the first and last core dump files for a crashed process.
Note
By default, the Cisco IOS XR software assigns filenames to core dump files according to the following format:
process[.by.requester |.abort][.sparse].date-time.node.processor-type[.Z]
For example:
packet.by.dumper_gen.20040921-024800.node0_RP0_CPU0.ppc.ZTable 65 describes the default core dump filenaming convention.
You can modify the default naming convention by specifying a filename to be appended to core dump files with the optional filename keyword and filename argument and by specifying a lower and higher limit ranges of values to be appended to core dump filenames with the lower-limit and higher-limit arguments, respectively. The filename that you specify for the filename argument is appended to the core dump file and the lower and higher limit ranges of core dump files to be sent to a specified destination before the filenames are recycled. Valid values for the lower-limit argument are 0 to 4. Valid values for the higher-limit argument are 5 to 64. A hyphen (-) must immediately follow the lower-limit argument. In addition, to uniquely identify each core dump file, a value is appended to each core dump file, beginning with the lower-limit value specified with the lower-limit argument and continuing until the higher-limit value specified with the higher-limit keyword has been reached. When the configured higher-limit value has been reached, the Cisco IOS XR software begins to recycle the values appended to core dump files, beginning with the lower-limit value.
Task ID
Examples
The following example shows how to configure the core dump setting for the primary user-defined preferred location. In this example, core files are configured to be sent uncompressed; the filename of core dump files is set to "core" (that is, all core filenames will be named core); the range value is set from 0 to 5 (that is, the values 0 to 5 are appended to the filename for the first five generated core dump files, respectively, before being recycled); and the destination is set to a directory on the hard disk.
RP/0/RP0/CPU0:router(config)# exception choice 1 compress off filename core 0-5 filepath /harddisk:/corefileRelated Commands
Collects packet memory information in core dumps.
Enables or disables sparse core dumps.
Sets the maximum size of core dump files.
Displays the configured core dump settings.
exception pakmem
To configure the collection of packet memory information in core dump files, use the exception pakmem command in administration configuration mode or in global configuration mode. To remove the configuration, use the no form of this command.
exception pakmem {on | off}
no exception pakmem {on | off}
Syntax Description
on
Enables the collection of packet memory information in core dump files.
off
Disables the collection of packet memory information in core dump files.
Defaults
Packet memory information is not included in core dump files.
Command Modes
Administration configuration
Global configurationCommand History
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 exception pakmem on command to configure the collection of packet memory information in core dump files. Cisco Technical Support Center engineers and development engineers use packet memory information to debug packet memory issues related to a process.
Caution
Task ID
Examples
The following example shows how to configure core dumps to include packet memory information:
RP/0/RP0/CPU0:router(config)# exception pakmem onRelated Commands
Modifies core dump settings.
Enables or disables sparse core dumps.
Sets the maximum size of core dump files.
Displays the configured core dump settings.
exception sparse
To enable or disable sparse core dumps, use the exception sparse command in administration configuration mode or in global configuration mode. To remove the configuration, use the no form of this command.
exception sparse {on | off}
no exception sparse
Syntax Description
Defaults
Sparse core dumps are disabled.
Command Modes
Administration configuration
Global configurationCommand History
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 exception sparse command to reduce the amount of data generated in the core dump file. Sparse core dumps, thus, reduce the amount of time required to generate the core dump file because only referenced data is generated in the core file (at the cost of lost information in the core file). Reducing the time required to generate core dump files corresponds to faster process restart times.
Sparse core dumps contain the following information about crashed processes:
•
•
•
•
The exception sparse command dumps memory pages based on trigger addresses found in the previously listed dump information, according to the following criteria:
•
•
•
Task ID
Examples
The following example shows how to enable sparse core dumps:
RP/0/RP0/CPU0:router(config)# exception sparse onRelated Commands
Modifies core dump settings.
Collects packet memory information in core dumps.
Sets the maximum file size of core dump files.
Displays the configured core dump settings.
exception sprsize
To specify the maximum file size for core dumps, use the exception sprsize command in administration configuration mode or in global configuration mode. To remove the configuration, use the no form of this command.
exception sprsize megabytes
no exception sprsize
Syntax Description
Defaults
megabytes: 192 MB
Command Modes
Administration configuration
Global configurationCommand History
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 exception sprsize command to specify the maximum file size for core dumps. The maximum file size configured for the megabytes argument is used with the configuration set for the exception sparse command to determine whether or not to generate a sparse core dump file. If sparse core dumps are disabled and a core dump file is predicted to exceed the default value (192 MB) uncompressed or the value specified for the megabytes argument uncompressed, a sparse core dump file is generated. If sparse core dumps are enabled, a sparse core dump file is generated, regardless of the size of the core dump file.
Task ID
Examples
The following example shows how to set the file size of sparse core dumps to 300 MB:
RP/0/RP0/CPU0:router(config)# exception sprsize 300Related Commands
follow
To unobtrusively debug a live process or a live thread in a process, use the follow command in EXEC mode.
follow {job job-id | process pid | location node-id} [all] [blocked] [debug level] [delay seconds] [dump address size] [iteration count] [priority level] [stackonly] [thread tid] [verbose]
Syntax Description
Defaults
Entering the follow command without any optional keywords or arguments performs the operation for five iterations from the local node with a delay of 5 seconds between each iteration. The output includes information about all live threads. This command uses the default scheduling priority from where the command is being run.
Command Modes
EXEC
Command History
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 this command to unintrusively debug a live process or a live thread in a process. This command is particularly useful for debugging deadlock and livelock conditions, for examining the contents of a memory location or a variable in a process to determine the cause of a corruption issue, or in investigating issues where a thread is stuck spinning in a loop. A livelock condition is one that occurs when two or more processes continually change their state in response to changes in the other processes.
The following actions can be specified with this command:
•
•
•
•
•
•
Take a snapshot of the execution path of a thread asynchronously to investigate performance-related issues by specifying a high number of iterations with a zero delay.
Task ID
Examples
The following example shows how to use the follow command to debug the process associated with job ID 257 for one iteration:
RP/0/RP0/CPU0:router# follow job 257 iteration 1Attaching to process pid = 28703 (pkg/bin/packet)No tid specified, following all threadsDLL Loaded by this process-------------------------------DLL path Text addr. Text size Data addr. Data size Version/pkg/lib/libovl.dll 0xfc0c9000 0x0000c398 0xfc0c31f0 0x0000076c 0/pkg/lib/libplatform.dll 0xfc0d6000 0x0000aa88 0xfc0e1000 0x00002000 0/pkg/lib/libsysmgr.dll 0xfc0e3000 0x0000aeac 0xfc0c395c 0x00000388 0/pkg/lib/libinfra.dll 0xfc0ee000 0x000332ec 0xfc122000 0x00000c70 0/pkg/lib/libios.dll 0xfc123000 0x0002c4bc 0xfc150000 0x00002000 0/pkg/lib/libc.dll 0xfc152000 0x00077ae0 0xfc1ca000 0x00002000 0/pkg/lib/libsyslog.dll 0xfc1d4000 0x0000530c 0xfc122c70 0x00000308 0/pkg/lib/libbackplane.dll 0xfc1da000 0x0000134c 0xfc0c3e6c 0x000000a8 0/pkg/lib/libnodeid.dll 0xfc1e7000 0x000091fc 0xfc1e61a8 0x00000208 0/pkg/lib/libdebug.dll 0xfc23e000 0x0000ef64 0xfc1e6680 0x00000550 0/pkg/lib/lib_procfs_util.dll 0xfc24d000 0x00004e2c 0xfc1e6bd0 0x000002a8 0/pkg/lib/libsysdb.dll 0xfc252000 0x00046224 0xfc299000 0x0000079c 0/pkg/lib/libsysdbutils.dll 0xfc29a000 0x0000ae04 0xfc29979c 0x000003ec 0/pkg/lib/libwd_evm.dll 0xfc2a9000 0x0000481c 0xfc299b88 0x00000188 0/pkg/lib/lib_mutex_monitor.dll 0xfc35e000 0x00002414 0xfc340850 0x00000128 0/pkg/lib/libchkpt.dll 0xfc477000 0x0002ee04 0xfc474388 0x00000950 0/pkg/lib/libpacket_common.dll 0xfc617000 0x000130f0 0xfc6056a0 0x000007b0 0Iteration 1 of 1------------------------------Current process = "pkg/bin/packet", PID = 28703 TID = 1trace_back: #0 0xfc1106dc [MsgReceivev]trace_back: #1 0xfc0fc840 [msg_receivev]trace_back: #2 0xfc0fc64c [msg_receive]trace_back: #3 0xfc0ffa70 [event_dispatch]trace_back: #4 0xfc0ffc2c [event_block]trace_back: #5 0x48204410 [<N/A>]ENDOFSTACKTRACECurrent process = "pkg/bin/packet", PID = 28703 TID = 2trace_back: #0 0xfc1106dc [MsgReceivev]trace_back: #1 0xfc0fc840 [msg_receivev]trace_back: #2 0xfc0fc64c [msg_receive]trace_back: #3 0xfc0ffa70 [event_dispatch]trace_back: #4 0xfc0ffc2c [event_block]trace_back: #5 0xfc48d848 [chk_evm_thread]ENDOFSTACKTRACECurrent process = "pkg/bin/packet", PID = 28703 TID = 3trace_back: #0 0xfc17d54c [SignalWaitinfo]trace_back: #1 0xfc161c64 [sigwaitinfo]trace_back: #2 0xfc10302c [event_signal_thread]ENDOFSTACKTRACECurrent process = "pkg/bin/packet", PID = 28703 TID = 4trace_back: #0 0xfc1106c4 [MsgReceivePulse]trace_back: #1 0xfc0fc604 [msg_receive_async]trace_back: #2 0xfc0ffa70 [event_dispatch]trace_back: #3 0xfc0ffc5c [event_block_async]trace_back: #4 0xfc35e36c [receive_events]ENDOFSTACKTRACECurrent process = "pkg/bin/packet", PID = 28703 TID = 5trace_back: #0 0xfc17d564 [SignalWaitinfo_r]trace_back: #1 0xfc161c28 [sigwait]trace_back: #2 0x48203928 [<N/A>]ENDOFSTACKTRACEThe following example shows how to use the follow command to debug TID 5 of the process associated with job ID 257 for one iteration:
RP/0/RP0/CPU0:router# follow job 257 iteration 1 thread 5Attaching to process pid = 28703 (pkg/bin/packet)DLL Loaded by this process-------------------------------DLL path Text addr. Text size Data addr. Data size Version/pkg/lib/libovl.dll 0xfc0c9000 0x0000c398 0xfc0c31f0 0x0000076c 0/pkg/lib/libplatform.dll 0xfc0d6000 0x0000aa88 0xfc0e1000 0x00002000 0/pkg/lib/libsysmgr.dll 0xfc0e3000 0x0000aeac 0xfc0c395c 0x00000388 0/pkg/lib/libinfra.dll 0xfc0ee000 0x000332ec 0xfc122000 0x00000c70 0/pkg/lib/libios.dll 0xfc123000 0x0002c4bc 0xfc150000 0x00002000 0/pkg/lib/libc.dll 0xfc152000 0x00077ae0 0xfc1ca000 0x00002000 0/pkg/lib/libsyslog.dll 0xfc1d4000 0x0000530c 0xfc122c70 0x00000308 0/pkg/lib/libbackplane.dll 0xfc1da000 0x0000134c 0xfc0c3e6c 0x000000a8 0/pkg/lib/libnodeid.dll 0xfc1e7000 0x000091fc 0xfc1e61a8 0x00000208 0/pkg/lib/libdebug.dll 0xfc23e000 0x0000ef64 0xfc1e6680 0x00000550 0/pkg/lib/lib_procfs_util.dll 0xfc24d000 0x00004e2c 0xfc1e6bd0 0x000002a8 0/pkg/lib/libsysdb.dll 0xfc252000 0x00046224 0xfc299000 0x0000079c 0/pkg/lib/libsysdbutils.dll 0xfc29a000 0x0000ae04 0xfc29979c 0x000003ec 0/pkg/lib/libwd_evm.dll 0xfc2a9000 0x0000481c 0xfc299b88 0x00000188 0/pkg/lib/lib_mutex_monitor.dll 0xfc35e000 0x00002414 0xfc340850 0x00000128 0/pkg/lib/libchkpt.dll 0xfc477000 0x0002ee04 0xfc474388 0x00000950 0/pkg/lib/libpacket_common.dll 0xfc617000 0x000130f0 0xfc6056a0 0x000007b0 0Iteration 1 of 1------------------------------Current process = "pkg/bin/packet", PID = 28703 TID = 5trace_back: #0 0xfc17d564 [SignalWaitinfo_r]trace_back: #1 0xfc161c28 [sigwait]trace_back: #2 0x48203928 [<N/A>]ENDOFSTACKTRACEThe following example shows how to use the follow command to debug the chain of threads blocking thread 2 associated with the process assigned PID 139406:
RP/0/RP0/CPU0:router# follow process 139406 blocked iteration 1 thread 2Attaching to process pid = 139406 (pkg/bin/lpts_fm)DLL Loaded by this process-------------------------------DLL path Text addr. Text size Data addr. Data size Version/pkg/lib/libplatform.dll 0xfc0d6000 0x0000aa88 0xfc0e1000 0x00002000 0/pkg/lib/libsysmgr.dll 0xfc0e3000 0x0000aeac 0xfc0c395c 0x00000388 0/pkg/lib/libinfra.dll 0xfc0ee000 0x000332ec 0xfc122000 0x00000c70 0/pkg/lib/libios.dll 0xfc123000 0x0002c4bc 0xfc150000 0x00002000 0/pkg/lib/libc.dll 0xfc152000 0x00077ae0 0xfc1ca000 0x00002000 0/pkg/lib/libltrace.dll 0xfc1cc000 0x00007f5c 0xfc0c3ce4 0x00000188 0/pkg/lib/libsyslog.dll 0xfc1d4000 0x0000530c 0xfc122c70 0x00000308 0/pkg/lib/libbackplane.dll 0xfc1da000 0x0000134c 0xfc0c3e6c 0x000000a8 0/pkg/lib/libnodeid.dll 0xfc1e7000 0x000091fc 0xfc1e61a8 0x00000208 0/pkg/lib/libdebug.dll 0xfc23e000 0x0000ef64 0xfc1e6680 0x00000550 0/pkg/lib/lib_procfs_util.dll 0xfc24d000 0x00004e2c 0xfc1e6bd0 0x000002a8 0/pkg/lib/libsysdb.dll 0xfc252000 0x00046224 0xfc299000 0x0000079c 0/pkg/lib/libsysdbutils.dll 0xfc29a000 0x0000ae04 0xfc29979c 0x000003ec 0/pkg/lib/libwd_evm.dll 0xfc2a9000 0x0000481c 0xfc299b88 0x00000188 0/pkg/lib/libbag.dll 0xfc40c000 0x0000ee98 0xfc41b000 0x00000368 0/pkg/lib/libwd_notif.dll 0xfc4f8000 0x00005000 0xfc4fd000 0x00001000 0/pkg/lib/libifmgr.dll 0xfc665000 0x00029780 0xfc68f000 0x00003000 0/pkg/lib/libnetio_client.dll 0xfca6a000 0x000065c8 0xfca2c4f8 0x000001b4 0/pkg/lib/libpa_client.dll 0xfcec5000 0x00006e9c 0xfcecc000 0x00003000 0/pkg/lib/libltimes.dll 0xfcecf000 0x00002964 0xfcdc4f20 0x000000a8 0Iteration 1 of 1------------------------------Current process = "pkg/bin/lpts_fm", PID = 139406 TID = 2trace_back: #0 0xfc110744 [MsgSendv]trace_back: #1 0xfc0fbf04 [msg_sendv]trace_back: #2 0xfc0fbbd8 [msg_send]trace_back: #3 0xfcec7580 [pa_fm_close]trace_back: #4 0xfcec78b0 [pa_fm_process_0]ENDOFSTACKTRACEREPLY (node node0_RP1_CPU0, pid 57433)No specific TID, following all threads of 57433 (pkg/bin/lpts_pa)-----------------------------------------------------------------DLL Loaded by this process-------------------------------DLL path Text addr. Text size Data addr. Data size Version/pkg/lib/libplatform.dll 0xfc0d6000 0x0000aa88 0xfc0e1000 0x00002000 0/pkg/lib/libsysmgr.dll 0xfc0e3000 0x0000aeac 0xfc0c395c 0x00000388 0/pkg/lib/libinfra.dll 0xfc0ee000 0x000332ec 0xfc122000 0x00000c70 0/pkg/lib/libios.dll 0xfc123000 0x0002c4bc 0xfc150000 0x00002000 0/pkg/lib/libc.dll 0xfc152000 0x00077ae0 0xfc1ca000 0x00002000 0/pkg/lib/libltrace.dll 0xfc1cc000 0x00007f5c 0xfc0c3ce4 0x00000188 0/pkg/lib/libsyslog.dll 0xfc1d4000 0x0000530c 0xfc122c70 0x00000308 0/pkg/lib/libbackplane.dll 0xfc1da000 0x0000134c 0xfc0c3e6c 0x000000a8 0/pkg/lib/libnodeid.dll 0xfc1e7000 0x000091fc 0xfc1e61a8 0x00000208 0/pkg/lib/libdebug.dll 0xfc23e000 0x0000ef64 0xfc1e6680 0x00000550 0/pkg/lib/lib_procfs_util.dll 0xfc24d000 0x00004e2c 0xfc1e6bd0 0x000002a8 0/pkg/lib/libsysdb.dll 0xfc252000 0x00046224 0xfc299000 0x0000079c 0/pkg/lib/libsysdbutils.dll 0xfc29a000 0x0000ae04 0xfc29979c 0x000003ec 0/pkg/lib/libwd_evm.dll 0xfc2a9000 0x0000481c 0xfc299b88 0x00000188 0/pkg/lib/lrdlib.dll 0xfc2f6000 0x0000a900 0xfc2f551c 0x00000610 0/pkg/lib/liblrfuncs.dll 0xfc30e000 0x00001998 0xfc2ebd80 0x000001ec 0/pkg/lib/libdscapi.dll 0xfc310000 0x0000457c 0xfc2f5b2c 0x0000035c 0/pkg/lib/liblrdshared.dll 0xfc315000 0x00005fec 0xfc31b000 0x00002000 0/pkg/lib/libbag.dll 0xfc40c000 0x0000ee98 0xfc41b000 0x00000368 0/pkg/lib/libchkpt.dll 0xfc477000 0x0002ee04 0xfc474388 0x00000950 0/pkg/lib/libwd_notif.dll 0xfc4f8000 0x00005000 0xfc4fd000 0x00001000 0/pkg/lib/libltrace_sdt.dll 0xfc65c000 0x000034fc 0xfc65b73c 0x00000568 0/pkg/lib/libfabhandle.dll 0xfc6be000 0x00003354 0xfc65bca4 0x00000248 0/pkg/lib/libfsdb_ltrace_util_rt.dll 0xfc6ea000 0x00001b74 0xfc605e50 0x00000108 0/pkg/lib/libbcdl.dll 0xfc6fb000 0x0000f220 0xfc6fa6e8 0x0000045c 0/pkg/lib/liblpts_pa_fgid.dll 0xfc8d7000 0x00006640 0xfc7acd5c 0x00000208 0/pkg/lib/libfgid.dll 0xfc910000 0x0001529c 0xfc926000 0x00002000 0/pkg/lib/libltimes.dll 0xfcecf000 0x00002964 0xfcdc4f20 0x000000a8 0Current process = "pkg/bin/lpts_pa", PID = 57433 TID = 1trace_back: #0 0xfc1106dc [MsgReceivev]trace_back: #1 0xfc0fc840 [msg_receivev]trace_back: #2 0xfc0fc64c [msg_receive]trace_back: #3 0xfc0ffa70 [event_dispatch]trace_back: #4 0xfc0ffc2c [event_block]trace_back: #5 0x48201904 [<N/A>]trace_back: #6 0x48201e3c [<N/A>]ENDOFSTACKTRACECurrent process = "pkg/bin/lpts_pa", PID = 57433 TID = 2trace_back: #0 0xfc1106dc [MsgReceivev]trace_back: #1 0xfc0fc840 [msg_receivev]trace_back: #2 0xfc0fc64c [msg_receive]trace_back: #3 0xfc0ffa70 [event_dispatch]trace_back: #4 0xfc0ffc2c [event_block]trace_back: #5 0x4821e978 [<N/A>]ENDOFSTACKTRACECurrent process = "pkg/bin/lpts_pa", PID = 57433 TID = 3trace_back: #0 0xfc1106dc [MsgReceivev]trace_back: #1 0xfc0fc840 [msg_receivev]trace_back: #2 0xfc0fc64c [msg_receive]trace_back: #3 0xfc0ffa70 [event_dispatch]trace_back: #4 0xfc0ffc2c [event_block]trace_back: #5 0x482064c4 [<N/A>]ENDOFSTACKTRACEThe following example shows how to use the follow command to debug the chain of threads blocking thread 2 associated with the process assigned PID 139406:
RP/0/RP0/CPU0:router# follow process 139406 blocked iteration 1 stackonly thread 2Attaching to process pid = 139406 (pkg/bin/lpts_fm)Iteration 1 of 1------------------------------Current process = "pkg/bin/lpts_fm", PID = 139406 TID = 2trace_back: #0 0xfc110744 [MsgSendv]trace_back: #1 0xfc0fbf04 [msg_sendv]trace_back: #2 0xfc0fbbd8 [msg_send]trace_back: #3 0xfcec7580 [pa_fm_close]trace_back: #4 0xfcec78b0 [pa_fm_process_0]ENDOFSTACKTRACEREPLY (node node0_RP1_CPU0, pid 57433)No specific TID, following all threads of 57433 (pkg/bin/lpts_pa)-----------------------------------------------------------------Current process = "pkg/bin/lpts_pa", PID = 57433 TID = 1trace_back: #0 0xfc1106dc [MsgReceivev]trace_back: #1 0xfc0fc840 [msg_receivev]trace_back: #2 0xfc0fc64c [msg_receive]trace_back: #3 0xfc0ffa70 [event_dispatch]trace_back: #4 0xfc0ffc2c [event_block]trace_back: #5 0x48201904 [<N/A>]trace_back: #6 0x48201e3c [<N/A>]ENDOFSTACKTRACECurrent process = "pkg/bin/lpts_pa", PID = 57433 TID = 2trace_back: #0 0xfc1106dc [MsgReceivev]trace_back: #1 0xfc0fc840 [msg_receivev]trace_back: #2 0xfc0fc64c [msg_receive]trace_back: #3 0xfc0ffa70 [event_dispatch]trace_back: #4 0xfc0ffc2c [event_block]trace_back: #5 0x4821e978 [<N/A>]ENDOFSTACKTRACECurrent process = "pkg/bin/lpts_pa", PID = 57433 TID = 3trace_back: #0 0xfc1106dc [MsgReceivev]trace_back: #1 0xfc0fc840 [msg_receivev]trace_back: #2 0xfc0fc64c [msg_receive]trace_back: #3 0xfc0ffa70 [event_dispatch]trace_back: #4 0xfc0ffc2c [event_block]trace_back: #5 0x482064c4 [<N/A>]ENDOFSTACKTRACERelated Commands
monitor processes
To display auto-updating statistics on processes in a full-screen mode, use the monitor processes command in administration EXEC mode or in EXEC mode.
monitor processes [dumbtty] [location node-id]
Syntax Description
Defaults
If you omit all keywords, the command displays the top 10 processes of CPU usage for the local node, sorted in descending order by the time used. The display is cleared and updated every 5 seconds until you quit the monitor processes command by pressing the q key.
Command Modes
Administration EXEC
EXECCommand History
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 processes command to display the top ten processes based on CPU usage. The display refreshes every 10 seconds.
•
•
•
The available interactive commands are described in Table 66.
Task ID
Examples
The following is sample output from the monitor processes command:
RP/0/RP0/CPU0:router# monitor processes195 processes; 628 threads; 3300 channels, 4579 fdsCPU states: 47.6% idle, 1.2% user, 51.1% kernelMemory: 2048M total, 1576M avail, page size 4KJID TIDS Chans FDs Tmrs MEM HH:MM:SS CPU NAME1 27 198 8 1 0 5:53:31 51.11% kernel52 5 215 44 5 228K 0:00:02 0.52% devc-conaux342 4 195 14 6 1M 0:00:08 0.34% wdsysmon495806 1 1 10 0 648K 0:00:00 0.16% ptop293 7 31 39 11 352K 0:00:09 0.07% shelfmgr55 11 24 14 5 16M 0:00:29 0.06% eth_server121 3 10 8 2 564K 0:00:05 0.02% bcm_process311 4 7 18 4 216K 0:00:02 0.01% sysdb_medusa_s138 4 14 40 5 240K 0:00:01 0.01% devc-vty265 5 31 19 4 204K 0:00:09 0.01% packetThe following is sample output from the monitor processes command using the optional location keyword and node-id argument:
RP/0/RP0/CPU0:router# monitor processes location 0/RP0/CPU0202 processes; 724 threads; 3750 channels, 5092 fdsCPU states: 48.8% idle, 0.8% user, 1.5% kernelMemory: 2048M total, 1526M avail, page size 4KJID TIDS Chans FDs Tmrs MEM HH:MM:SS CPU NAME1 27 205 3 1 0 10:54:12 1.52% procnto-600-smp-cisco-instr264 5 42 19 4 272K 0:00:15 0.37% packet53 2 202 564 0 1M 0:00:06 0.10% dllmgr180 15 93 42 6 1M 0:00:19 0.05% gsp69 22 94 8 3 1M 0:00:54 0.04% qnet67 5 4 6 0 956K 0:00:04 0.03% pkgfs156 2 6 18 1 480K 0:00:00 0.02% envmon294 1 6 12 1 112K 0:00:00 0.02% showd_lc314 3 185 14 4 1M 0:00:17 0.02% sysdb_svr_local310 4 7 18 4 276K 0:00:07 0.02% sysdb_medusa_sThe following is sample output from the show processes command using the dumbtty optional keyword:
RP/0/RP0/CPU0:router# monitor processes dumbttyComputing times...195 processes; 628 threads; 3721 channels, 4801 fdsCPU states: 37.1% idle, 1.1% user, 61.7% kernelMemory: 2048M total, 1576M avail, page size 4KJID TIDS Chans FDs Tmrs MEM HH:MM:SS CPU NAME1 27 198 6 1 0 6:33:33 61.76% kernel544958 1 1 8 0 648K 0:00:00 0.64% ptop293 7 31 39 11 352K 0:00:10 0.10% shelfmgr180 15 82 42 6 5M 0:00:26 0.10% gsp304 3 14 29 7 304K 0:00:02 0.06% statsd_manager55 11 24 14 5 16M 0:00:32 0.03% eth_server70 22 91 8 3 1M 0:00:31 0.03% qnet153 2 35 18 4 120K 0:00:01 0.03% dsc303 3 25 34 5 292K 0:00:00 0.03% statsd_server121 3 10 8 2 564K 0:00:06 0.03% bcm_process195 processes; 628 threads; 3409 channels, 4601 fdsCPU states: 46.5% idle, 0.5% user, 52.8% kernelMemory: 2048M total, 1576M avail, page size 4KJID TIDS Chans FDs Tmrs MEM HH:MM:SS CPU NAME1 27 198 6 1 0 6:33:44 52.89% kernel52 5 215 44 5 228K 0:00:06 0.38% devc-conaux309 6 25 23 8 352K 0:00:08 0.03% sysdb_mc315 3 177 14 4 1M 0:00:12 0.03% sysdb_svr_local138 4 14 40 5 240K 0:00:02 0.02% devc-vty298 9 25 111 9 2M 0:00:09 0.01% snmpd67 4 4 7 0 804K 0:00:04 0.00% pkgfs53 2 195 547 0 944K 0:00:06 0.00% dllmgr311 4 7 18 4 216K 0:00:03 0.00% sysdb_medusa_s342 4 195 14 6 1M 0:00:08 0.00% wdsysmonTable 67 describes the significant fields shown in the display.
Using Interactive Commands
When the n or d interactive command is used, the monitor processes command prompts you to enter a number. For example, when the interactive command n is entered, the prompt responds as shown below:
Enter number of procs to display: 15195 processes; 628 threads; 3375 channels, 4495 fdsCPU states: 49.0% idle, 0.9% user, 50.0% kernelMemory: 2048M total, 1576M avail, page size 4KJID TIDS Chans FDs Tmrs MEM HH:MM:SS CPU NAME1 27 198 2 1 0 6:11:43 50.01% kernel52 5 215 44 5 228K 0:00:05 0.72% devc-conaux293 7 31 39 11 352K 0:00:09 0.04% shelfmgr315 3 177 14 4 1M 0:00:11 0.03% sysdb_svr_local304 3 14 29 7 304K 0:00:01 0.02% statsd_manager309 6 25 23 8 352K 0:00:08 0.02% sysdb_mc342 4 195 14 6 1M 0:00:08 0.01% wdsysmon298 9 25 111 9 2M 0:00:09 0.00% snmpd265 5 31 19 4 204K 0:00:09 0.00% packet153 2 35 18 4 120K 0:00:00 0.00% dsc290 4 6 17 2 112K 0:00:00 0.00% sc_reddrv275 7 34 36 7 588K 0:00:00 0.00% qlink303 3 25 34 5 292K 0:00:00 0.00% statsd_server262 5 23 46 6 1M 0:00:00 0.00% ospf239 3 26 31 9 452K 0:00:00 0.00% lpts_paIf the number you enter is outside the acceptable range, you are prompted for another number:
Enter number of procs to display: 435Please enter a number between 5 and 40Enter number of procs to display:Related Commands
Displays auto-updating process and thread statistics in a full-screen mode.
Displays information about the running processes.
monitor threads
To display auto-updating statistics on threads in a full-screen mode, use the monitor threads command in administration EXEC mode or in EXEC mode.
monitor threads [dumbtty] [iteration number] [location node-id]
Syntax Description
Defaults
When all keywords are omitted, the command displays the first ten threads for the local node, sorted in descending order by the time used. The display is cleared and updated every 5 seconds until you quit the monitor threads command.
Command Modes
Administration EXEC
EXECCommand History
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 threads command to show the top ten threads based on CPU usage. The display refreshes every 10 seconds.
•
•
•
The available interactive display commands are described in Table 68.
Task ID
Examples
The following is sample output from the monitor threads command:
RP/0/RP0/CPU0:router# monitor threads195 processes; 628 threads;CPU states: 98.2% idle, 0.9% user, 0.7% kernelMemory: 2048M total, 1576M avail, page size 4KJID TID LAST_CPU PRI STATE HH:MM:SS CPU COMMAND1 12 1 10 Rcv 0:00:09 0.42% procnto-600-smp-cisco-instr1 25 1 10 Run 0:00:30 0.36% procnto-600-smp-cisco-instr342 1 1 19 Rcv 0:00:07 0.20% wdsysmon52 5 0 21 Rcv 0:00:03 0.15% devc-conaux52 3 1 18 Rcv 0:00:02 0.07% devc-conaux532670 1 0 10 Rply 0:00:00 0.07% top293 6 0 55 Rcv 0:00:06 0.03% shelfmgr55 8 0 10 Rcv 0:00:02 0.03% eth_server315 3 0 10 Rcv 0:00:11 0.03% sysdb_svr_local55 7 0 55 Rcv 0:00:11 0.02% eth_serverThe following is sample output from the monitor threads command using the optional location keyword:
RP/0/RP0/CPU0:router# monitor threads location 0/RP0/CPU0Computing times...195 processes; 628 threads;CPU states: 95.1% idle, 2.7% user, 2.0% kernelMemory: 2048M total, 1576M avail, page size 4KJID TID LAST_CPU PRI STATE HH:MM:SS CPU COMMAND1 25 0 10 Run 0:00:32 2.08% procnto-600-smp-cisco-instr265 5 0 10 SigW 0:00:09 0.89% packet279 1 1 10 Rcv 0:00:00 0.65% qsm557246 1 0 10 Rply 0:00:00 0.51% top293 5 1 55 Rcv 0:00:01 0.07% shelfmgr180 13 1 10 Rcv 0:00:02 0.07% gsp315 3 0 10 Rcv 0:00:12 0.07% sysdb_svr_local55 7 1 55 Rcv 0:00:12 0.04% eth_server180 1 0 10 Rcv 0:00:01 0.04% gsp298 9 0 10 Rcv 0:00:01 0.04% snmpdTable 69 describes the significant fields shown in the display.
Using Interactive Commands
When the n or d interactive command is used, the monitor threads command prompts for a number appropriate to the specific interactive command. The following is sample output from the monitor threads command showing the use of the interactive command n after the first display cycle to change the number of threads:
RP/0/RP0/CPU0:router# monitor threadsComputing times... 87 processes; 249 threads;CPU states: 84.8% idle, 4.2% user, 10.9% kernelMemory: 256M total, 175M avail, page size 4KJID TID PRI STATE HH:MM:SS CPU COMMAND1 6 10 Run 0:00:10 10.92% kernel553049 1 10 Rply 0:00:00 4.20% top58 3 10 Rcv 0:00:24 0.00% sysdbsvr1 3 10 Rcv 0:00:21 0.00% kernel69 1 10 Rcv 0:00:20 0.00% wdsysmon1 5 10 Rcv 0:00:20 0.00% kernel159 2 10 Rcv 0:00:05 0.00% qnet160 1 10 Rcv 0:00:05 0.00% netio157 1 10 NSlp 0:00:04 0.00% envmon_periodic160 9 10 Intr 0:00:04 0.00% netionEnter number of threads to display: 3Please enter a number between 5 and 40Enter number of threads to display: 887 processes; 249 threads;CPU states: 95.3% idle, 2.9% user, 1.7% kernelMemory: 256M total, 175M avail, page size 4KJID TID PRI STATE HH:MM:SS CPU COMMAND1 6 10 Run 0:00:11 1.76% kernel69 1 10 Rcv 0:00:20 1.11% wdsysmon58 3 10 Rcv 0:00:24 0.40% sysdbsvr157 1 10 NSlp 0:00:04 0.23% envmon_periodic159 19 10 Rcv 0:00:02 0.20% qnet553049 1 10 Rply 0:00:00 0.20% top159 12 10 Rcv 0:00:03 0.13% qnet160 1 10 Rcv 0:00:05 0.10% netioWhen a number outside the acceptable range is entered, the acceptable range is displayed:
Please enter a number between 5 and 40Enter number of threads to display:Related Commands
placement memory
To set the process memory threshold, use the placement memory command in global configuration or administration configuration mode. To return the settings to the default value, use the no form of this command.
placement memory {maximum | threshold} value
no placement memory
Syntax Description
Defaults
The maximum value is 200 percent.
The threshold value is 80 percent.Command Modes
Administration configuration
Global configurationCommand History
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 placement memory command with the maximum value keyword and argument to set the maximum percentage of memory that can be used on a node (based on the estimated memory usage of the processes). For example:
•
•
•
Use the placement memory command with the threshold value keyword and argument to set the preferred percentage of memory use for each node. The system attempts to balance all nodes at or below the threshold memory percentage. In other words, the system does not place a process on a node that has exceeded the threshold value, unless all other nodes have also reached their thresholds (or unless some other large affinity overrides this consideration).
Use the show placement policy global command to display the current settings:
RP/0/RP0/CPU0:router# show placement policy globalPer-location placement policy parameters----------------------------------------Memory preferred threshold: 80%Memory maximum threshold: 200%Threshold satisfaction affinity points: 50Task ID
Examples
In the following example, the maximum memory threshold is set to 80 percent:
RP/0/RP0/CPU0:router(config)# placement memory maximum 80Related Commands
placement program
To enter placement program configuration mode to set process affinities (preferences), use the placement program command in global configuration mode. To remove the assigned process placement, use the no form of this command.
placement program {program [instance instance] | default}
no placement program program {instance instance | default}
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
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.
The placement program command allows you to change the placement policy for any placeable process, such as Open Shortest Path First (OSPF) and Border Gateway Protocol (BGP).
Placement policy consists of two types: resource consumption and affinities. Resource consumption involves CPU and memory usage and is a "hard" resource requirement. Affinities are preferences, and are considered "soft" requirements for a placement policy. Only affinities can be configured by the operator.
The placement program command handles configuration for these affinity types:
•
•
•
•
•
To obtain a list of running placeable processes and placement policy parameters on your router system, use the show placement policy command.
Task ID
Examples
The following example enters placement program configuration mode to set all Protocol Independent Multicast (PIM) processes on the node pair that it had already started on so that PIM does not move automatically when system conditions change:
RP/0/RP0/CPU0:router(config)# placement program pimRP/0/RP0/CPU0:router(config-place)# affinity location-type current attract 100Related Commands
placement reoptimize
To reoptimize the placement of processes on a system among the available RP and DRP nodes in a secure domain router (SDR), use the placement command in EXEC mode.
placement reoptimize
Syntax Description
This command has no arguments or keywords.
Defaults
The default is to reoptimize process placement for all processes.
Command Modes
EXEC
Command History
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 placement reoptimize command to reoptimize the placement of running proccesses on the available RP and DRP nodes. The processes are redistributed to the available nodes based on memory usage and other calculations. This placement reoptimize command first displays the predicted results of the reoptimization before running the command. You can accept the changes and run the command, or cancel the procedure without impacting the router.
Task ID
Examples
The following example illustrates how to use the placement reoptimize command. The predicted changes are displayed, showing the current location of the process and the new location of the process. You can then decide to continue the operation or abort the reoptimization.
RP/0/RP0/CPU0:router# placement reoptimizePredicted changes to the placement:bpm 0/RP0/CPU0 (0/RP1/CPU0) --> 0/2/CPU0 (0/3/CPU0)bgp instance 0 0/RP0/CPU0 (0/RP1/CPU0) --> 0/2/CPU0 (0/3/CPU0)ipv4_rib 0/RP0/CPU0 (0/RP1/CPU0) --> 0/2/CPU0 (0/3/CPU0)ipv4_arm 0/RP0/CPU0 (0/RP1/CPU0) --> 0/2/CPU0 (0/3/CPU0)rcp_fs 0/RP0/CPU0 (0/RP1/CPU0) --> 0/2/CPU0 (0/3/CPU0)Continue? [yes/no] yesRP/0/RP0/CPU0:router#RP/0/RP0/CPU0:Nov 12 1:1:1.1 : placed[170]: %PLACED_PLACE-6-REOP_START: Re-optimization of the placement requested. You will be notified on completion.RP/0/RP0/CPU0:Nov 12 1:1:1.1 : placed[254]: %OS-PLACED_PLACE-6-REOP_COMPLETE: Re-optimization of the placement complete. Use 'show placement' to view the new placementRelated Commands
process
To start, terminate, or restart a process, use the process command in administration EXEC mode.
process {blocked | crash | restart | shutdown | start} {executable-name | job-id} {location {node-id | all}}
Syntax Description
Defaults
No default behavior or values
Command Modes
Administration EXEC
Command History
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.
Under normal circumstances, processes are started and restarted automatically by the operating system as required. If a process crashes, it is automatically restarted.
Use this command to manually stop, start, or restart individual processes.
Caution
process shutdown
The process shutdown command shuts down (terminates) the specified process and copies associated with the specified process. The process is not restarted, even if considered "mandatory." Use the show processes command to display a list of executable processes running on the system.
Caution
process restart
The process restart command restarts a process, such as a process that is not functioning optimally.
process start
The process start command starts a process that is not currently running, such as a process that was terminated using the process kill command. If multiple copies are on the system, all instances of the process are started simultaneously.
process blocked
This command is used by Cisco Technical Support engineers to collect debug information about a process. If the process mandatory command is set for a process, the process blocked command also causes the node to restart.
Task ID
Examples
The following example shows how to restart a process. In this example, the IS-IS process is restarted:
RP/0/RP0/CPU0:router# process restart isisRP/0/RP0/CPU0:router#RP/0/RP0/CPU0:Mar 30 15:24:41 : isis[343]: %ISIS-6-INFO_STRTUP_START : Cisco NSF controlled start beginningRP/0/RP0/CPU0:router#RP/0/RP0/CPU0:Mar 30 15:24:52 : isis[352]: %ISIS-6-INFO_STRTUP_FINISH : Cold controlled start completedThe following example shows how to terminate a process. In this example, the IS-IS process is stopped:
RP/0/RP0/CPU0:router# process shutdown isisRP/0/RP0/CPU0:router#The following example shows how to start a process. In this example, the IS-IS process is started:
RP/0/RP0/CPU0:router# process start isisRP/0/RP0/CPU0:router#RP/0/RP0/CPU0:Mar 30 15:27:19 : isis[227]: %ISIS-6-INFO_STARTUP_START : Cold controlled start beginningRP/0/RP0/CPU0:Mar 30 15:27:31 : isis[352]: %ISIS-6-INFO_STARTUP_FINISH : Cold controlled start completedRelated Commands
Sets the options for mandatory processes.
Displays information about the running processes.
process core
To modify the core dump options for a process, use the process core command in administration EXEC mode or in EXEC mode.
process {executable-name | job-id} core {context | copy | fallback | iomem | mainmem | off | sharedmem | sparse | sync | text} [maxcore value] location node-id
Syntax Description
Defaults
By default, processes are configured to dump shared memory, text area, stack, data section, and heap information.
Command Modes
Administration EXEC
EXECCommand History
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.
The modular architecture of the Cisco IOS XR software allows core dumps for individual processes. By default, processes are configured to dump shared memory, text area, stack, data section, and heap information.
Specifying an executable name for the executable-name argument changes the core dump option for all instances of the process. Specifying a job ID for the job-id value changes the core dump option for a single instance of a running process.
Task ID
Examples
The following example shows how to enable the collection of shared memory of a process:
RP/0/RP0/CPU0:router# process ospf core sharedmemThe following example shows how to turn off core dumping for a process:
RP/0/RP0/CPU0:router# process media_ether_config_di core offRelated Commands
process mandatory
To set the mandatory reboot options for a process, use the process mandatory command in administration EXEC mode or in EXEC mode.
process mandatory
process mandatory {on | off} {executable-name | job-id} location node-id
process mandatory reboot
process mandatory reboot {enable | disable}
process mandatory toggle
process mandatory toggle {executable-name | job-id} location node-id
Defaults
Command Default
No default behavior or values
Syntax Description
Administration EXEC
EXECCommand History
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.
If a process unexpectedly goes down, the following action occurs based on whether the process is considered "mandatory."
•
•
Task ID
Examples
The following example shows how to turn on a mandatory attribute. In this example, the mandatory attribute is turned on for the media_ether_config_di process.
RP/0/RP0/CPU0:router# process mandatory on media_ether_config_diThe following example shows how to turn the reboot option on. In this example, the router is set to reboot the node if a mandatory process goes down and cannot be restarted.
RP/0/RP0/CPU0:router# process mandatory reboot enableRP/0/RP0/CPU0:Mar 19 19:28:10 : sysmgr[71]: %SYSMGR-4-MANDATORY_REBOOT_ENABLE :mandatory reboot option enabled by requestThe following example shows how to turn off the reboot option. In this example, the router is set not to reboot the node if a mandatory process goes down and cannot be restarted. In this case, the mandatory process is restarted, but the node is not rebooted.
RP/0/RP0/CPU0:router# process mandatory reboot disableRP/0/RP0/CPU0:Mar 19 19:31:20 : sysmgr[71]: %SYSMGR-4-MANDATORY_REBOOT_OVERRIDE: mandatory reboot option overridden by requestRelated Commands
show context
To display core dump context information, use the show context command in administration EXEC mode or in EXEC mode.
show context [coredump-occurrence | clear] [location {node-id | all}]
Syntax Description
Command Default
If no coredump-occurrence value is specified, core dump context information for all core dumps is displayed.
Command Modes
Administration EXEC
EXECCommand History
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 show context command to display core dump context information. This command displays context information for the last ten core dumps. Cisco Technical Support Center engineers and development engineers use this command for post-analysis in the debugging of processes.
Use the clear context command to clear core dump context information.
Task ID
Examples
The following is sample output from the show context command:
RP/0/RP0/CPU0:router# show contextCrashed pid = 20502 (pkg/bin/mbi-hello)Crash time: Thu Mar 25, 2004: 19:34:14Core for process at disk0:/mbi-hello.20040325-193414.node0_RP0_CPU0Stack Trace#0 0xfc117c9c#1 0xfc104348#2 0xfc104154#3 0xfc107578#4 0xfc107734#5 0x482009e4Registers infor0 r1 r2 r3R0 0000000e 481ffa80 4820c0b8 00000003r4 r5 r6 r7R4 481ffb18 00000001 481ffa88 48200434r8 r9 r10 r11R8 00000000 00000001 00000000 fc17ac58r12 r13 r14 r15R12 481ffb08 4820c080 481ffc10 00000001r16 r17 r18 r19R16 481ffc24 481ffc2c 481ffcb4 00000000r20 r21 r22 r23R20 00398020 00000000 481ffb6c 4820a484r24 r25 r26 r27R24 00000000 00000001 4820efe0 481ffb88r28 r29 r30 r31R28 00000001 481ffb18 4820ef08 00000001cnt lr msr pcR32 fc168d58 fc104348 0000d932 fc117c9ccnd xerR36 24000022 00000004DLL InfoDLL path Text addr. Text size Data addr. Data size Version/pkg/lib/libinfra.dll 0xfc0f6000 0x00032698 0xfc0f5268 0x00000cb4The following is sample output from the show context command. The output displays information about a core dump from a process that has not crashed.
RP/0/RP0/CPU0:router# show contextnode: node0_RP0_CPU0------------------------------------------------------------------Crashed pid = 28703 (pkg/bin/packet)Crash time: Tue Sep 21, 2004: 02:48:00Core for process at harddisk:/packet.by.dumper_gen.20040921-024800.node0_RP0_CPU0.ppc.ZTable 70 describes the significant fields shown in the display.
Related Commands
show dll
To display dynamically loadable library (DLL) information, use the show dll command in administration EXEC mode or in EXEC mode.
show dll [jobid job-id [virtual] | address virtual-address | dllname dll-virtual-path | memory | symbol address virtual-address | virtual] [location node-id]
Syntax Description
Command Default
No default behavior or values
Command Modes
Administration EXEC
EXECCommand History
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.
Task ID
Examples
The following is sample output from the show dll command. In this example, the output displays all the DLLs loaded on the router:
RP/0/RP0/CPU0:router# show dllDLL path Text VA Text Sz Data VA Data Sz Refcount----------------------------------------------------------------------------------------/lib/libui.dll 0xfc000000 0x00007000 0xfc007000 0x00001000 1/disk0/crs-base-0.48.0/lib/liblogin.dll 0xfc008000 0x00006000 0xfc00e000 0x00001000 1/mbi/lib/libbanner.dll 0xfc00f000 0x00003000 0xfc012000 0x00001000 1/disk0/crs-base-0.48.0/lib/libaaav2.dll 0xfc013000 0x0000f000 0xfc022000 0x00001000 1/disk0/crs-base-0.48.0/lib/libaaatty.dll 0xfc023000 0x00004000 0xfc027000 0x00001000 1/mbi/lib/libtermcap.dll 0xfc028000 0x00003000 0xfc02b000 0x00001000 1/mbi/lib/lib_show_dll.dll 0xfc02c000 0x00004000 0xfc030000 0x00001000 1/mbi/lib/libihplatform.dll 0xfc0bf2d4 0x00000c18 0xfc1e4f88 0x00000068 1/lib/libovl.dll 0xfc0c8000 0x0000c3b0 0xfc0c21f0 0x0000076c 23/disk0/crs-admin-0.48.0/lib/libfqm_ltrace_util_common.dll 0xfc0d43b0 0x00000bfc 0xfc391f7c 0x00000068 1/lib/libplatform.dll 0xfc0d5000 0x0000aa88 0xfc0e0000 0x00002000 165/lib/libsysmgr.dll 0xfc0e2000 0x0000ab48 0xfc0c295c 0x00000368 166/lib/libinfra.dll 0xfc0ed000 0x0003284c 0xfc120000 0x00000c70 169/lib/libios.dll 0xfc121000 0x0002c4bc 0xfc14e000 0x00002000 166/lib/libc.dll 0xfc150000 0x00077ae0 0xfc1c8000 0x00002000 175/mbi/lib/libltrace.dll 0xfc1ca000 0x00007f5c 0xfc0c2cc4 0x00000188 96/lib/libsyslog.dll 0xfc1d2000 0x0000530c 0xfc120c70 0x00000308 129/disk0/crs-base-0.48.0/lib/liblpts_ifib_platform.dll 0xfc1d730c 0x00000cc8 0xfcef4000 0x00000068 1/lib/libbackplane.dll 0xfc1d8000 0x0000134c 0xfc0c2e4c 0x000000a8 163/disk0/crs-base-0.48.0/lib/libipv6_platform_client.dll 0xfc1d934c 0x00000c48 0xfcef4f8c 0x00000068 1/mbi/lib/libpkgfs_node.dll 0xfc1da000 0x000092d4 0xfc1e4000 0x000001a8 3The following is sample output from the show dll command with the optional jobid keyword and job-id argument:
RP/0/RP0/CPU0:router# show dll jobid 186DLLs mapped by PID 86111DLL path Text VA Text Sz Data VA Data Sz Refcount----------------------------------------------------------------------------------------/lib/libovl.dll 0xfc0c8000 0x0000c3b0 0xfc0c21f0 0x0000076c 23/lib/libplatform.dll 0xfc0d5000 0x0000aa88 0xfc0e0000 0x00002000 165/lib/libsysmgr.dll 0xfc0e2000 0x0000ab48 0xfc0c295c 0x00000368 167/lib/libinfra.dll 0xfc0ed000 0x0003284c 0xfc120000 0x00000c70 169/lib/libios.dll 0xfc121000 0x0002c4bc 0xfc14e000 0x00002000 166/lib/libc.dll 0xfc150000 0x00077ae0 0xfc1c8000 0x00002000 175/mbi/lib/libltrace.dll 0xfc1ca000 0x00007f5c 0xfc0c2cc4 0x00000188 96/lib/libsyslog.dll 0xfc1d2000 0x0000530c 0xfc120c70 0x00000308 129/lib/libbackplane.dll 0xfc1d8000 0x0000134c 0xfc0c2e4c 0x000000a8 163/lib/libnodeid.dll 0xfc1e5000 0x000091fc 0xfc1e41a8 0x00000208 163/mbi/lib/libinst_mem.dll 0xfc232000 0x000044f8 0xfc1e43b0 0x00000108 4/lib/libdebug.dll 0xfc23c000 0x0000ef64 0xfc1e4680 0x00000550 159Table 71 describes the significant fields shown in the display.
The following is sample output from the show dll command with the optional dllname keyword and optional dll-virtual-path argument:
RP/0/RP0/CPU0:router# show dll dllname /pkg/lib/libinst_mem.dllPID: 4102 Refcount: 1PID: 4105 Refcount: 1PID: 24600 Refcount: 1PID: 86111 Refcount: 1Table 72 describes the significant fields shown in the display.
Table 72 show dll dllname Field Descriptions
PID:
Process ID of the process.
Refcount
Number of references to the DLL by the process.
The following is sample output from the show dll command with the optional memory keyword:
RP/0/RP0/CPU0:router# show dll memory----------------------------------------------------------------------------Total DLL Text - 14778896 bytes Total DLL Data - 12688500 bytesTotal DLL Memory - 27467396 bytesshow exception
To display the configured core dump settings, use the show exception command in administration EXEC mode or in EXEC mode.
show exception
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Administration EXEC
EXECCommand History
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 show exception command to display the configured core dump settings. The output from this command displays the core dump settings configured with the following commands:
Task ID
Examples
The following is sample output from the show exception command:
RP/0/RP0/CPU0:router# show exceptionChoice 1 path = harddisk:/coredump compress = on filename = <process_name.time>Choice 2 path = tftp://223.255.254.254/users/xyz compress = on filename = <process_name.time>Exception path for choice 3 is not configured or removedChoice fallback one path = harddisk:/dumper compress = on filename = <process_name>Choice fallback two path = disk1:/dumper compress = on filename = <process_name>Choice fallback three path = disk0:/dumper compress = on filename = <process_name>Kernel dump not configuredTftp route for kernel core dump not configuredDumper packet memory in core dump enabledSparse core dump enabledDumper will switch to sparse core dump automatically at size 300MBRelated Commands
Modifies core dump settings.
Collects packet memory information in core dumps.
Enables or disables sparse core dumps.
Sets the maximum size of core dump files.
show memory
To display the available physical memory and memory usage information of processes on the router, use the show memory command in administration EXEC mode or in EXEC mode.
show memory [job-id | summary [bytes | detail]] location node-id
Syntax Description
Command Default
No default behavior or values
Command Modes
Administration EXEC
EXECCommand History
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.
To display detailed memory information for the entire router, enter the show memory command without any parameters.
Task ID
Examples
The following is partial sample output from the show memory command entered without keywords or arguments. This command displays details for the entire router.
RP/0/RP0/CPU0:router# show memoryPhysical Memory:2048M totalApplication Memory :1802M (1636M available)Image:116M (bootram:116M)Reserved:128M, IOMem:0, flashfsys:0Total shared window:0kernel:jid 1Address Bytes What0008f000 12288 Program Stack000b2000 12288 Program StackTotal Allocated Memory:0Total Shared Memory:0sbin/devc-pty:jid 68Address Bytes What4817f000 4096 Program Stack (pages not allocated)48180000 516096 Program Stack (pages not allocated)481fe000 8192 Program Stack48200000 28672 Physical Mapped Memory48207000 4096 ANON FIXED ELF SYSRAM48208000 4096 ANON FIXED ELF SYSRAMThe following is sample output from the show memory command entered with the job ID 7 to show the memory usage information for the process associated with this job identifier:
RP/0/RP0/CPU0:router# show memory 7Physical Memory: 256M totalApplication Memory : 249M (217M available)Image: 2M (bootram: 2M)Reserved: 4M, IOMem: 0, flashfsys: 0sbin/pipe: jid 7Address Bytes What07f7c000 126976 Program Stack (pages not allocated)07f9b000 4096 Program Stack07f9d000 126976 Program Stack (pages not allocated)07fbc000 4096 Program Stack07fbe000 126976 Program Stack (pages not allocated)07fdd000 4096 Program Stack07fdf000 126976 Program Stack (pages not allocated)07ffe000 4096 Program Stack08000000 122880 Program Stack (pages not allocated)0801e000 8192 Program Stack08020000 12288 Physical Mapped Memory08023000 4096 Program Text or Data08024000 4096 Program Text or Data08025000 16384 Allocated Memory08029000 16384 Allocated Memory7c001000 319488 DLL Text libc.dll7e000000 8192 DLL Data libc.dllThe following example shows how to display a detailed summary of memory information for the router:
RP/0/0/CPU0:router# show memory summary detailPhysical Memory: 256.000M totalApplication Memory : 140.178M (15.003M available)Image: 95.739M (bootram: 95.739M)Reserved: 20.000M, IOMem: 0, flashfsys: 0Shared window fibv6: 257.980KShared window PFI_IFH: 207.925KShared window aib: 8.972MShared window infra_statsd: 3.980KShared window ipv4_fib: 1.300MShared window atc_cache: 35.937KShared window qad: 39.621KTotal shared window: 10.805MAllocated Memory: 49.933MProgram Text: 6.578MProgram Data: 636.000KProgram Stack: 4.781MTable 73 describes the significant fields shown in the display.
Related Commands
Displays information about the heap space for a process.
Displays information about the running processes.
show memory compare
To display details about heap memory usage for all processes on the router at different moments in time and compare the results, use the show memory compare command in administration EXEC mode or in EXEC mode.
show memory compare {start | end | report}
Syntax Description
Command Default
No default behavior or values
Command Modes
Administration EXEC
EXECCommand History
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 show memory compare command to display details about the heap memory usage of all processes on the router at different moments in time and compare the results. This command is useful for detecting patterns of memory usage during events such as restarting processes or configuring interfaces.
Use the following steps to create and compare memory snapshots:
Step 1
Note
Step 2
Step 3
Step 4
Task ID
Examples
The following is sample output from the show memory compare report command:
RP/0/RP0/CPU0:router# show memory compare reportJID name mem before mem after difference mallocs restarted--- ---- ---------- --------- ---------- ------- ---------84 driver_infra_partner 577828 661492 83664 65279 gsp 268092 335060 66968 396236 snap_transport 39816 80816 41000 5237 mpls_lsd_agent 36340 77340 41000 5268 fint_partner 24704 65704 41000 590 null_caps_partner 25676 66676 41000 5208 aib 55320 96320 41000 5209 ipv4_io 119724 160724 41000 5103 loopback_caps_partne 33000 74000 41000 5190 ipv4_arm 41432 82432 41000 5191 ipv6_arm 33452 74452 41000 5104 sysldr 152164 193164 41000 585 nd_partner 37200 78200 41000 5221 clns 61520 102520 41000 5196 parser_server 1295440 1336440 41000 575 bundlemgr_distrib 57424 98424 41000 5200 arp 83720 124720 41000 5201 cdp 56524 97524 41000 5204 ether_caps_partner 39620 80620 41000 5206 qosmgr 55624 96624 41000 5240 imd_server 92880 104680 11800 28260 improxy 77508 88644 11136 10111 nrssvr 29152 37232 8080 60275 sysdb_svr_local 1575532 1579056 3524 30205 cfgmgr 31724 33548 1824 2599 sysdb_svr_shared 1131188 1132868 1680 1451 mbus-rp 26712 27864 1152 466 wdsysmon 298068 299216 1148 15168 netio 1010912 1012060 1148 6283 itrace_manager 17408 17928 520 359 devc-conaux 109868 110300 432 467 syslogd_helper 289200 289416 216 2117 fctl 41596 41656 60 254 sysmgr 171772 171076 -696 -5269 ifmgr 539308 530652 -8656 -196 *Table 74 describes the significant fields shown in the display.
Related Commands
Displays information about the heap space for a process.
Displays information about the running processes.
show memory heap
To display information about the heap space for a process, use the show memory heap command in administration EXEC mode or in EXEC mode.
show memory heap {job-id | allocated [dllname] [free] job-id | dllname job-id | free [dllname] job-id | failure {job-id | all} | summary {job-id | all}}
Syntax Description
Defaults
No default behavior or values
Command Modes
Administration EXEC
EXECCommand History
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.
Task ID
Examples
The following is sample output from the show memory heap command, specifying a job ID for the job-id argument:
RP/0/RP0/CPU0:router# show memory heap 111Malloc summary for pid 16433:Heapsize 16384: allocd 6328, free 8820, overhead 1236Calls: mallocs 144; reallocs 73; frees 5; [core-allocs 1; core-frees 0]Block Allocated ListTotal Total Block Name/ID/CallerUsize Size Count0x000008c1 0x000008cc 0x00000001 0x7c018a100x000005ac 0x00000974 0x00000079 0x7c02b9e00x000004f0 0x000004f8 0x00000001 0x7c02b6fc0x00000080 0x00000088 0x00000001 0x7c01936c0x00000034 0x00000048 0x00000001 0x7c0189540x00000024 0x00000030 0x00000001 0x7c0192780x00000018 0x00000020 0x00000001 0x7c019b2c0x00000008 0x00000010 0x00000001 0x7c0171780x00000008 0x00000010 0x00000001 0x7c00fb540x00000008 0x00000010 0x00000001 0x7c00fb800x00000008 0x00000010 0x00000001 0x7c00fbb8Table 75 describes the significant fields shown in the display.
The following is sample output from the show memory heap command, specifying the summary keyword and a job ID for the job-id argument:
RP/0/RP0/CPU0:router# show memory heap summary 65Malloc summary for pid 20495 process pcmciad:Heapsize 65536: allocd 40332, free 16568, overhead 8636Calls: mallocs 883; reallocs 3; frees 671; [core-allocs 4; core-frees 0]Band size 16, element per block 48, nbuint 1Completely free blocks: 0Block alloced: 2, Block freed: 0allocs: 85, frees: 20allocmem: 1040, freemem: 496, overhead: 448blocks: 2, blknodes: 96Band size 24, element per block 34, nbuint 1Completely free blocks: 0Block alloced: 1, Block freed: 0allocs: 243, frees: 223allocmem: 480, freemem: 336, overhead: 168blocks: 1, blknodes: 34Band size 32, element per block 26, nbuint 1Completely free blocks: 0Block alloced: 1, Block freed: 0allocs: 107, frees: 97allocmem: 320, freemem: 512, overhead: 136blocks: 1, blknodes: 26Band size 40, element per block 22, nbuint 1Completely free blocks: 0Block alloced: 2, Block freed: 0allocs: 98, frees: 74allocmem: 960, freemem: 800, overhead: 240blocks: 2, blknodes: 44Band size 48, element per block 18, nbuint 1Completely free blocks: 0Block alloced: 1, Block freed: 0allocs: 53, frees: 42allocmem: 528, freemem: 336, overhead: 104blocks: 1, blknodes: 18Band size 56, element per block 16, nbuint 1Completely free blocks: 0Block alloced: 1, Block freed: 0allocs: 8, frees: 4allocmem: 224, freemem: 672, overhead: 96blocks: 1, blknodes: 16Band size 64, element per block 14, nbuint 1Completely free blocks: 0Block alloced: 1, Block freed: 0allocs: 6, frees: 2allocmem: 256, freemem: 640, overhead: 88blocks: 1, blknodes: 14Band size 72, element per block 12, nbuint 1Completely free blocks: 0Block alloced: 1, Block freed: 0allocs: 1, frees: 0allocmem: 72, freemem: 792, overhead: 80blocks: 1, blknodes: 12Table 76 describes the significant fields shown in the display.
Related Commands
show placement location
To display all placeable processes by location, use the show placement location command in EXEC mode.
show placement location {node-id | all}
Syntax Description
node-id
The node-id argument is expressed in the rack/slot/module notation.
all
Displays all placement locations.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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.
The show placement location command identifies the process placement locations, the operational state of the nodes, and the processes currently running on the nodes.
To display the node location and operational state for a program, use the show placement program command.
Task ID
Examples
The following example shows all the nodes on the routing system and the placeable programs on those node locations:
RP/0/RP0/CPU0:router# show placement location allLocations: [0/RP0/CPU0] 0/RP1/CPU0 (RP)State: running Primary: yes Paired: noPrograms placed at this location:rt_check_mgrfm_serverfm_script_dirfm_metric_dirfm_fd_statsfm_fd_hardwarefm_fd_drvinfrafm_fd_counteripv6_rumpipv6_localipv6_connectedipv4_rumpipv4_localipv4_connectedtftp_fsrcp_fsftp_fsdomain_servicesbfdipv6_mpaipv4_mpaipv6_armipv4_armpolicy_repositoryipv6_ribipv4_ribcdp_mgrstatsd_managerTable 77 describes the significant fields shown in the display.
Related Commands
show placement policy
To display placement policy parameters and programs, use the show placement policy command in EXEC mode.
show placement policy {global | program {program | all | default}}
Syntax Description
Command Default
No default behavior or values
Command Modes
EXEC
Command History
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.
The show placement policy command displays placement policy items that influence program or process placement. The global option lists the per node threshold parameters, and the remaining options list the policy based on program.
If you configured the placement policy, the scope could be the default program, a given program, or even a particular program instance. Alternatively, the policy could be specified in a placement file (entered by the system) with different levels of affinities. To view all this information, you can specify the program all option to display the source of each program, and the policy applied to the default program or the program that you configured to override it.
Task ID
Examples
The following example shows how to display the global parameters for the placement policy:
RP/0/RP0/CPU0:router# show placement policy globalPer-location placement policy parameters----------------------------------------Memory preferred threshold: 80%Memory maximum threshold: 200%Threshold satisfaction affinity points: 50Table 78 describes the significant fields shown in the display.
The following example displays placement policy for all programs running on the system:
RP/0/RP0/CPU0:router# show placement policy program allProgram: rsvp : source----------------------------------------------------------Assumed mem: 1 MB : system [default]Slow migration interval: 1 second : system [default]affinity location-type primary attract 40 : system [default]affinity location-type paired attract 60 : system [default]affinity existence attract 90 : system [default]affinity location-type current attract 100 : system [default]Program: [default] : source----------------------------------------------------------Assumed mem: 1 MB : system [default]Slow migration interval: 1 second : system [default]affinity location-type primary attract 40 : system [default]affinity location-type paired attract 60 : system [default]affinity existence attract 90 : system [default]affinity location-type current attract 100 : system [default]Program: mpls_static : source----------------------------------------------------------Assumed mem: 1 MB : system [default]Slow migration interval: 1 second : system [default]affinity location-type primary attract 40 : system [default]affinity location-type paired attract 60 : system [default]affinity existence attract 90 : system [default]affinity location-type current attract 100 : system [default]Program: mpls_rid_helper : source----------------------------------------------------------Assumed mem: 1 MB : system [default]Slow migration interval: 1 second : system [default]affinity location-type primary attract 40 : system [default]affinity location-type paired attract 60 : system [default]affinity existence attract 90 : system [default]affinity location-type current attract 100 : system [default]Program: mpls_ldp : source----------------------------------------------------------Assumed mem: 1 MB : system [default]Slow migration interval: 1 second : system [default]affinity location-type primary attract 40 : system [default]affinity location-type paired attract 60 : system [default]affinity existence attract 90 : system [default]affinity location-type current attract 100 : system [default]Program: isis : source----------------------------------------------------------Assumed mem: 1 MB : system [default]Slow migration interval: 1 second : system [default]affinity location-type primary repulse 40 : system isisaffinity location-type paired attract 60 : system [default]affinity existence attract 90 : system [default]affinity location-type current attract 100 : system [default]Program: ipv6_static : source----------------------------------------------------------Assumed mem: 1 MB : system [default]Slow migration interval: 1 second : system [default]affinity location-type primary repulse 40 : system ipv6_staticaffinity location-type paired attract 60 : system [default]affinity existence attract 90 : system [default]affinity location-type current attract 100 : system [default]Program: ipv4_static : source----------------------------------------------------------Assumed mem: 1 MB : system [default]Slow migration interval: 1 second : system [default]affinity location-type primary repulse 40 : system ipv4_staticaffinity location-type paired attract 60 : system [default]affinity existence attract 90 : system [default]affinity location-type current attract 100 : system [default]Program: brib : source----------------------------------------------------------Assumed mem: 1 MB : system [default]Slow migration interval: 1 second : system [default]affinity location-type current attract 600 : system bribaffinity location-type paired attract 200 : system bribaffinity location-type primary repulse 150 : system bribaffinity program ipv6_rib attract 70 : system bribaffinity program ipv4_rib attract 70 : system bribaffinity existence attract 90 : system [default]Program: ipv6_rib : source----------------------------------------------------------Assumed mem: 1 MB : system [default]Slow migration interval: 1 second : system [default]affinity location-type paired attract 250 : system ipv6_ribaffinity location-type primary repulse 200 : system ipv6_ribaffinity program brib attract 70 : system ipv6_ribaffinity program bgp attract 250 : system ipv6_ribaffinity existence attract 90 : system [default]affinity location-type current attract 100 : system [default]Program: ipv4_rib : source----------------------------------------------------------Assumed mem: 1 MB : system [default]Slow migration interval: 1 second : system [default]affinity location-type paired attract 250 : system ipv4_ribaffinity location-type primary repulse 200 : system ipv4_ribaffinity program brib attract 70 : system ipv4_ribaffinity program bgp attract 250 : system ipv4_ribaffinity existence attract 90 : system [default]affinity location-type current attract 100 : system [default]Program: bgp : source----------------------------------------------------------Assumed mem: 1 MB : system [default]Slow migration interval: 1 second : system [default]affinity location-type current attract 600 : system bgpaffinity location-type paired attract 50 : system bgpaffinity location-type primary repulse 50 : system bgpaffinity self repulse 160 : system bgpaffinity program ipv6_rib attract 250 : system bgpaffinity program ipv4_rib attract 250 : system bgpaffinity existence attract 90 : system [default]Table 79 describes the significant fields shown in the display.
show placement program
To display the operational state for each placement program, use the show placement program command in EXEC mode.
show placement program {program | all}
Syntax Description
program
Specific program or program group.
all
Displays operational state for all placement programs.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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.
The show placement program command displays information that identifies that the process (or program) is running, where the process is located, locations where the process was rejected, and location where the process is waiting to start.
Task ID
Examples
The following example shows that all placement programs are running on the node pair 0/RP0/CPU0 and 0/RP1/CPU0:
RP/0/RP0/CPU0:router# show placement program allIf a program is shown as having 'rejected locations' (i.e., locations on whichit cannot be placed), the locations in question can been seen using the "showplacement policy program" command.If a program has been placed but not yet started, the amount of time elapsedsince the program was placed is shown in the 'waiting to start' field.Parentheses around the node indicate that the node has not yet fully booted.This will be true of standby nodes.Program Placed at location # rejected Waitinglocations to start--------------------------------------------------------------------------------mpls_vpn_mib 0/RP0/CPU0 (0/RP1/CPU0)ipv4_static 0/RP0/CPU0 (0/RP1/CPU0)rt_check_mgr 0/RP0/CPU0 (0/RP1/CPU0)mpls_rid_helper 0/RP0/CPU0 (0/RP1/CPU0)ital_test2 0/RP0/CPU0 (0/RP1/CPU0)ital_test1 0/RP0/CPU0 (0/RP1/CPU0)fm_metric_dir 0/RP0/CPU0 (0/RP1/CPU0)fm_fd_stats 0/RP0/CPU0 (0/RP1/CPU0)fm_fd_hardware 0/RP0/CPU0 (0/RP1/CPU0)fm_fd_drvinfra 0/RP0/CPU0 (0/RP1/CPU0)fm_fd_counter 0/RP0/CPU0 (0/RP1/CPU0)ipv6_rump 0/RP0/CPU0 (0/RP1/CPU0)ipv6_local 0/RP0/CPU0 (0/RP1/CPU0)ipv6_connected 0/RP0/CPU0 (0/RP1/CPU0)ipv4_rump 0/RP0/CPU0 (0/RP1/CPU0)ipv4_local 0/RP0/CPU0 (0/RP1/CPU0)ipv4_connected 0/RP0/CPU0 (0/RP1/CPU0)tftp_fs 0/RP0/CPU0 (0/RP1/CPU0)rcp_fs 0/RP0/CPU0 (0/RP1/CPU0)ftp_fs 0/RP0/CPU0 (0/RP1/CPU0)domain_services 0/RP0/CPU0 (0/RP1/CPU0)bfd 0/RP0/CPU0 (0/RP1/CPU0)ipv6_mpa 0/RP0/CPU0 (0/RP1/CPU0)ipv4_mpa 0/RP0/CPU0 (0/RP1/CPU0)ipv6_arm 0/RP0/CPU0 (0/RP1/CPU0)ipv4_arm 0/RP0/CPU0 (0/RP1/CPU0)policy_repository 0/RP0/CPU0 (0/RP1/CPU0)ipv6_rib 0/RP0/CPU0 (0/RP1/CPU0)ipv4_rib 0/RP0/CPU0 (0/RP1/CPU0)statsd_manager 0/RP0/CPU0 (0/RP1/CPU0)rsi_master 0/RP0/CPU0 (0/RP1/CPU0)RP/0/RP0/CPU0:router#Table 80 describes the significant fields shown in the display.
Related Commands
show placement reoptimize
To display the predicted changes to reoptimize the placement of processes, use the show placement reoptimize command in EXEC mode.
show placement reoptimize [program {program instance program-instance | all}]
Syntax Description
Defaults
The default is to display predicted changes for all for all route processor (RP) and distributed route processor (DRP) nodes and processes.
Command Modes
EXEC
Command History
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 show placement reoptimize command to display the predicted changes that will occur when the placement reoptimize command is run.
Task ID
Examples
The following example is of the show placement reoptimize command, entered without keywords or arguments:
RP/0/RP0/CPU0:router# show placement reoptimizePredicted changes to the placementProgram Current location New location--------------------------------------------------------------------------------ipv4_rib 0/7/CPU1 (1/14/CPU1) 1/RP0/CPU0 (1/RP1/CPU0)ipv6_rib 0/7/CPU1 (1/14/CPU1) 1/RP0/CPU0 (1/RP1/CPU0)brib instance 81 0/7/CPU1 (1/14/CPU1) 1/RP0/CPU0 (1/RP1/CPU0)bgp instance 1 0/7/CPU1 (1/14/CPU1) 1/RP0/CPU0 (1/RP1/CPU0)Related Commands
show processes
To display information about active processes, use the show processes command in administration EXEC or in EXEC mode.
show processes {job-id | process-name | aborts | all | blocked | boot | cpu | distribution process-name | dynamic | failover | family | files | location node-id | log | mandatory | memory | pidin | searchpath | signal | startup | threadname} [location node-id] [detail] [run]
Syntax Description
Command Default
No default behavior or values
Syntax Description
EXEC
Administration EXECCommand History
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 show processes command to display general information about the active processes. To display more detailed information for a process, specify a job ID or process for the job-id argument or process-name argument, respectively.
You can also use the monitor processes and monitor threads commands to determine the top processes and threads based on CPU usage.
Task ID
Examples
The show processes process-name command displays detailed information about a process:
RP/0/RP0/CPU0:router# show processes ospfJob Id: 261PID: 139453Executable path: /crs-rout-0.44.0/bin/ospfInstance #: 1Version ID: 00.00.0000Respawn: ONRespawn count: 1Max. spawns per minute: 12Last started: Wed Mar 17 07:46:26 2004Process state: RunPackage state: NormalStarted on config: cfg/gl/ipv4-ospf/proc/100/ord_a/routeridcore: TEXT SHAREDMEM MAINMEMMax. core: 0Mandatory: ONPlacement: ONstartup_path: /pkg/startup/ospf.startupProcess cpu time: 0.410 user, 0.183 kernel, 0.593 totalJID TID LastCPU Stack pri state HR:MM:SS:MSEC NAME261 1 0 40K 10 Receive 0:00:00:0397 ospf261 2 1 40K 10 Receive 0:00:00:0003 ospf261 3 0 40K 10 Receive 0:00:00:0007 ospf261 4 1 40K 10 Condvar 0:00:00:0000 ospf--More--Table 81 describes the significant fields shown in the display.
The show processes memory command displays details of memory usage for a given process or for all processes, as shown in the following example:
RP/0/RP0/CPU0:router# show processes memoryJID Text Data Stack Dynamic Process55 28672 4096 69632 17072128 eth_server164 143360 4096 20480 13238272 crs_fgid_server317 167936 4096 45056 10526720 syslogd122 512000 4096 77824 9797632 bgp265 57344 4096 57344 5877760 parser_server254 40960 4096 143360 3084288 netio63 8192 4096 24576 2314240 nvram314 4096 4096 36864 1699840 sysdb_svr_local341 495616 4096 40960 1576960 wdsysmon259 53248 4096 28672 1490944 nvgen_server189 32768 4096 32768 1425408 hd_drv69 77824 4096 110592 1421312 qnet348 323584 4096 40960 1392640 ospf347 323584 4096 40960 1392640 ospf346 323584 4096 40960 1392640 ospf345 323584 4096 40960 1392640 ospf344 323584 4096 40960 1392640 ospf261 323584 4096 40960 1392640 ospf--More--Table 82 describes the significant fields shown in the display.
The show processes command with the all keyword displays summary information for all processes as shown in the following example:
RP/0/RP0/CPU0:Router# show processes allJID LAST STARTED STATE RE- PLACE- MANDA- MAINT- NAME(IID) ARGSSTART MENT TORY MODE-------------------------------------------------------------------------------------82 03/16/2007 14:54:52.488 Run 1 M Y wd-mbi(1)58 03/16/2007 14:54:52.488 Run 1 M Y dllmgr(1)-r 60 -u 3074 03/16/2007 14:54:52.488 Run 1 M Y pkgfs(1)57 03/16/2007 14:54:52.488 Run 1 Y devc-conaux(1) -h -d librs232.dll -m libconaux.dll -u libst16550.dll76 03/16/2007 14:54:52.488 Run 1 Y devc-pty(1) -n 3256 Not configured None 0 Y clock_chip(1) -r -b--More--Table 83 describes the significant fields shown in the display.
Related Commands
Displays interactive auto-updating process statistics in a full-screen mode.
Displays auto-updating process and thread statistics in a full-screen mode.
slow-migration-interval
To set the slow migration interval for the program, use the slow-migration-interval command in placement program configuration mode. To return the slow migration interval to its default value, use the no form of this command.
slow-migration-interval length
no slow-migration-interval
Syntax Description
Defaults
length: 1 second
Command Modes
Placement program configuration
Command History
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.
The placement reoptimize command identifies processes that must be moved to achieve optimal placement. To prevent disruption on the router, you can use the slow-migration-interval command to specify the time to wait after moving each process, to allow the router to recover before preceding to move the next process.
Task ID
Examples
The following example shows how to set the slow migration interval:
RP/0/RP0/CPU0:router(config)# placement program ipv4_ribRP/0/RP0/CPU0:router(config-place)# slow-migration-interval 240Related Commands
Enters placement program configuration mode to set process affinities (preferences).
