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
|