Add a Virtual Disk to Panorama on an ESXi Server
Table of Contents
11.0 (EoL)
Expand all | Collapse all
-
- Determine Panorama Log Storage Requirements
-
- Setup Prerequisites for the Panorama Virtual Appliance
- Perform Initial Configuration of the Panorama Virtual Appliance
- Set Up The Panorama Virtual Appliance as a Log Collector
- Set Up the Panorama Virtual Appliance with Local Log Collector
- Set up a Panorama Virtual Appliance in Panorama Mode
- Set up a Panorama Virtual Appliance in Management Only Mode
-
- Preserve Existing Logs When Adding Storage on Panorama Virtual Appliance in Legacy Mode
- Add a Virtual Disk to Panorama on an ESXi Server
- Add a Virtual Disk to Panorama on vCloud Air
- Add a Virtual Disk to Panorama on Alibaba Cloud
- Add a Virtual Disk to Panorama on AWS
- Add a Virtual Disk to Panorama on Azure
- Add a Virtual Disk to Panorama on Google Cloud Platform
- Add a Virtual Disk to Panorama on KVM
- Add a Virtual Disk to Panorama on Hyper-V
- Add a Virtual Disk to Panorama on Oracle Cloud Infrastructure (OCI)
- Mount the Panorama ESXi Server to an NFS Datastore
-
- Increase CPUs and Memory for Panorama on an ESXi Server
- Increase CPUs and Memory for Panorama on vCloud Air
- Increase CPUs and Memory for Panorama on Alibaba Cloud
- Increase CPUs and Memory for Panorama on AWS
- Increase CPUs and Memory for Panorama on Azure
- Increase CPUs and Memory for Panorama on Google Cloud Platform
- Increase CPUs and Memory for Panorama on KVM
- Increase CPUs and Memory for Panorama on Hyper-V
- Increase the CPUs and Memory for Panorama on Oracle Cloud Infrastructure (OCI)
- Complete the Panorama Virtual Appliance Setup
-
- Convert Your Evaluation Panorama to a Production Panorama with Local Log Collector
- Convert Your Evaluation Panorama to a Production Panorama without Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing with Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing without Local Log Collector
- Convert Your Production Panorama to an ELA Panorama
-
- Register Panorama
- Activate a Panorama Support License
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is Internet-connected
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is not Internet-connected
- Activate/Retrieve a Firewall Management License on the M-Series Appliance
- Install the Panorama Device Certificate
- Install the Device Certificate for a Dedicated Log Collector
-
- Migrate from a Panorama Virtual Appliance to an M-Series Appliance
- Migrate a Panorama Virtual Appliance to a Different Hypervisor
- Migrate from an M-Series Appliance to a Panorama Virtual Appliance
- Migrate from an M-500 Appliance to an M-700 Appliance
- Migrate from an M-600 Appliance to an M-700 Appliance
- Migrate from an M-100 Appliance to an M-500 Appliance
- Migrate from an M-100 or M-500 Appliance to an M-200 or M-600 Appliance
-
- Configure an Admin Role Profile
- Configure an Admin Role Profile for Selective Push to Managed Firewalls
- Configure an Access Domain
-
- Configure a Panorama Administrator Account
- Configure Local or External Authentication for Panorama Administrators
- Configure a Panorama Administrator with Certificate-Based Authentication for the Web Interface
- Configure an Administrator with SSH Key-Based Authentication for the CLI
- Configure RADIUS Authentication for Panorama Administrators
- Configure TACACS+ Authentication for Panorama Administrators
- Configure SAML Authentication for Panorama Administrators
- Configure Tracking of Administrator Activity
-
- Add a Firewall as a Managed Device
- Change Between Panorama Management and Cloud Management
-
- Add a Device Group
- Create a Device Group Hierarchy
- Create Objects for Use in Shared or Device Group Policy
- Revert to Inherited Object Values
- Manage Unused Shared Objects
- Manage Precedence of Inherited Objects
- Move or Clone a Policy Rule or Object to a Different Device Group
- Push a Policy Rule to a Subset of Firewalls
- Device Group Push to a Multi-VSYS Firewall
- Manage the Rule Hierarchy
- Manage the Master Key from Panorama
- Schedule a Configuration Push to Managed Firewalls
- Redistribute Data to Managed Firewalls
-
- Plan the Transition to Panorama Management
- Migrate a Firewall to Panorama Management and Reuse Existing Configuration
- Migrate a Firewall to Panorama Management and Push a New Configuration
- Migrate a Firewall HA Pair to Panorama Management and Reuse Existing Configuration
- Migrate a Firewall HA Pair to Panorama Management and Push a New Configuration
- Load a Partial Firewall Configuration into Panorama
- Localize a Panorama Pushed Configuration on a Managed Firewall
-
- Configure a Managed Collector
- Monitor Managed Collector Health Status
- Configure Log Forwarding to Panorama
- Configure Syslog Forwarding to External Destinations
- Forward Logs to Strata Logging Service
- Verify Log Forwarding to Panorama
- Modify Log Forwarding and Buffering Defaults
- Configure Log Forwarding from Panorama to External Destinations
-
- Add Standalone WildFire Appliances to Manage with Panorama
- Remove a WildFire Appliance from Panorama Management
-
-
- Configure a Cluster and Add Nodes on Panorama
- Configure General Cluster Settings on Panorama
- Remove a Cluster from Panorama Management
- Configure Appliance-to-Appliance Encryption Using Predefined Certificates Centrally on Panorama
- Configure Appliance-to-Appliance Encryption Using Custom Certificates Centrally on Panorama
- View WildFire Cluster Status Using Panorama
-
-
- Preview, Validate, or Commit Configuration Changes
- Commit Selective Configuration Changes for Managed Devices
- Push Selective Configuration Changes to Managed Devices
- Enable Automated Commit Recovery
- Compare Changes in Panorama Configurations
- Manage Locks for Restricting Configuration Changes
- Add Custom Logos to Panorama
- Use the Panorama Task Manager
- Reboot or Shut Down Panorama
- Configure Panorama Password Profiles and Complexity
-
-
- Verify Panorama Port Usage
- Resolve Zero Log Storage for a Collector Group
- Replace a Failed Disk on an M-Series Appliance
- Replace the Virtual Disk on an ESXi Server
- Replace the Virtual Disk on vCloud Air
- Migrate Logs to a New M-Series Appliance in Log Collector Mode
- Migrate Logs to a New M-Series Appliance in Panorama Mode
- Migrate Logs to a New M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Logs to the Same M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Log Collectors after Failure/RMA of Non-HA Panorama
- Regenerate Metadata for M-Series Appliance RAID Pairs
- View Log Query Jobs
- Troubleshoot Registration or Serial Number Errors
- Troubleshoot Reporting Errors
- Troubleshoot Device Management License Errors
- Troubleshoot Automatically Reverted Firewall Configurations
- View Task Success or Failure Status
- Generate a Stats Dump File for a Managed Firewall
- Recover Managed Device Connectivity to Panorama
- Restore an Expired Device Certificate
End-of-Life (EoL)
Add a Virtual Disk to Panorama on an ESXi Server
To expand log storage capacity on the Panorama
virtual appliance, you can add virtual logging disks. If the appliance
is in Panorama mode, you can add 1 to 12 virtual logging disks of
2TB each or 1 24TB logging disk, for a maximum total of 24TB. If
the appliance is in Legacy mode, you can add one virtual logging
disk of up to 8TB on ESXi 5.5 and later versions or one disk of
up to 2TB on earlier ESXi versions. Additionally, it is recommended
to add logging disks with the same disk provisioning format to avoid
any unexpected performance that may arise from having multiple disk
with different provisioning formats.
If Panorama loses
connectivity to the new virtual disk, Panorama might lose logs during
the failure interval.
To allow for redundancy, use the virtual
disk in a RAID configuration. RAID10 provides the best write performance
for applications with high logging characteristics.
If necessary,
you can Replace
the Virtual Disk on an ESXi Server.
- Add additional disks to PanoramaIn all modes, the first logging disk on the Panorama VM must be at least 2TB in order to add additional disks. If the first logging disk is smaller than 2TB, you will be unable to add additional disk space.
- Access the VMware vSphere Client and select Virtual Machines.Right-click the Panorama virtual appliance and select PowerPower off.Right-click the Panorama virtual appliance and select Edit Settings.Click Add in the Hardware tab to launch the Add Hardware wizard.Select Hard Disk as the hardware type and click Next.Create a new virtual disk and click Next.Set the Disk Size. If the Panorama virtual appliance is in Panorama mode, set the size to at least 2TB. If the appliance is in Legacy mode, you can set the size to as much as 8TB.In Panorama mode, you can add disk sizes larger than 2TB and Panorama will automatically create as many 2TB partitions as possible. For example, if disk sdc was 24TB, it will create 12 2TB partitions. These disks will be named sdc1-12.Select the Disk Provisioning format and click Next.Specify a datastore or datastore structure, Browse to a datastore with enough space for the specified Disk Size, click OK, and click Next.Select a SCSI Virtual Device Node (you can use the default selection) and click Next.The selected node must be in SCSI format; Panorama will fail to boot if you select another format.Verify that the settings are correct and then click Finish and OK.The new disk appears in the list of devices for the virtual appliance.Repeat Step 4 through Step 11 to add additional disks to the Panorama virtual appliance if necessary.Right click the Panorama virtual appliance and select PowerPower On. The virtual disk initializes for first-time use. The size of the new disk determines how long initialization takes.Configure each disk.The following example uses the sdc virtual disk.
- Log in to the Panorama CLI.Enter the following command to view the disks on the Panorama virtual appliance:show system disk detailsThe user will see the following response:
Name : sdb State : Present Size : 2048000 MB Status : Available Reason : Admin enabled Name : sdc State : Present Size : 2048000 MB Status : Available Reason : Admin disabled
Enter the following command and confirm the request when prompted for all disks with the Reason : Admin disabled response:request system disk add sdcThe request system disk add command is not available on a Panorama management server in Management Only mode because logging is not supported in this mode. If you do not see the command, Set up a Panorama Virtual Appliance in Panorama Mode to enable the logging disks. Once in Panorama mode, Log in to the Panorama CLI and continue to Step 4 to verify the disk addition.Enter the show system disk details command to verify the status of the disk addition. Continue to Step 3 when all newly added disk responses display Reason : Admin enabled.Make disks available for logging.- Log in to the Panorama web interface.Select PanoramaManaged Collectors and edit the Log Collector.Select Disks and Add each newly added disk.Click OK.Select CommitCommit to Panorama.For Panorama in an Active/Passive high availability (HA) configuration, wait for HA sync to complete before continuing.Select CommitPush to Devices and push the changes to the Collector Group the Log Collector belongs to.Configure Panorama to receive logs.This step is intended for new Panorama deployments in Panorama mode. If you are adding logging disks to an existing Panorama virtual appliance, continue to Step 5.
- Configure a Managed Collector.Configure a Collector Group.Configure Log Forwarding to Panorama.Verify that the Panorama Log Storage capacity has been increased.
- Log in to the Panorama web interface.Select PanoramaCollector Groups and select the Collector Group that the Panorama virtual appliance belongs to.Verify that the Log Storage capacity accurately displays the disk capacity.