Changes to Default Behavior

The following chapter details the changes in default behavior after you upgrade to the Cloud Services plugin version 1.8.
Component
Change
You now allocate bandwidth at an aggregate level per compute location, rather than per remote network location.
The aggregate bandwidth model is available for all new Prisma Access 1.8 deployments and for existing deployments that have not had any remote networks onboarded before upgrading to 1.8. If you have an existing Prisma Access deployment that has onboarded remote networks and you then upgrade to Prisma Access 1.8, this model does not apply and you still apply bandwidth per location.
Secure inbound access for remote network sites and Quality of Service (QoS) for remote networks is not supported in Prisma Access 1.8 when you use the aggregate bandwidth model for remote network bandwidth allocation.
Traffic Steering Changes
Prisma Access has made the following changes to traffic steering:
  • To ensure consistency, Prisma Access has renamed the following fields in the Cloud Services plugin in the Traffic Steering area (
    Panorama
    Cloud Services
    Configuration
    Traffic Steering
    ):
    • The
      Target Service Connections for Traffic Forwarding
      area is changed to
      Target Service Connections for Traffic Steering
      .
    • The
      Dedicate for PBF
      column in the
      Target Service Connections for Traffic Steering
      area is changed to
      Dedicated for Traffic Steering
      .
    • Traffic Forwarding Rules
      is changed to
      Traffic Steering Rules
      .
    • When you create a
      Target Service Connection for Traffic Forwarding
      , the
      Dedicated for PBF Only
      check box is changed to
      Dedicated for Traffic Steering Only
      and the window name is changed from
      Target Service Connections for Traffic Forwarding
      to
      Target Service Connections for Traffic Steering
      .
    • When you
      Add
      a traffic steering rule, the window name is changed from
      Policy-Based Forwarding Rules
      to
      Traffic Steering Rules
      .
  • The
    Destination
    tab contains
    Destination
    and
    URL Category
    areas and the
    URL
    area is removed. If you want to add URLs to traffic steering rules, you must add them to a custom URL category.
    Existing URLs in the
    URL
    area are moved to a custom URL category named
    Custom_URL_Category_TFR
    number
    , where
    number
    is a number appended to the custom URL category. For this reason, do not create any custom URL categories named
    Custom_URL_Category_TFR
    number
    .
    Prisma Access prepends an asterisk to URLs in these migrated URLs. If you use the same URL category policies for both traffic steering and other security policy rules, these changes apply to both the traffic steering rules and other security policy rules.

Recommended For You