Service Set Configuration Example

The following configuration shows how service sets can use multiple services.

In this example, there are two services defined in the application's services (that is, the [edit acme services]) hierarchy level: acme-svc1 and acme-svc2. Both of these services are included in service set sset1.

Looking at the example, notice the following:

   acme {
      acme-svc1 { # External service (provider-defined)
         svc1-rule1 { # First rule's name
            . . . # First rule defined
         svc1-rule2 { 
            . . . 
         svc1-rule3 { 
            . . . 
      acme-svc2 { # External service (provider-defined)
         rule-set svc2-rule-set { # Rule set name
            [ rules rule-names ]; # The rules' definitions
   service-set sset1 {
      next-hop-service {
         inside-service-interface ms 50/0.1;
         outside-service-interface ms-5/0/0.2;
      extension-service acme-svc1 {    
      extension-service acme-svc2 {    
         rule-set svc2-rule-set;

      /* Now define the order */
      service-order {
         forward-flow [acme-svc1 acme-svc2];
         reverse-flow [acme-svc1 acme-svc2];

The inside-service-interface and outside-service-interface logical units cannot be shared across service sets.
Other Configuration Guidelines:
Guidelines for Configuring SDK Applications

See also:
Statement Summary

Configuration Command Summary

Operational Command Reference

SDK CLI Configuration

2007-2009 Juniper Networks, Inc. All rights reserved. The information contained herein is confidential information of Juniper Networks, Inc., and may not be used, disclosed, distributed, modified, or copied without the prior written consent of Juniper Networks, Inc. in an express license. This information is subject to change by Juniper Networks, Inc. Juniper Networks, the Juniper Networks logo, and JUNOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.
Generated on Sun May 30 20:26:48 2010 for Juniper Networks Partner Solution Development Platform JUNOS SDK 10.2R1 by Doxygen 1.4.5