cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Bookmark
|
Subscribe
|
428
Views
0
Helpful
1
Replies

High cpu due to Pix garbage collector

dbjelf
Level 1
Level 1

I have two pix 525's running 6.3(3). I failed over to the secondary and rebooted the primary.

When the primary came back up its cpu is running close to 60%. "sh proc" shows the Pix Garbage Collector using alot of cpu time. Is this normal

behavior?

pix-1# sh cpu usage

CPU utilization for 5 seconds = 57%; 1 minute: 56%; 5 minutes: 57%

pix-1#

pix-1# sh proc

PC SP STATE Runtime SBASE Stack Process

Hsi 001eaa09 00a6ee14 00555860 0 00a6de8c 3404/4096 arp_timer

Lrd 001effad 00b3203c 00555d28 10 00b310c4 3800/4096 FragDBGC

Lwe 00119abf 02c4f21c 00558fc0 0 02c4e3b4 3688/4096 dbgtrace

Lwe 003e3f55 02c513ac 00555d28 0 02c4f464 6972/8192 Logger

Hwe 003e80d0 02c544a4 0054e438 0 02c5252c 8024/8192 tcp_fast

Hwe 003e8049 02c56554 0054e438 0 02c545dc 8024/8192 tcp_slow

Lrd 003006f9 04b36644 00555d28 0 04b356bc 3944/4096 xlate clean

Lrd 00300607 04b376e4 00555d28 0 04b3676c 3928/4096 uxlate clean

Mrd 002f82d3 04fc3ae4 00555898 0 04fc1b4c 7908/8192 tcp_intercept_timer_process

Lrd 0043a545 0506e39c 00555d28 0 0506d414 3900/4096 route_process

Hrd 002e8101 0506f43c 00555848 888620 0506e4c4 2748/4096 PIX Garbage Collector

Hwe 00217101 0507955c 00555860 0 050755f4 16048/16384 isakmp_time_keeper

Lrd 002e5e74 050938e4 00555d28 0 0509295c 3944/4096 perfmon

Mrd 0020e719 050bdd14 00555898 70 050bbd9c 7784/8192 IPsec timer handler

Hwe 0039a4db 050d28dc 00570980 0 050d0994 7048/8192 qos_metric_daemon

Mrd 002aca49 050ed284 00555898 0 050e94ac 15592/16384 IP Background

Lwe 002f8f4a 051a02a4 0056bc98 0 0519f42c 3704/4096 pix/trace

Lwe 002f9182 051a1354 0056c3c8 0 051a04dc 3704/4096 pix/tconsole

H* 0011f217 0009ff2c 00555848 20 051b3c7c 13436/16384 ci/console

Hwe 00433b3a 051b9494 005cac68 0 051b855c 3308/4096 lu_ctl

Csi 002f0fd3 051ba564 00555860 0 051b960c 3432/4096 update_cpu_usage

Hwe 002dcba1 0525e4fc 00534c00 0 0525a674 15884/16384 uauth_in

Hwe 003e6b5d 052605fc 00b69948 0 0525e724 7896/8192 uauth_thread

Hwe 003fce0a 0526174c 0054e788 0 052607d4 3960/4096 udp_timer

Crd 001df490 0526280c 00555cd8 99200 05261884 3776/4096 i82543_timer

Hsi 001e2636 052644bc 00555860 0 05263544 3928/4096 557mcfix

Crd 001e25eb 0526557c 00555cd8 588180 052645f4 3720/4096 557poll

Lrd 001e26a5 0526661c 00555d28 0 052656a4 3720/4096 557timer

Cwe 001e4229 055686f4 007bfc58 0 055667fc 7292/8192 pix/intf0

Mwe 003fcb7a 05569804 00bb2570 0 055688cc 3896/4096 riprx/0

Mrd 003a3999 0556a914 00555898 0 0556999c 3888/4096 riptx/0

Cwe 001e4229 0566caac 0074a6e8 0 0566abb4 7388/8192 pix/intf1

Mwe 003fcb7a 0566dbbc 00bb2528 0 0566cc84 3896/4096 riprx/1

Cwe 001eccfd 0587528c 00a0b408 0 05873324 8040/8192 pix/intf3

Cwe 001eccfd 05a7d9fc 00a0b2b8 0 05a7ba94 8040/8192 pix/intf5

Hwe 00433665 05c8b5d4 00551f38 50 05c8a66c 2604/4096 lu_rx

Hwe 001b0a3f 05d746e4 0055d4d8 70 05d7377c 2664/4096 fover_thread

Hwe 0011f217 05d7543c 00502c18 40 05d74794 3044/4096 fover_rx

Hwe 001b3791 05d76724 0055db5c 0 05d757ac 3736/4096 fover_tx

Hwe 001b0c44 05d7773c 0055db68 0 05d767c4 3960/4096 fover_rep

Lwe 001b0dfd 05d78764 0055db70 0 05d777dc 3976/4096 fover_lu_rep

Hwe 001b3d72 05d7c76c 0055db78 3280 05d787f4 12452/16384 fover_parse

Hwe 002f97f2 05da23ac 00555860 650 05d9a414 29820/32768 turboacl_process

Mwe 00370852 06059694 00555860 440 0605771c 5476/8192 Crypto CA

Hwe 003e6df1 05fa126c 00b400d0 0 05fa0fc4 284/1024 listen/http1

pix-1#

Thanks

-Dan

1 Reply 1

nkhawaja
Cisco Employee
Cisco Employee

Hi,

May be during the failover process, connections are still left over, hence this process is trying to clean them up. for more information

http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_tech_note09186a008009456c.shtml

can you run "clear xlat" at some off time to clear up the transations and connections etc.

thanks

Nadeem

Review Cisco Networking for a $25 gift card