EP2782294A1 - Appareil de traitement d'informations et procédé pour générer des informations de couplage - Google Patents

Appareil de traitement d'informations et procédé pour générer des informations de couplage Download PDF

Info

Publication number
EP2782294A1
EP2782294A1 EP14151260.8A EP14151260A EP2782294A1 EP 2782294 A1 EP2782294 A1 EP 2782294A1 EP 14151260 A EP14151260 A EP 14151260A EP 2782294 A1 EP2782294 A1 EP 2782294A1
Authority
EP
European Patent Office
Prior art keywords
adapter
data
address
coupled
port
Prior art date
Legal status (The legal status 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 status listed.)
Granted
Application number
EP14151260.8A
Other languages
German (de)
English (en)
Other versions
EP2782294B1 (fr
Inventor
Atsushi Nagase
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
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 Fujitsu Ltd filed Critical Fujitsu Ltd
Publication of EP2782294A1 publication Critical patent/EP2782294A1/fr
Application granted granted Critical
Publication of EP2782294B1 publication Critical patent/EP2782294B1/fr
Not-in-force legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/40—Bus structure
    • G06F13/4063—Device-to-bus coupling
    • G06F13/4068—Electrical coupling
    • G06F13/4072—Drivers or receivers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G06F13/16—Handling requests for interconnection or transfer for access to memory bus
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/40—Bus structure
    • G06F13/4004—Coupling between buses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40052—High-speed IEEE 1394 serial bus
    • H04L12/40078—Bus configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks

Definitions

  • the embodiments discussed herein are related to a technique of generating coupling information of a network.
  • Link Layer Discovery Protocol is utilized to obtain information on the coupling between a port of a network switch and a network adapter of an apparatus coupled to the port.
  • the LLDP is a protocol for performing various kinds of setting or administration by detecting a coupling destination node. For example, as illustrated in FIG. 1 , when a network adapter 1001 of a physical server and a port n of a network switch sw1 are coupled to each other, the LLDP enables the network switch sw1 to recognize that a media access control (MAC) address of the network adapter 1001 to which the network switch sw1 is coupled indicates "A".
  • the coupling relation may be ascertained by searching for the physical server that has the MAC address "A" in another manner.
  • a physical network adapter 1002 is divided into a plurality of logical network adapters 1002a, 1002b, 1002c, and 1002d.
  • the MAC addresses of the logical network adapters 1002a, 1002b, 1002c, and 1002d indicate "A", "B", "C”, and "D", respectively.
  • the MAC address of the coupling destination node is acquired in the network switch sw1 via the LLDP, only one MAC address, which is for example, the MAC address "A”, may be obtained while it is unclear which port of which network switch the nodes corresponding to the other MAC addresses "B" to "D" are coupled to.
  • a technique may be provided that enables coupling information of a network to be obtained even when a network adapter logically divided is used.
  • a processing apparatus includes a memory, and a processor coupled to the memory and configured to acquire first data that indicates correspondence relationship between a first address given to a first adapter of a first device and a first bus number given to a first bus coupled to the first adapter, acquire second data that indicates correspondence relationship between a second address given to a second adapter of a first device and a second bus number given to a second bus coupled to the second adapter, acquire third data that indicates correspondence relationship between the first address and a port number given to a port of a second device, the port being coupled to the first adapter with the first bus, and when the second bus number is identical to the first bus number, generate fourth data that indicates that the second adapter is coupled to the port.
  • a plurality of physical servers are coupled to a plurality of network switches while one or more of the physical servers include a network adapter logically divided.
  • An information processing apparatus 100 which performs main processes in the present embodiment, is coupled to each of the physical servers and each of the network switches through a local area network (LAN) for management 200.
  • LAN local area network
  • FIG. 4 is a function block diagram illustrating the information processing apparatus 100.
  • the information processing apparatus 100 is coupled to the LAN for management 200 to which the plurality of physical servers and network switches are coupled, and includes a processing unit 101, a first data acquiring unit 102, a second data acquiring unit 103, a data storing unit 104, and an output unit 105.
  • the first data acquiring unit 102 acquires server data from each hypervisor and causes the server data to be stored in the data storing unit 104.
  • the second data acquiring unit 103 acquires switch data from each network switch and causes the switch data to be stored in the data storing unit 104.
  • the processing unit 101 generates coupling information of the network by performing processes using the server data and the switch data stored in the data storing unit 104, and causes the generated coupling information to be stored in the data storing unit 104 as, for example, a coupling data table.
  • the output unit 105 outputs the coupling information of the network stored in the data storing unit 104 to, for example, a display device, a printing device, or another computer coupled through the network.
  • the coupling state illustrated in FIG. 5 is assumed so as to facilitate the description below. That is, the physical server managed by a hypervisor hv1 includes network adapters 1010 to 1012. The network adapter 1010 is logically divided into four while the network adapters 1011 and 1012 are not logically divided.
  • the physical network adapter 1010 includes logical network adapters na1 to na4, which have MAC addresses of "A", "B", “C”, and "D", respectively.
  • the hypervisor hv1 may recognize na1 to na4 as identifiers.
  • the physical network adapter 1011 is identified as a network adapter corresponding to an identifier na5
  • the physical network adapter 1012 is identified as a network adapter corresponding to an identifier na6.
  • the network adapters are coupled to peripheral component interconnect (PCI) buses, and each logical device is provided with location information on the PCI bus.
  • PCI peripheral component interconnect
  • the logical network adapter na1 is provided with location information "02:00.0”
  • the logical network adapter na2 is provided with location information "02:00.1”
  • the logical network adapter na3 is provided with location information "02:00.2”
  • the logical network adapter na4 is provided with location information "02:00.3”
  • the logical network adapter na5 is provided with location information "04:00.0”
  • the logical network adapter na6 is provided with location information "06:00.0".
  • the location information as illustrated in FIG.
  • xx represents a bus number
  • yy represents a device number
  • z represents a function number.
  • the logical network adapters na1 to na4 of the identical physical network adapter 1010 have an identical bus number.
  • all the bus numbers of the logical network adapters na1 to na4 indicate "02", which is not identical with the bus numbers in the location information on the physical network adapters 1011 and 1012 different from the physical network adapter 1010.
  • the physical network adapter 1010 is coupled to a port n of a network switch sw1
  • the physical network adapter 1011 is coupled to a port m of a network switch sw2
  • the physical network adapter 1012 is coupled to a port p of a network switch sw3.
  • the first data acquiring unit 102 outputs a request to each of the hypervisors to acquire server data from the hypervisors, and causes the server data to be stored in the data storing unit 104 (S1).
  • the data illustrated in FIG. 8 is acquired from the hypervisor hv1.
  • the data in the example of FIG. 8 includes a plurality of combinations, each of which is made up of an identifier (ID) of a logical network adapter, a MAC address, and location information, and an identifier of a hypervisor.
  • the second data acquiring unit 103 outputs a request to each of the network switches to acquire switch data from the network switches, and causes the switch data to be stored in the data storing unit 104 (S3).
  • the data illustrated in FIG. 9 is acquired from the network switches.
  • the data in the example of FIG. 9 includes a plurality of combinations, each of which is made up of a switch ID, a port number, and a coupling destination MAC address.
  • the processing unit 101 identifies one unprocessed network switch in the switch data (S5).
  • the processing unit 101 identifies one unprocessed port of the identified network switch in the switch data (S7).
  • processing unit 101 identifies one unprocessed hypervisor in the server data (S9).
  • processing unit 101 identifies one unprocessed network adapter server data managed by the identified hypervisor (S11).
  • the processing unit 101 compares the coupling destination MAC address of the port identified in S7 and the MAC address of the network adapter identified in S11 (S13). After that, the process moves on to the process of FIG. 10 through a terminal A.
  • the processing unit 101 determines whether the MAC addresses compared in S13 match (S15). When the MAC addresses do not match, the process moves on to the process of FIG. 13 through a terminal B.
  • the processing unit 101 causes the switch ID, the port number, the hypervisor ID, and the MAC address of the identified network adapter to be registered in the coupling data table of the data storing unit 104 (S17). For example, when the switch ID "sw1", the port number "n”, the coupling destination MAC address "A”, the hypervisor ID "hv1”, the network adapter ID "na1", and the MAC address "A" are processed, the data illustrated in FIG. 11 is stored in the coupling data table.
  • the processing unit 101 identifies the PCI bus number of the network adapter identified in S11 based on the server data (S19). In the above-described example, "02" is identified as indicated in FIG. 8 .
  • the processing unit 101 searches for another network adapter that has a PCI bus number identical with the identified bus number and is managed by the identified hypervisor in the server data (S21).
  • another network adapter ID with the PCI bus number "02" is searched for except "na1" in the location information with which the hypervisor ID "hv1" is correlated, "na2", “na3", and "na4" are obtained.
  • the processing unit 101 determines whether or not another network adapter has been extracted in S21 (S23). For example, when processing the network adapter ID "na5" or "na6", another network adapter, which satisfies such conditions, may not be extracted. When another network adapter, which satisfies such conditions, is not extracted, the process moves on to the process of FIG. 13 through the terminal B.
  • the processing unit 101 causes the switch ID, the port number, the hypervisor ID, and the MAC address of the another network adapter having been extracted to be registered in the coupling data table in the data storing unit 104 (S25). Then, the process moves on to the process of FIG. 13 through the terminal B.
  • the MAC address "B" corresponding to the network adapter "na2”, the MAC address "C” corresponding to the network adapter "na3”, and the MAC address "D” corresponding to the network adapter "na4" are registered. That is, the coupling data table is changed as illustrated in FIG. 12.
  • FIG. 12 illustrates that four different MAC addresses are registered even when the switch IDs, the port numbers, and the hypervisor IDs each are identical.
  • the network adapters "na2", “na3”, and “na4" may be treated as processed network adapters in S11.
  • the processing unit 101 determines whether an unprocessed network adapter is present in the server data (S27). When an unprocessed network adapter is present, the process returns to S11 through a terminal C. When no unprocessed network adapter is present, the processing unit 101 determines whether an unprocessed hypervisor is present in the server data (S29). When an unprocessed hypervisor is present, the process returns to S9 through a terminal D. When no unprocessed hypervisor is present, the processing unit 101 determines whether an unprocessed port is present in the switch data (S31). When an unprocessed port is present, the process returns to S7 through a terminal E.
  • the processing unit 101 determines whether an unprocessed network switch is present in the switch data (S33). When an unprocessed network switch is present, the process returns to S5 through a terminal F. When no unprocessed network switch is present, the output unit 105 outputs the coupling data table (S35) and the process ends.
  • the coupling data table illustrated in FIG. 14 may be obtained by performing the processes described above. Since the physical network adapters 1011 and 1012 are not logically divided, addition by one record is performed for the network switches sw2 and sw3.
  • the network configuration may be correctly grasped and in case of failure occurrence, for example, the failure causing portion or the range in which the failure exerts influence may be easily identified.
  • resources may be utilized advantageously by, for example, changing the virtualization environment so that the virtualization environment is suitable for the allocation of bands for the logical division. That is, the operational management of the network may be facilitated and costs desired for the operational management may be reduced.
  • one physical network card 1500 is coupled to a physical server and the physical network card 1500 is provided with two physical network adapters 1510 and 1520, each of which is logically divided. That is, a hypervisor hv1 grasps that logical network adapters na11 to na14 are provided.
  • the MAC address of the logical network adapter na11 indicates "A” and the PCI location information on the logical network adapter na11 indicates "02:00.0".
  • the MAC address of the logical network adapter na12 indicates "B” and the PCI location information on the logical network adapter na12 indicates "02:00.1".
  • the MAC address of the logical network adapter na13 indicates "C” and the PCI location information on the logical network adapter na13 indicates "02:00.2".
  • the MAC address of the logical network adapter na14 indicates "D” and the PCI location information on the logical network adapter na14 indicates "02:00.3”.
  • a port n of a network switch sw1 is coupled to the physical network adapter 1510, and a port m of a network switch sw2 is coupled to the physical network adapter 1520.
  • the PCI location information indicates the identical bus numbers and this situation may not be handled in the first embodiment.
  • the hypervisor hv1 grasps the relations between virtual network adapters of virtual machines and the logical network adapters of the network card.
  • a virtual network adapter 1 of the virtual machine is coupled to the logical network adapter na11 through a virtual switch vsw1
  • virtual network adapters 2 and 3 of the virtual machines are coupled to the logical network adapter na12 through a virtual switch vsw2.
  • a virtual network adapter 4 of the virtual machine is coupled to the logical network adapter na13 through a virtual switch vsw3
  • a virtual network adapter 5 of the virtual machine is coupled to the logical network adapter na14 through a virtual switch vsw4.
  • Each of the virtual network adapters is provided with an IP address.
  • a coupling data table may be generated.
  • an information processing apparatus 100b is configured as illustrated in FIG. 17 .
  • the information processing apparatus 100b differs from the information processing apparatus 100 according to the first embodiment, which is illustrated in FIG. 4 , in that a ping execution instructing unit 106 is provided, and that since the contents of the server data to be acquired are different, a first data acquiring unit 102b is provided instead of the first data acquiring unit 102, and that since the processes to be performed are partially different, a processing unit 101b is provided instead of the processing unit 101.
  • the network switch is provided with a ping executing unit 301 that executes a ping operation in accordance with an instruction from the ping execution instructing unit 106.
  • FIG. 18 The server data acquired by the first data acquiring unit 102b in S1 is illustrated in FIG. 18 .
  • the data in the example of FIG. 18 includes a plurality of combinations, each of which is made up of a network adapter ID, a MAC address, location information, a virtual switch ID, an IP address of a virtual network adapter, and a hypervisor ID.
  • two virtual network adapters corresponding to two respective IP addresses are coupled to the virtual switch vsw2.
  • the switch data acquired by a second data acquiring unit 103 according to the second embodiment are substantially the same in contents as the switch data acquired by the second data acquiring unit 103 according to the first embodiment, and when the coupling relations are made as illustrated in FIG. 16 , the switch data illustrated in FIG. 19 may be acquired.
  • the processing unit 101b determines whether the MAC addresses compared in S13 match (S41). When the MAC addresses do not match, the process moves on to the process of FIG. 13 through the terminal B.
  • the processing unit 101b causes the switch ID, the port number, hypervisor ID, and the MAC address of the identified network adapter to be registered in the coupling data table in a data storing unit 104 (S43).
  • the switch ID "sw1”, the port number "n”, the hypervisor ID "hv1”, and the MAC address "A" of the network adapter "na11" are processed, similar to the first embodiment, the data illustrated in FIG. 11 is stored in the coupling data table.
  • the processing unit 101b identifies the PCI bus number of the network adapter identified in S11 based on the server data (S45). In the above-described example, "06" is identified as indicated in FIG. 18 .
  • the processing unit 101b searches for another network adapter that has a PCI bus number identical with the identified bus number and is managed by the identified hypervisor in the server data (S47).
  • another network adapter ID with the PCI bus number "06" is searched for except "na11” in the location information with which the hypervisor ID "hv1" is correlated, "na12", “na13", and "na14" are obtained.
  • the processing unit 101b determines whether or not another network adapter has been extracted in S47 (S49).
  • the network adapter that does not satisfy the conditions is not present and when the network adapter that satisfies the conditions is not extracted, the process moves on to the process of FIG. 13 through the terminal B.
  • the processing unit 101b acquires the IP address of the virtual network adapter coupled to the another network adapter having been extracted from the server data (S51).
  • a plurality of virtual network adapters are correlated with the network adapter, such as "na12" in FIG. 18 , one representative IP address may be extracted instead of extracting a plurality of IP addresses. After that, the process moves on to the process of FIG. 21 through a terminal G.
  • the processing unit 101b identifies one unprocessed IP address in the acquired IP addresses (S53). Then, the processing unit 101b causes the ping execution instructing unit 106 to instruct the ping executing unit 301 to execute a ping operation for the identified IP address from the identified port of the identified network switch (S55). The ping executing unit 301 of the identified network switch replies to the ping execution instructing unit 106 regarding the presence or absence of a response, and the ping execution instructing unit 106 notifies the processing unit 101b of the presence or absence of a response.
  • the processing unit 101b determines whether the notification indicating there is a response is received (S57). When the notification indicating there is no response is received, the process moves on to S61. When the notification indicating there is a response is received, the processing unit 101b causes the switch ID, the port number, the hypervisor ID, and the MAC address of another network adapter extracted and correlated with the IP address from which there is a response to be registered in the coupling data table if they are unregistered (S59). Then, the coupling data table illustrated in FIG. 22 may be obtained.
  • the processing unit 101b determines whether or not an unprocessed IP address is present in the IP addresses acquired in S51 (S61). When an unprocessed IP address is present, the process returns to S53. When no unprocessed IP address is present, the process moves on to the process of FIG. 13 through the terminal B.
  • the coupling data table illustrated in FIG. 23 may be obtained.
  • the coupling data table may be obtained even when a plurality of physical network adapters exist in one network card and moreover, the physical network adapters are logically divided.
  • the present application is not limited to the embodiments described above.
  • the function block diagrams in FIGs. 4 and 17 are mere examples and may differ from the configurations of program modules.
  • some processes may be performed in a different order or a plurality of steps may be performed in parallel as long as the results of the processes remain unchanged.
  • the above-described information processing apparatuses 100 and 100b are computer apparatuses, in which for example, as illustrated in FIG. 24 , memory 2501, a central processing unit (CPU) 2503, a hard disk drive (HDD) 2505, a display controlling unit 2507 coupled to a display device 2509, a drive device 2513 for a removable disc 2511, an input device 2515, and a communication controlling unit 2517 for being coupled to a network are coupled through a bus 2519.
  • An operating system (OS) and an application program for performing the processes according to the present embodiments are stored in the HDD 2505, and when executed by the CPU 2503, are read from the HDD 2505 to the memory 2501.
  • OS operating system
  • an application program for performing the processes according to the present embodiments are stored in the HDD 2505, and when executed by the CPU 2503, are read from the HDD 2505 to the memory 2501.
  • the CPU 2503 controls the display controlling unit 2507, the communication controlling unit 2517, and the drive device 2513, which are thus caused to perform certain operations.
  • In-process data is stored mainly in the memory 2501, but may also be stored in the HDD 2505.
  • the application program for performing the above-described processes is stored in the computer-readable removable disc 2511 and distributed, and installed from the drive device 2513 into the HDD 2505.
  • the application program may also be installed into the HDD 2505 via a network, such as the Internet, and the communication controlling unit 2517.
  • a computer apparatus implements various functions as described above when the hardware, such as the CPU 2503 and the memory 2501, and the OS and a program, such as the application program, which are described above, cooperate systematically.
  • the information processing method includes the processes of (A) acquiring first correlation data that includes a port identifier and a first address of a coupling destination device for each port of a communication device, (B) acquiring second correlation data that includes the first address and location information on a logical adapter for each logical adapter of the coupling destination device of the communication device, and (C) when the first correlation data and the second correlation data including the first addresses that match each other are detected, identifying another second correlation data that includes certain data identical to certain data included in the location information on the logical adapter, and generating coupling information on the coupling between the communication device and the coupling destination device based on the first correlation data and the detected second correlation data, which include the matching first addresses, and the another identified second correlation data.
  • To use the location information as described above may bring the coupling information even when the adapter is logically divided.
  • the above-described second correlation data may further include a second address of a virtual device correlated with the logical adapter.
  • the above-described generation process may include (c1) causing the second address of the virtual device included in the another identified second correlation data to be accessed from a port of the communication device related to the first correlation data that includes the matching first address, and being notified of the presence or absence of a response, and (c2) generating the coupling information based on the presence or absence of a response. Then, even when the location information only is not sufficient for the distinction, the coupling information may be obtained desirably.
  • the above-described generation process may be a process of generating coupling information based on the second correlation data that includes the second address from which there is a response and the first correlation data that includes the matching first address.
  • the above-described coupling information may further include data that correlates the identifier, the port identifier, and the first address of the communication device. Additionally, the identifier of the hypervisor or the identifier of the physical device may be correlated.
  • the above-described certain data may be the bus number.
  • the identical bus numbers may indicate existence on the same physical adapter or adapter card.
  • a program for causing a computer to perform the above-described processes may be created, and the program is stored in a computer-readable recording medium or a storage device, which is for example, a flexible disc, an optical disc such as a compact disc read-only memory (CD-ROM), a magnetooptical disc, semiconductor memory such as ROM, or a hard disk.
  • a storage device such as random-access memory (RAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
EP14151260.8A 2013-03-18 2014-01-15 Appareil de traitement d'informations et procédé pour générer des informations de couplage Not-in-force EP2782294B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2013054641A JP6011401B2 (ja) 2013-03-18 2013-03-18 接続情報を生成するための情報処理装置及び方法

Publications (2)

Publication Number Publication Date
EP2782294A1 true EP2782294A1 (fr) 2014-09-24
EP2782294B1 EP2782294B1 (fr) 2015-08-19

Family

ID=49989537

Family Applications (1)

Application Number Title Priority Date Filing Date
EP14151260.8A Not-in-force EP2782294B1 (fr) 2013-03-18 2014-01-15 Appareil de traitement d'informations et procédé pour générer des informations de couplage

Country Status (3)

Country Link
US (2) US9632962B2 (fr)
EP (1) EP2782294B1 (fr)
JP (1) JP6011401B2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017097734A1 (fr) * 2015-12-07 2017-06-15 Eaton Electrical Ip Gmbh & Co. Kg Système de bus comprenant un abonné disposant d'une adresse de sécurité et procédé pour faire fonctionner un système de bus

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111031149B (zh) * 2019-12-19 2022-07-29 北京浪潮数据技术有限公司 一种服务器管理方法、系统、设备及计算机可读存储介质

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010048668A1 (en) * 2000-05-23 2001-12-06 Fujitsu Limited Method and device for controlling data transmission
US6633943B1 (en) * 1999-09-21 2003-10-14 Sony Corporation Method and system for the simplification of leaf-limited bridges
US20050047352A1 (en) * 1998-05-26 2005-03-03 Nicolas Burdin Method for identifying devices in a communication network and device for implementing said method
US20060209848A1 (en) * 2003-04-17 2006-09-21 Helmut Burklin Method for the tranmission of buss ieee 1394 reinitialization messages and device for carrying out said method
JP2007316724A (ja) 2006-05-23 2007-12-06 Hitachi Ltd 計算機システム、管理計算機及びプログラム配布方法
JP2010124129A (ja) 2008-11-18 2010-06-03 Kddi Corp 仮想計算機送信方法、システム、管理装置及びプログラム
JP2011203810A (ja) 2010-03-24 2011-10-13 Hitachi Ltd サーバ、計算機システム及び仮想計算機管理方法

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3631434B2 (ja) * 2000-12-14 2005-03-23 日本電信電話株式会社 Ｉｐルーティング装置及びｉｐルーティング方法
US8838743B2 (en) * 2004-02-13 2014-09-16 Intel Corporation Apparatus and method for a dynamically extensible virtual switch
JP4622835B2 (ja) * 2005-12-07 2011-02-02 株式会社日立製作所 仮想計算機システム及びそのネットワーク通信方法
US20080137676A1 (en) * 2006-12-06 2008-06-12 William T Boyd Bus/device/function translation within and routing of communications packets in a pci switched-fabric in a multi-host environment environment utilizing a root switch
US7940785B2 (en) * 2007-01-08 2011-05-10 International Business Machines Corporation Ethernet adapter packet management
US8184631B2 (en) * 2007-01-22 2012-05-22 Oracle America, Inc. Method for specifying a MAC identifier for a network-interface-device
JP4995015B2 (ja) * 2007-09-13 2012-08-08 株式会社日立製作所 仮想計算機の実行可否検査方法
US8798056B2 (en) * 2007-09-24 2014-08-05 Intel Corporation Method and system for virtual port communications
JP4964735B2 (ja) * 2007-10-24 2012-07-04 株式会社日立製作所 ネットワークシステム、管理計算機、及びフィルタ再構成方法
JP2010010997A (ja) * 2008-06-26 2010-01-14 Alaxala Networks Corp 中継装置及びその制御方法
US8626879B2 (en) * 2009-12-22 2014-01-07 Sling Media, Inc. Systems and methods for establishing network connections using local mediation services
JP5347982B2 (ja) * 2010-01-18 2013-11-20 富士通株式会社 仮想ネットワーク制御プログラム、仮想ネットワーク制御方法および管理装置
US8726093B2 (en) * 2010-06-30 2014-05-13 Oracle America, Inc. Method and system for maintaining direct hardware access in the event of network interface card failure
US8386679B2 (en) * 2011-04-12 2013-02-26 International Business Machines Corporation Dynamic allocation of a direct memory address window
US20140074960A1 (en) * 2012-09-11 2014-03-13 International Business Machines Corporation Compacting a non-biased results multiset

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050047352A1 (en) * 1998-05-26 2005-03-03 Nicolas Burdin Method for identifying devices in a communication network and device for implementing said method
US6633943B1 (en) * 1999-09-21 2003-10-14 Sony Corporation Method and system for the simplification of leaf-limited bridges
US20010048668A1 (en) * 2000-05-23 2001-12-06 Fujitsu Limited Method and device for controlling data transmission
US20060209848A1 (en) * 2003-04-17 2006-09-21 Helmut Burklin Method for the tranmission of buss ieee 1394 reinitialization messages and device for carrying out said method
JP2007316724A (ja) 2006-05-23 2007-12-06 Hitachi Ltd 計算機システム、管理計算機及びプログラム配布方法
JP2010124129A (ja) 2008-11-18 2010-06-03 Kddi Corp 仮想計算機送信方法、システム、管理装置及びプログラム
JP2011203810A (ja) 2010-03-24 2011-10-13 Hitachi Ltd サーバ、計算機システム及び仮想計算機管理方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017097734A1 (fr) * 2015-12-07 2017-06-15 Eaton Electrical Ip Gmbh & Co. Kg Système de bus comprenant un abonné disposant d'une adresse de sécurité et procédé pour faire fonctionner un système de bus
US10762022B2 (en) 2015-12-07 2020-09-01 Eaton Intelligent Power Limited Bus arrangement and method for operating a bus arrangement

Also Published As

Publication number Publication date
US20170154004A1 (en) 2017-06-01
EP2782294B1 (fr) 2015-08-19
JP2014183337A (ja) 2014-09-29
US20140281103A1 (en) 2014-09-18
US9632962B2 (en) 2017-04-25
JP6011401B2 (ja) 2016-10-19

Similar Documents

Publication Publication Date Title
US11048560B2 (en) Replication management for expandable infrastructures
US10402293B2 (en) System for virtual machine risk monitoring
CN110865867B (zh) 应用拓扑关系发现的方法、装置和系统
US11093296B2 (en) System, virtualization control apparatus, method for controlling a virtualization control apparatus, and program
US20130107889A1 (en) Distributed Address Resolution Service for Virtualized Networks
US9311163B2 (en) Configuration data management system, and configuration data management method
US20140032753A1 (en) Computer system and node search method
US10728084B2 (en) Virtualized rack management modules
US11463379B2 (en) Information processing system, information processing apparatus, and non-transitory computer-readable recording medium storing therein information processing program
US11228490B1 (en) Storage management for configuration discovery data
JP2017090946A (ja) ログ情報採取システム、ログ情報採取プログラムおよびログ情報採取方法
EP2782294B1 (fr) Appareil de traitement d'informations et procédé pour générer des informations de couplage
JP2014182576A (ja) 構成管理装置と構成管理方法及び構成管理プログラム
US20160127231A1 (en) Information processing system, method, and management device
CN110049148B (zh) 一种Vcenter环境中虚拟机IP地址获取方法
US20120265860A1 (en) Sharing A Hosted Device In A Computer Network
US20150142960A1 (en) Information processing apparatus, information processing method and information processing system
JP2018018415A (ja) 情報処理装置、情報処理システム、プログラム及び情報処理方法
US20200235993A1 (en) Automatic network configuration in data protection operations
US9882796B2 (en) Apparatus and method for suppressing a delay in monitoring communication
US20230179657A1 (en) Storage management system and storage system management method
CN109756585B (zh) 识别新入网设备位置的方法和控制装置
US10417093B2 (en) Methods for providing global spare data storage device management and devices thereof
CN117061459A (zh) 流量采集规则的配置方法及其系统、存储介质
JP2015109047A (ja) 設定支援プログラム、設定支援装置および設定支援方法

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20140624

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 12/40 20060101AFI20150105BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20150305

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 744467

Country of ref document: AT

Kind code of ref document: T

Effective date: 20150915

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602014000141

Country of ref document: DE

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 3

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 744467

Country of ref document: AT

Kind code of ref document: T

Effective date: 20150819

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20150819

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151119

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151120

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151221

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151219

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602014000141

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160131

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20160520

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: LU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160115

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 4

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160115

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20161215

Year of fee payment: 4

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20170110

Year of fee payment: 4

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170131

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170131

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20171101

Year of fee payment: 5

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20140115

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160131

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602014000141

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180801

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150819

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180131

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20180928

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20190115

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190115