Well, it turns out that you need ppp multilink fragment delay 500 on the Cisco side to keep mutilink negotiation alive, otherwise the Cisco switches to non-ML PPP when only one T1 is up, while Juniper does not...
Michael Wilson brought this to my attention, and the juniper manual also shows it :) Ebben Aries [EMAIL PROTECTED] wrote: > I am running the same scenario terminating on a P-AS in L2 mode and have not > had any problems regarding the bundle going down if only 1 member T1 goes > down. > > By default, only 1 link needs to be up for the bundle to be labeled as up. > The amount of minimum links however is a configurable option. > > http://www.juniper.net/techpubs/software/junos/junos82/swconfig82-services/html/link-services-config10.html > > Do you have a copy of your mlppp config ? _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
