Skip Links

Cisco vs. Juniper: How different are their SDN strategies?

Analysts see more convergence than divergence with recent Cisco, Juniper releases

By , Network World
February 07, 2013 01:43 PM ET

Page 3 of 3

And even though the timelines for deliverables differ, they are in keeping with each company's traditions.

"That's Juniper's way, right?" Fratto says. "Produce a road map and then deliver over a longer timeline like 12 to 24 months."

Where the strategies diverge will be in partner ecosystems for SDN-enabled services, he says.

"In both cases, they will need to attract partners into their respective ecosystems. The market for services has a ton of players -- think (application delivery controllers), firewalls, WAN optimization. For those services to be chained, they have to be integrated with Juniper's stuff. Same for Cisco. That's going to be the attractor."

Casemore sees differences in initial target markets too.

"I look at Juniper's strategy as being more attuned to the SP/carrier community than the enterprise -- their service chaining concept is very close to network functions virtualization -- whereas the strategy and technologies Cisco has rolled out thus far are more enterprise oriented," he says. "That's not to say that Juniper won't develop more of an enterprise orientation or that Cisco won't push its SDN strategy into carriers -- both will happen. But that's how I see them now at this particular snapshot in time."

Jim Duffy has been covering technology for over 25 years, 21 at Network World. He also writes The Cisco Connection blog and can be reached on Twitter @Jim_Duffy.

Read more about lans & wans in Network World's LANs & WANs section.

Our Commenting Policies
Latest News
rssRss Feed
View more Latest News