PAN 3.1.6 use of proxy for updates

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

PAN 3.1.6 use of proxy for updates

L2 Linker

Hello all,

After upgrading a PAN Device to PANOS 3.1.6, we see a strange behaviour, when the mananement plane is using a proxy for the updates (as defined in the Device->Setup->Edit).

We have defined a proxy over there, for example 10.0.0.4 and port 8080, and then we changed the proxy to 10.0.0.18 and port 8080.

After doing some checks with the new proxy 10.0.0.18:8080 we have changed back to 10.0.0.4:8080. The strange behaviour is that we see from the 10.0.0.18 proxy's logs that this is the proxy that the PAN device is using, ignoring the last configuration that was to return back to the 10.0.0.4 proxy. The PAN device's management IP is 10.0.0.20.

I am trying to troubleshoot this strange behaviour and find out what is the actual proxy tha the device is using (as it seems that is not using the one that is defined in the Device->Setup configuration) by using a kind of debugging command from the command line interface.

Also, in case that something went wrong in the commit of the configuration of the device, I am trying to remember what is the command to commit the whole configuration and not the "delta" config that is being commited when the commit button is pressed, in case this will resolve the problem!

Please help,

Regards

George G.

4 REPLIES 4

L3 Networker

please do a commit force from the cli.

Indeed the "commit force" command will submit the whole configuration.

By doing a commit force did not resolve the strange issue with the proxy used by the management interface.

Is there any other command that will allow me to view which proxy is being used for the anagement interface (and why the correct proxy is not used?).

Regards,

George G.

Do you use a password with your proxy server? if so try changing it to something simple like 1234abcd. if you are still having issue please open a case via the web or call into support for further debugging.

The proxy used does not require authentication, so no username / password has been set.

  • 3160 Views
  • 4 replies
  • 0 Likes
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!