10-23-2024 07:28 AM - edited 10-23-2024 07:31 AM
Routes 213.251.59.0/29(MCR-Systems-Tills) , 81.136.231.141/32 and 82.152.31.5/32 (TelephoneTechnology) are not being redistributed
The static entries exist in the routing table and are included in the route-map but don’t seem to behave in the same way as 192.168.208.0/24 which is being redistributed.
Below is the configuration from the CLI of the FTD
route-map STATIC_INTO_OSPF permit 10
match ip address prefix-list SecureBoundary_DC1
!
route-map STATIC_INTO_OSPF permit 20
match ip address prefix-list HIN_VPN_Clients
!
route-map STATIC_INTO_OSPF deny 30
match ip address prefix-list Planet_FM
!
route-map STATIC_INTO_OSPF permit 40
match ip address prefix-list Parking
set metric 110
set metric-type type-2
!
route-map STATIC_INTO_OSPF permit 50
match ip address prefix-list GE_Support
!
route-map STATIC_INTO_OSPF permit 60
match ip address prefix-list MCR-Systems-Tills
set metric 100
set metric-type type-2
!
route-map STATIC_INTO_OSPF permit 70
match ip address prefix-list TelephoneTechnology
set metric 100
set metric-type type-2
!
router ospf 1
router-id 192.168.250.94
network 46.254.185.248 255.255.255.248 area 0
network 192.168.90.0 255.255.255.0 area 0
network 192.168.208.0 255.255.255.0 area 0
network 192.168.236.0 255.255.255.0 area 0
network 192.168.254.0 255.255.255.0 area 0
no nsf Cisco helper
no nsf ietf helper
no capability opaque
no capability lls
no compatible rfc1583
log-adj-changes
redistribute static route-map STATIC_INTO_OSPF
Why are the MCR System and TelephoneTechnology routes not being advertised?
static routes configured as a workaround with admin distance of 254 so they’d be superseded by a route from OSPF if one existed.
Solved! Go to Solution.
10-30-2024 12:05 AM - edited 10-30-2024 02:08 AM
MHM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide