Solved

Cisco 1720 Point-to-Point routing issue

Posted on 2007-03-20
3
283 Views
Last Modified: 2010-04-17
Sorry...previous question posting was a bit wordy. We have two cisco 1720's connecting two sites. The two sites have T1's to the internet and an additional point-to-point T1 for inter-office communication. A backup VPN over the internet T1's is up and working.

I am testing the routes with traceroute on the Cisco and I am unable to get traffic to route through the point-to-point. It always goes out the default-gateway and through the firewall/vpn. I put the route commands in as per Question 22395697.  Help?

Here are the route commands that I implemented per the earlier question:

Site #1
interface Serial0
 ip address 192.168.24.1 255.255.255.0
 ip mask-reply
 no cdp enable
ip default-gateway 209.125.127.2
ip route 0.0.0.0 0.0.0.0 209.125.127.2
ip route 216.217.211.192 255.255.255.224 192.168.24.2

Site #2
interface Serial0
 ip address 192.168.24.2 255.255.255.0
 ip mask-reply
 no cdp enable
ip default-gateway 216.217.211.194
ip route 0.0.0.0 0.0.0.0 216.217.211.194
ip route 209.125.127.0 255.255.255.192 192.168.24.1
0
Comment
Question by:jeremy95926
  • 2
3 Comments
 
LVL 3

Accepted Solution

by:
cyoncon earned 500 total points
Comment Utility
Hi, can u post the complete configurations?
It seems you dont have routing protocols, you will have to use floating static routes.
Any way, post first and then we can discuss some solution
0
 

Author Comment

by:jeremy95926
Comment Utility
Here are my two configs:

Site #1
version 12.1
hostname cisco_fc
memory-size iomem 25
clock timezone PST -8
clock summer-time PDT recurring
ip subnet-zero
!
interface Serial0
 ip address 192.168.24.1 255.255.255.0
 ip mask-reply
 no cdp enable
!
interface FastEthernet0
 ip address 209.125.127.9 255.255.255.192
 ip mask-reply
 speed auto
 full-duplex
 no cdp enable
!
ip default-gateway 209.125.127.2
ip classless
ip route 0.0.0.0 0.0.0.0 209.125.127.2
ip route 216.217.211.192 255.255.255.224 192.168.24.2
!
end

Site #2
version 12.1
hostname cisco_sr
memory-size iomem 15
clock timezone PST -8
clock summer-time PDT recurring
ip subnet-zero
!
interface Serial0
 ip address 192.168.24.2 255.255.255.0
 ip mask-reply
 no cdp enable
!
interface FastEthernet0
 description connected to local network
 ip address 216.217.211.200 255.255.255.224
 ip mask-reply
 speed auto
 full-duplex
 no cdp enable
!
ip classless
ip default-gateway 216.217.211.194
ip route 0.0.0.0 0.0.0.0 216.217.211.194
ip route 209.125.127.0 255.255.255.192 192.168.24.1
end

Site 1 IP Routing Table:

Gateway of last resort is 209.125.127.2 to network 0.0.0.0

     209.125.127.0/26 is subnetted, 1 subnets
C       209.125.127.0 is directly connected, FastEthernet0
C    192.168.24.0/24 is directly connected, Serial0
     216.217.211.0/27 is subnetted, 1 subnets
S       216.217.211.192 [1/0] via 192.168.24.2
S*   0.0.0.0/0 [1/0] via 209.125.127.2

Site 2 IP Routing Table

Gateway of last resort is 216.217.211.194 to network 0.0.0.0

     209.125.127.0/26 is subnetted, 1 subnets
S       209.125.127.0 [1/0] via 192.168.24.1
C    192.168.24.0/24 is directly connected, Serial0
     216.217.211.0/27 is subnetted, 1 subnets
C       216.217.211.192 is directly connected, FastEthernet0
S*   0.0.0.0/0 [1/0] via 216.217.211.194
0
 

Author Comment

by:jeremy95926
Comment Utility
ok...I think I've figured out the issue. I found another posting that showed a similiar setup (thanks to your floating static route comment) and the issue was that the other site test machine didn't have the correct gateway setup so the pings didn't come back. Since it didn't seem like the settings were working, I didn't want to change the computers on the network to the new gateway. With the correct gateway on both sides test computers...all is working. I can shutdown the Serial0 and the traffic routes correctly through the internet VPN.

I noticed an issue crop up after I change stations to the new gateway (previously they used the sonicwall firewall as the gateway IP). If this becomes a big question, I'd be happy to open another question but since it relates to this issue, I thought I'd post it here first.

The routing table on my clients (Windows XP) stays the same except for 0.0.0.0 and default gateway. On my servers (Windows 2003) it goes from the same as the XP to a much larger list that includes a bunch of routes to weird things like google, etc. It seems strange that this change causes the routing tables on my servers to grow. Is there some sort of route advertisement going on in my config that I don't understand that only effects Windows 2003 servers?

FYI...here are the route print statements.

Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    209.125.127.1    209.125.127.3     10
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
    209.125.127.0  255.255.255.192    209.125.127.3    209.125.127.3     10
    209.125.127.3  255.255.255.255        127.0.0.1        127.0.0.1     10
  209.125.127.255  255.255.255.255    209.125.127.3    209.125.127.3     10
        224.0.0.0        240.0.0.0    209.125.127.3    209.125.127.3     10
  255.255.255.255  255.255.255.255    209.125.127.3    209.125.127.3      1
Default Gateway:     209.125.127.1

To a much large table like this:
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    209.125.127.9    209.125.127.3     10
   63.209.251.102  255.255.255.255    209.125.127.1    209.125.127.3      1
     64.232.128.3  255.255.255.255    209.125.127.1    209.125.127.3      1
   64.232.187.101  255.255.255.255    209.125.127.1    209.125.127.3      1
   64.232.187.110  255.255.255.255    209.125.127.1    209.125.127.3      1
    64.233.161.99  255.255.255.255    209.125.127.1    209.125.127.3      1
    64.233.174.81  255.255.255.255    209.125.127.1    209.125.127.3      1
     64.233.179.9  255.255.255.255    209.125.127.1    209.125.127.3      1
     66.249.95.69  255.255.255.255    209.125.127.1    209.125.127.3      1
    70.61.150.205  255.255.255.255    209.125.127.1    209.125.127.3      1
      72.5.77.145  255.255.255.255    209.125.127.1    209.125.127.3      1
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
       192.5.6.32  255.255.255.255    209.125.127.1    209.125.127.3      1
    192.175.48.42  255.255.255.255    209.125.127.1    209.125.127.3      1
   192.203.230.10  255.255.255.255    209.125.127.1    209.125.127.3      1
    192.228.91.19  255.255.255.255    209.125.127.1    209.125.127.3      1
    195.60.159.12  255.255.255.255    209.125.127.1    209.125.127.3      1
     207.20.85.66  255.255.255.255    209.125.127.1    209.125.127.3      1
    209.125.127.0  255.255.255.192    209.125.127.3    209.125.127.3     10
    209.125.127.3  255.255.255.255        127.0.0.1        127.0.0.1     10
  209.125.127.253  255.255.255.255    209.125.127.1    209.125.127.3      1
  209.125.127.255  255.255.255.255    209.125.127.3    209.125.127.3     10
      209.244.0.1  255.255.255.255    209.125.127.1    209.125.127.3      1
     216.177.32.3  255.255.255.255    209.125.127.1    209.125.127.3      1
     216.217.22.3  255.255.255.255    209.125.127.1    209.125.127.3      1
    216.239.32.10  255.255.255.255    209.125.127.1    209.125.127.3      1
        224.0.0.0        240.0.0.0    209.125.127.3    209.125.127.3     10
  255.255.255.255  255.255.255.255    209.125.127.3    209.125.127.3      1
Default Gateway:     209.125.127.9
===========================================================================
Persistent Routes:
  None
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

New Server 172.16.200.2  was moved from behind Router R2 f0/1 to behind router R1 int f/01 and has now address 172.16.100.2. But we want users still to be able to connected to it by old IP. How to do it ? We can used destination NAT (DNAT).  In DNAT…
Hello , This is a short article on how would you go about enabling traceoptions on a Juniper router . Traceoptions are similar to Cisco debug commands but these traceoptions are implemented in Juniper networks router . The following demonstr…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now