[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


Configuring QoS Profile-Tracking Plug-Ins with the SRC CLI

Use the following configuration statements to configure the QoS profile tracking plug-in with the SRC CLI:

shared sae configuration plug-ins name name qos-profile-tracking {
threads threads; 

default-qos-profile default-qos-profile; 

separator separator; 

qos-profile-prefix qos-profile-prefix; 

service-selection-attribute service-selection-attribute; 

search-filter search-filter; 

invisible-qos-service invisible-qos-service; 

qos-profile-parameter-name qos-profile-parameter-name; 
}

  1. From configuration mode for the QoS profile tracking plug-in.
  2. user@host# edit shared sae configuration plug-ins name QosTracking 
    qos-profile-tracking 
    
    
    
  3. Configure the number of working threads that all QTP instances share when they process QTP events.
  4. [edit shared sae configuration plug-ins name QosTracking qos-profile-tracking]
    
    user@host# set threads threads 
    
    
    
  5. Configure the name of the QoS profile that is attached to the interface when QoS services have been deactivated.

See Reestablishing Default QoS Profile.

[edit shared sae configuration plug-ins name QosTracking qos-profile-tracking]
user@host# set default-qos-profile default-qos-profile 

  1. Configure the character that is placed between QoS profile input values when the system concatenates the values during the process of creating QoS profile names.
  2. [edit shared sae configuration plug-ins name QosTracking qos-profile-tracking]
    
    user@host# set separator separator 
    
    
    
  3. Configure the prefix added to the QoS service name as part of the process to determine the name of the QoS profile that needs to be attached to an interface for a particular service.
  4. [edit shared sae configuration plug-ins name QosTracking qos-profile-tracking]
    
    user@host# set qos-profile-prefix qos-profile-prefix 
    
    
    
  5. Configure the name of the attribute in the service definition that you want the QTP to use as QoS profile input values.
  6. [edit shared sae configuration plug-ins name QosTracking qos-profile-tracking]
    
    user@host# set service-selection-attribute service-selection-attribute 
    
    
    
  7. Configure the search filter that the SAE uses to search service objects in the directory to find QoS services.

See Configuring Search Filters for QoS Profile-Tracking Plug-Ins

[edit shared sae configuration plug-ins name QosTracking qos-profile-tracking]
user@host# set search-filter search-filter 

  1. Configure the name of the hidden QoS profile attachment service that the QTP uses to attach QoS profiles to and remove QoS profiles from a router interface.
  2. [edit shared sae configuration plug-ins name QosTracking qos-profile-tracking]
    
    user@host# set invisible-qos-service invisible-qos-service 
    
    
    
  3. Configure the name of the variable parameter used in the QoS profile name field in the QoS profile attachment action of the policy group that is assigned to the hidden QoS service.
  4. [edit shared sae configuration plug-ins name QosTracking qos-profile-tracking]
    
    user@host# set qos-profile-parameter-name qos-profile-parameter-name 
    
    
    
  5. Verify your configuration.
  6. [edit shared sae configuration plug-ins name QosTracking 
    qos-profile-tracking]
    
    user@host# show 
    
    threads 1;
    
    default-qos-profile ;
    
    separator -;
    
    qos-profile-prefix qos-profile;
    
    service-selection-attribute serviceName;
    
    search-filter (attribute.trackPlug=);
    
    invisible-qos-service svc-qos-attach;
    
    qos-profile-parameter-name qpName;
    

Configuring Search Filters for QoS Profile-Tracking Plug-Ins

The SAE uses a search filter to search service objects in the directory to find QoS services. You can set up the filter to search the values of any attribute in the service object, such as service name, category, or tracking plug-in. The search is successful when a value matches the filter.

For information about obtaining a list of attribute names for the sspService object class, see the documentation for the LDAP schema in the SRC software distribution in the folder SDK/doc/ldap or on the Juniper Networks Web site at

http://www.juniper.net/techpubs/software/management/sdx

Configure the search filter in a format similar to the LDAP search filter. Table 5 lists the values that you can use for filters. Each filter string <filter> contains a simplified LDAP query.




Table 5: Settings for Filter Strings 
Filter String
Action

()

Matches no objects

(*)

Matches all objects

List of <attribute>= <value> pairs

<attribute>—Name of a property or attribute <ldapAttributeName>

<value>—One of the following

  • * (asterisk)
  • Explicit string
  • String that contains an *

Note: To define a special character (* & , ! | \ )in a string, precede it with the backslash symbol (\).

  • If <value> is *, checks for any value.
  • If <value> is an explicit string, checks whether any value of the property matches the string, regardless of case.
  • If <value> is a string that contains a *, checks whether any value of the property contains the string, regardless of case.

(&<filter><filter>...)

True if all filters match

(|<filter><filter>...)

True if at least one filter matches

(!<filter>)

True if the filter does not match


[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]