JP2011061623A - Network system, hub device and faulty node specifying method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a network system that is enhanced in resistance to a system down. <P>SOLUTION: On a network formed using ARCNET(R), a function of monitoring a state of a token path is mounted on Active-Hub 100 to which a node is connected. Namely, a token capture part 50a captures a token, a monitor processing unit 50b monitors a destination node ID of the token, and a specification processing unit 50c specifies a faulty node from results thereof. Once the faulty node is specified, a port connected to the node is disconnected to isolate the faulty node from the network. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a network system conforming to ARCNET (Attached Resource Computer Network) (registered trademark), a hub apparatus used in the system, and a failure node identifying method.

  In recent years, many of the old analog broadcasting facilities have been digitized, and this trend is certain to continue to develop. Against this background, facilities for controlling various broadcasting devices have also been digitized. This type of automatic program transmission control equipment is formed by connecting controlled devices such as a recorder that stores video materials and a switcher that switches a plurality of videos via a LAN (Local Area Network). For such applications, ARCNET (registered trademark), which has strength in real-time control, is generally used.

  The feature of ARCNET (registered trademark) is that the network adopts a token passing system, and that the configuration data reconstruction process at the physical layer level is started immediately after the network topology changes. By providing such a function, it can be said that ARCNET (registered trademark) has a relatively high degree of freedom in topology.

  On the other hand, if there is a node that repeatedly issues a reconstruction request signal (burst signal) due to some failure, the node on the LAN cannot pass the token (usage right) to the next node (token pass), Token circulation in the network stops. If such a situation occurs, the entire LAN goes down, and there is a risk that no communication will be possible.

  For example, a technique for preventing network down in an optical LAN employing a token ring system is known (see Patent Document 1), but this technique cannot be applied to ARCNET (registered trademark). There is a demand for a technology that can cope with the generation of a burst signal due to the specifications of ARCNET (registered trademark) and can prevent the ARCNET (registered trademark) -LAN from going down.

JP-A-11-261618

As described above, in ARCNET (registered trademark), when a node that continues to output a burst signal appears, tokens cannot be transferred between the nodes because of network specifications. If such a situation occurs, the entire system may go down, and some countermeasure is required.
The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a network system, a hub device, and a faulty node identification method that have improved resistance to system down.

  In order to achieve the above object, according to one aspect of the present invention, in a network system that operates a network formed by a plurality of nodes using the ARCNET (registered trademark) protocol, an identifier # 255 is assigned to one of the plurality of nodes. A plurality of nodes, when the state where the token has not been reached continues for a certain period of time, a reconfiguration request for sending a burst signal to the network to request reconfiguration of the circulation route of the token And reconstructing means for reconstructing the network by sending the token to the network while incrementing a destination node identifier when the burst signal is detected, and the monitoring node uses the reconstruction means to Is sent from (# 255) to ( 256), incrementing in the order of (# 00), capturing means for capturing a token that circulates in the network, a register for recording a destination node identifier written in the captured token, and before and after the reconstruction And a specifying means for specifying a node that has transmitted the burst signal based on the result of comparing the contents of the registers.

  By taking such measures, the destination node recorded in each token is recorded in the register in the monitoring node. In ARCNET (registered trademark), the node IDs (identifiers) # 01 to # 255 can be set as destinations. For example, these lists may be managed by setting a flag. Further, in the present invention, including the node IDs # 00 and # 256, the destination node ID of the token is incremented as the reconstruction progresses. Therefore, by monitoring the change over the specified period, it is possible to specify whether or not reconstruction has occurred, and further, the node (failure node) that transmitted the burst signal.

  According to the present invention, it is possible to provide a network system, a hub device, and a faulty node identification method with improved resistance to system down.

The figure which shows embodiment of the network system concerning this invention. The schematic diagram which shows the logical connection relation of the network system of FIG. The figure which shows an example of the state by which each node was connected to Active-Hub100. The functional block diagram which shows embodiment of Active-Hub100. The functional block diagram which shows embodiment of the control unit 200. FIG. The figure explaining the response | compatibility with the content of the token and the management register 40a. The figure which shows an example of the content of the management register | resistor 40a after a burst signal is transmitted.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. First, ARCNET (registered trademark) will be described. ARCNET (registered trademark) is a network system in which only a node (communication terminal) having a token can transmit a message on a network by passing [usage right] called a token. A node on the network has a network ID (identifier) indicated by a number, and the token circulates the nodes in the order of ID.

  A node that does not transmit a message immediately passes a token to the next node (referred to as a token path). A node that transmits a message transmits a message only when a token is received, and then passes the token to the next node. With this token, a plurality of nodes do not transmit at the same time, and collision on the network can be prevented. A token can be received by all nodes at the same time, but a message can be transmitted only to a node having an ID number in the order next to the number described in the token.

  In ARCNET (registered trademark), when a new node joins the network, the new node sends a signal called [burst] on the network. As a result, transmission from the node having the token is interrupted, and a state where no right to use (token) exists is created. Thereafter, a route around the token is reset by a procedure based on the ARCNET (registered trademark) protocol. Such processing is referred to as reconstruction (reconfiguration).

  Restructuring is also done if the token disappears for some reason. Also, when a failure occurs in a node on the network and the burst signal continues to be output, the node on the network cannot pass the token to the next node and cannot perform any communication. Hereinafter, embodiments capable of solving such problems will be described.

  FIG. 1 is a diagram showing an embodiment of a network system according to the present invention. The system of FIG. 1 is configured by connecting a plurality of nodes via a hub device (Active-Hub) 100. Each node is uniquely assigned an identifier (ID) from # 01 to # 255 (FE).

  In other words, in ARCNET (registered trademark), a maximum of 255 nodes can exist (log on) in the same network. A node that actually logs on to the network is assigned a unique ID from # 01 to # 255 (FE). In this embodiment, the identifier # 00 is particularly used as an ID for identifying an abnormal node. Also, a node ID # 255 is assigned to Active-Hub 100, and this Active-Hub 100 is also caused to function as a node.

  In ARCNET (registered trademark), the transmission rights are obtained in order from the node with the largest ID in the token circulation in the reconstruction process. Therefore, by giving # 255 (#FE), which is the maximum value of ID, to Active-Hub 100, Active-Hub 100 can always obtain a token transmission right first, and as a result, it provides a network monitoring function. Can do.

  FIG. 2 is a schematic diagram showing a logical connection relationship of the network system of FIG. ARCNET (registered trademark) is a token-passing protocol, and the logical connection form between nodes is a ring when viewed in the order in which the tokens circulate. If the network state is stable, the token is transmitted in order through the nodes of this ring. In this embodiment, Active-Hub 100 also participates in the network as one node.

  Assume that a node (# 02 in FIG. 2) that cannot receive a token occurs due to some kind of failure. When a state in which the token cannot be received is a certain period, that is, when 840 milliseconds elapse in ARCNET (registered trademark), the internal timer (network state monitoring timer) of the node # 02 times out. Then, the node # 02 immediately sends a burst signal to the network and requests network reconfiguration (reconfiguration). To put it simply, reconfiguration is a process of resetting and resetting the route around which the token circulates. The node that has detected the burst signal immediately starts the reconstruction process.

  FIG. 3 is a diagram illustrating an example of a state in which each node is connected to the Active-Hub 100. In FIG. 3, Active-Hub 100 includes a plurality of ports 1 to 8. Of these, ports 1, 2, 4, 5, and 8 are respectively connected to node # 05, node # 02, node # 10, node # 01, node # 212 Is connected. Active-Hub 100 recognizes (stores) the correspondence between the port number and the node ID in advance.

  FIG. 4 is a functional block diagram showing an embodiment of Active-Hub 100. 4, each port 1, 2, 3,... Of the Active-Hub 100 is connected to the blocking units 11, 21, 31,. .., Are controlled by the control unit 200 to block / connect ports.

  Here, the control unit 200 is assigned ID # 255 (#FE), which is one less than the maximum ID value # 256 (#FF). The control unit 200 functions as one of the nodes to monitor signals introduced from each port and grasp the state of the network in FIG. In particular, the control unit 200 identifies a failed node (failed node) by a method described later, and blocks a port connected to the failed node.

  The Active-Hub 100 further includes a reset button 20 and a light emitting diode (LD) 30. The reset button 20 is used to reconnect the blocked port, and is operated after recovery from the node failure, whereby the recovered node is reconnected to the network. The LD 30 changes the display color, for example, and notifies the network administrator or the like that a blocking port has occurred.

  FIG. 5 is a functional block diagram showing an embodiment of the control unit 200 of the Active-Hub 100. The control unit 200 includes a hardware (H / W) interface unit 10, a memory 40, a CPU (Central Processing Unit) 50, and an ARCNET (registered trademark) chipset 60. Among these, the H / W interface unit 10 is connected to the reset button 20 and the LD 60 and converts an instruction from the CPU 50 into an electric signal.

  The CPU 50 has a token capture unit 50a, a monitor processing unit 50b, a specific processing unit 50c, a blocking processing unit 50d, a notification processing unit 50e as processing functions based on a program stored in the memory 40, and a level close to the physical layer. The firmware 50f supported by is provided.

  The memory 40 includes a management register 40a as a temporary storage unit unique to this embodiment. The management register 40a records a destination node ID (NID: Next Node ID) of a token that circulates between nodes. The management register 40a is used for identifying a failed node and monitoring a node's participation (logon) state in a network. It is done.

  The token capture unit 50a captures a token that circulates within the network. The monitor processing unit 50 b monitors the destination node ID recorded in the captured token and writes the result in the management register 40 a of the memory 40. The identification processing unit 50c identifies the node that has transmitted the burst signal from the contents of the management register 40a.

  The blocking processing unit 50d blocks a port connected to the node specified by the specifying processing unit 50c. That is, the blocking processing unit 50d opens / closes the blocking unit connected to the port to be blocked, and isolates the node connected through the port from the network. When a port blocked by the blocking processing unit 50d is generated, the notification processing unit 50e turns on the LD 30 (FIG. 4) and notifies the user or the network administrator to that effect. Note that the occurrence of a blocking port may be notified to an external server device or the like via a network.

  Next, the ARCNET (registered trademark) chipset 60 is an existing chipset mounted on a node device that conforms to the ARCNET (registered trademark), and includes a token processing unit 60a, a reconstruction processing unit 60b, an internal timer 60c, and a burst. A signal transmission unit 60d is provided. That is, in this embodiment, the control unit 200 also has a function as a node.

  The token processing unit 60a performs processing related to token transmission / reception. When the network status monitoring timer times out when the token has not been reached, the reconstruction processing unit 60b gives an instruction to the burst signal transmission unit 60d, and transmits the burst signal to the network to request network reconstruction. When a burst signal from another node is detected, the reconstruction processing unit 60b starts a network reconstruction process.

  The internal timer 60c is a timekeeping function provided in a node compliant with ARCNET (registered trademark), and in addition to a network state monitoring timer that times out in 840 milliseconds, a network response monitoring timer (timeout in 78 microseconds), and an idle state monitoring timer (Time out at 86 microseconds). Next, the operation of the above configuration will be described.

  FIG. 6 is a diagram for explaining the correspondence between tokens and the contents of the management register 40a. FIG. 6A shows the structure of the token packet and its contents. The token packet comprises an Alert, EOT, and two NID fields. Alert is a header indicating that this packet is control information such as a token, and 6-bit (1) is written therein. (04H) indicating a token is written in EOT, and NID is the destination node ID of the token.

  FIG. 6B shows an example of the contents of the management register 40a when the network is in a stable state (that is, in a normal state). The tokens are nodes having NIDs (01), (02)... (FE). Shows the state of lap. The management register 40a is a 256-bit register, and by setting the flag 1 to the bit corresponding to the NID of the captured token, the ID of the node existing in the network can be managed. The node ID (#FE) is the same as (# 255).

  The firmware 50f periodically samples the contents of the management register 40a at intervals at which the token reception status can be monitored. If the sampled state is the same twice in succession, the data is recorded in the work memory (not shown). If the sampling data does not match the previous sampling data, the current time and the changed bit number are recorded. In other words, the work memory stores the operation history of the management register 40a.

  The management register 40a maintains the state until the clear instruction is received from the firmware 50f once the flag 1 is set. The firmware 50f samples the register and clears the management register 40a if the same state continues twice.

  FIG. 7 is a diagram showing an example of the contents of the management register 40a after the burst signal is transmitted. FIG. 7A shows a state in which tokens turn in the order of nodes scheduled to be repeated, such as node # 1, node # 2,..., Node #FE. FIG. 7B shows the management register 40a at the timing when the token is transmitted from the node #FE to the node #FE immediately after the burst occurs.

  Here, the token processing procedure after burst reception in ARCNET (registered trademark) will be summarized. All the nodes that have received the burst clear the token destination and once stop sending tokens. Each node starts a timer of (255-node ID value) × 146 microseconds, and transmits a token with the node having the next ID number as the destination ID (NID in FIG. 6) from the node that has timed out first. . After the first token is transmitted, the tokens are transferred between the nodes in the order of ID numbers.

  At the start of reconstruction, here, the chip set 60 of the node (# 255) of the control unit 200 to which the largest ID is assigned transmits the token to the next number (# 256). The CPU 50 monitors this token transmission, and bit (1) is set in (# 256 (#FF)) of the management register 40a as shown in FIG. 7B.

  However, since there is no node having the ID number (# 256), the node (# 255) cannot receive the token response even if the response time of 78 microseconds has elapsed. Therefore, the chip set 60 further increments the destination ID, and transmits the next number as the destination (NID), which is the first (# 00) of the next round (FIG. 7C).

  In ARCNET (registered trademark), the NID (# 00) is originally reserved for broadcasting and is not assigned to a node, but in this embodiment, it is used as a temporary destination in the reconstruction process. That is, in this embodiment, a virtual node assigned with # 00 as an ID is provided, and this ID (# 00) is used to identify the failed node.

  In FIG. 7C, since (# 00) is a virtual address, there is no token response, and the control unit 200, that is, the node (# 255) further transmits a token to the next node (# 01). Here, the node (# 255) receives the token response from the node (# 01) for the first time, and the chip set 60 of the control unit 200 sets the token destination (NID) from the next time to (# 01).

  Subsequently, the node (# 01) transmits the token to the node (# 02) in the same manner, but the node (# 2) that has transmitted a burst due to an abnormality (cannot receive the previous token) also responds this time. It cannot be returned to the node (# 1). Therefore, the node (# 01) increments the destination ID number (NID) and continues to the node (# 3) until the next token response is obtained (FIG. 7 (d) (FIG. 7 (e)...). Here, there is a token response from the node (# 5), and the node (# 01) sets the next token destination to (# 05) (FIG. 7 (f)).

  Similarly, the node (# 05) repeats the operation of incrementing and transmitting this token (FIG. 7 (g)). As a result, when the token arrives at the node (#FE) of the control unit 200 once, the management register 40a All the bits of (1) become (1). That is, the management register 40a is also rewritten as shown in FIGS. Thereafter, since a token is transmitted from each node to the node destination set in each node, all (1) including bit 0 is repeated (FIG. 7 (h)).

  In this state, the CPU 50 that monitors the management register 40a clears the management register 40a (FIG. 7 (i)). After clearing, the destination token set in each node is newly written into the management register 40a. Then, as described above, the node (#FE) of the control unit 100 transmits a token to the setting destination node (# 01), and (# 00) is skipped, so the token is not transmitted. After being cleared once, only the bit corresponding to the node to which the token is actually transmitted becomes (1) in the management register 40a.

  With the above procedure, bit 0 is always (0) for normal operation after reconstruction, and FIG. 7 (j) is maintained. Therefore, the firmware 50f monitors bit 0, and if it is (0), it is determined that normal (constant) network operation is being performed, and if (1), it is determined that reconstruction is occurring after a burst has occurred.

  The history of the state of the management register 40a is stored in the memory 40 or other work memory (not shown), and if compared with the current state, the presence / absence of a node used as a token destination (corresponding to each node) It is possible to decipher nodes that have joined or left the network from bit X being 1 or 0).

  That is, when the bit 0 of the management register 40a is (0) and the bit X changes from (0) to (1), the firmware 50f records in the work memory that the node X has joined the network. When bit 0 is (0) and bit X changes from (1) to (0), the fact that node X has left the network is recorded in the work memory.

  In the above procedure, the destination node ID written in the token by the control unit 200 is always monitored using the management register 40a. The management register 40a is periodically sampled and compared with the work memory in which the state of the management register 40a is recorded, and its change is monitored. From the result of monitoring, (1) of bit 0 is detected. To detect whether or not a burst has occurred.

  Furthermore, it is possible to detect to which node the token has been rotated before the reconstruction occurs. Here, for example, comparing FIG. 7 (a) with FIG. 7 (j), the bit corresponding to the node (# 02) has changed from (1) to (0). Can be identified, that is, the node (# 02) in which the failure has occurred.

  Next, in this embodiment, the port connected to the specified failure node is blocked. That is, when the faulty node (# 02) is specified by the specific processing unit 50c of the control unit 200, the cutoff processing unit 50d turns off the cutoff unit 21 of the port 2 connected to the node # 02, and becomes a node causing the fault Isolate (# 02) from the network.

  In summary, in this embodiment, in a network formed using ARCNET (registered trademark), a node ID (#FE) is given to the Active-Hub 100 to which the node is connected to function as a node, and the token path Implement the function to monitor the status. That is, during the reconstruction process, a token is captured by the token capture unit 50a, and the destination node ID of the token monitored by the monitor processing unit 50b is recorded in the management register 40a. Based on the result, the failure processing node 50c identifies the failed node.

  Particularly in this embodiment, (# 00) is used as the destination node ID in the reconstruction process. In other words, the Active-Hub 100 (ID (#FE)) that has first obtained the transmission right performs the token transmission procedure defined in ARCNET (registered trademark) with the original (# 00) as the destination. Therefore, at the time of reconstruction, (1) is written to the 0 bit of the management register 40a. On the other hand, when the token turns to each node in ascending order of ID and the token circulates to the node of the active hub, Becomes 1.

  When all bits (1) are set, this state is stored in the work memory, and then the management register 40a is once cleared. At the subsequent token circulation, only the flag (only the bit corresponding to the node existing in the network) is flagged ( 1) stands. The specific processing unit 50c determines the failed node by comparing and collating the contents of the management register 40a recorded in the work memory with the contents of the management register 40a thereafter. That is, the node that has changed from the network state (1) to (0) managed by the management register 40a before and after the reconfiguration process can be identified as a failure node. When the failed node is specified, the port connected to the node is blocked, and the failed node is isolated from the network. In other words, the failure node is automatically disconnected from the network when a failure is detected, so that the downtime of the entire system can be minimized, and the network system, the hub device, and the failure with increased resistance to the system down. A node identification method can be provided.

  In addition, this invention is not limited to the said embodiment, In an implementation stage, a component can be deform | transformed and embodied in the range which does not deviate from the summary. In addition, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment.

  DESCRIPTION OF SYMBOLS 100 ... Active-Hub, 1-8 ... Port, 11, 21, 31 ... Blocking part, 200 ... Control unit, 20 ... Reset button, 30 ... Light emitting diode (LD), 10 ... Hardware (H / W) interface part , 40 ... Memory, 50 ... CPU (Central Processing Unit), 60 ... ARCNET (registered trademark) chipset, 50a ... Token capture unit, 50b ... Monitor processing unit, 50c ... Specific processing unit, 50d ... Blocking processing unit, 50e ... Notification processing unit, 50f ... firmware, 40a ... management register, 60a ... token processing unit, 60b ... reconstructing processing unit, 60c ... internal timer, 60d ... burst signal sending unit

Claims (8)

In a network system that operates a network formed by a plurality of nodes using an ARCNET (Attached Resource Computer Network) protocol,
An identifier # 255 is assigned to any one of the plurality of nodes as a monitoring node
The plurality of nodes are:
When the state where the token has not been reached continues for a certain period of time, restructuring requesting means for sending a burst signal requesting restructuring of the circulation route of the token to the network;
Reconstructing means for reconstructing the network by detecting the burst signal and sending the token to the network while incrementing its destination node identifier;
The monitoring node is
When the token is sent out by the reconstruction means, the destination node identifier is incremented in the order of (# 255) to (# 256), (# 00),
Capture means for capturing tokens circulating in the network;
A register for recording a destination node identifier recorded in the captured token;
A network system comprising: a specifying unit that compares the contents of the register before and after the reconfiguration and specifies a node that has transmitted the burst signal based on the result. In a network system that operates a network formed by a plurality of nodes connected via a hub device using an ARCNET (Attached Resource Computer Network) protocol,
The hub device is provided with an identifier # 255 as a node in the network,
The plurality of nodes are:
When the state where the token has not been reached continues for a certain period of time, restructuring requesting means for sending a burst signal requesting restructuring of the circulation route of the token to the network;
Reconstructing means for reconstructing the network by detecting the burst signal and sending the token to the network while incrementing its destination node identifier;
The hub device is
When the token is sent out by the reconstruction means, the destination node identifier is incremented in the order of (# 255) to (# 256), (# 00),
Capture means for capturing tokens circulating in the network;
A register for recording a destination node identifier recorded in the captured token;
A means for comparing the contents of the register before and after the reconstruction, and identifying the node that sent the burst signal from the result;
A network system comprising: blocking means for blocking a port connected to the node specified by the specifying means. The network system according to claim 2, wherein the hub device further includes a reset button for reconnecting the blocked port. The network system according to claim 2, wherein the hub device further includes notification means for notifying a manager of the network that the port is blocked. A hub device that connects a plurality of nodes forming a network operated by an ARCNET (Attached Resource Computer Network) protocol,
Provided with identifier # 255 as a node in the network,
Incrementing the destination node identifier of the token sent when the network is reconstructed with the generation of the burst signal in the order of (# 255) to (# 256), (# 00),
Capture means for capturing tokens circulating in the network;
A register for recording a destination node identifier recorded in the captured token;
A means for comparing the contents of the register before and after the reconstruction, and identifying the node that sent the burst signal from the result;
A hub device comprising: a blocking unit that blocks a port connected to the node specified by the specifying unit. The hub device according to claim 5, further comprising a reset button for reconnecting the blocked port. 6. The hub device according to claim 5, further comprising notification means for notifying a manager of the network that the port is blocked. A method for identifying a faulty node in a network system that operates a network formed by a plurality of nodes using an ARCNET (Attached Resource Computer Network) protocol,
An identifier # 255 is assigned to any one of the plurality of nodes as a monitoring node,
When the state where the token has not been reached continues for a certain period of time, a burst signal requesting the reconstruction of the circulation route of the token is sent to the network,
When the burst signal is detected, the token is sent to the network while incrementing its destination node identifier, and the network is reconstructed.
When sending the token from the monitoring node, the destination node identifier is incremented in the order of (# 255) to (# 256), (# 00),
Capture tokens that circulate in the network,
Record the destination node identifier written in the captured token in a register,
A failure node identification method characterized in that the contents of the register before and after the reconstruction are compared, and the node that transmitted the burst signal is identified from the result.

Images