BGP OSPF routing loop

[Support ACME]

Dear ALL,

I had a problem in the BGP using neighbor XXX default-originate, if using "neighbor XXX default-originate" this command, the default route will always announce to the neighbor, my problem is if received the default route learn from other site OSPF(metric is 100) and will to announce to BGP neighbor, then the BGP neighbor will not announce the default route(metric is 0)  to the router?

anyone can help?

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is 192.168.10.1 to network 0.0.0.0

O*E2 0.0.0.0/0 [110/100] via 192.168.10.1, 00:09:56

router ospf 1
router-id 10.255.255.10
log-adjacency-changes
redistribute connected subnets tag 2200
redistribute static subnets tag 2200
redistribute bgp 65532 metric 100 subnets
network 192.168.10.0 0.0.0.255 area 0
network 192.168.11.0 0.0.0.255 area 0
default-information originate metric 200 metric-type 1
!
router bgp 65532
bgp router-id 10.255.255.10
bgp log-neighbor-changes
neighbor 10.194.0.253 remote-as 65531
!
address-family ipv4
redistribute connected
redistribute ospf 1 metric 2 match internal external 1 external 2 nssa-external 1 nssa-external 2
neighbor 10.194.0.253 activate
neighbor 10.194.0.253 default-originate route-map OSPF-to-BGP
neighbor 10.194.0.253 weight 50000
neighbor 10.194.0.253 soft-reconfiguration inbound
no auto-summary
no synchronization
table-map SetTag
exit-address-family

ip prefix-list static seq 8 permit 0.0.0.0/0
!
route-map OSPF-to-BGP permit 10
match ip address prefix-list static
match route-type external type-2

BGP table version is 19, local router ID is 10.255.255.10
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

Originating default network 0.0.0.0

Network Next Hop Metric LocPrf Weight Path

*> 10.194.0.0/24 0.0.0.0 0 32768 ?

Total number of prefixes 13

Support@ACMEHK

[MHM Cisco World]

can you draw the topology?
regarding your previous post you send to me the topology but I want to be sure.

[MHM Cisco World]

this My topology for some case are this same as you have,
cisco recommend to make bypass FW 
i.e. make the BGP between the Edge router and Core SW directly because there is no meaning of config FW as BGP Peer.
please if you have any point share it

[paul driver]

Hello

The EBGP/OSPF peer are the same so why are you advertising to the same router via both routing processes?

[Support ACME]

this switch is layer 3 switch and connected the fortigate FW, the fortigate FW is internet facing firewall, this switch are  running EBGP to fortigate  and OSPF to other site.

[paul driver]

Hello

I still think you do not need to advertise a default into both process of the same device?
Can you provide a topology diagram?

[Elliot Dierksen]

Why are you doing mutual redistribution? That is certainly is causing the loop, but I can't offer a solution without more information including a topology as @paul driver mentioned. IMHO, mutual redistribution is rarely actually needed and is frequently a source of problems. Core devices with a lot of links need to know a route for everything, but most other devices do not. A summary route or a a default route is all they need to get it to a device that a complete route table.

[Support ACME]

Dear ALL,

I had fixed the routing issue,the fortigate can receive the two 0.0.0.0, but the 0.0.0.0 weight from switch is  bigger than the fortigate generated default route.

Support@ACMEHK

[MHM Cisco World]

Good job friend.