[88797] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: MLPPP over MPLS

daemon@ATHENA.MIT.EDU (Brent A O'Keeffe)
Mon Feb 20 08:57:25 2006

In-Reply-To: <Pine.LNX.4.61.0602171529050.1846@soloth.lewis.org>
To: Jon Lewis <jlewis@lewis.org>
Cc: "Jon R. Kibler" <Jon.Kibler@aset.com>, nanog@merit.net
From: "Brent A O'Keeffe" <bokeeffe@csc.com>
Date: Mon, 20 Feb 2006 08:56:47 -0500
Errors-To: owner-nanog@merit.edu


This is a multipart message in MIME format.
--=_alternative 004C9AA98525711B_=
Content-Type: text/plain; charset="US-ASCII"

It may also be worth noting that if the provider is running Juniper and 
not Cisco, there are fragmentation issues with certain versions of Juniper 
code.  The MLPPP session cannot agree on an MTU and usually stop somewhere 
around 100 bytes if they do.  The workaround is to implement "ppp 
multilink fragment disable" on the Cisco Multilink interface.

Brent



Jon Lewis <jlewis@lewis.org> 
Sent by: owner-nanog@merit.edu
02/17/2006 03:38 PM

To
"Jon R. Kibler" <Jon.Kibler@aset.com>
cc
nanog@merit.net
Subject
Re: MLPPP over MPLS







On Fri, 17 Feb 2006, Jon R. Kibler wrote:

> We have a customer that is implementing an MPLS network that will have 2 

> to 6 T1 feeds at some locations that will be using MLPPP for channel 
> bonding. This is a telco provided network that will be customer managed.

It's not clear from your message, but I'm assuming the MLPPP will be from 
PE to CE and that the MPLS you speak of is MPLS VPN.  If that's the case, 
on the customer end, it's just a MLPPP, and on your end, it's an MLPPP 
with an "ip vrf forwarding foo" statement.  It's probably more than the 
average CCNA can handle (but so are MLPPP, MPLS, and most day to day IOS 
config work).  Anyone who actually uses IOS on a regular basis (as opposed 

to someone who crammed for an exam and knows squat) should have no trouble 

with it.

> The customer is being told by their router vendor that an MLPPP/MPLS 
> network is 'too complex' to be managed by anyone except for the router 
> vendor's VARs or the telco. They indicated that it would be impossible 
> for the customer's router vendor certified network person to come up to 
> speed on MLPPP/MPLS configurations and manage such a network -- that it 
> takes years to adequately learn how to manage that type of network 
> configuration.

I think someone may be confusing "providing MPLS service" with "buying 
MPLS service".  A customer buying MPLS VPN service never sees any of the 
MPLS tags or messes with MPLS/tag-switching commands.  There is no added 
complexity...or at least there doesn't need to be any.

> ==================================================
> Filtered by: TRUSTEM.COM's Email Filtering Service
> http://www.trustem.com/
> No Spam. No Viruses. Just Good Clean Email.


Virus-free, because I say it is...and I run Pine on Linux :)

----------------------------------------------------------------------
  Jon Lewis                   |  I route
  Senior Network Engineer     |  therefore you are
  Atlantic Net                |
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________


--=_alternative 004C9AA98525711B_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">It may also be worth noting that if
the provider is running Juniper and not Cisco, there are fragmentation
issues with certain versions of Juniper code. &nbsp;The MLPPP session cannot
agree on an MTU and usually stop somewhere around 100 bytes if they do.
&nbsp;The workaround is to implement &quot;ppp multilink fragment disable&quot;
on the Cisco Multilink interface.</font>
<br>
<br><font size=2 face="sans-serif">Brent</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Jon Lewis &lt;jlewis@lewis.org&gt;</b>
</font>
<br><font size=1 face="sans-serif">Sent by: owner-nanog@merit.edu</font>
<p><font size=1 face="sans-serif">02/17/2006 03:38 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">&quot;Jon R. Kibler&quot; &lt;Jon.Kibler@aset.com&gt;</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">nanog@merit.net</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: MLPPP over MPLS</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt><br>
On Fri, 17 Feb 2006, Jon R. Kibler wrote:<br>
<br>
&gt; We have a customer that is implementing an MPLS network that will
have 2 <br>
&gt; to 6 T1 feeds at some locations that will be using MLPPP for channel
<br>
&gt; bonding. This is a telco provided network that will be customer managed.<br>
<br>
It's not clear from your message, but I'm assuming the MLPPP will be from
<br>
PE to CE and that the MPLS you speak of is MPLS VPN. &nbsp;If that's the
case, <br>
on the customer end, it's just a MLPPP, and on your end, it's an MLPPP
<br>
with an &quot;ip vrf forwarding foo&quot; statement. &nbsp;It's probably
more than the <br>
average CCNA can handle (but so are MLPPP, MPLS, and most day to day IOS
<br>
config work). &nbsp;Anyone who actually uses IOS on a regular basis (as
opposed <br>
to someone who crammed for an exam and knows squat) should have no trouble
<br>
with it.<br>
<br>
&gt; The customer is being told by their router vendor that an MLPPP/MPLS
<br>
&gt; network is 'too complex' to be managed by anyone except for the router
<br>
&gt; vendor's VARs or the telco. They indicated that it would be impossible
<br>
&gt; for the customer's router vendor certified network person to come
up to <br>
&gt; speed on MLPPP/MPLS configurations and manage such a network -- that
it <br>
&gt; takes years to adequately learn how to manage that type of network
<br>
&gt; configuration.<br>
<br>
I think someone may be confusing &quot;providing MPLS service&quot; with
&quot;buying <br>
MPLS service&quot;. &nbsp;A customer buying MPLS VPN service never sees
any of the <br>
MPLS tags or messes with MPLS/tag-switching commands. &nbsp;There is no
added <br>
complexity...or at least there doesn't need to be any.<br>
<br>
&gt; ==================================================<br>
&gt; Filtered by: TRUSTEM.COM's Email Filtering Service<br>
&gt; http://www.trustem.com/<br>
&gt; No Spam. No Viruses. Just Good Clean Email.<br>
<br>
<br>
Virus-free, because I say it is...and I run Pine on Linux :)<br>
<br>
----------------------------------------------------------------------<br>
 &nbsp;Jon Lewis &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; | &nbsp;I route<br>
 &nbsp;Senior Network Engineer &nbsp; &nbsp; | &nbsp;therefore you are<br>
 &nbsp;Atlantic Net &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|<br>
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________<br>
</tt></font>
<br>
--=_alternative 004C9AA98525711B_=--

home help back first fref pref prev next nref lref last post