JP2769260B2 - Network equipment operation management system - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a computer network to which a plurality of computers and network devices are connected, and more particularly to a network management system for smoothly operating and managing a network.

[0002]

2. Description of the Related Art With the development of communication technology as the basis of a network, it has become possible to construct a high-speed and highly reliable network in recent years. As high-speed communication becomes possible and the construction of a global network progresses, the necessity of network management has been emphasized. However, even if resource sharing and business efficiency can be achieved, the number of management tasks may increase compared to before the construction of the network.

At present, a system called a network management tool for improving the efficiency of network management work has been proposed. The common feature of these tools is that they manage the network at the communication protocol level.

The network management function at the protocol level includes a network traffic monitoring function,
It has a statistical processing function that summarizes monitoring results, an alarm generation function when traffic is abnormal, and the like.

[0005] For example, Dual Manager, which is sold by Nippon Steel Pipe Co., Ltd. is SNMP (SimpleNetwork Management
Protcol) is a communication protocol-based management system, but even if you use an industry standard communication protocol,
Not all products support the protocol, so the system alone may not be able to manage the network.

Also, Sun Micro Systems' Sun Net Ma
nager is a network management system based on Sun's original protocol, which makes it difficult to manage third-party products, as is the case with IBM's Net View . Furthermore, these systems cannot manage information such as what devices are physically connected.

[0007] Further, in this type of technology relating to a network management system, which is described in a patent publication, (1) a maintenance subsystem described in JP-A-61-180340, and (2) a maintenance subsystem described in JP-A-63-180340. network monitoring apparatus according to 117,532 JP, (3) a network diagnostic apparatus according to JP 63-279643 and JP (4) network address Ma Tsu ping method described in JP-a-2-18651, ( 5) There is a LAN control system described in JP-A-2-305140.

The maintenance subsystem (1) executes a diagnostic routine for a computer in which a fault has occurred, transmits the cause and location of the fault, and makes it possible to correct the fault from a remote terminal.

[0009] The network monitoring device of the above (2) enables a component failure investigation from a remote location by storing information on the monitored component in a definition information file.

[0010] In the network diagnostic device of the above (3), the diagnostic processor receives a diagnostic command sent from the network component and returns a diagnostic result, so that the component user can investigate the cause of the failure on the spot. Is to do so.

[0011] Network address Ma Tsu <br/> ping method of (4), the mapping indicating the node name and the physical location of the computer by distributed administration scalability and high change ease network system It enables construction.

The LAN control method (5) analyzes packets on a network, simplifies shared resources of a server, and improves operability.

[0013]

However, the above-mentioned prior art cannot solve the following problems.

(1) Prevention of Loss Due to Network Failure In an environment where the network is an infrastructure, it is normal that the network is in operation,
As a result, cost calculations and productivity predictions are made.
Therefore, when the network is not operating due to some abnormality, productivity is reduced or loss occurs. To prevent such a situation, you need to understand what machines are connected to the network in what configurations, and design an efficient network topology.
It is necessary to be able to detect network traffic anomalies instantly. However, with the conventional technology, monitoring is possible but not until the topology is designed.

(2) Instruction for countermeasures in the event of a network failure When a failure occurs in the network, a loss occurs as described above. To minimize this loss, the network administrator needs to quickly restore the network. When the importance of data loss and reliability degradation due to a network down is emphasized, and when the response is degraded, the countermeasures for failures differ, but first, the situation of failures is accurately grasped and the cause is analyzed. You have to decide where and how to fix it most efficiently. It is also necessary to identify the department in charge and eliminate the cause so that similar failures do not occur in the future. However, in the network management system according to the related art, there is nothing to issue an instruction for troubleshooting.

(3) Management of Complicated Management Data Network components, including computers, are diverse and many. To manage the network well, the connected devices, even those with a small single function, are managed devices. Network-related devices have a fast product cycle, and high-performance and inexpensive devices are being released one after another, and the number of managed devices to be managed is expected to continue to increase. Furthermore, there are various attributes and attribute values for devices connected to the network. Even if one workstation is considered, there are dozens of product names, model numbers, serial numbers, prices, memory sizes, disk sizes, operating OSs, and the like. If necessary information can be stored in a form that can be immediately retrieved, management work can be performed efficiently. In addition, management information may be included in graphic data such as machine layout and network wiring, tabular data such as equipment configuration and running software list, text data such as how to use it, and product catalogs. image data of products such, are Nde wealth to the very variety.

[0017] Further, even if the graphics data and the tabular data are referred to at once, the data format is different if the tools for creating the data are different, and it is impossible to use the data because of incompatibility because it is not compatible. In the conventional technology, there is no tool that can simultaneously operate graphic data and data on a floor map at the same time as manipulating tabular data or text data. It is.

(4) Distribution of Information If the management source differs depending on the type of equipment and equipment, price, etc., the information will be dispersed. The distribution of management departments, rather than distribution on the network, makes it difficult to collect necessary information when new equipment is installed or moved. For example, in the case of an in-house company, the management source differs depending on the type of information, such as the accounting department in the accounting department, the power source in the computer center equipment department, and the telephone in the general affairs department general affairs department. Further, when the management information is managed on a large-sized host machine, the information cannot be easily taken out or processed because it is not connected to a word processor or a personal computer on the desk of the worker.

(5) It is difficult to separate maintenance / support departments in the event of a failure In most cases, networks have a multi-vendor configuration, and it is not possible to request a specific maintenance company to perform work. Even if there is a management department in the company, it does not maintain the individually installed network. In addition, it is very difficult to determine where the abnormality is after the failure and where to fix it.

The present invention has been made in order to solve the above problems, and an object of the present invention is to provide a technique capable of reducing the management work of a network administrator.

Another object of the present invention is to be simplified for management of the network manager itself to provide a technique capable.

Another object of the present invention is to provide a technique capable of reducing the management work of an article manager.

Another object of the present invention is to provide a technique capable of simplifying the management work of the article manager itself.

Another object of the present invention is to provide a technique capable of promptly coping with a network abnormality.

Another object of the present invention is to provide a technique capable of saving resources by sharing computer resources and data.

Another object of the present invention is to provide a technique capable of improving the reliability of a network.

The above and other objects and novel features of the present invention will become apparent from the description of the present specification and the accompanying drawings.

[0028]

In order to achieve the above object, the present invention provides a network equipment operation management system for managing and operating a network to which a plurality of network devices including an electronic computer are connected. Includes a map of the installation location and wiring status information.
The storing information about the physical layout and connection relationship of the network devices in the network structure of the non-current 1
Database and history of network traffic,
A second database that stores logical information indicating the network topology in the current network configuration including information on changes in disk usage and information on connection relations, laying cable length, electric capacity, installation area, power supply position, network physical requirements and connectable number of machines includes information port shape, the upper limit of network traffic, disk usage, the usage of swap size
Input means for inputting the logical requirements needed to network topology analysis including information, a third database storing check contents corresponding to the physical requirements and logical requirements, the physical by said input means When a requirement is input, a check content corresponding to the input physical requirement is searched from the third database, and information on the input physical requirement is searched from the first database. First checking means for checking whether the physical arrangement and connection relationship of the network devices in the network configuration satisfy the condition indicated by the check content, and when the logical requirement is input by the input means, When the check contents corresponding to the input logical requirement are searched from the third database, Searching the second database for information on the input logical requirements, and checking whether the logical connection relation of the network devices in the current network configuration satisfies the condition indicated by the check content. 2, a means for generating a current network physical configuration diagram by referring to the storage information of the first database, and a current network logical configuration diagram by referring to the storage information of the second database Means for performing the check, information on the check result of the first and second check means, and the network physical configuration diagram,
A display unit for displaying a network logical configuration diagram; a fourth database storing attributes including information on a product name, a model name, an interface, and a processing speed of each network device in the current network configuration; In response to a network device selection instruction operation displayed in the network physical configuration diagram or network logical configuration diagram displayed on the display screen of the display means, the attribute of the selected network device is searched from the fourth database. Means for displaying the information of the searched attribute on the display screen of the display means.

Further , when each network device operates,
Information and users of other network devices required for
That stores information on network devices used by
And a network device is assumed to have failed.
Network devices or devices affected by the failure
Identifies the user by the information stored in the table
It is characterized by comprising means .

[0030] In addition, the information specified by the specifying means is specified.
Affected devices or affected users
At least one of a logical configuration diagram and a network logical configuration diagram
Is provided .

In addition, in the current network configuration,
The means to specify the network number of the desired hierarchy and this method
Network device in the lower layer of the layer specified by the column
Network topology of devices and sub-networks
Network traffic in the network topology
Fick history is searched from the second database,
Based on the search results, low-traffic networks
A means for inferring and creating a network configuration .

Further, the data stored in the second database is
Refer to the information on logical and connection relationships
Identify the input / output end of the fraudulent information,
Means for creating a road map and displaying it on the display screen of the display device
Characterized in that it comprises.

[0033]

[0034]

[0035]

[0036]

[0037]

According to the above-mentioned means, in the network equipment operation management system, the work of the network manager and the equipment, asset and article manager is reduced, and the smooth network operation is supported. For example, in the network equipment operation management system of the present invention, it is assumed that tens of thousands of persons own one computer or terminal and are connected to a network. A vertical trunk local area network is set up inside the building, and a horizontal branch line local area network is connected to each floor from there. A local area network of several tens of people is created on the branch line network. Such a hierarchical local area network is constructed on a nationwide or global scale, so that the same computing environment is ensured at any location. A large-scale business host computer or supercomputer is connected to the core local area network in the building, and can be freely accessed even from a remote terminal. A router is also connected to the backbone network, and serves as a point of contact with external networks and networks between buildings. Number 1 in the future
00 enables high-speed communication of megabytes (MB) / sec,
It will be possible to communicate with remote networks in real time.

[0038] That is, network equipment management system of the present invention is connected to such a local network
Exchanges data over a network with an asset management business host machine, a workstation with a map information database, and a workstation with a product database , running on a server machine configured and connected to the local area network I do.

The network equipment operation management system of the present invention has a user interface for accessing various databases, and it is possible to input and update any data and any data with the same interface. .

The equipment to be managed in the network equipment operation management system of the present invention includes telephones, power supplies, air conditioning, floor maps, building maps, and network wiring as the equipment. Examples of the computer device include a workstation, a personal computer, a printer, a host computer, a file server, a terminal, a word processor, and the like. Examples of network devices include routers, bridges, repeaters, transceivers, terminal servers, protocol converters, modems, and faxes. In addition to the above, software, machine environment, system configuration, network traffic, and the like are also managed.

The attributes of the managed device handled by the network equipment operation management system of the present invention include the following. First, the map information includes the lot number, building name, floor,
There are area, desk position, seat, machine position, etc. For computer and network equipment, product name, model name, model number, price, supplier, purchase date, power consumption, serial number, shape image, dimensions, weight, necessary Number of outlets, operating environment,
Includes repair history, maintenance costs, etc. The attributes specific to the product include the workstation name, the CPU name,
Processing speed, number of clocks, operating OS, external interface, MAC address, logical machine name, IP address, memory size, hard disk capacity, extension board, etc.
Software-specific attributes such as the number of ports, port shapes, interface types, and the number of expandable slots include product name, version, operating OS, operating environment, manual, installation machine, storage location, function overview, version upgrade cost, etc. Can be The information listed here is registered in the product database in advance, and necessary information can be obtained by specifying the product name and the model name.

Further, the network equipment operation management system of the present invention has the following functions.

(1) Network Facility Database Interface The above-mentioned managed devices and their respective attribute information are stored in a database, and can be registered and searched. Serial number that is unique to each product, maintenance contract status, supplier,
The maintenance contract and the like are registered in the database at the time of new purchase.

(2) Map database Using CAD-based graphic processing, the map data is stored hierarchically from nationwide map information to building drawings for each floor in the building. A user interface is provided that is linked to the network equipment database described above and that can also access device information on a map displayed on a screen.

(3) Management of Hardware Layout and Network Wiring Network wiring, connection status, power supply layout, machine layout, telephone wiring, etc. are created based on the map stored in the map database.

(4) System Configuration Management When purchasing a new computer, a list of necessary device configurations and software is generated, and it is checked whether the system configuration is suitable for the purpose.

(5) Machine Environment Management For example, it is possible to search for information such as where is the home directory, what is on what disk, what is the system configuration of the machine, who has an account, and so on. .

(6) Network Environment Management The network environment is managed in a physical sense. Check where and what machines or terminals are connected, meet network standards for Ethernet, etc.

(7) Software Management The above-described attributes of software are managed.

(8) Article Inventory Management The number of unused cables, connectors, transceivers, terminators, etc., and a rental list are managed.

(9) Monitor Function In cooperation with a network management tool at the communication protocol level, a regular network status is monitored, and statistics such as network traffic, machine load average, and printer operation status are obtained. Also, for security purposes, it constantly monitors whether suspicious data is flowing through the network.

(10) Network Installation Support When a network is added, a device is added, or a position is changed, whether or not the network is installed is diagnosed at a physical level. For example, the power supply is insufficient, the number of outlets, the local area network
Check the limit length of the physical cable and the number of connectable terminals.

(11) Network monitoring In cooperation with the diagnosis-type expert system, a failure location is specified when a failure occurs, and a countermeasure instruction for recovery is issued. Also, a machine or a terminal connected to the network is automatically detected by using a management protocol. further,
An error is detected before a failure occurs from the analysis result of the load measurement of the host machine or the network, and an alarm is notified to a network administrator.

(12) Network integration Information regarding the network described above is comprehensively determined, and advice is given on what is lacking in smooth network operation and how to achieve an efficient network.

In other words, according to the above-mentioned means, it is possible to reduce the management work of the network administrator, and
It is possible to simplify the management tasks of the network administrator itself. Further, the management work of the article manager can be reduced, and the management work of the article manager itself can be simplified . Also, it is possible to save resources by sharing of computer resources and data. Also,
Network reliability can be improved.

[0056]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the present invention will be specifically described below with reference to the drawings. FIG. 1A is a diagram showing a configuration of a network equipment operation management system according to one embodiment of the present invention.
Here, a target device managed by the network equipment operation management system is referred to as a managed device. The managed devices are classified into five categories: computers, terminals, network devices, peripheral devices, and cables. The electronic computer is a workstation, a personal computer, a host machine, or the like. The terminal is an X terminal, a cataracter terminal, a graphic terminal, or the like. Network devices are routers, repeaters, terminal servers, transceivers, and the like. Peripheral devices are printers,
Facsimile, scanner, etc. Cables are
Ethernet cable, telephone line, power cable, etc. The network is a network to which managed devices are connected and communication is performed between the devices.

In FIG. 1A, reference numeral 1a1 denotes a communication control device, which controls communication between the network equipment operation management system and the network (1a2). Reference numeral 1a2 denotes a network in which managed devices managed by the network equipment operation management system are connected by cables. 1a3 is a central processing unit (CPU) for data processing, system control,
Perform various pre-programmed processes. An input device 1a4 uses a keyboard, a mouse, a scanner, or the like. Reference numeral 1a5 denotes an output device, such as a display or a printer. 1a6 is an auxiliary storage device,
Magneto-optical disks, metal tapes, hard disks and the like are used.

First, terms used in this embodiment and a network configuration will be described. The network configuration indicates how the computers, terminals, network devices, peripheral devices, and cables are connected. The one indicating the connection status including the actual positional relationship and distance of the connection is called a physical network configuration, and the one indicating the connection status in a logical unit such as a subnet or a segment is called a logical network configuration.

[0059] Figure 1b, the configuration of the logical network is a diagram schematically illustrating. FIG. 1B shows the present embodiment.
In the network equipment operation management system, the output of FIG.
In the display example of the network configuration diagram displayed on the device 1a5,
is there. In FIG. 1b, 1b1 is a communication network, 1b2 is a computer, 1b3 is a network device, and 1b4 is a terminal.

Next, a description will be given of a procedure for checking whether or not the network specification satisfies the physical requirements by using the information stored in the database in the network equipment operation management system. The physical requirements here are: Ethernet cable length and bend rate restrictions, relationship between electrical capacity and power supply required for managed devices, area required for installation of managed devices, cable length, number of transceivers, Available number of second Ethernet boards, terminal
These are conditions such as the number of server ports and multi-port repeaters.

FIG. 2A is a flowchart showing a procedure for checking physical conditions in the network equipment operation management system when the physical requirements of this embodiment are input. The flow of the physical condition check processing of the network equipment operation management system will be described with reference to FIG. 2A. First, in step 2a1, physical requirements are input using an input device. Here, the requirements for checking the cable length, electric capacity, installation device area, installation location, connection terminal, number of extension boards, and the shape of the network port required for network construction are input. Next, step 2
In a2, data related to the physical requirement input in step 2a1 is searched with reference to a database. In this database, data enough to grasp the current network construction status is stored, and a search can be performed using physical requirements as keywords.
The network facility operation management system stores, for example, physical data such as a map, a layout, a wiring state, the number of installed machines, power supply wiring, and connected devices as data from which a network construction state can be grasped. Further, in step 2a3, a physical check condition as shown in FIG. 2b stored in the network equipment operation management system is searched according to the requirement input in step 2a1. In step 2a4, using the search result regarding the check item obtained in step 2a3 and the search result regarding the current network construction status obtained in step 2a2, whether the check item is satisfied or not is compared. I do. Next, in step 2a5, the comparison result obtained in step 2a4 is stored in a predetermined storage location. In step 2a6, the comparison result stored in step 2a5 is displayed on the display device.

A procedure for checking whether or not the network specification satisfies the logical requirements using the information stored in the database in the network equipment operation management system will be described below. The logical requirements here are the number of machines that can be connected to one segment, the upper limit of the traffic volume, detection of illegal packets, the upper limit of the load average of the central processing unit (CPU), the disk usage, and the swap size usage. Conditions, such as lack of memory, how to segment logical segments in bridges and routers.

FIG. 3A is a flowchart for explaining an example of a logical condition check processing procedure in the network equipment operation management system when the logical requirement of this embodiment is input. The flow of the logical condition check process of the network equipment operation management system will be described with reference to FIG. First, in step 3a1, logical requirements are input using an input device. Here, the requirements for checking the cable length, electric capacity, installation device area, installation location, connection terminal, number of extension boards, and the shape of the network port required for network construction are input. Next, in step 3a2, data related to the logical requirement input in step 3a1 is searched with reference to a database. This database stores enough data to understand the current network topology,
Search can be performed using logical requirements as keywords. As data that can grasp the network topology, for example, a log of network traffic as shown in FIG. 3B, statistics of a load average of a central processing unit (CPU), a change in disk usage, a log of outgoing packets, a virtual used The network equipment operation management system stores logical data such as the number of terminals. Further, in step 3a3, a logical check condition shown in Figure 3c network equipment management system we are saved searches in accordance with the requirements input in step 3a1. In step 3a4, step 3a
Using the search result of the check item obtained in step 3 and the search result of the current network topology obtained in step 3a2, the check item is compared with the check item. Next, in step 3a5, the comparison result obtained in step 3a4 is stored in a predetermined storage location. Step 3a6
In step 3, the comparison result stored in step 3a5 is displayed on the display device.

A network configuration diagram showing connection states of computers, terminals, network devices, peripheral devices, and cables is displayed in the management target range of the network facility operation management system in this embodiment, and is displayed in the network configuration diagram. If you indicate a computer, terminal, network device, peripheral device or cables,
A method by which the corresponding information can be searched will be described below.

In order to search for information on computers, terminals, network devices, peripheral devices, or cables, the network equipment operation management system constructs an equipment operation management database shown in FIG. 4A in an auxiliary storage device. . In the facility operation management database shown in FIG. 4A, the attribute information on the computers is registered in the computer data 4a1 one by one. The registered information includes a product name, a model name, a CPU name, a processing speed, the number of clocks, an operating OS, and additional peripheral devices. The terminal data 4a2 includes a product name, a model name, a display size, a resolution, and the like. The network device data 4a3 includes a product name, a model name, a connection interface, a type of a communication protocol, and the like. The peripheral device data 4a4 contains a product name,
There are model name, connection interface, connection protocol, etc. The cable data 4a5 includes a product name, a model name, a connection model, electrical characteristics, and the like.

The network equipment operation management system has a filtering table shown in FIG. 4B in addition to the equipment operation management database shown in FIG. 4A. The filtering table includes the computer data 4a1 and the terminal data 4a stored in the facility operation management database.
2, network device data 4a3, peripheral device data 4
a4, cable data 4a5, computer data filtering, terminal data filtering, network device data filtering, peripheral device data filtering, and cable data filtering. These data filtering can specify whether to display the attribute of each device, and FIG.
Used when searching for information from the equipment operation management database.

Computers, terminals, network devices, and the like stored in the facility operation management database shown in FIG.
FIG. 4C shows a process of searching for information on peripheral devices and cables.
Will be described along the flowchart of FIG. First, step 4
In c1, the user wants to retrieve information on a computer;
The terminal, the network device, the peripheral device, and the cables are connected to the corresponding computer, terminal, network device, and peripheral device in the network configuration diagram shown in FIG. 1B displayed on the terminal used by the user. Equipment, cables, keyboard,
Use the mouse or touch screen to make a selection on the screen.

In step 4c2, step 4c1
Enter search conditions to search for information required by the user with respect to the computer, terminal, network device, peripheral device, and cables selected in. As the search condition, the attribute of each device stored in the equipment operation management database shown in FIG. 4A can be specified, and the network equipment operation management system can be instructed to retrieve only the information of the attribute. Further, the search condition can be specified using a database search language of a database system, for example, an international standard search language such as SQL. In step 4c3, information on the attribute that satisfies the search condition specified in step 4c2 is extracted from the facility operation management database in FIG. 4a. In step 4c4, only the information required by the user is selected from the attribute information searched in step 4c3 by data filtering specified in 4b1 to 4b5 of the filtering table in FIG. 4B. In step 4c5, the information selected in step 4c4 is displayed near the corresponding computer, terminal, network device, peripheral device, or cable in the network configuration diagram.

In the management target range in this embodiment,
A method for investigating how a computer, terminal, network device, peripheral device, and power supply (which will be referred to as a device assumed to be stopped) affect users and machines will be described below.

The network equipment operation management system has tables of “ static information ” on the network shown in FIGS. 5A, 5B, 5C, and 5D on the auxiliary storage device. FIG. 5A is a correspondence table of terminals and computers on the network to be managed, and managed devices required for their operation. From this table, for example, information indicating that the device A stops operating when the power source A, the host machine B, or the transceiver C fails, or that the device A does not operate unless the power source A, the host machine B, and the transceiver C are operating Is obtained.

FIG. 5B is a correspondence table of network devices on a network to be managed and managed devices required for their operation. From this table, for example, information is obtained that the router B does not operate when the device A or the power supply B fails, or that the router B does not operate unless the device A and the power supply B are operating.

FIG. 5C is a correspondence table between the users on the network to be managed and the managed devices normally used by the users. From this table, for example, if the device A, the terminal D, or the power supply D fails, the user 1 is affected, or the user 1 cannot use the device 1 as usual unless the device A, the terminal D, and the power supply D are operating. Information is obtained.

FIG. 5D is a correspondence table between the computers on the network to be managed and the software unique to the machines. From this table, for example, device A
Is obtained, information that the software 1 and the software 2 cannot be used if the device fails.

A process for specifying and displaying an affected device when one of the managed devices such as a computer, a terminal, a network device, a peripheral device, and a power supply is assumed to be stopped will be described with reference to the flowchart of FIG. 5E. I do.

First, in step 5e1, the network equipment operation management system displays a network configuration diagram of a managed range on a display device. Next, step 5e
In 2, the stop assumption target device on the network configuration diagram of the managed range in FIG. 5G is designated by an input device such as a mouse or a keyboard. For example, assume that the power supply A5g1 of the device A5g2 shown in FIG. 5G is designated.
Next, in step 5e3, devices affected when the power supply A5g1 is stopped are searched from the tables in FIGS. 5A and 5B by a search routine shown in FIG . 5F. In step 5e4, the network equipment operation management system displays the managed devices affected when the power supply A is stopped by coloring or enclosing the network configuration diagram in FIG. 5g (encircled by a dashed line in FIG. 5h). region).

A routine for searching for an affected device when the device A stops will be described with reference to the flowchart shown in FIG. 5F. In this routine, list A is used for storing a search target, list B is used for work, and list C is used for storing search results. In step 5f1, the designated stop assumed target device is stored in the search target storage list A. Next, in step 5f2, the devices that are affected when the devices in the list A are stopped are searched from the table 5a, and the results are stored in the work list B. Next, in step 5f3, it is checked whether all the results (list B) searched in step 5f2 are included in the result storage list C. If false in step 5f3, in step 5f4, among the affected devices in the work list B, those not included in the result storage list C are added to the list C and the search target storage devices are added. It is stored in the application list A. Step 5f3
In step 5f5, the contents of the search result storage list C are stored in the search target storage list A in step 5f5. Next, in step 5F6, searching each device affected if the device list A is stopped from Table Figure 5b, is stored in the working list B results.
Next, in step 5f7, it is checked whether all the results (list B) searched in step 5f6 are included in the result storage list C. If false in step 5f7, in step 5f8, among the affected devices in the work list B, those not included in the result storage list C are added to the list C and the search target storage device is added. It is stored in the application list A. Step 5f7
If it is true, the search routine is terminated.

FIG. 5i shows a process for specifying and displaying the affected user and unusable software when the managed device such as a computer, a terminal, a network device, a peripheral device, and a power supply is halted. This will be described along the flowchart shown in FIG.

First, in step 5i1, the network equipment operation management system displays a network configuration diagram of a managed range on a display device. Next, step 5i
In 2, the device to be assumed to be stopped on the network configuration diagram of the managed range shown in FIG. 5g is designated by an input device such as a mouse or a keyboard. For example, it is assumed that the power source A of the device A5g2 in FIG. Next, in step 5e3, devices affected when the power supply A is stopped are searched from the tables in FIGS. 5A and 5B by the search routine in FIG. 5F. The search result is output to list C. Next, in step 5I4, searches the user from the table to 5c affected if the equipment list C is stopped. Next, in step 5I5, the software can not be used to search from the table view 5d when the device list C is stopped. In step 5i6, the network equipment operation management system displays each list searched in steps 5i4 and 5i5 on a display device (FIG. 5j).

Next, a description will be given of a method in which the network equipment operation management system displays a network configuration diagram showing logical connections of managed devices and networks.

FIG. 6D is a diagram showing a display screen of the network configuration diagram of the present embodiment, where 6d1 is a computer, 6d
2 is a terminal, 6d3 is a peripheral device, 6d4, 6d5, 6d6
Is a network device, and 6d7 is a cable network.

FIG. 6E is a schematic diagram showing the two-dimensional configuration of the present embodiment, where 6e1 is a computer, 6e2 is a terminal, 6e
Reference numeral 3 denotes a peripheral device, 6e4, 6e5, and 6e6 denote network devices, 6e7 denotes a cable network, 6e8 denotes a desk, and 6e9 denotes a pillar.

Next, the hierarchical structure of the network of this embodiment will be described with reference to FIGS. 6fa to 6fc. FIG. 6f
FIGS. 6a, 6fb, and 6fc are schematic diagrams for explaining a three-layer network of the present embodiment. Here, the first layer, the second layer,
.. Are referred to as layers. A layer with a smaller number is called an upper layer, and a layer with a larger number is called a lower layer. 6f1, 6f5, 6
f10 is the first, second, and third layers, respectively.

A number is assigned to each layer so that a sub-network or a managed device can be uniquely determined in that layer. The number obtained by arranging the numbers for each layer from the highest layer to the lowest layer is called a network number. In the case of the three-layer network shown in FIG.
g. By using the network number, a subnetwork or a managed device can be uniquely specified from the entire network. When sub-networks and managed devices in each layer shown in FIG. 6fa are numbered by two-digit numbers as shown in FIG. 6fb, the respective network numbers are as shown in FIG. 6fc. The sub-network is represented by setting the number part of the lower hierarchy to 0 for the number of digits. Therefore, the network 6f1 including all the management targets shown in FIG. 6fa is represented by the network number 000000.

In FIG. 6fa, reference numeral 6f1 is a diagram showing the whole image of the network to be managed, and has a configuration in which four sub-networks 6f4 are connected by a network device 6f2. The sub-network is a network in which several computers, terminals, network devices, and peripheral devices are connected by a cable network, which is classified according to a logical meaning, for example, a department or a region.

The sub-network 6f4 is one of the sub-networks forming the whole picture 6f1 of the network, and the detailed configuration of the entire sub-network 6f4 is represented by the sub-network 6f5. In the subnetwork 6f5, three subnetworks 6f9 are connected by a network device 6f7. Cable net 6
f6 is the same as the cable network 6f3 constituting the overall image 6f1 of the network. Similarly, the entire detailed configuration of the sub-network 6f9 is
It is represented by 10. The cable network 6f11 is the same as the cable network 6f6 of the subnetwork 6f5. The sub-network 6f10 includes only managed devices.

Next, various databases necessary for the network equipment operation management system to display a network configuration diagram showing logical connections of the network will be described. First, there is a database of correspondence between managed devices and sub-networks and network numbers shown in FIG. 6h. Further, there are a connection information database shown in FIG. 6i, a display information database shown in FIG. 6j, and a basic topology database shown in FIG. 6kb.

The connection information indicates the connection relationship between the managed device and the sub-network, and to which cable network the sub-network or the computer is connected, or to the cable network connected to the upper layer network. The information such as which cable in the lower layer is stored using the network number (FIG. 6i).

The display information is a form displayed on the display device. The display shape, characters, colors, and patterns can be specified for each managed device or subnetwork. For example, although FIG. 6d shows an example of a network configuration diagram network equipment management system displays, Datosuruto network number 01010 1 electronic computer 6d1, with rectangular box shape, and displays the letters WS in, color By searching this database, the size is white and the size is known (FIG. 6j).

The basic topology is a form of a network. As shown in FIG. 6ka, the basic topology is a bus type (6k1) in which one cable network serves as a backbone and connects managed devices and networks, and a ring-shaped cable network serves as a backbone. The thing is a ring type (6k
2) A device in which a central computer is the backbone is called a star type (6k3), and a device in which managed devices and networks are freely connected is a free type (6k4). The network is represented by a backbone topology of any of these types (Fig. 6kb).

Referring to the flowchart shown in FIG.
A process in which the network facility operation management system displays a network configuration diagram indicating logical connections of managed devices and networks will be described.

First, in step 6a1, a network or a sub-network for which a network configuration diagram is to be displayed is designated by a network number. In step 6a2, a network number of a managed device or a sub-network constituting a lower layer of the network number specified in step 6a1 is searched from the database shown in FIG. 6h. In step 6a3, step 6
Based on the network numbers of the managed devices and sub-networks searched in a2, respective connection information and display information are searched from the databases shown in FIGS. 6i and 6j. Step 6
In a4, the main topology of the network or sub-network specified in step 6a1 is searched from the database shown in FIG. 6kb. Step 6a
In 5, the basic topology retrieved in step 6a4 is displayed on the display screen in a display configuration shown in FIG. 61 (l is a lowercase letter). Here, 6l1 is a bus type, 6l2
Denotes a ring type screen, and 613 denotes a star type / free type screen configuration. In step 6a6, the managed device and the subnetwork searched in step 6a2 are stored in step 6a3.
Step 6a based on the display information and connection information searched in
It is additionally displayed on the basic topology screen displayed in step 4. In step 6a7, based on the connection information searched in step 6a3, a cable network connecting the hierarchy of the network to be displayed and the higher hierarchy is searched.
Display with dotted line on the screen displayed by.

Next, with reference to the flowchart shown in FIG. 6B, a process in which the network equipment operation management system displays a two-dimensional configuration diagram will be described. Here, the drawing showing the position on the physical plane of the managed device and the sub-network is called a two-dimensional configuration diagram.

The network equipment operation management system uses a database (FIG. 6m) for associating network numbers with plane maps, and a display position database (FIG. 6m) representing coordinates of managed devices and sub-networks on the plane map. 6n), and has a display information database (FIG. 6j) of managed devices and sub-networks. The plane map is a general term for a layout or a map on which the columns 6o1 and the desks 6o2 are displayed as shown in FIG. 6o.

First, in step 6b1, a network or a sub-network for which a two-dimensional configuration diagram is to be displayed is designated by a network number from an input device such as a keyboard or a mouse. Next, in step 6b2, a plane map corresponding to the network number specified in step 6b1 is searched from the database of FIG. 6m. Next, in step 6b3, the plane map searched in step 6b2 is displayed on the display device. Step 6
In b4, the network number of the managed device or the sub-network constituting the lower hierarchy of the network number specified in step 6b1 is searched from the database shown in FIG. 6h. In step 6b5, step 6
The display position and display information of the managed device and the subnetwork searched in b4 are searched from the databases shown in FIGS. 6n and 6j. In step 6b6, step 6b4
Based on the display information and display position searched in step 6b5, the managed device and the sub-network searched in step 6b5 are displayed as a two-dimensional configuration diagram on the plane map displayed in step 6b3.

Referring to a flowchart shown in FIG. 6C, a process in which the network equipment operation management system displays a three-dimensional configuration diagram will be described. The drawing showing the position of the managed device and the sub-network in the physical space is called a three-dimensional configuration diagram. FIG. 6p is a diagram illustrating a three-dimensional configuration diagram of the present embodiment. In FIG. 6p, 6p1 is a subnetwork, 6p
2 managed equipment, 6P3 cable network, 6 p 4 is a spatial map showing the layout of the building network is built. The space map is a layout in which buildings are displayed only by the skeleton 6q1 as shown in FIG. 6q.

The network equipment operation management system has 3
For displaying a dimensional configuration diagram, a database (FIG. 6r) corresponding to network signals and space maps, a display position database (FIG. 6s) representing coordinates of managed devices and subnetworks on the space map, managed devices and subnetworks. Has a display information database (FIG. 6j).

First, in step 6c1, a network or a sub-network for displaying a three-dimensional configuration diagram is designated by a network number from an input device such as a keyboard or a mouse. Next, in step 6c2, a space map corresponding to the network number specified in step 6c1 is searched from the database shown in FIG. 6r. In step 6c3, the space map searched in step 6c2 is displayed on the display device as shown in FIG. 6q. In step 6c4, the network number of the managed device or sub-network constituting the lower hierarchy of the network number specified in step 6c1 is searched from the database shown in FIG. 6h. Step 6c5
In FIG. 6 s and FIG. 6, the display position and display information of the managed
Search from the database indicated by j. In step 6c6, the managed device and the sub-network searched in step 6c4 are displayed as a three-dimensional configuration diagram on the space map displayed in step 6c3 based on the display information and the display position searched in step 6c5.

Next, the flow of processing in which the network equipment operation management system of the present embodiment analyzes the current network traffic and proposes an efficient new network configuration will be described with reference to the flowchart shown in FIG. 7A. I do. The network traffic represents the traffic between the managed device and the sub-network. Here, the description will be made by taking the amount of packets transmitted between the managed device and the sub-network as an example. The packet is one of the units of communication between the managed device and the sub-network.

The network equipment operation management system of the present embodiment has a history information database for analyzing the current network traffic. The history information is obtained by recording the traffic between the computer and the sub-network at regular intervals.

FIG. 7B is a diagram showing history information in which the network number of the transmission destination and the number of transmitted packets according to the present embodiment are recorded. In FIG. 7B, reference numeral 7b1 denotes a managed device to which a packet is transmitted or a network number of a subnetwork. 7b2 indicates the network number of the managed device or the network device that receives the packet transmitted from 7b1. 7b3 records the number of transmission packets from one week ago, and 7b4 records the number of transmission packets from two weeks ago. Such histories are stored in the history information database for each computer and sub-network.

First, in step 7a1, a network number of a network or a sub-network to be investigated is specified. In step 7a2, a network number of a managed device or a sub-network constituting a lower layer of the network number designated in step 7a1 is searched from the database shown in FIG. 6h. In step 7a3, the history of the managed device searched in step 7a2 is searched from the history information database. In step 7a4, it searches the database indicating the hierarchy of the topology of the network specified in step 7a1 in FIG 6k b. In step 7a5, a network with little traffic is inferred based on the history information searched in step 7a3 and the topology searched in step 7a4.

Here, the inference performed by the network equipment operation management system will be described.

For example, three sub-networks having history information shown in FIG. 7B (network number 010100,
010200, 010300) is the cable network 01010
It is assumed that the connection state shown in FIG. FIG. 7c b shows the total number of mutual transmission packets between the respective sub-networks in FIG. 7c1 is a subnetwork 010100
And the total number of packets transmitted by the sub-network 010300 to each other. Similarly, 7c2 is total mutual transmission number of packets between subnetworks 0101 00 and subnetwork 010200, 7c3 is the sum of the cross-transmission packet number of the sub-networks 010200 and subnetworks 010300.

The network equipment operation management system includes a sub network 010100 and a sub network 010.
The cable network 01010
1. Both traffic on the cable network 010102 is increasing, and as a result, the sub-network 010100
7c2 between the sub-network 010200 and the sub-network 010200
The communication 7c3 between the 300s is also determined to be inefficient. Based on the judgment, the sub-network 01010
Infer that there should be a direct connection between 0 and the sub-network 010300. Further, the numerical values of 7c2 and 7c3 are compared, and 7c2 with more traffic is prioritized, and the subnetwork 010200 is set to the subnetwork 01010.
It is determined that it is better to connect to 0.

In this way, a new efficient network configuration is inferred. In step 7a6, the network configuration inferred in step 7a5 is displayed on the display device in a form as shown in FIG. 7d.

Next, when any one of the managed devices such as the computer, the terminal, the network device, the peripheral device, and the power supply is stopped in the management target range in the network device operation management in this embodiment, the operation is affected in advance. The process of specifying the device and the user and notifying the user of the device will be described with reference to the flowchart shown in FIG. 8A.

First, in step 8a1, the network equipment operation management system displays a network configuration diagram of a managed range on a display device. Next, step 8a
In 2, the device to be assumed to be stopped on the network configuration diagram of the managed range shown in FIG. 5G is designated by an input device such as a mouse or a keyboard. For example, the power supply A (5 g 1) shown in FIG. 5 g is designated. Then step 8
In a3, the devices affected when the power supply A is stopped are searched from the tables of FIGS. 5A and 5B by the search routine shown in FIG. 5F. The search result is output to list C. Next, in step 8a4, the user affected when the device in list C is stopped is identified by the table in FIG. 5c.
Search from Le. Next, in step 8a5, software that becomes unusable when the device in the list C is stopped is searched from the table in FIG. 5D . Step 8a6
In the network equipment operation management system, the user searched in step 8a4
And the information retrieved in step 8a5 (the affected devices and software that cannot be used) is notified by e-mail (FIG. 8b). Step 8a6 may be displayed on a terminal used by the user instead of sending an e-mail.

Next, when a certain computer, terminal, network device, or peripheral device is illegally used via a network in the management target range of the network equipment operation management system of this embodiment, the network equipment operation management system A method of notifying the administrator of the unauthorized use of the information will be described.

In order to use a computer, a terminal, a network device, and a peripheral device from a remote terminal via a network, the computer, the terminal,
It is necessary to transmit command data called a packet from a network device or a peripheral device to a computer, a terminal, a network device, or a peripheral device that wants to use the packet via the network.

FIG. 9A is a diagram showing the data structure of a packet according to the present embodiment, and 9a1 is an address of a computer, a terminal, a network device, and a peripheral device used by the user in the network. 9a2 is the network address of the computer, terminal, network device, or peripheral device that the user wants to use. 9a3 and 9a4 are relay machines that relay the packet and transmit the packet to a target receiving machine when the transmitting machine cannot directly transmit the packet to the receiving machine. A plurality of machines may relay a packet on a path from a transmitting machine to a receiving machine. When one relay machine transmits a packet to another relay machine, 9a3 is a machine that transmits the packet to relay the packet, and 9a4 is a machine that receives the packet to relay the packet. Since the computer, terminal, network device, and peripheral device used by the user are transmission machines themselves and do not have transmission relay machines, the transmission relay machine address 9a3 indicates that there is no transmitting machine. It is assumed that the address itself is included. If the packet can be transmitted to the receiving machine without passing through the receiving relay machine, it is assumed that the receiving relay machine address 9a4 contains the receiving machine address itself to indicate that there is no receiving relay machine. 9a5 is a network number uniquely assigned to each network service, and 9a6 is transmission data used by the network service.

The network equipment operation management system stores the communication permission table shown in FIG. 9B in the network equipment operation management table so as to allow data exchange between the computer, the terminal, the network equipment, and the peripheral equipment via the network. Stored on a disk managed by the system. In each column shown in FIG. 9B, the network equipment operation management system uses the service number 9b3 designated in the same column from the machine having the sending machine address 9b1 to the machine having the receiving machine address 9b2 designated in the same column. Permit use of the specified network service.

When an electronic computer, a terminal, a network device, or a peripheral device is illegally used through a network, a transmission path of a packet transmitted or transmitted for illegal use is detected, and a system is detected. The process of notifying the administrator of the transmission route will be described with reference to the flowchart shown in FIG. 9D.

First, in step 9d1, the network equipment operation management system uses the communication control device to
Monitor packets flowing on the network. In each packet, the network equipment operation management system uses the transmission machine address 9a1, the reception machine address 9a2, the transmission relay machine address 9a3 shown in FIG.
The reception relay address 9a4 and the service number 9a5 are extracted. Next, it is checked whether the transmission machine address 9a1, the reception machine address 9a2, and the service number 9a5 are registered in the communication permission table shown in FIG. 9B. If it is registered in the communication permission table, it is not an unauthorized use, so the network equipment operation management system does not perform any processing, returns to step 9d1, and monitors another packet again. If the packet is not registered in the communication permission table, the packet is an illegally used packet.
Step 9d2 and subsequent steps are performed.

In step 9d2, step 9d1
It is checked whether or not the transmission machine address 9a1 of the illegal packet detected in step 4 matches the transmission relay machine address 9a3. In step 9d3, if the transmission machine address 9a1 is not the same as the transmission relay machine address 9a3, the transmission relay machine address 9a3 is registered in the transmission machine address 9c1 shown in FIG. 9c, and the reception relay machine address 9a4 is changed to the reception machine address shown in FIG. 9c. Register to 9c2.

Next, the transmission relay machine is accessed, and it is checked from which machine the illegal packet is requested to be relayed. Then, the transmission machine is checked, and until the transmission machine address 9a1 matches the transmission relay machine address 9a3, the transmission machine address 9c1 in the routing table of FIG.
And the transmission machine address 9c
2 is registered with the receiving relay machine address. Step 9d
In step 4, the receiving machine address 9a2 of the invalid packet detected in step 9d1 is
Check if it matches a4.

In step 9d5, if the receiving machine address 9a2 is not the same as the receiving relay machine address 9a4, the transmitting relay machine address 9a3 is registered in the transmitting machine address 9c1 shown in FIG. 9c, and the receiving relay machine address 9a4 is shown in FIG. 9c. Receiving machine address 9c2
Register with.

Next, access is made to the receiving relay machine to check to which machine the illegal packet is to be relayed. And
Check the receiving machine and send machine address 9a
Until 2 matches the receiving relay machine address 9a4, the transmitting relay machine address is registered in the transmitting machine address 9c1 and the receiving relay machine address is registered in the receiving machine address 9c2 in the routing table of FIG. 9C.

In step 9d6, step 9d3
Using the route table of FIG. 9c created in step 9d5, a route from the receiving machine address extracted in step 9d1 to the transmitting machine address is obtained. And
Extracts information on the connection form of computers, terminals, network devices, and peripheral devices stored in the network equipment operation management system, and displays all the computers, terminals, network devices, and peripheral devices that appear in the routing table, and displays the unauthorized use routes Create a diagram. Finally step 9
At d7, the unauthorized use route diagram created at step 9d6 is automatically transferred to the system administrator by e-mail. When the system administrator uses a terminal connected to the network, the unauthorized use route diagram is displayed on the terminal used by the system administrator.

Although the present invention has been described in detail with reference to the embodiments, it is needless to say that the present invention is not limited to the above-described embodiments and can be variously modified without departing from the gist thereof. .

[0120]

As described above, according to the present invention, the following effects can be obtained.

(1) Information indicating the physical arrangement, connection relationship, and logical relationship of each network device in the current network configuration that has already been constructed, and the product name, model name, and processing speed of each network device including a computer . Emotion
The information required for network topology analysis, including information on network topology, is registered in a database and managed in a unified manner, so that the current network physical configuration diagram and network logic It can display the configuration diagram, check whether the physical and logical requirements are satisfied, and display the attribute information including the product name information of each network device. Relieved from complicated management work, the management work of the network administrator can be reduced and simplified. In addition, to centrally manage attribute information including information on the product name, model name, and processing speed of each network device, reduce and simplify the management tasks of the article manager and asset manager in the current network configuration. Can be. In addition, by checking whether the physical and logical requirements are met before the network system starts operation or at an appropriate time after the operation starts, it is possible to grasp potential problems before a network failure occurs, Such measures can be taken to help prevent losses due to network failures, and this is extremely effective especially in an environment where a large number of network devices are newly added or reduced.

(2) A certain network device is out of order
Affected by the failure, assuming that
By identifying network equipment or users,
If the assumed device fails, where and how
Preliminary measures should be taken to see if recovery is most efficient
And immediately take countermeasures when a failure occurs.
Can direct and stop the dissemination of disability. Further
Check the cable break position and connection
Plan measures for network down due to goodness in advance
be able to. Users affected by the failure
You can specify measures only for
It is possible to eliminate waste such as instructing the user to take measures.
Network configuration is complicated and sophisticated.
It is effective for prompt response.

(3) Devices affected by these
And users to network physical diagram or network
By displaying in the logical configuration diagram, you can grasp related parts.
It will be easier. Also, low traffic networks
Infer, create, and suggest configurations to network administrators
This allows efficient networks with low traffic
Contributing to the realization of work systems. In addition, fraud
Identify the input / output end of the information and input / output path diagram of the illegal information
And display it on the display screen of the display device.
To prevent damages and failures caused by unauthorized use,
Quality can be improved.

(4) Each machine connected to the network
Share resources such as hard disks and printers with each other.
You can have each other. However, that alone is "possible.
Is not actually used effectively?
I don't know. So, what mega on which diskPart-Time Job
(MB) or if the central processing unit (CPU)
-What is the average, and the swap area usage
Is the disk size that can be allocated to each user
IswhatMegaPart-Time Job(MB) information of the present invention.
Comprehensively with the network equipment operation management system
To share resources properly,
Resources by sharing data resources and data.
Wear.

(5) Correct information is always held, and monitoring of network traffic and monitoring of machine utilization can be performed at all times. Therefore, careless network down can be avoided, and overall network reliability can be improved. be able to.

[Brief description of the drawings]

FIG. 1A is a block diagram showing a configuration of a network equipment operation management system according to an embodiment of the present invention;

FIG. 1B is a schematic configuration diagram for explaining the configuration of a logical network according to the embodiment;

FIG. 2A is a flowchart illustrating a physical condition check processing unit according to the embodiment;

FIG. 2B is a diagram showing physical check conditions according to the embodiment;

FIG. 3A is a flowchart showing a logical condition check processing unit according to the embodiment;

FIG. 3B is a diagram showing logical check conditions according to the embodiment;

FIG. 3C is a diagram showing a logical check condition of the embodiment;

FIG. 4A is a diagram showing a configuration of a facility operation management database according to the embodiment;

FIG. 4B is a diagram showing a configuration of a filtering table according to the embodiment;

FIG. 4C is a flowchart showing a processing procedure for retrieving information from the equipment operation management database according to the embodiment;

FIG. 5A is a diagram illustrating a correspondence table between a terminal, a computer, and a server device according to the embodiment;

FIG. 5B is a diagram showing a correspondence table between network devices and server devices according to the embodiment;

FIG. 5C is a diagram showing a correspondence table between the user and the device used by the user according to the embodiment;

FIG. 5D is a diagram showing a correspondence table between the computer of this embodiment and the unique software;

FIG. 5E is a flowchart illustrating a processing procedure for displaying an affected area according to the present embodiment;

FIG. 5F is a flowchart of a process of searching for an affected area according to the embodiment;

FIG. 5g is a diagram illustrating a network configuration diagram on the display device according to the present embodiment;

FIG. 5H is a diagram showing a display form of an influence range according to the embodiment;

FIG. 5i is a flowchart of processing for displaying an affected user and unusable software according to the embodiment;

FIG. 5j is a diagram showing a display screen of an affected user and unusable software according to the embodiment;

FIG. 6A is a flowchart illustrating a display processing procedure of a network configuration diagram according to the present embodiment;

FIG. 6B is a flowchart illustrating a display processing procedure of a two-dimensional network configuration diagram according to the present embodiment;

FIG. 6C is a flowchart illustrating a display processing procedure of a three-dimensional network configuration diagram according to the present embodiment;

FIG. 6D is a diagram showing a display screen of a network configuration diagram of the present embodiment;

FIG. 6E is a diagram showing a display screen of a two-dimensional configuration diagram of the present embodiment;

FIG. 6fa is a schematic diagram for explaining the concept of the hierarchical structure of the network according to the present embodiment;

FIG. 6fb is a schematic diagram showing numbering at each layer of the network according to the present embodiment;

FIG. 6fc is a schematic diagram showing network numbers in each layer of the network according to the present embodiment;

FIG. 6G is an explanatory diagram for explaining the configuration of the network number according to the embodiment;

FIG. 6H is a diagram showing a correspondence table between managed devices and sub-networks and network numbers according to the embodiment;

FIG. 6I is a diagram showing a correspondence table between network numbers and connection information according to the embodiment;

FIG. 6j is a diagram showing a correspondence table between network numbers and display information according to the embodiment;

FIG. 6ka is a schematic diagram for explaining the concept of the topology according to the embodiment.

FIG. 6kb is a diagram showing a correspondence table of network numbers, topologies, and managed devices serving as a backbone of the embodiment;

FIG. 6L is a diagram showing a display screen for each topology according to the present embodiment;

FIG. 6m is a diagram showing a plane map table according to the embodiment;

FIG. 6n is a diagram showing a correspondence table between network numbers and display positions on a plane map according to the embodiment;

FIG. 6o is a diagram showing a display screen of a plane map according to the embodiment;

FIG. 6p is a diagram showing a display screen of a three-dimensional configuration diagram of the present embodiment,

FIG. 6q is a diagram showing a display screen of a space map according to the embodiment;

FIG. 6r is a diagram showing a correspondence table between a network number and a space map according to the embodiment;

FIG. 6S is a diagram showing a correspondence table between network numbers and display positions on a space map according to the embodiment;

FIG. 7A is a flowchart illustrating a network configuration creation processing procedure with a small amount of traffic according to the embodiment;

FIG. 7B is a diagram showing a correspondence table between network numbers and traffic history information according to the embodiment;

FIG. 7ca is a schematic diagram showing a configuration of a network before inference according to the embodiment;

FIG. 7Cb is a diagram showing the traffic of the network before inference according to the embodiment;

FIG. 7D is a schematic diagram showing the configuration of a network after inference according to the embodiment;

FIG. 8A is a flowchart showing a processing procedure for calling attention to a user under the influence of the embodiment,

FIG. 8B is a diagram showing an e-mail notifying of unusable software according to the embodiment;

FIG. 9A is a diagram showing the structure of a packet according to the embodiment;

FIG. 9B is a diagram showing a communication permission table according to the embodiment;

FIG. 9C is a diagram showing a route table according to the embodiment;

FIG. 9D is a flowchart illustrating a processing procedure for detecting unauthorized access according to the embodiment;

[Explanation of symbols]

1a1 Network 1a2 Communication control device 1a3
... Central processing unit, 1a4 ... Input device, 1a5 ... Output device, 1a6 ... Auxiliary storage device, 1b1 ... Communication network, 1b2 ...
Electronic computer, 1b3 network device, 1b4 terminal.

Continued on the front page (72) Inventor Yumiko Mori 6-81 Onoe-cho, Naka-ku, Yokohama-shi, Kanagawa Prefecture Inside Hitachi Software Engineering Co., Ltd. (72) Inventor Toshiyuki Tsutsumi 6-81-Oue-cho, Naka-ku, Yokohama, Kanagawa Software Engineering Co., Ltd. (56) References JP-A-1-251835 (JP, A) JP-A-1-147444 (JP, U) (58) Fields investigated (Int. Cl. ⁶ , DB name) G06F 13/00 G06F 15/60 H04L 12/00

Claims (5)

(57) [Claims] In a network equipment operation management system for managing and operating a network to which a plurality of network devices including a computer are connected , a current map including a map of a place where each network device is installed and wiring status information is provided . A first database storing information on the physical arrangement and connection relationships of network devices in the network configuration, and logical information indicating the network topology in the current network configuration including information on the history of network traffic and information on changes in disk usage And a second database storing information on connection relationships, physical requirements including information on laying cable length, electric capacity, installation area, power supply position, network port shape , number of connectable machines, network traffic upper limit, disk Input means for inputting logical requirements necessary for network topology analysis, including information on the usage amount of the system and the usage amount of the swap size, and the check contents corresponding to the physical requirements and the logical requirements are stored. A third database, when the physical requirement is input by the input means,
The content of the check corresponding to the input physical requirement is searched from the third database, and the information on the input physical requirement is searched from the first database. First checking means for checking whether the logical arrangement and the connection relationship satisfy the condition indicated by the check content, and when the logical requirement is input by the input means,
The content of the check corresponding to the input logical requirement is searched from the third database, and the information on the input logical requirement is searched from the second database, and the logic of the network device in the current network configuration is searched. Checking means for checking whether a typical connection relationship satisfies the condition indicated by the check content, and means for generating a current network physical configuration diagram by referring to information stored in the first database Means for generating a current network logical configuration diagram by referring to information stored in the second database; information on check results of the first and second check means, and the network physical configuration diagram and network logical configuration A display means for displaying a diagram, and a display for each network device in the current network configuration. Includes product name, model name, interface, and processing speed information.
A fourth database in which attributes are stored, and a network instructed to be selected in response to a network device selection instruction operation displayed in the network physical configuration diagram or network logical configuration diagram displayed on the display screen of the display means. Means for retrieving device attributes from the fourth database, and displaying information of the retrieved attributes on a display screen of the display means. 2. Necessary for each network device to operate
Other network device information and users
Table that stores information on network devices used
And assume that a certain network device has failed
The network equipment or
A method for specifying a user by information stored in the table
The network of claim 1, comprising a step.
Equipment operation management system. 3. The object specified by the specifying means.
The affected device or the affected user is
Table in at least one of the schematic diagram and the network logical configuration diagram.
3. The method according to claim 2, further comprising:
Network equipment operation management system. 4. A system according to the present invention, wherein
A means for specifying the network number of the hierarchy, and this means
Therefore, network devices in the lower layer of the specified layer and
The network topology of the subnetwork and the
Network traffic in network topology
The history of the lock from the second database.
Networks with low traffic based on search results
Characterized by having means for inferring and creating a configuration
The network equipment operation according to any one of claims 1 to 3.
For management system. 5. An argument stored in the second database
Refer to physical information and information about connection
Identify the input / output end of the information and input / output path diagram of the illegal information
And a means for creating and displaying on the display screen of the display device
The method according to any one of claims 1 to 4, wherein
Network equipment operation management system.