10-10-2021 05:55 PM
Thanks for commenting. I heard back from Support. The suggested that the issue is the region as it exists in the config, is causing the error. Support posted the following information.
Also, you can run the command "show device-telemetry settings" and check what region it is showing, and if the region name is shown all in lower case format, we will need to modify it as it is case-sensitive. In your case, I see it says "americas" all in lower case, therefore we would need to change this setting through CLI.
Please use the below commands to modify the region name:
> configure
#set deviceconfig system device-telemetry region Americas
#commit
So what appeared to resolve this so far on one PA-820 was disabling Telemetry and committing. Then re-enabling Telemetry, Committing... Then setting the region with a capital A and committing again. It's not clear that this exact process is needed. But I had tried setting the regain names as directed while Telemetry was active and failing. Then committing. But the uipload continued to fail. So I waited for another cycle. Saw the same failure and tried this and the telemetry upload was successful on the PA-820 and it's HA paired device.
I just tried the same process on a VM Series. Waiting for status as I believe this is a 2 or 4 hours cycle. I'll post results.
As to why this became an issue on Oct 8th, I do not know. We made no changes. No commits. No OS upgrade. I suspect the change may have been made on Palo Alto's side. We are running 10.0.5 and planning to update the OS to 10.0.6 next weekend. Possibly the region names in 10.0.5 and earlier are not compliant.
That's what I know. I hope it helps. I realize telemetry function isn't critical. But as you wrote, the critical alerts are annoying.
Thnx again
