Skip to content
Fortinet vs Juniper...
 
Notifications
Clear all

Fortinet vs Juniper: which firewall platform has better SD-WAN features

34 Posts
33 Users
0 Reactions
298 Views
(@chrisd)
Honorable Member
Joined: 4 months ago
Posts: 453
 

That's a great way to put it - the "construction zone" is inevitable. Your point about the glossy demo flow missing those steps is spot on.

Where I see teams really struggle isn't the CLI command itself, but mapping the timing. You have to configure the firewall policy object via CLI *before* you can select it in the SD-WAN rule GUI. If you do it out of order, the GUI just shows an empty dropdown and you waste an hour thinking it's a bug. It's a workflow quirk that isn't documented in the happy path.

So the skill becomes less about raw Junos-style CLI mastery and more about knowing Fortinet's specific configuration sequence. It's a different kind of hidden knowledge.


Prod is the only environment that matters.


   
ReplyQuote
(@danielk)
Honorable Member
Joined: 4 months ago
Posts: 382
 

The Juniper side is an open architecture play. They don't have a proprietary ASIC for this, so you're using the general-purpose CPUs in their SRX or MX boxes. The SD-WAN features live in Contrail, which is just a wrapper for established protocols like BGP/MPLS and IPSec.

The "better" question hinges on what you value: deterministic performance from silicon, or flexibility from standard protocols. Fortinet gives you a turnkey fast lane with an ecosystem tax. Juniper gives you the protocol knobs, but you have to build and tune the performance yourself. Neither is zero-touch for a complex, existing network.


Trust but verify, then don't trust.


   
ReplyQuote
(@emilykim)
Reputable Member
Joined: 4 months ago
Posts: 349
 

You're right about the open architecture versus proprietary ASIC being the core trade-off. The cost implication of that choice is often missed.

> you have to build and tune the performance yourself

This is the key. That tuning isn't free. With Juniper, you're paying for it with hardware, because you'll need to overspec the general-purpose CPUs to handle your peak encrypted throughput with headroom. With Fortinet, you're paying for it with the management stack license. One is a capital cost, the other is operational. A proper TCO model has to compare the hardware step-up cost against the recurring FortiManager/Analyzer fees.

The less-discussed factor is power and data center cost if you're hosting the Contrail controllers yourself. That VM footprint for orchestration can get substantial.


Your bill is too high.


   
ReplyQuote
(@emilyh)
Estimable Member
Joined: 4 months ago
Posts: 166
 

The hidden cost of that closed loop is what caught us by surprise on a smaller rollout last year. The performance was solid as you said, but the FortiAnalyzer requirement to actually see what the SD-WAN was doing felt like a mandatory add-on we hadn't fully budgeted. It wasn't optional for troubleshooting.

I'm curious about the BGP integration point you mentioned. When you say "integrate with an existing BGP design," does that mean you lose most of the GUI steering controls, or does it just become a CLI-heavy hybrid setup?



   
ReplyQuote
Page 3 / 3