Referencing Policies In Service Definitions - Juniper JUNOSE SOFTWARE 11.0.X - BROADBAND ACCESS CONFIGURATION GUIDE 4-1-2010 Configuration Manual

JUNOSe 11.0.x Broadband Access Configuration Guide

Referencing Policies in Service Definitions

In Profile Configuration mode, policy interface commands for IP and L2TP allow
attachments to be merged into any existing merge-capable attachment at an
attachment point. Merged policies are dynamically created. Service Manager can
request that multiple interface profiles be applied or removed at an interface as part
of service activation or deactivation. Service Manager also specifies whether or not
the attachments created from these interface profiles persist on subsequent reloads.
Service Manager can specify whether a component policy attachment is non-volatile.
If the interface where the component policy is attached is volatile, then policy
management makes the attachment volatile even when the Service Manager specifies
otherwise. A non-volatile interface can have both volatile and non-volatile component
policy attachments. The merged policy that is created is the merge of all component
policies attached at a given attachment point regardless of their volatility. The merged
policy and its attachments are always volatile and reconstructed on each reload
operation.
For further details on merging policies, see the Merging Policies chapter inJUNOSe
Policy Management Configuration Guide.
644
Referencing Policies in Service Definitions
During installation, Service Manager precompiles the service definition and
extracts the definition file's timestamp.
After you install the service definition, you can use the definition to create service
sessions for subscribers.
To update an existing service definition, you make changes to the original macro
file on your computer, copy the updated file to NVS, and install the updated file.
All subsequent service sessions use the new service definition file. However,
currently active service sessions continue to use the original definition file until
the sessions are deactivated, then reactivated.
Example 1 Installing
host1(config)#service-management install tiered.mac
Example 2 Uninstalling
host1(config)#no service-management install tiered.mac
Example 3 Updating
! update the original macro file on the remote system
! copy the updated macro file to the router
host1#copy boston:/serviceDefs/triplePlay/tiered.mac tiered.mac
host1#configure terminal
! install the updated service definition on the router
host1(config)#service-management install tiered.mac
Use the no version to uninstall a service definition.
See service-management install