>> This is true because of what (I feel) is a fundamental problem with the
design of NetView, namely that the API for the map database is provided by
the GUI process itself (ovw).

I suspect that you may be right about this.   We have been asking for CLI
map functions since the days of NetView 6000 (we are long time customers of
this).

We are right to ask for this;  as many of us know there are automated
processes in large data centers that track devices, including whether they
are to be monitored or not.   This issue "is it to be monitored" becomes
much more important as the network size, complexity, and rate of change
grows.  We in fact spend far too much time tweaking the maps manually than
we should, because we cannot automate.   As far as catching the unwanted
alerts, we drop them in TEC, but I would rather stop them at the source.

So, if I had my wish list:

1) ability to manage and unmanage interfaces from the CLI
2) ability to add a device and have it discovered via the CLI, even picking
what map to put it on
3) ability to delete a device and all its interfaces via the cli
4) cli method of dumping and viewing topology


It should have been done by now unless it is a complete rewrite?


Don Mahler
Telcordia


ps I wonder if HP has ever added this into openview (no shot intended)