AW: [nv-l] automation of add,delete, change activities
2004-10-12 07:18:46
Hi Leslie,
thanks for your reply
and the hint dealing with the S flag.
Before a request is
accepted and is forwarded to the Netview servers, a check is done via our
internal request portal.
Only if the
check ensures that a new interface can be added for instance, the add
activity is performed in the next step on the Netview server.
The S flag is something
important that we might need, cause as long as an interface should stay linked
to a device in Netview (i.e. as long as no delete request was set up), a config
poll should not be able to remove this interface from the device at all.
best regards,
Thorsten Mildeberger
EMS Solutions - SMC Tools &
Automation ITO - Central
Region EDS Deutschland GmbH
Eisenstr. 43 65428 Rüsselsheim Tel.: +49 (0) 6142 80-3706 Fax.: +49 (0) 6142
80-3030
mailto:thorsten.mildeberger AT eds DOT com
Just a clarification: there is a difference between
configuration polling and new node discovery polling. You can turn off new node
discovery polling, and add nodes as directed by your change control process, and
allow configuration polling to discovery new interfaces on existing devices. In
some cases it will also remove interfaces that no longer exist in the interface
tables of the device. That depends on whether there is an S flag in the
oid_to_type file for that kind of device.
Cordially,
Leslie A. Clark IBM Global Services - Systems
Mgmt & Networking Detroit
Stephen
Hochstetler/Austin/IBM@IBMUS Sent by: owner-nv-l AT lists.us.ibm DOT com
10/01/2004 07:15 AM
|
To
| nv-l AT lists.us.ibm DOT com
|
cc
|
|
Subject
| Re: [nv-l] automation of
add,delete, change activities |
|
Thorsten,
I helped setup an environment that needed this function
a number of years ago. I can talk about it in general terms.
1 -- doing a
config poll is still VERY IMPORTANT. Don't let people tell you that you should
not do this. If this is true, then you have lost much of the power of NetView.
You will end up with many 'islands' of nodes in your view. It is better to
discover all the interfaces on a device and unmanage the interfaces that you do
not wish to monitor.
1 (part b) NetView generates a trap every time a new
interfaces is discovered. You can log those to see if new interfaces should be
managed. Some automation is possible with scripts too to see if the change is
ok. If not ok, then have script unmanage the interface.
2 -- you need a
'database' of nodes with IP addresses that you will be managing. This database
needs to be able to generate a list of IP addresses and node names to
discover/manage....as well as be able to generate a list of managed IP addresses
(all interfaces). Then you can do the following: a) take the list of IP
addresses and node names and update your DNS (hopefully running on your NetView
server) b) the the list of IP addresses and node names and use 'loadhosts' to
discover them. (via a script that does a demandpoll right away) c) either
manually or via a script verify the interfaces on those new nodes are just those
you want to manage. Unmanage any interface you need to. d) run another script
that takes your NetView database and generates DNS zone files for the IP addr to
name mapping. This gives EVERY IP address in your NetView a DNS name. But you
want to leave your name to IP Adress lookup to remain one IP address. (should be
the IP interface on node that you are doing management through).
3 - For
the delete process, I still think it is best to have a person do this using the
map. NetView will do its own cleanup after a period of time, but usually you
want it done before that.
Stephen Hochstetler
shochste AT us.ibm DOT com International Technical Support Organization at
IBM Office - 512-838-6198 (t/l 678) FAX - 512-838-6931 http://www.redbooks.ibm.com
|
Previous by Date: |
AW: [nv-l] automation of add,delete, change activities, Mildeberger, Thorsten |
Next by Date: |
Re: [nv-l] Problem with dying event windows, Jane Curry |
Previous by Thread: |
AW: [nv-l] automation of add,delete, change activities, Mildeberger, Thorsten |
Next by Thread: |
Re: [nv-l] V7.1.3 FixPack3, syoung |
Indexes: |
[Date]
[Thread]
[Top]
[All Lists] |
|
|