We have a point-to-point fiber that connects two thumpers across site which is used for replication of data. Normally this is just a matter of two interfaces, no route and no problem. However, on this system (Solaris 10), when the system reboots, we end up with a route that completely shuts down other traffic. IE:
10.0.0.0 10.111.233.3
Where on other interfaces we use the same IP space like:
10.1.3.4
(ie: 10/8)
It's easy to manually delete the route, our /etc/defaultrouter is correctly set to the primary interface.
I'm more of a Linux person, but I'm wondering if we need to add a persistent route entry for that specific /24 that is not related to our internal networks?
I also noticed, and this may be a side effect of the above, the interfaces are not automatically coming up at boot (ie: ifconfig <interface> up, resolves it). I think it's due to the mishap route.
Any tips would be appreciated.
Thanks.
10.0.0.0 10.111.233.3
Where on other interfaces we use the same IP space like:
10.1.3.4
(ie: 10/8)
It's easy to manually delete the route, our /etc/defaultrouter is correctly set to the primary interface.
I'm more of a Linux person, but I'm wondering if we need to add a persistent route entry for that specific /24 that is not related to our internal networks?
I also noticed, and this may be a side effect of the above, the interfaces are not automatically coming up at boot (ie: ifconfig <interface> up, resolves it). I think it's due to the mishap route.
Any tips would be appreciated.
Thanks.
Ours is just a standard, there is nothing referencing any other networks there.