Enabling Service Packages

For AS PICs, MultiServices PICs, and the internal Adaptive Services Module (ASM) in the M7i platform, there are two service packages: Layer 2 and Layer 3. Both service packages are supported on all adaptive services interfaces, but you can enable only one service package per PIC, with the exception of a combined package supported on the ASM. On a single routing platform, you can enable both service packages by installing two or more PICs on the platform.

Note: Graceful Routing Engine switchover (GRES) is automatically enabled on all services PICs and DPCs except the ES PIC. It is supported on all M-series and T-series platforms except for TX Matrix installations. Layer 3 services should retain state after switchover, but Layer 2 services will restart. For IPsec services, Internet Key Exchange (IKE) negotiations are not stored and must be restarted after switchover. For more information about GRES, see the JUNOS High Availability Configuration Guide.

You enable service packages per PIC, not per port. For example, if you configure the Layer 2 service package, the entire PIC uses the configured package. To enable a service package, include the service-package statement at the [edit chassis fpc slot-number pic pic-number adaptive-services] hierarchy level, and specify layer-2 or layer-3:

To determine which package an AS PIC supports, issue the show chassis hardware command: if the PIC supports the Layer 2 package, it is listed as Link Services II, and if it supports the Layer 3 package, it is listed as Adaptive Services II. To determine which package a MultiServices PIC supports, issue the show chassis pic fpc-slot slot-number pic-slot slot-number command. The Package field displays the value Layer-2 or Layer-3.

Note: The ASM has a default option (layer-2-3) that combines the features available in the Layer 2 and Layer 3 service packages.

After you commit a change in the service package, the PIC is taken offline and then brought back online immediately. You do not need to manually take the PIC offline and online.

Note: Changing the service package causes all state information associated with the previous service package to be lost. You should change the service package only when there is no active traffic going to the PIC.

The services supported in each package differ by PIC and platform type. Table 4 lists the services supported within each service package for each PIC and platform. Some of these services are also available on J-series Services Routers, but they are implemented in a different way and do not use the Layer 2 and Layer 3 service packages. For more information, see the J-series Services Router Advanced WAN Access Configuration Guide.

On the AS and MultiServices PICs, link services support includes JUNOS software CoS components, LFI (FRF.12), MLFR end-to-end (FRF.15), MLFR UNI NNI (FRF.16), MLPPP (RFC 1990), and multiclass MLPPP. For more information, see Layer 2 Service Package Capabilities and Interfaces and Link Services IQ Interfaces Configuration Guidelines.

Note: The AS PIC II for Layer 2 Service is dedicated to supporting the Layer 2 service package only.

For additional information about Layer 3 services, see the JUNOS Feature Guide.

Table 4: AS and MultiServices PIC Services by Service Package, PIC, and Platform

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:

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 4.

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 sp is created because it is needed by the JUNOS software. For the Layer 2 service package, the sp interface is not configurable, but you should not disable it.