This KB explains a known issue where a static route configured in the master instance is not advertised through BGP in a Secure Edge VPN deployment, even when an export policy is configured for that route.

In a setup where BGP is configured over Secure Edge VPN, there may be a requirement to advertise a subnet that is not directly connected and is configured as a static route in the master instance.

Even after configuring a BGP export policy for the subnet, the route is not advertised to BGP peers.

This issue is currently being tracked internally by the Mist Engineering team.

As a workaround, import the required static routes from the master instance into the routing instance where BGP is configured.

Use the following configuration:

set groups top policy-options policy-statement master_direct-1 term 01_direct from instance master

set groups top policy-options policy-statement master_direct-1 term 01_direct from protocol static

set groups top policy-options policy-statement master_direct-1 term 01_direct then accept

set groups top routing-instances <Instance name> routing-options instance-import master_direct-1

Note: Replace <Instance name> with the routing instance where BGP is configured.

After applying the workaround, the static routes from the master instance can be imported into the BGP routing instance and advertised as expected.