From: Chua, Parry (Parry.Chua@xxxxxxxxxx)
Date: Fri Mar 22 2002 - 08:16:23 GMT-3
I suspect that the mask at R13 on network 172.16.x.x is not at /24 which casue
the directly connected network 10.1.1.0/24 problem.
Regards
Parry
-----Original Message-----
From: Jason T. Rohm [mailto:jtrohm@athenet.net]
Sent: Friday, March 22, 2002 4:30 PM
To: CCIELIST (E-mail)
Subject: Redistribution IGRP into OSPF
I have a weird problem that I thought I would bounce off the list before I
open a TAC ticket.
I am starting to suspect a bug of some sort.
I am running through NLI's Security Lab 3.
I am running 12.2(6a) IP/Plus/3DES/FW/IDS on a 2620.
Problem:
Router 13 has one leg in OSPF land and one in IGRP land.
When I redistribute IGRP into OSPF all downstream 10.x.x.x networks are
injected into OSPF as E2 subnets EXCEPT for the 10.1.1.0/24 network that is
directly connected to Router 13.
All IGRP networks are FLSM /24 subnets of the 10.0.0.0 network.
I am not filtering that network and do not know why all the other IGRP
networks would show up, but not the connected network.
Anyone have any ideas?
Rough Diagram:
[R1] --- (OSPF - 172.16.x.x) --- [R13] --- (IGRP - 10.1.1.x/24) ---
[R14] --- (IGRP - 10.x.x.x/24)
(R1 has all 10.x.x.x routes EXCEPT 10.1.1.0/24)
R13 Configuration (Edited for your consumption):
router ospf 3
log-adjacency-changes
redistribute igrp 3 subnets route-map IGRP2OSPF
network 172.16.1.0 0.0.0.255 area 1
default-metric 10
!
router igrp 3
redistribute ospf 3 route-map OSPF2IGRP
network 10.0.0.0
default-metric 10000 0 255 128 1500
!
access-list 11 permit 10.1.1.0 0.0.0.255
access-list 11 permit 10.1.2.0 0.0.0.255
access-list 11 permit 10.1.4.0 0.0.0.255
access-list 12 permit any
!
route-map IGRP2OSPF permit 10
match ip address 11
!
route-map IGRP2OSPF deny 20
match ip address 12
!
route-map OSPF2IGRP deny 10
match ip address 11
!
route-map OSPF2IGRP permit 20
match ip address 12
!
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:17 GMT-3