Cisco Technology, Inc.

Rajesh Babu Nataraja

Shyam N Kapadia

Nilesh Shah

Yibin Yang

Padmanabhan Krishnan

Naoshad Mehta

Rick G Chang

Viral Rajeshbhai Barot

Akshya Kumar Singh

Sri Goli

Nader Lahouti

Jay Ajaykumar Gheewala

Liqin Dong

Ming Zhang

Suran Saminda De Silva

Chengelpet Ramesh

Stephanie Wong

Huilong Huang

Esha Desai

Srividya Vemulakonda

Chirag Tayal

Pei-chun Cheng

Sujatha Balaraman

Ganesh P Murthy

Yaonan Liang

Lei Fu

Ganeshmani Venkatesh

Chengelpet V Ramesh

Techniques are presented herein for providing a persistent external Internet Protocol (IP) address for extra-cluster services. One example involves initiating, in a cluster, a first pod with a label that identifies a service. The first pod is configured to provide the service to one or more network entities outside the cluster. The first pod is assigned an IP address configured for communicating outside the cluster. A mapping of the service to the IP address is stored. In response to a determination that the service has been disrupted, a second pod is initiated in the cluster with the label that identifies the service. The second pod is configured to provide the service to the one or more network entities outside the cluster. Based on the mapping and the label that identifies the service, the IP address is assigned to the second pod.

Providing persistent external internet protocol address for extra-cluster services

A source host device masks the hardware address of a hosted container from a network device to mitigate the use of resources in the network device. A virtual switch on the source host receives a frame from a hosted container. The frame includes a source hardware address of the hardware address corresponding to the hosted container. The frame also includes a source network address of the network address corresponding to the hosted container. The virtual switch replaces the source hardware address of the frame with the hardware address associated with the source host, and send the frame to the network device. The frame sent to the network device includes the host hardware address as the source hardware address and the container network address as the source network address.

Mitigating network/hardware address explosion in network devices

In one example, a network device detects when a deployment request for the network device from a network controller is stored in a directory corresponding to the network device. Deployment information is stored as a value of a first key in the directory and includes information to configure the network device to attain a set of goals. The network device retrieves the deployment information from the directory. The network device is configured to attain the set of goals by the network device applying the retrieved deployment information. The network device generates one or more status notifications indicating a status of configuring the network device, and stores the one or more status notifications as a value of a second key in the directory to indicate the status to the network controller.

Intent deployment in a network environment

Techniques for virtual workload deployment based on computing resource hardware load and associated network hardware load. For each of a plurality of computing resources within one or more data centers onto which a virtual workload can be deployed, a computing resource hardware load of the respective computing resource is determined. Network topology information is maintained for at least one network fabric of the one or more data centers, and an associated network hardware load of a network device communicatively connected to the respective computing resource is determined. Embodiments automatically select one or more computing resources. The virtual workload is deployed onto the automatically selected one or more computing resources.

Network-aware workload placement in a data center

In one implementation, a method performed by a first node with interfaces configured as IP unnumbered interfaces sharing a single IP address and to communicate with a DHCP-associated second node includes: obtaining a first message that indicates a configuration status of a third node at a respective interface; obtaining a second message for the third node from the DHCP-associated second node that includes a temporary IP address for the third node and an indicator of a file server; obtaining a third message associated with the third node that includes the temporary IP address, the third message requests address information for the file server; and configuring the third node by establishing a connection between the third node and the file server to transfer at least one configuration file, where configuring the third node includes providing the temporary IP address to the DHCP-associated second node via BGP.

Method and device for provisioning a new node using IP unnumbered interfaces

A network controller deploys network management applications to containers hosted on compute nodes. For each container on each compute node, the controller determines the network connectivity required by the application; assigns to the container one or more Internet Protocol (IP) addresses that satisfy the network connectivity, and provides the one or more IP addresses to the container; upon detecting the container is lost, blocks the one or more IP addresses so that the they cannot be re-assigned to any other container; and upon detecting that the application has been re-deployed to a new container on a new compute node, unblock the blocked one or more IP addresses, and assign and send the one or more IP addresses to the new container to enable the new container to establish the network connectivity required by the application without network address translation.

Container networking for connecting network controller applications to a switch fabric

In accordance with one example embodiment, there is provided a system configured for virtual local area network (VLAN) blocking on a virtual port channel (vPC) member link to handle discrepant virtual network instance (VNI) to VLAN mappings. In other embodiments, the system can be configured for providing Virtual Switch Interface Discovery Protocol (VDP) and virtual switch enhancements to accommodate discrepant VNI to VLAN mappings. In another example embodiment, an apparatus is provided that includes a processor, and a memory coupled to the processor, where the apparatus is configured such that if a server is connected through a virtual port channel, a VDP is used to notify the server of different VNI to VLAN mappings. In another embodiment, the apparatus can extend a VDP Filter Info Field to carry a set of VLANs mapped to a VNI, keyed by leaf MAC addresses that serve as bridge identifiers.

Automatic resolution of virtual network instance to VLAN mapping conflicts in dual-homed deployments in a dynamic fabric automation network architecture

A method is described and in one embodiment includes receiving at a top-of-rack ('TOR') switch a notification concerning a virtual machine ('VM'), wherein the received notification identifies a host associated with the VM; determining whether the identified host is directly connected to the TOR switch; and if the identified host is not directly connected to the TOR switch, identifying an intermediate switch to which the identified host is directly connected; and determining whether the identified intermediate switch to which the identified host is directly attached is attached to the TOR switch.

Techniques for integration of blade switches with programmable fabric

Embodiments include determining computing resources within one or more data centers onto which a virtual workload can be deployed. Network state data is determined for a plurality of network resources within a network fabric of a data center. For each of the plurality of computing resources, embodiments determine a respective suitability value describing a fitness of the respective physical server for deploying at least a portion of the virtual workload. Such a determination includes determining a respective at least one of the plurality of network resources within the at least one network fabric corresponding to the respective computing resource and determining a current workload of the at least one network resource, based on the network state data. Upon selecting one or more computing resources of the plurality of computing resources based on the determined suitability values, embodiments deploy the virtual workload onto the selected one or more computing resources.

A method is provided in one example embodiment and includes receiving at a first network element a packet from a second network element; processing the packet at the first network element to obtain information regarding an identity of a virtual machine ('VM') hosted by the second network element contained within the packet; and storing at the first network element the identifying information. The identifying information stored at the first network element is accessible by at least one third network element. In some embodiments, the first network element comprises a physical switch and the second network element comprises a virtual switch.

Growing community of inventors

Sunnyvale, CA, United States of America

Rajesh Babu Nataraja