Juniper switching platforms provide a high-density, high-performance foundation for your most demanding data center and cloud environments. As your business grows, your data center must scale to accommodate increased network traffic and users, without compromising scalability, manageability, and sustainability. Our data center architectures support dozens to thousands of ports, scaling to address your evolving business needs while maximizing agility and investment dollars.
Modern data centers running at scale typically use an IP fabric architecture with EVPN-VXLAN overlay.
Powered with a robust control plane, faster convergence, and flexible deployment models, this standards-based fabric helps your data center become multicloud ready.
For smaller scale data center networks, you can use our Virtual Chassis technology in the leaf layer to create pairs of devices connected together. You can configure and manage them as a single, logical device.
Data Center Network Management
A management platform helps you simplify data center operations and manage network resources as a single, cohesive infrastructure. Juniper's Apstra solution enables you to easily manage your physical data center infrastructure.
This solution provides intent-driven automation for deployment along with robust monitoring for assured operation, enabling you to automate, manage, and monitor your data center fabric.
In order to realize the full benefits of a QFX Series EVPN/VXLAN IP fabric network, one must first overcome the challenge of migrating existing server endpoints, firewalls, and network services to the new platform without placing undue burden on application owners and end users.
Juniper’s Junos Fusion to EVPN/ VXLAN IP Fabric Migration service manages the transition of Junos Fusion data center deployments to new EVPN platforms, using proven methods and tools to provide a high degree of confidence, speed to completion, and reduced risk.
Juniper’s Virtual Chassis Fabric to EVPN/VXLAN IP Fabric Migration service manages the transition of Virtual Chassis Fabric data center deployments to new EVPN platforms, using proven methods and tools to provide a high degree of confidence, speed to completion, and reduced risk.
This service is designed to interconnect and then incrementally migrate all elements from the existing Virtual Chassis Fabric system to the new IP fabric
Juniper’s Cisco Catalyst CATOS and Nexus NX-OS to EVPN/ VXLAN IP Fabric Migration service manages the transition of Cisco CAT-OS and NX-OS data center deployments to new EVPN platforms, using proven methods and tools to provide a high degree of confidence, speed to completion, and reduced risk.
This service manages the transition of all Cisco CAT-OS and NX-OS system connections and network functions to the new EVPN/VXLAN IP fabric, removing all dependencies on the Cisco CAT-OS and NX-OS systems.
Juniper Professional Services QFabric to EVPN/VXLAN IP Fabric Migration service manages the transition of QFabric data center deployments to new EVPN platforms. Proven methods and tools are used to provide a high degree of assurance, speed to completion, and reduced risk.
In the multicloud era, cloud providers, service providers, and enterprises need Data Center Interconnect (DCI) networking that can scale and adapt as quickly as business and operational demands change.
First-generation DCI solutions address scalability constraints with inflexible, proprietary network elements and control software. Juniper’s DCI solutions break through those limitations. We span Layer 3 to the photonic layer and support DCI from the data center edge or the data center spine layer.With our solutions, network operators gain the versatility to interconnect data centers with the right combination of high-capacity coherent optics and DCI-optimized packet, security, and virtualization technologies. And the DCI environment is unconstrained by vendor lock-in or interoperability challenges.
Juniper solutions address DCI deployments for all kinds of network operators:
Cloud providers and Internet exchanges
can innovate at the pace of their business. Open, interoperable, and secure DCIs use both Ethernet and WDM interfaces available on Juniper’s MX and QFX platforms.
Service providers, telcos, and cable operators
can offer more competitive cloud services over shared or dedicated infrastructure. They can create new, geographically distributed cloud network services using MX Series 5G Universal Routers, PTX Series Packet Transport Routers, and QFX Series Switches with end-to-end DCI network visibility and control.
Enterprises
can use Juniper's Apstra solution to orchestrate EVPN/VXLAN DCI overlays with QFX Series Switches. Harnessing EVPN/VXLAN to connect data centers allows you to support efficient Layer 2/Layer 3 network connectivity with agility and simplicity—without the need to own or control the underlying DCI lines.
Enterprises can also connect to hybrid clouds with minimal operational overhead. These organizations can exploit the integrated terabit-scale coherent card on the QFX10000 line of switches to connect to cloud services quickly with a low-power, small-footprint solution in a Junos OS environment.
Modern data centers running at scale typically use an IP fabric architecture with EVPN-VXLAN overlay. The IP fabric enables you to collapse traditional networking layers into a two-tier spine-and-leaf architecture optimized for large-scale environments.
This highly interconnected Layer 3 network acts as an underlay to provide high resiliency and low latency across your network and can easily be scaled out horizontally as needed.
The EVPN-VXLAN overlay sits on top of the IP fabric, enabling you to extend and interconnect your Layer 2 data center domains and place endpoints (such as servers or virtual machines) anywhere in the network, including across data centers.
As content and applications migrate to the cloud, the demand for network bandwidth is accelerating, and users’ quality-of-experience (QoE) expectations are reaching new heights. At the same time, service provider networks are struggling to keep pace using their current transport architectures and management approaches.
To more easily and affordably meet demand and improve user experiences, service providers need a network transport solution that will provide greater control, agility, application awareness, and simplified traffic management for their networks. Operators can get all these capabilities with Juniper’s segment routing solution.
Segment Routing uses a routing technology or technique known as source packet routing. In source packet routing, the source or ingress router specifies the path a packet will take through the network, rather than the packet being routed hop by hop through the network based upon its destination address.
However, source packet routing is not a new concept. As an example, MPLS is one of the most widely adopted forms of source packet routing, which uses labels to direct packets through a network. In an MPLS network, when a packet arrives at an ingress node an MPLS label is prepended to the packet which determines the packet’s path through the network.
While SR and MPLS are similar, in that they are both source-based routing protocols, there are a few differences between them. One of these key differences lies in a primary objective of SR, which is documented in RFC7855, “The SPRING [SR] architecture MUST allow putting the policy state in the packet header and not in the intermediate nodes along the path. Hence, the policy is instantiated in the packet header and does not require any policy state in midpoints and tail-ends.” Unlike MPLS, SR does not require the intermediate routers to maintain path information. This provides a couple of benefits, which we will cover in a subsequent blog, but the primary benefit is that you are able to remove protocols like RSVP and LDP from the network.
Because the SR ingress node encodes path information in the SR header, transit nodes are not required to maintain information regarding each path that they support. They are only required to process the segment identifiers found in the packet header, forwarding the packet from the current segment to the next segment.
This is the major benefit of SR. Because transit nodes are not required to maintain path information, overhead associated with maintaining that information is eliminated. As a result, routing protocols are simplified, scaling characteristics are improved, and network operations become less problematic.
Unrelenting traffic growth, together with broad cloud adoption, emerging IoT trends and 5G forecasts, are challenging the ability of network operators to efficiently scale their infrastructure, accelerate service delivery and introduce new service offerings.
Today, innovative network operators are implementing Source Packet Routing (SPRING) in combination with centralized path computation to profitably address these challenges without compromising customer experience, performance or reliability.
Working together, SPRING and centralized path computation simplify network design and operation and improve network economics by increasing network utilization and service availability without requiring traffic re-engineering or compromising service SLAs.
In this webinar, industry experts Aman Kapoor of Juniper Networks, Dan Voyer of Bell Canada and Paul Mattes of Microsoft Corporation discuss key factors to consider when evaluating and deploying SPRING and centralized path computation technology in IP/MPLS networks, including: - Market trends and the challenges and opportunities they present - SPRING technology overview; architectural and operational perspectives - Real-world use cases from telecom and cloud SP markets -
Key considerations – features, functions, coexistence with/migration from existing deployments
Segment routing simplifies operations and reduces resource requirements in the network by removing network state information from intermediate routers and placing path information into packet headers at the ingress node.
From there, our NorthStar Controller further simplifies the design, implementation, and management of segment-routed net
Segment routing simplifies operations and reduces resource requirements in the network by removing network state information from intermediate routers and placing path information into packet headers at the ingress node.
From there, our NorthStar Controller further simplifies the design, implementation, and management of segment-routed networks. As an SDN controller, it computes source-routing paths centrally, while delivering cross-domain network visibility and conducting real-time, application-level traffic management. By managing individual application traffic flows across the network, NorthStar Controller helps you meet SLAs and provide the best possible QoE to end users.
When you use Juniper segment routing, you won’t have to swap out your network hardware as you transition. That’s because we design our equipment using high-performance programmable ASICs. The high performance of Juniper ASICs enables you to build out your segment-routing environment on your existing Juniper hardware with industry-leading
When you use Juniper segment routing, you won’t have to swap out your network hardware as you transition. That’s because we design our equipment using high-performance programmable ASICs. The high performance of Juniper ASICs enables you to build out your segment-routing environment on your existing Juniper hardware with industry-leading scalability while continuing to use the same, consistent Junos operating system you already rely on.
Juniper uniquely allows you to design, manage, and concurrently support multiple network types as you introduce segment routing into your environment. With our NorthStar Controller, you can run multiple control planes at the same time: segment routing over MPLS (SR-MPLS), Label Distribution Protocol (LDP), Resource Reservation Protocol (R
Juniper uniquely allows you to design, manage, and concurrently support multiple network types as you introduce segment routing into your environment. With our NorthStar Controller, you can run multiple control planes at the same time: segment routing over MPLS (SR-MPLS), Label Distribution Protocol (LDP), Resource Reservation Protocol (RSVP) and native IP.
In this way, Juniper simplifies your transition from one control plane technology to another, enabling you to add segment routing into your environment incrementally and phase out your existing transport protocols when you’re ready.
This website uses cookies. By continuing to use this site, you accept our use of cookies.