RE: (ASCEND) Overloading of MAX ethernet ports?

[Neale Banks <neale@idesign.com.au>]

On Mon, 13 Jul 1998, Adam Neat wrote:

> I thought people would be interested to know we have found a possible solution 
> to this - I was flooded with others saying they had similar problems.
> 
> It does boil down to some limitation with the Max - not doubt there. Whether 
> its a CPU or actual interface issue I dont know.
> 
> ICMP requests on our network were 'flooding' the interface of the MAX - its 
> only an 1800 so our 4060 or other people's 4060's may not suffer - who knows.
> 
> We killed all the default routes on all our servers and ran routed (routing 
> daemon for Unix). We turned on V2 RIP send only on the max.
> 
> Our ping times over the ethernet dropped from between 5.5ms - 7000ms down to 
> 2.4ms to 500ms. Still not perfect, but we havent changed over all servers yet.

Hi Adam,

Not sure that I'm fully with you here...

Are we concluding that the problem was related to the MAX1800 being set
as the default gateway for some/most/all systems on the local ethernet?
And that the resultant number of ICMPs (small packets, so low volume?) was
just too much for the MAX1800?

With the default routes removed, are you reducing ICMPs from local
ethernet servers to the MAX1800?  If so, where do they go now?

Regards,
Neale.

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

---

References:

• RE: (ASCEND) Overloading of MAX ethernet ports?
• From: Adam Neat <adamneat@ipax.com.au>

---

• Prev by Date: RE: (ASCEND) Overloading of MAX ethernet ports?
• Next by Date: RE: (ASCEND) Overloading of MAX ethernet ports?
• Next by thread: (ASCEND) What the big ones do
• Index(es):
  • Main
  • Thread