Hello Kem -
Demand poll is a process that requires the poller to send a trap to netmon to do
the poll and wait for results. If netmon is very busy doing other things, then
you may encounter this message. This is particularly true right after startup,
and for the first 15 minutes or so of netmon's life, and during every config
check when he is doing SNMP gets to every node in the network. What to do?
Well, if the problem doesn't subside in time, then I don't know what to tell you
to do, exactly. I can tell you that the demand poll function has been
significantly enhanced in NetView 6.0.1 to reduce the incidence of his kind of
thing, but as to what you can do at the level you have, I don't know. Short of
sending a note to email@example.com and ordering the 6.0.1 maintenance upgrade,
I have no other suggestions.
I am sorry that I have no real suggestions for you. I don't do netmon nor do I
do client-server, especially on NT, so my only advice, other than get 6.0.1, is
that you call IBM/Tivoli Support (1-800-TIVOLI-8) and open a problem with them
for some assistance by someone who can help you. I cannot shorten that process
for you as I forbidden to take any problems except those that come in through
the Support channels.
I am copying the NetView list with response in case anyone there has a better
Hope this helps
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
Kem Shin <KemS@fool.com> on 08/29/2000 02:27:29 PM
To: James Shanks/Tivoli Systems@Tivoli Systems
Subject: problem with demand poll
My name is Kem H. Shin /network engineering at The Motley Fool.
We have recently implemented Netview v6.0 for NT ,and we are having
problems with demand poll. We would appreciate any comments or suggestions
regarding this issue.
Problem: When demand poll is ran on any object, we receive following errors:
Error: Cannot establish a connection to the Network Monitor (netmon) on the
The Network Monitor must be running on the server.Also, check
/usr/ov/log/nv.log on the server for possible errors.:
Waiting for a process to open the other end of the pipe.
Ovstatus shows that netmon and all other process is running/well behaved;
and we are able to retrieve SNMP values from any objects using the MIB