Network Management Appliance

FIELD OF INVENTION

0001The present invention relates broadly to a network management appliance, to a method for managing a network, and to a computer readable data storage medium having stored thereon computer code means for instructing a computer to execute a method for managing a network.

BACKGROUND

0002Businesses are leveraging information technology to gain and maintain a competitive edge, while efficient support of the IT infrastructure poses a real challenge. The IT infrastructure managers of today are facing increasing demands to deliver new systems, services and applications, while the deployment of each new technology is adding to the complexity of the enterprise support model.

0003Traditionally, network management are software-only solutions, requiring complex installation and configuration procedures before it can be up and running, to manage the network devices in an IP (Internet Protocol) network. These may include network routers/switches, firewalls, servers and applications. In additional, end-users usually need to acquire dedicated server and client machines to host and use the network management software. This consequently results in high complexities and high costs for a typical network management solution deployment.

0004To effectively manage the IT infrastructure, enterprises require a support model managing the network, systems, services and applications. The complexity of the enterprise support model has manifested itself as the prime concern of the IT managers. The IT infrastructure managers realize the burgeoning need of a simple approach to the complex enterprise management solution involving quick-to-deploy tools that provide real and immediate acceleration towards to the business goals.

0005The infusion and proliferation of new technology must be supported by an integrated reliable management tools to achieve desirable business benefits, control costs and ultimately avoid IT failures. The management tools are needed not only to understand and monitor various technologies but also effectively implement these technologies to achieve business goals.

0006The management tools would help the managers to view the entire IT infrastructure as an integrated whole and make useful information for infrastructure management readily available across the enterprise. The tool set for IT managers would typically provide for continuous and real-time monitoring of systems, services and applications, report generation on the health of the infrastructure, flexibility to add new services and technologies, notification of service level or device faults, initiation of problem resolution, knowledge-base to advice on problems, identification of root cause as well as workforce co-ordination and problem assignment.

0007The above mentioned tool sets would value-add to their service delivery to reduce costs, improve systems, applications, services, databases and network availability, continuously improve on quality and business process, sharpens competitive edge, while providing access to advanced technologies and achieve best-in-class standards.

0008End-to-end management across multiple components in a distributed heterogeneous environment has also emerged as a requirement in infrastructure management. It is no longer viable to manage individual systems, computers, subnets and networks services in isolation. These components inter-operate to provide connectivity and services. The customer oriented point of view goes through the boundaries of network, services, applications and their performance and service levels. The management tools must provide for end-to-end management across the different management layers.

0009An end-to-end management solution provides a strategic solution, covering management of all critical components of all services, simplifies and improves setup, deployment, monitoring and measuring of services for faster ROI. End-to-end management also allows the management of enterprise services based on business priorities as well as the maximisation of service availability, keeping services fully operational on 24×7×357 basis to satisfy customers and protect revenue. The end-to-end management solution is also able to keep service delivery costs under control.

0010The current generation of enterprise management solutions can be broadly classified into two categories. The first category is the central server based management with autonomous agents where there is high scalability but the cost is higher. Upgrades are performed on the central server. These upgrades can be expensive hardware/server and software upgrades. The second category is the usage of thick agents that are resource intensive agents. These agents have limited scalability and lower cost as compared to the central server based management system. Any required upgrades are carried out individually on each agent.

0011Thus, there is a need for an appliance oriented enterprise management solution that offers central server based management where the cost per agent is driven down to a level that is comparable to that of thick clients while maintaining the advantage of central server based management. The central server provides completely web-based secure and integrated management anytime from anywhere.

0012Hence, it is with the knowledge of the above concerns and restrictions that the present invention has been made.

SUMMARY

0013In accordance with one aspect of the present invention, there is provided a network management appliance comprising, a central bus element, a plurality of network management modules each coupled to the central bus element, a server element coupled to the central bus element, a network interface for interfacing the central bus element with a network to be managed, and wherein network management functions executed by the network management modules are remotely accessible through the server element via the network interface.

0014The network management appliance may further comprise, a standard event format supported and operable on the central bus element for integrating the plurality of network management modules with the standard event format, and wherein the standard event format enables the plurality of network management modules to communicate with one another.

0015The network management modules may comprise two or more of a group consisting of, a configuration utility module, an auto-discovery process module, an alarm correlation engine module, a role-based security utility module, a module consisting of data monitors and collectors, a Service Level Agreement (SLA) management processes module, an inventory management utility module, a notification engine module, an automatic-actions on alarms utility module, and a management tasks automation utility module.

0016The configuration utility module may be used for consolidating and configuring parameters for the network to be managed.

0017The network management appliance may further comprise, a set of alarm correlation rules in the alarm correlation engine module, and wherein the alarm correlation engine is used for managing alarms from the network to be managed with the set of alarm correlation rules.

0018The role-based security utility module may provide a centralised allocation of access and domain rights to network users based on their roles as recorded in an access system implemented in the role-based security utility module.

0019The network management appliance may further comprise, criteria for thresholds of service levels implemented in the Service Level Agreement (SLA) management processes module, and wherein the Service Level Agreement (SLA) management processes module compares performance data against the criteria for thresholds of service levels and decides on the next course of action.

0020The network management appliance may further comprise, an user database query utility implemented in the inventory management utility module, and wherein the user database query utility is used to retrieve inventory information of the network to be managed from the inventory management utility module.

0021The notification engine module may send out notifications based on a set of notification rules implemented in the notification engine module.

0022The network management appliance may further comprise, a filtering criteria implemented in the automatic-actions on alarms utility module, and wherein the automatic-actions on alarms utility module executes automatic actions based on matching alarm events provided by the alarm correlation engine module to the filtering criteria.

0023The network management appliance may further comprise, a central data repository, and wherein management data associated with the network management functions executed by the network management modules is stored in the central data repository.

0024The server element may comprise a web server.

0025The network management modules may be remotely accessible by utilising one or more of a group consisting, an object-modelling capability, an agent-based technology, an applet based technology, and a scripting engine.

0026The network management appliance may further comprise, a plurality of performance counters, a plurality of transient performance counters, a file system for temporary storing of storing of performance data in a memory, and wherein output from the plurality of performance counters are stored as performance data in the or a central data repository, and output from the plurality of transient performance counters are not stored in the central data repository.

0027The performance data may be stored into the central depository periodically.

0028In accordance with another aspect of the present invention, there is provided a method comprising providing a central bus element; coupling a plurality of network management modules to the central bus element; coupling a server element to the central bus element; providing a network interface for the central bus element to be interfaced with a network to be managed; and wherein network management functions executed by the network management modules are remotely accessed through the server element via the network interface.

0029In accordance with yet another aspect of the present invention, there is provided a computer readable data storage medium having stored thereon computer code means for instructing a computer to execute a method for managing a network, the method comprising providing a central bus element; coupling a plurality of network management modules to the central bus element; coupling a server element to the central bus element; providing a network interface for the central bus element to be interfaced with a network to be managed; and wherein network management functions executed by the network management modules are remotely accessed through the server element via the network interface.

BRIEF DESCRIPTION OF THE DRAWINGS

0030Embodiments of the invention will be better understood and readily apparent to one of ordinary skill in the art from the following written description, by way of example only, and in conjunction with the drawings, in which:

0031<figref idref="DRAWINGS">FIG. 1</figref> is a schematic illustration for an architecture used for software modules in an example embodiment.

0032<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram showing the hierarchy structures in object modelling in an example embodiment.

0033<figref idref="DRAWINGS">FIG. 3</figref> is a diagram illustrating a Central Repository in an example embodiment.

0034<figref idref="DRAWINGS">FIG. 4</figref> is an illustration for agent-based communications in an example embodiment.

0035<figref idref="DRAWINGS">FIG. 5</figref> is an illustration of a role-based security system in an example embodiment.

0036<figref idref="DRAWINGS">FIG. 6</figref> shows information collections and monitoring from a wide range of sources in an example embodiment.

0037<figref idref="DRAWINGS">FIG. 7</figref>(<i>a</i>) shows different possible equipment connections and collectors to the appliance in an example embodiment.

0038<figref idref="DRAWINGS">FIG. 7</figref>(<i>b</i>) shows different possible monitor communications with the appliance in an example embodiment.

0039<figref idref="DRAWINGS">FIG. 8</figref> is a flow diagram illustrating an Auto Discovery process in an example embodiment.

0040<figref idref="DRAWINGS">FIG. 9</figref> is a flow diagram illustrating a Network Monitoring process in an example embodiment.

0041<figref idref="DRAWINGS">FIG. 10</figref> is a flow diagram illustrating an Alarm Management process in an example embodiment.

0042<figref idref="DRAWINGS">FIG. 11</figref> is a flow diagram illustrating a Report Generation process in an example embodiment.

0043<figref idref="DRAWINGS">FIG. 12</figref> shows a schematic drawing of a computer system for implementing a method in accordance with an example embodiment.

0044<figref idref="DRAWINGS">FIG. 13</figref> is a flow diagram illustrating an method of managing a network in an example embodiment.

DETAILED DESCRIPTION

0045The example embodiment described herein can provide a method for reducing the complexities of network management.

0046In an example embodiment, a network management software is designed and developed. This software can be embedded into a linux-based hardware appliance. There are no requirements for a monitor display, mouse or keyboard to be attached to the appliance. The network management appliance comes with a built-in web server and the users are able to access the network management functions using a web browser from any PC terminals. There are no client software requirements for these client PC terminals. The appliance, once connected to the network, will be able to auto-discover the network, systems and applications. It will then be able to automatically start managing these objects.

0047In the example embodiment, the appliance hardware is an intel-based architecture, with made-to-order components and chassis. It is installed with an operating system such as a Red Hat Linux OS (v9 or above) and NetGain System's in-house developed network management software as mentioned above. This intelligent appliance shall be known as “NetGain Enterprise Manager”. End users can attain benefits such as quick installation and setup of the appliance, cost savings on additional hardware and easy access to the appliance's functions from any PC terminals, anytime and anywhere. End users will thus no longer be worried about long deployment cycles, high complexities and high costs of network management projects.

0048The various features of the appliance in this example embodiment are further elaborated in the following.

0000NetGain Enterprise Manager Architecture

0049The architecture (<b>100</b>), as shown in <figref idref="DRAWINGS">FIG. 1</figref>, of the NetGain Enterprise Manager is based on carrier-class, component-based, highly scalable architecture. The system architecture (<b>100</b>) with a central software integration bus (<b>102</b>) makes it possible to have well integrated but loosely coupled software components (<b>104</b>) which are robust, independent and distributed in nature. The central software integration bus (<b>102</b>) allows additional, distributed and independent software components (<b>104</b>) to be easily ‘plugged-in’ to the system. The distributed design allows the scalability of the solution as the network expands and new services (<b>104</b>) are introduced.

0000Central Event Bus:

0050In order for additional components to be plugged in independently, a modular architecture where the components are loosely coupled but tightly integrated is required. Therefore, a system wide communication bus or a central event bus (<b>102</b>) is used to support a standard event format used by all the components (<b>104</b>) to communicate with each other as seen in <figref idref="DRAWINGS">FIG. 1</figref>. It provides a three-tier architecture to the entire system with the central event bus (<b>102</b>) decoupling the components while keeping them tightly integrated with the standard event format.

0000Linux-Based

0051In this example embodiment, there is a need for a secure and stable operating system, which does not degrade in performance over a considerable period of time. In order to fulfil this need, a subset of the Linux operating system was used as a base for this appliance. The software programs, such as seen in (<b>104</b>) in <figref idref="DRAWINGS">FIG. 1</figref>, that are part of the appliance start along with the operating system when the system is switched on. The entire system is externally connected through the LAN cable only. The system can be completely configured, monitored and managed through any web browser, such as Internet Explorer (IE).

0000Object-Modeling:

0052In this example embodiment, there is a need for the modelling of real world entities such as network elements like routers, PCs, servers, services, monitors etc so that their characteristics and behaviors can be faithfully replicated in software. As a result, XML-based object modeling was utilised to describe the relationships, hierarchy (<b>200</b> in <figref idref="DRAWINGS">FIG. 2</figref>) and characteristics of the network elements. The Object modeling defines the containment of the defined objects as a containment hierarchy (<b>204</b>), such as IP Device Group may contain IP Device, which in turn may contain a Monitor (<b>202</b>). The inheritance hierarchy (<b>208</b>) definitions are defined from the most generic definition such as a Monitor (<b>206</b>) to more specific descriptions such as the CPU or Memory or Disk monitors, i.e. a specific definition extends a generic definition. Therefore, it is possible to define and introduce new technologies, as the newer definitions can inherit from earlier definitions.

0000Time-Series Based Performance DB:

0053To facilitate fast and easy access to monitoring and performance data collected from various network elements, services and applications, while using minimal amount of disk space, a time-series based performance database is implemented in the appliance. The performance counters and their values of monitor objects are stored as performance data records in performance data files within the folders named after the day they were collected. The transient performance counters are not saved in the database. The performance data being collected is kept in memory by the system until the data is saved to the file system, which is done periodically. Thus, the periodic saving of performance data collected by the system in memory will reduce the disk input/output time, which is the major performance bottle-neck in today's computer technology. The performance data files arranged as folders named by date will allow fast and easy access while generating and browsing historical and current performance data reports.

0000Multi-Threaded Architecture:

0054For high performance computing and faster response time, the system design is based on multi-threaded architecture. The architecture leads to higher performance, faster communication and sharing of process space and data.

0000Built-in Web Server:

0055In order to provide a fast and efficient web interface to the system, the web server runs within the same process space as other components in the system. This provides a fast and efficient interface as the process and data spaces are shared.

0000Central Repository &amp; Designer:

0056In order to consolidate and configure all the configurable parameters in the system (<b>300</b>) under one sub-application, the Designer (<b>302</b>) is used as seen in <figref idref="DRAWINGS">FIG. 3</figref>. The Designer (<b>302</b>) is a one-stop configuration utility for the whole system (<b>300</b>) while the sub-application is termed the ‘Central Repository’ (<b>304</b>). All the configurable parameters are arranged hierarchically as “resources”. A standard editor or a special editor can edit these resources through a web interface (<b>306</b>). The changes in the configuration are updated even while the system (<b>300</b>) is running. The total configuration information is saved in the ‘Central Repository’ (<b>304</b>).

0000Applet-Based Technology:

0057In order to eliminate the need to install the NetGain software in client PCs, a Web-based client (<b>306</b>) for the system (<b>300</b>), NetGain Enterprise Manager, is created. This client (<b>306</b>) provides an anytime, anywhere interface to configure, monitor and maintain the system through a standard web-browser. The applet based Desktop (<b>306</b>) can be run from the home page of the NetGain Enterprise Manager (<b>300</b>) device within a web-browser such as Internet Explorer. This provides the interface to start various other applications such as auto-discovery, network/service configurators, topology window, alarm viewer.

0000Agent-Based Technology:

0058To provide monitoring data to the appliance (<b>400</b>) and scripting support for systems, services and applications that need more than what SNMP support (<b>402</b>) provides or those that lack SNMP support, an agent (<b>404</b>) can be installed as shown in <figref idref="DRAWINGS">FIG. 4</figref>. The agent can be installed and run on various operating systems such as Windows 98/2000/NT/XP, Linux, Solaris, HPUX, IBM-AIX etc. The agent is able to discover and provide monitoring support (<b>406</b>) for various types of services and applications. Additionally, it can provide scripting support in the native system's (<b>408</b>) scripting language. Thus, a high level of local control can be achieved over the monitored system with the installation of a lightweight agent (<b>404</b>).

0000Role-Based Security:

0059In order to provide multi-user access to the system based on access rights (<b>500</b>) and domain rights, an access system is set up where the access for users (<b>502</b>) to the system is based on the role (<b>504</b>) a user (<b>502</b>) belongs to. The role (<b>504</b>) of a user (<b>502</b>) contains the access rights (<b>500</b>) and the domain rights, such as allowed resources like a set of computers in a subnet. Once the user (<b>502</b>) is logged into the system, the interface and its components depend on the user's access rights (<b>500</b>) and domain rights. The various actions that are restricted will check for the access rights (<b>500</b>) of the user (<b>502</b>) if required. Thus, there is a centralised allocation of access rights (<b>500</b>) and domain rights to a role. Multiple users (<b>502</b>) can also share the same role.

0000Proactive Monitoring

0000Lightweight Monitors &amp; Collectors

0060In this example embodiment, the appliance (<b>600</b>) can perform data collection for service level and performance monitoring such as shown in process (<b>602</b>) through a wide variety of lightweight monitors and collectors. The collectors and monitors collect fault and service level information from a wide range of devices, databases, logs and other sources (<b>604</b>) as can be seen in <figref idref="DRAWINGS">FIG. 6</figref>.

0061The collectors can be deployed virtually anywhere, allowing the collection of alarms (<b>700</b>) from remote sites and different locations (<b>702</b>) as shown in <figref idref="DRAWINGS">FIG. 7</figref>(<i>a</i>). The collectors enable unified alarm management by converting different types of alarms from disparate sources (<b>702</b>) such as SNMP Traps, Syslog etc into unified X.733 standard alarms, containing all the information provided by the native alarm.

0062The monitors (<b>704</b>) as shown in <figref idref="DRAWINGS">FIG. 7</figref>(<i>b</i>) pro-actively collect (<b>706</b>) performance and availability data from a wide range of managed environments (<b>708</b>) spanning across systems, services and applications, periodically and calculate the service, and if necessary trigger service level alarms on impending service disruptions.

0063A wide range of monitors (<b>704</b>) collect the necessary data using different methods. When using SNMP (<b>708</b>), the monitor requests necessary data from the native SNMP agents of the managed devices or applications, such as routers, databases, computers etc. When using the NetGain Agent (<b>710</b>), the necessary data can also be requested from lightweight NetGain agents (<b>710</b>) installed on remote servers/hosts. These agents (<b>710</b>) can be used to get specific or custom data such as application outputs, results of scripts etc, securely. The monitors can also use the secure shell method (<b>712</b>) to access the required data.

0000Management Scope

0064In this embodiment, the appliance NetGain Enterprise Manager helps to manage a wide range of environments and technologies, including network-based or internet-based devices and services, computing platforms, systems and servers, applications and services. For networks, management can be extended to network devices such as routers, switches, modems, etc. Management can also be extended to standard network services such as RADIUS, Ping, Remote Ping, DNS, DHCP, DayTime, FTP, TFTP, etc. Examples will be Network interfaces: availability, input/output error rate, input/output utilization, input/output discard rate, input/output error rate, input/output packet rate etc.

0065For systems, management can be extended to Unix-based hosts such as Linux, Sun, IBM-AIX, HP-UX. Examples are CPU utilization, Memory utilization, Disk utilization. Management can be extended to Windows servers and clients as well as database servers such as Oracle, Sybase, Informix, MS-SQL etc. Examples include Cache hit ratio, Transaction rate, Network read/write rate, User connections, Tablespace/database utilization etc. Management of systems can also be extended to firewalls, email servers such as MS Exchange etc., Application servers such as Apache Tomcat, Web Logic etc., middleware and Specific in-house applications.

0066Along with the out-of-the-box provided functionality and management scope, it is modular and flexible enough to extend to new technologies, services and applications, by introducing custom-made plug-in modules, when required.

0000Auto-Discovery and Monitoring:

0067The example embodiment also provides a system to enable automatic discovery and monitoring of network elements such as systems, servers and the services and applications running on them. The auto-discovery process is shown in <figref idref="DRAWINGS">FIG. 8</figref>. The discovering (<b>800</b>) of network elements, services and applications running on them is carried out through multi-threaded discovery scanners using SNMP, Agent and other protocols. The multiple discovery scanners scan (<b>802</b>) the network for additional systems, services and applications to monitor and generate discovery records (<b>804</b>). At the same time in separate threads there are discovery handlers processing the newly created discovery records to create objects (<b>806</b>) for the monitors. Multi-threaded and pipe-line discovery enables the system to discover (<b>800</b>) network elements, services and applications faster. Modular architecture allows introducing future support for newer systems, services and applications.

0000Monitoring Architecture:

0068In order to support a large number of intelligent monitors while consuming minimal resources such as processor time, disk space and memory space, the monitoring architecture (<b>900</b>) as shown in <figref idref="DRAWINGS">FIG. 9</figref> is based on a complex multi-threaded object-oriented design. This enables the performance of effective monitoring (<b>900</b>) while maximizing the supported number of monitors within the available resources such as cpu-time, disk and memory space. A monitoring agent is responsible for monitoring a set of devices, services and applications; it periodically distributes the actual monitoring load across a large number of monitor workers running in separate threads. These monitor workers create (<b>902</b>) the monitor from its description on-demand and execute (<b>904</b>) it to get the monitor results. The creation (<b>902</b>) of monitor on demand reduces the memory space required to support a large number of monitors. The monitor results are processed (<b>906</b>) by the monitor workers to detect failure or degradation of service based on specified service level criteria (<b>908</b>) and then saved (<b>910</b>) to the performance DB.

0000SLA Management

0069The IT infrastructure managers would need the systems, services and applications in an enterprise to perform at an acceptable level and provide the required functions or services at a perceived service level considered to be satisfactory. To quantify and measure the acceptable and satisfactory levels of service and performance would greatly enhance the IT manager's view of the health of their infrastructure as well as their customer's perception of their services. By getting to know the up-to-date system health and customer's experience of their services the IT managers can protect revenue and enhance customer satisfaction.

0070The Service Level Agreements or SLAs of systems, services and applications in the enterprise help to define the acceptable levels of availability, performance and service levels. The SLAs could be agreements between the enterprise and the customers or could be the expected behavior for disruption-free IT operations.

0071In this embodiment, NetGain monitors help to ensure the SLAs are being honored while reflecting the real-time performance and service level status of the device, service or application it is monitoring. A monitor's SLAs are defined by their monitoring parameters and service level criteria.

0072The parameters of a monitor include the status of monitoring, for example, enabled or disabled, the monitoring interval between two discrete measurements, the period of timeout for a discrete measurement to be considered a failure, the number of retry attempts to be made as well as any other parameters specific to the monitor, such as IP address or port number etc.

0073The service level criteria of a monitor specify the rules for unacceptable values of measured parameters and the Service level agreement (SLA) thresholds, such as SLA warning threshold and SLA violation threshold.

0074In this example embodiment, a monitor can measure multiple parameters for a single measurement. Under the service level criteria, the rules of unacceptable values of these parameters specify whether the measured set of parameter values is unacceptable. In the event where the parameter values are unacceptable, the single/discrete measurement is considered a failure.

0075Under the service level criteria, the SLA thresholds define the percentage of failed single/discrete measurements over a specified period of time. The status of service level of a monitor can be in good, SLA warning or SLA violation over a specified period of time, based on these thresholds. The following will be a good example of this feature. Consider a website URL monitor. The single parameter ‘Response time in milliseconds’ can be used in a rule, specifying the unacceptable values, such as: Response time greater than 10,000 milliseconds=unacceptable, if it is specified that 50% of failed measurements lead to service level violation over any specified time period and in a day if there are 48 measurements, once every half an hour, then if 24 measurements or more fail, then the monitor is in SLA violation status. Similarly, in an hour if there are 2 measurements, once every half an hour, then if 1 measurement or more fail, then the monitor is in SLA violation status.

0000Scripting Engine:

0076In order to specify actions in scripts that resemble a high-level programming language such as Java, to execute at specified points of customization, a scripting engine is created. This provides a highly customizable solution with an easily programmable framework where in certain points of customization, such as, creation of objects, propagation of an event etc., the behavior of the system can be further customized by allowing for programming the system to perform flexible tasks using the APIs provided by the system itself.

0000Event/Alarm Correlation Engine

0077In this example embodiment, the appliance NetGain Enterprise Manager (<b>600</b>) provides unified management of alarms (<b>606</b>) from various disparate sources (<b>604</b>) such as devices, services and applications. The fault information in alarms are put through an intelligent set of correlation rules to suppress redundant information, isolate and quickly identify and resolve cause of the problem. The alarm management process (<b>1000</b>) is shown in <figref idref="DRAWINGS">FIG. 10</figref>.

0078The alarm correlation rules are applied to each alarm to be propagated with regards to other alarm information as specified in the rules. The supported correlation rules are alarm root cause rules, alarm threshold count rules and alarm transient correlation rules.

0079The alarm root cause rule defines the relation of a root cause object's alarm to the dependant object's alarm in a time window. Such rules can be defined for well-known dependencies, such as a web-server and a web-site. If a root cause alarm arrives (<b>1002</b>) prior to the dependant alarms, the dependant alarms are not propagated till the root cause is fixed within a time window. A check for other alarms is also carried out as shown in stage <b>1004</b>. This behavior could help to quickly identify the root cause, while helping to focus away from the dependant alarms. The following is an example of this alarm. If a web-server is down the web-site would be down as well. Therefore if a root-cause alarm ‘web-server down’ is present within a reasonable amount of time prior to the arrival of ‘web-site down’ alarm, then the ‘web-site down’ alarm is not sent.

0080The alarm transient correlation rules are intended for a flood of alarms that notify a changing attribute, for instance state of a device. The final value of the attribute is considered (<b>1006</b>) while ignoring the transient values using this rule, over a specified time window. The following is an example of this alarm. If a state of a communication port changes very frequently, say every few micro-seconds, it could send a changing status signals as alarms. The transient rule helps to receive the final status during a given time window, say a second.

0081The alarm threshold count rule specifies the threshold value of the number of times a particular type of alarm should be allowed to propagate. This rule helps to suppress ‘alarm flood’ or repetitive alarms of the same type from the same source. The following is an example of this alarm. There could be a device or service such as a communication port which would send multiple similar alarms repeatedly every few micro-second on an existing error. The threshold count rule can help to de-duplicate (<b>1008</b>) the multiple alarms and present them as a single alarm if they arrive within a given time window, say a second.

0000Inventory Management

0082Effective IT infrastructure management practices need accurate physical inventory, due to the fact that knowing what is available is necessary to plan to manage and control the assets effectively. The asset management practice can only succeed if the underlying asset repository is accurate and it must be maintained and validated by periodic checks on the physical inventories or over time the repository will become inaccurate. Experience shows inaccurate asset repository can be worse than no repository since users can make important decisions based on very flawed data.

0083In this embodiment, the appliance NetGain Enterprise Manager (<b>600</b>) keeps track of the managed devices and related inventory, through a process of auto-discovery and inventory query. It helps to periodically check the physical and logical assets through communication processes (<b>602</b>) while being able to query and classify by their types and sub-types.

0084The auto-discovery process helps to populate the inventory database with up-to-date information on devices. Their attributes such as, the type of Operating System, other attributes, including SNMP attributes, services, devices installed on the host, processes running on the host and the software installed on the host are recorded in the inventory database.

0085The users can perform inventory queries based on the types and subtypes of resources (<b>604</b>) such as, network routers, network switches, network bridges, computers, performance monitors, Operating systems, protocol based devices, categories and the IP Address.

0086The types of resources may be further categorized and sub-categorized where necessary. The inventories queried are with details of the resource such as services, monitors and other related objects.

0000Automating Management Tasks

0087To increase business process efficiency, quickening the pace of information exchange and bridging the semi-automated and manual tasks becomes an utmost priority. For instance, routine IT infrastructure issues such as notifications could be automatically generated, assigned and sent to the responsible groups or individuals swiftly. The automation should be flexible enough to be adjusted and introduced into the system efficiently with minimal delay.

0088In this embodiment, the appliance NetGain Enterprise Manager (<b>600</b>) provides very flexible automation framework to trigger various tasks on incoming fault or service level information. It is a direct result of integration and sharing of real-time information in a common model across the components.

0000Notification

0089In this example embodiment, each user with a user account in the NetGain Enterprise Manager can create rules (<b>1102</b>) to specify various ways of notifying himself about creation or changes in the status of SLA, and alarms (<b>900</b>). Such notifications can be in different templates (<b>1104</b>) such as in the form of e-mails, SMS, popup-window or sound. The process of report generation from monitors can be seen in <figref idref="DRAWINGS">FIG. 11</figref>.

0000Notification Engine:

0090In the embodiment, the appliance is required to distribute notifications efficiently and reliably. Efficient and reliable notification of users is carried out by the central notification engine which processes the asynchronous requests. The central notification engine operates on a set of notification rules (<b>1010</b>) for each user. It receives notification causes such as alarms or service level changes. These notification causes are relayed (<b>1012</b>) to the users as specified by the notification rules (<b>1010</b>). The notification rules (<b>1010</b>) specify the description (<b>1106</b>) of the cause, such as type of an alarm or object that caused the alarm or service level change etc. The rule also specifies the type of notification such as email, SMS, sound or a pop-up window etc.

0000Auto-Action on Alarms

0091Auto-actions on alarms are configured to be executed when an alarm is generated in the system. The auto-actions that match the ‘Filtering Criteria’ will be invoked (<b>1014</b>) for each alarm generated. The different types of alarm auto-actions are the script auto-action where a specified script is executed and the acknowledge auto-action where the alarm is auto-acknowledged and assigned to a specified user (<b>1016</b>).

0000Advantages of Example Embodiment Over Other Appliances:

0000Integrated all-in-One Functionality

0092NetGain Enterprise Manager provides out-of-the-box integrated functionality spanning across inventory management, fault management, topology management, and performance and SLA management, using shared information and data model.

0093The integrated functionality enables faster and more efficient information sharing across the various functionalities which in-turn would make end-to-end automation affordable and immediate reality. Automation combined with faster and more efficient information sharing can help to meet the critical business goals such as to reduce cost, increase efficiency, reduce service time-to-market, accelerate time-to-revenue, ensure quality of service and guarantee customer satisfaction.

0094The cost to integrate products addressing different functionalities, such as inventory management, service level management, fault management etc., is eliminated. Even in the integration of best of breed products, the format differences, content duplication and mismatches in files or database entries create a significant bottle-neck in both performance and information-flow.

0000Quick Installation &amp; Deployment

0095The network appliance concept enables NetGain Enterprise Manager to be rapidly deployed without any installation hassles and requirements. It can be mounted in a rack and hooked onto the LAN, while the users can login and perform their management tasks, including configuration through their favourite web browsers.

0096Typical turn-around period of deployment, installation and basic training such that users could perform basic management of their network, services and application could be expected to be a matter of a day or two.

0000Ease of Learning and Usage

0097The system is presented in an intuitive and user friendly manner, while the usage and user interface has been designed to have a very quick learning curve.

0098Traditionally complexity of usage means increase of cost for training as well as the need for trained man-power. While maintaining the simplicity of usage with a simpler facade to complex problems, NetGain Enterprise Manager provides a simple and easy solution for non-experts to manage the system at the level of a true expert.

0099The NetGain Enterprise Manager is a unique network appliance based enterprise management solution that offers out-of-the-box integrated management of network services and applications, with holistic support of the hardware and software areas of the solution. It provides a wide range of integrated functionality spanning service level management, topology management, alarm management and inventory management and helps to automate tasks with shared data and up-to-date information.

0100The modular and flexible architecture and central server concept helps the solution to meet the growing needs of the IT infrastructure by making upgrades and maintenance hassle-free. With its rapid deployment and ease of usage it promises faster return on investment, while keeping the cost low per managed system. The integrated end-to-end management of service delivery infrastructure would certainly help the enterprise towards achieving its business goals.

0101The method and system of the example embodiment can be implemented on a computer system (<b>1200</b>), schematically shown in <figref idref="DRAWINGS">FIG. 12</figref>. It may be implemented as software, such as a computer program being executed within the computer system (<b>1200</b>), and instructing the computer system (<b>1200</b>) to conduct the method of the example embodiment.

0102The computer system (<b>1200</b>) comprises a computer module (<b>1202</b>), input modules such as a keyboard (<b>1204</b>) and mouse (<b>1206</b>) and a plurality of output devices such as a display (<b>1208</b>), and printer (<b>1210</b>).

0103The computer module (<b>1202</b>) is connected to a computer network (<b>1212</b>) via a suitable transceiver device (<b>1214</b>), to enable access to e.g. the Internet or other network systems such as Local Area Network (LAN) or Wide Area Network (WAN).

0104The computer module (<b>1202</b>) in the example includes a processor (<b>1218</b>), a Random Access Memory (RAM) (<b>1220</b>) and a Read Only Memory (ROM) (<b>1222</b>). The computer module (<b>1202</b>) also includes a number of Input/Output (I/O) interfaces, for example I/O interface (<b>1224</b>) to the display (<b>1208</b>), and I/O interface (<b>1226</b>) to the keyboard (<b>1204</b>).

0105The components of the computer module (<b>1202</b>) typically communicate via an interconnected bus (<b>1228</b>) and in a manner known to the person skilled in the relevant art.

0106The application program is typically supplied to the user of the computer system (<b>1200</b>) encoded on a data storage medium such as a CD-ROM or floppy disk and read utilising a corresponding data storage medium drive of a data storage device (<b>1230</b>). The application program is read and controlled in its execution by the processor (<b>1218</b>). Intermediate storage of program data maybe accomplished using RAM (<b>1220</b>).

0107<figref idref="DRAWINGS">FIG. 13</figref> shows a flowchart illustrating a method for managing a network in an example embodiment. At step <b>1300</b>, a central bus element is provided. At step <b>1302</b>, a plurality of network management modules are coupled to the central bus element. At step <b>1304</b>, a server element is coupled to the central bus element. At step <b>1306</b>, a network interface is provided for the central bus element to be interfaced with a network to be managed, and, at step <b>1308</b>, network management functions executed by the network management modules are remotely accessed through the server element via the network interface.

0108It will be appreciated by a person skilled in the art that numerous variations and/or modifications may be made to the present invention as shown in the specific embodiments without departing from the spirit or scope of the invention as broadly described. The present embodiments are, therefore, to be considered in all respects to be illustrative and not restrictive.