Configure an NGFW Cluster

Before you configure an NGFW cluster, perform the following prerequisites:

• Confirm that Panorama and the PA-7500 Series firewalls that you will assign to an NGFW cluster are all running the same software version (PAN-OS 11.1.3 or a later 11.1 release).
• Install Panorama Clustering plugin 2.0.0 if you're using PAN-OS 11.1.3; refer to Install Panorama Plugins. For subsequent PAN-OS releases, you must install a compatible Panorama Clustering plugin release. Also refer to the Panorama plugin for Clustering in the VM-Series and Panorama Plugin Release Notes.
• Be familiar with Panorama tasks, such as managing devices and creating templates, template stacks, and device groups.
• Add the two PA-7500 Series firewalls as managed devices of Panorama so that they are communicating with each other over the management interface. Confirm by selecting PanoramaManaged DevicesSummary, and verify the two firewalls (nodes) have an IP address on their management interface and the Device State is Connected.
• Connect the PA-7500 Series firewalls back-to-back with 100G or 400G HSCI-A and HSCI-B links. (Verify the connections on each firewall by using the CLI command show interface all to see the hsci-a and hsci-b interfaces.)
• Familiarize yourself with NGFW Clusters.

The steps in the example task to configure an NGFW cluster are based on this topology example of two MC-LAGs. The orange links connected to Node 1 and Node 2 on the client side belong to AE1 (an MC-LAG). The orange links connected to Node 1 and Node 2 on the server side belong to AE2 (another MC-LAG). Traffic from the client at 10.1.7.100 goes to the switch and is then divided between the two ingress AE1 interfaces and then egresses the two AE2 interfaces to the switch, and then goes over the orange link to the server at 10.1.8.200.

The gray links connected Node 1 and Node 2 are orphan ports. Traffic from the client at 10.1.1.100 goes to the switch, to Node 1, across an HSCI interface to Node 2, egresses Node 2 to the switch, and then to the server at 10.1.2.100.

1. Log in to the Panorama Web Interface.
2. Create an NGFW cluster.

   1. Select PanoramaFirewall ClustersCreate Cluster.
   2. Enter a Cluster Name containing zero or more alphanumeric characters, underscores (_), hyphens (-), dots (.), or spaces.
   3. Select Cluster Type as PA.
   4. Click OK.
3. Add the firewalls to the cluster.

   1. Select PanoramaFirewall ClustersSummary View and select the cluster you created.
   2. Enter a Group ID in the range 1 to 63; the default is 1.
   3. Select the two PA-7500 Series firewalls to assign to the cluster. The first firewall you select automatically becomes Node 1.

   4. Click OK.
   5. View the firewalls in the cluster by selecting PanoramaFirewall ClustersSummary View and selecting the cluster you created. The General tab displays nonconfigurable fields: Device serial number and Node ID (1 or 2). Click OK to close the window.

   6. Select Commit to Panorama and Commit. Both firewalls are rebooted and get assigned a Node ID, the existing configuration (policy, network, etc.) is cleared, and the firewalls are connected back to Panorama.
   7. Select Push to Devices, select Push All Changes, select the newly created firewall cluster, and Push.
4. Verify the cluster state and node state.

   1. Access the CLI.
   2. > show cluster leader
   3. > show cluster local node-id
   4. > show cluster local state
   5. > show cluster all
   6. > exit
5. Log in to the Panorama Web Interface.
6. View the Config Sync Status.

   1. Select PanoramaFirewall ClustersSummary View and select PA-Series.
   2. View the Config Sync Status. After the Commit All is successful, the firewalls have a Config Sync Status of In Sync.

7. Add a cluster template.

   1. Select PanoramaTemplates and Add a template.
   2. Enter a Name and Description of the template.
   3. Enable clustering. You must enable clustering when you first create the template; you can't go back to enable clustering later.
   4. Click OK.

8. Create a template stack.

   1. Select PanoramaTemplatesAdd Stack.
   2. Enter a Name for the template stack.
   3. In the Devices section, select the two firewalls in the cluster.
   4. In the Templates section, Add the template you created.
   5. Enable clustering. You must enable clustering when you first create the template stack; you can't go back to enable clustering later. (If you don't Enable clustering for the template stack now, it won't match the template and an Operation Failed message appears.)
   6. Click OK.

9. Add a device group.

   1. Select PanoramaDevice GroupsAdd.
   2. Enter a Name for the device group.
   3. In the Devices section, select the Names of the two firewalls in the cluster.
   4. In the Reference Templates section, Add the template stack that you created.
   5. Click OK.
10. Commit to Panorama and Commit to apply your configuration in Panorama.
11. (Two-node cluster only) Verify that the management interface permits the same IP addresses on the two nodes. The firewalls use the management interface to exchange heartbeats to detect and avoid a split-brain situation.

    1. Select DeviceSetupInterfaces.
    2. In the Template field, select your template.
    3. Select the Management interface.
    4. If you added Permitted IP Addresses on one of the nodes, you must also permit the same IP addresses on the peer node. Each node must be able to reach the management interface of the peer node. (If you deny the IP address or network of the peer, split brain detection won't work.)
    5. Click OK.

12. Configure the template.

    1. Select Network
    2. In the Template field, select your template.
13. To configure the orphan port, configure a Layer 3 interface on the firewall that connects to the client.

    1. Select NetworkInterfacesCluster Ethernet and Add Interface.
    2. Select the Node ID (1 for this example).
    3. Select the Slot (Slot 4).
    4. Select the Interface Name, for example, node1:ethernet4/6.
    5. Select the Interface Type as Layer3.
    6. On the Config tab, create a Logical Router by adding a Name; click OK.
    7. Create a Security Zone, such as client.
    8. Select IPv4, select the Type as Static, for example, and Add the IPv4 address with netmask (10.1.1.1/24 in this example).

       Alternatively, select IPv6, Enable IPv6 on the interface, select the Type as Static, and Add the IPv6 Address with network prefix length. This task example uses static IP addressing; DHCP, DHCPv6, PPPoE, and PPPoEv6 are also supported.
    9. Select the Advanced tab and then the Other Info tab.
    10. For Management Profile, create a new Interface Management profile to allow access to the interface. Select the management and network services allowed (such as HTTPS, SSH, and Ping) and click OK.
    11. Click OK.
14. Configure the other orphan port on node 2, Slot 2, node2:ethernet2/19, using IP address 10.1.2.1/24 for the interface that faces the server. Create a different security zone. The gray path in the example topology is configured.
15. Configure the AE interface (MC-LAG) for the client-facing interface on Node 1.

    1. Select NetworkInterfacesCluster Ethernet and Add Aggregate Group.
    2. For Interface Name, next to ae, enter the interface number (in this example, 1).
    3. Select Interface Type as Layer3.
    4. On the Config tab, select the same Logical Router.
    5. Select the Security Zone.
    6. Click OK.
    7. Select IPv4, select the Type as Static, and Add the IPv4 address with netmask (10.1.7.1/24 in this example).
    8. (Optional) Configure LACP settings if you want to enable LACP for the aggregate group.
    9. Select the Advanced tab and then the Other Info tab.
    10. For Management Profile, create a new Interface Management profile to allow access to the interface. Select the services allowed and click OK.
    11. Click OK.
16. Configure the AE interface (MC-LAG) for the server-facing interface for Node 1. For this interface, follow similar substeps as in the prior step, but configure AE2, add the IP address (10.1.8.1/24), the same logical router, and a server Security zone.
17. Add an interface member to the MC-LAG on the client side.

    1. Select NetworkInterfacesCluster Ethernet and Add Interface.
    2. On the Cluster Ethernet Interface, select the Node ID Node 1.
    3. Select the Slot (Slot 2).
    4. Select the Interface Name, for example, node1:ethernet2/1.
    5. Select the Interface Type as Aggregate Ethernet.
    6. Select the Aggregate Group, such as ae1.
    7. Click OK.
18. Add a second interface member to the MC-LAG on the client side, assigning Node ID as Node 2, Slot 2, node2:ethernet2/11. Select the same Aggregate Group (ae1).
19. Add an interface member to the MC-LAG on the server side. Select Node 1, Slot 4, node1:ethernet4/16. Select the Aggregate Group, ae2.
20. Add a second interface member to the MC-LAG on the server side, assigning it to Node 2, Slot 6, node2:ethernet6/16. Select the Aggregate Group, such as ae2.
21. (PAN-OS 11.1.5 and later releases) Prepare to configure MACsec for the HSCI ports by creating a MACsec profile.

    IMPORTANT: When you migrate from a non-MACsec cluster to a MACsec cluster, you must do so during a maintenance window.

    1. Select NetworkNetwork ProfilesMACsec Profile and select MACsec Policy.
    2. Add a MACsec crypto profile by Name, which contains zero or more alphanumeric characters, underscores (_), hyphens (-), dots (.), or spaces. The Name is a maximum of 31 characters.
    3. Select the Encryption type: AES-128-GCM (default) or AES-256-GCM.
    4. Select the Confidentiality Offset to specify a number of bytes (starting from the frame header), after which MACsec encrypts the bytes in a frame. Values are 0 (default), 30, or 50.
    5. Enable SCI Include to include the Secure Channel Identifier (SCI) tag in the Security Tag field of the MACsec header. Default is disabled.
    6. Enable Anti Replay to enable replay protection. This allows a MACsec port to accept frames out of order if they are within the Anti Replay Window. Default is disabled.
    7. Specify the Anti Replay Window size in the range 0 to 65,535; the default is 16,384. This value determines the range of packet numbers that the port will accept, for packets that might be out of order. The port will accept packets with a packet number greater than or equal to the last packet number minus the window size. For example, after the port receives packet number 12, if the window is 5, the port will subsequently accept only packets numbered 7 or higher.

       Specify an Anti Replay window size based on the traffic rate because the HSCI ports will likely experience packets arriving out of order due to prioritization or load balancing in the network.
    8. Specify the SAK Rekey Interval (sec) in seconds; range is 60 to 86,400; default is 3,600. Connectivity Association participants negotiate a Secure Association agreement, which includes a cipher suite and keys. A Key Server generates a Secure Association Key (SAK) from the Connectivity Association Key (CAK); the SAK is refreshed at the SAK rekey interval. The end-to-end nodes use the SAK to encrypt traffic for a given session. To avoid the SAKs of all interfaces being refreshed at the same time, MACsec might spread the rekeying actions evenly by subtracting a small random number from the SAK rekey interval.
    9. Click OK.

22. (PAN-OS 11.1.5 and later releases) Create a MACsec Pre Shared Key Profile.

    1. Select NetworkNetwork ProfilesMACsec Profile and select Pre Shared Key.
    2. Add a MACsec Pre Shared Key Profile by Name, which contains zero or more alphanumeric characters, underscores (_), hyphens (-), dots (.), or spaces. The Name is a maximum of 31 characters.
    3. Enter the CKN (Connectivity Association Key Name) that identifies the Connectivity Association Key. The CKN is 1 to 32 bytes of hexadecimal string (2 to 64 hex digits) with an even number of digits; for example, 1234.
    4. Enter the CAK (Connectivity Association Key), which is a 16-byte hexadecimal string (32 hex digits) for AES-128-GCM, or a 32-byte hexadecimal string (64 hex digits) for AES-256-GCM. The CAK is used to generate all other keys used for MACsec. An example CAK for AES-128-GCM is 12345678912345678912345678912345. A CAK for AES-256-GCM is twice as long as a CAK for AES-128-GCM.

       The Pre Shared Key, CKN, and CAK must match on the two ends of the HSCI-A link. Likewise, the Pre Shared Key, CKN, and CAK must match on the two ends of the HSCI-B link.
    5. Click OK.

23. (PAN-OS 11.1.5 and later releases) Commit to Panorama.
24. (PAN-OS 11.1.5 and later releases) Push to Devices and Push Templates so that the devices have the MACsec profiles, thus allowing you to later push the cluster configuration with MACsec enabled.
25. (PAN-OS 11.1.5 and later releases) Identify the leader node and non-leader node.

    1. Access the CLI on one of the firewall nodes. (If you already know which node is the non-leader, access the CLI on the non-leader node.)
    2. >show cluster nodes

26. (PAN-OS 11.1.5 and later releases) Suspend the non-leader node.

    1. Access the CLI on the non-leader node.
    2. >request cluster node state suspend

       The suspension takes approximately 120 seconds (the default delay value).

27. (PAN-OS 11.1.5 and later releases) Confirm the non-leader node is suspended.

    1. >show cluster nodes

28. (PAN-OS 11.1.5 and later releases) Apply your MACsec profiles to the HSCI-A and HSCI-B ports.

    1. Select PanoramaFirewall Clusters and select Summary View.
    2. Select PA-Series or All Clusters.
    3. Select a Cluster Name to edit the cluster.
    4. Select Communications.
    5. Select hsci-a and enter the Key Server Priority in the range from 0 to 255; the default is 16. The lower the value, the higher the priority of the Key Server.

       If the priority values for the HSCI-A links on the two nodes are equal, the node with the lower MAC address is the Key Server. The Key Server (one of the nodes in the cluster) selects and advertises a cipher suite, and also generates the SAK from the CAK.
    6. For Crypto Profile, select the MACsec crypto profile you created or select the default profile.
    7. For Pre Shared Key Profile, select the profile you created.
    8. Select hsci-b and perform the same steps to assign a Key Server Priority and apply the Crypto Profile and Pre Shared Key Profile to the port.
    9. Click OK.

29. (PAN-OS 11.1.5 and later releases) Commit, Commit to Panorama, and Commit.
30. (PAN-OS 11.1.5 and later releases) Push to Devices and Push , which enables MACsec on the ports.
31. (PAN-OS 11.1.5 and later releases) Confirm MACsec is enabled on both ports.

    1. Access the CLI.
    2. >show macsec mka session interface hsci-a
    3. >show macsec mka session interface hsci-b

32. (PAN-OS 11.1.5 and later releases) Unsuspend the non-leader node.

    1. Access the CLI on the non-leader node.
    2. >request cluster node state unsuspend

       It takes a few minutes to unsuspend the non-leader node; the length of time depends on the traffic level.
33. (PAN-OS 11.1.5 and later releases) Verify that both nodes are online.

    1. >show cluster nodes

34. Create Security policy rules.

    1. Select Policies and select the Device Group.
    2. Create Security policy rules to control access, such as allowing a specific source zone, destination zone, address, user, device, application, and service.
35. Configure routing and other features your firewalls require (except for HA). Refer to the PAN-OS Administrator's Guide and the PAN-OS Networking Administrator's Guide.
36. Configure system monitoring for the NGFW cluster.

    1. Select PanoramaFirewall ClustersSummary View and select a cluster or a single firewall in the cluster.
    2. Select System Monitoring.

    3. Select the State Upon Capacity Loss:

       • degraded—Specifies that the firewall will be in a DEGRADED state if the count of functional network cards or data processing cards goes below the configured Minimum Network Cards or Minimum Data Processing Cards, respectively. Furthermore:
         • A cluster node in DEGRADED state has traffic ports down, but is still a part of the sharded (fragmented) member table.
         • Data processing card resources of a DEGRADED cluster node can be used to process traffic and for Layer 7 processing.
         • A cluster node in INIT or ONLINE state transitions to DEGRADED state when a soft fault is reported to the cluster node state machine.
         • A cluster node in ONLINE state transitions to DEGRADED state (and a node in DEGRADED state remains in DEGRADED state) if you suspend the cluster node after a delay (using the CLI operational command: request cluster node state suspend). A delay allows data planes to gracefully complete L7 processing or other processes that were underway.
         • If all soft faults are cleared, the cluster node transitions to INIT state.
         • If a hard fault occurs, a cluster node in DEGRADED state transitions to FAILED state.
         • A cluster node in DEGRADED state transitions to SUSPENDED state if the maximum number of state flaps is seen or you suspend the cluster node.
         • If a chassis has no functional data processing cards remaining (all DPC slots are powered off or in a FAILED state), the cluster node state will be FAILED, even if you configured degraded, because having no functional DPC is a hard fault.
       • failed—Specifies that the firewall will be in a FAILED state if the count of functional network cards or data processing cards goes below the configured Minimum Network Cards or Minimum Data Processing Cards, respectively. Furthermore:
         • A cluster node in FAILED state has traffic ports down and isn't part of the sharded member table.
         • Data processing card resources of a FAILED cluster node can't be used to process traffic or for Layer 7 processing.
         • A cluster node in INIT, ONLINE, or DEGRADED state transitions to FAILED state when a hard fault is reported to the cluster node state machine.
         • A cluster node in FAILED state transitions to INIT state if all hard faults are cleared.
         • A cluster node in FAILED state transitions to SUSPENDED state if the maximum number of state flaps is seen or you suspend the cluster node.

       NGFW Clusters provides a list of hard faults and soft faults.
    4. In the Minimum Chassis Capacity Required section, enter the Minimum Network Cards required; range is 1 to 7, default is 1. When fewer Network Cards than the configured value are functional, the firewall in the cluster goes to the State Upon Capacity Loss that you configured (degraded or failed).
    5. Enter the Minimum Data Processing Cards required; range is 1 to 7, default is 1. When fewer Data Processing Cards than the configured value are functional, the firewall in the cluster goes to the State Upon Capacity Loss that you configured (degraded or failed).
    6. Click OK.
37. (Optional) Configure Log Forwarding for the PA-7500 Series firewall.
38. Push the configuration from Panorama to the PA-7500 Series firewalls in the cluster.

    1. Commit and Commit and Push and Commit.
    2. Commit and Push to Devices, Push All Changes, select the cluster, and Push the configuration to both nodes.
39. View NGFW cluster information for an individual firewall on its Dashboard.

    1. Log on to an individual PA-7500 Series firewall (not Panorama).
    2. Select Dashboard and for Widgets, select System Firewall Cluster to view the Firewall Cluster card, which displays the Cluster Name and Node ID.

40. View NGFW Cluster Summary and Monitoring information and health for the cluster.