I don't think this is just OSPF, but rather any protocol that recognized
Internal and External Routes. From what I understand, the basic reason is
to keep from shooting yourself in the foot. For example, why would you
want to advertise addresses that belong to another AS?
On Page 135 of "Internet Routing Architectures", Halabi writes, "(In the
Cisco implementation, external OSPF routes
are automatically blocked from being redistributed into BGP; the
administrator has the option of overriding this behavior.)"
I haven't tries it, but on page 318, it looks like you simply "match" both
types on the redistribution command...
router bgp 3
redistribute ospf 10 match external 1 external 2.
Also on 318, Halabi states this is for "loop avoidance" in the case the
external OSPF information came from BGP.
For more info you can look on CCO:
http://www.cisco.com/warp/public/104/bgp-ospf-redis.html
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/np1_c
/1cprt1/1cbgp.htm
Ed
"Jeff Hillman" wrote in message
news:[EMAIL PROTECTED]...
> I have not been able to find any information on Cisco's site on why BGP
> synchronization does not recognize OSPF E1 or E2 external routes when
> checking the IGP routing table. Does anyone have an explination for this?
>
> If I put a static route into the local routing table, it synchronizes
> without any problems. The same is true with any other IGP except OSPF.
>
> Has anyone else seen this? Is there a work-around (other than 'no
> synchronization')?
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=35186&t=35131
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
