You can also use snmp views to restrict snmp polling to certain
branches of the mib tree. You can define different community strings to
specific branches of the mib tree for greater flexibility.
If this applies, Openview is particularly cpu intensive as it uses
snmp to look at a router's arp cache for periodic node discovery. If can
mitigate the issue if you give Openview an snmp community string that is
limited to only the system and interfaces branch of the mib tree, on your
router.
You can try no snmp-server to stop the snmp process. A reboot would
definitely help if the memory cannot be reclaimed.
Rick Cheung
mailto:rick.cheung@nextelpartners.com
-----Original Message-----
From: Hassan, Shehzad [mailto:shehzad.hassan@bellnexxia.com]
Sent: Friday, November 30, 2001 12:22 PM
To: 'routing4food@lycos.com'; cisco-nsp@puck.nether.net
Subject: RE: [nsp] Kill/Stop/Restart a Router Process?
Not sure if you can kill an individual process on a Cisco router, unless you
remove that feature and put it back in,
that should do it.
Are you running low on memory ?
I would be more concerned of why are these messages been generated ?
Search CCO for reasons.
Hope this helps.
-----Original Message-----
From: Routing Food [mailto:routing4food@lycos.com]
Sent: Thursday, November 29, 2001 6:23 PM
To: cisco-nsp@puck.nether.net
Subject: [nsp] Kill/Stop/Restart a Router Process?
Hello,
I am getting MALLOCFAIL messages in my log.
It basically references the process = "IP SNMP".
When I do a "show proc mem | inc IP SNMP" I see that
the allocated has 20 billion for this process.
How do I kill this process or restart it?
thanks,
J
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:25 EDT