(/content/techdocs/en_US.

html)

Updated on Thu Mar 13 20:26:10 UTC 2025

Home (/) | Panorama (/content/techdocs/en_US/panorama.html)

| Panorama Administrator's Guide (/content/techdocs/en_US/panorama/10-1/panorama-admin.html)
| Set Up Panorama (/content/techdocs/en_US/panorama/10-1/panorama-admin/set-up-panorama.html)
| Set Up the M-Series Appliance (/content/techdocs/en_US/panorama/10-1/panorama-admin/set-up-panorama/set-up-the-m-series-
appliance.html)
| Set Up the M-Series Appliance as a Log Collector (/content/techdocs/en_US/panorama/10-1/panorama-admin/set-up-panorama/set-up-
the-m-series-appliance/set-up-the-m-series-appliance-as-a-log-collector.html)

DOWNLOAD PDF (/CONTENT/DAM/TECHDOCS/EN_US/PDF/PANORAMA/10-1/PANORAMA-ADMIN/PANORAMA-

ADMIN.PDF)

Panorama Administrator's Guide

(/content/techdocs/en_US/panorama/10-
1/panorama-admin.html)
Set Up the M-Series Appliance as a Log Collector

Table of Contents

If you want a dedicated appliance for log collection, configure an M-200, M-500, or M-600 appliance in Log Collector mode.
To do this, you first perform the initial configuration of the appliance in Panorama mode, which includes licensing, installing
software and content updates, and configuring the management (MGT) interface. You then switch the M-Series appliance to
Log Collector mode and complete the Log Collector configuration. Additionally, if you want to use dedicated M-Series
Appliance Interfaces (/content/techdocs/en_US/panorama/10-1/panorama-admin/set-up-panorama/set-up-the-m-series-
appliance/m-series-appliance-interfaces.html#id6bd65976-95fb-484b-91f6-65639d0fb260) ( 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 M-Series appliance as a Log Collector or to convert an existing M-Series appliance
that was previously deployed as a Panorama management server.

If you are configuring an M-Series appliance in Log Collector mode with 10GB interfaces, you must com-
plete this entire configuration procedure for the 10GB interfaces to display as Up.

Switching the M-Series 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 man-

 agement access settings. Switching the mode does not delete licenses, software updates, or content
updates.

STEP 1 -
This site usesSet
cookies essential
up the Panorama to its management
operation, for analytics, and will
server that for personalized
manage thecontent and ads. ifByyou have not already done so.
Log Collector
continuing to browse this site, you acknowledge the use of cookies. Privacy statement ❯ Cookie Settings
Perform one of the following tasks:
(https://www.paloaltonetworks.com/legal-notices/privacy)
 Set Up the Panorama Virtual Appliance (/content/techdocs/en_US/panorama/10-1/panorama-admin/set-
up-panorama/set-up-the-panorama-virtual-appliance.html#id2a72f335-ec44-4af8-9a72-f584cfcf450e)

Set Up the M-Series Appliance (/content/techdocs/en_US/panorama/10-1/panorama-admin/set-up-

panorama/set-up-the-m-series-appliance.html#id383e50d3-22a6-4ebf-9995-b0224cfffaf7)

STEP 2 -
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.

A Log in to the web interface of the Panorama management server.

B Record the IP Address of the solitary (non-HA) or active (HA) Panorama by selecting Panorama > Setup >
Management and checking the Management Interface Settings.

C For an HA deployment, record the Peer HA IP Address of the passive Panorama by selecting Panorama >
High Availability and checking the Setup section.

STEP 3 -
Set up the M-Series 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 M-Series appliance in Log Collector mode does not have a web interface for configuration tasks, only a CLI.
Therefore, before changing the mode on the M-Series appliance, use the web interface in Panorama mode to:

A Perform Initial Configuration of the M-Series Appliance (/content/techdocs/en_US/panorama/10-

1/panorama-admin/set-up-panorama/set-up-the-m-series-appliance/perform-initial-configuration-of-the-
m-series-appliance.html#id18ac8feb-d32f-4e7e-b3fe-c0649814ba24).

B Register Panorama and Install Licenses (/content/techdocs/en_US/panorama/10-1/panorama-admin/set-

up-panorama/register-panorama-and-install-licenses.html#id8efb174f-7c44-4ea0-b3c0-4766ada61ab7).

C Install Content and Software Updates for Panorama (https://docs.paloaltonetworks.com/pan-os/10-1/pan-

os-upgrade/upgrade-panorama.html).

STEP 4 -
Access the CLI of the M-Series appliance.

A Connect to the M-Series appliance in one of the following ways:

Attach a serial cable from your computer to the Console port on the M-Series appliance. Then use

terminal emulation software (9600-8-N-1) to connect.

Use terminal emulation software such as PuTTY to open an SSH session to the IP address that you

specified for the MGT interface of the M-Series appliance during initial configuration.
This site uses cookies essential to its operation, for analytics, and for personalized content and ads. By
continuing to browse this site, you acknowledge the use of cookies. Privacy statement ❯
(https://www.paloaltonetworks.com/legal-notices/privacy)
 B Log in to the CLI when prompted. Use the default admin account and the password that you specified
during initial configuration.

STEP 5 -
Switch from Panorama mode to Log Collector mode.

A Switch to Log Collector mode by entering the following command:

> request system system-mode logger

B Enter Y to confirm the mode change. The M-Series appliance reboots. If the reboot process terminates your
terminal emulation software session, reconnect to the M-Series 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.

C Log back in to the CLI.

D 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

STEP 6 -
Configure the logging disks as RAID1 pairs.

If you previously deployed the appliance as a Panorama management server, you can skip this step because the
disk pairs are already configured and available.

The time required to configure the drives varies from several minutes to a couple of hours,
based on the amount of data on the drives.

A Determine which disk pairs are present for configuring as RAID pairs on the M-Series appliance:

> show system raid detail

This site uses cookies essential to its operation, for analytics, and for personalized content and ads. By
continuing to browse this site, you acknowledge the use of cookies. Privacy statement ❯
(https://www.paloaltonetworks.com/legal-notices/privacy)
 Perform the remaining steps to configure each disk pair that has present disks. This example uses disk pair

A1/A2.

B To add the first disk in the pair, enter the following command and enter y when prompted to confirm the
request:

> request system raid add A1

Wait for the process to finish before adding the next disk in the pair. To monitor the progress of the RAID
configuration, re-enter:

> show system raid detail

After the process finishes for the first disk, the output displays the disk pair status as Available but degraded.

C Add the second disk in the pair:

> request system raid add A2

D Verify that the disk setup is complete:

> show system raid detail

After the process finishes for the second disk, the output displays the disk pair status as Available and
clean:

Disk Pair A Available

Status clean

STEP 7 -
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

This site usesSTEP

cookies8essential
- to its operation, for analytics, and for personalized content and ads. By
continuing toRecord
browse this site, you acknowledge
the serial number of thethe
Loguse of cookies. Privacy statement
Collector. ❯
(https://www.paloaltonetworks.com/legal-notices/privacy)
 You need the serial number to add the Log Collector as a managed collector on the Panorama management
server.

A At the Log Collector CLI, enter the following command to display its serial number.

> show system info | match serial

B Record the serial number.

STEP 9 -
Create a device registration authentication key.

A Select Panorama > Device Registration Auth Key and Add a new authentication key.

B Configure the authentication key.

Name—Add a descriptive name for the authentication key.

Lifetime—Specify the key lifetime for how long you can use the authentication key to onboard new Log
Collectors.

Count—Specify how many times you can use the authentication key to onboard new Log Collectors.

Device Type—Specify that this authentication key is used to authenticate only a Log Collector.

You can select Any to use the device registration authentication key to onboard fire-
walls, Log Collectors, and WildFire appliances.

( Optional ) Devices—Enter one or more device serial numbers to specify for which Log Collectors the

authentication key is valid.

C Click OK.

D Copy Auth Key and Close.

STEP 10 -
Add the Log Collector as a managed collector to the Panorama management server.

This site uses cookies essential to its operation, for analytics, and for personalized content and ads. By
continuing to browse this site, you acknowledge the use of cookies. Privacy statement ❯
(https://www.paloaltonetworks.com/legal-notices/privacy)
 A Select Panorama > Managed Collectors and Add a managed collector.

B In the General settings, enter the serial number (Collector S/N) you recorded for the Log Collector.

C 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
(/content/techdocs/en_US/panorama/10-1/panorama-admin/set-up-panorama/set-up-the-m-series-

appliance.html#id383e50d3-22a6-4ebf-9995-b0224cfffaf7) that is a Panorama management server.

D Select Interfaces, click Management, and configure one or both of the following field sets for the MGT
interface based on the IP protocols of your network.

IPv4—IP Address, Netmask, and Default Gateway

IPv6—IPv6 Address/Prefix Length and Default IPv6 Gateway

E Click OK twice to save your changes to the Log Collector.

F Select Commit > Commit to Panorama and Commit your changes to the Panorama configuration.

This step is required before you can enable logging disks.

G Verify that Panorama > Managed 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 (Step Assign the Log Collector to a Collector

Group.).

STEP 11 -
( Dedicated Log Collector only ) Add the device registration authentication key to the Log Collector.

Add the device registration authentication key only to a Dedicated Log Collector. A Panorama in Panorama
mode does not need to authenticate its own local Log Collector.

This site uses cookies essential to its operation, for analytics, and for personalized content and ads. By
continuing to browse this site, you acknowledge the use of cookies. Privacy statement ❯
(https://www.paloaltonetworks.com/legal-notices/privacy)
 A Log in to the Log Collector CLI (/content/techdocs/en_US/panorama/10-1/panorama-admin/set-up-
panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-
cli.html#id22bca7a1-2603-49f1-b937-51de02f52ae2).

B Add the device registration authentication key.

admin>

request authkey set <auth-key>

STEP 12 -
Enable the logging disks.

A Select Panorama > Managed Collectors and edit the Log Collector.

B Select Disks and Add each RAID disk pair.

C Click OK to save your changes.

D Select Commit > Commit to Panorama and Commit your changes to the Panorama configuration.

STEP 13 -
( 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 (Switch from Panorama mode
to Log Collector mode.) would have deleted all configurations except the management access settings.

A Configure each interface on the Panorama management server (other than the MGT interface) if you haven’t
already:

1. Select Panorama > Setup > Interfaces and click the Interface Name.

2. Select <interface-name> to enable the interface.

3. Complete one or both of the following field sets based on the IP protocols of your network:

IPv4—IP Address, Netmask, and Default Gateway

This site uses cookiesIPv6—

essential
IPv6 toAddress/Prefix
its operation, for analytics,
Length andand for personalized
Default content and ads. By
IPv6 Gateway
continuing to browse this site, you acknowledge the use of cookies. Privacy statement ❯
(https://www.paloaltonetworks.com/legal-notices/privacy)
4. 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.

5. Click OK to save your changes.

B Configure each interface on the Log Collector (other than the MGT interface):

1. Select Panorama > Managed Collectors and edit the Log Collector.

2. Select Interfaces and click the name of the interface.

3. Select <interface-name> to enable the interface.

4. Complete one or both of the following field sets based on the IP protocols of your network:

IPv4—IP Address, Netmask, and Default Gateway

IPv6—IPv6 Address/Prefix Length and Default IPv6 Gateway

5. 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.

6. Click OK to save your changes to the interface.

C Click OK to save your changes to the Log Collector.

D Select Commit > Commit to Panorama and Commit your changes to the Panorama configuration.

STEP 14 -
( 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 (/content/techdocs/en_US/panorama/10-1/panorama-admin/set-up-panorama/set-
up-authentication-using-custom-certificates.html#id14acb184-5a00-497c-979b-5a4b5fcac48b).

This site uses cookies essential to its operation, for analytics, and for personalized content and ads. By
continuing to browse this site, you acknowledge the use of cookies. Privacy statement ❯
(https://www.paloaltonetworks.com/legal-notices/privacy)
 A Select Panorama > Certificate Management > Certificate Profile and choose the certificate profile from the
drop-down or click New Certificate Profile to create one.

B Select Panorama > Managed Collectors > Add > Communication for a Log Collector.

C Select the Secure Client Communication check box.

D 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.

E Click OK.

STEP 15 -
( Optional ) Configure Secure Server Communication on a Log Collector. For more information, see Set Up
Authentication Using Custom Certificates (/content/techdocs/en_US/panorama/10-1/panorama-admin/set-
up-panorama/set-up-authentication-using-custom-certificates.html#id14acb184-5a00-497c-979b-
5a4b5fcac48b).

A Select Panorama > Managed Collectors > Add > Communication.

B 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 au-

 thenticate and cannot receive logs from devices using predefined certificates.

C 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.

D Select the certificate profile from the Certificate Profile drop-down.

E 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.

This site usesFcookies essential toWait

In Disconnect its operation,
Time (min)for analytics,
, enter theand for personalized
number content
of minutes and ads.should
Panorama By wait before breaking and
continuing to browse this site, you acknowledge the use of cookies. Privacy statement
reestablishing the connection with its managed devices. This field is blank by default and ❯ the range is 0 to
(https://www.paloaltonetworks.com/legal-notices/privacy)
44,640 minutes.
 The disconnect wait time does not begin counting down until you commit the new

configuration.

G ( Optional ) Configure an authorization list.

1. Click Add under Authorization List.

2. Select the Subject or Subject Alt Name as the Identifier type.

3. Enter an identifier of the selected type.

4. Click OK.

5. Select Check Authorization List to enforce the authorization list.

H Click OK.

I Select Commit > Commit to Panorama.

STEP 16 -
Assign the Log Collector to a Collector Group.

A Configure a Collector Group (/content/techdocs/en_US/panorama/10-1/panorama-admin/manage-log-

collection/manage-collector-groups/configure-a-collector-group.html#ide673d91e-8a6f-439a-a269-
6536c092b28e). 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, 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.

B Select Panorama > Managed 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.

This site usesCcookies

Accessessential
the Log to its operation,
Collector CLIforand
analytics, and following
enter the for personalized content
command toand ads.that
verify By its interfaces are operational:
continuing to browse this site, you acknowledge the use of cookies. Privacy statement ❯
(https://www.paloaltonetworks.com/legal-notices/privacy)
 > show interface all

The output displays the state as up for each interface that is operational.

D If the Collector Group has multiple Log Collectors, Troubleshoot Connectivity to Network Resources
(/content/techdocs/en_US/panorama/10-1/panorama-admin/troubleshooting/test-policy-match-and-
connectivity-for-managed-devices/troubleshoot-connectivity-to-network-resources.html#id7a159d7e-

7d7c-46da-a3b7-833b66710b16) 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.

STEP 17 -
Next steps...

To enable the Log Collector to receive firewall logs:

A Configure Log Forwarding to Panorama (/content/techdocs/en_US/panorama/10-1/panorama-

admin/manage-log-collection/configure-log-forwarding-to-panorama.html#id80fca380-dbad-4432-8aec-
d0f3265ba358).

B Verify Log Forwarding to Panorama (/content/techdocs/en_US/panorama/10-1/panorama-admin/manage-

log-collection/verify-log-forwarding-to-panorama.html#id628d9192-20db-4bc2-b6d7-671cc2fa2e6d).

Was this information helpful?

Yes No

Previous
Next
Set Up an (/content/techdocs/en_US/panorama/10-
Increase (/content/techdocs/en_US/panorama/10-
M-Series 1/panorama-admin/set-up-panorama/set-
Storage on 1/panorama-admin/set-up-panorama/set-
Appliance up-the-m-series-appliance/m-series-setup-
the M- up-the-m-series-appliance/increase-
in Log overview/set-up-an-m-series-appliance-in-
Series storage-on-the-m-series-appliance.html)
Collector log-collector-mode.html)
Appliance
Mode

This site uses cookies essential to its operation, for analytics, and for personalized content and ads. By
continuing to browse this site, you acknowledge the use of cookies. Privacy statement ❯
(https://www.paloaltonetworks.com/legal-notices/privacy)
 Technical Documentation Co

Release Notes (/content/techdocs/en_US/release-notes.html) Abo

Search (/content/techdocs/en_US/search.html) Care
Blog (https://www.paloaltonetworks.com/blog/category/technical- Cus
documentation/) LIVE
Compatibility Matrix (/content/techdocs/en_US/compatibility- Kno
matrix.html)
OSS Listings (/content/techdocs/en_US/oss-listings.html)
Sitemap (/content/techdocs/en_US/sitemap.html)

(https://www.facebook.com/PaloAltoNetworks) (https://w
(https://www.youtube.com/channel/UCPRouchFt58TZnjoI65aelA)

(/content/techdocs/en_US.html) © 2025 Palo Alto Ne

This site uses cookies essential to its operation, for analytics, and for personalized content and ads. By
continuing to browse this site, you acknowledge the use of cookies. Privacy statement ❯
(https://www.paloaltonetworks.com/legal-notices/privacy)