Examples described herein include systems and methods for providing dynamic serviceability for a software-defined data center (“SDDC”). An example method can include collecting data-center metrics from a management service that monitors the SDDC, filtering the data-center information based on a predetermined list of metrics provided by a partner entity, and translating the filtered data-center information into a partner-specific format requested by the partner entity. The example method can also include generating metadata associated with the translated data-center information and transmitting the metadata and translated data-center information to a partner site associated with the partner entity. If the partner site is not available, the method can include transmitting the information to a partner-accessible storage location and, when the partner site becomes available, identifying the storage location and failed attempt to deliver the information.

Examples described herein include systems and methods for providing dynamic serviceability for a software-defined data center (“SDDC”). An example method can include collecting data-center metrics from a management service that monitors the SDDC, filtering the data-center information based on a predetermined list of metrics provided by a partner entity, and translating the filtered data-center information into a partner-specific format requested by the partner entity. The example method can also include generating metadata associated with the translated data-center information and transmitting the metadata and translated data-center information to a partner site associated with the partner entity. If the partner site is not available, the method can include transmitting the information to a partner-accessible storage location and, when the partner site becomes available, identifying the storage location and failed attempt to deliver the information.

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.

A fault recovery method and apparatus, and a storage medium are provided, and belong to the field of Internet technologies. In the method, network composition information and abnormal event information of a target network are obtained, where the network composition information includes a network topology of the target network and device information of a plurality of network devices on the target network, and the device information includes one or more of interface configuration information, protocol configuration information, and service configuration information; and then a possible root cause of a fault of the target network is determined based on the network composition information and the abnormal event information, where the possible root cause of the fault is used to determine a corresponding fault recovery plan.

A fault recovery method and apparatus, and a storage medium are provided, and belong to the field of Internet technologies. In the method, network composition information and abnormal event information of a target network are obtained, where the network composition information includes a network topology of the target network and device information of a plurality of network devices on the target network, and the device information includes one or more of interface configuration information, protocol configuration information, and service configuration information; and then a possible root cause of a fault of the target network is determined based on the network composition information and the abnormal event information, where the possible root cause of the fault is used to determine a corresponding fault recovery plan.

A method of managing a controller of a software defined networking (SDN) network is implemented by a computing device in the SDN network. The method includes receiving status information for the controller, receiving usage information for the operating environment, generating at least one failure prediction for the controller based on the received status information, and outputting prediction information for the at least one failure prediction.

A computer system is configured to perform a reconciliation process with respect to a current state of a cloud service and a goal state of the cloud service. Performing the reconciliation process includes obtaining the current state of the cloud service, obtaining the goal state of the cloud service, evaluating the current state against the goal state to generate a reconciliation plan that comprises a plurality of operations, and starting execution of the reconciliation plan at the cloud service including performing at least one of the plurality of operations in the reconciliation plan. In response to detecting an event, the computer system reperforms the reconciliation process again such that one or more current state, the goal state, or the reconciliation plan changes.

A computer system is configured to perform a reconciliation process with respect to a current state of a cloud service and a goal state of the cloud service. Performing the reconciliation process includes obtaining the current state of the cloud service, obtaining the goal state of the cloud service, evaluating the current state against the goal state to generate a reconciliation plan that comprises a plurality of operations, and starting execution of the reconciliation plan at the cloud service including performing at least one of the plurality of operations in the reconciliation plan. In response to detecting an event, the computer system reperforms the reconciliation process again such that one or more current state, the goal state, or the reconciliation plan changes.

A troubleshooting method, a device, and a readable storage medium are provided, to detect a unidirectional fault in a ring Ethernet and provide a fault recovery mechanism after the unidirectional fault occurs. In embodiments of this application, if determining that a link corresponding to a receiving unit of a first port is in a fault status, the first device performs loopback on the first port, and sends a first continuity check message to a second device via the first port. The first continuity check message carries first indication information. The first indication information indicates that a link corresponding to a receiving unit of a port that sends the first indication information is in a fault status.