02-01-2010 08:47 AM - edited 03-06-2019 09:32 AM
Hello
This 2924 switch is reporting very high process memory usage. I cannot help noticing that holding column of show proc memory is highest for the IP SNMP usage.
Is it normal for IP SNMP to require a lot of memory or could it be a memory leak?
xxxxxxxxxx#show proc mem Total: 3779364, Used: 3229356, Free: 550008 PID TTY Allocated Freed Holding Getbufs Retbufs Process 0 0 48800 1504 394160 0 0 *Init* 0 0 1680 9178808 1680 0 0 *Sched* 0 0 21204200 18959200 988044 1099092 510632 *Dead* 1 0 268 268 3836 0 0 Load Meter 2 0 114548 9420 6900 13608 0 TACACS+ 3 0 0 114964 6836 0 0 Check heaps 4 0 20248 0 27084 0 0 Chunk Manager 5 0 96 12288 6932 0 34480 Pool Manager 6 0 268 268 6836 0 0 Timers 7 0 96 0 6932 0 0 Entity MIB API 8 0 180 168 7016 0 0 ARP Input 9 0 8688 268 15256 0 0 Enet Aging 10 0 96 0 6932 0 0 Critical Bkgnd 11 0 208692 179288 15916 0 0 Net Background 12 0 17392 268 18524 9072 0 Logger 13 0 268 268 6836 0 0 TTY Background 14 0 1878063884 1380815372 6836 0 0 Per-Second Jobs 15 0 192 0 7028 0 0 Net Input 16 0 268 268 6836 0 0 Compute load avg 17 0 0 3404688 6836 0 7923888 Per-minute Jobs 18 0 3456702528 2114128928 7980 1560 0 LED Control Proc PID TTY Allocated Freed Holding Getbufs Retbufs Process 19 0 0 0 3836 0 0 RAM Access (dm 0 20 0 1142765272 655434380 8616 780 0 Port Status Proc 21 0 244 0 7080 0 0 VM Prune Events 22 1 345932 335704 16004 0 0 Virtual Exec 23 0 902685460 902685252 3908 0 0 GDS Frame Ager 24 0 0 0 6900 0 0 IP NAT Ager 28 0 0 0 3836 0 0 RAM Access (dm 1 30 0 2724120940 1104215440 7308 0 0 Broadcast Storm 31 0 96 0 3932 0 0 Port Group Chang 33 0 428 339296 3932 0 0 Address Learning 34 0 0 0 3836 0 0 RAM Access (dm 2 35 0 4200168060 3851135040 22936 1560 0 Enet Aging 36 0 1436732 1073380 15716 0 0 IP Input 37 0 96 389268 3932 0 0 Address Deletion 38 0 177488308 168629860 18528 6355440 0 CDP Protocol 39 0 588 268 7156 0 0 UDLD 40 0 14748 5332 12416 0 0 Switch CGMP Prot 41 0 22804 15504 20892 0 0 VLAN Manager 42 0 0 695688 12836 0 0 TCP Timer 43 0 10425424 425908 14488 0 0 TCP Protocols 44 0 0 0 6836 0 0 Socket Timers 45 0 0 0 6836 0 0 HTTP Timer PID TTY Allocated Freed Holding Getbufs Retbufs Process 46 0 244 0 4080 0 0 CGMP Forwarding 47 0 364 268 6932 0 0 Cluster L2 48 0 96 0 6932 0 0 Cluster RARP 49 0 1156 600 7392 0 0 Cluster Base 50 0 4524 13972 7600 780 0 Spanning Tree 51 0 420 268 3988 0 0 STP Hello 52 0 50076 268 20548 14040 0 STP Queue Handle 53 0 328 12592 6996 0 0 Malibu STP Adjus 54 0 0 0 6836 0 0 Time Range Proce 55 0 96 0 12932 0 0 SNMP ConfCopyPro 56 0 12176 13592 3932 0 0 Bridge MIB traps 58 0 268 268 3836 0 0 Runtime diags 59 0 0 0 6836 0 0 SNMP Timers 60 0 1829583108 1828522940 1319796 0 0 IP SNMP 61 0 96 0 12932 0 0 SNMP Traps 62 0 1416 268 7984 0 0 NTP 63 0 117924192 115566088 15236 1261008 0 BootP Resolver 64 0 254088 142812 7168 0 0 AAA Accounting 3228952 Total
02-01-2010 09:06 AM
Hi H,
Take a look at this doc regarding high CPU with SNMP engine and how to mitigate it.
http://www.ciscosystems.ro/en/US/tech/tk648/tk362/technologies_tech_note09186a00800948e6.shtml
HTH
Reza
02-02-2010 01:16 AM
Thanks
It was process memory usage rather than high CPU utilisation that I was concerned about.
02-01-2010 02:18 PM
Hello,
what IOS image is running on the device?
We experience a different problem that they become unreachable at L3 (no telnet possible, no ping) but they are still acting as L2 switches.
Hope to help
Giuseppe
02-02-2010 01:19 AM
12.0(5.2)XU Maint Rel
02-08-2010 03:01 AM
The following bug is a memory leak in in IP SNMP. That might be what I am hitting. Unfortunately, none of the fixed-in versions give are available for the 2924XL switch.
02-08-2010 03:48 AM
The bug I meant to say in my previous post was:
CSCds06656 Bug Details Bug #3 of 3 | < Previous | Next >
memory leak in MakeOctetString() for various get
Problem Description:
Router may experience memory leak in IP SNMP or other processes using
MakeOctetString()
Conditions:
Problem may appear during normal operating conditions when a process
using MakeOctetString()
Possible Workaround:
Disable SNMP or orther process using MakeOctetString()
Status
Fixed
(Resolved)
Severity
3 - moderate
Last Modified
In Last month
Product
Cisco IOS software
Technology
1st Found-In
12.1M
12.0(4)T
12.0(5)T1
12.1T
Known Affected Versions
Fixed-In
12.1(4.1)M
12.0(12.6)SC
12.1(3a)EC1
12.1(4)DB
12.1(4)DC
12.1(4)DC1
12.1(4.0.3)PI
12.1(4.0.3)T
12.1(4.3)PI
12.1(4.4)E
12.1(4.4)EC
Component(s)
ubr7200
Related Bug Information
Processor memory leak in SNMP MakeOctetString
A Cisco router running 12.0(4)T or later 12.0 T code that has Simple
Network Management Protocol (SNMP) configured may experience a slow
memory leak in Processor memory. Workaround: Disable SNMP.
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