Pages

network cisco ccna gns3 certification arteq

network cisco ccna gns3 certification arteq
a network runs through it

Search insearchofthecert

Showing posts with label default-information originate. Show all posts
Showing posts with label default-information originate. Show all posts

Sunday, November 4, 2012

default-information originate (always)..

default-information originate (OSPF)

To generate a default external route into an OSPF routing domain, use the default-information originate command in router configuration mode


Whenever you use the redistribute or the default-information router configuration command to redistribute routes into an OSPF routing domain, the Cisco IOS software automatically becomes an Autonomous System Boundary Router (ASBR). However, an ASBR does not, by default, generate a default route into the OSPF routing domain. The software still must have a default route for itself before it generates one, except when you have specified the always keyword

and this:


There are two ways to inject a default route into a normal area.
  1. If the ASBR already has the default route in its routing table, you can advertise the existing 0.0.0.0/0 into the OSPF domain with the default-information originate router configuration command.
  2. If the ASBR doesn't have a default route, you can add the keyword always to the default-information originate command (default-information originate always).

    This command will advertise a default route into the OSPF domain, regardless of whether it has a route to 0.0.0.0. Another benefit of adding always keyword is that it can add stability to the internetwork. For example, if the ASBR is learning a default route from another routing domain such as RIP and this route is flapping, then without the always keyword, each time the route flaps, the ASBR will send a new Type 5 LSA into the OSPF domain causing some instability inside the OSPF domain. With the always keyword, the ASBR will advertise the default inside the OSPF domain always, and thus the flapping of the default route from the RIP domain will not cause any instability inside the OSPF domai

Saturday, December 24, 2011

rip defect route propagation...

simply rip, 2 routers connected serially to 1... notice the gateway of last resort is not set...  if you follow the output you'll see default-information originate put to good use in a rip environment... might save some typing...

r2620_01(config)#do sh run | begin  router rip
router rip
 network 1.0.0.0
 network 10.0.0.0


r2620_01#sh ip route


Gateway of last resort is not set

     1.0.0.0/24 is subnetted, 1 subnets
C       1.1.1.0 is directly connected, Loopback0
R    2.0.0.0/8 [120/1] via 10.0.20.2, 00:00:20, Serial0/0
R    3.0.0.0/8 [120/1] via 10.0.30.2, 00:00:04, Serial0/1
     10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
C       10.0.30.0/24 is directly connected, Serial0/1
C       10.0.30.2/32 is directly connected, Serial0/1
C       10.0.20.2/32 is directly connected, Serial0/0
C       10.0.20.0/24 is directly connected, Serial0/0

r2620_01#

r2620_02#sh ip route

Gateway of last resort is not set

R    1.0.0.0/8 [120/1] via 10.0.20.1, 00:00:27, Serial0/0
     2.0.0.0/24 is subnetted, 1 subnets
C       2.2.2.0 is directly connected, Loopback0
R    3.0.0.0/8 [120/1] via 10.0.20.1, 00:00:27, Serial0/0
     10.0.0.0/8 is variably subnetted, 5 subnets, 3 masks
R       10.0.30.0/24 [120/1] via 10.0.20.1, 00:00:27, Serial0/0
R       10.0.30.2/32 [120/1] via 10.0.20.1, 00:00:27, Serial0/0
C       10.0.20.0/24 is directly connected, Serial0/0
C       10.0.20.1/32 is directly connected, Serial0/0
r2620_02#


r2620_03#sh ip route


Gateway of last resort is not set

R    1.0.0.0/8 [120/1] via 10.0.30.1, 00:00:24, Serial0/0
R    2.0.0.0/8 [120/1] via 10.0.30.1, 00:00:24, Serial0/0
     3.0.0.0/24 is subnetted, 1 subnets
C       3.3.3.0 is directly connected, Loopback0
     10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
C       10.0.30.0/24 is directly connected, Serial0/0
C       10.0.30.1/32 is directly connected, Serial0/0
R       10.0.20.2/32 [120/1] via 10.0.30.1, 00:00:24, Serial0/0
R       10.0.20.0/24 [120/1] via 10.0.30.1, 00:00:24, Serial0/0
r2620_03#

r2620_01(config)#router rip
r2620_01(config-router)#default-information originate
r2620_01(config-router)#end
r2620_01#


r2620_02#sh ip route


Gateway of last resort is 10.0.20.1 to network 0.0.0.0
R    1.0.0.0/8 [120/1] via 10.0.20.1, 00:00:11, Serial0/0
     2.0.0.0/24 is subnetted, 1 subnets
C       2.2.2.0 is directly connected, Loopback0
R    3.0.0.0/8 [120/1] via 10.0.20.1, 00:00:11, Serial0/0
     10.0.0.0/8 is variably subnetted, 5 subnets, 3 masks
R       10.0.30.0/24 [120/1] via 10.0.20.1, 00:00:11, Serial0/0
R       10.0.30.2/32 [120/1] via 10.0.20.1, 00:00:11, Serial0/0
C       10.0.20.0/24 is directly connected, Serial0/0
C       10.0.20.1/32 is directly connected, Serial0/0
R*   0.0.0.0/0 [120/1] via 10.0.20.1, 00:00:11, Serial0/0

r2620_03#sh ip route

Gateway of last resort is 10.0.30.1 to network 0.0.0.0

R    1.0.0.0/8 [120/1] via 10.0.30.1, 00:00:19, Serial0/0
R    2.0.0.0/8 [120/1] via 10.0.30.1, 00:00:19, Serial0/0
     3.0.0.0/24 is subnetted, 1 subnets
C       3.3.3.0 is directly connected, Loopback0
     10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
C       10.0.30.0/24 is directly connected, Serial0/0
C       10.0.30.1/32 is directly connected, Serial0/0
R       10.0.20.2/32 [120/1] via 10.0.30.1, 00:00:19, Serial0/0
R       10.0.20.0/24 [120/1] via 10.0.30.1, 00:00:19, Serial0/0
R*   0.0.0.0/0 [120/1] via 10.0.30.1, 00:00:19, Serial0/0
r2620_03#


so rip propagated some default routes as noted by the asterisks in the output of  r2 and r3... sigh... but not on r1... this is very exciting...

r2620_01#sh ip route

Gateway of last resort is not set

     1.0.0.0/24 is subnetted, 1 subnets
C       1.1.1.0 is directly connected, Loopback0
R    2.0.0.0/8 [120/1] via 10.0.20.2, 00:00:20, Serial0/0
R    3.0.0.0/8 [120/1] via 10.0.30.2, 00:00:20, Serial0/1
     10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
C       10.0.30.0/24 is directly connected, Serial0/1
C       10.0.30.2/32 is directly connected, Serial0/1
C       10.0.20.2/32 is directly connected, Serial0/0
C       10.0.20.0/24 is directly connected, Serial0/0
r2620_01#