Related Documentation
Configuring PCMM Policies and Parameter Substitutions (SRC CLI)
This topic describes how to define your SRC policies and parameter substitutions so that they comply with the PCMM Web service interface. The sample data shows the types of policies and parameters that you can configure. View the sample data with the following command:
If you use parameter substitutions, the PCMM Web service interface provides the values for the substitutions. You must name your parameters as specified in this topic.
Configuring Classify-Traffic Conditions for Dynamic Service Activator
Table 1 lists the classify-traffic condition fields that you can configure for PCMM classifiers that will be used with PCMM Web service interface. It also provides the parameter names that you must use if you configure parameter substitutions for the classifier.
Table 1: Parameter Names for Classify-Traffic Conditions
Field | Parameter Name |
---|---|
Protocol | protocol |
Source IP Address | sourceIpAddress |
Source IP Mask | sourceIpMask |
Port | sourcePortStart and sourcePortEnd destinationPortStart and destinationPortEnd |
Destination IP Address | destinationIpAddress |
Destination IP Mask | destinationIpMask |
Configuring FlowSpec Actions for Dynamic Service Activator
You can use a FlowSpec action to specify the traffic profile in CommitResource messages. Table 2 lists the fields that you can use for PCMM policies that will be used with PCMM Web service interface. It also provides the parameter names that you must use if you configure parameter substitutions for the FlowSpec action.
Table 2: Parameter Names for FlowSpec Actions
Field | Parameter Name |
---|---|
Service Number | serviceNumber |
Token Bucket Rate | bucketRate |
Token Bucket Size | bucketDepth |
Peak Data Rate | peakRate |
Minimum Policed Unit | minPolicedUnit |
Maximum Packet Size | maxDatagramSize |
Rate | reservedRate |
Slack Term | slackTerm |
Configuring Service Class Name Actions for Dynamic Service Activator
You can use a service class name action to specify the traffic profile in CommitResource messages. Table 3 lists the field that you can use for PCMM policies that will be used with PCMM Web service interface. It also provides the parameter names that you must use if you configure parameter substitutions for a service class name action.
Table 3: Parameter Names for Service Class Actions
Field | Parameter Name |
---|---|
Service Class | TrafficClass |
Configuring DOCSIS Actions for Dynamic Service Activator
You can use a DOCSIS action to specify the priority and bandwidth in the traffic profile in CommitResource messages. Table 4 lists the fields that you can use for PCMM policies that will be used with PCMM Web service interface. It also provides the parameter names that you must use if you configure parameter substitutions for the DOCSIS action.
Table 4: Parameter Names for DOCSIS Actions
Field | Parameter Name |
---|---|
Traffic Priority | priority |
Maximum Sustained Traffic Rate | bandwidth |
Maximum Traffic Burst | bandwidth |
Minimum Reserved Traffic Rate | bandwidth |