|
CYR-39553
|
Fixed an issue where the Autonomous DEM AIOps Allocated total
number is incorrect for multitenant setups.
|
| CYR-38068 | Fixed an issue where an integration may not happen
the first time a user tries to connect to "Managed Cloud WANs" in
the integration page. If this is the case, the user may have to
reenter the pairing key. |
| CYR-37500 | Fixed an issue where, if you have enabled IPv6 for
remote networks, the public IPv6 Address was not displayed for edge
locations. |
| CYR-37003 | Fixed an issue where, after upgrading the Panorama
that manages Prisma Access to 10.2, multitenant deployments had one
or more sub-tenants deleted after a local commit was performed.
Note that, after you install the plugin that contains this
hotfix and delete a tenant, the tenant is deleted locally on the
Panorama but its configuration remains in the Prisma Access
infrastructure. It is recommended that you backup your Panorama
configuration before you delete any sub-tenants. To completely
delete the tenant, reach out to your Palo Alto Networks account
representative or partner, who will contact the SRE team and
submit a request to delete the tenant from your
infrastructure. |
| CYR-36709 | Fixed an issue where, when allocating bandwidth in
legacy mode (on a per-location basis) for Remote Networks,
onboarding of more than 250 RN sites was failing due to a SaaS agent
Exception. |
| CYR-36121 | Fixed an issue where traffic steering network traffic
was being dropped due to a route asymmetry issue. |
| CYR-35811 | Fixed an issue where a Commit and Push operation was
failing due to an empty subtenant ID for a newly added
subtenant. |
| CYR-34173 | Fixed an issue where, when configuring multiple
GlobalProtect portals with Traffic Steering, you could not configure
Accept Default Routes over Service Connections . |
| CYR-34078 |
Fixed an issue where, if you configured a Colo-Connect subnet
before configuring and performing a Commit and Push operation
for the Infrastructure Subnet, Colo-Connect Commit and Push
operations would fail.
|
| CYR-33815 | Fixed an issue where, to enable Source IP
based Visibility and Enforcement in Explicit Proxy,
you also had to enable Enable Agent Proxy
(for Prisma Access (Managed by Strata Cloud Manager)) or Use GlobalProtect
Agent to Authenticate (for Panorama Managed Prisma
Access), even if you have not enabled the Explicit
Proxy-GlobalProtect agent functionality. |
| CYR-33695 | Fixed an issue where traffic steering rules could not
be disabled or moved. In other cases, an No object to
edit in move handler error was encountered and no
changes could be applied to the traffic steering rule. |
| CYR-33625 |
Fixed an issue where, when configuring Colo-Connect for the first
time and performing a partial commit, you received a
'Colo_Connect_Device_Group' is
invalid error.
|
| CYR-33584 | Fixed an issue where, in a multi-tenant deployment,
if the first tenant's license expired, all sub-tenants license were
also marked as expired. |
| CYR-33553 |
Fixed an issue where the Connector availability graph shown under displayed the graph in complete red color even
when the connector IPSec tunnel has been continuously up for the
last 24 hours.
|
| CYR-33539 | Fixed an issue where a new warning message displayed
during a commit when Explicit Proxy is configured in a deployment
with multiple tenants. |
| CYR-33180 | Fixed an issue where, in order to use the Prisma
Access Explicit Proxy Connectivity in GlobalProtect for Always-On
Internet Security feature, you had to onboard at least one mobile
user gateway. |
| CYR-32782 | Fixed an issue where, if you deleted a Colo-Connect
service connection and then Committed and Pushed your changes, it
could can take some time to delete Colo-Connect service
connections. |
| CYR-32188 |
Fixed an issue where, in Prisma Access Insights, the Connector
Availability graph for a given ZTNA Connector did not show up if
the IPSec tunnel between the connector and the ZTNA Tunnel
Terminator (ZTT) had been up without interruption for the last
24 hours.
|
| CYR-32170 | Fixed an issue where, when using ZTNA Connector,
diagnostic tools such as ping, traceroute and nslookup that are
accessible from the ZTNA Connector UI icon were not functional. |
| CYR-32006 |
Fixed an issue where, when using Dynamic DNS (DDNS) registration
using the Cloud Services plugin 3.2, nsupdate commands were not
working as expected, which caused issues with DDNS update
queries.
|
| CYR-31623 |
Fixed an issue where only one Panorama HA pair could be
associated with a CDL instance.
|
| CYR-30610 | Fixed an issue where, in a Prisma Access multitenant
deployment, Commit and Push operations were failing because
subtenant IDs were not being populated correctly. |