I received just a couple responses. Unfortunately, no new "holy grail" procedures. What I have done already is disable ARP on the interface and create static ARP entries. This is an intrusive procedure that must be manually performed on each system. Having hundreds of these pairs makes this a challenging maintenance task. Joe On Tue, 28 Sep 2004 09:06:39 -0700, Webpro <aielloster@gmail.com> wrote: > I have a server configuration where a pair or servers are connected > via a x-over cable. They are connected to one or more LANs via other > interfaces. The private x-cover connection uses addresses in the > reserved ranges. Servers A and B are directly connected and servers D > and E are directly connected. e.g. > > Server A Server B > Public: 210.210.210.21 Public: 210.210.210.22 > 10.10.210.21 Xover 10.10.210.22 > > Server D Server E > Public: 210.210.210.23 Public: 210.210.210.24 > 10.10.210.21 Xover 10.10.210.22 > > We often see when server B x-over sends and ARP for 10.10.210.21, it > is sent out the public interface. Server D responds with it's private > interface MAC address (for its 10.10.210.21 IP address). Server A > updates its local ARP table with the MAC from server D. vital > communications between Server A and B over this x-over connection are > disrupted. > > I am not running ip forwarding or routed. > > I need to ensure the Solaris does not forward the ARP from the private > link to the public interface. I am not sure why it would since it is > locally connected and permanent. Joe -- "Despite the hight cost of living, it still remains popular!" _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Wed Sep 29 12:33:36 2004
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:37 EST