JP2010268342A - Network equipment - Google Patents

Abstract

A power saving operation of a complex and large-scale network is automatically realized.
When a device stop notification is received via a device for exchanging device information with a neighboring device and a neighboring device, the device is set to a power saving shiftable mode, and the device stop notification is sent to another neighboring device. Means for transferring to the device, and means for determining whether the own device is a device capable of shifting to the power saving mode from the device information of the own device and neighboring devices when the own device is in the power saving mode. When it is determined that the device can shift to the power saving mode, the device shifts to the power saving mode when a device stop release notification is received via the adjacent device and a means for shifting the device to the power saving mode. And a unit for setting the disabled mode and transferring the device stop cancellation notification to another adjacent device.
[Selection] Figure 1

Description

  The present invention relates to a power saving operation technique for a network device such as a router or a switch used as a component of an IP (Internet Protocol) network or the like.

  In recent years, companies have used networks for various purposes such as production / production line control, collection / propagation of various management control data, document sharing for communication, and mail use (see, for example, Patent Document 1). ). A small-scale network scattered across a plurality of activity bases and a large number of floors / departments is connected to each other to form a complex and large-scale configuration.

  In addition, there is a high demand for performance and reliability for such a network, and high-performance network devices are arranged in a hierarchy, and a redundant configuration is often used in order to avoid a business stop due to a failure.

  A network device used as a component of such a network has high power consumption because of non-stop operation. For this reason, from the viewpoint of contributing to society by reducing CO2 and acquiring a corporate image of an eco-brand, there is a strong need to reduce power consumption and reduce running costs.

Japanese Patent Laid-Open No. 10-93547

  However, it is difficult to use these functions safely and reliably, even if the network products have standby operation functions based on scheduling and traffic volume due to the uneven usage time due to network configuration and business. .

  In addition, the network management system can grasp the latest network configuration and power-saving operation of the network device by remote control, but since advanced management skills are required and the operator must always stick and respond, It does not lead to cost reduction.

  Due to these problems, the case where the standby operation function based on scheduling and traffic volume is practically used is limited to a small-scale network in which operation can be fixed.

  In view of the above-described conventional problems, an object is to provide a network device that can automatically realize power-saving operation of a complex and large-scale network.

  In one embodiment of this network device, when receiving the device stop notification via the adjacent device and the means for exchanging device information with the adjacent device, the own device is set to the power saving transition possible mode and the device is stopped. Whether the device is a device capable of shifting to the power saving mode from the device information of the device and the neighboring device when the notification device is transferred to another neighboring device and the device is in the power saving mode. If the device is determined to be a device that can be shifted to the power saving mode, the device is configured to shift the own device to the power saving mode, and the device stop release notification is received via the adjacent device, And a unit for setting the device to the power saving transition impossible mode and transferring the device stop cancellation notification to another adjacent device.

  In the disclosed network device, information for determining whether or not the own device can perform power saving operation is automatically collected, and each network device autonomously uses the information to autonomously operate in power saving mode. Switch to. As a result, it is possible to safely and reliably perform advanced network power-saving operation and to eliminate the need for maintenance operator intervention.

It is a figure which shows the structural example of the network apparatus concerning one Embodiment. It is a figure which shows the example of a data structure of own apparatus information and adjacent apparatus information. It is a flowchart which shows the process example of a network apparatus. It is a figure which shows the example of a format of the hierarchy information request | requirement (own apparatus) using ARP. It is a flowchart which shows the example of the confirmation process of the hierarchy information of a transmission origin. It is a flowchart which shows the example of the confirmation process of a mode state. It is a flowchart which shows the example of the process at the time of a port link down. It is a flowchart which shows the example of the process at the time of a port link up. It is a figure which shows the example of a format of the apparatus stop notification using ARP, and an apparatus stop cancellation notification. It is a flowchart which shows the example of an apparatus stop notification process. It is a flowchart which shows the example of an apparatus stop cancellation | release notification process. It is a network block diagram in the 1st operation example. It is a processing sequence figure in the 1st example of operation. It is a figure which shows the own apparatus information in a 1st operation example. It is a figure which shows the adjacent apparatus information in a 1st operation example. It is a network block diagram in the 2nd operation example. It is a processing sequence figure in the 2nd example of operation. It is a figure which shows the own apparatus information in the 2nd operation example. It is a figure which shows the adjacent apparatus information in the 2nd operation example. It is a network block diagram in the 3rd operation example. It is a processing sequence figure in the 3rd example of operation. It is a figure which shows the own apparatus information in the 3rd operation example. It is a figure which shows the adjacent apparatus information in a 3rd operation example. It is a network block diagram in the 4th example of operation. It is a processing sequence figure in the 4th example of operation. It is a figure which shows the own apparatus information in the 4th operation example. It is a figure which shows the adjacent apparatus information in the 4th operation example. It is a network block diagram in the 5th example of operation. It is a processing sequence figure in the 5th example of operation. It is a figure which shows the own apparatus information in the 5th operation example. It is a figure which shows the adjacent apparatus information in the 5th operation example. It is a network block diagram in the 6th operation example. It is a processing sequence figure in the 6th example of operation. It is a figure which shows the own apparatus information in the 6th operation example. It is a figure which shows the adjacent apparatus information in a 6th operation example. It is a network block diagram in the 7th operation example. It is a processing sequence figure in the 7th example of operation. It is a figure which shows the own apparatus information in the 7th operation example. It is a figure which shows the adjacent apparatus information in a 7th operation example. It is a network block diagram in the 8th operation example. It is a processing sequence figure in the 8th example of operation. It is a figure which shows the own apparatus information in the 8th operation example. It is a figure which shows the adjacent apparatus information in the 8th operation example. It is a network block diagram in the 9th operation example. It is a processing sequence diagram in the ninth operation example. It is a figure which shows the own apparatus information in the 9th operation example. It is a figure which shows the adjacent apparatus information in the 9th operation example. It is a network block diagram in the 10th operation example. It is a processing sequence figure in the 10th example of operation. It is a figure which shows the own apparatus information in a 10th operation example. It is a figure which shows the adjacent apparatus information in a 10th operation example. It is a network block diagram in the 11th operation example. It is a processing sequence figure in the 11th example of operation. It is a figure which shows the own apparatus information in the 11th operation example. It is a figure which shows the adjacent apparatus information in the 11th operation example. It is a network block diagram in the 12th operation example. It is a processing sequence figure in the 12th example of operation. It is a figure which shows the own apparatus information in the 12th operation example. It is a figure which shows the adjacent apparatus information in a 12th operation example. It is a network block diagram in the 13th operation example. It is a tree structure figure in the 13th example of operation. It is a processing sequence figure in the 13th example of operation. It is a figure which shows the own apparatus information in the 13th operation example. It is a figure which shows the adjacent apparatus information in a 13th operation example. It is a network block diagram in the 14th operation example. It is a processing sequence figure in the 14th example of operation. It is a figure which shows the own apparatus information in the 14th operation example. It is a figure which shows the adjacent apparatus information in a 14th operation example. It is a network block diagram in a realistic operation example. It is a figure which shows the state which started the server apparatus. It is a figure which shows the state which connected the client apparatus. It is a figure which shows a hierarchy state. It is a figure which shows the tree structure of the network device in which the routing mechanism is operate | moving. It is a figure which shows the mode of transfer to a power saving mode by having performed the apparatus stop notification from the server apparatus. It is a figure which shows the state change by the stop of a client apparatus. It is a figure which shows the state change by an apparatus stop cancellation | release notification. It is a figure which shows the transition of the hierarchy information of each network device.

  Hereinafter, preferred embodiments of the present invention will be described.

<Configuration>
FIG. 1 is a diagram illustrating a configuration example of a network device according to an embodiment.

  In FIG. 1, the network device 1 includes a control unit 11, a switch unit 12, a storage unit 13, an Ingress packet processing unit 14, an Egress packet processing unit 15, a power supply unit 16, and physical port units 17-1 to 17-4. And a power control unit 18.

  The control unit 11 is a part that performs overall control of the network device 1.

  The switch unit 12 is a part for connecting packets between the Ingress packet processing unit 14 and the Egress packet processing unit 15.

  The storage unit 13 is a part that holds data necessary for processing in the control unit 11.

  The Ingress packet processing unit 14 is a part that processes packets input from the physical port units 17-1 and 17-2.

  The egress packet processing unit 15 processes the packet input from the switch unit 12 and outputs the packet to the physical port units 17-3 and 17-4.

  The power supply unit 16 is a part that supplies power to each unit in the network device 1.

  The physical port units 17-1 to 17-4 are parts connected to an external network.

  The power saving control unit 18 is a part that controls power supply to each unit in the network device 1 in the power saving mode. That is, when shifting to the power saving mode, the power supply from the power supply unit 16 to other than the physical port units 17-1 to 17-4 and the power saving control unit 18 is stopped. When shifting to the power saving transfer enable mode, when an electrical signal is received by the physical port unit 17-1 or the physical port unit 17-2 upon activation of an adjacent device and notified to the power saving control unit 18, each unit Power supply unit 16 is requested to refresh the physical port units 17-3 and 17-4. By this refresh, an electrical signal is transmitted to the adjacent device connected to the physical port units 17-3 and 17-4, and the adjacent device in the power saving mode is activated.

  FIG. 2 is a diagram showing an example of the data structure of the own device information and neighboring device information held in the storage unit 13 (FIG. 1).

  As shown in FIG. 2A, the own device information includes “mode state” and “hierarchy information of the own device”. In the mode state, “OFF (0x000)” which does not shift to the power saving operation, “ON (0x1000)” which shifts to the power saving operation if possible, and actually enters the power saving operation. "Medium (0x1100)" indicating that the The default is “OFF”. In the hierarchy information of the own device, the default is “1024”. Needless to say, information necessary for communication such as the IP address and MAC address of the own device is held in the device separately from the own device information.

  As shown in FIG. 2B, the neighboring device information includes “port number”, “port state”, “hierarchical information reception flag”, “hierarchical information transmission flag”, “mode state”, “MAC address of neighboring device”, “neighboring device information”. IP address ”and“ hierarchical information of neighboring devices ”. The port number is a number that identifies each of the plurality of ports. The port state is either “operating (1)” or “stopped (0)”. In the following description, “in operation” may be expressed as “active”, and “stopped” may be expressed as “down”. The hierarchy information reception flag is either “Done (1)” or “Not (0)”. The hierarchy information transmission flag is either “Done (1)” or “Not (0)”. The mode state is any one of “OFF (0x000)”, “ON (0x1000)”, and “Medium (0x1100)”. The MAC address of the neighboring device, the IP address of the neighboring device, and the hierarchy information of the neighboring device are set for each port number.

<Basic operation>
FIG. 3 is a flowchart illustrating a processing example of the network device 1. Note that only processing for power saving operation is shown, and general processing as a network device is omitted.

  In FIG. 3, when an event occurs (step S1), the network device 1 branches the process according to the content of the event (step S2). When each process is completed, the network apparatus 1 enters a standby state for the next event (step S13). .

  When the content of the event is connection detection with an adjacent device (excluding port link up in the power saving mode), the network device 1 creates and transmits a hierarchy information request (self device) (step S3). The hierarchy information request (self apparatus) is to transmit the mode state of the transmission source and the hierarchy information to the adjacent apparatus.

  FIG. 4 is a diagram showing a format example of a hierarchical information request (local device) using ARP (Address Resolution Protocol). In the format of the normal ARP request shown on the right side of the figure, the “destination MAC address” includes the mode state and hierarchy information of the sender. Since this part is all “0x00” in the normal ARP request, if the extension of this embodiment is not supported, the mode state of the sender corresponds to “OFF”, and the hierarchy information corresponds to “0”. To do. In the hierarchical information request (own device), the IP address of the transmission source (own device) is set in the “destination IP address”.

  In addition, although the example using ARP was demonstrated, it is also possible to use protocols, such as DHCP (Dynamic Host Configuration Protocol) and BOOTP (BOOTstrap Protocol).

  Returning to FIG. 3, when the content of the event is reception of a hierarchy information request (own device), the network device 1 updates neighboring device information (FIG. 2B) based on the received content (step). S4). Subsequently, a confirmation process of the source hierarchy information (step S5) and a mode state confirmation process (step S6) are performed.

  FIG. 5 is a flowchart showing an example of the confirmation process of the source hierarchy information. In this process, based on the hierarchical information request (own device) received from the neighboring device, the hierarchical information of the own device (default is the maximum value “1024”) is updated. An information request (own device) is transmitted. As the hierarchy information of the own device, the hierarchy information of the server or PC (Personal Computer) is set to “0”, and when the own device is adjacent to it, the hierarchy information of the own device is updated to “1”. I will do it.

  In FIG. 5, when the process of confirming the sender hierarchy information is started (step S101), it is determined whether or not the sender hierarchy information is “0” (step S102). When the hierarchy information of the transmission source is “0” (Yes in step S102), the hierarchy information of the own device is updated to “1” (step S103). Note that the processing may be shifted to the next processing without determining whether or not the source hierarchy information is “0”. By dividing the processing when the hierarchy information of the transmission source is “0”, the processing for checking a plurality of neighboring device information can be omitted, and the processing can be slightly lightened.

  If the source hierarchy information is not “0” (No in step S102), “1” is added to the smallest value in the hierarchy information of the neighboring device information (step S104). Then, it is determined whether or not the maximum value is “1024” (step S105).

  If it is greater than “1024” (Yes in step S105), the hierarchy information of the own device is updated to “1024” (step S106). If it is not greater than “1024” (No in step S105), the information is updated to a value obtained by adding the hierarchy information of the own device (step S107).

  Thereafter, it is determined whether or not there is a change in the hierarchy information of the own apparatus (step S108). If there is a change (Yes in step S108), a hierarchy information request (own apparatus) is created and transmitted (step S109). The process ends (step S110). If there is no change (No in step S108), the process is terminated as it is (step S110).

  FIG. 6 is a flowchart illustrating an example of a mode state confirmation process. In this process, when the mode state is “ON”, depending on whether the own device is the most peripheral, whether the own device is a routing blocking port, whether the own device is the standby side of the redundancy group, etc. The device is shifted to the power saving mode.

  In FIG. 6, when the mode state confirmation process is started (step S111), it is determined whether or not the mode state of the device information is “ON” (step S112). When the mode state of the own apparatus information is not “ON” (No in step S112), the process is ended (step S129).

  When the mode state of the own device information is “ON” (Yes in step S112), it is determined whether or not the routing mechanism is operating in the own device (step S113). When the routing mechanism is operating (Yes in step S113), the routing flag is set to “ON” (step S114).

  Next, it is determined whether or not the redundancy mechanism is operating in the own apparatus (step S115). If the redundancy mechanism is operating (Yes in step S115), the redundancy flag is set to “ON” (step S115). S116).

Next, the following four states: Whether or not the hierarchical information of the own device information is larger than the hierarchical information of all the neighboring device information and whether there is one neighboring device information (steps S117 and S118)
Whether the routing flag is “ON” and the port is a blocking port in a tree structure (steps S119 and S120)
Whether the redundancy flag is “ON” and the redundancy group is on the standby side (steps S121 and S122)
Whether the routing flag and the redundancy flag are “ON” and the redundancy group is a standby side and is a blocking port in a tree structure (steps S123 to S125)
Are judged in parallel.

  If any of these is true, the mode state of the own device information is updated to “medium” (step S126), and a hierarchical information request (own device) is created and transmitted (step S127). The mode is shifted to the power saving mode (step S128), and the process is terminated (step S129).

  Returning to FIG. 3, if the event content is port link down detection, processing at the time of port link down is performed (step S <b> 7).

  FIG. 7 is a flowchart showing an example of port link down processing. In this processing, the port link down of the neighboring device is recorded as neighboring device information, and the hierarchical information of the own device is updated.

  In FIG. 7, when the port link down process is started (step S131), the port state of the target port of the neighboring device information is changed to “down” (step S132).

  Next, it is determined whether or not there are one or more devices whose neighboring device information port status is “active” (step S133).

  If one or more of the neighboring device information port states are “active” (No in step S133), the hierarchical information of the own device is updated to “1024”, and the mode state of the own device is set to “OFF”. Update (step S134), and the process ends (step S143).

  If there is one or more ports whose neighboring device information port status is “active” (Yes in step S133), there is information whose neighboring device information port status is “active” and whose hierarchy information is “0”. It is determined whether or not to perform (step S135). If it does not exist (No in step S135), the process ends (step S143).

  When the port status of the adjacent device information is “active” and the information of the hierarchy information is “0” (Yes in step S135), it is determined whether the hierarchy information of the own device is “1” (step S136).

  When the hierarchy information of the own apparatus is “1” (Yes in step S136), the hierarchy information of the own apparatus is updated to “1024” (step S137), and a hierarchy information request (own apparatus) is created and transmitted ( Step S138), the process ends (Step S143).

  If the hierarchical information of the own device is not “1” (No in step S136), “1” is added to the smallest value in the hierarchical information in which the port status of the neighboring device information is “active” (step S139).

  Next, it is determined whether or not the added value and the hierarchy information of the own device are the same (step S140). If they are the same (Yes in step S140), the process ends (step S143).

  If the added value and the hierarchy information of the own device are not the same (No in step S140), the hierarchy information of the own device is updated to the added value (step S141), and the mode state confirmation process (step S142) is performed. Is finished (step S143). The mode state confirmation process (step S142) is the same as that shown in FIG.

  Returning to FIG. 3, when the event content is port link up detection in the power saving mode, processing at the time of port link up is performed (step S <b> 8).

  FIG. 8 is a flowchart showing an example of processing at the time of port link up. In this process, a return from the power saving mode to the power saving mode is possible.

  In FIG. 8, when the port link up process is started (step S151), the connection port is refreshed (step S152).

  Then, the mode state of the own device is updated to “ON” (step S153), and the process is terminated (step S154).

  Returning to FIG. 3, when the event content is reception of a device stop notification, the neighboring device information is updated (step S9), and device stop notification processing (step S10) is performed.

  If the event content is reception of a device stop release notification, the neighboring device information is updated (step S11), and device stop release notification processing (step S12) is performed.

  FIG. 9 is a diagram showing a format example of a device stop notification and a device stop release notification using ARP. (A) shows a device stop notification, and (b) shows a device stop release notification. The difference from the hierarchical information request (own device) shown in FIG. 4 is that the protocol type is changed to “0x0807”, and the operation number is “0x0001” when the device stop notification is received. In the case of the cancellation notification, it is “0x0002”, and the destination IP address is “0.0.0.0”.

  In addition, although the example using ARP was demonstrated, it is also possible to use protocols, such as DHCP and BOOTP.

  FIG. 10 is a flowchart illustrating an example of the apparatus stop notification process. In this process, after the mode state is set to “ON”, a device stop notification is transferred to another active port. Further, depending on whether the own device is the most peripheral, the own device is a routing blocking port, or the own device is the standby side of the redundancy group, the own device is shifted to the power saving mode.

  In FIG. 10, when the device stop notification process is started (step S161), the mode state of the own device information is updated to “ON” (step S162), and a device stop notification is created and transmitted to all active ports (step S162). S163).

  Next, it is determined whether or not the routing mechanism is operating in the own apparatus (step S164). When the routing mechanism is operating (Yes in step S164), the routing flag is set to “ON” (step S165).

  Next, it is determined whether or not the redundancy mechanism is operating in the local apparatus (step S166). If the redundancy mechanism is operating (Yes in step S166), the redundancy flag is set to “ON” (step S166). S167).

Next, the following four states: Whether or not the hierarchical information of the own device information is larger than the hierarchical information of all neighboring device information and whether there is one neighboring device information (steps S168 and S169)
Whether the routing flag is “ON” and the port is a blocking port in a tree structure (steps S170 and S171)
Whether the redundancy flag is “ON” and the redundancy group is on the standby side (steps S172 and S173)
Whether the routing flag and the redundancy flag are “ON” and the redundancy group is a standby side and is a blocking port in a tree structure (steps S174 to S176)
Are judged in parallel.

  If any of these is true, the mode state of the own device information is updated to “medium” (step S177), and a hierarchical information request (own device) is created and transmitted (step S178). The mode is shifted to the power saving mode (step S179), and the process is terminated (step S180).

  FIG. 11 is a flowchart illustrating an example of the apparatus stop cancellation notification process. In this process, the mode state “ON” is returned to “OFF”.

  In FIG. 11, when the device stop release notification process is started (step S181), the mode state of the own device information is updated to “OFF” (step S182).

  Next, the connection port is refreshed (step S183), an apparatus stop cancellation notification is created and transmitted to all active ports (step S184), and the process is terminated (step S185).

<Operation example>
Next, a specific operation example will be described.

(First operation example)
As shown in FIG. 12A, consider a case where there are two network devices 1 # 1 and 1 # 2, and the port 1 of the network device 1 # 1 and the port 1 of the network device 1 # 2 are connected.

  In this case, as shown in FIG. 12B, the hierarchical information requests (own device) are transmitted to each other, the mutual information is exchanged, and the adjacent device information is updated. FIG. 12C shows own device information, and FIG. 12D shows neighboring device information.

(Second operation example)
As shown in FIG. 13A, in a state where the network device 1 # 1 and the network device 1 # 2 are connected (results of the first operation example), the server device SV is connected to the port 2 of the network device 1 # 1. Think about the case.

  In this case, as shown in FIG. 13B, the server apparatus SV sets the IP address of its own apparatus as the IP address of the transmission destination of the ARP request and transmits it.

  The network device 1 # 1, which has received the ARP request from the server device SV, determines that it is a device that does not support expansion of hierarchical information exchange since all the MAC addresses of the transmission sources are 0x00, and determines the hierarchy of its own device. After changing the information to “1” and updating the neighboring device information, a hierarchy information request (own device) is transmitted to the active port.

  Receiving the hierarchical information request from the network device 1 # 1, the network device 1 # 2 changes its own hierarchical information to “2”, updates the neighboring device information, and then transmits the hierarchical information request (own device). .

  Receiving the hierarchical information request from the network device 1 # 2, the network device 1 # 1 updates the neighboring device information. Since there is no change in the hierarchy information of the own apparatus, the hierarchy information request (own apparatus) is not transmitted.

(Third operation example)
As shown in FIG. 14A, when the server apparatus SV, the network apparatus 1 # 1, and the network apparatus 1 # 2 are connected (result of the second operation example), the network apparatus is connected to the port 2 of the network apparatus 1 # 2. Consider a case where port # 1 of 1 # 3 is connected.

  In this case, as shown in FIG. 14B, when the network device 1 # 2 and the network device 1 # 3 are connected, the hierarchy information request (own device) is transmitted to each other, and the adjacent device information is updated.

  The network device 1 # 3 receives the layer information “2” of the network device 1 # 2, changes the layer information of the own device to “3”, and transmits a layer information request (own device) to the active port.

  Receiving the hierarchy information request from the network device 1 # 3, the network device 1 # 2 updates the neighboring device information.

(Fourth operation example)
As shown in FIG. 15A (a), the network device 1 in a state where the server device SV, the network device 1 # 1, the network device 1 # 2, and the network device 1 # 3 are connected (result of the third operation example). Consider a case where the client apparatus PC is connected to port # 2 of # 3.

  In this case, as shown in FIG. 15B, the client apparatus PC sets the IP address of its own apparatus as the transmission destination IP address of the ARP request, and transmits it.

  The network device 1 # 3 that has received the ARP request from the client device PC determines that the MAC address of the transmission source is all 0x00, so that it is a device that does not support expansion of hierarchical information exchange. After changing the information to “1” and updating the neighboring device information, a hierarchy information request (own device) is transmitted to the active port.

  Receiving the hierarchy information request from the network device 1 # 3, the network device 1 # 2 updates the neighboring device information. Since there is no change in the hierarchy information of the own apparatus, the hierarchy information request (own apparatus) is not transmitted.

  A network configuration reflecting the hierarchy information is shown in FIG. 15A (b).

(Fifth operation example)
As shown in FIG. 16A (a), in a state where the server apparatus SV, the network apparatus 1 # 1, the network apparatus 1 # 2, the network apparatus 1 # 3, and the client apparatus PC are connected (result of the fourth operation example). Consider the case where the client device PC is disconnected due to the power stop or the like.

  In this case, as illustrated in FIG. 16B, the network device 1 # 3 detects the link down of the port 2 and determines that “0” is lost in the hierarchical information of the adjacent device.

  Since the smallest value in the hierarchy information of other neighboring devices is “2”, the hierarchy information of the own device is changed to “3”, the neighboring device information is updated, and then the hierarchy information request to the active port (own device) Send. If there is no neighboring device information, the hierarchical information of the own device is changed to “1024”.

  Receiving the hierarchy information request from the network device 1 # 3, the network device 1 # 2 updates the neighboring device information. Since there is no change in the hierarchy information of the own apparatus, the hierarchy information request (own apparatus) is not transmitted.

  A network configuration reflecting the hierarchy information is shown in FIG. 16A (b).

(Sixth operation example)
As shown in FIG. 17A, in a state where the server apparatus SV, the network apparatus 1 # 1, the network apparatus 1 # 2, the network apparatus 1 # 3, and the client apparatus PC are connected (result of the fourth operation example), the server apparatus Consider a case where an apparatus stop notification is made from SV.

  In this case, as illustrated in FIG. 17B, the network device 1 # 1 that has received the device stop notification sets the mode state of its own device information to “ON”. Also, the reception flag / transmission flag of the neighboring device information is cleared. Since the device stop notification (# 1) has been received, it is assumed that the reception flag for port number 2 has been completed. Also, device stop notifications (# 2) / (# 3) are made, and the transmission flag is completed. After that, a device stop notification (# 4) is received, and the reception flag of port number 1 is set.

  Similarly, a device stop notification is propagated to each device.

(Seventh operation example)
As shown in FIG. 18A, a case is considered in which connection / disconnection is performed after power-off of the client apparatus PC after the apparatus stop notification.

  In this case, as shown in FIG. 18B, when the client apparatus PC stops, the hierarchical structure changes.

  At this time, the network device 1 # 3 recognizes that the mode state is “ON” from the own device information and is a terminal device from the hierarchical information of the adjacent device information, and the mode state of the own device information is “medium”. And sends a hierarchical information request (own device) to shift to the power saving mode of the device.

  In the network device 1 # 2, the network device 1 # 2 also changes the mode state of its own device information to “medium” in response to the transition to the mode state “medium” of the network device 1 # 3. To shift to the power saving mode of the device.

(Eighth operation example)
As shown in FIG. 19A (a), consider a case where the client apparatus PC is started after the network apparatus 1 # 2 and the network apparatus 1 # 3 have shifted to the power saving mode.

  In this case, as shown in FIG. 19B, when the port connected to the client device PC of the network device 1 # 3 is linked up, the power saving mode returns to the steady state.

  At that time, the mode state of the own device information is set to “ON” and an ARP request is received from the client device PC.

  After that, as shown in FIG. 19A (b), the state is the same as in the fourth operation example.

(Ninth operation example)
As shown in FIG. 20A, a case is considered in which after the eighth operation example, an apparatus stop cancellation notification is made from the server apparatus SV.

  In this case, as illustrated in FIG. 20B, the network device 1 # 1 that has received the device stop cancellation notification sets the mode state of the own device information to “OFF”. Also, the reception flag / transmission flag of the neighboring device information is cleared. Since the device stop release notification (# 1) has been received, it is assumed that the reception flag for port number 2 has been completed. Further, the device stop cancellation notification (# 2) / (# 3) is performed, and the transmission flag is set. It is assumed that the device stop release notification (# 4) has been received and the reception flag for port number 1 has been completed.

  Similarly, a device stop release notification is propagated to each device.

(Tenth operation example)
As shown in FIG. 21A, consider a case where a device stop cancellation notification is made after the seventh operation example.

  In this case, as illustrated in FIG. 21B, the network device 1 # 1 that has received the device stop cancellation notification sets the mode state of the own device information to “OFF”. Also, the reception flag / transmission flag of the neighboring device information is cleared. Since the device stop release notification (# 1) has been received, it is assumed that the reception flag for port number 2 has been completed. Device stop release notifications (# 2) / (# 3) are made, and the transmission flag is completed. It is assumed that the device stop release notification (# 4) has been received and the reception flag for port number 1 has been completed.

  Upon receiving the device stop release notification, the network device 1 # 2 returns from the power saving mode to the steady state, sets the mode state of its own device information to “OFF”, and notifies the active port of the device stop release notification (# 4). ) / (# 5).

(Eleventh operation example)
As shown in FIG. 22A (a), consider a case where a server stop notification is sent from the server SV.

  Here, the network device 1 # 3 and the network device 1 # 4 have an Act / Stand-by redundancy configuration, and the network device 1 # 4 is on the Stand-by side.

  As illustrated in FIG. 22B, the network device 1 # 1 that has received the device stop notification sets the mode state of its own device information to “ON”. Also, the reception flag / transmission flag of the neighboring device information is cleared. Since the device stop notification (# 1) has been received, it is assumed that the reception flag for port number 2 has been completed. Device stop notifications (# 2) / (# 3) / (# 4) are made and the transmission flag is set. It is assumed that the device stop notification (# 6) / (# 8) has been received and the reception flag for port number 1/3 has been completed.

  Hereinafter, a device stop notification is propagated to each device.

  As a result, as shown in FIG. 22A (b), the network device 1 # 4 enters the power saving mode.

(Twelfth operation example)
As shown in FIG. 23A (a), a case is considered in which an apparatus stop cancellation notification is sent from the server apparatus SV.

  Here, the network device 1 # 3 and the network device 1 # 4 have an Act / Stand-by redundancy configuration, and the network device 1 # 4 is on the Stand-by side.

  As illustrated in FIG. 23B, the network device 1 # 1 that has received the device stop cancellation notification sets the mode state of its own device information to “OFF”. Also, the reception flag / transmission flag of the neighboring device information is cleared. Since the device stop release notification (# 1) has been received, it is assumed that the reception flag for port number 2 has been completed. Device stop release notifications (# 2) / (# 3) / (# 4) are made to complete the transmission flag. It is assumed that the device stop release notification (# 6) / (# 8) is received and the reception flag of the port number 1/3 is completed.

  Thereafter, the device stop cancellation notification is propagated to each device.

  As a result, as shown in FIG. 23A (b), the network device 1 # 4 returns to the power saving shift impossible mode.

(13th operation example)
As shown in FIG. 24A1 (a), consider a case where a server stop notification is sent from the server SV.

  Here, the network devices 1 # 3, 1 # 4, 1 # 5, and 1 # 6 have a tree structure shown in FIG. 24A2 by the routing mechanism.

  As illustrated in FIG. 24B, the network device 1 # 1 that has received the device stop notification sets the mode state of its own device information to “ON”. Also, the reception flag / transmission flag of the neighboring device information is cleared. Since the device stop notification (# 1) has been received, it is assumed that the reception flag for port number 2 has been completed. Device stop notifications (# 2) / (# 3) / (# 4) are made and the transmission flag is set. It is assumed that the device stop notification (# 6) / (# 8) is received and the reception flag of the port number 1/3 is completed.

  Hereinafter, a device stop notification is propagated to each device.

  As a result, as shown in FIG. 24A1 (b), the network device 1 # 6 enters the power saving mode.

(14th operation example)
As shown in FIG. 25A (a), a case is considered in which an apparatus stop cancellation notification is sent from the server apparatus SV.

  Here, the network devices 1 # 3, 1 # 4, 1 # 5, and 1 # 6 have a routing mechanism.

  As illustrated in FIG. 25B, the network device 1 # 1 that has received the device stop cancellation notification sets the mode state of the own device information to “OFF”. Also, the reception flag / transmission flag of the neighboring device information is cleared. Since the device stop release notification (# 1) has been received, it is assumed that the reception flag for port number 2 has been completed. Device stop release notifications (# 2) / (# 3) / (# 4) are made to complete the transmission flag. It is assumed that the device stop release notification (# 6) / (# 8) is received and the reception flag of the port number 1/3 is completed.

  Thereafter, the device stop cancellation notification is propagated to each device.

  As a result, as shown in FIG. 25A (b), the network device 1 # 6 returns to the power saving shift impossible mode.

<Realistic operation example>
FIG. 26 is a network configuration diagram in a practical operation example, in which network devices 1 # 1 to 1 # 16 are connected. The network devices 1 # 1, 1 # 2, 1 # 15, and 1 # 16 are assumed to be L2SW (Layer 2 switch). The network devices 1 # 3, 1 # 4, and 1 # 11 to 1 # 14 are assumed to be L3SW (Layer 3 switch). The network devices 1 # 5 to 1 # 10 are assumed to be routers. Further, the network devices 1 # 3, 1 # 4, the network devices 1 # 11, 1 # 12, and the network devices 1 # 13, 1 # 14 have a duplex (redundant) configuration, respectively. Assume that the standby side is the standby side.

  Hereinafter, a flow of automatically generating hierarchy information will be described.

  (1) All devices have layer information “1024” by default, and when all devices are activated, layer information requests are exchanged between adjacent devices by ARP to which layer information is added.

  (2) As shown in FIG. 27, when the server apparatus SV is activated, the ARP of the hierarchy information “0” is transmitted from the server apparatus SV to the network apparatuses 1 # 1 and 1 # 2.

  (3) The network devices 1 # 1, 1 # 2 regenerate the hierarchy information to “1”, and transmit the ARP with the hierarchy information request.

  (4) The network devices 1 # 3 and 1 # 4 regenerate the hierarchical information to “2” and transmit the ARP with the hierarchical information request. Similarly, each device propagates a hierarchy information request.

  (5) As shown in FIG. 28, the client apparatuses PC1 and PC2 are connected to the network apparatuses 1 # 15 and 1 # 16.

  (6) The hierarchical state is as shown in FIG.

  (7) When a device stop notification is transmitted from the server device SV, all the network devices are in the mode state “ON”. Further, in the process of propagating the device stop notification, the network devices 1 # 3, 1 # 11, and 1 # 13 in the redundant configuration become the “medium” mode state and stop.

  (8) The tree structure of the layer 3/4 network devices 1 # 5 to 1 # 10 in which the routing mechanism is operating is as shown in FIG. 30, and the blocking port is on the network device 1 # 7 side.

  (9) As a result of the apparatus stop notification being propagated throughout, as shown in FIG. 31 with “x”, the network apparatuses 1 # 3, 1 # 5, 1 # 7, 1 # 9, 1 # 11, 1 # 13 shifts to the power saving mode.

  (10) When the client apparatus PC2 is stopped from this state, the hierarchical state changes as shown in FIG. Further, the network devices 1 # 14 and 1 # 16 at the end also shift to the power saving mode.

  (11) In this state, when the device stop release notification is transmitted from the server device SV, all the network devices are in the mode state “OFF”. Also, as shown in FIG. 33, the network devices 1 # 3, 1 # 5, 1 # 7, 1 # 9, 1 # 11, 1 # 13, 1 # 14, and 1 # 16 that are in the power saving mode are also saved. Return to power transfer disabled mode.

  FIG. 34 shows the transition of the hierarchical information of each device in (2), (5), and (10) described above.

<Summary>
As described above, according to this embodiment, information for determining whether or not the own device is capable of power saving operation (configuration of peripheral devices and installation hierarchy of the own device on the network topology) is automatically collected. Then, each network device autonomously switches to the power saving operation mode based on the information. As a result, it is possible to safely and reliably perform advanced network power-saving operation and to eliminate the need for maintenance operator intervention.

The present invention has been described above by the preferred embodiments of the present invention. While the invention has been described with reference to specific embodiments, various modifications and changes may be made to the embodiments without departing from the broad spirit and scope of the invention as defined in the claims. Obviously you can. In other words, the present invention should not be construed as being limited by the details of the specific examples and the accompanying drawings.
(Appendix 1)
Means for exchanging device information with neighboring devices;
When a device stop notification is received via an adjacent device, the device sets the own device in a power saving transition possible mode, and transfers the device stop notification to another adjacent device;
Means for determining whether the own device is a device capable of shifting to the power saving mode from the device information of the own device and the neighboring device when the own device is in the power saving mode;
When it is determined that the device can shift to the power saving mode, a means for shifting the own device to the power saving mode;
When the device stop release notification is received via the adjacent device, the device is set to a power saving transition impossible mode, and the device stop release notification is transferred to another adjacent device. Network device.
(Appendix 2)
In the network device according to attachment 1,
When the own device is in the power saving mode, it is determined from the device information of the own device and neighboring devices that the device can be shifted to the power saving mode when the own device is an unnecessary device in the vicinity. A network device characterized by the above.
(Appendix 3)
In the network device according to any one of Appendix 1 or 2,
When the self device is in a power saving mode, it is determined from the device information of the own device and neighboring devices that the device can be shifted to the power saving mode when the self device is a standby device. Network device.
(Appendix 4)
In the network device according to any one of appendices 1 to 3,
When the own device is in the power saving mode, it is determined from the device information of the own device and neighboring devices that the device can enter the power saving mode when the own device is in an unused detour path. A network device characterized by:
(Appendix 5)
Exchanging device information with neighboring devices;
When receiving a device stop notification via an adjacent device, the step of setting the own device in a power saving transition possible mode and transferring the device stop notification to another adjacent device;
A step of determining whether or not the own device is a device that can be shifted to the power saving mode from the device information of the own device and the neighboring device when the own device is in the power saving mode; and
When it is determined that the device can be shifted to the power saving mode, the step of shifting the own device to the power saving mode;
A step of setting the own device to a power-saving transition impossible mode and transferring the device stop release notification to another adjacent device when the device stop release notification is received via the adjacent device. A network device control method.
(Appendix 6)
In the network device control method according to attachment 5,
When the own device is in the power saving mode, it is determined from the device information of the own device and neighboring devices that the device can be shifted to the power saving mode when the own device is an unnecessary device in the vicinity. A network device control method characterized by the above.
(Appendix 7)
In the network device control method according to any one of appendices 5 and 6,
When the self device is in a power saving mode, it is determined from the device information of the own device and neighboring devices that the device can be shifted to the power saving mode when the self device is a standby device. A network device control method.
(Appendix 8)
In the network device control method according to any one of appendices 5 to 7,
When the own device is in the power saving mode, it is determined from the device information of the own device and neighboring devices that the device can enter the power saving mode when the own device is in an unused detour path. And a network device control method.

1, 1 # 1 to 1 # 16 Network device 11 Control unit 12 Switch unit 13 Storage unit 14 Ingress packet processing unit 15 Egress packet processing unit 16 Power supply unit 17-1 to 17-4 Physical port unit 18 Power saving control unit SV Server device PC, PC1, PC2 Client device

Claims (5)

Means for exchanging device information with neighboring devices;
When a device stop notification is received via an adjacent device, the device sets the own device in a power saving transition possible mode, and transfers the device stop notification to another adjacent device;
Means for determining whether the own device is a device capable of shifting to the power saving mode from the device information of the own device and the neighboring device when the own device is in the power saving mode;
When it is determined that the device can shift to the power saving mode, a means for shifting the own device to the power saving mode;
When the device stop release notification is received via the adjacent device, the device is set to a power saving transition impossible mode, and the device stop release notification is transferred to another adjacent device. Network device. The network device according to claim 1,
When the own device is in the power saving mode, it is determined from the device information of the own device and neighboring devices that the device can be shifted to the power saving mode when the own device is an unnecessary device in the vicinity. A network device characterized by the above. The network device according to any one of claims 1 and 2,
When the self device is in a power saving mode, it is determined from the device information of the own device and neighboring devices that the device can be shifted to the power saving mode when the self device is a standby device. Network device. The network device according to any one of claims 1 to 3,
When the own device is in the power saving mode, it is determined from the device information of the own device and neighboring devices that the device can enter the power saving mode when the own device is in an unused detour path. A network device characterized by: Exchanging device information with neighboring devices;
When receiving a device stop notification via an adjacent device, the step of setting the own device in a power saving transition possible mode and transferring the device stop notification to another adjacent device;
A step of determining whether or not the own device is a device that can be shifted to the power saving mode from the device information of the own device and the neighboring device when the own device is in the power saving mode; and
When it is determined that the device can be shifted to the power saving mode, the step of shifting the own device to the power saving mode;
A step of setting the own device to a power-saving transition impossible mode and transferring the device stop release notification to another adjacent device when the device stop release notification is received via the adjacent device. A network device control method.

Images