Juniper Networks, Inc.

Jacopo Pianigiani

Atul S Moghe

Tong Jiang

Vivekananda Shenoy

Ankur Tandon

Manish Krishnan

Rishabh Ramakant Tulsian

Sukhdev S Kapur

Sridevi JeevaRaj

Anantharamu Suryanarayana

Sahana Sekhar Palagrahara Chandrashekar

Suresh K Balineni

Dhiraj D Ballal

Vinod Nair

Ashok Ganesan

Saravanadas P Subramanian

Michael Henkel

Michal Styszynski

Ignatious Johnson Christober

Joseph Williams

Soumil Ramesh Kulkarni

Jeba Paulaiyan

Thomas Murray

Mahesh Sivakumar

Sanjay Agrawal

Harsha Srinath

Sandesh Kumar Sodhi

Gregory M Dalle

Kiran N Kasim

Manas Pal

Abhinav Pandit

Akshaya Muralidharan

Rahul Suhas Vaidya

Sreelakshmi Sarva

Shivayogi Ugaji

Christian Lambert

Parag Sanghvi

Patrik Bok

Supriya Sridhar

Ignacio Suarez Navas

Christian Thrun

Luca Tosolini

Julio Carrasco Pinto

Carlos Parada

Francis Xavier Antonio Santana

Nachi Ueno

Dheeraj Gautam

Thomas A Murray

Sridevi Jeevaraj

Virtual network controllers are described that automatically generate policies and configuration data for routing traffic through physical network function (PNF) service chains in a multi-tenant data center. An example network controller includes a memory and processing circuitry configured to: automatically generate, for one or more integrated routing and bridging (IRB) units of corresponding virtual network forwarding tables of a switch of a switch fabric of a data center network, configuration information that, when deployed, causes the IRB units to direct data traffic conforming to multiple communication protocols and flowing over a plurality of virtual networks between a first set of server devices and a second set of server devices positioned outside of the switch fabric (i) toward a service device logically positioned outside of the switch fabric and coupled to the switch, and (ii) back from the service device into the switch fabric via the switch.

Multi-protocol service chaining among devices of interconnected topology

In general, a device comprising a processor and a memory may be configured to perform various aspects of the techniques described in this disclosure. The memory may store source configuration data of a source environment descriptor associated with a source operating environment and target configuration data of a target environment descriptor associated with a target operating environment. The processor may compare the source configuration data to the target configuration data, and generate, based on the comparison, update data including software component versions. The processor may generate, based on the update data, a unified release including a new application release version, the new application release version including release propagation data. The processor may further propagate the unified release to the target operating environment, where the release propagation data may provide instructions for the target operating environment to update the target configuration data and deploy a new application service.

Automated application service deployment across multiple environments

An example data center system includes server devices hosting data of a first tenant and a second tenant of the data center, network devices of an interconnected topology coupling the server devices including respective service virtual routing and forwarding (VRF) tables, and one or more service devices that communicatively couple the network devices, wherein the service devices include respective service VRF tables for the first set of server devices and the second set of server devices, and wherein the service devices apply services to network traffic flowing between the first set of server devices and the second set of server devices using the first service VRF table and the second service VRF table.

Service chaining among devices of interconnected topology

A system for configuring a data center includes a fabric management server coupled to a management switch. A provisional Software Defined Networking (SDN) controller executing on the fabric management server can discover physical servers coupled to the management switch, receive network interface configuration information from the physical servers, and use the discovered network interface configuration information to determine a configuration for switches and servers coupled to an IP fabric. The configuration can be migrated to a full functionality SDN controller.

Initializing network device and server configurations in a data center

A virtual port group abstraction can facilitate automated configuration of devices in a data center. For example, a data center administrator can define a virtual port group to include a set of logical and physical interfaces for devices allocated to a particular department or other group within a company. An administrator for the department can then utilize a user interface to perform actions with respect to the virtual port group. The actions can include configuration actions, modeling actions and/or deployment actions. An action received by a network management controller such as a Software-Defined Networking (SDN) controller can be converted into the appropriate actions for the relevant logical and physical interfaces that are configured to be part of the virtual port group.

Virtual port group

Techniques are described in which a centralized controller constructs a service chain between a bare metal server (BMS) and a virtual execution element (e.g., virtual machine or container), or in some instances a remote BMS, across a plurality of networks. In some examples, the controller may construct a service chain between a BMS and a virtual execution element or remote BMS using Ethernet Virtual Private Network (EVPN)-Virtual Extensible Local Area Network (VXLAN) and Internet Protocol Virtual Private Networks (IP VPNs) such as BGP/Multiprotocol Label Switching (BGP/MPLS) IP VPNs.

Inter-network service chaining

Network controllers are described that enable creation of logical interconnects between logical routers of different, isolated virtual networks and for auto-generation and deployment of routing policies to control 'leaking' of select routes amongst the different virtual networks. In one example, a network controller includes a memory and processing circuitry configured to identify a source logical router of a first virtual network and a destination logical router of a second virtual network implemented on one or more physical devices of a switch fabric, form a policy defining one or more rules for controlling leaking of one or more of the routes through a logical router interconnect from the source logical router to the destination logical router, and push the policy to the one or more physical devices of the switch fabric for application to communications through the logical router interconnect.

Data center tenant network isolation using logical router interconnects for virtual network route leaking

In general, techniques are described for defining and executing device-independent commands on a network having a plurality of network devices. In some examples, a controller includes a graphical user interface. The controller displays, via the graphical user interface, network devices that support a device-independent command selected from one or more device-independent commands, wherein each device-independent command performs one or more operations on supported network devices. The controller receives, via the graphical user interface, user input selecting two or more of the displayed network devices and performs the one or more operations of the selected device-independent command on the selected network devices. In some examples, performing includes executing tasks associated with each network device, wherein the tasks, when executed, perform the one or more operations on each respective network device.

User customization and automation of operations on a software-defined network

An access profile includes configuration characteristics that are defined using device and operating system agnostic attributes. Thus, the access profiles are not necessarily dependent or otherwise tied to any particular vendor or network OS. When a system administrator configures one or more service access points, the system administrator need only specify the vendor and network OS agnostic characteristics that are to be associated with the service access point. A configuration generator can generate vendor specific and/or network specific configuration commands and data from the vendor and network OS agnostic access profile attributes. The generated configuration commands and data can be provided to a network device hosting the service access point using a vendor specific and/or network OS specific configuration application program interface.

Vendor agnostic profile-based modeling of service access endpoints in a multitenant environment

Techniques are disclosed for providing a Software Defined Networking (SDN) controller with real-time or near-real time visibility of the operation of data center fabrics to determine whether the DCI was properly configured. For example, an SDN controller receives high-level configuration data that describes a desired state of a network managed by the SDN controller at a high level of abstraction. The SDN controller applies a transformation function to the high-level configuration data to generate a low-level configuration data for network devices configured to implement the desired state of the network. SDN controller configures the SDN controller as a peer to the network devices to obtain one or more routes exchanged between the network devices. The SDN controller sends the low-level configuration data to the network devices to cause the network devices to implement the desired state of the network.

Inter-data center software-defined network controller network

Initializing server configurations in a data center

In some examples, a software-defined networking engine is configured to receive a user-defined cabling plan for a computer network and receive information indicative of a physical cabling topology for the computer network. The software-defined networking engine is also configured to determine a difference between the user-defined cabling plan and the physical cabling topology. The software-defined networking engine is further configured to output an indication of the difference between the user-defined cabling plan and the physical cabling topology.

Validation of a user-defined cabling plan for a computer network based on a physical cabling topology

Growing community of inventors

Cupertino, CA, United States of America

Jacopo Pianigiani