Log in to the IPQoS-enabled application server, and create a new IPQoS configuration file with a .qos extension.
For example, you would create the /var/ipqos/BigAPPS.qos file for the application server. Begin with the following required phrases to start the action statement that invokes the ipgpc classifier:
fmt_version 1.0 action { module ipgpc name ipgpc.classify params { global_stats TRUE } |
For an explanation of the opening action statement, refer to How to Create the IPQoS Configuration File and Define Traffic Classes.
Create classes to select traffic from three applications on the BigAPPS server.
Add the class definitions after the opening action statement.
class { name smtp enable_stats FALSE next_action markAF13 } class { name news next_action markAF21 } class { name ftp enable_stats TRUE next_action meterftp } |
Creates a class that is called smtp, which includes email traffic flows to be handled by the SMTP application
Enables statistics collection for the smtp class. However, because the value of enable_stats is FALSE, statistics for this class are not taken.
Instructs the ipgpc module to pass packets of the smtp class to the markAF13 action statement after ipgpc completes processing.
Creates a class that is called news, which includes network news traffic flows to be handled by the NNTP application.
Instructs the ipgpc module to pass packets of the news class to the markAF21 action statement after ipgpc completes processing.
Creates a class that is called ftp, which handles outgoing traffic that is handled by the FTP application.
Enables statistics collection for the ftp class.
Instructs the ipgpc module to pass packets of the ftp class to the meterftp action statement after ipgpc completes processing.
For more information about defining classes, refer to How to Create the IPQoS Configuration File and Define Traffic Classes.
Define filter clauses to select traffic of the classes defined in Step 2.
filter { name smtpout sport smtp class smtp } filter { name newsout sport nntp class news } filter { name ftpout sport ftp class ftp } filter { name ftpdata sport ftp-data class ftp } } |
Gives the name smtpout to the filter.
Selects traffic with a source port of 25, the well-known port for the sendmail (SMTP) application.
Identifies the class to which the filter belongs, in this instance, class smtp.
Gives the name newsout to the filter.
Selects traffic with a source port name of nntp, the well-known port name for the network news (NNTP) application.
Identifies the class to which the filter belongs, in this instance, class news.
Gives the name ftpout to the filter.
Selects control data with a source port of 21, the well-known port number for FTP traffic.
Gives the name ftpdata to the filter.
Selects traffic with a source port of 20, the well-known port number for FTP data traffic.
Identifies the class to which the ftpout and ftpdata filters belong, in this instance ftp.
To define filters, refer to How to Define Filters in the IPQoS Configuration File.
To define forwarding behaviors for application traffic, refer to How to Configure Forwarding for Application Traffic in the IPQoS Configuration File.
To configure flow control by using the metering modules, refer to How to Configure Flow Control in the IPQoS Configuration File.
To configure flow accounting, refer to How to Enable Accounting for a Class in the IPQoS Configuration File.