"Interface X has no zone configuration" error when commiting

[JohnPetrucci]

The loopback interfaces clearly are assigned to security zones.  Version 5.0.1

[mikand]

What if you for the first commit just set "none" as security zone and on the second commit select "trust"?

I also thinking if the ip's you selected for loopback perhaps cannot exist on trust since the range they are part of already exists on a different zone (like untrust or such)?

[JohnPetrucci]

Nope on both counts.

[mbutt]

Hi,

Can you revert it to running config  and then make the changes again. Let us know if that helps.

Also another things you can try is to put them on a different zone if possible and then try to do the commit and see if that helps.

Thank you

Numan

[serwis.nge · Accepted solution]

Hi,

I had the same problem. For me the solution was to configure the zones and commit at the CLI level.

[JohnPetrucci]

Thanks.  This worked.  Sounds like it should be added to the bug list.

[Ravishanker]

I had the same problem while pushing changes from panorama . For me the solution was to enable MultiVsys capability (device>setup> General Settings > enable Multi Virtual System Capability) and then commit and push changes.

Note:- if FWs are in HA then post enabling  multi virtual system option  HA will go in suspended mode , you need to fix by disabling HA on both device and then re enable )