Service management
US-2024334169-A1 · Oct 3, 2024 · US
US9912534B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9912534-B2 |
| Application number | US-201214232055-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 21, 2012 |
| Priority date | Jul 11, 2011 |
| Publication date | Mar 6, 2018 |
| Grant date | Mar 6, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A computer system includes a server computer including a processor, a main memory and a system management chip, a management station that manages server profiles and selects a server profile from server profiles and associates it with the server computer, and at least one data network via which the server computer and the management station are coupled to interchange data, wherein the system management chip of the server computer is set so that, when the system management chip activates, it sends an inquiry regarding a server profile associated by the management station to the management station, so that, if a management connection can be set to the management station, it configures a component of the server computer by using a network identifier transmitted by the management station, and to otherwise prevent starting of the server computer with a network identifier transmitted by the management station previously.
Opening claim text (preview).
The invention claimed is: 1. A method of starting a server computer comprising: activating a system management chip of the server computer, the server computer being a rack server; checking, by the system management chip, whether virtualization of the rack server is desired; if no virtualization is desired, booting the rack server using physical addresses stored in respective plug-in cards of the rack server; and if virtualization is desired, attempting to send, in a preboot phase, from the system management chip an inquiry over a data network, addressed to a management station independent of the rack server, regarding a server profile associated with the management station in order to request a virtual network identifier from the management station or to validate a virtual network identifier previously stored in a local memory of the rack server; ascertaining, in the preboot phase, whether a management connection has been set up to the management station; if the management connection has been set up successfully between the system management chip and the management station within a predetermined time period, configuring, in the preboot phase and before a power supply for at least one processor is activated, at least one network component of the rack server with a virtual network identifier transmitted by the management station, and starting the rack server; and if the management connection has not been set up successfully between the system management chip and the management station within the predetermined time period, preventing starting of the rack server with a virtual network identifier transmitted by the management station previously by remaining in the preboot phase or starting at least one server computer using the physical addresses stored in respective plug-in cards of the at least one server computer. 2. The method according to claim 1 , wherein the attempted sending and ascertainment are performed repeatedly in the preboot phase of the rack server until the management connection has been set up successfully. 3. The method according to claim 1 , further comprising: marking a virtual network identifier received from the management station previously as invalid if it is not possible for a management connection to be set up between the system management chip and the management station within the predetermined period. 4. The method according to claim 1 , wherein the system management chip configures at least one plugin card of the rack server by writing appropriate configuration data directly into suitable configuration registers of the at least one plug-in card via a system management bus of the rack server. 5. The method according to claim 1 , further comprising: storing a first address table for a plurality of server blades in a management blade, the plurality of server blades and management blade arranged in a shared blade chassis, each server blade comprising a first BIOS chip and at least one I/O adapter, and the first BIOS chip of each server blade is configured to retrieve associated address information for the at least one I/O adapter of the respective server blade from the first address table of the management blade; and storing in the system management chip a second address table, the at least one rack server comprises a second BIOS chip; and the second BIOS chip retrieves configuration data for the at least one plug-in card from the second address table. 6. The method according to claim 1 , wherein each one of the plurality of server profiles is associated with a separate application or a server service, comprising at least one of the following: a web server profile, a Microsoft Exchange Server profile and a database server profile. 7. A rack server comprising: at least one processor and a main memory coupled to the processor to process data; at least one network component that provides a data connection for the rack server; and a system management chip that manages the rack server via a management connection; wherein the system management chip is set up so that, when the system management chip is activated, the system management chip checks whether virtualization of the rack server is desired; if no virtualization is desired, the rack server is booted using physical addresses stored in respective plug-in cards of the rack server; and if virtualization is desired, the system management chip sends, in a preboot phase, at least one inquiry over a data network regarding a server profile associated with a management station in order to request a virtual network identifier from the management station or to validate a virtual network identifier previously stored in a local memory of the rack server; so that, if at least one management connection can be set up between the system management chip and the management station within a predetermined time period, the system management chip configures, in the preboot phase and before a power supply for the processor is activated, the at least one network component of the rack server with a virtual network identifier received from the management station; and to otherwise prevent starting of the rack server with a virtual network identifier received from the management station previously by remaining in the preboot phase or starting at least one server computer using physical addresses stored in respective plug-in cards of the at least one server computer. 8. The rack server according to claim 7 , wherein the rack server comprises at least one power supply unit to operate the rack server independently of the power supply of the management station. 9. The rack server according to claim 7 , further comprising at least one second network component to set up the management connection, wherein the first and second network components are independent of one another and the second network component has a second, physical network identifier. 10. The rack server according to claim 7 , wherein the system management chip configures at least one plugin card of the rack server by writing appropriate configuration data directly into suitable configuration registers of the at least one plug-in card via a system management bus of the rack server. 11. The rack server according to claim 7 , wherein each one of the plurality of server profiles is associated with a separate application or a server service, comprising at least one of the following: a web server profile, a Microsoft Exchange Server profile and a database server profile. 12. A computer system comprising: at least one blade chassis comprising a management blade and at least one server blade; at least one rack server arranged outside the at least one blade chassis and comprising at least one processor, a main memory, at least one plugin-card and a system management chip; a management station that manages a plurality of server profiles and selects at least one server profile from the plurality of server profiles and associates it selectively with the at least one server blade or the at least one rack server; and a data network via which the management blade of the at least one blade chassis, the at least one rack server and the management station are coupled to interchange data; wherein the system management chip of the at least one rack server is set up to perform the following steps: on activation, to send, in a preboot phase of the respective rack server, an inquiry over the data network requesting a server profile from the management station and to await a response from the management station; if a management connection can be set up between the system management chip and the management station within a predetermined time period, the system management
I/O management, e.g. providing access to device drivers or storage · CPC title
for initial configuration or provisioning, e.g. plug-and-play · CPC title
Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455) · CPC title
Hypervisors; Virtual machine monitors · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.