I am using two systems running with 2.6.9-89.0.3.EL.

My Setup is like this:

Server-A has two IP interfaces:

192.168.25.68
192.168.29.3

Server-B has two IP interfaces:
192.168.27.68
192.168.31.3


/etc/sysconfig/network file in Server-A has following entries:

-------------------------------------------------------------------------------------------------------

route add default gw 192.168.25.65 metric 0 eth0
route add default gw 192.168.29.1 metric 1 eth1

route add -net 192.168.27.64 netmask 255.255.255.192 gw 192.168.25.65 dev eth0
route add -net 192.168.31.0 netmask 255.255.255.224 gw 192.168.29.1 dev eth1
-------------------------------------------------------------------------------------------------------

Where as Server-B it is:

-------------------------------------------------------------------------------------------------------
route add default gw 192.168.27.65 metric 0 eth0
route add default gw 192.168.31.1 metric 1 eth1

route add -net 192.168.25.64 netmask 255.255.255.192 gw 192.168.27.65 dev eth0
route add -net 192.168.29.0 netmask 255.255.255.224 gw 192.168.31.1 dev eth1
-------------------------------------------------------------------------------------------------------

We are using lksctp for our application with multihoming, with those two local IP addresses on each side.

Now in this case, if there is any fault in the "primary path" between Server-A (192.168.25.6 and Default-GW (192.168.25.65), simultaneously with "Secondary Path" between Server-B (192.168.31.3) and Default-GW (192.168.31.1), my SCTP association is going down.

However, network can route packet between 192.168.29.3 to 192.168.27.68, and vice versa. But, I am not sure what additional routing configuration is required to maintain stability of SCTP association.

Please advise.