Hello Riverbed,
the hierarchical QoS queueing would be much easier to configure if there was a way to specify classification rules in a similar manner.
Currently, if you can't grip all traffic for one queue in one classifier, the rule set for larger deployments grow quite large.
For example, instead of specifying
Rule 1: Source Net 192.168.1.0/24, dest Net 192.168.128.0/24 class interactive-location1
Rule 2: Source Net 192.168.2.0/24, dest Net 192.168.128.0/24 class low-priority-location1
Rule 3: Source Net 192.168.1.0/24, dest Net 192.168.130.0/24 class interactive-location2
Rule 4: Source Net 192.168.2.0/24, dest Net 192.168.130.0/24 class low-priority-location2
I would like a way to specify:
Rule1: Source Net 192.168.1.0/24 Dest Any --> interactive
Rule2: Source Net 192.168.2.0/24 Dest Any --> low priority
Rule3: Source Any Dest 192.168.128.0/24 --> location1
Rule4: Source Any Dest 192.168.130.0/24 --> location2
or a way to nest classifiers as in
Source 192.168.1.0/24 --> Group MyInteractive ! Important Hosts
Source 192.168.3.17/32 -> Group MyInteractive ! another important host
Group MyInteractive dest net 192.168.128.0/24 --> class interactive-location1
Group MyInteractive dest net 192.168.128.0/24 --> class interactive-location1
Sincerely
Hartwig Tronnier
