JP4518487B2 - L2 transfer system using optical network - Google Patents

Description

  The present invention relates to an L2 transfer system using an optical network, and in particular, an L2 transfer system using an optical network capable of effectively performing wavelength path setting and deletion (bandwidth control), load distribution, path setting, and the like. About.

  An Ethernet (registered trademark) network composed of a plurality of L2 switches is known as a network for transferring L2 frames (packets). FIG. 10 shows a relay network composed of L2 switches 101-104. Each L2 switch 101-104 analyzes VLAN (Virtual LAN) information included in the L2 frame, and forwards each frame to the output side port accordingly.

  In the L2 network, in order to be able to cope with the increase and decrease of traffic, assuming the peak traffic, the links between the L2 switches 101-102, 101-103, 103-104, 102-104 are increased in advance. deep. For example, when traffic rapidly increases between the L2 switches 101-104, a band called LAG (Link Aggregation) is used to increase the bandwidth between the L2 switches 101-102 and between the L2 switches 102-104. .

Further, when a loop is formed by links connecting the L2 switches 101 to 104, a protocol called STP (Spanning Tree Protocol) or RSTP (Rapid STP) is generally used to prevent packets from circulating infinitely in the loop. Used. The packet transfer path is automatically determined uniquely by this protocol. For example, when the root switch is the L2 switch 101, the link between the L2 switches 103-104 (or between the L2 switches 102-104) is blocked by STP or RSTP, and the transfer path from the L2 switch 101 to the L2 switch 104 is L2 The switch 101-102-104 (or L2 switch 101-103-104) is determined.
JP 2001-355448 A "IDG Information and Communication Series 10 Gigabit Ethernet Textbook" IDG Japan Co., Ltd. April 2002 pages 358-359

  However, in the conventional L2 transfer system, it is possible to control the bandwidth between the L2 switches by increasing the interface or LAG, but there is a problem that it is difficult to flexibly cope with a sudden increase in traffic.

  In addition, since the packet transfer route is uniquely determined by STP and RSTP regardless of whether there is a surplus of network resources, it is difficult to distribute traffic and determine the transfer route reflecting the operator's intention. There is a problem that cannot be used effectively.

  An L2 network transfer system called MPLS (Multi-Protocol Label Switching) is known to realize traffic load distribution and route setting that reflect the operator's intentions, but MPLS will rapidly increase traffic in the future. On the other hand, it is necessary to increase the interface (photoelectric conversion unit) of the forwarding node for MPLS.

  In the future, it is expected that the speed of the relay node interface will increase in response to a sudden increase in traffic, so it is desirable to build a cost effective relay network that does not require expensive interfaces as much as possible. The interface of the photoelectric conversion unit to a network of 10 GbE or more that would be expensive is expensive, and it is difficult to provide the service at a low cost by increasing such an expensive interface in advance.

  An object of the present invention is to use an optical network that solves the above-mentioned problems, can flexibly perform band control, path setting, load distribution, etc., and can construct a cost effective L2 network relay network. It is to provide an L2 transfer system.

In order to solve the above problems, the present invention configures an L2 network having a GMPLS network as a relay network by interposing a GMPLS network including a plurality of optical cross-connect devices between L2 switches,
The L2 switch has an L2 switch unit, and an L2SW / GMPLS linkage unit for linking the L2 switch unit and the GMPLS network is connected to the L2 switch unit, and a GMPLS network is connected to the L2SW / GMPLS linkage unit A GMPLS control unit that controls the setting of wavelength paths, a path information management database that stores information on wavelength paths that are updated according to additional settings and deletions of wavelength paths and that are set between the L2 switch units, and The IF correspondence table indicating the correspondence between the physical interface and the control interface ID in the L2 switch unit is connected, and the L2SW / GMPLS linkage unit collects MIB information from the L2 switch unit to calculate traffic, and the result According to the path information management database and the F requests the GMPLS control unit to add or delete a wavelength path with reference to the F correspondence table and requests the L2 switch unit to set or cancel the LAG. The GMPLS control unit receives a request from the L2SW / GMPLS cooperation unit. Add set or remove a wavelength path in GMPLS network controls the additional settings or delete request to the thus optical cross-connect device of a wavelength path, the L2 switch unit, the LAG setting or canceling from the L2SW / GMPLS linkage unit It is characterized in that LAG setting or cancellation is performed according to a request .

Here, or as the root of the wavelength path is autonomously set in accordance with the priority of the link between the L2 switch unit, the L2SW / GMPLS coordination unit collects VLAN information from the L2 switch unit, its priority It is possible to reflect the bit in the wavelength path additional setting request and to set the route of the wavelength path autonomously according to the priority of the traffic engineering link set between the optical cross-connect devices.

It is also possible to be set explicitly route between the L2 switch unit according to operator's policy. The L2SW / GMPLS linkage unit and GMPLSL2 all functions or some functions of the switch between the control unit can be provided as part of the L2 switch. Path information management database and IF correspondence table may be included in the L2 switch.

  In the present invention, an L2 transfer system is configured using a GMPLS network including an optical cross-connect device as a relay network, a wavelength path is set and deleted using a path information management database and an IF correspondence table, and bandwidth control is performed. Flexible band control can be easily performed. In addition, by setting the priority of the wavelength path according to the priority setting of VLAN information and the priority of traffic engineering, the operator's policy can be reflected in route control and traffic distribution. Furthermore, since the GMPLS network is used as a relay network, it is not necessary to use an expensive interface such as an optoelectric conversion unit, so that a cost effective L2 network relay network can be constructed.

  The present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing a basic configuration of an L2 transfer system according to the present invention. The transmission line 11 and a plurality of optical cross-connect devices (OXC) 12 to 14 constitute a GMPLS network 10.

  The L2 switches 15 and 16 are respectively coupled to the optical cross-connect devices 12 and 13 so as to be located at the edge of the GMPLS network 10. Accordingly, an L2 network transfer system using the GMPLS network 10 as a relay network is configured as a whole. Here, in order to simplify the explanation, two L2 switches 15 and 16 and three OXCs 12 to 14 are shown, but it is general that more L2 switches and OXCs are included.

  The L2 switches 15 and 16 are respectively provided with L2 switch units 17 and 18, L2SW / GMPLS cooperation units 19 and 20 are connected to the L2 switch units 17 and 18, and GMPLS control units are connected to the L2SW / GMPLS cooperation units 19 and 20. 21 and 22 are connected. In this example, the L2SW / GMPLS linking units 19 and 20 and the GMPLS control units 21 and 22 are provided as part of the L2 switches 15 and 16, but all or some of these functions are provided in the L2 switches 15 and 16 respectively. It can also be provided separately.

  Path information management databases 23 and 24 and IF correspondence tables 25 and 26 are connected to the L2SW / GMPLS cooperation units 16 and 17. The path information management databases 23 and 24 store information on wavelength paths set in the GMPLS network 10. The IF correspondence tables 25 and 26 represent the correspondence between the physical interfaces (IFs) of the L2 switch units 17 and 18 and their identifiers (IF IDs), and this information is stored in advance.

  The L2SW / GMPLS linkage units 16 and 17 use the path information management databases 23 and 24 and the IF correspondence tables 25 and 26 to link the controls of the L2 switch units 17 and 18 and the OXCs 12 to 14 as described later. The GMPLS control units 21 and 22 control the OXCs 11 to 14 via the control plane 27 of the GMPLS network 10 and set an optimum wavelength path in the GMPLS network 10. The L2SW / GMPLS cooperation units 19 and 20 and the GMPLS control units 21 and 22 can be configured by software.

  Hereinafter, the L2 switch 15 will be described, but the same applies to the L2 switch 16. FIG. 2 is a flowchart showing a schematic operation of the L2SW / GMPLS cooperation unit 19 when the traffic amount increases. The L2SW / GMPLS linkage unit 19 collects the number of packets transferred between the L2 switch 15 and each of the other L2 switches, other MIB information (Management Information Base) (S21), calculates the traffic volume from the collected MIB information, Compare with the set threshold value (S22). When the traffic volume of a certain link (or interface) exceeds the upper limit setting threshold, the path information management database 23 (see FIG. 4) is referenced as a trigger, and the wavelength between the L2 switches whose traffic volume exceeds the upper limit threshold The GMPLS control unit 21 is requested to set additional paths (S23).

  The GMPLS control unit 21 controls the OXCs 12 to 14 via the control plane 27 in accordance with a request for additional setting of wavelength paths, and sets additional wavelength paths. Further, after confirming that the wavelength path is normally set, the L2SW / GMPLS cooperation unit 19 refers to the IF correspondence table 25 (see FIG. 5), and the link of the wavelength path additionally set is the L2 switch unit 17 Which IF is supported is checked, and the L2 switch unit 17 is requested to set LAG for two links, that is, a link whose traffic volume has exceeded the upper limit threshold value and a link whose wavelength path is additionally set (S24). The L2 switch unit 17 sets the LAG according to this request.

  FIG. 3 is a flowchart showing a schematic operation of the L2SW / GMPLS cooperation unit 19 when the traffic volume decreases. The L2SW / GMPLS linkage unit 19 collects the number of packets transferred between the L2 switch 15 and each of the other L2 switches and other MIB information (S31), calculates the traffic volume from the collected MIB information, and sets the set threshold value. Compare (S32). When the traffic volume in the link group in which LAG is set falls below the lower threshold, the L2 switch unit 17 is requested to cancel the LAG setting for a certain link in the link group (S33). The L2 switch unit 17 releases the LAG setting according to this request.

  Further, the L2SW / GMPLS cooperation unit 19 checks which wavelength path corresponds to the link for which the LAG setting is canceled with reference to the path information management database 23 (see FIG. 4), and deletes the wavelength path by the GMPLS control unit. 21 is requested (S34). The GMPLS control unit 21 controls the OXCs 12 to 14 via the control plane 27 in accordance with the wavelength path deletion request, and deletes the wavelength path.

  FIG. 4 shows an example of the path information management database 23. The path information management database 23 stores path information used for control for each currently set wavelength path. This path information includes wavelength path ID (Tunnel ID), L2 inter-switch wavelength path ID (LSP ID), ingress L2 switch ID (Ingress L2SW ID) and egress L2 switch ID (Egress L2SW ID), ingress L2 switch This includes the logical IF ID (Ingress IF ID) on the OXC side corresponding to the physical IF. Note that the OXC-side IF ID (Egress IF ID) corresponding to the physical IF of the exit-side L2 switch is automatically recognized on the Egress side at the time of path setting, and the physical IF ID of the L2 switch is specified from the correspondence table shown in FIG. . These contents are automatically updated when the wavelength path is added or deleted.

  4 shows three wavelength paths (LSP ID: 1 to 3) from the logical IF (Ox3232321b to d) on the OXC side corresponding to the physical IF of the L2 switch (Ox3232321a) to the opposite L2 switch (Ox3232322a). These wavelength paths are set to LAG from the relationship of Tunnel ID = LAG number × 100 + LSP ID. By using such a path information management database 23, the L2SW / GMPLS linkage unit 19 can easily recognize which physical IF is set between the L2 switches in cooperation with the correspondence table of FIG. The LAG can be set and released according to traffic easily and quickly.

  FIG. 5A shows an example of the IF correspondence table 25. The IF correspondence table 25 stores OXC side port information (IF ID) physically connected to the physical IF of the L2 switch unit 17 in association with each other. FIG. 5B shows that the IF IDs of the physical IFs GE2 / 1, GE2 / 2, and GE2 / 3 of the L2 switch unit 17 are Ox3232321b, Ox3232321c, and Ox3232321d, respectively. The L2SW / GMPLS linkage unit 19 can control the wavelength path addition setting / deletion and the LAG setting / release easily in correspondence with each other by referring to the IF correspondence table 25 described above. Further, even if the physical interface changes due to the change of the L2 switch unit 17 or the like, it can be easily dealt with by rewriting the IF correspondence table, and there is no need to change the control content of the L2SW / GMPLS linkage unit 19.

  FIG. 6 is a functional block diagram illustrating a specific example of the L2SW / GMPLS cooperation unit 19. The L2SW / GMPLS cooperation unit 19 includes a MIB information collection module 61, a traffic monitor module 62, a setting module 63, and a common processing module 64. The setting module 63 includes an L2SW setting module 65, a GMPLS setting module 66, and a communication module 67. A GUI display module is connected to the common processing module 64, and a user can set various states of the system and view various information via the GUI display module. In addition, transmission / reception of information to / from the setting file, path information management database, IF correspondence table, and the like is performed via the common processing module 64.

  The MIB information collection module 61 collects MIB information and VLAN-related information necessary for traffic calculation from the L2 switch unit 17 via SNMP-API (Simple Network Management Protocol-Application Programming Interface).

  The traffic monitor module 62 calculates a link usage rate based on the MIB information collected by the MIB information collection module 61, compares the calculated link usage rate with a preset threshold value, and according to the comparison result. Requests the setting module 63 to add (bandwidth increase) or delete (bandwidth reduction) the wavelength path. The GMPLS setting module 66 of the setting module 63 transmits a wavelength path addition setting or deletion command to the GMPLS control unit 21 according to this request, and the L2SW module 65 transmits a LAG setting or cancellation command to the L2 switch unit 17. These transmissions are performed via the CLI-API 67 of the communication module.

  The link usage rate can be calculated by, for example, the following calculation formula. The link usage rate calculates two link usage rates: an In link usage rate based on the number of In octets entering each IF, and an Out link usage rate based on the number of Out octets coming out from each IF.

  Link usage rate (%) = {(number of octets collected-number of octets collected last time) x 8} x (polling interval x ifSpeed value)

  Here, the number of octets can be obtained from MIB information: ifHCInOctets and ifHCOutOctets (64-bit counter). The ifSpeed value represents the transfer rate of the interface and can be obtained from MIB information: mib-2.interfaces.ifTable.ifSpeed. The link usage rate calculation formula is not limited to the above formula, and an appropriate calculation formula may be used by appropriately changing the link usage rate.

  FIG. 7 is a flowchart showing operations of the MIB information collection module 61 and the traffic monitor module 62. The MIB information collection module 61 polls the L2 switch unit 17 (S71) and collects MIB information (S72). The collected MIB information is stored as a MIB data file. The traffic monitor module 62 calculates the link usage rate as described above based on the collected MIB information and the MIB information stored so far (S73), and compares it with the link usage rate upper limit threshold (S74). . The link usage rate upper limit threshold should be arbitrarily settable.

  If the link usage rate exceeds the upper limit threshold value, a check is made for a match with the condition set by the upper limit counter (S75). The upper limit counter includes an In counter that counts the time when the In link usage rate exceeds the upper limit threshold, and an Out counter that counts the time when the Out link usage rate exceeds the upper limit threshold. These counters are reset at a fixed time (set in units of minutes or seconds). This fixed time should be set manually.

  The upper limit counter is the count value of at least one of the In counter and Out counter, that is, at least one of the time when the In link usage rate exceeds the upper limit threshold and the time when the Out link usage rate exceeds the upper limit threshold continues for a certain period of time. Condition is met. If the conditions match, the upper limit counter requests the setting module 63 to perform additional wavelength path setting (bandwidth increase) (S76), and also requests SNMP-API to stop polling (S77). If the conditions do not match, the process returns to S71, and the processes after polling are repeatedly executed at predetermined intervals.

  When the link usage rate is equal to or lower than the upper limit threshold value, the link usage rate is compared with the link usage rate lower limit threshold value (S78). It is preferable that the link usage rate lower limit threshold can be set arbitrarily. When the link usage rate is equal to or lower than the lower limit threshold value, a match with the condition set by the lower limit counter is checked (S79). The lower limit counter includes an In counter that counts time when the In link usage rate is equal to or lower than the lower limit threshold value, and an Out counter that counts time when the Out link usage rate is equal to or lower than the lower limit threshold value. These counters are reset at a fixed time (set in units of minutes or seconds). This fixed time should be set manually.

  The lower limit counter is the count value of both the In counter and Out counter, that is, both the time when the In link usage rate is less than or equal to the lower threshold and the time when the Out link usage rate is less than or equal to the lower threshold continues for a certain period of time. The condition is met. If the conditions match, the lower limit counter requests the setting module 63 to delete the wavelength path (band reduction) (S80), and requests the SNMP-API to stop polling (S77). If the conditions do not match, the process returns to S71, and the processes after polling are repeatedly executed at predetermined intervals.

  FIGS. 8 and 9 are flowcharts showing the operation of the setting module 63. FIG. 8 shows a case where a wavelength path setting (bandwidth increase) is requested from the traffic monitor module 62. FIG. This is a case where bandwidth reduction is requested.

  In FIG. 8, upon receiving the wavelength path addition setting command, the setting module 63 refers to the VLAN information and determines whether the L2 switch 15 is a master / slave for each VLAN (S81).

  When the L2 switch 15 becomes the master, first, a wavelength path addition setting command is transmitted to the GMPLS control unit 21 via the communication module 67 (S82). The GMPLS control unit 21 sets an appropriate wavelength path in the GMPLS network 10 via the control plane 27 and returns a response. The setting module 63 confirms the normality and identifies the IF on which the wavelength path is additionally set based on the response to the wavelength path addition setting command (S83). If there is an abnormality, the process returns to S82 and the transmission of the wavelength path addition setting command is repeated for a certain period. If it is still abnormal, the cooperative application is stopped and an alarm is generated. If it is normal, a LAG setting command is transmitted to the L2 switch unit 17 (S84), and the response is confirmed (S85). If the response is not confirmed here, the process returns to S82 and the transmission of the wavelength path additional setting request command is repeated for a certain period. If it is still abnormal, the cooperative application is stopped and an alarm is generated. If the response of the LAG setting command can be confirmed, the normality of the response is confirmed (S86). If the response is not normal, the process returns to S82 and the transmission of the wavelength path additional setting request command is repeated for a certain period. If it is still abnormal, the cooperative application is stopped, and the fact is notified to the common processing module 64 to generate an alarm or the like. Also, if the response is normal, the polling is resumed as wavelength path addition setting completion (S87).

  When the L2 switch 15 is a slave, first, the character string appearing on the CLI is confirmed when setting the wavelength path (S88). The IF to which the wavelength path is additionally set is specified from the character string displayed here (S89). Next, a LAG setting command is transmitted to the L2 switch unit 17 (S90), and the response is confirmed (S91). If the response cannot be confirmed, the process returns to S90 and the transmission of the LAG setting command is repeated for a certain period until the response is confirmed. If it is still abnormal, the fact is notified to the common processing module 64 and an alarm is generated. If the response of the LAG setting command can be confirmed, the normality of the response is confirmed (S92). If the response is not normal, the fact is notified to the common processing module 64 to generate an alarm or the like. If the response is normal, polling is resumed as wavelength path addition setting completion (S93).

  In FIG. 9, upon receiving a wavelength path deletion (bandwidth reduction) command, the setting module 63 refers to the VLAN information and determines whether the L2 switch 15 is a master / slave for each VLAN (S81).

  When the L2 switch 15 becomes the master, first, the IF of the L2 switch unit 17 to be deleted is selected, the LAG release command is transmitted to the L2 switch unit 17 via the communication module 67 (S94), and the response is confirmed. (S95). If the response cannot be confirmed here, the process returns to S94 and the transmission of the LAG cancellation command is repeated for a certain period. If it is still abnormal, the cooperative application is stopped and an alarm is generated. If the LAG cancellation operates normally, the IF correspondence table in FIG. 5 is referred to, the deleted IF and the logical IF ID of the wavelength path are recognized, and the wavelength path deletion command is transmitted to the GMPLS control unit 21 (S96). .

  The GMPLS control unit 21 deletes the wavelength path selected in the GMPLS network 10 via the control plane 27, and returns a response. The setting module 63 confirms normality based on the response to the wavelength path deletion command (S97). If there is an abnormality, the process returns to S96 and the transmission of the wavelength path deletion command is repeated for a certain period. If it is still abnormal, the cooperative application is stopped and an alarm is generated. Finally, the normality of the response is confirmed (S98). If the response is not normal, the cooperative application is stopped, and the common processing module 64 is notified to that effect and an alarm is generated. Also, if the response is normal, polling is resumed as wavelength path deletion completion (S99).

  When the L2 switch 15 becomes a slave, first, a character string appearing on the CLI is confirmed (S100). The IF ID of the wavelength path deleted from the character string shown here is specified, and the IF of the L2 switch unit 17 is specified from the IF correspondence table of FIG. 5 (S101). Next, an LAG release command is transmitted to the L2 switch unit 17 (S102), and the response is confirmed (S103). If the response cannot be confirmed here, the process returns to S102, and the transmission of the LAG cancellation command is repeated for a certain period. If it is still abnormal, the cooperative application is stopped and an alarm is generated. If the response of the LAG cancellation command can be confirmed, the normality of the response is confirmed (S104). If the response is not normal, the cooperative application is stopped, and the common processing module 64 is notified to that effect and an alarm is generated. Also, if the response is normal, polling is resumed as wavelength path deletion completion (S105).

In the above embodiment, for example, the following two methods can be considered as wavelength path additional setting methods when the traffic volume increases.
(1) Set the route between OXCs explicitly according to the operator's policy.
(2) The wavelength path route is autonomously set according to the link priority.

In the method (2) above, for example, the priority setting of VLAN information is reflected in the wavelength path request, and the route of the wavelength path is autonomous according to the priority of the traffic engineering link (Telink: Trafic engineering link) set between XOCs. It can be realized by being set to .

  Traffic transmitted through the IF group set with LAG can be distributed by the L2 switch based on information such as the MAC address, IP address, MPLS label, and TCP / UDP port.

  As described above, in the present invention, an L2 transfer system is configured by using a GMPLS network including an optical cross-connect device as a relay network, and additional setting (bandwidth increase) of wavelength paths using the path information management database and IF correspondence table, and Since deletion (band reduction) is performed, flexible band control becomes possible. In addition, by setting the priority of the wavelength path according to the priority setting of VLAN information and the priority of traffic engineering, the operator's policy can be reflected in route control and traffic distribution. Furthermore, since the GMPLS network is used as a relay network, it is not necessary to use an expensive interface such as an optoelectric conversion unit, and a cost-effective relay network can be constructed. Therefore, according to the present invention, effective use of resources can be realized while performing bandwidth control in an environment where wavelength resources are not sufficient as in an international network.

It is a block diagram which shows the basic composition of the L2 transfer system which concerns on this invention. It is a flowchart which shows schematic operation | movement of the L2SW / GMPLS cooperation part when the traffic amount increases. It is a flowchart which shows schematic operation | movement of the L2SW / GMPLS cooperation part when the traffic amount reduces. It is explanatory drawing which shows the example of a path information management database. It is explanatory drawing which shows the example of IF correspondence table. It is a functional block diagram which shows the specific example of a L2SW / GMPLS cooperation part. It is a flowchart which shows operation | movement of a MIB information collection module and a traffic monitor module. It is a flowchart which shows the operation | movement (in the case of wavelength path addition setting) of a setting module. It is a flowchart which shows the operation | movement (in the case of wavelength path deletion) of a setting module. It is a block diagram which shows the conventional wide area Ethernet (trademark) network.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 ... GMPLS network, 11 ... Transmission path, 12-14 ... Optical cross-connect apparatus, 15, 16 ... L2 switch, 17, 18 ... L2 switch part, 19, 20 ... L2SW / GMPLS linkage unit, 21, 22 ... GMPLS control unit, 23, 24 ... path information DB, 25, 26 ... IF correspondence table, 27 ... control plane, 61 ... MIB information collection Module, 62 ... Traffic monitor module, 63 ... Setting module, 64 ... Common processing module 64, 65 ... L2SW setting module, 66 ... GMPLS setting module 66, 67 ... Communication module

Claims (5)

A GMPLS network including a plurality of optical cross-connect devices is interposed between L2 switches to form an L2 network using the GMPLS network as a relay network,
The L2 switch has an L2 switch unit, and an L2SW / GMPLS linkage unit for linking the L2 switch unit and the GMPLS network is connected to the L2 switch unit, and a GMPLS network is connected to the L2SW / GMPLS linkage unit A GMPLS control unit that controls the setting of wavelength paths, a path information management database that stores information on wavelength paths that are updated according to additional settings and deletions of wavelength paths and that are set between the L2 switch units, and Connect the IF correspondence table indicating the correspondence between the physical interface and the control interface ID in the L2 switch unit,
The L2SW / GMPLS cooperation unit collects MIB information from the L2 switch unit, calculates traffic, and refers to the path information management database and the IF correspondence table according to the result, to the GMPLS control unit wavelength path Requesting additional setting or deletion of LAG and requesting LAG setting or cancellation to the L2 switch unit,
The GMPLS control unit adds set or remove a wavelength path in GMPLS network controls the request thus the optical cross-connect device of additional settings or removing wavelength path from the L2SW / GMPLS linkage unit,
The L2 network transfer system , wherein the L2 switch unit performs LAG setting or cancellation in accordance with a LAG setting or cancellation request from the L2SW / GMPLS cooperation unit .   The L2 network transfer system according to claim 1, wherein a route of a wavelength path is autonomously set according to a priority of a link between the L2 switch units.   The L2SW / GMPLS cooperation unit collects VLAN information from the L2 switch unit, reflects the priority bit in a wavelength path additional setting request, and according to the priority of the traffic engineering link set between the optical cross-connect devices. The L2 network transfer system according to claim 2, wherein a route of the wavelength path is set autonomously.   4. The L2 network transfer system according to claim 1, wherein a route between the L2 switch sections is explicitly set according to an operator policy.   5. The L2 network transfer system according to claim 1, wherein all or a part of functions of the L2SW / GMPLS cooperation unit and the GMPLS control unit are provided as a part of the L2 switch.

Images