13.07.2015 Views

Administration of the Avaya G350 Media Gateway - Avaya Support

Administration of the Avaya G350 Media Gateway - Avaya Support

Administration of the Avaya G350 Media Gateway - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuring RIPRIPv1RIPv2The very simplicity <strong>of</strong> RIP has a disadvantage however. This protocol does not take into accountnetwork bandwidth, physical cost, and data priority. The <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong> supportstwo versions <strong>of</strong> RIP:●●RIPv1RIPv2RIPv1 is <strong>the</strong> original version <strong>of</strong> <strong>the</strong> RIP protocol. The RIPv1 protocol imposes some limitationson <strong>the</strong> network design with regard to subnetting. When operating RIPv1, you must not configurevariable length subnetwork masks (VLMS). Each IP network must have a single mask, implyingthat all subnetworks in a given IP network are <strong>of</strong> <strong>the</strong> same size. Also, when operating RIPv1,you must not configure supernets. RIPv1 is defined in RFC 1058.RIPv2 is a newer version <strong>of</strong> <strong>the</strong> RIP routing protocol. RIPv2 solves some <strong>of</strong> <strong>the</strong> problemsassociated with RIPv1. The most important change in RIPv2 is <strong>the</strong> addition <strong>of</strong> a subnetworkmask field which allows RIPv2 to support variable length subnetworks. RIPv2 also includes anau<strong>the</strong>ntication mechanism similar to <strong>the</strong> one used in OSPF. RIPv2 is defined in RFC 2453.Table 9: RIPv1 vs. RIPv2 on page 191 summarizes <strong>the</strong> differences between RIP and RIP2.Table 9: RIPv1 vs. RIPv2RIPv1Broadcast addressingTimer-based – updated every 30 secondsFixed subnetwork masksNo securityNo provision for external protocolsRIPv2Multicast addressingTimer-based – updated every 30 secondsVLSM support – subnet information transmittedSecurity (au<strong>the</strong>ntication)Provision for EGP/BGP (Route tag)Preventing routing loops in RIPYou can use <strong>the</strong> following features in RIP to help avoid routing loops:●Split-horizon● Poison-reverseThe split-horizon technique prevents information about routes from exiting <strong>the</strong> router interfacethrough which <strong>the</strong> information was received. This prevents small routing loops. Use <strong>the</strong>ip rip split-horizon command to enable <strong>the</strong> split-horizon mechanism. Use <strong>the</strong> no form<strong>of</strong> this command to disable <strong>the</strong> split-horizon mechanism. By default, split-horizon is enabled.Issue 3 January 2005 191

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!