Configure Virtual Systems

Creating a virtual system requires that you have the following:
  • A
    superuser
    administrative role.
  • An interface configured.
  • A Virtual Systems license if you are configuring a PA-3000 Series firewall, or if you are creating more than the base number of virtual systems supported on the platform. See Platform Support and Licensing for Virtual Systems.
  1. Enable virtual systems.
    1. Select
      Device
      Setup
      Management
      and edit the
      General Settings
      .
    2. Select the
      Multi Virtual System Capability
      check box and click
      OK
      . This action triggers a commit if you approve it.
      Only after enabling virtual systems will the
      Device
      tab display the
      Virtual Systems
      and
      Shared Gateways
      options.
  2. Create a virtual system.
    1. Select
      Device
      Virtual Systems
      , click
      Add
      and enter a virtual system
      ID
      , which is appended to “vsys” (range is 1-255).
      The default ID is 1, which makes the default virtual system
      vsys1
      . This default appears even on platforms that do not support multiple virtual systems.
    2. Select
      Allow forwarding of decrypted content
      if you want to allow the firewall to forward decrypted content to an outside service. For example, you must enable this option for the firewall to be able to send decrypted content to WildFire for analysis.
    3. Enter a descriptive
      Name
      for the virtual system. A maximum of 31 alphanumeric, space, and underscore characters is allowed.
  3. Assign interfaces to the virtual system.
    The virtual routers, virtual wires, or VLANs can either be configured already or you can configure them later, at which point you specify the virtual system associated with each.
    1. On the
      General
      tab, select a
      DNS Proxy
      object if you want to apply DNS proxy rules to the interface.
    2. In the
      Interfaces
      field, click
      Add
      to enter the interfaces or subinterfaces to assign to the virtual system. An interface can belong to only one virtual system.
    3. Do any of the following, based on the deployment type(s) you need in the virtual system:
      • In the
        VLANs
        field, click
        Add
        to enter the VLAN(s) to assign to the vsys.
      • In the
        Virtual Wires
        field, click
        Add
        to enter the virtual wire(s) to assign to the vsys.
      • In the
        Virtual Routers
        field, click
        Add
        to enter the virtual router(s) to assign to the vsys.
    4. In the
      Visible Virtual System
      field, check all virtual systems that should be made visible to the virtual system being configured. This is required for virtual systems that need to communicate with each other.
      In a multi-tenancy scenario where strict administrative boundaries are required, no virtual systems would be checked.
    5. Click
      OK
      .
  4. (
    Optional
    ) Limit the resource allocations for sessions, rules, and VPN tunnels allowed for the virtual system. The flexibility of being able to allocate limits per virtual system allows you to effectively control firewall resources.
    1. On the
      Resource
      tab, optionally set limits for a virtual system. Each field displays the valid range of values, which varies per firewall model. The default setting is 0, which means the limit for the virtual system is the limit for the firewall model. However, the limit for a specific setting isn’t replicated for each virtual system. For example, if a firewall has four virtual systems, each virtual system can’t have the total number of Decryption Rules allowed per firewall. After the total number of Decryption Rules for all of the virtual systems reaches the firewall limit, you cannot add more.
      • Sessions Limit
        If you use the show session meter CLI command, it displays the Maximum number of sessions allowed per dataplane, the Current number of sessions being used by the virtual system, and the Throttled number of sessions per virtual system. On a PA-5200 or PA-7000 Series firewall, the Current number of sessions being used can be greater than the Maximum configured for Sessions Limit because there are multiple dataplanes per virtual system. The Sessions Limit you configure on a PA-5200 Series or PA-7000 Series firewall is per dataplane, and will result in a higher maximum per virtual system.
      • Security Rules
      • NAT Rules
      • Decryption Rules
      • QoS Rules
      • Application Override Rules
      • Policy Based Forwarding Rules
      • Authentication Rules
      • DoS Protection Rules
      • Site to Site VPN Tunnels
      • Concurrent SSL VPN Tunnels
    2. Click
      OK
      .
  5. Commit the configuration.
    Click
    Commit
    . The virtual system is now an object accessible from the
    Objects
    tab.
  6. Create at least one virtual router for the virtual system in order to make the virtual system capable of networking functions, such as static and dynamic routing.
    Alternatively, your virtual system might use a VLAN or a virtual wire, depending on your deployment.
    1. Select
      Network
      Virtual Routers
      and
      Add
      a virtual router by
      Name
      .
    2. For
      Interfaces
      , click
      Add
      and from the drop-down, select the interfaces that belong to the virtual router.
    3. Click
      OK
      .
  7. Configure a security zone for each interface in the virtual system.
    For at least one interface, create a Layer 3 security zone. See Configure Interfaces and Zones.
  8. Configure the security policy rules that allow or deny traffic to and from the zones in the virtual system.
  9. Commit the configuration.
    Click
    Commit
    .
    After creating a virtual system, you can use the CLI to commit a configuration for only a specific virtual system:
    commit partial vsys
    <vsys-id>
  10. (
    Optional
    ) View the security policies configured for a virtual system.
    Open an SSH session to use the CLI. To view the security policies for a virtual system, in operational mode, use the following commands:
    set system setting target-vsys
    <vsys-id>
    show running security-policy

Related Documentation