[j-nsp] SRX for MPLS

Giuliano Cardozo Medalha giulianocm at uol.com.br
Fri Oct 22 10:25:40 EDT 2010


We are studying it:

    * J Series or SRX Series devices do not support aggregated Ethernet
      interfaces. Therefore, aggregated Ethernet interfaces between CE
      devices and PE routers are not supported for VPLS routing
      instances on J Series or SRX Series devices.
    * VPLS routing instances on J Series or SRX Series devices use BGP
      to send signals to other PE routers. LDP signaling is not supported.
    * VPLS multihoming, which allows connecting a CE device to multiple
      PE routers to provide redundant connectivity, is not supported on
      J Series or SRX Series devices.
    * J Series or SRX Series devices do not support BGP mesh groups.
    * J Series or SRX Series devices support only the following
      encapsulation types on VPLS interfaces that face CE devices:
      extended VLAN VPLS, Ethernet VPLS, and VLAN VPLS. Ethernet VPLS
      over ATM LLC encapsulation is not supported.
    * Virtual ports are generated dynamically on a Tunnel Services PIC
      on some Juniper Networks routing platforms. J Series or SRX Series
      devices do not support Tunnel Services modules or virtual ports.
    * The VPLS implementation on J Series or SRX Series devices does not
      support dual-tagged frames. Therefore, VLAN rewrite operations are
      not supported on dual-tagged frames. VLAN rewrite operations such
      as pop-pop, pop-swap, push-push, swap-push, and swap-swap, which
      are supported on M Series and T Series routing platforms, are not
      supported on J Series or SRX Series devices.
    * Firewall filters for VPLS are not supported.



BGP Signaling must be a big limitation, because of address space of this 
boxes.


More information about the juniper-nsp mailing list