Thanks for the information. Chris, help me with my understanding of the
netmon daemon and the -g -Gmlmseed -z switches which assume the discovery
role for that mlm domain. If you were to provide the MLM with multiple
subnets, through an automated collection modification, would these options
not force discovery of subnets outside the initial MLM segment? I'm going
to try it, I'll keep you posted as to the results.
----- Original Message -----
From: "Chris Cowan" <chris.cowan@2ND-WAVE.COM>
To: <NV-L@UCSBVM.UCSB.EDU>
Sent: Tuesday, October 19, 1999 6:58 PM
Subject: Re: mlm discovery process
> > "Frank W. Hansen" wrote:
> >
> > Could someone please define how an MLM's discovery process works after
> > it has discovered the devices in its own subnet? More specifically,
> > if I add a subnet to the collection, should I not see the discovered
> > devices in the log file on the MLM server?
> >
> > Best Regards,
> >
> > Frank W. Hansen
> > Tivoli Enterprise Certified Consultant
> > 919 467 9183
>
> The MLM will never discovery outside of it's subnet (the engine and the
> engine and options are just too simplistic for the task), status polling
> is another story. The MLM will of course discover multiple subnets, if
> it is multi-homed.
>
> There is some time lag before you will see the change to status polling,
> netmon and the APM handle it. You can verify who is actually polling
> status by browsing the Status and Interface Monitor tables (using
> smconfig or the MIB Browser), and the netmon the ping list (generated in
> netmon.trace with the -a15 and -a16 flags to netmon).
|