ZTP Models can be deployed as a traditional models?
cancel
Showing results for 
Search instead for 
Did you mean: 

ZTP Models can be deployed as a traditional models?

L1 Bithead

Hello guys, I want to know if someone has seen this behavior with Port Management Configuration on ZTP NGFW Models ... The IP address, Netmask and gateway shows an incorrect value 0.0.0.0 or Unknown, but the CLI shows the correct configuration parameters. We previously performed a "request disable-ztp" besides "Disable Device and Network Template" and "Disable Panorama Policy and Objects" on Panorama Settings. We thought that this behavior is causing problems when we trying to add a PA-3260-ZTP as a managed device on Panorama.

 

egarantiva_1-1616164599996.png

 

8 REPLIES 8

L4 Transporter

So from th CLI you see that the firewall is configured correctly right and it has full configuration? I also see that  you have GUI picture so you can access the managment ip even if the gui shows no IP? I am asking because when I see  unknown fo interfaces I do a factory default reset on the firewall but first I save the config snapshot or/and device state (https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Clkn) and load it again after the reset

Hi Nikolay

 

Thanks for your reply. Please let me know if you have seen this behavior of "Unknown Mgmt IP info on GUI" when you're deploying ZTP models in a traditional way. If I reset to factory default a ZTP Model, it comes back to the original ZTP state according to the notes in the procedure "Disable the ZTP state machine on the firewall" and I think the issue is related to this ZTP pre-configured template.

 

https://docs.paloaltonetworks.com/panorama/9-1/panorama-admin/manage-firewalls/set-up-zero-touch-pro...

We had an issue like that without ZTP deployment but we seen it in the CLI as well so we did factory default reset.

 

Did you test restarting just the web service or managment server as it seems a GUI issue:

 

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClaGCAS

 

 

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000POIHCA4

 

 

 

Also you can run Validate Changes to see if  the ZTP intoduced a bad config(you may need to make a small change before that to be able to validate)

 

 

https://docs.paloaltonetworks.com/panorama/8-1/panorama-admin/administer-panorama/preview-validate-o...

 

 

 There is a bug  PAN-160870 when deploying the ZTP firewalls in the normal way so you can check it and test the workaround:

 

https://docs.paloaltonetworks.com/plugins/vm-series-and-panorama-plugins-release-notes/panorama-plug...

 

 

 

Otherwise of that check with the TAC.

Hello Nikolay, thanks for your all advices , we're going to test those suggestions, until we can check with TAC in a Live Meeting. I'll let you know when we have more clues about the issue with these ZTP models.

Any news about what is the issue as I am also interested in what it could be ?

 

Hello Nikolay

 

We're still waiting for a fix in the next PAN-OS 9.1 release (9.1.9). Apparently, the WebUI Mgmt "Unknown" Issue is related to bug  PAN-156264. This behavior doesn't permit add PAs as a managed devices on Panorama in a traditional way. 

We tried the PAN-160870 Workaround to disable ZTP Pre-configuration but it didn't work after reboot the PAs. Using the ZTP plugin to deploy PAs works, but still keeping requiring the ZTP DG and Template configuration to avoid the PAN-160870 issue after finishing the deployment and it does not make much sense to me.

As soon as I have news I'll let you know.

L1 Bithead

I am having a similar issue.  As the ISP doesn't provide any DHCP, in the site I am adding the device to, and I have access to the Management network I tried disabling ZTP and adding the Panorama servers manually, but they went into a weird state, where the management interface was still routing to the network, but they wouldn't send any traffic to the Panorama servers.  I could still get on the interface to manage it, but it wouldn't respond to pings from panorama, but would from everything else.  resetting to factory default and re-enabling DHCP on the management interface and it would respond.

I also tried removing the ZTP template by disabling the panorama templates and policies, but then it wouldn't commit any changes because of a very unhelpful message:

 

network  is missing 'interface'

 

I didn't realize ZTP would be Mandatory and such a PITA.  I wish I had bought the normal ones.

L1 Bithead

Hi Rich 

 

You're right, try to add the ZTP models on Panorama using a traditional way results in a weird "Disconnected" state. Try to remove the ZTP template by disabling the panorama templates and policies(as it says  PAN-160870 workaround) causes an Autommit failure after a PA reboot due to "network is missing interface" and some other issues and you will need to do the factory reset to correct that. I figured out the only way to deploy those ZTP models was using the Panorama ZTP Plugin to register and add the PA as a managed device using DHCP via WAN (on eth1/1) and then disable the ztp state (request disable ztp) to be able to reach the PA from mgmt port (being careful to change locally on the PA the "Panorama service route" to mgmt port in the proper moment). Next, from the Panorama and locally on the PA, you should remove the ZTP template and DG from Panorama progressively until you get free the PA of that ZTP configuration.

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 LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!