Use this procedure to open the Policy tab.
When you define multiple meters that may match the same traffic, you must specify the in-profile and out-of-profile traffic as drop or pass to ensure that the traffic is processed at the prescribed rate. If you do not do this, each meter processes the traffic, and this interaction can cause traffic to be treated in unexpected ways.
The following table outlines the parameters of the Policy tab.
Variable | Value |
---|---|
Id | Specifies the number of the QoS policy. |
Status | Allows you to enable or disable the policy. |
Name | Displays the name for the policy. |
ClassifierType | Specifies whether a classifier or a classifier block identifies traffic. |
ClassifierName | Specifies the name of the classifier or classifier block associated with this policy. |
InterfaceRoles | Specifies the interfaces to which the policy applies.
![]() You must configure the role combinations before you associate it with a policy. |
InterfaceIndex | Specifies the interface to which the policy is to be applied. A policy is associated with an interface explicitly using this attribute or implicitly using a role combination through the ntnQosPolicyInterfaceRole attribute. An interface must be identified by one and only one of these attributes. This attribute can identify an interface that does not currently exist in the system, as long as the specified interface index represents a potentially valid system interface.
![]() The InterfaceRoles and InterfaceIndex fields are mutually exclusive. When the InterfaceIndex field is not zero, the InterfaceRoles must be empty (select none when insert the policy). When the InterfaceRoles specifies a valid role combination, the InterfaceIndex field must be 0. |
Precedence | Specifies the order in which multiple policies are associated with the same interface. Policies with greater precedence have higher numbers.
![]() Policies with higher precedence values are applied before policies with lower precedence values. |
Meter | Specifies metering associated with this policy. Specifying a metering component causes any action criteria specified explicitly by the policy to be rejected as an error.
![]() You must configure meters before you associate them with a policy. |
InProfileAction | Identifies the action to be applied to traffic with this policy. This will not be used when a meter is specified.
![]() You must configure actions before you associate them with a policy. |
NonMatchAction | Identifies action taken for flows that do not match policy criteria. |
StatsType | Specifies statistics tracking:
|
SessionId | Specifies the numerical identification for the current session. |
Storage | Specifies the type of storage:
|
Version | Specifies the version. |
This section contains information about the following topics: