Networks and methods are provided for use in directing retry requests for content based on intervals to retry defined by network conditions. One example method generally includes receiving, from a computing device, an application programming interface (API) request for content and determining whether the API request exceeds a predefined rate limit of API requests. The method then includes, in response to the API request exceeding the predefined rate limit, calculating a retry interval for the API request based on the predefined rate limit of API requests and a number of expected API requests for an upcoming interval, appending the retry interval to a failure notice, and transmitting the failure notice to the computing device thereby indicating to the computing device to retry the API request based on the retry interval rather than immediately or rather than at another preset interval of the computing device.

A mapping system, under administrative control of a Wide Area Network (WAN) controller, can track each host, authorized to access a plurality of Local Area Networks (LANs), in one or more mapping databases including a first network address representing an identifier and a second network addressing representing a locator for each host. The mapping system can receive a request for resolution of a first identifier of a host not presently connected to the network. The mapping system can determine the mapping databases exclude a mapping for the first identifier. The mapping system can update the mapping databases with a first mapping including the first identifier and a first locator corresponding to a honeypot network device. The mapping system can transmit, to one or more LANs of the plurality of LANs, routing information to route traffic destined for the first identifier to the honeypot network device.

An example operation may include a method comprising one or more of receiving a heartbeat failure notification message when a VNFCI is in standby state, building, at a VNFCI, a next state request message with standby and heartbeat failure parameters, sending the next state request message to an EMS, retrieving, at the EMS, a peer VNFCI state when the next state request message is received, sending a next state response message to the VNFCI with active state when one or more of: a peer VNFCI admin state is not online, and when a peer VNFCI is not reachable when the peer VNFCI admin state is online, sending a next state response message with standby state when the peer operational state is active, and sending the next state response message with standby to the VNFCI when the request of current issues on resources associated with the VNFCI from the VNFM is received and there are critical issues at the EMS.

Methods and systems related to speculative resource allocation for routing on an interconnect fabric are disclosed herein. One disclosed method includes speculatively allocating a collection of resources to support a set of paths through an interconnect fabric. The method also includes aggregating a set of responses from the set of paths at a branch node on the set of paths. If a resource contention is detected, the set of responses will include an indicator of a resource contention. The method will then further include transmitting, from the branch node and in response to the indicator of the resource contention, a deallocate message downstream and the indicator of the resource contention upstream, and reallocating resources for the multicast after a hold period.

One example disclosed method involves a computing system determining that a first shared computing resource, included among a plurality of shared computing resources managed by a controller, is potentially faulty. The system may configure the controller to identify the first shared computing resource with a tag, the tag configured to cause the controller, in response to a client requesting the controller for access to a first application, to assign the first shared computing resource to deliver the first application to the client. The system may instruct the client to request the controller for access to the first application. The system may determine that the first shared computing resource is faulty based on the client being unable to access the first application at a time of application of the tag to the first shared computing resource. The system may take a corrective action with respect to the first shared computing resource.

A method and a system for processing an NF component exception, where the method is applied to a network including user equipment, a first NF component, a second NF component, and an NF repository management function component. The method includes: receiving, by the NF repository management function component, an NF discovery request message that includes an identifier of a set to which the second NF component belongs; determining, by the NF repository management function component based on the identifier of the set to which the second NF component belongs, that a third NF component having a same function as the second NF component exists in the network; and sending, by the NF repository management function component to the first NF component, a first message that includes an identifier of the third NF component.

A method includes receiving a packet. The method further includes determining whether the packet is part of a responsive connection. The method further includes determining whether a responsive buffer is full in response to a determination that the packet is part of the responsive connection. The method further includes applying a responsive probability to the packet in response to a determination that the responsive buffer is full. The method further includes determining whether to drop the packet based on the responsive probability. The method further includes accepting the packet for processing in response to a determination that the responsive buffer is not full or in response to a determination not to drop the packet.

Techniques are provided for load balancing for IP failover. A backend address of a first node is identified as a routing destination to which a request is to be routed by a load balancer based upon a load balancer rule mapping a frontend address, specified by the request as a request destination, to the backend address of the first node. The request is routed to a primary network interface of the first node using the backend address. The first node has a loopback interface with an address matching the frontend address for routing the request to a destination data structure based upon the request maintaining the frontend address as the request destination. Health probes are used by the load balancer for detecting a failure of the first node in order to failover to routing requests to a second backend address of a second node.

One example disclosed method involves a computing system determining that a first shared computing resource, included among a plurality of shared computing resources managed by a controller, is potentially faulty. The system may configure the controller to identify the first shared computing resource with a tag, the tag configured to cause the controller, in response to a client requesting the controller for access to a first application, to assign the first shared computing resource to deliver the first application to the client. The system may instruct the client to request the controller for access to the first application. The system may determine that the first shared computing resource is faulty based on the client being unable to access the first application at a time of application of the tag to the first shared computing resource. The system may take a corrective action with respect to the first shared computing resource.

Aspects of the present disclosure are directed to an automated remediation system that can receive service level objective (SLO) alerts or notifications and, based on the type, take automated remedial actions. The automated remediation system can perform automated responses to various SLO alerts such as latency alerts, error budget alerts, burn rate alerts, etc. The automated remediation system can utilize a mapping to select which automated response to perform; can measure the effectiveness of the automated response using a metric defined for the alert type; and, until the issue is resolved or no further actions are mapped to the alert type, can repeat the initial automated response or can take secondary automated responses. The automated remediation system can also report the alert and the remedial actions taken.