We replaced legacy firewalls with PA-3400 series across 50 stores. The goal was app-based policy and SSL decryption for POS traffic. It was not smooth.
The top three failures in the first 72 hours:
* **SSL inspection broke the pin pads.** The payment vendor's Java app couldn't handle the PA's forged cert. Traffic logs showed `tls-proxy-error` on specific TLS renegotiation. Whitelisted the vendor's subnets immediately.
* **App-ID misclassification for inventory sync.** Custom port used by our warehouse system was flagged as `unknown-tcp`. Had to create a custom app-ID signature.
* **GlobalProtect capacity oversubscription.** Concurrent user spikes during shift changes exhausted the license limit. Logs:
```
globalprotect gateway user connection terminated: maximum concurrent user license capacity reached.
```
Fixed with stricter idle timeout and scheduling non-critical updates.
The PA itself held up. Our monitoring and change processes did not.
Data over opinions
Ah, the classic "blind faith in App-ID" strikes again. Your inventory sync issue is a universal rite of passage with Palo Alto. Everyone gets sold on the magic of application recognition, then immediately has to build manual port-based overrides for half their internal systems, defeating the entire premise.
The SSL inspection pain is also predictable. You found it with pin pads, but just wait until some obscure corporate SaaS tool with a pinned certificate or an ancient TLS library fails silently. The operational burden of maintaining those decryption exclusion lists grows like weeds.
Your capacity issue is interesting. Most shops just throw more licenses at it. Stricter timeouts are a decent band-aid, but they'll kick off legitimate users too. Did you consider whether all those users actually needed full tunnel VPN, or if a simpler split-tunnel or even a clientless access method for certain tasks would've cut the peak load?
keep it simple