Layer 2 Service Package Capabilities and Interfaces
When you enable the Layer 2 service package, you can configure link services. On the AS and MultiServices PICs and the ASM, link services include support for the following:
- JUNOS CoS components—Link Services IQ Interfaces Configuration Guidelines describes how the JUNOS CoS components work on link services IQ (
lsq) interfaces. For detailed information about JUNOS CoS components, see the JUNOS Class of Service Configuration Guide. - LFI on Frame Relay links using FRF.12 end-to-end fragmentation—The standard for FRF.12 is defined in the specification FRF.12, Frame Relay Fragmentation Implementation Agreement.
- LFI on MLPPP links.
- MLFR UNI NNI (FRF.16)—The standard for FRF.16 is defined in the specification FRF.16.1, Multilink Frame Relay UNI/NNI Implementation Agreement.
- MLPPP (RFC 1990)
For the LSQ interface on the AS and MultiServices PICs, the configuration syntax is almost the same as for Multilink and Link Services PICs. The primary difference is the use of the interface-type descriptor lsq instead of ml or ls. When you enable the Layer 2 service package, the following interfaces are automatically created:
gr-fpc/pic/port
ip-fpc/pic/port
lsq-fpc/pic/port
lsq-fpc/pic/port:0
...
lsq-fpc/pic/port:N
mt-fpc/pic/port
pd-fpc/pic/port
pe-fpc/pic/port
sp-fpc/pic/port
vt-fpc/pic/port
Interface types gr, ip, mt, pd, pe, and vt are standard tunnel interfaces that are available on the AS and MultiServices PICs whether you enable the Layer 2 or the Layer 3 service package. These tunnel interfaces function the same way for both service packages, except that the Layer 2 service package does not support some tunnel functions, as shown in Table 5.
Interface type lsq-fpc/pic/port is the physical link services IQ (lsq) interface. Interface types lsq-fpc/pic/port:0 through lsq-fpc/pic/port:N represent FRF.16 bundles. These interface types are created when you include the mlfr-uni-nni-bundles statement at the [edit chassis fpc slot-number pic pic-number] option. For more information, see Link Services IQ Interfaces Configuration Guidelines and Link and Multilink Services Configuration Guidelines.
 |
NOTE: Interface type |