|
I'm
not complaining :) It might be a nuisance but not for me. Just seems a
lot of other folks miss some stuff in the release notes. Sounds like
the doc is catching up. I didn't receive any 7.1.4 manuals so I went right to
the electronic version of the release notes.
Product
documentation is updated by IBM on a different schedule than is code.
This is not a new thing for the company nor for NetView.
It is perhaps unfortunate, but that is how
things are.
I am sorry that you
find it a nuisance, but the Release Notes is where doc updates will go until
the formal manuals can be updated the next time. The best practice is to
check the Release Notes for each major level (e.g 7.1) and again for the
latest FixPack you have ( for example, 7.1.3 FixPack2) in addition to
the formal manuals which were shipped with the product. When you want
to learn about something which is new to you, I recommend the formal manual
first and then a quick look in the Release Notes for additions and changes.
There was a full doc
update for 7.1.4 so a lot of things that were in the Release Notes for
7.1 and later are no longer there, having been migrated into their proper
places.
James Shanks
Level 3
Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM
Software Group
"Barr, Scott"
<Scott_Barr@csgsystems.com>
Sent by: owner-nv-l@lists.us.ibm.com
02/23/2004 01:48 PM
|
|
To
| <nv-l@lists.us.ibm.com>
|
|
cc
|
|
|
Subject
| RE: [nv-l] Same device
multiple times |
|
Check the Netview v7.1 release notes. Pieces of the
information about location.conf appear in the each of the release notes. The
one you are asking about is page 17 (out of 114 acrobat PDF pages) in the
NetView v7.1 release notes (called readme.pdf) in the doc folder on the
Netview CD.
As a side note to any IBMers.... this is a frequently
occuring problem where "documentation" is in the release notes. It's great you
put the new features in there, how about updating the admin guide with that
info before it gets shipped so it's in the manuals as well?
-----Original Message-----
From:
owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On Behalf
Of Christopher J Petrina
Sent: Monday, February 23, 2004 12:03
PM
To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] Same
device multiple times
Is there
documentation that is as specific as what youa re describing that i can obtain
and read somewhere? The only rela documentation that I know
forlocation.conf is the first half of the actual file itself in the commented
out section. Things such as how routers are defined and what all needs
to be defined are not in the specs. The things you talk about such as
having to make sure all the different subnets have to be in the location.conf
file would be helpful. We rely heavily on the location.conf file for
placement of all devices, we have over 100 remote sites that need to be
populated correctly from a seedfile without the use of auto
discovery.
Thanks
Chris Petrina
|
|
| "Barr,
Scott" <Scott_Barr@csgsystems.com>
Sent by:
owner-nv-l@lists.us.ibm.com
02/23/2004 11:20 AM
Please respond to
nv-l
|
To:
<nv-l@lists.us.ibm.com>
cc:
Subject:
RE: [nv-l] Same device multiple
times |
In order for location.conf to automatically
place the router ALL subnets present on the device must be in location.conf
container. If you have a router with 5 interfaces say in 4 different subnets
(lets assume you have a pair of serial links to another location that are in
the same subnet). all 4 of those subnets must be in location.conf container
for that physical site. If you miss one subnet in location.conf the icon will
float back to the ip internet map.
-----Original Message-----
From:
owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On Behalf
Of Christopher J Petrina
Sent: Monday, February 23, 2004 9:35
AM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Same
device multiple times
Correct. However using a fairly specific Location.conf
file. That device with the same name and ip addresses which shows up
correctly in the submap that it should, also keeps showing up on the main IP
Internet map. Now if you are saying that because this device has
multiple IP addresses that it will show up wherever that network segment is,
then I can understand that and remedy that.
|
|
| "Bernard
Disselborg" <BDisselborg@triple-p.nl>
Sent by: owner-nv-l@lists.us.ibm.com
02/23/2004 10:24 AM
Please respond to nv-l
|
To:
<nv-l@lists.us.ibm.com>
cc:
Subject:
Re: [nv-l] Same device multiple
times |
Chris,
NetView places a device on the IP Internet
submap, when a device has
multiple IP addresses in different IP subnets.
HTH
Bernard
>>> cjp8@meadwestvaco.com
23-02-2004 15:43:57 >>>
Me again,
Q1: Why does
entview continually find teh same device multiple times?
I
have a
device that is already in one submap but it keeps finding it
again
and
placing it ont he IP Internet map. I have deleted it from that
submap, I have ran ovtopofix and ovmapcount and even after I delete
it
once it is polling time again it just finds it again and places it
back
on
the map again?
Anyone?
-Chris
Petrina
________________________________________________________________________
This
email has been scanned for all viruses by the MessageLabs SkyScan
service._______________________________________________________________
Note:
Please update your email address for this user to
reflect
MeadWestvaco Corporation. MeadWestvaco employee email
addresses
are in the format of user@MeadWestvaco.com
This
electronic message contains information from MeadWestvaco
Corporation or
subsidiary companies, which may be confidential,
privileged or otherwise
protected from disclosure. The
information is intended to be used
solely by the recipient(s)
named. If you are not an intended
recipient, be aware that
any review, disclosure, copying, distribution or
use of this
transmission or its contents is prohibited. If you
have
received this transmission in error, please notify
MeadWestvaco
immediately at
postmaster@MeadWestvaco.com.
_______________________________________________________________________
________________________________________________________________________
This
email has been scanned for all viruses by the MessageLabs
SkyScan
service._______________________________________________________________
________________________________________________________________________
This
email has been scanned for all viruses by the MessageLabs
SkyScan
service._______________________________________________________________
|