In an example implementation, a network topology map with storage paths between servers and storage volumes of storage arrays in a storage network through network switches may be generated. A network switch may be identified from the network switches in the network topology map as a bottleneck by monitoring a performance parameter for each of the network switches. The performance parameter is indicative of I/O load at a port of a respective network switch. Storage volumes in the network topology map and connected to the bottlenecked network switch may be identified, and storage volume I/O metrics associated with each of the servers with respect to the identified storage volumes may be aggregated. Based on the aggregated storage volume I/O metrics, at least one of the servers may be determined as a candidate for a root-cause of the bottleneck.

Approaches for performing all DOCSIS downstream and upstream data forwarding functions using executable software. DOCSIS data forwarding functions may be performed by classifying one or more packets, of a plurality of received packets, to a particular DOCSIS system component, and then processing the one or more packets classified to the same DOCSIS system component on a single CPU core. The one or more packets may be forwarded between a sequence of one or more software stages. The software stages may each be configured to execute on separate logical cores or on a single logical core.

A system includes masking servers, transport servers, and signal servers. Each transport server stores masking server Internet Protocol (IP) addresses. Each signal server is configured to store transport server IP addresses, receive an update request from a client, and send the transport server IP addresses to the client in response to the update request. Each transport server is configured to receive a request data payload for a destination target server from the client, select a masking server, and send the request data payload to the selected masking server. The selected masking server is configured to send the request data payload to the target server, receive a response data payload from the target server, and send the response data payload to the transport server from which the request data payload was received. The transport server that receives the response data payload sends the response data payload to the client.

A method of utilizing the same hardware network interface card (NIC) in a gateway of a datacenter to communicate datacenter tenant packet traffic and packet traffic for a set of applications that execute in the user space of the gateway and utilize a network stack in the kernel space of the gateway. The method sends and receives packets for the datacenter tenant packet traffic through a packet datapath in the user space. The method sends incoming packets from the NIC to the set of applications through the datapath in the user space, a user-kernel transport driver connecting the kernel network stack to the datapath in the user space, and the kernel network stack. The method receives outgoing packets at the NIC from the set of applications through the kernel network stack, the user-kernel transport driver, and the data path in the user space.

Methods and systems for managing data transmissions. The methods disclosed herein may involve receiving requests for a first and a second service, and routing communications with the second service through the first service without requiring the firewall to be reconfigured to allow communications with the second service.

A method of relocating application context by an edge enabler client (EEC) in an edge computing system includes determining whether the application context should be relocated based on at least one piece of location information of a user equipment (UE) including the EEC and service area information for an edge data network (EDN), an edge enabler server (EES), or an edge application server, transmitting a context relocation request to a source edge enabler server (S-EES), based on the determination, receiving a context relocation response message indicating completion of the context relocation from the source edge enabler server, and rerouting application data traffic, based on the context relocation response message.

A novel design of a gateway that handles traffic in and out of a network by using a datapath daemon is provided. The datapath daemon is a run-to-completion process that performs various data-plane packet-processing operations at the edge of the network. The datapath daemon dispatches packets to other processes or processing threads outside of the daemon by utilizing a user space network stack.

A first distributed processing node transmits distributed data to a second distributed processing node as intermediate consolidated data. A third distributed processing node generates intermediate consolidated data after update from received intermediate consolidated data and distributed data, and transmits the intermediate consolidated data to a fourth distributed processing node. The first distributed processing node transmits the received intermediate consolidated data to fifth distributed processing node as consolidated data. The third distributed processing node transmits the received consolidated data to a sixth distributed processing node. When an aggregation communication time period required by each distributed processing node to consolidate the distributed data or an aggregation dispatch communication time period being a total time period of the aggregation communication time period and a time period required by each distributed processing node to dispatch the consolidated data exceeds a predetermined time period, the first distributed processing node issues a warning.

A method disclosed herein may include receiving a portal group from a node of a distributed storage system, the portal group comprising a plurality of network portals for accessing a storage unit, and transmitting data of the portal group to a first client and to a second client, wherein data transmitted to the first client and data transmitted to the second client each identify the plurality of network portals and indicate a different preferred network portal. The method may further include receiving a request from the first client to initiate a storage session that uses one of the plurality of network portals, establishing the storage session, wherein the storage session comprises multiple paths to the storage unit over at least two of the plurality of network portals, and providing data of the storage unit to the first client using the storage session.

Enhanced packet redirect capabilities are disclosed herein for draining traffic to a server. In an implementation, a server in an infrastructure service receives a packet from a stateless load balancer. The packet may comprise a request for content. A user space program on the server determines whether a connection identified in the packet belongs to the server. If the connection belongs to the server, the user space program handles the request for the content. If not, the server forwards the packet to a secondary server in the infrastructure service. The secondary server, to which the connection may belong, can then handle the request.