Not that I know of. It is documented that it works. I just have no use for them
and so have not tested that function. But that is how you do it on NT. You
put them in the seedfile with @ in front of them. Try it and tell us how it
works.
On NT you also have the option of having DHCP nodes set to user1
status when they go down, which means they will be pink and
propogate as good, sort of like AdminDown for router interfaces. So they
won't turn your map yellow every day at 4PM. That's done in the
Discovery settings. I would recommend it if you are discoverying DHCP.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Is there a problem with discovering dhcp clients as dhcp clients, in the seed
file ?
>>> Leslie Clark <lclark@US.IBM.COM> 05/13 10:33 PM >>>
On both NT and on AIX I have successfully excluded DHCP nodes from
being discovered at all by putting entries in the seedfile like this:
If your ranges is 1.2.3.64 to 1.2.5.255 with class-c mask, use
!1.2.3.64-255
!1.2.4-5.*
Depending on your mask, you may need a bunch of entries. If it is
really messy I hope to be on AIX where I can use !@oid 0 to just
exclude non-snmp nodes altogether.
On NT, those same entries with @ instead of ! would define them as
DHCP. On AIX, they are determined to be dhcp by their changing
names. If a new address matches a name already known by another
address and that old address no longer resolves to that name, the
address is changed. That is, you need dynamic dns to deal with dhcp.
Excluding nodes from discovery does not affect their ability to send
you traps, if they are capable of it.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
If you get a workstation that's beaconing, chances are you whole Token
Ring is temporarily out of commission. The only trap or event you
should see should come out of the Token-ring interface of the router,
and on your map the whole ring should be down. I don't think
workstations can generate traps concerning hard errors such as
beaconing, your hubs or switches, may be able to.
Hope this helps
Xu He
Network Solutions, Inc
--- "Todd E. Lewis" <telewis@PROVIDENTBANKMD.COM> wrote:
> What is you get a workstation that is beaconing, do
> you need to have the workstation in the database in
> order to see this problem or is this trap that is
> unrelated?
>
> >>> Xu He <xuhe@YAHOO.COM> 05/12 4:15 PM >>>
> If you know the DHCP range and you don't want to
> manage the clients,
> shouldn't you just exclude the range from discovery.
> This way, it
> won't clutter you database. The sites I am managing
> uses the lower 128
> addresses of a range with 255.255.254.0 mask for
> servers, routers, and
> switches. I just excluded all other addresses from
> getting discovered
> at all. At one point, I had about 3000 nodes. I
> was able to cut it
> down to around 700 at when I manually enter the
> ranges. It make our
> job a lot easier if there is a good IP addressing
> scheme implemented.
>
> Xu
> Network Solutions, Inc
>
> --- "Todd E. Lewis" <telewis@PROVIDENTBANKMD.COM>
> wrote:
> > Has anyone been successful in putting in ranges in
> > the seed file for dhcp and having the nodes
> > discovered as dhcp ? Thus adding to DHCP smartset.
> > I'm trying to do this so I can unmanage the
> smartset
> > full of dhcp clients, so that I don't poll them
> for
> > status.
> >
>
> _________________________________________________________
> Do You Yahoo!?
> Free instant messaging and more at
> http://messenger.yahoo.com
>
_________________________________________________________
Do You Yahoo!?
Free instant messaging and more at http://messenger.yahoo.com
|