CN100426756C - Network management system for integrative supervision and management of application software system and host resource - Google Patents

Abstract

The invention relates to a network manage system, used in detecting software and host, wherein it comprises device access module for building projection software system and public information mode of host, while the public information mode has logic network unit layer whose logic network units are used in each part of projection software system, with inquired standard interface; physical network unit layer with physical network units for projecting the hosts of each part, with inquired standard interface, and modular service layer for projecting the logic network unit and physical network unit. And the network manage system also comprises service network subsystem for using the standard interface of logic network unit layer to manage the software system, and an IP network manage subsystem for using the standard interface of physical network unit layer to manage host. The invention also provides relative network manage method.

Description

Network management system and method for realizing integrated supervision of application software system and host resources

technical field

The present invention relates to the communication field, and more specifically, relates to a network management system and method for realizing comprehensive supervision of application software systems and host resources.

Background technique

There are a large number of different hardware devices and application software systems of different scales distributed in the carrier-class network. They are abstracted as Network Elements (Network Elements) in the Network Element Management Layer of the Telecom Management Network (TMN). Network element for short), in which various network devices, servers and other hardware devices are usually called physical network elements (Physical Network Element, abbreviated as PNE), which are located at the IP level; and various application software systems are abstracted into logical network elements (Logic NetworkElement, abbreviated as LNE). A logical network element generally consists of several modules (Module), and each module contains several process entities running on a server (host). These modules and process entities can be deployed on one or more servers (hosts), and these resources can be shared among multiple logical network elements.

Fig. 1 shows a simple network management model according to the related art. The NEs in the figure may be physical network elements or logical network elements.

In this network management model, the actual deployment of logical network elements can be divided into four levels: logical network element (LNE), module (Module), process entity (Process) and host. According to the sequence from top to bottom, each Each layer is dependent on its next layer. According to the transitivity of dependencies, the logical network elements at the top layer have dependencies on the hosts at the bottom layer, and these hosts are abstracted as physical network elements in the network element management layer of the telecom management network, so there is a relationship between logical network elements and physical network elements rely. Fig. 2 shows a hierarchical structure of logical network element deployment according to related technologies.

In Figure 2, this kind of dependence is embodied in that the operating status and processing performance of the host (such as whether the CPU is too busy, whether the memory is sufficient, whether the hard disk has enough free space, etc.) will directly affect the overall operating status of the software system, so Ensuring the availability, reliability, and performance of the host where the software system is deployed and running is one of the foundations for ensuring the normal operation of the software system, so it is necessary to combine the monitoring and management of the host, process, and application software system.

For the specific implementation of many Network Management Systems (NMS), the management of hosts and processes is generally included in the IP network management, while the management of software systems and their modules is included in the closely related software system product manufacturers. Service network management is monitored and managed by these two different network management systems.

The industry has formed some relatively mature industrial standards and application solutions for the supervision of the host itself. According to the RFC2790 standard, a unified and public host resource management model is defined, and the management interface of hardware resources such as CPU, network device (network card), printer, disk (hard disk, floppy disk, CD, etc.), keyboard, Modem, port, etc. is determined; RFC1514 The standard provides a management interface for the utilization rate of storage entities (memory, virtual memory, disk, etc.); all types of hosts generally implement the content defined in the above standards, and implementers of the network management system can implement them at a relatively small cost. Realize the host supervision function.

A network management solution for supervising application software systems and host resources in the related art will be described below with reference to the drawings and embodiments.

Fig. 3 shows a network management system module division scheme provided according to related technologies. In this solution, the network management system modules are divided as follows:

The software system, process, and host are managed separately by the service network management and IP network management subsystems integrated in a large network management system, maintaining consistent interface features and user operating habits, and sharing the same basic functional subsystems (such as alarm, performance, data, etc.) collection and other subsystems), only the simplest interface integration is satisfied. There is no business logic correlation between the service network management and the IP network management subsystem.

However, since the software system and the host computer are monitored and managed by different network management subsystems, the two subsystems do not share relevant management information and their functions do not communicate with each other, so the dependency information between the software system and the host computer is lost. , The impact of the host's operating status and performance on the software system cannot be directly expressed by the system itself, and can only be discovered and identified manually.

In addition, since the two network management subsystems may actually be maintained by different personnel, this effect cannot be detected in a timely and effective manner, so that it is actually impossible to effectively shorten the equipment maintenance cycle and reduce maintenance costs.

A more representative example: For example, a host generates an alarm because the remaining disk space is insufficient, but the maintenance personnel in charge of the software system do not know that the alarm is generated until the disk is completely full, causing the software system to run abnormally and generate an alarm , Therefore, the maintenance personnel cannot give an early warning before the software system alarm occurs, and cannot quickly locate the root cause of the alarm after the alarm is generated.

Another network management solution is also provided in the related art.

According to this scheme, the software system agent (Agent) module deployed in the software system is customized and developed, so that it can collect and store the host monitoring information such as the CPU usage rate, memory usage rate, and disk usage of the host, and provide corresponding interface, so that the network management side can access the information while accessing the management target application software and business modules; at the same time, the software system pre-defines some host-related alarms, and the software system agent collects and reports these alarms; the business network management subsystem also Develop for the host monitoring interface and provide a management interface for host monitoring. That is to say, the association between services and hardware resource nodes is realized by the network element side.

However, this solution mainly has the following disadvantages:

(1) The standardized and relatively mature host management interface cannot be used, and the managed software system needs to realize the collection, storage and reporting of host information by itself, which increases the complexity and development difficulty of application software and business modules;

(2) There is a lack of corresponding industry standards, the host monitoring functions provided by each managed software system are inconsistent, and the interfaces are not compatible;

(3) The network management system developer cannot provide a consistent host monitoring model, and has to customize corresponding host monitoring models and interfaces for various managed software systems, resulting in high access management costs.

It can be seen from the above description that the solutions of the above-mentioned related technologies have their own problems. Therefore, people need a new network management solution that can solve the problems in the above-mentioned related technologies.

Contents of the invention

The present invention aims to provide a solution capable of comprehensively supervising the application software system and the host where it is deployed. This solution solves the problems of the complexity and development difficulty of the business software system and business modules in the above-mentioned related technologies.

According to one aspect of the present invention, a network management system is provided, which is used for comprehensive supervision of the software system and its deployed host, including: a device access module, used to create a public information model of the mapping software system and its deployed host, public The information model includes: logical network element layer, each logical network element included in it is used to map various parts of the software system, and has a standard interface available for query; physical network element layer, each physical network element included in it is used for mapping The hosts deployed in each part have standard interfaces that can be queried; and the module service layer is used to map the corresponding relationship between logical network elements and physical network elements; the network management system also includes: business network management The standard interface of the network element layer is used to supervise the software system; and the IP network management subsystem is used to supervise the host computer through the standard interface of the physical network element layer.

In the above-mentioned network management system, the device access module is used to record the IP address of the host where the logical network element is deployed, and locate the physical network element according to the IP address, create an association between the logical network element and the physical network element, and associate the Information is stored in the module service layer.

In the above-mentioned network management system, the device access module is used to find the matching logical network element through the host IP address, create an association between the logical network element and the physical network element, and store the association information in the module service layer middle.

In the above network management system, the service network management subsystem includes at least one of the following: configuration management subsystem, security management subsystem, fault management subsystem, performance management subsystem, billing management subsystem, service management subsystem, alarm subsystem System, data acquisition subsystem; IP network management subsystem includes at least one of the following: configuration management subsystem, safety management subsystem, fault management subsystem, performance management subsystem, alarm subsystem, data acquisition subsystem.

In the above-mentioned network management system, both the service network management subsystem and the IP network management subsystem include alarm, performance management, and configuration management subsystems, and the alarm, performance management, and configuration management subsystems all include preprocessing modules, which are used for query The association information of logical network elements and physical network elements stored in the public information model enables the subsystem to identify the relationship between logical network elements and physical network elements.

In the above-mentioned network management system, after the host computer has a hardware failure and sends an alarm, the IP network management subsystem is used to receive and process the alarm, and the preprocessing module of the alarm subsystem in the IP network management subsystem The association information between physical network elements and logical network elements is used to query which logical network elements are affected, and notify the service network management subsystem to handle accordingly, so that the alarms that have occurred on the host can be observed on the service network management subsystem side.

In the above-mentioned network management system, if an alarm on the host may cause abnormal operation of the software system, the service network management subsystem will issue an early warning and notify the service maintenance personnel to take measures.

In the above-mentioned network management system, after the monitoring task or fault detection task of monitoring the operation status of the physical network element is created on the logical network element, the preprocessing module of the performance management subsystem in the IP network management subsystem is used to send relevant parameters to the IP The network management subsystem, the IP network management subsystem is used to collect the status data of the physical network elements according to these parameters, and send the collected results to the status monitoring interface in real time.

In the above network management system, the service network management subsystem and the IP network management subsystem are divided based on the management field, and they are divided into a service topology view and a host topology view.

According to another aspect of the present invention, a network management method is provided for comprehensive supervision of a software system and its deployed host, comprising the following steps: creating a public information model that maps the software system and its deployed host, the public information model includes: Logical network element layer, each logical network element it includes is used to map each part of the software system, and has a standard interface available for query; physical network element layer, each physical network element it includes is used to map each part deployed The host has a standard interface available for query; and the module service layer is used to map the corresponding relationship between logical network elements and physical network elements; the service network management subsystem supervises the software system through the standard interface of the logical network element layer; and The IP network management subsystem supervises the host through the standard interface of the physical network element layer.

In the above-mentioned network management method, creating the physical network element layer in the public information model includes the following steps: record the IP address of the host where the logical network element is deployed, and map the physical network element according to the IP address, and then connect the logical network element and the physical network element Create an association between them, and store the association information in the module service layer.

In the above-mentioned network management method, creating the logical network element layer in the public information model includes the following steps: searching for a matching logical network element through the host IP address, and creating an association between the logical network element and the physical network element, and Association information is stored in the module service layer.

In the above network management method, the service network management subsystem includes at least one of the following: configuration management subsystem, safety management subsystem, fault management subsystem, performance management subsystem, billing management subsystem, service management subsystem, alarm subsystem System, data acquisition subsystem; IP network management subsystem includes at least one of the following: configuration management subsystem, safety management subsystem, fault management subsystem, performance management subsystem, alarm subsystem, data acquisition subsystem.

In the above-mentioned network management method, the service network management subsystem and the IP network management subsystem both include alarm, performance management, and configuration management subsystems, and the alarm, performance management, and configuration management subsystems all include preprocessing modules, and the supervisory host includes the following steps: The preprocessing module queries the association information of the logical network element and the physical network element stored in the public information model, so that the subsystem can identify the relationship between the logical network element and the physical network element.

In the above-mentioned network management method, supervising the host includes the following steps: after a hardware failure occurs in the host and sends an alarm, the IP network management subsystem receives and processes the alarm, and the preprocessing module of the alarm subsystem in the IP network management subsystem is based on the data stored in the public In the information model, use the correlation information between physical network elements and logical network elements to query which logical network elements are affected, and notify the service network management subsystem to deal with it accordingly, so that the service network management subsystem can observe the events that have occurred on the host alarm.

In the above-mentioned network management method, supervising the host includes the following steps: if an alarm on the host may cause abnormal operation of the software system, the service network management subsystem will issue an early warning and notify the service maintenance personnel to take measures.

In the above-mentioned network management method, the supervisory host includes the following steps: After creating a monitoring task or a fault detection task for monitoring the health of the physical network element on the logical network element, the preprocessing module of the performance management subsystem in the IP network management subsystem will The parameters are sent to the IP network management subsystem, and the IP network management subsystem collects the status data of the physical network elements according to these parameters, and sends the collected results to the status monitoring interface in real time.

In the above-mentioned network management method, the service network management subsystem and the IP network management subsystem are divided based on the management field, and the two are divided into a service topology view and a host topology view.

From the above description, it can be seen that the present invention makes full use of the standard interface supervised by the host, and does not require large-scale adaptability development of the application software system, and the implementation of the network management system is relatively simple.

Specifically, the present invention achieves the following technical effects:

By integrating the host supervision function in the service network management subsystem to realize the comprehensive supervision of the application software system and the host where it is deployed, the occurrence rate of software system failures caused by hardware failures can be effectively reduced (by timely early warning), and the system can be improved. Improve the troubleshooting efficiency of such faults, reduce the maintenance cost of the application software system, and reduce the overall development cost of the network management system and application software system providers.

The network management system does not distinguish between service network management and IP network management subsystems, but only distinguishes different topology views (service topology view and host topology view), and provides these different types of views at the same time after the application software system is connected. IP addresses automatically perform monitoring for associated hosts.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Description of drawings

The accompanying drawings described here are used to provide a further understanding of the present invention and constitute a part of the application. The schematic embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations to the present invention. In the attached picture:

Fig. 1 shows a simple network management model according to the related art;

FIG. 2 shows a hierarchical structure of logical network element deployment according to related technologies;

Fig. 3 shows a kind of network management system module division scheme provided according to the related art;

Fig. 4 shows the block diagram of the network management system according to the embodiment of the present invention;

FIG. 5 shows a network element management information model according to an embodiment of the present invention;

FIG. 6 shows a network element management information model according to an embodiment of the present invention;

Figure 7 shows a network management system according to an embodiment of the present invention; and

Fig. 8 shows a flowchart of a network management method according to an embodiment of the present invention.

Detailed ways

The present invention will be described in detail below with reference to the accompanying drawings and in combination with embodiments.

The present invention proposes that the application software system and the host are still managed separately by the service network management and IP network management subsystems integrated in a large network management system, and the two maintain consistent interface characteristics and user operating habits, and share the same basic function modules (such as Alarm, performance, data acquisition and other modules), with data integration as the core, while satisfying interface integration and function integration. The data integration between the application software system and the host management information model is realized based on the IP address.

Add a dedicated equipment access subsystem to the original system, establish a public information model, and add some preprocessing modules to other subsystems, so as to completely associate the host computer and the application in the model and each associated function.

Fig. 4 shows a block diagram of a network management system according to an embodiment of the present invention. As shown in FIG. 4, a network management system 400 according to an embodiment of the present invention includes:

The device access module 406 is used to create a public information model that maps the software system and its deployed host. The public information model includes: a logical network element layer, and each logical network element included in it is used to map various parts of the software system, with The standard interface available for query; the physical network element layer, each physical network element included in it is used to map the hosts deployed in each part, and has a standard interface available for query; and the module service layer, used for mapping logical network elements and Correspondence between physical network elements;

The service network management subsystem 404 is used to supervise the software system through the standard interface of the logical network element layer; and

The IP network management subsystem 402 is used for supervising the host through the standard interface of the physical network element layer.

Optionally, the device access module 406 is configured to record the IP address of the host where the logical network element is deployed, locate the physical network element according to the IP address, create an association between the logical network element and the physical network element, and store the association information in In the module service layer.

Optionally, the device access module 406 is configured to search for a matching logical network element through the host IP address, create an association between the logical network element and the physical network element, and store the association information in the module service layer.

Optionally, the service network management subsystem 404 includes at least one of the following: configuration management subsystem, security management subsystem, fault management subsystem, performance management subsystem, billing management subsystem, service management subsystem, alarm subsystem, Data acquisition subsystem; the IP network management subsystem includes at least one of the following: configuration management subsystem, safety management subsystem, fault management subsystem, performance management subsystem, alarm subsystem, and data acquisition subsystem.

Optionally, both the service network management subsystem 404 and the IP network management subsystem 402 include alarm, performance management, and configuration management subsystems, and the alarm, performance management, and configuration management subsystems all include preprocessing modules, and these preprocessing modules are used for querying and storing The association information between logical network elements and physical network elements in the public information model enables the subsystem to identify the relationship between logical network elements and physical network elements.

Optionally, after a hardware fault occurs in the host and sends an alarm, the IP network management subsystem 402 is used to receive and process the alarm, and the preprocessing module of the alarm subsystem in the IP network management subsystem 402 is based on the physical The associated information between network elements and logical network elements is used to query which logical network elements are affected, and notify the service network management subsystem to handle accordingly, so that the alarms that have occurred on the host can be observed on the service network management subsystem side.

Optionally, if an alarm on the host may cause abnormal operation of the software system, the service network management subsystem 404 will issue an early warning and notify service maintenance personnel to take measures.

Optionally, after creating a monitoring task or a fault detection task for monitoring the operating status of a physical network element on a logical network element, the preprocessing module of the performance management subsystem in the IP network management subsystem is used to send relevant parameters to the IP network management subsystem 402. The IP network management subsystem 402 is used to collect status data of physical network elements according to these parameters, and send the collected results to the status monitoring interface in real time.

Optionally, the service network management subsystem 404 and the IP network management subsystem 402 are divided based on the management field, and they are divided into a service topology view and a host topology view.

Fig. 8 shows the flowchart of the network management method according to the embodiment of the present invention, and it comprises the following steps:

Step S802, creating a public information model for mapping the software system and its deployed hosts. The public information model includes: a logical network element layer, each logical network element included in it is used to map various parts of the software system, and has standards that can be queried Interface; physical network element layer, each physical network element included is used to map the hosts deployed in each part, with standard interfaces available for query; and module service layer, used to map between logical network elements and physical network elements corresponding relationship;

Step S804, the service network management subsystem monitors the software system through the standard interface of the logical network element layer; and

Step S806, the IP network management subsystem supervises the host through the standard interface of the physical network element layer.

Optionally, creating the physical network element layer in the common information model includes the following steps: record the IP address of the host where the logical network element is deployed, and map the physical network element according to the IP address, and then create a network element between the logical network element and the physical network element. Association, store association information in the module service layer.

Optionally, creating the logical network element layer in the public information model includes the following steps: searching for a matching logical network element through the host IP address, creating an association between the logical network element and the physical network element, and storing the association information in the module service layer.

Optionally, the service network management subsystem includes at least one of the following: configuration management subsystem, security management subsystem, fault management subsystem, performance management subsystem, billing management subsystem, service management subsystem, alarm subsystem, data The acquisition subsystem; the IP network management subsystem includes at least one of the following: configuration management subsystem, safety management subsystem, fault management subsystem, performance management subsystem, alarm subsystem, and data acquisition subsystem.

Optionally, both the service network management subsystem and the IP network management subsystem include alarm, performance management, and configuration management subsystems, and the alarm, performance management, and configuration management subsystems all include preprocessing modules, and the supervisory host includes the following steps: These preprocessing modules Query the association information between logical network elements and physical network elements stored in the public information model, so that the subsystem can identify the relationship between logical network elements and physical network elements.

Optionally, supervising the host computer includes the following steps: after a hardware failure occurs in the host computer and an alarm is sent, the IP network management subsystem receives and processes the alarm, and the preprocessing module of the alarm subsystem in the IP network management subsystem is stored in the public information model according to The associated information between physical network elements and logical network elements can be used to query which logical network elements are affected, and notify the service network management subsystem to handle accordingly, so that the alarms that have occurred on the host can be observed on the service network management subsystem side.

Optionally, supervising the host includes the following steps: if an alarm on the host may cause abnormal operation of the software system, the service network management subsystem will issue an early warning and notify service maintenance personnel to take measures.

Optionally, the supervisory host includes the following steps: After creating a monitoring task or a fault detection task for monitoring the health of the physical network element on the logical network element, the preprocessing module of the performance management subsystem in the IP network management subsystem sends relevant parameters to IP network management subsystem, the IP network management subsystem collects status data of physical network elements according to these parameters, and sends the collected results to the status monitoring interface in real time.

Optionally, the service network management subsystem and the IP network management subsystem are divided based on the management field, and the two are divided into a service topology view and a host topology view.

The corresponding network element management information model is described in detail below.

Fig. 5 shows a network element management information model according to an embodiment of the present invention.

As shown in Figure 5, the network element management information model is divided into four layers: logical network element (LNE)/module (Module)/service (Service)/host (Host); where LNE is the mapping of the application software system, and Service is the process Mapping of entities; the Module object stores the network element object identifier (NEID) containing the object, each Service object stores the module identifier (ModuleID) containing the object, and the Service object also stores the host IP where the service runs address. The Host object is a map of host resources.

Fig. 6 shows a network element management information model according to an embodiment of the present invention.

For some application software systems with less complex structures, each module is a separate process entity. Therefore, according to another embodiment of the present invention, as shown in FIG. 6, the network element management information model can also be simplified to a certain extent: the Service layer is merged into the Module layer, and the Module object stores the network element object identifier (NEID) containing the object. ), also stores the IP address of the host where the Module runs.

Fig. 7 shows a network management system according to an embodiment of the present invention. In this embodiment, the basic process of comprehensive supervision of the application software system and the host is as follows:

A. The agent of the application software system provides the deployment information of each part of the application software system (including the IP address of the host);

B. The supervision of the host is based on the industry standard interface of the industry;

C. When the application software system is connected to the service network management subsystem for management, the device access subsystem queries the deployment information of each part of the application software system from the agent and stores it in the public model;

D. If the device access module finds that the host where the application software system is deployed has been accessed by the IP network management, it will create a relationship between the logical network element and the physical network element after the abstract mapping between the application software system and the host computer, and identify the logical network element for Dependence on physical network elements, each functional module in the subsequent process will query and use these relationships to perform some associated operations;

E. After the host has a hardware failure and sends an alarm, the IP network management subsystem receives and processes the alarm, and the preprocessing module notifies the service network management subsystem. If a host where a software system is deployed fails, the service network management subsystem receives the notification. Reset the alarm state of the logical network element corresponding to the target software system;

F. When business maintenance personnel query the alarm status of logical network elements, they can observe the hardware alarms generated on the host where the software system is deployed. If some hardware alarms may eventually lead to abnormal operation of the software system, they need to notify the host maintenance personnel to repair them in time These hardware alarms; when business maintenance personnel confirm and clear these alarms, the corresponding operation commands are finally issued to the corresponding hosts;

G. After business maintenance personnel create monitoring tasks or fault detection tasks for monitoring the running status of hosts on logical network elements, the performance management preprocessing module sends relevant parameters to the IP network management subsystem, and the IP network management subsystem collects target hosts based on these parameters status data, and send the collected results to the status monitoring interface in real time; once the service maintenance personnel find that the target host is running abnormally, they will notify the IP service maintenance personnel to deal with it in time to restore the normal operation of the target host;

H. If a module of the software system generates specific alarms, the business maintenance personnel first check whether some specific alarms have been generated on the host where the module is deployed, and confirm whether these alarms will trigger target alarms; if the software failure is confirmed by the host hardware failure If triggered, the host maintainer is notified to fix it.

Processes C and D are also applicable to the situation where the application software system is equal to the relevant host equipment connected to the network management, but the former queries the relevant physical network elements according to the host IP where the application software system module is deployed, and the latter queries the relevant physical network elements through the host IP. logical network element. In addition, the business maintenance personnel and the host maintenance personnel may be the same group of people, and the above process is also applicable to this situation.

The network management system that realizes the comprehensive supervision of the application software system and the host where it is deployed includes, in addition to traditional functional subsystems such as configuration management, fault management, performance management, and security management, it also includes a public model management module, a fault management preprocessing The processing module and the extended device access module, among which the public model management module is responsible for storing and managing various objects such as NE, Module and Service and the relationship between them, and the fault management preprocessing module is responsible for the host (physical network element) The alarms are associated with the corresponding logical network elements, the performance management preprocessing module is responsible for associating part of the performance statistics tasks and monitoring tasks preset on the host (physical network elements) with the corresponding logical network elements, and the extended device access module It is responsible for discovering and completing the association between physical network elements and logical network elements during the process of device access.

From the above description, it can be seen that the present invention makes full use of the standard interface supervised by the host, and does not require large-scale adaptability development of the application software system, and the implementation of the network management system is relatively simple.

Specifically, the present invention achieves the following technical effects:

By integrating the host supervision function in the service network management subsystem to realize the comprehensive supervision of the application software system and the host where it is deployed, the occurrence rate of software system failures caused by hardware failures can be effectively reduced (by timely early warning), and the system can be improved. Improve the troubleshooting efficiency of such faults, reduce the maintenance cost of the application software system, and reduce the overall development cost of the network management system and application software system providers.

The network management system does not distinguish between service network management and IP network management subsystems, but only distinguishes different topology views (service topology view and host topology view), and provides these different types of views at the same time after the application software system is connected. IP addresses automatically perform monitoring for associated hosts.

Obviously, those skilled in the art should understand that each module or each step of the above-mentioned present invention can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network formed by multiple computing devices Optionally, they can be implemented with program codes executable by a computing device, so that they can be stored in a storage device and executed by a computing device, or they can be made into individual integrated circuit modules, or they can be integrated into Multiple modules or steps are fabricated into a single integrated circuit module to realize. As such, the present invention is not limited to any specific combination of hardware and software. It should be understood that changes in these specific implementations are obvious to those skilled in the art and do not depart from the spirit protection scope of the present invention.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (18)

1. A network management system, used for integrated supervisory software system and deployed host computer thereof, is characterized in that, comprising: A device access module, configured to create a public information model that maps the software system and its deployed host, the public information model includes: Logical network element layer, each logical network element included in it is used to map various parts of the software system, and has a standard interface available for query; The physical network element layer, each physical network element included in it is used to map the hosts deployed by the various parts, and has a standard interface available for query; and A module service layer, configured to map the correspondence between the logical network element and the physical network element; The network management system also includes: A service network management subsystem, configured to supervise the software system through the standard interface of the logical network element layer; and The IP network management subsystem is used for supervising the host through the standard interface of the physical network element layer. 2. The network management system according to claim 1, wherein the device access module is configured to locate the physical network according to the IP address by recording the IP address of the host on which the logical network element is deployed. Create an association between the logical network element and the physical network element, and store the association information in the module service layer. 3. The network management system according to claim 1, wherein the device access module is configured to search for the matching logical network element through the host IP address, and connect the logical network element with the logical network element. Create an association between the physical network elements, and store the association information in the module service layer. 4. The network management system according to claim 1, wherein the service network management subsystem comprises at least one of the following: configuration management subsystem, safety management subsystem, fault management subsystem, performance management subsystem, billing Management subsystem, service management subsystem, alarm subsystem, data acquisition subsystem; the IP network management subsystem includes at least one of the following: configuration management subsystem, security management subsystem, fault management subsystem, performance management subsystem, Alarm subsystem, data acquisition subsystem. 5. The network management system according to claim 1, wherein the service network management subsystem and the IP network management subsystem all include an alarm, performance management, configuration management subsystem, and the alarm, performance management, configuration management The subsystems all include preprocessing modules, and these preprocessing modules are used to query the association information between logical network elements and physical network elements stored in the public information model, so that the subsystems can identify the relationship between logical network elements and physical network elements. relation. 6. The network management system according to claim 5, wherein, after a hardware failure occurs in the host and an alarm is sent, the IP network management subsystem is used to receive and process the alarm, and the IP network management subsystem in the IP network management subsystem The preprocessing module of the alarm subsystem inquires which logical network elements are affected according to the association information between physical network elements and logical network elements stored in the public information model, and notifies the service network management subsystem to deal with it accordingly. The system side can observe the alarms that have occurred on the host. 7. The network management system according to claim 6, wherein, if the alarm generated on the host may cause the software system to run abnormally, the service network management subsystem will issue an early warning and notify service maintenance personnel to take measures. 8. The network management system according to claim 5, characterized in that, after the monitoring task or the fault detection task of monitoring the physical network element operating condition is created on the logical network element, the performance management subsystem in the IP network management subsystem The preprocessing module is used to send relevant parameters to the IP network management subsystem, and the IP network management subsystem is used to collect status data of physical network elements according to these parameters, and send the collected results to the status monitoring interface in real time. 9. The network management system according to claim 1, characterized in that, the service network management subsystem and the IP network management subsystem are divided based on management fields, and the two are divided into a service topology view and a host topology view. 10. A network management method, used for comprehensive supervision software system and the deployed host thereof, is characterized in that, comprising the following steps: Create a common information model that maps the software system and its deployed host, the common information model includes: Logical network element layer, each logical network element included in it is used to map various parts of the software system, and has a standard interface available for query; The physical network element layer, each physical network element included in it is used to map the hosts deployed by the various parts, and has a standard interface available for query; and A module service layer, configured to map the correspondence between the logical network element and the physical network element; The service network management subsystem supervises the software system through the standard interface of the logical network element layer; and The IP network management subsystem supervises the host through the standard interface of the physical network element layer. 11. The network management method according to claim 10, wherein creating the physical network element layer in the public information model comprises the following steps: recording the IP address of the host where the logical network element is deployed, and according to the IP address The address is mapped to the physical network element, and then an association is created between the logical network element and the physical network element, and the association information is stored in the module service layer. 12. The network management method according to claim 10, characterized in that, creating the logical network element layer in the public information model comprises the following steps: searching for the matching logical network element by the host IP address, and An association is established between the logical network element and the physical network element, and the association information is stored in the module service layer. 13. The network management method according to claim 10, wherein the service network management subsystem comprises at least one of the following: configuration management subsystem, security management subsystem, fault management subsystem, performance management subsystem, billing Management subsystem, service management subsystem, alarm subsystem, data acquisition subsystem; the IP network management subsystem includes at least one of the following: configuration management subsystem, security management subsystem, fault management subsystem, performance management subsystem, Alarm subsystem, data acquisition subsystem. 14. The network management method according to claim 10, characterized in that, the service network management subsystem and the IP network management subsystem both include alarm, performance management, configuration management subsystems, and the alarm, performance management, configuration management The subsystems all include preprocessing modules, and supervising the host includes the following steps: These preprocessing modules query the association information between logical network elements and physical network elements stored in the public information model, so that the subsystems can identify logical network elements and physical network elements. The relationship between physical network elements. 15. The network management method according to claim 14, wherein supervising the host comprises the following steps: after a hardware failure occurs in the host and an alarm is sent, the IP network management subsystem receives and processes the alarm, the The preprocessing module of the alarm subsystem in the IP network management subsystem queries which logical network elements are affected based on the association information between physical network elements and logical network elements stored in the public information model, and notifies the service network management subsystem to handle accordingly , so that the alarms that have occurred on the host can be observed on the service network management subsystem side. 16. The network management method according to claim 15, wherein supervising the host comprises the following steps: if an alarm occurring on the host may cause abnormal operation of the software system, the service network management subsystem will issue an early warning, And notify the service maintenance personnel to take measures. 17. The network management method according to claim 14, wherein supervising the host comprises the following steps: after creating a monitoring task or a fault detection task for monitoring the running status of a physical network element on a logical network element, the IP network management sub The preprocessing module of the performance management subsystem in the system sends relevant parameters to the IP network management subsystem, and the IP network management subsystem collects the status data of the physical network elements according to these parameters, and sends the collected results to the status monitoring in real time interface. 18. The network management method according to claim 10, characterized in that, the service network management subsystem and the IP network management subsystem are divided based on management fields, and the two are divided into a service topology view and a host topology view.

Images