End-of-Life (EoL)

Device > Virtual Systems

A virtual system (vsys) is an independent (virtual) firewall instance that you can separately manage within a physical firewall. Each vsys can be an independent firewall with its own Security policy, interfaces, and administrators; a vsys enables you to segment the administration of all policies, reporting, and visibility functions that the firewall provides. For example, if you want to customize the security features for the traffic that is associated with your Finance department, you can define a Finance vsys and then define security policies that pertain only to that department. To optimize policy administration, you can maintain separate administrator accounts for overall firewall and network functions while creating vsys administrator accounts that allow access to individual vsys. This allows the vsys administrator in the Finance department to manage the security policies only for that department.
Networking functions (such as static and dynamic routing, IP addresses of interfaces, and IPSec tunnels) pertain to an entire firewall and all of its virtual systems. A virtual system configuration (
Virtual Systems
) doesn’t control firewall-level and network-level functions (such as static and dynamic routing, IP addresses of interfaces, IPSec tunnels, VLANs, virtual wires, virtual routers, DHCP, DNS Proxy, QoS, LLDP, and network profiles). For each vsys, you can specify a collection of physical and logical firewall interfaces (including VLANs and virtual wires) and security zones. If you require routing segmentation for each vsys, you must create and assign additional virtual routers and assign interfaces, VLANs, and virtual wires as needed.
If you use a Panorama template to define vsys, you can set one vsys as the default. The default vsys and Multiple Virtual Systems mode determine whether firewalls accept vsys-specific configurations during a template commit:
  • Firewalls that have Multi Virtual System Capability enabled accept vsys-specific configurations for all vsys that are defined in the template.
  • Firewalls that don’t have Multi Virtual System Capability enabled accept vsys-specific configurations only for the default vsys. If you do not set a vsys as the default, these firewalls accept no vsys-specific configurations.
    PA-3000 Series, PA-5000 Series,
    PA-5200 Series,
    and PA-7000 Series firewalls support multiple virtual systems; however, PA-3000 Series firewalls require a license for enabling multiple virtual systems. The PA-200 and
    , PA-220,
    , and PA-800 Series
    firewalls do not support multiple virtual systems.
Before enabling multiple vsys, consider the following:
  • A vsys administrator creates and manages all items needed for Security policy per assigned virtual system.
  • Zones are objects within vsys. Before defining a policy or policy object, select the
    Virtual System
    from the drop-down on the
  • You can set remote logging destinations (SNMP, syslog, and email), applications, services, and profiles to be available to all vsys (shared) or to a single vsys.
  • You can configure global (to all vsys on a firewall) or vsys-specific service routes (see Device > Setup > Services).
  • You can rename a vsys only on the local firewall. On Panorama, renaming a vsys is not supported. If you rename a vsys on Panorama, you will create an entirely new vsys, or the new vsys name may get mapped to the wrong vsys on the firewall.
Before defining vsys, you must first enable the multiple vsys capability on the firewall: select
, edit the
General Settings
, select
Multi Virtual System Capability
, and click
. This adds a
Virtual Systems
page. Select the page, click
, and specify the following information.
Virtual System Settings
Enter an integer identifier for the vsys. Refer to the data sheet for your firewall model for information on the number of supported vsys.
If you use a Panorama template to configure the vsys, this field does not appear.
Enter a name (up to 31 characters) to identify the vsys. The name is case-sensitive and must be unique. Use only letters, numbers, spaces, hyphens, and underscores.
If you use a Panorama template to push vsys configurations, the vsys name in the template must match the vsys name on the firewall.
Allow Forwarding of Decrypted Content
Select this option to allow the virtual system to forward decrypted content to an outside service when port mirroring or sending WildFire files for analysis. For information on Decryption Port Mirroring, see Decryption Port Mirroring.
General Tab
Select a
DNS Proxy
object if you want to apply DNS proxy rules to this vsys. See Network > DNS Proxy.
To include objects of a particular type, select that type (interface, VLAN, virtual wire, virtual router, or visible virtual system), click
, and select the object from the drop-down. You can add one or more objects of any type. To remove an object, select it and click
Resource Tab
Specify the following resource limits allowed for this 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 vsys is the limit for the firewall model. However, the limit for a specific setting isn’t replicated for each vsys. 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
    —Maximum number of sessions.
    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 Series or PA-7000 Series firewall, the Current number of sessions 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 or PA-7000 Series firewall is per dataplane, and will result in a high maximum per virtual system.
  • Security Rules
    —Maximum number of security rules.
  • NAT Rules
    —Maximum number of NAT rules.
  • Decryption Rules
    —Maximum number decryption rules.
  • QoS Rules
    —Maximum number of QoS rules.
  • Application Override Rules
    —Maximum number of application override rules.
  • Policy Based Forwarding Rules
    —Maximum number of policy based forwarding (PBF) rules.
  • Captive Portal Rules
    —Maximum number of captive portal (CP) rules.
  • DoS Protection Rules
    —Maximum number of denial of service (DoS) rules.
  • Site to Site VPN Tunnels
    —Maximum number of site-to-site VPN tunnels.
  • Concurrent GlobalProtect Tunnels
    —Maximum number of concurrent remote GlobalProtect users.

Recommended For You