default-information originate
The default-information originate command injects a default route into a RIP routing domain, typically used to provide internet or WAN connectivity to downstream routers.
Definition: default-information originate is a Cisco IOS router config command. The default-information originate command injects a default route into a RIP routing domain, typically used to provide internet or WAN connectivity to downstream routers.
Overview
The `default-information originate` command is a powerful tool in Cisco IOS that injects a default route (0.0.0.0/0) into a Routing Information Protocol (RIP) routing domain. This command is essential for providing connectivity to external networks, such as the internet or a corporate WAN, to downstream routers that rely on RIP for routing updates. In many network designs, a border router connects to an upstream provider or a central site and learns a default route via static configuration, dynamic routing protocols like BGP, or DHCP. Without `default-information originate`, RIP would not advertise this default route to other RIP-speaking routers, leaving them without a path to destinations outside the RIP domain. The command essentially tells RIP to generate and propagate a default route, ensuring that all routers in the RIP network can reach external networks by forwarding traffic to the originating router.
The networking concept behind this command is the controlled distribution of a default route. In RIP, routes are learned from neighbors and advertised based on the routing table. However, a default route is not automatically redistributed into RIP unless explicitly configured. The `default-information originate` command creates a RIP route for 0.0.0.0/0 with a metric that can be set using the `metric` keyword. This is different from simply configuring a static default route and relying on redistribution; the command is specifically designed for RIP and ensures the default route is advertised even if the router does not have a default route in its routing table (though typically it does). It is commonly used in hub-and-spoke topologies where the hub router has connectivity to external networks and needs to provide internet access to spoke routers running RIP.
When would you reach for this command versus alternatives? If you are running RIP and need to advertise a default route, this is the most straightforward method. Alternatives include using `redistribute static` if you have a static default route, but that requires careful filtering to avoid redistributing other static routes. Another option is to use a route map to match the default route and then redistribute it, but that adds complexity. The `default-information originate` command is simpler and more targeted. In contrast, for OSPF, the equivalent command is `default-information originate`, which works similarly but with OSPF-specific parameters. For EIGRP, you would use `ip default-network` or redistribute a static default route. So, for RIP, this command is the go-to solution.
In the broader network configuration workflow, this command is typically applied on the router that acts as the gateway to external networks. After configuring the default route (e.g., via static route or BGP), you enter RIP configuration mode and issue `default-information originate`. You may also set the metric to influence path selection. Verification involves checking the RIP database with `show ip rip database` or `show ip route` to confirm the default route is present and being advertised. Troubleshooting may involve checking if the default route is being received by neighbors using `debug ip rip` or `show ip rip database`.
Important IOS behaviors: The command is available in router configuration mode for RIP. It does not require any special privilege level beyond the standard 15 for configuration. The command takes effect immediately and is saved to the running configuration. If you omit the `metric` keyword, RIP uses a default metric of 1 (or the metric set by the `default-metric` command under router rip). The command can be removed with `no default-information originate`. Note that if the router does not have a default route in its routing table, the command will still inject a default route into RIP updates, but it may be less meaningful. Also, the command does not affect the router's own routing table; it only influences RIP advertisements.
default-information originateWhen to Use This Command
- Inject a default route from a border router into a RIP network to provide internet access to internal routers.
- Advertise a default route from a corporate headquarters router to branch offices running RIP.
- Ensure that stub networks can reach external networks without static default routes on each router.
- Redistribute a default route learned via another protocol (e.g., BGP) into RIP for downstream routers.
Parameters
| Parameter | Syntax | Description |
|---|---|---|
| metric | <0-16> | Specifies the metric value for the default route. Valid values are from 0 to 16, where 16 is considered unreachable. If not specified, the default metric is 1 (or the value set by the default-metric command). Common mistake: setting a metric too high (e.g., 16) will cause the route to be considered unreachable and not installed in neighbors' routing tables. |
| route-map | WORD | Specifies a route map to filter or modify the default route advertisement. The route map can be used to set conditions such as metric, tag, or next-hop. Common mistake: forgetting to create the route map before referencing it, which results in the command being rejected. |
Command Examples
Basic default route injection into RIP
Router(config-router)# default-information originateRouter# show ip route rip
Codes: R - RIP, O - OSPF, C - connected, S - static
10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
R 10.1.1.0/24 [120/1] via 192.168.1.2, 00:00:12, GigabitEthernet0/0
R* 0.0.0.0/0 [120/1] via 192.168.1.1, 00:00:05, GigabitEthernet0/0The output shows RIP routes. The line starting with 'R*' indicates a default route (0.0.0.0/0) learned via RIP. The '*' denotes the default route. The metric is 1 (hop count), next-hop is 192.168.1.1, and the route was learned 5 seconds ago via GigabitEthernet0/0.
Default route with metric override
Router(config-router)# default-information originate metric 5Router# show ip route rip
Codes: R - RIP, O - OSPF, C - connected, S - static
10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
R 10.1.1.0/24 [120/1] via 192.168.1.2, 00:00:12, GigabitEthernet0/0
R* 0.0.0.0/0 [120/5] via 192.168.1.1, 00:00:08, GigabitEthernet0/0The default route now shows a metric of 5 (instead of the default 1). This can be used to influence path selection, making the default route less preferred than other routes.
Understanding the Output
When you use 'show ip route rip', the output lists all RIP-learned routes. Each line starts with 'R' for RIP routes, and an asterisk '*' indicates a candidate default route. The format is: [administrative distance/metric] via next-hop, time since last update, outgoing interface.
For the default route, the network is 0.0.0.0/0. A healthy default route should have a reasonable metric (typically 1-15 for RIP) and a recent timestamp (under 30 seconds). If the route disappears or shows a high metric, the originating router may be unreachable or the metric has been artificially increased.
Watch for multiple default routes with different metrics, which could cause suboptimal routing.
Configuration Scenarios
Inject a default route from a border router to provide internet access to spoke routers
A company has a hub-and-spoke network using RIP. The hub router (R1) has a default route to the internet via a static route. Spoke routers (R2, R3) need to reach the internet through R1. The goal is to advertise the default route into RIP so that spokes can forward internet traffic to R1.
Topology
Internet---(Gi0/0)R1(Gi0/1)---192.168.1.0/30---(Gi0/0)R2
R1(Gi0/2)---192.168.2.0/30---(Gi0/0)R3Steps
- 1.Step 1: Configure a static default route on R1 pointing to the internet gateway: R1(config)# ip route 0.0.0.0 0.0.0.0 203.0.113.1
- 2.Step 2: Enter RIP configuration mode: R1(config)# router rip
- 3.Step 3: Enable RIP on the interfaces connecting to spokes: R1(config-router)# network 192.168.1.0 and network 192.168.2.0
- 4.Step 4: Inject the default route into RIP: R1(config-router)# default-information originate
- 5.Step 5: Optionally set a metric: R1(config-router)# default-information originate metric 2
- 6.Step 6: Verify on R1: show ip route and show ip rip database
! R1 configuration ip route 0.0.0.0 0.0.0.0 203.0.113.1 ! router rip version 2 network 192.168.1.0 network 192.168.2.0 default-information originate metric 2 ! ! R2 configuration (minimal) router rip version 2 network 192.168.1.0
Verify: On R2, use 'show ip route' to see a default route via 192.168.1.1 (R1's interface). Expected output includes: 'R* 0.0.0.0/0 [120/2] via 192.168.1.1, 00:00:17, GigabitEthernet0/0'. Also 'show ip rip database' on R1 should show '0.0.0.0/0 auto-summary' and '0.0.0.0/0' with metric 2.
Watch out: If the static default route is not present on R1, the default-information originate command will still advertise a default route, but it may cause routing loops if R1 does not actually have a path. Always ensure the router has a valid default route before using this command.
Advertise a default route with a route map to control metric and tag
A network administrator wants to inject a default route into RIP but with a specific metric and tag for administrative purposes. A route map is used to set these attributes, allowing for more granular control over the advertisement.
Topology
R1(Gi0/0)---10.0.0.0/30---(Gi0/0)R2
R1(Gi0/1)---10.0.1.0/30---(Gi0/0)R3Steps
- 1.Step 1: Create a route map that sets the metric and tag: R1(config)# route-map DEFAULT permit 10
- 2.Step 2: Set the metric: R1(config-route-map)# set metric 3
- 3.Step 3: Set the tag: R1(config-route-map)# set tag 100
- 4.Step 4: Enter RIP configuration: R1(config)# router rip
- 5.Step 5: Enable RIP on interfaces: R1(config-router)# network 10.0.0.0 and network 10.0.1.0
- 6.Step 6: Inject default route with route map: R1(config-router)# default-information originate route-map DEFAULT
- 7.Step 7: Verify on R2: show ip route and show ip rip database
! R1 configuration route-map DEFAULT permit 10 set metric 3 set tag 100 ! router rip version 2 network 10.0.0.0 network 10.0.1.0 default-information originate route-map DEFAULT ! ! R2 configuration router rip version 2 network 10.0.0.0
Verify: On R2, 'show ip route' should show the default route with metric 3 (RIP hop count). 'show ip rip database' on R1 should show the default route with tag 100. Example: '0.0.0.0/0 auto-summary, metric 3, tag 100'.
Watch out: If the route map does not exist or is misconfigured, the default-information originate command will fail. Ensure the route map is created and permits the default route. Also, the route map must be applied before the command is issued.
Troubleshooting with This Command
When troubleshooting the `default-information originate` command, the primary focus is on whether the default route is being advertised and received correctly. A healthy scenario shows that the originating router has the default route in its routing table and that RIP is advertising it to neighbors. On the originating router, use `show ip route` to confirm the presence of a default route (e.g., 'S* 0.0.0.0/0 [1/0] via 203.0.113.1').
Then use `show ip rip database` to see if the default route appears as a RIP route. A healthy output includes an entry like '0.0.0.0/0 auto-summary' and '0.0.0.0/0' with a metric. If the default route is not in the RIP database, check if the command is configured: `show running-config | section router rip` should show `default-information originate`.
If it is missing, add it. On the receiving router, use `show ip route` to see if the default route is installed. It should appear as 'R* 0.0.0.0/0 [120/2] via <next-hop>'.
If not, check RIP neighbor relationships with `show ip rip neighbor` and ensure RIP updates are being exchanged. Use `debug ip rip` on the originating router to see if the default route is being sent in updates. Look for lines like 'RIP: sending v2 update to 224.0.0.9 via GigabitEthernet0/0' followed by '0.0.0.0/0 via 0.0.0.0, metric 2, tag 0'.
If the update is not sent, verify that the interface is included in the RIP network statement. Common symptoms include: the default route not appearing on neighbors, which could be due to a missing network statement, passive interface configuration, or access lists blocking RIP. Another symptom is the default route appearing but with an incorrect metric (e.g., metric 16, which is unreachable).
Check the metric value in the `default-information originate` command or the `default-metric` command. Also, if a route map is used, verify the route map permits the default route and sets the correct attributes. Use `show route-map` to confirm.
If the originating router does not have a default route in its routing table, the command will still advertise a default route, but it may cause routing loops. Ensure the router has a valid default route. Correlate with `show ip route` and `show ip protocols` to see RIP configuration.
A step-by-step diagnostic flow: 1) Check the originating router's routing table for a default route. 2) Verify the RIP configuration includes `default-information originate`. 3) Check the RIP database on the originating router. 4) On the receiving router, check the routing table and RIP database. 5) Use debug commands to see RIP updates. 6) Check for ACLs or distribute lists that might filter the default route. 7) Verify interface states and RIP neighbor relationships.
CCNA Exam Tips
CCNA exam tip: The 'default-information originate' command is used with RIP, but similar commands exist for OSPF and EIGRP; know the differences.
CCNA exam tip: Without this command, RIP does not propagate default routes even if one exists in the routing table.
CCNA exam tip: The metric can be set to influence path selection; the default metric is 1.
CCNA exam tip: This command is often used on a border router to provide internet access to internal RIP routers.
Common Mistakes
Mistake 1: Forgetting to configure a default route (e.g., ip route 0.0.0.0 0.0.0.0 <next-hop>) before using default-information originate; the command only works if a default route exists in the routing table.
Mistake 2: Using 'default-information originate' in OSPF context on a RIP router; the command is mode-specific.
Mistake 3: Setting an excessively high metric (e.g., 16) which makes the route unreachable (RIP max hop count is 15).
default-information originate vs show ip route
Although both commands are related to IP routing, 'default-information originate' is a configuration command used to inject a default route into RIP updates, while 'show ip route' is a verification command that displays the current routing table. They are often mentioned together when troubleshooting default route propagation or verifying routing information.
| Aspect | default-information originate | show ip route |
|---|---|---|
| Scope | Controls redistribution of default route into RIP | Displays entire IP routing table |
| Configuration mode | Router configuration (config-router) | Privileged EXEC (#) |
| Persistence | Persistent in running-config | Non-persistent; runtime output only |
| Output type | No immediate output; effects seen in routing updates | Detailed table of prefixes, next-hops, metrics, etc. |
| Trigger | Configures the router to originate default route in RIP | One-time snapshot of the routing table |
| Purpose | Provide default gateway info to RIP neighbors | Troubleshoot and verify routing knowledge |
Use default-information originate when you need to advertise a default route into a RIP domain from an edge router.
Use show ip route when you need to verify the current routing table contents or troubleshoot routing issues.
Platform Notes
In IOS-XE, the `default-information originate` command syntax and behavior are identical to classic IOS. The command is available under `router rip` configuration mode. Output formats for `show ip rip database` are similar, though IOS-XE may display additional fields like 'Uptime' in some versions.
In NX-OS, RIP is not supported; NX-OS uses EIGRP, OSPF, and BGP. There is no direct equivalent for RIP. For OSPF in NX-OS, the command is `default-information originate` under `router ospf`, with similar parameters.
For EIGRP, NX-OS uses `ip default-network` or redistribution. On the ASA platform, RIP is not supported; the ASA uses OSPF, EIGRP, and BGP. For OSPF on ASA, the command is `default-information originate` under `router ospf`.
In IOS-XR, RIP is not supported; IOS-XR uses OSPF, ISIS, and BGP. There is no RIP equivalent. Between IOS versions (12.x, 15.x, 16.x), the command syntax remains consistent.
However, in older IOS versions (12.x), the `route-map` parameter might not be available; it was introduced in later versions. Always check the documentation for your specific IOS version. In IOS 15.x and later, the command supports both `metric` and `route-map` parameters.
The behavior of the command is unchanged across versions. Note that in some IOS versions, if you do not specify a metric, the default metric is taken from the `default-metric` command under router rip, or if not set, it defaults to 1. This is consistent across versions.
Related Commands
show ip protocols
Displays the current state of all IP routing protocols running on the router, including timers, filters, and network advertisements.
show ip route
Displays the IP routing table showing all known routes, their source protocols, administrative distances, metrics, next-hops, and outgoing interfaces.
Practice for the CCNA 200-301
Test your knowledge with practice questions covering all CCNA 200-301 exam domains.
Practice CCNA 200-301 Questions