US7590727B1 - System and method for software failover on a bladed system - Google Patents
System and method for software failover on a bladed system Download PDFInfo
- Publication number
- US7590727B1 US7590727B1 US10/952,405 US95240504A US7590727B1 US 7590727 B1 US7590727 B1 US 7590727B1 US 95240504 A US95240504 A US 95240504A US 7590727 B1 US7590727 B1 US 7590727B1
- Authority
- US
- United States
- Prior art keywords
- bladed
- failover
- server
- application
- servers
- 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.)
- Active, expires
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
- G06F11/2033—Failover techniques switching over of hardware resources
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
- G06F11/2025—Failover techniques using centralised failover control functionality
Definitions
- the present disclosure relates to virtualization and network server technology. More specifically, but not by way of limitation, a method and a system are provided that permit more effective resource utilization of bladed network servers.
- IT Information technology
- Bladed systems are those in which individual servers are implemented as removable rack-mounted blades.
- a bladed system includes some combination of the following features: hot insertion and removal of blades, consolidation of cables, integrated system management software, and automated software deployment.
- Currently available blades may include one to four central processing units (“CPUs”) and a typical bladed server may hold in the range of 48 to 250 CPUs.
- a processing area network (“PAN”) architecture as exemplified by the bladed systems available from Egenera, Inc., is one approach used to design and implement bladed servers.
- a PAN architecture includes the components required to implement multiple servers on a single bladed system, i.e., the hardware, software, and network and I/O resources.
- a PAN architecture may include processing resources, integrated networking, centrally managed network and storage resources, management software, and operating system software. This architecture provides for high availability clustering with such features as load balancing and automatic hardware failover.
- Bladed systems comprising a PAN architecture also include functionality supporting automatic failover of software or applications.
- Application failover in this context requires a redundant, passive failover blade and the installation of the application software, operating system, and all required support software on at least two disks—one active and one passive.
- the dedicated, i.e., passive, boot disk is required to have the same configuration as the primary, i.e., active, boot disk. That is, the failover boot disk must have the identical version of the application installed along with the same operating system, support software, etc.
- a third disk is required to store any application data that persists between executions of the application.
- This failover implementation also requires three internet protocol (“IP”) addresses, one for the primary blade, one for the failover blade, and a floating IP address that moves with the application.
- IP internet protocol
- the PAN management software monitors the application as it executes on the active blade. If that application fails, the PAN management software activates the application on the passive blade using the passive disk.
- a system for managing software failover on a bladed system includes a plurality of bladed servers, including a first bladed server and a second failover bladed server.
- the system includes a server control, a storage device, and software.
- the server control is in communication with the plurality of bladed servers, and the storage device is accessible by the plurality of bladed servers.
- the software is stored on the storage device.
- the system also includes a management component that is operable on the server control.
- the management component monitors execution of the software on the first bladed server.
- the management component is operable in response to detecting failure of the software on the first bladed server to promote execution of the software from the external storage device by the second failover bladed server.
- a method for automated application failover on a bladed server includes providing a plurality of bladed servers, and storing an application on a storage device accessible by at least some of the plurality of blades.
- the method includes executing the application on a first bladed server of the bladed server from the storage device.
- the method provides for monitoring the application during execution, and detecting failure of the application.
- the method also includes executing the application on a failover bladed server from the storage device.
- a system in another embodiment, includes a plurality of bladed servers, and a storage device that is sharable by the plurality of bladed servers.
- the system includes software that is stored on the storage device, and a component that is operable to monitor execution of the software on a first bladed server of the plurality of bladed servers.
- the component is also operable in response to detecting failure of the software on the first bladed server to promote execution of the software from the storage device by a second bladed server of the plurality of bladed servers.
- FIG. 1 shows a bladed system with multiple bladed servers according to one embodiment of the present disclosure.
- FIGS. 2A and 2B illustrate application failover in accordance with another embodiment of the present disclosure.
- Embodiments of the present disclosure provide a system and method for improving application failover on a bladed server. More specifically, a bladed server with a PAN architecture is provided that includes the ability to perform application failover without requiring additional application licenses, disks, and IP addresses. According to one embodiment, the bladed server is diskless and stateless.
- application and/or “software” as used herein includes, but is not limited to, any software, application, operating system or other computer program(s) or instructions, or combinations thereof. For example, monitoring an application or software for failure may include monitoring one or more computer programs, the operating system whereon the user computer program(s) operate, or both.
- FIG. 1 shows a bladed system 100 which may be configured in a PAN architecture in accordance with one embodiment.
- Embodiments of the bladed system 100 may be comprised of the Egenera® BladeFrame® or the Egenera® BladeFrame® ES available from Egenera, Inc.
- Egenera and BladeFrame are registered trademarks of Egenera, Inc.
- Elements of this disclosure may include features and functionality of these bladed systems or servers, additional descriptions of which may be found in Egenera's White Papers entitled “Improving Datacenter Performance” and “The Egenera Processing Area Network (PAN) Architecture” available at www.egenera.com.
- the bladed system 100 comprises multiple bladed servers 101 a - 101 n in a redundant network using an integrated high-speed switch (not shown) connected to external storage 102 and a network 104 through redundant interconnections 106 and 108 .
- the external storage 102 may be implemented as a storage area network (“SAN”), network-attached storage (“NAS”), or a combination of the two.
- the hardware components of the PAN bladed system 100 may be housed in a chassis (not shown) that provides the infrastructure for administrators to configure and run the bladed servers 101 a - 101 n , 110 , and 112 .
- This chassis contains a backplane (not shown) that provides the physical connectivity for the I/O among the bladed servers 101 a - 101 n and for network communication.
- the backplane includes two redundant serial buses. These serial buses connect the bladed servers 101 a - 101 n , 110 , and 112 and provide the physical internal network of the bladed system 100 .
- the two switched-fabric interconnects 106 and 108 provide secure, point-to-point data transfer between the bladed servers 101 a - 101 n , 110 , and 112 .
- the two server controls 110 and 112 perform all actual I/O for the bladed system 100 .
- Each server control 110 and 112 is connected by two host bus adapters to the storage area network 102 that contains all disk partitions available to the bladed system 100 , and by two network interface cards to the external network 104 .
- the server controls 110 and 112 include functionality to perform the switching of both external and internal network traffic and to support the dynamic creation of connections between the bladed servers 101 a - 101 n .
- the server controls 110 and 112 may also include a DVD drive, a local hard disk drive, a serial port, and an Ethernet port.
- the server controls 110 and 112 share the processing of external traffic with one handling inbound traffic and the other handling outbound traffic—allowing the bladed system 100 to use the processing power of both simultaneously.
- the functionality of the two server controls 110 and 112 is completely redundant, allowing the bladed system 100 to continue operation on a single server control if one should fail.
- the server controls 110 and 112 may also execute PAN management software and contain functionality to continuously monitor system health at both the hardware and application levels, and initiate hardware or application failover when needed.
- two redundant switching blades are included in the bladed system 100 to provide the physical switching layer of the point-to-point architecture of the bladed system 100 for both internal and external I/O and network traffic rather than housing this functionality in the server controls 110 and 112 .
- the bladed servers 101 a - 101 n and the server controls 110 and 112 each include two redundant switching blade host adapters for connecting to the switching blades and individually connect to each switching blade via the backplane. If a host adapter or switching blade fails and a bladed server loses its connectivity to a specific switching blade, that bladed server sends all network and I/O traffic to the other switching blade.
- the drivers in the switching blades may conform to the Virtual Interface Architecture (VIA) industry standard.
- the switching blades are implemented with a shared memory architecture that permits dynamic routing and non-blocking performance and include functionality for load balancing incoming and outgoing I/O and network traffic.
- the bladed servers 101 a - 101 n operate as conventional servers once they are configured with virtual links to external storage 102 and the network 104 .
- the bladed servers 101 a - 101 n contain one or more processors, memory, and two network connections, one to each of the server controls 110 and 112 .
- the operating system on each bladed server 101 a - 101 n simulates the availability of hardware such as disk drives and Ethernet cards by interfacing with the I/O server functionality provided on the two server controls 110 and 112 .
- the bladed system 100 includes PAN management software that executes on the server controls 110 and 112 .
- the PAN management software includes functionality allowing an administrator to create virtual servers that comprise all the functionality of conventional servers. To create a virtual server, an administrator defines the processing capacity for an application, and then associates that capacity with storage available in the external storage 102 and with network resources 104 .
- the PAN management software also includes functionality permitting an administrator to remotely monitor and control virtual servers using either a command line interface or a browser-based graphical user interface.
- the PAN bladed system 100 includes a virtual I/O feature that provides all I/O for data storage in the external storage 102 , network accesses, and inter-node access for the bladed servers 101 a - 101 n .
- This virtual I/O architecture provides an I/O channel that works with any Fibre Channel-based storage system.
- this virtual I/O feature enables functionality in the PAN management software for creating logical connections that can be shared among clustered virtual servers, and for high speed mapping of these connections to failover bladed servers.
- the PAN management software provides provisioning functionality allowing administrators to network virtual servers without configuring the hardware and other physical resources.
- the basic components of the network of virtual servers are virtual Ethernet interfaces and virtual switches.
- a virtual Ethernet interface implements all the functionality of a physical network interface card for a virtual server and a virtual switch implements all the functionality of a physical switch for a virtual server.
- These virtual components provide communication channels to other virtual servers and to external networks that are secure, private, and redundant.
- the PAN management software contains functionality permitting administrators to configure virtual Ethernet interfaces that are similar to the way physical network interfaces are configured. Using the PAN management software, an administrator can create multiple virtual Ethernet interfaces on a single virtual server, add and reconfigure virtual Ethernet interfaces on executing virtual servers without rebooting, and place a virtual server in a network without stopping any services executing on that virtual server.
- the PAN management software also contains functionality allowing an administrator to configure virtual server connections by assigning a virtual Ethernet interface of a virtual server to a virtual switch.
- the PAN management software creates and manages the connections once the assignment is made.
- a virtual server connected to a virtual switch and a virtual Ethernet interface follows the same connectivity and availability rules as a conventional server connected to a conventional switch through a convention Ethernet interface.
- the virtual switches are designed to never run out of ports.
- an administrator can add or remove assignments of virtual Ethernet interfaces to virtual switches without reconfiguring the virtual switches or rebooting the affected virtual servers.
- the architecture of the PAN bladed system 100 allows administrators to create logical processing area networks (“LPANs”).
- An LPAN includes virtual servers and other virtualized network and storage components that are logically separated from resources not included in the LPAN. While the majority of the resources in an LPAN are used exclusively within an LPAN, some resources, e.g., virtual switches and failover bladed servers, may be shared by virtual servers in other LPANs.
- the PAN management software includes functionality permitting virtual servers to be dynamically moved among LPANS, clusters and services.
- the PAN management software provides system monitoring functionality allowing an administrator to monitor the processing requirements of applications and to reallocate processing capacity while the bladed system 100 is running.
- the PAN management software also includes functionality that can be configured to reallocate processing capacity automatically at specific times based on historical usage patterns.
- the architecture of the PAN bladed system 100 is designed for high availability computing.
- the combination of the system design and failover functionality implemented in the PAN management software provides both automatic hardware failover and automatic application failover.
- This architecture provides for N+1 failover, i.e., a single bladed server can be designated as the failover target for any and/or all other bladed servers in the bladed system 100 .
- the PAN management software includes a failover framework for specifying and managing failover policies and for monitoring the system for hardware and application failures.
- the failover framework includes functionality allowing an administrator to designate a specific failover bladed server or a pool of failover bladed servers for each virtual server.
- Two types of pools are supported: a global pool in which the designated failover bladed servers are available as failover targets for all bladed servers in the system; and a local pool in which the designated failover bladed servers are exclusively available to one LPAN.
- This pooling capability allows administrators flexibility in matching failover requirements with processing resources. For example, an administrator can create a local pool of two failover bladed servers to provide failover for five virtual servers in an LPAN, rather than assign a failover bladed server to each virtual server.
- the PAN management software determines that a virtual server has failed due to failure of a bladed server assigned to that virtual server, the PAN management software automatically remaps all disk, networking and switch connections assigned to the virtual server to a failover bladed server designated for that virtual server.
- the failover bladed server is then booted. During the boot process, the virtual server and the application(s) that were executing on that virtual server are restarted.
- the failover framework contains additional functionality to manage application failover in a manner similar to bladed server failover. This additional functionality allows an administrator to define a set of highly available application services and to place these services under start/stop control of the PAN management software.
- the failover framework causes application health monitoring software to be executed on the bladed servers assigned to each of the virtual servers running applications designated as requiring high availability. This application health monitoring software notifies the failover framework if the application it is monitoring fails.
- the failover framework determines that a monitored application has failed, the framework shuts down the virtual server and the bladed server that was executing the failed application, remaps all disk, networking and switch connections assigned to the virtual server to a failover bladed server designated for the virtual server, and boots the failover bladed server. During the boot process, the virtual server and the application are restarted.
- FIGS. 2A and 2B illustrate application failover on a bladed server with a PAN architecture in accordance with another embodiment.
- FIG. 2A illustrates the state of the system before an application fails and
- FIG. 2B illustrates the system after application failover is performed.
- an application 204 is executing on a virtual server that comprises a bladed server 200 , a disk 208 in a storage area network, and a network connection with the IP address 1.1.1.1.
- the disk 208 contains the installed executable code of the application 204 , boot scripts, and any state data maintained as the application executes.
- the application 204 has been designated as a highly available application so application health monitoring software 206 is executing on bladed server 200 to monitor the state of the application 204 .
- Bladed server 202 has been designated as the failover blade for the virtual server executing on bladed server 200 . Bladed server 202 is idle and has no disk or network resources assigned to it.
- FIG. 2B the application 204 has been failed over to bladed server 202 .
- Bladed server 200 has been shut down and the disk 208 and the IP address originally configured with process blade 200 are now configured with bladed server 202 .
- the bladed server 202 has been booted using the boot sequence stored on the disk 208 and the application 204 has been restarted during the boot sequence.
- the application 204 is executing on bladed server 202 with the identical storage and network resources it was using prior to failing on bladed server 200 .
- the application health monitoring software 206 has been moved to bladed server 202 and continues to monitor the state of the application.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Hardware Redundancy (AREA)
Abstract
Description
Claims (18)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/952,405 US7590727B1 (en) | 2004-09-28 | 2004-09-28 | System and method for software failover on a bladed system |
US12/501,198 US8250166B1 (en) | 2004-09-28 | 2009-07-10 | System and method for software failover on a bladed system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/952,405 US7590727B1 (en) | 2004-09-28 | 2004-09-28 | System and method for software failover on a bladed system |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/501,198 Continuation US8250166B1 (en) | 2004-09-28 | 2009-07-10 | System and method for software failover on a bladed system |
Publications (1)
Publication Number | Publication Date |
---|---|
US7590727B1 true US7590727B1 (en) | 2009-09-15 |
Family
ID=41058908
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/952,405 Active 2027-11-12 US7590727B1 (en) | 2004-09-28 | 2004-09-28 | System and method for software failover on a bladed system |
US12/501,198 Expired - Lifetime US8250166B1 (en) | 2004-09-28 | 2009-07-10 | System and method for software failover on a bladed system |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/501,198 Expired - Lifetime US8250166B1 (en) | 2004-09-28 | 2009-07-10 | System and method for software failover on a bladed system |
Country Status (1)
Country | Link |
---|---|
US (2) | US7590727B1 (en) |
Cited By (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060248199A1 (en) * | 2005-04-29 | 2006-11-02 | Georgi Stanev | Shared closure persistence of session state information |
US20060248036A1 (en) * | 2005-04-29 | 2006-11-02 | Georgi Stanev | Internal persistence of session state information |
US20060248200A1 (en) * | 2005-04-29 | 2006-11-02 | Georgi Stanev | Shared memory implementations for session data within a multi-tiered enterprise network |
US20060248283A1 (en) * | 2005-04-29 | 2006-11-02 | Galin Galchev | System and method for monitoring threads in a clustered server architecture |
US20060248119A1 (en) * | 2005-04-29 | 2006-11-02 | Georgi Stanev | External persistence of session state information |
US20090006684A1 (en) * | 2005-12-20 | 2009-01-01 | Georgy Martsinovsky | Backplane |
US20090077413A1 (en) * | 2007-09-17 | 2009-03-19 | International Business Machines Corporation | Apparatus, system, and method for server failover to standby server during broadcast storm or denial-of-service attack |
US20090100142A1 (en) * | 2007-10-15 | 2009-04-16 | International Business Machines Corporation | System and method for interruption management |
US20090119600A1 (en) * | 2007-11-02 | 2009-05-07 | International Business Machines Corporation | System and method for evaluating response patterns |
US20090217082A1 (en) * | 2006-04-21 | 2009-08-27 | Hitachi, Ltd. | Method of Achieving High Reliablility of Network Boot Computer System |
US20090265493A1 (en) * | 2008-04-16 | 2009-10-22 | Mendu Krishna R | Efficient Architecture for Interfacing Redundant Devices to a Distributed Control System |
US20100011139A1 (en) * | 2006-09-25 | 2010-01-14 | Ju Wang | Network apparatus and method for communication between different components |
US20100180025A1 (en) * | 2009-01-14 | 2010-07-15 | International Business Machines Corporation | Dynamic load balancing between chassis in a blade center |
US20110055622A1 (en) * | 2009-09-02 | 2011-03-03 | Masaya Arai | Network system and network relay apparatus |
US20110060824A1 (en) * | 2007-12-17 | 2011-03-10 | Johan Lundstrom | Signalling Proxy System for a Switching Center Server |
US20110087799A1 (en) * | 2009-10-09 | 2011-04-14 | Padhye Jitendra D | Flyways in Data Centers |
US8024566B2 (en) | 2005-04-29 | 2011-09-20 | Sap Ag | Persistent storage implementations for session data within a multi-tiered enterprise network |
US20110289304A1 (en) * | 2010-05-20 | 2011-11-24 | John Peters | Systems, methods, and computer program products for configuring network settings |
US20120102135A1 (en) * | 2010-10-22 | 2012-04-26 | Netapp, Inc. | Seamless takeover of a stateful protocol session in a virtual machine environment |
US8250166B1 (en) | 2004-09-28 | 2012-08-21 | Sprint Communications Company L.P. | System and method for software failover on a bladed system |
US20130173810A1 (en) * | 2011-12-30 | 2013-07-04 | Dell Products, Lp | System and Method of Enabling a Multi-Chassis Virtual Switch for Virtual Server Network Provisioning |
JP2013164763A (en) * | 2012-02-13 | 2013-08-22 | Mitsubishi Electric Corp | Duplex system switching controller |
US8589562B2 (en) | 2005-04-29 | 2013-11-19 | Sap Ag | Flexible failover configuration |
US8707323B2 (en) | 2005-12-30 | 2014-04-22 | Sap Ag | Load balancing algorithm for servicing client requests |
US8799359B2 (en) | 2004-12-28 | 2014-08-05 | Sap Ag | Session management within a multi-tiered enterprise network |
US20140297180A1 (en) * | 2011-11-15 | 2014-10-02 | John Minjae Cho | Mobilized Sensor System |
US20140317247A1 (en) * | 2011-07-11 | 2014-10-23 | Fujitsu Technology Solutions Intellectual Property Gmbh | Computer system, method for starting a server computer, server computer, management station, and use |
US9391716B2 (en) | 2010-04-05 | 2016-07-12 | Microsoft Technology Licensing, Llc | Data center using wireless communication |
US9497039B2 (en) | 2009-05-28 | 2016-11-15 | Microsoft Technology Licensing, Llc | Agile data center network architecture |
US9954751B2 (en) | 2015-05-29 | 2018-04-24 | Microsoft Technology Licensing, Llc | Measuring performance of a network using mirrored probe packets |
US20200104204A1 (en) * | 2018-09-28 | 2020-04-02 | Nxp Usa, Inc. | Fault detection circuit with progress register and status register |
US11966350B2 (en) * | 2018-02-05 | 2024-04-23 | Cisco Technology, Inc. | Configurable storage server with multiple sockets |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20120062174A (en) * | 2010-12-06 | 2012-06-14 | 한국전자통신연구원 | Apparatus and method for dynamic processing a variety of characteristics packet |
US9229825B2 (en) * | 2013-06-28 | 2016-01-05 | International Business Machines Corporation | Quick failover of blade server |
IL242353B (en) * | 2015-10-29 | 2021-01-31 | Verint Systems Ltd | System and method for soft failovers for proxy servers |
US10613906B2 (en) * | 2017-11-17 | 2020-04-07 | International Business Machines Corporation | Shared hardware and software resource replacement |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040078711A1 (en) * | 2001-08-10 | 2004-04-22 | King James E. | Computer system monitoring |
US20040109406A1 (en) * | 2002-12-08 | 2004-06-10 | Rothman Michael A. | Facilitating communications with clustered servers |
US20040111559A1 (en) * | 2002-12-10 | 2004-06-10 | Thomas Heil | Apparatus and method for sharing boot volume among server blades |
US20050257213A1 (en) * | 2004-05-14 | 2005-11-17 | International Business Machines Corporation | Management module failover across multiple blade center chassis |
US20070168476A1 (en) * | 2003-04-23 | 2007-07-19 | Dot Hill Systems Corporation | Network storage appliance with integrated redundant servers and storage controllers |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8165155B2 (en) * | 2004-07-01 | 2012-04-24 | Broadcom Corporation | Method and system for a thin client and blade architecture |
US6865157B1 (en) * | 2000-05-26 | 2005-03-08 | Emc Corporation | Fault tolerant shared system resource with communications passthrough providing high availability communications |
US7139809B2 (en) * | 2001-11-21 | 2006-11-21 | Clearcube Technology, Inc. | System and method for providing virtual network attached storage using excess distributed storage capacity |
JP2007510198A (en) * | 2003-10-08 | 2007-04-19 | ユニシス コーポレーション | Paravirtualization of computer systems using hypervisors implemented in host system partitions |
US7590727B1 (en) | 2004-09-28 | 2009-09-15 | Sprint Communications Company L.P. | System and method for software failover on a bladed system |
-
2004
- 2004-09-28 US US10/952,405 patent/US7590727B1/en active Active
-
2009
- 2009-07-10 US US12/501,198 patent/US8250166B1/en not_active Expired - Lifetime
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040078711A1 (en) * | 2001-08-10 | 2004-04-22 | King James E. | Computer system monitoring |
US20040109406A1 (en) * | 2002-12-08 | 2004-06-10 | Rothman Michael A. | Facilitating communications with clustered servers |
US20040111559A1 (en) * | 2002-12-10 | 2004-06-10 | Thomas Heil | Apparatus and method for sharing boot volume among server blades |
US20070168476A1 (en) * | 2003-04-23 | 2007-07-19 | Dot Hill Systems Corporation | Network storage appliance with integrated redundant servers and storage controllers |
US20050257213A1 (en) * | 2004-05-14 | 2005-11-17 | International Business Machines Corporation | Management module failover across multiple blade center chassis |
Non-Patent Citations (9)
Title |
---|
"Egenera, Inc. Announces Commercial Availability of BladeFrame Release 1.1," Supercomputing Online.com, http://supercomputingonline.com/print-php?sid=702, Sep. 24, 2004, 5 pgs. |
Egenera, "Advantages of Running Oracle9i Database with Real Application Clusters on the Egenera BladeFrame," White Paper, 2002, 6 pgs. |
Egenera, "BladeFrame: Utility Computing through Datacenter Virtualization," 2001, 12 pgs. |
Egenera, "Emerging Server Architectures," White Paper, 2001, 13 pgs. |
Egenera, "Improving Datacenter Performance," White Paper, 2001, 19 pgs. |
Egenera, "The Egenera Processing Area Network (PAN) Architecture," White Paper, 2002, 21 pgs. |
Gartner, Inc., "Egenera BladeFrame System" Product Report, Apr. 1, 2004, 10 pgs. |
Intel, Corp., Egenera, "Modular Computing: The New Model Enterprise Computing Model," White Paper, Cross Industry, 2003, 12 pgs. |
Sybase, "Adaptive Server Enterprise on Egenera BladeFrame Platform," White Paper, Jan. 2003, 10 pgs. |
Cited By (58)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8250166B1 (en) | 2004-09-28 | 2012-08-21 | Sprint Communications Company L.P. | System and method for software failover on a bladed system |
US8799359B2 (en) | 2004-12-28 | 2014-08-05 | Sap Ag | Session management within a multi-tiered enterprise network |
US8762547B2 (en) | 2005-04-29 | 2014-06-24 | Sap Ag | Shared memory implementations for session data within a multi-tiered enterprise network |
US20060248200A1 (en) * | 2005-04-29 | 2006-11-02 | Georgi Stanev | Shared memory implementations for session data within a multi-tiered enterprise network |
US20060248119A1 (en) * | 2005-04-29 | 2006-11-02 | Georgi Stanev | External persistence of session state information |
US7853698B2 (en) | 2005-04-29 | 2010-12-14 | Sap Ag | Internal persistence of session state information |
US8589562B2 (en) | 2005-04-29 | 2013-11-19 | Sap Ag | Flexible failover configuration |
US7761435B2 (en) | 2005-04-29 | 2010-07-20 | Sap Ag | External persistence of session state information |
US9432240B2 (en) | 2005-04-29 | 2016-08-30 | Sap Se | Flexible failover configuration |
US20060248283A1 (en) * | 2005-04-29 | 2006-11-02 | Galin Galchev | System and method for monitoring threads in a clustered server architecture |
US20060248036A1 (en) * | 2005-04-29 | 2006-11-02 | Georgi Stanev | Internal persistence of session state information |
US20060248199A1 (en) * | 2005-04-29 | 2006-11-02 | Georgi Stanev | Shared closure persistence of session state information |
US8024566B2 (en) | 2005-04-29 | 2011-09-20 | Sap Ag | Persistent storage implementations for session data within a multi-tiered enterprise network |
US7987388B2 (en) * | 2005-12-20 | 2011-07-26 | Siemens Aktiengesellschaft | Backplane |
US20090006684A1 (en) * | 2005-12-20 | 2009-01-01 | Georgy Martsinovsky | Backplane |
US8707323B2 (en) | 2005-12-30 | 2014-04-22 | Sap Ag | Load balancing algorithm for servicing client requests |
US20090217082A1 (en) * | 2006-04-21 | 2009-08-27 | Hitachi, Ltd. | Method of Achieving High Reliablility of Network Boot Computer System |
US20110060941A1 (en) * | 2006-04-21 | 2011-03-10 | Hitachi, Ltd. | Method of Achieving High Reliability of Network Boot Computer System |
US8407514B2 (en) | 2006-04-21 | 2013-03-26 | Hitachi, Ltd. | Method of achieving high reliability of network boot computer system |
US7966515B2 (en) | 2006-04-21 | 2011-06-21 | Hitachi, Ltd. | Method of achieving high reliability of network boot computer system |
US7840835B2 (en) * | 2006-04-21 | 2010-11-23 | Hitachi, Ltd. | Method of achieving high reliability of network boot computer system |
US20110225449A1 (en) * | 2006-04-21 | 2011-09-15 | Hitachi, Ltd. | Method of Achieving High Reliability of Network Boot Computer System |
US20100011139A1 (en) * | 2006-09-25 | 2010-01-14 | Ju Wang | Network apparatus and method for communication between different components |
US9602391B2 (en) | 2006-09-25 | 2017-03-21 | Hewlett Packard Enterprise Development Lp | Network apparatus and method for communication between different components |
US9083565B2 (en) * | 2006-09-25 | 2015-07-14 | Hangzhou H3C Technologies Co., Ltd. | Network apparatus and method for communication between different components |
US20090077413A1 (en) * | 2007-09-17 | 2009-03-19 | International Business Machines Corporation | Apparatus, system, and method for server failover to standby server during broadcast storm or denial-of-service attack |
US8683033B2 (en) * | 2007-09-17 | 2014-03-25 | International Business Machines Corporation | Apparatus, system, and method for server failover to standby server during broadcast storm or denial-of-service attack |
US8635278B2 (en) * | 2007-10-15 | 2014-01-21 | International Business Machines Corporation | System and method for interruption management |
US20090100142A1 (en) * | 2007-10-15 | 2009-04-16 | International Business Machines Corporation | System and method for interruption management |
US20090119600A1 (en) * | 2007-11-02 | 2009-05-07 | International Business Machines Corporation | System and method for evaluating response patterns |
US9167452B2 (en) * | 2007-12-17 | 2015-10-20 | Optis Wireless Technology, Llc | Signalling proxy system for a switching center server, wherein an indication of operation in an active state is transmitted from a signaling proxy via at least one processing blade to the remaining signaling proxies |
US20110060824A1 (en) * | 2007-12-17 | 2011-03-10 | Johan Lundstrom | Signalling Proxy System for a Switching Center Server |
US20090265493A1 (en) * | 2008-04-16 | 2009-10-22 | Mendu Krishna R | Efficient Architecture for Interfacing Redundant Devices to a Distributed Control System |
US7877625B2 (en) * | 2008-04-16 | 2011-01-25 | Invensys Systems, Inc. | Efficient architecture for interfacing redundant devices to a distributed control system |
US20110099416A1 (en) * | 2008-04-16 | 2011-04-28 | Mendu Krishna R | Efficient Architecture for Interfacing Redundant Devices to a Distributed Control System |
US8516296B2 (en) | 2008-04-16 | 2013-08-20 | Invensys Systems, Inc. | Efficient architecture for interfacing redundant devices to a distributed control system |
US8108503B2 (en) * | 2009-01-14 | 2012-01-31 | International Business Machines Corporation | Dynamic load balancing between chassis in a blade center |
US20100180025A1 (en) * | 2009-01-14 | 2010-07-15 | International Business Machines Corporation | Dynamic load balancing between chassis in a blade center |
US9497039B2 (en) | 2009-05-28 | 2016-11-15 | Microsoft Technology Licensing, Llc | Agile data center network architecture |
US8489913B2 (en) * | 2009-09-02 | 2013-07-16 | Alaxala Networks Corporation | Network system and network relay apparatus |
US20110055622A1 (en) * | 2009-09-02 | 2011-03-03 | Masaya Arai | Network system and network relay apparatus |
US8972601B2 (en) * | 2009-10-09 | 2015-03-03 | Microsoft Technology Licensing, Llc | Flyways in data centers |
US20110087799A1 (en) * | 2009-10-09 | 2011-04-14 | Padhye Jitendra D | Flyways in Data Centers |
US10110504B2 (en) | 2010-04-05 | 2018-10-23 | Microsoft Technology Licensing, Llc | Computing units using directional wireless communication |
US9391716B2 (en) | 2010-04-05 | 2016-07-12 | Microsoft Technology Licensing, Llc | Data center using wireless communication |
US20110289304A1 (en) * | 2010-05-20 | 2011-11-24 | John Peters | Systems, methods, and computer program products for configuring network settings |
US20120102135A1 (en) * | 2010-10-22 | 2012-04-26 | Netapp, Inc. | Seamless takeover of a stateful protocol session in a virtual machine environment |
US9600315B2 (en) * | 2010-10-22 | 2017-03-21 | Netapp, Inc. | Seamless takeover of a stateful protocol session in a virtual machine environment |
US20140317247A1 (en) * | 2011-07-11 | 2014-10-23 | Fujitsu Technology Solutions Intellectual Property Gmbh | Computer system, method for starting a server computer, server computer, management station, and use |
US9912534B2 (en) * | 2011-07-11 | 2018-03-06 | Fujitsu Limited | Computer system, method for starting a server computer, server computer, management station, and use |
US20140297180A1 (en) * | 2011-11-15 | 2014-10-02 | John Minjae Cho | Mobilized Sensor System |
US9935901B2 (en) * | 2011-12-30 | 2018-04-03 | Dell Products, Lp | System and method of enabling a multi-chassis virtual switch for virtual server network provisioning |
US20130173810A1 (en) * | 2011-12-30 | 2013-07-04 | Dell Products, Lp | System and Method of Enabling a Multi-Chassis Virtual Switch for Virtual Server Network Provisioning |
JP2013164763A (en) * | 2012-02-13 | 2013-08-22 | Mitsubishi Electric Corp | Duplex system switching controller |
US9954751B2 (en) | 2015-05-29 | 2018-04-24 | Microsoft Technology Licensing, Llc | Measuring performance of a network using mirrored probe packets |
US11966350B2 (en) * | 2018-02-05 | 2024-04-23 | Cisco Technology, Inc. | Configurable storage server with multiple sockets |
US20200104204A1 (en) * | 2018-09-28 | 2020-04-02 | Nxp Usa, Inc. | Fault detection circuit with progress register and status register |
US10831578B2 (en) * | 2018-09-28 | 2020-11-10 | Nxp Usa, Inc. | Fault detection circuit with progress register and status register |
Also Published As
Publication number | Publication date |
---|---|
US8250166B1 (en) | 2012-08-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8250166B1 (en) | System and method for software failover on a bladed system | |
US11106456B2 (en) | Live updates for virtual machine monitor | |
US11218364B2 (en) | Network-accessible computing service for micro virtual machines | |
JP5222651B2 (en) | Virtual computer system and control method of virtual computer system | |
EP1920345B1 (en) | Virtual data center for network resource management | |
US7984108B2 (en) | Computer system para-virtualization using a hypervisor that is implemented in a partition of the host system | |
US10599458B2 (en) | Fabric computing system having an embedded software defined network | |
US8683172B2 (en) | Method and apparatus for management between virtualized machines and virtualized storage systems | |
US8914546B2 (en) | Control method for virtual machine and management computer | |
US8918512B2 (en) | Managing a workload of a plurality of virtual servers of a computing environment | |
US8327372B1 (en) | Virtualization and server imaging system for allocation of computer hardware and software | |
US9600309B2 (en) | SR-IOV failover and aggregation control system to ensure within-physical-port VEB loopback | |
US8984115B2 (en) | Ensemble having one or more computing systems and a controller thereof | |
US20070061441A1 (en) | Para-virtualized computer system with I/0 server partitions that map physical host hardware for access by guest partitions | |
US20070067366A1 (en) | Scalable partition memory mapping system | |
US20170277573A1 (en) | Multifunction option virtualization for single root i/o virtualization | |
US11805102B2 (en) | Remote management of software on private networks | |
US10965616B2 (en) | Nonstop computing fabric arrangements | |
US20040047299A1 (en) | Diskless operating system management | |
Mayer et al. | Unified resource manager virtualization management |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SPRINT COMMUNICATIONS COMPANY, L.P., KANSAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BARNES, JAMES D.;REEL/FRAME:015852/0240 Effective date: 20040927 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
CC | Certificate of correction | ||
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: DEUTSCHE BANK TRUST COMPANY AMERICAS, NEW YORK Free format text: GRANT OF FIRST PRIORITY AND JUNIOR PRIORITY SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:SPRINT COMMUNICATIONS COMPANY L.P.;REEL/FRAME:041895/0210 Effective date: 20170203 |
|
AS | Assignment |
Owner name: SPRINT COMMUNICATIONS COMPANY L.P., KANSAS Free format text: TERMINATION AND RELEASE OF FIRST PRIORITY AND JUNIOR PRIORITY SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:052969/0475 Effective date: 20200401 Owner name: DEUTSCHE BANK TRUST COMPANY AMERICAS, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNORS:T-MOBILE USA, INC.;ISBV LLC;T-MOBILE CENTRAL LLC;AND OTHERS;REEL/FRAME:053182/0001 Effective date: 20200401 |
|
AS | Assignment |
Owner name: T-MOBILE INNOVATIONS LLC, KANSAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SPRINT COMMUNICATIONS COMPANY L.P.;REEL/FRAME:055604/0001 Effective date: 20210303 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |
|
AS | Assignment |
Owner name: SPRINT SPECTRUM LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: SPRINT INTERNATIONAL INCORPORATED, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: SPRINT COMMUNICATIONS COMPANY L.P., KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: SPRINTCOM LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: CLEARWIRE IP HOLDINGS LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: CLEARWIRE COMMUNICATIONS LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: BOOST WORLDWIDE, LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: ASSURANCE WIRELESS USA, L.P., KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: T-MOBILE USA, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: T-MOBILE CENTRAL LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: PUSHSPRING, LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: LAYER3 TV, LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: IBSV LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 |