done a few and it's not hard; just a tedious job. To do it you
must understand your network topology. It isn't complicated and
there really isn't much more to say than is in the sources you named and the
mailing list archives. Here's my cookbook approach.
Tivoli NetView Support for DOE
the map manually so it looks correct. At least do it on paper so you
understand the topology.
- Create a temporary Location Container (ICON) on your IP Internet
map. Cut everything from the master map and paste it in the
- Create location containers to represent your Home Site and other main
geographic or organizational divisions. Keep the number down about
twenty. For your ninety sites I'd expect about ten regions plus
- Go to
the temporary Location container and use the Locate menu function to find the
routers at your Home Site. You may need the Shift-ClickAndDrag to
magnify the map to find what you're looking for.
- Select the highlighted items and any one-legged networks connected to
them and cut them FROM THIS SUBMAP.
to your Home Site submap and paste them.
- Go to
each of your regional locations and create individual Location Containers for
sites in those regions.
- Go to
the temporary Location Container, locate and cut the routers associated with
the site and any one-legged networks. Paste them in the appropriate
- REPEAT for the NINETY locations. There ain't no such thing as a
free lunch. If the routers and their one-legged networks make the
location too messy, create a Location just to hold the router and its networks
but prefix the router name with Rtr- to make the name unique.
the intra-region multi-leg networks on the Regional maps and they will connect
the Sites. Place Multi-Region connecting networks on the top
start on the Location.conf file. You have two choices, get the tool now on
the web and capture the map you built by hand or build the location.conf file by
hand. We don't worry about networks at this point.
Create entries for the IP Internet level. Using the address
255 as a place holder will create the container. It will look like:
Create entries for each of the Regional sites and point them back to
their parent region.
Site1A 255 Site
Site1C 255 Site
Create Containers for the Routers
and their networks and point them to the parent region. Make sure none
of the location entries have the same name as any router or any
Now create the entries for the
Routers using their unique LOOPBACK addresses or their hostname (which will
resolve to the loopback address). These entries all start with the
name of the containing location container. You don't need the type of
container or the parenting of the container; they were taken care of with the
previous definition. Omitting the type and parent here avoids problems
resulting from conflicting definitions.
Now that we have the file built,
clear the existing map (or make one to use for testing) and let the
location.conf file control its layout. The Networks will place themselves
in the containers associated with the routers; one-legged networks will be in
the same container as its router and multi-legged ones will show up in the
regions or the top level.
can find detail information about location.conf (how exactly it
already looked at the documentation which comes with the product and web based
information which is in location.conf is also not enough.
facing lot of problem to create a map using location.conf.
more than 90 sites, 200 subnets and 500 devices. The map which is created by Netview is
impossible to read.
we are using smartsets to represent the map.
To create an excellent city that provides the
essence of success and comfort of living.
Disclaimer: This Electronic
Mail and any files transmitted with it are confidential and intended solely
for the use of the individual or entity to whom they are addressed. If you are
not an addressee, or have received the message by error, please notify the
sender via E-Mail or over the telephone and delete this e-mail. You are not
authorized to read, copy, disseminate, distribute or use this E-Mail or any of
its attachment in any way. Any views or opinions presented in this email are
solely those of the author and do not necessarily represent Dubai
Municipality. The recipient should check this email and any attachments for
the presence of viruses/worms. Dubai Municipality accepts no liability for any
damage caused by any virus/worms transmitted by this email.
Municipality, Dubai, UAE, http://www.dm.gov.ae