On Thu, 1 Apr 2004, Paul Stewart wrote:
> Any issues with more than 2 connections? We have a customer that we are
> doing this for right now with two T1's.. Customer wants a third one
> possibly.. Can't see a problem but thought I'd ask...
>
> How many could you theoretically do if you really ha
On Wed, 31 Mar 2004, Mark E. Mallett wrote:
> > ip route X.X.X.X 255.255.255.252 Serial1/0/0/13:0
> > ip route X.X.X.X 255.255.255.252 Serial2/1/0/14:0
> >
> >
> > The only problem that we ran into was that we had to use the Serial designator
> > of the interface in our route statement otherwise
On Wed, Mar 31, 2004 at 01:45:47PM -0800, Bruce Robertson wrote:
> > FWIW I have also observed that it is necessary to specify the
> > interface when doing per-packet load balancing across multiple PVCs,
>
> H... we're not having this trouble. What are you using to propagate
> your loopback
> FWIW I have also observed that it is necessary to specify the
> interface when doing per-packet load balancing across multiple PVCs,
H... we're not having this trouble. What are you using to propagate
your loopback interfaces? It works just fine with OSPF.
--
Bruce Robertson, President/C
On Tue, Mar 30, 2004 at 12:36:37PM -0800, Richard J. Sears wrote:
> I asked the group some time ago about some problems we were seeing with
> MLPPP on our Cisco 7513s.
...
>
> ip route X.X.X.X 255.255.255.252 Serial1/0/0/13:0
> ip route X.X.X.X 255.255.255.252 Serial2/1/0/14:0
>
>
> The onl
I asked the group some time ago about some problems we were seeing with
MLPPP on our Cisco 7513s.
I have had 5 or 6 people contact me off list to ask how we solved the
problem, so I figured I would post "our" solution to the group. I am
sure there may be other fixes, however this works great for
