Yes, you can do what you have suggested.
is a simple matter of creating a list of devices to feed into a nmdemandpoll
This will cause netview to resolve the new
name and update the map accordingly.
However. what you are planning to do, is NOT trivial if you have any automation that is
upon a hard-coded hostname.
Be aware that a hostname
change will affect everything that is dependent upon a hard-coded
Off the top of my head, this is what could
3. Mid Level Managers
4. scripts (I have 68 scripts
would be affected)
5. Event customization
6. TEC rules
7. Static routes
8. snmpCollect configuration
Historical data would probably have to be
purged or updated with new names too.
SNMP data collection
I'm sure there are more.
Be careful what you ask for!
First Citizens Bank
You can write a script and use /usr/OV/bin/nmdemandpoll
<selection name> . In side your script you can have it read all the
selection names from a file and do a demand poll on each.
This is on AIX, you did not mention which OS you are using. I did a
similar thing last year. I dump the contents from the smartsets and used
as the input variable/file.
>>> "DePhillips, Frank"
<fdephillips@McLeodUSA.com> 07/16/03 09:56AM
We are changing are naming
standard and all routers will be changing names at one time. What is
best way to do this all at once? I can do a demand poll on one device
a time but can I do it all at once?
NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use,
copying or disclosure by any other person is strictly prohibited. If you
received this transmission in error, please notify the sender via
This electronic mail and any files transmitted with it are confidential and
are intended solely for the use of individual or entity to whom they are
addressed. If you are not the intended recipient or the person responsible
for delivering the electronic mail to the intended recipient, be advised that
you have received this electronic mail in error and that any use,
dissemination, forwarding, printing, or copying of this electronic mail is
strictly prohibited. If you have received this electronic mail in error,
please immediately notify the sender by return mail.