Set Up The Panorama Virtual Appliance as a Log Collector
Table of Contents
9.1 (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 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
- 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 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
- 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
-
- 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-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 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
-
- Add a Firewall as a Managed Device
-
- 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
- Manage the Rule Hierarchy
- Manage the Master Key from Panorama
- Redistribute User-ID Information 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
-
- Add Standalone WildFire Appliances to Manage with Panorama
- Configure Basic WildFire Appliance Settings on 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
- Upgrade a Cluster Centrally on Panorama with an Internet Connection
- Upgrade a Cluster Centrally on Panorama without an Internet Connection
-
-
- Manage Licenses on Firewalls Using Panorama
-
- Supported Updates
- Schedule a Content Update Using Panorama
- Upgrade Log Collectors When Panorama Is Internet-Connected
- Upgrade Log Collectors When Panorama Is Not Internet-Connected
- Upgrade Firewalls When Panorama Is Internet-Connected
- Upgrade Firewalls When Panorama Is Not Internet-Connected
- Upgrade a ZTP Firewall
- Revert Content Updates from Panorama
-
- Preview, Validate, or Commit Configuration Changes
- 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
- Troubleshoot Registration or Serial Number Errors
- Troubleshoot Reporting Errors
- Troubleshoot Device Management License Errors
- Troubleshoot Automatically Reverted Firewall Configurations
- Complete Content Update When Panorama HA Peer is Down
- View Task Success or Failure Status
- Restore an Expired Device Certificate
- Downgrade from Panorama 9.1
End-of-Life (EoL)
Set Up The Panorama Virtual Appliance as a Log Collector
How to set up a Panorama virtual appliance on AWS, AWS
GovCloud, Microsoft Azure, KVM, Hyper-V, or ESXi as a Dedicated
Log Collector.
If you want a dedicated virtual appliance
for log collection, configure a Panorama virtual appliance on ESXi,
AWS, AWS GovCloud, Azure, Google Cloud Platform, KVM, or Hyper-V
in Log Collector mode. To do this, you first perform the initial
configuration of the virtual appliance in Panorama mode, which includes
licensing, installing software and content updates, and configuring
the management (MGT) interface. You then switch the Panorama virtual
appliance to Log Collector mode and complete the Log Collector configuration.
Additionally, if you want to use dedicated M-Series
Appliance Interfaces (recommended) instead of the
MGT interface for log collection and Collector Group communication,
you must first configure the interfaces for the Panorama management
server, then configure them for the Log Collector, and then perform
a Panorama commit followed by a Collector Group commit.
Perform
the following steps to set up a new virtual appliance as a Log Collector
or to convert an existing virtual appliance that was previously
deployed as a Panorama management server.
Switching
the virtual appliance from Panorama mode to Log Collector mode reboots
the appliance, deletes the local Log Collector, deletes any existing
log data, and deletes all configurations except the management access
settings. Switching the mode does not delete licenses, software
updates, or content updates.
- Set up the Panorama virtual appliance management
server that will manage the Log Collector if you have not already
done so.Perform one of the following tasks:
- Record the management IP addresses of the Panorama management
server.If you deployed Panorama in a high availability (HA) configuration, you need the IP address of each HA peer.
- Log in to the web interface of the Panorama management server.
- Record the IP Address of the solitary (non-HA) or active (HA) Panorama by selecting PanoramaSetupManagement and checking the Management Interface Settings.
- For an HA deployment, record the Peer HA IP Address of the passive Panorama by selecting PanoramaHigh Availability and checking the Setup section.
- Set up the Panorama virtual appliance that will serve
as a Dedicated Log Collector.If you previously deployed this appliance as a Panorama management server, you can skip this step because the MGT interface is already configured and the licenses and updates are already installed.The Panorama virtual appliance in Log Collector mode does not have a web interface for configuration tasks, only a CLI. Therefore, before changing the mode on the Panorama virtual appliance, use the web interface in Panorama mode to:
- Set up the Panorama virtual appliance in one of the following supported hypervisors:
- Perform Initial Configuration of the Panorama Virtual Appliance.
- Register Panorama and Install Licenses.
- Install Content and Software Updates for Panorama.
- (Panorama on Azure only) Modify the admin password.The Dedicated Log Collector supports only the admin Administrator user in order to change in to Log Collector mode. Modify the admin password to allow you to log in using the admin Administrator user.
- Log in to the Panorama Web Interface.
- Select PanoramaAdministrators and select admin.
- Enter the Password, Confirm Password and click OK.
- Select CommitCommit to Panorama and Commit your changes.
- (Panorama on AWS and Azure only) Delete all
users, except for the admin user.
- Log in to the Panorama Web Interface as admin.
- Select PanoramaAdministrators.
- Select the existing Administrators, except admin, and Delete.
- Select CommitCommit to Panorama and Commit your changes.
- Log in to the Panorama CLI.
- Switch
from Panorama mode to Log Collector mode.
- Switch to Log Collector mode by entering
the following command:
> request system system-mode logger
- Enter Y to confirm the mode
change. The virtual appliance reboots. If the reboot process terminates
your terminal emulation software session, reconnect to the virtual
appliance to see the Panorama login prompt.If you see a CMS Login prompt, this means the Log Collector has not finished rebooting. Press Enter at the prompt without typing a username or password.
- Log back in to the CLI.
- Verify that the switch to Log Collector mode succeeded:
> show system info | match system-mode
If the mode change succeeded, the output displays:system-mode: logger
- Switch to Log Collector mode by entering
the following command:
- Enable connectivity between the Log Collector and Panorama
management server.Enter the following commands at the Log Collector CLI, where <IPaddress1> is for the MGT interface of the solitary (non-HA) or active (HA) Panorama and <IPaddress2> is for the MGT interface of the passive (HA) Panorama, if applicable.
> configure # set deviceconfig system panorama-server <IPaddress1> panorama-server-2 <IPaddress2> # commit # exit
- Record the serial number of the Log Collector.You need the serial number to add the Log Collector as a managed collector on the Panorama management server.
- At the Log Collector CLI, enter the following
command to display its serial number.
> show system info | match serial
- Record the serial number.
- At the Log Collector CLI, enter the following
command to display its serial number.
- Add the Log Collector as a managed collector to the Panorama
management server.
- Select PanoramaManaged Collectors and Add a managed collector.
- In the General settings, enter the serial number (Collector S/N) you recorded for the Log Collector.
- In the Panorama Server IP field,
enter the IP address or FQDN of the solitary (non-HA) or active
(HA) Panorama. For HA deployments, enter the IP address or FQDN
of the passive Panorama peer in the Panorama Server IP
2 field.These IP addresses must specify a Panorama interface that has Device Management and Device Log Collection services enabled. By default, these services are enabled only on the MGT interface. However, you might have enabled the services on other interfaces when you Set Up the M-Series Appliance that is a Panorama management server.
- Select Interfaces, click Management, and enter the Public IP Addressof the Dedicated Log Collector.
- Click OK twice to save your changes to the Log Collector.
- Select CommitCommit to Panorama and Commit your changes to the Panorama configuration.
- Verify that PanoramaManaged Collectors lists the
Log Collector you added. The Connected column displays a check mark
to indicate that the Log Collector is connected to Panorama. You
might have to wait a few minutes before the page displays the updated
connection status.At this point, the Configuration Status column displays Out of Sync and the Run Time Status column displays disconnected. The status will change to In Sync and connected after you configure a Collector Group.
- Enable the logging disks.
- Select PanoramaManaged Collectors and edit the Log Collector.
- Select Disks and Add each disk.
- Click OK to save your changes.
- Select CommitCommit to Panorama and Commit your changes to the Panorama configuration.
- (Recommended) Configure the Ethernet1, Ethernet2, Ethernet3, Ethernet4,
and Ethernet5 interfaces if the Panorama management
server and Log Collector will use them for Device Log
Collection (receiving logs from firewalls) and Collector Group
Communication.If you previously deployed the Log Collector as a Panorama management server and configured these interfaces, you must reconfigure them because switching to Log Collector mode would have deleted all configurations except the management access settings.
- Configure each interface on the Panorama
management server (other than the MGT interface) if you haven’t
already:
- Select PanoramaSetupInterfaces and click the Interface Name.
- Select <interface-name> to enable the interface.
- Complete one or both of the following field sets based on the IP protocols of your network:
- For ESXi
- IPv4—Public IP Address, IP Address, Netmask, and Default GatewayIPv6—IPv6 Address/Prefix Length and Default IPv6 Gateway
- For AWS, Azure, and Google™ Cloud Platform
- Public IP address
- Select the Device Management Services that the interface supports:Device Management and Device Log Collection—You can assign one or more interfaces.Collector Group Communication—You can assign only one interface.Device Deployment (software and content updates)—You can assign only one interface.
- Click OK to save your changes.
- Configure each interface on the Log Collector (other
than the MGT interface):
- Select PanoramaManaged Collectors and edit the Log Collector.
- Select Interfaces and click the name of the interface.
- Select <interface-name> to enable the interface.
- Complete one or both of the following field sets based on the IP protocols of your network:
- For ESXi
- IPv4—Public IP Address, IP Address, Netmask, and Default GatewayIPv6—IPv6 Address/Prefix Length and Default IPv6 Gateway
- For AWS and Azure
- Public IP address
- Select the Device Management Services that the interface supports:Device Log Collection—You can assign one or more interfaces.Collector Group Communication—You can assign only one interface.
- Click OK to save your changes to the interface.
- Click OK to save your changes to the Log Collector.
- Select CommitCommit to Panorama and Commit your changes to the Panorama configuration.
- Configure each interface on the Panorama
management server (other than the MGT interface) if you haven’t
already:
- (Optional) If your deployment is using custom
certificates for authentication between Panorama and managed devices,
deploy the custom client device certificate. For more information,
see Set
Up Authentication Using Custom Certificates.
- Select PanoramaCertificate ManagementCertificate Profile and choose the certificate profile from the drop-down or click New Certificate Profile to create one.
- Select PanoramaManaged CollectorsAddCommunication for a Log Collector.
- Select the Secure Client Communication check box.
- Select the type of device certificate the Type drop-down.
- If you are using a local device certificate, select the Certificate and Certificate Profile from the respective drop-downs.
- If you are using SCEP as the device certificate, select the SCEP Profile and Certificate Profile from the respective drop-downs.
- Click OK.
- (Optional) Configure Secure Server Communication
Sn a Log Collector. For more information, see Set
Up Authentication Using Custom Certificates.
- Select PanoramaManaged CollectorsAddCommunication.
- Verify that the Custom Certificate Only check
box is not selected. This allows you to continue managing all devices
while migrating to custom certificates.When the Custom Certificate Only check box is selected, the Log Collector does not authenticate and cannot receive logs from devices using predefined certificates.
- Select the SSL/TLS service profile from the SSL/TLS Service Profile drop-down. This SSL/TLS service profile applies to all SSL connections between the Log Collector and devices sending it logs.
- Select the certificate profile from the Certificate Profile drop-down.
- Select Authorize Client Based on Serial Number to have the server check clients against the serial numbers of managed devices. The client certificate must have the special keyword $UDID set as the CN to authorize based on serial numbers.
- In Disconnect Wait Time (min),
enter the number of minutes Panorama should wait before breaking
and reestablishing the connection with its managed devices. This
field is blank by default and the range is 0 to 44,640 minutes.The disconnect wait time does not begin counting down until you commit the new configuration.
- (Optional) Configure an authorization list.
- Click Add under Authorization List.
- Select the Subject or Subject Alt Name as the Identifier type.
- Enter an identifier of the selected type.
- Click OK.
- Select Check Authorization List to enforce the authorization list.
- Click OK.
- Select CommitCommit to Panorama.
- Assign
the Log Collector to a Collector Group.
- Configure
a Collector Group. You must perform a Panorama commit and
then a Collector Group commit to synchronize the Log Collector configuration
with Panorama and to put the Eth1, Eth2, Eth3, Eth4, and Eth5 interfaces
(if you configured them) in an operational state on the Log Collector.In any single Collector Group, all the Log Collectors must run on the same Panorama model: all M-600 appliances, all M-500 appliances, all M-200 appliances, all M-100 appliances, or all Panorama virtual appliances.As a best practice, Enable log redundancy across collectors if you add multiple Log Collectors to a single Collector group. This option requires each Log Collector to have the same number of logging disks.
- Select PanoramaManaged Collectors to verify
that the Log Collector configuration is synchronized with Panorama.The Configuration Status column should display In Sync and the Run Time Status column should display connected.
- Access the Log Collector CLI and enter the following
command to verify that its interfaces are operational:
> show interface all
The output displays the state as up for each interface that is operational. - If the Collector Group has multiple Log Collectors, Troubleshoot Connectivity to Network Resources to verify they can communicate with each other by performing a Ping connectivity test for each interface that the Log Collectors use. For the source IP address, specify the interface of one of the Log Collectors. For the host IP address, specify the matching interface of another Log Collector in the same Collector Group.
- Configure
a Collector Group. You must perform a Panorama commit and
then a Collector Group commit to synchronize the Log Collector configuration
with Panorama and to put the Eth1, Eth2, Eth3, Eth4, and Eth5 interfaces
(if you configured them) in an operational state on the Log Collector.
- Next steps...To enable the Log Collector to receive firewall logs: