Host route question

Discussion in 'Cisco' started by Jake, Jun 10, 2004.

  1. Jake

    Jake Guest

    Hello all

    I'm trying to verify whether host routes will work in our network.
    What I want to do, for testing purposes only, is route a connection
    from A, through B, to C. Normally traffic goes directly from A to C.

    We have a frame network - our operation center has 2 pipes coming in.
    Each remote branch is connected directly to our operation center via
    one of those pipes. Each branch also has a PVC to our St. Paul
    location for backup purposes. St. Paul pushes traffic over either of
    the 2 pipes going into the operation center. What I'm trying to
    confirm is if one pipe at operations goes down, the remote branches
    connecting through that line can re-route traffic to St. Paul and then
    on to Ops. Hope that makes sense.

    172.17.1.0 network is for the Operation center
    192.168.2.0 is for the remote branch
    192.168.1.0 is for St. Paul

    Here is the config from the remote branch:

    ip route 0.0.0.0 0.0.0.0 172.17.1.1
    ip route 172.17.1.0 255.255.255.0 10.1.1.69
    ip route 172.17.1.188 255.255.255.255 10.1.1.133
    ip route 192.168.1.0 255.255.255.0 10.1.1.133

    Here is the config from the St. Paul router:

    ip route 0.0.0.0 0.0.0.0 172.17.1.1
    ip route 172.17.1.0 255.255.255.0 10.1.1.65
    ip route 172.17.1.0 255.255.255.0 10.1.1.13
    ip route 192.168.2.0 255.255.255.0 10.1.1.132

    Here is the config from the Operation Center:

    ip route 0.0.0.0 0.0.0.0 172.17.1.241
    ip route 192.168.1.0 255.255.255.0 10.1.1.66
    ip route 192.168.1.0 255.255.255.0 10.1.1.14
    ip route 192.168.2.0 255.255.255.0 10.1.1.70

    When those configs are in place I am unable to ping from the remote
    branch router to the 172.17.1.188 address at Operations. The
    connection just times out. Shouldn't the St. Paul router see that
    request coming through and route it to the 172.17.1.0 subnet? Am I
    missing something extremely obvious?

    Any insight would be great!
     
    Jake, Jun 10, 2004
    #1
    1. Advertisements

  2. The best way to achieve this failover is to use a routing protocol.
    Yes, but maybe the problem is in the reverse direction. The operation
    center router only has one route back to the 192.168.2.0 network.

    What do you see when you do a traceroute in each direction?
     
    Barry Margolin, Jun 10, 2004
    #2
    1. Advertisements

  3. Why do you have 2 static equal cost routes for the same subnet to 2
    different destinations?
    Why do you have 2 static equal cost routes for the same subnet to 2
    different destinations?
    What routing protocol(s) are you using?
     
    Buzz Lightbeer, Jun 10, 2004
    #3
  4. Do yourself a favor and look into a routing protocol. EIGRP is simple and
    has fast convergance time. Just remember the "no auto-summary" command.
     
    Richard R. Field, Jun 12, 2004
    #4
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.