Invalid Zones after importing ASA configuration

Reply
Highlighted
L1 Bithead

Invalid Zones after importing ASA configuration

Hi,

 

I have loaded an ASA configuration to Expedition and the dashboard shows 2 invalid zones, however I can't get any clue as what it is invalid on those 2 zones.

 

There are 10 zones in total and I can't tell what's different on these 2. Looking at the Monitor tab I can't see what's the problem. Any idea where I can find why are these zones reported as invalid?

 

Screen Shot 2018-07-25 at 3.27.48 pm.pngDashboardScreen Shot 2018-07-25 at 3.28.14 pm.pngthe 2 zones showing as invalid

Tags (3)
L7 Applicator

Re: Invalid Zones after importing ASA configuration

Name length longer than 15chars?

L1 Bithead

Re: Invalid Zones after importing ASA configuration

Sounds about right. All other zones are less that 15 chars. Is there a restriction? Isn't the max number of chars for a zone name 31?

Tags (1)
L7 Applicator

Re: Invalid Zones after importing ASA configuration

It depends on the Base config Panos version.  So After you merge the Zones with your Base Config if it is like 8.0 the warning should dissapear....

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!