M-700, M-600, M-300, M-200, and Panorama virtual appliances can have one or more Log
Collectors in each Collector Group. You assign Log Collectors to a Collector Group
based on the logging rate and log storage requirements of that Collector Group. If
the rates and required storage increase in a Collector Group, the best practice is
to
Increase Storage on the M-Series Appliance
or
Configure a Collector
Group with additional Log Collectors. However, in some deployments, it
might be more economical to move Log Collectors between Collector Groups.
When a Log Collector is local to an M-700, M-600, M-300, or M-200 in Panorama
mode, move it only if the appliance is the passive peer in a high availability
(HA) configuration. HA synchronization applies the configurations associated
with the new Collector Group. Never move a Log Collector that is local to the
active HA peer.
In any single Collector Group, all the Log Collectors must run on the same
Panorama model: all M-700 appliances, all M-600 appliances, all M-300
appliances, all M-200 appliances, or all Panorama virtual appliances.
Before you move a Log Collector to a different Collector Group, you must erase
all existing ES data on the Log Collector. If you move a Log Collector without
erasing its ES data, the ES cluster metadata persists on the Log Collector and
breaks ES cluster quorum, which disrupts log collection for the entire Collector
Group. To erase the ES data before adding the Log Collector to the new Collector
Group, run the
debug elasticsearch erase data command on the
Log Collector CLI. For the full procedure, see
Migrate Logs to a New M-Series
Appliance in Log Collector Mode. If you are unsure whether ES data
cleanup is required, contact Palo Alto Networks support before proceeding.