Well, I believe finally I have a good understanding of the cause of
the problems that I have experienced. I haven't solved it to my liking
but at least I now know of one get around (even partially).
Thanks to the following kind fellow Sun managers who responded (one is
a me too :)
John Cheshire <email@example.com>
Mr T Crummey <firstname.lastname@example.org>
Steve Phelps <email@example.com>
Tom Mornini <firstname.lastname@example.org>
John suggested me to use /usr/sbin/in.routed -q
Tom suggested me to run gated
Steve believes it's a bug in Solaris in.routed.
The final Tom provided me a conjecture.
I played with the /usr/sbin/in.routed in various ways using -s -S -q
to no avil. Reviewing the implementation of in.routed, I simply believe
it's even a good idea to run it. Thus, I ftped the latest gated beta,
compiled it and installed it. It runs ok other than an annoying ioctl
error message that keeps showing up on the console :(
The best way, IMHO, is to replace our current router (a stupid
Livingston, which I will never buy! Any router that runs RIP on its
ethernet interface(s) should be junked asap if condition permits :->
with a programmable one like cisco. I will learn how to
program ciscos and then get one. Hardware solution should be more
efficient than (if more costly) the software get arounds.
Thanks to everyone who responded.
My original question:
I was trying out the Solaris ifconfig le0:N IP logical interface assignment
feature on our network tonight. The machine is a SS5 running Solaris 2.5.
It's physical interface's IP is from our 1st block of Class C IP. On the
same LAN, there is another SS which runs SunOS 4.1.3U1. On the later,
there are quite a few VIFs assigned to its interface already.
Because of this, I tried to assign IPs from another class C block to
the logical interfaces on the SS5. Since such addresses are from a
different IP block, so the SS5 becomes a router, and thus I invoked
the /usr/sbin/in.routed -s on it.
To see how the machine/LAN handle such logical interfaces, I created
and assigned 254 logical interfaces. Then suddenly, the machine felt
strained, and the transciver lights on another SS showed lots red lights
- collisions, i.e. packet storms.
I immediately killed in.routed on the SS5 and things calmed down right
away. But then of course all logical interfaces created on the SS5
As far as I can see, the packet storms that I saw were caused by the
broadcasting of RIP by in.routed. The broadcast went to all devices
on the LAN, real or logical. Since there are quite a few of them,
so ethernet packet jams (or storms) occured.
Is there a way to prevent such random/blind broadcasting of RIP stuff?
Thanks for any hints/suggestions.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:55 CDT