Do netstat -an.  Is 162/udp shown?  Then some process or other has it and you
will have to find that one and kill it for trapd to start.  Do a ps -ef  (or
even ovstatus) and see what you find.  If Nways installed midmand, then kill it,
as he cannot run in the same box as NetView without reconfiguration.  Not him?
Then find what new stuff is running and kill it one at a time.  Or kill all the
daemons down to nvsecd, ovstart trapd, and then ovstart.  I'll bet the guy who
has trapd's port won't start if trapd comes up first.   This should get you back
and running while you review what took place.

James Shanks
Tivoli (NetView for UNIX) L3 Support