Configure RIPv2 on an Advanced Routing Engine
Table of Contents
Expand All
|
Collapse All
Next-Generation Firewall Docs
-
Cloud Management of NGFWs
- Cloud Management of NGFWs
- PAN-OS 10.0 (EoL)
- PAN-OS 10.1
- PAN-OS 10.2
- PAN-OS 11.0 (EoL)
- PAN-OS 11.1 & Later
- PAN-OS 9.1 (EoL)
-
-
-
- Configure a Filter Access List
- Configure a Filter Prefix List
- Configure a Filter Community List
- Configure a BGP Filter Route Map
- Configure a Filter Route Maps Redistribution List
- Configure a Filter AS Path Access List
- Configure an Address Family Profile
- Configure a BGP Authentication Profile
- Configure a BGP Redistribution Profile
- Configure a BGP Filtering Profile
- Configure an OSPF Authentication Profile
- Configure a Logical Router
- Configure a Static Route
- Configure OSPF
- Configure BGP
- Configure an IPSec Tunnel
- Web Proxy
- Cheat Sheet: GlobalProtect for Cloud Management of NGFWs
-
PAN-OS 10.2
- PAN-OS 10.1
- PAN-OS 10.2
- PAN-OS 11.0 (EoL)
- PAN-OS 11.1 & Later
-
- 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
-
-
Cloud Management and AIOps for NGFW
- Cloud Management and AIOps for NGFW
- PAN-OS 10.0 (EoL)
- PAN-OS 10.1
- PAN-OS 10.2
- PAN-OS 11.0 (EoL)
- PAN-OS 11.1
- PAN-OS 11.2
- PAN-OS 8.1 (EoL)
- PAN-OS 9.0 (EoL)
- PAN-OS 9.1 (EoL)
Configure RIPv2 on an Advanced Routing Engine
Configure RIPv2 on an Advanced Routing Engine.
The Advanced Routing Engine supports RIPv2.
Consider
the RIPv2 Routing Profiles and filters that
you can apply to RIPv2 and thereby save configuration time and maintain
consistency. You can create profiles and filters in advance or as
you configure RIPv2.
- Configure a Logical Router.
- Enable RIPv2 and configure general settings.
- Select NetworkRoutingLogical Routers and select a logical router.
- Select RIPv2 and Enable it.
- Select advertise default route in RIP to advertise the default route even if it doesn’t exist in the RIB of the routing engine.
- If you want to apply BFD to RIPv2, select a BFD Profile you created, or select the default profile, or create a new BFD Profile. Default is None (Disable BFD).
- Select a Global General Timer or create a new RIPv2 Global Timer Profile.
- Select an Auth Profile or create a new RIPv2 Authentication Profile.
- Select a Redistribution Profile or create a new Redistribution Profile to redistribute IPv4 static routes, connected routes, BGP IPv4 routes, or OSPFv2 routes to RIPv2.
- Select a Global Inbound Distribute List to control the incoming routes accepted.
- Select an Global Outbound Distribute List to control the routes advertised to RIP neighbors.
- Configure an interface for RIPv2.
- Add an Interface by selecting one and Enable it.
- For Split Horizon, select one
of the following:
- split-horizon—Does not advertise a route back on the same interface where it was received.
- no-split-horizon—Disables split horizon.
- no-split-horizon-with-poison-reverse—Allows the advertisement back on the same interface where it was received and sets the metric for these routes to the maximum allowed for RIP, which is 16.
- Select the Mode:
- active—The interface will advertise networks and send RIP updates.
- passive—The interface will advertise networks, but not send RIP updates. (Useful if there are no RIP routers for the network, and therefore no reason to send RIP updates on the interface.)
- send-only—Can be used if the firewall is an end node and you only want to advertise a prefix to RIP, but use static routes or a default route to reach external prefixes.
- Select an Authentication profile if you want to override the profile you applied at the logical router level.
- By default, the interface will inherit the BFD profile you applied to the logical router for RIPv2 (Inherit-lr-global-setting). Alternatively, select a different BFD Profile, create a new BFD Profile, or select None (Disable BFD) to disable BFD for the interface.
- For Interface Inbound Distribute List, select an Access List to control the routes coming to this interface.
- Specify the Metric applied to incoming routes; range is 1 to 16.
- For Interface Outbound Distribute List, select an Access List to control the routes advertised out this interface to RIP neighbors.
- Specify the Metric to apply to advertised routes; range is 1 to 16.
- Click OK.
- Click OK.
- (Optional) Control RIP routes that are placed
in the global RIB.You might learn routes and redistribute them, but not want them in the protocol’s local route table or global RIB. You might want to add only specific routes to the global RIB.
- Select NetworkRoutingLogical Routers and select a logical router.
- Select RIB Filter to allow routes into or prevent routes from being added to the global RIB.
- To filter RIPv2 routes going to the RIB, in the IPv4 area, for RIP Route-Map, select a Redistribution Route Map or create a new one.
- Click OK.