The configuration of all 3 sections are spread out over different routers to expand the scope of the Lab. The third section will deal with QoS policy settings. The second section will deal with Traffic marking. The first section will deal with traffic classification. The configuration will be divided in 3 sections according to how QoS is implemented. You might need the help of a Linux admin if you intend to run this lab as you have to enable Web server, FTP server and Samba on the Linux machine. Windows XP is used as user and is connected to R5. I am using Ubuntu Studio as content source and it is connected to R1. If you are using a NAT interface simultaneously, the reachability will not be complete as then both interfaces will have default route, so shutdown the NAT interface. I am using only one interface on the virtualbox host for connecting it with the GNS3. OSPF is run on all links of all routers using network 0.0.0.0 255.255.255.255 area 0 command. The Loopbacks have been numbered as 1.1.x.1/32 where the 3rd octet is the router number. The ip addressing of the links is 1.1.x.x/24 where the 3rd octet is the router number combination of the link and the 4th octet is the router number. The topology consists of 6 7200s as represented in the diagram. PC with i7 processor and sufficient ram to run 6 routers and 2 Virtualbox guests.In GNS3, we get throughput of 1Mbps on all the links and thus we will configure our QOS policies below this value to test it properly. We must note here that although there are options for Gigabit interfaces and Fast Ethernet interfaces on GNS3 yet these are in reality simulated interfaces and thus do not give us the theoretical throughput. We can also use the relevant show commands to verify proper operations. We will rate limit some, prioritise some and remark some on our network and see its effects on the destination end. In this blog, we will cover basic user traffic like web, ftp and windows sharing and classifying them to mark for QOS treatment. The options for QOS testing are limited by your imagination. You can set bandwidth caps on certain protocols, you can prioritise certain protocols, you can remark certain protocols, etc. You can use actual user traffic and classify and mark it on your routers to give it preferential treatment. Now you do not have to rely on boring traffic to test QOS. It used to bother me a lot to run a network topology and rely on ping and tftp as test traffic for QOS. With the addition of Virtualbox to GNS3, you can do all sorts of simulations (except full switching) involving routers, firewalls, servers (windows or linux), applications, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |