[c-nsp] mpls label stack limit ???

[Amos Thong]

Hi James, 
 
Adding on to Mark's comment, we have one MX480 running Junos 10.4R4.5 which has been generating this error below but there has been no service affected. 
-------------------------------------
Feb 21 23:07:36.670 2013  er-01-xxxx-re0 rpd[1457]: %DAEMON-3-RPD_MPLS_INTF_MAX_LABELS_ERROR: Maximum labels exceeded - failed to stack additional label to nexthop on interface xe-0/0/0.0
-------------------------------------
 
That prompted us to check the Junos release note to see if there is a known bug and here is what we found : 
11.2 and 12.1 release note
-------------------------------
RPD_MPLS_INTF_MAX_LABELS_ERROR can be seen in log messages even if the
maximum-labels option is configured under "family mpls". [PR/734680: This issue
has been resolved.]
 
We hope this helps. 
 
Regards
Amos


 

> Date: Sat, 6 Oct 2012 14:24:13 -0400
> From: james at freedomnet.co.nz
> To: mark.tinka at seacom.mu
> CC: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] mpls label stack limit ???
> 
> @Adam and @Mike What versions of Junos have you seen the limitations?
> 
> -James
> 
> On Sat, Oct 6, 2012 at 2:01 PM, Mark Tinka <mark.tinka at seacom.mu> wrote:
> 
> > On Wednesday, September 05, 2012 07:20:26 AM Oliver Boehmer
> > (oboehmer) wrote:
> >
> > > There is a limit how far an LSR can peek into the frame
> > > for loadsharing hash decisions (I recall 10 labels deep
> > > on the CRS). Other than that, the MTU is the limit.
> > >
> > > CRS can push a max of 7 labels onto the stack, ASR9k does
> > > 6.. Don't think there is any use-case (yet?) that would
> > > need to push that many labels.
> >
> > The OP is right, I have seen Juniper routers (both MX- and
> > M-series) log error messages in certain scenarios,
> > particularly if the stack was larger than 3 labels, if my
> > memory is anything to go by. This was Junos 10.4R4.5.
> >
> > In my case, that log was on the back of an NG-MVPN
> > deployment, and only participating routers logged the issue.
> > That said, the log never resulted in any service issues. It
> > appeared while were troubleshooting something else.
> >
> > Mark.
> >
> > _______________________________________________
> > cisco-nsp mailing list cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/