JP2014112977A - Packet relay device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a technique for a packet relay device comprising a plurality of pieces of link aggregation connected with a plurality of redundant network interface units, that can control standby power of the standby network interface units.SOLUTION: A packet relay device determines standby port units in link aggregation, determines whether each of redundant network interface units has an operating port unit, and when the network interface unit has no operating port unit, performs processing for changing a state of the network interface unit into a standby state. The device monitors occurrence of failure in the operating network interface unit, and when the failure is detected in the operating network interface unit, starts up the standby network interface unit, and changes the state of the network interface unit having the failure into the standby state.

Description

  The present invention relates to a packet relay device, and more particularly, to a high reliability technology aiming at communication reliability by a redundant configuration and a packet relay device that reduces surplus power.

  The number of packet relay devices that are routers and switches is increasing. In addition, the use of large-capacity information such as moving images has become widespread. As a result, the amount of traffic in the network has increased rapidly. Further, it is predicted that the power consumption of the packet relay apparatus in Japan is required to be 13 times the power consumption in 2025 compared to 2006. In order to help prevent global warming, the power saving of the packet relay device is an important issue.

  As a power saving technique of the packet relay apparatus, there is a technique of changing a clock frequency of a packet transfer unit that determines a transfer destination of a packet to be transmitted / received as disclosed in Patent Document 1. Further, there is a technique for suppressing the power supply of the port unit and the packet transfer unit that connect the network lines shown in Non-Patent Document 1.

  On the other hand, if power saving is simply applied to the packet relay device, the continuity of communication is sacrificed. For this reason, power saving is often achieved in combination with a reliability technique in which the port unit and the packet transfer unit are configured redundantly. Specifically, there is link aggregation standardized by IEEE 802.3ad as a technology for making the port part redundant. Link aggregation is a technology that allows communication to be continued even if a plurality of port sections are logically handled as one line, resulting in an increase in bandwidth and a failure of one line. As a technique for avoiding communication interruption in link aggregation, there is a method of dynamically changing the number of ports accommodated by the link aggregation in accordance with the time zone and traffic amount shown in Patent Document 2. In addition, there is a method in which control information related to link aggregation is always synchronized in a plurality of network interface units described in Patent Document 3.

  In addition, the technology for making the packet transfer unit redundant includes a case where all of the redundant packet transfer units are used as an active system and a case where a part of the packet transfer unit is made standby as a spare for switching in the event of a failure. Further, when waiting, there are a hot standby in which the same state as the active system is maintained and switching to the failed active system can be performed immediately, and a cold standby which takes a little time for switching. In general, cold standby is more effective in terms of power reduction.

JP 2007-228491 A JP 2008-098720 A JP 2008-244907 A

“AX6700S / AX6600S / AX6300S Software Manual Configuration Guide for Vol.1 Ver.11.2”, ALAXALA Networks Corporation, October 2009, pp. 269-290

  The present invention provides a technology for controlling standby power of a standby network interface unit in a packet relay apparatus including a plurality of link aggregations connected to a plurality of redundant network interface units.

  Further, in the present invention, in the packet relay device, communication interruption occurs due to repeated start and stop of the standby network interface unit due to a failure that occurs intermittently at the port unit on the operational network interface unit and recovers. Provide technology to avoid this.

  In order to solve at least one of the above problems, a port unit to be waited in link aggregation is determined from information set by the user for the device, and there is an operating port unit belonging to each redundant network interface unit If there is no operating port part in the network interface part, the network interface part itself is changed to standby, the occurrence of a fault in the operating network interface part is monitored, and a fault is detected. Provided is a network relay device that activates a standby network interface unit and changes a port unit or a network interface unit to a standby state for a network interface unit in which a failure has occurred.

  In addition, based on threshold information specified by the user, the upper limit value of the traffic volume according to the number of ports belonging to the link aggregation is calculated, and the traffic volume of the port unit and the entire link aggregation to which the port unit belongs is measured at a certain period, Compare with the upper limit value, select the optimal number of ports according to the measured traffic volume, change the power state of the current number of link aggregation ports to match the optimal number of ports, and then make each redundant network interface unit There is provided a network relay device that determines whether or not there is an operating port unit belonging to the network interface, and performs processing to change the network interface unit itself to standby when there is no operating port unit in the network interface unit.

  In addition, it maintains the normal value range that is the standard in the inspection items that inspect the quality of the port part included in the link aggregation and the allowable number of occurrences that allow the abnormality. Network relay that performs processing to change the operating network interface unit itself to standby after starting the standby network interface unit when the port unit belonging to the redundant operating network interface unit is abnormal Providing equipment.

  While the standby power in the standby network interface unit is reduced, if a failure occurs in the operating network interface unit, the standby network interface can be activated to continue communication.

It is a block diagram explaining the structure of a packet relay apparatus, and the structure of a network. It is a figure explaining the structure of an operation management part. It is a figure explaining the group management table of link aggregation. It is a figure explaining the port management table of link aggregation. It is a figure explaining the group management table of a network interface part. It is a power-saving flowchart by the port aggregation of link aggregation. It is a flowchart of the state determination A of a network interface part. It is an operation processing flowchart of a standby network interface unit. It is a figure explaining the structure of an operation management part. It is a figure explaining the total traffic amount management table of link aggregation. It is a figure explaining the port traffic volume management table of link aggregation. It is a figure explaining the upper limit management table of the traffic amount according to the number of ports. It is a figure explaining the group management table of a network interface part. It is a figure explaining the port traffic volume management table of link aggregation. It is a figure explaining the group management table of a network interface part. It is a power-saving flowchart based on the traffic volume of link aggregation. It is a flowchart for calculating the upper limit value of the traffic volume according to the number of ports. It is a port state determination flowchart of link aggregation. It is a figure explaining the structure of an operation management part. It is a figure explaining the structure of a hardware control part. It is a figure explaining the port inspection status management table of link aggregation. It is a figure explaining the group management table of a network interface part. It is a figure explaining the inspection result management table of a port part. It is a figure explaining an inspection standard table. It is a control flowchart of the network interface part at the time of an intermittent failure occurrence. It is a quality inspection flowchart of a port part. It is a flowchart of the state determination B of a network interface part. It is a figure explaining the structure of an operation management part. It is a figure explaining the state management table of a link aggregation. It is a power saving flowchart by the port gathering of the link aggregation at the time of LACP use. It is a flowchart of the state determination C of a network interface part. It is a flowchart which confirms the state of LACP. It is a flowchart which updates the LACP state accompanying LACPDU reception. It is a figure explaining the structure of an operation management part. It is a figure explaining the port management table of link aggregation. It is a figure explaining the failure criteria table of a network interface part. It is a figure explaining the group management table of a network interface part. It is a flowchart which controls redundant NIF accompanying failure recovery of NIF. It is a flowchart of the state determination D of a network interface part.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings using examples. The same reference numerals are assigned to substantially the same parts, and the description will not be repeated.

  With reference to FIG. 1, an internal structure of a packet relay device and a network configuration using the packet relay device will be described. In FIG. 1, the network 50 includes three packet relay apparatuses 10. In order to improve the reliability of communication between the packet relay devices 10, the packet relay device 10 uses link aggregation to achieve line redundancy.

  The packet relay device 10 includes a two-type device control unit 20, a two-type packet transfer unit 30, and a two-type network interface unit 40. The device control unit 20 includes a command analysis unit 100, an operation management unit 200, and a hardware control unit 500. The network interface unit 40 has a plurality of port units 700. The port unit 700-1 is connected to the packet relay apparatus 10-2. The port unit 700-2 is connected to the packet relay apparatus 10-3. The port unit 700- (n-1) is connected to the packet relay apparatus 10-2. The port unit 700-n is connected to the packet relay apparatus 10-3.

  The network interface unit 40 controls packet transmission / reception with respect to the network 50. The packet transfer unit 30 connects the network interface unit 40 and determines a packet relay destination based on header information of the packet to be transmitted / received. The device control unit 20 stores a software program for controlling the packet relay device 10 itself. The device control unit 20, the packet transfer unit 30, and the network interface unit 40 are connected by a bus.

  The port unit 700 terminates the physical line. The physical line between the packet relay apparatuses 10 adopts a link aggregation configuration connected to the port unit 700 in the different network interface unit 40.

  The software program in the device control unit 20 controls the following operations. The command analysis unit 100 analyzes configuration information set by the user. The operation management unit 200 controls the reflection of configuration information from the command analysis unit 100 and the determination and command of the power state of the apparatus based on the hardware state. The hardware control unit 500 performs setting value registration in the hardware, power control, collection of statistical information, and failure detection.

  Details of the operation management unit 200 will be described with reference to FIG. In FIG. 2, the operation management unit 200 holds a link aggregation group management table 220, a link aggregation port management table 240, and a network interface unit group management table 260. The operation management unit 200 refers to the link aggregation group management table 220, the link aggregation port management table 240, and the network interface unit group management table 260 to determine the state of the ports belonging to the link aggregation. The operation management unit 200 controls to reduce unnecessary power for the port unit 700 and the network interface unit 40 based on the state of the port.

  Details of each table of the operation management unit 200 will be described with reference to FIGS. 3 to 5. In FIG. 3, the link aggregation group management table 220 includes an LA (Link Aggregation) number 222, a port number 224, and a maximum operating port number 226. The maximum operating port number 226 is a value indicating the maximum number of ports among a plurality of ports belonging to the same link aggregation set by the user in the configuration. The LA number 222 is a value for identifying link aggregation. The port number 224 is a value of the number of ports belonging to the link aggregation.

  The link aggregation port management table 240 will be described with reference to FIG. 4, the link aggregation port management table 240 includes an LA number 242, an NIF (Network Interface) number 244, a port number 246, an LA priority 248, and a port state 250.

  The LA priority 248 is information for determining the priority of a port to be operated from a plurality of link aggregation ports set by the user. The LA priority 248 is information managed on a port basis. The LA number 242 is a value for identifying link aggregation. The NIF number 244 is a value indicating the position of the network interface designated as the link aggregation port. The port number 246 is a value indicating the position of the port. The LA priority 248 is a value indicating the priority in link aggregation of the port. It is assumed that the LA priority 248 has a higher priority as the value is smaller in the link aggregation. The port state 250 indicates the state of the port. The port state 250 is “ACT (active)”, “SBY (standby)”, or “failure”. When “ACT”, the port 700 is in an active state. When “SBY”, the port 700 is in an inactive state. When “Fault”, the port 700 is in a fault state.

  In FIG. 4, it can be seen that both the link aggregation with the LA number 242 of “1” and the link aggregation with the LA number 242 of “2” set the priority of the port with the NIF number 244 “1” high. As a result, any port whose NIF number 244 is “2” is SBY, and the corresponding network interface unit 40 can be set in power saving mode.

  The network interface unit group management table 260 will be described with reference to FIG. In FIG. 5, the network interface unit group management table 260 includes an NIF group number 262, an NIF number 264, an LA ACT port presence / absence 266, and an NIF state 268.

  The network interface unit group management table 260 manages information that makes the network interface unit redundant and the state of the network interface unit. The NIF group number 262 identifies the redundancy group of the network interface unit 40. The NIF number 264 is a value indicating the position of the network interface designated as the link aggregation port. The LA ACT port presence / absence 266 indicates whether there is a link-up port (ACT port) in the link aggregation port on the NIF. The LA ACT port presence / absence 266 takes a value of “present” or “absent”. The NIF state 268 indicates the state of the network interface unit. The NIF state 268 is either “ACT” or “SBY”. In the case of “ACT”, the network interface unit 40 is in an active state. When “SBY”, the network interface unit 40 is in an inactive state.

  Next, the processing flow of the first embodiment will be described with reference to FIGS. In the first embodiment, the packet relay apparatus 10 controls the power supply of the network interface unit 40 by making full use of the group management table 220, the port management table 240, and the group management table 260 and interlocking with the link aggregation port state. .

  The user sets the configuration of the packet relay device 10 in advance in order to make the port unit and the network interface unit redundant. For the ring aggregation setting to make the port part redundant, the LA number that identifies the link aggregation, the NIF number and port number belonging to the LA number, and the maximum number of port parts among the port parts belonging to the LA number are used. It is necessary to have the maximum number of operating ports that determine whether to perform the operation, and the LA priority that determines which port unit is to be kept on standby. In addition, when there are a plurality of link aggregations, it is more effective to match the LA priority to a specific network interface between the link aggregations.

  Note that the setting for making the network interface unit redundant requires an NIF group number for grouping and identifying the network interface unit, and an NIF number that is the number of the network interface unit belonging to the NIF group number.

  The command analysis unit 100 analyzes the configuration information. The command analysis unit 100 notifies the operation management unit 200 of the analysis result, and the processing sequence is started.

  In FIG. 6, the operation management unit 200 reflects the information on the group management table 220, the port management table 240, and the group management table 260 (S101). The operation management unit 200 calculates the number of ports belonging to one LA number from the port management table 240 and records it in the number of ports in the group management table 220. The operation management unit 200 performs the above-described processing for the number of LA numbers (S102).

  The operation management unit 200 calculates, from the group management table 220, the number of port units to be put into standby (hereinafter referred to as standby links) among the port units belonging to the link aggregation, and determines whether all the standby port numbers have been checked. (S103). If YES, the operation management unit 200 jumps to the NIF state determination A subroutine and ends after returning.

  When NO in step 103, the operation management unit 200 determines whether “number of ports−number of active ports> 0” for each LA number from the group management table 220 (S104). When YES, the operation management unit 200 determines that the port management table 240 has a low LA priority for the port number belonging to the LA number, and sets the port state of the port number to standby (port power supply). Off). The operation management unit 200 instructs the hardware control unit 500 to set the port number to standby, and the hardware control unit 500 suppresses the power supply of the corresponding port unit. On the other hand, when step 104 is not applicable (NO), the port status of the port number belonging to the LA number is set to ACT (link up) in the port management table 240 (S106), and the process proceeds to step 103.

  After updating the port state based on the link aggregation configuration, the operation management unit 200 updates the state of the redundant network interface unit. This process will be described with reference to FIG.

In FIG. 7, the operation management unit 200 refers to the port management table 240 to confirm the port status of the port number belonging to the same NIF number. If there is one or more ACTs, the LA ACT in the group management table 260 is checked. Record “Yes” in the presence of port. If there is no ACT, “None” is recorded. (S121)
The operation management unit 200 determines whether or not the group management table 260 has been checked for the presence or absence of ACT ports of LAs belonging to all NIF group numbers (S122). If YES, the operation management unit 200 returns.

  If NO in step 122, it is determined whether the LA ACT port is “present” (S123). If YES, the operation management unit 200 sets the NIF in the operating state, records ACT in the NIF state (S124), and proceeds to step 122. Specifically, when the NIF state of the NIF number is changed from SBY to ACT, the operation management unit 200 instructs the hardware control unit 500 to activate the NIF. Then, ACT is recorded in the NIF state 268 of the group management table 260. If the NIF state is already ACT, nothing is done.

  On the other hand, if the LA ACT port is “None” in step 123 (S123: NO), the operation management unit 200 sets the NIF to standby (NIF power off) and records SBY in the NIF state (S125). , Transition to step 122. Specifically, when changing the NIF state of the NIF number from ACT to SBY, the operation management unit 200 instructs the hardware control unit 500 to stop the power supply of the NIF number. Then, SBY is recorded in the NIF state 268 of the group management table 260. If the NIF state is already SBY, nothing is done.

  Next, processing when a link aggregation port failure occurs in the active network interface unit 40 will be described with reference to FIG. In FIG. 8, the hardware control unit 500 determines whether a failure of a port unit used for link aggregation is detected in the NIF 40 whose NIF state is ACT (S151). When NO, the hardware control unit 500 makes a transition to Step 151 again. When YES in step 151, the hardware control unit 500 notifies the operation management unit 200 of failure information. The operation management unit 200 selects a NIF number with the NIF state SBY from among the NIF numbers belonging to the NIF group number that is the same as the NIF number in the group management table 260, and performs hardware control so that the NIF operates. Command unit 500. If there are a plurality of NIF numbers whose NIF state is SBY, the number with the smallest NIF number is preferentially selected (S152). Thereafter, the operation management unit 200 records the NIF state of the NIF number as ACT.

  The failure of the link aggregation port refers to the hardware failure of the port of the own device specified in the link aggregation or the port of the opposite device, and the LACPDU (Link Aggregation Control Protocol Data Unit) specified by IEEE 802.3ad cannot be received within the specified time. Or when a unidirectional link failure is detected by UDLD (Uni-Directional Link Detection).

  Subsequently, the operation management unit 200 determines whether or not the NIF including the failed port number is set in the configuration when the NIF is set to standby (S153). When YES, the operation management unit 200 instructs the hardware control unit 500 to set the NIF number to standby, and records the NIF state 268 as SBY. Further, the port states of all port numbers on the NIF number are set to SBY (S154), and the process proceeds to step 151. When NO is determined in step 153, the operation management unit 200 determines that only the port state 250 of the port number in which the failure has been detected is a failure (S155), and transitions to step 151.

  According to the first embodiment, the network interface in operation is reduced while reducing standby power in the standby network interface unit by controlling the state of the redundant network interface unit in conjunction with the port state of the link aggregation. If a failure occurs in the network, the standby network interface can be activated to continue communication.

  According to the first embodiment, in a packet relay device configured by a plurality of link aggregations connected to a plurality of redundant network interface units, a packet relay device for controlling standby power of a standby network interface unit is provided. Can do.

  A second embodiment will be described with reference to FIGS. 9 to 18. In the second embodiment, the packet relay apparatus 10 uses a total traffic volume management table 280, a port traffic volume management table 300, a traffic volume upper limit management table 320, and a group management table 340, which will be described later, and traffic in link aggregation. The port unit 700 and the network interface unit 40 are controlled to shift to an optimal state by interlocking with the change in the amount.

  First, the operation management unit 200A according to the second embodiment will be described with reference to FIG. In FIG. 9, the operation management unit 200A holds a link aggregation total traffic volume management table 280, a link aggregation port traffic management table 300, a link aggregation traffic volume upper limit management table 320, and a network interface unit group management table 340. To do. The operation management unit 200A refers to the link aggregation total traffic volume management table 280, the link aggregation port traffic management table 300, the link aggregation traffic volume upper limit value management table 320, and the network interface unit group management table 340. As the amount changes, the ACT / SBY of the port unit 700 and the network interface unit 40 is switched.

  With reference to FIG. 10, the link aggregation total traffic amount management table 280 will be described. In FIG. 10, the total traffic volume management table 280 includes an LA number 282, a port number 284, an LA total traffic volume 286, and an LA threshold 288.

  The LA number 282 is a value for identifying link aggregation. The port number 284 is the value of the number of ports belonging to the link aggregation. The LA total traffic volume 286 is a total value of the traffic volume of each port belonging to the LA number. The LA threshold 288 is a threshold for the LA number.

  When the traffic volume of link aggregation increases, it is necessary to link up the number of ports waiting and increase the number of ports. At this time, since the line bandwidth becomes the upper limit, there is a high possibility of packet discard. Therefore, even if the number of ports belonging to link aggregation is changed, the LA threshold 288 is used as means for reducing packet discard. The unit of the LA total traffic volume 286 is Mbit / sec. The unit of the LA threshold 288 is%.

  Next, the port traffic volume management table 300 for link aggregation will be described with reference to FIG. In FIG. 11, a link aggregation port traffic volume management table 300 manages the traffic volume in units of ports. The link aggregation port traffic volume management table 300 includes an LA number 302, an NIF number 304, a port number 306, a traffic volume 308, and a port status 310.

With reference to FIG. 12, the upper limit management table 320 of the traffic amount according to the number of ports will be described. In FIG. 12, the traffic volume upper limit management table 320 includes a port number 322 and an LA total traffic volume upper limit 324 for each LA number. The port number 322 indicates the number of ports belonging to the LA and in ACT. The upper limit value 324 of the LA total traffic amount is calculated from the number of ports, the line bandwidth of the port portion, and the corresponding LA threshold value. The traffic volume upper limit management table 320 is used to determine the optimum number of ports based on the traffic volume.
In FIG. 12, only LA number 1 is shown.

  The group management table 340 of the network interface unit will be described with reference to FIG. The group management table 340 of the network interface unit manages information on the redundant network interface unit. In FIG. 13, the group management table 340 of the network interface unit includes an NIF group number 342, an NIF number 344, an NIF priority 346, an LA ACT port presence / absence 348, and an NIF state 350. The NIF priority 346 is a priority of a plurality of redundant network interface units. The NIF priority 346 has a higher priority as the value is smaller.

  The link aggregation port traffic volume management table 300A in FIG. 14 and the network interface group management table 340A in FIG. 15 are different states of the port traffic volume management table 300 and the group management table 340, respectively.

  Next, with reference to FIG. 16, a description will be given of a processing flow for determining the port state and NIF state of the operation management unit 200A. As a premise, the user sets the configuration of the device in order to make the port part and the network interface part redundant. For setting the ring aggregation for making the port part redundant, the LA number for identifying the link aggregation, the NIF number and port number belonging to the LA number, and the threshold for the total LA traffic amount are required. The purpose of the threshold of the total LA traffic volume is to reduce packet loss due to a change in the number of ports belonging to link aggregation. When the traffic volume tends to increase, if the line bandwidth is set as the upper limit, there is a possibility that packets will be discarded until the standby port is put into operation. In order to avoid this situation, a bandwidth smaller than the line bandwidth can be set as a threshold value, and operation with a sufficient bandwidth is enabled.

  In addition, for setting the network interface unit to be redundant, the NIF group number that identifies the network interface unit as a group, the NIF number that is the number of the network interface unit belonging to the NIF group number, and which network interface unit is made to wait NIF priority is required to decide whether or not.

  The command analysis unit 100 performs analysis on these configuration information. The command analysis unit 100 starts the flow by notifying the operation management unit 200A of the analysis result. The operation management unit 200A reflects the information on the total traffic volume management table 280, the port traffic volume management table 300, and the group management table 340 (S201).

  The operation management unit 200 </ b> A calculates the number of ports belonging to one LA number from the port traffic volume management table 300 and records the number of ports in the total traffic volume management table 280. The operation management unit 200A performs the above-described processing for the number of LA numbers (S202). The operation management unit 200A executes an LA total traffic volume upper limit calculation subroutine (S220). The operation management unit 200A determines whether a certain time has elapsed when returning (S203). When YES, the operation management unit 200A records the collected traffic volume for each port number in the port traffic volume management table 300 (S204). The operation management unit 200A records the total traffic volume of the port numbers belonging to each link aggregation number in the LA total traffic volume of the total traffic volume management table 280 (S205). The operation management unit 200A executes a port state determination subroutine (S240). When returning, the operation management unit 200A executes the NIF state determination A subroutine (S120A). When returning, the operation management unit 200 </ b> A transitions to step 203.

  With reference to FIG. 17, a subroutine for calculating the upper limit value of the LA total traffic amount will be described. In FIG. 17, the operation management unit 200A determines whether the number of ports in the total traffic amount management table 280 is greater than 0 (S221). When YES, the operation management unit 200A calculates the upper limit value of the LA total traffic amount according to the number of ports in (Equation 1) based on the LA threshold set by the user.

Upper limit value of total LA traffic volume = line bandwidth × number of ports × LA threshold value (Expression 1)
The operation management unit 200A records the calculated upper limit value to the LA total traffic volume upper limit value 324 corresponding to the corresponding number of ports in the traffic volume upper limit management table 320 (S222). The operation management unit 200A decreases the number of ports by 1 (S223), and executes Step 221 again. If NO in step 221, the process returns. Although omitted for simplicity of illustration, the above processing is performed for all the LA numbers, and the process returns.

  With reference to FIG. 18, the subroutine for determining the state of the port section will be described. In FIG. 18, the operation management unit 200A calculates, for each link aggregation number, which number of ports in the traffic volume upper limit management table 320 the LA total traffic volume of the total traffic volume management table 280 becomes (S241). This number of ports is called the optimum number of ports. Next, the operation management unit 200A acquires the number of currently operating ports (S242). This number of ports is called the number of active ports. The operation management unit 200A determines whether the number of operating ports matches the optimal number of ports (S243). If they do not match (NO), the operation management unit 200A further determines whether the number of active ports is larger than the optimum number of ports (S244). If larger (YES), the operation management unit 200A waits (powers off) the port on the NIF number with the lower NIF priority in the group management table 340, sets the port state to SBY (S245), and proceeds to step 242.

On the other hand, if the number of active ports is small in step 244 (NO), the operation management unit 200A operates (powers on) the port on the NIF number having a high NIF priority in the group management table 340, and sets the port state as ACT ( S246), the process proceeds to step 242. In step 242, if the number of active ports matches the optimal number of ports (YES), the operation management unit 200A returns as it is.
It should be noted that the power supply of the port unit 700 is turned on / off by the hardware control unit 500 according to an instruction from the operation management unit 200A.

  In the NIF state determination A subroutine (S120A) of FIG. 16, the port management table 240 of the NIF state determination A subroutine (S120) of FIG. 7 is replaced with the port traffic management table 300, and the group management table 260 is replaced with the group management table 340. Is.

  According to this embodiment, the standby power of the standby network interface unit is controlled in accordance with the change in the traffic amount in the packet relay apparatus configured by a plurality of link aggregations connected to the plurality of redundant network interface units. A packet relay device can be provided.

  A third embodiment will be described with reference to FIGS. In the third embodiment, the operation management unit 200B of the packet relay apparatus 10 uses a port inspection status management table 400 and a group management table 420 described later, and the hardware control unit 500 makes full use of the inspection result management table 520 and the inspection reference table 540. In order to reduce the communication interruption time due to the occurrence of intermittent (called intermittent) failures in the operational system port unit, the port unit and the network interface unit are controlled to shift to the optimum state.

  First, details of the operation management unit 200B will be described with reference to FIG. In FIG. 19, the operation management unit 200B holds a link aggregation port inspection status management table 400 and a network interface unit group management table 420. The operation management unit 200B refers to the link aggregation port inspection status management table 400 and the network interface unit group management table 420 to determine the state of the ports belonging to the link aggregation.

  Details of the hardware control unit 500 will be described with reference to FIG. In FIG. 20, the hardware control unit 500 holds an inspection result management table 520 and an inspection reference table 540. The hardware control unit 500 refers to the inspection standard table 540, reads the state of the hardware unit corresponding to the inspection item, and manages the state result in the inspection result management table 520.

  With reference to FIG. 21, the link aggregation port inspection status management table 400 will be described. In FIG. 21, a link aggregation port inspection status management table 400 manages the quality inspection status of each port. Therefore, the port inspection status management table 400 includes an LA number 402, an NIF number 404, a port number 406, a port status 408, and an inspection status 410. The inspection status 410 records “completed” or “not yet” indicating whether or not the inspection is performed.

  The group management table 420 of the network interface unit will be described with reference to FIG. In FIG. 22, the group management table 420 of the network interface unit manages information on the redundant network interface unit. Therefore, the group management table 420 includes an NIF group number 422, an NIF number 424, an NIF priority 426, an unstable port presence / absence 428, and an NIF state 430. The NIF priority 426 indicates the priority of a plurality of redundant network interface units. The unstable port presence / absence 428 indicates whether there is a port portion that cannot ensure stable quality.

  The inspection result management table 520 will be described with reference to FIG. 23, the inspection result management table 520 includes inspection items 522, actual measurement values 524, the number of occurrences 526, and inspection results 528. The inspection item 522 is used for quality determination. The actual measurement value 524 indicates the actual measurement value for the inspection item. The number of occurrences 526 indicates the number of times the actual measurement result is determined to be abnormal. The inspection result 528 is a result determined from a comparison with the inspection standard table 540. FIG. 23 shows only NIF number 1 and port number 1.

  The inspection standard table 540 will be described with reference to FIG. In FIG. 24, the inspection standard table 540 includes inspection items 542, normal values 544, and allowable occurrence counts 546. The inspection item 542 is the same as the inspection item 522 in FIG. A normal value 544 indicates a normal reference range of the inspection item. The allowable number of occurrences 546 indicates the number of times that can be permitted outside the range of the normal value. Note that the inspection item 542, the normal value 544, and the allowable number of occurrences 546 can be changed by the user by configuration or the like as necessary.

  The processing flow will be described with reference to FIG. In FIG. 25, as a premise, the user sets the configuration of the device in order to make the port unit and the network interface unit redundant. For setting the ring aggregation for making the port part redundant, the LA number for identifying the link aggregation, the NIF number belonging to the LA number, and the port number are required. In addition, for setting the network interface unit to be redundant, the NIF group number that identifies the network interface unit as a group, the NIF number that is the number of the network interface unit belonging to the NIF group number, and which network interface unit is made to wait NIF priority is required to decide whether or not. Further, the inspection item for judging the quality of the port part, the normal value for the item and the allowable number of occurrences are set as necessary.

  The command analysis unit 100 performs analysis on these configuration information. The command analysis unit 100 notifies the operation management unit 200B about the LA number, NIF number, port number, NIF group number, and NIF priority. Further, the command analysis unit 100 notifies the hardware control unit 500 about the inspection item, normal value, and allowable number of occurrences. With these notifications, the processing flow is started, and the operation management unit 200B and the hardware control unit 500 reflect the information on the port inspection status management table 400, the group management table 420, and the inspection reference table 540, respectively (S301).

  Subsequently, the operation management unit 200B determines whether a certain time has elapsed (S302). If NO, the operation management unit 200B returns to Step 302. When YES in step 302, the operation management unit 200B executes a quality inspection subroutine for all the port units (S320). After returning from the quality inspection subroutine, the operation management unit 200B executes a subroutine for determining the state of the network interface unit based on the inspection result (S340). After returning from the NIF state determination subroutine, the operation management unit 200B transitions to step 302.

  With reference to FIG. 26, the processing flow of the quality inspection for the port unit will be described. In FIG. 26, the operation management unit 200B sets all the inspection status 410 columns of the port inspection status management table 400 to be unexecuted (S321). The operation management unit 200B determines from the port inspection status management table 400 and the group management table 420 whether the inspection status 410 for the port number 406 is not executed and the NIF state 430 to which the port number belongs is ACT (S322). . When both conditions are satisfied (YES), the operation management unit 200B requests the hardware control unit 500 to inspect the quality of the port unit. The hardware control unit 500 reads hardware information corresponding to each inspection item 522 of the inspection result management table 520 and records the information in the actual measurement value 524 (S323). If the actual value 524 for each inspection item 522 in the inspection result management table 520 is outside the range of the normal value 544 in the inspection reference table 540, the hardware control unit 500 increments the number of occurrences 526 by 1 (S324). The hardware control unit 500 determines whether the number of occurrences 526 is greater than the allowable number of occurrences 546 (S325). If YES, the hardware control unit 500 records an abnormality in the inspection result 528 (S326).

  If it is within the allowable number of occurrences in step 325 (NO), the hardware control unit 500 records normality in the inspection result 528 (S327). Subsequent to step 326 or step 327, the hardware control unit 500 confirms all the inspection results 528 for the inspection item 522, and if there is any abnormality, it indicates that the inspection result for the port is abnormal. If there is, it notifies the operation management unit 200B that it is normal. The operation management unit 200B records a failure in the port state 408 of the port inspection status management table 400 if the received inspection result is abnormal, and records ACT if the inspection result is normal (S328). Finally, the operation management unit 200B records the inspection status 410 of the port number as completed (S329). A series of these processes are performed for all the port units, and when all the inspection statuses 410 in the port inspection status management table 400 are completed (S322: NO), the processing ends and returns.

  With reference to FIG. 27, a processing flow for determining the state of the redundant network interface unit 40 will be described. In FIG. 27, the operation management unit 200B confirms the port status of the port number belonging to the same NIF number from the port inspection status management table 400, and if there is one or more failures, the presence or absence of unstable ports 428 in the group management table 420 Record “Yes”. If there is no failure, “None” is recorded (S341). The operation management unit 200B determines whether there is “present” in the unstable port presence / absence 428 (S342). When YES, the operation management unit 200B activates the NIF number 424 having the highest NIF priority 426 and the NIF state 430 of SBY among the NIFs having the same NIF group number 422 as the NIF number 424, and ACT is recorded in the NIF state 430 (S343). Subsequently, the operation management unit 200B determines whether the NIF including the faulty port number is set in the configuration when the NIF is set to standby (S344). When YES, the operation management unit 200B instructs the hardware control unit 500 to set the NIF number 424 to standby, and records SBY in the NIF state 430. Further, the port status 408 of all the port numbers on the NIF number is set to SBY except for the failure (S345). If the NIF number including the failed port number is not set to standby in step 344 (NO), the operation management unit 200B ends the process and returns. If NO in step 342, the operation management unit 200B ends the process and returns.

  According to this embodiment, the communication disconnection time can be shortened by suppressing the start and stop of the standby network interface unit due to the intermittent port failure in the port unit of the active network interface unit.

  The fourth embodiment is a method of waiting or starting a redundant network interface unit at a date and time specified by a schedule by combining with a schedule function that activates an operation at a user specified date and time as a prior art. For the standby network interface unit, as in the case of steps 151 to 155 shown in FIG. 8, when a failure occurs in the active network interface unit, the standby network interface unit is activated to ensure communication continuity. To do.

  A fifth embodiment will be described with reference to FIGS. The fifth embodiment has a configuration in which the packet relay device 10 monitors the connection state of the link aggregation using a protocol in connection with the opposite packet relay device 10. Here, LACP (Link Aggregation Control Protocol) defined in IEEE802.3ad is used as a protocol.

  With reference to FIG. 28, the operation management unit 200C of the fifth embodiment will be described. In FIG. 28, the operation management unit 200C of the packet relay apparatus 10 includes a link aggregation group management table 220, a link aggregation port management table 240, a network interface unit group management table 260, and a link aggregation state management table 380. The operation management unit 200C uses these tables 220, 240, 260, and 380 to control the power supply of the network interface unit 40 in conjunction with the link aggregation port state and LACP state.

  The link aggregation state management table 380 will be described with reference to FIG. In FIG. 29, the link aggregation state management table 380 includes an NIF number 382, a port number 384, and an LACP state 386. The LACP state 386 indicates a link connection state between the packet relay device 10 and the opposite device. The LACP state 386 takes values of “established” indicating that packet communication is possible and “not established” indicating that packet communication is not possible.

  In order to make the port unit 700 and the network interface unit 40 redundant, the user sets the configuration of the packet relay device 10 in advance. The ring aggregation for making the port unit 700 redundant requires setting of the LA number, the NIF number and port number belonging to the LA number, the maximum number of operating ports, the LA priority, and the LACP mode.

  Here, the LA number specifies link aggregation. The maximum number of operating ports is the maximum number of port parts that belong to the LA number. The LA priority determines which port part is made to wait. The LACP mode is “ACTIVE mode” or “PASSIVE mode”. In the ACTIVE mode, LACPDU is transmitted regardless of the state of the opposite device. In the PASSIVE mode, the LACPDU is transmitted only when the LACPDU is received from the opposite device.

  In addition, when there are a plurality of link aggregations, it is more effective to match the LA priority with a specific network interface unit 40 between the link aggregations. Further, the setting for making the network interface unit 40 redundant requires an NIF group number for grouping and identifying the network interface units, and an NIF number that is the number of the network interface unit belonging to the NIF group number.

  The command analysis unit 100 analyzes the configuration information. The command analysis unit 100 notifies the operation management unit 200C of the analysis result. As a result, the operation management unit 200C starts the processing sequence of FIG.

  In FIG. 30, the operation management unit 200C reflects the information on the group management table 220, the port management table 240, and the group management table 260 (S101A). The operation management unit 200C calculates the number of ports belonging to one LA number from the port management table 240 and records it in the number of ports 224 of the group management table 220. The operation management unit 200C performs the above-described processing for the number of LA numbers (S102A).

  The operation management unit 200C calculates the number of standby standby links among the port units belonging to the link aggregation from the group management table 220, and determines whether all the standby port numbers have been checked (S103A). If YES, the operation management unit 200C jumps to the NIF state determination C subroutine, and ends after returning.

  When NO in step 103A, the operation management unit 200C determines whether “number of ports−number of active ports> 0” for each LA number from the group management table 220 (S104A). When YES, the operation management unit 200C determines in the port management table 240 that a numerical value with a large LA priority of the port number belonging to the LA number is low priority, and sets the port state of the port number to standby (port power supply). Off). The operation management unit 200C instructs the hardware control unit 500 to set the port number to standby, and the hardware control unit 500 suppresses the power supply of the corresponding port unit (S105A). On the other hand, if step 104A is not applicable (NO), the port status of the port number belonging to the LA number is set to ACT (link up) in the port management table 240 (S106A), and the process proceeds to step 103A.

  After updating the port state based on the configuration of the link aggregation, the operation management unit 200C updates the state of the redundant network interface unit 40 (S400). This process will be described with reference to FIG.

In FIG. 31, the operation management unit 200C refers to the port management table 240 to check the port state of the port number belonging to the same NIF number. If there is one or more ACTs, the LA ACT in the group management table 260 is checked. Record “Yes” in the presence of port. If there is no ACT, “None” is recorded. (S401)
The operation management unit 200C determines whether the group management table 260 has been checked for the presence or absence of the ACT port of the LA belonging to all NIF group numbers (S402). If YES, the operation management unit 200C returns.

  If NO in step 402, it is determined whether the LA ACT port is “present” (S403). If YES, the operation management unit 200C sets the NIF in the operating state, records ACT in the NIF state (S404), and proceeds to step 402. Specifically, when the NIF state of the NIF number is changed from SBY to ACT, the operation management unit 200C instructs the hardware control unit 500 to activate the NIF. Then, ACT is recorded in the NIF state 268 of the group management table 260. If the NIF state is already ACT, nothing is done.

  On the other hand, if the LA ACT port is “None” in step 403 (S403: NO), the operation management unit 200C calls a LACP state confirmation subroutine for confirming the LACP state (S410). After the return, the operation management unit 200C determines whether the LACP state is established (S405). When YES, the operation management unit 200C sets the NIF in standby (NIF power off), records SBY in the NIF state (S406), and proceeds to step 402. Specifically, when changing the NIF state of the NIF number from ACT to SBY, the operation management unit 200 instructs the hardware control unit 500 to stop the power supply of the NIF number. Then, SBY is recorded in the NIF state 268 of the group management table 260. If the NIF state is already SBY, nothing is done. If the LACP state is not established in step 405 (S405: NO), the operation management unit 200C transitions to step 402.

  When the link state with the opposite device is monitored using LACP, if LACP is not established, the port is in a state where packet communication cannot be performed even if the port is ACT (link up). With reference to FIG. 32, the LACP state confirmation process for avoiding such a state will be described.

  In FIG. 32, the operation management unit 200C checks all the LACP states of NIF numbers belonging to the same NIF group number as the NIF number scheduled to be changed to SBY in the network interface unit group management table 260 (S411). When step 411 is YES, the operation management unit 200C establishes the LACP state (S412) and returns.

  On the other hand, when step 411 is NO, the operation management unit 200C checks whether there is an NIF whose NIF state is ACT in the NIF group number other than the NBY scheduled NIF from the network interface unit group management table 260 (S413). ). When YES, the operation management unit 200C confirms the NIF state of each NIF number (S414). When step 414 is YES, the operation management unit 200 </ b> C searches the link aggregation port management table 240 for the port number of the ACT whose port status belongs to the NIF number, and then the NIF number in the link aggregation status management table 380. The LACP state corresponding to the port number is confirmed (S415). When the LACP state is established (S416: YES), the operation management unit 200C makes a transition to Step 411. When step 416 is NO, the operation management unit 200C determines that the LACP state is not established (S417), and returns. When step 413 is NO, the operation management unit 200C transitions to step 417. When step 414 is NO, the operation management unit 200C transitions to step 414.

  With reference to FIG. 33, processing when the packet relay apparatus 10 receives a LACPDU from the opposite apparatus will be described. In FIG. 33, the operation management unit 200C sets the LACP state of the link aggregation state management table 380 corresponding to the NIF number and port number that received the LACPDU to establishment (S420). The operation management unit 200C confirms whether the LACP state has been changed from unestablished to established (S421). When YES, the operation management unit 200C executes the NIF state determination C subroutine (S400), and ends after returning. When step 421 is NO, the operation management unit 200C ends the process as it is.

  According to the present embodiment, when LACP is used in link aggregation across redundant network interface units, a network that waits after establishing LACP in the operational network interface unit to guarantee continuity of communication. The power supply for the interface unit is stopped to save power. According to the present embodiment, it is possible to avoid a case where communication is interrupted when the power supply of the network interface unit used for communication in the standby system is stopped only by the link up trigger in the active network interface unit.

  Example 6 will be described with reference to FIGS. 34 to 39. FIG. In the sixth embodiment, the operation management unit 200D of the packet relay apparatus 10 makes full use of the link aggregation port management table 240A, the network interface unit failure criterion table 440, and the network interface unit group management table 460, and the active network interface unit and port unit. In accordance with the state of occurrence of the failure in the network, control is performed without stopping the power supply of the standby network interface unit.

  First, the operation management unit 200D will be described with reference to FIG. In FIG. 34, the operation management unit 200D holds a link aggregation port management table 240A, a network interface unit failure criterion table 440, and a network interface unit group management table 460. The operation management unit 200D refers to the link aggregation port management table 240A and the network interface unit group management table 460 to determine the state of the port belonging to the link aggregation and the state of the network interface unit to which the port belongs.

  The link aggregation port management table 240A will be described with reference to FIG. In FIG. 35, the link aggregation port management table 240A includes an LA number 242A, an NIF number 244A, a port number 246A, an LA priority 248A, and a port state 250A. Each item is the same as that described in FIG. The only difference from FIG. 4 is the port state 250A.

  The failure criterion management table 440 of the network interface unit will be described with reference to FIG. In FIG. 36, the network interface unit failure criterion management table 440 manages the response criterion at the time of NIF failure. For this reason, the network interface unit failure criterion management table 440 includes a retry count 442 and an NIF failure allowable occurrence count 444. The retry count 442 specifies how many times the NIF restart process (hereinafter referred to as retry) is performed as a recovery measure when a failure occurs in the NIF. The NIF failure allowable occurrence count 444 defines how many NIF failures are allowed.

  The group management table 460 of the network interface unit will be described with reference to FIG. In FIG. 37, the group management table 460 of the network interface unit manages information on the redundant network interface unit. Therefore, the group management table 460 includes an NIF group number 462, an NIF number 464, an NIF priority 466, an NIF state 468, the number of NIF failures 470, and an NIF failure 472.

  The NIF priority 426 indicates the priority of a plurality of redundant network interface units. The NIF failure frequency 470 is an item indicating the number of NIF failures. When the failure is not recovered even if the number of times indicated in the retry count 442 is implemented, the NIF failure frequency 470 is determined as an NIF failure and the number of NIF failure times 470 is increased. The NIF failure 472 is an item for managing whether the NIF failure frequency 470 exceeds the NIF failure allowable frequency 444. The NIF failure 472 records “1” when the NIF failure frequency 470 exceeds the NIF failure allowable frequency 444.

  With reference to FIG. 38, a control processing flow of the redundant NIF accompanying the NIF failure recovery of the operation management unit 200D will be described. In FIG. 38, as a premise, the user sets the configuration of the device in order to make the port unit and the network interface unit redundant. For setting ring aggregation for making the port part redundant, it is necessary to specify the LA number, the NIF number and port number belonging to the LA number, and the LACP mode when LACP is used.

  Here, the LA number specifies link aggregation. The LACP mode specifies either the ACTIVE mode or the PASSIVE mode. In the ACTIVE mode, LACPDU is transmitted regardless of the state of the opposite device. In the PASSIVE mode, the LACPDU is transmitted only when the LACPDU is received from the opposite device.

  In addition, the NIF group number, the NIF number, the NIF priority, and the maximum number of operating NIFs are required for setting the network interface unit to be redundant.

The NIF group number identifies the network interface unit as a group. The NIF number is the number of the network interface unit belonging to the NIF group number. The NIF priority determines from which network interface unit to wait. The maximum number of operating NIFs determines the maximum number of grouped network interface units to operate.
Furthermore, the number of NIF failure retries and the allowable number of NIF failures that determine the failure criteria of the network interface unit are set as necessary.

  The command analysis unit 100 performs analysis on these configuration information. The command analysis unit 100 notifies the operation management unit 200D of the LA number, NIF number, port number, LACP mode, NIF group number, NIF priority, maximum number of active NIFs, NIF failure retry count, and NIF failure allowable occurrence count. . With these notifications, the processing flow of FIG. 38 is started. In FIG. 38, the operation management unit 200D reflects the information on the link aggregation port management table 240A, the network interface unit failure criterion table 440, and the network interface unit group management table 460 (S450).

  Subsequently, the operation management unit 200D monitors whether the failed NIF has been recovered (S451). When NO, the operation management unit 200D returns to Step 451. Note that the step 451 is realized by periodic processing for a fixed time, interrupt notification from the hardware control unit 500, or the like. When YES in step 451, the operation management unit 200D executes a subroutine for determining the state of the network interface unit (S460). After returning from the NIF state determination subroutine, the operation management unit 200D proceeds to step 460.

  With reference to FIG. 39, a processing flow for determining the state of the redundant network interface unit 40 will be described. 39, the operation management unit 200D determines that the NIF number 464 in which the number of NIF failures 470 exceeds the number of allowable NIF failures 444 in the NIF group number 462 to which the NIF number 464 restored from the network interface unit group management table 460 belongs. In response to this, “1” is recorded in the NIF failure 472 (S461). The operation management unit 200D counts the number of NIFs whose NIF state 468 is ACT and compares whether the number of NIFs in ACT is larger than the maximum number of active NIFs (S462). When the result is YES, the operation management unit 200D substitutes the number in which the NIF failure 472 is “1” in the NIF number 464 of the ACT in the NIF state 468 into ERR_NIF_NUM (S463). The operation management unit 200D determines whether ERR_NIF_NUM is greater than 0 (S464). If YES, the operation management unit 200D determines whether the difference between the ACT NIF number and the ERR_NIF_NUM is larger than the maximum operating NIF number (S465). When the difference is larger than 0 (S465: YES), the operation management unit 200D waits for the NIF having the lowest NIF priority 466 among the NIFs other than the NIF failure 474 of “1”, and the NIF state of the NIF number 464 Record 468 as SBY and return. When step 465 is NO, the operation management unit 200D returns as it is.

  When step 462 is NO, the operation management unit 200D determines whether the ACT NIF number is smaller than the maximum operating NIF number (S467). When YES, the operation management unit 200D determines that the NIF number 464 of the same NIF group number 462 has an NIF state 468 other than SBY and the NIF failure 472 has a NIF other than “1”. Then, the NIF number 464 having the highest NIF priority 466 (the smallest number) is activated, ACT is recorded in the NIF state 468 of the NIF number 464 (S468), and the process returns. When step 467 is NO, the operation management unit 200D returns without doing anything.

  When step 464 is NO, the operation management unit 200D waits for the NIF having the lowest NIF priority 466 in the NIF number 464 of the ACT in the NIF state 468, and records SBY in the NIF state 468 of the NIF number 464. (S469) and return.

  According to this embodiment, a network interface unit that exceeds the specified allowable number of NIF failures is not treated as a working network interface unit, so that power is saved even if an intermittent failure occurs in the network interface unit. The communication interruption time can be shortened while realizing the above.

  In addition, it can be combined with the fifth embodiment by setting the NIF failure when the failure of the port section exceeds the specified allowable number of times from the handling flow for the occurrence of an intermittent failure in the port section shown in the third embodiment. .

  DESCRIPTION OF SYMBOLS 10 ... Packet relay apparatus, 20 ... Device control part, 30 ... Packet transfer part, 40 ... Network interface part, 50 ... Network, 100 ... Command analysis part, 200 ... Operation management part, 220 ... Link aggregation group management table, 240 ... Link aggregation port management table, 260 ... Network interface unit group management table, 280 ... Link aggregation total traffic volume management table, 300 ... Link aggregation port traffic volume management table, 320 ... Link aggregation group total traffic volume upper limit management table, 340 ... Network interface unit group management table, 380... Link aggregation status management table, 400... Port inspection status management table, 4 DESCRIPTION OF SYMBOLS 0 ... Network interface part group management table, 440 ... Network interface part failure standard table, 460 ... Network interface part group management table, 500 ... Hardware control part, 520 ... Inspection result management table, 540 ... Inspection standard table, 700 ... Port Department.

Claims (10)

A packet relay device,
A plurality of redundant control units;
A plurality of redundant packet transfer units;
A plurality of redundant network interface units connected to at least one of the packet transfer units,
The packet transfer unit determines a relay destination from header information of a packet received via any of the plurality of network interface units, and transfers the packet to any of the plurality of network interface units;
Each of the network interface units has a plurality of ports,
A packet relay device, wherein at least one network interface unit among a plurality of redundant network interface units is set in a standby state based on the status of the plurality of ports. The packet relay device according to claim 1,
The network interface unit is set to be in a standby state when each of a plurality of port states of the network interface unit is in a standby state. The packet relay device according to claim 1,
Provide link aggregation to be handled as one virtual line by multiple ports of different network interface units made redundant,
The control unit determines a port to be waited among the ports constituting the link aggregation, determines whether there is an operating port belonging to each redundant network interface unit based on the status of the port, and A packet relay device, wherein when there is no port in operation in the network interface unit, the first network interface unit is set to standby. The packet relay device according to any one of claims 1 to 3,
The packet relay device, wherein the control unit activates the first network interface unit set during standby under a predetermined condition. The packet relay device according to any one of claims 1 to 4, wherein
The packet relay apparatus according to claim 1, wherein the control unit controls starting and stopping of the redundant network interface unit at a designated date and time. A packet relay device according to any one of claims 1 to 5,
When the control unit detects a failure in the second network interface unit in operation,
Starting the first network interface unit that is in standby, and performing a process of changing the failed port or the second network interface unit to standby for the second network interface unit in which a failure has occurred A packet relay device characterized. The packet relay device according to any one of claims 1 to 6,
A packet relay device that changes a setting of a network interface unit during operation or standby based on a traffic state. The packet relay device according to any one of claims 1 to 7,
The packet relay device, wherein the control unit sets power supply corresponding to each of the network interface unit during operation and standby. In packet relay devices connected to multiple networks,
A plurality of network interface units for transmitting and receiving packets to and from the network;
A packet transfer unit that determines a relay destination from header information of a packet received via any of the plurality of network interface units, and transfers the packet to any of the plurality of network interface units;
A control unit for controlling the packet transfer unit and the network interface unit,
The network interface unit includes a plurality of port units that connect physical network lines, and uses a plurality of link aggregations that treat each port unit of a plurality of redundant network interface units as one virtual line. And
The control unit is configured to make the plurality of network interface units redundant, and among the port units constituting a link aggregation that handles each port unit of the plurality of redundant network interface units as one virtual line. The first network interface is determined when the port unit to be determined is determined, the presence / absence of an operating port unit belonging to each redundant network interface unit is determined, and when there is no operating port unit in the first network interface unit A packet relay device characterized in that the unit is set to standby. The packet relay device according to claim 9, wherein
The control unit activates the first network interface unit set during standby under a predetermined condition,
When the control unit detects a failure in the second network interface unit in operation,
When a failure is notified from the hardware control unit, the first network interface unit in standby is activated, and the failed port unit or the second network interface unit is connected to the second network interface unit in which the failure has occurred. A packet relay apparatus, wherein the network interface unit is changed to a standby state.

Images