To control the rate at which a particular traffic flow is released onto the network, you must define parameters for the meter. You can use either of the two meter modules, tokenmt or tswtclmt, in the IPQoS configuration file.
This next procedure continues to build the IPQoS configuration file for the application server in Example 6, Sample IPQoS Configuration File for an Application Server. In the procedure, you configure the meter and two marker actions that are called within the meter action statement.
Before You Begin
The procedure assumes that you have already defined a class and a filter for the application to be flow-controlled.
For more information, see Using Your Assigned Administrative Rights in Securing Users and Processes in Oracle Solaris 11.4.
Begin making changes after the following marker action:
action { module dscpmk name markAF21 params { global_stats FALSE dscp_map{0-63:18} next_action continue } }
action { module tokenmt name meterftp
Invokes thetokenmt meter.
Assigns the name meterftp to the action statement.
params { committed_rate 50000000 committed_burst 50000000
Assigns a transmission rate of 50,000,000 bps to traffic of the ftp class.
Commits a burst size of 50,000,000 bits to traffic of the ftp class.
For an explanation of tokenmt parameters, refer to Configuring tokenmt as a Two-Rate Meter.
red_action markAF31 green_action_name markAF22 global_stats TRUE } }
Indicates that when the traffic flow of the ftp class exceeds the committed rate, packets are sent to the markAF31 marker action statement.
Indicates that when traffic flows of class ftp conform to the committed rate, packets are sent to the markAF22 action statement.
Enables metering statistics for the ftp class.
For more information about traffic conformance, see Meter Module.
action { module dscpmk name markAF31 params { global_stats TRUE dscp_map{0-63:26} next_action continue } }
Invokes the marker module dscpmk.
Assigns the name markAF31 to the action statement.
Enables statistics for the ftp class.
Assigns a DSCP of 26 to the packet headers of the traffic class ftp whenever this traffic exceeds the committed rate.
Indicates that no further processing is required on packets of the traffic class ftp, and that these packets can return to the network stream.
The DSCP of 26 instructs the marker to set all entries in the dscp map to the decimal value 26 (binary 011010). The DSCP of 26 sets the AF31 per-hop behavior. The marker marks packets of the ftp traffic class with the DSCP of 26 in the DS field.
AF31 assures that all packets with a DSCP of 26 receive a low-drop precedence but with only Class 3 priority. Therefore, the possibility of nonconformant FTP traffic being dropped is low. Figure 4, Table 4, Assured Forwarding Codepoints lists possible AF codepoints.
action { module dscpmk name markAF22 params { global_stats TRUE dscp_map{0-63:20} next_action continue } }
Assigns the name markAF22 to the marker action.
Assigns a DSCP of 20 to the packet headers of the traffic class ftp whenever ftp traffic conforms to its configured rate.
The DSCP of 20 tells the marker to set all entries in the dscp map to the decimal value 20 (binary 010100). The DSCP of 20 sets the AF22 per-hop behavior. The marker marks packets of the ftp traffic class with the DSCP of 20 in the DS field.
AF22 assures that all packets with a DSCP of 20 receive a medium-drop precedence with Class 2 priority. Therefore, conformant FTP traffic is assured a medium-drop precedence among flows that are simultaneously released by the IPQoS system. However, the router gives a higher forwarding priority to traffic classes with a Class 1 medium-drop precedence mark or higher. Figure 4, Table 4, Assured Forwarding Codepoints lists possible AF codepoints.
See How to Start the ipqos Service for specific instructions about starting or restarting the service.
See General IPQoS Configuration Planning Task Map for a list of additional changes that might be needed.