US20010013107A1 - Method and apparatus for inter-domain alarm correlation - Google Patents
Method and apparatus for inter-domain alarm correlation Download PDFInfo
- Publication number
- US20010013107A1 US20010013107A1 US09/811,748 US81174801A US2001013107A1 US 20010013107 A1 US20010013107 A1 US 20010013107A1 US 81174801 A US81174801 A US 81174801A US 2001013107 A1 US2001013107 A1 US 2001013107A1
- Authority
- US
- United States
- Prior art keywords
- domain
- alarm
- network
- computer
- alarms
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0062—Provisions for network management
- H04Q3/0095—Specification, development or application of network management software, e.g. software re-use
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0062—Provisions for network management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0062—Provisions for network management
- H04Q3/0075—Fault management techniques
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13516—Indexing scheme relating to selecting arrangements in general and for multiplex systems agents or brokers - user, terminal etc., also OSI agent/managers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13521—Indexing scheme relating to selecting arrangements in general and for multiplex systems fault management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13533—Indexing scheme relating to selecting arrangements in general and for multiplex systems multivendor and hybrid, e.g. public/private, networks, inc. international
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13535—Indexing scheme relating to selecting arrangements in general and for multiplex systems distributed systems - also domains in service creation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13566—Indexing scheme relating to selecting arrangements in general and for multiplex systems mediation
Definitions
- This invention relates generally to communications networks, and more particularly, to communications networks having multiple domains, each of which may cause intra-domain alarms. These intra-domain alarms may be correlated to provide inter-domain alarms and to facilitate more effective user notification and corrective action.
- Networks are widely used to provide increased computing power, sharing of resources and communication between users.
- Networks may include a number of computer devices within a room, building or site that are connected by a high-speed local data link such as token ring, Ethernet, or the like.
- Local area networks (LAN's) in different locations may be interconnected by for example packet switches, microwave links and satellite links to form a wide area network (WAN).
- WAN wide area network
- a network may include several hundred or more connected devices, distributed across several geographical locations and belonging to several organizations.
- Many existing networks are so large that a network administrator will partition the network into multiple domains for ease of management.
- One example is based on geographical location.
- a company may own or manage a network that includes a first domain geographically located in a first city and a second domain geographically located in a second city, as well as other domains disposed in other geographical locations.
- Another domain type is based on organization or departments, e.g., accounting, engineering, sales, etc.
- a company may have a computer network spanning multiple organizations and multiple geographical locations, but there may not be a one-to-one mapping of organizations to geographical locations.
- a first organization and a second organization may both share network resources within first and second geographical locations.
- network accounting e.g., to allocate network charges to the appropriate organization
- a third example of a domain type is a grouping based upon functional characteristics of network resources.
- one functional domain may be considered to be network resources belonging to a company that are provided for performing computer-aided design, which may draw upon common databases and have similar network traffic.
- Another functional domain may be network resources of the same company that are provided for financial analysis, which may be resources specially adapted to provide financial data.
- the network resources of these two domains may be distributed across several geographical locations and several organizations of the company. However, it may be desirable for a network administrator to group the computer-aided design network resources into one domain and to group the financial analysis network resources into another domain. Additional examples of communication network domains also exist, and a single company or organization may have domains that fall into several categories.
- Network management systems are intended to resolve such issues. Older management systems typically operated by collecting large volumes of information which then required evaluation by a network administrator, and thus placed a tremendous burden on and required a highly-skilled network administrator.
- Newer network management systems systematize the knowledge of the networking expert such that common problems of a single domain (i.e., a portion of the network under common management) can be detected, isolated and repaired, either automatically or with the involvement of less-skilled personnel.
- a system typically includes a graphical representation of that portion of the network being monitored by the system.
- Alarms are generated to inform an external entity that an event has occurred or requires attention. Since a large network may have many such events occurring simultaneously, some network management systems provide alarm filtering (i.e., only certain events generate an alarm).
- the existing network management system manages only a single domain.
- a company having a network consisting of several domains will typically purchase one copy of a network management system for each domain.
- Each copy of the network management system may be referred to as an instance.
- a first instance of a network management system may manage the computer-aided design domain, while a second instance of a network management system may manage the financial analysis domain.
- Each instance of the network management system receives information only from the resources of a single respective domain, and generates alarms that are specific only to the single respective domain. Such alarms may be referred to as intra-domain alarms.
- a first domain in a network may include a router that forwards network traffic to a resource in a second domain. If the router fails or begins to degrade, the performance of the second domain may appear sluggish (e.g., excessive delays, low throughput), even though the network resources within the second domain are operating correctly.
- This sluggishness may cause an alarm to be generated from the instance of the network management system that manages the second domain.
- no alarm relating to this situation has been generated by the first instance of the network management system that manages the first domain, because there is no performance degradation within the first domain. It is currently necessary to apply human intervention and human reasoning to resolve such a situation.
- a multi-domain alarm manager provides alarm correlation among a plurality of domains in a communications network.
- Individual network management systems each monitor a single respective domain of the communications network, and provide intra-domain alarms indicative of status specific to the single respective domain.
- the manager receives the intra-domain alarms, and correlates them to provide inter-domain alarms as well as responses in the form of corrective actions.
- the manager thus provides a high level of correlation and response for the entire network while each single-domain network management system provides a lower level of correlation and response for an individual domain of the network.
- the method comprises the steps of receiving a first intra-domain alarm from a first domain, receiving a second intra-domain alarm from a second domain, and correlating the first alarm with the second alarm to generate an inter-domain alarm.
- the inter-domain alarm may be analyzed to determine a corrective action, and a command may be provided to a network resource within the communications network to implement the corrective action.
- status information may be received from at least one resource in the first domain, and a first portion of the status information may be correlated to generate a first intra-domain alarm.
- a second portion of the status information may be correlated to determine a second corrective action, and a second command may be provided to a second network resource within the communications network to implement the second corrective action.
- correlating includes determining a domain that is adjacent to a first domain. Correlating may also include determining a severity of a condition indicated by a combination of a first intra-domain alarm and a second intra-domain alarm, the inter-domain alarm including an indication of the severity of the condition. Additionally, correlating may include providing a first intra-domain alarm and a second intra-domain alarm to a state machine, and receiving an output from the state machine indicative of a severity and a correlation of a combination of the first intra-domain alarm and the second intra-domain alarm.
- FIG. 1 is a schematic illustration of the relationship between a network and a network management system
- FIG. 2 is a view of a user interface of a network management system such as that shown in FIG. 1;
- FIG. 3 is a schematic illustration of one embodiment of the invention, in which a multi-domain manager operates in conjunction with a plurality of single-domain network management systems, each of which monitors a single respective domain of a communications network;
- FIG. 4A is a schematic flow diagram of a multiple-loop architecture according to one embodiment of the invention.
- FIG. 4B is a more detailed flow diagram of one level of operation of FIG. 4A;
- FIG. 5 is a block diagram correlating the different levels of the multiple-loop architecture of FIG. 4A to the elements of FIG. 3;
- FIG. 6 is a flow diagram showing the steps of a process in accordance with an embodiment of the invention.
- FIG. 7 is a flow diagram showing steps of a process in which intra-domain alarms are received and responded to, as performed by an embodiment of the inter-domain alarm correlation system depicted in FIG. 3;
- FIG. 8 is a state transition diagram illustrating a method of determining the severity of a condition indicated by one or more intra-domain alarms from a single domain
- FIG. 9 is a state transition diagram illustrating correlation between intra-domain alarms from a single domain
- FIG. 10 is a state transition diagram illustrating correlation of intra-domain alarms, for example alarms generated from the state transition diagrams of FIGS. 8 - 9 , to generate inter-domain alarms;
- FIG. 11 is a block diagram of a general purpose computer which may be employed to implement embodiments of the invention.
- a multi-domain manager provides correlation among network domains having entities that make up a communications network.
- the network entities also known as network resources
- the network entities include not only hardware devices such as personal computers (PCS), workstations, hubs, routers, bridges, and repeaters, but also software applications.
- PCS personal computers
- the manager facilitates high-level insight into the operation of a network that has previously not been feasible without highly-skilled human intervention.
- FIG. 1 is a block diagram illustrating generally the arrangement of a network management system 11 which monitors a live network 10 via a communication interface 12 .
- the network management system (NMS) 11 is a client-server based NMS known as SPECTRUM®, which includes a database of models relating to corresponding network entities and relationships among those entities.
- the SPECTRUM server includes a network interface and control module 14 and a virtual network machine 16
- the SPECTRUM client includes a user interface 18 .
- the SPECTRUM network management system continually monitors the network 10 and maintains a database of information about managed entities within the network 10 .
- An understanding of the present invention is furthered by an understanding of a model-based network management system such as SPECTRUM, which is described in U.S. Pat. No. 5,261,044, issued Nov. 9, 1993 to R. Dev et al., and hereby incorporated by reference in its entirety.
- the SPECTRUM system is commercially available and also described in various user manuals and literature available from Cabletron Systems, Inc., Rochester, N.H.
- SPECTRUM is a system for maintaining and processing information pertaining to the condition of the computer network and providing the same to a user, the network including a plurality of network resources such as computer devices and software applications being executed on such devices.
- the system includes a virtual network machine 16 , comprising a programmed digital computer, wherein a program is implemented using an object-oriented programming language such as C++, Eiffel, SmallTalk, and Ada.
- the virtual network machine 16 includes interrelated intelligent models of network entities and relations between network entities, including a capability for acquiring network data pertaining to the condition of a network entity from the corresponding network entity, and for those entities not capable of being contacted, inferring their status from the status of other entities.
- the virtual network machine 16 maintains objects which include network data relating to the corresponding network entity and one or more inference handlers for processing the network data, the inference handlers being responsive to changes occurring in the same and/or a different object.
- the network data can then be transferred to a user interface 18 coupled to the virtual network machine 16 , for supplying the network data to a user.
- the models may be implemented as software “objects” containing both “data” (attributes) relating to the corresponding network entity and one or more “inference handlers” (functions) for processing the data. See Grady Booch, “Object-Oriented Analysis And Design, With Applications,” 2nd Edition, Benjamin/Cummings Publishing Co., Redwood City, Calif., Chapter 2 (1994).
- the inference handlers may be initiated by predetermined virtual network events, such as a change in specified network data in the same model, a change in specified network data in a different model, and predefined events or changes in models or model relations.
- Information pertaining to the condition of the network resource can be obtained from the network entity by polling the resource, can be automatically received from the network resource without polling, or can be inferred from data contained in other models.
- An alarm condition may be generated when the network data meets a predetermined criteria. Events, alarms and statistical information from the virtual network may be stored in a database to be selectively displayed for the user.
- the data in the SPECTRUM database may be used for generating topological displays of the network, showing hierarchial relationships between network devices, isolating a network fault, reviewing statistical information, as well as other functions.
- the SPECTRUM network management system allows for collective management of autonomous local area networks (LANs), with equipment from different vendors. It complies with the current Simple Network Management Protocol (SNMP) standards, and can also accommodate other standard and proprietary protocols.
- the virtual network machine 16 preprocesses the raw information coming from the network entities through the network interface and control module 14 in order to construct a model of the network's current status and performance characteristics. Network entities that cannot be directly communicated with (e.g., cables and buildings) can infer their status from the status of the entities connected to or contained within them.
- the virtual network machine 16 provides a consistent interface for management applications to access any of the information in the model and thereby provides these applications with a unified view of the network 10 .
- the SPECTROGRAPH® user interface 18 provides a highly graphical multi-perspective view into the network model.
- the user interface enables the user to navigate through a landscape in which cables, networks, local area networks and even rooms show up as icons, and which icons indicate the health and performance characteristics of those elements. Many of these icons can be further queried for additional information.
- the main function of the user interface 18 is to visually present to the user the model within the virtual network machine 16 . It allows the user to navigate freely within the network model, only limited by the access rights assigned by the network administrator. The information can be accessed at varying degrees of detail, from a macro overview, down to the level of the devices and the cables which connect them.
- the SPECTROGRAPH user interface provides an alarm management facility, an event log window, a reporting facility, a find facility, and other features.
- the alarm log view 23 may include an area 20 for the listing of current alarms, and an area 22 for displaying information pertaining to a selected alarm.
- a user such as a system administrator or a technician, may select a particular alarm in the listing of current alarms to obtain more information.
- a multi-function icon 24 representing the network device having the fault is displayed in area 22 , and one or more text fields 26 and 28 which provide information regarding the cause of the alarm and the status of the device. By selecting specified areas of the icon 24 , the user can obtain further information regarding the device for which an alarm is registered.
- information from the virtual network machine 16 may be provided directly to another computer program, or may be provided to a user via electronic mail or a telephone message that is automatically transmitted.
- One method for fault management in large communications networks is to use a “trouble-ticketing” system.
- This system provides a number of tools for use by network users, administrators, and repair and maintenance personnel.
- the basic data structure, a trouble-ticket has a number of fields in which a user can enter data describing the parameters of an observed network fault.
- a trouble-ticket filled out by a user may then be transmitted by, for example, an electronic mail system to maintenance and repair personnel.
- a trouble-ticket describing a current network fault requiring attention or action is referred to as an outstanding trouble-ticket.
- the solution to the problem typically called a resolution
- the system stores completed trouble-tickets in memory and thus a library of such tickets is created, allowing users, administrators, and maintenance and repair personnel to refer to the same for assistance in determining solutions to future network faults.
- a trouble-ticketing system is the ACTION REQUEST system, developed by Remedy Corporation, Mountain View, Calif., and sold by Cabletron Systems, Inc., Rochester, N.H.
- ARS GatewayTM is an application sold by Cabletron Systems, Inc. which incorporates the SPECTRUM and ACTION REQUEST systems, i.e., the ARS Gateway application receives fault information from the SPECTRUM system and automatically generates and processes a trouble-ticket.
- the ARS Gateway system is described in copending and commonly owned U.S. Ser. No. 08/023,972 filed Feb. 26, 1993 by Lundy Lewis, entitled “Method and Apparatus For Resolving Faults In Communications Networks,” which is hereby incorporated by reference in its entirety.
- each instance of the previously existing network management system manages only a single domain, and thus will correlate events only within the single domain to generate one or more inter-domain alarms.
- An improvement over these prior systems is the SPECTRUM Alarm Notification Manager (SANM), which utilizes policy-based filters to create an alarm notification policy that may apply to alarms received from several instances of a network management system.
- SAM SPECTRUM Alarm Notification Manager
- Such a system is described in copending and commonly owned U.S. Ser. No. 08/558,425 filed Nov. 16, 1995 by Arrowsmith et al., entitled “Method and Apparatus For Policy-Based Alarm Notification in a Distributed Network Management Environment,” which is hereby incorporated by reference in its entirety.
- FIG. 3 illustrates an embodiment of the invention in which intra-domain alarms are correlated and analyzed to provide inter-domain alarms, corrective actions, and other responses.
- a communications network 10 is arranged into a plurality of domains—domain A, domain B, and domain C.
- Network management system (NMS) 11 A manages only domain A via interface 12 A
- NMS 11 B manages only domain B via interface 12 B
- NMS 11 C manages only domain C via interface 12 C.
- the NMSs 11 A-C may be different instances of one type of NMS, or may be instances of different network management systems such as those described earlier.
- the NMSs 11 A- 11 C need not be directly connected to their respective domains A-C, but some path will exist for information transfer between each NMS 11 A- 11 C and its respective domain A-C.
- the information transfer from the domains A-C to their respective NMS 11 A- 11 C typically includes messages regarding the status of network resources within the respective domain.
- a network resource may be a device that includes built-in-test functions. When such functions indicate that the device may be faulty or degraded, a message is provided to the NMS. Additionally, some devices monitor network parameters such as throughput and error rate, and provide results to the NMS. The NMS may perform certain monitoring functions as well.
- a message provided from a network resource to an NMS may be referred to as a report, and a succession of such reports is typically referred to as an event stream.
- each NMS 11 A- 11 C is operatively coupled to the multi-domain manager 30 , in order to provide messages to and receive responses back from the manager 30 .
- NMS 11 A monitors domain A via interface 12 A, produces intra-domain alarms 35 A that are specific to domain A, and provides the intra-domain alarms 35 A to the manager 30 .
- NMS 11 B monitors domain B via interface 12 B, produces intra-domain alarms 35 B and provides them to manager 30
- NMS 11 C monitors domain C via interface 12 C, produces intra-domain alarms 35 C and provides them to manager 30 .
- the manager 30 correlates the intra-domain alarms 35 A- 35 C and provides in response inter-domain alarm responses 38 A- 38 C to one or more of the NMSs 11 A- 11 C.
- manager 30 includes an alarm notifier 31 , an inter-domain alarm correlation system 32 , and a response interface 33 .
- Alarm notifier 31 receives intra-domain alarms on links 35 A- 35 C from the NMSs 11 A- 11 C and provides them on link 36 to correlation system 32 .
- Correlation system 32 provides inter-domain responses on link 37 to response interface 33 , which in turn provides the inter-domain responses on one or more of links 38 A- 38 C to the respective NMSs 11 A- 11 C.
- the inter-domain responses may include inter-domain alarms, commands, and requests for more information.
- An example of an inter-domain alarm is a notification that a router in domain A may be faulty or degraded, and thus may affect the throughput or other performance characteristics of domain B.
- An example of a command is a command to re-route data from domain A intended for domain B through a different router than the faulty or degraded router.
- a request for information may be generated by correlation system 32 when, for example, an intra-domain alarm has been received, but a sufficient inter-domain alarm cannot be generated until additional information is received. Accordingly, the messages from domains A-C may also include responses to requests for information, which may or may not be alarms as previously defined.
- the structure illustrated in FIG. 3 allows for event and alarm correlation to be performed at multiple levels of abstraction, and thus facilitates quick corrective action by NMSs 11 A- 11 C to some events, while also providing more highly-correlated inter-domain responses (e.g., from manager 30 ) to events that may be of a more complex nature.
- FIG. 4A illustrates a multiple loop architecture (MLA) that facilitates multiple levels of coordination in network management.
- FIG. 4A is generalized to represent a system having inputs (network monitoring) and outputs (network control).
- a first (lower) level of coordination includes operator 41 and operator 42 , which are coupled together to provide a first control loop 43 .
- the term “operator” may mean any entity that performs an aspect of control processing at a particular level. Such an operator may be an individual computer or software routine, specialized hardware, or a portion of software on a general purpose computer.
- Operators 41 and 42 represent a first level of abstraction, and a first level of coordination takes place between operators 41 and 42 to provide output in response to some inputs.
- Operators 44 and 45 represent a second (higher) level of abstraction, and thus a second control loop 46 includes operators 41 , 42 , 44 , and 45 .
- Operators 47 and 48 represent a third (highest) level of abstraction, and thus a third control loop 49 includes operators 41 , 42 , 44 , 45 , 47 , and 48 .
- the coordination that takes place at a lower level for example, the first level via first loop 43
- Lower level coordination may be referred to as reflexive behavior that generates short-term solutions, while higher level coordination may be referred to as deliberative behavior that generates longer-term solutions.
- Each control loop 43 , 46 , 49 may be viewed as a separate control loop that corresponds to a specific class of problems, where problems are partitioned and assigned to levels according to the amount of time and type of information required to solve the problems.
- the short-term abstraction/coordination/decomposition (first loop 43 ) at the lowest level typically operates on raw data and provides quick reaction, bypassing upper level control mechanisms.
- such tasks might include intelligent routing and temporary disconnections to a network resource such as a host that is too busy to effectively communicate.
- the second loop 46 may provide reaction to more complex problems and operates on increasingly abstract input such as signs and symbols. Tasks for the second loop 46 may include alarm correlation for a single domain of a network, where some alarms represent actual problems and other alarms are only apparent problems. Due to the information that the second control loop 46 contains regarding network resources of a single domain, it is possible to distinguish between actual problems and apparent problems to achieve effective alarm filtering.
- the third control loop 49 may provide reaction to problems that require more time as well as a higher class of information.
- An example of a task performed by the third loop 49 is reasoning involved in deciding to re-allocate a host from domain A to domain B because a majority of the host's clients reside in domain B, thereby causing increased but unnecessary traffic on a link between domain A and domain B.
- FIG. 4B shows an example of a single level of operation of the multi-loop architecture of FIG. 4A.
- the single level 50 which may represent both operator 44 and operator 45 of FIG. 4A, includes an abstraction agent 51 , a coordination agent 52 , and a decomposition agent 53 .
- the coordination agent 52 evaluates network information N handed up from the level beneath and a task T handed down from the level above, and passes information (for example, a modified task) to the decomposition agent 53 and passes network information (possibly modified) to the abstraction agent 51 .
- the decomposition agent 53 receives the task information T, decomposes it, and transmits the resulting task information T′′ to a coordination agent on the level beneath.
- the abstraction agent 51 receives the network information N, abstracts it, and transmits the correlated network information N′′ to a coordination agent on the level above.
- N and T may be represented as state vectors wherein N is the current state of the environment/platform (such as an operating efficiency of a network domain) and T is the goal state.
- the coordination agent 52 computes the difference between N and T.
- a significant difference between N and T may denote a problem.
- the solutions to the problem, from the perspective of level L, are N′ and T′, where N′ is new network information and T′ is a new task (i.e. a solution).
- N′ is new network information
- T′ is a new task (i.e. a solution).
- N′ and T′ there is likely no problem, as exemplified by “nil” N′ and T′.
- N is abstracted into N′′ and transmitted to level L+1, and T′ is decomposed into T′′ and transmitted to level L ⁇ 1.
- T′ is decomposed into T′′ and transmitted to level L ⁇ 1, and N′ is abstracted into N′′ and passed to level L+1. Note that T′′ replaces the old task, as instructed by the coordination agent 52 .
- N′ is abstracted into N′′ and transmitted to level L+1, and T′ is decomposed into T′′ and transmitted to level L ⁇ 1.
- N′′ contains an abstraction of N plus information relating to a problem perceived by the coordination agent 52 .
- case 4 there may be a problem which the single level 50 can offer a partial (possibly incomplete) solution.
- Case 4 exemplifies a situation in which two or more levels will have to contribute partial solutions to a problem that may not be effectively solved by any one level alone.
- FIG. 5 is a functional flow diagram illustrating different levels of correlation and response, similar to FIG. 4A, as applied to the multi-domain manager 30 and any one instance of a network management system 11 N.
- a plurality of network management systems for example systems 11 A- 11 C may be implemented, but only a single instance 11 N is depicted in FIG. 5 for clarity.
- a first lower level of correlation and response includes intra-domain event correlation operator 54 and intra-domain event response operator 55 , forming a first control loop.
- a second mid-level of correlation and response includes intra-domain alarm correlation operator 56 and intra-domain alarm response operator 57 , forming a second control loop.
- the second control loop may require more time as well as more information from the network resources in the domain monitored by the network management system 11 N. Both the first and second control loops take place within one instance of a network management system 11 N, and provide correlation and response for the single domain managed by that NMS 11 N.
- a third high level of correlation and response includes inter-domain alarm correlation operator 58 which may operate on the results of intra-domain alarm correlation 56 from one or more instances of a network management system, and inter-domain response operator 59 .
- the results of the response operator 59 are provided to the appropriate network management systems as discussed earlier, and may include inter-domain alarms, commands, and requests for additional information. Due to the hierarchial nature of the correlation disclosed herein, the multi-domain manager may receive intra-domain alarms, correlate them as necessary, and provide a single user with insight as to the status of several networks.
- FIG. 6 is a flow chart of a method embodiment of the present invention.
- steps 60 - 62 are typically performed by one instance (e.g., 11 A of FIG. 3) of a single-domain network management system
- steps 63 - 64 are typically performed by a second instance (e.g., 11 B of FIG. 3) of a single-domain network management system.
- Steps 65 - 68 are performed by the multi-domain manager 30 shown in FIG. 3.
- one single-domain NMS 11 N may also contain the manager 30 .
- step 60 status information is received from a resource in a first domain, such as domain A in FIG. 3.
- NMS 11 A may provide corrective action as shown in step 61 , if there exists sufficient information upon which to determine such action.
- step 62 an intra-domain alarm is generated, which may be provided to a user in any manner previously described. This intra-domain alarm is also provided to the multi-domain manager 30 .
- step 63 status information is received from a resource in a second domain, such as domain B.
- NMS 11 B generates an intra-domain alarm in step 64 .
- lower level corrective action could take place as in step 61 ).
- step 65 information in addition to the two intra-domain alarms may be requested and received by the manager; such action is not required.
- An inter-domain alarm is generated in step 66 by correlating the intra-domain alarms together and with any additional information. This inter-domain alarm may then be sent to users or to any appropriate NMS or individual network entities, as described below with respect to FIG. 7.
- step 67 the inter-domain alarm is analyzed to determine any corrective action, and in step 68 such corrective action is implemented. Because a multi-domain manager has insight into the operation and structure of several domains, such corrective action may be more effective than corrective action determined only from a limited amount of information (i.e., available from a single domain).
- FIG. 7 illustrates steps of a process performed by one particular embodiment of the inter-domain alarm correlation system 32 (of FIG. 3).
- an intra-domain alarm is received, for example from NMS 11 A.
- Such an intra-domain alarm may represent a non-critical condition, for example a one-time event, or it may represent a severe condition that may soon impact other domains B, C of the network 10 .
- the severity of the condition (represented by the intra-domain alarm) is determined. If the severity is sufficiently great, an inter-domain alarm is sent to some or all of the domains on the network 10 .
- domains adjacent to domain A are determined, and in step 78 the inter-domain alarm is sent to the NMSs 11 B, 11 C of each adjacent domain.
- An inter-domain alarm may include an indication of the severity of the condition which caused the alarm, in case any of the NMSs 11 B, 11 C have different corrective actions that depend upon the severity.
- FIG. 8 shows a state transition diagram (STG) by which the severity of a condition may be determined for a single domain (“domain A”).
- STG state transition diagram
- FIG. 8 is simplified in that only three states are shown, and only with respect to one type of failure indication (“failure indication A”).
- failure indication A Such an STG may be implemented within a single-domain network management system, for example 11 A in FIG. 3.
- state 1 - 1 ( 81 ) no failure indications have been received, and accordingly no alarms are sent.
- a failure indication “M” is received from a device within domain A
- the system is transitioned to state 1 - 2 ( 82 ).
- no alarm is sent while in state 1 - 2 ( 82 ).
- a certain time elapses e.g., one minute
- state 1 - 3 ( 83 ) is indicative of a mild condition, so a mild domain A alarm “X” may be sent, as shown in action 84 .
- Alarm “X” is an intra-domain alarm, because it was generated from information regarding only a single domain A.
- Alarm “X” may be processed as indicated previously, but may also be sent to a multi-domain manager for further processing as described in more detail below.
- FIG. 9 shows an STG for a domain different from the domain represented by FIG. 8, for example domain B in FIG. 3, managed by NMS 11 B.
- FIG. 9 is an example of a single-domain STG in which an alarm should be sent if a second type of a failure indication is received within a certain amount of time following a first type of a failure indication.
- state 2 - 1 ( 93 ) represents an initial condition.
- the system transitions to state 2 - 2 ( 92 ).
- Subsequent failure indications “N” may cause the system to stay within state 2 - 2 , and may also reset a timer which would otherwise return the system to state 2 - 1 ( 91 ) if no further failure indications “N” are received within a certain amount of time.
- domain B alarm “Y” is sent (action 93 ). Both failure indications “N” and “O” are generated from devices within domain B.
- FIG. 10 is an example of an inter-domain STG which uses the results of the STGs of FIGS. 8 - 9 .
- the inter-domain STG of FIG. 10 may represent an implementation of the inter-domain correlation system 32 .
- Such an inter-domain STG has the capability of analyzing and responding to intra-domain alarms in conjunction with one another. Since the intra-domain alarms represent some previous analysis, the inter-domain STG provides insight into domains A and B which was not previously possible.
- State I- 1 ( 101 ) represents an initial condition of the inter-domain STG.
- a mild alarm “X” (for example, as sent during action 84 of FIG. 8)
- the system transitions to state I- 2 ( 102 ).
- Subsequent mild alarms “X” will not change the state, but if an alarm “Y” is received (for example as sent during action 93 of FIG. 9), then a mild inter-domain alarm “Z” is generated (action 103 ).
- an inter-domain alarm “Z” would not be possible, because no system used the results of the respective network management systems of two different domains.
- FIG. 10 does not show timeouts, but such timeouts as depicted in FIGS. 8 - 9 may also be applied to the inter-domain STG of FIG. 10.
- a strong alarm “X” is received while the system is in state I- 2 ( 102 ) or from the initial state I- 1 , then the system transitions to state I- 4 ( 105 ). In this example, subsequent strong alarms “X” and mild alarms “X” do not change the state. However, if an alarm “Y” is received subsequent to a strong alarm “X”, then a strong inter-domain alarm “Z” is generated (action 106 ), and corrective action ( 107 ) may also be taken. Such actions 106 , 107 may also be taken if a strong alarm “X” is received subsequent to an alarm “Y”. The corrective action 107 may represent actions which would not have been taken were it not for the correlation of intra-domain alarm “X” with intra-domain alarm “Y”, because each of the inter-domain network management systems only have knowledge regarding devices within their respective domain.
- the alarm notifier 31 (see FIG. 3) is the SPECTRUM Alarm Notification Manager (SANM) described above, and each network management system 11 A- 11 C is an instance of SPECTRUM.
- the response interface 33 is the SPECTRUM Command Line Interface (CLI).
- CLI SPECTRUM Command Line Interface
- the inter-domain alarm correlation system 32 may be implemented as a state transition graph (STG) in the product NerveCenter, available from NetLabs Inc., 4920 El Camino Real, Los Altos, Calif. 94022.
- STG state transition graph
- the inter-domain alarm correlation system 32 may be implemented in specially-designed hardware such as a state machine, or in any of several programming languages on a general purpose computer, or as a programmed general purpose computer itself.
- elements of the multi-domain manager 30 may be implemented as software on a floppy disk, compact disk, or hard drive, which controls a computer, for example a general purpose computer such as a workstation, a mainframe or a personal computer, to perform the process steps disclosed in FIGS. 6 - 10 .
- a general purpose computer 110 shown in FIG. 11, typically includes a central processing unit 112 (CPU) coupled to random access memory (RAM) 114 and program memory 116 via a data bus 118 .
- the general purpose computer 110 may be connected to the network 10 in order to receive reports, and may provide commands to devices on the network in order to control the network configuration.
- the elements of the multi-domain network manager 30 may be implemented as special purpose electronic hardware. Additionally, in either a hardware or software embodiment, the functions performed by the different elements within the multi-domain network manager 30 may be combined in varying arrangements of hardware and software.
Abstract
Description
-
b 1. Field of the Invention - This invention relates generally to communications networks, and more particularly, to communications networks having multiple domains, each of which may cause intra-domain alarms. These intra-domain alarms may be correlated to provide inter-domain alarms and to facilitate more effective user notification and corrective action.
- 2. Discussion of the Related Art
- Computer networks are widely used to provide increased computing power, sharing of resources and communication between users. Networks may include a number of computer devices within a room, building or site that are connected by a high-speed local data link such as token ring, Ethernet, or the like. Local area networks (LAN's) in different locations may be interconnected by for example packet switches, microwave links and satellite links to form a wide area network (WAN). A network may include several hundred or more connected devices, distributed across several geographical locations and belonging to several organizations.
- Many existing networks are so large that a network administrator will partition the network into multiple domains for ease of management. There are various types of domains. One example is based on geographical location. For example, a company may own or manage a network that includes a first domain geographically located in a first city and a second domain geographically located in a second city, as well as other domains disposed in other geographical locations.
- Another domain type is based on organization or departments, e.g., accounting, engineering, sales, etc. A company may have a computer network spanning multiple organizations and multiple geographical locations, but there may not be a one-to-one mapping of organizations to geographical locations. Thus, a first organization and a second organization may both share network resources within first and second geographical locations. For purposes of network accounting (e.g., to allocate network charges to the appropriate organization) or for other reasons, it may be advantageous to consider the network resources of the first organization as being a separate domain from the network resources of the second organization.
- A third example of a domain type is a grouping based upon functional characteristics of network resources. For example, one functional domain may be considered to be network resources belonging to a company that are provided for performing computer-aided design, which may draw upon common databases and have similar network traffic. Another functional domain may be network resources of the same company that are provided for financial analysis, which may be resources specially adapted to provide financial data. The network resources of these two domains may be distributed across several geographical locations and several organizations of the company. However, it may be desirable for a network administrator to group the computer-aided design network resources into one domain and to group the financial analysis network resources into another domain. Additional examples of communication network domains also exist, and a single company or organization may have domains that fall into several categories.
- The above examples were discussed with respect to one company owning and managing its own network. Similar situations exist for any entity that manages and/or owns a network, for example a service company that provides network management services to several companies.
- In the operation and maintenance of computer networks a number of issues arise, including traffic overload on parts of the network, optimum placement and interconnection of network resources, security, isolation of network faults, and the like. These issues become increasingly complex and difficult to understand and manage as the network becomes larger and more complex. For example, if a network device is not sending messages, it may be difficult to determine whether the fault is in the device itself, a data communication link, or an intermediate network device between the sending and receiving devices.
- Network management systems are intended to resolve such issues. Older management systems typically operated by collecting large volumes of information which then required evaluation by a network administrator, and thus placed a tremendous burden on and required a highly-skilled network administrator.
- Newer network management systems systematize the knowledge of the networking expert such that common problems of a single domain (i.e., a portion of the network under common management) can be detected, isolated and repaired, either automatically or with the involvement of less-skilled personnel. Such a system typically includes a graphical representation of that portion of the network being monitored by the system. Alarms are generated to inform an external entity that an event has occurred or requires attention. Since a large network may have many such events occurring simultaneously, some network management systems provide alarm filtering (i.e., only certain events generate an alarm).
- Commercially available network management systems and applications for alarm filtering include: (1) SPECTRUM®, Cabletron Systems, Inc., 35 Industrial Way, Rochester, N.H. 03867; (2) HP OpenView, Hewlett Packard Corp., 3000 Hanover Street, Palo Alto, Calif. 94304; (3) LattisNet, Bay Networks, 4401 Great American Pkwy., Santa Clara, Calif. 95054; (4) IBM Netview/6000, IBM Corp., Old Orchard Road, Armonk, N.Y. 10504; (5) SunNet Manager, SunConnect, 2550 Garcia Ave., Mountain View, Calif. 94043; and (6) NerveCenter, NetLabs Inc., 4920 El Camino Real, Los Altos, Calif. 94022.
- However, in each instance the existing network management system manages only a single domain. For example, a company having a network consisting of several domains will typically purchase one copy of a network management system for each domain. Each copy of the network management system may be referred to as an instance. Thus, in the functional domain example described above, a first instance of a network management system may manage the computer-aided design domain, while a second instance of a network management system may manage the financial analysis domain. Each instance of the network management system receives information only from the resources of a single respective domain, and generates alarms that are specific only to the single respective domain. Such alarms may be referred to as intra-domain alarms.
- Because each instance of a network management system manages only one domain, there is currently no diagnosis or management which takes into account the relationships among multiple domains. Since domains may be interconnected, an intra-domain alarm might be generated for a first domain, even though the event or fault that is causing the intra-domain alarm may be contained within the network resources of a different domain. For example, a first domain in a network may include a router that forwards network traffic to a resource in a second domain. If the router fails or begins to degrade, the performance of the second domain may appear sluggish (e.g., excessive delays, low throughput), even though the network resources within the second domain are operating correctly. This sluggishness may cause an alarm to be generated from the instance of the network management system that manages the second domain. However, no alarm relating to this situation has been generated by the first instance of the network management system that manages the first domain, because there is no performance degradation within the first domain. It is currently necessary to apply human intervention and human reasoning to resolve such a situation.
- According to one aspect of the invention, a multi-domain alarm manager provides alarm correlation among a plurality of domains in a communications network. Individual network management systems each monitor a single respective domain of the communications network, and provide intra-domain alarms indicative of status specific to the single respective domain. The manager receives the intra-domain alarms, and correlates them to provide inter-domain alarms as well as responses in the form of corrective actions. The manager thus provides a high level of correlation and response for the entire network while each single-domain network management system provides a lower level of correlation and response for an individual domain of the network.
- According to a method embodiment of the invention, the method comprises the steps of receiving a first intra-domain alarm from a first domain, receiving a second intra-domain alarm from a second domain, and correlating the first alarm with the second alarm to generate an inter-domain alarm.
- In the above embodiments, the inter-domain alarm may be analyzed to determine a corrective action, and a command may be provided to a network resource within the communications network to implement the corrective action. Moreover, status information may be received from at least one resource in the first domain, and a first portion of the status information may be correlated to generate a first intra-domain alarm. A second portion of the status information may be correlated to determine a second corrective action, and a second command may be provided to a second network resource within the communications network to implement the second corrective action.
- In a particular embodiment, correlating includes determining a domain that is adjacent to a first domain. Correlating may also include determining a severity of a condition indicated by a combination of a first intra-domain alarm and a second intra-domain alarm, the inter-domain alarm including an indication of the severity of the condition. Additionally, correlating may include providing a first intra-domain alarm and a second intra-domain alarm to a state machine, and receiving an output from the state machine indicative of a severity and a correlation of a combination of the first intra-domain alarm and the second intra-domain alarm.
- By providing two levels of correlation, one at the network management system level (within a domain) which utilizes for example model based reasoning, and a second at the alarm manager level (across multiple domains) which utilizes for example a state transition graph (or case based reasoning or intelligent systems), an improvement in scaleability is provided not possible with prior systems.
- These and other features and advantages of the present invention shall appear from the following description of an exemplary embodiment, said description being made with reference to the appended drawings, of which:
- FIG. 1 is a schematic illustration of the relationship between a network and a network management system;
- FIG. 2 is a view of a user interface of a network management system such as that shown in FIG. 1;
- FIG. 3 is a schematic illustration of one embodiment of the invention, in which a multi-domain manager operates in conjunction with a plurality of single-domain network management systems, each of which monitors a single respective domain of a communications network;
- FIG. 4A is a schematic flow diagram of a multiple-loop architecture according to one embodiment of the invention;
- FIG. 4B is a more detailed flow diagram of one level of operation of FIG. 4A;
- FIG. 5 is a block diagram correlating the different levels of the multiple-loop architecture of FIG. 4A to the elements of FIG. 3;
- FIG. 6 is a flow diagram showing the steps of a process in accordance with an embodiment of the invention;
- FIG. 7 is a flow diagram showing steps of a process in which intra-domain alarms are received and responded to, as performed by an embodiment of the inter-domain alarm correlation system depicted in FIG. 3;
- FIG. 8 is a state transition diagram illustrating a method of determining the severity of a condition indicated by one or more intra-domain alarms from a single domain;
- FIG. 9 is a state transition diagram illustrating correlation between intra-domain alarms from a single domain;
- FIG. 10 is a state transition diagram illustrating correlation of intra-domain alarms, for example alarms generated from the state transition diagrams of FIGS.8-9, to generate inter-domain alarms; and
- FIG. 11 is a block diagram of a general purpose computer which may be employed to implement embodiments of the invention.
- In accordance with a specific embodiment of the present invention, a multi-domain manager provides correlation among network domains having entities that make up a communications network. The network entities (also known as network resources), include not only hardware devices such as personal computers (PCS), workstations, hubs, routers, bridges, and repeaters, but also software applications. The manager facilitates high-level insight into the operation of a network that has previously not been feasible without highly-skilled human intervention.
- FIG. 1 is a block diagram illustrating generally the arrangement of a
network management system 11 which monitors alive network 10 via acommunication interface 12. In this example the network management system (NMS) 11 is a client-server based NMS known as SPECTRUM®, which includes a database of models relating to corresponding network entities and relationships among those entities. The SPECTRUM server includes a network interface andcontrol module 14 and avirtual network machine 16, and the SPECTRUM client includes auser interface 18. - The SPECTRUM network management system (NMS) continually monitors the
network 10 and maintains a database of information about managed entities within thenetwork 10. An understanding of the present invention is furthered by an understanding of a model-based network management system such as SPECTRUM, which is described in U.S. Pat. No. 5,261,044, issued Nov. 9, 1993 to R. Dev et al., and hereby incorporated by reference in its entirety. The SPECTRUM system is commercially available and also described in various user manuals and literature available from Cabletron Systems, Inc., Rochester, N.H. - In summary, SPECTRUM is a system for maintaining and processing information pertaining to the condition of the computer network and providing the same to a user, the network including a plurality of network resources such as computer devices and software applications being executed on such devices. The system includes a
virtual network machine 16, comprising a programmed digital computer, wherein a program is implemented using an object-oriented programming language such as C++, Eiffel, SmallTalk, and Ada. Thevirtual network machine 16 includes interrelated intelligent models of network entities and relations between network entities, including a capability for acquiring network data pertaining to the condition of a network entity from the corresponding network entity, and for those entities not capable of being contacted, inferring their status from the status of other entities. Thevirtual network machine 16 maintains objects which include network data relating to the corresponding network entity and one or more inference handlers for processing the network data, the inference handlers being responsive to changes occurring in the same and/or a different object. The network data can then be transferred to auser interface 18 coupled to thevirtual network machine 16, for supplying the network data to a user. - Thus, the models may be implemented as software “objects” containing both “data” (attributes) relating to the corresponding network entity and one or more “inference handlers” (functions) for processing the data. See Grady Booch, “Object-Oriented Analysis And Design, With Applications,” 2nd Edition, Benjamin/Cummings Publishing Co., Redwood City, Calif., Chapter 2 (1994). The inference handlers may be initiated by predetermined virtual network events, such as a change in specified network data in the same model, a change in specified network data in a different model, and predefined events or changes in models or model relations. Information pertaining to the condition of the network resource can be obtained from the network entity by polling the resource, can be automatically received from the network resource without polling, or can be inferred from data contained in other models. An alarm condition may be generated when the network data meets a predetermined criteria. Events, alarms and statistical information from the virtual network may be stored in a database to be selectively displayed for the user.
- The data in the SPECTRUM database may be used for generating topological displays of the network, showing hierarchial relationships between network devices, isolating a network fault, reviewing statistical information, as well as other functions.
- The SPECTRUM network management system allows for collective management of autonomous local area networks (LANs), with equipment from different vendors. It complies with the current Simple Network Management Protocol (SNMP) standards, and can also accommodate other standard and proprietary protocols. The
virtual network machine 16 preprocesses the raw information coming from the network entities through the network interface andcontrol module 14 in order to construct a model of the network's current status and performance characteristics. Network entities that cannot be directly communicated with (e.g., cables and buildings) can infer their status from the status of the entities connected to or contained within them. Thevirtual network machine 16 provides a consistent interface for management applications to access any of the information in the model and thereby provides these applications with a unified view of thenetwork 10. - The SPECTROGRAPH
® user interface 18 provides a highly graphical multi-perspective view into the network model. The user interface enables the user to navigate through a landscape in which cables, networks, local area networks and even rooms show up as icons, and which icons indicate the health and performance characteristics of those elements. Many of these icons can be further queried for additional information. The main function of theuser interface 18 is to visually present to the user the model within thevirtual network machine 16. It allows the user to navigate freely within the network model, only limited by the access rights assigned by the network administrator. The information can be accessed at varying degrees of detail, from a macro overview, down to the level of the devices and the cables which connect them. In addition to its navigation functions, the SPECTROGRAPH user interface provides an alarm management facility, an event log window, a reporting facility, a find facility, and other features. - An example of the alarm log view provided by the
SPECTROGRAPH user interface 18 is illustrated in FIG. 2. Thealarm log view 23 may include anarea 20 for the listing of current alarms, and anarea 22 for displaying information pertaining to a selected alarm. A user, such as a system administrator or a technician, may select a particular alarm in the listing of current alarms to obtain more information. Amulti-function icon 24 representing the network device having the fault is displayed inarea 22, and one or more text fields 26 and 28 which provide information regarding the cause of the alarm and the status of the device. By selecting specified areas of theicon 24, the user can obtain further information regarding the device for which an alarm is registered. - Alternatively, instead of or in combination with the
user interface 18, information from thevirtual network machine 16 may be provided directly to another computer program, or may be provided to a user via electronic mail or a telephone message that is automatically transmitted. - One method for fault management in large communications networks is to use a “trouble-ticketing” system. This system provides a number of tools for use by network users, administrators, and repair and maintenance personnel. The basic data structure, a trouble-ticket, has a number of fields in which a user can enter data describing the parameters of an observed network fault. A trouble-ticket filled out by a user may then be transmitted by, for example, an electronic mail system to maintenance and repair personnel. A trouble-ticket describing a current network fault requiring attention or action is referred to as an outstanding trouble-ticket. When the network fault has been corrected, the solution to the problem, typically called a resolution, is entered into an appropriate data field in the trouble-ticket and the trouble-ticket is classified as being completed. The system stores completed trouble-tickets in memory and thus a library of such tickets is created, allowing users, administrators, and maintenance and repair personnel to refer to the same for assistance in determining solutions to future network faults.
- An example of a trouble-ticketing system is the ACTION REQUEST system, developed by Remedy Corporation, Mountain View, Calif., and sold by Cabletron Systems, Inc., Rochester, N.H. ARS Gateway™ is an application sold by Cabletron Systems, Inc. which incorporates the SPECTRUM and ACTION REQUEST systems, i.e., the ARS Gateway application receives fault information from the SPECTRUM system and automatically generates and processes a trouble-ticket. The ARS Gateway system is described in copending and commonly owned U.S. Ser. No. 08/023,972 filed Feb. 26, 1993 by Lundy Lewis, entitled “Method and Apparatus For Resolving Faults In Communications Networks,” which is hereby incorporated by reference in its entirety.
- As described earlier, however, each instance of the previously existing network management system manages only a single domain, and thus will correlate events only within the single domain to generate one or more inter-domain alarms. An improvement over these prior systems is the SPECTRUM Alarm Notification Manager (SANM), which utilizes policy-based filters to create an alarm notification policy that may apply to alarms received from several instances of a network management system. Such a system is described in copending and commonly owned U.S. Ser. No. 08/558,425 filed Nov. 16, 1995 by Arrowsmith et al., entitled “Method and Apparatus For Policy-Based Alarm Notification in a Distributed Network Management Environment,” which is hereby incorporated by reference in its entirety.
- FIG. 3 illustrates an embodiment of the invention in which intra-domain alarms are correlated and analyzed to provide inter-domain alarms, corrective actions, and other responses. A
communications network 10 is arranged into a plurality of domains—domain A, domain B, and domain C. Network management system (NMS) 11A manages only domain A viainterface 12A,NMS 11B manages only domain B via interface 12B, andNMS 11C manages only domain C viainterface 12C. TheNMSs 11A-C may be different instances of one type of NMS, or may be instances of different network management systems such as those described earlier. TheNMSs 11A-11C need not be directly connected to their respective domains A-C, but some path will exist for information transfer between eachNMS 11A-11C and its respective domain A-C. - The information transfer from the domains A-C to their
respective NMS 11A-11C typically includes messages regarding the status of network resources within the respective domain. For example, a network resource may be a device that includes built-in-test functions. When such functions indicate that the device may be faulty or degraded, a message is provided to the NMS. Additionally, some devices monitor network parameters such as throughput and error rate, and provide results to the NMS. The NMS may perform certain monitoring functions as well. Generally, a message provided from a network resource to an NMS may be referred to as a report, and a succession of such reports is typically referred to as an event stream. - As shown in FIG. 3, each
NMS 11A-11C is operatively coupled to themulti-domain manager 30, in order to provide messages to and receive responses back from themanager 30. In particular,NMS 11A monitors domain A viainterface 12A, producesintra-domain alarms 35A that are specific to domain A, and provides theintra-domain alarms 35A to themanager 30. Similarly,NMS 11B monitors domain B via interface 12B, produces intra-domain alarms 35B and provides them tomanager 30 andNMS 11C monitors domain C viainterface 12C, produces intra-domain alarms 35C and provides them tomanager 30. Themanager 30 correlates theintra-domain alarms 35A-35C and provides in responseinter-domain alarm responses 38A-38C to one or more of theNMSs 11A-11C. - According to one embodiment of the invention,
manager 30 includes analarm notifier 31, an inter-domainalarm correlation system 32, and aresponse interface 33.Alarm notifier 31 receives intra-domain alarms onlinks 35A-35C from theNMSs 11A-11C and provides them onlink 36 tocorrelation system 32.Correlation system 32 provides inter-domain responses onlink 37 toresponse interface 33, which in turn provides the inter-domain responses on one or more oflinks 38A-38C to therespective NMSs 11A-11C. - The inter-domain responses may include inter-domain alarms, commands, and requests for more information. An example of an inter-domain alarm is a notification that a router in domain A may be faulty or degraded, and thus may affect the throughput or other performance characteristics of domain B. An example of a command is a command to re-route data from domain A intended for domain B through a different router than the faulty or degraded router. A request for information may be generated by
correlation system 32 when, for example, an intra-domain alarm has been received, but a sufficient inter-domain alarm cannot be generated until additional information is received. Accordingly, the messages from domains A-C may also include responses to requests for information, which may or may not be alarms as previously defined. - The structure illustrated in FIG. 3 allows for event and alarm correlation to be performed at multiple levels of abstraction, and thus facilitates quick corrective action by
NMSs 11A-11C to some events, while also providing more highly-correlated inter-domain responses (e.g., from manager 30) to events that may be of a more complex nature. - FIG. 4A illustrates a multiple loop architecture (MLA) that facilitates multiple levels of coordination in network management. FIG. 4A is generalized to represent a system having inputs (network monitoring) and outputs (network control). A first (lower) level of coordination includes
operator 41 andoperator 42, which are coupled together to provide afirst control loop 43. With respect to FIG. 4A, the term “operator” may mean any entity that performs an aspect of control processing at a particular level. Such an operator may be an individual computer or software routine, specialized hardware, or a portion of software on a general purpose computer. -
Operators operators Operators second control loop 46 includesoperators Operators third control loop 49 includesoperators first loop 43, is simpler than higher level coordination and thus can be achieved in less time and with less resources. Lower level coordination may be referred to as reflexive behavior that generates short-term solutions, while higher level coordination may be referred to as deliberative behavior that generates longer-term solutions. - Each
control loop - The
second loop 46 may provide reaction to more complex problems and operates on increasingly abstract input such as signs and symbols. Tasks for thesecond loop 46 may include alarm correlation for a single domain of a network, where some alarms represent actual problems and other alarms are only apparent problems. Due to the information that thesecond control loop 46 contains regarding network resources of a single domain, it is possible to distinguish between actual problems and apparent problems to achieve effective alarm filtering. - The
third control loop 49 may provide reaction to problems that require more time as well as a higher class of information. An example of a task performed by thethird loop 49 is reasoning involved in deciding to re-allocate a host from domain A to domain B because a majority of the host's clients reside in domain B, thereby causing increased but unnecessary traffic on a link between domain A and domain B. - FIG. 4B shows an example of a single level of operation of the multi-loop architecture of FIG. 4A. The
single level 50, which may represent bothoperator 44 andoperator 45 of FIG. 4A, includes anabstraction agent 51, acoordination agent 52, and adecomposition agent 53. Thecoordination agent 52 evaluates network information N handed up from the level beneath and a task T handed down from the level above, and passes information (for example, a modified task) to thedecomposition agent 53 and passes network information (possibly modified) to theabstraction agent 51. Thedecomposition agent 53 receives the task information T, decomposes it, and transmits the resulting task information T″ to a coordination agent on the level beneath. Theabstraction agent 51 receives the network information N, abstracts it, and transmits the correlated network information N″ to a coordination agent on the level above. - The inputs to a given level L are network information (N) from next lower level L−1, and task information (T) from next higher
level L+ 1. N and T may be represented as state vectors wherein N is the current state of the environment/platform (such as an operating efficiency of a network domain) and T is the goal state. Here, thecoordination agent 52 computes the difference between N and T. A significant difference between N and T may denote a problem. The solutions to the problem, from the perspective of level L, are N′ and T′, where N′ is new network information and T′ is a new task (i.e. a solution). There exist four solution types, as shown in Table 2, based upon a result of the computation of the difference between N and T.TABLE 2 Solution Types N' T' Case 1: nil nil Case 2: nil non-nil Case 3: non-nil nil Case 4: non-nil non-nil - In
case 1, there is likely no problem, as exemplified by “nil” N′ and T′. Thus, N=N′ and T=T′. N is abstracted into N″ and transmitted to level L+1, and T′ is decomposed into T″ and transmitted to level L−1. - In
case 2, there may be a problem within the range of expertise of thesingle level 50. Thus, N=N′ and thecoordination agent 52 generates task T′=ƒ(T), where ƒ is a function which transforms T into T′, e.g. a lookup table. T′ is decomposed into T″ and transmitted to level L−1, and N′ is abstracted into N″ and passed to levelL+ 1. Note that T″ replaces the old task, as instructed by thecoordination agent 52. - In
case 3, there may be a problem that is beyond the range of expertise of thesingle level 50. Thus, thecoordination agent 52 generates N′=g(N) and T=T′, where g is a function which transforms N into N′ to yield, for example, additional network information. N′ is abstracted into N″ and transmitted to level L+1, and T′ is decomposed into T″ and transmitted to level L−1. Note that N″ contains an abstraction of N plus information relating to a problem perceived by thecoordination agent 52. - In
case 4, there may be a problem which thesingle level 50 can offer a partial (possibly incomplete) solution. Here, thecoordination agent 52 generates information N′= g(N) and task T′=ƒ(T).Case 4 exemplifies a situation in which two or more levels will have to contribute partial solutions to a problem that may not be effectively solved by any one level alone. - Other approaches may be implemented to perform functions similar to those described with respect to FIG. 4B, in order to provide a hierarchical network management system.
- FIG. 5 is a functional flow diagram illustrating different levels of correlation and response, similar to FIG. 4A, as applied to the
multi-domain manager 30 and any one instance of anetwork management system 11N. For inter-domain correlation, a plurality of network management systems, forexample systems 11A-11C may be implemented, but only asingle instance 11N is depicted in FIG. 5 for clarity. A first lower level of correlation and response includes intra-domainevent correlation operator 54 and intra-domainevent response operator 55, forming a first control loop. A second mid-level of correlation and response includes intra-domainalarm correlation operator 56 and intra-domainalarm response operator 57, forming a second control loop. The second control loop may require more time as well as more information from the network resources in the domain monitored by thenetwork management system 11N. Both the first and second control loops take place within one instance of anetwork management system 11N, and provide correlation and response for the single domain managed by thatNMS 11N. - A third high level of correlation and response includes inter-domain
alarm correlation operator 58 which may operate on the results ofintra-domain alarm correlation 56 from one or more instances of a network management system, andinter-domain response operator 59. The results of theresponse operator 59 are provided to the appropriate network management systems as discussed earlier, and may include inter-domain alarms, commands, and requests for additional information. Due to the hierarchial nature of the correlation disclosed herein, the multi-domain manager may receive intra-domain alarms, correlate them as necessary, and provide a single user with insight as to the status of several networks. - FIG. 6 is a flow chart of a method embodiment of the present invention. In FIG. 6, steps60-62 are typically performed by one instance (e.g., 11A of FIG. 3) of a single-domain network management system, and steps 63-64 are typically performed by a second instance (e.g., 11B of FIG. 3) of a single-domain network management system. Steps 65-68 are performed by the
multi-domain manager 30 shown in FIG. 3. In one embodiment, one single-domain NMS 11N may also contain themanager 30. - In
step 60, status information is received from a resource in a first domain, such as domain A in FIG. 3.NMS 11A may provide corrective action as shown instep 61, if there exists sufficient information upon which to determine such action. Instep 62, an intra-domain alarm is generated, which may be provided to a user in any manner previously described. This intra-domain alarm is also provided to themulti-domain manager 30. - In
step 63, status information is received from a resource in a second domain, such as domain B. In response,NMS 11B generates an intra-domain alarm in step 64. (Alternatively, lower level corrective action could take place as in step 61). - In
step 65, information in addition to the two intra-domain alarms may be requested and received by the manager; such action is not required. An inter-domain alarm is generated instep 66 by correlating the intra-domain alarms together and with any additional information. This inter-domain alarm may then be sent to users or to any appropriate NMS or individual network entities, as described below with respect to FIG. 7. - In
step 67, the inter-domain alarm is analyzed to determine any corrective action, and instep 68 such corrective action is implemented. Because a multi-domain manager has insight into the operation and structure of several domains, such corrective action may be more effective than corrective action determined only from a limited amount of information (i.e., available from a single domain). - FIG. 7 illustrates steps of a process performed by one particular embodiment of the inter-domain alarm correlation system32 (of FIG. 3). In
step 72, an intra-domain alarm is received, for example fromNMS 11A. Such an intra-domain alarm may represent a non-critical condition, for example a one-time event, or it may represent a severe condition that may soon impact other domains B, C of thenetwork 10. Accordingly, instep 74, the severity of the condition (represented by the intra-domain alarm) is determined. If the severity is sufficiently great, an inter-domain alarm is sent to some or all of the domains on thenetwork 10. In one approach, as shown instep 76, domains adjacent to domain A are determined, and instep 78 the inter-domain alarm is sent to theNMSs - An inter-domain alarm may include an indication of the severity of the condition which caused the alarm, in case any of the
NMSs - FIG. 8 shows a state transition diagram (STG) by which the severity of a condition may be determined for a single domain (“domain A”). FIG. 8 is simplified in that only three states are shown, and only with respect to one type of failure indication (“failure indication A”). Such an STG may be implemented within a single-domain network management system, for example11A in FIG. 3.
- In state1-1 (81), no failure indications have been received, and accordingly no alarms are sent. When a failure indication “M” is received from a device within domain A, the system is transitioned to state 1-2 (82). In order to reduce false alarms, for example if a non-critical transient condition caused the first failure indication “M” to be received, no alarm is sent while in state 1-2 (82). Additionally, if a certain time elapses (e.g., one minute) prior to receiving another subsequent failure indication of type “M”, then the system is transitioned back to state 1-1 (81). If instead, a subsequent failure indication “M” is received prior to the state 1-2 (82) timeout, then the system will transition to state 1-3 (83). In this example, state 1-3 (83) is indicative of a mild condition, so a mild domain A alarm “X” may be sent, as shown in
action 84. Alarm “X” is an intra-domain alarm, because it was generated from information regarding only a single domain A. Alarm “X” may be processed as indicated previously, but may also be sent to a multi-domain manager for further processing as described in more detail below. - From state1-3 (83), if no subsequent failure conditions are received prior to a state 1-3 timeout, then the system returns to state 1-1 (81). Alternatively, if a third failure indication “M” is received prior to a state 1-3 (93) timeout, then the system sends a strong domain A alarm “X” (action 85), and may also take additional action within domain A (action 86). The strong domain A alarm “X” may be similar to the mild domain A alarm “X” but with a different severity value, or may be an entirely different alarm, depending upon the diagnostic information regarding domain A. The corrective action is limited to devices managed by the network management system generating alarm “X,” however. Following such actions, the system returns to state 1-1 (81).
- FIG. 9 shows an STG for a domain different from the domain represented by FIG. 8, for example domain B in FIG. 3, managed by
NMS 11B. FIG. 9 is an example of a single-domain STG in which an alarm should be sent if a second type of a failure indication is received within a certain amount of time following a first type of a failure indication. - In FIG. 9, state2-1 (93) represents an initial condition. In response to a failure indication “N” from within domain B, the system transitions to state 2-2 (92). Subsequent failure indications “N” may cause the system to stay within state 2-2, and may also reset a timer which would otherwise return the system to state 2-1 (91) if no further failure indications “N” are received within a certain amount of time. If a failure indication “O” is received prior to a state 2-2 timeout, then domain B alarm “Y” is sent (action 93). Both failure indications “N” and “O” are generated from devices within domain B.
- FIG. 10 is an example of an inter-domain STG which uses the results of the STGs of FIGS.8-9. For example, the inter-domain STG of FIG. 10 may represent an implementation of the
inter-domain correlation system 32. Such an inter-domain STG has the capability of analyzing and responding to intra-domain alarms in conjunction with one another. Since the intra-domain alarms represent some previous analysis, the inter-domain STG provides insight into domains A and B which was not previously possible. - State I-1 (101) represents an initial condition of the inter-domain STG. In response to a mild alarm “X” (for example, as sent during
action 84 of FIG. 8), the system transitions to state I-2 (102). Subsequent mild alarms “X” will not change the state, but if an alarm “Y” is received (for example as sent duringaction 93 of FIG. 9), then a mild inter-domain alarm “Z” is generated (action 103). with previous systems, such an inter-domain alarm “Z” would not be possible, because no system used the results of the respective network management systems of two different domains. - If an alarm “Y” is received first while the system is in state I-1 (101), then the system transitions to state I-3 (104). Subsequent alarms “Y” do not change the state, but if a mild alarm “X” is received, then the mild inter-domain alarm “Z” will be sent (action 103). FIG. 10 does not show timeouts, but such timeouts as depicted in FIGS. 8-9 may also be applied to the inter-domain STG of FIG. 10.
- If a strong alarm “X” is received while the system is in state I-2 (102) or from the initial state I-1, then the system transitions to state I-4 (105). In this example, subsequent strong alarms “X” and mild alarms “X” do not change the state. However, if an alarm “Y” is received subsequent to a strong alarm “X”, then a strong inter-domain alarm “Z” is generated (action 106), and corrective action (107) may also be taken.
Such actions corrective action 107 may represent actions which would not have been taken were it not for the correlation of intra-domain alarm “X” with intra-domain alarm “Y”, because each of the inter-domain network management systems only have knowledge regarding devices within their respective domain. - In one embodiment, the alarm notifier31 (see FIG. 3) is the SPECTRUM Alarm Notification Manager (SANM) described above, and each
network management system 11A-11C is an instance of SPECTRUM. Theresponse interface 33 is the SPECTRUM Command Line Interface (CLI). Such a CLI facilitates commands, queries, and other responses to be provided to any appropriate instances of SPECTRUM. - Alternatively, the inter-domain
alarm correlation system 32 may be implemented as a state transition graph (STG) in the product NerveCenter, available from NetLabs Inc., 4920 El Camino Real, Los Altos, Calif. 94022. Alternatively, the inter-domainalarm correlation system 32 may be implemented in specially-designed hardware such as a state machine, or in any of several programming languages on a general purpose computer, or as a programmed general purpose computer itself. - For example, elements of the
multi-domain manager 30 may be implemented as software on a floppy disk, compact disk, or hard drive, which controls a computer, for example a general purpose computer such as a workstation, a mainframe or a personal computer, to perform the process steps disclosed in FIGS. 6-10. Such ageneral purpose computer 110, shown in FIG. 11, typically includes a central processing unit 112 (CPU) coupled to random access memory (RAM) 114 andprogram memory 116 via adata bus 118. Thegeneral purpose computer 110 may be connected to thenetwork 10 in order to receive reports, and may provide commands to devices on the network in order to control the network configuration. - Alternatively, the elements of the
multi-domain network manager 30 may be implemented as special purpose electronic hardware. Additionally, in either a hardware or software embodiment, the functions performed by the different elements within themulti-domain network manager 30 may be combined in varying arrangements of hardware and software. - Having thus described various illustrative embodiments of the invention, additional modifications and improvements will readily occur to those skilled in the art and are intended to be within the scope of the invention. Accordingly, the foregoing description is by way of example only, and not intended to be limiting.
Claims (14)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/811,748 US6430712B2 (en) | 1996-05-28 | 2001-03-19 | Method and apparatus for inter-domain alarm correlation |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/654,305 US5768501A (en) | 1996-05-28 | 1996-05-28 | Method and apparatus for inter-domain alarm correlation |
US09/094,428 US6000045A (en) | 1996-05-28 | 1998-06-08 | Method and apparatus for inter-domain alarm correlation |
US09/455,041 US6205563B1 (en) | 1996-05-28 | 1999-12-06 | Method and apparatus for inter-domain alarm correlation |
US09/811,748 US6430712B2 (en) | 1996-05-28 | 2001-03-19 | Method and apparatus for inter-domain alarm correlation |
Related Parent Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/094,428 Continuation US6000045A (en) | 1996-05-28 | 1998-06-08 | Method and apparatus for inter-domain alarm correlation |
US09/455,041 Continuation US6205563B1 (en) | 1996-05-28 | 1999-12-06 | Method and apparatus for inter-domain alarm correlation |
Publications (2)
Publication Number | Publication Date |
---|---|
US20010013107A1 true US20010013107A1 (en) | 2001-08-09 |
US6430712B2 US6430712B2 (en) | 2002-08-06 |
Family
ID=24624307
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/654,305 Expired - Lifetime US5768501A (en) | 1996-05-28 | 1996-05-28 | Method and apparatus for inter-domain alarm correlation |
US09/094,428 Expired - Lifetime US6000045A (en) | 1996-05-28 | 1998-06-08 | Method and apparatus for inter-domain alarm correlation |
US09/455,041 Expired - Lifetime US6205563B1 (en) | 1996-05-28 | 1999-12-06 | Method and apparatus for inter-domain alarm correlation |
US09/811,748 Expired - Lifetime US6430712B2 (en) | 1996-05-28 | 2001-03-19 | Method and apparatus for inter-domain alarm correlation |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/654,305 Expired - Lifetime US5768501A (en) | 1996-05-28 | 1996-05-28 | Method and apparatus for inter-domain alarm correlation |
US09/094,428 Expired - Lifetime US6000045A (en) | 1996-05-28 | 1998-06-08 | Method and apparatus for inter-domain alarm correlation |
US09/455,041 Expired - Lifetime US6205563B1 (en) | 1996-05-28 | 1999-12-06 | Method and apparatus for inter-domain alarm correlation |
Country Status (1)
Country | Link |
---|---|
US (4) | US5768501A (en) |
Cited By (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030014462A1 (en) * | 2001-06-08 | 2003-01-16 | Bennett Andrew Jonathan | Method and system for efficient distribution of network event data |
US20040024865A1 (en) * | 2002-07-30 | 2004-02-05 | Jiandong Huang | Method and apparatus for outage measurement |
US20040208175A1 (en) * | 2003-04-17 | 2004-10-21 | Mccabe Alan J. | Linking autonomous systems with dual premise routing domains |
US20040221296A1 (en) * | 2003-03-18 | 2004-11-04 | Renesys Corporation | Methods and systems for monitoring network routing |
US20040223461A1 (en) * | 2000-06-16 | 2004-11-11 | Ciena Corporation. | Method and apparatus for aggregating alarms and faults of a communications network |
US20040230868A1 (en) * | 2003-03-17 | 2004-11-18 | Sabet Sameh A. | System and method for fault diagnosis using distributed alarm correlation |
US20040233859A1 (en) * | 2001-05-18 | 2004-11-25 | Martin Daniel J. | Method and system for determining network characteristics using routing protocols |
US20040249828A1 (en) * | 2003-06-05 | 2004-12-09 | International Business Machines Corporation | Automated infrastructure audit system |
US20050027845A1 (en) * | 2000-01-03 | 2005-02-03 | Peter Secor | Method and system for event impact analysis |
US20050157654A1 (en) * | 2000-10-12 | 2005-07-21 | Farrell Craig A. | Apparatus and method for automated discovery and monitoring of relationships between network elements |
US20050216584A1 (en) * | 2004-03-24 | 2005-09-29 | Nortel Networks Limited | Method and apparatus for collecting management information on a communication network |
US20050286685A1 (en) * | 2001-08-10 | 2005-12-29 | Nikola Vukovljak | System and method for testing multiple dial-up points in a communications network |
EP1635506A1 (en) * | 2004-09-13 | 2006-03-15 | Avaya Technology Corp. | Distributed expert system for automated problem solution in a communication system |
WO2007063445A2 (en) * | 2005-12-01 | 2007-06-07 | Telefonaktiebolaget L M Ericsson (Publ) | Method and management agent for event notifications correlation |
US20070220368A1 (en) * | 2006-02-14 | 2007-09-20 | Jaw Link C | Data-centric monitoring method |
US7418490B1 (en) * | 2003-12-29 | 2008-08-26 | Sun Microsystems, Inc. | System using multiple sets of device management policies for managing network devices connected on different network interfaces |
EP1976185A1 (en) * | 2007-03-27 | 2008-10-01 | Nokia Siemens Networks Gmbh & Co. Kg | Operating network entities in a communication system comprising a management network with agent and management levels |
US20080276130A1 (en) * | 2007-05-01 | 2008-11-06 | Almoustafa Ahmed M | Distributed logging apparatus system and method |
WO2009033500A1 (en) * | 2007-09-14 | 2009-03-19 | Nec Europe Ltd. | Method and system for optimizing network performances |
US20110154099A1 (en) * | 2009-12-18 | 2011-06-23 | Fujitsu Network Communications, Inc. | Method and system for masking defects within a network |
US20110153804A1 (en) * | 2009-12-18 | 2011-06-23 | Fujitsu Network Communications, Inc. | Method and system for reporting defects within a network |
US20110161741A1 (en) * | 2009-12-28 | 2011-06-30 | International Business Machines Corporation | Topology based correlation of threshold crossing alarms |
WO2012041555A1 (en) * | 2010-09-30 | 2012-04-05 | Telefonaktiebolaget L M Ericsson (Publ) | Method for determining a severity of a network incident |
US20120159519A1 (en) * | 2010-12-17 | 2012-06-21 | Fujitsu Limited | Event dependency management apparatus and event dependency management method |
US20140057626A1 (en) * | 2012-08-24 | 2014-02-27 | Oceus Networks Inc. | Mobile cellular networks |
US9198221B2 (en) | 2012-08-24 | 2015-11-24 | Oceus Networks Inc. | Mobile cellular networks |
US9226192B2 (en) | 2013-04-29 | 2015-12-29 | Oceus Networks Inc. | Mobile cellular network backhaul |
WO2016093861A1 (en) * | 2014-12-12 | 2016-06-16 | Nokia Solutions And Networks Oy | Alarm correlation in network function virtualization environment |
US9628354B2 (en) | 2003-03-18 | 2017-04-18 | Dynamic Network Services, Inc. | Methods and systems for monitoring network routing |
US9686238B1 (en) | 2016-07-07 | 2017-06-20 | Oceus Networks Inc. | Secure network enrollment |
US9924427B2 (en) | 2016-07-07 | 2018-03-20 | Oceus Networks Inc. | Network backhaul access |
US10172078B2 (en) | 2017-03-31 | 2019-01-01 | Oceus Networks Inc. | Targeted user equipment-base station communication link |
WO2020069739A1 (en) * | 2018-10-04 | 2020-04-09 | Telefonaktiebolaget Lm Ericsson (Publ) | Network node and method performed therein for handling operations in a set of communication networks |
USRE48065E1 (en) | 2012-05-18 | 2020-06-23 | Dynamic Network Services, Inc. | Path reconstruction and interconnection modeling (PRIM) |
US10805144B1 (en) * | 2019-06-18 | 2020-10-13 | Cisco Technology, Inc. | Monitoring interactions between entities in a network by an agent for particular types of interactions and indexing and establishing relationships of the components of each interaction |
US10873891B2 (en) | 2016-07-06 | 2020-12-22 | Oceus Networks, Llc | Secure network rollover |
US11246031B2 (en) | 2018-08-15 | 2022-02-08 | Oceus Networks, Llc | Disguising UE communications in a cellular network |
US20230069434A1 (en) * | 2021-08-31 | 2023-03-02 | Juniper Networks, Inc. | Identifying root cause of failures through detection of network scope failures |
Families Citing this family (268)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6515968B1 (en) | 1995-03-17 | 2003-02-04 | Worldcom, Inc. | Integrated interface for real time web based viewing of telecommunications network call traffic |
US6032184A (en) * | 1995-12-29 | 2000-02-29 | Mci Worldcom, Inc. | Integrated interface for Web based customer care and trouble management |
US6859783B2 (en) | 1995-12-29 | 2005-02-22 | Worldcom, Inc. | Integrated interface for web based customer care and trouble management |
US5768501A (en) * | 1996-05-28 | 1998-06-16 | Cabletron Systems | Method and apparatus for inter-domain alarm correlation |
US8621032B2 (en) * | 1996-07-18 | 2013-12-31 | Ca, Inc. | Method and apparatus for intuitively administering networked computer systems |
US7342581B2 (en) | 1996-07-18 | 2008-03-11 | Computer Associates Think, Inc. | Method and apparatus for displaying 3-D state indicators |
US7680879B2 (en) * | 1996-07-18 | 2010-03-16 | Computer Associates Think, Inc. | Method and apparatus for maintaining data integrity across distributed computer systems |
US5958012A (en) * | 1996-07-18 | 1999-09-28 | Computer Associates International, Inc. | Network management system using virtual reality techniques to display and simulate navigation to network components |
GB2318479B (en) * | 1996-10-21 | 2001-04-04 | Northern Telecom Ltd | Problem model for alarm correlation |
US7249344B1 (en) | 1996-10-31 | 2007-07-24 | Citicorp Development Center, Inc. | Delivery of financial services to remote devices |
US5867153A (en) | 1996-10-30 | 1999-02-02 | Transaction Technology, Inc. | Method and system for automatically harmonizing access to a software application program via different access devices |
US7668781B2 (en) * | 1996-10-31 | 2010-02-23 | Citicorp Development Center, Inc. | Global method and system for providing enhanced transactional functionality through a customer terminal |
US8112330B1 (en) | 1997-08-07 | 2012-02-07 | Citibank Development Center, Inc. | System and method for delivering financial services |
US6175931B1 (en) * | 1997-01-31 | 2001-01-16 | Hewlett-Packard Company | Global hard error distribution using the SCI interconnect |
US6115362A (en) * | 1997-03-28 | 2000-09-05 | Cabletron Systems, Inc. | Method and apparatus for determining frame relay connections |
FR2762951B1 (en) * | 1997-05-02 | 1999-07-23 | Alsthom Cge Alcatel | METHOD FOR TRANSMITTING A NOTIFICATION IN A NETWORK COMPRISING A NOTIFICATION SERVICE AND A NETWORK FOR IMPLEMENTING IT |
US6134615A (en) * | 1997-05-13 | 2000-10-17 | Micron Electronics, Inc. | System for facilitating the replacement or insertion of devices in a computer system through the use of a graphical user interface |
US6219711B1 (en) | 1997-05-13 | 2001-04-17 | Micron Electronics, Inc. | Synchronous communication interface |
US6553416B1 (en) * | 1997-05-13 | 2003-04-22 | Micron Technology, Inc. | Managing computer system alerts |
US6425006B1 (en) | 1997-05-13 | 2002-07-23 | Micron Technology, Inc. | Alert configurator and manager |
US6266694B1 (en) * | 1997-06-19 | 2001-07-24 | Nortel Networks Limited | Architecture for network manager |
US7315893B2 (en) * | 1997-07-15 | 2008-01-01 | Computer Associates Think, Inc. | Method and apparatus for filtering messages based on context |
US20030023721A1 (en) * | 1997-07-15 | 2003-01-30 | Computer Associates Think, Inc. | Method and apparatus for generating context-descriptive messages |
US20030018771A1 (en) * | 1997-07-15 | 2003-01-23 | Computer Associates Think, Inc. | Method and apparatus for generating and recognizing speech as a user interface element in systems and network management |
US6604137B2 (en) * | 1997-07-31 | 2003-08-05 | Mci Communications Corporation | System and method for verification of remote spares in a communications network when a network outage occurs |
US7502752B1 (en) * | 1997-08-07 | 2009-03-10 | Citicorp Development Center, Inc. | System and method for delivering financial services |
US5960421A (en) * | 1997-08-20 | 1999-09-28 | Bea Systems, Inc. | Service interface repository internationalization |
US5931900A (en) * | 1997-08-25 | 1999-08-03 | I2 Technologies, Inc. | System and process for inter-domain interaction across an inter-domain connectivity plane |
US6473407B1 (en) | 1997-09-05 | 2002-10-29 | Worldcom, Inc. | Integrated proxy interface for web based alarm management tools |
US6714979B1 (en) | 1997-09-26 | 2004-03-30 | Worldcom, Inc. | Data warehousing infrastructure for web based reporting tool |
US6763376B1 (en) | 1997-09-26 | 2004-07-13 | Mci Communications Corporation | Integrated customer interface system for communications network management |
US6381644B2 (en) | 1997-09-26 | 2002-04-30 | Mci Worldcom, Inc. | Integrated proxy interface for web based telecommunications network management |
US7225249B1 (en) | 1997-09-26 | 2007-05-29 | Mci, Llc | Integrated systems for providing communications network management services and interactive generating invoice documents |
US6745229B1 (en) | 1997-09-26 | 2004-06-01 | Worldcom, Inc. | Web based integrated customer interface for invoice reporting |
US7058600B1 (en) * | 1997-09-26 | 2006-06-06 | Mci, Inc. | Integrated proxy interface for web based data management reports |
US6574661B1 (en) | 1997-09-26 | 2003-06-03 | Mci Communications Corporation | Integrated proxy interface for web based telecommunication toll-free network management using a network manager for downloading a call routing tree to client |
US6012149A (en) * | 1997-09-30 | 2000-01-04 | Bull Hn Information Systems Inc. | Computer system with polymorphic fault processing |
JP3351318B2 (en) * | 1997-11-07 | 2002-11-25 | 株式会社日立製作所 | Computer system monitoring method |
US6055574A (en) * | 1998-03-10 | 2000-04-25 | Unisys Corporation | Method of providing a service through a server with a virtual single network address |
US6148338A (en) * | 1998-04-03 | 2000-11-14 | Hewlett-Packard Company | System for logging and enabling ordered retrieval of management events |
US6973668B1 (en) | 1998-06-30 | 2005-12-06 | Cisco Technology, Inc. | Method and apparatus for locating a faulty component in a cable television system having cable modems |
US6588016B1 (en) | 1998-06-30 | 2003-07-01 | Cisco Technology, Inc. | Method and apparatus for locating a faulty component in a cable television system having cable modems |
US6594305B1 (en) | 1998-06-30 | 2003-07-15 | Cisco Technology, Inc. | Media access layer ping protocol for diagnosing cable modem links |
DE19831825C2 (en) * | 1998-07-15 | 2000-06-08 | Siemens Ag | Process and communication system for handling alarms through a management network with multiple management levels |
US6401119B1 (en) * | 1998-09-18 | 2002-06-04 | Ics Intellegent Communication Software Gmbh | Method and system for monitoring and managing network condition |
US6253339B1 (en) * | 1998-10-28 | 2001-06-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Alarm correlation in a large communications network |
US6321338B1 (en) * | 1998-11-09 | 2001-11-20 | Sri International | Network surveillance |
GB9828582D0 (en) * | 1998-12-23 | 1999-02-17 | Northern Telecom Ltd | Communication system architecture apparatus and method of call handling |
US6393474B1 (en) * | 1998-12-31 | 2002-05-21 | 3Com Corporation | Dynamic policy management apparatus and method using active network devices |
FR2788396B1 (en) * | 1999-01-11 | 2001-02-09 | Sagem | DEVICE FOR DISCRIMINATING DEFECTS IN A DIGITAL LEASED LINK |
US6425008B1 (en) | 1999-02-16 | 2002-07-23 | Electronic Data Systems Corporation | System and method for remote management of private networks having duplicate network addresses |
DE69933919T2 (en) * | 1999-04-07 | 2007-06-06 | Lucent Technologies Inc. | Filtering of a secondary alarm |
US6915457B1 (en) * | 1999-04-23 | 2005-07-05 | Nortel Networks Limited | Apparatus and method for monitoring messages forwarded between applications |
US6707795B1 (en) | 1999-04-26 | 2004-03-16 | Nortel Networks Limited | Alarm correlation method and system |
US6918059B1 (en) * | 1999-04-28 | 2005-07-12 | Universal Music Group | Method and system for handling errors in a distributed computer system |
WO2000068824A1 (en) | 1999-05-10 | 2000-11-16 | 3Com Corporation | Method and system for network management |
EP1190342A2 (en) | 1999-05-24 | 2002-03-27 | Aprisma Management Technologies, Inc. | Service level management |
US6603742B1 (en) | 1999-06-02 | 2003-08-05 | Sun Microsystems, Inc. | Network reconfiguration |
US6791939B1 (en) | 1999-06-02 | 2004-09-14 | Sun Microsystems, Inc. | Dynamic generation of deadlock-free routings |
US6584073B1 (en) | 1999-06-02 | 2003-06-24 | Sun Microsystems, Inc. | Network topologies |
US6631421B1 (en) * | 1999-06-02 | 2003-10-07 | Sun Microsystems, Inc. | Recursive partitioning of networks |
US6567856B1 (en) | 1999-06-02 | 2003-05-20 | Sun Microsystems, Inc. | Deadlock-free routing |
US6408407B1 (en) * | 1999-06-03 | 2002-06-18 | Ncr Corporation | Methods and apparatus for delegated error handling |
US6968371B1 (en) * | 1999-06-23 | 2005-11-22 | Clearwire Corporation | Design for scalable network management systems |
US6513129B1 (en) * | 1999-06-30 | 2003-01-28 | Objective Systems Integrators, Inc. | System and method for managing faults using a gateway |
US6636983B1 (en) | 1999-10-07 | 2003-10-21 | Andrew E. Levi | Method and system for uniform resource locator status tracking |
US6833787B1 (en) | 1999-10-07 | 2004-12-21 | Asap Software Express, Inc. | Method and system for device tracking |
US6658585B1 (en) | 1999-10-07 | 2003-12-02 | Andrew E. Levi | Method and system for simple network management protocol status tracking |
US6658586B1 (en) * | 1999-10-07 | 2003-12-02 | Andrew E. Levi | Method and system for device status tracking |
US6477667B1 (en) | 1999-10-07 | 2002-11-05 | Critical Devices, Inc. | Method and system for remote device monitoring |
DE19949531A1 (en) * | 1999-10-14 | 2001-04-19 | Deutsche Telekom Ag | Device for controlling a telecommunication system |
US7289994B2 (en) * | 1999-10-18 | 2007-10-30 | Fisher-Rosemount Systems, Inc. | Interconnected zones within a process control system |
JP3875436B2 (en) * | 1999-10-28 | 2007-01-31 | 富士通株式会社 | Network management apparatus and recording medium |
US6876991B1 (en) | 1999-11-08 | 2005-04-05 | Collaborative Decision Platforms, Llc. | System, method and computer program product for a collaborative decision platform |
US8271336B2 (en) | 1999-11-22 | 2012-09-18 | Accenture Global Services Gmbh | Increased visibility during order management in a network-based supply chain environment |
US6606744B1 (en) | 1999-11-22 | 2003-08-12 | Accenture, Llp | Providing collaborative installation management in a network-based supply chain environment |
US7124101B1 (en) | 1999-11-22 | 2006-10-17 | Accenture Llp | Asset tracking in a network-based supply chain environment |
US8032409B1 (en) | 1999-11-22 | 2011-10-04 | Accenture Global Services Limited | Enhanced visibility during installation management in a network-based supply chain environment |
US6671818B1 (en) * | 1999-11-22 | 2003-12-30 | Accenture Llp | Problem isolation through translating and filtering events into a standard object format in a network based supply chain |
US7716077B1 (en) | 1999-11-22 | 2010-05-11 | Accenture Global Services Gmbh | Scheduling and planning maintenance and service in a network-based supply chain environment |
US7130807B1 (en) | 1999-11-22 | 2006-10-31 | Accenture Llp | Technology sharing during demand and supply planning in a network-based supply chain environment |
US6901582B1 (en) | 1999-11-24 | 2005-05-31 | Quest Software, Inc. | Monitoring system for monitoring the performance of an application |
US6883120B1 (en) * | 1999-12-03 | 2005-04-19 | Network Appliance, Inc. | Computer assisted automatic error detection and diagnosis of file servers |
FR2802676B1 (en) * | 1999-12-16 | 2002-02-08 | Bull Sa | METHOD AND DEVICE FOR DEPLOYING A DISTRIBUTED SUPERVISION |
US7139728B2 (en) * | 1999-12-30 | 2006-11-21 | Rod Rigole | Systems and methods for online selection of service providers and management of service accounts |
US7197546B1 (en) * | 2000-03-07 | 2007-03-27 | Lucent Technologies Inc. | Inter-domain network management system for multi-layer networks |
US6829734B1 (en) * | 2000-04-04 | 2004-12-07 | International Business Machines Corporation | Method for discovering problem resolutions in a free form computer helpdesk data set |
US6604208B1 (en) * | 2000-04-07 | 2003-08-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Incremental alarm correlation method and apparatus |
US7111205B1 (en) * | 2000-04-18 | 2006-09-19 | Siemens Communications, Inc. | Method and apparatus for automatically reporting of faults in a communication network |
US6643802B1 (en) * | 2000-04-27 | 2003-11-04 | Ncr Corporation | Coordinated multinode dump collection in response to a fault |
US7500143B2 (en) * | 2000-05-05 | 2009-03-03 | Computer Associates Think, Inc. | Systems and methods for managing and analyzing faults in computer networks |
US7237138B2 (en) * | 2000-05-05 | 2007-06-26 | Computer Associates Think, Inc. | Systems and methods for diagnosing faults in computer networks |
AU2001261275A1 (en) * | 2000-05-05 | 2001-11-20 | Aprisma Management Technologies, Inc. | Systems and methods for isolating faults in computer networks |
AU2001261258A1 (en) * | 2000-05-05 | 2001-11-20 | Aprisma Management Technologies, Inc. | Help desk systems and methods for use with communications networks |
US7752024B2 (en) * | 2000-05-05 | 2010-07-06 | Computer Associates Think, Inc. | Systems and methods for constructing multi-layer topological models of computer networks |
US7225244B2 (en) * | 2000-05-20 | 2007-05-29 | Ciena Corporation | Common command interface |
US6983362B1 (en) | 2000-05-20 | 2006-01-03 | Ciena Corporation | Configurable fault recovery policy for a computer system |
US6715097B1 (en) | 2000-05-20 | 2004-03-30 | Equipe Communications Corporation | Hierarchical fault management in computer systems |
US6718481B1 (en) * | 2000-05-26 | 2004-04-06 | Emc Corporation | Multiple hierarichal/peer domain file server with domain based, cross domain cooperative fault handling mechanisms |
US7130261B1 (en) * | 2000-05-31 | 2006-10-31 | Siemens Communications, Inc. | Hierarchical dependability for open distributed environments |
AU2001268134A1 (en) * | 2000-06-05 | 2001-12-17 | Mci Worldcom, Inc. | Centralized multi-domain server for network management |
US6694364B1 (en) * | 2000-06-16 | 2004-02-17 | Cisco Technology, Inc. | System and method for suppressing out-of-order side-effect alarms in heterogeneous integrated wide area data and telecommunication networks |
US6748432B1 (en) * | 2000-06-16 | 2004-06-08 | Cisco Technology, Inc. | System and method for suppressing side-effect alarms in heterogenoeus integrated wide area data and telecommunication networks |
US7769847B2 (en) * | 2000-07-13 | 2010-08-03 | Computer Associates Think, Inc. | Method and apparatus for a comprehensive network management system |
AU2001280536A1 (en) * | 2000-07-13 | 2002-01-30 | Aprisma Management Technologies, Inc. | Method and apparatus for automated service provisioning across multiple networking technologies |
DE10035966A1 (en) * | 2000-07-24 | 2002-02-21 | Siemens Ag | Interference suppression procedure for a higher-level NMC by correlating alarms with results of automatic tests |
JP5085831B2 (en) * | 2000-07-27 | 2012-11-28 | オラクル・インターナショナル・コーポレイション | System and method for request concentration and load balancing |
US6901530B2 (en) * | 2000-08-01 | 2005-05-31 | Qwest Communications International, Inc. | Proactive repair process in the xDSL network (with a VDSL focus) |
US7058707B1 (en) | 2000-08-01 | 2006-06-06 | Qwest Communications International, Inc. | Performance modeling in a VDSL network |
WO2002023808A2 (en) * | 2000-09-15 | 2002-03-21 | Cymtec Systems, Inc. | Network management system |
US7627665B2 (en) | 2000-09-28 | 2009-12-01 | Barker Geoffrey T | System and method for providing configurable security monitoring utilizing an integrated information system |
US8392552B2 (en) * | 2000-09-28 | 2013-03-05 | Vig Acquisitions Ltd., L.L.C. | System and method for providing configurable security monitoring utilizing an integrated information system |
AU2001296925A1 (en) | 2000-09-28 | 2002-04-08 | Vigilos, Inc. | Method and process for configuring a premises for monitoring |
WO2002027704A1 (en) * | 2000-09-28 | 2002-04-04 | Vigilos, Inc. | System and method for dynamic interaction with remote devices |
ATE379897T1 (en) * | 2000-10-17 | 2007-12-15 | Computer Ass Think Inc | METHOD AND APPARATUS FOR SELECTIVELY DISPLAYING LAYERED NETWORK DIAGRAM |
US20020147809A1 (en) * | 2000-10-17 | 2002-10-10 | Anders Vinberg | Method and apparatus for selectively displaying layered network diagrams |
US7043661B2 (en) * | 2000-10-19 | 2006-05-09 | Tti-Team Telecom International Ltd. | Topology-based reasoning apparatus for root-cause analysis of network faults |
US7379994B2 (en) * | 2000-10-26 | 2008-05-27 | Metilinx | Aggregate system resource analysis including correlation matrix and metric-based analysis |
US20030061061A1 (en) * | 2000-10-27 | 2003-03-27 | Cox Earl D. | Uniform data model |
US7225467B2 (en) | 2000-11-15 | 2007-05-29 | Lockheed Martin Corporation | Active intrusion resistant environment of layered object and compartment keys (airelock) |
US7213265B2 (en) | 2000-11-15 | 2007-05-01 | Lockheed Martin Corporation | Real time active network compartmentalization |
US7383191B1 (en) * | 2000-11-28 | 2008-06-03 | International Business Machines Corporation | Method and system for predicting causes of network service outages using time domain correlation |
KR100346185B1 (en) * | 2000-12-01 | 2002-07-26 | 삼성전자 주식회사 | System and method for managing alarm in network management system |
US7050391B1 (en) | 2000-12-22 | 2006-05-23 | Turin Networks | Method and apparatus for efficient link redundancy |
US20040205689A1 (en) * | 2000-12-29 | 2004-10-14 | Ellens Christian C. | System and method for managing a component-based system |
US7797409B1 (en) * | 2001-01-26 | 2010-09-14 | Sobha Renaissance Information Technology | System and method for managing a communication network utilizing state-based polling |
US20020124201A1 (en) * | 2001-03-01 | 2002-09-05 | International Business Machines Corporation | Method and system for log repair action handling on a logically partitioned multiprocessing system |
US20020124214A1 (en) * | 2001-03-01 | 2002-09-05 | International Business Machines Corporation | Method and system for eliminating duplicate reported errors in a logically partitioned multiprocessing system |
US6966015B2 (en) * | 2001-03-22 | 2005-11-15 | Micromuse, Ltd. | Method and system for reducing false alarms in network fault management systems |
US7461369B2 (en) * | 2001-03-30 | 2008-12-02 | Bmc Software, Inc. | Java application response time analyzer |
US7506047B2 (en) * | 2001-03-30 | 2009-03-17 | Bmc Software, Inc. | Synthetic transaction monitor with replay capability |
US7792948B2 (en) * | 2001-03-30 | 2010-09-07 | Bmc Software, Inc. | Method and system for collecting, aggregating and viewing performance data on a site-wide basis |
US6782350B1 (en) | 2001-04-27 | 2004-08-24 | Blazent, Inc. | Method and apparatus for managing resources |
GB0112781D0 (en) * | 2001-05-25 | 2001-07-18 | Global Continuity Plc | Method for rapid recovery from a network file server failure |
US6999468B2 (en) * | 2001-06-04 | 2006-02-14 | Turin Networks | Method and apparatus for line and path selection within SONET/SDH based networks |
EP1253747A1 (en) * | 2001-07-11 | 2002-10-30 | Agilent Technologies, Inc. (a Delaware corporation) | Network management system |
US7516208B1 (en) | 2001-07-20 | 2009-04-07 | International Business Machines Corporation | Event database management method and system for network event reporting system |
US20030041167A1 (en) * | 2001-08-15 | 2003-02-27 | International Business Machines Corporation | Method and system for managing secure geographic boundary resources within a network management framework |
EP1286498A1 (en) * | 2001-08-21 | 2003-02-26 | Alcatel | Method, service - agent and network management system for operating a telecommunications network |
US20030061326A1 (en) * | 2001-09-25 | 2003-03-27 | Gilbert Gary L. | Managing one or more domains in a system |
US7302700B2 (en) | 2001-09-28 | 2007-11-27 | Juniper Networks, Inc. | Method and apparatus for implementing a layer 3/layer 7 firewall in an L2 device |
WO2003036914A1 (en) * | 2001-10-25 | 2003-05-01 | General Dynamics Government Systems Corporation | A method and system for modeling, analysis and display of network security events |
US6810496B1 (en) * | 2001-11-07 | 2004-10-26 | Ciena Corporation | System and method for troubleshooting a network |
US7437450B1 (en) | 2001-11-30 | 2008-10-14 | Cisco Technology Inc. | End-to-end performance tool and method for monitoring electronic-commerce transactions |
US7197558B1 (en) * | 2001-12-17 | 2007-03-27 | Bellsouth Intellectual Property Corp. | Methods and systems for network element fault information processing |
US7099879B2 (en) * | 2001-12-21 | 2006-08-29 | Hewlett-Packard Development Company, L.P. | Real-time monitoring of service performance through the use of relational database calculation clusters |
US6848062B1 (en) * | 2001-12-21 | 2005-01-25 | Ciena Corporation | Mesh protection service in a communications network |
US7363368B2 (en) | 2001-12-24 | 2008-04-22 | International Business Machines Corporation | System and method for transaction recording and playback |
US20040153692A1 (en) * | 2001-12-28 | 2004-08-05 | O'brien Michael | Method for managing faults it a computer system enviroment |
US7127441B2 (en) * | 2002-01-03 | 2006-10-24 | Scott Abram Musman | System and method for using agent-based distributed case-based reasoning to manage a computer network |
US6862698B1 (en) * | 2002-01-22 | 2005-03-01 | Cisco Technology, Inc. | Method of labeling alarms to facilitate correlating alarms in a telecommunications network |
CA2369351A1 (en) * | 2002-01-24 | 2003-07-24 | Alcatel Canada Inc. | System and method for providing error analysis and correlation in a network element |
US7480715B1 (en) * | 2002-01-25 | 2009-01-20 | Vig Acquisitions Ltd., L.L.C. | System and method for performing a predictive threat assessment based on risk factors |
US7043549B2 (en) * | 2002-01-31 | 2006-05-09 | International Business Machines Corporation | Method and system for probing in a network environment |
US7269651B2 (en) * | 2002-09-26 | 2007-09-11 | International Business Machines Corporation | E-business operations measurements |
US8086720B2 (en) | 2002-01-31 | 2011-12-27 | International Business Machines Corporation | Performance reporting in a network environment |
US8527620B2 (en) | 2003-03-06 | 2013-09-03 | International Business Machines Corporation | E-business competitive measurements |
US7412502B2 (en) | 2002-04-18 | 2008-08-12 | International Business Machines Corporation | Graphics for end to end component mapping and problem-solving in a network environment |
US7047291B2 (en) * | 2002-04-11 | 2006-05-16 | International Business Machines Corporation | System for correlating events generated by application and component probes when performance problems are identified |
US20030167335A1 (en) * | 2002-03-04 | 2003-09-04 | Vigilos, Inc. | System and method for network-based communication |
US20030206172A1 (en) * | 2002-03-05 | 2003-11-06 | Vigilos, Inc. | System and method for the asynchronous collection and management of video data |
US20030228059A1 (en) * | 2002-06-06 | 2003-12-11 | Atul Khanduri | Data collator for a plurality of asynchronous/synchronous data generation entities |
US9917883B2 (en) | 2002-06-13 | 2018-03-13 | Throughputer, Inc. | Direct binary file transfer based network management system free of messaging, commands and data format conversions |
US20080117068A1 (en) * | 2006-11-16 | 2008-05-22 | Mark Henrik Sandstrom | Intelligent Network Alarm Status Monitoring |
FR2841340B1 (en) * | 2002-06-19 | 2005-05-20 | Eurocopter France | DEVICE FOR ASSISTING THE LOCATION OF FAILURE OF A COMPLEX SYSTEM |
US7580998B2 (en) * | 2002-08-14 | 2009-08-25 | Alcatel-Lucent Canada Inc. | Method for describing problems in a telecommunications network |
US7069512B2 (en) * | 2002-10-08 | 2006-06-27 | Overture Networks, Inc. | Command line interface with indication of network element status |
CN100450008C (en) * | 2002-10-22 | 2009-01-07 | 华为技术有限公司 | Processing method of communication network warning and relatively analysis management device |
US7146643B2 (en) * | 2002-10-29 | 2006-12-05 | Lockheed Martin Corporation | Intrusion detection accelerator |
US7080094B2 (en) * | 2002-10-29 | 2006-07-18 | Lockheed Martin Corporation | Hardware accelerated validating parser |
US7962589B1 (en) * | 2002-11-07 | 2011-06-14 | Cisco Technology, Inc. | Method and apparatus for providing notification of network alarms using a plurality of distributed layers |
US7734637B2 (en) * | 2002-12-05 | 2010-06-08 | Borland Software Corporation | Method and system for automatic detection of monitoring data sources |
US7454761B1 (en) | 2002-12-20 | 2008-11-18 | Cisco Technology, Inc. | Method and apparatus for correlating output of distributed processes |
JP4318643B2 (en) * | 2002-12-26 | 2009-08-26 | 富士通株式会社 | Operation management method, operation management apparatus, and operation management program |
US20040205184A1 (en) * | 2003-03-06 | 2004-10-14 | International Business Machines Corporation | E-business operations measurements reporting |
US7137041B2 (en) * | 2003-06-20 | 2006-11-14 | International Business Machines Corporation | Methods, systems and computer program products for resolving problems in an application program utilizing a situational representation of component status |
US7500144B2 (en) * | 2003-06-20 | 2009-03-03 | International Business Machines Corporation | Resolving problems in a business process utilizing a situational representation of component status |
US7681068B2 (en) * | 2003-07-02 | 2010-03-16 | Tyco Telecommunications (Us) Inc. | System and method for providing event hysteresis in network management systems |
US7363528B2 (en) * | 2003-08-25 | 2008-04-22 | Lucent Technologies Inc. | Brink of failure and breach of security detection and recovery system |
US7246271B2 (en) * | 2003-10-23 | 2007-07-17 | Agilent Technologies, Inc. | Method for diagnosing complex system faults |
US20050097144A1 (en) * | 2003-11-04 | 2005-05-05 | Taiwan Semiconductor Manufacturing Co. | Performance tuning at CM loader program while replicating EQP list for IBM SiView |
US7529979B2 (en) * | 2003-12-12 | 2009-05-05 | International Business Machines Corporation | Hardware/software based indirect time stamping methodology for proactive hardware/software event detection and control |
US7290181B2 (en) * | 2004-01-05 | 2007-10-30 | International Business Machines Corporation | Apparatus and method for context-sensitive error event notification |
US7480828B2 (en) * | 2004-06-10 | 2009-01-20 | International Business Machines Corporation | Method, apparatus and program storage device for extending dispersion frame technique behavior using dynamic rule sets |
WO2006002108A2 (en) | 2004-06-21 | 2006-01-05 | Musman Scott A | Computer network management using agent-based distributed reasoning |
US20060031469A1 (en) * | 2004-06-29 | 2006-02-09 | International Business Machines Corporation | Measurement, reporting, and management of quality of service for a real-time communication application in a network environment |
US20060031473A1 (en) * | 2004-07-07 | 2006-02-09 | Wood John A | System and method for high capacity fault correlation |
US7631222B2 (en) * | 2004-08-23 | 2009-12-08 | Cisco Technology, Inc. | Method and apparatus for correlating events in a network |
US7493300B2 (en) * | 2004-09-30 | 2009-02-17 | International Business Machines Corporation | Model and system for reasoning with N-step lookahead in policy-based system management |
WO2006091247A2 (en) * | 2004-11-12 | 2006-08-31 | Taser International, Inc. | Systems and methods for electronic weaponry having audio and/or video recording capability |
KR100628317B1 (en) * | 2004-12-03 | 2006-09-27 | 한국전자통신연구원 | Apparatus for detecting attacks toward network and method thereof |
US7594252B2 (en) * | 2005-03-01 | 2009-09-22 | Time Warner Cable, Inc. | Early warning fault identification and isolation system for a two-way cable network |
US20060218612A1 (en) * | 2005-03-01 | 2006-09-28 | Keith Johnson | Fault detection and isolation system for an HFC cable network and method therefor |
US7706252B2 (en) * | 2005-07-21 | 2010-04-27 | Time Warner Cable, Inc. | System and method for locating faults in a hybrid fiber coax (HFC) cable network |
US20070038896A1 (en) * | 2005-08-12 | 2007-02-15 | International Business Machines Corporation | Call-stack pattern matching for problem resolution within software |
US7810127B2 (en) * | 2005-08-31 | 2010-10-05 | Time Warner Cable, Inc. | System and method for evaluating the operational status of a STB in a cable network |
US7599300B2 (en) * | 2005-08-31 | 2009-10-06 | Time Warner Cable, Inc. | Cable modem analysis system and method therefor for an HFC cable network |
US7509669B2 (en) * | 2005-08-31 | 2009-03-24 | Time Warner Cable, Inc. | VOD transaction error correlator |
US7506354B2 (en) | 2005-08-31 | 2009-03-17 | Time Warner Cable, Inc. | VOD transaction error correlator |
US7596800B2 (en) * | 2005-08-31 | 2009-09-29 | Time Warner Cable, Inc. | System and method for assigning and verifying CPE service calls in a cable network |
JP4527642B2 (en) * | 2005-09-29 | 2010-08-18 | 富士通株式会社 | Network failure diagnosis apparatus, network failure diagnosis method, and network failure diagnosis program |
US20070198993A1 (en) * | 2006-02-06 | 2007-08-23 | Zhongyao Zhang | Communication system event handling systems and techniques |
US8576855B2 (en) * | 2006-05-17 | 2013-11-05 | Alcatel Lucent | System and method of interface association for interface operational status event monitoring |
US7979245B1 (en) | 2006-05-17 | 2011-07-12 | Quest Software, Inc. | Model-based systems and methods for monitoring computing resource performance |
US8090361B2 (en) * | 2006-05-26 | 2012-01-03 | At&T Intellectual Property I, Lp | Methods and systems for monitoring computer systems using wireless devices |
US20080126283A1 (en) * | 2006-09-12 | 2008-05-29 | Odom Michael L | Method of capturing Problem Resolution for Subsequent Use in Managed Distributed Computer Systems |
US7603455B2 (en) * | 2006-09-27 | 2009-10-13 | Fujitsu Limited | Managing a user network of a partitioned network |
US7979494B1 (en) | 2006-11-03 | 2011-07-12 | Quest Software, Inc. | Systems and methods for monitoring messaging systems |
FR2911457A1 (en) * | 2007-01-12 | 2008-07-18 | France Telecom | Event e.g. failure, determining method for e.g. Internet network, involves calculating intersection of regrouped paths for trees, and estimating localization of event estimated according to calculated intersection |
US7917810B2 (en) * | 2007-10-17 | 2011-03-29 | Datadirect Networks, Inc. | Method for detecting problematic disk drives and disk channels in a RAID memory system based on command processing latency |
US8175863B1 (en) | 2008-02-13 | 2012-05-08 | Quest Software, Inc. | Systems and methods for analyzing performance of virtual environments |
US8331221B2 (en) * | 2008-04-30 | 2012-12-11 | Centurylink Intellectual Property Llc | Automatic outage alert system |
US8230269B2 (en) * | 2008-06-17 | 2012-07-24 | Microsoft Corporation | Monitoring data categorization and module-based health correlations |
US8086907B1 (en) | 2008-09-30 | 2011-12-27 | Juniper Networks, Inc. | Systems and methods for network information collection |
US8850347B2 (en) | 2010-09-30 | 2014-09-30 | Honeywell International Inc. | User interface list control system |
US20100106543A1 (en) * | 2008-10-28 | 2010-04-29 | Honeywell International Inc. | Building management configuration system |
US8719385B2 (en) * | 2008-10-28 | 2014-05-06 | Honeywell International Inc. | Site controller discovery and import system |
US8819562B2 (en) | 2010-09-30 | 2014-08-26 | Honeywell International Inc. | Quick connect and disconnect, base line configuration, and style configurator |
US20110093493A1 (en) * | 2008-10-28 | 2011-04-21 | Honeywell International Inc. | Building management system site categories |
US8572502B2 (en) * | 2008-11-21 | 2013-10-29 | Honeywell International Inc. | Building control system user interface with docking feature |
US9471202B2 (en) * | 2008-11-21 | 2016-10-18 | Honeywell International Inc. | Building control system user interface with pinned display feature |
US7956737B2 (en) * | 2008-12-24 | 2011-06-07 | At&T Intellectual Property I, L.P. | Method and apparatus for network service assurance |
US8495245B2 (en) * | 2009-01-08 | 2013-07-23 | Alcatel Lucent | Connectivity, adjacencies and adaptation functions |
US9021317B2 (en) * | 2009-03-12 | 2015-04-28 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Reporting and processing computer operation failure alerts |
US8554714B2 (en) * | 2009-05-11 | 2013-10-08 | Honeywell International Inc. | High volume alarm management system |
US8224763B2 (en) | 2009-05-11 | 2012-07-17 | Honeywell International Inc. | Signal management system for building systems |
JP5325981B2 (en) * | 2009-05-26 | 2013-10-23 | 株式会社日立製作所 | Management server and management system |
CN101674196B (en) * | 2009-06-16 | 2011-12-07 | 北京邮电大学 | Multi-domain collaborative distributed type fault diagnosis method and system |
US8352047B2 (en) | 2009-12-21 | 2013-01-08 | Honeywell International Inc. | Approaches for shifting a schedule |
US8375255B2 (en) * | 2009-12-23 | 2013-02-12 | At&T Intellectual Property I, Lp | Device and method for detecting and diagnosing correlated network anomalies |
US20110196539A1 (en) * | 2010-02-10 | 2011-08-11 | Honeywell International Inc. | Multi-site controller batch update system |
US8640098B2 (en) * | 2010-03-11 | 2014-01-28 | Honeywell International Inc. | Offline configuration and download approach |
US8890675B2 (en) | 2010-06-02 | 2014-11-18 | Honeywell International Inc. | Site and alarm prioritization system |
US8648706B2 (en) | 2010-06-24 | 2014-02-11 | Honeywell International Inc. | Alarm management system having an escalation strategy |
US9213539B2 (en) | 2010-12-23 | 2015-12-15 | Honeywell International Inc. | System having a building control device with on-demand outside server functionality |
US9215142B1 (en) | 2011-04-20 | 2015-12-15 | Dell Software Inc. | Community analysis of computing performance |
US9223839B2 (en) | 2012-02-22 | 2015-12-29 | Honeywell International Inc. | Supervisor history view wizard |
US9037922B1 (en) * | 2012-05-01 | 2015-05-19 | Amazon Technololgies, Inc. | Monitoring and analysis of operating states in a computing environment |
US8924773B1 (en) * | 2012-06-29 | 2014-12-30 | Emc Corporation | Reducing file system data unavailability window by adapting hierarchical recovery framework |
CN103580904A (en) * | 2012-08-08 | 2014-02-12 | 中兴通讯股份有限公司 | Method and device for sending inter-domain fault information |
US9086960B2 (en) * | 2012-08-21 | 2015-07-21 | International Business Machines Corporation | Ticket consolidation for multi-tiered applications |
US8418230B1 (en) * | 2012-08-28 | 2013-04-09 | Netcomm Wireless Limited | Apparatus and method for mobile communications and computing |
US9529349B2 (en) | 2012-10-22 | 2016-12-27 | Honeywell International Inc. | Supervisor user management system |
US9557879B1 (en) | 2012-10-23 | 2017-01-31 | Dell Software Inc. | System for inferring dependencies among computing systems |
US10333820B1 (en) | 2012-10-23 | 2019-06-25 | Quest Software Inc. | System for inferring dependencies among computing systems |
EP3001606B1 (en) * | 2013-06-27 | 2018-12-19 | Huawei Technologies Co., Ltd. | Fault processing method, device and system |
US9971977B2 (en) | 2013-10-21 | 2018-05-15 | Honeywell International Inc. | Opus enterprise report system |
US11005738B1 (en) | 2014-04-09 | 2021-05-11 | Quest Software Inc. | System and method for end-to-end response-time analysis |
US9479414B1 (en) | 2014-05-30 | 2016-10-25 | Dell Software Inc. | System and method for analyzing computing performance |
US9933762B2 (en) | 2014-07-09 | 2018-04-03 | Honeywell International Inc. | Multisite version and upgrade management system |
EP2985949B1 (en) * | 2014-08-14 | 2018-05-23 | Hewlett-Packard Enterprise Development LP | Correlation engine comprising root cause and service impact analyses |
US10291493B1 (en) | 2014-12-05 | 2019-05-14 | Quest Software Inc. | System and method for determining relevant computer performance events |
US9274758B1 (en) | 2015-01-28 | 2016-03-01 | Dell Software Inc. | System and method for creating customized performance-monitoring applications |
US9996577B1 (en) | 2015-02-11 | 2018-06-12 | Quest Software Inc. | Systems and methods for graphically filtering code call trees |
US10187260B1 (en) | 2015-05-29 | 2019-01-22 | Quest Software Inc. | Systems and methods for multilayer monitoring of network function virtualization architectures |
US10200252B1 (en) | 2015-09-18 | 2019-02-05 | Quest Software Inc. | Systems and methods for integrated modeling of monitored virtual desktop infrastructure systems |
US10209689B2 (en) | 2015-09-23 | 2019-02-19 | Honeywell International Inc. | Supervisor history service import manager |
US10362104B2 (en) | 2015-09-23 | 2019-07-23 | Honeywell International Inc. | Data manager |
US10230601B1 (en) | 2016-07-05 | 2019-03-12 | Quest Software Inc. | Systems and methods for integrated modeling and performance measurements of monitored virtual desktop infrastructure systems |
US10304522B2 (en) | 2017-01-31 | 2019-05-28 | International Business Machines Corporation | Method for low power operation and test using DRAM device |
US9916890B1 (en) | 2017-02-21 | 2018-03-13 | International Business Machines Corporation | Predicting data correlation using multivalued logical outputs in static random access memory (SRAM) storage cells |
US11526768B2 (en) | 2017-06-02 | 2022-12-13 | International Business Machines Corporation | Real time cognitive reasoning using a circuit with varying confidence level alerts |
US10037792B1 (en) | 2017-06-02 | 2018-07-31 | International Business Machines Corporation | Optimizing data approximation analysis using low power circuitry |
US10663502B2 (en) | 2017-06-02 | 2020-05-26 | International Business Machines Corporation | Real time cognitive monitoring of correlations between variables |
US10598710B2 (en) | 2017-06-02 | 2020-03-24 | International Business Machines Corporation | Cognitive analysis using applied analog circuits |
US10652208B2 (en) * | 2018-10-03 | 2020-05-12 | Axonius Solutions Ltd. | System and method for managing network connected devices |
WO2021165725A1 (en) * | 2020-02-21 | 2021-08-26 | Nokia Solutions And Networks Oy | Coordination of compensation of network part failure impacts |
CN117041012A (en) * | 2020-11-20 | 2023-11-10 | 华为技术有限公司 | Cross-domain fault analysis method and system |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4977390A (en) * | 1989-10-19 | 1990-12-11 | Niagara Mohawk Power Corporation | Real time method for processing alaarms generated within a predetermined system |
JP2810171B2 (en) * | 1989-12-18 | 1998-10-15 | 株式会社日立製作所 | Network system and network management method applying the same |
WO1992005485A2 (en) * | 1990-09-17 | 1992-04-02 | Cabletron Systems, Inc. | Network management system using model-based intelligence |
US5293323A (en) * | 1991-10-24 | 1994-03-08 | General Electric Company | Method for fault diagnosis by assessment of confidence measure |
US5309448A (en) * | 1992-01-03 | 1994-05-03 | International Business Machines Corporation | Methods and systems for alarm correlation and fault localization in communication networks |
US5211044A (en) * | 1992-01-14 | 1993-05-18 | Kim Kwon W | Universal lock and key |
US5495470A (en) * | 1992-04-02 | 1996-02-27 | Applied Digital Access, Inc. | Alarm correlation system for a telephone network |
US5640505A (en) * | 1994-09-07 | 1997-06-17 | British Telecommunications Public Limited Company | Operational support structure for a telecommunications network |
US5696486A (en) * | 1995-03-29 | 1997-12-09 | Cabletron Systems, Inc. | Method and apparatus for policy-based alarm notification in a distributed network management environment |
US5761502A (en) * | 1995-12-29 | 1998-06-02 | Mci Corporation | System and method for managing a telecommunications network by associating and correlating network events |
US6131112A (en) * | 1996-05-17 | 2000-10-10 | Cabletron Systems, Inc. | Method and apparatus for integrated network and systems management |
US5768501A (en) * | 1996-05-28 | 1998-06-16 | Cabletron Systems | Method and apparatus for inter-domain alarm correlation |
-
1996
- 1996-05-28 US US08/654,305 patent/US5768501A/en not_active Expired - Lifetime
-
1998
- 1998-06-08 US US09/094,428 patent/US6000045A/en not_active Expired - Lifetime
-
1999
- 1999-12-06 US US09/455,041 patent/US6205563B1/en not_active Expired - Lifetime
-
2001
- 2001-03-19 US US09/811,748 patent/US6430712B2/en not_active Expired - Lifetime
Cited By (95)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8296412B2 (en) | 2000-01-03 | 2012-10-23 | International Business Machines Corporation | Method and system for event impact analysis |
US20050027845A1 (en) * | 2000-01-03 | 2005-02-03 | Peter Secor | Method and system for event impact analysis |
US7313736B2 (en) * | 2000-06-16 | 2007-12-25 | Ciena Corporation | Method and apparatus for aggregating alarms and faults of a communications network |
US20040223461A1 (en) * | 2000-06-16 | 2004-11-11 | Ciena Corporation. | Method and apparatus for aggregating alarms and faults of a communications network |
US20050157654A1 (en) * | 2000-10-12 | 2005-07-21 | Farrell Craig A. | Apparatus and method for automated discovery and monitoring of relationships between network elements |
US20040233859A1 (en) * | 2001-05-18 | 2004-11-25 | Martin Daniel J. | Method and system for determining network characteristics using routing protocols |
US20030014462A1 (en) * | 2001-06-08 | 2003-01-16 | Bennett Andrew Jonathan | Method and system for efficient distribution of network event data |
US20050286685A1 (en) * | 2001-08-10 | 2005-12-29 | Nikola Vukovljak | System and method for testing multiple dial-up points in a communications network |
US20040024865A1 (en) * | 2002-07-30 | 2004-02-05 | Jiandong Huang | Method and apparatus for outage measurement |
US7523355B2 (en) | 2002-07-30 | 2009-04-21 | Cisco Technology, Inc. | Method and apparatus for outage measurement |
US20070028147A1 (en) * | 2002-07-30 | 2007-02-01 | Cisco Technology, Inc. | Method and apparatus for outage measurement |
US7149917B2 (en) * | 2002-07-30 | 2006-12-12 | Cisco Technology, Inc. | Method and apparatus for outage measurement |
US7257744B2 (en) * | 2003-03-17 | 2007-08-14 | Tyco Telecommunications (Us) Inc. | System and method for fault diagnosis using distributed alarm correlation |
US20040230868A1 (en) * | 2003-03-17 | 2004-11-18 | Sabet Sameh A. | System and method for fault diagnosis using distributed alarm correlation |
US8161152B2 (en) * | 2003-03-18 | 2012-04-17 | Renesys Corporation | Methods and systems for monitoring network routing |
US20040221296A1 (en) * | 2003-03-18 | 2004-11-04 | Renesys Corporation | Methods and systems for monitoring network routing |
US9628354B2 (en) | 2003-03-18 | 2017-04-18 | Dynamic Network Services, Inc. | Methods and systems for monitoring network routing |
US8155122B2 (en) * | 2003-04-17 | 2012-04-10 | Verizon Business Global Llc | Linking autonomous systems with dual premise routing domains |
US20040208175A1 (en) * | 2003-04-17 | 2004-10-21 | Mccabe Alan J. | Linking autonomous systems with dual premise routing domains |
US20080095157A1 (en) * | 2003-04-17 | 2008-04-24 | Verizon Business Global Llc | Linking autonomous systems with dual premise routing domains |
US7366187B2 (en) * | 2003-04-17 | 2008-04-29 | Verizon Business Global Llc | Linking autonomous systems with dual premise routing domains |
US20040249828A1 (en) * | 2003-06-05 | 2004-12-09 | International Business Machines Corporation | Automated infrastructure audit system |
WO2004109977A1 (en) * | 2003-06-05 | 2004-12-16 | International Business Machines Corporation | Automated network infrastructure audit system |
US7418490B1 (en) * | 2003-12-29 | 2008-08-26 | Sun Microsystems, Inc. | System using multiple sets of device management policies for managing network devices connected on different network interfaces |
US7657623B2 (en) * | 2004-03-24 | 2010-02-02 | Nortel Networks Limited | Method and apparatus for collecting management information on a communication network |
US20050216584A1 (en) * | 2004-03-24 | 2005-09-29 | Nortel Networks Limited | Method and apparatus for collecting management information on a communication network |
US7302611B2 (en) | 2004-09-13 | 2007-11-27 | Avaya Technology Corp. | Distributed expert system for automated problem resolution in a communication system |
EP1635506A1 (en) * | 2004-09-13 | 2006-03-15 | Avaya Technology Corp. | Distributed expert system for automated problem solution in a communication system |
US20060069957A1 (en) * | 2004-09-13 | 2006-03-30 | Sangeetha Ganesh | Distributed expert system for automated problem resolution in a communication system |
US10749735B2 (en) | 2005-12-01 | 2020-08-18 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and management agent for event notifications correlation |
US9032420B2 (en) | 2005-12-01 | 2015-05-12 | Telefonaktiebolaget L M Ericsson (Publ) | Method and management agent for event notifications correlation |
WO2007063445A3 (en) * | 2005-12-01 | 2007-12-13 | Ericsson Telefon Ab L M | Method and management agent for event notifications correlation |
US8069452B2 (en) | 2005-12-01 | 2011-11-29 | Telefonaktiebolaget L M Ericsson (Publ) | Method and management agent for event notifications correlation |
US20070130319A1 (en) * | 2005-12-01 | 2007-06-07 | Edwin Tse | Method and management agent for event notifications correlation |
WO2007063445A2 (en) * | 2005-12-01 | 2007-06-07 | Telefonaktiebolaget L M Ericsson (Publ) | Method and management agent for event notifications correlation |
US9985821B2 (en) | 2005-12-01 | 2018-05-29 | Telefonaktiebolaget L M Ericcson (Publ) | Method and management agent for event notifications correlation |
US7496798B2 (en) * | 2006-02-14 | 2009-02-24 | Jaw Link | Data-centric monitoring method |
US20070220368A1 (en) * | 2006-02-14 | 2007-09-20 | Jaw Link C | Data-centric monitoring method |
US20100103823A1 (en) * | 2007-03-27 | 2010-04-29 | Nokia Siemens Networks Gmbh & Co. | Operating network entities in a communications system comprising a management network with agent and management levels |
US9313089B2 (en) | 2007-03-27 | 2016-04-12 | Nokia Solutions And Networks Gmbh & Co. Kg | Operating network entities in a communications system comprising a management network with agent and management levels |
WO2008116861A1 (en) * | 2007-03-27 | 2008-10-02 | Nokia Siemens Networks Gmbh & Co. Kg | Operating network entities in a communications system comprising a management network with agent and management levels |
EP1976185A1 (en) * | 2007-03-27 | 2008-10-01 | Nokia Siemens Networks Gmbh & Co. Kg | Operating network entities in a communication system comprising a management network with agent and management levels |
US7734961B2 (en) * | 2007-05-01 | 2010-06-08 | International Business Machines Corporation | Distributed logging apparatus system and method |
US20080276130A1 (en) * | 2007-05-01 | 2008-11-06 | Almoustafa Ahmed M | Distributed logging apparatus system and method |
US20100309799A1 (en) * | 2007-09-14 | 2010-12-09 | Nec Europe Ltd. | Method and system for optimizing network performances |
WO2009033500A1 (en) * | 2007-09-14 | 2009-03-19 | Nec Europe Ltd. | Method and system for optimizing network performances |
US9210042B2 (en) | 2007-09-14 | 2015-12-08 | Nec Europe Ltd. | Method and system for optimizing network performances |
US8521869B2 (en) * | 2009-12-18 | 2013-08-27 | Fujitsu Limited | Method and system for reporting defects within a network |
US8566634B2 (en) | 2009-12-18 | 2013-10-22 | Fujitsu Limited | Method and system for masking defects within a network |
US20110154099A1 (en) * | 2009-12-18 | 2011-06-23 | Fujitsu Network Communications, Inc. | Method and system for masking defects within a network |
US20110153804A1 (en) * | 2009-12-18 | 2011-06-23 | Fujitsu Network Communications, Inc. | Method and system for reporting defects within a network |
US20110161741A1 (en) * | 2009-12-28 | 2011-06-30 | International Business Machines Corporation | Topology based correlation of threshold crossing alarms |
US8423827B2 (en) * | 2009-12-28 | 2013-04-16 | International Business Machines Corporation | Topology based correlation of threshold crossing alarms |
WO2012041555A1 (en) * | 2010-09-30 | 2012-04-05 | Telefonaktiebolaget L M Ericsson (Publ) | Method for determining a severity of a network incident |
US9680722B2 (en) | 2010-09-30 | 2017-06-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for determining a severity of a network incident |
US20120159519A1 (en) * | 2010-12-17 | 2012-06-21 | Fujitsu Limited | Event dependency management apparatus and event dependency management method |
USRE48065E1 (en) | 2012-05-18 | 2020-06-23 | Dynamic Network Services, Inc. | Path reconstruction and interconnection modeling (PRIM) |
US10021619B2 (en) | 2012-08-24 | 2018-07-10 | Oceus Networks Inc. | Mobile cellular networks |
US9167442B2 (en) * | 2012-08-24 | 2015-10-20 | Oceus Networks Inc. | Mobile cellular networks |
US9445280B2 (en) * | 2012-08-24 | 2016-09-13 | Oceus Networks Inc. | Mobile cellular networks |
US20140057626A1 (en) * | 2012-08-24 | 2014-02-27 | Oceus Networks Inc. | Mobile cellular networks |
US11240677B2 (en) | 2012-08-24 | 2022-02-01 | Oceus Networks, Llc | Mobile cellular networks |
US11743740B2 (en) | 2012-08-24 | 2023-08-29 | Oceus Networks, Llc | Mobile cellular networks |
US9769674B2 (en) | 2012-08-24 | 2017-09-19 | Oceus Networks Inc. | Mobile cellular networks |
US10750423B2 (en) | 2012-08-24 | 2020-08-18 | Oceus Networks Inc. | Mobile cellular networks |
US11582671B2 (en) | 2012-08-24 | 2023-02-14 | Oceus Networks, Llc | Mobile cellular networks |
US10757579B2 (en) | 2012-08-24 | 2020-08-25 | Oceus Networks Inc. | Mobile cellular networks |
US10244405B2 (en) | 2012-08-24 | 2019-03-26 | Oceus Networks Inc. | Mobile cellular networks |
US9451646B2 (en) | 2012-08-24 | 2016-09-20 | Oceus Networks Inc. | Mobile cellular networks |
US9198221B2 (en) | 2012-08-24 | 2015-11-24 | Oceus Networks Inc. | Mobile cellular networks |
US9226192B2 (en) | 2013-04-29 | 2015-12-29 | Oceus Networks Inc. | Mobile cellular network backhaul |
US10382393B2 (en) | 2013-04-29 | 2019-08-13 | Oceus Networks Inc. | Mobile cellular network backhaul |
US9742729B2 (en) | 2013-04-29 | 2017-08-22 | Oceus Networks Inc. | Mobile cellular network backhaul |
US11252128B2 (en) | 2013-04-29 | 2022-02-15 | Oceus Networks, Llc | Mobile cellular network backhaul |
EP3231135A4 (en) * | 2014-12-12 | 2018-06-06 | Nokia Solutions and Networks Oy | Alarm correlation in network function virtualization environment |
US20170346676A1 (en) * | 2014-12-12 | 2017-11-30 | Nokia Solutions And Networks Oy | Alarm correlation in network function virtualization environment |
WO2016093861A1 (en) * | 2014-12-12 | 2016-06-16 | Nokia Solutions And Networks Oy | Alarm correlation in network function virtualization environment |
US11671893B2 (en) | 2016-07-06 | 2023-06-06 | Oceus Networks, Llc | Secure network rollover |
US10873891B2 (en) | 2016-07-06 | 2020-12-22 | Oceus Networks, Llc | Secure network rollover |
US10742610B2 (en) | 2016-07-07 | 2020-08-11 | Oceus Networks Inc. | Secure network enrollment |
US10602410B2 (en) | 2016-07-07 | 2020-03-24 | Oceus Networks Inc. | Network backhaul access |
US9924427B2 (en) | 2016-07-07 | 2018-03-20 | Oceus Networks Inc. | Network backhaul access |
US11588790B2 (en) | 2016-07-07 | 2023-02-21 | Oceus Networks, Llc | Secure network enrollment |
US11134425B2 (en) | 2016-07-07 | 2021-09-28 | Oceus Networks, Llc | Network backhaul access |
US9912640B2 (en) | 2016-07-07 | 2018-03-06 | Oceus Networks Inc. | Secure network enrollment |
US9686238B1 (en) | 2016-07-07 | 2017-06-20 | Oceus Networks Inc. | Secure network enrollment |
US10172078B2 (en) | 2017-03-31 | 2019-01-01 | Oceus Networks Inc. | Targeted user equipment-base station communication link |
US11184840B2 (en) | 2017-03-31 | 2021-11-23 | Oceus Networks, Llc | Targeted user equipment-base station communication link |
US10631237B2 (en) | 2017-03-31 | 2020-04-21 | Oceus Networks Inc. | Targeted user equipment-base station communication link |
US11792721B2 (en) | 2017-03-31 | 2023-10-17 | Oceus Networks, Llc | Targeted user equipment-base station communication link |
US11246031B2 (en) | 2018-08-15 | 2022-02-08 | Oceus Networks, Llc | Disguising UE communications in a cellular network |
WO2020069739A1 (en) * | 2018-10-04 | 2020-04-09 | Telefonaktiebolaget Lm Ericsson (Publ) | Network node and method performed therein for handling operations in a set of communication networks |
US10805144B1 (en) * | 2019-06-18 | 2020-10-13 | Cisco Technology, Inc. | Monitoring interactions between entities in a network by an agent for particular types of interactions and indexing and establishing relationships of the components of each interaction |
US20230069434A1 (en) * | 2021-08-31 | 2023-03-02 | Juniper Networks, Inc. | Identifying root cause of failures through detection of network scope failures |
US11838172B2 (en) * | 2021-08-31 | 2023-12-05 | Juniper Networks, Inc. | Identifying root cause of failures through detection of network scope failures |
Also Published As
Publication number | Publication date |
---|---|
US6205563B1 (en) | 2001-03-20 |
US6430712B2 (en) | 2002-08-06 |
US6000045A (en) | 1999-12-07 |
US5768501A (en) | 1998-06-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6430712B2 (en) | Method and apparatus for inter-domain alarm correlation | |
US7007104B1 (en) | Method and apparatus for integrated network management and systems management in communications networks | |
US6255943B1 (en) | Method and apparatus for distributed object filtering | |
US5751965A (en) | Network connection status monitor and display | |
EP0818096B1 (en) | Method and apparatus for policy-based alarm notification in a distributed network management environment | |
AU720871B2 (en) | Apparatus and method for network capacity evaluation and planning | |
EP0549677B1 (en) | Network management system using model-based intelligence | |
US5261044A (en) | Network management system using multifunction icons for information display | |
US6751661B1 (en) | Method and system for providing intelligent network management | |
US9509524B2 (en) | System and method for service level management | |
CA2345117A1 (en) | Interface system for integrated monitoring and management of network devices in a telecommunications network | |
US20100046379A1 (en) | Operating network entities in a communications system | |
EP0963077A2 (en) | Node and link representation of network services | |
Fuller | Network management using expert diagnostics | |
Lewis et al. | Incorporating business process management into network and systems management | |
De Franceschi et al. | Employing Remote Monitoring and Artificial Intelligence Techniques to Develop the Proactive Network Management | |
Cheng | A High-Level Approach in Network Management | |
Disabato | Key Technologies for Integraed Network Management. | |
GECKIL | Apparatus and method for determining a computer network topology | |
Kim et al. | ExNet: An Intelligent Network Management System. | |
Ideguchi et al. | An implementation of a hierarchical LAN management system based upon analysis of network management operations | |
Westphall et al. | Two Different Approaches about the Development of the Proactive Network Management | |
Olawuyi et al. | COMPUTER NETWORK FAULT MANAGEMENT SYSTEM USING THE OSI STANDARDS | |
Lorenz et al. | PMS: A PVC management system for ATM networks | |
De Almeida | Tiili" TTTTT: ETTETITETTTEI5E" TTTTTT |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: FOOTHILL CAPITAL CORPORATION, A CALIFORNIA CORPORA Free format text: SECURITY INTEREST;ASSIGNOR:APRISMA MANAGEMENT TECHNOLOGIES, INC., A DELAWARE CORPORATION;REEL/FRAME:013447/0331 Effective date: 20021014 |
|
AS | Assignment |
Owner name: APRISMA MANAGEMENT TECHNOLOGIES, INC., NEW HAMPSHI Free format text: NUNC PRO TUNC - EFFECTIVE 03-19-01;ASSIGNOR:CABLETRON SYSTEMS, INC.;REEL/FRAME:015328/0084 Effective date: 20000929 Owner name: APRISMA MANAGEMENT TECHNOLOGIES, INC., NEW HAMPSHI Free format text: NUNC PRO TUNC - EFFECTIVE 03/19/01.;ASSIGNOR:LEWIS, LUNDY M.;REEL/FRAME:015328/0098 Effective date: 19960717 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: APRISMA MANAGEMENT TECHNOLOGIES, INC,NEW HAMPSHIRE Free format text: RELEASE OF SECURITY INTEREST RECORDED 10262002 R/F 013447/0331;ASSIGNOR:WELLS FARGO FOOTHILL, INC. (FORMERLY KNOWN AS FOOTHILL CAPITAL CORPORATION);REEL/FRAME:018668/0833 Effective date: 20050222 Owner name: APRISMA MANAGEMENT TECHNOLOGIES, INC, NEW HAMPSHIR Free format text: RELEASE OF SECURITY INTEREST RECORDED 10262002 R/F 013447/0331;ASSIGNOR:WELLS FARGO FOOTHILL, INC. (FORMERLY KNOWN AS FOOTHILL CAPITAL CORPORATION);REEL/FRAME:018668/0833 Effective date: 20050222 |
|
AS | Assignment |
Owner name: CONCORD COMMUNICATIONS, INC.,MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:APRISMA MANAGEMENT TECHNOLOGIES, INC.;REEL/FRAME:019028/0320 Effective date: 20070208 Owner name: CONCORD COMMUNICATIONS, INC., MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:APRISMA MANAGEMENT TECHNOLOGIES, INC.;REEL/FRAME:019028/0320 Effective date: 20070208 |
|
AS | Assignment |
Owner name: COMPUTER ASSOCIATES THINK, INC.,NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CONCORD COMMUNICATIONS, INC.;REEL/FRAME:019047/0414 Effective date: 20070208 Owner name: COMPUTER ASSOCIATES THINK, INC., NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CONCORD COMMUNICATIONS, INC.;REEL/FRAME:019047/0414 Effective date: 20070208 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: CABLETRON SYSTEMS, INC., NEW HAMPSHIRE Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE NAME AND ADDRESS OF THE ASSIGNEE PREVIOUSLY RECORDED ON REEL 015328 FRAME 0098. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNEE'S NAME AND ADDRESS ARE CABLETRON SYSTEMS, INC., 35 INDUSTRIAL WAY, P.O. BOX 5005, ROCHESTER, NEW HAMPSHIRE 03867-5005;ASSIGNOR:LEWIS, LUNDY;REEL/FRAME:028154/0755 Effective date: 19960717 |
|
AS | Assignment |
Owner name: GOOGLE INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:COMPUTER ASSOCIATES THINK, INC.;REEL/FRAME:028801/0049 Effective date: 20120330 |
|
FPAY | Fee payment |
Year of fee payment: 12 |
|
AS | Assignment |
Owner name: GOOGLE LLC, CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:GOOGLE INC.;REEL/FRAME:044144/0001 Effective date: 20170929 |