[69245] in North American Network Operators' Group
Re: MLPPP Follow Up - How we fixed the problem
daemon@ATHENA.MIT.EDU (jlewis@lewis.org)
Wed Mar 31 23:29:21 2004
Date: Wed, 31 Mar 2004 23:28:34 -0500 (EST)
From: jlewis@lewis.org
To: "Mark E. Mallett" <mem@mv.mv.com>
Cc: "Richard J. Sears" <rsears@adnc.com>,
nanog list <nanog@merit.edu>
In-Reply-To: <20040331211208.GG12478@iridium.mv.net>
Errors-To: owner-nanog-outgoing@merit.edu
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 it will not work (or
> > at least it did not for us).
>
> FWIW I have also observed that it is necessary to specify the
> interface when doing per-packet load balancing across multiple PVCs,
> e.g. as when doing load balancing across multiple DSL circuits. I
I've done lots of this (with clear T1's, no frame or DSL), and never run
into that issue on 3640, 7206, 7500 series routers.
----------------------------------------------------------------------
Jon Lewis *jlewis@lewis.org*| I route
Senior Network Engineer | therefore you are
Atlantic Net |
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
