Cisco Technology, Inc.

Kaushik Pratap Biswas

Siva S Jayasenan

Senthil M Sivakumar

Jayesh Chokshi

Vinay Jayant Pande

Mark Denny

Yanping Qu

Anantha Ramaiah

Sabita Jasty

Yegappan Lakshmanan

Sepehr Safari

Daniel George Wing

Balaji Sundararajan

Vamsidhar Valluri

Chandramouli Balasubramanian

Madhuri Kolli

Mahadev Somasundaram

Suresh Satapati

Ankush Verma

Bhavana Malhotra Bodas

Anirudh Ramnath Ramakrishna

Michael J Sullenberger

Ahmad Reza Yazdi

Michael Lee Sullenberger

Vikas Butaney

Ian Herbert Wilson

Melinda L Shore

Thimmappa Thejaswi

Tuan Q Le

Alexander Yeh

Methods, systems, and non-transitory computer-readable media are provided for deploying intent-driving cloud branches. An example method can include obtaining, by one or more controllers in a software-defined network (SDN), a branch network design template for deploying a remote branch in the SDN, wherein the branch network design template defines networking settings for a plurality of services to be provisioned at the remote branch; obtaining, by the one or more controllers, a plurality of software packages for the plurality of services to be provisioned at the remote branch; and based on the branch network design template and the plurality of software packages, provisioning, by the one or more controllers, the plurality of services at the remote branch and a network connectivity of the plurality of services.

Intent-driven cloud branches

A virtual machine management service obtains a request to instantiate a virtual machine image (VMI) to implement a virtual network function (VNF). The request specifies a set of processor requirements corresponding to instantiation of the VMI. In response to the request, the service identifies, from a server comprising a set of processor cores, available processor capacity. The service determines, based on the available processor capacity and the set of processor requirements, whether to instantiate the VMI on to a subset of processor cores of the server. Based on this determination, the service instantiates the VMI on to the subset of processor cores to implement the VNF.

Computing resource allocation for virtual network functions

Systems, methods, and computer-readable media are provided for software defined branch single IP orchestration. An example method can include establishing, by a controller, a secure tunnel agent to an orchestrator, generating, by the controller, a single IP address on a virtual router for a virtual branch site, and monitoring, by the controller, reachability of the single IP address on the virtual router.

Software defined branch single internet protocol orchestration

An elastic Internet Protocol (IP) address for hypervisor and virtual router management in a branch environment may be provided. First, an IP address may be assigned to a hypervisor associated with a virtual branch. Next, it may be determined that a virtual machine (VM) has been instantiated at the virtual branch. In response to determining that the VM has been instantiated at the virtual branch, the IP address may then be released. It may next be determined that the VM is in a failed state and then, in response to determining that the VM is in the failed state, the IP address may be reassigned to the hypervisor.

Elastic internet protocol (IP) address for hypervisor and virtual router management in a branch environment

In one embodiment, an apparatus comprises logic for optimizing return traffic paths using network address translation (NAT). The logic is operable to receive outbound data from a source node in a source network, and to replace a source address in a source address field in the outbound data with a first address from a first address pool associated with a first connection. The logic is operable to determine that return traffic on the first connection needs to be switched over to a second connection, where a second address pool is associated with the second connection. The logic is operable to generate a mapping that associates the first address with a second address from the second address pool and, based on the mapping, to replace the first address in the source address field in the outbound data with the second address. The logic is also operable to send the outbound data to the destination node over the second connection.

Optimizing return traffic paths using network address translation

In one embodiment, a device comprises an input port for receiving network packets that are being communicated via a computer network. A processor is in communication with the input port. The processor is configured to facilitate dynamic monitoring and updating of port addresses assigned by at least one non-ALG PAT router so as to facilitate communication of packets that are exchanged between an inside user agent and an outside user agent in a manner that mitigates a likelihood of communication interruption during a VOIP session. An output port is in communication with the processor for transmitting packets via the computer network.

Mechanisms for session border control of VOIP communication from non-symmetric port address translation device

Example systems and methods associated with router synchronization are described. One example method includes reducing a likelihood that a first network device will be favored over a peer device as a router. This likelihood may be increased after the first network device has received a threshold amount of routing information from the peer device. This may allow the first network device to begin performing non-routing related tasks after it starts up without causing interruption of data streams for which the first network device does not have current routing information.

Router synchronization

Disclosed are methods and apparatus for handling data having an embedded address (and port). In general terms, a host of a private network is operable to obtain from its corresponding edge router a global address (GA) and optionally an additional global port range (GPR). When the host then wishes to transmit data out of the private network, the obtained GA (and GPR) may then be used for an embedded address (and port) within data sent by the host to a public network. The obtained GA (and GPR) may also be used by the host to translate its own source address and port in its IP and/or TCP/UDP header if needed.

Method and apparatus for making end-host network address translation (NAT) global address and port ranges aware

In one embodiment, a signaling message is received from an endpoint. It is determined from the signaling message whether, prior to sending the signaling message, the endpoint performed network address translation on the body of the signaling message. If it is determined from the signaling message that, prior to sending the signaling message, the endpoint did not perform network address translation on the body of the signaling message, application layer gateway functionality is applied to the body of the signaling message such that a modified signaling message is generated.

Intelligent ALG functionality in networks supporting endpoints performing network address translation

Disclosed are apparatus and methods for managing session data in a session border controller (SBC), where the session data is sent from a first node, such as a first phone, to a second node, such as a registrar or second phone. In one example embodiment, the following operations are performed in a first intermediary node that is configured to provide network address translation (NAT) for both a header and payload of a session packet and has an inside interface coupled with a second intermediary node that is configured to perform NAT for only a header of session packets. It is determined whether an end node is sending session packets that are not used to set up a session and that result in a binding that was formed by the second intermediary node being retained. The binding associates inside and outside addresses of the end node, and an end node is defined as a node that originates a session packet. It is determined whether to inhibit a registration throttling process from being performed by the first intermediary node, that results in the binding being retained, based on whether it is determined that the end node is sending session packets that are not used to set up a session and that result in the binding being retained.

Mechanisms for providing intelligent throttling on a NAT session border controller

Disclosed are apparatus and methods for managing session data in a session border controller (SBC), where the session data is sent from a first node, such as a first phone, to a second node, such as a registrar or second phone. In general, embodiments of the present invention support SBC functionality by managing sessions through the SBC without implementing a terminate and regenerate of the sessions, but rather by intercepting packets destined to the second node and efficiently handling such functionality in the forwarding-path. Also in deployments where the endnodes require NAT (network address translation), mechanisms are provided in the SBC to perform NAT on the addresses embedded in the payload of the session data. In other aspects, mechanisms for keeping the sessions or NAT entries alive are facilitated at the SBC, even when an endnode has a expiration time that differs an expiration time of another device, such as a registar device. Other embodiments allow the actual media packets to flow through the SBC (e.g., for security, accounting, etc) while allowing two endnodes to utilize a same private address or domain.

Growing community of inventors

San Jose, CA, United States of America

Kaushik Pratap Biswas