WO2012020481A1 - Dispositif de gestion, dispositif de traitement d'informations, procédé et programme de commande - Google Patents

Dispositif de gestion, dispositif de traitement d'informations, procédé et programme de commande Download PDF

Info

Publication number
WO2012020481A1
WO2012020481A1 PCT/JP2010/063611 JP2010063611W WO2012020481A1 WO 2012020481 A1 WO2012020481 A1 WO 2012020481A1 JP 2010063611 W JP2010063611 W JP 2010063611W WO 2012020481 A1 WO2012020481 A1 WO 2012020481A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
common
switch
blade
common information
Prior art date
Application number
PCT/JP2010/063611
Other languages
English (en)
Japanese (ja)
Inventor
高岡雅憲
久保勇人
Original Assignee
富士通株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社 filed Critical 富士通株式会社
Priority to PCT/JP2010/063611 priority Critical patent/WO2012020481A1/fr
Priority to JP2012528535A priority patent/JP5413514B2/ja
Priority to EP10855882.6A priority patent/EP2605458B1/fr
Publication of WO2012020481A1 publication Critical patent/WO2012020481A1/fr
Priority to US13/758,310 priority patent/US9432244B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks

Definitions

  • the present invention relates to a management device, an information processing device, a control method, and a program.
  • each server blade included in the blade server has a network interface such as a LAN (Local Area Network) port. Therefore, whenever a server blade is changed, added, or integrated, the entire blade server Network design optimization is required.
  • the blade server includes a plurality of switch blades that aggregate data from each server blade via a LAN port and efficiently transmit and receive data to and from the blade server.
  • each of the plurality of switch blades has unique management information unique to each switch blade and common management information common to the plurality of switch blades as configuration definition information.
  • the unique management information includes a device name and an IP (Internet Protocol) address
  • the common management information includes virtual LAN information described later, a password, and settings of each interface mounted on the switch blade.
  • FIG. 2A and FIG. 2B show processing executed by the administrator when a server blade is changed, such as a server blade upgrade. Note that the administrator executes the processes of FIGS. 2A and 2B even when server blades are added or integrated.
  • the administrator first checks whether or not the server blade to be changed can communicate (step S1). As a result of the communication confirmation, when there is no communication failure of the change target server blade, the administrator shuts down the power supply of the change target server blade (step S2). The administrator replaces the server blade to be changed with a new server blade (step S3), and changes the configuration definition information in the setting file including the unique management information and the common management information in each switch blade (step S4). ). Thereafter, the administrator turns on the power of the new server blade (step S5), checks whether the new server blade can communicate (step S6), and ends this processing.
  • step S4 of FIG. 2A will be described in detail.
  • the administrator confirms the configuration definition information in one switch blade (step S11), and backs up the configuration definition information in a memory (step S12). Thereafter, the administrator changes the configuration definition information in one switch blade (particularly, setting of the interface including the LAN port) (step S13). Similarly, the administrator confirms the configuration definition information in the other switch blade (step S14), and backs up the configuration definition information in the memory (step S15). Thereafter, the administrator changes the configuration definition information in the other switch blade (particularly, setting of the interface including the LAN port) (step S16). As described above, when the server blade is changed, added, or integrated, the administrator performs optimization of the network.
  • a file environment information management method is known in which common information in the file environment information is prevented from inconsistent between machines and individual information can be freely changed for each machine.
  • a system that supplies information to all machines in the system by simply defining information for one machine is known.
  • JP 7-36764 A Japanese Patent Laid-Open No. 6-60001
  • the administrator changes the interface setting included in the common management information by the number of server blades changed, added or integrated. It takes a lot of time to change the interface settings.
  • the configuration definition information of one switch blade cannot be simply copied to the other switch blade, and an erroneous setting may occur.
  • a management device, an information processing device, a control method, and a program disclosed in the specification are intended to reduce the update time of common information set in a plurality of switch devices.
  • the management device disclosed in the specification is based on an update flag that is set in a change location when common information set in a plurality of switch devices is changed.
  • a detecting unit that detects a change in information; and when the detecting unit detects a change in the common information, the information on the changed part in which the update flag is set, which is included in one switch device, Updating means for updating common information set in the switch device.
  • the information processing device disclosed in the specification includes a plurality of switch devices having setting means for setting an update flag at a change location when common information set in the plurality of switch devices is changed, and the update flag Based on the detection means for detecting the change of the common information, and when the detection means detects the change of the common information, the change location in which the update flag is set included in one switch device And a management device having update means for updating common information set in the other switch device.
  • the program disclosed in the specification detects a change in common information based on an update flag set in a change location when common information set in a plurality of switch devices is changed. And when the detection means detects a change in the common information, the information is set in the other switch device by using the information of the change location in which the update flag is set, which is included in one switch device. It is made to function as an updating means for updating common information.
  • the management device, information processing device, control method, and program disclosed in the specification can shorten the update time of common information set in a plurality of switch devices.
  • FIG. 1 It is a figure which shows an example of structure definition information.
  • (A), (B) is a flowchart which shows the process which an administrator performs. It is a figure which shows schematic structure of a blade server.
  • (A) is a block diagram showing a configuration of a switch blade.
  • (B) is a block diagram showing a configuration of a management blade. It is a figure which shows the connection relation of a some switch blade, a some server blade, and a management blade. It is a figure which shows the connection relation of a some switch blade, a some server blade, and a management blade.
  • (A) to (C) are explanatory diagrams of a common management information flag and a configuration definition update flag.
  • FIG. 3 is a diagram schematically showing a schematic configuration of the blade server.
  • a blade server 1 serving as an information processing device includes a plurality of server blades 2 (information processing units), a plurality of switch blades 3 (switch devices), a plurality of pass-through blades 4, a plurality of management blades 5 (management devices), and a plurality of power supplies. 6 and a plurality of fans 7 are mounted.
  • the plurality of switch blades 3, the plurality of pass-through blades 4, the plurality of management blades 5, the plurality of power supplies 6, and the plurality of fans 7 are respectively configured redundantly. This is because even if one of these fails, the other can be used.
  • Each server blade 2 is a single unit that aggregates server functions, and includes a memory, a hard disk, a processor, an interface, and the like.
  • Each switch blade 3 is a switch that performs switching of a plurality of wirings such as an inter-server interface that connects a plurality of server blades 2.
  • Each pass-through blade 4 is an interface for connecting the blade server 1 to a LAN (Local Area Network).
  • Each management blade 5 performs power on / off, temperature management, communication failure detection, and the like.
  • Each power source 6 supplies power to each element included in the blade server 1.
  • Each fan 7 discharges hot air in the blade server 1 to the outside.
  • FIG. 4A is a block diagram showing the configuration of the switch blade 3.
  • FIG. 4B is a block diagram showing the configuration of the management blade 5.
  • the switch blade 3 is connected to a user PC (Personal Computer) via a CPU (Central Processing Unit) 31 (setting means) that controls the entire switch blade, a memory 32 that stores configuration definition information and a control program described later, and a LAN cable.
  • the switch blade 3 may include a plurality of LAN ports 33 and a plurality of console ports 34.
  • the management blade 5 includes a CPU 51 (detection unit, update unit) that controls the entire management blade, a memory 52 that stores configuration definition information and a control program, which will be described later, a power controller 53 that controls on / off of the power supply 6, and a user interface 54.
  • the user interface 54 includes a serial port connected to the switch blade 3 via a serial cable and a LAN port connected to the user PC via a LAN cable.
  • FIG. 5 and 6 are diagrams showing a connection relationship among the plurality of switch blades 3, the plurality of server blades 2, and the management blade 5.
  • FIG. 5 and 6, the plurality of switch blades 3 shown in FIG. 3 are switch blades 3A and 3B
  • the plurality of server blades 2 shown in FIG. 3 are server blades 2A and 2B.
  • the switch blade 3A includes a memory 32A, a plurality of LAN ports 33A-1 to 33A-3, and a console port 34A.
  • the switch blade 3B includes a memory 32B, a plurality of LAN ports 33B-1, 33B-2, and a console port 34B.
  • the server blade 2A includes LAN ports 21A-1 and 21A-2.
  • the server blade 2B includes LAN ports 21B-1 to 21B-3.
  • the management blade 5 includes console ports 54-1 to 54-3. 5 and 6, the solid line indicates a LAN cable connecting LAN ports, and the alternate long and short dash line indicates a serial cable connecting user interfaces.
  • the user sets the switch blade 3A as a master switch blade that mainly operates in a redundant configuration, for example, via the user PC 10, and the switch blade 3B is a slave that mainly waits in a redundant configuration, for example.
  • the switch blade 3B may be set as a master switch blade
  • the switch blade 3A may be set as a slave switch blade.
  • the memory 32A of the switch blade 3A and the memory 32B of the switch blade 3B include, as configuration definition information such as a setting file, unique management information unique to each switch blade and both switch blades.
  • Specific management information includes the device name and IP address
  • common management information includes virtual LAN information, passwords, settings of each interface mounted on the switch blade (that is, settings of each port including a LAN port), etc.
  • the virtual LAN information is information indicating a virtual LAN group to which each interface (each port) belongs. For example, when a server blade is added, setting of virtual LAN information is executed in order to assign a port connected to the added server blade to an existing virtual LAN group or a new virtual LAN group.
  • the password is information necessary for the switch blade to access each server blade.
  • Each interface setting is information indicating connection destinations of a plurality of LAN ports and console ports provided in the switch blade.
  • the memory 52 of the management blade 5 holds the changed contents when the common management information in the setting file of the switch blade 3A (master switch blade) is changed.
  • the management blade 5 reflects the contents of the change in the common management information such as the setting file of the switch blade 3B (slave switch blade).
  • the user PC 10 since the user PC 10 is connected to the management blade 5 via a serial cable, the user can change the common management information of the switch blade 3 ⁇ / b> A via the management blade 5.
  • the user PC 10 since the user PC 10 is connected to the switch blade 3A via the TELNET protocol, the user can change the common management information of the switch blade 3A.
  • the user PC 10 may be connected to the switch blade 3B via the TELNET protocol.
  • the common management information in the setting file or the like of the switch blade 3A is displayed on the user PC 10.
  • the switch blade 3B using the TELNET command the common management information in the setting file or the like of the switch blade 3B is displayed on the user PC 10.
  • the switch blades 3A and 3B have a common management information flag (common flag) indicating that the information is commonly set in the switch blades 3A and 3B (that is, common management information), and the common management information.
  • a configuration definition update flag (update flag) indicating changed information is set in the common management information.
  • the management blade 5 monitors the common management information of the switch blade 3A based on the common management information flag of the switch blade 3A.
  • the management blade 5 can specify the monitoring target from the configuration definition information using the common management information flag.
  • the management blade 5 updates the common management information of the switch blade 3B using the changed common management information of the switch blade 3A based on the configuration definition update flag of the switch blade 3A.
  • the switch blades 3A and 3B set the common management information flag (“*” in FIG. 7A) to the common management information by writing it in a setting file or the like.
  • the CPU 31 of the switch blade 3A writes in the setting file or the like to change the common management information.
  • the configuration definition update flag (“-” in FIG. 7B) is set.
  • the CPU 51 of the management blade 5 monitors the configuration definition information of the switch blade 3A periodically (for example, every 5 minutes).
  • the CPU 51 stores the information in which the configuration definition update flag is set in the configuration definition information of the switch blade 3A in the memory 52.
  • the CPU 51 updates the common management information of the switch blade 3B using the changed information of the switch blade 3A when monitoring the configuration definition information of the switch blade 3A.
  • FIG. 7C shows a state where the common management information of the switch blade 3B is updated. Note that the monitoring timing of the configuration definition information of the switch blades 3A and 3B is set in advance in the memory 52 of the management blade 5 and can be changed by the user PC 10.
  • the CPU 51 monitors the presence / absence of the setting of the configuration definition update flag in the configuration definition information of the switch blade 3A periodically, that is, every preset time, so that the switch blade is set every preset time. 3B common management information can be updated.
  • the CPU 51 transmits a change completion command to the switch blade 3A.
  • the CPU 31 of the switch blade 3A cancels the configuration definition update flag in the configuration definition information. Even after the configuration definition update flag is canceled, the CPU 51 periodically monitors the configuration definition information of the switch blade 3A in order to cope with the change of the common management information.
  • FIG. 8 is a flowchart showing an example of setting and operation of the blade server 1.
  • the CPU 31 of the switch blades 3A and 3B sets a common management information flag in the common management information (step S20).
  • the user sets the master switch blade and the slave switch blade to the switch blades 3A and 3B, respectively (step S21).
  • the switch blade 3A is set as a master switch blade and the switch blade 3B is set as a slave switch blade.
  • step S32 If the user has not changed the common management information in the setting file or the like of the master switch blade (NO in step S22), the process of step S32 described later is executed.
  • the CPU 31 of the master switch blade sets the configuration definition update flag in the changed portion of the common management information of itself (step S23). ).
  • the CPU 51 of the management blade 5 logs in to the master switch blade (step S24), and acquires the common management information of the portion where the configuration definition update flag is set in the configuration definition information (step S25). Thereafter, the CPU 51 logs out from the master switch blade that has logged in via the TELNET protocol (step S26).
  • the CPU 51 logs in to the slave switch blade via the TELNET protocol (step S27), and updates the common management information of the slave switch blade using the common management information of the part changed by the master switch blade (step S28).
  • the CPU 51 logs out from the slave switch blade that has logged in via the TELNET protocol (step S29), and notifies the master switch blade of the change completion command (step S30).
  • the CPU 31 of the master switch blade cancels the configuration definition update flag in the configuration definition information (step S31).
  • the CPU 51 periodically monitors the common management information of the master switch blade (step S32). The process returns to step S22.
  • FIG. 9 is a diagram showing a processing sequence when the user changes the common management information of the master switch blade via the console port (ie, serial communication) of the management blade.
  • the user sets the switch blade 3A as a master switch blade (A1), and sets the switch blade 3B as a slave switch blade (A2).
  • the user notifies the management blade 5 of a command for monitoring the configuration definition update flag set in the common management information such as the setting file of the switch blade 3A (A3).
  • the management blade 5 monitors whether the configuration definition update flag is set in the common management information such as the setting file of the switch blade 3A (A4).
  • the switch blade 3A sets a configuration definition update flag in the changed portion of the common management information (A6).
  • the management blade 5 monitors whether the configuration definition update flag is set in the common management information such as the setting file of the switch blade 3A (A7). At this time, since the configuration definition update flag is set in the common management information of the switch blade 3A, the management blade 5 acquires the common management information of the portion where the configuration definition update flag is set (A8). Then, the management blade 5 updates the common management information of the switch blade 3B using the common management information of the part changed by the switch blade 3A (A9). Specifically, the management blade 5 overwrites information corresponding to the switch blade 3B with information on the part changed by the switch blade 3A. Thereafter, the management blade 5 notifies the switch blade 3A of a change completion command (A10). The switch blade 3A cancels the configuration definition update flag (A11). Thereafter, the management blade 5 periodically monitors the configuration definition update flag in the configuration definition information in the switch blade 3A (A12).
  • FIG. 10 is a diagram showing a processing sequence when the user changes the common management information of the master switch blade via the TELNET protocol.
  • the processing sequence of FIG. 10 is that the user changes the common management information of the switch blade 3A using the TELNET protocol (that is, the LAN port 33A-3 of the switch blade 3A) (A5 ′). Different from the sequence.
  • the other processing sequence is the same as the processing sequence of FIG.
  • the management blade 5 monitors the change of the common management information such as the setting file of the master switch blade, and updates the common management information of the slave switch blade using the changed common management information. .
  • the management blade 5 monitors the change of the common management information of both switch blades, and uses the common management information of the changed part of one switch blade to The common management information of the corresponding part of the slave switch blades may be updated. In this case, the user does not need to set the master switch blade and the slave switch blade in the switch blades 3A and 3B, respectively.
  • the CPU 51 of the management blade 5 is set at the change location when the common management information set in the setting files of the switch blades 3A and 3B is changed. Based on the configuration definition update flag, a change in the common management information is detected. Then, the CPU 51 updates the common management information set in the setting file or the like of the switch blade 3B, using the information on the changed part in which the configuration definition update flag is set, which is included in the switch blade 3A. Therefore, the update time of the common management information set in the switch blades 3A and 3B can be shortened. In addition, since the common management information set in the setting file of the switch blade 3B and the like is not manually changed, mistakes in setting change can be reduced. For example, when the switch blade 3 is replaced, the common management information of the other switch blade 3 can be easily reflected on the new switch blade 3.
  • the CPU 51 of the management blade 5 can specify the monitoring target (that is, the common management information) in the configuration definition information. Further, since the configuration definition update flag is set in the changed common management information, the CPU 51 of the management blade 5 can easily detect the information on the changed location of the common management information.
  • the above-described embodiment can also be realized by supplying a recording medium in which a software program for realizing the function of the management blade 5 is recorded to the blade server 1 and the CPU 51 reads and executes the program stored in the storage medium.
  • Examples of the storage medium for supplying the program include a CD-ROM, DVD, Blu-ray, or SD card.
  • the CPU 51 executes the software program for realizing the function of the management blade 5, and the same effects as those of the above embodiment can be obtained.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)
  • Computer And Data Communications (AREA)
  • Stored Programmes (AREA)

Abstract

Lorsqu'un ensemble d'information de gestion commune fixées dans les lames de contact (3A, 3B) a été modifié, une unité de traitement centrale (51) d'un lame de contact de gestion (5) détecte des changements dans l'information de gestion commune sur la base d'un drapeau de mise à jour de définition de configuration réglé dans la section modifiée, et utilise l'information de la section changée dans laquelle le drapeau de mise à jour de définition de configuration a été défini - de telles informations étant comprises dans la lame de contact (3A) - pour actualiser l'informations de gestion commune fixée par la lame de contact (3B), ce qui permet de réduire le temps requis pour la mise à jour de l'information de gestion communes dans les lames de contact (3A, 3B).
PCT/JP2010/063611 2010-08-11 2010-08-11 Dispositif de gestion, dispositif de traitement d'informations, procédé et programme de commande WO2012020481A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/JP2010/063611 WO2012020481A1 (fr) 2010-08-11 2010-08-11 Dispositif de gestion, dispositif de traitement d'informations, procédé et programme de commande
JP2012528535A JP5413514B2 (ja) 2010-08-11 2010-08-11 管理装置、情報処理装置、制御方法及びプログラム
EP10855882.6A EP2605458B1 (fr) 2010-08-11 2010-08-11 Dispositif de gestion, dispositif de traitement d'informations, procédé et programme de commande
US13/758,310 US9432244B2 (en) 2010-08-11 2013-02-04 Management device, information processing device and control method that use updated flags to configure network switches

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2010/063611 WO2012020481A1 (fr) 2010-08-11 2010-08-11 Dispositif de gestion, dispositif de traitement d'informations, procédé et programme de commande

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/758,310 Continuation US9432244B2 (en) 2010-08-11 2013-02-04 Management device, information processing device and control method that use updated flags to configure network switches

Publications (1)

Publication Number Publication Date
WO2012020481A1 true WO2012020481A1 (fr) 2012-02-16

Family

ID=45567460

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2010/063611 WO2012020481A1 (fr) 2010-08-11 2010-08-11 Dispositif de gestion, dispositif de traitement d'informations, procédé et programme de commande

Country Status (4)

Country Link
US (1) US9432244B2 (fr)
EP (1) EP2605458B1 (fr)
JP (1) JP5413514B2 (fr)
WO (1) WO2012020481A1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5948345B2 (ja) 2011-01-11 2016-07-06 エイ１０ ネットワークス インコーポレイテッドＡ１０ Ｎｅｔｗｏｒｋｓ， Ｉｎｃ． 仮想アプリケーションデリバリシャーシシステム
US9154577B2 (en) 2011-06-06 2015-10-06 A10 Networks, Inc. Sychronization of configuration file of virtual application distribution chassis
US10742559B2 (en) 2014-04-24 2020-08-11 A10 Networks, Inc. Eliminating data traffic redirection in scalable clusters
US9961130B2 (en) 2014-04-24 2018-05-01 A10 Networks, Inc. Distributed high availability processing methods for service sessions
US10771475B2 (en) 2015-03-23 2020-09-08 Extreme Networks, Inc. Techniques for exchanging control and configuration information in a network visibility system
US10129088B2 (en) 2015-06-17 2018-11-13 Extreme Networks, Inc. Configuration of rules in a network visibility system
US10911353B2 (en) * 2015-06-17 2021-02-02 Extreme Networks, Inc. Architecture for a network visibility system
US10318288B2 (en) 2016-01-13 2019-06-11 A10 Networks, Inc. System and method to process a chain of network applications
US10243813B2 (en) 2016-02-12 2019-03-26 Extreme Networks, Inc. Software-based packet broker

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0660001A (ja) 1992-05-26 1994-03-04 Nec Corp 共通情報デリバリ装置
JPH0736764A (ja) 1993-07-22 1995-02-07 Nec Corp ファイル環境情報管理方式
JPH11154110A (ja) * 1997-11-20 1999-06-08 Nippon Telegr & Teleph Corp <Ntt> ミラーサーバの同期方法

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6128656A (en) * 1998-09-10 2000-10-03 Cisco Technology, Inc. System for updating selected part of configuration information stored in a memory of a network element depending on status of received state variable
JP4148605B2 (ja) * 1999-08-06 2008-09-10 富士通株式会社 ネットワークシステムおよびサーバ
US7397768B1 (en) * 2002-09-11 2008-07-08 Qlogic, Corporation Zone management in a multi-module fibre channel switch
US7904599B1 (en) * 2003-03-28 2011-03-08 Cisco Technology, Inc. Synchronization and auditing of zone configuration data in storage-area networks
US7433300B1 (en) * 2003-03-28 2008-10-07 Cisco Technology, Inc. Synchronization of configuration data in storage-area networks
JP2007011704A (ja) * 2005-06-30 2007-01-18 Canon Inc 情報処理装置及びその制御方法及びプログラム
US20070038679A1 (en) * 2005-08-15 2007-02-15 Mcdata Corporation Dynamic configuration updating in a storage area network
TWI280764B (en) * 2005-11-02 2007-05-01 Inst Information Industry Method for rapidly linking mobile node and access point in wireless local area network
JP5115085B2 (ja) * 2006-10-27 2013-01-09 富士通株式会社 ネットワーク管理プログラム及びネットワーク管理装置
US20080109568A1 (en) * 2006-11-03 2008-05-08 Varadachari Rengarajan Method and System for Detecting Device Configuration Changes
US20090070425A1 (en) * 2007-09-12 2009-03-12 Hewlett-Packard Development Company, L.P. Data processing system, method of updating a configuration file and computer program product
US8326978B2 (en) * 2010-02-05 2012-12-04 International Business Machines Corporation Automatic updates to fabric alert definitions for fabric segmentation, fabric merge, and fabric principal switch changes
US8244839B2 (en) * 2010-06-30 2012-08-14 International Business Machines Corporation Network problem determination

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0660001A (ja) 1992-05-26 1994-03-04 Nec Corp 共通情報デリバリ装置
JPH0736764A (ja) 1993-07-22 1995-02-07 Nec Corp ファイル環境情報管理方式
JPH11154110A (ja) * 1997-11-20 1999-06-08 Nippon Telegr & Teleph Corp <Ntt> ミラーサーバの同期方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP2605458A4
TOSHIHIRO OZAWA ET AL.: "Organic Computing", FUJITSU 2005-1 GATSUGO, vol. 56, no. 1, 11 January 2005 (2005-01-11), pages 70 - 74, XP055126913 *

Also Published As

Publication number Publication date
US9432244B2 (en) 2016-08-30
US20130151686A1 (en) 2013-06-13
JP5413514B2 (ja) 2014-02-12
EP2605458B1 (fr) 2016-06-22
JPWO2012020481A1 (ja) 2013-10-28
EP2605458A4 (fr) 2015-06-10
EP2605458A1 (fr) 2013-06-19

Similar Documents

Publication Publication Date Title
JP5413514B2 (ja) 管理装置、情報処理装置、制御方法及びプログラム
US8547825B2 (en) Switch fabric management
US8661434B1 (en) Migration of computer security modules in a virtual machine environment
JP5637873B2 (ja) 計算機システムおよびｐｃｉカードのｈｂａ識別子引き継ぎ方式
US20140129819A1 (en) Cloud cluster system and boot deployment method for the same
US8127128B2 (en) Synchronization of swappable module in modular system
JP4448878B2 (ja) 障害回復環境の設定方法
US10657232B2 (en) Information processing apparatus and method of controlling information processing apparatus
JP5333579B2 (ja) 管理サーバ、ブートサーバ、ネットワークブートシステムおよびネットワークブート方法
US20170010874A1 (en) Provisioning storage devices in a data center
US8904055B2 (en) Switching control device and switching control method
JP4797636B2 (ja) 複合型情報プラットフォーム装置とその情報処理装置構成方法
JP2007164394A (ja) ストレージ切替システム、ストレージ切替方法、管理サーバ、管理方法および管理プログラム
US20130262700A1 (en) Information processing system and virtual address setting method
JP2013073289A (ja) 多重化システム、データ通信カード、状態異常検出方法、及びプログラム
JPWO2012176922A1 (ja) ポリシー更新装置、ポリシー管理システム、ポリシー更新方法およびポリシー管理方法
JP5509176B2 (ja) 計算機システムおよび計算機システムにおけるモジュール引き継ぎ方法
US11126516B2 (en) Dynamic formation of a failure domain
JP5531487B2 (ja) サーバシステム及びサーバシステムの管理方法
US20170078151A1 (en) Control apparatus, information processing system, and computer-readable storage medium having control program stored therein
JP2006079379A (ja) 複合型計算機装置およびその管理方法
JP5854130B2 (ja) 情報処理装置、情報処理方法及びプログラム
JP5439736B2 (ja) コンピュータ管理システム、コンピュータシステムの管理方法、及びコンピュータシステムの管理プログラム
JP2010244129A (ja) 計算機システム
WO2015011895A1 (fr) Dispositif de traitement d&#39;informations, système d&#39;entrée-sortie (e/s) et procédé de commande e/s

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10855882

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2012528535

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 2010855882

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE