Abstract: Presented herein are systems, and methods thereof, that is configured to enter a maintenance mode to isolate itself from its neighbor and to gracefully cause neighbor devices to isolate themselves from the system, as to cause minimal or “zero” service disruption with its neighbors. The system broadcasts a maintenance-related message, via a standard transport layer, over routing protocols, to counter parts protocols at the neighbor device and waits for an acknowledgement message from the neighbor network devices. The broadcast and acknowledgement, through standard transport layer messaging, ensures that traffic generated by such protocols at the neighbor devices, regardless of manufacturer, are redirected before the system fully enters into the maintenance mode.

Abstract: Embodiments herein describe an upgrade system that provides suggestions for upgrades using a confidence metric. In one embodiment, the upgrade system tracks network elements in multiple network fabrics to determine whether an upgrade performed on a first network element was successful. The upgrade system can generate one or more vectors that store various data about the network elements such as enabled features, telemetry data, control plane faults, system settings, locations of the network elements in a fabric, and the like. By evaluating these vectors, the upgrade system can derive a reliability confidence metric regarding the upgrade. If the reliability confidence metric exceeds a threshold, this indicates the upgrade was successful. The upgrade system can then compare vectors for different network elements to determine whether to apply the same upgrade to similar network elements.

Abstract: Methods and systems are provided for link health forecasting to determine potential link failures such that remedial action may be taken prior to any data loss or degradation. DDM/DOM information may be used in conjunction with OAM protocols to monitor and predict link health degradation for faster failovers or self healing.

Abstract: Methods and systems for tracking transactions in a network fabric, include: receiving a message generated by a node in the network fabric; assigning a uniform fabric identifier (“UFID”) to the node; assigning a uniform transaction identifier (“UTID”) to the message”; appending the UFID and the UTID to the message; and storing the message in a database.

Abstract: Presented herein are systems, and methods thereof, that is configured to enter a maintenance mode to isolate itself from its neighbor and to gracefully cause neighbor devices to isolate themselves from the system, as to cause minimal or “zero” service disruption with its neighbors. The system broadcasts a maintenance-related message, via a standard transport layer, over routing protocols, to counter parts protocols at the neighbor device and waits for an acknowledgement message from the neighbor network devices. The broadcast and acknowledgement, through standard transport layer messaging, ensures that traffic generated by such protocols at the neighbor devices, regardless of manufacturer, are redirected before the system fully enters into the maintenance mode.

Abstract: Presented herein are systems, and methods thereof, that is configured to enter a maintenance mode to isolate itself from its neighbor and to gracefully cause neighbor devices to isolate themselves from the system, as to cause minimal or “zero” service disruption with its neighbors. The system broadcasts a maintenance-related message, via a standard transport layer, over routing protocols, to counter parts protocols at the neighbor device and waits for an acknowledgement message from the neighbor network devices. The broadcast and acknowledgement, through standard transport layer messaging, ensures that traffic generated by such protocols at the neighbor devices, regardless of manufacturer, are redirected before the system fully enters into the maintenance mode.

Abstract: Embodiments herein describe an upgrade system that provides suggestions for upgrades using a confidence metric. In one embodiment, the upgrade system tracks network elements in multiple network fabrics to determine whether an upgrade performed on a first network element was successful. The upgrade system can generate one or more vectors that store various data about the network elements such as enabled features, telemetry data, control plane faults, system settings, locations of the network elements in a fabric, and the like. By evaluating these vectors, the upgrade system can derive a reliability confidence metric regarding the upgrade. If the reliability confidence metric exceeds a threshold, this indicates the upgrade was successful. The upgrade system can then compare vectors for different network elements to determine whether to apply the same upgrade to similar network elements.

Abstract: Control plane analytics and policing may be provided. First, packets that traverse a port may be parsed. Next, based on the parsed packets, metrics for each of a plurality of hosts on a per-protocol basis may be created. The created metrics may then be analyzed and at least one restriction on at least one of the plurality of hosts may be applied based on the analysis.

Abstract: Methods and systems are provided for link health forecasting to determine potential link failures such that remedial action may be taken prior to any data loss or degradation. DDM/DOM information may be used in conjunction with OAM protocols to monitor and predict link health degradation for faster failovers or self healing.

Abstract: Presented herein are systems, and methods thereof, that is configured to enter a maintenance mode to isolate itself from its neighbor and to gracefully cause neighbor devices to isolate themselves from the system, as to cause minimal or “zero” service disruption with its neighbors. The system broadcasts a maintenance-related message, via a standard transport layer, over routing protocols, to counter parts protocols at the neighbor device and waits for an acknowledgement message from the neighbor network devices. The broadcast and acknowledgement, through standard transport layer messaging, ensures that traffic generated by such protocols at the neighbor devices, regardless of manufacturer, are redirected before the system fully enters into the maintenance mode.

Abstract: Methods and systems for configuring a local switch and a remote switch configured as peers. The method includes: receiving a configuration for configuring the local switch and the remote switch; checking if resources are available for the configuration on the local switch; when resources are available on the local switch, reserving those resources; checking if resources are available for the configuration of the remote switch; when resources are available on the remote switch, reserving those resources; and applying the configuration to the local switch and the remote switch when resources are available on the local switch and the remote switch.

Abstract: In one example, a security application that interfaces one or more cloud application clients in an enterprise network and one or more cloud applications detects a request made by one of the one or more cloud application clients to access a cloud application. The security application sends one or more prompts to the cloud application for one or more responses reflecting current empirical data obtained from the cloud application. The security application receives, from the cloud application, the one or more responses, and generates an application fingerprint that includes the one or more responses.

Abstract: Presented herein are systems, and methods thereof, that is configured to enter a maintenance mode to isolate itself from its neighbor and to gracefully cause neighbor devices to isolate themselves from the system, as to cause minimal or “zero” service disruption with its neighbors. The system broadcasts a maintenance-related message, via a standard transport layer, over routing protocols, to counter parts protocols at the neighbor device and waits for an acknowledgement message from the neighbor network devices. The broadcast and acknowledgement, through standard transport layer messaging, ensures that traffic generated by such protocols at the neighbor devices, regardless of manufacturer, are redirected before the system fully enters into the maintenance mode.

Abstract: Methods and systems are provided for link health forecasting to determine potential link failures such that remedial action may be taken prior to any data loss or degradation. DDM/DOM information may be used in conjunction with OAM protocols to monitor and predict link health degradation for faster failovers or self healing.

Abstract: Techniques are provided for correcting the operational state of a multi-process system without disrupting any running processes. A library providing error correction and logging functionality is statically linked to modules in the system. A script in the library loads a package file having a patch for returning an error state to a normal state. The script issues commands to invoke functions in the patch. Once the error state has returned to a normal state, the script issues commands to remove the package file from the system.

Abstract: An example method for diagnosis and throughput measurement of FC ports in a SAN environment is provided and includes generating, by a control processor at a generator in the SAN, a control packet requesting a link test to be performed with a reflector in the SAN, sending the control packet to the reflector through a media access controller (MAC) of the generator, receiving, at the MAC of the generator, an acknowledgement from the reflector indicating ability to perform the requested link test, generating, at the MAC of the generator, a test data packet for the link test, performing the link test with the reflector, and analyzing, at the generator, network parameters based on results of the link test.

Abstract: Control plane analytics and policing may be provided. First, packets that traverse a port may be parsed. Next, based on the parsed packets, metrics for each of a plurality of hosts on a per-protocol basis may be created. The created metrics may then be analyzed and at least one restriction on at least one of the plurality of hosts may be applied based on the analysis.

Abstract: Methods and systems for tracking transactions in a network fabric, include: receiving a message generated by a node in the network fabric; assigning a uniform fabric identifier (“UFID”) to the node; assigning a uniform transaction identifier (“UTID”) to the message”; appending the UFID and the UTID to the message; and storing the message in a database.

Abstract: In one example, a security application that interfaces one or more cloud application clients in an enterprise network and one or more cloud applications detects a request made by one of the one or more cloud application clients to access a cloud application. The security application sends one or more prompts to the cloud application for one or more responses reflecting current empirical data obtained from the cloud application. The security application receives, from the cloud application, the one or more responses, and generates an application fingerprint that includes the one or more responses.

Abstract: Methods and systems for configuring a local switch and a remote switch configured as peers. The method includes: receiving a configuration for configuring the local switch and the remote switch; checking if resources are available for the configuration on the local switch; when resources are available on the local switch, reserving those resources; checking if resources are available for the configuration of the remote switch; when resources are available on the remote switch, reserving those resources; and applying the configuration to the local switch and the remote switch when resources are available on the local switch and the remote switch.