10-14-2013 02:10 AM
Hi,
Can someone make me understand how to read the output of show process blocked. Everytime i use this command on XR platform and i got some of process are always there .. I need to understand what exactly we look in this output ?
RP/0/7/CPU0:PE1#show processes blocked
Jid Pid Tid Name State TimeInState Blocked-on
65548 12300 1 ksh Reply 28:45:49:0389 12298 devc-conaux
62 16402 2 mbus_text Reply 0:00:02:0156 12295 mbus-prp3-b
90 16403 1 timesync_client Reply 28:46:13:0825 12295 mbus-prp3-b
59 45093 3 mbi-hello Reply 28:46:09:0418 12295 mbus-prp3-b
59 45093 4 mbi-hello Reply 28:46:09:0418 12295 mbus-prp3-b
59 45093 7 mbi-hello Reply 28:46:09:0418 12295 mbus-prp3-b
59 45093 8 mbi-hello Reply 28:46:09:0418 12295 mbus-prp3-b
59 45093 10 mbi-hello Reply 28:46:09:0417 12295 mbus-prp3-b
56 45095 3 gsr_prp_pm Reply 28:46:09:0204 12295 mbus-prp3-b
355 81968 5 psarb Reply 0:00:00:0024 12295 mbus-prp3-b
355 81968 6 psarb Reply 28:45:20:0981 12295 mbus-prp3-b
121 110664 2 backplane Reply 28:21:54:0056 12295 mbus-prp3-b
208 110665 4 fctl Reply 28:45:03:0823 12295 mbus-prp3-b
208 110665 5 fctl Reply 28:45:03:0823 12295 mbus-prp3-b
208 110665 6 fctl Reply 28:42:49:0033 12295 mbus-prp3-b
284 110671 1 kaa-rp Reply 28:45:17:0953 12295 mbus-prp3-b
202 110681 6 envmon_periodic Reply 0:00:01:0791 12295 mbus-prp3-b
117 114794 2 attachd Reply 0:00:00:0710 12295 mbus-prp3-b
117 114794 3 attachd Reply 28:45:17:0250 16399 mqueue
285 143549 5 kd_mbus_server Reply 0:00:00:0473 12295 mbus-prp3-b
295 147659 2 lpts_fm Reply 0:00:00:0061 131194 lpts_pa
65744 29843664 1 exec Reply 0:00:00:0104 1 kernel
1118 164125 8 l2vpn_mgr Reply 28:16:29:0187 4108594 lspv_server
65827 29847843 1 more Reply 0:00:00:0055 16397 pipe
1108 4108584 7 snmpd Mutex 0:00:00:0003 4108584-10 #1
1040 4108591 10 mpls_ldp Reply 28:16:31:0749 4108594 lspv_server
1094 5292343 9 mibd_interface Reply 0:00:00:0012 164118 statsd_manager_g
65853 29847869 1 show_processes Reply 0:00:00:0000 1 kernel
Steve
Solved! Go to Solution.
10-14-2013 08:46 AM
Hi Steve,
On a nut shell, your looking at all the blocked process in the PRP3 and obviously you can run this against every LC.
Some of the processes meant to be blocked while other are not supposed to. Each process has its unique job id, process id and the left column is the thread id. The next column is the process name then the time in its current state. The last column is very important, it tells you what is blocking that process.
Few things that stands out "Mutex", long time in the same state, not necessarily these are wrong but you may want to look further with these.
Although this is C12K, you can benefit from the following document that facilitates the IOS-XR SW architecure(the majority of this doc addresses the entire XR platfrom family while some is more ASR9K oriented):
https://supportforums.cisco.com/docs/DOC-36339
Another doc in CCO which facilatates troubleshooting process and memory:
Actually, when you open a SR and able to provide that kind of information it will save us both a significant time to identify the root cause and the right course of action to recover.
Enjoy IOS-XR
10-14-2013 08:46 AM
Hi Steve,
On a nut shell, your looking at all the blocked process in the PRP3 and obviously you can run this against every LC.
Some of the processes meant to be blocked while other are not supposed to. Each process has its unique job id, process id and the left column is the thread id. The next column is the process name then the time in its current state. The last column is very important, it tells you what is blocking that process.
Few things that stands out "Mutex", long time in the same state, not necessarily these are wrong but you may want to look further with these.
Although this is C12K, you can benefit from the following document that facilitates the IOS-XR SW architecure(the majority of this doc addresses the entire XR platfrom family while some is more ASR9K oriented):
https://supportforums.cisco.com/docs/DOC-36339
Another doc in CCO which facilatates troubleshooting process and memory:
Actually, when you open a SR and able to provide that kind of information it will save us both a significant time to identify the root cause and the right course of action to recover.
Enjoy IOS-XR
10-15-2013 09:45 PM
Thx Yigal. Nice reply !!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide