Redistributing OSFP routes into BGP

[blackout]

Hey all

Using a 'hybrid' network model with Fortigate 80F and a Cisco catalyst 9200L
Forti handles the routing and is relayed to Cisco.

Im trying to relay OSPF routes learnt by Fortigate into iBGP handled by our ISP, however its not working.
i can see in Forti that the routes are connected locally but not propagated into BGP

I get routes from BGP so i can confirm that its working atleast one way, but not the other.

Im trying to propagate 10.0.1.1 10.0.2.1 10.0.3.1 all /25 to BGP for advertised routing

get router info bgp summary

VRF 0 BGP router identifier 172.16.0.10, local AS number 65500
BGP table version is 6
8 BGP AS-PATH entries
0 BGP community entries

Neighbor   V         AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
172.16.0.9 4      65535     473     449        5    0    0 03:14:03      130

Total number of neighbors 1


corenet0-a # 

get router info bgp summary

VRF 0 BGP router identifier 172.16.0.10, local AS number 65500
BGP table version is 6
8 BGP AS-PATH entries
0 BGP community entries

Neighbor   V         AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
172.16.0.9 4      65535     473     449        5    0    0 03:14:03      130

Total number of neighbors 1


corenet0-a # get router info bgp neighbors
VRF 0 neighbor table:
BGP neighbor is 172.16.0.9, remote AS 65535, local AS 65500, external link
  BGP version 4, remote router REDACTED
  BGP state = Established, up for 03:14:32
  Last read 00:00:17, hold time is 90, keepalive interval is 30 seconds
  Configured hold time is 180, keepalive interval is 60 seconds
  Neighbor capabilities:
    Route refresh: advertised and received (old and new)
    Address family IPv4 Unicast: advertised and received
    Address family VPNv4 Unicast: advertised
    Address family IPv6 Unicast: advertised
    Address family VPNv6 Unicast: advertised
    Address family L2VPN EVPN: advertised
  Received 474 messages, 0 notifications, 0 in queue
  Sent 450 messages, 0 notifications, 0 in queue
  Route refresh request: received 0, sent 0
  NLRI treated as withdraw: 0
  Minimum time between advertisement runs is 30 seconds
  Update source is VLAN22-MPLS

 For address family: IPv4 Unicast
  BGP table version 6, neighbor version 5
  Index 1, Offset 0, Mask 0x2
  NEXT_HOP is always this router
  Community attribute sent to this neighbor (both)
  Outbound path policy configured
  Route map for outgoing advertisements is *RM_OSPF_TO_BGProot
  130 accepted prefixes, 130 prefixes in rib
  6 announced prefixes

 For address family: VPNv4 Unicast
  BGP table version 1, neighbor version 1
  Index 1, Offset 0, Mask 0x2
  Community attribute sent to this neighbor (both)
  0 accepted prefixes, 0 prefixes in rib
  0 announced prefixes

 For address family: IPv6 Unicast

get router info bgp neighbors 172.16.0.9 advertised-routes 
VRF 0 BGP table version is 6, local router ID is 172.16.0.10
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric     LocPrf Weight RouteTag Path
*> 10.0.0.0/30      172.16.0.10                        32768        0 ? <-/->
*> 10.0.1.0/25      172.16.0.10                        32768        0 ? <-/->
*> 10.0.2.0/25      172.16.0.10                        32768        0 ? <-/->
*> 10.0.3.0/25      172.16.0.10                        32768        0 ? <-/->
*> 10.0.4.0/25      172.16.0.10                        32768        0 ? <-/->
*> 172.16.0.8/29    172.16.0.10                        32768        0 ? <-/->

Total number of prefixes 6

get router info ospf route

OSPF process 0:
Codes: C - connected, D - Discard, 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

C  10.0.0.0/30 [1] is directly connected, vlan9-control, Area 0.0.0.0
C  10.0.1.0/25 [1] is directly connected, VLAN11-Users, Area 0.0.0.0
C  10.0.2.0/25 [1] is directly connected, VLAN12-aux, Area 0.0.0.0
C  10.0.3.0/25 [1] is directly connected, VLAN13-Core, Area 0.0.0.0
C  10.0.4.0/25 [1] is directly connected, VLAN14-dmz, Area 0.0.0.0

[ElwinBERRAR · Accepted solution]

Hi From what I see, the FortiGate is already advertising the /25 routes since they show up under advertised routes. So it’s likely just a filtering issue on the provider side or something in the outbound route map.

[blackout]

duh, that fixed it! many thanks