This is a multipart message in MIME format. 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
Sent by: owner-nv-l AT tkg DOT com
12/17/2001 09:39 AM
Please respond to IBM NetView Discussion
To: IBM NetView Discussion <nv-l AT tkg DOT com>
cc:
Subject: [NV-L] MLM on NT (Win2k) not forwarding traps (new info)
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
Sent by: owner-nv-l AT tkg DOT com
14.12.2001 13:12
Please respond to IBM NetView Discussion
To: IBM NetView Discussion <nv-l AT tkg DOT com>
cc:
Subject: [NV-L] MLM on NT (Win2k) not forwarding traps
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
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
Sent by: owner-nv-l AT tkg DOT com
12/17/2001 09:39 AM
Please respond to IBM NetView Discussion
|
To: IBM NetView Discussion <nv-l AT tkg DOT com>
cc:
Subject: [NV-L] MLM on NT (Win2k) not forwarding traps (new info)
|
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
Sent by: owner-nv-l AT tkg DOT com
14.12.2001 13:12
Please respond to IBM NetView Discussion
|
To: IBM NetView Discussion <nv-l AT tkg DOT com>
cc:
Subject: [NV-L] MLM on NT (Win2k) not forwarding traps
|
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
|