GE MDS ORBIT ECR, Technical Manual

Page: 298 / 463

298 MDS Orbit MCR/ECR Technical Manual MDS 05-6632A01, Rev. F
% set services qos classifier SFTP metric 5
The other way to solve the problem would to be use the not syntax and explicitly prevent the FROM1234
classifier from matching SFTP traffic.
% set services qos classifier FROM1234 match M1 ipv4 protocol not assigned-number tcp
% set services qos classifier FROM1234 match M2 ipv4 src-address address 1.2.3.4/32
% set services qos classifier FROM1234 match M2 ipv4 protocol assigned-number tcp
% set services qos classifier FROM1234 match M2 ipv4 dst-port services ssh not
This will make the FROM1234 classifier:
% show services qos classifier FROM1234
match-type any;
match M1 {
ipv4 {
protocol {
not;
assigned-number tcp;
}
src-address {
address
1.2.3.4/32;
}
}
}
match M2 {
ipv4 {
protocol {
assigned-number tcp;
}
src-address {
address
1.2.3.4/32;
}
dst-port {
not;
services [ ssh ];
}
}
}
This will make the classifier match everything from 1.2.3.4 that is not TCP and everything from 1.2.3.4
that is TCP and port is not SFTP. The coupling of ports to IP protocols complicates negating ports. Either
constricting higher priority rules with the not syntax or inverting the order classification is evaluated with
metric will work.
Example: Fairness
Taking the last example if we wanted to extend it so that all traffic from 1.2.3.4 is evaluated fairly, we
could apply a next policy to that class.
% set services qos policy FAIR fairness sfq
% set services qos policy Policy1 prioritization class HIGH next-policy FAIR
Now multiple traffic flows from 1.2.3.4 will be treated fairly.