| Oracle® Communications IP Service Activator QoS User’s Guide Release 7.2 E47716-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Communications IP Service Activator QoS User’s Guide Release 7.2 E47716-01 |
|
|
PDF · Mobi · ePub |
This chapter explains how configuration policies extend the capabilities of Oracle Communications IP Service Activator.This chapter includes the following:
an overview of configuration policies
loading and accessing configuration policies
customizing the organization of configuration policies in the GUI
adding configuration policy files to Policy Types
exporting policy files from Policy Types
applying configuration policies
applying configuration policies at the device level
Configuration policies extend the services supported by IP Service Activator. They are applied through the Configuration Policy functionality of the IP Service Activator GUI.
Configuration policies are used to add a variety of services to IP Service Activator and can be applied to object model targets at various points in the object hierarchy, depending on the nature of the service.
You can access configuration policies through the Add Configuration Policy context menu item for Customer, Site, Network, Device, Interface or Sub-interface objects. The information gathered through the HTML interface on the Configuration Policy dialog box is configured on devices through the Network Processor and appropriate underlying cartridge support.
Note:
IP Service Activator will not prevent you from applying configuration policies to objects in the object model that do not support them. You can confirm the appropriate targets a configuration policy by referring to its detailed field-level description topic in the IP Service Activator IP Service Activator online Help.A large number of ready-to-use configuration policies are provided with IP Service Activator and can be used as-is for various purposes.
Alternatively, you can use the IP Service Activator SDK to create and customize configuration policies as well as a service cartridge to support the implementation of the services that the configuration policy provides.
For detailed information about particular configuration policies, including descriptions of all fields and ranges supported on the HTML input screen, refer to IP Service Activator online Help.
For details on how to use the IP Service Activator SDK to create configuration policies, refer to IP Service Activator SDK Configuration Policy Extension Developer Guide. Additional concepts including the integration of configuration policies with service cartridges are also described.
For easier access, available configuration policies are grouped by functionality in sub-folders of the Policy Types folder in the Policy tab. This hierarchy is also used to organize available configuration policy choices when choosing from the Add Configuration Policy pop-up menu.
When .policy files are created, information is included which dictates their initial sub-folder organization when they are loaded into IP Service Activator.
These sub-folders include:
Interface: Contains interface-oriented configuration policies
Service: Contains configuration policies for particular modelled services
Unclassified: Contains miscellaneous configuration policy not oriented to a modelled service
There may be additional sub-folders in the hierarchy as well. These can be from custom configuration policies that have been loaded or from your own Policy Type sub-folder customizations.
Note:
The menu hierarchy in which configuration policies are presented when you right-click on a target object and select Add Configuration Policy matches the hierarchy of the sub-folders and configuration policies in the Policy Type folder in the Policy tab. When you customize the organization of configuration policies in the Policy Type folder, this also affects the menu organization.You can set permissions to configuration policies on their Ownership property page. Denied permission can be selected on the Ownership property page for users who must not access specific configuration policies. For more information, see IP Service Activator User's Guide.
To view the configuration policies currently loaded into IP Service Activator:
On the Global Setup window, double-click a Domain from the Hierarchy pane to open it.
Select the Policy tab
Expand the Policy Types folder.
Explore the hierarchy by expanding sub-folders to see which configuration policies are available.
To create a new configuration policy sub-folder:
Right-click on the parent folder and select Add Folder.
The Policy Type Folder dialog box is displayed.
On the Policy Type Folder property page, enter a value for the Name.
Optionally, select the Ownership property page and specify user permissions for the folder.
Click OK.
Commit the transaction.
The new folder is created in the Policy Types hierarchy.
To move a configuration policy, drag it from the source to the target folder under the Policy Types folder hierarchy and commit the transaction. There are restrictions on which folders particular configuration policies can be placed, based on their functional grouping. If a configuration policy can't be placed in a particular folder, you will not be able to drag and drop it to that location.
Note:
Once you move a configuration policy from its original location, do not reload it.To delete a configuration policy from the GUI:
Right-click on the target configuration policy and select Delete.
Commit the transaction.
The target configuration policy is deleted.
To delete a configuration policy sub-folder:
Right-click on the target folder and select Delete.
Commit the transaction.
The target folder and its contents are deleted.
Note:
When you delete a configuration policy subfolder, its contents and any sub-folders and their contents are also deleted.Configuration policies are applied to various types of target objects in the object model, depending on their function and design. See "Applying Configuration Policies at the Device Level" for information on device-level configuration policies.
Applied configuration policies employ the normal IP Service Activator concepts of inheritance and roles. In order for a configuration policy to be successfully applied it must match a device and interface role and create a concrete at the interface, sub-interface or VC object level.
Note:
Configuration policies must be installed before you can use them in the GUI. See IP Service Activator Administrator's Guide for details.To apply a configuration policy:
Click either the Service or Topology tab.
Locate the Customer, Site, Network, Device, Interface or Sub-interface target.
Right click the target, and select Add Configuration Policy... from the pop-up menu and choose the desired configuration policy from the cascading menu.
The Configuration Policy dialog box displays the properties of a selected Configuration Policy, which allows the entry of either a set of raw XML commands, or an HTML-based entry form to collect information which is then converted to XML.
Provide the required information in the HTML-based entry form.
Click OK.
Commit the transaction.
For complete details on the fields in each configuration policy and the ranges of values that can be entered, see the individual configuration policy topics in IP Service Activator online Help.
The Disable check box disables a configuration policy that is provisioned at the device level and applied to numerous interfaces through inheritance. This will disable the policy for all the interfaces it has been applied to.
Checking the Disable check box at the interface level disables the configuration policy only from the currently selected interface.
Some configuration policies are designed to apply device-level commands (that is, command which are not applied in the context of an interface). However, to apply the configuration, the configuration policy must be applied to an interface object in order to generate the required concrete.
One approach is to attach these types of device-level configuration policies to the Loopback interface of the device. Concretes will be automatically created on the Loopback interface (or other interface if a non-loopback interface is chosen).
To apply configuration policies:
Create a new interface role called Device Policy.
Set the Device Policy role on the selected interface on each device (for example, Loopback0).
Apply the desired device-level configuration policy to the device and on the Role property page of the Configuration Policy dialog, set the configuration policy interface role to Device Policy.
A number of general use configuration policies are provided with IP Service Activator that are applied at the device-level. These are organized into the Policy Types > Service > General hierarchy. These configuration policies place specific data on the device, or configure particular resources on the device that may be required for other services. They are not used to configure a modelled service by themselves.
See "Applying Configuration Policies at the Device Level" for details on applying configuration policies at the device level.
When you load the GeneralPolicyTypes.policy file, the general usage configuration polices loaded include the following:
Banner
IP Pools
Key Chain
Prefix List
SNMP Community
SNMP Host
Static Route
User Authentication
User Data
The function of most of these configuration policies is self-evident from their name. The Banner configuration policy configures MOTD type banners on devices, and most of the other policies configure data in accordance with their name. For complete details on the fields included in each configuration policy, refer to its topic in IP Service Activator online Help.
This configuration policy can be used to configure additional separate local user accounts on the device, rather than having to perform this task manually. Using the configuration policy has the advantage that the account data is maintained in IP Service Activator, rather than having to be configured and maintained manually.
Refer to the appropriate cartridge guides to determine device support for this policy.
Note:
Within the IP Service Activator system, the password for accounts configured with the User Authentication configuration policy is not protected.This configuration policy is unique in that it is not intended to configure any service or configuration on the device and has no pre-defined purpose. The use of the User Data configuration policy is to provide a system-integrated method of attaching free form user data to objects which are modelled in IP Service Activator. The data is stored as name/value pairs, making it easier to process or manage this information outside IP Service Activator, through the OJDL API for example.
When you apply the User Data configuration policy to an object, it must be done in such a way that no concrete is generated. The network processor will generate errors if a concrete is created.
When you apply the configuration policy to a target, before you commit the transaction:
Ensure that no roles are specified for the configuration policy.
check the Disable check box in the Rule Status pane of the Configuration Policy property page of the Configuration Policy dialog box.
Some configuration policies such as Static Route and Banner allow for multiple definitions either within the same policy definition, or across multiple policy instances on the same device. This allows for the creation of groups of definitions that may be defined at different levels in the policy inheritance hierarchy.
For example, a general banner policy can be defined at the Network level with a common login and incoming banner definition that would apply to all devices, while a separate MOTD (message of the day) banner could be defined specifically at the device level. See Figure 5-1 for an example of banners.
Each collection based policy must contain at least one valid definition. If the last definition is removed, the policy must either be disabled or deleted from the device.
Included with IP Service Activator are a number of configuration policies to extend the QoS capabilities of IP Service Activator on various devices.
QoS support is provided for Alcatel devices, for example, through configuration policies.
In cases where IP Service Activator doesn't support the exact QoS mechanism you need, or for whatever reason, you choose not to use IP Service Activator's QoS provisioning capabilities, you can use attachment configuration policies to attach the QoS configuration elements already configured your router to a service or interface within IP Service Activator.
For complete details on the fields and controls in specific configuration policies, refer to IP Service Activator online Help.
For details on specific vendor support for this configuration policy, refer to the appropriate vendor-specific Cartridge guide.
Attachment QoS policies allow you to use IP Service Activator to link existing QoS configuration elements pre-existing on devices with targets in the object model.
The qosCosAttachment configuration policy allows you to create references to existing QoS (quality of service) and/or CoS (class of service) policies on interfaces or PVCs on Cisco devices.
The supplied vendor-specific QoS policies provide additional QoS capabilities on various vendors' equipment.
Default QoS templates, typically with little or no service specific configuration details, are pre-configured on Alcatel devices through the Service Aware Manager (SAM) software. The broadcast of templates to Alcatel devices is managed by the SAM. The Alcatel QoS configuration policies provided with IP Service Activator allow the provision of overrides to these default policies to provide specific parameters at the service level. For example, when applied to a target such as a VPN, you could use the default templates as-is, or you could override specific values such as CIR, PIR, or Bandwidth at a particular site using the Alcatel QoS configuration policies.Alcatel QoS configuration policies include:
alcatelSamQosPool
alcatelSamQosOverridePolicy
alcatelSamAggregatedScheduler
alcatelSamSchedulerOverridePolicy
Various configuration policies provide the ability to configure additional QoS elements on various platforms.
catOSPolicingRule: CatOS does not support MQC PHBs. This configuration policy enables policing-type QoS on these devices.
rate-limit: Provides rate-limiting on Brocade devices
Configuration policies must be installed before they can be applied to target objects. Before using the complementary QoS configuration policies you must load the following .policy files:
AlcatelSAMPolicyTypes.policy
CiscoCatOSQoSPolicyTypes.policy
CiscoIOSQoSPolicyTypes.policy
FoundryIronWareQoSPolicyTypes.policy
JuniperJUNOSQoSPolicyTypes.policy
ExtensionPackCPolicyTypes.policy
For complete details on how to install configuration policies, see IP Service Activator Administrator's Guide.
As with other configuration policies, IP Service Activator's role-based inheritance rules apply to QoS and attachment configuration policies. The inheritance model enables policy defined at a high level, such as the domain or network, to be inherited to lower level objects, such as devices and interfaces. Roles enable you to group devices and interfaces by, for example, customer and service package, and create policies targeted at that group. Policies can be directed towards specific groups of devices and interfaces.
For details on roles, refer to IP Service Activator User's Guide.
Attachment QoS policies allow you to use IP Service Activator to link existing QoS configuration elements on devices with targets in the object model.
There may be cases where IP Service Activator does not support the QoS capabilities you want to implement. Or, you may prefer to define QoS configurations outside of IP Service Activator.
On new installations, there may be a significant investment in QoS configuration already on existing devices that you don't want to reproduce in the IP Service Activator object model.
In these cases, you can use IP Service Activator to apply QoS configurations defined on devices to interfaces on those devices through the use of an attachment configuration policy. One advantage of this approach is that IP Service Activator will not remove the QoS configuration from the device, even when it is unlinked from targets in the object model
This configuration policy allows you to create references to QoS (quality of service) and/or CoS (class of service) policies on interfaces or PVCs, primarily on Cisco devices.
The QoSCosAttachment configuration policy allows you to use predefined QoS policy on a device in a manner similar to a template and attach it to target interfaces. A single QoS definition can be attached to multiple interfaces. For example, if you provide the name of the policy map, IP Service Activator maintains the link between the interface and the defined policy map. In the interface, IP Service Activator issues configuration commands to link the policy map to the interface.
Note:
You can link both a QoS and a CoS with one instance of this configuration policy.This section describes vendor-specific configuration policies that extend the QoS capabilities of IP Service Activator.
The Alcatel QoS configuration policies take values as specified in the configuration policy, and apply them as override parameters of the default template values broadcast by the SAM.
This configuration policy allows you to apply overrides to slope policies, in particular, slope policies which apply to access ingress and egress buffer pools, and network egress buffer pools. Slope policies define the Random Early Detection (RED) slope characteristics as a percentage of pool size for the buffer pool on which the policy is applied.
This policy is typically applied at the interface level in IP Service Activator.
This configuration policy allows you to create service ingress and egress QoS policies against a specific VPRN service instance. If you want to apply both an ingress and an egress policy against a single target sub-interface, you need to apply two separate instances of this configuration policy.
This policy is typically applied at the sub-interface level in IP Service Activator.
This configuration policy allows you to configure Alcatel SAM aggregation.This policy is typically applied at the interface level.
This configuration policy allows you to configure overrides to ingress or egress scheduler policies.
A set of global Scheduler and Qos policies are defined in the SAM. You can choose which global policy to attach to each interface. Then, as an option, you override individual parameters of the Scheduler or QoS policies.
The policy is applied at different levels depending on the desired behavior:
Applying the configuration policy against a Layer 3 Access interface results in Scheduler Policy overrides defined against a specific VPRN service.
Applying the policy against a port results in the creation of a multi-service-site or Aggregation scheduler on that port. This Aggregation scheduler can then be referenced in an applied Layer 3 Access Interface creation policy (specifically, the alcatelSRL3Interface configuration policy) to attach the multi-service-site to the appropriate VPRN service instance.
The following sections describe the possible Cisco QoS configuration policies.
This configuration policy allows you to create a Layer 2 QoS aggregate policer with ACL configuration for IP, MAC and IPX traffic types on an Ethernet interface or VLAN. At least one classification must be declared as part of the policy definition. This configuration policy is supported for the Cisco CatOS cartridge only.
This policy is applied to interfaces and VLANs, with one policy per target. CatOS doesn't support MQC PHBs. This configuration policy enables policing-type QoS on these devices.
This configuration policy allows you to configure hardware-based WRR transmit queues (with their associated WRED or tail-drop thresholds) of LAN/OSM interfaces on Cisco routers that support such configuration.
This policy only works with Cisco Cartridge Unit (CU) 4, Ethernet, FastEthernet, Gigabit Ethernet (Cisco 7600 and 6500 Devices with IOS above 12.1). You can deploy one configuration policy per interface.
|
 Copyright © 2012, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
