Cisco Technology, Inc.

John Mullooly

Fabio Rodolfo Maino

Darrel Jay Lewis

Gregg Schudel

Ali Sajassi

James Neil Guichard

Samer Salam

Dino Farinacci

Pradosh Mohapatra

Jesper Skriver

Christian Cassar

Isidoros Kouvelas

Brian Eliot Weis

Eric C Rosen

Bruce Stuart Davie

W Scott Wainner

Vincent Mammoliti

Viktor Mats Emanuel Leijon

Roger Fredrik Jansson

Gerhard Wieser

Vincent John Mammoliti

Presented herein are techniques to automatically provision cross-domain end-to-end services. A method includes receiving, at a cross-domain orchestrator, a request for a service, decomposing the request for the service into a first provisioning command and into a second provisioning command, sending the first and second provisioning commands to the first and second domains, respectively, receiving, from the first domain, in response to the first provisioning command, a first constraint associated with the first resource of the first domain, receiving, from the second domain, in response to the second provisioning command, a second constraint associated with the second resource of the second domain, distributing the first constraint to the second domain, and the second constraint to the first domain; and initiating, based on the first and second constraints, the service using the first resource of the first domain and the second resource of the second domain.

Cross-domain orchestration through boundary conditions

In one embodiment, a method includes receiving at a first network device in a first virtual private network, a packet destined for a second network device in communication with a second virtual private network, and transmitting the packet over the second network, wherein the packet is encapsulated for transmittal on a tunnel extending from the first network device to the second network device. The first network device is in communication with a system operable to map and encapsulate the packet and provide an overlay that traverses over the second virtual private network. An apparatus and logic are also disclosed herein.

Interconnecting virtual private networks

In one embodiment, a method includes receiving a packet at a first provider edge device in communication with a mapping system comprising mappings of customer routes to provider edge devices, and mappings of customer virtual routing and forwarding (VRF) instances to a service provider VRF instance, mapping a customer route to one of the provider edge devices and mapping a customer VRF instance to the service provider VRF instance, encapsulating the packet at the first provider edge device based on the mappings, and transmitting the packet to the provider edge device. An apparatus and logic are also disclosed herein.

Network virtualization using IP map and encapsulation

In one embodiment, a method includes receiving from a plurality of customer edge devices, endpoint addresses at a central mapping system operating as a control plane for a provider network in communication with a plurality of customer networks, and mapping the endpoint addresses to provider edge devices in the provider network. Wherein the customer edge devices store customer endpoint routes for active flows and the provider edge devices store customer edge device site locator addresses for use in a mapping and encapsulation overlay in the provider network. An apparatus and logic are also disclosed herein.

In an embodiment, a method of signaling status at a routing device is provided. In this method, the routing device establishes an inter-chassis control plane channel session with a remote routing device. Here, the routing device and the remote routing device are linked to a multi-homed routing device. The routing device then synchronizes with the remote routing device by way of the inter-chassis control plane channel session to identify a state of a link from the routing device to the multi-homed routing device. The state of the link is thereafter advertised by way of Border Gateway Protocol (BGP). Additionally, a method of discovering inter-chassis communication peers via BGP between the first and remote routing devices is provided.

Signaling of attachment circuit status and automatic discovery of inter-chassis communication peers

Techniques for configuring customer premises equipment for communication with a provider network include establishing a physical layer network connection between a particular customer node and a first provider node. The particular customer node is an intermediate network node on a customer premises. The first provider node is an intermediate network node on a first provider network of a first service provider different from the customer. Configuration data for one or more network interfaces on the particular customer node are automatically received through the physical layer network connection. The particular customer node is automatically configured based on that configuration data. The automatic provisioning of the customer node allows equipment to be more economically shipped and installed at customer premises and allows upgraded or replacement equipment to be more economically swapped in place of equipment previously installed. Traffic management data can also be automatically received and used at the particular customer node.

Techniques configuring customer equipment for network operations from provider edge

A method, apparatus and computer program product for providing secure multipoint Internet Protocol Virtual Private Networks (IPVPNs) is presented. A packet lookup is performed in order to determine a next hop. A VPN label is pushed on the packet, as is an IP tunnel header. Group encryption through the use of DGVPN is further utilized. In such a manner secure connectivity and network partitioning are provided in a single solution.

Secure multipoint internet protocol virtual private networks

An MPLS router operable for labeled switch path (LSP) operation defines a compression index for identifying a decompression context between other MPLS LSP routers. The compression index allows a multipoint-to-point link between MPLS routers, thereby avoiding an exhaustive mesh of point-to-point links between each of the MPLS routers. The originator ID identifies each of the multipoint originating endpoints at a common destination, and maintains the context of each compressed header to match incoming compressed headers to the corresponding header values. The originator ID, typically the IP address of the originator, operates as the compression index on the multipoint-to-point connection, operable to distinguish multiple originators of the multipoint-to-point connection and provide header compression for each.

Growing community of inventors

Colts Neck, NJ, United States of America

John Mullooly