Techniques for defining a service flow definition among container pods that provide services in a network. The techniques may include an orchestrator of a computer network platform of the network determining which container pods need to communicate with which container pods. The service flow definition thus indicates needed paths between the container pods. In configurations, a cluster topology may be determined where the cluster topology indicates corresponding nodes of the network in which each container pod is located, as well as end points of the network with which the corresponding nodes communicate. Based at least in part on the service flow definition and the cluster topology, corresponding route distribution policies may be determined for the end points. The corresponding route distribution policies may be applied to the end points.

A communication method, a device, and a system are disclosed. An SF device adds a first location identifier including an identifier of the SF device and an identifier of a first physical port to a received first packet sent by first user equipment, and sends a second packet to which the first location identifier is added to a first UP device. The first UP device sends a third packet to a CP device, and the CP device sends the third packet to a USF device. The USF device interacts with an SDN controller, to enable the SDN controller to deliver a configuration instruction to the corresponding SF device. The first packet may be a DHCP packet or a PPPoE packet, and OPTION82/OPTION18 is added to carry the first location identifier.

Techniques disclosed herein provide a method and systems for installing routes by a route reflect (RR) device when the tunnel RIB of the RR device does not include any tunnel labels definitions. The unicast routing information base (RIB) of route reflector (RR) device is configured to include a next hop associated with a first network device. When the RR device receives a route from the first network device that comprises a tunnel label for reaching the second network device, the RR device resolves the next hop of the received route using the unicast RIB of the RR device. In response to the resolving, the RR device forwards the route to a third network device (e.g., identified by an export route target of the RR device).

Example implementation relates to a method of failure detection and seamless traffic switchover in a VPN system. A cluster of nodes exchange heartbeat messages to detect a failure at a first node in the cluster. When failure is detected at the first node, a master node transmits a failover message to a network end node connected to the first node. The failover message includes a list of active nodes to which traffic may be routed. The network end node updates its routing table based on the failover message and switches the traffic to a second node in the cluster of nodes.

Aspects of the disclosure involve systems and methods for utilizing Virtual Local Area Network separation in a connection, which may be a single connection, between a customer to a telecommunications network and a cloud environment to allow the customer to access multiple instances within the cloud through the connection. A customer may purchase multiple cloud resource instances from a public cloud environment and, utilizing the telecommunications network, connect to the multiple instances through a communication port or connection to the cloud environment. To utilize the single connection or port, communication packets intended for the cloud environment may be tagged with a VLAN tag that indicates to which cloud instance the packet is intended. The telecommunications network may route the packet to the intended cloud environment and configure one or more aspects of the cloud environment to analyze the attached VLAN tag to transmit the packet to the intended instance.

Techniques are described for communications in an L2 virtual network. In an example, the L2 virtual network includes a plurality of L2 compute instances hosted on a set of host machines and a plurality of L2 virtual network interfaces and L2 virtual switches hosted on a set of network virtualization devices. An L2 virtual network interface emulates an L2 port of the L2 virtual network. IGMP configuration is distributed to the L2 virtual switches. A control plane of the L2 virtual network coordinates IGMP configuration across the L2 virtual switches.

Disclosed herein is a manufacturing line computer system including: first and second computers. The first computer includes a storage section adapted to store a template that associates role information of the second computer and a network address of the second computer; and a reply section adapted to return the network address of the second computer associated with the role information to the second computer in response to reception of the role information from the second computer. The second computer includes an input section adapted to input the role information of the second computer; a transmission section adapted to send the input role information of the second computer to the first computer; and a network address setup section adapted to specify the network address, returned from the first computer, for the second computer.

A method includes a second provider edge (PE) device sending, to a first PE device, a media access control (MAC) route learned from a customer edge (CE) device, wherein the first PE device generates a MAC forwarding entry based on the MAC route, wherein the first PE device may forward, based on the MAC forwarding entry using the CE device, a packet whose destination MAC address is the CE device or a MAC address of a terminal device accessing the CE device, and wherein an outbound interface identifier included in the MAC forwarding entry is an identifier of an interface connected to the CE device.

Techniques for transmitting data packets on a shared channel in a data communications network, include determining a time slot interval, T, based on a longest data packet to be transmitted on a shared channel in a data communications network. At a first node in the data communications network a local base time, t.sub.0, is determined equal to a time at an end of receipt of a successful acknowledgement control packet on the shared channel. A local data packet is transmitted from the first node onto the shared channel at a transmit time that is an integer multiple n of T after the local base time t.sub.0. The local data packet is determined to be successfully transmitted when a successful acknowledgement control packet that uniquely indicates the local data packet is received on the shared channel within the interval T of transmitting the local data packet.

The present technology pertains to a system and method for extending enterprise networks' trusted policy frameworks to cloud-native applications. The present technology comprises sending, by an enterprise network controller, a first communication to a service mesh orchestrator for a service mesh, wherein the first communication informs the service mesh orchestrator of traffic segmentation policies to be applied to traffic originating at an enterprise network and of layer 7 extension headers which correspond to the enterprise network traffic segmentation policies.