expedition pre-define http mismatch actual firewall


ATTENTION Customers, All Partners and Employees: The Customer Support Portal (CSP) will be undergoing maintenance and unavailable on Saturday, November 7, 2020, from 11 am to 11 pm PST. Please read our blog for more information.

L2 Linker

expedition pre-define http mismatch actual firewall

We had migration activity that causing the outage. After review the technical detail. we notice when merge service object, TCP-80 over write service-http.


the actual firewall service-http use port 80 and 8080. Expedition pre-define as 80 only, that causing the problem.


One more thing, when show running security policy and nat policy, palo alto not sort output of ip address, service, it's very painful to compare the result that make migration more challenge and risk.

L3 Networker

We are looking into the issue and have a ticket internally.

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!