Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Point to Point T1 with Cisco 1721

Status
Not open for further replies.

ReklesAbandon

IS-IT--Management
Joined
Dec 12, 2003
Messages
3
Location
US
I am trying to connect to locations via a dedicated T1 using two Cisco 1721 routers with T1 WICs installed. I have gotten to th epoint where I can ping the remote router from either location(i.e. can ping routerA from LocationB and vice-versa) but I can not ping any ip on the other side. Here are the configs I am working with...

[/b]RouterA[/b]
ip subnet-zero
!
interface FastEthernet0
ip address 192.168.101.90 255.255.255.0
speed auto
no keepalive
!
interface Serial0
ip unnumbered FastEthernet0
no fair-queue
service-module t1 remote-alarm-enable
!
router rip
version 2
network 192.168.101.0
no auto-summary
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.101.1
ip route 192.168.195.0 255.255.255.0 192.168.195.252



[/b]RouterB[/b]
ip subnet-zero
!
interface FastEthernet0
ip address 192.168.195.252 255.255.255.0
speed auto
no keepalive
!
interface Serial0
ip unnumbered FastEthernet0
no fair-queue
service-module t1 remote-alarm-enable
!
router rip
version 2
network 192.168.195.0
no auto-summary
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.195.252
ip route 192.168.101.0 255.255.255.0 192.168.101.90

With this config I can ping 192.168.101.90 from the 192.168.195.0 network, but I can not see any other ip on the 192.168.101.0 network (i.e. 192.168.101.70).

Must be something basic, but I am too new to this. Thanks in advance for your help...

 
On Router A you have:
ip route 0.0.0.0 0.0.0.0 192.168.101.1
This statement says to the router if any traffic comes in and it doesn't know what to do with it send it to the interface 192.168.101.1. Where is that interface 192.168.101.1?
Try taking the static routing statements off of both routers.
ip route 0.0.0.0 0.0.0.0 192.168.101.1
ip route 192.168.195.0 255.255.255.0 192.168.195.252

You have rip. That might take care of your routing. If you are going out to the Internet, then put in a default route.
ip route 0.0.0.0 0.0.0.0 204.17.98.80 where 204.17.98.80 is the address of the interface the traffic should be routed out of(statement and ip should be on the same router).
 
Thx for your response.

192.168.101.1 is the current default gateway for the network (The inside interface on the firewall). I figured all packets should go there if the router does not know what to do with them.

I do not understand you other comment. can you clarify for a newbie?

 
What he is saying is that RIP should take care of your routing so that you don't need that 2nd static route , that is what a routing protocol is for . It's possible that RIP is not actually working , coming from an OSPF environment I'm not real familiar with RIP , but you need to verify that rip is indeed working correctly . Do a show ip route and see if you can see routes on the other side of the connections , if it's working correctly you should , if not you will need to troubleshoot that problem . Make sure you interfaces are not passive , some of the newer ios's use passive as default and as such routing updates will not be sent out that interface .


 
Since these are point-to-point circuit, why don't you put a /30 subnet on the serial interface and get rid of the ip unnumbered. Makes life easier plus, if needed, you can snmp the interface and run certain exec commands.

I would make sure that the default gateway on the clients are correct. How are the serial interfaces configured? Clock source, encapsulation?? Post your show interface.

On router B, you have a default route to 195.252. That should be pointing to the other router.
 
first off the /30 is not the answer.
It is indeed a preference, but a not needed step in configuring this protocol.

The static routes are wrong as indicated. In order to make sure packets are sent out of your router you need to indicate the "door" out, for example:
192.168.195.252 is your fa IP
If traffic is to go out this interface then you need to specify the IP, or in a more simple form create the static route like this

ip route 0.0.0.0 0.0.0.0 FastEthernet 0

This is telling the traffic that all traffic is to be sent through the outbound interface, in this case is the fastethernet interface.



 
Thanks all for your comments. I had many problems. The biggest of which was that I did not have return routes set properly on the default gateways. After doing this and simplifying a few other routes all is well. Thanks again. I think I have been promoted to Rookie from Newbie.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top