For systems that are short of memory and being flooded with unsolicited
traps that cannot be turned off for a while, I wonder if this approach
would be appropriate: reduce the 'no' setting for udp_recvspace to
something rather smaller, but leave tcp_recvspace at the correct value.
Would this cause trapd to miss out on incoming traps, but still get all of
the Netview - generated ones? Trapd is handling the flood fine, but nvcorrd
can't keep up. Just wondering... My next suggestion is going to be an MLM
on the same box.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
|