A system for efficient routing of an (OAM) frame in an Ethernet switch receives an OAM frame at a first port; building a first classification key dependent on an OAM frame header; classifies in a context of the first port to create a first classification; resolves action dependent on the first classification; modifies the first classification key to create a second classification key; classifies the frame in a context of the second port to create a second classification; sends the second classification key to an OAM engine coupled to the Ethernet switch for modification into a third classification key; receives the third classification key from the OAM engine; modifies the third classification key into a final classification key; modifies the header of the OAM frame with the final classification key; and sends the modified OAM frame to a switching fabric of the Ethernet switch.

A system for efficient routing of an (OAM) frame in an Ethernet switch receives an OAM frame at a first port; building a first classification key dependent on an OAM frame header; classifies in a context of the first port to create a first classification; resolves action dependent on the first classification; modifies the first classification key to create a second classification key; classifies the frame in a context of the second port to create a second classification; sends the second classification key to an OAM engine coupled to the Ethernet switch for modification into a third classification key; receives the third classification key from the OAM engine; modifies the third classification key into a final classification key; modifies the header of the OAM frame with the final classification key; and sends the modified OAM frame to a switching fabric of the Ethernet switch.

Methods, systems, and devices for communications are described. One or more flows between a node and one or more other nodes in a communication network may be monitored over a time period. During the monitoring, it may be identified that, during a subset of the time period, communications over at least one of the flows were restricted by the communication network based on receiving at least one indicator of congestion for the at least one flow. A quantity of traffic communicated over the one or more flows during the subset of the time period may then be determined, and respective flow rates of the one or more flows may be obtained. The obtained flow rates may be used to calculate a data rate of one or more connections between the node and the one or more other nodes.

Methods, systems, and devices for communications are described. One or more flows between a node and one or more other nodes in a communication network may be monitored over a time period. During the monitoring, it may be identified that, during a subset of the time period, communications over at least one of the flows were restricted by the communication network based on receiving at least one indicator of congestion for the at least one flow. A quantity of traffic communicated over the one or more flows during the subset of the time period may then be determined, and respective flow rates of the one or more flows may be obtained. The obtained flow rates may be used to calculate a data rate of one or more connections between the node and the one or more other nodes.

Various data bus monitoring, analysis, and logging systems, devices, and methods are described herein. In one example, an apparatus includes a first circuit configured to monitor first packets among traffic carried by one or more first directional lanes of a communication link established between a host and one or more endpoint devices and determine header information for the first packets. The apparatus includes a second circuit configured to detect second packets among traffic carried by one or more second directional lanes of the communication link based at least in part on the header information determined for the first packets. The apparatus includes an analysis element configured to establish transaction metadata comprising properties of transactions on the communication link based at least on correlations among the first packets and the second packets.

Various data bus monitoring, analysis, and logging systems, devices, and methods are described herein. In one example, an apparatus includes a first circuit configured to monitor first packets among traffic carried by one or more first directional lanes of a communication link established between a host and one or more endpoint devices and determine header information for the first packets. The apparatus includes a second circuit configured to detect second packets among traffic carried by one or more second directional lanes of the communication link based at least in part on the header information determined for the first packets. The apparatus includes an analysis element configured to establish transaction metadata comprising properties of transactions on the communication link based at least on correlations among the first packets and the second packets.

There is described a method for determining a play duration estimate of an adaptive bit rate (ABR) media presentation. The method comprises receiving at a network entity a media playlist manifest file of the media presentation, wherein the manifest file is transmitted from a content server to a client and comprises a plurality of entries, each entry linking to a respective different one of a plurality of media segments of the media presentation. The method further comprises determining a data size of the manifest file; and determining a play duration estimate of the media presentation based on the determined data size of the manifest file, a first value that represents a data size of each of the plurality of entries in the manifest file and a second value that represents a play duration of each media segment of the plurality of media segments of the media presentation.

The disclosed apparatus, systems and methods relate a failover and internet connection monitoring system featuring a cloud server running an API, a probe, a firewall and a policy routing system. The failover connection monitoring system is capable of gathering and analyzing performance data and controlling the flow of packets to and from the internet over one or more connections to optimize performance of the network.

In general, techniques described are for bandwidth sharing between resource reservation protocol label switched paths (LSPs) and non-resource reservation protocol LSPs. For example, in networks where resource reservation protocol LSPs and non-resource reservation protocol LSPs co-exist within the same domain, resource reservation protocol LSPs and non-resource reservation protocol LSPs may share link bandwidth. However, when non-resource reservation protocol LSPs are provisioned, resource reservation protocol path computation elements computing resource reservation protocol paths may not account for non-resource reservation protocol LSP bandwidth utilization. The techniques described herein provide a mechanism for automatically updating traffic engineering database (TED) information about resource reservation protocol LSPs in a way that accounts for non-resource reservation protocol LSP traffic flow statistics, such as bandwidth utilization. Path computation elements may thus rely on an accurate TED for LSP path computation.

An output circuit, included in a device, may determine counter information associated with a packet provided via an output queue managed by the output circuit. The output circuit may determine that a latency event, associated with the output queue, has occurred. The output circuit may provide the counter information and time of day information associated with the counter information. The output circuit may provide a latency event notification associated with the output queue. An input circuit, included in the device, may receive the latency event notification associated with the output queue. The input circuit may determine performance information associated with an input queue. The input queue may correspond to the output queue and may be managed by the input circuit. The input circuit may provide the performance information associated with the input queue and time of day information associated with the performance information.