This article explains how to troubleshoot, the AAMWD control channel is down, and it will impact AAMW functionality
About the AAMWD alarm below, this could be a legitimate alarm related to device connectivity,
show chassis alarms no-forwarding
1 alarms currently active
Alarm time Class Description
2024-08-08 23:23:05 -05 Minor AAMWD control channel down, it will impact AAMW functionality
show services advanced-anti-malware status
node0:
--------------------------------------------------------------------------
Server connection status:
Server hostname: srxapi.us-west-2.sky.junipersecurity.net
Server port: 443
Proxy hostname: None
Proxy port: None
Control Plane:
Connection time: 2024-08-23 15:56:37 -05
Connection status: "Requesting server certificate validation"
Service Plane:
node0.fpc0
Connection active number: 17
Connection retry statistics: 1469970
node1.fpc0
Connection active number: 1
Connection retry statistics: 257882
Check the connectivity to the cloud, please refer to the chapter "Troubleshooting Juniper Advanced Threat Prevention Cloud: Checking DNS and Routing Configurations" in the document below.
https://www.juniper.net/documentation/us/en/software/atp-cloud/atp-cloud-troubleshooting/atp-cloud-troubleshooting.pdf
If the connectivity to cloud works well, then the AAMW or PKI daemon could be stuck, restart the processes to resolve this issue.
Restarting the processes above won't affect production traffic.