 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
This section explains the use of service sets in SDK applications. For more information about service sets, see the JUNOS Services Interfaces Configuration Guide.
A service set is a collection of policies taken from multiple services that can be applied as a unit to traffic coming to the PIC. Service sets are the building blocks of SDK plugins. Currently, up to two SDK plugins are supported per PIC.
Policies are maintained per service set only. For defining policies using the command-line interface (CLI), the SDK does not specify how providers must set up the configuration hierarchy. However, two things are mandatory:
To specify the order of the policies within a service set, configure the service-order statement at the [edit services extension-service] hierarchy level.
To define a service set, configure statements at the [edit services service-set service-set-name extension-service] hierarchy level. For specific information, see the application-specific documentation.
SDK application providers may want to follow the JUNOS software method of configuring a service set. In the native JUNOS software, policies known as “rules” or groups of rules known as “rule sets” are configured at the [edit services] hierarchy level. These services are then gathered together in a service set at the [edit services service-set service-set-name extension-service] hierarchy level by referencing the names of the rules or rule sets.
The following sections briefly explain service sets as they relate to SDK applications:
| Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |