How to fix error--primary active stuck in suspend due to Peer device VM number of cores (xx) not matching with local

How to fix error--primary active stuck in suspend due to Peer device VM number of cores (xx) not matching with local

9320
Created On 02/06/21 04:43 AM - Last Modified 07/11/25 20:16 PM


Symptom


Device is suspended in high availability.
The following error will appear "primary-active-stuck-in-suspend-due-to-Peer-device-VM-number-of-cores-xx-not-matching-with-local"
 


Environment


  • Affect VM Panorama
  • Affect PAN_OS 8.1, 9.0., 9.1, 10.0


Cause


In order for High Availability to form vCPU and memory need to match for VM Panorama.
If not, then the device will be put in Suspended until value match.

The following  error will appear in Dashbooard.
User-added image
 
Example of system log output:
2021/02/05 12:44:57 2021/02/05 12:44:57 critical ha            Peer-co 0  0007EV30914     Peer device VM number of cores (16) not matching with local (4); going to Suspended state


 


Resolution


To resolve, both vcpu and memory need to match on both VM.
To do this VM Panorama need to be shutdown one at a time.

Follow this link below:
Increase CPUs and Memory on the Panorama Virtual Appliance
 


Additional Information


Setting the number of cores per CPU in a virtual machine  (VMWare)

Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000HCmmCAG&lang=en_US&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail

Choose Language