Just to confuse, two replies for one
message.
First query: Since Bandwidth Utilization
is a mibExpr.conf definition, create a duplicate for it under another
name. Then define the first threshold entry with the original name and
the second with the name of the duplicate entry. I’m using five copies
and variations of the basic definition.
Your other query is a bit more complex and
involves the fundamental design of NetView.
.
- Do you really mean NetView
Client? There is a distincton among the NetView Server which
includes an integral NetView Client and the NetVIew Client which executes
on a separate processor complex and shares the databases resident on the Server.
The primary need for the NV Client was the shortage of resources on 1990
vintage machines to open enough X-Windows consoles to operate a big
network. The processor complex of that era could only support about
five X-window based operators before the server function began to
suffer. A Client processor could handle about ten X-operators.
- I’m at a loss as to why one
would create a NetView Client installation today with the Web Console Cllient
available. The Web Console, in my opinion, is better adapted for
operations while you need the X-windows client for administration. With
today’s memory sizes and the Web Console you should be able to
support a nearly unlimited host of operators with one NetView Server.
That assumes you can migrate those operators to the Web Console. At
the same time, an installation with multiple administrators should probably
be using a development NetVIew on a different processor from the
production one instead of a NetView Client.
- The closure of Client/Console
windows is dependent on the MAP you open (Default, Development, Custom,
etc.) and the operator instance which has it open. In any case it
also depends on how much of the server function you want to close.
It’s not an “all or nothing” situation.
- My installation uses only a NetView
Server on which we open two X-Console instances. There is only one
map. The one X-console instance is the read-write image of the
Default map. All web consoles are opened against this
instance. A second X-console instance is opened to allow the
display of a bitmap behind the submap showing the wide area network.
We can close the map-associated daemons supporting the read-write session
and the web-console daemons without affecting the read-only X-console
display.
- Closure of the database daemons
will affect all clients. You can identify which daemons will affect
which consoles by looking at a diagram of the daemons and their connectivity.
Unfortunately I can’t find a published diagram of that outside of classroom
materials. If you are interested in that level of detail send me a
message offline. (bill.evans@hq.doe.gov).
Bill Evans
Tivoli NetView Support for DOE
570-639-5691 (home)
570-852-9549 (cell)
-----Original Message-----
From: owner-nv-l@lists.us.ibm.com
[mailto:owner-nv-l@lists.us.ibm.com] On
Behalf Of Meyos Yemveng
Sent: Thursday,
November 25, 2004 2:33 PM
To: netview Tivoli
Subject: [nv-l] Netview Clients
(UNIX and Web Console)
Is it possible to stop the NV Server without closing
the Client ( Both UNIX and Web Console)?
Thank You,
Meyos
"ALLEZ LES LIONS INDOMPTABLES"
Post your free ad now! Yahoo!
Canada Personals