[c-nsp] Small routing issue
Matlock, Kenneth L
MatlockK at exempla.org
Mon Feb 23 18:04:47 EST 2009
The F0/0 interface on the 2651 is configured for 198.70.224.117/30, yet
you're routing 198.70.33.176/29 to them. Is there NAT'ing going on, or
did I miss something?
Ken Matlock
Network Analyst
Exempla Healthcare
(303) 467-4671
matlockk at exempla.org
-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Todd Shipway
Sent: Monday, February 23, 2009 2:07 PM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] Small routing issue
I'm working on a small issue that I just can't track down. The
connection is 2 T1's bonded in a multilink interface. Connection within
the core network is fine from the remote end, but the traffic will not
make it to the default route on the core 7513.
Hundreds of other connections are setup absolutely identical and work
fine. Default route is fine and debugging doesn't show anything at all.
Config is below:
7513 (Core)
interface Multilink68
ip address 10.10.58.1 255.255.255.252
ppp chap hostname group68
ppp multilink
ppp multilink fragment disable
ppp multilink group 68
interface Serial9/0/0:1
no ip address
encapsulation ppp
ppp chap hostname group68
ppp multilink
ppp multilink group 68
!
interface Serial9/0/0:2
no ip address
no ip unreachables
encapsulation ppp
ppp chap hostname group68
ppp multilink
ppp multilink group 68
ip route 198.70.33.176 255.255.255.248 10.10.58.2
2651 (Remote End)
interface Multilink68
ip address 10.10.58.2 255.255.255.252
ppp chap hostname group68
ppp multilink
ppp multilink fragment disable
ppp multilink group 68
!
interface FastEthernet0/0
ip address 198.70.224.117 255.255.255.252
duplex auto
speed auto
!
interface Serial0/0
bandwidth 1540
no ip address
encapsulation ppp
fair-queue
ppp chap hostname group68
ppp multilink
ppp multilink group 68
interface Serial0/1
bandwidth 1540
no ip address
encapsulation ppp
ppp chap hostname group68
ppp multilink
ppp multilink group 68
ip route 0.0.0.0 0.0.0.0 Multilink68
#ping 10.10.53.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.53.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms
ping 74.125.45.100
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 74.125.45.100, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
trace 74.125.45.100
Type escape sequence to abort.
Tracing the route to yx-in-f100.google.com (74.125.45.100)
1 10.10.58.1 4 msec 4 msec 4 msec
2 * * *
'debug ip icmp' shows nothing on 10.10.58.1 when pinging outside.
Core network is 10.10.x.x and remote end can ping anything within the
core network or anything within our infrastructure. Will not ping
anything outside the network. Seems like a routing issue, but I can't
seem to track it down. Any idea as to what to look for or how to
pinpoint a deeper routing issue?
Any help would be appreciated.
-Todd
More information about the cisco-nsp
mailing list