Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All
     

    Related Documentation

     

    Example: Configuring HTTP Redirect Services and Attaching to a Dynamic Interface

    This example shows how to configure HTTP redirect services and attach it to a dynamic interface.

    Requirements

    This example uses the following hardware and software components:

    • MX240, MX480, or MX960 3D Universal Edge Router with a Multiservices Modular PIC Concentrator (MS-MPC) and Multiservices Modular Interfaces Card (MS-MIC) installed.
    • Junos OS Release 15.1 or later.

    Overview

    A dynamic service attachment uses a dynamic profile. To handle scalability more efficiently, this dynamic profile example shows that the name of the service set can be populated dynamically for each subscriber at instantiation time. This dynamic profile encapsulates a service attachment point associated with a statically preprovisioned service set.

    Configuration

    To configure HTTP redirect services and attach it to a dynamic interface, perform these tasks:

    CLI Quick Configuration

    To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, and then copy and paste the commands into the CLI.

    [edit]set chassis fpc 3 pic 0 adaptive-services service-package extension-provider package jservices-cpcdset chassis fpc 3 pic 1 adaptive-services service-package extension-provider package jservices-cpcd
    [edit]edit dynamic-profiles profile prof-2edit interfaces $junos-interface-ifd-name unit $junos-interface-unitset family inet service input service-set set1 service-filter serv-filter1set family inet service output service-set set2 service-filter serv-filter2

    Configuring the Package and Installation for Captive Portal Content Delivery

    Step-by-Step Procedure

    The following example requires that you navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode.

    1. Configure Junos OS to support a service package on an adaptive services interface on an MX Series 3D Universal Edge Router with MS-MPCs/MS-MICs.

      [edit chassis]
      user@host# edit fpc 3 pic 0 adaptive-services service-package extension-provider

    2. Specify the CPCD package for installation on the PIC.

      [edit chassis fpc 3 pic 0 adaptive-services service-package extension-provider]
      user@host# set package jservices-cpcd

      Note: Up to eight packages can be installed on a PIC; however, only one data package can be on a PIC.

    3. Configure a second PIC to support a service package on an adaptive services interface.

      [edit chassis]
      user@host# edit fpc 3 pic 1 adaptive-services service-package extension-provider

    4. Specify the CPCD package for installation on the PIC.

      [edit chassis fpc 3 pic 1 adaptive-services service-package extension-provider]
      user@host# set package jservices-cpcd

    Results

    From configuration mode, confirm your configuration by entering the show configuration chassis command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

    [edit]root@host# show configuration chassis
    fpc 3 {pic 0 {adaptive-services {service-package {extension-provider {package jservices-cpcd;}}}}pic 1 {adaptive-services {service-package {extension-provider {package jservices-cpcd;}}}}}

    If you are done configuring the device, enter commit from configuration mode.

    Configuring an HTTP Redirect Service and Attaching It to a Dynamic Interface

    Step-by-Step Procedure

    The following example requires that you navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode.

    1. Create a dynamic profile to use as the parameterized service attachment.

      [edit]
      user@host# edit dynamic-profiles prof-2

    2. Configure the dynamic interface name using the predefined interface variable.

      [edit dynamic-profiles profile prof-2]
      user@host# set interfaces $junos-interface-ifd-name

    3. Configure the logical unit number using the predefined variable on a dynamic underlying VLAN interface.

      [edit dynamic-profiles profile prof-2 interfaces $junos-interface-ifd-name]
      user@host# set unit $junos-interface-unit

    4. Configure protocol family information for the logical interface.

      [edit dynamic-profiles profile prof-2 interfaces $junos-interface-ifd-name unit $junos-interface-unit]
      user@host# edit family inet

    5. Configure the input service sets and filters to apply to traffic by a dynamic profile.

      [edit dynamic-profiles profile prof-2 interfaces $junos-interface-ifd-name unit $junos-interface-unit family inet service]
      user@host# set input service-set set1 service-filter serv-filter1

    6. Configure the output service sets and filters to apply to traffic by a dynamic profile.

      [edit dynamic-profiles profile prof-2 interfaces $junos-interface-ifd-name unit $junos-interface-unit family inet service]
      user@host# set output service-set set2 service-filter serv-filter2

    Results

    From configuration mode, confirm your configuration by entering the show dynamic-profiles command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

    [edit]root@host# show dynamic-profiles
    dynamic-profiles prof-2 (interfaces {$junos-interface-ifd-name {unit $junos-interface-unit {family inet {service {input {service-set set1 service-filter serv-filter1;}output {service-set set2 service-filter serv-filter2;}}}}}}}

    Verification

    To confirm that a service set has been configured correctly for a service interface, perform these tasks:

    Verifying Service Set Summary Information for a Services Interface

    Purpose

    Display the summary information about the service sets for service interfaces.

    Action

    From operational mode, enter the show services service-sets summary command.

    user@host> show services service-sets summary
                       Service sets                                                                    CPU 
    Interface    configured             Bytes used   Policy bytes used  utilization 
    ms-1/0/0           1   385021900      (81.96%)     299796 ( 0.44%)  92.89 % OVLD 
    
    

    Meaning

    The output lists summarized information for the configured service interface and its configured service sets.

    Verifying Statistics for the Configured Service Set Interface

    Purpose

    Display statistics for the configured service set interface.

    Action

    From operational mode, enter the show services captive-portal-content-delivery statistics interface ms-1/0/0 command.

    user@host> show services captive-portal-content-delivery statistics interface ms-1/0/0
    service-set interface: ms-1/0/0
    
    Packets received   Packets altered  
    5                     3          
    

    Meaning

    The output lists the packet flow statistics for the configured service set interface.

     

    Related Documentation

     

    Modified: 2017-03-01