VM-Series Deployment Guide
    : Create the Service Definitions on Panorama
    Focus
    Download PDF
    Focus
    1. Home
    2. VM-Series
    3. VM-Series Deployment Guide
    4. Set Up the VM-Series Firewall on VMware NSX
    5. Set Up the VM-Series Firewall on VMware NSX-V
    6. Register the VM-Series Firewall as a Service on the NSX-V Manager
    7. Create the Service Definitions on Panorama
    Download PDF

    VM-Series Deployment Guide

    Create the Service Definitions on Panorama

    Table of Contents
    End-of-Life (EoL)

    Create the Service Definitions on Panorama

    A service definition specifies the configuration for the VM-Series firewalls installed on each host in an ESXi cluster. The service definition must include the device group, the license auth-codes for deploying the VM-Series firewalls, and a template stack with one or more NSX-V service profile zones. Typically, you create a service definition for the VM-Series firewall in an ESXi cluster. If you have different ESXi clusters that have workloads that require the VM-Series firewall to handle traffic differently, you can create multiple service definitions on Panorama.
    On a Panorama commit, each service definition is registered on the NSX-V Manager. On registration with the NSX-V Manager, the NetX API implementation makes each zone (defined within the template stack) available for redirecting traffic. When you deploy the VM-Series firewalls, you can select the profile name for the VM-Series firewall(s) to which you want to redirect traffic from the objects in NSX-V security groups. The appropriately configured firewall can then inspect the traffic and enforce policy from the virtual machines that belong to the NSX-V security groups.
    1. (Optional) Configure a Notify Group
      Create a notify group by specifying devices groups that should be notified of changes in the virtual environment. The firewalls included in the specified device groups receive a real-time update of security groups and IP addresses of guest VMs in them. The firewalls use this update to determine the most current list of members that constitute dynamic address groups referenced in policy
      1. Select PanoramaVMwareNSX-VNotify Group and click Add.
      2. Give your Notify Group a descriptive Name.
      3. Select the boxes of all devices groups that should be notified of changes to the virtual environment. If a device group does not have a check box available, it means that the device group is automatically included by virtue of the device group hierarchy.
      4. Click OK.
    2. Add a new service definition.
      You can create up to 32 service definitions on Panorama.
      1. Select PanoramaVMwareNSX-VService Definitions.
      2. Select Add to create a new service definition. The maximum number of characters in a service definition name is 40.
        On the NSX-V Manager, this service definition name displays in the Services column on Networking & SecurityService DefinitionsServices.
      3. (Optional) Add a Description that identifies the function or purpose for the VM-Series firewalls that will be deployed using this service definition.
    3. Assign a device group and a template stack to the service definition.
      Make sure to Create the zone(s) for each template stack.
      Because the firewalls deployed in this solution will be centrally administered from Panorama, you must specify the Device Group and the Template Stack that the firewalls belong to. All the firewalls that are deployed using this service definition belong to the specified template stack and device group.
      1. Select the device group or device group hierarchy in the Device Group drop-down.
      2. Select the template stack in the Template drop-down.
        You cannot reuse a template stack or a device group assigned to one service definition in another service definition.
    4. Specify the location of the OVF file.
      Download the zip file, unzip it to extract and save the .ovf, mf and .vmdk files to the same directory. Both the files are used to deploy each instance of the firewall.
      If needed, modify the security settings on the server so that you can download the file types. For example, on the IIS server modify the Mime Types configuration; on an Apache server edit the .htaccess file.
      Do not change the Panorama service definition OVF path after a successful NSX Service Deployment of VM-Series firewalls. Changing the OVF path, after a successful VM-Series firewall deployment, can result in a NSX Service Deployment failed state. You may resolve this failure in NSX-V Manager, however this may cause all VM-Series firewalls to redeploy.
      It is recommended that you use an OVF path name that scales and allows you to change the base image without impacting your deployed firewalls. Instead of a path such as https://acme.com/software/PA-VM-NSX.9.1.0.ovf, use something such as https://acme.com/software/PanoSvcDef1-Cluster1.ovf. Using a static path reference will eliminate any future need to change the OVF path. It is recommended to create a path for each Panorama service definition (vSphere cluster) in your deployment and change the PAN-OS base images references on the web server as needed.
      In VM-Series OVF URL, add the location of the web server that hosts the ovf file. Both http and https are supported protocols.
      Select the ovf file that matches the VM-Series model you plan to deploy. For the VM-200, use vm100.ovf. For the VM-1000-HV, use vm300.ovf.
      You can use the same ovf version or different versions across service definitions. Using different ovf versions across service definitions allows you to vary the PAN-OS version on the VM-Series firewalls in different ESXi clusters.
    5. (Optional) Select a Notify Group.
      To create context awareness between the virtual and security environments so that policy is consistently applied to all traffic steered to the firewalls, select the device groups to notify when there are changes in the virtual environment.
      Select each device group to which you want to enable notifications in the Notify Device Groups drop-down. If a device group does not have a checkbox available, it means that the device group is automatically included by virtue of the device group hierarchy.
      The firewalls included in the specified device groups receive a real-time update of security groups and IP addresses. The firewalls use this update to determine the most current list of members that constitute dynamic address groups referenced in policy.
    6. Enable Device Certificate if your OVF is PAN-OS 9.1.5 or later. Otherwise, disable it.
    7. Save the service definition and attach it to the service manager.
      1. Click OK.
      2. Select PanoramaVMwareNSX-VService Manager and click the link of the service manager name.
      3. Under Service Definitions, click Add and select your service definition from the drop-down.
      4. Click OK.
      5. Select Commit and Commit Type: Panorama.
        Committing the changes triggers the process of registering each service definition as a security service on the NSX-V Manager.
    8. Add the authorization code to license the firewalls.
      The auth-code must be for the VM-Series model NSX bundle; for example, PAN-VM-300-PERP- BND-NSX.
      Verify that the order quantity/ capacity is adequate to support the number of firewall you need to deploy in your network.
      1. Select PanoramaDevice Groups and choose the device group you associated with the service definition you just created.
      2. Under Dynamically Added Device Properties, add the authorization code you received with your order fulfillment email and select a PAN-OS software version from the SW Version drop-down.
        When a new firewall is deployed under NSX-V and added to the selected device group, the authorization code is applied and the firewall is upgraded to the select version of PAN-OS.
        On the support portal, you can view the total number of firewalls that you are authorized to deploy and the ratio of the number of licenses that have been used to the total number of licenses enabled by your auth-code.
      3. Synchronize the configuration between Panorama and the NSX-V Manager.
        1. Select PanoramaVMwareNSX-VService Managers.
        2. Select NSX Config-Sync under the Actions column.
        3. Click Yes to confirm the sync.
    9. Verify that the service definition and the NSX-V service profile that you defined on Panorama are registered on the NSX-V Manager.
      1. On the NSX-V Manager, to verify that the service definition is available, select Networking & SecurityService DefinitionsServices. The service definition is listed as a Service on the NSX-V Manager.
      2. To verify that the zones are available on the NSX-V Manager:
        1. Select Networking and SecurityService ComposerSecurity Policies, and click Create Security Policy.
        2. Select Network Introspection Services, and click Add.
        3. In the Service Name drop-down, select a Palo Alto Networks service that you verified in the step above.
        4. In the Profile drop-down, verify that you can view all the zones you defined for that service definition on Panorama.
    10. (Optional) Synchronize the configuration between Panorama and the NSX-V Manager.
      If you add or update the service definitions configured on Panorama, select NSX Config Sync in the Action column under PanoramaVMwareNSX-VService Managers to synchronize the changes on the NSX-V Manager.
      This link is not available, if you have any pending commits on Panorama.
      If the synchronization fails, view the details to know whether to fix the error on Panorama or on the NSX-V Manager. For example, if you delete a service definition on Panorama, but the service definition cannot be deleted from the NSX-V Manager because it is referenced in a rule on the NSX-V Manager, the synchronization will fail with an error message that indicates the reason for failure.

    © 2024 Palo Alto Networks, Inc. All rights reserved.