Thanks Leslie..
I am going keep this
note as keeper, as I haven’t tackled the other box yet. As now I need to figure
out how to publish a read only ip map and ensure that map is synchronous with
the main netview map. (I think some one just went through this a few days ago,
and our set up is similar Unix box no video interfaces
etc.)
However I am happy to
say....
We are
finally seeing a decent map on the netview box that has just the routers.
Things did not line up until we placed all devices in snmpd.conf, we stop and
start nekton to force a db check of known devices vs. seedfile and few minutes
later we had very few items in ip map and everything else got slotted
automagically : - ).
The
timing was perfect as we saw a rash of ISDN link up alerts on TEC console and
could not isolate root cause, but about 20 minutes later, graphically we could
see who was impacted ( we have polling set to 20 minutes). As it turned out
something happened at a local CO and caused outages at
15 geographically different sites in different ospfs, so really in this
instance no correlation rules could of helped but graphically seeing in was very
pleasing.
I
think my issue was not understanding the relationship with the snmp config panel
and the map. Although we had devices in ip map and some in smpd.conf they were
not slotted correctly as we liked, and when we had all of them in
there everything was OK. Documentation is not clear on this relationship
or am I way on left field on my assumption ??
I
Still have a lot to learn......
Regards, and thanks
John
Sobrinho aka NV newbie..
So you are
looking for a way to generate a location.conf with a map that has already been
layed out and cleaned up. That is not what this tool is for.
I've made plenty of location.conf files
programmatically based on the customer's knowledge of the network. You know
what your general heirarchy will be, and you know which routers will be in
them. You can start with that. Edit the file and enter the heirarchy of
locations, like:
A501 255
Site2
A502 255 Site2
etc. where 255 is just a placeholder
dummy network. Under each subarea, enter the names of the routers that go in
there. You can also make entries for the subnets assigned to that OSPF
subarea. You can retreive the subarea assigments of routers with mib appls as
well. For instance,
#!/bin/ksh
#
get_ospf_if.sh
# A convenience
routine to display OSPF interfaces for a node
# at the commandline or from a script.
# Invocation: get_ospf_if.sh $NODENAME
<optional community string>
#set -x
NODE=$1
if [ -z "$NODE" ]
then echo "syntax is $0 nodename "
exit
fi
if [
-z "$2" ]
then COMM=""
else COMM="-c $2"
fi
/usr/OV/bin/mibtable \
-table ".1.3.6.1.2.1.14.7.1" \
-fields
"ospfIfIpAddress=1:15,ospfIfAreaId=3:15,ospfIfAdminStat=5:8 " \
-node $NODE $COMM
| grep -v disabled | grep -v MIB | grep -v ospf | sort -t. +4
exit 0
Do the File..New Map thing once and use that map as a
starting point. Then it is much easier to manually put everything away.
But don't stop there. Once you have it
roughly arranged, use the script to produce a new location.conf . Look
at that output. It will have many specific entries. You then can generalize
them into ranges. Those ranges (as opposed to specific entries) are what
should lessen the administrative burden later on.
Cordially,
Leslie A. Clark
IBM Global
Services - Systems Mgmt & Networking
Detroit
Paul
<pstroud@bellsouth.net>
Sent by: owner-nv-l@lists.us.ibm.com
04/13/2004 08:47 PM
|
|
To
| nv-l@lists.us.ibm.com
|
|
cc
|
|
|
Subject
| Re: [nv-l]
locations |
|
John,
One way or another, you are going to have to do the work.
Try creating
the location.conf file on the fly. This is not that
complicated, Create
a New Map, check it, add more stuff to the
location.conf rinse, repeat.
You can zoom the map down and do a few devices
at a time.
You could clear your database, control discovery, and build
your
location.conf as your discover more devices. This would be my
real
suggestion. This way you don't discover what you don't want to
monitor.
You specfically place the device where you want them via the
location.conf file. I would suggest this for anyone starting a
NetView
project. You network is a complex creature and just setting
NetView
loose can be a dangerous thing(as you have seen). It takes time
to
build a good network and it takes time to build a good map. A
good
one of each is worth their weight in gold.
You could rediscover
everything and then cut and paste stuff into the
locations, controlling
your discovery as above, once that is complete,
you can use script to
create the location.conf. The script is really
just a way to turn the hard
work of cutting and pasting into a nicely
formatted location.conf file, or
a nice way to clean up the
location.conf file if it has become unwieldy as
a result of repeated
changes.
I think perl 5.0 might be a problem,
try perl 5.0.6(8). I have used it
on both and it worked as
expected.
Paul
John Sobrinho wrote:
>
Paul/Leslie..
>
> One netview I have an existing Location.conf.
other box there is none.
>
> On the box with location.conf we
divided into East Central West, and under
> theses areas we have our
corresponding OSPF areas. We are finding that some
> of the devices are
placed correctly in the opsf area, others jut end up in
> ip map. This
box only has routers (soon to have switches), and only loopback
> ip
address is defined in DNS and in seed file when we did the discovery.
>
When this project is complete we expect about 2000 devices.
>
>
Other box is a mish mash of stuff and that map looks like a giant golf
ball
> with the skin torn off, this box has about 1500 devices.
>
> In both cases I could not produce a file.
>
> In both
cases we do not want to do any manual cut and pastes, for the amount
>
of devices we have this would be ludicrous to do and to maintain. I
was
> hoping Location could automate this, and as we discover devices
they would
> be automatically be placed in the correct
container.
>
> So I am very interetsed in this routine to see
what it will produce.
>
> Leslie.. I know were on Perl 5.0 or
better, I'll have to check the exact
> version.
>
>
>
> -----Original Message-----
> From:
owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On
>
Behalf Of Paul
> Sent: Tuesday, April 13, 2004 6:12 AM
> To:
nv-l@lists.us.ibm.com
> Subject: Re: [nv-l] locations
>
>
> John,
> Have you already customized your map to include
locations? For the
> script to work, you map must already look as you
want it to with
> locations in place and all the network devices
properly placed. It
> simply creates the location.conf file from the
locations you already
> created.
>
> Paul
>
>
>
>
>
>
> John Sobrinho wrote:
>
>>Has anyone tried this ?
>>
>>I have tried on two
different netviews one on 7.1.3 and other on 7.1.2 to
>
>
no
>
>>avail on AIX 5.1 and 4.3.3
respectively.
>>Routine runs, and but file does not get created, no
error code
return.
>>
>>
>>
>>
>>-----Original
Message-----
>>From: owner-nv-l@lists.us.ibm.com
[mailto:owner-nv-l@lists.us.ibm.com]On
>>Behalf Of Barr,
Scott
>>Sent: Monday, April 12, 2004 9:09 AM
>>To:
nv-l@lists.us.ibm.com
>>Subject: RE: [nv-l]
locations
>>
>>
>>Mario, the Tivoli NetView Users
Group has released a script (PERL) that
>
> will
>
>>build your location.conf for you based on your map. Here is the
link to
>
> the
>
>>user
group:
>>
>>http://www.tivoli-ug.org/groups.php?groupid=151
>><http://www.tivoli-ug.org/groups.php?groupid=151>
>>
>>The
code is available on the Netview users group home web page (it's
>
> called
>
>>build_location.pl):
>>
>>http://www.nv-l.org/twiki/bin/view/Netview/WebHome
>><http://www.nv-l.org/twiki/bin/view/Netview/WebHome>
>>
>>It's
under the contributed code / End User Interface
section.
>>
>>And yes, you can do location.conf after
discovery. Until you make a new
>
> map
>
>>or
restart map generation your old map would remain in
place.
>>
>>
>>
_____
>>
>>From: owner-nv-l@lists.us.ibm.com
[mailto:owner-nv-l@lists.us.ibm.com] On
>>Behalf Of Mario
Behring
>>Sent: Saturday, April 10, 2004 11:44 AM
>>To:
nv-l@lists.us.ibm.com
>>Subject: [nv-l]
locations
>>
>>
>>Hi
list,
>>
>>Can I configure a location.conf file in a NV
7.1.4 running on a AIX box
>>after the initial discovery (a
production box) ? I mean, will NV put each
>>discovered objet in its
appropriate location container ? Or this can be
>
> done
>
>>only at the initial discovery
?
>>
>>Thanks.
>>
>>Mario
Behring
>>Tivoli Certified Consultant
>>IBM
Brazil
>>55 19 2104-3006
>>55 11 8125-5598
>>
<mailto:mariob@br.ibm.com> mariob@br.ibm.com
>>
<mailto:mariobehring@yahoo.com>
mariobehring@yahoo.com
>>
>>
>>
>>
>>
_____
>>
>>Do you Yahoo!?
>>Yahoo! Tax Center
- File online by April
>><http://taxes.yahoo.com/filing.html>
15th
>>
>
>
>
|