10-30-2024 07:25 AM
I have a datacenter ION9k that is connected via standard VPN to AWS. On another connection I have a PA-1400 series firewall. The connections look something like this:
PA-1400 (AS 65002) -- DC ION (AS 65003) -- AWS VPN (AS 65417)
The ION receives routes from from AWS and from the PA-1400. The problem I'm having is that the ION is not advertising the routes it learns from AWS to the PA-1400 and vice versa. Any ideas on what's causing this is appreciated.
12-05-2024 08:43 AM
This issue has been resolved and was caused by the default, auto-generated route map on the ION9k. Once that was updated with a custom route map, prefixes started getting exchanged between the devices in question.
12-05-2024 08:39 AM
Do you have them set as Global?
Branch ION devices can learn or advertise prefixes based on the scope configured. A branch ION device does not advertise routes learned on one BGP peer to another BGP peer. The device advertises only LAN networks, static routes, and interface addresses. To advertise any of these prefixes, set the Scope to Global when configuring a BGP peer.
12-05-2024 08:43 AM
This issue has been resolved and was caused by the default, auto-generated route map on the ION9k. Once that was updated with a custom route map, prefixes started getting exchanged between the devices in question.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
