Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Enabling Service Packages

 

For AS PICs, Multiservices PICs, Multiservices DPCs, and the internal Adaptive Services Module (ASM) in the M7i router, 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 router, 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, MX Series, and T Series routers except for TX Matrix routers. 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 High Availability Feature 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 1 lists the services supported within each service package for each PIC and platform.

On the AS and Multiservices PICs, link services support includes Junos OS 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 Layer 2 Service Package Capabilities and Interfaces.

Note

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

Table 1: AS and Multiservices PIC Services by Service Package, PIC, and Platform

Services

ASM

AS/AS2 PICs and Multiservices PICs

AS/AS2 and Multiservices PICs

AS2 and Multiservices PICs

AS2 and Multiservices PICs

Layer 2 Service Package (Only)M7iM7i, M10i, and M20M40e and M120M320, T320, and T640TX Matrix

Link Services:

     
  • Link services

Yes

Yes

Yes

Yes

No

  • Multiclass MLPPP

Yes

Yes

Yes

Yes

No

Voice Services:

     
  • CRTP and LFI

Yes

Yes

Yes

Yes

No

  • CRTP and MLPPP

Yes

Yes

Yes

Yes

No

  • CRTP over PPP (without MLPPP)

Yes

Yes

Yes

Yes

No

Layer 3 Service Package (Only)M7iM7i, M10i, and M20M40e and M120M320, T320, and T640TX Matrix

Security Services:

     
  • CoS

Yes

Yes

Yes

Yes

No

  • Intrusion detection system (IDS)

Yes

Yes

Yes

Yes

No

  • IPsec

Yes

Yes

Yes

Yes

No

  • NAT

Yes

Yes

Yes

Yes

No

  • Stateful firewall

Yes

Yes

Yes

Yes

No

Accounting Services:

     
  • Active monitoring

Yes

Yes

Yes

Yes

Yes

  • Dynamic flow capture (Multiservices 400 PIC only)

No

No

No

Yes

No

  • Flow-tap

Yes

Yes

Yes (M40e only)

Yes

No

  • Passive monitoring (Multiservices 400 PIC only)

No

Yes

Yes (M40e only)

Yes

No

  • Port mirroring

Yes

Yes

Yes

Yes

Yes

LNS Services:

     
  • L2TP LNS

Yes

Yes (M7i and M10i only)

Yes (M120 only)

No

No

Voice Services:

     
  • BGF

Yes

Yes

Yes

Yes

No

Layer 2 and Layer 3 Service Package (Common Features)M7iM7i, M10i, and M20M40e and M120M320, T320, and T640TX Matrix

RPM Services:

     
  • RPM probe timestamping

Yes

Yes

Yes

Yes

No

Tunnel Services:

     
  • GRE (gr-fpc/pic/port)

Yes

Yes

Yes

Yes

Yes

  • GRE fragmentation (clear-dont-fragment-bit)

Yes

Yes

Yes

No

No

  • GRE key

Yes

Yes

Yes

Yes

No

  • IP-IP tunnels (ip-fpc/pic/port)

Yes

Yes

Yes

Yes

Yes

  • Logical tunnels (lt-fpc/pic/port)

No

No

No

No

No

  • Multicast tunnels (mt-fpc/pic/port)

Yes

Yes

Yes

Yes

Yes

  • PIM de-encapsulation (pd-fpc/pic/port)

Yes

Yes

Yes

Yes

Yes

  • PIM encapsulation (pe-fpc/pic/port)

Yes

Yes

Yes

Yes

Yes

  • Virtual tunnels (vt-fpc/pic/port)

Yes

Yes

Yes

Yes

Yes

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—Layer 2 Service Package Capabilities and Interfaces describes how the Junos CoS components work on link services IQ (lsq) interfaces. For detailed information about Junos CoS components, see the Class of Service Feature Guide (Routers and EX9200 Switches).

  • 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)

  • MLFR end-to-end (FRF.15)

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

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 Layer 2 Service Package Capabilities and Interfaces and Link and Multilink Services Interfaces Feature Guide for Routing Devices.

Note

Interface type sp is created because it is needed by the Junos OS. For the Layer 2 service package, the sp interface is not configurable, but you should not disable it.