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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cisco 2800 - Routing Issue

Status
Not open for further replies.

SEMSD

Technical User
Joined
Apr 19, 2005
Messages
10
Location
US
OK, I am stumped and humbly looking for a little help. I have 2 2800's connected via T-1's using PPP multilink. The Network I am having the issue with is 172.16.0.0/16. The default gateway for nodes on this network is 172.16.1.1 (Checkpoint Firewall). The LAN interface on the 2800 is 172.16.1.100. The Checkpoint firewall has a static route and routes traffic just fine...all nodes can ping the far end of the PPP Multilink connection (192.168.2.0/24).

The nodes on the 192.168.2.0 network cannot ping nodes on 172.16.0.0 unless the node on 172.16.0.0 has a static route defined for the 192.168.2.0 network.

With my troubleshooting steps I have established that tracert's from 192.168.2.0 timeout at the PPP Multilink interface on the router connected to 172.16.0.0. In addition, doing a "Ping IP" from the multilink interface 192.168.0.5 on the router directly connected to 172.16.0.0 fails. Obviously, I am missing something!


The following is the relevant info from my config and I appreciate any/all help in advance.

interface Multilink1
bandwidth 3088
ip address 192.168.0.5 255.255.255.0
ip nbar protocol-discovery
service-policy output SDM-Pol-Multilink1
ip route-cache flow
ppp multilink
ppp multilink group 1
!
interface FastEthernet0/0
description $ETH-SW-LAUNCH$$INTF-INFO-FE 0/0$$ETH-LAN$
ip address 172.16.1.100 255.255.0.0
ip route-cache flow
duplex auto
speed auto
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0
no ip address
ip nbar protocol-discovery
service-policy output SDM-Pol-Serial0/0/0
encapsulation ppp
ip route-cache flow
service-module t1 clock source internal
ppp multilink
ppp multilink group 1
!
interface Serial0/1/0
no ip address
encapsulation ppp
service-module t1 clock source internal
ppp multilink
ppp multilink group 1
!
router rip
network 172.16.0.0
network 192.168.0.0
no auto-summary
!
ip classless
ip route 0.0.0.0 0.0.0.0 FastEthernet0/0
ip route 10.1.1.0 255.255.255.0 172.16.1.1



Gateway of last resort is 0.0.0.0 to network 0.0.0.0

C 172.16.0.0/16 is directly connected, FastEthernet0/0
R 192.168.200.0/24 [120/2] via 192.168.0.6, 00:00:08, Multilink1
10.0.0.0/24 is subnetted, 1 subnets
S 10.1.1.0 [1/0] via 172.16.1.1
192.168.0.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.0.0/24 is directly connected, Multilink1
C 192.168.0.6/32 is directly connected, Multilink1
R 192.168.2.0/24 [120/1] via 192.168.0.6, 00:00:08, Multilink1
S* 0.0.0.0/0 is directly connected, FastEthernet0/0
 
The first thing I need to understand is when you say the nodes default gateway is the pix , you mean the nic card gateway , if so this should always be the router interface address 172.16.1.100 . If rip is working correctly you shouldn't need any kind of static routes except the default static route 0.0.0.0 . The ping responses may be goofed up if the users gateway is pointed at the pix , point them at the router interface and recheck . The router is doing the routing not the checkpoint so that may be screwing things up . If this aasumption is incorrect let us know and we can work from there . Probably the equivalent info from the far end would also help for further troubleshooting.
 
Always include a topology diagram with these sort of questions please. thanks.

Burt
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top