JPH05244164A - Dynamic assignment system for network identifier of duplex system - Google Patents

Abstract

PURPOSE:To facilitate the system control by extracting the network identifiers different from each other between the cases where its own system serves as a master system and a slave system respectively and then assigning these identifiers to each network interface part. CONSTITUTION:A data processor 10 of a system O serves as a master system and a data processor 20 of a system 1 serves as a slave system respectively. Under such conditions, a control part 15 reads a network identifier IPa of the master system out of a table 14 and an assignment part 12 assigns the identifier IPa to a network interface part 13. Meanwhile a control part 25 reads a network identifier IPb of the slave system out of a table 24. Then an assignment part 22 assigns the identifier IPb to a network interface part 23 respectively. Therefore the processor 10 can work as a master system and also can have an access to the processor 20 of the slave system by means of the identifier IPb.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a duplex system in which one of the data processing devices connected to a network such as a LAN operates as a master system and the other as a slave system so that the data can be transmitted from other workstations on the network by a network identifier. The present invention relates to a dynamic allocation method of a network identifier used when accessing a data processing device.

[0002]

2. Description of the Related Art In a data processing device, the system is duplicated in order to improve the reliability of the system. In this case, two data processing devices are used. For example, as shown in FIG. 5, a data processing device 10 of 0 system and a data processing device 20 of 1 system that operate as a main system for a LAN (Local Area Network) 1 such as Ethernet ( In this example, only 10) is connected via the network interface unit 13.

Since the same network identifier cannot exist on the network, the same network identifier is used for the 0-system data processing device 10 and the 1-system data processing device 20 in the example of FIG.

That is, the data processing apparatus 10 is provided with a judging section 11, an allocating section 12, and a network interface section 13. Similarly, the data processing apparatus 20 also has a judging section 21, an allocating section 22, and a network interface. A face portion 23 is provided. The determination units 11 and 21 determine whether the data processing device operates as a master system or a slave system, and the allocation units 12 and 22 assign the network identifier to the network interface unit 1.
3 and 23 are assigned so that data having the network identifier can be received when transmitted via the LAN 1.

Therefore, when the 0-system data processing device 10 operates as the master system and the 1-system data processing device 20 operates as the slave system, in the master-system data processing device 10, the determination unit 11 operates as the master system. It is determined and the allocation unit 12 is notified of this. The allocator 12 thereby allocates the network identifier to the network interface unit 13. In this way, the data processing device 10 is connected to the LAN 1
Can be connected and can be transmitted and received using the network identifier. However, in the subordinate data processing device 20,
LAN1 because no network identifier is assigned
Unable to communicate via.

The operation of FIG. 5 will be further described with reference to the flowchart of FIG. When starting the system, 0
It is preset to make the system the main system. When the data processing devices 10 and 20 are powered on from the stopped state and the system is started up, the 0-system data processing device 1
In 0, the determination unit 11 determines that the own system device is the main system and notifies the allocation unit 12 of this. The allocation unit 12 allocates the network identifier to the network interface unit 13 accordingly. Then, the network interface unit 13 is activated to enter the service state, and the LAN
It will be accessible from other devices on the one.

On the other hand, in the 1-system data processing apparatus 20, the deciding section 21 decides that the self-system apparatus is a slave and notifies the allocating section 22 of this, so that the allocating section 22 uses the network interface. A standby state is entered without assigning a network identifier to the unit 23.

When a failure occurs in the main system when the 0 system is in the service state as the main system and the 1 system is in the standby state as the slave system, the network interface unit 13 of the main system is disconnected. , 0 system goes down.

A monitoring device (not shown) detects this and
When this is notified to the system determination unit 21, it is determined that the own system will become the main system this time, the standby state is released, a network identifier is assigned to the network interface unit 23, and the network interface is determined. The service unit 23 is activated to enter the service state as the main system.

When the repair work is completed for the 0-system which is in the down state, the 1-system is already in the service state, so that the judging section 11 judges that the self-system should become the slave system and enters the standby state.

By the way, as shown in FIG. 5, in the case where the same network identifier is used in the main system and the subordinate system, only one network interface unit operates at a time, so there is no concern that the network identifier will be duplicated. Since the subordinate data processing device cannot be accessed via the network, even if there is a desire to access the subordinate in terms of system management, it is not possible for system management.

In some cases, the main system and the sub system share one network interface unit, but in this case, in addition to the above-mentioned inconvenience, a failure occurs in the network interface unit. At that time, I could not do anything because I could not recover the interface with the network even if I switched the system.

In order to improve this, as shown in FIG.
The system and the system 1 data processing devices 10 and 20 are each provided with a network interface unit, and this time, the data processing devices 10 and 20 are assigned different network identifiers. As a result, it becomes possible to separately access the master and slave data processing devices.

[0014]

By the way, since different network identifiers are assigned to the 0-system data processing apparatus and the 1-system data processing apparatus, each time the master system and the slave system are switched, the master system and the slave system are switched. There is a disadvantage that the network identifier for accessing the data processing device is changed, and the user sees the same service, but the network identifier is changed.

Therefore, an object of the present invention is to facilitate access to both the main system and the sub system in the duplex system so that system management can be performed, and even if the main system and the sub system are switched, the user can switch the system. It is to be able to access with the same network identifier as before without being aware of.

[0016]

In order to achieve the above object, in the present invention, as shown in FIG. 1, tables 14 and 24 are provided in a 0-system data processing device 10 and a 1-system data processing device 20, respectively. In each of these tables 14, 24, the network identifier IPa when the data processing device is the primary system and the network identifier IPb when the data processing device is the secondary system are shown.
Fill in. Then, the management units 15 and 25 take out the network identifier IPa when the main system is the master system from the tables 14 and 24 when the own system is the master system, and take out the network identifier IPb when the own system is the slave system from the tables 14 and 24. , Assign it to each network interface section.

[0017]

In FIG. 1, when the 0-system data processing device 10 operates as the master system and the 1-system data processing device 20 operates as the slave system, the management unit 15 uses the table 14 to identify the network identifier IPa as the master system. Read out and assign unit 1
2 assigns it to the network interface unit 13, the management unit 25 reads the network identifier IPb as a slave from the table 24, and the assigning unit 22 assigns it to the network interface unit 23.

As a result, the data processing device 10 can operate as a master system and can access the slave data processing device 20 by using the network identifier IPb as a slave system.

When a failure occurs in the data processing device 10 operating as the main system, the determination unit 21 in the data processing device 20 next determines that the own system should operate as the main system, and manages accordingly. Since the unit 25 reads the network identifier IPa as the main system from the table 24 and the assigning unit 22 assigns it to the network interface unit 23, the data processing device 20 operates as the main system.

At this time, in the data processing device 10, the judgment unit 11 judges that it should operate as a subordinate system, so that the management unit 15 reads out the network identifier IPb as the subordinate system from the table 14 and the network interface. -Assigned to the memory unit 13.

Therefore, the user side can always access by the primary system network identifier IPa, and can access by the secondary system network identifier IPb when accessing the secondary system data processing device.

[0022]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described with reference to FIGS. 2 is a configuration diagram of an embodiment of the present invention, FIG. 3 is an operation state explanatory diagram in the 0 system, and FIG. 4 is an operation state explanatory diagram in the 1 system. In the figure, the same symbols as the other figures indicate the same parts. 1
6 and 26 are access units, which are the table 14 and
A database for accessing 24 and a database for storing data commonly used by the 0-system data processing apparatus 10 and the 1-system data processing apparatus 20.

Next, the operation of FIG. 2 will be described with reference to FIGS. 3 and 4. It is to be noted that, when the system is started up, for example, the 0-system data processing device 10 is the master system and the 1-system data processing device 20 is the slave system.

When each of the 0-system data processing device 10 and the 1-system data processing device 20 is in a stopped state, both are LAN1 which is a network such as Ethernet.
The network interface units 13 and 23 are not activated.

When both the 0-system data processing device 10 and the 1-system data processing device 20 are started by turning on the power, for example, the determination unit 11 of the 0-system data processing device 10 has its own system as the main system. It is determined that there is and notifies the management unit 15 of this. Accordingly, the management unit 15 instructs the access unit 16 to read the network identifier IPa of the main system from the table 14, and passes the network identifier IPa thus obtained to the allocation unit 12. The allocation unit 12 allocates this network identifier IPa to the network interface unit 13.

Then, the network interface unit 13 is activated to enter the service state, and can be accessed from another computer on the LAN 1 which is a network.

On the other hand, as shown in FIG. 4, the determination unit 21 of the data processing device 20 of the 1st system determines that the self-system device is the slave system and notifies the management unit 25 of this. As a result, the management unit 25 uses the network identifier IP of the slave system from the table 24.
The access unit 26 is instructed to read out b, and the obtained network identifier IPb is passed to the allocation unit 22. The allocator 22 assigns this network identifier IPb to the network
It is assigned to the interface unit 23.

Then, the network interface unit 23 is activated to be in a standby state, and can be accessed from another computer on the LAN 1 via the network.

When a failure occurs in the main system when the 0 system is in the service state as the main system and the 1 system is in the standby state as the slave system, the network interface unit 13 of the main system is disconnected. Then, the 0 system goes down.

When this failure occurrence is detected by a monitoring device (not shown), and the 1-system judging section 21 is notified of this, the judging section 21 judges that the self-system becomes the main system, and once The network interface unit 23 is disconnected to release the standby state.

Then, the judging section 21 tells the managing section 25 that
Instruct to read the network identifier IPa of the main system,
The main system network identifier IPa thus obtained is assigned by the assigning unit 22 to the network interface unit 23.
Assigned to the network interface unit 2
3 is activated, and this time it becomes the service state as the main system.

By the way, in the 0 system which is in the down state, the repair work of the failure is performed, and when this is finished, the 1 system is already in the service state, so the judging section 11 judges that the self system should be the slave system. Then, this time, the management unit 15 is instructed to read the slave network identifier IPb. Then, the obtained slave network identifier IPb is similarly assigned to the network interface unit 13, activated, and brought into a service state as a slave.

In the above description, a case has been described in which a monitoring device (not shown) detects a 0-system or 1-system failure and notifies the other party of the failure. It is also possible to control so as to switch between the main system and the sub system by monitoring.

[0034]

According to the present invention, in a duplex system, a primary network identifier and a slave network identifier can be dynamically assigned to a data processing device that constitutes the duplex system, rather than being fixed. Since the user can access the master system without changing the network identifier of the access destination and can also access the slave system via the network, it is possible to manage the system. Information correction work can be performed via the network.

[Brief description of drawings]

FIG. 1 is a principle configuration diagram of the present invention.

FIG. 2 is a configuration diagram of an embodiment of the present invention.

FIG. 3 is an explanatory diagram of the operation of the 0 system in the present invention.

FIG. 4 is an operation explanatory diagram of the first system in the present invention.

FIG. 5 is an explanatory diagram of a duplex system connected to a conventional network.

FIG. 6 is an operation explanatory diagram of a conventional example.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 LAN 100 Data processing device of 11 system 11 Determination part 12 Allocation part 13 Network interface part 14 Table 15 Management part 16 Access part 20 Data processing device of 1 system 21 Judgment part 22 Allocation part 23 Network interface Database 24 Table 25 Management 26 Access 30 Database

Claims (1)

[Claims] 1. A network interface unit for operating one of two data processing devices as a master system and the other as a slave system, and connecting these to a network, and a network identifier for a network interface. In a duplex system having an allocation unit allocated to a face unit, tables (14) and (24) in which a plurality of network identifiers are registered in the data processing devices (10) and (20)
And a management unit (1 that manages these network identifiers
5) and (25). The tables (14) and (24) are respectively filled with the network identifier in the case of the master system and the network identifier in the case of the slave system. A network in a duplex system characterized in that a network identifier for a master system is assigned to a network interface section when it is determined to be a system and a network identifier for a slave system is assigned to a network interface unit when it is determined to be a slave system. Dynamic identifier allocation method.