Any kind of bandwith limiting or priority for specific network services ?

Question

I tried IPQoS to limit the bandwith for a ftp-service. This is very well documented in the IPQoS Administration Guide, but it seems to have no effect at all in my lan. The ftp-transfer still consumes all
available bandwith and any other interactive traffic like ssh is slow as hell. I think this is due to the fact that i do not have a diffserv capable router. Is it correct that IPQoS in Solaris 9 only marks packages but don't do anything else ?
My kstat output says:
"kstat -m tokenmt"
module: tokenmt instance: 10
name: tokenmt statistics class: meterftp
crtime 171043.6888275
epackets 0
green_bits 369888
green_packets 196
red_bits 205079496
red_packets 18160
snaptime 174628.7017885
yellow_bits 0
yellow_packets 0
Nearly all packets are marked red and the target for red packets is markAF31 with dscp_map{0-63:26}.
Strange to see that "kstat -m dscpmk" shows no results at all. This is possible a bug or not well
documented in the IPQoS Administration Guide.
Is there any (other) way to priorize interactive traffic or limit/shape the bandwith for specific services without additional Hardware in my network ?

Answer 1

You may have already resolved your problem, but here is what I've been using -- I'm just recently (like two days ago) trying IPQoS.
As you can see from my code I really restricted bandwith so I could see the reaction, and tested with a specific machine so it wouldn't mess with other stuff. Turn on ftp hash and watch it crawl. I've only tested outgoing so far, but will also test incoming.
We are not using DiffServ on our routers, so I just drop 'red' packets. I'm using yellow just to play and get stats.
Am looking for tools to read the flowacct data when I came across your post.
good luck!
fmt_version 1.0
# TEST configuration
# Monitor and gather ftp statistics from pilasvp101 (only)
# this host: ssrv194bw (163.241.195.249)
# this host: pilasrp101 (163.241.205.147)
# remote hosts: pilasvp101 (163.241.195.240)
action {
module ipgpc
name ipgpc.classify
params {
global_stats TRUE
class {
name ftp_traffic
enable_stats TRUE
next_action meter_ftp
filter {
name ftp_in
sport ftp
saddr 163.241.195.240
direction LOCAL_IN
ip_version V4
class ftp_traffic
filter {
name ftp_data_in
sport ftp-data
saddr 163.241.195.240
direction LOCAL_IN
ip_version V4
class ftp_traffic
filter {
name ftp_out
dport ftp
daddr 163.241.195.240
direction LOCAL_OUT
ip_version V4
class ftp_traffic
filter {
name ftp_data_out
dport ftp-data
daddr 163.241.195.240
direction LOCAL_OUT
ip_version V4
class ftp_traffic
# 10 Mbps, or 10000000 bits per second.
# 100 Mbps, or 100000000 bits per second.
# 1000 Mbps, or 1000000000 bits per second.
# USED BELOW:
# committed_rate - 100000 bits per second = 0.10 Mbps.
# committed_burst - 100000 bits per second = 0.10 Mbps.
# peak_rate - 150000 bits per second = 0.15 Mbps.
# peak_burst - 150000 bits per second = 0.15 Mbps.
# committed_rate - allowable transmission rate
# committed_burst - allowable burst size. Defines how many outgoing packets
# of a particular class can pass onto the network at the
# committed rate.
# peak_rate - peak rate in bits per second
# peak_burst - peak or excess burst size in bits. The peak burst parameter
# grants to a traffic class a peak-burst size that exceeds
# the committed rate.
# color_aware - turns on color-aware mode for tokenmt, which expects the
# bits to have already been modified for DSCP
# color_map - defines an integer array that maps DSCP values to
# green, yellow, or red.
# red_action - action to take when traffic flow exceeds peak rate
# yellow_action - the packet causes the flow to exceed its committed_rate
# but not its peak rate (committed_burst). This must be used
# if 'peak_rate' is defined.
# green_action - action to take for conforming traffic flow
# global_stats - enable metering stats for the class
action {
module tokenmt
name meter_ftp
params {
global_stats TRUE
committed_rate 100000
committed_burst 100000
peak_rate 150000
peak_burst 150000
red_action_name red_accounting
yellow_action_name yellow_accounting
green_action_name green_accounting
color_aware FALSE
# timer - scanning interval in milliseconds (default 15 seconds)
# timout - a flow "times-out" when its packets are no longer seen
# by the IPQoS system in milliseconds (default 60 seconds)
# max_limit - maximum number of entries a flow table can contain
action {
module flowacct
name red_accounting
params {
global_stats TRUE
timer 10000
timeout 10000
max_limit 2048
next_action drop
action {
module flowacct
name yellow_accounting
params {
global_stats TRUE
timer 10000
timeout 10000
max_limit 2048
next_action continue
action {
module flowacct
name green_accounting
params {
global_stats TRUE
timer 10000
timeout 10000
max_limit 2048
next_action continue
}