Create RIPv2 Routing Profiles
Table of Contents
Expand all | Collapse all
-
- Tap Interfaces
-
- Layer 2 and Layer 3 Packets over a Virtual Wire
- Port Speeds of Virtual Wire Interfaces
- LLDP over a Virtual Wire
- Aggregated Interfaces for a Virtual Wire
- Virtual Wire Support of High Availability
- Zone Protection for a Virtual Wire Interface
- VLAN-Tagged Traffic
- Virtual Wire Subinterfaces
- Configure Virtual Wires
- Configure an Aggregate Interface Group
- Configure Bonjour Reflector for Network Segmentation
- Use Interface Management Profiles to Restrict Access
-
- DNS Overview
- DNS Proxy Object
- DNS Server Profile
- Multi-Tenant DNS Deployments
- Configure a DNS Proxy Object
- Configure a DNS Server Profile
- Use Case 1: Firewall Requires DNS Resolution
- Use Case 2: ISP Tenant Uses DNS Proxy to Handle DNS Resolution for Security Policies, Reporting, and Services within its Virtual System
- Use Case 3: Firewall Acts as DNS Proxy Between Client and Server
- DNS Proxy Rule and FQDN Matching
-
- NAT Rule Capacities
- Dynamic IP and Port NAT Oversubscription
- Dataplane NAT Memory Statistics
-
- Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
- Enable Clients on the Internal Network to Access your Public Servers (Destination U-Turn NAT)
- Enable Bi-Directional Address Translation for Your Public-Facing Servers (Static Source NAT)
- Configure Destination NAT with DNS Rewrite
- Configure Destination NAT Using Dynamic IP Addresses
- Modify the Oversubscription Rate for DIPP NAT
- Reserve Dynamic IP NAT Addresses
- Disable NAT for a Specific Host or Interface
-
- Network Packet Broker Overview
- How Network Packet Broker Works
- Prepare to Deploy Network Packet Broker
- Configure Transparent Bridge Security Chains
- Configure Routed Layer 3 Security Chains
- Network Packet Broker HA Support
- User Interface Changes for Network Packet Broker
- Limitations of Network Packet Broker
- Troubleshoot Network Packet Broker
-
- Enable Advanced Routing
- Logical Router Overview
- Configure a Logical Router
- Create a Static Route
- Configure BGP on an Advanced Routing Engine
- Create BGP Routing Profiles
- Create Filters for the Advanced Routing Engine
- Configure OSPFv2 on an Advanced Routing Engine
- Create OSPF Routing Profiles
- Configure OSPFv3 on an Advanced Routing Engine
- Create OSPFv3 Routing Profiles
- Configure RIPv2 on an Advanced Routing Engine
- Create RIPv2 Routing Profiles
- Create BFD Profiles
- Configure IPv4 Multicast
- Create Multicast Routing Profiles
- Create an IPv4 MRoute
Create RIPv2 Routing Profiles
Create routing profiles for RIPv2 global timers, authentication,
and route redistribution on an Advanced Routing Engine.
The Advanced Routing Engine supports RIPv2;
create the following profiles to apply to the protocol. The profiles
can be used across multiple logical routers and virtual systems.
This topic describes the profiles and how to configure them.
- RIPv2 Global Timer Profiles—Specify RIPv2 update, expire, and delete intervals. Apply the profile in the RIPv2 general configuration.
- RIPv2 Interface Authentication Profiles—Specify RIPv2 authentication using a password or MD5; apply the profile in the RIPv2 general configuration.
- RIPv2 Redistribution Profiles—Specify how to redistribute IPv4 static routes, connected routes, BGP IPv4 routes, and OSPFv2 routes to RIPv2. Apply the profile in the RIPv2 general configuration.
- Create a RIPv2 Global Timer Profile.
- Select.NetworkRoutingRouting ProfilesRIPv2
- AddaRIPv2 Global Timer ProfilebyName(a maximum of 63 characters). The name must start with an alphanumeric character, underscore (_), or hyphen (-), and can contain a combination of alphanumeric characters, underscore, or hyphen. No dot (.) or space is allowed.
- SpecifyUpdate Intervalin seconds, which is the length of time between regularly scheduled Update messages; range is 5 to 2,147,483,647; default is 30.
- SpecifyExpire Intervalin seconds, which is the length of time that a route can be in the routing table without being updated; range is 5 to 2,147,483,647; default is 180. After the Expire Interval is reached, the route is still included in Update messages until the Delete Interval is reached.
- SpecifyDelete Intervalin seconds; range is 5 to 2,147,483,647; default is 120. When an expired route in the routing table reaches the Delete Interval, it is deleted from the routing table.
- ClickOK.
- Create a RIPv2 Authentication Profile.
- Select.NetworkRoutingRouting ProfilesRIPv2
- AddaRIPv2 Authentication ProfilebyName(a maximum of 63 characters). The name must start with an alphanumeric character, underscore (_), or hyphen (-), and can contain a combination of alphanumeric characters, underscore, or hyphen. No dot (.) or space is allowed.
- Specify thetypeof authentication:md5 (use RIP MD5 authentication method)orpassword (Simple password authentication).
- ForSimple password authentication, enter thePassword(a maximum of 16 characters) andConfirm Password.
- ForRIP MD5 authentication:
- Addan MD5 Key-ID; range is 0 to 255.
- Enter theKey(a maximum of 16 alphanumeric characters) andConfirm Key.
- Selectuse this key when sending packetto make this key the Preferred key.
- ClickOK.
- Create a RIPv2 Redistribution Profile to specify any combination of IPv4 static routes, connected routes, BGP IPv4 routes, and OSPFv2 routes to redistribute to RIPv2.
- Select.NetworkRoutingRouting ProfilesRIPv2
- AddaRIPv2 Redistribution ProfilebyName(a maximum of 63 characters). The name must start with an alphanumeric character, underscore (_), or hyphen (-), and can contain a combination of alphanumeric characters, underscore, or hyphen. No dot (.) or space is allowed.
- SelectIPv4 Staticto allow configuration of this portion of the profile.
- Enablethe IPv4 static redistribution portion of the profile.
- Specify theMetricto apply to the static routes being redistributed into RIPv2 (range is 1 to 65,535).
- Select aRedistribute Route-Mapor create a new Redistribute Route Map whose match criteria control which IPv4 static routes to redistribute into RIPv2. Default isNone. If the route map Set configuration includes a Metric Action and Metric Value, they are applied to the redistributed route. Otherwise, the Metric configured on this redistribution profile is applied to the redistributed route.
- SelectConnectedto allow configuration of this portion of the profile.
- Enablethe connected route redistribution portion of the profile.
- Specify theMetricto apply to the connected routes being redistributed into RIPv2 (range is 1 to 65,535).
- Select aRedistribute Route-Mapor create a new Redistribute Route Map. Default isNone. If the route map Set configuration includes a Metric Action and Metric Value, they are applied to the redistributed route. Otherwise, the Metric configured on this redistribution profile is applied to the redistributed route.
- SelectBGP AFI IPv4to allow configuration of this portion of the profile.
- Enablethe BGP IPv4 route redistribution portion of the profile.
- Specify theMetricto apply to the BGP routes being redistributed into RIPv2 (range is 0 to 4,294,967,295).
- Select aRedistribute Route-Mapor create a new Redistribute Route Map. Default isNone. If the route map Set configuration includes a Metric Action and Metric Value, they are applied to the redistributed route. Otherwise, the Metric configured on this redistribution profile is applied to the redistributed route.
- SelectOSPFv2to allow configuration of this portion of the profile.
- Enablethe OSPFv2 route redistribution portion of the profile.
- Enablethe IPv4 default route redistribution portion of the profile.
- Specify theMetricto apply to the default route being redistributed into RIPv2 (range is 0 to 4,294,967,295).
- Select aRedistribute Route-Mapor create a new Redistribute Route Map. Default isNone.If the route map Set configuration includes a Metric Action and Metric Value, they are applied to the redistributed route. Otherwise, the Metric configured on this redistribution profile is applied to the redistributed route.
- ClickOK.