Let us learn more about to onboard an ecmp enabled site.
ECMP is now enabled by default within the
CloudBlade. With the Local-AS configuration in the 3.0.1 version
for the CloudBlade, the ECMP onboarding of sites is simplified by
just having to configure the prisma_access tag on a site, in conjunction
with the IPSec Termination Node region tags applied.
provides the ability to add new links to the site and have them
automatically be added to the ECMP bundle, providing the site with
an additional path to Prisma Access.
ECMP is enabled on all
circuits, but can be disabled or modified for a given site. All
circuits that have reachability to Prisma Access will automatically
be added to the ECMP bundle, with up to four interfaces in the ECMP
select your site.
Click the extended tags icon on the
to view ECMP.
When you create an ECMP bundle, the default selection
sections by default.
In 3.0.1, the auto region detection
for ECMP bundles is NOT recommended to be used as is available in
the 2.0.3 CloudBlade release. There is no current logic today from
the CloudBlade and Prisma integration to determine if a region has
bandwidth allocated (and IPSec Termination Nodes behind it). The
current CloudBlade logic assumes that ALL regions have bandwidth available.