We are maintaining a separate very simple asset database where we register
our new routers.
When a new router is registrated the application (web/perl scripts) updates
/etc/hosts on the
Netview computer (rcp) and then sends a trap to Netview how starts a script.
The script
makes a loadhosts on the new router.
The daily Netview admin. staff then places the object into the map.
I think its a very good idea to keep a separate asset database just
containing
for ex. routername, associated IP address, domain.
Our network is also very dynamic. We are very strict about change management
so when a
config change is done in the network it also has to be manually (demand
poll/delete) done
in Netview.
Unfortunately there is no way to automate the removal of old routers. As you
pointed out
this has to be done manually.
(Our WAN today=786 routers)
---
Mikael Fältman (mifal@wmdata.com)
Network Services
WM-data Infrastruktur AB, BOX 164, S-295 22 BROMOLLA
> -----Original Message-----
> From: Rob Wilkinson [SMTP:Rob.Wilkinson@MBS.GOV.ON.CA]
> Sent: den 23 februari 1999 16:09
> To: NV-L@UCSBVM.UCSB.EDU
> Subject: Netview 4 with cisco routers
>
> Hi,
>
> We use Netview for monitoring 1600 cisco routers. The environment is very
> dynamic in that there are constant changes to the network such as removal,
> upgrading, additions of cisco routers daily.
>
> Netview maps are always wrong because they contain the old information and
> it is always necessary to go and update them manually. We use a seed file
> so we need to add the new entries to this and bounce netmon. When a
> router is removed physically we need to go and remove it manually from the
> maps.
>
> We always have disconnected elements on our root map and have tried
> deleteing them and they always come back..
>
> Does anyone have a similar situation and how do you manage this or
> automate it?
>
> Thanks,
>
> Rob
|