redis in ospf w/prefix-list & route-maps

[mohAmed khAdr]

Hello,

Doing an OSPF redis lab I stuck on this:

1) static routes gets redis no problems.

2) connected routes does not get redis, even thou I have a prefix-list & route-map to match.

Pls. tell me what am missing?

Thx

mohAmed

PS: pls. see attached.

[Reza Sharifi]

Hi,

You don't need any route-map to redistribute connected routes.  Can you post "sh ip route"?

HTH

[mohAmed khAdr]

Reza,

Does it make a differnet what type OS network is confg?

The conneted routes are showing as O( area 0) and in the routing table.

!

  172.20.0.0/32 is subnetted, 4 subnets

O       172.20.255.65 [110/11] via 10.10.10.1, 00:01:04, FastEthernet0/0

O       172.20.255.97 [110/11] via 10.10.10.1, 00:01:04, FastEthernet0/0

O       172.20.255.1 [110/11] via 10.10.10.1, 00:01:04, FastEthernet0/0

O       172.20.255.33 [110/11] via 10.10.10.1, 00:01:04, FastEthernet0/0

!!

and why are they showing with a cost of 11...I have not add and cost value on the interface?

Thx.

mohamed

[Ryan Newell]

Mohamed,

I believe it has something to do with the following statement.

network 0.0.0.0 255.255.255.255 area 0

This command matches all connected interfaces.

R,

Ryan

[Reza Sharifi]

Hi Mohamed,

These are not connected routes.  They are OSPF learned routes.  Connected routes have a C instead of an O.

Can you post sh run?

HTH

[Ryan Newell · Accepted solution]

Is the output above from R1 or R2. According to the attachment I was lead to believe the output was from R2. It looks like the 0.0.0.0 network statement is causing R1 to advertise those networks to R2. Correct that and I also suggest modifying the prefix-list singo. The networks are all /32 so it should be ge 32 or le 32 would also work.

R,

Ryan

[mohAmed khAdr]

Ryan,

Yu za man!!!!!dude...you nail it....

!

take a look

     201.122.22.0/25 is subnetted, 1 subnets

C       201.122.22.0 is directly connected, Loopback1

     172.20.0.0/28 is subnetted, 4 subnets

O E2    172.20.255.64 [110/20] via 10.10.10.1, 00:00:18, FastEthernet0/0

O E2    172.20.255.96 [110/20] via 10.10.10.1, 00:00:18, FastEthernet0/0

O E2    172.20.255.0 [110/20] via 10.10.10.1, 00:00:18, FastEthernet0/0

O E2    172.20.255.32 [110/20] via 10.10.10.1, 00:00:18, FastEthernet0/0

!

R2#sh ip rou 172.20.255.65

Routing entry for 172.20.255.64/28

  Known via "ospf 1", distance 110, metric 20

  Tag 200, type extern 2, forward metric 10

  Last update from 10.10.10.1 on FastEthernet0/0, 00:02:56 ago

  Routing Descriptor Blocks:

  * 10.10.10.1, from 10.254.255.1, 00:02:56 ago, via FastEthernet0/0

      Route metric is 20, traffic share count is 1

      Route tag 200

they got redis...I recofig the network statemnets under OS...they hit the prefix-list & route-map...

Q: going forward: should I refrain from config the default network 0.0.0.0 255.255.255.255 area? under OSPF ?

And what sitution I should use it for?

!

wow...I am impressed.

Well said.

Thx

mohAmed

[Ryan Newell · Accepted solution]

Only refrain if you don't intend to add all connected networks to OSPF. Personally I prefer statements which match each interface (e.g. 172.20.225.64 0.0.0.0 area x). It gives more control over what networks are advertised and what interfaces will form adjacencies. 

So earlier I said change the prefix-list from le 28 to ge or le 32. The previous output from R2 showed /32 masks for 172.20.255.x. Now I realize those are loopback interfaces without point-to-point ospf network type applied.

Are you studying for a test?

Ryan

[mohAmed khAdr]

Yes sir...R&S ie written....

Any tips, practice Qs  or reading material  will be greatly appricated.

Thx again

mohamed