Just out of curiosity, what are you trying to do here? If you are using
the Sun server as a router, why not just turn on routing (try "man
If the intent is to provide multihoming to the Sun server, why not
define a loopback port with an appropriate address not on either LAN and
turn on routing (both on the Sun and on the routers) so that if one LAN
or router goes down, users can reach it via the other router without
having to change the target address. Of course, local users on the same
LAN should use the LAN interface address instead of the loopback address
if they don't understand IP redirect or don't age it out properly.
If the need for static routes is security, there are ways to drive
static routes with dynamically learned routes without accepting or
otherwise using untrustworthy dynamic routing data.
>I have a Static route question and need some advice, the configuration
>is like this:
> 2514A-e0 ------ 1900 ------ e0-SUN SERVER-e1 ------ 1900 ------
> 10.1.1.1/24 10.1.1.2/24
>The SUN SERVER has two Ethernet NIC cards, each has an IP address but in
>different subnet, static routes is configured between the two NICs.
>The switch is in its default setting, no VLANs (except the default VLAN
>ip route 10.1.2.0 255.255.255.0 10.1.1.2
>ip route 10.1.1.0 255.255.255.0 10.1.2.2
>When everything is working, each static route shows in its respective
>routing table. When I disconnect SUN-e0 from the switch, the static
>route of 2514A still shows in its (the 2514A) routing table, so it will
>still send packets destined to the 2.0 subnet through its e0 interface.
>My question is how do I configure the 2514 to aware that the static
>route is not valid when any of the NICs on the SUN server goes down.
>Alex Yeung, CCNP, MCSE
Dr. Vincent C. Jones, PE Expert advice and a helping hand
Computer Network Consultant for those who want to manage and
Networking Unlimited, Inc. control their networking destiny
14 Dogwood Lane, Tenafly, NJ