JP5147080B2 - VLAN path design method and apparatus - Google Patents

Description

  The present invention designs a VLAN path connecting a plurality of communication bases connected to a layer 2 network used in a wide area Ethernet (registered trademark) service or the like, particularly a layer 2 network partially completed in redundancy, The present invention relates to a technique for managing the route information.

  VLAN (Virtual LAN) is a technique for constructing a plurality of logical networks on an L2 network, which is a physical network configured by connecting layer 2 (hereinafter, L2) switches by communication cables. By using a VLAN, a broadcast domain is logically constructed on the L2 network, and two or more communication bases (hereinafter referred to as bases) of the same communication group connected to the L2 network can be handled as one broadcast domain. it can. Thereby, the L2 network can be efficiently used in a plurality of communication groups.

  VLAN has a concept of an access link that connects a base and an L2 switch, and a trunk link that connects between L2 switches. The access link is a path connecting the base and the L2 network, and the trunk link is a logical path for each communication group. In order to use the VLAN, it is necessary to design an access link for each base and a trunk link that connects all the bases, and to make settings in an L2 switch or an equivalent device.

  These route design / setting operations are performed for each communication group. It is necessary to consider the path in the form of a tree (having no loop), the number of remaining VIDs of the device and the trunk link, and further to consider the remaining bandwidth of the device and the trunk link when guaranteeing the bandwidth.

  Redundancy is required to construct an L2 network that is resistant to failures. Even if a failure occurs, communication can be maintained by bypassing the failed portion by redundancy. If a physically redundant structure is taken in the L2 network, a loop structure is formed, which circulates the frame and becomes a serious problem.

  For this problem, a loop is avoided by dynamically setting a logical tree structure on the physical structure. When a failure occurs, the failure can be avoided by automatically changing the logical structure. There are STP (Spanning Tree Protocol) and ERP (Ethernet (registered trademark) Ring Protection) as protocols for automatically realizing these. The STP constructs a mesh network and realizes redundancy by blocking some links so that no loop is generated on the network. ERP builds a ring network and realizes redundancy by blocking a part of the ring so that no loop occurs on the ring.

  There is MSTP (Multiple Spanning Tree Protocol) as a mechanism for simultaneously realizing redundancy (STP) on the VLAN. Setting up the VLAN path taking redundancy into account is complicated, but in MSTP, the path for each communication group has a one-to-one correspondence with the device. It was easy to design a route on that topology.

  FIG. 1 shows a conventional VLAN route design apparatus, which comprises a network configuration information storage unit 1, a device setting information storage unit 2, a base information storage unit 3, a route design unit 4, a device setting unit 5 and a control unit 6. ing.

  The control unit 6 instructs the route design unit 4 to design a route according to an instruction from the outside. The route design unit 4 uses the network configuration information, the device setting information, and the base information stored and held in the network configuration information storage unit 1, the device setting information storage unit 2, and the base information storage unit 3, respectively. Design configuration information. Further, the control unit 6 instructs the device setting unit 5 to set the device in order to make the new route effective in the actual network. The device setting unit 5 sets the device setting information designed by the route design unit 4 for an actual device. This makes the new route effective. The device setting unit 5 changes the actual device settings and updates the device setting information in the device setting information storage unit 2.

  Although the network configuration information, the device setting information, and the base information are statically stored in FIG. 1, an information collection unit that collects information from an actual network may be provided as necessary.

  The network configuration information is information that represents the configuration of the L2 network, and includes information relating to the available bandwidth for each device that constitutes the L2 network, the connection partner device, and the like. The device setting information is setting information for each device constituting the L2 network, and includes information related to the allocated bandwidth, VID, and the like for each communication group set for the device in units of devices. The base information is information related to the base connected to the L2 network, and includes information related to a communication group and a connection device for each base.

  When a base is newly established or deleted, or when a route is changed, route design by the route design unit 4 is required. The route design unit 4 derives a new route that connects a new base and an existing route (a route that connects existing bases) when creating a new base, and generates device setting information that reflects this route on the network. To do. If there is no existing route, a route that simply connects the bases is derived. When deleting a base, a route that is unnecessary due to the deletion of the base is derived, and device setting information that reflects this on the network is generated. Also, when it is desired to change a route connecting between bases for some reason, a route is derived in response to a request, and device setting information that reflects this route on the network is generated. In this way, a route that matches the request is derived, and device setting information that reflects this route in the actual network is generated (see, for example, Patent Document 1).

Japanese Patent No. 3938582

  In a relatively small network, redundancy and VLAN coexistence are possible for the entire L2 network by using the above-described technology such as MSTP. However, in a large-scale network, if the entire network is to be made redundant, the automatic switching time when a failure occurs increases in proportion to the size of the network. Also, some failures are likely to affect the entire network.

  In order to solve these problems, it is necessary to reduce the range of redundancy. For this reason, it is impossible to construct a large-scale L2 network that can be switched quickly when a failure occurs, simply by using a redundancy technique. This problem can be solved by providing complete redundancy for the small L2 network and interconnecting the small L2 networks for which redundancy has been completed. When ERP is used, one ring corresponds to a small L2 network in which one redundancy is completed.

  FIG. 2 shows an example of an L2 network that combines small L2 networks that have been fully redundant. Various combinations of L2 switches indicated by reference signs a to l, that is, L2 switches (a, b, c), (c, d, i), (d, e), (h, i, g, f), ( Local (partial) redundancy is achieved by a combination of d, j, k) and (b, h, l). When the network configuration of FIG. 2 is expressed by topology, it is as shown in FIG.

  Since redundancy has been achieved, for example, in a portion made redundant by the combination of L2 switches (a, b, c) (hereinafter referred to as a redundant domain) [A], even if a single failure occurs in the wiring between devices Communication is possible. In addition, the influence of path switching does not spread outside the redundant domain [A]. It should be noted that L2 switches (for example, b, c, d,...) That connect the redundant domains are greatly affected by a failure, and therefore it is better to multiplex them.

  As shown in FIG. 4, a base is added to the L2 network. Specifically, in order to connect the LANs 1 and 2 to the L2 switches a and f as bases and connect the two LANs by the VLAN, the following settings are required. There is.

  That is, since the frame passes through the redundant domains [a], [c] and [v] by the L2 switches (a, b, c), (c, d, i) and (h, i, g, f), It is necessary to set the L2 switches a, b, c, d, h, i, g, and f. The setting determines the VID used in each redundant domain [A], [C], and [E], and sets each L2 switch based on the VID. In the example of FIG. 4, it is assumed that the same VID number 1000 is used in redundant domains [A], [C] and [E].

  At this time, in the L2 switch a, the port 1 is set as the access port of the VID 1000, and the passage permission setting of the frame of the VID 1000 is performed on the redundant trunk ports of the ports 3 and 4. In the L2 switch b, the VID 1000 frame passage permission setting is performed on the redundant trunk ports of the ports 3 and 4. In the L2 switch c, the VID 1000 frame passing permission setting is performed on the redundant trunk ports of the ports 1, 2 and 3, 4, and the VID 1000 number between the ports 1, 2 and 3, 4 is set. Allows the passage of frames. When the L2 switch c has a function of converting the VID when the frame passes between the ports 1 and 2 and the ports 3 and 4, it is possible to allocate different VIDs in the redundant domains [A] and [C]. is there.

  As described above, on the L2 network where the redundancy is partially completed, the VLAN path connecting the bases is not determined only by the simple topology of the apparatus. When designing a route, it is necessary to design the route in consideration of partial redundancy. For this reason, it becomes a subject to give a big burden to the operator who determines a path | route.

  In actual route design, it is necessary to design a route in consideration of the number of remaining VIDs and the remaining bandwidth (link and device). On the L2 network where redundancy has been partially completed, the number of remaining VIDs and the remaining bandwidth are not determined only by the information of one device, but by the balance of all devices in the redundant range. For this reason, in the topology display of FIGS. 3 and 4, the burden on the operator who performs the route design becomes very large.

  The present invention provides a technology capable of easily performing VLAN path design and management of necessary information on an L2 network in which redundancy is partially completed.

  In the present invention, in order to solve the above-mentioned problem, the structure of the L2 network partially completed in redundancy is expressed as a graph using a redundant node representing a redundancy range and a device node representing a device. It is possible to display various information necessary for route setting. A route is designed manually or automatically on this graph, and a specific setting of the device is generated based on this information.

  According to the present invention, the structure of the L2 network that is partially redundant is expressed as a graph composed of device nodes and redundant nodes, and this graph is also provided with various information necessary for route setting. In addition, route design and information management considering partial redundancy become easy. In addition, by using this graph, it is possible to easily generate apparatus setting information automatically from an automatic route design by an algorithm or a graph.

Configuration diagram showing an example of a conventional VLAN path design apparatus An explanatory diagram showing an example of a layer 2 network in which redundancy is partially completed Explanatory drawing which shows an example of the topology of the layer 2 network of FIG. Explanatory drawing which shows an example of the topology of the layer 2 network at the time of adding a base The block diagram which shows an example of embodiment of the VLAN path | route design apparatus of this invention Explanatory drawing which shows an example of a layer 2 network Explanatory diagram showing an example of network configuration information Explanatory drawing which shows an example of apparatus setting information Explanatory diagram showing an example of site information Flow chart showing the procedure for generating the basic structure of a route design graph Explanatory drawing which shows an example of the basic structure of the graph for route design Flow chart showing generation procedure of remaining VID information Explanatory drawing which shows an example of remaining VID information Explanatory drawing which shows an example of the graph which showed the information for route design together Explanatory drawing which shows the example which added the base to the layer 2 network of FIG. Flow chart showing the procedure for adding a base node Explanatory drawing which shows an example of the graph which added the base node Explanatory drawing which shows an example of the graph which set the path | route of VLAN which connects between bases

  FIG. 5 shows an example of an embodiment of the VLAN route design apparatus of the present invention. The network configuration information storage unit 11, the device setting information storage unit 12, the base information storage unit 13, the graph generation unit 14, and the route design unit 15 are shown. The apparatus setting unit 16 and the control unit 17 are configured.

  The network configuration information storage unit 11 stores and holds network configuration information representing the configuration of the L2 network. The device setting information storage unit 12 stores and holds device setting information for individual devices constituting the L2 network. The base information storage unit 13 stores and holds base information related to bases connected to the L2 network.

  The graph generation unit 14 generates a route design graph to be presented to the operator based on the network configuration information, the device setting information, and the base information, that is, a redundant node representing a redundancy range and a device constituting the L2 network. A graph composed of a device node representing a redundant node and an edge connecting a redundant node and a device node belonging to the redundancy range, generating route design information, generating a base node representing the base, and generating the graph Add to

  The route design unit 15 sets a VLAN route connecting base nodes on the graph, and generates device setting information corresponding to the setting. The device setting unit 16 sets the device setting information for the device and updates the device setting information storage unit with the device setting information. The control unit 17 controls each unit described above.

  A feature of the VLAN route design method of the present invention is that the network structure is graphed in consideration of partial redundancy, and the route design is performed on the graph. The graph generation unit 14 generates a route design graph from the network configuration information, device setting information, and base information, and the route design unit 15 designs a route based on the graph.

  In order to explain the VLAN route design method of the present invention, an L2 network (topology display) as shown in FIG. 6 is assumed. Here, it is assumed that the L2 network is configured by connecting an L2 switch or a device equivalent thereto (hereinafter referred to as a device) with a communication cable such as an Ethernet (registered trademark) cable. Each device has (a, b, c), (c, d, i), (d, e), (h, i, g, f), (d, j, k) and (b, h, l). Local redundancy is achieved by the combination.

  FIG. 7 shows an example of network configuration information, here an example corresponding to the L2 network of FIG. 6. Various information for each device constituting the L2 network, that is, device ID, device bandwidth, port number, port bandwidth, It is composed of an access link flag, a partner device ID, a partner device port number, a link bandwidth, and a redundant domain ID (each area).

  An ID for identifying a device is recorded in the device ID area, and a maximum bandwidth that can be processed by the device is recorded in the device bandwidth area. In the port number area, a number for identifying each port of the apparatus is recorded, and in the port band area, the maximum band that can be processed by each port of the apparatus is recorded. The access link flag is a flag indicating whether the use for each port is for an access link or not (for a trunk link) (“1” for an access link, “0” for a trunk link). )) Is recorded.

  In the partner device ID area, the device ID of the partner device that configures the trunk link connected to the port that is used for the trunk link is recorded, and the partner device port number is a port that is used for the trunk link. The port number of the partner apparatus constituting the connected trunk link is recorded. The maximum bandwidth of each port whose usage is for trunk links is recorded in the link bandwidth region, and the ID identifying the redundant domain to which the trunk link belongs for the ports whose usage is for trunk links is recorded in the redundancy domain ID region. It is recorded.

  FIG. 8 shows an example of the device setting information, here, an example corresponding to the device a in FIG. 6. Various information for each communication group set in the device, that is, a setting number, an assigned device band, and a port number , Usage flag, allocated port bandwidth, access link flag, and VID (each area). Actually, the number of pieces of device setting information corresponding to the number of devices constituting the L2 network is provided.

  A number for identifying the set communication group is recorded in the setting number area, and a maximum band in which the communication group is guaranteed in the apparatus is recorded in the allocated apparatus band area. In the port number area, a number for identifying each port of the apparatus is recorded, and in the use flag area, a flag indicating whether or not each port of the apparatus is used by the communication group (in the case of using “1”, When not used, “0”) is recorded.

  The allocated port bandwidth area records the maximum guaranteed bandwidth for each port when used by the communication group, and the access link flag area indicates the use of each port when the communication group uses the access link. A flag (“1” for an access link, “0” for a trunk link) indicating whether it is for or not (for a trunk link) is recorded.

  In the VID area, the VID used for each port when the communication group uses is recorded. Ports belonging to the same redundancy domain need to belong to the same VID in the VID area. If the device has a VID conversion function and the redundancy domain is a different port, it is possible to specify a different VID. is there.

  FIG. 9 shows an example of the base information, here corresponding to the base connected to the L2 network of FIG. 6. Various information for each base, that is, base ID, communication group ID, connection device ID, connection It consists of device port number and allocated bandwidth (each area).

  An ID for identifying a connected base is recorded in the base ID area, and an ID of a communication group to which each base belongs is recorded in the communication group ID area. In addition, the ID of the connection destination device for each base is recorded in the connection device ID area, the port number of the connection destination device for each base is recorded in the connection device port number, and the allocated bandwidth is guaranteed for each base. The maximum bandwidth is recorded.

  In the present invention, a graph for path design to be presented to the operator is generated based on these three pieces of information.

  First, the basic structure of the path design graph is generated by the graph generation unit 14. FIG. 10 shows a procedure for generating a basic structure of a path design graph in the graph generation unit 14.

  That is, the graph generation unit 14 reads the network configuration information from the network configuration information storage unit 11, and generates redundant nodes (representing the redundancy range) corresponding to all redundant domain IDs in the network configuration information (step) s1-s4). Specifically, the redundant domain ID in the network configuration information is set to M (s1), and it is determined whether or not a redundant node having the redundant domain ID M is not generated on the graph (s2). Repeat for all redundant domain IDs in the network configuration information (s4). On the other hand, if not generated, a redundant node having a redundant domain ID of M is generated (s3), and this is repeated for all redundant domain IDs in the network configuration information (s4).

  Next, the graph generation unit 14 generates device nodes (representing devices constituting the L2 network) corresponding to all device IDs in the network configuration information (steps s5 to s7, s14). Specifically, the device ID in the network configuration information is set to N (s5), information with a device ID of N is extracted from the network configuration information (s6), and a device node with a device ID of N is generated (s7). Repeat for all device IDs in the network configuration information (s14).

  At this time, if a redundant domain ID is set for the port corresponding to all device IDs in the network configuration information, the graph generation unit 14 and the device node corresponding to the device ID and the redundancy A redundant node corresponding to the domain ID is connected by a side (steps s8 to s13). Specifically, the port number of the device having the device ID N in the network configuration information is set as i (s8), and the redundant domain ID to which the port with the device ID N and the port number i belongs is extracted as L from the network configuration information ( Whether or not L is set is determined (s9), and if not set, this is repeated for all the port numbers in the network configuration information (s13). On the other hand, if it is set, it is further determined whether or not the device node with the device ID M and the redundant node with the redundancy domain ID L are not connected on the graph (s11). It repeats about all the port numbers in (s13). On the other hand, if it is not connected, the device node with device ID M and the redundant node with redundancy domain ID L are connected by sides (s12), and this is repeated for all the port numbers in the network configuration information (s13).

  FIG. 11 shows an example of the basic structure of the path design graph generated in this way, here, the basic structure of the path design graph corresponding to the layer 2 network of FIG.

  In the above description, all redundant domain IDs and all device IDs in the network configuration information are processed. However, redundant domains in a predetermined range (for example, a range desired by the operator) of the network configuration information. It is good also as what processes about ID and apparatus ID.

  Next, information for route design is generated by the graph generation unit 14 and presented together with the nodes of the graph. Although there is a wide variety of information necessary for route design, it is not possible to represent all of them comprehensively, so only the remaining VID information and the remaining bandwidth information are described here. The remaining VID information is a list of available VIDs for each redundant domain (redundant node), and the remaining bandwidth information is a usable bandwidth in the redundant domain and a bandwidth that can be processed by the device (device node).

  FIG. 12 shows a procedure for generating route design information, here, remaining VID information in the graph generation unit 14.

  That is, the graph generation unit 14 reads the network configuration information from the network configuration information storage unit 11 and the device setting information from the device setting information storage unit 12, and initializes all the remaining VID information areas unused (step s21). ), For all ports for which redundant domain IDs are set for devices corresponding to all device IDs in the network configuration information, the VIDs set for the corresponding ports in the device setting information corresponding to the device IDs, and The remaining VID information area corresponding to the redundant domain ID is set as used (steps s22 to s31).

  Specifically, the graph generation unit 14 initializes all areas of the remaining VID information unused (step s21), sets the device ID in the network configuration information to N (s22), and sets the device ID in the network configuration information as the device ID. The port number of the N device is i (s23), the redundant domain ID to which the port with the device ID N and the port number i belongs is extracted as M from the network configuration information (s24), and whether M is set or not is determined. If it is not set, this is repeated for all the port numbers in the network configuration information (s30), and further repeated for all the device IDs in the network configuration information (s31).

  On the other hand, if M is set, the graph generation unit 14 sets the set setting number in the device setting information corresponding to the device with the device ID N as j (s26), and the device corresponding to the device with the device ID N The VID having the setting number j and the port number i is extracted from the setting information as L (s27), the redundant domain ID of the remaining VID information is set to M, and the area corresponding to the VID L is set to used (s28). Is repeated for all setting numbers (s29). Similarly to the above, this is repeated for all port numbers in the network configuration information (s30), and further repeated for all device IDs in the network configuration information (s31).

  An example of the remaining VID information generated in this way is shown in FIG.

  In the above description, processing is performed for all device IDs in the network configuration information, but processing is performed for device IDs in a predetermined range (for example, a range desired by the operator) of the network configuration information as described above. It is good as a thing.

  Next, the remaining band information generation rule is shown. The remaining bandwidth of the redundant node is determined by the lowest value among the unallocated bandwidths of devices and trunk links constituting the redundant domain corresponding to the redundant node. Specifically, the unassigned device bandwidth is checked for all devices belonging to the redundant domain, the unassigned link bandwidth is checked for all trunk links belonging to the redundant domain, and the lowest value among these unassigned bandwidths is set to the redundant node. Of the remaining bandwidth. The remaining bandwidth of the device node is determined by an unassigned device bandwidth of the device corresponding to the device node. If the device has independent device bandwidths within the redundant domain and between the redundant domains, consider the device bandwidth in the redundant domain when generating the remaining bandwidth of the redundant node, and between the redundant domains when generating the remaining bandwidth of the device node. Consider device bandwidth.

  FIG. 14 shows an example of a graph in which the information for route design generated in this way is also presented to the operator (however, here, “the number of remaining VIDs” is displayed as the remaining VID information, and the display for the device node is Omitted.)

  When performing route design, first, the operator specifies the ID of the communication group for which route design is to be performed to the graph generation unit 14 via the control unit 17, and adds a base node representing the base of the communication group to the graph. To do.

  For example, in the L2 network of FIG. 6, the bases 1 and 2 as shown in FIG. 15, that is, the bases 1 and 2 of the base IDs belonging to the communication group ID = 001 among the base information shown in FIG. Is added to the graph of FIG. 11 or FIG. The base information is assumed to be stored in advance in the base information storage unit 13 via the control unit 17.

  FIG. 16 shows a procedure for adding a base node in the graph generation unit 14.

  That is, when the communication group ID to be processed is specified by the operator (s41), the graph generation unit 14 reads the base information from the base information storage unit 13, and among all the base IDs in the base information, the communication is performed. A base node is generated corresponding to the base ID whose group ID matches the communication group ID to be processed, and connected to the device node of the connection device ID corresponding to the base ID on the side (steps s42 to s47).

  Specifically, when the designation of the communication group ID to be processed is accepted as L (s41), the base ID in the base information is set as M (s42), and the communication group ID of the base whose base ID is M from the base information is N, The connection device ID is extracted as O (s43), and it is determined whether or not the communication group ID: L and the communication group ID: N of the communication group to be processed match (s44). It repeats about all the base IDs in (s47). On the other hand, if they match, a base node with base ID M is generated on the graph (s45), and the base node with base ID M and the device node with device ID O are connected by edges (s46). Is repeated for all site IDs in the site information (s47).

  FIG. 17 shows an example of a graph in which the base node added in this way is presented to the operator together with various information necessary for route design.

  In the above description, processing is performed for all base IDs in the base information, but processing may be performed for base IDs within a predetermined range (for example, a range desired by the operator) of the base information.

  When displaying a graph to the operator, there is no restriction on the arrangement method of each node. In addition, as a method of presenting information for route design, it may be displayed with a balloon as shown in FIGS. 14 and 17, or only when an operator performs an operation such as clicking on the node. There is no limitation on the display method.

  According to the graph of FIG. 17, the operator connects “1-a-ac-woo-of-f-2” and “1-a-a-b-car” as routes connecting the base 1 and the base 2. It can be easily seen that there are two paths “h-of-2”. The difference between the former and the latter is the difference between passing through the redundant domain [c] or passing through the redundant domain [f]. Both routes have a sufficient number of remaining VIDs (the number of VIDs that can be used in the redundant domain), but the remaining bandwidth of the redundant domain [c] is small, so the route using the redundant domain [f] is used I understand that is good.

  FIG. 18 shows a state in which a route between the bases 1 and 2 is set by an instruction from the operator or automatically by the route design unit 15. In FIG. 18, the set route is displayed with a bold line, and the VID assigned to this communication group for each redundant domain is displayed with a speech bubble. Through this design process, the operator knows that the route is not looping and that the assigned VID is available. At this time, the device setting information generated by the route design unit 15 is set for the actual device by the device setting unit 16 and the device setting information storage unit 12 is updated.

  When the operator sets the device based on this design, the following information can be read.

  First, it can be seen that it is necessary to make a setting for realizing redundancy for a device corresponding to a device node adjacent to a redundant node through which a route passes. In the redundant node [e] in FIG. 18, it is necessary to set the devices h, i, g, and f to pass a frame having a VID of 1001 between ports belonging to the redundant domain.

  Second, it is necessary to make a setting for connecting the redundant domains to the device corresponding to the device node through which the route passes. In the apparatus h in FIG. 18, in order to connect the redundant domain [f] and the redundant domain [e], the frame is passed between the port belonging to the redundant domain [f] and the port belonging to the redundant domain [e] of the apparatus h. Need to do. Further, since the VID assigned to this communication group is different between the redundant domain [f] and the redundant domain [e], it is necessary to set the VID to be converted when a frame passes through the device h.

  Third, it is necessary to set an access link for the device corresponding to the device node to which the base is connected. In the apparatus f of FIG. 18, the base 2 of the apparatus f performs the process of removing the VLAN tag and flowing the frame flowing from the redundant domain [e] to the port to which the base 2 is connected, and vice versa. It is necessary to set the connected port.

  In this way, the route design and setting are compared with the case where the operator uses the various types of information shown in FIGS. 7, 8, and 9 as they are or when the topology of the network is simply expressed as shown in FIG. It is very easy to grasp the necessary information. Further, the graph of the present invention can be easily designed automatically by an algorithm.

  The present invention can also be realized by installing a program having the procedures shown in the flowcharts of FIGS. 10, 12, and 16 via a medium or a communication line in a known computer.

  11: Network configuration information storage unit, 12: Device setting information storage unit, 13: Site information storage unit, 14: Graph generation unit, 15: Route design unit, 16: Device setting unit, 17: Control unit

Claims (9)

A method of designing a VLAN path that connects bases connected to a partially redundant L2 network,
The graph generation unit reads out network configuration information including various pieces of information for each device configuring the L2 network from the network configuration information storage unit, and a redundant node representing a redundancy range and a device node representing a device configuring the L2 network And a graph generation step for generating a graph composed of edges connecting the redundant nodes and the device nodes belonging to the redundancy range;
The graph generation means reads out network configuration information composed of various information for each apparatus constituting the L2 network from the network configuration information storage means, and reads out apparatus setting information for individual apparatuses constituting the L2 network from the apparatus setting information storage means. An information generation process for generating information for route design;
A base node adding step of reading base information relating to the base connected to the L2 network from the base information storage means, generating a base node representing the base, and adding the base node to the graph;
A route design unit that sets a VLAN route connecting base nodes on the graph and generates device setting information corresponding to the setting;
A VLAN path design method, comprising: a device setting unit configured to set the device setting information for the device and updating the device setting information storage unit with the device setting information. The graph generation process
Generating a redundant node corresponding to the redundant domain ID in the network configuration information;
Generating a device node corresponding to the device ID in the network configuration information;
When a redundant domain ID is set for a port corresponding to a device ID in the network configuration information, a device node corresponding to the device ID and a redundant node corresponding to the redundant domain ID are connected by a side. The VLAN path design method according to claim 1, further comprising: a step. The information generation process
Initializing the remaining VID information area unused;
Regarding a port in which a redundant domain ID is set for a device corresponding to the device ID in the network configuration information, it corresponds to the VID set in the corresponding port in the device setting information corresponding to the device ID and the redundant domain ID. The VLAN path design method according to claim 1, further comprising: setting a remaining VID information area as used. The base node addition process is
Receiving a designation of a communication group ID to be processed;
Among the base IDs in the base information, a base node is generated corresponding to the base ID whose communication group ID matches the communication group ID to be processed, and the device node and edge of the connection device ID corresponding to the base ID The VLAN path design method according to claim 1, further comprising: A VLAN path design apparatus for designing a VLAN path connecting bases connected to a partially redundant L2 network,
Network configuration information storage means for storing network configuration information composed of various types of information for each device constituting the L2 network;
Device setting information storage means for storing device setting information for individual devices constituting the L2 network;
Base information storage means for storing base information related to bases connected to the L2 network;
Network configuration information storage means, device setting information storage means and base information storage means read out network configuration information, device setting information and base information, a redundant node representing the scope of redundancy, and a device node representing a device constituting the L2 network And a node that connects the redundant node and the device node belonging to the redundancy range, generates a route design information, generates a base node representing the base, and adds it to the graph Graph generation means;
A route design unit configured to set a route of the VLAN connecting the base nodes on the graph and generate device setting information corresponding to the setting;
A VLAN path design device comprising: device setting means for setting the device setting information for a device and updating device setting information storage means with the device setting information. The graph generation means
Means for generating a redundant node corresponding to the redundant domain ID in the network configuration information;
Means for generating a device node corresponding to the device ID in the network configuration information;
When a redundant domain ID is set for a port corresponding to a device ID in the network configuration information, a device node corresponding to the device ID and a redundant node corresponding to the redundant domain ID are connected by a side. The VLAN path design apparatus according to claim 5, further comprising: means. The graph generation means
Means for initializing the remaining VID information area unused;
Regarding a port in which a redundant domain ID is set for a device corresponding to the device ID in the network configuration information, it corresponds to the VID set in the corresponding port in the device setting information corresponding to the device ID and the redundant domain ID. The VLAN path design apparatus according to claim 5, further comprising: means for setting a remaining VID information area as used. The graph generation means
Means for accepting designation of a communication group ID to be processed;
Among the base IDs in the base information, a base node is generated corresponding to the base ID whose communication group ID matches the communication group ID to be processed, and the device node and edge of the connection device ID corresponding to the base ID The VLAN path design device according to claim 5, further comprising:   The program for making a computer perform each process process of the VLAN path | route design method in any one of Claims 1 thru | or 4.

Images