In one embodiment, a method comprises: obtaining, by a process, path trace data collected by a plurality of performance monitoring agents across a computer network; obtaining, by the process, one or more catalogs having application-based correlation information for the path trace data; generating, by the process, network mapping directed graphs by correlating the path trace data using the one or more catalogs, the network mapping directed graphs logically comprising nodes categorized at a plurality of levels of aggregation and edges connecting the nodes; associating, by the process, test-based performance data with the edges of the network mapping directed graphs; and providing, by the process, at least one Sankey diagram based on the network mapping directed graphs and test-based performance data associated with their edges for selectable display by a user interface.

A solution for route selection includes receiving, by a network repository, from a first network function (NF), a query related to a target NF; querying, by the network repository, a route selection node for a shortest path to the target NF; receiving, by the network repository, from the route selection node, an indication of the shortest path to the target NF; and based on at least receiving the indication of the shortest path to the target NF, transmitting, by the network repository, to the first NF, a route to the target NF. In some examples, the shortest path has at least one of: a minimum number of hops, a minimum latency, a minimum jitter, and a minimum weighted transport score. In some examples, the route selection node is co-located with the network repository, which may be a network repository function (NRF).

Various approaches for allocating resources to an application having multiple application components, with at least one executing one or more functions, in a serverless service architecture include identifying multiple routing paths, each routing path being associated with a same function service provided by one or more containers or serverless execution entities; determining traffic information on each routing path and/or a cost, a response time and/or a capacity associated with the container or serverless execution entity on each routing path; selecting one of the routing paths and its associated container or serverless execution entity; and causing a computational user of the application to access the container or serverless execution entity on the selected routing path and executing the function(s) thereon.

A packet processing method and a gateway device are provided. The method includes: A first gateway device receives, by using a first link, a first one-arm BFD echo packet returned by a network device, where the first one-arm BFD echo packet includes identification information, and the identification information is used to uniquely identify a second gateway device. The first gateway device determines, based on the identification information, to forward the first one-arm BFD echo packet to the second gateway device. The first gateway device sends the first one-arm BFD echo packet to the second gateway device. The network device is multi-homed connected to the first gateway device and the second gateway device. The first gateway device and the second gateway device form a multi-active gateway. According to the method, efficiency of detecting, by using a one-arm BFD echo session in a VXLAN multi-active gateway scenario is improved.

Systems and methods of mesh network communication enabling a relay node to autonomously select a packet propagation mechanism. Upon receiving a packet, which may carry an indication for flooding propagation as set by the edge node originating the packet, or carry no specification for any propagation mode, the relay node determines whether the packet is eligible for routing-propagation based on a number of factors, such as whether there is an existent valid route from the source node to the destination node, whether the packet is originated from a friend edge node, and whether a route discovery process has been initiated. Accordingly, the relay node may change the indication to routing propagation and forward it by routing-relaying. Thus, the packet can be propagated over the mesh network by routing propagation, despite the initial setting for flooding propagation as specified by the edge node or no setting by the edge node.

Systems, methods, and devices for improved routing operations in a network computing environment. A system includes a virtual customer edge router and a host routed overlay comprising a plurality of host virtual machines. The system includes a routed uplink from the virtual customer edge router to one or more of the plurality of leaf nodes. The system is such that the virtual customer edge router is configured to provide localized integrated routing and bridging (IRB) service for the plurality of host virtual machines of the host routed overlay.

A method for automatic configuration of a communication network includes: generating a request message, the request message including a communication address associated; transmitting the generated request message as a broadcast message to a plurality of computing devices using a predefined user datagram protocol (UDP) port, the message being broadcast with a predetermined time to live; receiving agreement messages from computing devices transmitted by the respective computing device using the predefined UDP port, each agreement message including a communication address associated with the respective computing device and a specified transmission control protocol (TCP) port; identifying at least one of the one or more agreement messages for establishment of communication; and establishing a communication connection to the computing device associated with each identified agreement message using the specific TCP port.

A method and system for packet tracing is described. In one embodiment, a method includes selecting a packet for tracing through a cluster of a plurality of nodes. The method includes preparing the packet for tracing by generating a cluster-wide unique ID, associating the unique ID with the packet, generating a running counter, and associating the counter with the packet. The method includes generating a first record buffer on a first node of the plurality of nodes and recording the unique ID and an initial value of the counter. The method includes recording a description of an operation performed on the packet in the first record buffer along with a value of the counter. The method also includes transferring the packet to a second node, along with the unique ID, the value of the running counter, and an attribute that indicates that the packet is to be traced.

A method for providing cloud network reachability analysis includes receiving a reachability query requesting a reachability status of a target including a packet header associated with a data packet. The packet header includes a source IP address and a destination IP address. The method also includes generating one or more simulated forwarding paths for the data packet based on the packet header using a data plane model. Each simulated forwarding path includes corresponding network configuration information. The method includes determining the reachability status of the target based on the one or more simulated forwarding paths and providing the determined reachability status and the one or more simulated forwarding paths to a user device associated with the reachability query which causes the user device to present the network configuration information for each simulated forwarding path.

A provider edge (PE) device may receive traffic associated with one or more services, wherein the traffic includes a plurality of packets, and may determine, based on the plurality of packets, one or more packets respectively associated with each service of the one or more services. The PE device may determine, based on the one or more packets respectively associated with each service of the one or more services, a respective status of each of the one or more services. The PE device may generate type-length-value (TLV) data that indicates the respective status of each of the one or more services and may cause the TLV data to be added to a link layer discovery protocol (LLDP) packet. The PE device may send the LLDP packet that includes the added TLV data to a customer edge (CE) device.