Increase the System Disk for Panorama on Azure

1. Add a 224GB system disk to replace the default 81GB system disk.

   1. Log in to the Azure Console.
   2. Expand Settings and click Disks > Create and attach a new disk.

   3. Enter a Disk name to the new disk you are creating.
   4. Select the Storage type and Encryption similar to the ones you had selected for the 81 GB disk.
   5. Enter 224 as the Size (GB).
   6. Select Read/write option for Host caching.
   7. Click Apply.
2. Check the disk size in the Panorama.

3. Reboot the Panorama.
4. Initiate disk cloning.

   1. Initiate disk cloning by executing the following command:

      request system clone-system-disk target <disk name>
   2. Verify the ongoing cloning status from the console.

   3. Shutdown the Panorama VM from the Azure console.
5. Detach the data disk from the Panorama VM to which it was added initially, and convert the data disk to OS disk using powershell commands.

   $managedDisk = Get-AzDisk -DiskName pnrma_new_data_disk -ResourceGroupName arus-cpt-pnrma-rg
   # Create disk configuration for the copy
   $diskConfig = New-AzDiskConfig -SourceResourceId $managedDisk.Id -Location $managedDisk.Location -CreateOption Copy -OsType Linux
   New-AzDisk  -Disk $diskConfig -DiskName  pnrma_new_data_os_disk -ResourceGroupName arus-cpt-pnrma-rg   
   
   pnrma_new_data_disk     -  name of the Data Disk that was initially created in the previous step
   arus-cpt-pnrma-rg            -  name of the resource group where disk is present
   pnrma_new_data_os_disk -  name of the new os disk that will be created
   

   $managedDisk = Get-AzDisk -DiskName pnrma_new_data_disk -ResourceGroupName arus-cpt-pnrma-rg

   $diskConfig = New-AzDiskConfig -SourceResourceId $managedDisk.Id -Location $managedDisk.Location -CreateOption

   New-AzDisk -Disk $diskConfig -DiskName pnrma_new_data_os_disk -ResourceGroupName arus-cpt-pnrma-rg

6. Verify the OS disk you created.

7. Create an Azure compute gallery.

   1. From the Azure Console home page, click Azure compute galleries.
   2. In the Azure compute gallery page, Click Create.
   3. Select a Resource group.
   4. You may retain the default settings for Sharing and Tags tabs.
   5. Click Review+create.

8. Add a VM image definition from the Azure compute gallery.

   1. Add the following details:

      • Subscription
      • Resource Group
      • Region
      • Target Azure Compute Gallery
      • VM image definition name
      • OS type
      • Security type
      • VM generation
      • Higher storage performance with NVMe
      • Accelerated networking
      • VM architecture
      • Hibernation supported
      • OS state
      • Publisher - Enter publisher as paloaltonetworks
      • Offer - Enter offer as panorama
      • SKU - Enter SKU as byol

      • Ensure that the region, publisher, SKU, offer, and VM-Deployment sections are similar to that of the existing Panorama. You can view this information in the Source image details section of the VM Overview page in Azure Portal page.
      • The OS disk must be the one you created in step 5. Ensure that you select this OS disk under the version tab while creating a VM definition.
      • The CPU and memory values must be the same as that of the Panorama.

   2. Click Review+Create to create the Azure compute gallery.
9. Create a VM from the Azure compute gallery.

   1. Click the VM definition and click Create VM to create a VM from the Azure compute gallery. This will create a new Panorama instance which will boot from the VM definition.

   1. Configure the Basics settings.

      1. When choosing the image, select the relevant Gallery Image definition that was created in previous steps.
      2. Ensure that the Azure infrastructure-related options align with the existing Panorama configuration.

   2. Add the Disks settings and ensure that the OS Disk selected is 224GB or more.

   3. Add the Networking settings similar to that of the existing Panorama. This will bring up a new panorama with the resized OS disk details.

10. Execute the following command to verify if the panrepo folder size has increased:

    Show system disk space

11. The new Panorama will have a different private IP address. You need to configure it with the same IP address as the existing Panorama. To make the existing Panorama's IP address available, assign a temporary, unused IP address to the existing Panorama. The existing Panorama's IP address can only be changed when the VM is shut down. From the Azure portal, assign the existing Panorama's IP address to the new Panorama's interface. Once the IP addresses are swapped, the Network Interface Card (NIC) will reset, and the new Panorama will then have the IP address of the existing Panorama.

    To change private/public IP of the Panorama, click PanoramaVM > Network Settings > IP configurations. Select the network for which you need to change the IP address and click Edit.

12. If your existing Panorama had any data disks, detach them and then reattach them to the new Panorama. Finally, boot the Panorama. The new Panorama should now have all devices connected and function identically to the existing Panorama.

    For an Active-Passive Panorama setup, apply these steps first to the Passive Panorama, then repeat them for the Active Panorama.

    In case of a Cloud NGFW set-up, the newly deployed Panorama instance will be assigned a different Private IP address. It is necessary to configure this new instance to use the same IP address as the existing Panorama.

    To make the existing Panorama IP available to the new Panorama instance, you must first assign a temporary, unused IP address to the current Panorama. The existing Panorama IP address can only be changed while the VM is shut down.

    Assign the existing Panorama IP to the new Panorama interface from the Azure portal. Interchanging the IP addresses will cause the NIC to reset, resulting in the new Panorama instance adopting the IP address of the existing Panorama instance. After replacing the existing Panorama, complete the following steps:

    1. If the original Panorama had any data disks, detach them and reattach them to the new Panorama instance.
    2. Start the new Panorama instance. The new Panorama should now be fully functional, with all devices connected, and operating the same way as the original Panorama.
    3. After the Panorama is back online, you must re-fetch the device certificate and licenses.