In my opinion, the reason why NetView has not been designed to put routers
in to location objects is as follows:

1. Location objects exist to contain networks - as many or as few as you
want.
2. Routers are network devices that connect networks together.
3. Therefore, if you have a router connecting two networks (A and B) and
have network A in one location and network B in the other, where would the
router be placed? This is probably an impossible question for any sort of
automation to answer.

Of course, if all the networks that a router is connected to are in one
location, then there is an argument for the router to automatically be
placed in that location .... but what if another network is added in the
future, and that network isn't in the location.

The way that we made life easier at a customer with 1000s of routers, was
to incrementally discover the network, location by location, cutting and
pasting the routers in to the appropriate location objects as appropriate.
Note - before we had installed NetView 6.0.1, we had the GUI crashing very
often during the cut & paste operations.

This is probably not of much help to anyone, but maybe it can serve as a
sign that we aren't alone out there, having to move around loads of network
objects!

Danny Williams
IBM Global Services