Skip to main content
1ryan1
Explorer II
Aug 9, 2022 3:20 PM UTC
Question

Cannot deploy configs from FTM after upgrading FTGs to 7.2.1

I upgraded my FTGs to 7.2.1 but now I cannot deploy my policies. I get the following error message from FTM deploy log, which I do not know how to resolve.

 

(proxy-address) $  purge IPv6-address can not be deleted because it is a static entry. IPv4-address can not be deleted because it is a static entry.

 Running 7.2.0 FTM.

4 replies

1ryan1
1ryan1Author
Explorer II
Aug 9, 2022 5:12 PM UTC

What's interesting is if I make a policy change, it does push through to the FTGs but FTM stills says failed. This can be verified by making a change then logging on the FTGs and verifying.

Debbie_FTNT
Staff & Editor
Staff & Editor
Aug 10, 2022 1:40 PM UTC

Hey ryan,

did you also upgrade your FortiManager to firmware version 7.2.1? That was just released; an upgrade could help.

Other than that, this just means FortiManager is trying to remove some proxy addresses (that are not in use) but fails to do so, and has no other impact.

You could try if a retrieve config in Device Manager (not import, but retrieving in Revision History) fixes it; this issue (and fix) sometimes happens if FortiGate considers something a default value and FortiManager doesn't, or vice versa.

1ryan1
1ryan1Author
Explorer II
Aug 10, 2022 8:52 PM UTC

I assumed the latest update that auto-downloaded from the FTM was installed but that was not the case. I downloaded/installed 7.2.1 on FTM and that corrected the issue. Thanks.

tonifan1
New Member
Aug 17, 2022 1:45 PM UTC

I had the same issue: I fixed updating FM to 7.2.1

Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
Security Operations Summit: Modernize SecOps. Operate AI-Native.AMER: November 4 | 9:00 AM PST. India and SAARC: November 5 | 10:00 AM IST. EMEA: November 5 | 10:30 AM CET. APAC: November 5 | 11:00 AM SGT