You will have to get your TEC people to assit with the debugging. Whoever
set up the TEC will have to tell you what port it is listening on. Unless
you specify ServerPort in the tecint.conf file, the default port of 0 will
be used. If your TEC server is running on UNIX, then port 0 will monitored
by the portmapper daemon, who will redirect the TEC traffic to the port TEC
actually listens to. If you aren't running portmapper, or you have an NT
TEC server (there is no portmapper on NT) then you will have to specify the
actual TEC port in the tecint.conf See the man page on tecint.conf for
more information.
More than likely, if this works some of the time and not others, then you
have a problem with something not running properly on the TEC server or
there being a network problem between them. There is not much that can go
wrong on the NetView side.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
"Treptow, Craig" <Treptow.Craig@principal.com>@tkg.com on 03/06/2001
09:49:27 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "'IBM NetView Discussion'" <nv-l@tkg.com>
cc:
Subject: RE: [NV-L] Rulesets and forwarding to T/EC
Hi. Well, since the problem came back my /etc/Tivoli/tec/cache file is
indeed growing. Stopping and starting nvserverd didn't help. Can you tell
me what TEC process is listening and on which port so I can start doing
some debugging to see what is happening.
Or do you have a better suggestion to help me look into this?
Thanks for your help!
Craig
> -----Original Message-----
> From: James_Shanks@tivoli.com [mailto:James_Shanks@tivoli.com]
> Sent: Saturday, March 03, 2001 10:03 PM
> To: IBM NetView Discussion
> Subject: Re: [NV-L] Rulesets and forwarding to T/EC
>
>
> Hmmm. NO events? Have you looked to see whether the
> /etc/Tivoli/tec/cache
> file is growing? If so, then you have a connectivity problem
> and not a
> ruleset one. Basically, if your ruleset works in the events
> window then it
> should work fine for TEC, because nvcorrd's does the logic in
> both cases.
> Forward still means "return this event to the application
> which registered
> this ruleset". In both cases that is nvserverd, he sends the
> events back
> to each event window, and in the case of TEC, calls his internal TEC
> forwarding routines. So it sounds like you can't get through.
>
> James Shanks
> Team Leader, Level 3 Support
> Tivoli NetView for UNIX and NT
>
>
>
> "Treptow, Craig" <Treptow.Craig@principal.com>@tkg.com on 03/03/2001
> 09:52:49 PM
>
> Please respond to IBM NetView Discussion <nv-l@tkg.com>
>
> Sent by: owner-nv-l@tkg.com
>
>
> To: "NetView List (E-mail)" <nv-l@tkg.com>
> cc:
> Subject: [NV-L] Rulesets and forwarding to T/EC
>
>
>
> Hi. We are running Netview 6.0.1 on AIX 4.3. I setup
> another ruleset to
> remove the authentication errors from the event monitor display. This
> worked well, but it seems to have stopped events from being
> forwarded to
> T/EC. I'm using the same ruleset for the forwarding to T/EC
> as I am for
> the event monitoring.
>
> The ruleset has the event stream(pass) going to four different trap
> settings for the four types of authentication errors. All
> four of those go
> into one "Block Event Display". That's it. I'm ok with this
> right now, if
> it would just forward all of the non-authentication error
> events to T/EC.
>
> Does anybody have an idea of what I need to be doing differently?
>
> Thanks.
>
> Craig Treptow
> Principal Financial Group
> I/S Network Administration
>
>
> ______________________________________________________________
> ___________
> NV-L List information and Archives: http://www.tkg.com/nv-l
>
>
> ______________________________________________________________
> ___________
> NV-L List information and Archives: http://www.tkg.com/nv-l
>
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|