Abstract: The network management system (NMS) assesses behavior data such as Ethernet error, speed flapping, cold restart, and/or cloud disconnect collected from a respective one of access points (APs) or other wired client-side devices at an edge of a wired network, and determines whether features of the behavior data are indicative of a bad cable issue at a particular port of a particular network device of the wired network to which the respective AP is connected via a cable. The particular network device may be a third-party network device from which the NMS does not receive behavior data. In the case of a bad cable issue being detected, the NMS outputs a bad cable notification including identification information of the particular port and the particular network device. The NMS enables client-side only, behavior-based bad cable detection at network devices that avoids network traffic disruptions caused by conventional cable tests.

Abstract: A network management system (NMS) is described that includes one or more processors coupled to memory storing network data. The one or more processors are configured to receive a query identifying a site and determine, based on the network data, a first set of troubleshooting issues for a wide area network (WAN) deployment at the site, a second set of troubleshooting issues for a wireless deployment at the site, and a third set of troubleshooting issues for a wired deployment at the site. The one or more processors are configured to determine, based on a user experience metric, a first troubleshooting issue from the first set of troubleshooting issues for the WAN deployment, a second troubleshooting issue from the second set of troubleshooting issues for the wireless deployment, and a third troubleshooting issue from the third set of troubleshooting issues for the wired deployment.

Abstract: A network management system (NMS) is described that provides a granular troubleshooting workflow at an application session level using an application session-specific topology from a client device to a cloud-based application server. During an application session of a cloud-based application, a client device running the application exchanges data through one or more access point (AP) devices, one or more switches at a wired network edge, and one or more network nodes, e.g., switches, routers, and/or gateway devices, to reach a cloud-based application server. For a particular application session, the NMS generates a topology based on network data received from a subset of network devices, e.g., client devices, AP devices, switches, routers, and/or gateways, that were involved in the particular application session over a duration of the particular application session. In this way, the NMS enables backward-looking troubleshooting of the particular application session.

Abstract: A network management system (NMS) is described that provides a granular troubleshooting workflow at an application session level using an application session-specific topology from a client device to a cloud-based application server. During an application session of a cloud-based application, a client device running the application exchanges data through one or more access point (AP) devices, one or more switches at a wired network edge, and one or more network nodes, e.g., switches, routers, and/or gateway devices, to reach a cloud-based application server. For a particular application session, the NMS generates a topology based on network data received from a subset of network devices, e.g., client devices, AP devices, switches, routers, and/or gateways, that were involved in the particular application session over a duration of the particular application session. In this way, the NMS enables backward-looking troubleshooting of the particular application session.

Abstract: Techniques are described by which a network management system (NMS) is configured to provide identification of root cause failure through the detection of network scope failures. For example, the NMS comprises one or more processors; and a memory comprising instructions that when executed by the one or more processors cause the one or more processors to: generate a hierarchical attribution graph comprising attributes representing different network scopes at different hierarchical levels; receive network event data, wherein the network event data is indicative of operational behavior of the network, including one or more of successful events or one or more failure events associated with one or more client devices; and apply a machine learning model to the network event data and to a particular network scope in the hierarchical attribution graph to detect whether the particular network scope has failure.

Abstract: Techniques are described by which a network management system (NMS) is configured to provide identification of root cause failure through the detection of network scope failures. For example, the NMS comprises one or more processors; and a memory comprising instructions that when executed by the one or more processors cause the one or more processors to: generate a hierarchical attribution graph comprising attributes representing different network scopes at different hierarchical levels; receive network event data, wherein the network event data is indicative of operational behavior of the network, including one or more of successful events or one or more failure events associated with one or more client devices; and apply a machine learning model to the network event data and to a particular network scope in the hierarchical attribution graph to detect whether the particular network scope has failure.

Abstract: A network management system (NMS) initiates, for each of a plurality of wireless and/or wired client devices, a wireless/wired stateful machine configured to continuously monitor at least one pre-connection state and at least one post-connection state of a corresponding wireless/wired connection session, and determines one or more network connection assessments for the plurality of wireless/wired client devices based on success or failure of the pre-connection states and/or the post-connection states. The NMS may also output a notification including identification of a root cause of any network connection failure(s) and/or automatically invoke remedial action intended to address or mitigate the root cause of the network connection failure(s).

Abstract: A network management system (NMS) is described that provides a granular troubleshooting workflow at an application session level using an application session-specific topology from a client device to a cloud-based application server. During an application session of a cloud-based application, a client device running the application exchanges data through one or more access point (AP) devices, one or more switches at a wired network edge, and one or more network nodes, e.g., switches, routers, and/or gateway devices, to reach a cloud-based application server. For a particular application session, the NMS generates a topology based on network data received from a subset of network devices, e.g., client devices, AP devices, switches, routers, and/or gateways, that were involved in the particular application session over a duration of the particular application session. In this way, the NMS enables backward-looking troubleshooting of the particular application session.

Abstract: This disclosure describes a system including a plurality of access point (AP) devices configured to provide a wireless network at a site; and a network management system (NMS) including a memory storing AP-side data collected by the plurality of AP devices and storing client-side data collected by a plurality of client devices connected to one or more of the AP devices to access the wireless network. The NMS is configured to correlate the client-side data for a particular client device of the plurality of client devices with a device identifier of the particular client device; associate, based on the device identifier, the client-side data for the particular client device and the AP-side data for the particular client device; analyze the client-side data and the associated AP-side data for the particular client device to detect a wireless issue; and output a notification including an indication of the wireless issue.

Abstract: Techniques are described by which a network management system (NMS) is configured to provide identification of root cause failure through the detection of network scope failures. For example, the NMS comprises one or more processors; and a memory comprising instructions that when executed by the one or more processors cause the one or more processors to: generate a hierarchical attribution graph comprising attributes representing different network scopes at different hierarchical levels; receive network event data, wherein the network event data is indicative of operational behavior of the network, including one or more of successful events or one or more failure events associated with one or more client devices; and apply a machine learning model to the network event data and to a particular network scope in the hierarchical attribution graph to detect whether the particular network scope has failure.

Abstract: In an embodiment, a drug delivery system and method of use thereof to treat inflammation and bacterial pathogens including multi-drug resistant pathogens, such as MDR-Pseudomonas aeruginosa, or reactive oxygen species in a subject is provided. In some embodiments, the drug delivery system includes a polymeric material, an excepient, an antioxidant agent, and an anti-inflammatory and antimicrobial agent. In some embodiments, the anti-inflammatory and antimicrobial agent is a salt of an anti-inflammatory agent and an antimicrobial agent formulated to provide a combination of antimicrobial and anti-inflammatory action from a single molecule. In some embodiments, the combined anti-inflammatory and antimicrobial agent is a silver salt of ibuprofen. In other embodiments, the combined anti-inflammatory and antimicrobial agent is unmodified, native ibuprofen.

Abstract: In one aspect, the present disclosure provides diaryl compounds of the formula presented herein. The application also provides compositions and methods of treatment thereof. In some embodiments, these compounds are used in the treatment of bacterial infections or in the treatment of cancer.

Abstract: In one aspect, lubricant compositions are described herein. In some embodiments, a lubricant composition described herein comprises a grease and milled metal sulfide particles dispersed in the grease. In other cases, a lubricant composition described herein comprises a grease, polytetrafluroethylene particles, zinc dithiophosphate, and molybdenum dialkyldithiocarbamate, wherein the polytetrafluroethylene particles, zinc dithiophosphate, and molybdenum dialkyldithiocarbamate are dispersed in the grease.

Abstract: In one aspect, lubricant compositions are described herein. In some embodiments, a lubricant composition described herein comprises a grease and milled metal sulfide particles dispersed in the grease. In other cases, a lubricant composition described herein comprises a grease, polytetrafluroethylene particles, zinc dithiophosphate, and molybdenum dialkylthiocarbamate, wherein the polytetrafluroethylene particles, zinc dithiophosphate, and molybdenum dialkyldithiocarbamate are dispersed in the grease.