Re: Netview Client

1998-08-17 11:11:05
Subject: Re: Netview Client
From: Stephen_Hochstetler AT TIVOLI DOT COM
To: nv-l AT lists.tivoli DOT com
Date: Mon, 17 Aug 1998 11:11:05 -0400

Using NetView client instead of an X-client is actually easier on the
machine, less network traffic.
Are you running 10MB Ethernet?   You may be dropping some packets which
mean that you miss
some status traps being sent to the NetView client.   Since the X-client
gets its status traps via
loopback, it does not depend on the network.      When my customers clean
up the bottlenecks
on their infrastructure, the problem has always gone away.     Once in a
while I have also found
bad interface cards this way.   It talks, but it does drop some packets.

When this happens, there is a quicker way to reset all status than to
refresh the map.    All you
have to do is to stop the "ipmap" process that is running for your Netview
Session.    Make sure
it is your ipmap and no one elses.    Netview automatically restarts it and
 you will see your
map drop into "sync" mode while it verifies the status of all icons.

Steve Hochstetler
Tivioli Professional Services

Michael Seibold wrote,


> Date:    Fri, 14 Aug 1998 09:03:56 +0200
> From:    Michael Seibold PTS/M-SW <mseibold AT STR.DAIMLER-BENZ DOT COM>
> Subject: Re: Installing a Netview Client
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit


> Hi Diba,

> I can't tell you which one is better, but with the X-Clients we have
> less problems. But it's true that also the X-Client shows sometimes
> different object status on different screens, using the same map. Only a
> "refresh map" solves this problem. Some folks from IBM told me that,
> when the AIX-Clients were available, some code was removed which updated
> the maps of X-Clients (speeking of the object status, to get topology
> changes I can accept to refresh the map). I still can't believe that
> they really took away this part of the code, but at the moment we have
> no other solution than refreshing the map from time to time.

> To avoid this problem we use a collection group showing only those
> devices where an interface or the node itself is down, but then you need
> to have read/write - access to the map to get the changes visualized on
> the screen, so we have to make a secondary map of each of our maps for
> the network control center, which means a lot of work.

> So I am sorry, but I have no solution to this (we are hoping and waiting
> for NV5.1 to be better ...)

> Michael Seibold

Adibah Mohamed wrote:
> Hi,
>   I've always been using x-host for clients but seem to have the same
> problem of my clients showing different ovject status... (had to refresh
> the map).  I'm tempted to install NV Client instead, hoping to eliminate
> this problem.
>   Micheal, if you're saying that you have the same problem as I am with
> my x-host, which is the better?
> Diba
> Michael Seibold PTS/M-SW wrote:
> >
> > Hi Frank,
> >
> > we installed NV Clients (didn't do it myself, so i can't tell you how),
> > but we had a lot of problems with clients showing different object
> > status (after restarting the clients they showed the correct status,
> > that's no way to work) so we stopped using NV Clients and went back
> > using X-Clients.
> >
> > Won't help you, but just a hint.
> >
> > Michael Seibold
> >
> > GribbonFG AT STENTOR DOT CA wrote:
> > >
> > > Has anyone installed the Netview Client and what procedure did you
> > >
> > > Regards,
> > > Frank

<Prev in Thread] Current Thread [Next in Thread>
  • Re: Netview Client, Stephen_Hochstetler <=