12-07-2011 06:40 PM - edited 03-07-2019 03:47 AM
Hi All,
I've noticed that my 6509's running VSS seem to have high I/O memory utilization. Does anyone have any ideas?
I/O memory: Sw/Mod Bytes: Total Used %Used
1/1 8126344 7886544 97%
1/2 11796240 11442472 97%
1/5 RP 12058384 10715832 89%
1/5 SP 8388608 8104304 97%
1/7 8126344 7886544 97%
2/1 8126344 7886544 97%
2/2 11796240 11442472 97%
2/5 RP 12058384 10715832 89%
2/5 SP 8388608 8104304 97%
2/7 8126344 7886544 97%
12-07-2011 06:56 PM
Hi,
What version of IOS are you running?
12-07-2011 07:27 PM
Adding to Reza,
Please also attache full
show platform hardware cap cpu
and "show proc mem" from several modules including Supervisors RP and SP processors.
Nik
12-08-2011 05:36 AM
I'm running IOS s72033-ipservicesk9_wan-vz.122-33.SXI4a.bin
CPU Resources
CPU utilization: Sw/Mod 5 seconds 1 minute 5 minutes
1/1 0% / 8% 2% 2%
1/2 8% / 2% 5% 5%
1/5 RP 8% / 16% 5% 5%
1/5 SP 21% / 12% 13% 13%
1/7 0% / 6% 1% 1%
2/1 1% / 9% 2% 2%
2/2 5% / 3% 5% 5%
2/5 RP 3% / 2% 1% 1%
2/5 SP 5% / 6% 7% 7%
2/7 0% / 6% 0% 1%
Processor memory: Sw/Mod Bytes: Total Used %Used
1/1 268435456 198148096 74%
1/2 1073741824 242540544 23%
1/5 RP 1073741824 383926272 36%
1/5 SP 1073741824 467812352 44%
1/7 268435456 198144000 74%
2/1 268435456 198176768 74%
2/2 1073741824 242556928 23%
2/5 RP 1073741824 382885888 36%
2/5 SP 1073741824 467795968 44%
2/7 268435456 198148096 74%
I/O memory: Sw/Mod Bytes: Total Used %Used
1/1 8126344 7886544 97%
1/2 11796240 11442472 97%
1/5 RP 12058384 10715832 89%
1/5 SP 8388608 8104304 97%
1/7 8126344 7886544 97%
2/1 8126344 7886544 97%
2/2 11796240 11442472 97%
2/5 RP 12058384 10715832 89%
2/5 SP 8388608 8104304 97%
2/7 8126344 7886544 97%
CORE#show proc memory
System Memory : 1048576K total, 374929K used, 673647K free, 1000K kernel reserve
d
Lowest(b) : 685490176
PID Text Data Stack Dynamic Total Process
1 0 0 0 0 0 kernel
16386 2164 128 12 208 2512 sbin/chkptd.proc
3 644 28 4 192 868 sbin/devc-pty
4 772 32 12 112 928 sbin/devc-mistral.proc
5 604 24 12 96 736 sbin/pipe
4102 2380 176 32 292 2880 sbin/dumper.proc
4103 2592 328 32 480 3432 sbin/pcmcia_driver.proc
4104 2592 348 24 400 3364 sbin/bflash_driver.proc
12297 2444 184 20 224 2872 sbin/flashfs_hes.proc
12298 604 24 4 96 728 sbin/mqueue
12299 2792 340 12 380 3524 sbin/dfs_bootdisk.proc
12300 2700 184 28 240 3152 sbin/ldcache.proc
12301 2080 124 8 176 2388 sbin/watchdog.proc
12302 2152 132 20 260 2564 sbin/syslogd.proc
12303 2092 124 24 1072 3312 sbin/name_svr.proc
12304 3108 204 40 424 3776 sbin/wdsysmon.proc
12305 3000 244 76 480 3800 sbin/sysmgr.proc
16402 3000 244 12 240 3496 sbin/sysmgr.proc
16403 2780 172 8 208 3168 sbin/syslog_dev.proc
16404 2104 128 16 208 2456 sbin/itrace_exec.proc
16405 2216 136 24 252 2628 sbin/packet.proc
16406 88304 4 96 90472 178876 sbin/ios-base
16407 2788 176 24 240 3228 sbin/fh_fd_rf.proc
16408 2804 176 24 240 3244 sbin/fh_fd_rpc.proc
16409 2800 180 24 240 3244 sbin/fh_fd_oir.proc
16410 2800 180 24 240 3244 sbin/fh_fd_env.proc
16411 2832 180 24 224 3260 sbin/fh_fd_cli.proc
16412 2772 168 32 544 3516 sbin/fh_metric_dir.proc
16413 2796 180 24 240 3240 sbin/fh_fd_test.proc
16414 2928 188 28 240 3384 sbin/fh_fd_snmp.proc
16415 2804 176 24 240 3244 sbin/fh_fd_none.proc
16416 2812 176 24 240 3252 sbin/fh_fd_intf.proc
16417 2820 180 24 256 3280 sbin/fh_fd_gold.proc
16418 2832 180 24 224 3260 sbin/fh_fd_track.proc
16419 2808 176 24 224 3232 sbin/fh_fd_timer.proc
16420 2792 176 24 224 3216 sbin/fh_fd_counter.proc
16421 2856 180 24 224 3284 sbin/fh_fd_ioswd.proc
16422 3392 212 48 640 4292 sbin/fh_server.proc
16423 4540 248 32 436 5256 sbin/fh_policy_dir.proc
16424 5156 288 40 400 5884 sbin/call_home.proc
16425 4048 244 92 416 4800 sbin/tcp.proc
16426 2152 140 24 208 2524 sbin/ipfs_daemon.proc
16427 2788 176 24 224 3212 sbin/fh_fd_config.proc
16428 3820 192 48 288 4348 sbin/raw_ip.proc
16429 3136 148 44 260 3588 sbin/inetd.proc
16430 3972 212 48 288 4520 sbin/udp.proc
16431 13520 4 40 268 13832 sbin/iprouting.iosproc
16432 5984 356 36 952 7328 sbin/cdp2.iosproc
I'm not sure how to pull processor mem from individual cards.
Thanks Dave
12-08-2011 07:40 AM
Hi Dave,
I am pretty sure this is the cosmetic bug affecting ION (Modular IOS) :
CSCtb43697 output of "show platform hardware cap cpu" not correct on modular IOS
which has been duplicated into
CSCtb45475 sh plat hard capacity cpu report system memory usage incorrectly
Bug notes report that it should be fixed in SXI4, so you should have the fix as you run SXI4a.
However since ION is in end of engineering status I would not be suprised if it did not get fixed.
I did not have time to check the code directly and see if the diff made into it.
Anyway this is not the point in my opinion. The point is :
1) confirm if this is a cosmetic issue.
Just connect to some module (attach 1; attach 2 etc.) and run show memory. This is the value to trust (as the I/O memory which is apparently high refer to the LCs installed in the 2 chassis). If you see a lower value just forget about 'show plat hard capacity cpu report'.
2) What are you still doing on ION? As I wrote modular IOS got to a dead end, it is not developed anymore and don't offer any added value (I would say the contrary). FYI the 'v' in the system image name tells you that you have ION.
s72033-ipservicesk9_wan-vz.122-33.SXI4a.bin.
Why don't you move back to standard IOS and get rid of similar (or worse) issues?
regards,
Riccardo
12-08-2011 07:40 AM
Dave,
I know that SXI4a is pretty stable. One thing I noticed, is that you are running a modular version of IOS (wan-vz). Usually with modular IOS your CPU runs at higher capacity. Also, Cisco has decided to eliminate the modular IOS for the 6500 series. So, it can probably help if you load a non-modular IOS next time you are planning to upgrade your devices.
HTH
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