WO2012054023A1 - Système informatique comprenant des ordinateurs qui exécutent des amorçages réseau - Google Patents

Système informatique comprenant des ordinateurs qui exécutent des amorçages réseau Download PDF

Info

Publication number
WO2012054023A1
WO2012054023A1 PCT/US2010/053280 US2010053280W WO2012054023A1 WO 2012054023 A1 WO2012054023 A1 WO 2012054023A1 US 2010053280 W US2010053280 W US 2010053280W WO 2012054023 A1 WO2012054023 A1 WO 2012054023A1
Authority
WO
WIPO (PCT)
Prior art keywords
computer
client
server
network
network boot
Prior art date
Application number
PCT/US2010/053280
Other languages
English (en)
Inventor
John Michael Robinson
Marc Lecourieux
Philippe Auphelle
Ming Chen
Yves Gattegno
Original Assignee
Hewlett-Packard Development Company, L.P.
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 Hewlett-Packard Development Company, L.P. filed Critical Hewlett-Packard Development Company, L.P.
Priority to PCT/US2010/053280 priority Critical patent/WO2012054023A1/fr
Publication of WO2012054023A1 publication Critical patent/WO2012054023A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4416—Network booting; Remote initial program loading [RIPL]

Definitions

  • the present invention relates to computer systems with computers that perform network boots.
  • Computer networks can include hundreds or thousands of computers or workstations connected to the network. Determining which computers are on the network and managing these computers are time consuming tasks.
  • Figure 1 is a computer system that performs a network boot of client computers according to an example implementation.
  • Figure 2 is a flow diagram of a modified network boot sequence in which an inventory of a computer is performed during a network boot of the computer according to an example implementation.
  • Figure 3 is a flow diagram during a modified network boot sequence showing client and server side executions according to an example embodiment.
  • Figure 4 shows an administrator computer system for implementing example embodiments.
  • Example embodiments relate to apparatus and methods that perform an inventory of a computer using a pre-boot (non-operating system (OS))
  • OS non-operating system
  • the computer performs the inventory during a network boot of the computer.
  • Figure 1 is a system 100 that performs a network boot of client computers according to an example implementation.
  • the system includes a Preboot Execution Environment (PXE) server 1 10, and an administrator computer or server 130 coupled to a client computer or workstation 150 through a network 160. Multiple client computers 150 may be connected to the network 160 in one embodiment.
  • PXE server 1 10 can be a separate server (as shown in Figure 1 ) or included with a Dynamic Host Configuration Protocol (DHCP) server.
  • DHCP Dynamic Host Configuration Protocol
  • the client computer includes PXE boot code 155 so the client computer can execute a PXE network boot.
  • server is computer hardware and/or software that communicates with other electronic devices through a network.
  • preboot execution environment or “PXE” refers to various methods to boot a computer with a network interface without using a data storage device (such as a hard drive) or an installed operating system.
  • a data storage device such as a hard drive
  • DHCP Dynamic Host Configuration Protocol
  • IP network a configuration protocol on an IP network that configures computers on the network so the computers can communicate with each other. DHCP automatically configures the computers and tracks computers connected to the network to ensure each computer receives a different IP address.
  • the PXE server 1 10 sends the computer a boot loader that includes an operating system image from which the computer can boot.
  • Example embodiments use this network booting process to survey the computer, determine a configuration of the computer, and report this configuration to another server, such as the administrator computer 130.
  • the boot loader can either power-off the computer (for example, so the administrator computer can power the computer on again) or instruct the computer to reboot.
  • the computer can also remain on without a reboot (for example, if the computer is running virtualization software the computer may not need to reboot).
  • the administrator computer 130 uses the configuration information to discover the computer 150 on the network 160 and automatically generate characteristics and/or attributes for the computer. For example, a name of a computer may be generated from a prefix entered in the administrator computer 130 plus an index. The name may be based on a characteristic of the computer, such as a Media Access Control (MAC) address, an Internet Protocol (IP) address, or a subnet.
  • MAC Media Access Control
  • IP Internet Protocol
  • the term "Media Access Control" or "MAC" address is a unique identifier assigned to network interfaces for communicating on a network.
  • MAC addresses can be assigned by a manufacturer of a network interface card (NIC) and stored in the NIC card or other location.
  • NIC network interface card
  • the PXE server 1 10 sends the computer 150 an operating system (OS) boot image file.
  • OS operating system
  • PXE is not specific to an operating system, so the image file can load various kinds of operating systems.
  • PXE can be provided as a boot read only memory (ROM) chip on a Network Interface Card (NIC) or included in a system Basic Input/Output System (BIOS) if the network interface is on the motherboard of the computer.
  • ROM read only memory
  • NIC Network Interface Card
  • BIOS Basic Input/Output System
  • a client computer, personal computer, or network card can support PXE boot via the network card.
  • the BIOS transfers control to the PXE client, either in the boot ROM of the motherboard, or a boot ROM on a network card.
  • the PXE client checks with DHCP to see if there is a PXE environment available on the network, and the PXE client receives the IP address of a server (for example, a Trivial File Transfer Protocol (TFTP) server), and a filename on that server to retrieve.
  • the PXE client retrieves this file, and transfers control to it.
  • the file received then performs some tasks to set the computer up for a network boot, and continues with the boot process.
  • TFTP Trivial File Transfer Protocol
  • One example embodiment modifies the PXE network boot protocol to discover and inventory computers connected to the network.
  • a network bootable PXE computer is modified to not continue the PXE boot process. Instead, the process performs an inventory on the computer and reports parameters, configuration settings, and other information back to a server on the network.
  • Figure 2 is a flow diagram of a modified PXE network boot sequence in which an inventory of a computer is performed during a network boot of the computer according to an example implementation.
  • a PXE network boot of a computer commences.
  • the PXE network boot of the computer is discontinued (in other words, stopped) or interrupted before boot sequence is completed.
  • the process performs an inventory of the computer to collect information including, but not limited to, parameters, configuration settings, and other information (such as BIOS strings, codes, MAC address, and computer identifications).
  • the client computer transmits the collected information to a server on the network.
  • the client computer 150 sends the information to the administrator computer 130.
  • the information is sent from the client computer using a unicast User Datagram Protocol (UDP) frame.
  • UDP User Datagram Protocol
  • the term "User Datagram Protocol” or "UDP” is a network protocol used on the internet so computers can send messages to hosts on an IP network without requiring prior communications to establish a transmission channel or data path. UDP uses datagrams to send messages without a handshaking dialogue.
  • the server stores the collected information (for example, the information is stored in a database).
  • the server has a set of criteria or rules (for example, provided by administrator) that describe which client computers to control and which client computers to ignore.
  • these criteria can be a specific make and model of a client computer, which can be verified against the BIOS strings, or the criteria can be a particular hardware profile, which can be verified against the Peripheral Component Interconnect (PCI) vendor number.
  • PCI Peripheral Component Interconnect
  • the criteria can also include device code of the NIC, processor, or chipset, or any other machine readable information available on the computer.
  • the server After the client computer is identified as meeting the rules or criteria, then the server generates a unique machine name based upon the information received from the client computer. This name can be stored, transmitted, and/or displayed on a computer screen (for example, displayed on an administrator console so a user or administrator can view the name). The administrator can choose to keep or modify the name being proposed.
  • the MAC address of the client computer is added to a list and the list is stored. In the case of this being a client that the server wants to control (for example, the BIOS string or the PCI vendor number of the network card matched some predetermined criteria), the MAC address of the client computer is added to a "serviced" list.
  • the computer When the client computer reboots, the computer now receives the correct image for that client, rather than the "discovery" image. In the event that the client computer is not of interest (in other words, does not match the predetermined criteria), then the MAC address of the client computer is added to an "ignored" list. Now, when this client computer attempts a network PXE boot, the computer is ignored and allowed to boot from another PXE server on the network.
  • the client computer reboots or is shutdown. Hence, the PXE boot sequence did not complete.
  • An administrator can also decide what action is taken on client computers that meets the pre-determined criteria and client computers that are added to the ignore list (in other words, fail to meet the criteria). These actions include rebooting the computer or shutting down the computer. In the case of a reboot, this restarts the PXE network boot process. If the rebooting client computer previously met the criteria, then it should get the particular boot image destined for it. Alternatively, if the rebooting client did not meet the criteria, then the client is booted and serviced from another PXE server (in other words, a different PXE server that boots the client computers meeting the criteria).
  • Example embodiments can execute on a computer or electronic device equipped as a PXE network boot client.
  • Such devices include servers, desktop computers, laptops, or any other machine that is equipped with PXE boot code (for example, PXE boot code 155 shown in Figure 1 ).
  • PXE boot code for example, PXE boot code 155 shown in Figure 1
  • example embodiments can be implemented to manage existing computer systems that do not include additional hardware / firmware to handle the discovery process.
  • the computing device can be equipped with a plug-in network card, which can manage the PXE boot process.
  • Example embodiments cause minimal disruption to a computer network in order to discover and inventory computers on the network.
  • example embodiments recognize devices with PXE boot code and determine which of these clients to manage. Client computers that are not being managed may receive one extra reboot (but user intervention is not required to execute the discovery process). Further, a name for each machine is selected based on one or more characteristics of the machine, in line with a naming convention that is selected by an administrator.
  • an administrator computer uses the MAC address of the computer in order to identify and manage the computer. Gathering these addresses is can be time consuming and inconvenient. Downloading a bare machine executable simplifies this since it can report the MAC address back to the administrator computer.
  • Example embodiments enable an administrator to manage a selected group of client computers that meet certain criteria. For example, an administrator may desire to manage all personal computers with a particular model number, with a particular processor, at a specific geographical location, with particular installed hardware, etc. Thus, an administrator can tailor the criteria to a certain class of computers or computers having a certain profile (including hardware, firmware, or software installed on the computer). Furthermore, the administrator or
  • FIG. 3 is a flow diagram during a modified PXE network boot sequence showing client and server side executions according to an example embodiment.
  • the server waits for a network boot request, and the client computer powers on at block 305.
  • the client then sends the server a network boot request and its MAC address 308 at block 310.
  • a determination at block 315 is made as to whether the client is existing (for example, previously met pre-defined criteria). If the client is existing, then the server delivers an appropriate OS image 312 to the client at block 370. If the client is not existing, then at block 320 the server delivers a boot load 322 via TFTP and a client name 324 to the client. At block 325, the client executes a standard PXE boot to receive the boot loader 322.
  • a bootloader is a program that the client computer uses to execute a PXE network boot. The bootloader enables the client load boot images from the boot server and allows the client machines to boot these images.
  • the client performs a hardware inventory, and the bootloader reports collected information 332 (for example, hardware information) to the server.
  • the server compares the received information against a rule base to determine a match per block 335.
  • the server sends the client a name pre-fix 342 which is based on the collected hardware information.
  • the client then provisions the user for numeric suffix via a keyboard at block 345 and sends a full name 347 to the server.
  • the server provisions the client into a database and makes the client known (in other words, recognizable for subsequent reboots).
  • FIG. 4 shows an administrator computer system 400 for implementing example embodiments.
  • the computer system includes one or more storage devices, databases, or warehouses 410 coupled to an administrator computer 420.
  • the computer 420 includes memory 430, a management tool 440, a display 450, a processing unit 460, and one or more buses or
  • the processor unit includes a processor (such as a central processing unit, CPU, microprocessor, application-specific integrated circuit (ASIC), etc.) for controlling the overall operation of memory 430 (such as random access memory (RAM) for temporary data storage, read only memory (ROM) for permanent data storage, and firmware).
  • the processing unit 460 communicates with memory 430 and management tool 440 to perform
  • the memory 430 stores applications, data, programs, algorithms (including software to implement or assist in implementing example embodiments) and other data.
  • one or more blocks or steps discussed herein are automated. In other words, apparatus, systems, and methods occur automatically.
  • automated or “automatically” (and like variations thereof) mean controlled operation of an apparatus, system, and/or process using computers and/or mechanical/electrical devices without the necessity of human intervention, observation, effort and/or decision.
  • the storage media include different forms of memory including semiconductor memory devices such as DRAM, or SRAM, Erasable and Programmable Read-Only Memories (EPROMs), Electrically Erasable and Programmable Read-Only Memories (EEPROMs) and flash memories; magnetic disks such as fixed, floppy and removable disks; other magnetic media including tape; and optical media such as Compact Disks (CDs) or Digital Versatile Disks (DVDs).
  • semiconductor memory devices such as DRAM, or SRAM, Erasable and Programmable Read-Only Memories (EPROMs), Electrically Erasable and Programmable Read-Only Memories (EEPROMs) and flash memories
  • magnetic disks such as fixed, floppy and removable disks
  • other magnetic media including tape and optical media such as Compact Disks (CDs) or Digital Versatile Disks (DVDs).
  • CDs Compact Disks
  • DVDs Digital Versatile Disks
  • Example embodiments are implemented as a method, system, and/or apparatus. As one example, example embodiments and steps associated therewith are implemented as one or more computer software programs to implement the methods described herein.
  • the software is implemented as one or more modules (also referred to as code subroutines, or "objects" in object-oriented
  • the software programming code for example, is accessed by a processor or processors of the computer or server from long-term storage media of some type, such as a CD-ROM drive or hard drive.
  • the software programming code is embodied or stored on any of a variety of known physical and tangible media for use with a data processing system or in any memory device such as semiconductor, magnetic and optical devices, including a disk, hard drive, CD- ROM, ROM, etc.
  • the code is distributed on such media, or is distributed to users from the memory or storage of one computer system over a network of some type to other computer systems for use by users of such other systems.
  • the programming code is embodied in the memory and accessed by the processor using the bus.
  • the techniques and methods for embodying software programming code in memory, on physical media, and/or distributing software code via networks are well known and will not be further discussed herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

La présente invention se rapporte à un chargeur d'amorçage qui peut être fourni à un ordinateur en vue d'exécuter un amorçage réseau dans un système. L'amorçage réseau peut être suspendu, et l'ordinateur rapporte à un serveur des données relatives au matériel. Le serveur peut fournir un nom à l'ordinateur qui redémarre pour exécuter l'amorçage réseau.
PCT/US2010/053280 2010-10-20 2010-10-20 Système informatique comprenant des ordinateurs qui exécutent des amorçages réseau WO2012054023A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2010/053280 WO2012054023A1 (fr) 2010-10-20 2010-10-20 Système informatique comprenant des ordinateurs qui exécutent des amorçages réseau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2010/053280 WO2012054023A1 (fr) 2010-10-20 2010-10-20 Système informatique comprenant des ordinateurs qui exécutent des amorçages réseau

Publications (1)

Publication Number Publication Date
WO2012054023A1 true WO2012054023A1 (fr) 2012-04-26

Family

ID=45975506

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2010/053280 WO2012054023A1 (fr) 2010-10-20 2010-10-20 Système informatique comprenant des ordinateurs qui exécutent des amorçages réseau

Country Status (1)

Country Link
WO (1) WO2012054023A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104079434A (zh) * 2014-07-07 2014-10-01 用友软件股份有限公司 云计算系统中物理设备管理的装置及方法
CN113645046A (zh) * 2021-06-30 2021-11-12 浪潮电子信息产业股份有限公司 一种网卡驱动安装方法、主服务器及介质
CN114661367A (zh) * 2022-04-26 2022-06-24 苏州浪潮智能科技有限公司 一种IPv6环境的操作系统安装方法、装置、设备及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030200428A1 (en) * 2002-04-19 2003-10-23 Sen-Ta Chan Method and system for booting a client computer system over a network
US20070021434A1 (en) * 2005-06-24 2007-01-25 Migenix Inc. Non-nucleoside anti-hepacivirus agents and uses thereof
US20080140816A1 (en) * 2002-04-18 2008-06-12 Gintautas Burokas System for and method of network booting of an operating system to a client computer using hibernation

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080140816A1 (en) * 2002-04-18 2008-06-12 Gintautas Burokas System for and method of network booting of an operating system to a client computer using hibernation
US20030200428A1 (en) * 2002-04-19 2003-10-23 Sen-Ta Chan Method and system for booting a client computer system over a network
US20070021434A1 (en) * 2005-06-24 2007-01-25 Migenix Inc. Non-nucleoside anti-hepacivirus agents and uses thereof

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104079434A (zh) * 2014-07-07 2014-10-01 用友软件股份有限公司 云计算系统中物理设备管理的装置及方法
CN113645046A (zh) * 2021-06-30 2021-11-12 浪潮电子信息产业股份有限公司 一种网卡驱动安装方法、主服务器及介质
CN113645046B (zh) * 2021-06-30 2023-06-02 浪潮电子信息产业股份有限公司 一种网卡驱动安装方法、主服务器及介质
CN114661367A (zh) * 2022-04-26 2022-06-24 苏州浪潮智能科技有限公司 一种IPv6环境的操作系统安装方法、装置、设备及介质
CN114661367B (zh) * 2022-04-26 2023-08-04 苏州浪潮智能科技有限公司 一种IPv6环境的操作系统安装方法、装置、设备及介质

Similar Documents

Publication Publication Date Title
US10044795B2 (en) Methods and apparatus for rack deployments for virtual computing environments
US10177974B2 (en) Configuring managed server
JP5150593B2 (ja) ブート前環境におけるウェブサービスを利用したプラットフォーム検出
US8332490B2 (en) Method, apparatus and program product for provisioning a computer system
US7802084B2 (en) System and method for management and installation of operating system images for computers
US7953830B2 (en) Automatic network reconfiguration upon changes in DHCP IP addresses
CN106911729B (zh) 一种适用于国产处理器的操作系统远程安装方法
US20120239729A1 (en) Methods and apparatus for connecting a thin client to a virtual desktop
US20070118654A1 (en) Method and apparatus for provisioning heterogeneous operating systems onto heterogeneous hardware systems
CN112199197B (zh) 一种服务器管理方法及系统
CN110908753B (zh) 一种智能融合的云桌面服务器、客户端及系统
JP2013218687A (ja) サーバー監視システム及びその方法
US7949736B2 (en) Centralization configuration of data processing systems
US10924350B1 (en) Software sensor for reporting controller metrics
CN104850442A (zh) 一种操作系统安装方法及装置
US11349721B2 (en) Discovering switch port locations and internet protocol addresses of compute nodes
US10972350B2 (en) Asynchronous imaging of computing nodes
US20230229481A1 (en) Provisioning dpu management operating systems
CN114115917A (zh) 操作系统安装方法及装置
WO2012054023A1 (fr) Système informatique comprenant des ordinateurs qui exécutent des amorçages réseau
WO2020096845A1 (fr) Réalisation d'actions de manière opportuniste en conjonction avec des événement de réamorçage dans un système informatique en nuage
US20230325203A1 (en) Provisioning dpu management operating systems using host and dpu boot coordination
NL2007368C2 (en) Method and server for instructing configuration of a computer.
CN116775540A (zh) Pcie设备信息获取方法、装置、设备及存储介质
WO2023141069A1 (fr) Provisionnement de systèmes d'exploitation de gestion de dpu

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: 10858746

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10858746

Country of ref document: EP

Kind code of ref document: A1