Cisco Technology, Inc.

Ramesh Yeevani-Srinivas

Sanjay Kumar Hooda

Rajeev Kumar

Prakash C Jain

Shivaji Pundlik Diwane

Rohit Bahl

Roberto Mitsuo Kobo

Parthiv Shah

Automated techniques for converting network devices from a Layer 2 (L2) network into a Layer 3 (L3) network in a hierarchical manner are described herein. The network devices may be configured to boot such that their ports are in an initialization mode in which the ports are unable to transmit locally generated DHCP packets. When a network device detects that a neighbor (or 'peer') device has acquired an IP address or has been configured by a network controller, then the port on which the neighbor device is detected can then be transitioned from the initialization mode into a forwarding mode. In the forwarding mode, the port can be used to transmit packets to obtain an IP address. Thus, the network devices are converted from an L2 device to an L3 device in a hierarchical order such that upstream devices are discovered and converted into L3 devices before downstream devices.

Hierarchical provisioning of network devices

A system and method for onboarding a virtual machine in a bridge host extension mode are provided. The method includes: creating a virtual machine on a host computing device, wherein the host computing device is associated with a first MAC address and a first IP address; assigning the virtual machine a second MAC address by the host computing device; receiving a first DHCP packet from the virtual machine by the host computing device, wherein the first DHCP packet comprises a first field that includes the second MAC address; replacing the second MAC address in the first field with the first MAC address by the host computing device; adding the second MAC address to a second field of the first DHCP packet by the host computing device; and providing the first DHCP packet to a DHCP server through a network by the host computing device.

Systems and methods for the handling of bridged virtual machines

Services with policy control may be provided. A computing device may receive registration information associated with a border device. The registration information may comprise information identifying a service provided by a server associated with the border device, information identifying the border device, and policies associated with the service. Then an address for the server may be determined. Next a request may be received comprising the information identifying the service provided by the server. In response to receiving the request comprising the information identifying the service provided by the server, the address for the server, the information identifying the border device, and the policies associated with the service may be provided.

Zero day zero touch providing of services with policy control

Differentiated sidecars in a service mesh may be provided. A first routing rule includes a first plurality of weights to be associated with a first plurality of data paths of a first microservice instance may be received. Next, first mapping between a first set of features associated with the first microservice instance and the first plurality of weights may be determined. Then a second microservice instance may be detected and a second set of features associated with the second microservice instance may be detected. A second routing rule comprising a second plurality of weights to be associated with a second plurality of data paths of the second microservice instance may be determined. The second plurality of weights may be determined such that a second mapping between the second set of features and the second plurality of weights imitates the first mapping.

Differentiated smart sidecars in a service mesh

Systems and methods are disclosed for processing framed routes initiated by user equipment (UE) at customer-premises equipment (CPE) and gateways using protocol configuration options (PCO). The PCO can include encoding and decoding framed route information using a PCO information element (IE). The framed route information can include a framed route and a virtual private networking routing and forwarding (VRF) name. The framed route information can also include a tunnel identifier and a packet data protocol (PDP) address. The gateway can include a packet data network gateway (PGW) and a gateway general packet radio service support node (GGSN). When the gateway receives an attach request message from the UE with the encoded PCO, the gateway decodes the PCO to extract the framed route and VRF name, associates a tunnel identifier and PDP address with the extracted framed route and VRF name, and installs the framed route in a corresponding VRF.

Growing community of inventors

Freemont, CA, United States of America

Ramesh Yeevani-Srinivas