Palo Alto Networks PA-220 vs Fortinet: How to Choose

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

Quick comparison

Compare Palo Alto Networks PA-220 against Fortinet on price, ecosystem, support tier, and your existing team skill set.

Decision criteria

| Criterion | Why it matters |

|---|---|

| Existing skills | Your team's training is a sunk cost; switching vendors carries a re-training tax. |

| TCO over 5 years | Hardware + licenses + support + training + power. |

| Ecosystem fit | Controllers, cloud management, APIs: does it integrate with what you already run? |

| Support / RMA | Tier-1 vendors have predictable 24x7 TAC; smaller vendors vary by region. |

| Compliance | If your regulator names a specific vendor, comparison ends there. |

| Feature parity | Some vendor-specific features (SDN fabric, telemetry) don't have direct equivalents. |

When to stay with Palo Alto Networks

• Standardisation across enterprise.
• Palo Alto TAC + RMA matters for your SLAs.
• Existing investment in Palo Alto Networks management / fabric.

When to switch to Fortinet

• Palo Alto Networks refresh quote is 2-3x the alternative for the same use case.
• Your team is already strong on the alternative vendor.
• The alternative's cloud-managed / SaaS architecture is the goal.

Frequently asked questions

Will this work on my specific PAN-OS version?

The procedure reflects current PAN-OS behaviour. Older releases may need minor syntax adjustments, use the CLI help (? or tab-completion) to verify.

Should I open a Palo Alto TAC case immediately?

Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your support entitlement is active first.

Where can I find the Palo Alto Networks official documentation?

https://knowledgebase.paloaltonetworks.com. search the product family + feature name.

Is this procedure safe in production?

Test in a lab or maintenance window first. Capture pre-change state so you can roll back.

Related guides

• All Palo Alto Networks fix guides → /paloalto/
• All vendor guides → /vendors/

Related fixes

Related guides worth a look while you sort this one out:

• Palo Alto Networks PA-220 all ports dead: Diagnose & Fix
• Palo Alto Networks PA-220: How to back up configs nightly to a Git repo
• Palo Alto Networks PA-220: How to deploy with a Python script (paramiko / netmiko / native API)
• Palo Alto Networks PA-220: How to deploy with Ansible
• Palo Alto Networks PA-220: How to deploy with Terraform (provider where available)
• Palo Alto Networks PA-220: How to deploy with the vendor's controller / manager

References

• Palo Alto Networks support portal: https://support.paloaltonetworks.com
• Palo Alto Networks knowledge base: https://knowledgebase.paloaltonetworks.com
• Palo Alto Networks security advisories: https://security.paloaltonetworks.com
• Open a case: https://support.paloaltonetworks.com/Support/Index

Reference material, not professional advice. Validate against your specific PAN-OS version and test in a non-production environment before applying.

Why this matters for your day-to-day

A Palo device that's misbehaving costs more than the fix itself: lost productivity, missed calls, security risk, even safety risk in some categories. Treating the symptom quickly with a documented procedure is cheaper than letting it persist. The steps above are written to get you back to working in under an hour where possible, and to flag clearly when escalation is the right call.

Before you start

A few things to confirm so the Palo device fix goes cleanly:

• Latest firmware downloaded if you're going to update.
• Warranty + support contract status checked, opening sealed parts may void it.
• Backup of current configuration (where applicable) taken.
• Spare parts on hand if you anticipate replacement.
• Adequate workspace, lighting, and time: rushing causes regressions.

Verification checklist

After applying the fix on your Palo device, confirm:

• The original symptom is no longer reproducible.
• Related features (status LEDs, app sync, paired accessories) still work.
• The device responds to a soft reboot without the fault returning.
• Any error codes that were on display have cleared.
• Documentation (your service log, the brand companion app) reflects the change.

Escalation guide

For a Palo device, the right escalation depends on impact:

• Cosmetic / minor: log a ticket via the Palo app or web portal. Response 1-3 business days.
• Mid-impact: phone support. Have your serial number ready.
• Critical (production down, safety issue): in-person dealer / TAC visit. Bring proof of purchase.
• Out of warranty: third-party repair shop with manufacturer-certified technicians.

More frequently asked questions

Are there safer alternatives for non-technical users?

Yes, the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.

Should I update firmware first or last?

Update firmware first if a release note specifically mentions your symptom. Otherwise, finish the troubleshooting flow first, then update; that way you can isolate whether the update or the underlying fix solved it.

Is it safe to apply during business hours?

If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.

How long does this fix usually take?

Most users complete the steps in 20-45 minutes the first time, and 5-10 minutes on subsequent runs once the menu paths are familiar.

Why is this happening on a brand-new unit?

Out-of-box defects do occur. If you've owned the device under 30 days and the symptom persists after a factory reset, escalate to the seller for replacement under DOA terms before opening a manufacturer support case.