Service scopes let you customize which services are to be delivered to specific organizations or specific locales. You can use service scopes to provision services for a group of subscribers by specifying:
A service scope is a collection of services and mutex groups, and optionally defines parameter substitutions for its associated services. For more information about parameter substitutions, see Parameters and Substitutions . The object o=Services is the generic service scope—a collection of services and mutex groups available to all subscribers.
You can assign service scopes to virtual routers (VRs) and to some types of subscribers.
You can also assign a service scope to multiple VRs and subscribers. For example, by assigning a service scope to a group of VRs, you can specify that a service is available only in the locations served by those VRs. If a subscriber of this service accesses the network from a location where you do not offer this service, the portal will not display the service, and the subscriber will not be able to use it.
If you assign a service scope to multiple VRs and subscribers, you specify a precedence—a numerical ranking—for each service scope. The lower the precedence value, the higher the ranking of the service scope. By default, the object o=Services has the highest precedence value and the lowest ranking.
If multiple service scopes that define the same service are assigned to a VR or subscriber, the SAE selects the parameters to use for the service as follows:
For example, consider the situation shown in Table 5in which three scopes define several parameters for the same service.
Table 5: Parameter Selection Example
|
Service Scope Name |
Precedence Value |
Parameter Definitions |
|---|---|---|
|
s1 |
1 |
description, policy group |
|
s2 |
5 |
description, URL |
|
s3 |
5 |
description, URL |
The SAE will use the following parameter definitions for the service:
You can also configure a generic Internet access service, and use service scopes to define the access parameters for different locations to use this service. If multiple service scopes that define this Internet access service are assigned to a VR, the SAE uses the precedence values to determine how to customize the service.
You can use service scopes to create a limited set of services to be made available to specified organizations. For enterprise users, you could define a set of services available on the JUNOS routing platform.
To deliver a small set of services to specified enterprises:
- user@host> show configuration services scope
EntJunos
- user@host# edit subscribers retailer ENT subscriber-folder
entAcme enterprise Acme
- [edit subscribers retailer ENT subscriber-folder entAcme
enterprise Acme]
- user@host# set scope EntJunos
[edit subscribers retailer ENT subscriber-folder entAcme enterprise Acme] user@host# show scope EntJunos;
If you use a portal to manage enterprises, you see only the services for the specified scope from the portal. Other services are not visible to the IT managers who manage services and subscriptions from the enterprise service portal. To see the services available to Acme from Enterprise Manager Portal, see the SRC-PE Sample Applications Guide.
You could use service scopes to customize a generic audio service called Audio-Bronze on a regional basis. This example assumes that the network is configured so that VR boston serves the Boston subnet and VR chicago serves the Chicago subnet.
When the network starts operating, the SAE substitutes the parameters you specified in the service scope definition for the corresponding fields in the service subordinate to that scope.
To customize the new service Audio-Bronze for the Boston and Chicago subnets:
This IP address and mask determine an access point to the service provider’s equipment.
- user@host# edit services scope boston
- [edit services scope boston]
- user@host# edit service Audio-Bronze
- [edit services scope boston service Audio-Bronze]
- user@host# set parameter service-ip-address
10.10.40.33
- [edit services scope boston service Audio-Bronze]
- user@host# set parameter service-ip-mask 255.255.255.255
- user@host# edit services scope chicago
- [edit services scope chicago]
- user@host# edit service Audio-Bronze
- [edit services scope chicago service Audio-Bronze]
- user@host# set parameter service-ip-address
10.10.55.1
- [edit services scope chicago service Audio-Bronze]
- user@host# set parameter service-ip-mask 255.255.255.255
- user@host# edit shared network device region_one
virtual-router boston
- [edit shared network device region_one virtual-router boston]
- user@host# set scope boston
- user@host# edit shared network device region_two
virtual-router chicago
- [edit shared network device region_two virtual-router chicago]
- user@host# set scope chicago