More than likely, as James pointed out, netmon has reloaded the topology
database, and is busy with that and subsequently with daily config checks
before it starts doing any status polling. If you follow the CPU time of
netmon with the ps -ef command, you will see it is very busy.  It will
eventually get to your demand poll. You can put netmon in full debug mode by
typing
  "netmon -M -1"
from the command line, and follow netmon.trace to verify it's doing DAILY
checks. (You will see lots of "op = DAILY" messages for the various nodes.)
If netmon is not using any CPU, something else is going on.  You may want to
contact support.

> -----Original Message-----
> From: Discussion of IBM NetView and POLYCENTER Manager on NetView et
> alia [mailto:NV-L AT UCSBVM.UCSB DOT EDU]On Behalf Of Rama, R. (Reggie)
> Sent: Wednesday, October 07, 1998 3:41 AM
> To: NV-L AT UCSBVM.UCSB DOT EDU
> Subject: Netmon traps
>
>
> Hello
>
> I would like to query something. I am using NV5.0 &  AIX 4.2.
>
> When I stop all my NV daemons & thereafter restart them, it takes an
> extremely long time before I start to receive traps from netmon.
> Also, if I
> demandpoll any node, this also does not work.
>
> Why is this. Have I not configured something properly or is
> netmon extremely
> busy polling nodes. How can I find out what is netmon doing after I have
> restarted all my daemons. Also, I have checked my trapd.log and
> there are no
> netmon trapd therein as well.
>
> Thanks in advance for all the assistance.
>
> Regards
> Reggie Rama
> Nedcor IT, S.A
>