JP2010010997A - Relay device and method of controlling the same - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To indicate a right connection destination so as to be visually recognized even before connection of a cable, to shorten working hours and improve the efficiency of work in construction of environment, in a relay device between networks. <P>SOLUTION: A CPU 100A specifies a connection port to which the cable should be connected among a plurality of connection ports PA1-PA24 based on information included in an event received via a connection terminal RPA and an input/output interface 120A, and connection information 112A stored in a memory 110A, and performs green lighting of a link LED of the specified connection port. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a relay device for configuring a communication network.

  In recent years, in the Internet, the use forms have been diversified and the number of users has been increasing, and accordingly, the amount of data flowing on the network is also increasing. Therefore, in a relay device between networks, a plurality of physical ports are logically bundled into one in order to cope with high-speed and large-capacity communication. For this reason, it is required to increase the number of ports. In addition, with the increase in the number of accommodated users, the increase in the number of ports is required. At the same time, in order to accommodate more lines in a limited space, space saving is required, and the degree of port integration in the relay device is increasing.

  By the way, when constructing the environment, in order to confirm which connection port the cable should be connected to in the relay device, and whether the cable connecting the relay devices is connected correctly, the worker can check the device configuration diagram and configuration. It was necessary to manually check the cable from one end while searching for the setting information. For this reason, such confirmation is difficult when there are many connection ports, when the target relay devices are very far away, or when the cable laying route is narrow, such as under the floor or between desks. It took a lot of labor and time.

  In addition, if a cable is connected by mistake, a so-called loop configuration will occur, in which signals flow into the path that should not flow, and incorrect connection at the end of the network will spread to the failure of the entire network. Was.

  Conventionally, as an erroneous connection detection method of a cable, for example, the one described in Patent Document 1 below is known.

JP 2006-269213 A

  In a relay device between networks, there is a need for means for confirming in a short time which connection port to connect between devices and detecting a connection error.

  In the technique described in Patent Literature 1 described above, after connecting the own device and the connection destination device with a cable, the information on the own device is notified to the connection destination device through the connected cable, and there is no connection destination error. I was trying to judge.

  However, in the technique described in Patent Document 1, since an erroneous connection cannot be detected unless the devices are connected with a cable, an operator refers to the device configuration diagram, configuration setting information, and the like. I had to check the cable manually. In addition, since the display is not visually easy to understand and correct, there is a problem that as the number of ports increases, the number of connection trials for connecting a cable increases, which takes time.

  Accordingly, an object of the present invention is to visually indicate a correct connection destination in a relay device between networks even before connection of a cable, thereby shortening the work time and improving the work efficiency at the time of environment construction. There is.

  SUMMARY An advantage of some aspects of the invention is to solve at least a part of the problems described above, and the invention can be implemented as the following forms or application examples.

[Application Example 1]
A relay device for configuring a communication network,
Multiple connection ports,
A plurality of lighting sections provided corresponding to each connection port;
A receiving unit for receiving external events;
A storage unit for storing connection information indicating a connection relationship of cables between connection ports with other devices;
A control unit;
With
The control unit specifies a connection port to which a cable is to be connected among the plurality of connection ports based on information included in the event received via the reception unit and the connection information, and specifies the specified connection A relay device characterized in that the lighting unit is lit so that a port can be distinguished from other connection ports.

  As described above, in application example 1, the lighting unit is turned on so that the connection port to which the cable is to be connected can be distinguished from the other connection ports, so that the user can determine the position of the port to which the cable is to be connected. It is possible to confirm visually and easily. In addition, since the port to which the cable is to be connected is specified based on information received from the outside or connection information stored in advance, it is possible to prevent unintended communication and network failure due to a connection error in advance. Become.

[Application Example 2]
In the relay device according to Application Example 1, the control unit, based on information included in an event received via the reception unit and the connection information when the cable is connected to the connection port. Determining whether or not the cable is correctly connected to a connection port to which a cable in the own device and the other device is to be connected, and lighting the lighting unit based on the determination result Relay device to do.

  As described above, in Application Example 2, the lighting unit is turned on based on the determination result of whether or not the lighting unit is correctly connected to the connection port to which the cable in the own device and the other device is connected. By observing the lighting state of the lighting part, it is possible to immediately find out the erroneous connection. In addition, it is possible to construct a connection configuration of relay devices between networks accurately in a short time.

[Application Example 3]
In the relay device according to Application Example 2, when the control unit determines that the cable is connected to an incorrect connection port other than the connection port to which the cable is to be connected, the control unit and the other device A relay device characterized in that the lighting unit is turned on so that it can be distinguished which of the devices is connected to an incorrect connection port.

  As described above, in Application Example 3, the lighting unit is turned on so that it can be distinguished whether the lighting device is connected to the wrong connection port in the own device or another device. Can immediately grasp the erroneously connected device.

[Application Example 4]
In the relay device according to any one of Application Examples 1 to 3, the relay device further includes a management port connectable to the other device with a cable,
The control unit transmits at least a part of the connection information to the other device via the management port.

  As described above, in Application Example 4, since the control unit transmits at least part of the connection information to the other device, the connection information stored in the own device and the other device are stored. It is possible to synchronize with the connection information. For example, even if the system configuration changes and the cable connection configuration changes, the connection information stored in the local device can be corrected and stored in another device. The connected connection information is also automatically corrected, and it is possible to easily cope with it.

[Application Example 5]
In the relay device according to any one of Application Examples 1 to 4, the storage unit further stores first network configuration information related to the own device for configuring the communication network. ,
The control unit acquires second network configuration information related to the other device from the other device, and based on the stored first network configuration information and the acquired second network configuration information A relay device that generates the connection information.

  As described above, in Application Example 5, since the control unit automatically generates the connection information, the user can save time and effort to create the connection information or transmit it to the relay device.

[Application Example 6]
The relay device according to any one of Application Examples 1 to 5, further comprising a plurality of operation state display lighting units provided corresponding to each connection port, separately from the lighting unit. ,
The said control part controls lighting of the said lighting part for operation state display so that the operation state of a corresponding connection port may be displayed.

  Therefore, in Application Example 6, while the operation state display lighting unit displays the operation state of the corresponding connection port, the lighting unit identifies whether the corresponding connection port is a port to which a cable is to be connected. Is also possible.

[Application Example 7]
In the relay device according to any one of Application Examples 1 to 6, the control unit, based on information included in an event received via the reception unit and the connection information, When a plurality of physical ports that are logically bundled and used as a connection port to which a cable is to be connected among a plurality of connection ports, the specified plurality of physical ports can be distinguished from other connection ports. As described above, a relay device characterized in that the lighting unit is turned on.

  As described above, in the application example 7, when a plurality of physical ports are logically bundled and used, even when the physical ports are designated as connection ports to which a cable is to be connected, The position of the physical port can be displayed visually in an easily understandable manner.

[Application Example 8]
In the relay device according to any one of Application Examples 1 to 7, the relay device further includes a connection detection unit that detects connection of the cable to the connection port,
When the connection detection unit detects the connection of the cable, the control unit refers to the connection information, and specifies information for specifying a connection port to which the cable is to be connected in the other device. A relay device that notifies the device.

  In this way, when the cable is connected to the connection port in its own device, the other device is notified as described above, and the other device connects the cable based on the notification. The position of the connection port to be displayed can be displayed visually and easily.

[Application Example 9]
A control method for controlling a relay device for configuring a communication network,
The relay device is
Multiple connection ports,
A plurality of lighting sections provided corresponding to each connection port;
A storage unit for storing connection information indicating a connection relationship of cables between connection ports with other devices;
With
The control method is:
(A) receiving an event from outside;
(B) identifying a connection port to which a cable is to be connected among the plurality of connection ports based on the information included in the received event and the connection information;
(C) turning on the lighting unit so that the identified connection port can be distinguished from other connection ports;
A control method comprising:
As described above, according to the control method of the application example 9, the same effect as that of the application example 1 can be obtained.

  Note that the present invention is not limited to the above-described aspects of the device invention such as the relay apparatus and the method invention such as the control method of the relay apparatus, but may be an aspect as a computer program for constructing these methods and apparatuses. The present invention can also be realized in various modes such as a recording medium on which such a computer program is recorded.

Hereinafter, embodiments of the present invention will be described in the following order based on examples.
A. Example configuration:
B. Example operation:
B-1. Device mode change processing (change to connection destination confirmation mode):
B-2. Connection destination confirmation target notification process:
B-3. Interrupt event handling processing:
B-4. Connection confirmation process during link up:
B-5. Device mode change processing (change to normal mode):
C. Effects of the embodiment:
D. Variation:

A. Example configuration:
FIG. 1 is an explanatory diagram showing a network connection system using a relay device as an embodiment of the present invention.

  A management terminal C is connected to one of the relay devices A and B of the present embodiment. In this embodiment, in order to distinguish between both relay apparatuses A and B, the relay apparatus A may be referred to as a connection source apparatus A, and the relay apparatus B may be referred to as a connection destination apparatus B.

  As shown in FIG. 1, the relay devices A and B are respectively CPUs 100A and 100B for controlling each component in the device, memories 110A and 110B for storing desired information, and ports described later. 24 for performing cable connection between the input / output interfaces 120A and 120B for exchanging data and information with each other and driving each link LED to be described later, and other relay devices. The management ports APA and APB for exchanging management information between the connection ports PA1 to PA24 and PB1 to PB24 and other relay apparatuses and the management terminal C via an RS-232C cable or the like Connection terminals RPA and RPB for connection are mainly provided. Among these, the memories 110A and 110B can store connection information 112A and 112B, network configuration information 114A and 114B, which will be described later. In addition, link LEDs (light emitting diodes) αA1 to αA24, αA, αB1 to αB24, and αB are provided on the outer surfaces of the relay devices A and B, respectively, for each port. On the other hand, the management terminal C is configured by a personal computer or the like.

  In this embodiment, it is assumed that “A” is assigned as the device ID to the relay device A, and “B” is assigned as the device ID to the relay device B. The connection ports PA1 to PA24 of the relay device A have port numbers “1” to “24”, and the connection ports PB1 to PB24 of the relay device B have port numbers “1” to “24”. Are assigned respectively.

  In the present embodiment, the relay devices A and B are connected to the relay device in the claims, the connection ports PA1 to PA24, PB1 to PB24, and the connection ports in the claims are the link LEDs αA1 to αA24 and αB1 to αB24. The lighting terminals in the section include the connection terminals RPA and RPB and the input / output interfaces 120A and 120B, the receiving section in the claims, the memories 110A and 110B, the storage section in the claims, and the CPUs 100A and 100B in the claims. The management ports APA and APB respectively correspond to the management ports in the claims. Note that the management ports APA, APB, connection ports PA1 to PA24, PB1 to PB24, and the like may also correspond to the receiving unit in the claims depending on the contents of the processing.

B. Example operation:
In this embodiment, an operation when a user tries to connect a relay device B, which is a connection destination device, to the relay device A, which is a connection source device, with a cable in order to configure a network.

  First, the user (worker) connects the management terminal C to the connection terminal RPA of the connection source device A via an RS-232C cable or the like, and connects one end of the cable 202 to the management port APA of the connection source device A. Connect the other end to the management port APB of the connection destination device B. Next, when the user operates the management terminal C to issue a desired instruction, connection information preset by the user (administrator) is transmitted from the management terminal C to the connection source apparatus A. In the connection source device A, when the CPU 100A receives the transmitted connection information from the connection terminal RPA via the input / output interface 120A, the CPU 100A stores the connection information 112A in the memory 110A. Thereafter, the CPU 100A reads the connection information 112A from the memory 110A, and transmits the connection information 112A to the connection destination device B from the management port APA via the input / output interface 120A. In the connection destination apparatus B, when the CPU 100B receives the transmitted connection information from the management port APB via the input / output interface 120B, the CPU 100B stores the connection information 112B in the memory 110B.

  In this way, the same connection information 112A and 112B are stored in the connection source device A and the connection destination device B, respectively. As described above, in this embodiment, the connection information can be held in the connection destination device B only by setting the connection information in the connection source device A.

  FIG. 2 is an explanatory diagram showing an example of connection information stored in the connection source device A and the connection destination device B of FIG. The connection information is information necessary for connecting the connection source device A and the connection destination device B with a cable, and which connection port each connection port is between the connection source device A and the connection destination device B. Information indicating whether to be connected.

  As shown in FIG. 2, the connection information is composed of a plurality of connection entries, and each connection entry is divided into a connection source device item and a connection destination device item. A device ID, a port number, and an LA (Link Aggregation) group number are input, respectively. With these pieces of information, connection ports to be connected can be specified between the connection source device A and the connection destination device B. Further, for example, even when the ratio between the number of connection ports of the connection source device belonging to the same LA group and the number of connection ports of the device destination device is in a relationship of N: M (N ≠ M), By generating appropriate connection candidates in units of LA groups, it is possible to specify a connection port to be connected.

  Further, in this embodiment, when there is a change in the connection information, only the difference information from the previous time is transmitted from the connection source device A to the connection destination device B, and the connection information stored in the connection source device A The synchronization is performed so that 112A and the connection information 112B stored in the connection destination device B always match. By doing so, even when the system configuration changes and the cable connection configuration changes, the connection information 112B stored in the connection destination device B can be simply modified by correcting the connection information 112A stored in the connection source device A. Are automatically corrected, and can be easily handled. In addition, as the device configuration increases, the amount of information becomes enormous. However, as described above, only the difference information from the previous time is transmitted from the connection source device A to the connection destination device B, thereby reducing the time required for synchronization and by synchronous communication. Overhead can be reduced.

  3 is a flowchart showing the operation contents of the CPU 100A in the connection source apparatus A of FIG. 1, and FIG. 4 is a flowchart showing the operation contents of the CPU 100B in the connection destination apparatus B of FIG.

As shown in these figures, the CPU 100A in the connection source device A and the CPU 100B in the connection destination device B are both in a standby state until receiving an event from the outside, and when receiving the event thereafter (steps S10 and S60), The event type is determined (steps S12 and S62), and corresponding processing is executed according to the event type (steps S14 to S18 and S64 to S68).
Hereinafter, the content of the process executed according to the event type will be described. Note that the processing in steps S20 and S22 in FIG. 3 and step S70 in FIG. 4 will be described in Modification 1 described later.

B-1. Device mode change processing (change to connection destination confirmation mode):
Each of the connection source device A and the connection destination device B can adopt either the “normal mode” or the “connection destination confirmation mode” as the mode of the entire device, that is, the device mode. In addition, for each port mounted on the connection source device A and the connection destination device B, either one of “normal mode” and “connection destination confirmation mode” can be adopted as the operation mode of the link LED. .

  Therefore, first, a mode change event is transmitted from the management terminal C to the connection source device A, and the CPU 100A in the connection source device A receives the event from the connection terminal RPA via the input / output interface 120A (step S10). If it is determined that the event type is a mode change event (step S12), the CPU 100A executes a device mode change process (step S14). Note that the mode change event is one of a connection port confirmation start event and a connection port confirmation end event, as will be described later.

  FIG. 5 is a flowchart showing the contents of the device mode change process executed by the CPU 100A in the connection source device A of FIG.

  The CPU 100A determines whether or not the device mode is the “normal mode” (step S102). If the device mode is the normal mode, the CPU 100A determines whether or not the received mode change event is a connection port confirmation start event (step S104). ). As a result of the determination, if it is a connection port confirmation start event, the CPU 100A changes the device mode to the “connection destination confirmation mode” (step S106), and the link LED operation mode of all ports mounted on the connection source device A. Is changed to “connection destination confirmation mode” (step S108), and the link LEDs of all the ports are turned off (step S110). Thereafter, the CPU 100A notifies the connection destination apparatus B of the connection port confirmation start event as a mode change event from the management port APA via the input / output interface 120A (step S112), and ends the apparatus mode change process.

  On the other hand, in the connection destination device B, the CPU 100B receives the event from the management port APB via the input / output interface 120B (step S60), and determines that the event type is a mode change event (step S62). The CPU 100B executes device mode change processing (step S64).

  FIG. 6 is a flowchart showing the contents of the device mode change process executed by the CPU 100B in the connection destination device B of FIG.

  The CPU 100B determines whether or not the device mode is “normal mode” (step S602). If the device mode is “normal mode”, the CPU 100B determines whether or not the received mode change event is a connection port confirmation start event ( Step S604). As a result of the determination, if it is a connection port confirmation start event, the CPU 100B changes the device mode to the “connection destination confirmation mode” (step S606), and the link LED operation mode of all ports mounted on the connection destination device B. Is changed to “connection destination confirmation mode” (step S608), and the link LEDs of all the ports are turned off (step S610), and the device mode change processing is terminated.

  In most existing relay apparatuses, the specification is such that the link LED is turned on according to the operating state of the port. In this embodiment, the method of turning on the link LED when checking the connection port as described later. Then, it becomes impossible to distinguish from the normal operation of the link LED (that is, the operation indicating the operation state of the port). Therefore, in this embodiment, when the connection destination confirmation work is started, as described above, the device modes of the connection source device A and the connection destination device B are changed by the mode change event transmitted from the management terminal C. Then, each shifts to the “connection destination confirmation mode”, and all the link LEDs are turned off in order to separate the operation state of each port from the state of the link LED.

  By the way, in the device mode change process in the connection source device A, if the result of determination in step S104 is not a connection port confirmation start event but a connection port confirmation end event, the CPU 100A, via the input / output interface 120A, A message is output from the connection terminal RPA to the management terminal C that the device mode is already “normal mode” (step S114), and the device mode changing process is terminated. On the other hand, in the device mode change process in the connection destination device B, if the result of determination in step S604 is a connection port confirmation end event, the CPU 100B ends the device mode change process as it is.

  The operation when it is determined in step S102 in FIG. 5 and step S602 in FIG. 6 that the device mode is the “connection destination confirmation mode” will be described later.

B-2. Connection destination confirmation target notification process:
Next, a connection destination confirmation target notification event is transmitted from the management terminal C to the connection source device A, and the CPU 100A in the connection source device A receives the event from the connection terminal RPA (step S10). Is determined to be a connection destination confirmation target notification event (step S12), the CPU 100A executes a connection destination confirmation target notification process (step S16). Note that the connection destination confirmation target notification event from the management terminal C includes a port number and an LA group number in order to specify the connection destination confirmation target.

  FIG. 7 is a flowchart showing the contents of the connection destination confirmation target notification process executed by the CPU 100A in the connection source apparatus A of FIG.

  After identifying the connection destination confirmation target from the received connection destination confirmation target notification event (step S151), the CPU 100A determines whether or not the device mode is the “connection destination confirmation mode” (step S152). As a result of the determination, if it is in the connection destination confirmation mode, the CPU 100A turns off the link LEDs of all the ports mounted on the connection source apparatus A (step S154), and whether or not the connection destination confirmation target is physical port designation. Is determined (step S156). When the connection destination confirmation target is specified as the port number, it is determined that the physical port is specified, and when it is specified as the LA group number, it is determined that the logical port is specified. If the physical port is specified as a result of the determination, the CPU 100A determines whether or not the corresponding port number exists in the connection information 112A stored in the memory 110A (step S158). In this case, the link LED of the corresponding port is lit in green (step S160), the number of the connection entry corresponding to the corresponding port number is derived from the connection information 112A, and the management port APA is used as the connection destination confirmation target notification event. To the connection destination device B (step S162), and the connection destination confirmation target notification process is terminated.

  Therefore, for example, when the port number corresponding to the connection destination confirmation target is “4”, the port number exists in the connection information (specifically, connection entry # 4) as shown in FIG. The link LED αA4 of the connection port PA4 corresponding to the number “4” is lit in green.

  If it is determined in step S156 that the logical port is designated, the CPU 100A determines whether or not the corresponding LA group number exists in the connection information 112A (step S164). The link LEDs of all the ports belonging to the corresponding LA group are lit in green (step S166), and the connection entry number corresponding to the corresponding LA group number is derived from the connection information 112A, and the connection destination confirmation target notification is made. As an event, the connection destination device B is notified from the management port APA (step S168), and the connection destination confirmation target notification process is terminated.

  Therefore, for example, when the LA group number corresponding to the connection destination confirmation target is “2”, as shown in FIG. 2, it exists in the connection information (specifically, connection entries # 2, # 3). Since the port numbers belonging to the LA group with the number “2” are “2” and “3”, the link LEDs αA2 and αA3 of the connection ports PA2 and PA3 corresponding to the port numbers “2” and “3” Are lit in green.

  On the other hand, in the connection destination device B, when the CPU 100B receives the event from the management port APB (step S60) and determines that the event type is a connection destination confirmation target notification event (step S62), the CPU 100B A connection destination confirmation target notification process is executed (step S66).

  FIG. 8 is a flowchart showing the contents of the connection destination confirmation target notification process executed by the CPU 100B in the connection destination device B of FIG.

  After acquiring the connection entry number from the received connection destination confirmation target notification event (step S651), the CPU 100B determines whether or not the device mode is the “connection destination confirmation mode” (step S652). As a result of the determination, if it is in the connection destination confirmation mode, the CPU 100B turns off the link LEDs of all the ports mounted on the connection destination device B (step S654), and stores the acquired connection entry number in the memory 110B. It is determined whether or not the connection information 112B is present (step S658), and if it exists, the link LED of the port corresponding to the corresponding connection entry is lit in green (step S660), and the connection destination The confirmation target notification process is terminated.

  Therefore, for example, when “# 4” is acquired as the connection entry number, as shown in FIG. 2, the connection entry number exists in the connection information, and the connection entry corresponding to the connection entry with the number “# 4” is present. Since the port number of the destination device B is “5”, the link LED αB5 of the connection port PB5 corresponding to the port number “5” is lit in green. For example, when “# 2” and “# 3” are acquired as connection entry numbers, the connection entry numbers are present in the connection information as shown in FIG. The port number of the connection destination device B corresponding to the connection entry is “10” and the port number of the connection destination device B corresponding to the connection entry of the number “# 3” is “15”. The link LEDs αB10 and αB15 of the connection ports PB10 and PB15 corresponding to “10” and “15” are respectively lit in green.

  As described above, before the connection ports are actually connected to each other between the connection source device A and the connection destination device B with the cable, the link LED of the port that is the connection destination confirmation target is set in each of the devices A and B. By turning on the green light, the user can visually confirm the position of the port to which the cable is to be connected in an easy-to-understand manner. In addition, since the port to which the cable is to be connected is specified based on the connection destination confirmation target instructed from the management terminal C or connection information stored in advance, unintended communication or network failure due to a connection error is detected in advance. It can also be prevented.

  By the way, in the connection destination confirmation target notification process in the connection source apparatus A, if the corresponding port number does not exist in the connection information 112A as a result of the determination in step S158, the CPU 100A determines from the connection terminal RPA to the management terminal. A message is output to C that the corresponding port number does not exist in the connection information (step S174), and the connection destination confirmation target notification process is terminated. Similarly, if the result of determination in step S164 is that the corresponding LA group number does not exist in the connection information 112A, the CPU 100A sends the corresponding LA group number from the connection terminal RPA to the management terminal C. Is output from the connection information (step S172), and the connection destination confirmation target notification process is terminated. Furthermore, if the result of determination in step S152 is that the device mode is “normal mode”, the CPU 100A outputs a message from the connection terminal RPA to the management terminal C that the device mode is not “connection destination confirmation mode”. (Step S170), the connection destination confirmation target notification process is terminated. On the other hand, in the connection destination confirmation target notification process in the connection destination device B, if the acquired connection entry number does not exist in the connection information 112B as a result of the determination in step S658, or the result of the determination in step S652, the device When the mode is “normal mode”, the CPU 100B ends the connection destination confirmation target notification process as it is.

B-3. Interrupt event handling processing:
Next, interrupt event handling processing, which is processing when the connection ports are connected between the connection source device A and the connection destination device B with a cable, or when the cable is removed from the connection port, will be described. In the following, in order to distinguish the connection port of the connection source device A from the connection port of the connection destination device B, the connection port of the connection source device A is referred to as “connection source port”, and the connection port of the connection destination device B is referred to as “connection port”. Sometimes referred to as “connection port”.

  9 is a flowchart showing the contents of the interrupt event processing executed by the CPU 100A in the connection source apparatus A of FIG. 1, and FIG. 10 is a flowchart showing the contents of the interrupt event processing executed by the CPU 100B in the connection destination apparatus B of FIG. is there.

  Both the CPU 100A in the connection source device A and the CPU 100B in the connection destination device B are in a standby state until an interrupt event is detected. Then, by the connection destination confirmation target notification process described above, the connection source device A and the connection destination device B in the connection source device A and the connection destination device B in a state where the link LED of the port to be connected is lit in green. When the connection ports are connected to each other with a cable, the connected ports are linked up. That is, the connection port becomes in a communicable state when the cable is connected.

  For example, in the connection source device A, when the connection port PA4 with the port number “4” is linked up, the connection port PA4 generates a link up event as an interrupt event. When CPU 100A detects the interrupt event via input / output interface 120A (step S30), CPU 100A determines whether the interrupt event is a link-up event (step S32). Is “connection destination confirmation mode” (step S34). As a result of the determination, if it is “connection destination confirmation mode”, the CPU 100A determines from the connection information 112A stored in the memory 110A the number of the connection entry to which the linked connection port (that is, the connection source port) PA4 belongs ( In this case, the connection entry number “# 4”) is acquired, and the connection destination device uses the connection entry number “# 4” of the connection source port as the link-up confirmation event from the link-up connection source port PA4. B is notified (step S36), and the interrupt event handling process is terminated.

  On the other hand, in the connection destination device B, for example, when the connection port PB5 with the port number “5” is linked up, the connection port PA5 generates a link up event as an interrupt event. When the CPU 100B detects the interrupt event via the input / output interface 120B (step S80), the CPU 100B determines whether or not the interrupt event is a link-up event (step S82). Is “connection destination confirmation mode” (step S84). If the result of the determination is “connection destination confirmation mode”, the CPU 100B determines from the connection information 112B stored in the memory 110B the number of the connection entry to which the link-up connection port (ie, connection destination port) PB5 belongs ( In this case, the connection entry number “# 4”) is acquired, and the connection source device uses the connection entry number “# 4” of the connection destination port from the connection destination port PB5 linked up as a confirmation event at the time of link up. A is notified (step S86), and the interrupt event handling process is terminated.

  By the way, in the connection source device A and the connection destination device B, when the cable is removed from the connection port while the cable is connected to the connection port, the removed port is linked down. That is, the connection port becomes unable to communicate because the cable is removed. When the connection port is linked down, the connection port generates a link down event as an interrupt event.

  In the interrupt event handling process in the connection source device A and the connection destination device B, when the interrupt event is a link down event as a result of the determination in steps S32 and S82, the CPU 100A, 100B has the device mode “connection destination confirmation mode”. (Steps S40 and S90), and if it is in the “connection destination confirmation mode”, the connection destination confirmation target notification event being confirmed is retransmitted to the own device (steps S42 and S92), and the interrupt event The corresponding process is terminated.

  Further, in the interrupt event handling processing in the connection source device A and the connection destination device B, if the device mode is “normal mode” as a result of the determination in steps S34 and S84, the CPUs 100A and 100B connect the linked up connections. The link LED of the port is lit in green (steps S38 and S88), and the interrupt event handling process is terminated. Similarly, when the device mode is “normal mode” as a result of the determination in steps S40 and S90, the CPUs 100A and 100B turn on the link LED of the connection port that has been linked down (steps S44 and S94). Then, the interrupt event handling process ends.

B-4. Connection confirmation process during link up:
Next, a link up confirmation event is transmitted from the connection destination device B to the connection source device A, and the CPU 100A in the connection source device A receives the event from a certain connection port (step S10 in FIG. 3). If it is determined that the event type is a link-up confirmation event (step S12), the CPU 100A executes a link-up connection destination confirmation process (step S18). The link up confirmation event from the connection destination device B includes the connection entry number of the connection destination port as described above.

  FIG. 11 is a flowchart showing the contents of the link-up connection destination confirmation process executed by the CPU 100A in the connection source apparatus A of FIG.

  The CPU 100A acquires the connection entry number from the received link-up confirmation event, and refers to the connection information 112A stored in the memory 110A to identify the connection destination port (step S182). For example, when “# 4” is acquired as the connection entry number, the port number of the connection destination apparatus B corresponding to the connection entry with the number “# 4” is “5” as shown in FIG. The connection destination port is specified as the connection port PB5 of the boat number “5” in the connection destination device B.

  Next, the CPU 100A determines whether or not the connection source port that has received the link-up confirmation event is a port that has been a connection destination confirmation target (step S184). For example, when the connection source port that received the link up confirmation event is the connection port PA4 with the port number “4”, the CPU 100A determines that the connection port PA4 is the management terminal C during the connection destination confirmation target notification process. It is determined whether or not the port is a connection destination confirmation target port (see step S151 in FIG. 7) instructed by.

  As a result of the determination, if the connection source port is the connection destination confirmation target port, the CPU 100A further determines whether or not the connection destination port identified in step S182 is the port that was the connection destination confirmation target. (Step S186). Specifically, for example, the CPU 100A determines that the connection entry number acquired in step S182 is the connection entry number notified as the connection destination confirmation target notification event during the connection destination confirmation target notification process (see step S162 in FIG. 7). ), If it matches, it is determined that the connection destination port specified in step S182 is a port to be connected, and if it does not match, it is specified in step S182. It is determined that the connection destination port is not a connection destination confirmation target port.

  As a result of the determination, if the connection destination port is also a connection destination confirmation target port, both the connection source device A and the connection destination device B are connected to the correct connection port (that is, the cable is connected in the connection destination confirmation target notification process). Since the link LED is connected to the connection port in which the link LED is lit in green), the CPU 100A turns on the link LED of the connection source port that received the link up confirmation event in green (step S188). The connection confirmation process at the time of up ends.

  By the way, in the connection destination confirmation process at the time of link up in the connection source device A, as a result of the determination in step S184, if the connection source port that received the link up confirmation event is not the connection destination confirmation target port, the connection source In apparatus A, since the cable is connected to an incorrect connection port (that is, a connection port whose link LED is not lit green in the connection destination confirmation target notification process), CPU 100A receives the confirmation event at the time of link up. The link LED of the connected source port is lit in orange (step S190), and the connection destination confirmation process at the time of link up is completed.

  As a result of the determination in step S186, if the connection destination port identified in step S182 is not the connection destination confirmation target port, the connection source device A has connected the cable to the correct connection port. In the destination device B, since the cable is connected to the wrong connection port, the CPU 100A alternately blinks the link LED of the connection source port that has received the confirmation event at the time of link up in green and orange (step S192). Terminates the connection destination confirmation process at the time of link up.

  On the other hand, a link-up confirmation event is transmitted from the connection source device A to the connection destination device B, and the CPU 100B in the connection destination device B receives the event from a certain connection port (step S60 in FIG. 4). If it is determined that the event type is a link up confirmation event (step S62), the CPU 100B executes a link up connection destination confirmation process (step S68). Note that the link up confirmation event from the connection source device A includes the connection entry number of the connection source port as described above.

  FIG. 12 is a flowchart showing the contents of the link-up connection destination confirmation process executed by the CPU 100B in the connection destination device B of FIG.

  As is apparent from the figure, the connection destination confirmation process at the time of link up in the connection destination device B is the same as the connection destination confirmation process at the time of link up in the connection source device A shown in FIG. Is omitted.

  As described above, when the connection destination confirmation process at the time of link up is executed, if the cable is connected to the wrong connection port, the link LED of the connection port lights in orange or alternately blinks green and orange. Makes it possible to immediately detect misconnections. In other words, the link LED of the correct connection port to which the cable is originally connected remains lit in green, and the link LED of the erroneously connected port is lit in a different color. be able to. In addition, it is possible to construct a connection configuration of relay devices between networks accurately in a short time.

B-5. Device mode change processing (change to normal mode):
In the device mode change process described above, the operation when changing to the “connection destination confirmation mode” has been described in order to start connection destination confirmation work etc. when the device mode is “normal mode”. In the case where the device mode is the “connection destination confirmation mode”, the operation for returning to the “normal mode” after completing the connection destination confirmation work will be described.

  As shown in FIG. 5, in the device mode change process in the connection source device A, if the device mode is “connection destination confirmation mode” as a result of the determination in step S102, the CPU 100A has received from the management terminal C. It is determined whether or not the mode change event is a connection port confirmation end event (step S116). As a result of the determination, if it is a connection port confirmation end event, the CPU 100A changes the device mode to “normal mode” (step S118) and sets the LED operation modes of all ports mounted on the connection source device A to “normal”. The mode is changed to “mode” (step S120), and the LEDs of all the ports are reset according to the operating state of each port (step S122). Thereafter, the CPU 100A notifies the connection destination device B of the connection port confirmation end event as a mode change event from the management port APA via the input / output interface 120A (step S124), and ends the device mode change processing.

  On the other hand, as shown in FIG. 6, even in the device mode change process in the connection destination device B, if the device mode is “connection destination confirmation mode” as a result of the determination in step S <b> 602, the CPU 100 </ b> B It is determined whether or not the received mode change event is a connection port confirmation end event (step S616). As a result of the determination, if it is a connection port confirmation end event, the CPU 100B changes the device mode to “normal mode” (step S618) and sets the LED operation mode of all ports mounted on the connection destination device B to “normal”. The mode is changed to “mode” (step S620), and the LEDs of all the ports are reset according to the operation state of each port (step S622), and the device mode changing process is terminated.

  Thus, in this embodiment, when the connection destination confirmation work is finished, the device modes of the connection source device A and the connection destination device B are changed to “normal” in response to the mode change event transmitted from the management terminal C. To return to "mode".

C. Effects of the embodiment:
As described above, the present embodiment has the following effects.
(1) In the connection source device A and the connection destination device B, by illuminating only the link LED, the position of the port to be connected can be instructed visually and easily.
(2) Even when the system configuration changes and the cable connection configuration changes, it can be easily handled by correcting the connection information.
(3) Since it is possible to instruct a port to be connected before cable connection, unintended communication and network failure due to a connection error can be prevented.
(4) Even when the connection is wrong, the link LED indicating fraud is lit, so that a user (worker) mistake can be detected early.

D. Variation:
The present invention is not limited to the above-described examples and embodiments, and can be implemented in various modes without departing from the scope of the invention.

D-1. Modification 1:
In the above-described embodiment, the connection information stored in the connection source device A and the connection destination device B is preset by the user (administrator) and transmitted from the management terminal C to the connection source device A. Is not limited to this, and can be automatically generated from network configuration information set in advance in the connection source device A and the connection destination device B. The automatic generation of such connection information will be described below.

  First, the network configuration information 114A corresponding to the connection source device A is stored in the memory 110A of the connection source device A, and the network configuration information 114B corresponding to the connection destination device B is stored in the memory 110B of the connection destination device B, respectively. Stored.

  Therefore, a connection information automatic generation event is transmitted from the management terminal C to the connection source device A, and the CPU 100A in the connection source device A receives the event from the connection terminal RPA (step S10 in FIG. 3). If it is determined that the type is a connection information automatic generation event (step S12), the CPU 100A executes a network configuration information acquisition request process (step S20).

  FIG. 13 is a flowchart showing the contents of the network configuration information acquisition request process executed by the CPU 100A in the connection source apparatus A of FIG. As illustrated in FIG. 13, the CPU 100A notifies a network configuration information acquisition request event from the management port APA to the connection destination device B (step S202), and ends the network configuration information acquisition request process.

  On the other hand, in the connection destination device B, when the CPU 100B receives the event from the management port APB (step S60) and determines that the event type is a network configuration information acquisition request event (step S62), the CPU 100B A network configuration information acquisition response process is executed (step S70).

  FIG. 14 is a flowchart showing the contents of the network configuration information acquisition response process executed by the CPU 100B in the connection destination apparatus B of FIG. As shown in FIG. 14, the CPU 100B acquires the network configuration information 114B corresponding to the connection destination device B from the memory 110B, and notifies the connection destination device B from the management port APB as a network configuration information acquisition response event. (Step S702), the network configuration information acquisition response process is terminated.

  On the other hand, in the connection source device A, the CPU 100A receives the event from the management port APA (step S10 in FIG. 3), and determines that the event type is a network configuration information acquisition response event (step S12). CPU 100A executes connection information automatic generation processing (step S22).

  FIG. 15 is a flowchart showing the contents of connection information automatic generation processing executed by the CPU 100A in the connection source apparatus A of FIG. As shown in FIG. 15, first, the CPU 100A acquires the network configuration information 114A corresponding to the connection source device A from the memory 110A (step S212), and the connection destination device B from the received network configuration information acquisition response event. The network configuration information 114B corresponding to is acquired (step S214). Then, the CPU 100A compares the acquired network configuration information 114A corresponding to the connection source device A with the network configuration information 114B corresponding to the connection destination device B, and automatically generates connection information according to a desired algorithm. (Step S216).

  FIG. 16 is an explanatory diagram showing an example of the network configuration information of the connection source device A, the network configuration information of the connection destination device B, and connection information generated from them. As shown in FIG. 16, the network connection information includes a port number, an LA group number, and a VLAN (Virtual LAN) number. In FIG. 16, the connection information is automatically generated as follows. In other words, the network configuration information of the connection source device A is used as a reference, and the port numbers are assigned in ascending order.

  Specifically, in the network configuration information of the connection source apparatus A, since the LA group number “1” and the VLAN number “2” correspond to the port number “1”, the LA group number “1”, When a port number that matches the VLAN number “2” is searched from the network configuration information of the connection destination device B, “9” is obtained as the port number having the smallest value. Therefore, for the connection entry “# 1” of the connection information, the port number “1” and the LA group number “1” are allocated from the network configuration information of the connection source device A, and the network configuration information of the connection destination device B A port number “9” and an LA group number “1” are allocated. Next, in the network configuration information of the connection source apparatus A, the LA group number “2” and the VLAN number “3” correspond to the port number “2”. When a port number matching “3” is searched from the network configuration information of the connection destination apparatus B, “14” is obtained as the port number having the smallest value. Therefore, for the connection entry “# 2” of the connection information, the port number “2” and the LA group number “2” are allocated from the network configuration information of the connection source device A, and the network configuration information of the connection destination device B A port number “14” and an LA group number “2” are allocated. Next, in the network configuration information of the connection source device A, since the port number “3” corresponds to only the VLAN number “10”, the port number that matches the VLAN number “10” is set as the connection destination device. When searching from the network configuration information of B, “1” is obtained as the port number having the smallest value. Therefore, for the connection entry “# 3” of the connection information, the port number “3” is allocated from the network configuration information of the connection source apparatus A, and the port number “1” is allocated from the network configuration information of the connection destination apparatus B. . In the same manner, port numbers and LA group numbers are allocated to connection entry “# 24”.

  When the connection information is automatically generated in this way, the CPU 100A stores the generated connection information in the memory 110A and transmits the connection information to the connection destination device B. The connection information is synchronized with the device B (step S218), and the connection information automatic generation process is terminated.

D-2. Modification 2:
In the above-described embodiment, in the connection source device A and the connection destination device B, the link LED is used not only to indicate the operation state of the port but also to check the connection of the port. However, the present invention is not limited to this. For each port, a connector check LED may be provided exclusively for port connection confirmation separately from the link LED. That is, in this case, the lighting of the link LED is controlled by the CPU so as to display the operation state of the corresponding port, and the connector check LED is a port to which the corresponding port is to be connected to the cable by the CPU. The lighting is controlled so that it can be identified.

  Therefore, by providing such a connector check LED, even if the connection port is in the normal mode, the port check status is displayed by the link LED without turning off the LED, and the port to be connected by the connector check LED. Identification is also possible.

D-3. Modification 3:
In the above-described embodiment, in the connection destination confirmation target notification process, the connection destination confirmation target is received in each of the devices A and B when the connection destination confirmation target notification event is transmitted from the management terminal C to the connection source device A. By illuminating the link LED of the port that is green, the position of the port to which the cable is to be connected can be confirmed visually and easily. However, the present invention is not limited to this. For example, in each connection port of the connection source device A, a mechanism for detecting the connection of the cable is mounted, and when the cable is connected to the connection port of the connection source device A, the cable in the connection destination device B The link LED of the port to be connected to may be lit in green so that the connection destination port can be confirmed.

  Specifically, for example, in the connection source apparatus A, when a cable is connected to a certain connection port, if the connection detection unit detects the connection of the cable, the CPU 100A performs step S162 shown in FIG. As a result, the number of the connection entry corresponding to the corresponding port number is derived from the connection information 112A, and is notified from the management port APA to the connection destination device B as a connection destination confirmation target notification event. Thereby, in the connection destination apparatus B, the CPU 100B may acquire the connection entry number from the received connection destination confirmation target notification event, and the link LED of the port corresponding to the acquired connection entry may be lit in green.

D-4. Modification 4:
In the above-described embodiment, as a method of lighting the link LED, when displaying a connection port to which a cable is to be connected, green lighting is performed. When there was an incorrect connection in the device, the green and orange were alternately flashing, and when both the device and other devices were properly connected, the green flashing was made. The present invention is not limited to such a lighting method, and any lighting method can be used as long as the lighting method can be identified by the user. For example, instead of turning on the link LED of the target connection port in green to display the connection port to which the cable should be connected, the link LED of the target connection port is turned off and all other connections are made. Even if the link LED of the port is turned on, the position of the connection port to which the cable should be connected can be grasped from the user's perspective.

D-5. Modification 5:
In the above-described embodiment, the number of connection ports is 24 in both the connection source device A and the connection destination device B. However, other numbers may be used. Further, the number of the connection source device A and the connection destination device B may be different.

D-6. Modification 6:
In the above-described embodiment, two relay devices A and B are targeted. However, the present invention is not limited to two devices, and three or more relay devices are connected to each other by a cable. It can also be applied to.

It is explanatory drawing which shows the network connection system using the relay apparatus as one Example of this invention. It is explanatory drawing which shows an example of the connection information stored in the connection origin apparatus A and the connection destination apparatus B of FIG. It is a flowchart which shows the operation | movement content of CPU100A in the connection origin apparatus A of FIG. FIG. 4 is a flowchart showing the operation content of the CPU 100B in the connection destination device B of FIG. It is a flowchart which shows the content of the apparatus mode change process which CPU100A in the connection origin apparatus A of FIG. 1 performs. It is a flowchart which shows the content of the apparatus mode change process which CPU100B in the connecting point apparatus B of FIG. 1 performs. It is a flowchart which shows the content of the connection destination confirmation object notification process which CPU100A in the connection origin apparatus A of FIG. 1 performs. It is a flowchart which shows the content of the connection destination confirmation object notification process which CPU100B in the connection destination apparatus B of FIG. 1 performs. It is a flowchart which shows the content of the interruption event process which CPU100A in the connection origin apparatus A of FIG. 1 performs. It is a flowchart which shows the content of the interrupt event process which CPU100B in the connecting point apparatus B of FIG. 1 performs. It is a flowchart which shows the content of the connection confirmation process at the time of link up which CPU100A in the connection origin apparatus A of FIG. 1 performs. It is a flowchart which shows the content of the link destination connection destination confirmation process which CPU100B in the connection destination apparatus B of FIG. 1 performs. It is a flowchart which shows the content of the network configuration information acquisition request process which CPU100A in the connection origin apparatus A of FIG. 1 performs. It is a flowchart which shows the content of the network configuration information acquisition response process which CPU100B in the connecting point apparatus B of FIG. 1 performs. It is a flowchart which shows the content of the connection information automatic generation process which CPU100A in the connection origin apparatus A of FIG. 1 performs. It is explanatory drawing which shows an example of the network configuration information of the connection origin apparatus A, the network configuration information of the connection destination apparatus B, and the connection information produced | generated from them.

Explanation of symbols

100A, 100B ... CPU
110A, 110B ... Memory 112A, 112B ... Connection information 114A, 114B ... Network configuration information 120A, 120B ... Input / output interface 202 ... Cable A ... Connection source device (relay device)
B ... Connection destination device (relay device)
APA, APB ... management port PA1-PA24, PB1-PB24 ... connection port RPA, RPB ... connection terminal αA1-αA24, αB1-αB2 ... link LED

Claims (9)

A relay device for configuring a communication network,
Multiple connection ports,
A plurality of lighting sections provided corresponding to each connection port;
A receiving unit for receiving external events;
A storage unit for storing connection information indicating a connection relationship of cables between connection ports with other devices;
A control unit;
With
The control unit specifies a connection port to which a cable is to be connected among the plurality of connection ports based on information included in the event received via the reception unit and the connection information, and specifies the specified connection A relay device characterized in that the lighting unit is lit so that a port can be distinguished from other connection ports. The relay device according to claim 1,
The control unit, when the cable is connected to the connection port, based on the information included in the event received through the reception unit and the connection information, the cable is connected to the own device and the other A relay device characterized in that it is determined whether or not a connection port to which a cable in the device is connected is correctly connected, and the lighting unit is turned on based on the determination result. The relay device according to claim 2,
When the control unit determines that the cable is connected to an incorrect connection port other than the connection port to which the cable is to be connected, the control unit is erroneous in any of the own device and the other device. A relay device characterized in that the lighting unit is lit so that it can be distinguished whether it is connected to a connection port. In the relay device according to any one of claims 1 to 3,
It further comprises a management port connectable to the other device with a cable,
The control unit transmits at least a part of the connection information to the other device via the management port. In the relay device according to any one of claims 1 to 4,
The storage unit further stores first network configuration information related to the device for configuring the communication network,
The control unit acquires second network configuration information related to the other device from the other device, and based on the stored first network configuration information and the acquired second network configuration information A relay device that generates the connection information. In the relay device according to any one of claims 1 to 5,
Separately from the lighting part, further comprising a plurality of operating state display lighting parts provided corresponding to each connection port,
The said control part makes the said operation state display lighting part light so that the operation state of a corresponding connection port may be displayed, The relay apparatus characterized by the above-mentioned. In the relay device according to any one of claims 1 to 6,
The control unit is logically bundled as a connection port to which a cable is to be connected among the plurality of connection ports based on the information included in the event received via the reception unit and the connection information. A relay apparatus characterized in that, when a plurality of physical ports to be used are specified, the lighting unit is lit so that the specified plurality of physical ports and other connection ports can be distinguished. In the relay device according to any one of claims 1 to 7,
A connection detector for detecting the connection of the cable to the connection port;
When the connection detection unit detects the connection of the cable, the control unit refers to the connection information, and specifies information for specifying a connection port to which the cable is to be connected in the other device. A relay device that notifies the device. A control method for controlling a relay device for configuring a communication network,
The relay device is
Multiple connection ports,
A plurality of lighting sections provided corresponding to each connection port,
A storage unit for storing connection information indicating a connection relationship of cables between connection ports with other devices;
With
The control method is:
(A) receiving an event from outside;
(B) identifying a connection port to which a cable is to be connected among the plurality of connection ports based on the information included in the received event and the connection information;
(C) turning on the lighting unit so that the identified connection port can be distinguished from other connection ports;
A control method comprising:

Images