> RIP Technical Configuration Guide

Transcription

1 Ethernet Routing Switch 8600/8800 Engineering > RIP Technical Configuration Guide Avaya Data Solutions Document Date: Document Number: NN Document Version: 1.1

2 2010 Avaya Inc. All Rights Reserved. Notices While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. End User agree to indemnify and hold harmless Avaya, Avaya s agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked Web sites referenced within this site or documentation(s) provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product, while under warranty, is available to Avaya customers and other parties through the Avaya Support Web site: Please note that if you acquired the product from an authorized reseller, the warranty is provided to you by said reseller and not by Avaya. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER, AND AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS "YOU" AND "END USER"), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ("AVAYA"). Copyright Except where expressly stated otherwise, no use should be made of the Documentation(s) and Product(s) provided by Avaya. All content in this documentation(s) and the product(s) provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Third Party Components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party Terms"). Information regarding distributed Linux OS source code (for those Products that have distributed the Linux OS source code), and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: Trademarks The trademarks, logos and service marks ("Marks") displayed in this site, the documentation(s) and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the documentation(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-avaya trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support. Web site: Contact Avaya Support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is in the United States. For additional support telephone numbers, see the Avaya Web site: 2

3 Abstract The following provide configuration examples on configuring RIP on the Ethernet Routing Switch Note that these examples are included in the Release 3.5 Configuring IP Operation publication. Revision Control No Date Version Revised By Remarks 1 14/05/ JVE Initial Draft 2 12/22/ K. Marshall Rebranded Avaya 3

4 Table of Contents Figures... 5 Tables Overview: Configuring RIP on the ERS RIP support on the ERS RIP Configuration Steps Configuration Examples Base Configuration Spanning Tree in an ERS8600 Routed Network Configuring RIPv Supplying a Default Route ERS8600A Configuration: ERS8600B Configuration: ERS8600C Configuration: Using RIP Accept Policy: Using RIP Announce Policy Reference Documentation

5 Figures 5

6 Tables 6

7 Conventions This section describes the text, image, and command conventions used in this document. Symbols Tip Highlights a configuration or technical tip. Note Highlights important information to the reader. Warning Highlights important information about an action that may result in equipment damage, configuration or data loss. Text Bold text indicates emphasis. Italic text in a Courier New font indicates text the user must enter or select in a menu item, button or command: ERS T show running-config Output examples from Avaya devices are displayed in a Lucida Console font: ERS T show sys-info Operation Mode: Switch MAC Address: B0-00 PoE Module FW: Reset Count: 83 Last Reset Type: Management Factory Reset Power Status: Primary Power Autotopology: Enabled Pluggable Port 45: None Pluggable Port 46: None Pluggable Port 47: None Pluggable Port 48: None Base Unit Selection: Non-base unit using rear-panel switch sysdescr: Ethernet Routing Switch T-PWR HW:02 FW: SW:v Mfg Date: HW Dev:H/W rev.02 7

8 1. Overview: Configuring RIP on the ERS 8600 This document describes how to configure RIP and RIP Policies on the Ethernet Routing Switch The Routing Information Protocol (RIP) is an interior gateway protocol (IGP). RIP is one of a class of algorithms known as distance vector algorithms. The distance or hop count is used as the metric to determine the best path to a remote network or host where the hop count does not exceed 15 hops assuming a cost of one for each network. RIP uses broadcast User Datagram Protocol (UDP) data packets to exchange routing information. RIP sends routing information updates every 30 seconds. This update contains known networks and the distances (hop count) associated with each one. For RIPv1, no mask information is exchanged; the natural mask is always applied by the router receiving the update. For RIPv2, mask information is sent. If information about a network is not received for 90 seconds, the metric associated with the network is raised to infinity (U) the metric is set for 16 which means the network becomes unreachable. If information about a network is not received for 180 seconds (six update intervals), it is removed from the routing table. These default timers can be changed by configuring the RIP Interface Timeout Timer parameter and Holddown Timer parameters. 2. RIP support on the ERS8600 The Ethernet Routing Switch 8600 support fours RIP send modes that are configurable on all Router interfaces: 1. rip1comp Broadcast RIP-2 updates using RFC 1058 route consumption rules. This is the default setting on the Ethernet Routing Switch 8600 o Destination MAC is a broadcast, ff-ff-ff-ff-ff-ff o Destination IP is a broadcast for the network, i.e o RIP Update is formed as a RIP-2 update, including network mask o RIP version = 2 2. rip1 RIP updates compliant with RFC 1058 o Destination MAC is a broadcast, ff-ff-ff-ff-ff-ff o Destination IP is a broadcast for the network, i.e o RIP Update is formed as a RIP-1 update, no network mask included o RIP version = 1 3. rip2 Multicast RIP-2 updates o Destination MAC is a multicast, e o Destination IP is the RIP-2 Multicast address, o RIP Update is formed as a RIP-2 update including network mask o RIP version = 2 4. nosend No RIP updates are sent on the interface 8

9 In regards to receiving RIP updates, there are three choices: 1. rip1orrip2 Accepts RIPv1 or RIPv2 updates 2. rip1 Accepts RIPv1 updates only 3. rip2 Accepts RIPv2 updates only To configure the send mode, this is accomplished at the IP interface level using the following command: Example: config ip rip interface <IP address of interface> send-mode <notsend : rip1 : rip1comp : rip2> config ip rip send-mode rip2 To configure the receive mode, this is accomplished at the IP interface level again using the following command Example: config ip rip interface <IP address of interface> receive-mode <rip1 : rip2 : rip1orrip2> config ip rip interface receive-mode rip2 3. RIP Configuration Steps RIP can be configured on a VLAN or a brouter port basis. If configuring RIP on a VLAN, the following steps are performed Configure VLAN, add ports and STG group Enable RIP Disable supply RIP updates if required Disable listen for RIP updates if required **By default, RIP Split Horizon is enabled. By setting the Poison parameter to true, Poison Reverse is enabled. Enable Default Route Supply if a default route exists in the route table Default Route listen can be enabled to add a default route to the route table if advertised from another router Add in or out Route Policy Enable Triggered Updates if required Cost of the link. Enter a value of 1 to 15 where 1 is default. **If Split Horizon is invoked, IP routes learned from an immediate neighbor are not advertised back to the neighbor. If Poison Reverse is enabled, the RIP updates sent to a neighbor from whom a route is learned are "poisoned" with a metric of 16. Therefore, the receiver neighbor will ignore this route because the metric 16 indicates infinite hops in the network. These mechanisms are used to prevent routing loops. 9

10 4. Configuration Examples 4.1 Base Configuration In this example, we wish to Use IP Subnet VLANs to provide routing between VLAN 2 and VLAN 3 on port 1/48 connected to the BPS-2000 switch Configure the core port 2/7 as a Brouter port with RIP 1 Configure tagging on port 1/48 config ether 1/48 perform-tagging enable Tagging is required in order to support multiple VLANs on the same interface. 2 Configuration for Access VLAN 2 config vlan 2 create byipsubnet /24 config vlan 2 ports remove 1/1-1/48,2/1-2/8 member portmember This command creates VLAN = 2 using Spanning Tree Group = 1 and VLAN type of IP Subnet. If using another STG group, create the new STG group first, then add port 1/48 to the new STG group. These commands configure port 1/48 as a static member for VLAN 2 and removes all other potential members. config vlan 2 ports add 1/48 member portmember config vlan 2 ports add 1/48 member static config vlan 2 ip create /24 config vlan 2 ip rip enable config vlan 2 ip rip supply disable config vlan 2 ip rip listen disable This command adds the IP address of /24 to IP Subnet VLAN 2 This command enables RIP for VLAN 2 and disables RIP supply and listen. RIP supply and listen are not required as there is no Router attached to VLAN 2. 3 Configuration for Access VLAN 3 config vlan 3 create byipsubnet /24 This command creates VLAN = 3 using Spanning Tree Group = 1 and VLAN type of IP Subnet. If using another STG group, create the new STG group first, then add port 1/48 to the new STG group. 10

11 config vlan 3 ports remove 1/1-1/48,2/1-2/8 member portmember These commands configure port 1/48 as a static member for VLAN 2 and remove all other potential members. config vlan 3 ports add 1/48 member portmember config vlan 3 ports add 1/48 member static config vlan 3 ip create /24 config vlan 3 ip rip enable config vlan 3 ip rip supply disable This command adds the IP address of /24 to IP Subnet VLAN 3 This command enables RIP for VLAN 3 and disables RIP supply and listen. config vlan 3 ip rip listen disable 4 Configuration of Brouter port 1 config ethernet 2/7 ip create / This command adds the IP address of /30 to port 2/7using brouter VLAN = config ethernet 2/7 ip rip enable This command enables RIP on this interface. 5 Enable RIP Globally config ip rip enable ERS8600 Configuration File: PORT CONFIGURATION - PHASE I ethernet 1/48 perform-tagging enable VLAN CONFIGURATION vlan 1 ip igmp mrdisc mrdisc-enable disable vlan 2 create byipsubnet / vlan 2 ports remove 1/1-1/47,2/1-2/8,3/1-3/8 member portmember vlan 2 ports add 1/48 member portmember vlan 2 ports add 1/48 member static vlan 2 ports remove 1/1-1/47,2/1-2/8,3/1-3/8 member portmember vlan 2 ip create / mac_offset 0 vlan 2 ip rip enable vlan 2 ip rip listen disable vlan 2 ip rip supply disable vlan 3 create byipsubnet /

12 vlan 3 ports remove 1/1-1/47,2/1-2/8 member portmember vlan 3 ports add 1/48,3/1-3/8 member portmember vlan 3 ports add 1/48 member static vlan 3 ports remove 1/1-1/47,2/1-2/8 member portmember vlan 3 ip create / mac_offset 1 vlan 3 ip rip enable vlan 3 ip rip listen disable vlan 3 ip rip supply disable PORT CONFIGURATION - PHASE II ethernet 2/7 ip create / mac_offset 2 ethernet 2/7 ip rip enable IP ROUTE POLICY CONFIGURATION ip rip enable 4.2 Spanning Tree in an ERS8600 Routed Network In the example above, a brouter port was used to connect to the network core. A brouter port is a singleport VLAN that can route IP packets as well as bridge all non-routable traffic. The difference between a brouter port and a standard IP protocol-based VLAN configured to do routing is that the routing interface of the brouter port is not subject to the Spanning Tree state of the port. Hence, using brouter ports eliminates the Spanning Tree protocol from the backbone network. If VLAN connectivity is required in the core to support non-ip protocols, care must be taken to prevent blocked ports due to Spanning Tree. This could occur if using one Spanning Tree (STG) instance. 12

13 One solution to get around this issue is to use multiple Spanning Tree groups. Using multiple STGs can be used to eliminate loops at Layer 2 while still permitting Layer 2 and Layer 3 connectivity between devices. If using VLANs in the core, one should follow the following rules: 1. A VLAN can exist in only one STG 2. Use only one STG on Access Ports 3. Use many STGs on Trunk Port ports 4.3 Configuring RIPv2 When RIP is enabled on a VLAN or brouter port, the default settings are as follows: Send Mode: rip1compatible Receive Mode: rip1orrip2 Depending on the configuration required, you may want to force the Ethernet Routing Switch 8600 to only operate in RIPv1 or RIPv2 mode. In this example, we will configure the Ethernet Routing Switch 8600 to only operate in RIPv2 mode using the previous configuration example. In this case, use the following commands to add RIP version 2 to VLAN s 2 and 3 and the brouter port. 1 Configure RIPv2 to VLAN 2 config ip rip interface sendmode rip2 These two commands enable RIPv2 mode on the IP address used for VLAN 2. config ip rip interface receivemode rip2 2 Configure RIPv2 to VLAN 3 config ip rip interface sendmode rip2 These two commands enable RIPv2 mode on the IP address used for VLAN 3. config ip rip interface receivemode rip2 13

14 3 Configure RIPv2 to Brouter Port config ip rip interface send-mode rip2 These two commands enable RIPv2 mode to the IP address used for the brouter port. config ip rip interface receivemode rip2 4.4 Supplying a Default Route In this example, we wish to 4.5 Use brouter ports for all core links Configure port based VLANs for local networks. Configure ERS8600A to add a default route pointing to the Network Core and advertise the default route to ERS8600B and ERS8600C. ERS8600A Configuration: 1 Configuration for Access VLAN 2 config vlan 2 create byport 1 This command creates VLAN = 2 using Spanning Tree Group = 1. If using another STG group, create the new STG group first, then add port 1/48 to the new STG group. config vlan 2 ports add 1/48 This command adds the access port 1/48 to VLAN 2. config vlan 2 ip create /24 config vlan 2 ip rip enable config vlan 2 ip rip supply disable config vlan 2 ip rip listen disable This command adds the IP address of /24 to VLAN 2. This command enables RIP for VLAN 2 and disables RIP supply and listen. Unless there is an external router attached to VLAN 2, there is no need to supply nor listen for RIP updates. 14

15 2 Configuration of Brouter port 1 config ethernet 2/7 ip create / This command adds the IP address of /30 to port 2/7 using brouter VLAN = config ethernet 2/7 ip rip default-supply enable config ethernet 2/7 ip rip enable These commands enable RIP and will advertise a default route out this interface. Note: we still have to add a RIP Out-Policy for this interface in order to advertise the local default route. 3 Configuration of Brouter port 2 config ethernet 2/8 ip create / config ethernet 2/8 ip rip default-supply enable config ethernet 2/8 ip rip enable This command adds the IP address of /30 to port 2/8 using brouter VLAN = These commands enable RIP and will advertise a default route out this interface. Note: we still have to add a RIP Out-Policy for this interface in order to advertise the local default route. 4 Configuration of Brouter port 3 config ethernet 2/1 ip create / This command adds the IP address of /30 to port 2/8 using brouter VLAN = config ethernet 2/1 ip rip enable config ethernet 2/1 ip rip listen disable These commands enable RIP for this interface. For this interface, we will also disable RIP supply and listen. config ethernet 2/1 ip rip supply disable 5 Create the default route config ip static-route create /0 next-hop cost 1 This command creates the static default route. 6 Enable RIP Globally config ip rip enable 7 Create an IP Prefix config ip prefix-list "default" add-prefix /0 This command adds a prefix list named default with the default route address. This will be used for the Route Policy in Step 8. 8 Create a Route Policy config ip route-policy "default_route" seq 1 create config ip route-policy "default_route" seq 1 enable These commands create a route policy named default_route with a match for the IP Prefix list created in Step 7. 15

16 config ip route-policy "default_route" seq 1 action permit config ip route-policy "default_route" seq 1 match-network "default" 9 RIP Policy Configuration config ip rip interface outpolicy "default_route" config ip rip interface outpolicy "default_route" These two commands add the route policy created in Step 8 to the two core links to ERS8600B and ERS8600C from ERS8600A. 4.6 ERS8600B Configuration: 1 Configuration for Access VLAN 2 config vlan 2 create byport 1 This command creates VLAN = 2 using Spanning Tree Group = 1. If using another STG group, create the new STG group first, then add port 1/48 to the new STG group. config vlan 2 ports add 1/48 This command adds the access port 1/48 to VLAN 2. config vlan 2 ip create /24 config vlan 2 ip rip enable config vlan 2 ip rip supply disable This command adds the IP address of /24 to VLAN 2 These commands enable RIP for VLAN 2 and disables RIP supply and listen. config vlan 2 ip rip listen disable 2 Configuration of Brouter port 1 config ethernet 2/7 ip create / config ethernet 2/7 ip rip default listen enable This command adds the IP address of /30 to port 2/7 using brouter VLAN = These commands enable RIP and default route listen for this port. config ethernet 2/7 ip rip enable 3 Configuration of Brouter port 2 config ethernet 2/1 ip create / This command adds the IP address of /30 to port 2/1 using brouter VLAN = config ethernet 2/1 ip rip default-listen enable These commands enable RIP and default route supply and listen for this interface. config ethernet 2/1 ip rip default-supply 16

17 enable config ethernet 2/1 ip rip enable 4 Enable RIP Globally config ip rip enable 4.7 ERS8600C Configuration: 1 Configuration for Access VLAN 2 config vlan 2 create byport 1 This command creates VLAN = 2 using Spanning Tree Group = 1. If using another STG group, create the new STG group first, then add port 1/48 to the new STG group. config vlan 2 ports add 1/48 This command adds the access port 1/48 to VLAN 2. config vlan 2 ip create /24 config vlan 2 ip rip enable config vlan 2 ip supply disable This command adds the IP address of /24 to VLAN 2 This command enables RIP for VLAN 2 and disables RIP supply and listen. config vlan 2 ip listen disable 2 Configuration of Brouter port 1 config ethernet 2/8 ip create / config ethernet 2/8 ip rip default-listen enable This command adds the IP address of /30 to port 2/8 using brouter VLAN = These commands enable RIP and default route listen for this port. config ethernet 2/8 ip rip enable 3 Configuration of Brouter port 2 config ethernet 2/1 ip create / config ethernet 2/1 ip rip default-listen enable This command adds the IP address of /30 to port 2/1 using brouter VLAN = These commands enable RIP and default route supply and listen for this interface. config ethernet 2/1 ip rip default-supply enable config ethernet 2/1 ip rip enable 17

18 4 Enable RIP Globally config ip rip enable Configuration Files: ERS8600A: VLAN CONFIGURATION vlan 2 create byport 1 vlan 2 ports remove 1/1-1/47,2/1-2/8,3/1-3/8 member portmember vlan 2 ports add 1/48 member portmember vlan 2 ip create / mac_offset 0 vlan 2 ip rip enable vlan 2 ip rip listen disable vlan 2 ip rip supply disable PORT CONFIGURATION - PHASE II ethernet 2/1 ip create / mac_offset 3 ethernet 2/1 ip ospf metric 0 ethernet 2/1 ip rip enable ethernet 2/1 ip rip listen disable ethernet 2/1 ip rip supply disable ethernet 2/7 ip create / mac_offset 1 ethernet 2/7 ip rip enable ethernet 2/7 ip rip default-supply enable ethernet 2/8 ip create / mac_offset 2 ethernet 2/8 ip rip enable ethernet 2/8 ip rip default-supply enable IP PREFIX LIST CONFIGURATION ip prefix-list "default" add-prefix /0 masklenfrom 0 masklento 0 IP ROUTE POLICY CONFIGURATION 18

19 ip route-policy "default_route" seq 1 create ip route-policy "default_route" seq 1 enable ip route-policy "default_route" seq 1 action permit ip route-policy "default_route" seq 1 match-network "default" ip route-policy "default_route" seq 1 set-metric-type type2 ip route-policy "default_route" seq 1 set-nssa-pbit enable ip static-route create / next-hop cost 1 preference 5 ip rip enable ip rip interface send-mode rip2 ip rip interface send-mode rip2 ip rip interface send-mode rip2 RIP POLICY CONFIGURATION ip rip interface out-policy "default_route" ip rip interface out-policy "default_route" ERS8600B VLAN CONFIGURATION vlan 2 create byport 1 vlan 2 ports remove 1/1-1/47,2/1-2/8,3/1-3/8 member portmember vlan 2 ports add 1/48 member portmember vlan 2 ip create / mac_offset 0 vlan 2 ip rip enable vlan 2 ip rip listen disable vlan 2 ip rip supply disable PORT CONFIGURATION - PHASE II ethernet 2/1 ip create / mac_offset 2 ethernet 2/1 ip ospf metric 0 ethernet 2/1 ip rip enable ethernet 2/1 ip rip default-listen enable ethernet 2/1 ip rip default-supply enable 19

20 ethernet 2/7 ip create / mac_offset 1 ethernet 2/7 ip ospf metric 0 ethernet 2/7 ip rip enable ethernet 2/7 ip rip default-listen enable ethernet 2/7 ip rip default-supply enable ethernet 2/8 state disable IP ROUTE POLICY CONFIGURATION ip rip enable ERS8600C VLAN CONFIGURATION vlan 2 create byport 1 vlan 2 ip create / mac_offset 0 vlan 2 ip rip enable vlan 2 ip rip listen disable vlan 2 ip rip supply disable PORT CONFIGURATION - PHASE II ethernet 2/1 ip create / mac_offset 2 ethernet 2/1 ip ospf metric 0 ethernet 2/1 ip rip enable ethernet 2/1 ip rip default-listen enable ethernet 2/1 ip rip default-supply enable ethernet 2/2 state disable ethernet 2/8 ip create / mac_offset 1 ethernet 2/8 ip ospf metric 0 ethernet 2/8 ip rip enable ethernet 2/8 ip rip default-listen enable ethernet 2/8 ip rip default-supply enable IP ROUTE POLICY CONFIGURATION ip rip enable 20

21 4.8 Using RIP Accept Policy: RIP Accept policies can be used on the Ethernet Routing Switch 8600 to selectively accept routes from RIP updates. If no policies are defined, the default behavior is applied which will add all learned routes to the route table. A RIP Accept policy may be used to: Listen to RIP updates only from certain gateways Listen only for specific networks Assign a specific mask to be included with a network in the routing table, i.e. network summary In this example, we wish to use a RIP Accept policy on ERS8600A to create a single route that will point to ERS8600C for all networks configured on it. The accept policy will take in any network from to and create a single entry in the routing table on ERS8600A. In order to calculate the summary route, comparing the common bits in the address range derives the summary address. In this example, the range of IP addresses is from to The network address to use for this example will be /20. 1 Configure the IP Prefix List config ip prefix-list Prefix_1 addprefix /20 masklenfrom 20 masklento 32 This command creates a Prelist list named Prefix_1 with a IP range from to Configure the Route Policy config ip route-policy "rip_pol_1" seq 1 create config ip route-policy "rip_pol_1" seq 1 These commands configure a route policy named rip_pol_1 with match criteria using the IP Prefix configured in Step 1. This will have the effect of injecting one route of /20 into the route table. 21

22 enable config ip route-policy "rip_pol_1" seq 1 action permit config ip route-policy "rip_pol_1" seq 1 match-network "Prefix_1" config ip route-policy "rip_pol_1" seq 1 set-injectlist "Prefix_1" 3 Add the Route Policy to the appropriate RIP interfaces config ip rip interface inpolicy "rip_pol_1" These two commands add the Route Policy created in Step 2 to both RIP core ports. config ip rip interface inpolicy "rip_pol_1" ERS8600 Config File IP PREFIX LIST CONFIGURATION ip prefix-list "Prefix_1" add-prefix /20 masklenfrom 20 masklento 32 IP ROUTE POLICY CONFIGURATION ip route-policy "rip_pol_1" seq 1 create ip route-policy "rip_pol_1" seq 1 enable ip route-policy "rip_pol_1" seq 1 action permit ip route-policy "rip_pol_1" seq 1 match-network "Prefix_1" ip route-policy "rip_pol_1" seq 1 set-injectlist "Prefix_1" ip route-policy "rip_pol_1" seq 1 set-metric-type type2 ip route-policy "rip_pol_1" seq 1 set-nssa-pbit enable ip rip enable RIP POLICY CONFIGURATION ip rip interface in-policy "rip_pol_1" ip rip interface in-policy "rip_pol_1" 22

23 4.9 Using RIP Announce Policy In the previous configuration example, a RIP Accept policy was used on ERS8600A to insert a single route into its route table for all networks from ERS8600C. Instead of using an Accept Policy on ERS8600A, we could use an RIP Announce Policy on ERS8600C to announce a single route to both ERS8600A and ERS8600B for it local network range. Use the following configuration step to configure the RIP Announce Policy on ERS8600C. 1 Configure the IP Prefix List config ip prefix-list Prefix_1 addprefix /20 This command creates a Prelist list named Prefix_1 with an IP address of /20. 2 Configure the Route Policy config ip route-policy "Policy_Rip" seq 1 create config ip route-policy "Policy_Rip" seq 1 enable These commands configure a route policy named "Policy_Rip" with match criteria using the IP Prefix configured in Step 1. config ip route-policy "Policy_Rip" seq 1 action permit config ip route-policy "Policy_Rip" seq 1 set-injectlist "Prefix_1" 3 Add the Route Policy to the appropriate RIP interfaces config ip rip interface outpolicy "Policy_Rip" These two commands add the Route Policy created in Step 2 to both RIP core ports. config ip rip interface outpolicy "Policy_Rip" ERS8600C Configuration File IP PREFIX LIST CONFIGURATION ip prefix-list "Prefix_1" add-prefix /20 masklenfrom 20 masklento 20 IP ROUTE POLICY CONFIGURATION ip route-policy "Policy_Rip" seq 1 create ip route-policy "Policy_Rip" seq 1 enable ip route-policy "Policy_Rip" seq 1 action permit ip route-policy "Policy_Rip" seq 1 set-injectlist "Prefix_1" 23

24 ip route-policy "Policy_Rip" seq 1 set-metric-type type2 ip route-policy "Policy_Rip" seq 1 set-nssa-pbit enable ip rip enable RIP POLICY CONFIGURATION ip rip interface out-policy "Policy_Rip" ip rip interface out-policy "Policy_Rip" 24

25 5. Reference Documentation Publication Number C Rev 00 May 2003 Document Title 8000 Series Software Release Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. and are registered in the United States and other countries. All trademarks identified by, TM or SM are registered marks, trademarks, and service marks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. Avaya may also have trademark rights in other terms used herein. References to Avaya include the Nortel Enterprise business, which was acquired as of December 18,