JP6053637B2 - Method for upgrading virtual host and network device - Google Patents

Description

  The present invention relates to a method for upgrading a virtual host in which the service order entry stop time is shortened, and a network device that executes this method.

  Network devices represented by routers and the like are required to have high reliability, and therefore, active devices and standby devices are often operated in a duplex manner. In such a network apparatus, there are the following methods for updating an OS (Operating System) installed in the apparatus and software operating on the OS.

  The first method is a method of performing update while continuing the service. For example, Non-Patent Document 1 describes a technique called ISSU (in-service software upgrade) in which a network device updates software on the device without interrupting the network service.

  In the first method, the update is sequentially performed for each one of the devices while switching between the active device and the standby device. For this reason, there are periods in which the versions of the OS and software differ between modules. If a service order is received within this period, there is a risk that operation inconsistency may occur due to a difference in the version of the OS or software, and thus stable operation of the network device cannot be ensured.

  The second method is a method of updating by stopping reception of service orders in order to ensure stable operation of the apparatus. In the second method, for example, the operator instructs the apparatus being updated not to input the service order, thereby stopping the reception of the service order. Alternatively, the acceptance of the service order may be stopped by rejecting the service order being updated by the device itself.

Shamus McGillicuddy, “ISSU (In-Service Software Upgrade)”, [online], April 2013, [Search July 30, 2013], Internet <URL: http: //searchnetworking.techtarget.com/definition / ISSU-In-Service-Software-Upgrade>

  The time for updating the software on the network device is usually a long time, and if the reception of the service order during that time is stopped, the operation of the network is affected. Therefore, it is required to shorten the time required for software update on the network device, reduce the work cost, and shorten the service order entry regulation time.

  It is an object of the present invention to provide a virtual host version upgrade method and network device that solve the above-described problems, shorten the version upgrade work time, and reduce the service order entry restriction time. .

In order to solve the above-described problem, in the invention of the version upgrade method for the virtual host of the active device and the virtual host of the standby device according to claim 1, the network processing unit controlled by the virtual host embodied by the hypervisor The active apparatus and the standby apparatus, which are network apparatuses including The active device and the standby device start and implement a new virtual host that is a new version when the old virtual host that is an old version is embodied by the hypervisor; and After performing the step of synchronizing configuration information and state information between the old virtual host and the new virtual host, between the new virtual host of the active device and the new virtual host of the standby device Step to synchronize configuration information and state information is executed. Thereafter, the operation system instructs the old virtual host of the active device to restrict service order , and the operation system instructs the old virtual host of the active device and the standby device to Changing the role with the new virtual host; instructing the new virtual host of the active device according to an instruction from the operation system ; releasing the service order restriction; and according to an instruction from the operation system; A step of shutting down the old virtual host of the standby system device and a step of synchronizing configuration information and state information between the virtual host of the active system device and the virtual host of the standby system device are executed.

  By doing so, it is possible to upgrade both the duplicated active device and standby device in parallel at the same time. Since the new virtual host is newly activated by the hypervisor, the work time can be shortened compared to the version upgrade of the old virtual host that is already operating. Furthermore, since the time to activate the new virtual host and stop the old virtual host is very short, the service order entry restriction time can be shortened.

Furthermore, the new virtual host of the standby system apparatus can be brought close to the latest state by synchronizing the configuration information and the state information with its old virtual host. The new virtual host of the standby system device can further synchronize with the new virtual host of the active system device so that the configuration information and the state information can be updated to the latest information in a short time.

According to a second aspect of the present invention, when the old virtual host is instructed to change roles with the new virtual host, the step of instructing the new virtual host to make it active, and the old virtual host that is itself a step of sparing the host, and the version-up process of the virtual host according to claim 1, characterized by the execution.

  In this way, the role of the old virtual host can be changed to the new virtual host in a short time.

In the invention described in claim 3, wherein the virtual host is a line Umono communicate with operating system via the first virtual network to which the hypervisor provides. The hypervisor embodies the new virtual host in a state where the interface of the first virtual network is blocked and reserved. The old virtual host and the new virtual host communicate via a second virtual network provided by the hypervisor to synchronize configuration information and state information, and the new virtual host is connected to the first virtual network. The old virtual host takes the role of the old virtual host and the new virtual host by unblocking the interface of the first virtual network and making it active, and the old virtual host blocks the interface of the first virtual network and reserves itself. Take turns.

  In this way, each virtual host can easily reserve itself by blocking the interface of the first virtual network so that the current operation is not performed even before it shuts down.

Further, each virtual host can always communicate with the interface of the second virtual network. Therefore, each virtual host can synchronize configuration information and state information with other virtual hosts even when the virtual host is spared.

In the invention of the network device according to claim 4 , the hypervisor, one or more virtual hosts embodied by the hypervisor, a network processing unit controlled by any one of the virtual hosts, It is embodied by a hypervisor, and connects an external operation system and the virtual host so that they can communicate with each other, reserves the virtual host by blocking the interface of the virtual host, and releases the block of the virtual host interface. a first virtual network that working the virtual host, the embodied by the hypervisor, the provided interface of the first virtual network is closed, and a new virtual host with the new version, the first virtual The network interface is blocked Razz and and a second virtual network to synchronize configuration information and state information communicably connected to the old virtual hosts that are in the old version.

By doing so , one of these virtual hosts can control the network processing unit and can switch the control subject from one to the other in a short time. As a result, the service order entry restriction time can be shortened. The service order entry restriction time can also be shortened by synchronizing the configuration information and the state information in advance between the new virtual host and the old virtual host using the second virtual network. Furthermore, the service order entry restriction time can be shortened by synchronizing the configuration information and the state information in advance between the new virtual host of the second virtual network and the new virtual host of another network device. be able to.

  According to the present invention, it is possible to shorten the work time for version upgrade, and it is possible to shorten the service order entry restriction time.

It is a schematic block diagram which shows the network in 1st Embodiment. It is a schematic block diagram which shows each network apparatus. FIG. 5 is a sequence diagram illustrating a virtual host upgrade operation according to the first embodiment. 6 is a flowchart illustrating version upgrade processing of a virtual host in the first embodiment. It is a figure which shows the virtual network structure of a common process part. FIG. 10 is a sequence diagram illustrating a virtual host upgrade operation according to the second embodiment. It is a flowchart which shows the version upgrade process of the virtual host in 2nd Embodiment.

Next, modes for carrying out the present invention (referred to as “embodiments”) will be described in detail with reference to the drawings as appropriate.
FIG. 1 is a schematic configuration diagram showing a network system in the first embodiment.

  The network system 1 includes an active system device 2a and a standby system device 2b, which are edge routers, for example, and an operation system 3 that controls them. One of the active system device 2 a and the standby system device 2 b is connected to the terminal 4 via the layer 2 network 8, and the other is connected to the Internet 9. The active system device 2a and the standby system device 2b are operated in a duplex manner, and, for example, connect the terminal 4 and the Internet 9 so that they can communicate with each other. The active device 2a and the standby device 2b are not limited to edge routers, and may be core routers, center routers, and the like.

FIG. 2 is a schematic configuration diagram showing each network device.
Since the active system device 2a and the standby system device 2b are configured in the same manner, in FIG. 2, only the configuration of the active system device 2a is mainly described, and the description of the standby system device 2b is only the difference.
The active system device 2 a includes a common processing unit 21, a network processing unit 22, and a network interface 23. The active system device 2a includes a CPU (Central Processing Unit), a volatile storage memory, and a nonvolatile storage device (such as a hard disk). This nonvolatile storage device stores a common processing program for implementing the common processing unit 21.
Similarly to the active system device 2a, the standby system device 2b includes a common processing unit 21, a network processing unit 22 (not shown), and a network interface 23.

The network interface 23 physically communicates with an external device, and is realized as a network interface card, for example.
The network processing unit 22 performs a dedicated process on the packet input from the network interface 23, and performs, for example, a process of rewriting the contents of the packet based on a predetermined rule. The network processing unit 22 is realized as a service card, for example, and is accommodated in the packet forwarding card together with the network interface cart described above.

  The common processing unit 21 of the active device 2a includes a hypervisor 211a, and the virtual hosts 212a and 213a are realized by the hypervisor 211a. The old virtual host 212a stores configuration information 2121a and state information 2122a. The configuration information 2121a is setting information of the old virtual host 212a. The state information 2122a is information indicating the operation state of the old virtual host 212a. In FIG. 2, the configuration information 2121a and the like are described as “configuration”, and the state information 2122a and the like are described as “state”. The new virtual host 213a stores configuration information 2131a and state information 2132a.

The common processing unit 21 of the standby apparatus 2b includes a hypervisor 211b, and the old virtual host 212b and the new virtual host 213b are realized by the hypervisor 211b. The old virtual host 212b stores configuration information 2121b and state information 2122b. The new virtual host 213b stores configuration information 2131b and state information 2132b. The standby system device 2b is configured in the same manner as the active system device 2a except for these.
The hypervisor 211a is implemented by the CPU executing a hypervisor program stored in a nonvolatile storage device. The hypervisor 211a includes a virtual host processing unit 2112 and a virtual network processing unit 2111.

  The virtual host processing unit 2112 reads, for example, an OS program file and realizes one virtual host 212a or a plurality of virtual hosts 212a and 213a. This OS program file is stored, for example, in a virtual disk file used by the virtual host 212a. In this way, the virtual host processing unit 2112 permits activation of the plurality of virtual hosts 212a and 213a, and arbitrates so that the CPU, memory, and other hardware can be shared by the virtual hosts 212a and 213a.

  The virtual network processing unit 2111 provides a function for the virtual hosts 212a and 213a to communicate with an external device via the network interface 23, or to communicate between the virtual hosts 212a and 213a in the same device. The virtual network processing unit 2111 further operates as a DHCP (Dynamic Host Configuration Protocol) server, and issues an IP (Internet Protocol) address in response to a request from the virtual hosts 212a and 213a.

The virtual host 212a stores configuration information 2121a and state information 2122a. The virtual host 213a stores configuration information 2131a and state information 2132a. These virtual hosts 212a and 213a perform processing common to the active system device 2a.
Any one of the virtual hosts 212a and 213a controls the network processing unit 22, thereby realizing filtering processing and QoS (Quality of Service) processing and managing the routing table. Master data relating to filtering, QoS, and routing table is stored in the state information 2122a of the virtual host 212a and the state information 2132a of the virtual host 213a, respectively.

The virtual host 212a is an old version, and is indicated as “virtual host (old)” in each figure. The virtual host 213a is a new version and is indicated as “virtual host (new)” in each figure. Hereinafter, the virtual host 212a may be described as the old virtual host 212a, and the virtual host 213a may be described as the new virtual host 213a.
One of the old virtual host 212a and the new virtual host 213a controls the network processing unit 22, and the control subject can be switched from one to the other in a short time. As a result, the service order entry restriction time can be shortened.

  The common processing unit 21 of the active device 2a of the first embodiment realizes a plurality of virtual hosts 212a and 213a by the hypervisor 211a. As a result, synchronization is performed between the old virtual host 212a and the new virtual host 213a, and the synchronization time between the configuration information 2121a and the configuration information 2131a and the synchronization between the state information 2122a and the state information 2132a accompanying the version upgrade. Can be shortened.

  To synchronize configuration information and state information between the old virtual host 212a and the new virtual host 213a, an IP address issued by the DHCP server function of the virtual network processing unit 2111 is used as a synchronization interface. As a result, even if the configuration information of the virtual hosts 212a and 213a is the same, synchronization can be performed. This is because the state information such as the DHCP address assigned to the synchronization interface is not subject to takeover between the virtual host 212a and the virtual host 213a.

FIG. 3 is a sequence diagram illustrating a version upgrade operation of the virtual host according to the first embodiment.
Prior to the execution of version upgrade, the hypervisor 211a of the active system device 2a embodies the old virtual host 212a. The hypervisor 211b of the standby apparatus 2b embodies the old virtual host 212b.
In sequence Q10, the configuration information 2121a and the configuration information 2121b are synchronized between the old virtual host 212a of the active device 2a and the old virtual host 212b of the standby device 2b, and the state information 2122a and the state information 2122b are synchronized. Synchronized.

The operations of sequences Q20a to Q23a are the same as the operations of sequences Q20b to Q23b, and are executed in parallel with both operations. Here, sequences Q20a to Q23a will be mainly described.
In sequence Q20a, the operation system 3 instructs the hypervisor 211a of the active device 2a to start up the new virtual host 213a as a backup.

In sequence Q21a, the hypervisor 211a of the active device 2a implements the new version of the new virtual host 213a by reading and executing the new version of the virtual host program from the storage unit (not shown). Since the new version of the virtual host program is being executed in the new virtual environment, the environment in which the new version of the virtual host program can be operated in a shorter time than when updating the service of the old virtual host 212a is continued. Can be built.
In sequence Q22a, the new virtual host 213a of the active device 2a requests the IP address of the synchronization interface from the hypervisor 211a of the active device 2a.

In sequence Q23a, the hypervisor 211a of the active device 2a pays out the IP address of the synchronization interface to the new virtual host 213a of the active device 2a. Thereby, for example, the new virtual host 213a of the active device 2a communicates with the old virtual host 212a of the active device 2a, synchronizes the configuration information 2121a and the configuration information 2131a, and the state information 2122a and the state information Information 2132a can be synchronized. This synchronization interface will be described in detail with reference to FIG.
In sequences Q20b to Q23b, the new virtual host 213b on the standby system device 2b is similarly activated as a standby system, and an IP address is issued to the synchronization interface of the new virtual host 213b.

In sequence Q24, the configuration information 2121a and the configuration information 2131a are synchronized and the state information 2122a and the state information 2132a are synchronized between the old virtual host 212a and the new virtual host 213a of the active device 2a.
In sequence Q25, the configuration information 2131a and the configuration information 2131b are synchronized, and the state information 2132a and the state information 2132b are synchronized between the new virtual host 213a of the active device 2a and the new virtual host 213b of the standby device 2b. To do. The communication path for this synchronization will be described in detail with reference to FIG. By doing so, the new virtual host 213b of the standby system device 2b can bring the configuration information 2131b and the state information 2132b to the latest state. Therefore, even if a failure occurs in the new virtual host 213a of the active system device 2a immediately after the host change from the old virtual host 212a of the active system device 2a to the new virtual host 213a, the new system of the standby system device 2b. The service can be continued by switching to the virtual host 213b.

  In sequences Q30a, Q30c, Q30b, and Q30d, the operation system 3 includes the old virtual host 212a of the active device 2a, the new virtual host 213a of the active device 2a, the old virtual host 212b of the standby device 2b, and the standby device. Instruct the 2b new virtual host 213b to restrict the service order. As a result, the active device 2a and the standby device 2b stop accepting the service order of the edge router function.

Since the operations of the sequences Q31a to Q36a are the same as the operations of the sequences Q31b to Q36b, the sequences Q31a to Q36a will be described below.
In sequence Q31a, the operation system 3 instructs the old virtual host 212a of the active device 2a to change the host. Here, the host change is a change of role between the old virtual host 212a and the new virtual host 213a.
In sequence Q32a, the old virtual host 212a of the active device 2a instructs the new virtual host 213a of the active device 2a to make it active. As a result, the new virtual host 213a of the active device 2a releases the blockage of the interface in the operation system 3 direction.
In sequence Q33a, the operation system 3 instructs the new virtual host 213a of the active device 2a to cancel the restriction of the service order. Compared with the time required for the software update, the switching time from the old virtual host 212a to the new virtual host 213a in the active device 2a is extremely short. Therefore, the active apparatus 2a can cancel the restriction of the service order in a short time.

In sequence Q34a, the operation system 3 instructs the hypervisor 211a of the active apparatus 2a to shut down.
In sequence Q35a, the hypervisor 211a of the active device 2a shuts down the old virtual host 212a of the active device 2a.

  In sequence Q36a, the old virtual host 212a of the active device 2a executes its own shutdown. As a result, the active device 2a can release the physical resource held by the old virtual host 212a and provide the physical resource to the network processing unit 22 or the like.

FIG. 4 is a flowchart illustrating version upgrade processing of the virtual host according to the first embodiment.
When the active device 2a and the standby device 2b are activated, the operation system 3 instructs the active device 2a to start the new virtual host 213a, and instructs the standby device 2b to start the new virtual host 213b. If so, the version upgrade process starts.

The following processes in steps S10a and S11a are processes performed on the active apparatus 2a, and the processes in steps S10b and S11b are processes performed in parallel by the standby apparatus 2b. Here, representatively, the processing of steps S10a and S11a will be described.
In step S10a, the hypervisor 211a of the active device 2a activates the new virtual host 213a.
In step S11a, the hypervisor 211a of the active device 2a issues an IP address to its new virtual host 213a.

The processes in steps S20 to S22 below are sequential processes by each unit.
In step S20, the new virtual host 213a and the old virtual host 212a of the active device 2a synchronize the configuration information 2131a and the configuration information 2121a, and synchronize the state information 2132a and the state information 2122a.
In step S21, the new virtual host 213a of the active device 2a and the new virtual host 213b of the standby device 2b synchronize the configuration information 2131a and the configuration information 2131b, and synchronize the state information 2132a and the state information 2132b.
In step S22, the operation system 3 instructs the active system device 2a and the standby system device 2b to regulate the service order.

The following processes in steps S30a to S32a are processes performed on the active apparatus 2a, and the processes in steps S30b to S32b are processes performed in parallel with the standby apparatus 2b. Here, representatively, the processing of steps S30a to S32a will be described.
In step S30a, the operation system 3 instructs the old virtual host 212a of the active device 2a to change the host.

In step S31a, the old virtual host 212a of the active device 2a instructs the new virtual host 213a of the active device 2a to make it active. As a result, the new virtual host 213a of the active device 2a releases the blockage of the interface in the operation system 3 direction.
In step S32a, the old virtual host 212a of the active device 2a reserves itself. As a result, the old virtual host 212a of the active device 2a closes the interface in the operation system 3 direction. In this way, the role of the old virtual host 212a of the active device 2a can be replaced with the new virtual host 213a of the active device 2a in a short time.

The processes in steps S40 and S41 below are sequential processes by each unit.
In step S40, the operation system 3 instructs the active device 2a and the standby device 2b to cancel the restriction of the service order.
In step S41, the operation system 3 instructs the old virtual host 212a of the active device 2a and the old virtual host 212b of the standby device 2b to shut down. As a result, the old virtual host 212a of the active device 2a and the old virtual host 212b of the standby device 2b shut themselves down. Thereby, the active system device 2a and the standby system device 2b can release their physical resources. When the process of step S41 ends, the version upgrade process shown in FIG. 4 ends.

5A and 5B are diagrams illustrating a virtual network configuration of the common processing unit.
FIG. 5A shows a virtual network configuration when configuration information and state information are synchronized.
The active system device 2a and the standby system device 2b are communicably connected to the operation system 3. In the active device 2a, the virtual host processing unit 2112 implements the old virtual host 212a and the new virtual host 213a, and the virtual network processing unit 2111 implements virtual networks 241 and 242. In the standby system device 2b, the virtual host processing unit 2112 realizes the old virtual host 212b and the new virtual host 213b, and the virtual network processing unit 2111 realizes the virtual networks 241 and 242 as in the active system device 2a. Has been. Hereinafter, the configuration of the active system device 2a will be mainly described, and the similar configuration of the standby system device 2b will be omitted.
The old virtual host 212a of the active device 2a includes an interface 2122 that can communicate with the virtual network 241 and an interface 2123 that can communicate with the virtual network 242.

The new virtual host 213a of the active device 2a includes a blocked interface 2132 and an interface 2133 that can communicate with the virtual network 242.
The virtual network 241 (first virtual network) of the active device 2a is embodied by the hypervisor 211a of the active device 2a, and is one of the external operation system 3 and the virtual hosts 212a and 213a of the active device 2a. One is communicably connected. As a result, the old virtual host 212a of the active device 2a switches the state in which its own interface 2122 is communicably connected to the state in which the interface 2132 of the new virtual host 213a of the active device 2a is communicably connected. , You can change the host. Therefore, the active apparatus 2a can shorten the service order entry restriction time.

The virtual network 242 (second virtual network) of the active device 2a is embodied by the hypervisor 211a of the active device 2a, and includes a new virtual host 213a of the active device 2a and an old virtual host 212a of the active device 2a. Are connected so as to be communicable, and are also communicably connected to the new virtual host 213b of the standby system device 2b (other network device) having the same configuration. By synchronizing in advance between the old virtual host 212a of the active device 2a and the new virtual host 213a of the active device 2a, the service order entry restriction time can be shortened. Further, the virtual network 242 synchronizes the configuration information 2131a and the configuration information 2131b in advance and the state information 2132a and the state between the new virtual host 213a of the active device 2a and the new virtual host 213b of the standby device 2b. Synchronization with the information 2132b can be performed to shorten the service order entry restriction time.

  The old virtual host 212a of the active device 2a can communicate with the operation system 3 via the virtual network 241. The new virtual host 213a of the active system device 2a cannot communicate because the interface 2132 in the direction of the operation system 3 is blocked. As a result, after the new virtual host 213a of the active device 2a is activated, the operation system 3 continues to operate the old virtual device 2a of the active device 2a while the interface 2132 of the new virtual host 213a is closed. A service order can be input only to the host 212a.

  The old virtual host 212a of the active device 2a can communicate with the new virtual host 213a of the active device 2a via the virtual network 242. Accordingly, the old virtual host 212a of the active device 2a and the new virtual host 213a of the active device 2a can synchronize the configuration information 2121a and the configuration information 2131a and synchronize the state information 2122a and the state information 2132a. it can. Further, the new virtual host 213a of the active system device 2a communicates with the new virtual host 213b of the standby system device 2b via the old virtual host 212a of the active system device 2a and the old virtual host 212b of the standby system device 2b. The configuration information 2131a and the configuration information 2131b can be synchronized, and the state information 2132a and the state information 2132b can be synchronized.

FIG. 5B shows a virtual network configuration when the old virtual host 212a and the new virtual host 213a change hosts.
The active system device 2a and the standby system device 2b are communicably connected to the operation system 3. In the active device 2a, an old virtual host 212a and a new virtual host 213a are embodied, and virtual networks 241 and 242 are also embodied.
The old virtual host 212a of the active device 2a includes an interface 2122 that is blocked by the host change and an interface 2123 that can communicate with the virtual network 242.
The new virtual host 213 a of the active device 2 a includes an interface 2132 that can communicate with the virtual network 241 and an interface 2133 that can communicate with the virtual network 242. The block of the interface 2132 is released by the host change.

The new virtual host 213a of the active device 2a can communicate with the operation system 3 via the virtual network 241. The old virtual host 212a of the active device 2a cannot communicate because the interface 2122 in the direction of the operation system 3 is blocked. As a result, the operation system 3 does not perform the current operation even before the old virtual host 212a of the active device 2a shuts down, and can input the service order only to the new virtual host 213a of the active device 2a. it can.
Furthermore, the new virtual host 213a of the active device 2a and the new virtual host 213b of the standby device 2b can communicate with each other via the respective virtual networks 241. Thus, after the host is changed, the configuration information 2131a and the configuration information 2131b are synchronized between the new virtual host 213a of the active device 2a and the new virtual host 213b of the standby device 2b, and the state information 2132a The state information 2132b can be synchronized.

(Second Embodiment)
The network system 1 of the second embodiment is configured similarly to the network system 1 (see FIG. 1) of the first embodiment. The synchronization method of the configuration information 2131a and the state information 2132a of the new virtual host 213a of the second embodiment is different from that of the first embodiment. The second embodiment will be described in detail based on FIGS. 6 and 7 below.

FIG. 6 is a sequence diagram illustrating a virtual host version upgrade operation according to the second embodiment. The same reference numerals are given to the same elements as the virtual host version upgrade operation of the first embodiment shown in FIG.
The operation of the sequence Q10 that is synchronization of configuration information and state information is the same as that in the first embodiment.
The operations from sequence Q20a, Q20b, which is a version upgrade operation, to sequence Q23a, Q23b are the same as in the first embodiment.

In sequence Q26a, the operation system 3 instructs the old virtual host 212a of the active device 2a to upgrade the version.
In sequence Q26b, the operation system 3 instructs the old virtual host 212b of the standby apparatus 2b to upgrade.
In sequence Q27a, the configuration information 2121a and the configuration information 2131a are synchronized, and the state information 2122a and the state information 2132a are synchronized between the old virtual host 212a and the new virtual host 213a of the active device 2a. Thereby, the new virtual host 213a of the active device 2a can set the configuration information 2131a and the state information 2132a to the latest state.
In sequence Q27b, the configuration information 2121b and the configuration information 2131b are synchronized, and the state information 2122b and the state information 2132b are synchronized between the old virtual host 212b of the standby system device 2b and the new virtual host 213b of the standby system device 2b. To do. Thereby, the new virtual host 213b of the standby apparatus 2b can make the configuration information 2131b and the state information 2132b last synchronized with the old virtual host 212b of the standby apparatus 2b.

The active device 2a performs synchronization between its own old virtual host 212a and its own new virtual host 213a. In parallel with this, the standby apparatus 2b performs synchronization between its own old virtual host 212b and its own new virtual host 213b. As a result, the active system device 2a and the standby system device 2b can complete synchronization in a short time.
Operations from sequences Q30a to Q30d to sequences Q36a and Q36b are the same as those in the first embodiment.
In sequence Q37a, the operation system 3 instructs the new virtual host 213a of the active device 2a to synchronize with the new virtual host 213b of the standby device 2b.

In sequence Q37b, the operation system 3 instructs the new virtual host 213b of the standby system device 2b to synchronize with the new virtual host 213a of the active system device 2a.
In sequence Q38, the configuration information 2131a and the configuration information 2131b are synchronized and the state information 2132a and the state information 2132b are synchronized between the new virtual host 213a of the active device 2a and the new virtual host 213b of the standby device 2b. To do. Thus, since the new virtual host 213b of the standby system device 2b is synchronized with the old virtual host 212b of the standby system device 2b in advance, the configuration information 2131b and the state information 2132b can be updated in a short time. .

FIG. 7 is a flowchart illustrating version upgrade processing of the virtual host according to the second embodiment. The same symbols are assigned to the same elements as those of the virtual host version upgrade process of the first embodiment shown in FIG.
After the upgrade process of the virtual host 212a is started, the processes in steps S10a and S10b and the processes in steps S11a and S11b are the same as in the first embodiment.
In step S12a, the configuration information 2121a and the configuration information 2131a are synchronized, and the state information 2122a and the state information 2132a are synchronized between the old virtual host 212a of the active device 2a and the new virtual host 213a of the active device 2a. To do.

In step S12b, the old virtual host 212b of the standby apparatus 2b and the new virtual host 213b of the standby apparatus 2b synchronize the configuration information 2121b and the configuration information 2131b, and synchronize the state information 2122b and the state information 2132b. Thereby, the new virtual host 213b of the standby apparatus 2b can make the configuration information 2131b and the state information 2132b last synchronized with the old virtual host 212b of the standby apparatus 2b.
The processing in steps S12a and S12b is executed in parallel by the active device 2a and the standby device 2b. When the processes of steps S12a and S12b are completed, the process of step S22 is performed.

The processing in step S22, the parallel processing from steps S30a and S30b to steps S32a and S32b, and the processing in steps S40 and S41 are the same as in the first embodiment.
In step S42, the operation system 3 synchronizes the configuration information 2131a with the configuration information 2131b and the state information 2132a between the new virtual host 213a of the active device 2a and the new virtual host 213b of the standby device 2b. An instruction is given to synchronize with the state information 2132b, and the processing of FIG. 7 ends.
As a result, the new virtual host 213b of the standby apparatus 2b is synchronized with its own old virtual host 212a in advance, so that its own configuration information 2131b and state information 2132b can be updated in a short time.

(Modification)
The present invention is not limited to the above-described embodiment, and can be modified without departing from the spirit of the present invention. For example, there are the following (a) to (c).

(A) The active system device 2a and the standby system device 2b are not limited to routers, and may be servers that provide arbitrary network services or other network devices.

(B) The number of standby system devices 2b is not limited to one. For example, the system may be tripled by providing two standby system devices.

(C) The network system 1 is duplicated by the active system device 2a and the standby system device 2b. However, the present invention is not limited to this, and the network system 1 may operate so as to activate a plurality of virtual hosts on a single device and synchronize configuration information and state information between these virtual hosts.

DESCRIPTION OF SYMBOLS 1 Network system 2a Active system apparatus 2b Standby system 3 Operation system 4 Terminal 8 Layer 2 network 9 Internet 21 Common processing part 211a, 211b Hypervisor 2111 Virtual network processing part 2112 Virtual host processing part 212a, 212b Virtual host (old virtual host )
213a, 213b Virtual host (new virtual host)
2121a, 2131a, 2121b, 2131b Configuration information 2122a, 2132a, 2122b, 2132b State information 2122, 2123, 2132, 2133 Interface 22 Network processing unit 23 Network interface 241 Virtual network (first virtual network)
242 virtual network (second virtual network)

Claims (4)

A version upgrade method of a virtual host of a working system device and a virtual host of a standby system device, which is a network device including a network processing unit controlled by a virtual host embodied by a hypervisor,
The active system device and the standby system device are:
When the old virtual host that is the old version is realized by the hypervisor, the step of starting and realizing the new virtual host that is the new version;
After executing the step of synchronizing configuration information and state information between the old virtual host and the new virtual host, between the new virtual host of the active device and the new virtual host of the standby device Execute the step to synchronize the configuration information and state information with
An operation system instructing the old virtual host of the active device to regulate service orders;
In accordance with an instruction from the operation system, causing the old virtual host of the active device and the standby device to change roles with the new virtual host;
In response to an instruction from the operation system, causing the new virtual host of the active device to cancel service order restrictions;
Shutting down the old virtual host of the active device and the standby device according to an instruction of the operation system ;
Synchronizing configuration information and state information between the virtual host of the active device and the virtual host of the standby device;
A method for upgrading a virtual host, comprising: If the old virtual host is instructed to switch roles with the new virtual host,
Instructing the new virtual host to activate,
Preparating the old virtual host which is itself;
The virtual host version upgrade method according to claim 1, wherein: The virtual host, which communicates with the operating system via the first virtual network to which the hypervisor provided,
The hypervisor embodies the new virtual host in a state in which the interface of the first virtual network is blocked and reserved.
The old virtual host and the new virtual host communicate via a second virtual network provided by the hypervisor to synchronize configuration information and state information,
The new virtual host releases the block of the interface of the first virtual network and activates itself, and the old virtual host blocks the interface of the first virtual network and reserves itself, Changing roles between the old virtual host and the new virtual host,
The virtual host version upgrade method according to claim 2, wherein: Hypervisor,
One or more virtual hosts embodied by the hypervisor;
A network processing unit controlled by any one of the virtual hosts;
Implemented by the hypervisor, communicatively connecting an external operation system and the virtual host, making the virtual host spare by blocking the virtual host interface, and releasing the block of the virtual host interface A first virtual network that activates the virtual host;
Implemented by the hypervisor, the interface of the first virtual network is blocked, and the new virtual host that is the new version is used as the new virtual host, the interface of the first virtual network is not blocked, and the old version A second virtual network that is communicably connected to the old virtual host and that is communicably connected to the new virtual host of another network device having the same configuration and synchronizes configuration information and state information;
A network device comprising:

Images