The next suspect is a very busy netmon. At startup, or during the periodic
configuration poll,netmon will not respond to a request for a demand poll
right away. It is one way to test if it is busy. Look at the events
display.
Is it making events like 'system description updated'? You see those during
configuration polling and at startup. If it happens all the time, maybe
your polling cycle is too short for the number of nodes you are monitoring,
or the timeout is too long and you have a lot of down nodes, or you have
set configuration polling to happen too frequently.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking

Anytime I see something like this, my first suspect is DNS. Make sure
nslookups are working, both name and reverse lookups.

Blaine Owens
Eastman Chemical Company
Email - bowens AT eastman DOT com
Phone - (423)229-3579
Fax     - (423)229-1188

> -----Original Message-----
> From: Juan Echevarria [SMTP:echevarria AT es.ibm DOT com]
> Sent: Monday, April 19, 1999 5:45 AM
> To:   NV-L AT UCSBVM.ucsb DOT edu
> Subject:      Demand poll stopped working
>
> This is really strange:
>
> Demand Poll option from GUI stopped working. When I try it the Demand
Poll
> window opens but it gets no answer from the router/IP box. However
> snmpwalk
> works ok.
> I stopped NetView and re-started it without luck. Command ovstatus shows
> all daemons ok and running.
>
> Has it happened to somebody else? Thanks in advance,
> Juan.
>
> Juan Echevarría López
> Internet: echevarria AT es.ibm DOT com