Go to main content

Managing IP Quality of Service in Oracle® Solaris 11.3

Exit Print View

Updated: October 2017
 
 

How to Configure the IPQoS Configuration File for an Application Server

  1. Become an administrator.

    For more information, see Using Your Assigned Administrative Rights in Securing Users and Processes in Oracle Solaris 11.3.

  2. Log in to the IPQoS-enabled application server.
  3. Create a new IPQoS configuration file with a .qos extension.
  4. Insert 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.

  5. Add class definitions to select traffic from three applications on the BigAPPS server.
        class {
            name smtp
            enable_stats FALSE
            next_action markAF13
        }
        class {
            name news
            next_action markAF21
        }
        class {
            name ftp
            enable_stats TRUE
            next_action meterftp
        }
    name smtp

    Creates a class called smtp that includes email traffic flows to be handled by the SMTP application

    enable_stats FALSE

    Enables statistics collection for the smtp class. However, because the value of enable_stats is FALSE, statistics for this class are not taken.

    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 called news that 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 called ftp that handles outgoing traffic that is handled by the FTP application.

    enable_stats TRUE

    Enables statistics collection 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 Create the IPQoS Configuration File and Define Traffic Classes.

  6. 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
        }
    }
    name smtpout

    Assigns the name smtpout to the filter.

    sport smtp

    Selects traffic with a source port of 25, the usual port for the sendmail (SMTP) application.

    class smtp

    Identifies the class to which the filter belongs, in this instance, class smtp.

    name newsout

    Assigns the name newsout to the filter.

    sport nntp

    Selects traffic with a source port name of nntp, the usual port name for the network news (NNTP) application.

    class news

    Identifies the class to which the filter belongs, in this instance, class news.

    name ftpout

    Assigns the name ftpout to the filter.

    sport ftp

    Selects control data with a source port of 21, the usual port number for FTP traffic.

    name ftpdata

    Assigns the name ftpdata to the filter.

    sport ftp-data

    Selects traffic with a source port of 20, the usual port number for FTP data traffic.

    class ftp

    Identifies the class to which the ftpout and ftpdata filters belong, in this instance ftp.

  7. Save changes to the /etc/inet/ipqosinit.conf file.