Mike,
I too, have two bundled T1 circuits on a point-2-point network with MLP enabled. Things work just fine in the event one of the T1 circuits goes down. One trick in our scenario with the clocking is, since we have a point-2-point environment, the carrier is not providing the clocking so one router on one end of the bundle is providing clocking.
Here is a sample config:
RouterA:
interface Multilink1
description mu1:T1_Bundle
ip address 10.99.0.2 255.255.255.252
ip access-group 2001 in
no ip redirects
no ip unreachables
no ip proxy-arp
fair-queue 1024 256 64
ppp multilink
ppp multilink interleave
multilink-group 1
!
interface Serial0/0
description s0/0:T1_Circuit_ID
no ip address
encapsulation ppp
ip route-cache flow
no fair-queue
ppp multilink
multilink-group 1
!
interface Serial0/1
description s0/1:T1_Circuit_ID
no ip address
encapsulation ppp
ip route-cache flow
no fair-queue
ppp multilink
multilink-group 1
RouterB:
interface Multilink1
description mu1:T1_Bundle
ip address 10.99.0.1 255.255.255.252
no ip redirects
no ip unreachables
no ip proxy-arp
fair-queue 1024 256 64
ppp multilink
ppp multilink interleave
multilink-group 1
!
interface Serial0/0
description s0/0:T1_Circuit_ID
no ip address
encapsulation ppp
ip route-cache flow
no fair-queue
service-module t1 clock source internal
ppp multilink
multilink-group 1
!
interface Serial0/1
description s0/1:T1_Circuit_ID
no ip address
encapsulation ppp
ip route-cache flow
no fair-queue
service-module t1 clock source internal
ppp multilink
multilink-group 1
As you can see from the config, RouterB is providing the clocking for both T1 circuits. If one T1 fails, the remaining circuit in the bundle carries the load.
Hope this helps.
-m2
