nv-l
[Top] [All Lists]

MLM on NT (Win2k) not forwarding traps (new info)

To: nv-l@lists.tivoli.com
Subject: MLM on NT (Win2k) not forwarding traps (new info)
From: "Andy Mindnich1" <MINDNICH@de.ibm.com>
Date: Mon, 17 Dec 2001 15:39:49 +0100
This is a multipart message in MIME format.
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@tkg.com
14.12.2001 13:12
Please respond to IBM NetView Discussion

 
        To:     IBM NetView Discussion <nv-l@tkg.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


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@tkg.com

14.12.2001 13:12
Please respond to IBM NetView Discussion

       
        To:        IBM NetView Discussion <nv-l@tkg.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





<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web