• When the memory allocated is less than 4.5GB, you cannot upgrade the firewall. The following error message displays: Failed to install 9.0.0 with the following error: VM-50 in 9.0.0 requires 5.5GB memory, VM-50 Lite requires 4.5GB memory.Please configure this VM with enough memory before upgrading.
• If the memory allocation is more than 4.5GB but less that the licensed capacity requirement for the model, it will default to the capacity associated with the VM-50.
  The System log message System capacity adjusted to VM-50 capacity due to insufficient memory for VM-<xxx> license, indicates that you must allocate the additional memory required for licensed capacity for the firewall model.

• set session hwpredict disable yes

• Modify the PAN-DB Server IP address on the managed firewall.
  1. On the web interface, delete the PAN-DB Server IP address (DeviceSetupContent IDURL Filtering settings).
  2. Commit your changes.
  3. Add the new M-500 Eth1/1 IP PAN-DB IP address.
  4. Commit your changes.
• Restart the firewall (devsrvr) process.
  1. Log in to the firewall CLI.
  2. Restart the devsrvr process: debug software restart process device-server

1. Generate or import the new certificate in a Certificate Profile (DeviceCertificate ManagementCertificatesDevice Certificates) and select the appropriate vsys Location when you generate or import the certificate.
2. When you create or edit the Certificate Profile, specify the vsys Location and Add the certificate that you generated (or imported) from the list of existing certificates.

• Initiate a Commit to Panorama operation followed by a Push to Devices operation for the modified device group and template configurations.
• Manually select the devices that belong to the modified device group and template configurations.

• Save and export the configuration before you downgrade.
• After you downgrade, load the saved configuration and commit your changes. The firewall will resume operation without the HA configuration.

• Switch to the firewall Context on the Panorama management server.
• Commit changes when a dynamic update is being installed.
• Generate a custom report when a dynamic update is being installed.
• Generate custom reports during a commit.

> configure

# set
template  <template_name>  config
deviceconfig high-availability interface ha2 ip-address <IP_address>

• You did not configure a worker list to add at least one worker node to the cluster. (In a two-node cluster, both nodes are controller nodes configured as an HA pair. Adding a worker node would make the cluster a three-node cluster.)
• You did not configure a service advertisement (either by enabling or not enabling advertising DNS service on the controller nodes).

• After you import the two-node cluster into Panorama, push the configuration from Panorama to the cluster. After the push succeeds, Panorama reports that the controller nodes are in sync.
• Configure a worker list on the cluster controller:

  admin@wf500(active-controller)# set
  deviceconfig cluster mode controller worker-list <worker-ip-address>

  (<worker-ip-address> is the IP address of the worker node you are adding to the cluster.) This creates a three-node cluster. After you import the cluster into Panorama, Panorama reports that the controller nodes are in sync. When you want the cluster to have only two nodes, use a different workaround.
• Configure service advertisement on the local CLI of the cluster controller and then import the configuration into Panorama. The service advertisement can advertise that DNS is or is not enabled.

  admin@wf500(active-controller)# set
  deviceconfig cluster mode controller service-advertisement dns-service
  enabled
  yes

  or

  admin@wf500(active-controller)# set
  deviceconfig cluster mode controller service-advertisement dns-service
  enabled
  no

  Both commands result in Panorama reporting that the controller nodes are in sync.

• nCipher nShield Connect—The firewall requires at least four minutes to detect that an HSM was disconnected, causing SSL functionality to be unavailable during the delay.
• SafeNet Network—When losing connectivity to either or both HSMs in an HA configuration, the display of information from the show high-availability state and show hsm info commands are blocked for 20 seconds.