Feedback
|
Table Of Contents
Displaying CPU Hog Information for IPC Processes
Information About Displaying CPU Hog Information for IPC Processes
How to Display CPU Hog Information for IPC Processes
Displaying IPC Hog Information Statistics
Displaying CPU Hog Information for IPC Processes
The show ipc command displays various interprocess communication (IPC) counters and is used for troubleshooting issues with IPC services. Some IPC messages are delivered in batches, and waiting for the callback function to process the IPC message can lead to the IPC server process hogging the CPU. This feature introduces a new keyword—hog-info—to the show ipc command to display information about IPC messages that were processed when the IPC process hogged the CPU.
Feature History for the Displaying CPU Hog Information for IPC Processes Feature
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Information About Displaying CPU Hog Information for IPC Processes
•
How to Display CPU Hog Information for IPC Processes
Information About Displaying CPU Hog Information for IPC Processes
To use the Displaying CPU Hog Information for IPC Processes feature, you should understand the following concept:
Cisco IOS IPC Services
The Cisco IOS version of IPC provides a reliable ordered delivery of messages using an underlying platform driver transport or UDP transport protocol. Cisco IOS software IPC services allow line cards (LCs) and the central route processor (RP) in a distributed system, such as a Cisco 7500 series router, to communicate with each other by exchanging messages from the RP to the LCs. Communication messages are also exchanged between active and standby RPs. The IPC messages include configuration commands, responses to the configuration commands, and other events that are reported by an LC to the RP.
How to Display CPU Hog Information for IPC Processes
This section contains the following task:
•
Displaying IPC Hog Information Statistics (optional)
Displaying IPC Hog Information Statistics
Perform this task to track instances of IPC services hogging the CPU and to display information about IPC messages that were processed when the IPC process hogged the CPU.
SUMMARY STEPS
1.
enable
2.
show ipc {hog-info | nodes | ports [open] | queue | status [cumulative]}
DETAILED STEPS
Step 1
enable
Enters privileged EXEC mode. Enter your password if prompted.
Router> enableStep 2
show ipc {hog-info | nodes | ports [open] | queue | status [cumulative]}
Enter the show ipc hog-info privileged EXEC command to determine if the IPC services have hogged the CPU. In this first example, IPC services have not hogged the CPU.
Router# show ipc hog-infoIPC process has not hogged CPUEnter the show ipc hog-info privileged EXEC command again to determine if the IPC services have hogged the CPU. In this second example, IPC services have hogged the CPU.
Router# show ipc hog-infoTime last IPC process hogged CPU: 00:01:54IPC Messages Processed:Source Destination Name Message-Type Time-taken(0x) (msec)1070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 100
Additional References
The following sections provide references related to IPC services.
Related Documents
Related Topic Document TitleCisco IOS interface commands: complete command syntax, command mode, defaults, usage guidelines, and examples.
Cisco IOS Interface Command Reference, Release 12.0
MIBs
Technical Assistance
Command Reference
This section documents the following modified command. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command reference publications.
show ipc
To display interprocess communication (IPC) statistics, use the show ipc command in privileged EXEC mode.
show ipc {hog-info | nodes | ports [open] | queue | status [cumulative]}
Syntax Description
Command Modes
Privileged EXEC
Command History
Release Modification12.1(12c)EW
This command was introduced.
12.0(26)S
The hog-info and cumulative keywords were added.
Usage Guidelines
The Cisco IOS version of IPC provides a reliable ordered delivery of messages using an underlying platform driver transport or UDP transport protocol.
Hog-Info
Use the hog-info keyword when an error message is displayed stating that an IPC process has hogged the CPU. Information is displayed about the IPC messages that were processed when the IPC process hogged the CPU.
Nodes
A node (referred to as a seat) is an intelligent element, like a processor, that can communicate using IPC services. A seat is where entities and ports reside. A seat manager performs all the interprocessor communications by receiving messages from the network and forwarding the messages to the appropriate port.
Ports
IPC communication endpoints (ports) receive and queue received IPC messages.
Queue
Use the queue keyword to display information about the IPC retransmission queue and the IPC message queue.
Status
Use the status keyword to display the IPC statistics generated after a clear ipc statistics command has been entered. The show ipc status command with the cumulative keyword displays the IPC statistics gathered since the router was rebooted, regardless of how many times the statistics have been cleared.
Examples
The following is sample output from the show ipc command with the hog-info keyword. The first example shows the message that is displayed when the IPC process has not hogged the CPU. The second example shows the output when the IPC process has hogged the CPU.
Router# show ipc hog-infoIPC process has not hogged CPURouter# show ipc hog-infoTime last IPC process hogged CPU: 00:01:54IPC Messages Processed:Source Destination Name Message-Type Time-taken(0x) (msec)1070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 1001070000 10000.3 IPC Master:Control DEAD 100Table 1 describes the significant fields shown in the display.
The following is sample output from the show ipc command with the nodes keyword displaying the participating nodes:
Router# show ipc nodesThere are 3 nodes in this IPC realm.ID Type Name Last Sent Last Heard10000 Local IPC Master 0 02010000 Local GALIOS IPC:Card 1 0 02020000 Ethernet GALIOS IPC:Card 2 12 26Table 2 describes the significant fields shown in the display.
The following is sample output from the show ipc command with the ports keyword displaying the local and registered IPC ports:
Router# show ipc portsThere are 11 ports defined.Port ID Type Name (current/peak/total)10000.1 unicast IPC Master:Zone10000.2 unicast IPC Master:Echo10000.3 unicast IPC Master:Control10000.4 unicast Remote TTY Server Port10000.5 unicast GALIOS RF :Activeindex = 0 seat_id = 0x2020000 last sent = 0 heard = 1635 0/1/163510000.6 unicast GALIOS RED:Activeindex = 0 seat_id = 0x2020000 last sent = 0 heard = 2 0/1/22020000.3 unicast GALIOS IPC:Card 2:Control2020000.4 unicast GALIOS RFS :Standby2020000.5 unicast Slave: Remote TTY Client Port2020000.6 unicast GALIOS RF :Standby2020000.7 unicast GALIOS RED:StandbyRPC packets: current/peak/total0/1/17Table 3 describes the significant fields shown in the display.
The following is sample output from the show ipc command with the queue keyword displaying information about the IPC retransmission queue:
Router# show ipc queueMessage waiting for acknowledgement in Tx queue : 0Maximum acknowledgement msg usage in Tx queue : 6Message waiting for additional Fragments : 0Maximum message fragment usage : 0There are 0 IPC messages waiting for a response.There are 0 IPC messages currently on the IPC inboundQ.Messages currently in use : 0Message cache size : 1000Maximum message cache usage : 10000 times message cache crossed 5000 [max]Emergency messages currently in use : 0Inbound message queue depth 0Zone inbound message queue depth 0The following is sample output from the show ipc command with the status keyword:
Router# show ipc statusIPC System StatusTime last IPC stat cleared : neverThis processor is the IPC master server.Do not drop output of IPC frames for test purposes.1000 IPC Message Headers Cached.Rx Side Tx SideTotal Frames 1861 342Total from Local Ports 1845 422Total Protocol Control Frames 211 131Total Frames Dropped 0 0Service UsageTotal via Unreliable Connection-Less Service 1319 0Total via Unreliable Sequenced Connection-Less Svc 395 0Total via Reliable Connection-Oriented Service 131 211IPC Protocol Version 0Total Acknowledgements 211 131Total Negative Acknowledgements 0 0Device DriversTotal via Local Driver 0 0Total via Platform Driver 1861 211Total Frames Dropped by Platform Drivers 0 0Reliable Tx StatisticsRe-Transmission 0Re-Tx Timeout 0Rx Errors Tx ErrorsUnsupp IPC Proto Version 0 Tx Session Error 0Corrupt Frame 0 Tx Seat Error 0Duplicate Frame 0 Destination Unreachable 0Rel Out-of-Seq Frame 0 Unrel Out-of-Seq Frame 0Dest Port does Not Exist 0 Tx Driver Failed 0Rx IPC Msg Alloc Failed 0 Ctrl Frm Alloc Failed 0Unable to Deliver Msg 0 Tx Test Drop 0Buffer Errors Misc ErrorsIPC Msg Alloc 0 IPC Open Port 0Emer IPC Msg Alloc 0 No HWQ 0IPC Frame PakType Alloc 0 Hardware Error 0IPC Frame MemD Alloc 0Tx Driver ErrorsNo Transport 0MTU Failure 0Dest does not Exist 0Table 4 describes the significant fields shown in the display.
The following example shows how to display cumulative IPC counters for the local IPC server. Note that the recent IPC clearing has not cleared the IPC counters because the cumulative keyword displays the IPC statistics generated since the router was rebooted.
Router# show ipc status cumulativeIPC System StatusTime last IPC stat cleared : 00:00:05This processor is the IPC master server.Do not drop output of IPC frames for test purposes.1000 IPC Message Headers Cached.Rx Side Tx SideTotal Frames 3473 184Total from Local Ports 3473 92Total Protocol Control Frames 92 54Total Frames Dropped 0 0Service UsageTotal via Unreliable Connection-Less Service 2449 0Total via Unreliable Sequenced Connection-Less Svc 970 0Total via Reliable Connection-Oriented Service 54 92IPC Protocol Version 0Total Acknowledgements 0 0Total Negative Acknowledgements 0 0Device DriversTotal via Local Driver 0 0Total via Platform Driver 0 92Total Frames Dropped by Platform Drivers 0 0Reliable Tx StatisticsRe-Transmission 0Re-Tx Timeout 0Rx Errors Tx ErrorsUnsupp IPC Proto Version 0 Tx Session Error 0Corrupt Frame 0 Tx Seat Error 0Duplicate Frame 0 Destination Unreachable 0Out-of-Sequence Frame 0 Tx Test Drop 0Dest Port does Not Exist 0 Tx Driver Failed 0Rx IPC Msg Alloc Failed 0 Ctrl Frm Alloc Failed 0Unable to Deliver Msg 0Buffer Errors Misc ErrorsIPC Msg Alloc 0 IPC Open Port 0Emer IPC Msg Alloc 0 No HWQ 0IPC Frame PakType Alloc 0 Hardware Error 0IPC Frame MemD Alloc 0Tx Driver ErrorsNo Transport 0MTU Failure 0Dest does not Exist 0Related Commands
Copyright © 2003 Cisco Systems, Inc. All rights reserved.
Feedback