In an embodiment, the application provides a flexible Ethernet (FlexE) communication method, which includes: receiving, by a first network device by using a FlexE group, n first overhead blocks sent by a second network device, the FlexE group comprising n physical layer apparatuses (PHYs); and storing, by the first network device, the n first overhead blocks in n memories in the first time period. The method further includes simultaneously reading, by the first network device, the n first overhead blocks from the n memories, after a preset duration T starting from a moment at which a first overhead block is stored in a corresponding memory. The first overhead block is a last stored first overhead block in the n first overhead blocks, the duration T is greater than or equal to one clock cycle.

An example operation may include a system, comprising one or more of receiving a virtual network function component instance (VNFCI) status notification resumption message with an active state when a peer VNFCI operational state is active, retrieving a timestamp of a VNFCI state change to an active state from an element VNFCI state database, retrieving a timestamp of a peer VNFCI state change to active from an element VNFCI state database, sending one or more of: a request to a virtual network function manager (VNFM) to determine if the VNFCI network is isolating while an operating state was active, and a request to the VNFM to determine if the peer VNFCI network is isolating while an operating state was active, sending a state change request with standby state to the peer VNFCI when the VNFCI is not network isolated and the peer VNFCI is network isolated, and a VNFM response is received regarding the VNFCI, a timeout response from the VNFM, and a VNFM response is received regarding the peer VNFCI, and sending a state change request with standby to the VNFCI with one or more of: the VNFCI network isolate and peer VNFCI is not network isolated, and the VNFCI is network isolated or the peer VNFCI is not network isolated, and the VNFCI is not network isolated and the peer VNFCI is network isolated and the VNFCI is in preferred standby.

This application provides an isolation and recovery method and related network device for a case when one or more physical layer apparatuses (PHYs) in a flexible Ethernet group (FlexE group) are faulty. In the method, if a network device determines that a first overhead block corresponding to each current available PHY is stored in a corresponding memory, the network device determines that a FlexE group meets a PHY alignment condition, and starts to simultaneously read cached data from all memories. Therefore, there is no need to insert local fault LF code blocks to all clients, and there is no need to recreate a group. This effectively reduces the impact of a faulty PHY on client services carried by a normal PHY.

A vehicle transmission includes a shaft; speed-changing gears; switching mechanisms; and a shifting mechanism. The shifting mechanism is provided with a double-meshing preventing mechanism configured to switch between a one-way state in which the switching mechanisms are hindered from moving in a downshift direction and allowed to move in an upshift direction and a free state in which the switching mechanisms are allowed to move in both the downshift direction and the upshift direction.

A method for providing data relating to at least one user device to a data analysis entity. The method includes: collecting, for a plurality of events having impacted on at least one state of the user device in the network, data relating to the at least one impacted state; and supplying, to the data analysis entity, for at least one such state of the user device, at least one statistic obtained for this state by aggregating data relating to this state collected during the collecting step and a part of the data corresponding to an integer X greater than or equal to 1 of events among the most recent events of the plurality of events.

An embodiment may involve: (i) obtaining a set of data records that include respective pluralities of tuples characterizing operation of communication sessions in a network and that identify hardware or software components related to the network that were involved in the communication sessions, (ii) determining degrees to which signatures in the pluralities of tuples are associated with communication problems in the network; (iii) identifying, from the degrees, a subset of the signatures most associated with the communication problems; (iv) grouping specific pairs from the subset of the signatures into equivalence classes based on co-occurrence of signatures of the specific pairs within the data records; (v) generating and pruning a dependency graph between the equivalence classes; (vi) from the equivalence classes remaining in the dependency graph, selecting a subset of the hardware or software components related to the network that are candidates for involvement with the communication problems.

The current document is directed to methods and systems that process, classify, efficiently store, and display large volumes of event messages generated in modern computing systems. In a disclosed implementation, received event messages are assigned to event-message clusters based on non-parameter tokens identified within the event messages. A parsing function is generated for each cluster that is used to extract data from incoming event messages and to prepare event records from event messages that more efficiently and accessible store event information. The parsing functions also provide an alternative basis for assignment of event messages to clusters. Event types associated with the clusters are used for gathering information from various information sources with which to automatically annotate event messages displayed to system administrators, maintenance personnel, and other users of event messages.

The present disclosure describes methods, computer-readable media, and apparatuses supporting management and resolution of alarms of a communication network. In one example, management and resolution may include receiving a new alarm, determining an alarm resolution of the new alarm based on the new alarm and historical alarm information, and initiating an alarm resolution action for resolving the new alarm based on the alarm resolution of the new alarm. In one example, management and resolution may include maintaining historical alarm information for a set of historical alarms, receiving a new alarm, determining a set of similar alarms including one or more of the historical alarms similar to the new alarm, determining an alarm resolution for the new alarm based on the set of similar alarms similar to the new alarm, and initiating an alarm resolution action for resolving the new alarm based on the alarm resolution of the new alarm.

An information handling system includes a network interface device configured to provide indications of faults on the network interface device, a baseboard management controller agent configured to receive the indications, and a baseboard management controller coupled to a management system. The management system mitigates the faults on the network interface device. The network interface device further detects a fault on the network interface device and provides an indication to the baseboard management controller agent in response to detecting the fault. The baseboard management controller agent further receives the indication from the network interface device, receives an identification of the management system from the baseboard management controller, and provides a second indication to the management system based upon the identification.

Pausing alert notifications includes triggering an alert responsive to an event in a managed environment. A normalized title is obtained from a title of the alert. Using the normalized title, it is determined whether the alert is of a likely transient type, where the alert is of the likely transient type when it is predicted to resolve without human intervention. A transmission of notifications for the alert during a pause period is withheld responsive to determining that the alert is the likely transient type. A notification for the alert is transmitted to a responder responsive to determining that the alert is unresolved after the pause period.