If you cannot see anything by examining the config file that
gets updated by your remote activities, I would turn on tracing
and examine the log during startup, when it evaluates that
config file. I don't know for sure where this is done on MLM on
NT, but on AIX there is a place where you configure the level
of logging as well as the number and behavior of the logs.
Make sure the midmand daemon log is separate from the
trap log. I've been looking at them more than I like to, lately.
It is capable of a lot of detail.
Is it possible that it lost name resolution for the Netview box?
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
James
Shanks/Raleigh To: IBM NetView Discussion
<nv-l@tkg.com>
/IBM@IBMUS cc:
Sent by: Subject: Re: [NV-L] MLM on NT
(Win2k) not
owner-nv-l@tkg forwarding traps (new info)
.com
12/17/01 10:12
AM
Please respond
to IBM NetView
Discussion
size=2 face="sans-serif">No, but you should always check the MLM
configuration Table when things aren't working. Sometimes it can get
messed up when people try to set values remotely and then things don't
work. And I would always keep a known good copy as a backup.
If you have one, I would stop MLM and switch MLM's configuration Table
back to a known good copy, or the default if necessary, and start over.
That's the usual advice from the MLM guy in development.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group
Andy
Mindnich1/Germany/IBM@IBMDE To: IBM NetView Discussion
<nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com cc:
Subject: [NV-L] MLM on NT
(Win2k) not forwarding traps (new info)
12/17/2001 09:39 AM
Please respond to IBM
NetView Discussion
Hi all,
we have done some more problem determination regarding the previously
mentioned problem. Maybe now someone has an idea about this.....
We discovered, that the default trap destination doesn´t work any more.
When we implement a trap destination for every filter rule, it works again.
We
tried to remove all default trap destinations and set them again via a
demand
poll from the Netview server. But that didn´t solve the problem.
The only chance at the moment is, to set a destination per filter rule.....
Anybody out there who had already such roblems ????
Mit freundlichen Grüßen / Best Regards
Andy Mindnich
_________________________________________________________
IBM Campus Network Solutions , EMEA Technical Centre Germany
Am Keltenwald 1, 71139 Ehningen, Germany
Tel.: +49-7034-15-3084, Internal: *119-3084, Fax:... -3192
Andy
Mindnich1/Germany/IBM@IBMDE To: IBM NetView Discussion
Sent by: owner-nv-l@tkg.com <nv-l@tkg.com>
cc:
Subject: [NV-L] MLM on NT
14.12.2001 13:12 (Win2k) not forwarding traps
Please respond to IBM NetView
Discussion
Hi,
maybe someone can help me with the following problem. I have an attended
MLM setup on a Windows 2000 Server. In Netview (v 6.0.2) the trapfwd daemon
is
registred to forward all traps to the local machine on port 1662. This
works fine.
The MLM is now supposed to filter on specific traps and forward only these
to
a central Netview server running on AIX.
The MLM is configured to listen to port 1662, which seems to work because
all traps
can be seen in the trap log file of the MLM. The default action is set to
block traps.
Several filters have been implemented to match on about 8 specific Cisco
traps
and one filter for all Netview traps. This has worked fine for a while now.
The matched
traps have been forwarded and displayed correctly in the central Netview
server.
In a final week of testing and collecting the number of received events
prior to
production move we recognized in the middle of the week, that the MLM
doesn´t send
any traps any more.
We investigated the problem and came to the following conclusion. The MLM
receives
still all traps from the local Netview, because you can see them in the
trap log file of the MLM
and the received counter is increased. Even the filter matching seems to be
working,
because the counters for each filter are updated correctly.
But no trap packet leaves the box towards the netview server. The trap
destination
is set correctly and the network interface is running. We had a look at the
traffic with
the Windows Network Monitor (a kind of sniffer). Polling traffic can still
be seen, traps
are received and so on. But the MLM doesn´t send any traps to the netview
server.
Any ideas on this??
The only change happened during this week was, that somebody activated the
APM
daemon by accident on the AIX box. We disabled it again and deleted the
trap destination
entry that the APM had configured in the MLM (only the one for APM, not the
one for the
Netview server).
Mit freundlichen Grüßen / Best Regards
Andy Mindnich
_________________________________________________________
IBM Campus Network Solutions , EMEA Technical Centre Germany
Am Keltenwald 1, 71139 Ehningen, Germany
Tel.: +49-7034-15-3084, Internal: *119-3084, Fax:... -3192
|