Systems and methods for managing network health

Abstract

Implementations described and claimed herein provide systems and methods systems and methods for managing network health, including optimizing a network. In one implementation, an alarm list for a subnetwork of a telecommunications network is obtained. The alarm list has alarm data captured from a plurality of network elements forming the subnetwork. Network data associated with a subset of the network elements is captured by traversing a circuit path in the subnetwork from a source to a destination. The subset of network elements disposed is along the circuit path. The alarm list is correlated with the network data to identify a related network issue. A root cause of the related network issue is determined. One or more recommendations for resolving the root cause of the related network issue are generated, and at least one of the recommendations is deployed in the subnetwork.

What is claimed is: 
     
         1 . A method for alarm reduction, the method comprising:
 receiving an alarm list having alarm data captured from a plurality of remote nodes and consolidated at an aggregator node;   identifying a first alarm from the alarm list, the first alarm corresponding to an optical interface deployed in a circuit of a subnetwork of a telecommunications network;   discovering a topology associated with the optical interface by traversing a path of the circuit;   generating a ticket for a non-service impacting event   obtaining cross connect data from network elements associated with the first alarm;   determining an integrity of the circuit path through the network elements using the cross connect data; and   determining a priority for resolving the ticket based on the integrity of the circuit path through the network elements, the priority specifying an impact potential of the non-service impacting event corresponding to an amount of network assets recoverable on the subnetwork; and   based on the determined priority for resolving the ticket, (i) automatically resolving a network issue related to the first alarm, or (ii) prompting a user to address the ticket.   
     
     
         2 . The method of  claim 1 , further comprising:
 generating an interface list based on the topology;   identifying one or more alarms related to a root cause of the first alarm based on a comparison of the interface list to the alarm list; and   correlating the related alarms to the first alarm for concurrent resolution, wherein   the network elements further include network elements associated with each of the correlated and related alarms.   
     
     
         3 . The method of  claim 1 , further comprising:
 identifying related alarms correlated to the first alarm by tagging the related alarms with a tag assigned to the first alarm.   
     
     
         4 . The method of  claim 1 , wherein related alarms in the alarm list related to the firm alarm are correlated into the ticket. 
     
     
         5 . The method of  claim 1 , wherein the remote nodes are multiplexers and the aggregator node is a gateway network element. 
     
     
         6 . The method of  claim 1 , wherein the path of the circuit is traversed using one or more Transaction Language 1 commands. 
     
     
         7 . The method of  claim 1 , wherein the alarm list is received from an alarm monitor. 
     
     
         8 . One or more non-transitory tangible computer-readable storage media storing computer-executable instructions for performing a computer process on a computing system, the computer process comprising the method of  claim 1 . 
     
     
         9 . A system for alarm reduction, the system comprising:
 one or more databases storing an alarm list and an interface list, the alarm list having alarm data captured from a plurality of remote nodes and consolidated at an aggregator node, the interface list generated based on a topology associated with an optical interface; and   a network health manager executable by at least one computing unit in communication with the one or more databases, the network health manager configured to
 determine a priority for resolving a ticket for a non-service impacting event, the priority specifying an impact potential of the non-service impacting event corresponding to an amount of network assets recoverable on the subnetwork and determined based on an integrity of a circuit path through network elements associated with a first alarm in the alarm list determined using cross connect data obtained from each of the network elements, and 
 based on the determined priority for resolving the ticket, (i) automatically resolving a network issue related to the first alarm, or (ii) prompting a user to address the ticket. 
   
     
     
         10 . The system of  claim 9 , wherein the network health manager is further configured to generate an interface list based on the topology, identify one or more alarms related to a root cause of the first alarm based on a comparison of the interface list to the alarm list, and correlate the related alarms to the first alarm for concurrent resolution, wherein the network elements further include network elements associated with each of the correlated and related alarms. 
     
     
         11 . The system of  claim 9 , wherein the network health manager identifies related alarms correlated to the first alarm using a tag. 
     
     
         12 . The system of  claim 9 , wherein related alarms in the alarm list related to the first alarm are correlated into the ticket. 
     
     
         13 . The system of  claim 9 , wherein the remote nodes are multiplexers and the aggregator node is a gateway network element. 
     
     
         14 . The system of  claim 9 , wherein the topology is discovered using one or more Transaction Language 1 commands. 
     
     
         15 . The system of  claim 9 , wherein the alarm list is received from an alarm monitor in communication with the aggregator node and the network health manager.