11/1/11 How to Set DiffServ over MPLS Test-Bed on Linux Routers? _ MPLS Tutorial 1/3 mplstutorial.com/how-set-diffserv-over-mpls-test-bed-linux-routers mpls tutorial Home Programming Tutorials Ebizon Ebizon Blogs Objective C Tutorial for Beginners make a donaWion Wo VXppoUW Whe ViWe XVeU login UVeUname: * PaVVZoUd: * LRg iQ Create new account Request new password naYigaWion Home India Hotel Site Technology Blogs Programming Q/A, Tutorials UecenW blog poVWV Jquery HTML() Learning PHP Language Hashes in Ruby, Perl and Java more Home ª MPLS Tutorial how to set diffserv over mpls test-bed on linux routers? 8.1 network topology The topology of the test-network is as follows: Fig. 8.1 Network Topology This topology is primarily chosen since it is the simplest topology possible with which MPLS local path protection mechanism can be demonstrated and its efficiency compared. All the machines used are Intel machines with RedHat-9 as the Operating System. All the links are 100Mbps links, but the bandwidth has been throttled to 60Mbps between B-C and E-F, 20Mbps between C-D and 40Mbps between C-E and E-D. The throttling of bandwidth is used to give the network a more realistic look, and hence make the DiffServ provisioning more realistic. 8.2 configuring the network All the five machines within the DiffServ over MPLS domain were configured as follows: 1)IPtables utility was installed. 2) Linux kernel-2.4.18 was patched with MPLS and DiffServ patch and compiled from scratch. Also, the kernel was patched with Hierarchical Token Bucket (HTB) queuing discipline (Qdisc) since it is only supported on kernel versions greater than equal to 2.4.20. 3)Then the IProute2 package was installed. 4)Following this, RSVP-TE daemon [19] was compiled and configured on all the machines. (Note: Although the compilation and configuration procedure has been specified at http://dsmpls.atlantis.ugent.be/files/installation_rsvpd-0.70-rc2.txt, it is recommended that the procedure specified in Appendix A be followed, since quite a few changes had to be made to make the things work, especially if HTB support is to be compiled in.) 5)The SNMP software [20] was installed on each machine. The configuration file snmpd.conf was edited in each case and proper IP addresses with community names were added. (NOTE: It is important to include perl module support while configuring the net-SNMP software. These perl modules are essential for the mib2c tool which is of significant importance while trying to extend the net-SNMP agents support for MIBs (which can either be standard MIBs, not supported by the software or non-standard MIBs which have been written for experimental purpose.) In addition to all this, GateDs OSPF [21,22] routing daemon was installed on all 7 machines. The configuration files for the OSPF can be found in Appendix B. For the sake of simplicity, all the machines have been configured to be on the backbone area. For the purpose of synchronizing the clocks of the sender and the receiver for enabling accurate delay and jitter measurements, Network Time Protocol (NTP) has been used. The configuration files for NTP [23] can be