Creating Service Definitions

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 the JunosE System Basics Configuration Guide.

Figure 3 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 Example: Video-on-Demand Service Definition, Example: Voice-over-IP Service Definition , and Example: Guided Entrance Service Definition 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 9 describes the supported objects:

Table 9: JunosE Objects Tracked by Service Manager

Name

Requirement

Description

input-stat-clacl

Optional

  • Collects input statistics from policy manager
  • Can be a list of clacls

secondary-input-stat-clacl

Optional

  • Collects input statistics from policy manager
  • Can be a list of clacls

output-stat-clacl

Optional

  • Collects output statistics from policy manager
  • Can be a list of clacls

activate-profile

Required

  • Specifies the interface profile used on activation of the service
  • Deletion of the profile is Service Manager’s responsibility

deactivate-profile

Optional

  • Specifies the interface profile used on deactivation of the service
  • If not specified, is the same as the activation-profile
  • Deletion of the profile is Service Manager’s responsibility

command-in-error

Optional

  • Passes the value env.getErrorCommand
  • Service Manager displays the line in the service definition that has the error

command-error-status

Optional

  • Passes the value env.getErrorStatus
  • Service Manager displays the error status for the error

service-interface-type

  • Optional for IPv4 or L2TP services
  • Mandatory for independent IPv6 services or combined IPv4 and IPv6 services in a dual stack
  • Specifies the type of interface, IPv4, IPv6, combination of IPv4 and IPv6, or L2TP, to which the service session profile must be applied

input-stat-epg

Optional

  • Collects input statistics associated with the external group from policy manager
  • Both the external parent group and the corresponding hierarchical policy parameter must be specified
  • Can be multiple pairs of external parent groups and hierarchical policy parameters

output-stat-epg

Optional

  • Collects output statistics associated with the external group from policy manager
  • Both the external parent group and the corresponding hierarchical policy parameter must be specified
  • Can be multiple pairs of external parent groups and hierarchical policy parameters

secondary-input-stat-epg

Optional

  • Collects input statistics associated with the external group that is attached at the secondary input stage from policy manager
  • Both the external parent group and the corresponding hierarchical policy parameter must be specified
  • Can be multiple pairs of external parent groups and hierarchical policy parameters

Figure 3: Sample Service Definition Macro File

Sample Service Definition Macro File

Related Documentation