Hello Martin Kallukalam
Thank you for the update and additional details.
Based on your current route map dashboard, it appears you’re seeing only the summarized route as expected. The specific routes (10.30.96.0/19 and 10.30.224.0/19) should not be advertised to the VPN client, but it is reflecting the changes in VPN Client.
Steps we have tried in the lab environment:
Remove the existing rule that only performs a “replace” operation.
Create two separate rules,
Rule 1: Drop Specific Prefixes
- Match condition: 10.30.96.0/19, 10.30.224.0/19 (If comma separation doesn't work, create two separate rules with action drop and next step continue)
- Action: Drop
- Next step: Continue
This rule ensures the individual /19 routes are not propagated to the VPN client.
Rule 2: Permit and Replace with Summarized Prefix
- Match condition: Prefix contains 10.30.0.0/16
- Action: Modify
- Modification: Replace with 10.30.0.0/16
- Next step: Terminate
Even after trying several rules, we observed that summarization only occurred at the route map dashboard level and not at the VPN site level.
We will reach out to the backend team regarding this feature issue.
Thank you for your time, Martin!
Please don’t forget to close the thread by clicking "Accept the answer" and "Yes" wherever the information provided helps you, as this can be beneficial to other community members.