cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
227
Views
0
Helpful
2
Replies

routing issue with PPP multilink on 7513

amin.amor
Level 1
Level 1

Dear all,

I'm having the following problen when I configured 7513 for E1 multilink (2xE1); first in order to ping the P2P interface I need to disable route-cache

(no ip route-cache distributed) under both serail interfaces.

When I add this command I can ping the other side only from the directly connected router. All the others routers on the network can't access the other router on the other side.

interface Serial5/0/5:0

description * Uplink

no ip address

no ip directed-broadcast

encapsulation ppp

no ip route-cache distributed

no fair-queue

no cdp enable

ppp multilink

multilink-group 1

=================

interface Serial5/0/4:0

description * Uplink

no ip address

no ip directed-broadcast

encapsulation ppp

no ip route-cache distributed

no fair-queue

no cdp enable

ppp multilink

multilink-group 1

========================

interface Multilink1

description *

ip address 10.10.10.1 255.255.255.252

no ip directed-broadcast

no ip route-cache cef

no ip route-cache

load-interval 30

no cdp enable

ppp multilink

no ppp multilink fragmentation

multilink-group 1

same config on the other side.

Please note that the following two line below (under multilink interface) are added by default when you add no ip route-cache distributed (under the serial interfaces)

no ip route-cache cef

no ip route-cache

Routing part

Routing entry for 10.10.10.10/32

Known via "isis", distance 115, metric 50, type level-2

Redistributing via isis

Last update from 10.10.10.1on GigabitEthernet3/0/0, 01:48:30 ago

The ISIS is able to redistribute the the route to the other peers, but the peer is not able to ping this network. Default route is also defined on the customer network.

Thanks

Your network partner in Luxembourg
http://www.itnet.lu
2 Replies 2

mljohnson
Level 4
Level 4

Not sure I understand why the update from 10.10.10.1 was on a G-Ether; you should have seen the IP address of the G-Ether, instead. If you can ping point-to-point, then the MPPP stuff must be OK; so I'd focus on the routing. Using either the trace command or "sh ip route", you can see what the problem might be at each hop beyond the directly connected PPP device.

The problem was IOS bug. CEF and MLPPP is not working properly,

the routing is ok. check this out CSCdy43576 this is a new bug sep02.

Your network partner in Luxembourg
http://www.itnet.lu