How to Configure the IPQoS Configuration File for an Applications Server

1. 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 applications server. Begin with the following required phrases to start the action statement that invokes the ipgpc classifier.

   fmtversion 1.0 action { module ipgpc name ipgpc.classify params { global_stats TRUE {

   For an explanation of the opening action statement, refer to How to Begin the IPQoS Configuration File and Define Traffic Classes.

2. 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 }

   Entry	Description
   name smtp	Creates a class that is called smtp, which includes email traffic flows to be handled by the SMTP application.
   enable_stats FALSE	Enables statistics taking for the smtp class. However, because the value of enable_stats is FALSE, statistics for this class are not turned on.
   next_action markAF13	Instructs the ipgpc module to pass packets of the smtp class to the markAF13 action statement after ipgpc completes processing.
   name news	Creates a class that is called news, which includes network news traffic flows to be handled by the NNTP application.
   next_action markAF21	Instructs the ipgpc module to pass packets of the news class to the markAF21 action statement after ipgpc completes processing.
   name ftp	Creates a class that is called ftp, which handles outgoing traffic that is handled by the FTP application.
   enable_stats TRUE	Enables statistics taking for the ftp class.
   next_action meterftp	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 Begin the IPQoS Configuration File and Define Traffic Classes.

3. Define filter clauses to select traffic of the previously defined classes.

   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 } }

   Entry	Description
   name smtpout	Gives the name smtpout to the filter
   sport smtp	Selects traffic with a source port of 25, the well-known port for the sendmail (SMTP) application
   class smtp	Identifies the class to which the filter belongs, in this instance, class smtp
   name newsout	Gives the name newsout to the filter
   sport nntp	Selects traffic with a source port name of nntp, the well-known port name for the network news application
   class news	Identifies the class to which the filter belongs, in this instance, class news
   name ftpout	Gives the name ftpout to the filter
   sport ftp	Selects control data with a source port of 21, the well-known port number for FTP traffic
   name ftpdata	Gives the name ftpdata to the filter
   sport ftp-data	Selects traffic with a source port of 20, the well-known port number for FTP data traffic
   class ftp	Identifies the class to which the ftpout and ftpdata filters belong, in this instance ftp

For more information about defining filters, refer to How to Define Filters in the IPQoS Configuration File.

Where to Go From Here