PointRed Telecom Ltd. MCRD-2458 ユーザーズマニュアル
M i c r o R e d & M i c r o V i e w N M S U s e r M a n u a l v 1 . 0
Page 90
Figure 86. Parallel Classes
Classes 'ftp_traffic_in_ftp1' and 'ftp_traffic_in_ftp2' are considered
Parallel
Classes,
as far as the incoming interface flow of ath0 is concerned. This is
because they don't form a hierarchy and hence, for every arriving packet, both of
them are evaluated against it. Classes 'ftp_traffic_out_ftp1' and
'ftp_traffic_out_ftp2' are also parallel classes, as far as the outgoing interface
flow of ath0 is concerned.
them are evaluated against it. Classes 'ftp_traffic_out_ftp1' and
'ftp_traffic_out_ftp2' are also parallel classes, as far as the outgoing interface
flow of ath0 is concerned.
Parallel classes, although very convenient feature, should be used with caution.
By all means, you should avoid setting parallel classes that overlap each
other. In other words, it should be clear which class will be activated for every
arriving packet. For instance, the two classes depicted at picture 87 are
overlapping, cause is ambiguous which one will handle traffic originating within
subnet 172.8.1.0/24 and destined to host 192.168.1.1/32 with destination port
number 200.
By all means, you should avoid setting parallel classes that overlap each
other. In other words, it should be clear which class will be activated for every
arriving packet. For instance, the two classes depicted at picture 87 are
overlapping, cause is ambiguous which one will handle traffic originating within
subnet 172.8.1.0/24 and destined to host 192.168.1.1/32 with destination port
number 200.