A Virtual Router Schedule in the Practice of Creating Default Gateway

  ijett-book-cover  International Journal of Engineering Trends and Technology (IJETT)          
© 2013 by IJETT Journal
Volume-4 Issue-8                      
Year of Publication : 2013
Authors : K. Jayachandra , S. Prathap


K. Jayachandra , S. Prathap. "A Virtual Router Schedule in the Practice of Creating Default Gateway". International Journal of Engineering Trends and Technology (IJETT). V4(8):3319-3322 Jul 2013. ISSN:2231-5381. www.ijettjournal.org. published by seventh sense research group.


we tend to discuss on Dynamic Time adjust Reference Load equalization technique to reinforce the Virtual Router Redundancy Protocol with Dynamic load equalization feature to utilize the redundant VRRP Backup device, in order to share the traffic load. Virtual Router Redundancy Protocol acts as default entry for the hosts on the shared Ethernet segment. VRRP protocol doesn't support the feature of load equalization for each the incoming and outgoing traffic. during this case, the Master VRRP device monitors the length of the incoming traffic from a selected Virtual native space Network (VLAN) section and redirects the traffic to the Backup VRRP device incase if the Master VRRP device still has the existing session support ed the length of the flow of traffic and the variety of session through the Netflow cache information. whereas implementing Dynamic time correct reference Load equalization mechanism, the Master VRRP device redirects the traffic to Backup VRRP device thro ugh the ICMP airt message, encase there's an current session browsing the Master VRRP device by dynamically monitoring the Active Flow per Second parameter info through the Net flow cache data through the Layer three switch thereby achieving the Dynamic Load equalization feature with the utilization of existing Active Flow per Second timers to dynamically share the traffic load between the Master VRRP device and also the Backup VRRP device.


[1] J. Etienne, “VRRPd: overview, implementation and usage,” Ottawa Linux Symposium 2001, July 2001.
[2] J. Ranta, “Router Redundancy and Scalability Using Clustering,” Seminar on Internetworking, Spring 2004, eds. A. Ylä - Jääski, N. Kasinskaja, [Online] Available: http://www.tml.hut.fi/Studies/T - 110.551/2004/papers/Ranta.pdf , J une 2004.
[3] R. Hinden, D. Mitzel, P. Hunt, P. Higginson, M. Shand, A. Lindem, S. Knight, D. Weaver and D. Whipple, “Virtual Router Redundancy Protocol,” Internet Draft, draft - ietfvrrpspec - v2 - 06.txt, Feburary 2002.
[4] [VRRP] R. Hinden, Ed., “Virtual Rou ter Redundancy Protocol,” RFC 3768, April 2004.
[5] [VRRP] S. Knight, D. Weaver, D.Whipple, R.Hinden, D. Mitzel, P. Hunt, P. Higginson, M. Shand, and A. Lindem, “Virtual Router Redundancy Protocol,” RFC 2338, April 1998.
[6] [HSRP] T. Li, B. Cole, P. Mort on and D. Li, “Cisco Hot Standby Router Protocol (HSRP),” RFC 2281, March 1998.
[7] [ICMP] J. Postel, “Internet Control Message Protocol,” RFC 792, September 1981.
[8] [ARP] D. Plummer, “An Ethernet Address Resolution Protocol,” RFC 826, November 1982.
[9 ] VRRPd Linux Implementation, ImageStream Internet Solution, Inc., http://www.imagestream.com/VRRP.html
[10] Chariot, NetIQ Corporation, http://www.netiq.com/products/chr/default.asp
[11] Gentoo Linux, Gentoo Foundation, Inc., http://www.gentoo.org
[12] Avalanche 220™ and Reflector 220™, Spirent Communications, http://www.spirentcom.com

schedule, Gateway, Protocol, Router