Table Of Contents
Managing Traffic Configurations
Retrieving Traffic Configurations
Applying Configuration Changes
Exporting Traffic Configurations
Importing Traffic Configurations
Defining Traffic Classes and Protocols
Examples of Classes and Class Elements
Configuring Traffic Monitoring
Configuring Real-Time User RDRs
Configuring Transaction Usage RDRs
Understanding Filtering Traffic Flows
Adding a Global Filtering Rule
Editing a Global Filtering Rule
Deleting a Global Filtering Rule
Managing Global Bandwidth Controllers
Deleting Bandwidth Controllers
Adding User Bandwidth Controllers
Editing User Bandwidth Controllers
Effect of Burst Traffic on System Mode
Understanding System Mode versus ISR Diversion Mode
Renaming Time Frames in Global Calendars
Configuring Time Frames in Global Calendars
Configuring ToS Marking Settings
Understanding Redirection URLs
Traffic Management
The Traffic Management features allow you to define the way the APA analyzes and controls traffic. In general, the APA traffic management feature allows you to identify and define the following:
•
Applications—See Defining Traffic Classes and Protocols.
•
•
•
Managing Traffic Configurations
The APADC is a Graphical User Interface (GUI) which gives the NME-APA operator an intuitive method of modifying NME-APA configurations. Configuration changes are made to an NME-APA device through a process of retrieving the device's configuration for display in the APADC, modifying the configuration parameters in the APADC, and applying the modified configuration back to the NME-APA device.
The traffic configuration is one of the three configurations that you manage using the APADC and apply to an NME-APA device. It contains traffic classes and protocols, traffic monitoring settings, traffic filters and policies, and global settings. The other two configuration types are device configuration and user configuration.
Note
Note
NME-APA traffic configurations can also be stored offline in configuration files and restored to NME-APA devices through the configuration Export and Import functions. The default location for storing traffic configurations is C:\APADC\apache-tomcat-5.5.20\webapps\ROOT\scate_exports.
Caution
•
•
•
•
Retrieving Traffic Configurations
Step 1
The seleted provisioning screen appears in the Configuration pane, displaying the Retrieve button in the bottom section.
Step 2
The traffic configuration is retrieved and loaded into the APADC.
Related Topics
•
•
•
Applying Configuration Changes
The APADC interface allows you to modify a device's configuration without affecting the device. To use the modified configuration, you must apply it to the device.
Step 1
The seleted provisioning screen appears in the Configuration pane, displaying the Retrieve button in the bottom section.
Step 2
The traffic configuration is applied to the device.
Related Topics
•
•
•
Exporting Traffic Configurations
A traffic configuration can be exported and saved to a file so that it can be archived or applied to other devices.
Step 1
The seleted provisioning screen appears in the Configuration pane, displaying the Retrieve button in the bottom section.
Step 2
The Export Traffic Management dialog box appears.
Step 3
Step 4
The traffic configuration is exported to a file.
Note
Related Topics
•
•
•
Importing Traffic Configurations
Step 1
The seleted provisioning screen appears in the Configuration pane, displaying the Retrieve button in the bottom section.
Step 2
The Import Traffic Management Data dialog box appears.
Step 3
Step 4
Step 5
The traffic configuration is imported to the APADC.
Note
Related Topics
•
•
•
About Traffic Processing
There are two stages of traffic processing:
•
•
You control how classification and reporting are performed by editing configurations and applying them using the Application Performance Assurance Device Console (APADC).
Defining Traffic Classes and Protocols
When you choose Traffic Management > Applications, you can define the various traffic classes and related protocols.
APA classifies various traffic when a flow is established. The APA examines the first few packets of the session and decides to which class the session belongs. The session is then assigned a class ID that remains the same during the session's life cycle.
Traffic is classified and mapped to classes on the basis of some or all of the following class elements:
•
•
•
•
•
•
The APA uses these flow mappings to map each network connection passing through it to a class.
About Classes
In the traffic classification process, network sessions are categorized into classes. Classes are the building blocks for:
•
•
From a enterprise's point of view, a class is usually a network application—such as browsing, e-mail, file sharing, or voice—that the user uses. From a technical point of view, a class consists of one or more class elements, each of which enables a decision about the class associated with a network traffic flow type.
By default, APA has a number of predefined classes. You can modify these classes and add additional classes to a configuration. You can configure up to 500 classes in a configuration.
The following sections explain how to modify and manage classes:
Figure 3-1 illustrates the mappings of flow elements of a session to elements of a class:
Figure 3-1 How Flow Elements of a Session Map to Elements of a Class
Related Topics
•
Class Hierarchy
Classes are arranged in a hierarchical tree. APA has a single default class at the root. You can add parent and child classes. Child classes can inherit policy rules and usage counters of their parents.
Examples of Classes and Class Elements
Table 3-1 contains examples of classes and their network parameters:
Classes might share the same class usage counter. For example, in the default configuration, the SMTP service and the POP3 service share the E-Mail Counter. The assignment of classes to usage counters is determined by the class hierarchy.
Class Usage Counters
The class hierarchy provides a way to share usage counters and to organize classes according to their semantics. Classes are accounted in groups, as defined in the class hierarchy. Each class is assigned usage counters.
There are two categories of usage counters for classes:
•
•
A global usage counter and a user usage counter are assigned to each class. The use of a class can be accounted either exclusively for traffic classified to it or in conjunction with the traffic of its parent class. For example, if a class called Premium Video Content is defined as a child of Streaming, the operator can either define a special usage counter for Premium Video Content or configure it to use the same usage counter as Streaming. The global usage counter and the user usage counter are independent; for the same class, one usage counter may be the same for parent and child, whereas the other is exclusive to the child.
Adding Classes
Step 1
The list of configured classes appears in the Configuration pane.
Figure 3-2
Step 2
The Classes Configuration screen appears in the Configuration pane.
Figure 3-3
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
The Element Details screen appears in the Configuration pane.
Figure 3-4
For more information, see Managing Class Elements.
Step 9
The new class is saved in the configuration.
The Class Configuration screen of the new class appears in the Configuration pane.
Related Topics
Editing Classes
Step 1
The list of configured classes appears in the Configuration pane.
Step 2
Step 3
The Class Configuration screen appears in the Configuration pane.
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
The modified class is saved in the configuration.
Related Topics
Deleting Classes
Step 1
The list of configured classes appears in the Configuration pane.
Step 2
Step 3
Step 4
The class is removed from the list of classes.
Related Topics
Managing Class Elements
A class consists of one or more class elements; different network traffic flow types are mapped to different class elements. A class element maps a specific protocol, initiating side, zone, and flavor to the selected class. Some or all of these parameters can take wildcard values.
•
•
•
•
•
If a flow matches two class elements and one is more specific than the other, the flow is mapped to the more specific of the two. For example: Class A is defined for browsing and Class B is defined for browsing to a specific list of URLs. A browsing flow to a URL on Class B's list matches both classes, but is mapped to Class B.
If a flow matches one parameter of one class element and a different parameter of another class element, precedence is given first to matching flavors, then to protocols, then to zones, and finally to the initiating side. For example: Class A is defined for e-mail and Class B is defined for all traffic to a specific network zone. An e-mail flow to the specific network zone matches both classes, but is mapped to Class A.
The following sections explain how to manage class elements:
Initiating Side
When you add class elements, you specify the initiating side property. The APA is located between the enterprise's users and the network. User-initiated flows are initiated by the user toward the network; network-initiated flows are initiated from the network toward the user.
You can monitor some flow types to one initiating side. For example, with HTTP you can monitor the user-initiated traffic separately from the network-initiated traffic. HTTP is always user initiated when the user ventures outward to surf the Internet. If the direction of the HTTP flow is network initiated, this probably means that a web server is open on the user's local machine for receiving incoming HTTP traffic. The enterprise can monitor the network-initiated HTTP and use other criteria to evaluate if the traffic is legitimate.
Adding Class Elements
Step 1
The list of configured classes appears in the Configuration pane.
Step 2
Step 3
The Class Configuration screen appears in the Configuration pane, displaying the Elements box in the middle portion of the screen.
Figure 3-5
Step 4
The Element Details screen appears in the Configuration pane.
Figure 3-6
Step 5
Step 6
Step 7
Step 8
Step 9
The new class element is saved in the configuration.
Related Topics
Editing Class Elements
Step 1
The list of configured classes appears in the Configuration pane.
Step 2
Step 3
The Class Configuration screen appears in the Configuration pane, displaying the Elements box in the middle portion of the screen.
Step 4
The Element Details screen appears in the Configuration pane.
Step 5
Step 6
Step 7
Step 8
Step 9
The modified class element is saved in the configuration.
Related Topics
Deleting Class Elements
Step 1
The list of configured classes appears in the Configuration pane.
Step 2
Step 3
The Class Configuration screen appears in the Configuration pane, displaying the Elements box in the middle portion of the screen.
Step 4
Step 5
The element is removed from the list of class elements.
Related Topics
Understanding Signatures
The APA examines traffic flows using its deep packet inspection capabilities, and compares each flow with an installed set of protocol signatures to identify the network application that generated the flow. When you select Traffic Management > Applications > Signatures, you can view the signatures to be used for Layer 7 classification.
The APA comes with a set of predefined signatures for common network applications and protocols, such as browsing, e-mail, file sharing, and VoIP.
Viewing Signatures
Step 1
The list of Signatures appears in the Configuration pane.
Figure 3-7
Step 2
The list of signatures is not editable.
Viewing Signature Scripts
Step 1
Step 2
The DSS File Information screen appears.
Managing Protocols
One of the main classifications of a flow is the protocol of a session (that is, of the network application that generated the session).
A protocol, as defined in the system, is a combination of one or more signatures, one or more port numbers, and a transport type. The protocol of the network flow is identified according to these parameters. For example, if the port number is 80, the transport type is TCP, and content matches the HTTP signature, the APA maps the flow to the HTTP protocol.
When a TCP or UDP flow does not match a specific protocol definition, the APA maps the flow to the Generic TCP or Generic UDP protocol.
When a non-TCP/UDP flow does not match a specific protocol definition, the APA maps the flow to the Generic IP protocol.
The default APA configuration contains a long list of predefined protocols. You can add additional protocols.
The following sections explain how to manage protocols:
Filtering Protocols
You can filter the protocols by type, so that the Protocols tab displays only the selected type of protocol.
There are ten categories of protocols:
•
•
•
•
•
•
•
•
•
•
Note
Step 1
The list of configured protocols appears in the Configuration pane.
Figure 3-8
Step 2
The protocols of the type you selected appear in the Protocols tab.
Note
Related Topics
Adding Protocols
Step 1
The list of configured protocols appears in the Configuration pane.
Step 2
The Protocol Details screen appears in the Configuration pane.
Figure 3-9
Step 3
Step 4
Step 5
The new protocol is saved in the configuration.
Related Topics
Editing Protocols
Step 1
The list of configured protocols appears in the Configuration pane.
Step 2
The Protocol Details screen appears in the Configuration pane.
Step 3
Step 4
Step 5
The modified protocol is saved in the configuration.
Related Topics
Deleting Protocols
Step 1
The list of configured protocols appears in the Configuration pane.
Step 2
Step 3
The protocol is removed from the list of protocols.
Related Topics
Managing Protocol Elements
A protocol is a collection of protocol elements. A protocol element maps a specific signature, IP protocol, and port range to the selected protocol. Some or all of these parameters can take wildcard values; port numbers can take range values.
A traffic flow is mapped to a specific protocol if it meets all three of the following criteria:
•
•
•
If a flow matches two protocol elements and one is more specific than the other, the flow is mapped to the more specific of the two. For example: Protocol A is defined for flows that match the FTP signature and Protocol B is defined for flows that match the FTP signature on TCP port 21. An FTP flow on port 21 matches both protocols, but is mapped to Protocol B.
If a flow matches the signature of one protocol element and the port of another protocol element, it is mapped to the matching signature. For example: Protocol A is defined for flows that match the FTP signature and Protocol B is defined for flows on TCP port 21. An FTP flow on port 21 matches both protocols, but is mapped to Protocol A.
The following sections explain how to manage protocol elements:
Adding Protocol Elements
Step 1
The list of configured protocols appears in the Configuration pane.
Step 2
The Protocol Details screen appears in the Configuration pane, displaying the Protocol Elements box in the lower portion of the screen.
Figure 3-10
Step 3
The Element Details screen appears in the Configuration pane.
Note
Figure 3-11
Step 4
Note
Step 5
Step 6
Step 7
Step 8
The new protocol element is saved in the configuration.
Related Topics
Editing Protocol Elements
Step 1
The list of configured protocols appears in the Configuration pane.
Step 2
The Protocol Details screen appears in the Configuration pane, displaying the Protocol Elements box in the lower portion of the screen.
Step 3
The Element Details screen appears in the Configuration pane.
Step 4
Step 5
Step 6
Step 7
Step 8
The modified protocol element is saved in the configuration.
Related Topics
Deleting Protocol Elements
Step 1
The list of configured protocols appears in the Configuration pane.
Step 2
The Protocol Details screen appears in the Configuration pane, displaying the Protocol Elements box in the lower portion of the screen.
Step 3
Step 4
The protocol element is removed from the list of protocol elements.
Related Topics
Managing Zones
A zone is a collection of network-side IP addresses.
You configure zones by arranging IP addresses in groups connected by a common purpose. A user's network flow mapped to a class may be applied to a zone. In practice, zones often define geographical areas.
Zones are used to classify network sessions; each network session can be assigned to a class element based on its destination IP address.
The following sections explain how to manage zones:
Adding Zones
Step 1
The list of configured zones appears in the Configuration pane.
Figure 3-12
Step 2
The Zone Details screen appears in the Configuration pane.
Figure 3-13
Step 3
Step 4
Step 5
The Zone Item Details screen appears in the Configuration pane.
Figure 3-14
Step 6
Step 7
The new zone is saved in the configuration.
Related Topics
Editing Zones
Step 1
The list of configured zones appears in the Configuration pane.
Step 2
The Zone Details screen appears in the Configuration pane.
Step 3
Step 4
Step 5
The modified zone is saved in the configuration.
Related Topics
Deleting Zones
Step 1
The list of configured zones appears in the Configuration pane.
Step 2
Step 3
The zone is removed from the list of zones.
Related Topics
Managing Zone Elements
A zone element is an IP address or a range of IP addresses.
An example of a zone might be a "walled garden," which is a range of IP addresses on a server farm with premium video content, for which the enterprise would like to limit access to specific users and to ensure traffic priority.
Another example of using a zone might be to differentiate between off-net and on-net flows.
You can assign a zone to a session. Zone A and Zone B are two user-defined zones. Zone A includes the IP address range 10.1.0.0/16, and Zone B includes the IP address range 10.2.0.0/16. Analysis of a new session shows that its network IP address is 10.1.1.1—therefore, the session belongs to zone A.
The following sections explain how to manage zone elements:
Adding Zone Elements
Step 1
The list of configured zones appears in the Configuration pane.
Step 2
The Zone Details screen appears in the Configuration pane, displaying the Zone Items box in the lower portion of the screen.
Figure 3-15
Step 3
The Item Details screen appears in the Configuration pane.
Figure 3-16
Step 4
Step 5
The new zone item is saved in the configuration.
Related Topics
Editing Zone Elements
Step 1
The list of configured zones appears in the Configuration pane.
Step 2
The Zone Details screen appears in the Configuration pane, displaying the Zone Items box in the lower portion of the screen.
Step 3
The Item Details screen appears in the Configuration pane.
Step 4
Step 5
The modified zone item is saved in the configuration.
Related Topics
Deleting Zone Elements
Step 1
The list of configured zones appears in the Configuration pane.
Step 2
The Zone Details screen appears in the Configuration pane, displaying the Zone Items box in the lower portion of the screen.
Step 3
Step 4
The zone item is removed from the list of zone items.
Related Topics
Managing Flavors
Flavors are advanced classification elements that classify network sessions according to signature-specific Layer 7 properties.
Flavors provide an additional level of granularity in defining classes in the APA. A protocol flavor uses an additional protocol attribute in classifying a class, making this class a flavor of the class based on the protocol only. For example, the user-agent attribute of the HTTP protocol could be added as a protocol flavor, enabling the definition of all HTTP traffic generated by the same browser type (indicated in the user-agent field) as one class.
Examples of flavor types are HTTP User Agent and SIP Source Domain.
The following sections explain how to manage flavors:
Flavor Types and Parameters
Table 3-3 lists available flavor types.
Adding Flavors
You can add specific layer 7 properties, such as host names, to the definition of protocols for classification.
Step 1
The list of flavor groups appears in the Configuration pane.
Figure 3-17
Step 2
The list of flavors in the flavor group appears in the Configuration pane.
Figure 3-18
You can also go directly to the list of flavors by selecting your desired flavor group from the Navigation pane.
Step 3
The Flavor Details box appears at the top of the screen.
Figure 3-19
Step 4
Step 5
Step 6
The new flavor is saved in the configuration.
Related Topics
Editing Flavors
Step 1
The list of flavor groups appears in the Configuration pane.
Step 2
The list of flavors in the glavor group appears in the Configuration pane.
You can also go directly to the list of flavors by selecting your desired flavor group from the Navigation pane.
Step 3
The Flavor Details box appears at the top of the screen.
Step 4
Step 5
Step 6
The modified flavor is saved in the configuration.
Related Topics
Deleting Flavors
Step 1
The list of flavor groups appears in the Configuration pane.
Step 2
The list of flavors in the flavor group appears in the Configuration pane.
You can also go directly to the list of flavors by selecting your desired flavor group from the Navigation pane.
Step 3
Step 4
The flavor is removed from the list of flavors.
Related Topics
Managing Flavor Elements
A flavor is a collection of flavor elements.
The type of a flavor element depends on the flavor type.
The default configuration includes some predefined flavors, such as HTTP Streaming Agents (a flavor of HTTP) and Vonage (a flavor of SIP).
The following sections explain how to manage flavor elements:
Adding Flavor Elements
Step 1
The list of flavor groups appears in the Configuration pane.
Step 2
The list of flavors in the flavor group appears in the Configuration pane.
You can also go directly to the list of flavors by selecting your desired flavor group from the Navigation pane.
Step 3
The flavor elements are displayed in the box below the Flavor Details.
Figure 3-20
Step 4
The Flavor Item Details screen appears in the Configuration pane.
Figure 3-21
Step 5
Note
Step 6
The new flavor element is saved in the configuration.
Related Topics
Editing Flavor Elements
Step 1
The list of flavor groups appears in the Configuration pane.
Step 2
The list of flavors in the flavor group appears in the Configuration pane.
You can also go directly to the list of flavors by selecting your desired flavor group from the Navigation pane.
Step 3
The flavor elements are displayed in the box below the Flavor Details.
Step 4
The Flavor Item Details screen appears in the Configuration pane.
Step 5
Note
Step 6
The modified flavor element is saved in the configuration.
Related Topics
Deleting Flavor Elements
Step 1
The list of flavor groups appears in the Configuration pane.
Step 2
The list of flavors in the flavor group appears in the Configuration pane.
You can also go directly to the list of flavors by selecting your desired flavor group from the Navigation pane.
Step 3
The flavor elements are displayed in the box below the Flavor Details.
Step 4
Step 5
The flavor element is removed from the list of flavor elements.
Related Topics
Configuring Traffic Monitoring
APA generates and accumulates Raw Data Records (RDRs) that contain information relevant to the enterprise. When you select Traffic Management > Monitoring, you can chose from one of four main categories of RDRs:
•
•
•
•
This following sections explains how to configure the generation of the different types of RDRs.
Note
Note
Configuring Usage RDRs
Usage RDRs contain the state of the usage counters, per class and per accounting scope.
Step 1
The Monitoring Configuration screen appears in the Configuration pane, displaying the Usage RDRs tab.
Figure 3-22
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Configuring Transaction RDRs
Step 1
The Monitoring Configuration screen appears in the Configuration pane, displaying the Usage RDRs tab.
Step 2
The Transaction RDRs screen appears.
Figure 3-23
Each Transaction RDRs contains data about a single network transaction. They can be used to generate statistical histograms that help understand what kind of traffic is traversing the network.
Step 3
Step 4
Step 5
By default, at most 100 Transaction RDRs are generated per second, and all services are given the same weight.
Step 6
Step 7
Configuring Real-Time User RDRs
Real-Time User Usage RDRs are generated at fixed intervals. They report the amount of usage consumed by an individual user for each class (which was actually used) to allow more granular monitoring of selected users.
Caution
You can enable or disable the generation of Real-Time User Usage RDRs, set the generation interval for these RDRs, and set the maximum number generated per second. By default, Real-Time Subscriber Usage RDRs:
•
•
•
Step 1
The Monitoring Configuration screen appears in the Configuration pane, displaying the Usage RDRs tab.
Step 2
The Real-Time User RDRs screen appears.
Figure 3-24
Step 3
Step 4
Step 5
Step 6
Configuring Transaction Usage RDRs
Transaction Usage RDRs represent single network transactions. They can be used to generate detailed usage logs for specific classes and users of specific policy profile.
Caution
You can select the packages and services for which Transaction Usage RDRs are generated. The following RDRs are also generated for these packages and services:
•
•
•
By default, no transaction usage RDRs are generated.
Step 1
The Monitoring Configuration screen appears in the Configuration pane, displaying the Usage RDRs tab.
Step 2
The Transaction Usage RDRs screen appears.
Figure 3-25
Step 3
Step 4
a.
The Bytes field is enabled.
b.
Step 5
a.
The Minutes field is enabled.
b.
Step 6
Understanding Filtering Traffic Flows
The APA filtering mechanism bypasses portions of the traffic by defining filter rules that match relevant flows. A filter rule matches a packet according to its Layer 3 and Layer 4 properties, such as IP address, port number, and DSCP ToS, as well as the APA interface (user or network) from which the packet arrived. When a traffic flow enters the APA, APA checks whether a filter rule applies to this flow.
For packets that match a filter rule, APA bypasses the current packet (to reduce latency and avoid traffic control). When this action is applied, the current packet is directly transmitted from APA without going through any service configuration processing or reporting. You must map the bypassed packet to a Class of Service (CoS) to assign it to one of the transmit queues of the APA.
A filter rule can perform DSCP ToS marking (by changing the DSCP ToS field of the packet) of the matched traffic.
Although some traffic control policies work in full functionality mode only, APA filtering traffic rules work in both Full Functionality and Report Only mode. That way, even in Report Only mode, you are able to bypass some of the traffic for better service performance.
Understanding Policies
The following features appear under Traffic Management > Policies:
•
•
•
Managing Global Filtering
When you select Traffic Management > Policies > Global Filtering, APA displays a list of the filtering rules, their status, and a summary of the filtering rule.
The following sections explain global filtering rules:
•
•
•
Adding a Global Filtering Rule
Step 1
The Filtering Rules screen appears listing the default global filters.
Step 2
The Add Filtering Rule screen appears.
Step 3
Step 4
Step 5
Step 6
Step 7
•
•
–
–
–
–
Step 8
•
•
–
–
–
–
Step 9
•
•
–
–
–
–
Step 10
•
•
–
–
–
–
Step 11
•
•
–
–
–
–
Note
Now you can specify the action that APA takes for the new rule.
Step 12
•
•
•
•
•
Step 13
Note
Step 14
The rule is added to the filtering rules list.
Related Topics
•
•
Editing a Global Filtering Rule
Step 1
The Filtering Rules screen appears listing the default global filters.
Step 2
The Edit Filtering Rule screen appears.
Step 3
Step 4
The edited rule is saved to the filtering rules list.
Related Topics
•
•
Deleting a Global Filtering Rule
Step 1
The Filtering Rules screen appears listing the default global filters.
Step 2
Step 3
The filtering rule is deleted and no longer appears in the Filtering Rules screen.
Related Topics
•
•
Managing Global Policies
When you select Traffic Management > Policies > Global Policy, you can
•
•
•
Managing Global Policy Rules
When you select Traffic Management > Policies > Global Policy, you can add, modify, and delete global policy rules as explained in the following sections:
Adding Global Policy Rules
A global policy rule defines how APA reacts when it encounters flows that are mapped to the class to which the global policy rule is related. It is recommended that you first define classes (see Adding Classes) and then add and define global policy rules.
Step 1
The Global Policy screen appears displaying the Global Rules tab.
Step 2
The Add Global Policy Service Rule screen appears.
Step 3
Step 4
Step 5
•
•
Note
•
–
–
ToS—Choose the ToS marker for all the packets in either the Upstream or Downstream flow.
Bandwidth Controller—Choose the BWC (bandwidth controller) for the Upsteam and Downstream flow. This sets up bandwidth metering of all flows mapped to this rule, based on the characteristics of the BWC.
Limit Bandwidth per flow—Enter a value (in Kpbs) for the maximum per-flow bandwidth stream.
Step 6
The new global policy service rule is saved in the configuration.
Related Topics
Editing Global Policy Rules
Step 1
The Global Policy screen appears displaying the Global Rules tab.
Step 2
Step 3
The Edit Global Policy Service Rule screen appears.
Step 4
Step 5
The modified global policy service rule is saved in the configuration.
Related Topics
Deleting Global Policy Rules
Step 1
The Global Policy screen appears displaying the Global Rules tab.
Step 2
Step 3
The global rule is deleted.
Related Topics
Managing Global Bandwidth Controllers
The upstream and downstream interfaces are each assigned one default global controller that, by default, controls 100 percent of the link traffic. You can add additional global controllers.
A configuration can contain up to 1024 upstream global controllers and 1024 downstream global controllers (including the default global controllers).
After you have defined global controllers, you can add user bandwidth controllers (BWCs) to packages and map these subscriber BWCs to different global controllers.
Related Topics
•
•
Adding Bandwidth Controllers
You can add bandwidth controllers (BWCs) to control subscriber bandwidth consumption for upstream or downstream flows. The bandwidth controller controls and measures the bandwidth of an aggregation of traffic flows of a service or group of services.
By default, APA has two default bandwidth controllers, one for upstream traffic and one for downstream traffic.
Step 1
The Global Policy screen appears displaying the Global Rules tab.
Step 2
The Bandwidth Controllers screen appears listing the Upstream and Downstream BWCs.
Step 3
Step 4
The Bandwidth Controller—Upstream or the Bandwidth Controller—Downstream dialog box appears, depending on what you selected to add.
Step 5
Step 6
Step 7
Step 8
Step 9
The new bandwidth controller is saved in the configuration.
Related Topics
•
•
•
Editing Bandwidth Controllers
Step 1
The Global Policy screen appears displaying the Global Rules tab.
Step 2
The Bandwidth Controllers screen appears listing the Upstream and Downstream BWCs.
Step 3
Step 4
Step 5
Step 6
The edited bandwidth controller is saved in the configuration.
Related Topics
•
•
Deleting Bandwidth Controllers
Step 1
The Global Policy screen appears displaying the Global Rules tab.
Step 2
The Bandwidth Controllers screen appears listing the Upstream and Downstream BWCs.
Step 3
Step 4
The global controller is deleted.
Related Topics
•
•
Managing Global Controllers
When you select Traffic Management > Policies > Global Policy > Global Controllers, you can add, modify, and delete global controllers as explained in the following sections:
Adding Global Controllers
Step 1
The Global Controllers screen appears containing the Upstream area listing upstream global controllers and the Downstream area listing downstream global controllers. The Link BW (%) column displays the maximum percentage of the total link limit permitted to this global controller.
Step 2
Step 3
The Bandwidth Controller—Upstream or the Bandwidth Controller—Downstream dialog box appears, depending on what you selected to add.
Step 4
Note
Step 5
Step 6
Step 7
Related Topics
Editing Global Controllers
You can edit the maximum bandwidth (as a percentage of the total link limit) that a global controller can carry. You can set a different maximum bandwidth for each of the four available time frames.
Step 1
The Global Controllers screen appears containing the Upstream area listing upstream global controllers and the Downstream area listing downstream global controllers.
Step 2
Step 3
The Edit Bandwidth Controller form appears.
Step 4
Step 5
Step 6
Step 7
The updated global controller is saved in the configuration.
Related Topics
Deleting Global Controllers
Step 1
The Global Controllers screen appears containing the Upstream area listing upstream global controllers and the Downstream area listing downstream global controllers.
Step 2
Step 3
The global controller is deleted from the configuration.
Related Topics
Managing User Policies
When you select Traffic Management > Policies > User Policies, you can add user policies, add sub user policies, and add rules to user policies as explained in the following sections:
•
Adding User Policies
Step 1
The User Policies screen appears displaying the currently configured user policies.
Step 2
The User Policies screen appears displaying the User Policy tab.
Step 3
Step 4
Step 5
Note
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
The user policy is saved in the configuration.
Related Topics
•
Adding Sub User Policies
Step 1
The User Policies screen appears displaying the currently configured user policies.
Step 2
The User Policy screen appears displaying the Policy, Sub User Policies, and Rules for the user policy.
Step 3
Step 4
Related Topics
•
Adding Rules to User Policies
Step 1
The User Policies screen appears displaying the currently configured user policies.
Step 2
The User Policy screen appears displaying the Profile, Sub User Policies, and Rules for the user policy you selected.
Step 3
The Add User Policy Service Rule screen appears.
Step 4
Step 5
•
•
Note
•
–
–
–
ToS—Choose the ToS marker for all the packets in either the Upstream or Downstream flow.
Bandwidth Controller—Choose the BWC (bandwidth controller) for the Upsteam and Downstream flow. This sets up bandwidth metering of all flows mapped to this rule, based on the characteristics of the BWC.
Limit Bandwidth per flow—Enter a value (in Kpbs) for the maximum per-flow bandwidth stream.
Step 6
The new user policy service rule is saved in the configuration.
Related Topics
•
Adding User Bandwidth Controllers
After you have defined global controllers, you can add user BWCs to policies and map these user BWCs to different global controllers.
A User BWC controls user bandwidth consumption for upstream or downstream flows. It controls and measures the bandwidth of an aggregation of traffic flows of a service or group of services.
Each package has its own set of BWCs that determine the bandwidth available per policy user for each available service.
The two Primary BWCs, one for upstream traffic and one for downstream traffic, allocate bandwidth to specific users, depending upon the Committed Information Rate (CIR), the Peak Information Rate (PIR), and the User relative priority settings. You can configure these parameters, but the Primary BWCs cannot be deleted.
There are two default BWCs, one for upstream traffic and one for downstream traffic. By default, all services are mapped to one of these two BWCs. The BWC mechanism controls rate sub partitioning within the default BWC rate control, based on the CIR, PIR, and AL. You can configure these parameters, but the default BWCs cannot be deleted.
Step 1
The User Policies screen appears displaying the currently configured user policies.
Step 2
The User Policy screen appears displaying the Profile, Sub User Policies, and Rules for the user policy you selected.
Step 3
The User Policies screen appears displaying the Bandwidth Controllers tab.
Step 4
The Bandwidth Controller—Upstream or the Bandwidth Controller—Downstream dialog box appears, depending on what you selected to add.
Step 5
a.
b.
c.
d.
e.
f.
Step 6
Step 7
Step 8
Related Topic
•
Editing User Bandwidth Controllers
There are two default BWCs, one for upstream traffic and one for downstream traffic. By default, all services are mapped to one of these two BWCs. The BWC mechanism controls rate sub partitioning within the default BWC rate control, based on the CIR, PIR, and AL. You can configure these parameters, but the default BWCs cannot be deleted.
Step 1
The User Policies screen appears displaying the currently configured user policies.
Step 2
The User Policy screen appears displaying the Profile, Sub User Policies, and Rules for the user policy you selected.
Step 3
The User Policies screen appears displaying the Bandwidth Controllers tab.
Step 4
Step 5
Step 6
Step 7
Related Topic
•
Managing Global Settings
You can determine various system parameters that control:
•
•
•
•
Selecting the System Mode
Note
Step 1
The System Mode screen appears.
Step 2
•
•
•
Step 3
The system mode is changed.
Effect of Burst Traffic on System Mode
When operating in Full Functionality mode, if the NME-APA is overloaded with a burst of traffic that it cannot process, diversion is explicitly disabled by the NME-APA. As a result, the NME-APA does not work in Full Functionality mode, but goes into Transparent mode. This is a transient condition. After 300 seconds, the NME-APA returns automatically to Full Functionality mode. At this time however, if the overloaded condition persists the NME-APA returns to Transparent mode for an additional 300 seconds.
The following message appears on the NME-APA console when the overloaded condition is detected:
e1000_clean_rx_irq_ps::Massive overload detected. BVI FIFO size is more than 50331648 bytes...send_rbcp_message:workqueue::DIVERSION IS DISABLED, NME-APA is not inline now. Not receiving any packets.send_rbcp_message:workqueue::DIVERSION will be enabled in 300 seconds. Clearing queue...The following message appears on the NME-APA console when the NME-APA returns to Full Functionality mode:
send_rbcp_message:workqueue::DIVERSION IS ENABLED, NME-APA is inline now. Processing resumed...Understanding System Mode versus ISR Diversion Mode
The integrated services router (ISR) that contains an NME-APA device has a "diversion mode" setting that is similar to the NME-APA system mode. This section explains the system behavior for each combination of the two settings.
When an NME-APA module is installed in an ISR router, the router administrator must set the APA diversion mode. The mode is set in the ISR CLI using the command:
service-module apa traffic-management [inline | monitoring]In monitoring mode, APA receives a "promiscuous" copy of the traffic that traverses the router. APA can look at the copy, but it does not have any effect on the actual traffic.
In inline mode, the router traffic is diverted to APA, and APA is expected to send it back to the ISR (possibly with some flows blocked or modified).
Table 3-4 explains the NME-APA system mode behavior for each of the two ISR diversion modes.
Managing Global Calendars
Calendars are used to divide the hours of the week into four time frames.
After you configure a calendar, you can add time-based rules to a package that uses the calendar. A time-based rule is a rule that applies to only one time frame. Time-based rules allow you to set rule parameters that apply only at specific times. You might, for example, want to define different rules for peak, off-peak, nighttime, and weekend usage.
Each service configuration includes one default calendar. You can add nine more calendars, each with a different time-frame configuration. You can use different calendars for different packages. You can also use different calendars where a service provider has customers in more than one time zone by configuring calendars with a one-hour offset from each other.
Related Topics
•
•
Adding Global Calendars
Step 1
The Global Calendars screen appears displaying the currently configured global calendars.
Step 2
The Calendar Details screen appears.
Step 3
Step 4
The new global calendar is added to the configuration.
Related Topics
•
Deleting Global Calendars
You can delete any user-added calendar. The default calendar cannot be deleted.
Note
Step 1
The Global Calendars screen appears displaying the currently configured global calendars.
Step 2
Step 3
The calendar is deleted.
Related Topics
•
•
Renaming Time Frames in Global Calendars
By default, the global calendar time frames are named T1, T2, T3, and T4. You can change these names at any time; for example, you may want to name the time frames Peak, Off Peak, Night, and Weekend.
Note
Step 1
The Global Calendars screen appears displaying the currently configured global calendars.
Step 2
Step 3
The Calendar Details screen appears. Each of the four Time Frames are listed next to a colored square. The colored grid, representing one week, is laid out in the format of 24 hours x 7 days. Each cell represents one hour.
Step 4
Step 5
Step 6
The updated calendar is saved in the configuration.
Related Topics
•
Configuring Time Frames in Global Calendars
By default, all the hours of the week belong to one time frame. APA allows you to assign each of the 168 (24x7) hours of the week to one of four separate time frames. These time frames allow you to supply time-dependent differentiated services and to impose constraints on any service.
You might want, for example, to divide the week as follows:
•
•
•
•
You can define different time frames for each calendar.
Step 1
The Global Calendars screen appears displaying the currently configured global calendars.
Step 2
Step 3
The Calendar Details screen appears. Each of the four Time Frames are listed next to a colored square. The colored grid, representing one week, is laid out in the format of 24 hours x 7 days. Each cell represents one hour.
Step 4
Step 5
Step 6
You have now mapped the week into four different time frames. The following figure illustrates a possible time partition plan:
Step 7
The changes are saved to the global calendar.
Related Topics
•
Configuring ToS Marking Settings
ToS (Type of Service) marking is used in IP networks as a means to signal the type and priority of a flow between network elements.
The default marking option is not to mark the packet. Because classification might take a few packets to finalize, it is important to note that if ToS marking is enabled, the first few packets might still be processed under the default option and therefore might not be marked.
Step 1
The ToS Marking screen appears.
Step 2
•
If you disable Upstream ToS Marking, it overrides filter rule and service rule settings.
•
If you disable Downstream ToS Marking, it overrides filter rule and service rule settings.
Step 3
Note
Note
Step 4
The ToS marking settings are saved in the configuration.
Related Topic
Understanding Redirection URLs
The rules for a class might deny access to selected protocols. When a user tries to access a blocked protocol, the traffic flow can be redirected to a server where a posted web page explains the reason for the redirection (for example, a "Silver" user trying to access a service available only to "Gold" users). This web page can offer subscribers the opportunity to upgrade their packages.
Related Topic
Adding Redirection URLs
By default, each redirection set contains one redirection option for each of three protocols: HTTP Browsing, HTTP Streaming, and RTSP Streaming. APA provides a default redirection set, which cannot be deleted. You can add up to 49 additional sets.
Each redirection URL includes the URL specified name, the Subscriber ID, and the Service ID in the following format:
<URL>?n=<subscriber-ID>&s=<service-ID>
Step 1
The Redirection URLs screen appears.
Step 2
The Redirection URL Set Details screen appears.
Step 3
Step 4
•
•
•
Step 5
Changes to the redirection URLs are saved in the configuration.
Related Topic
•
Editing Redirection URLs
Step 1
The Redirection URLs screen appears.
Step 2
Step 3
The Redirection URL Set Details screen appears.
Step 4
Step 5
The changes to the redirection URLs are saved to the configuration.
Related Topic
•
Deleting Redirection URLs
Step 1
The Redirection URLs screen appears.
Step 2
Step 3
The redirection URL set is deleted.
Related Topic
•
