To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | Re: [nv-l] IP Address and $A option for automated action |
From: | James Shanks <jshanks@us.ibm.com> |
Date: | Wed, 30 Mar 2005 09:21:20 -0500 |
Delivery-date: | Wed, 30 Mar 2005 15:27:03 +0100 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
Sensitivity: |
$8 makes perfect sense if you are talking about certain NetView events, such as Node Up/Down or Interface Up/Down. If you are talking about non-NetView events, then it does not apply. You must be sending your events to TEC using postemsg, since you can specify the both the agent address and the agent hostname as TEC slots in trapd.conf if you are using nvserverd to send them. If that's the case, then I agree with Paul. You should implement a caching nameserver. Biggest performance improvement you can make for NetView, no matter what else you do. James Shanks Level 3 Support for Tivoli NetView for UNIX and Windows Tivoli Software / IBM Software Group |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | RE: [nv-l] netmon connected to trapd, Oliver Bruchhaeuser |
---|---|
Next by Date: | Re: [nv-l] netmon connected to trapd, James Shanks |
Previous by Thread: | Re: [nv-l] IP Address and $A option for automated action, Paul |
Next by Thread: | RE: [nv-l] IP Address and $A option for automated action, John Sobrinho |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web