Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Results Summary and Analysis

Known Issues, Limitations, Restrictions, Caveats

  • When implementing VLAN tagging on a Juniper device that uses service provider style interface configuration, you have the option to work with no tag, single tag (including what's known as a priority tag when VID is set to 0), dual tag, or a combination of them on the same interface. If prior to deployment of the port fan-out solution the PE used both outer and inner tags to identify one customer service, ability to work with no more than two VLAN tags on an IFL may be a limiting factor. Note that a frame can carry an arbitrarily deep stack of VLAN tags, a router or a switch is simply oblivious to anything beyond first two levels.
  • OAM state propagation with oam-on-svlan is currently unidirectional, from S-VLAN to C-VLANs (parent IFL to children IFLs). We are working on adding state propagation in C-VLANs to their parent S-VLAN direction in future versions of Junos software.
  • When several MEPs are attached to an IFL, only one should have its action profile configured with interface‑down action, otherwise there will be races, contention and indeterministic results.
  • State propagation like MEP1 ➜ IFL ➜ MEP2 is not possible between multiple MEPs configured on an IFL. Configuration commit fails when you attach more than one MEP with an action profile to an IFL.
  • Neither CFM-driven nor L2 circuit (RPD) driven have any effect on AE interfaces. They only work on non-AE interfaces.