On Mon, 17 Nov 2003, Tuomas Groves wrote:
> Has anyone heard of Nessus messing up HP 4000M switches? A scan was
> recently run on our network, for the first time, and we had the
> dangerous plugins turned off, but our switches still went nuts. We have
> meshing enabled and stacking disabled, and after the scan had run for
> about 5 minutes an alarm went off letting us know the network was down.
> All the mesh links were lost so none of the switches would talk to each
> other. We tried resetting the switches, etc, but in the end we had to
> rewrite the meshing info back in. Next time I�ll not scan the switches,
> but it really caused heck around here, so I was wondering if anyone else
> has had something like this happen to them?
I am unfamiliar with this mesh thing but a full nessus scan opens about
65000 port per host through multiple means and if the units must take some
decision and does not clear out these tables quicly you will see an
exhaustion of means and the switch will fail on you.
This may even occur if the unit is not targeted itself.
Another unit that can not stand to be in front of a nessus server (even
when not targeted) is a PacketShaper. It's tables will fill and it will
actually drop traffic as I found out the hard way.
Hugo.
--
All email sent to me is bound to the rules described on my homepage.
[EMAIL PROTECTED] http://hvdkooij.xs4all.nl/
Don't meddle in the affairs of sysadmins,
for they are subtle and quick to anger.
_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus
