RE: Route Tagging with Default Route

Hello Muzammil,

I just labbed this up and found that the OSPF 0/0 route was tagged along
with the others into RIP.
But I rechecked a few minutes later and the route tag for 0/0 was gone,
though it remained on the others.

Below you see some of the debug output from the redistributing router. I am
tagging 0/0 100 and all other OSPF routes 120. 0/0 is advertised with tag
100, then with tag 0.

Mar 1 00:37:30.735: RIP: sending v2 update to 224.0.0.9 via
FastEthernet0/1.17 (172.16.17.1)
Mar 1 00:37:30.739: RIP: build update entries
Mar 1 00:37:30.739: 0.0.0.0/0 via 0.0.0.0, metric 3, tag 100
<<<<<<<<<<<<<<<<
Mar 1 00:37:30.743: 3.3.3.0/24 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:30.747: 172.16.2.0/24 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:30.747: 172.16.10.0/25 via 0.0.0.0, metric 1, tag 0
Mar 1 00:37:30.751: 172.16.16.0/24 via 0.0.0.0, metric 1, tag 0
Mar 1 00:37:30.751: 172.16.20.0/24 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:30.751: 172.16.25.0/24 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:30.751: 172.16.28.0/22 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:30.751: 172.16.34.0/25 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:30.751: 172.16.40.0/25 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:30.751: 172.16.50.0/24 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:30.751: 172.16.62.0/24 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:30.751: 172.16.80.0/25 via 0.0.0.0, metric 2, tag 0
Mar 1 00:37:30.751: 172.16.88.0/24 via 0.0.0.0, metric 1, tag 0
Mar 1 00:37:30.751: 172.16.123.0/24 via 0.0.0.0, metric 1, tag 0
Mar 1 00:37:30.755: 172.16.140.0/24 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:35.155: RIP: received v2 update from 172.16.88.2 on
FastEthernet0/1.88
Mar 1 00:37:35.155: 172.16.80.0/25 via 0.0.0.0 in 1 hops
Mar 1 00:37:44.823: RT: NET-RED 0.0.0.0/0
Mar 1 00:37:46.751: RIP: sending v2 update to 224.0.0.9 via
FastEthernet0/1.88 (172.16.88.1)
Mar 1 00:37:46.755: RIP: build update entries
Mar 1 00:37:46.755: 0.0.0.0/0 via 0.0.0.0, metric 3, tag 0
<<<<<<<<<<<<<<
Mar 1 00:37:46.759: 3.3.3.0/24 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:46.763: 172.16.2.0/24 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:46.763: 172.16.10.0/25 via 0.0.0.0, metric 1, tag 0
Mar 1 00:37:46.767: 172.16.16.0/24 via 0.0.0.0, metric 1, tag 0
Mar 1 00:37:46.767: 172.16.17.0/24 via 0.0.0.0, metric 1, tag 0
Mar 1 00:37:46.767: 172.16.20.0/24 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:46.767: 172.16.25.0/24 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:46.767: 172.16.28.0/22 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:46.767: 172.16.34.0/25 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:46.767: 172.16.40.0/25 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:46.767: 172.16.50.0/24 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:46.767: 172.16.62.0/24 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:46.767: 172.16.77.0/24 via 0.0.0.0, metric 2, tag 0
Mar 1 00:37:46.771: 172.16.123.0/24 via 0.0.0.0, metric 1, tag 0
Mar 1 00:37:46.771: 172.16.140.0/24 via 0.0.0.0, metric 3, tag 120
Mar 1 00:37:46.827: RIP: sending v2 flash update to 224.0.0.9 via
FastEthernet0/1.17 (172.16.17.1)
Mar 1 00:37:46.831: RIP: build flash update entries
Mar 1 00:37:46.831: 0.0.0.0/0 via 0.0.0.0, metric 3, tag 0
<<<<<<<<<<<<<<<<<<<<
Mar 1 00:37:46.835: RIP: sending v2 flash update to 224.0.0.9 via
FastEthernet0/1.88 (172.16.88.1)
Mar 1 00:37:46.839: RIP: build flash update entries
Mar 1 00:37:46.843: 0.0.0.0/0 via 0.0.0.0, metric 3, tag 0
Mar 1 00:37:57.735: RIP: sending v2 update to 224.0.0.9 via
FastEthernet0/1.17 (172.16.17.1)
Mar 1 00:37:57.739: RIP: build update entries
Mar 1 00:37:57.739: 0.0.0.0/0 via 0.0.0.0, metric 3, tag 0
Mar 1 00:37:57.739: 3.3.3.0/24 via 0.0.0.0, metric 3, tag 120

I replaced the OSPF default with a static default and redistributed static
into RIP with a tag. Similarly, that tag was initially advertised and then
withdrawn, so it does not appear to be OSPF-specific, but route-specific.

Maybe someone can spot what is going on here?

Best regards

Bob Sinclair CCIE 10427 CCSI 30427
CIERS2 Online Instructor
www.tinyurl.com/ciers2online

> -----Original Message-----
> From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
> Muzammil Malick
> Sent: Thursday, October 07, 2010 6:26 AM
> To: Cisco certification
> Subject: Route Tagging with Default Route
>
> Hi Guys
>
> Hope someone can help me out.
>
> I am redistributing routes into RIP from OSPF. I have a route-map that
> sets a tag on the routes as they are redistributed into RIP.
> The problem is that all the routes seem to be tagged apart from the
> default route. The default route which is originated in OSPF always
> seems to have a tag of "0" when I debug RIP updates, however all the
> other routes have the correct tag of "110"
>
> Any ideas?
>
> Thanks
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.862 / Virus Database: 271.1.1/3182 - Release Date:
> 10/07/10 02:34:00

Blogs and organic groups at http://www.ccie.net
Received on Thu Oct 07 2010 - 10:07:54 ART