nv-l
[Top] [All Lists]

RE: [nv-l] IP Address and $A option for automated action

To: <nv-l@lists.us.ibm.com>
Subject: RE: [nv-l] IP Address and $A option for automated action
From: "John Sobrinho" <john_sobrinho@sympatico.ca>
Date: Wed, 30 Mar 2005 21:17:34 -0500
Delivery-date: Thu, 31 Mar 2005 03:18:16 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Importance: Normal
In-reply-to: <OF8B350289.23392761-ON85256FD4.004E3AAF-85256FD4.004EDB9A@us.ibm.com>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
james/paul thanks for you reply..

yes you are correct in your assumption,  we use postemsg to send tec event
out.

Thanks for your tips..

John


-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On
Behalf Of James Shanks
Sent: Wednesday, March 30, 2005 9:21 AM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] IP Address and $A option for automated action






$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>

Archive operated by Skills 1st Ltd

See also: The NetView Web