How to Migrate URL Database from BrightCloud to PAN-DB on HA Devices

How to Migrate URL Database from BrightCloud to PAN-DB on HA Devices

44046
Created On 09/25/18 19:43 PM - Last Modified 08/14/21 17:23 PM


Resolution


Overview

This document describes how to migrate the URL database from BrightCloud to PAN-DB on a High Availability (HA) pair of Palo Alto Networks devices.

 

Steps

  1. Suspend the Passive/Secondary device.
  2. Go to Device > High Availability > Operational commands  and suspend local device
  3.  Or from the CLI, execute the command below: 
    > request high-availability state suspend
  4. Run the following command on the Passive/Suspended device, if not already set 
    > set session tcp-reject-non-syn no
  5. Retrieve PAN-DB URL licenses from Device > Licenses tab.
  6. Activate the PAN-DB license on the suspended device (or Activate the Database from Device > License tab):
    > set system setting url-database paloaltonetworks
  7. Once activated, make the secondary device functional with the command below. However, this device will come up as "Non-functional" due to DB mismatch with the peer:
    > request high-availability state functional


    Note: When the device is showing as "Non-functional" after issuing the command above, all the interface will still be power down except for HA interface and that is expected.
     
  8. Suspend the Active/Primary device, this will make the secondary device functional.
    Note: While the device is in non-functional state, the sessions will not be synced. Since non-syn TCP is allowed, most of the existing TCP traffic will not be dropped
     
  9. Download and activate the PAN-DB license on this device (Steps 3 and 4) .
  10. Both devices are now using PAN-DB, once both devices are functional failover back to the original Primary/Active device.
  11. Revert back to original settings on secondary device:
> set session tcp-reject-non-syn yes
 

Delete the Brightcloud DB from the firewall once the above steps are completed.
It to be done manually as the Database is not removed even after the migrations to PAN-DB is complete.
This is to make it easy to switch back to Brightcloud if needed.
It is recommended to delete the Brightcloud DB after successful migration to PAN-DB so that the Disk space used by Brightcloud DB can be freed.

> delete url-database brightcloud

owner: kalavi



Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Clc5CAC&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail

Choose Language