Hi Juan,
the difference is useful by example if you have between your netview box and
the router a firewall which gives you access to only one ip network to manage
the router. You won't be able to ping the other interfaces (e.g. ip-adresses)
of the router to check if they are up. SNMP-Poll queries the MIB-Table of the
devices to see if the interfaces are all up and, hopefully, the snmp
implementation of the router is telling the correct status so you are able to
check those interfaces without having an ip route to them.
Hope this helps
Michael Seibold
Gmünder Ersatzkasse
>>> lclark AT us.ibm DOT com 28.11. 3.28 Uhr >>>
In my experience, a demandpoll on an snmp-status-polled node does
indeed check the status of each interface. Instead of showing the list
of interface addresses being pinged at the top of the output, it shows it
further down, by interface index number, with ifAdminStatus and
ifOperStatus
for each interface. If it is not doing this for you, you should call
Support.
If I have not understood the question, please ask again....
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
echevarria AT ES.IBM DOT [email protected] on 11/27/2000 01:11:09 PM
Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>
Sent by: owner-nv-l AT tkg DOT com
To: nv-l AT tkg DOT com
cc:
Subject: [NV-L] demandpoll in Netview 6.0
Hi all,
I've just tested Netview 6.0 and I found that demandpoll on a
SNMP-polled device is different to demandpoll on a IP-polled device. The
latter polls (with ping) all discovered interfaces but the former doesn't
poll any interface. Does anybody know why it is done like this? advantages?
replacement for missing functions (other than using MIB browser)?
Regards,
Juan
Juan Echevarría López
AT&T Global Network Services
Internet: jechevarria AT att DOT com
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
|
