A failure notification system includes a logical configuration provider which provides logical configurations in which a plurality of types of hardware are virtualized, a processor using logical configurations provided from the logical configuration provider, and a failure notifier which notifies the processor 3 of a failure in the logical configuration provider. A notifier includes a storage device 10 which stores hardware configuration data in which an ID of the hardware is associated with an ID of a logical configuration corresponding to the hardware, a logical configuration identifier which identifies a logical configuration corresponding to hardware from which a failure is detected from the hardware configuration data when a failure in the hardware is detected, and a notifier which notifies the processor of occurrence of a failure in the logical configuration identified by the logical configuration identifier.

Novel tools and techniques are provided for implementing error detection in a network, and, more particularly, to methods, systems, and apparatuses for implementing error and/or fault detection in a network and/or media stream and providing options to address the error and/or fault in the network and/or media stream. In various embodiments, a computer might detect an error in a first network and send a notification indicating that the error has occurred. The notification might contain one or more options to address the error in the first network. The computer, a user device, a service provider device, or a content provider device might receive and display the notification containing the one or more options. The computer, the user device, the service provider device, or the content provider device might then select at least one of the one or more options to address the error in the first network.

A system comprising a network cloud configured for a point of deployment containerized environment, a plurality of servers in communication with the network cloud, configured to establishing a point of deployment (POD) in one of the plurality of servers, receiving a determination that the POD is not operational, mapping the topology of the POD, and based on the mapping step, troubleshooting the POD in accordance with a set of rules.

A method for monitoring and rebooting a node of a wireless communications network is disclosed. The method includes acquiring an incident indication for a node site indicative of a performance drop. The method further includes analyzing the incident indication to identify at least one key term. The method further includes accessing a set of prior incidents having a prior incident indication including the key term. The method further includes providing a recommendation to a user device based at least in part on the prior incident indication that includes a site reset for the node site. The method further includes acquiring a resolution indication following the site reset. The method further includes logging the resolution indication as a prior incident indication in the set of prior incidents.

Disclosed embodiments are directed at systems, methods, and architecture for operating a control plan of a microservices application. The control plane corresponds with data plane proxies associated with each of a plurality of APIs that make up the microservices application. The communication between the data plane proxies and the control plane enables automatic detection of service groups of APIs and automatic repair of application performance in real-time in response to degrading service node conditions.

In general, embodiments of the invention relate to a method and system for enabling a peer state synchronization mechanism for dynamic network address translation (DNAT). More specifically, at least two network elements may be permitted to mount each other's DNAT tables, thereby providing redundancy for the implementation of DNATs in case of the failover of one of the network elements. The failed network element may then re-initialize while the functional network element continues to process packets, including packets that have been redirected to the functional network element post-failure of the failed network element. Upon completing re-initialization, the once failed network element recovers its DNAT table from the functional network element and proceeds to process packets normally.

An improved core network that includes a network resilience system that can detect network function virtualization (NFV)-implemented nodes that have been compromised and/or that are no longer operational, remove such nodes from the virtual network environment, and restart the removed nodes in a last-known good state is described herein. For example, the network resilience system can use health status messages provided by nodes, intrusion data provided by intrusion detection agents running on nodes, and/or operational data provided by the nodes as applied to machine learning models to identify nodes that may be compromised and/or non-operational. Once identified, the network resilience system can delete these nodes and restart or restore the nodes using the last-known good state.

Various embodiments are generally directed to techniques for dynamic network resiliency, such as by monitoring and controlling the configuration of one or more network components to ensure proper endpoint alignment, for instance. Some embodiments are particularly directed to a tool (e.g., resiliency agent) that can automatically recognize symptoms of issues with a network component, such as autoscaling, latency, traffic spikes, resource utilization spikes, etcetera, and respond appropriately to ensure continued and optimized operation of the network component. In many embodiments, the tool may dynamically reroute endpoint traffic, perform traffic balancing, and/or drive autoscaling to optimize operation of the network component in response to recognizing symptoms.

A method is provided in which a call agent process that supports one or more Internet Protocol (IP) calls, stores to persistent memory a set of data associated with the one or more IP calls. An outage is detected affecting the one or more IP calls. Using the data retrieved from the persistent memory, the one or more IP calls are resynthesized using a device simulator process to simulate connectivity with endpoints that were participating in the one or more IP calls prior to the outage. After resynthesizing, depending on activity detected from devices associated with the one or more IP calls, the one or more IP calls are internally re-stitched/re-establishing (without signaling to endpoints) with the endpoints involved in the one or more IP calls, or the one or more calls are fully re-stitched/re-established by signaling an endpoint that was participating in the one or more IP calls.

Systems and methods are disclosed for providing redundancy in a network node implementing a ring protection protocol. Each of the two ring ports connecting the node to other nodes in a ring supporting the protocol may be maintained by a separate line card. Should one line card fail, traffic passing through the node may be redirected through the remaining ring port under the control of the surviving state machine. The two state machines may be coordinated over the backplane of the node to maintain a common state, making them transparent to other nodes. Additionally, the backplane link between the state machines may be monitored for failures that may be addressed with messages used to respond to general ring failures and by assigning one state machine to block a ring port upon recovery to prevent a loop within the ring until the ring protection link can be blocked.