Systems and methods of disconnecting a network service provided over a network service path include using a computing device that obtains a service identifier assigned to network service and identifies a port of a network device included in a network service path associated with the service. The computing device transmits a request to the network device for port configuration data of the network device and based on the received port configuration data, determines whether the port is assigned to the network service. If so, the computing devices executes a remediation operation which includes transmitting a reconfiguration command to the network device that is adapted to cause the network device to update the port configuration data to free the port.

It is provided a communication device which transfers a signal, comprising: an arithmetic device configured to execute predetermined processing; a storage device accessible from the arithmetic device; a log collection module configured to collect first type logs from at least one of the communication device or an equipment coupled to the communication device; an alert generation module configured to generate alert when one of the collected the first type logs satisfies a predetermined condition; and a failure cause candidate determination module configured to determine failure cause candidates in response to the generated alert, and output, to the log collection module, an additional log collection request for collecting second type logs in an additional log collection order that is set based on the determined failure cause candidates.

Methods, systems, and devices are provided herein for a mechanism to identify link down reasons. As described herein, a first port of a first peer device may be determined to have unexpectedly changed to a port down state. Subsequently, a topology file may be referenced to identify a second port of a second peer device with which the first peer device is intended to have a link if not for the first port being in a port down state. In some examples, port settings of the first port may be compared with port settings of the second port. If a port setting for the first port mismatches an associated port setting for the second port, an alert message may be transmitted to a network administrator indicating this mismatch as a possible reason for the first port being in the port down state.

Methods, systems, and devices are provided herein for a mechanism to identify link down reasons. As described herein, a first port of a first peer device may be determined to have unexpectedly changed to a port down state. Subsequently, a topology file may be referenced to identify a second port of a second peer device with which the first peer device is intended to have a link if not for the first port being in a port down state. In some examples, port settings of the first port may be compared with port settings of the second port. If a port setting for the first port mismatches an associated port setting for the second port, an alert message may be transmitted to a network administrator indicating this mismatch as a possible reason for the first port being in the port down state.

To improve the reliability of nodes that are utilized by a cloud computing provider, information about the entire lifecycle of nodes can be collected and used to predict when nodes are likely to experience failures based at least in part on early lifecycle errors. In one aspect, a plurality of failure issues experienced by a plurality of production nodes in a cloud computing system during a pre-production phase can be identified. A subset of the plurality of failure issues can be selected based at least in part on correlation with service outages for the plurality of production nodes during a production phase. A comparison can be performed between the subset of the plurality of failure issues and a set of failure issues experienced by a pre-production node during the pre-production phase. A risk score for the pre-production node can be calculated based at least in part on the comparison.

To improve the reliability of nodes that are utilized by a cloud computing provider, information about the entire lifecycle of nodes can be collected and used to predict when nodes are likely to experience failures based at least in part on early lifecycle errors. In one aspect, a plurality of failure issues experienced by a plurality of production nodes in a cloud computing system during a pre-production phase can be identified. A subset of the plurality of failure issues can be selected based at least in part on correlation with service outages for the plurality of production nodes during a production phase. A comparison can be performed between the subset of the plurality of failure issues and a set of failure issues experienced by a pre-production node during the pre-production phase. A risk score for the pre-production node can be calculated based at least in part on the comparison.

Aspects of the present disclosure include methods, apparatuses, and computer readable media for radio link failure recovery and beam failure recovery on a secondary cell group (SCG) in dormancy state. In an example, a user equipment (UE) may determine the UE has entered a dormant state with respect to the SCG of a secondary node (SN) having a primary SCG cell (PSCell). The UE may monitor the PSCell to detect a beam failure or a radio link failure while the UE is in the dormant state with respect to the SCG. The UE may transmit, to the SN, a report based on the beam failure or the radio link failure on the PSCell being detected.

Aspects of the present disclosure include methods, apparatuses, and computer readable media for radio link failure recovery and beam failure recovery on a secondary cell group (SCG) in dormancy state. In an example, a user equipment (UE) may determine the UE has entered a dormant state with respect to the SCG of a secondary node (SN) having a primary SCG cell (PSCell). The UE may monitor the PSCell to detect a beam failure or a radio link failure while the UE is in the dormant state with respect to the SCG. The UE may transmit, to the SN, a report based on the beam failure or the radio link failure on the PSCell being detected.

During operation, an electronic device may store, in memory, information associated with operation of the electronic device, such as during communication and processing of one or more packets or frames. Furthermore, an error-event monitor in the electronic device may, during a time interval, analyze at least a portion of the stored information to detect an occurrence of an error event in one or more types of error events in the electronic device. When the error event occurs during the time interval, the electronic device may perform a remedial action and may persist, in the memory, at least a second portion of the stored information associated with the error event. Otherwise, when the error event does not occur during the time interval, the electronic device may overwrite, in the memory, the stored information with additional information associated with operation of the electronic device during subsequent communicating and processing.

A system and method for recovering application authentication with an application server by using an exponential back-off procedure via push notifications is discussed herein. The system allows for authentication of a user account after network outages or service disruptions without traffic overload during recovery. A user equipment (UE) receives a failed registration notification after a failed registration attempt of the user account with an application server associated with the application. A push notification includes an instruction that causes the application to switch from an inactive state to a temporary active state. The push notification is sent from a push notification service in response to a push request from a notification server based on a recovery request from the UE due to the failed registration notification. While the application is in the temporary active state, the instruction further causes the application to request registration with the application server.