07-07-2016 07:17 AM - edited 03-12-2019 01:00 AM
I have an ASA connected to a provider. We have our own IP space to advertise. But since it is not directly connected, it will be used for NAT, it is not in the routing table and therefore not being advertised.
I thought once a NAT is configured, that would be the trick, but no go.
How do i get the ASA to advertise the block, when the ASA itself is the destination for that block, and has no route for it?
thanks for any assistance
Mike
07-07-2016 01:27 PM
Is this a public IP address space or a private IP address space assigned to you?
If it is a public address space, request the ISP to route the subnet toward your ASA, then all that is require for proxy ARP to work is to configure NAT on the ASA.
If this is a private address space going over the providers MPLS VPN network then you will need to advertise the subnet into BGP from the ASA
for example:
router bgp 10
address-family ipv4
network 192.168.0.0 255.255.255.0
--
Please remember to select a correct answer and rate helpful posts
11-10-2017 06:15 AM
I know this is an old thread, but I'm looking for any other way to solve this. If my ISP refuses to put in a static route pointing to my public interface, how I can force this route to be advertised in BGP even if it isn't configured locally on the interface?
I have entered a static route for my public subnet and pointed it to the Null0 interface on my ASA. This allows me to have the route installed in the routing table. The ASA states that it is advertising the route to my ISP via BGP, but my ISP is saying they don't see it.
09-06-2020 04:24 PM
Hi
By any chance could you resolved this issue? I'm having the same situation
Best regards
Ricardo
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