Creating Service Definitions; Table 139: Junose Objects Tracked By Service Manager - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - BROADBAND ACCESS CONFIGURATION GUIDE 2010-10-12 Configuration Manual

JunosE 11.3.x Broadband Access Configuration Guide

Creating Service Definitions

638
Classifier lists—Specify the criteria by which the router defines a packet flow.
Rate-limit profiles—Specify a set of bandwidth attributes and associated actions that
limit a classified packet flow or a source interface to a rate that is less than the physical
rate of the port.
QoS parameters—Specify attributes such as shaping rate, shared-shaping rate, assured
rate, and scheduler weight for scheduler nodes and queues.
QoS profiles—Specify queue, drop statistics gathering, and scheduler configuration
for an interface hierarchy.
To create a service definition, you use the JunosE Software's macro language to specify
the parameters that define the desired service. A macro file can define only one
service—however, the file can have multiple templates to define characteristics of the
desired service. You create service definitions independent of the Service Manager
commands and operations, which are performed on the E Series router.
For detailed information about the JunosE Software's macro language, see the Command
Line Interface chapter in JunosE System Basics Configuration Guide.
Figure 29 on page 640 is an example of a service definition macro file that creates a tiered
service. A tiered service typically provides set bandwidths for both inbound and outbound
traffic for a subscriber. In this example, the input (inputBW) and output (outputBW)
bandwidth values are parameterized. This example assumes that QoS profile triplePlayIP
and QoS parameter maxSubscBW are configured. See "Service Definition Examples" on
page 682 for additional service definition examples.
Service Manager only tracks JunosE objects that are passed back in the env.setResult
method when a service definition is executed. Table 139 on page 638 describes the
supported objects:

Table 139: JunosE Objects Tracked by Service Manager

Name
input-stat-clacl
secondary-input-stat-clacl
output-stat-clacl
activate-profile
Requirement Description
Optional Collects input statistics from policy manager
Can be a list of clacls
Optional Collects input statistics from policy manager
Can be a list of clacls
Optional Collects output statistics from policy manager
Can be a list of clacls
Required Specifies the interface profile used on
activation of the service
Deletion of the profile is Service Manager's
responsibility
Copyright © 2010, Juniper Networks, Inc.