Well, it sounds like a sledge-hammer approach but yes, I think that would 
work.

Though I would only change the UDP port.  Only applications like MLM send 
traps over TCP.   And you would want to leave that avenue open for 
processes which are expecting to use it.  But if you do this, then trapd 
would not see any external traps. but he'd still get all of netmon's and 
the other daemons because they use a domain socket right on the box and 
don't go out over the net. 

Of course that assumes you don't need any external traps for operators to 
see, for rulesets or ovactiond to automate from, or to be passed on to 
TEC.  And it doesn't improve your network bandwidth.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group
 





"Scott Bursik" <tivoliesm AT hotmail DOT com>
03/07/2002 03:14 PM

 
        To:     nv-l AT lists.tivoli DOT com
        cc: 
        Subject:        [nv-l] Change SNMP trap receive port?

 

Sorry if I posted twice on this. Either there is a lag in email, or I miss 
sent.
Could I change the tcp and udp ports that netview listens on until I have 
control over the SNMP trap flood that our Cisco devices are throwing at 
NetView? I see the settings in serversetup. Would that have any ill 
effects on NetView? Would that give me the desired effect of dumping all 
incoming external traps?

Thanks,
Scott Bursik 
Pepsico Business Solutions Group 
scott.bursik AT pbsg DOT com 

Send and receive Hotmail on your mobile device: Click Here
--------------------------------------------------------------------- To 
unsubscribe, e-mail: nv-l-unsubscribe AT lists.tivoli DOT com For additional 
commands, e-mail: nv-l-help AT lists.tivoli DOT 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)