JP2008167321A - Hierarchical network management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve a problem that operational cost increases by performing it by hand because a setting change operation of distributed management server is complicated although a plurality of apparatus can be managed by performing management by management server group hierarchically distributed. <P>SOLUTION: The data communication system is provided with a plurality of management servers and a plurality of data communication apparatuses. The data communication apparatuses are mutually connected by the network of a tree structure. A first data communication apparatus is managed by a first management server. A second management server for managing a second data communication apparatus of which is lower order than the first data communication apparatus in the network, manages a third data communication apparatus of which is lower than the second data communication apparatus. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The technology disclosed in this specification relates to a network management system that can be easily managed.

  In recent years, there is a tendency that all IPs are used regardless of whether they are wide area networks or corporate networks. This is intended to reduce the capital investment cost by sharing and using inexpensive IP network devices by performing all communications over IP.

  However, since many services are placed on one IP network, it is necessary to manage what was conventionally managed as a separate service as a single network. This means that when viewed from the single management system side, the number of network devices to be managed increases and the cost of operation management increases.

  When a single management server manages many devices to be managed, scalability is limited. In order to cope with this, it is common practice to manage one network by sharing the processing among a plurality of management servers.

  For example, although Patent Document 1 is a single server, a technique that simplifies processing and reduces the burden on the administrator by dividing the network into a plurality of hierarchized domains and performing management for each domain. Is disclosed.

Similarly, Non-Patent Document 1 discloses a configuration in which a network name space is divided into a plurality of hierarchized domains and a server in charge is assigned to each domain. Scalability is ensured by performing name resolution for these servers in a distributed manner.
JP 2002-204254 A P. Mockapetris, “Domain Names—Concepts and Facilities”, IETF, Request for Comment: 1034.

  The configuration of the network domain is often closely related to the configuration of the management subject domain. In recent years, in an enterprise, the organization configuration is frequently changed as a result of progress in the flexibility of the organization configuration. For this reason, management entity changes such as mergers and spin-offs are becoming more frequent. This also affects network management. That is, as the organization changes, the scope of responsibility of the management entity and the management target device is changed, so it is necessary to make changes to the network management system each time.

  A problem to be solved by the present invention is that a domain configuration change operation that occurs when managing a network system composed of a plurality of management domains becomes complicated.

  A representative invention disclosed in the present application is a data communication system including a plurality of data communication devices and a plurality of management servers that manage the plurality of data communication devices, and each of the management servers is configured by a first bus. A first control unit, a user I / F unit, a first network I / F unit, and a first memory connected to each other, each of the data communication devices being connected to each other by a second bus A terminal I / F unit, a data transfer processing unit, a second network I / F unit, and a second memory, wherein the plurality of data communication devices are connected to each other by a tree-structured network, and the first data communication The device is managed by the first management server, and the second management server manages the second data communication device lower than the first data communication device in the network. It is further characterized in that managing the third data communication device lower than the second data communication apparatus.

  According to an embodiment of the present invention, network management can be hierarchized, so that management scalability can be improved. That is, when the number of devices that can be managed by one management server is 100, the number of devices that can be handled in the entire network can be increased 10 times by dividing the domain into ten.

  Further, according to an embodiment of the present invention, the domain division is completed by simply connecting the management server to the neighboring device at the point to be divided without setting the management server. Thus, the operation cost can be reduced by reducing the man-hours related to the domain configuration change.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  In the embodiment of the present invention, in a network composed of a plurality of management servers and a plurality of packet communication devices for transferring data packets, the relationship between each management server and the management domain is determined by the connection position of the management servers. Here, the domain is a range of packet communication devices that can be managed by one management server. Furthermore, the embodiment of the present invention automates the setting procedure regarding domain division, absorption, combination, and separation operations based on this determination method.

  FIG. 1 is an explanatory diagram of a configuration example of a network targeted by an embodiment of the present invention.

  The packet communication devices 101-1 to 101-11 are connected to each other by a management VLAN (Virtual Local Area Network) having a tree structure topology. In the following description, the packet communication device 101-1 to 101-11 or other packet communication devices (for example, the packet communication device 101-21 etc.) are also simply referred to as the packet communication device 101.

  Each of the management servers 102-1 to 102-3 is a computer that manages setting, operation, maintenance, and the like of one or more packet communication apparatuses 101. The management servers 102-1 to 102-3 are directly connected to the packet communication device 101 serving as the root of each domain.

  In the example of FIG. 1, the management servers 102-1, 102-2, and 102-3 are directly connected to the packet communication devices 101-1, 101-4, and 101-3, respectively. The packet communication devices 101-1, 101-4, and 101-3 are routes of the domain A (103-1), the domain B (103-2), and the domain C (103-3), respectively. In the following description, the management server 102-1 to 102-3 or other management server (for example, the management server 102-21 or the like) is also simply referred to as the management server 102. In order to indicate any one of the domains 103-1 to 103-3 or other domains (for example, the domain 103-21 or the like), it is also simply referred to as the domain 103.

  Next, four operations on the domain 103 will be described with reference to FIGS. 2A to 2D.

  FIG. 2A is an explanatory diagram of domain division in the embodiment of the present invention.

  Domain division is an operation of dividing one domain 103 into two domains 103 at a certain point.

  In the example of FIG. 2A, the domain 103-21 including the packet communication devices 101-21 to 101-26 is set before the division is executed. The packet communication devices 101-21 to 101-26 are connected to each other by a management VLAN having a tree structure topology. The management server 102-21 is directly connected to the packet communication device 101-21 that is the route of the domain 103-21 (see the left side of FIG. 2A). At this time, the domain 103-21 is managed by the management server 102-21.

  Thereafter, the domain 103-21 is divided by directly connecting the management server 102-22 to the packet communication apparatus 101-22. As a result, the domain 103-21 includes the domain 103-23 composed of the packet communication devices 101-22, 101-24, and 101-25, and the domain 103- composed of the packet communication devices 101-21, 101-23, and 101-26. 22 (see the right side of FIG. 2A). Thereafter, the domain 103-22 is managed by the management server 102-21, and the domain 103-23 is managed by the management server 102-22.

  The packet communication apparatus 101-22 to which the management server 102-22 is directly connected is a root of a subtree composed of the packet communication apparatuses 101-22, 101-24, and 101-25. As described above, when the management server 102 is newly directly connected to any one of the packet communication apparatuses 101, a domain 103 corresponding to a subtree having the packet communication apparatus 101 as a root is newly set. As a result, the original domain 103 is divided.

  In the above example, the packet communication device 101-22 that has become the route of the new domain 103-23 is lower than the packet communication device 101-21 that is the route of the original domain 103-21 (that is, in the tree structure). It was on the side close to the leaf. In this case, the domain 103-23 is a lower domain of the domain 103-22.

  FIG. 2B is an explanatory diagram of domain absorption in the embodiment of the present invention.

  Domain absorption is an operation of absorbing the lower domain 103 into the upper domain 103 by removing the management server 102 of the lower domain 103 out of the two domains 103.

  In the example of FIG. 2B, before absorption is performed, from the domain 103-23 composed of the packet communication devices 101-22, 101-24, and 101-25, and the packet communication devices 101-21, 101-23, and 101-26. The domain 103-22 is set. Management servers 102-22 and 102-21 are directly connected to the packet communication devices 101-22 and 101-21 that are routes of the domains 103, respectively. The packet communication apparatuses 101-22 and 101-21 are connected to each other by a management VLAN (see the left side of FIG. 2B). At this time, the domain 103-22 is managed by the management server 102-21, and the domain 103-23 is managed by the management server 102-22.

  Then, the domain 103-23 is absorbed by the domain 103-22 by disconnecting the management server 102-22 from the packet communication device 101-22 (see the right side of FIG. 2B). As a result, the domain 103-23 and the domain 103-22 become one domain 103-21. Thereafter, the domain 103-21 is managed by the management server 102-21.

  As described above, when the packet communication device 101 that is the route of the lower domain 103 is connected to any one of the packet communication devices 101 of the upper domain 103, the management server 102 receives the packet communication device 101 that is the route of the lower domain 103. The lower domain 103 is absorbed by the upper domain 103 by separating the. As a result, one new domain 103 is set.

  FIG. 2C is an explanatory diagram of domain binding in the embodiment of the present invention.

  Domain binding is an operation of combining two independent management VLANs into one management VLAN.

  In the example of FIG. 2C, before combining is performed, the domain 103-23 including the packet communication devices 101-22, 101-24, and 101-25, and the packet communication devices 101-21, 101-23, and 101-26 are used. The domain 103-22 is set. Management servers 102-22 and 102-21 are directly connected to the packet communication devices 101-22 and 101-21 that are routes of the domains 103, respectively. The packet communication devices 101-22 and 101-21 are not connected to each other by the management VLAN. That is, the domain 103-23 and the domain 103-22 belong to independent management VLANs (see the left side of FIG. 2C).

  Thereafter, the domain 103-23 and the domain 103-22 are joined by connecting the packet communication device 101-22 to the lower level of the packet communication device 101-21 (see the right side of FIG. 2C). As a result, the domains 103-23 and 103-22 are still independent domains 103, but these domains 103 belong to the same management VLAN.

  FIG. 2D is an explanatory diagram of domain separation according to the embodiment of this invention.

  Domain separation is an operation of separating the one management VLAN into two independent management VLANs by separating the two domains 103 in one management VLAN at a certain point.

  In the example of FIG. 2D, before separation is performed, from the domain 103-23 composed of the packet communication devices 101-22, 101-24, and 101-25, and from the packet communication devices 101-21, 101-23, and 101-26. The domain 103-22 is set. Management servers 102-22 and 102-21 are directly connected to the packet communication devices 101-22 and 101-21 that are routes of the domains 103, respectively. The packet communication apparatuses 101-22 and 101-21 are connected to each other by a management VLAN (see the left side of FIG. 2D).

  Thereafter, the domain 103-23 is separated from the domain 103-22 by separating the packet communication apparatus 101-22 from the packet communication apparatus 101-21 (see the right side of FIG. 2D). As a result, the domain 103-23 and the domain 103-22 belong to independent management VLANs.

  When one domain 103 is separated into two domains 103 in this way, one is described as a parent domain 103 and the other as a child domain 103. The packet communication device 101 that is the route of the parent domain 103 is higher than the packet communication device 101 that is the route of the child domain 103 in the original domain 103. For example, in FIG. 2D, the domain 103-22 is the parent domain 103, and the domain 103-23 is the child domain 103.

  Next, each component of the network management system of this embodiment will be described.

  FIG. 3 is a block diagram illustrating a configuration of the packet communication apparatus 101 that is a management target by the network management system according to the embodiment of this invention.

  The packet communication apparatus 101 includes a bus 301, a control unit 302, a memory 303, a terminal interface (I / F) 309, a network I / F 310, a network I / F 311, a network I / F 312, and a packet transfer processing unit 317. .

  The bus 301 is for transferring data within the packet communication apparatus 101. The bus 301 is connected to the terminal I / F 309, the control unit 302, and the memory 303.

  The control unit 302 executes the program stored in the memory 303 to execute the setting of the packet transfer processing unit 317 of the packet communication device 101 and the processing of the packet transmitted to the packet communication device 101.

  The memory 303 stores a program executed by the control unit 302 and data necessary for device control. The memory 303 according to the present embodiment stores at least device setting information 307 and responsible management server information 308.

  The terminal I / F 309 is an interface unit for connecting a terminal for setting the packet communication apparatus 101.

  Each of the network I / Fs 310 to 312 is an interface unit that includes one or more ports (not shown) connected to other packet communication apparatuses 101 or the management server 102 and transmits and receives packets. Although three network I / Fs 310 to 312 are shown in FIG. 3, the packet communication apparatus 101 may include an arbitrary number of network I / Fs 310 to 312.

  The packet transfer processing unit 317 receives a packet from the network I / Fs 310 to 312 and transfers the packet to an appropriate network I / F 310 to 312. When receiving a packet addressed to the own apparatus, the packet transfer processing unit 317 transfers the received packet to the control unit 302.

  FIG. 4 is an explanatory diagram showing the contents of the charge management server information 308 stored in the memory 303 of the packet communication apparatus 101 according to the embodiment of this invention.

  The responsible management server information 308 includes a management server identifier 401 and a management server IP address 402. The management server identifier 401 is an identifier of the management server 102 that manages the packet communication device 101 (that is, the packet communication device 101 that holds the responsible management server information 308). The management server IP address 402 is an IP address of the management server 102 that manages the packet communication apparatus 101.

  FIG. 5 is an explanatory diagram showing the contents of the device setting information 307 stored in the memory 303 of the packet communication device 101 according to the embodiment of this invention.

  The device setting information 307 includes a device IP address 501, a device identifier 502, a device configuration definition 503, and a management VLAN ID 504. The device IP address 501 indicates the management IP address of the packet communication device 101. The device identifier 502 indicates the identifier of the packet communication device 101. The device configuration definition 503 stores the configuration definition of the packet communication device 101. The management VLAN ID 504 indicates the identifier of the management VLAN to which the packet communication apparatus 101 is connected.

  FIG. 6 is a block diagram illustrating a configuration of the management server 102 according to the embodiment of this invention.

  The management server 102 includes a user I / F unit 602, a network I / F unit 603, a control unit 604, and a memory 608.

  The user I / F unit 602 is connected to a display device such as a monitor and an input device such as a keyboard and a mouse, and accepts an operation from the user and presents a setting state and the like to the user.

  The network I / F unit 603 executes processing for exchanging packets between the packet communication apparatus 101 and the other management server 102.

  The control unit 604 is a part that performs processing in the management server 102 in response to a received packet and a user instruction.

  The memory 608 is a storage device that stores programs executed by the control unit 604 and data necessary for device control. The memory 608 of this embodiment stores at least a management target device table 605, own server setting information 606, and a device information collection table 607.

  The managed device table 605 is a setting of the packet communication device 101 to be managed by the management server 102 (that is, the management server 102 that holds the managed device table 605) and the management server 102 of the lower domain 103. It is a table for recording information. The own server setting information 606 stores an identifier or the like of the management server 102 that manages the upper domain 103. The device information collection table 607 is used to collect information in the domain 103 in advance when performing a domain join operation.

  FIG. 7 is an explanatory diagram of the management target device table 605 stored in the memory 608 of the management server 102 according to the embodiment of this invention.

  The managed device table 605 is a table for storing information on managed devices. The managed device table 605 includes columns of a type 701, an IP address 702, an identifier 703, a connection destination list 704, configuration definition information 705, and a setting 706. Each entry (ie, row) of the management target device table 605 includes each device (ie, one packet communication device 101 managed by the management server 102 or the management server) managed by the management server 102. Information related to one management server 102 that manages the lower domain 103 of 102 is stored.

  The type 701 is a column indicating whether the management target of the management server 102 is the packet communication apparatus 101 or the management server 102 of the lower domain 103. In the entry in which “device” is stored as the type 701, information on the packet communication device 101 that is the management target of the management server 102 is stored. In the entry in which “lower domain management server” is stored as the type 701, information on the management server 102 of the lower domain 103 of the management server 102 is stored.

  The IP address 702 is a column indicating the IP address of the management target device used when performing communication between the management server 102 and the management target device.

  The identifier 703 is a column indicating an identifier value for identifying the management target device.

  The connection destination list 704 is a column indicating the identifier, connection port, and domain 103 of the packet communication apparatus 101 or the management server 102 connected to the management target apparatus via the management VLAN. By referring to the connection destination list 704, the packet communication apparatus 101 and the management server 102 connected to each packet communication apparatus 101 via the management VLAN can be known. In other words, by tracing the identifier set in the connection destination list 704, the tree structure of the connection of the packet communication apparatus 101 as shown in FIG. 1 can be clarified.

  The configuration definition information 705 is a column indicating the configuration definition to be input to the management target device.

  A setting 706 is a column indicating whether or not the setting to the management target device is completed.

  FIG. 8 is an explanatory diagram of the own server setting information 606 stored in the memory 608 of the management server 102 according to the embodiment of this invention.

  The own server setting information 606 stores setting information of the own management server 102 (that is, the management server 102 holding the own server setting information 606) itself. The own server setting information 606 includes an identifier 802, an IP address 803, a management VLAN-ID 804, an upper domain server identifier 805, an upper domain server IP address 806, and a management VLAN subnet 807. An identifier 802 indicates an identifier of the self management server 102. An IP address 803 indicates the IP address of the self management server 102. The management VLAN-ID 804 indicates an identifier of the management VLAN used by the self management server 102 for managing the packet communication apparatus 101. An upper domain server identifier 805 indicates an identifier of the management server 102 that manages the upper domain 103 of the domain 103 managed by the self management server 102. The upper domain server IP address 806 indicates the IP address of the management server 102 that manages the upper domain 103 of the domain 103 managed by the self management server 102. The management VLAN subnet 807 indicates the subnet of the management VLAN used for the self management server 102 to manage the packet communication apparatus 101.

  FIG. 9 is an explanatory diagram of the device information collection table 607 stored in the memory 608 of the management server 102 according to the embodiment of this invention.

  The device information collection table 607 is a table for collecting information on the lower domain 103. The device information collection table 607 includes a management VLAN ID 902, a management VLAN subnet 903, a device identifier 904, and a device IP address 905.

  The management VLAN ID 902 indicates the identifier of the management VLAN to which the domain 103 (that is, the domain 103 managed by the management server 102) belongs. The management VLAN subnet 903 indicates the subnet of the management VLAN to which the domain 103 belongs. The device identifier 904 is a column that stores the identifiers of the packet communication devices 101 included in the domain 103 and the lower domain 103. The device IP address 905 is a column that stores the IPs of the packet communication devices 101 included in the domain 103 and the lower domain 103.

  FIG. 10 is an explanatory diagram of information included in messages exchanged between the packet communication apparatus 101 and the management server 102 in the embodiment of the present invention.

  The adjacent advertisement message 1001 includes a message identifier 1021 and a self-node identifier 1022. In the adjacent advertisement message 1001, the local node means the packet communication apparatus 101 or the management server 102 that has transmitted the adjacent advertisement message 1001. The message identifier 1021 indicates that this message is the adjacent advertisement message 1001. The identifier 1022 of the own node is an identifier of the packet communication apparatus 101 or the management server 102 that has transmitted the adjacent advertisement message 1001.

  The neighbor discovery notification message 1002 includes a message identifier 1023, an own node identifier 1024, a port number 1025, and a discovered node identifier 1026. In the neighbor discovery notification message 1002, the local node means the packet communication apparatus 101 or the management server 102 that has transmitted the neighbor discovery notification message 1002. The message identifier 1023 indicates that this message is the neighbor discovery notification message 1002. The local node identifier 1024 is an identifier of the packet communication apparatus 101 or the management server 102 that has transmitted the neighbor discovery notification message 1002. The port number 1025 is the number of the port that has received the adjacent advertisement message 1001 among the ports of its own node. The discovered node identifier 1026 is an identifier of the discovered packet communication apparatus 101 or management server 102. That is, the value of the identifier 1022 of the own node included in the received adjacent advertisement message 1001 is set in the identifier 1026 of the discovered node.

  The management VLAN / IP setting message 1003 is used to set the management VLAN and IP address of the management server 102 and the packet communication apparatus 101. The management VLAN / IP setting message 1003 includes a message identifier 1027, a setting destination device identifier 1028, a port number 1029, a management VLAN ID 1030, an IP address 1031 and a subnet 1032. The message identifier 1027 indicates that this message is the management VLAN / IP setting message 1003. The setting destination device identifier 1028 is an identifier of a device (that is, the management server 102 or the packet communication device 101) set by this message. The port number 1029 is the port number of the device set by this message. The management VLAN ID 1030 is a VLAN identifier used for managing the device set by this message. The IP address 1031 and the subnet 1032 are the IP address and subnet set in the device set by this message.

  The management information setting message 1004 is transmitted when the correspondence relationship between the management server 102 and the packet communication apparatus 101 managed by the management server 102 is changed due to a change in the domain configuration. Specifically, the management server 102 that manages the packet communication apparatus 101 sends information necessary for managing the packet communication apparatus 101 to the management server 102 that will manage the packet communication apparatus 101 in the future. It is included in the management information setting message 1004 and transmitted.

  The management information setting message 1004 includes a message identifier 1033, a type 1034, an IP address 1035, an identifier 1036, a connection destination list 1037, and configuration definition information 1038. A message identifier 1033 indicates that this message is a management information setting message 1004. The type 1034, IP address 1035, identifier 1036, connection destination list 1037, and configuration definition information 1038 correspond to the type 701, IP address 702, identifier 703, connection destination list 704, and configuration definition information 705 of the management target device table 605, respectively. To do. The management server 102 transmits, as a management information setting message 1004, information related to a device to be managed by another management server 102 from among the information held in the management target device table 605 of the self management server 102. .

  The management server change message 1005 includes a message identifier 1039, a new management server identifier 1040, and an IP address 1041. The message identifier 1039 indicates that this message is the management server change message 1005. The management server change message 1005 changes when the management server 102 that manages the packet communication apparatus 101 is changed (in other words, when the packet communication apparatus 101 is transferred from the management of one management server 102 to the management of another management server). Is transmitted from the management server 102 to the packet communication apparatus 101. In the new management server identifier 1040 and the IP address 1041, the identifier and IP address of the management server 102 that newly manages the packet communication apparatus 101 are set, respectively.

  The management server change response message 1006 includes a message identifier 1042, a new management server identifier 1043, and an IP address 1044. The message identifier 1042 indicates that this message is the management server change response message 1006. As will be described later (see FIG. 11), when the packet communication apparatus 101 receives the management server change message 1005, the packet communication apparatus 101 sends a management server change response message 1006 to the management server change message 1005 to notify that the message has been received. To the sender of In this case, the new management server identifier 1043 and the IP address 1044 are set to the same values as the new management server identifier 1040 and the IP address 1041 of the received management server change message 1005.

  The management server stop message 1007 includes a message identifier 1045 and a stop management server identifier 1046. The message identifier 1045 indicates that this message is the management server stop message 1007. The stop management server identifier 1046 is an identifier of the management server 102 to be stopped.

  The device information collection message 1008 includes a message identifier 1047 indicating that this message is the device information collection message 1008.

  The device information collection response message 1009 includes a message identifier 1048, a management VLAN ID 1049, a subnet 1050, an IP address 1051, and an identifier 1052. The message identifier 1048 indicates that this message is a device information collection response message 1009. In the management VLAN ID 1049, the subnet 1050, the IP address 1051, and the identifier 1052, values of the management VLAN ID 902, the management VLAN subnet 903, the device IP address 905, and the device identifier 904 of the device information collection table 607 are set, respectively. As shown in FIG. 9, when the device information collection table 607 holds device IP addresses 905 and device identifiers 904 related to a plurality of packet communication devices 101, the device information collection response message 1009 includes a plurality of IP addresses 1051 and identifiers. 1052 is included.

  The separation request message 1010 includes a message identifier 1053 indicating that this message is the separation request message 1010.

  The separation request response message 1011 includes a message identifier 1054 indicating that this message is the separation request response message 1011.

  Although omitted in FIG. 10, each message includes a transmission source identifier and a destination identifier as lower layer header information.

  Hereinafter, operations when the packet communication apparatus 101 and the management server 102 receive the messages illustrated in FIG. 10 will be described.

  FIG. 11 is a flowchart illustrating a procedure of processing executed by the packet communication apparatus 101 according to the embodiment of this invention.

  In the following description, the process executed by the packet communication apparatus 101 is executed by the control unit 302 of the packet communication apparatus 101 in more detail.

  When the apparatus is started and the initial setting is completed, the process proceeds to step 1101.

  In step 1101, the packet communication apparatus 101 waits until an external message arrives. Hereinafter, the process branches depending on the type of the received message. The message type is determined based on the message identifier 1021 or the like.

  In step 1102, the packet communication apparatus 101 determines whether or not the received message is the adjacent advertisement message 1001. If it is determined that the received message is the adjacent advertisement message 1001, the process proceeds to step 1103. If it is determined that the received message is not the adjacent advertisement message 1001, the process proceeds to step 1104.

  Step 1103 is a process executed by the packet communication apparatus 101 to process the received adjacent advertisement message 1001. In step 1103, the packet communication apparatus 101 transmits a neighbor discovery notification message 1002 to the responsible management server 102. The responsible management server 102 is the management server 102 that manages the packet communication apparatus 101 that has received the adjacent advertisement message 1001.

  In the neighbor discovery notification message 1002 transmitted in step 1103, the identifier 1024 of the own node is the identifier of the packet communication apparatus 101 that has received the neighbor advertisement message 1001. The port number 1025 is the number of the port that has received the adjacent advertisement message 1001. The discovered node identifier 1026 is an identifier of the management server 102 that transmitted the adjacent advertisement message 1001, that is, an identifier indicated by the own node identifier 1022 of the received adjacent advertisement message 1001.

  Thus, the process of receiving the adjacent advertisement message 1001 ends, and the process returns to step 1101.

  In step 1104, the packet communication apparatus 101 determines whether or not the received message is a management VLAN / IP setting message 1003. If it is determined that the received message is the management VLAN / IP setting message 1003, the process proceeds to step 1105. If it is determined that the received message is not the management VLAN / IP setting message 1003, the process proceeds to step 1107.

  Steps 1105 to 1106 are processes executed by the packet communication apparatus 101 in order to process the received management VLAN / IP setting message 1003. In step 1105, the packet communication apparatus 101 determines that the setting destination apparatus identifier 1028 included in the received message is equal to the identifier of the own packet communication apparatus 101 and the transmission source identifier (not shown) included in the received message. It is determined whether it is equal to the identifier of the charge management server 102.

  In step 1005, it is determined that the setting destination device identifier 1028 included in the received message is equal to the identifier of the own packet communication device 101, and the transmission source identifier included in the received message is equal to the identifier of the responsible management server 102 If so, the process proceeds to Step 1106.

  On the other hand, when the setting destination device identifier 1028 included in the received message is different from the identifier of the own packet communication device 101, the received message is not for setting the own packet communication device 101. Further, when the transmission source identifier included in the received message is different from the identifier of the responsible management server 102, the received message is not transmitted from the responsible management server 102 of the own packet communication apparatus 101. Management servers other than the responsible management server 102 cannot set the own packet communication device 101. Therefore, in such a case, step 1106 is not executed, and the process returns to step 1101.

  In step 1106, the packet communication apparatus 101 sets a port according to the port number 1029 and the management VLAN ID 1030 included in the message. Specifically, the packet communication apparatus 101 sets the management VLAN ID 1030 included in the received message to the management VLAN ID 504 of the apparatus setting information 307.

  Thus, the processing of the management VLAN / IP setting message 1003 ends, and the process returns to step 1101.

  In step 1107, the packet communication apparatus 101 determines whether the received message is a management server change message 1005. If it is determined that the received message is a management server change message, the process proceeds to step 1108. If it is determined that the received message is not the management server change message 1005, the process returns to step 1101.

  Steps 1108 to 1110 are processes executed by the packet communication apparatus 101 in order to process the received management server change message 1005. In step 1108, the packet communication apparatus 101 determines whether or not the transmission source identifier included in the received message is equal to the identifier of the management server 102 in charge of the own packet communication apparatus 101. If it is determined that the transmission source identifier included in the received message is equal to the identifier of the responsible management server 102 of the own packet communication apparatus 101, the process proceeds to step 1109. On the other hand, when it is determined that the transmission source identifier included in the received message is different from the identifier of the management server 102 in charge of the own packet communication device 101, the management server 102 that transmitted the message may set the own packet communication device 101. Can not. For this reason, steps 1109 to 1110 are not executed, and the process returns to step 1101.

  In step 1109, the packet communication apparatus 101 returns the management server change response message 1006 to the transmission source, and copies the received message information as it is and returns it to the transmission source. That is, the new management server identifier 1043 and the IP address 1044 of the management server change response message 1006 transmitted in step 1109 are the same as the new management server identifier 1040 and the IP address 1041 of the received management server change message 1005, respectively.

  Next, in step 1110, the packet communication apparatus 101 sets a management server identifier and an IP address according to information included in the message. Specifically, the packet communication apparatus 101 uses the values of the new management server identifier 1040 and the IP address 1041 of the received management server change message 1005 as the management server identifier 401 and the management server IP of the management server information 308, respectively. Set to address 402.

  If the packet communication apparatus 101 receives a message other than the above, the packet communication apparatus 101 ignores the received message and returns to step 1101.

  Next, processing on the management server 102 side will be described. Here, the description is divided into three flowcharts (FIGS. 12 to 14) in relation to the area of the drawing, but basically, the point where processing proceeds after branching according to the received message is that the packet communication apparatus This is the same as the processing of 101.

  FIG. 12 is a first flowchart illustrating processing executed by the management server 102 according to the embodiment of this invention.

  When the management server 102 is activated and connected to the adjacent packet communication apparatus 101, the management server 102 transmits the adjacent advertisement message 1001 in step 1201. The identifier 1022 of the own node of the adjacent advertisement message 1001 transmitted here is the identifier of the own management server 102.

  Next, in step 1202, the management server 102 waits for reception of a message. Thereafter, the process branches according to the type of the received message.

  In step 1203, the management server 102 determines whether or not the received message is a neighbor discovery notification message 1002. If it is determined that the received message is the neighbor discovery notification message 1002, the process proceeds to step 1204. If it is determined that the received message is not the neighbor discovery notification message 1002, the process proceeds to step 1301 in FIG.

  Steps 1204 to 1212 are processes executed by the management server 102 in order to process the received neighbor discovery notification message 1002.

  In step 1204, the management server 102 searches the managed device table 605 using the discovered node identifier 1026 included in the received message as a key.

  Next, in step 1205, the management server 102 determines whether there is an entry that matches the search condition in step 1204, the entry type 701 is a server, and the entry setting 706 is not set. Determine whether or not. If it is determined that there is an entry that matches the condition of step 1204, the type 701 is a server, and the setting 706 is not set, the discovered node is the management server 102 that has not been set. In this case, the process proceeds to step 1206.

  On the other hand, if there is no entry that matches the condition in step 1204, the type 701 is not a server, or the setting 706 is not set, the processing is terminated.

  In step 1206, the management server 102 transmits a management VLAN / IP setting message 1003 to the transmission source of the received neighbor discovery notification message 1002. The management VLAN / IP setting message 1003 transmitted in step 1206 includes the same value as the port number 1025 of the received neighbor discovery notification message 1002 as the port number 1029. Further, the management VLAN / IP setting message 1003 includes the same value as the management VLAN ID 902 of the device information collection table 607 of the self management server 102 as the management VLAN ID 1030.

  Next, in step 1207, the management server 102 transmits a management VLAN / IP setting message 1003 to the discovered new management server 102. The management VLAN / IP setting message 1003 transmitted in step 1207 includes the same value as the IP address 702 of the entry that matches the condition of step 1204 as the IP address 1031. Further, the management VLAN / IP setting message 1003 includes the same values as the management VLAN ID 902 and the subnet 903 of the device information collection table 607 of the own management server 102 as the management VLAN ID 1030 and the subnet 1032, respectively.

  Next, processing for changing the management server 102 is executed. In step 1208, the management server 102 extracts a partial tree having the packet communication device 101 that is the transmission source of the neighbor discovery notification message 1002 as the root of the tree. For example, if the transmission source of the neighbor discovery notification message 1002 is the packet communication device 101-4 in FIG. 1, in step 1208, a subtree consisting of the packet communication devices 101-4, 101-7, and 101-8 is extracted. . In this subtree, the route is the packet communication device 101-4. The extraction of the partial tree is executed by following the identifier set in the connection destination list 704.

  In step 1209, the management server 102 includes a management information setting message including information on entries corresponding to the packet communication device 101 and the management server 102 included in the extracted subtree among the entries of the management target device table 605. 1004 is created.

  In step 1210, the management server 102 transmits the created management information setting message 1004 to the new management server 102. Thereafter, the management server 102 deletes the entry included in the transmitted management information setting message 1004 from the management target device table 605.

  Next, in Step 1211 and Step 1212, the management server 102 transmits a management server change message 1005 to all devices (that is, the packet communication device 101 and the management server 102) included in the extracted subtree. The identifier and IP address of the new management server 102 are set in the new management server identifier 1040 and the IP address 1041 of the management server change message 1005 transmitted here.

  Thus, the process of the neighbor discovery notification message 1002 ends, and the process returns to step 1202.

  FIG. 13 is a second flowchart illustrating processing executed by the management server 102 according to the embodiment of this invention.

  In the flowchart shown in FIG. 13, a message not processed in FIG. 12 is processed.

  In step 1301, the management server 102 determines whether or not the received message is a management VLAN / IP setting message 1003. If it is determined that the received message is the management VLAN / IP setting message 1003, the process proceeds to step 1302. If it is determined that the received message is not the management VLAN / IP setting message 1003, the process proceeds to step 1303.

  Step 1302 is executed to process the management VLAN / IP setup message 1003. In step 1302, the management server 102 sets the network I / F of the own management server 102 according to the management VLAN ID 1030, the IP address 1031 and the subnet 1032 included in the received message. Specifically, the management server 102 sets the management VLAN ID 1030, the IP address 1031 and the subnet 1032 included in the received message in the management VLAN ID 804, the device IP address 803 and the management VLAN subnet 807 of the own server setting information 606, respectively. .

  Thus, the processing of the management VLAN / IP setting message 1003 is completed, and the processing returns to step 1202 in FIG.

  In step 1303, the management server 102 determines whether or not the received message is a management information setting message 1004. If it is determined that the received message is the management information setting message 1004, the process proceeds to step 1304. If it is determined that the received message is not the management information setting message 1004, the process proceeds to step 1305.

  Step 1304 is executed to process the management information setting message 1004. In step 1304, the management server 102 adds the content of the received message to the management target device table 605 and completes the message processing. Specifically, the management server 102 stores the type 1034, the IP address 1035, the identifier 1036, the connection destination list 1037, and the configuration definition information 1038 of the received management information setting message 1004 in the type 701 of the management target device table 605, respectively. The IP address 702, the identifier 703, the connection destination list 704, and the configuration definition information 705 are set. Then, the process returns to step 1202 of FIG.

  In step 1305, the management server 102 determines whether or not the received message is a management server change message 1005. If it is determined that the received message is the management server change message 1005, the process proceeds to step 1306. If it is determined that the received message is not the management server change message 1005, the process proceeds to step 1309.

  Steps 1306 to 1308 are executed to process the management server change message 1005. In step 1306, the management server 102 determines whether or not the source identifier of the received message is the same as the identifier of the higher management server 102 (that is, the higher domain server identifier 805). If it is determined that these identifiers are the same, the process proceeds to step 1307. If it is determined that these identifiers are different, the management server 102 ignores the received message, and the process returns to step 1202 in FIG.

  Here, the upper management server 102 is the management server 102 that manages the packet communication apparatus 101 that is one level higher than the packet communication apparatus 101 connected to the own management server 102. For example, in FIG. 1, the upper management server 102 of the self management server 102-2 is the management server 102-1.

  In step 1307, the management server 102 transmits a management server change response message 1006 to the upper management server 102.

  Next, in step 1308, the management server 102 updates the information of the upper management server 102 held by the management server 102 to the new management server identifier 1040 and the IP address 1041 included in the received management server change message 1005. Specifically, the management server 102 sets the values of the new management server identifier 1040 and the IP address 1041 in the upper domain server identifier 805 and the upper domain server IP address 806 of the own server setting information 606, respectively.

  Thus, the processing of the management server change message 1005 ends. Then, the process returns to step 1202 of FIG.

  In step 1309, the management server 102 determines whether or not the received message is a management server change response message 1006. If it is determined that the received message is the management server change response message 1006, the process proceeds to step 1310. If it is determined that the received message is not a management server change response message, the process proceeds to step 1313.

  In steps 1310 to 1312, the management server change response message 1006 is processed. In step 1310, the management server 102 searches the management target device table 605 using the transmission source identifier as a key. If there is an entry having the same identifier 703 as the transmission source identifier, the entry is deleted from the managed device table 605 (steps 1311 and 1312). Then, the process returns to step 1202 of FIG.

  In step 1313, the management server 102 determines whether or not the received message is a management server stop message 1007. If it is determined that the received message is the management server stop message 1007, the process proceeds to step 1314. If it is determined that the received message is not the management server stop message 1007, the process proceeds to step 1301 in FIG.

  In steps 1314 to 1315, the management server stop message 1007 is processed. In step 1314, the management server 102 creates all the contents of the management target device table 605 as a management information setting message 1004. In step 1315, the management server 102 transmits the created management information setting message 1004 to the upper management server 102. Thus, the management server 102 ends the process.

  FIG. 14 is a third flowchart illustrating processing executed by the management server 102 according to the embodiment of this invention.

  In the flowchart shown in FIG. 14, messages that are not processed in FIGS. 12 and 13 are processed.

  In step 1401, the management server 102 determines whether or not the received message is a device information collection message 1008. If it is determined that the received message is the device information collection message 1008, the process proceeds to step 1402. If it is determined that the received message is not the device information collection message 1008, the process proceeds to step 1408.

  In steps 1402 to 1407, the device information collection message 1008 is processed. First, in step 1402, the management server 102 empties the device information collection table 607. This is because the management server 102 collects information related to the packet communication apparatus 101 under the management of the self management server 102 and information related to the packet communication apparatus 101 under the management of the management server 102 lower than the self management server 102. Because.

  The management server 102 lower than the own management server 102 means the management server 102 that manages the packet communication apparatus 101 lower than the packet communication apparatus 101 under the management of the own management server 102. For example, in FIG. 1, the management servers 102-2 and 102-3 are lower management servers 102 than the management server 102-1.

  In steps 1403 and 1404, the management server 102 searches the managed device table 605 for an entry whose type 701 is “server” (for example, “lower domain management server” shown in FIG. 7). The device information collection message 1008 is transmitted to the management server 102 indicated by each entry. Thereby, it is possible to instruct recursively the collection of device information managed by the management server 102 of the lower domain 103.

  Next, in step 1405, the management server 102 waits for the device information collection response message 1009 to be transmitted from all lower management servers 102.

  The device information collection response message 1009 is processed in steps 1408 to 1409 (described later).

  When the device information collection response message 1009 arrives from the management servers 102 of all lower domains 103, the management server 102 receives the device information collection response including the contents of the device information collection table 607 held by the self management server 102 in step 1406. A message 1009 is created. The management VLAN ID 1049, the subnet 1050, the IP address 1051, and the identifier 1052 of the device information collection response message 1009 include the management VLAN ID 902, the management VLAN subnet 903, the device identifier 904, and the management VLAN ID 902 of the device information collection table 607 held by the self management server 102, respectively. A device IP address 905 is set.

  In step 1407, the management server 102 responds the created device information collection response message 1009 to the transmission source of the device information collection message 1008. Thus, the processing of the device information collection message 1008 is completed, and the processing returns to step 1202 in FIG.

  In step 1408, the management server 102 determines whether or not the received message is a device information collection response message 1009. If it is determined that the received message is the device information collection response message 1009, the process proceeds to step 1409. If it is determined that the received message is not the device information collection response message 1009, the process proceeds to step 1410.

  In order to process the device information collection response message 1009, in step 1409, the management server 102 adds the content of the received device information collection response message 1009 to the device information collection table 607. Thus, the processing of the device information collection response message 1009 is completed, and the processing returns to step 1202 in FIG.

  In step 1410, the management server 102 determines whether the received message is a separation request message 1010 or a separation request response message 1011. If it is determined that the received message is the separation request message 1010 or the separation request response message 1011, the process proceeds to step 1411. If it is determined that the received message is neither the separation request message 1010 nor the separation request response message 1011, the process returns to step 1202 in FIG. 12.

  When receiving the separation request message 1010 (step 1411), the management server 102 transmits a separation request response message 1011 to the transmission source of the separation request message 1010 in step 1412.

  In step 1413, the management server 102 determines whether or not the transmission source identifier of the received separation request message 1010 or separation request response message 1011 is equal to the higher domain server identifier 805 of the own management server 102. If it is determined that these identifiers are equal, the process proceeds to step 1414. If it is determined that these identifiers are different, the process proceeds to step 1415.

  In step 1414, the management server 102 on the child domain 103 side updates the upper domain server identifier 805 and the upper domain server IP address 806 to null. Then, the process returns to step 1202 of FIG.

  In step 1415, the management server 102 on the parent domain 103 side searches the management target device table 605 using the transmission source identifier as a key.

  In step 1416 and step 1417, the management server 102 on the parent domain 103 side deletes the searched entry (that is, the entry whose identifier 703 is equal to the transmission source identifier). Thus, the processing of the separation request message 1010 and the separation request response message 1011 is completed, and the processing returns to Step 1202 in FIG.

  When the management server 102 receives a message other than the above, it simply ignores it and returns to step 1202 in FIG.

  Hereinafter, a typical sequence is shown for each operation shown in FIGS. 2A to 2D.

  FIG. 15 is an explanatory diagram of a network configuration referred to for explaining a typical sequence according to the embodiment of this invention.

  In FIG. 15, the packet communication device 2 (101-12) is connected to the lower level of the packet communication device 1 (101-11), and the packet communication device 3 (101-13) is connected to the lower level of the packet communication device 2 (101-12). Is connected. A management server 1 (102-11) and a management server 2 (102-12) are connected to the packet communication device 1 (101-11) and the packet communication device 2 (101-12), respectively. The packet communication device 1 (101-11) is the route of the upper domain 103-11. The packet communication device 2 (101-12) is the route of the lower domain 103-12. The upper domain 103-11 is a parent domain of the lower domain 103-12. The administrator 1506 can operate the management server 1 (102-11) and the management server 2 (102-12).

  FIG. 16 is a typical sequence diagram when domain division is executed in the embodiment of the present invention.

  The network configuration at the time when the processing shown in FIG. 16 is started is as shown in FIG. 15 except that the management server 2 (102-12) is not connected to the packet communication apparatus 2 (101-12). . At this point, the packet communication apparatuses 1 (101-11) to 3 (101-13) belong to a single domain 103.

  First, the administrator 1506 designates the identifier and IP address of the management server 2 (102-12) (1617).

  Next, the administrator 1506 connects the management server 2 (102-12) to the packet communication apparatus 2 (101-12) (1608).

  Next, the management server 2 (102-12) transmits the adjacent advertisement message 1001 to the packet communication apparatus 2 (101-12) (1609).

  Next, the packet communication device 2 (101-12) transmits an adjacent discovery notification message 1002 to the management server 1 (102-11) (1610). The processing executed by the packet communication device 2 (101-12) at this time is described in detail in step 1103 in FIG.

  The management server 1 (102-11) that has received the neighbor discovery notification message 1002 recognizes the position to which the management server 2 (102-12) is connected (that is, the packet communication device 2 (101-12)). Then, the management server 1 (102-11) determines that a new domain 103-12 having the packet communication device 2 (101-12) connected to the management server 2 (102-12) as a root is created. . Then, the management server 1 (102-11) transmits a management VLAN / IP setting message 1003 to the packet communication apparatus 2 (101-12) (1611). This transmission corresponds to step 1206 in FIG. As a result, layer 2 (L2) connectivity between the packet communication device 2 (101-12) and the management server 2 (102-12) is established (1612). The processing executed by the packet communication device 2 (101-12) at this time corresponds to steps 1105 to 1106 in FIG.

  Next, the management server 1 (102-11) transmits a management VLAN / IP setting message 1003 to the management server 2 (102-12) (1613). This transmission corresponds to step 1207 in FIG. As a result, an IP address is assigned to the management server 2 (102-12), and layer 3 (L3) connectivity between the management server 1 (102-11) and the management server 2 (102-12) is established. The processing executed by the management server 2 (102-12) at this time corresponds to step 1302 in FIG.

  Next, the management server 1 (102-11) transmits a management information setting message 1004 to the management server 2 (102-12) (1615). This transmission corresponds to step 1210 in FIG. Thereby, the information of the packet communication apparatus 101 that will be under the management of the management server 2 (102-12) is transferred to the management server 2 (102-12).

  Next, the management server 1 (102-11) transmits a management server change message 1005 to the packet communication device 2 (101-12) and the packet communication device 3 (101-13) (1616, 1617). These transmissions correspond to step 1212 in FIG. In response to these, the packet communication device 2 (101-12) and the packet communication device 3 (101-13) transmit a management server change response message 1006 to the management server 1 (102-11) (1618, 1619). These transmissions correspond to step 1109 in FIG.

  Finally, the management server 1 (102-11) deletes the information of the packet communication devices 2 (101-12) and 3 (101-13) from the management target device table 605 (1614). This deletion corresponds to step 1312 in FIG. This completes the domain division.

  As described above, when the management server 2 (102-12) is newly connected to the packet communication device 2 (101-12), two original domains 103 to which the packet communication device 2 (101-12) belongs are two. It is divided into. That is, the subtree having the root of the packet communication apparatus 2 (101-12) to which the management server 2 (102-12) is newly connected is one of the divided domains 103-12, and the remaining subtrees are The other domain 103-11.

  The management server 1 (102-11) that has managed the original domain 103 stores information used to manage the packet communication device 101 belonging to the subtree having the packet communication device 2 (101-12) as a root. To the management server 2 (102-12). Based on the information, the newly connected management server 2 (102-12) can manage one of the divided domains 103-12.

  FIG. 17 is a typical sequence diagram when domain absorption is performed in the embodiment of the present invention.

  The network configuration at the time when the processing shown in FIG. 17 is started is as shown in FIG.

  First, the administrator 1506 instructs the management server 1 (102-11) to stop the management server 2 (102-12) (1707).

  In response to this instruction, the management server 1 (102-11) transmits a management server stop message 1007 to the management server 2 (102-12) (1708).

  The management server 2 (102-12) creates a management information setting message 1004 based on the management target device table 605 (1709), and transmits the created management information setting message 1004 to the management server 1 (102-11). (1710). These creation and transmission correspond to steps 1314 and 1315 in FIG.

  The management server 1 (102-11) adds the information included in the received management information setting message 1004 to the management target device table 605 (1711). This addition corresponds to step 1304 in FIG.

  Next, the management server 2 (102-12) transmits a management server change message 1005 to the packet communication apparatus 2 (101-12) (1712). In response to this, the packet communication apparatus 2 (101-12) returns the management server change response message 1006 to the management server 2 (102-12) (1713), and then changes the responsible management server 102 to the management server 2 (102). -12) to management server 1 (102-11). This reply and change correspond to steps 1307 and 1308 in FIG.

  Similarly, the management server 2 (102-12) transmits a management server change message 1005 to the packet communication device 3 (101-13) (1714). In response to this, the packet communication apparatus 3 (101-13) returns a management server change response message 1006 to the management server 2 (102-12) (1715), and changes the responsible management server 102. This reply and change correspond to steps 1307 and 1308 in FIG.

  Finally, the management server 2 (102-12) executes server stop processing (1716). This completes domain absorption.

  As described above, the management server 2 (102-12) that manages the lower domain 103-12 receives the information used for managing the lower domain 103-12 as the upper domain 103-11 before stopping. It transmits to the management server 1 (102-11) to manage. Based on the transmitted information, the management server 1 (102-11) can manage the packet communication device 101 belonging to the lower domain 103-12 after the management server 2 (102-12) is stopped. .

  FIG. 18 is a typical sequence diagram in the case where domain binding is executed in the embodiment of the present invention.

  The network configuration at the time when the processing shown in FIG. 18 is started is as shown in FIG. 15 except that the packet communication device 1 (101-11) and the packet communication device 2 (101-12) are not connected. is there.

  At this time, the management server 1 (102-11) and the management server 2 (102-12) each independently manage the device information collection table 607. That is, for example, different management VLAN IDs 902 may be set for the management VLAN to which the management server 1 (102-11) is connected and the management VLAN to which the management server 2 (102-12) is connected. . In this case, before joining the domain 103, it is necessary to make these management VLAN IDs 902 the same. Similarly, even if the subnets 903 are different, they need to be the same.

  Further, there is a possibility that the same device IP address 905 is given to two packet communication devices 101 belonging to different domains 103 respectively. The identifier of each device needs to be unique within one domain 103. Therefore, as long as the two domains 103-11 and 103-12 are completely independent, duplication of identifiers as described above is not a problem. However, before combining these two domains 103, it is necessary to ensure the uniqueness of the identifier by eliminating the duplication of the identifier.

  First, the administrator 1506 transmits a device information collection message 1008 to the management server 2 (102-12) (1807). Specifically, for example, the administrator 1506 may input a command corresponding to the device information collection message 1008 to the management server 2 (102-12).

  The management server 2 (102-12) retrieves information related to the packet communication device 2 (101-12) from the managed device table 605 held by itself, and transmits a device information collection response message 1009 including the information to the administrator 1506. (1808). This transmission corresponds to step 1407 in FIG. In the example of FIG. 15, the network to which the management server 1 (102-11) belongs has no subdomain. For this reason, in the example of FIG. 18, recursive information collection shown in steps 1403 to 1405 of FIG. 14 is not performed.

  Next, the administrator 1506 causes the file conversion function unit (not shown) of the management server 1 (102-11) to read the device information collection response message 1009 transmitted from the management server 2 (102-12). (1809). At this point, the management server 1 (102-11) is not connected to the management server 2 (102-12). For this reason, the process of step 1809 needs to be performed manually by the administrator 1506. For example, in step 1808, the management server 2 (102-12) may store the device information collection response message 1009 in a data storage medium (not shown). In step 1809, the administrator 1506 may cause the management server 1 (102-11) to read the data storage medium storing the device information collection response message 1009.

  The file conversion function unit in the management server 1 (102-11) changes the management VLAN ID 1049, the IP address 1051, and the subnet 1050 included in the read data (1810). Specifically, for example, the management VLAN ID 1049 and the subnet 1050 included in the read data are changed to the same values as the management VLAN ID 902 and the management VLAN subnet 903 held by the management server 1 (102-11), respectively. On the other hand, the IP address 1051 included in the read data is changed to a value that does not overlap with the device IP address 905 held by the management server 1 (102-11).

  Next, the management server 1 (102-11) writes out information related to the converted child domain 103-12, and transmits the information to the administrator 1506 (1811).

  The administrator 1506 causes the management server 2 (102-12) to read information related to the child domain 103-12 (1812). Steps 1811 and 1812 may be performed in the same manner as steps 1808 and 1809.

  The management server 2 (102-12) changes the management VLAN ID 902, the device IP address 905, and the management VLAN subnet 903 of the device information collection table 607 held by the self management server 2 (102-12) according to the read information (1813). ). As a result, the management VLAN ID 1049, the IP address 1051, and the subnet 1050 values changed in Step 1810 are the management VLAN ID 902, the device IP address 905, and the management VLAN subnet in the device information collection table 607 held by the management server 2 (102-12). 903 is set.

  Finally, the management server 2 (102-12) transmits a management VLAN / IP setting message 1003 to the packet communication apparatus 2 (101-12) (1814). By this operation, the IP address changing process for domain combination is completed. Thereafter, the administrator 1506 executes an operation of connecting the packet communication device 1 (101-11) and the packet communication device 2 (101-12) to each management server 102. This completes the domain binding.

  As described above, the management server 1 (102-11) of the upper domain 103-11 receives the identification information used for managing the lower domain 103-12 from the management server 2 (102-12) of the lower domain 103-12. To get. And the management server 1 (102-11) changes the acquired identification information so that the identification information used for management of the high-order domain 103-11 may not overlap. The management server 2 (102-12) manages the lower domain 103-12 using the changed identification information. After the duplication of the identification information in the two domains 103 is eliminated in this way, the domains 103 are combined.

  FIG. 19 is a typical sequence diagram when domain separation is executed in the embodiment of the present invention.

  The network configuration at the time when the process shown in FIG. 19 is started is as shown in FIG.

  First, the administrator 1506 instructs the management server 1 (102-11) to separate domains (1907).

  Next, the management server 1 (102-11) transmits a separation request message 1010 to the management server 2 (102-12) (1908). In response to this, the management server 2 (102-12) transmits a separation request response message 1011 to the management server 1 (102-11) (1909). Further, the management server 2 (102-12) deletes the information of the higher management server (that is, the higher domain server identifier 805 and the higher domain server IP address 806 in the own server setting information 606) (1910).

  Finally, the management server 1 (102-11) deletes the information of the management server 2 (102-12) (1911). This completes domain separation.

  According to the above embodiment of the present invention, when the configuration of the management domain 103 of the packet communication device 101 is changed, the management server 102 and the packet communication device 101 automatically exchange information necessary for the change. Run it. As a result, man-hours related to the domain configuration change are reduced, so that the operation cost of the packet communication system can be reduced.

It is explanatory drawing of the structural example of the network which embodiment of this invention makes object. It is explanatory drawing of the domain division | segmentation in embodiment of this invention. It is explanatory drawing of domain absorption in embodiment of this invention. It is explanatory drawing of the domain coupling | bonding in embodiment of this invention. It is explanatory drawing of the domain isolation | separation in embodiment of this invention. It is a block diagram which shows the structure of the packet communication apparatus which is the management object by the network management system of embodiment of this invention. It is explanatory drawing which shows the content of the charge management server information stored in the memory of the packet communication apparatus of embodiment of this invention. It is explanatory drawing which shows the content of the apparatus setting information stored in the memory of the packet communication apparatus of embodiment of this invention. It is a block diagram which shows the structure of the management server of embodiment of this invention. It is explanatory drawing of the management object apparatus table stored in the memory of the management server of embodiment of this invention. It is explanatory drawing of the own server setting information stored in the memory of the management server of embodiment of this invention. It is explanatory drawing of the apparatus information collection table stored in the memory of the management server of embodiment of this invention. It is explanatory drawing of the information contained in the message exchanged between a packet communication apparatus and the management server in embodiment of this invention. It is a flowchart which shows the procedure of the process which the packet communication apparatus of embodiment of this invention performs. It is a 1st flowchart which shows the process which the management server of embodiment of this invention performs. It is a 2nd flowchart which shows the process which the management server of embodiment of this invention performs. It is a 3rd flowchart which shows the process which the management server of embodiment of this invention performs. It is explanatory drawing of the network structure referred in order to demonstrate the typical sequence of embodiment of this invention. It is a typical sequence diagram in the case where domain division is executed in the embodiment of the present invention. It is a typical sequence diagram in case domain absorption is performed in embodiment of this invention. It is a typical sequence diagram in the case of performing domain coupling | bonding in embodiment of this invention. It is a typical sequence diagram in case domain separation is performed in embodiment of this invention.

Explanation of symbols

101 packet communication device 102 management server 103 domain 301 bus 302 control unit 303 memory 307 device setting information 308 responsible management server information 309 terminal I / F
310, 311, 312 Network I / F
317 Packet transfer processing unit 401 Management server identifier 402 Management server IP address 501 Device IP address 502 Device identifier 503 Device configuration definition 504 Management VLAN ID
602 User I / F unit 603 Network I / F unit 604 Control unit 605 Managed device table 606 Local server setting information 607 Device information collection table 608 Memory 701 Type 702 IP address 703 Identifier 704 Connection destination list 705 Configuration definition information 706 Setting 802 Identifier 803 IP address 804 Management VLAN-ID
805 Upper domain server identifier 806 Upper domain server IP address 902 Management VLAN ID
903 Management VLAN subnet 904 Device identifier 905 Device IP address

Claims (15)

A data communication system comprising a plurality of data communication devices and a plurality of management servers for managing the plurality of data communication devices,
Each of the management servers includes a first control unit, a user I / F unit, a first network I / F unit, and a first memory connected to each other by a first bus,
Each of the data communication devices includes a second control unit, a terminal I / F unit, a data transfer processing unit, a second network I / F unit, and a second memory connected to each other by a second bus,
The plurality of data communication devices are connected to each other by a tree-structured network,
The first data communication device is managed by the first management server;
The second management server that manages the second data communication device lower than the first data communication device in the network further includes a third data communication device lower than the second data communication device. A data communication system characterized by managing.   2. The data communication according to claim 1, wherein the second management server acquires management information of the second data communication device and the third data communication device from the first management server. system.   3. The management information of each data communication device includes at least an identifier of each data communication device and an identifier of a data communication device adjacent to each data communication device on the network. The data communication system described.   The second management server receives, from the first management server, an identifier of a third management server that manages the fourth data communication device that is lower than the second data communication device in the tree-structured network. The data communication system according to claim 2, wherein the data communication device is acquired and managed in a range not including the fourth data communication device. The second data communication device includes:
Holding an identifier of the second management server that manages the second data communication device in the second memory;
When a message indicating that the management server that manages the second data communication device is changed from the second management server to a management server other than the second management server is received, the message is held in the second memory. The data communication system according to claim 1, wherein the identifier is changed to an identifier of a management server other than the second management server.   2. The data communication according to claim 1, wherein the first management server acquires management information of the second data communication device and the third data communication device from the second management server. system.   When the second management server receives a request for acquiring management information of the data communication device from the first management server, the management information of the second data communication device and the third data communication device The data communication system according to claim 6, wherein the data is transmitted to the first management server.   When the second management server receives a request for acquiring management information of the data communication device from the first management server, the second management server sends a fourth data communication device lower than the third data communication device. The management information of the fourth data communication device is acquired from the third management server to be managed, and the acquired management information is transmitted to the first management server. Data communication system. A management server for managing one or more data communication devices in a data communication system including a plurality of data communication devices,
The management server includes a first control unit, a user I / F unit, a first network I / F unit, and a first memory connected to each other by a first bus,
Each of the data communication devices includes a second control unit, a terminal I / F unit, a data transfer processing unit, a second network I / F unit, and a second memory connected to each other by a second bus,
The plurality of data communication devices are connected to each other by a tree-structured network,
The management server that manages the first data communication device further manages the second data communication device that is lower than the first data communication device in the network.   The management server receives the first data communication device and the second data from a first other management server that manages the third data communication device higher than the first data communication device in the network. The management server according to claim 9, wherein management information of the communication device is acquired.   The management server obtains, from the first other management server, an identifier of a second other management server that manages the fourth data communication device lower than the first data communication device in the network. The management server according to claim 10, wherein the data communication device in a range not including the fourth data communication device is managed.   The management server acquires management information of the fourth data communication device from a second other management server that manages the fourth data communication device lower than the first data communication device. The management server according to claim 9.   When the management server receives a request for acquiring management information of the data communication device from a first other management server that manages the third data communication device that is higher than the first data communication device. The management server according to claim 12, wherein management information of the first data communication apparatus is transmitted to the first other management server.   When the management server receives a request for acquiring the management information of the data communication device from the first other management server, the management server receives the request for the fourth data communication device from the second other management server. The management server according to claim 13, wherein management information is acquired, and the acquired management information is transmitted to the first other management server. A data communication device,
The data communication device is connected to one or more other data communication devices by a tree-structured network,
The management server that manages the data communication device includes a first control unit, a user I / F unit, a first network I / F unit, and a first memory that are connected to each other by a first bus.
The data communication apparatus includes a second control unit, a terminal I / F unit, a data transfer processing unit, a second network I / F unit, and a second memory connected to each other by a second bus.
The management server connected to the data communication device manages the data communication device and one or more other data communication devices lower than the data communication device in the network,
The data communication device includes:
Holding the identifier of the management server that manages its own data communication device in the second memory;
When the message indicating that the management server that manages the data communication device is changed to another management server is received, the identifier held in the second memory is changed to the identifier of the other management server. Data communication device.