RE: Re: [nv-l] nvserverd event in TEC

[James Shanks <jshanks@us.ibm.com>]

Then why are they paging you?  Haven't
they seen the problem before?  :-)

Seriously Ray, I'm as confused as I
can be about this.  This is 7.1.4, right? My only suggestion is that
you get an nvserverd trace and call Support.
Create a /usr/OV/bin/netnmrc.pre file
which contains the line,
        export
NVSERVERD_TRACE_TEC_EVENTS=TRUE
and then restart everything.  You'll
need to go all the way down, with "ovstop nvsecd" and come up
with "/etc/netnmrc"

I don't know whether this log will be
helpful or not, quite frankly, but I have no idea where else to look for
an answer at this time.
I don't see how nvserverd can have the
address wrong on shutdown, if he's had it right all the time before.  Once
the address and name of the NetView box have been determined for the first
time, nvserverd sets a flag to mark that and keeps them in storage.  He
shouldn't try to find a new address once the flag is set. So I am mystified
as to what is going on here.  

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

"Ray Westphal" <westphal2002@charter.net>
Sent by: owner-nv-l@lists.us.ibm.com

06/05/2004 11:03 AM

Please respond to
nv-l

To	<nv-l@lists.us.ibm.com>
cc	<owner-nv-l@lists.us.ibm.com>
Subject	RE: Re: [nv-l] nvserverd event in TEC

It was not an isolated event.
That was the 3rd weekend (3rd NetView shutdown) since the interface has
been added and the 3rd occurrence of the problem.
 
Thanks,
Ray Westphal
Enterprise Rent-A-Car
-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On
Behalf Of James Shanks
Sent: Friday, June 04, 2004 2:17 PM
To: nv-l@lists.us.ibm.com
Cc: nv-l@lists.us.ibm.com; owner-nv-l@lists.us.ibm.com
Subject: Re: Re: [nv-l] nvserverd event in TEC


So this is not an isolated event?  Or is that what you are waiting
to determine? 

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

<westphal2002@charter.net>
Sent by: owner-nv-l@lists.us.ibm.com

06/04/2004 03:01 PM

Please respond to
nv-l

To	<nv-l@lists.us.ibm.com>, <nv-l@lists.us.ibm.com>
cc
Subject	Re: Re: [nv-l] nvserverd event in TEC

James,
I found some inconsistencies in the NetView server host file. I also found
a misspelling for the NetView server hostname in the TMR's host file (although
that should not affect the source). 

I was reading the message from the 3.9 TEC Console (java GUI). This is
what our operations folks monitor. Here is the message from wtdumprl:
Nvserverd_Event;source=nvserverd;origin=0.0.0.0;hostname=UNKNOWN;adapter_host=UNKNOWN;date="05/30/04
01:03:47";status=OPEN;severity=
FATAL;msg="nvserverd is ending";END

DNS is not shutdown. However - the host files are read by the server first.

The message is received by the TMR very quickly. Other events appear correctly.

Let's see what happens this Sunday.

Thanks.
Ray Westphal
Enterprise Rent-A-Car




> 
> From: James Shanks <jshanks@us.ibm.com>
> Date: 2004/06/04 Fri PM 04:52:28 GMT
> To: nv-l@lists.us.ibm.com
> Subject: Re: [nv-l] nvserverd event in TEC
> 
> Well, that is the standard "nvserverd is ending message"
you get when he 
> is shut down, but that is not how it looks when you do wtdumprl, so
I'm 
> not certain where you are reading it from, though I suppose that does
not 
> matter.  From the nvserverd code, the only way that the hostname
would be 
> UNKOWN is if it could not be resolved, and the 0.0.0.0 IP address
is what 
> you get if we cannot determine that.    Does DNS get shutdown
too?  That 
> might explain the first case, but the latter has me confused too.
> 
> And this message should have come into TEC within seconds of when
you shut 
> everything down, which it now seems is what happened, not hours later.
> I thought you were home in bed at 1 am, and this was very old news.
  Or 
> am I missing something? 
> 
> But if we have bad name or address resolution then it should show
up in 
> many TEC events, not just this one.  The ones just before the
shutdown are 
> OK?   And things were OK after you brought it up?  Is the
adapter_host 
> still the same before and after?
> 
> I couldn't be more confused by this problem description.  There's
some 
> piece to this puzzle I don't have but I don't know what it looks like.
> 
> 
> James Shanks
> Level 3 Support  for Tivoli NetView for UNIX and Windows
> Tivoli Software / IBM Software Group
> 
> 
> 
> <westphal2002@charter.net> 
> Sent by: owner-nv-l@lists.us.ibm.com
> 06/04/2004 11:53 AM
> Please respond to
> nv-l
> 
> 
> To
> <nv-l@lists.us.ibm.com>
> cc
> 
> Subject
> Re: [nv-l] nvserverd event in TEC
> 
> 
> 
> 
> 
> 
> Sorry about that James,
> 
> I should have supplied more information. I hope the following helps
you 
> help me. 
> 
> 1) We added a interface to the IBM server. It is the 4th interface.
No 
> changes were made to the other interfaces.
> 2) The interface IP addresses and names of all of the interfaces are
in 
> the /etc/hosts files.
> 3) At 1am on Sunday morning - we backup the server so I shutdown NetView.
> After the restart, I run reset_ci. 
> 4)The message in TEC is:
> "nvserverd is ending. 
> This Fatal Nvserverd_Event event was received by a TEC server at 5/30/04
> 1:05:22 AM."
> The event source message is:
> "This event was reported by NetView (TEC) from UNKNOWN.
> It originated from 0.0.0.0 (TEC), on the host named "UNKNOWN".
> 
> Thanks in advance.
> Ray Westphal
> Enterprise Rent-A-Car
> 
> 
> 
> 
> 
> 
> From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]
On 
> Behalf Of James Shanks
> Sent: Thursday, June 03, 2004 3:48 PM
> To: nv-l@lists.us.ibm.com
> Subject: Re: [nv-l] nvserverd event in TEC
> 
> 
> 
> The short answer is "no", nvserverd does not bind to an
address, whatever 
> that means.  But it does try to resolve the address of it's own
NetView 
> box. That's how the fields like adapter_ host are set.   A new
interface 
> card?  Does it replace the old one? 
> If you have changed NetView's address then you must do reset_ci and
> restart the daemons. 
> 
> If none of this is helpful, it would be really helpful to the rest
of us 
> if you would post the actual message you were paged for.  It's
hard having 
> to guess what it looks like.  And it would be helpful to know
whether the 
> same fields were messed up in other messages sent to TEC or they are
> unique for this one. 
> 
> 
> James Shanks
> Level 3 Support  for Tivoli NetView for UNIX and Windows
> Tivoli Software / IBM Software Group 
> 
> 
> <westphal2002@charter.net> 
> Sent by: owner-nv-l@lists.us.ibm.com 
> 06/03/2004 03:44 PM Please respond to
> nv-l 
> 
> 
>  To <nv-l@lists.us.ibm.com> 
> cc 
> Subject [nv-l] nvserverd event in TEC 
> 
>  
> 
>  
> 
> 
> 
> Hello Everyone.
> NetView 7.1.3 on AIX 5.2 ML2
> 
> I recently was paged at 1am for a nvserverd "Fatal" event
that showed up 
> in TEC for an UNKNOWN server. The Tivoli admin checked his reception
log 
> and confirmed the event was received by the TMR with the host UNKNOWN
and 
> the IP address 0.0.0.0. Does nvserverd bind to a server IP address
and is 
> there a way to determine the IP address? I think this is related to
> installing a new interface on the NetView server. 
> 
> "wping", "odadmin odlist", "wlookup"
and other Tivoli commands all seem to 
> work correctly.
> 
> Thanks in advance.
> Ray Westphal
> Enterprise Rent-A-Car
> 
> 
> 
> 
> 
> 
>