Philosophically, Chris, the HQ is such a
state of mind it should be its own "State". Not part of Dayton.
That simplifies the hierarchical
connectivity. Top level map contains HQ and the regions. Regions
contain Countries and states. If they all come back to the state of HQ on
the IP Internet level it's perfectly clear what's going on.
Actually all you'll see on that level is four lines linking HQ to the
regions.
Within the regions you may wind up with
isolated locations if there is no inter-location connectivity among the
states/countries. If you have Regional concentrators, though, there will
be connections focusing on those regional HQ locations. Alternatively,
place the Network icons which bridge to HQ in the Regional containers.
The lines will be drawn between HQ and Regions. Regions will go Red or
Yellow when the associated link/network goes down.
Do the same with the State/Country
level. Networks for the bridge to Region plus the locations for the
sites. Hierarchical connectivity will take care of itself and upstream
connectivity will show when the network icons turn color.
Try it. I think your design problem
has been in trying to stick too strictly to a geographic model. Expose
the hierarchy of the infrastructure (the state of Mind) and it should make it a
bit easier.
Bill Evans
-----Original Message-----
From: Christopher J Petrina
[mailto:cjp8@meadwestvaco.com]
Sent: Thursday, February 26, 2004
1:29 PM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] More
location.conf questions...
Leslie,
I
guess the important requirements for Netview were left out of that. I was
stating how we get our information about devices. It is an imperfect
means of data but it is the closest thing we have to a central repository of
devices.
For
Netview and location.conf details though here is what I want to Accomplish:
The
top layer IP Internet Map of Netview consists of Regions: MIdwest, NorthEast,
International, etc. Each are a Container that holds states/countries.
Each state/country is also a location container that houses city location
containers. Each City name is a site. In each site I want that local
sites LAN to be mapped. from the border router that is the WAN/LAN device
as top device and then all the segments and switches and networks within the
site itself are all in that city container. My WAN links are the biggest
issue for tying sites together. They ahve to basically come back to the
HQ site in Dayton, Ohio (Which is a container in the State of Ohio,which is a
container in the Region of Midwest). Should I be placing my WAN networks
between the containers? And at what level? There are far too many of them
to put on the Top IP Internet map. It causes the Map to be very hard to
understand. &nb! sp; However if I place them incorrectly, accorrding to
location.conf rules then I do not get the desired results I am looking for.
Thanks
Chris
Petrina