JP6737397B2 - Control program, control method and control device - Google Patents

Description

The present invention relates to a control program, a control method and a control device.

2. Description of the Related Art A network management system that can provide various settings for a network of a corporate system and notification of a failure in a GUI (Graphical User Interface) environment by using a technology such as SDN (Software-Defined Networking) is provided.

The GUI environment can be realized by, for example, displaying a topology map in which a connection form of a network to be monitored is schematically illustrated. Therefore, in order for the network management system to provide a function in the GUI environment, information about the network device, for example, device registration such as an IP (Internet Protocol) address and an interface name of a port is a condition. Further, the device registration is realized by reflecting the interface name and the like collected from the network device on the network management system, so that the communication between the network management system and the network device is also a condition.

However, when the network is constructed, it may happen that the actual machine arrives at the site later than planned. In addition, even when an operator such as an SE (System Engineer) is in a place different from the site, there is a scene in which the work efficiency is desired to be improved by creating the topology map.

JP, 2003-216514, A

However, when the device registration is performed in advance, an error may occur in the content of the device registration performed before or after the actual device is deployed. In this case, there is inconsistency between the contents of both, and there is a contradiction between the display of the topology map and the actual connection status of the network. There is a possibility that it will fall into a situation where it does not function normally.

In one aspect, an object of the present invention is to provide a control program, a control method, and a control device that can realize device registration before deployment of an actual machine.

In one aspect, the control program registers an IP address to be assigned to a device included in a monitored network, registers identification information of a port included in the device as a first status, and registers the registered IP address. When a request to send setting information about the device is sent to the device by using, and the setting information is received from the device, whether or not the identification information of the port of the device registered in the setting information is included. If it is determined that all the registered identification information is included in the set setting information, the first status of the identification information is changed to the second status and registered. When the set setting information does not include a part of the registered identification information, the computer is caused to execute a process of outputting an error corresponding to a port relating to the identification information not included.

Device registration before actual deployment can be realized.

FIG. 1 is a diagram illustrating a configuration example of the network management system according to the first embodiment. FIG. 2 is a block diagram of the functional configuration of the network management apparatus according to the first embodiment. FIG. 3 is a diagram showing an example of transition from temporary registration to main registration. FIG. 4 is a diagram showing an example of transition from temporary registration to main registration. FIG. 5 is a diagram showing an example of transition from temporary registration to main registration. FIG. 6 is a flowchart illustrating a procedure of control processing according to the first embodiment. FIG. 7A is a diagram showing an example of the topology map. FIG. 7B is a diagram showing an example of the connection status of the actual machine. FIG. 7C is a diagram showing an output example of an error. FIG. 8 is a diagram illustrating a hardware configuration example of a computer that executes a control program according to the first and second embodiments.

A control program, a control method, and a control device according to the present application will be described below with reference to the accompanying drawings. Note that this embodiment does not limit the disclosed technology. Then, the respective embodiments can be appropriately combined within the range in which the processing contents do not contradict each other.

[System configuration]
FIG. 1 is a diagram illustrating a configuration example of the network management system according to the first embodiment. A network management system 1 shown in FIG. 1 provides a network management service that realizes settings related to a network NW constructed in a monitored system 3 such as a company system in a GUI environment. As a part of this network management service, the network management system 1 performs the device registration control process for suppressing the occurrence of inconsistency with the device registration performed after the actual device of the network device is deployed, before the actual device is deployed. Implement device registration.

As shown in FIG. 1, the network management system 1 includes a monitored system 3, a network management device 10, and a client terminal 50. The monitoring target system 3 accommodates the network devices 30A to 30C. Hereinafter, the network devices 30A to 30C may be collectively referred to as "network device 30".

FIG. 1 shows an example in which three network devices 30 are accommodated in the monitored system 3, but an arbitrary number of network devices may be accommodated. Further, although FIG. 1 shows the network management device 10 and the network device 30 as devices connected to the network NW, other devices other than these are not prevented from being connected to the network NW, and Another device may be connected to the device 30.

The network management device 10 is a computer that provides the above network management service. The network management device 10 is an example of a monitoring device.

As one embodiment, the network management device 10 can be implemented as an SDN (Software-Defined Networking) controller by installing package software or online software that realizes the above network management service in a desired computer. As an example of the network NW, the network management device 10 can perform management including monitoring, setting and control of carrier Ethernet such as IP-VPN (Internet Protocol Virtual Private Network) and wide area Ethernet (registered trademark). .. As described above, the network NW managed by the network management device 10 is not limited to a physical network, and may be a virtual network virtualized by a technique such as SDN or NFV (Network Function Virtualization).

The network device 30 is a device that forms the network NW of the monitored system 3. As the network device 30, for example, a data transfer device such as a router or a switch, a firewall, a load balancer, or the like can be adopted.

The client terminal 50 is a computer that receives the above network management service. The client terminal 50 is used, for example, by a person concerned such as a network administrator who manages the network NW. Here, the client terminal 50 does not necessarily have to have an operating environment of telnet or SSH (Secure SHell) by providing the network management service. Therefore, any computer having a general-purpose browser operating environment can be adopted as the client terminal 50.

[Configuration of Network Management Device 10]
FIG. 2 is a block diagram of the functional configuration of the network management device 10 according to the first embodiment. As shown in FIG. 2, the network management device 10 includes a communication I/F (interface) unit 11, a storage unit 13, and a control unit 15. The network management apparatus 10 may have various functional units of a known computer other than the functional units shown in FIG. 2, such as various input devices and audio output devices.

The communication I/F unit 11 is an interface that controls communication with other devices such as the network device 30 and the client terminal 50.

As an embodiment, the communication I/F unit 11 can employ a network interface card such as a LAN (Local Area Network) card. For example, the communication I/F unit 11 transmits various commands to the network device 30 and receives from the network device 30 all or part of Config information and MIB (Management Information Base) stored in the network device 30. Or In addition, the communication I/F unit 11 accepts registration of the network device 30 and operation input for network setting from the client terminal 50, and a window including a topology map in which the connection form of the network NW is schematic is displayed on the client terminal 50. Or send it to 50.

The storage unit 13 is a storage device that stores data used for various programs such as an OS (Operating System) executed by the control unit 15 and a network management program that realizes the above network management service.

As an embodiment, the storage unit 13 can be implemented as an auxiliary storage device in the network management device 10. For example, a HDD (Hard Disk Drive), an optical disk, an SSD (Solid State Drive), or the like can be used as the storage unit 13. The storage unit 13 does not necessarily have to be implemented as an auxiliary storage device, and can be implemented as a main storage device in the network management device 10. In this case, various semiconductor memory devices such as a RAM (Random Access Memory) and a flash memory can be used as the storage unit 13.

The storage unit 13 stores topology information 13a as an example of data used for a program executed by the control unit 15. Other than the topology information 13a, other electronic data can be stored together. For example, in the storage unit 13, in order to manage the authority of the user such as the network administrator, the user authority information in which the network device 30 or the group of the network device 30 which permits the setting operation and the browsing for each user is defined. Can be remembered.

The topology information 13a is information regarding the connection shape of the network NW. The topology information 13a includes device information 13a1, port information 13a2, link information 13a3, registration status information 13a4, and the like.

Of these, the device information 13a1 defines information about the network device 30. For example, the device information 13a1 may be data associated with items such as a device ID, a device name, an IP address, and a display position. The “device ID” mentioned here refers to identification information for identifying the network device 30. The “device name” refers to the name defined in the network device 30. Further, the “IP address” has a literal meaning, but here refers to the IP address assigned to the network device 30 having the device ID, and is set by SE or the like when the network NW is constructed. In addition, the “display position” refers to a position displayed on the topology map, and for example, the reference point of the icon of the network device 30, for example, the coordinates at which the center of gravity or the vertex is arranged on the topology map are registered. To be done. Note that, here, the device name and the IP address are illustrated as an example of the items that define the network device 30, but in addition to this, a user name, a password, an administrator password, and the like used for login of the SSH connection to the network device 30. Other items may be further included in the device information 13a1.

Further, in the port information 13a2, information regarding the port included in the network device 30 is defined. For example, the port information 13a2 can employ data in which items such as a device ID, a port ID, a display number, an interface name, and an untag VLAN (Virtual LAN) ID are associated. The “device ID” mentioned here refers to the identification information of the network device 30 like the device ID included in the device information 13a1, but here it means the network device 30 having the port identified by the port ID. To do. Further, the “port ID” refers to identification information that identifies a port included in the network device 30. The "display number" refers to the number when the port is expanded and displayed on the topology map. The "interface name" refers to the name of the interface defined in the port. The "untag VLAN ID" refers to the VLAN ID set in the access port. That is, when a static VLAN, that is, a so-called port-based VLAN is set, the VLAN ID set in the access port is described. The "tag VLAN ID" refers to the VLAN ID set in the trunk port. That is, when the tag VLAN is set in the port, one or more VLAN IDs set in the trunk port are described.

Further, the link information 13a3 defines information about a link connecting ports of the network device 30. For example, the link information 13a3 can employ data in which items such as a link ID, a device ID1, a port ID1, a device ID2, and a port ID2 are associated with each other. The "link ID" referred to here is identification information that identifies a link. Further, “port ID1” and “port ID2” indicate the identification information of the port, like the port ID included in the port information 13a2, but here, of the two ports connecting the link identified by the link ID. Means identification information. Further, “device ID1” and “device ID2” refer to the identification information of the network device 30 like the device ID included in the device information 13a1, but here, the network device 30 having a port identified by the port ID1. And the identification information of the network device 30 having the port identified by the port ID2. In this way, in the link information 13a3, among the ports included in the device information 13b, the connected port or the port after linkup is registered.

The registration status information 13a4 defines information related to the registration status of the network device 30.

Here, in the present embodiment, data registration regarding the network device 30 is permitted even before the actual deployment of the network device 30. Hereinafter, the data registration regarding the network device 30 may be referred to as “device registration”.

In this way, when the device registration before the actual device deployment is accepted, the device registration collects various information such as the interface, the VLAN, and the failure from the actual device after the actual device deployment and using the commands such as telnet and SSH from the actual device. It is carried out at two timings, that is, the timing to be performed. Of these, the data whose device registration was performed at the former timing may be referred to as the first status, and the data whose device registration was performed at the latter timing may be referred to as the second status. Furthermore, in the following, the device registration before the actual device deployment may be referred to as “temporary registration”, and the device registration after the actual device deployment may be referred to as the “main registration”.

For example, the registration status information 13a4 can employ data in which items such as a device ID and a registration status are associated with each other. The “registration status” here refers to the registration status of the network device 30, and for example, in the field of the registration status, information that can identify whether it is the first status or the second status, such as a flag. Binary information is set. By associating the registration status with the device ID in this way, the entries of the device information 13a1, the port information 13a2, and the link information 13a3 including the device ID in which the first status is set are the data registered before the actual deployment, that is, The entries of the device information 13a1, the port information 13a2, and the link information 13a3 that include the device ID for which the second status is set can be distinguished from the data of the temporary registration, but the entries registered after the actual device deployment, that is, the data of the main registration. Can be identified as In the following, the network device 30 having the device ID for which the first status is set may be referred to as a “temporary registration device”.

The control unit 15 is a processing unit that performs overall control of the network management device 10.

As one embodiment, the control unit 15 can be implemented by a hardware processor such as a CPU (Central Processing Unit) or MPU (Micro Processing Unit). Here, the CPU and the MPU are illustrated as an example of the processor, but the processor can be implemented by any processor regardless of general-purpose type and specialized type. In addition, the control unit 15 may be realized by a hard-wired logic such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

The control unit 15 is a control program that realizes the function of the network management service on a work area of a RAM such as a DRAM (Dynamic Random Access Memory) or an SRAM (Static Random Access Memory) implemented as a main storage device (not shown). The following processing units are virtually realized by developing.

As shown in FIG. 2, the control unit 15 includes a display control unit 15a, a first registration unit 15b, a collection unit 15c, a determination unit 15d, a second registration unit 15e, and an output unit 15f. ..

The display control unit 15a is a processing unit that performs display control on the client terminal 50.

As one aspect, the display control unit 15a refers to the topology information 13a stored in the storage unit 13 and displays, in the client terminal 50, a window including a topology map in which the connection shape between the devices included in the network NW is modeled. Display it. For example, the display control unit 15a arranges, for each device ID included in the device information 13a1 of the above-mentioned topology information 13a, a device icon in which the network device 30 is modeled according to the display position associated with the device ID. To do. At this time, the display control unit 15a distinguishes the display form of the device icon whose registration status included in the registration status information 13a4 is the first status from the display form of the device icon whose second status is the second status. For example, an icon indicating temporary registration, for example, a spanner mark, is added to the device icon having the first status. Further, the display control unit 15a further expands and displays the symbol in which each port included in the network device 30 corresponding to the device icon is schematically illustrated according to the port information 13a2 in the topology information 13a. Further, the display control unit 15a further draws a line drawing of a link connecting the symbols of the ports of the network device 30 whose port ID1 and port ID2 are registered in the link information 13a3 of the topology information 13a. The window of the topology map generated in this way is displayed on the client terminal 50.

The first registration unit 15b is a processing unit that performs device registration before deployment of an actual device.

As one embodiment, the first registration unit 15b can edit the topology map when a GUI component such as a tab or a menu for editing the topology map is operated on the window of the topology map. When editing this topology map, a window for device registration can be called. For example, on the device registration window, the device ID and device name can be automatically assigned by accepting the designation of the type of network device such as a switch or router and the designation of the model of the manufacturer. In addition, the first registration unit 15b receives the setting of the IP address and the interface name of the port assigned to the network device 30 as the basic information of the network device 30. At this time, it is not necessary to set the interface names of all the ports of the actual machine to be deployed. In other words, it is also possible to focus on the interface name of the port that draws and edits the connection on the topology map.

When a GUI component for confirming the intention of temporary registration, for example, a temporary registration button is operated after receiving these inputs, the first registration unit 15b performs temporary registration regarding the device. For example, the first registration unit 15b automatically assigns a device ID or device name and then creates a new entry in the device information 13a1, or responds to each interface according to the interface name that has been set. A new entry is created in the port information 13a2 after automatically assigning a port ID or display number, or a new status in which the first status is associated with the previously assigned device ID in the registration status information 13a4. Or create an entry for. After the temporary registration is performed in this way, a device icon to which an icon indicating the temporary registration is added is displayed on the topology map. Further, a symbol of a port corresponding to the interface name set at the time of temporary registration is expanded and displayed on the device icon. This device icon can be placed at any position by dragging and dropping or specifying coordinates.

When the device icon is displayed on the topology map in this way, it is possible to draw and edit the connection even with the temporarily registered device icon. Here, when the drawing operation of the connection that connects the port symbol expanded and displayed on the temporarily registered device icon and the port symbol expanded and displayed on the other device icon is performed, the first registration unit 15b Performs temporary registration for links. For example, the first registration unit 15b automatically assigns a link ID, identifies the device ID1 and the port ID1, the device ID2, and the port ID2 from the two ports connected by the above-described wiring, and newly adds the new link information 13a3. Generate an entry for. In addition, the VLAN settings and the temporary registration of the failure information can be performed by calling various menus such as the VLAN and the failure information from the temporary registration device icon. The VLAN settings and the failure information temporarily registered in this way can also be displayed on the topology map.

The collection unit 15c is a processing unit that collects various types of information from the network device 30.

As one aspect, when the collection unit 15c receives a request to shift the temporary registration of the network device 30 to the main registration, the collection unit 15c associates the first status among the device IDs included in the registration status information 13a4. The following processing is executed for each device ID thus obtained. That is, the collection unit 15c starts the IP address corresponding to the device ID of the temporary registration device whose registration status is the first status among the IP addresses included in the device information 13a1, and the user name and password used for login of the SSH connection. Or, when logging in as an administrator, refer to the user name, password, and administrator password. Subsequently, the collection unit 15c makes an SSH connection to the temporary registration device to which the IP address is assigned and logs in to the network device 30. Then, the collection unit 15c transmits commands such as show running-config and show interfaces status. As a result, the interface information such as the interface name of the port and the link-up state can be collected as the return value of the command from the actual device of the network device 30 corresponding to the temporarily registered device. Using the interface names of the ports thus collected, the determination unit 15d, which will be described later, determines whether or not there is a defect such as an error or omission in the interface name at the time of temporary registration.

In this way, when transitioning from temporary registration to main registration, other information can be further collected in addition to the interface information. That is, at the time of provisional registration, the detailed information is not necessarily registered as much as the information collected from the actual device after the network device 30 is deployed. For example, an interface name of a port that is not scheduled to be connected at the time of temporary registration is not always registered, and various VLAN settings set for the port are not necessarily registered. Therefore, at the time of transition from the temporary registration to the main registration, the collection unit 15c collects information about the topology and the VLAN setting.

More specifically, when the information about the topology is collected, the collection unit 15c performs the following process for each device ID associated with the first status among the device IDs included in the registration status information 13a4. To execute. That is, the collection unit 15c refers to the IP address corresponding to the device ID having the first status among the IP addresses included in the device information 13a1. Subsequently, the collection unit 15c makes an SSH connection to the network device 30 to which the IP address is assigned and logs in to the network device 30. Then, the collection unit 15c transmits a command such as show lldp neighbors to the network device 30. As a result, information that is advertised via the LLDP (Link Layer Discovery Protocol), for example, a link, is formed between the network device 30 that is the destination of the command and the network device 30 that is adjacent to the network device 30 that is the destination of the command. It is possible to acquire the interface information of the two ports to be used as the return value of the command. Then, the collection unit 15c creates a new entry in the link information 13a3 when there is a port combination that does not exist in the entry of the link information 13a3 among the port combinations collected using the command.

When various VLAN settings for the port are acquired, the collection unit 15c sends commands such as show vlan and show interfaces trunk to the network device 30 on the network NW. As a result, various VLAN settings for the port can be acquired for each port as the return value of the command. For example, in addition to the operation mode of the port, setting values of various VLANs are acquired. That is, when the operation mode is “access”, the VLAN ID of the port-based VLAN set in the access port is acquired. When the operation mode is "trunk", the VLAN ID of the tag VLAN set in the trunk port is acquired. According to the information collected by using these commands, the collection unit 15c newly registers a setting value in a field related to the VLAN setting included in the port information 13a2 of the topology information 13a, that is, in the untag VLAN ID or the tag VLAN ID. , Update or.

The collection of the topology and the VLAN settings is not limited to the transition from the temporary registration to the main registration, and is stored in the storage unit 13 by collecting the information about the topology and the VLAN settings at the following timings even after the main registration. The created topology information 13a can be updated. As an example of the timing at which such collection is executed, an instruction is input via the client terminal 50 in addition to the case where the time since the acquisition was executed last time has passed a predetermined cycle, for example, 5 seconds. In this case, the system time stored in an internal memory (not shown) may reach a predetermined regular time, for example, 6 o'clock, 12 o'clock, or 18 o'clock.

The determination unit 15d is a processing unit that determines whether or not there is a defect in the interface name of the port at the time of temporary registration.

As one embodiment, the determination unit 15d acquires the temporarily registered interface name associated with the device ID used for collection by the collection unit 15c, out of the interface names of the ports included in the port information 13a2. Then, the determination unit 15d compares the temporarily registered interface name acquired from the port information 13a2 with the interface name of the port collected from the actual device of the network device 30 by the collection unit 15c. For example, the determination unit 15d determines, for each temporary registration interface name, whether or not there is an interface name that exactly matches the character string of the temporary registration interface name among the interface names of the ports collected from the actual device. To do. At this time, if an interface name that exactly matches the character string of the temporary registration interface name exists in the interface names of the ports collected from the actual device for each temporary registration interface name, all temporary registration interface names will be included. It can be confirmed that there is no mistake. On the other hand, if the character string of any temporarily registered interface name does not exactly match with the interface name of the port collected from the actual machine, the character string will match exactly with the interface name of the port collected from the actual machine. Interface name does not exist It can be seen that there is an error in the temporarily registered interface name.

Subsequently, when there is no error in all the temporarily registered interface names, the determination unit 15d determines whether or not the number of temporarily registered interface names is the same as the number of port interface names collected from the actual device. Further judge. At this time, if the numbers of both are the same, it can be confirmed that the interface names of the temporary registration are complete. On the other hand, if the number of temporarily registered interface names is less than the number of port interface names collected from the actual device, it can be confirmed that the temporarily registered interface names are missing.

The second registration unit 15e is a processing unit that performs device registration after deployment of an actual device.

As one embodiment, when the number of interface names for temporary registration is smaller than the number of interface names for ports collected from the actual machine, the second registration unit 15e performs temporary registration among the interface names for ports collected from the actual machine. The interface name that does not exist in the interface name is additionally registered in the port information 13a2 as a supplementary interface name. Then, the second registration unit 15e sets the registration status corresponding to the device ID included in the registration status information 13a4, which is confirmed to have no error or omission in the interface name, to the first registration status. Update from status to second status. At this time, even if there is no error in the interface name set at the time of temporary registration, the registration order of the interface names in the port information 13a2 may not match the order of the interface names in which the ports are arranged on the actual device. In such a case, the second registration unit 15e rearranges the registration order of the interface names set in the port information 13a2 at the time of temporary registration in the order of the interface names in which the ports are arranged in the actual machine. By updating the registration status, the entries of the device information 13a1, the port information 13a2, and the link information 13a3 having the device ID are transferred from the temporary registration to the main registration. On the other hand, the second registration unit 15e skips the registration of the supplementary interface name when the number of provisionally registered interface names is the same as the number of port interface names collected from the actual device. , The registration status corresponding to the device ID that is confirmed to have no defect in the interface name is updated from the first status to the second status.

Although the description has been focused here on the registration of the interface name, the collecting unit 15c may be used to execute the registration from the actual device before or after the registration of the supplementary interface name and the update of the registration status. The collected VLAN settings and failure information of each port can be registered in the port information 13a2.

The output unit 15f is a processing unit that outputs an error.

As one embodiment, if there is an error in any of the temporarily registered interface names, the output unit 15f outputs the error interface name as an error. For example, the output unit 15f displays an error interface name and a message indicating that the interface does not exist and/or outputs a voice.

[Specific Example 1]
FIG. 3 is a diagram showing an example of transition from temporary registration to main registration. FIG. 3 shows an example in which the temporary registration of the device ID “Node-1” is transferred to the main registration. Reference numeral 300 in FIG. 3 indicates a list of entries of the port information 13a2 related to the device ID “Node-1”. Further, reference numeral 310 in FIG. 3 indicates a list of interface names collected from the actual device having the device ID “Node-1”. Further, reference numeral 320 in FIG. 3 indicates a list of entries of the port information 13a2 when the temporary registration is shifted to the main registration.

As shown in FIG. 3, the temporarily registered interface name included in the list 300 of the entries of the port information 13a2 related to the device ID “Node-1” and the list of interface names collected from the actual device having the device ID “Node-1”. The determination unit 15d compares the value with 310. In this case, in the interface name list 310 collected from the actual device with the device ID “Node-1”, there is an interface name that exactly matches the character string of the temporarily registered interface name for each temporarily registered interface name. That is, the interface name that completely matches the temporarily registered interface name “ether1” exists in the list 310, the interface name that completely matches the temporarily registered interface name “ether2” exists in the list 310, and An interface name that exactly matches the registered interface name “ether3” is also present in the list 310. Therefore, it can be confirmed that there is no error in the temporarily registered interface name.

On the other hand, in the example shown in FIG. 3, since the number of temporarily registered interface names is “3”<the number of interface names collected from the actual device having the device ID “Node-1” is “6”, You can see that there are three leaks. Therefore, as shown in the entry list 320 of the port information 13a2, the interface names “ether4” to “ether6” that do not exist in the temporarily registered interface names among the interface names collected from the actual device of the device ID “Node-1” are It is additionally registered in the port information 13a2 as a supplementary interface name.

[Specific example 2]
FIG. 4 is a diagram showing an example of transition from temporary registration to main registration. FIG. 4 shows an example in which the temporary registration of the device ID “Node-1” is transferred to the main registration. Reference numeral 400 in FIG. 4 indicates a list of entries of the port information 13a2 related to the device ID “Node-1”. Further, reference numeral 410 in FIG. 4 indicates a list of interface names collected from the actual device having the device ID “Node-1”. Reference numeral 420 in FIG. 4 shows a list of entries of the port information 13a2 when the temporary registration is shifted to the main registration.

As shown in FIG. 4, the temporarily registered interface names included in the list 400 of the entries of the port information 13a2 related to the device ID “Node-1” and the list of interface names collected from the actual device of the device ID “Node-1”. The determination unit 15d compares the value with 410. In this case, in the interface name list 410 collected from the actual device with the device ID “Node-1”, there is an interface name that exactly matches the character string of the temporarily registered interface name for each temporarily registered interface name. That is, the interface name that exactly matches the temporarily registered interface name “ether3” exists in the list 310, the interface name that completely matches the temporarily registered interface name “ether2” exists in the list 310, and An interface name that exactly matches the registered interface name “ether6” also exists in the list 410. Therefore, it can be confirmed that there is no error in the temporarily registered interface name.

On the other hand, in the example shown in FIG. 4, since the number of temporarily registered interface names is “3”<the number of interface names collected from the actual device with the device ID “Node-1” is “6”, You can see that there are three leaks. Therefore, as shown in the entry list 420 of the port information 13a2, the interface names “ether1”, “ether4”, and the like, which do not exist in the temporarily registered interface names among the interface names collected from the actual device with the device ID “Node-1”, “Ether5” is additionally registered in the port information 13a2 as a supplementary interface name.

Further, in the example shown in FIG. 4, the order of registering the interface names in the port information 13a2 does not match the order of the interface names in which the ports are arranged in the actual machine. That is, in the port information 13a2, the interface names are registered in the order of "ether3", "ether2", and "ether6". On the other hand, the order of the interface names in which the ports are arranged in the actual machine is "ether1", "ether2", "ether3", "ether4", "ether5", and "ether6". In this way, when the order of registering the interface names in the port information 13a2 does not match the order of the interface names in which the ports are arranged on the actual device, as shown in the entry list 420 of the port information 13a2, the port information 13a2 is registered in the temporary registration. The registration order of the set interface names is rearranged in the order of the interface names in which the ports are arranged in the actual machine.

For example, when the rearrangement is performed before the interface names are supplemented, the entry of the port information 13a2 is the interface name “ether3”, the interface name “ether2”, the interface name “ether6” in the order of registration, and the interface name “ether2” The names are sorted in the registration order of "ether3" and the interface name "ether6". Further, when the rearrangement is performed after the interface names are replenished, the entries of the port information 13a2 are interface names “ether1”, “ether3”, interface name “ether2”, interface name “ether4”, interface name “ether5”, interface The registration order of the name "ether6" is changed to the registration order of the interface name "ether1", the interface name "ether2", the interface name "ether3", the interface name "ether4", the interface name "ether5", and the interface name "ether6". ..

[Specific Example 3]
FIG. 5 is a diagram showing an example of transition from temporary registration to main registration. FIG. 5 shows an example in which the temporary registration of the device ID “Node-1” is transferred to the main registration. Reference numeral 500 in FIG. 5 indicates a list of entries of the port information 13a2 related to the device ID “Node-1”. Further, reference numeral 510 in FIG. 5 indicates a list of interface names collected from the actual device having the device ID “Node-1”. Reference numeral 520 in FIG. 5 indicates an error output example.

As shown in FIG. 5, the temporarily registered interface name included in the list 500 of the entries of the port information 13a2 related to the device ID “Node-1” and the list of interface names collected from the actual device of the device ID “Node-1”. The determination unit 15d compares the value 510 with the value 510. In this case, the interface names “ether3” and “ether6” among the interface names set at the time of temporary registration have a character string in the list 510 of interface names collected from the actual device with the device ID “Node-1”. Interface name exists. On the other hand, in the interface name “ether2a” set at the time of temporary registration, there is no interface name with a matching character string in the interface name list 510 collected from the actual device with the device ID “Node-1”. Therefore, it is found that the temporarily registered interface name "ether2a" has an error.

In this case, an error message indicating that there is no interface corresponding to the temporarily registered interface name “ether2a” is output to the client terminal 50. Further, as in the error output example 520 shown in FIG. 5, the display form of the entry having an error in the interface name of the port information 13a2 and the display form of the entry having no error in the interface name are distinguished from each other. For example, in the port information 13a2, the font or fill of the entry having an error in the interface name is highlighted. At this time, the interface name list 510 collected from the actual device with the device ID “Node-1” can be displayed together. As a result of the output of such an error, it is possible to prompt the network administrator or the like to correct the correct interface name.

[One Side of Effects of Concrete Example 1 to Concrete Example 3]
In this way, the transition from the temporary registration to the main registration is permitted only when the correct interface name is input. Further, if the temporarily registered interface name is missing, the missing interface name can be supplemented to perform the main registration. Furthermore, when the registration order of the interface names at the time of temporary registration is different from the order in which the ports are arranged on the actual machine, the interface names can be sorted according to the order in which the ports are arranged for main registration. Therefore, even if temporary registration is allowed, it is possible to suppress inconsistency in the contents of device registration between temporary registration and main registration, resulting in inconsistency between the display of the topology map and the entity of the network. Can also be suppressed. Therefore, the device registration before the actual device deployment can be realized.

[Process flow]
FIG. 6 is a flowchart illustrating a procedure of control processing according to the first embodiment. This processing is activated, as an example, on condition that a request for shifting the temporary registration of the network device 30 to the main registration is received. The processing of steps S102 to S111 shown in FIG. 6 is repeatedly executed for each device ID whose registration status is the first status.

As shown in FIG. 6, when the request for shifting the temporary registration of the network device 30 to the main registration is received (step S101), the collection unit 15c executes the following process. That is, the collection unit 15c starts the IP address corresponding to the device ID of the temporary registration device whose registration status is the first status among the IP addresses included in the device information 13a1, and the user name and password used for login of the SSH connection. Is referred to (step S102).

Subsequently, the collection unit 15c makes an SSH connection to the temporary registration device to which the IP address referred to in step S102 is assigned, and logs in to the network device 30 (step S103). Then, the collection unit 15c transmits commands such as show running-config and show interfaces status. Through the transmission of such a command, the collection unit 15c collects the interface information such as the interface name of the port and the link-up state from the actual device of the network device 30 corresponding to the temporary registration device as the return value of the command (step S104). ..

Then, the determination unit 15d compares the interface name of the temporarily registered device included in the port information 13a2 with the interface name of the port collected from the actual device of the network device 30 in step S104 (step S105).

At this time, if there is no error in all the temporarily registered interface names (No in step S106), the determination unit 15d determines that the number of temporarily registered interface names is the same as the number of port interface names collected from the actual device. It is further determined whether or not (step S107).

Here, when the number of the temporarily registered interface names is smaller than the number of the interface names of the ports collected from the actual device (Yes in step S107), it can be confirmed that the temporarily registered interface names are missing. In this case, the second registration unit 15e additionally registers, in the port information 13a2, an interface name that does not exist in the temporarily registered interface names among the interface names of the ports collected from the actual device as the supplementary interface name (step S108). .. If the numbers are the same (No in step S107), it can be confirmed that the interface names for temporary registration have no omissions, and thus the process in step S108 is skipped.

After that, the second registration unit 15e sets the registration status corresponding to the device ID included in the registration status information 13a4, which is confirmed to have no error or omission in the interface name, from the first status. The status is updated to the second status (step S109). Then, the second registration unit 15e displays on the client terminal 50, as a result of the transition from the temporary registration to the main registration, for example, an entry regarding the device ID in the port information 13a2 after the main registration, together with a message of transition OK ( Step S110), and the process ends.

On the other hand, if any of the temporarily registered interface names has an error (Yes in step S106), the output unit 15f outputs the interface name having the error as an error (step S111), and ends the process.

[One side of effect]
As described above, the network management device 10 according to the present embodiment temporarily registers the interface name registration state depending on whether the interface names temporarily registered before the actual device deployment are included in the interface names collected from the actual device. Controls whether to update from to main registration or output an error. Therefore, even if temporary registration is allowed, it is possible to suppress the inconsistency in the contents of device registration between the temporary registration and the main registration, and as a result, it is possible to suppress the inconsistency between the display of the topology map and the entity of the network. it can. Therefore, according to the network management device 10 according to the present embodiment, it is possible to realize the device registration before the actual device deployment.

Although the embodiments of the disclosed device have been described above, the present invention may be implemented in various different forms other than the embodiments described above. Therefore, other embodiments included in the present invention will be described below.

[Link judgment]
In the first embodiment described above, the case where the interface name set at the time of temporary registration and the interface name collected from the actual machine are compared has been exemplified. However, in addition to this, the link set at the time of temporary registration and the actual machine It is also possible to determine whether or not there is an error in the link for each link set at the time of temporary registration, by comparing with the connection information between the ports collected from.

That is, the first registration unit 15b can further register a connection connecting two ports, that is, a so-called link, in addition to the IP address and the interface name of the network device 30. For example, when a drawing operation of a connection that connects the port symbol expanded and displayed on the temporarily registered device icon and the port symbol expanded and displayed on another device icon is performed, the first registration unit 15b displays , Temporary registration for links is performed. For example, the first registration unit 15b automatically assigns a link ID, identifies the device ID1 and the port ID1, the device ID2, and the port ID2 from the two ports connected by the above-described wiring, and newly adds the new link information 13a3. Generate an entry for.

In the case of a link that was provisionally registered in this way, when transitioning from provisional registration to main registration, there is no error in the link that was set during provisional registration by comparison with the interface information between ports collected from the actual device. It is also possible to determine whether or not.

For example, the collection unit 15c logs in the network device 30 corresponding to the temporary registration device whose registration status is the first status, and then transmits a command such as show cdp neighbors to the network device 30. Thereby, information advertised via the LLDP between the network device 30 in the temporary registration state and another network device 30 adjacent to the network device 30, for example, interface information of two ports forming a link. Etc. can be obtained as the return value of the command.

Then, the determination unit 15d extracts an entry including the device ID collected by the collection unit 15c from the entries of the link information 13a3. Then, the determination unit 15d determines, for each entry extracted from the link information 13a3, a combination of interface names corresponding to a combination of port IDs, that is, a combination of interfaces that match the combination of interface names set as links at the time of temporary registration. It is determined by the collection unit 15c whether or not it is included in the interface information collected from the actual device of the network device 30.

At this time, if a combination of interfaces that matches a combination of interface names corresponding to a combination of port IDs held by the entry extracted from the link information 13a3 is not included in the interface information collected from the actual device, it will be temporarily registered. It turns out that the set link is incorrect.

If there is such an error, it can be classified into the following two cases. That is, if only one interface name of the combination of interface names set as a link at the time of temporary registration is included in the interface information collected from the actual machine, insert it into one of the ports of the connection made when deploying the actual machine. It turns out that there are mistakes. Also, if both of the two interface names included in the combination of interface names set as links at the time of temporary registration are not included in the interface information collected from the actual machine, the link of the temporarily registered link before the actual machine is deployed. It turns out that is not done. In these cases, the output unit 15f can notify a port insertion error or unconnected.

On the other hand, when all the combinations of interface names set as links at the time of temporary registration are included in the interface information collected from the actual device, it is found that each link set at the time of temporary registration has no error. In this case, the second registration unit 15e has no error in the interface name of the temporary registration device among the device IDs included in the registration status information 13a4, and there is an error in the link including the interface name of the temporary registration device in the combination. If not, the registration status corresponding to the device ID is updated from the first status to the second status.

FIG. 7A is a diagram showing an example of the topology map. In FIG. 7A, among the device icons included in the topology map, the device icons of Node-1 and Node-2 that have been temporarily registered are shown in an excerpted manner. As shown in FIG. 7A, a connection is drawn on the device icon of Node-1 and the device icon of Node-2. That is, a connection is made between the port with the display number “01” of the four ports that the device icon of Node-1 has and the port with the display number “01” of the four ports that the device icon of Node-2 has. Is drawn. By drawing and editing such a connection, the link information 13a3 corresponds to the port ID corresponding to the display number “01” of the device icon of Node-1 and the display number “01” of the device icon of Node-2. The entry including the combination with the port ID to be registered is provisionally registered as a link. Although the display number of the port expanded and displayed on the device icon on the topology map is shown here, the interface name is associated with the display number of the port on the port information 13a2.

FIG. 7B is a diagram showing an example of the connection status of the actual machine. FIG. 7B shows the connection status between the actual device of the network device 30 of Node-1 and the actual device of the network device 30 of Node-2. As shown in FIG. 7B, the port with the display number “01” of Node-1 and the port with the display number “02” of Node-2 are connected between the actual devices of Node-1 and Node-2. There is.

The link for temporary registration shown in FIG. 7A and the connection status of the actual device shown in FIG. 7B are compared. That is, the combination of the interface names corresponding to the combination of the port IDs included in the link entry of the link information 13a3, that is, the combination of the interface names set as the link at the time of temporary registration and the actual device of Node-1 or Node-2 are collected. Interface information is compared. Among these, the link information 13a3 includes an interface name corresponding to the display number “01” of the device icon of Node-1 and an interface name corresponding to the display number “01” of the device icon of Node-2. The combination is included as an entry. On the other hand, the interface information collected from the actual device of Node-1 includes the association between the interface name corresponding to the display number "01" of Node-1 and the interface name corresponding to the display number "02" of Node-2. Be done.

In this case, the combination of the interface name corresponding to the display number “01” of the device icon of Node-1 and the interface name corresponding to the display number “01” of the device icon of Node-2 is the interface information. Includes the interface name corresponding to the display number “01” of Node-1, but does not include the interface name corresponding to the display number “01” of the device icon of Node-2. For this reason, it is output as an error that there is a port insertion error in either the port with the display number "01" of Node-1 or the port with the display number "02" of Node-2.

FIG. 7C is a diagram showing an output example of an error. For example, as shown in FIG. 7C, in the port information 13a2, two entries that may cause a port insertion error, that is, the entry with the display number “01” of Node-1 and the display number “02” of Node-2 are shown. The entry is displayed in a display mode different from that of other entries. In addition to this, an error message indicating that there is an error in inserting the port into either the port with the display number “01” of Node-1 or the port with the display number “02” of Node-2 may be output, or the topology may be output. The symbols of the above two ports may be highlighted on the map.

As a result, the link can be updated from the temporary registration to the main registration only when there is no port insertion error or unconnected between the link set at the time of temporary registration and the interface information collected from the actual device.

[Distribution and integration]
In addition, each component of each device illustrated does not necessarily have to be physically configured as illustrated. That is, the specific form of distribution/integration of each device is not limited to that shown in the figure, and all or part of the device may be functionally or physically distributed/arranged in arbitrary units according to various loads and usage conditions. It can be integrated and configured. For example, the display control unit 15a, the first registration unit 15b, the collection unit 15c, the determination unit 15d, the second registration unit 15e or the output unit 15f may be connected as an external device of the network management device 10 via a network. Good. Further, another device has the display control unit 15a, the first registration unit 15b, the collection unit 15c, the determination unit 15d, the second registration unit 15e, or the output unit 15f, and each device is connected to the network to cooperate with each other. The functions of the network management device 10 described above may be realized. Further, even if another device has all or part of the topology information 13a stored in the storage unit and is network-connected and cooperates with each other, the function of the network management device 10 described above is realized. I don't care.

[Control program]
Further, the various processes described in the above embodiments can be realized by executing a prepared program on a computer such as a personal computer or a workstation. Therefore, in the following, an example of a computer that executes a control program having the same functions as those in the above embodiment will be described with reference to FIG.

FIG. 8 is a diagram illustrating a hardware configuration example of a computer that executes a control program according to the first and second embodiments. As illustrated in FIG. 8, the computer 100 includes an operation unit 110a, a speaker 110b, a camera 110c, a display 120, and a communication unit 130. Further, the computer 100 has a CPU 150, a ROM 160, an HDD 170, and a RAM 180. Each unit of these 110 to 180 is connected via a bus 140.

As shown in FIG. 8, the HDD 170 includes the display control unit 15a, the first registration unit 15b, the collection unit 15c, the determination unit 15d, the second registration unit 15e, and the output unit 15f shown in the first embodiment. A control program 170a having the same function is stored. This control program 170a is the same as each component of the display control unit 15a, the first registration unit 15b, the collection unit 15c, the determination unit 15d, the second registration unit 15e, and the output unit 15f shown in FIG. You can separate them. That is, the HDD 170 does not necessarily need to store all the data described in the first embodiment, and the data used for the processing may be stored in the HDD 170.

Under such an environment, the CPU 150 reads out the control program 170a from the HDD 170 and loads it on the RAM 180. As a result, the control program 170a functions as the control process 180a, as shown in FIG. The control process 180a expands various data read from the HDD 170 in an area allocated to the control process 180a in the storage area of the RAM 180, and executes various processes using the expanded various data. For example, the processing shown in FIG. 6 and the like are included as an example of the processing executed by the control process 180a. Note that in the CPU 150, not all the processing units described in the above-described first embodiment may operate, and the processing unit corresponding to the processing to be executed may be virtually realized.

The above control program 170a does not necessarily have to be stored in the HDD 170 or the ROM 160 from the beginning. For example, each program is stored in a “portable physical medium” such as a flexible disk inserted into the computer 100, a so-called FD, a CD-ROM, a DVD disk, a magneto-optical disk, an IC card, or the like. Then, the computer 100 may acquire and execute each program from these portable physical media. Further, each program is stored in another computer or a server device connected to the computer 100 via a public line, the Internet, a LAN, a WAN, etc., and the computer 100 acquires and executes each program from these. You may

1 Network Management System 3 Monitoring Target System 10 Network Management Device 11 Communication I/F Section 13 Storage Section 13a Topology Information 15 Control Section 15a Display Control Section 15b First Registration Section 15c Collection Section 15d Judgment Section 15e Second Registration Section 15f Output unit 30A, 30B, 30C Network device 50 Client terminal

Claims (5)

The IP address to be assigned to the device included in the monitored network is registered, and the identification information of the port included in the device is registered as the first status,
When the setting information transmission request for the device is transmitted to the device using the registered IP address and the setting information is received from the device, the identification information of the port of the device registered in the setting information. Is included,
As a result of the determination, when the set setting information includes all the registered identification information, the first status of the identification information is changed to the second status and registered,
When the set setting information does not include a part of the registered identification information, an error corresponding to the port regarding the identification information that is not included is output,
A control program that causes a computer to execute a process. The process of registering as the first status registers a combination of identification information of a port included in the device registered as the first status and identification information of a port included in another device different from the device. Then
The determination processing is performed by transmitting a request for transmitting connection information between ports related to the device to the device using the registered IP address, and when receiving connection information between the ports from the device, It is determined whether or not the registered combination is included in the setting information,
In the process of changing to the second status and registering, as a result of the determination, if all of the registered combinations are included in the setting information, the identification information is changed from the first status to the Change to the second status and register,
The process of outputting the error outputs an error corresponding to identification information of a port regarding a combination not included when the setting information does not include a part of the registered combination. The control program according to item 1. Using the registered IP address, a transmission request for setting information or fault information regarding virtual networks other than the setting information regarding the apparatus is transmitted to the apparatus included in the monitored network, and the apparatus relates to the virtual network. When the setting information or the failure information is received, the computer may be made to further execute the processing of displaying the setting information or the failure information regarding the virtual network regarding each device together with the connection relationship between the devices included in the monitored network. The control program according to claim 1, which is characterized in that. The IP address to be assigned to the device included in the monitored network is registered, and the identification information of the port included in the device is registered as the first status,
When the setting information transmission request for the device is transmitted to the device using the registered IP address and the setting information is received from the device, the identification information of the port of the device registered in the setting information. Is included,
As a result of the determination, when the set setting information includes all the registered identification information, the first status of the identification information is changed to the second status and registered,
When the set setting information does not include a part of the registered identification information, an error corresponding to the port regarding the identification information that is not included is output,
A control method characterized in that a computer executes a process. A first registration unit for registering an IP address to be assigned to a device included in the monitored network and for registering identification information of a port included in the device as a first status;
When the setting information transmission request for the device is transmitted to the device using the registered IP address and the setting information is received from the device, the identification information of the port of the device registered in the setting information. And a determination unit that determines whether or not
As a result of the determination, when the set setting information includes all the registered identification information, the second registration unit that changes the first status of the identification information to the second status and registers the changed status. When,
If the set setting information does not include a part of the registered identification information, an output unit that outputs an error corresponding to the port related to the identification information that is not included,
A control device having:

Images