To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | Re: [nv-l] Using a MLM as a trap receiver |
From: | Stephen Hochstetler <shochste@us.ibm.com> |
Date: | Wed, 11 Feb 2004 13:27:10 -0600 |
Delivery-date: | Wed, 11 Feb 2004 19:33:02 +0000 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
In-reply-to: | <42AF0749A8EB7448A661EC423CBE76FA05FD20@pbswmu00003.corp.pep.pvt> |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
Assuming you have a multi-CPU box, I would recommend you install the MLM on your NetView server. You still get great benefits with this. You would need to change the port that trapd is listening to. You would configure the forwarding address of your MLM to the trapd listening port. You can configure trap filters in the MLM as rate rules or other duplicate detection. For example, if you receive more than 10 of these in 1 minute, only send the first 10 and drop the rest. (whatever rate rule you want). You can even do things that say to forward one event AFTER you have received 10 in 1 minute. A lot of power is there. It complements NetView nicely.
AIX 4.3.3 NetView 7.1.3 We are considering deploying a MLM to offload the incoming SNMP traps to. At a high level are there any cons to doing this? Also, is there a way of doing any duplicate detection at the MLM level in the case of an event storm? Thanks, Scott Bursik |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | [nv-l] Using a MLM as a trap receiver, Bursik, Scott {PBSG} |
---|---|
Next by Date: | RE: [nv-l] Using a MLM as a trap receiver, Bursik, Scott {PBSG} |
Previous by Thread: | [nv-l] Using a MLM as a trap receiver, Bursik, Scott {PBSG} |
Next by Thread: | RE: [nv-l] Using a MLM as a trap receiver, Bursik, Scott {PBSG} |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web