Category Archives: Juniper

Juniper kills MobileNext mobile packet product line

Juniper MobileNext was a high-profile competitor to Cisco’s Starent gateway that was designed to enable non-interrupted delivery of high-definition voice and video over 2G/3G and LTE mobile networks

Juniper has killed a high-profile product for the core of mobile operator networks after combining business units to focus on potential growth opportunities.

Juniper has exterminated or what it calls end-of-lifed (EOL) its MobileNext mobile packet core product line, software introduced in 2009 as part of “Project Falcon” for its MX edge routers that was designed to enable non-interrupted delivery of high-definition voice and video to users over 2G/3G and LTE mobile networks. MobileNext was launched at Mobile World Congress in early 2011 to allow Juniper’s MX 3D to function as a broadband gateway, an authentication and management control plane for 2G/3G and LTE mobile packet cores, and as a policy manager for subscriber management systems.

MobileNext was intended to compete with Cisco’s ASR 5000 LTE gateway, obtained from its acquisition of Starent. But the product was struggling to gain traction in the market and was one of a handful of new Juniper products straining company financials as they went through lengthy evaluation cycles with potential customers.

Juniper is killing the entire MobileNext offering, which consists of three products: the Mobile Broadband Gateway; the Mobile Control Gateway; and the Mobile Policy Manager. The company claims, however, that its mobility strategy for the operator core remains intact.
“We have made the decision to end-of-life the MobileNext solution,” a Juniper spokesperson says. “However, our strategy remains unchanged: to virtualize mobile networks and deliver innovation through our existing portfolio of backhaul, security, routing and edge services with products such as the MX Series 3D Universal Edge Routers, SRX Series Services Gateways and JunosV App Engine software virtualization platform. We will continue to work with our partners to deliver best-in-class solutions that help customers improve network economics and accelerate delivery of new mobile services.”

Juniper will now address mobile packet core requirements through software-defined network (SDN) and network functions virtualization (NFV) capabilities, according to an internal memo authored by Daniel Hua, senior vice president of Juniper’s Routing Business Unit, and obtained by Network World.

“Despite our decision to EOL MobileNext we remain committed to executing on all existing commitments to our customers and to the mobility space longer term. We believe we can meet the needs of our customers by providing the underlying virtualized mobile infrastructure (routing, switching, SDN and NFV to enable customers to make this transition as well as offer specific virtualized network functions.”

Indeed, Juniper earlier this year announced a virtualized, SDN version of the Mobile Control Gateway based on the JunosV App Engine, which is shipping now on the MX router.

MobileNext’s demise comes as Juniper merges its Edge Services Business Unit into its Routing Business Unit. Hua explains the rationale for this in his memo:

“The compelling reason driving this organization alignment is to increase synergy and focus under the umbrella of a single routing business unit. We believe this step will ensure close alignment of our embedded and virtual services with our market-leading MX and PTX platforms. Many of the network edge services were originally developed as extensions of the Junos OS within RBU. We are realigning these services back to its original function allowing us to strengthen and further innovate in the areas of our Access, Edge, and Core offerings through tighter integration of network services.”

Sources say Juniper is also scaling down development of its Junos Content video and media delivery product line, formerly known as Media Flow and obtained from the $100 million acquisition of Ankeena Networks in 2010. Junos Content is designed to optimize mobile and fixed networks for efficient video and media delivery to smartphones and other mobile devices.


MCTS Training, MCITP Trainnig

Best Microsoft MCTS Certification,
Microsoft MCITP Training at

Microsoft, Juniper, others in coding consortium issue guidelines for safer applications

An industry consortium dedicated to assuring the security of software has issued guidelines to lower the risk that vulnerabilities that could be exploited by attackers will wind up in finished code.

In particular, the Software Assurance Forum for Excellence in Code (SAFECode) is addressing how to prevent vulnerabilities that may worm their way in during the Agile software development process.

MORE: SAP designs facility for ‘agile’ cloud application development

RELATED: ‘Rugged Manifesto’ promotes secure coding

Cisco CCNA Training, Cisco CCNA Certification

Best Microsoft MCTS Certification, Microsoft MCITP Training at

Agile is a framework for incremental software development by teams that work together in stages called sprints to develop the first iteration of code then revisit it regularly to refine the product based on new requirements and input from users.

SAFECode’s new paper, “Practical Security Stories and Security Tasks for Agile Development Environments,” presents Agile teams with a list of specific goals they may be trying to achieve at the outset and tasks necessary to achieve each one.

These tasks are refined at the end of each sprint in preparation for the next one, but they set Agile teams on a path that will lead to a safer end product, says Edward Bonver, a principal senior software engineer at Symantec who participates in SAFECode. The organization is made up of some major vendors: Adobe, EMC, Juniper, Microsoft, Nokia, SAP, Siemens and Symantec.

The paper lays down 36 goals Agile teams may wish to pursue while working on software products and is meant to supplement an earlier best practices paper written by the group. These goals are gleaned from the experiences of coding teams within SAFECode’s members as effective ways to approach Agile coding.

Called stories, these specific goals are written in plain language and from a particular perspective. For example, one story reads: “As a(n) architect/developer, I want to ensure AND as [quality assurance], I want to verify that cross-site scripting attacks are prevented.”

The story is accompanied by a set of tasks to accomplish this goal, each one marked with the category of team members who should work on each task. One task associated with the story in the example above is directed toward developers and testers and reads: “[D/T] When generating dynamic web pages, filter the input for any browser-executable content that is not intended (for example, from user-originated fields in a database). Consider all forms of input of content that might eventually be presented to and consumed by a browser, like events generated outside the system, log messages, arguments in a URL, form field values, etc. Perform this filtering at server-side, close to use.”

Depending on how much is accomplished toward that goal after the first sprint, it may remain as a task for the next one or be refined to address new issues that crop up. The task list is meant to guide Agile teams toward accomplishing goals that will lower risk of vulnerabilities, but not by setting down a rigid set of steps that may not be applicable to all projects.

“Incorporating security in Agile was a challenge,” for SAFECode member companies, Bonver says. “They decided to share their experiences, what they had success doing.”

Cisco CCNA Training, Cisco CCNA Certification

Best Microsoft MCTS Certification, Microsoft MCITP Training at