PointRed Telecom Ltd. MCRD-2458 Manuale Utente

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 89

Figure 85. Single class per policy

Up to now, we guarantee 3mbps for FTP traffic coming from any of the directly 
connected subnets, and destined to the other one. However, we make no 
provisions for users (of either subnet), who might set up an FTP server on their 
own initiative. Such FTP servers can consume part of the 3mbps quota, which is 
reserved for the two original FTP servers. If we want to prevent this, we will 
have to be more specific when defining our classes. In particular: 

1.

We rename ‘ftp_traffic_out’ to ‘ftp_traffic_out_ftp1’ to handle traffic destined 
to FTP server 192.168.1.220. We change the destination address to 
192.168.1.220/ 32. We leave the FTP application type to FTP. 

2.

Similarly, we rename ‘ftp_traffic_in’ to ‘ftp_traffic_in_ftp1’ to handle traffic 
originating for FTP server 192.168.1.220. Therefore, we change the source 
address to 192.168.1.220/ 32. The FTP application type of TARGET remains 
as it is. 

3.

In a similar manner, we create two new classes, named ‘ftp_traffic_out_ftp2’ 
and ‘ftp_traffic_in_ftp2’ to handle traffic originated from/ destined to 
192.168.1.190/ 32 (Picture 86). We also set the TARGET application type to 
FTP.

4.

Since we divided the total CIR/ PIR of the initial classes (one for each 
direction) in two classes, we have also to redefine the CIR/ PIR on each 
subclass to 1500/ 1750. This way, for each direction the policy guarantees an 
aggregated CIR of 3000 and an aggregated PIR of 3500.