v High availability and ease of serviceability. Blade server designs include
v Systems management and deployment. In blade servers, integrated systems
Deployment scenarios
The IBM
goals and environments, such as:
v Server consolidation
v E-business infrastructure
v Enterprise infrastructure
v High-performance computing
commerce applications (IBM WebSphere
Commerce Server), computational nodes (Linux clusters, rendering farms), and
workgroup infrastructure (Citrix MetaFrame terminal serving, Novell, or Microsoft
file/print serving).
high-availability features similar to those found in conventional rack servers, such
as redundant and hot-swap components (even the hot swapping of the blade
servers themselves). Removing a server for maintenance involves simply sliding
a blade out of the BladeCenter unit, which makes a policy of "hot-spare" servers
effective to implement. In addition, you can configure blades to fail over to one
another in the event of a failure.
management processors monitor the status of blades and modules all at once. In
the event of an alert, the processors can signal the systems management
software, which can then notify the administrator by e-mail or pager at any hour
of the day or night. In addition, the software is able to run system diagnostics
and integrate with enterprise-wide systems management software.
The ability to slide server blades in and out of the BladeCenter unit makes new
server deployment more efficient. When you insert a blade into an open bay, it is
connected to all infrastructure components in the BladeCenter unit. There is
typically no need to plug multiple cables into each server as it is installed. For
example, instead of having to attach a KVM cable, power cable, Ethernet cable,
and systems management cable per server, you may only need to attach one of
each cable per BladeCenter unit, which contains multiple servers. Even if you
decide to attach a second set of cables for redundancy you still have to attach
many fewer cables than is needed for a similar configuration of standalone
servers.
®
BladeCenter unit can be deployed to support a variety of networking
The IBM BladeCenter unit can be used by organizations with multiple server
locations that need to centralize or physically consolidate servers to increase
flexibility, reduce maintenance costs, and reduce human resources.
The IBM BladeCenter unit can be used by companies that need to deploy new
e-commerce and e-business applications and infrastructure quickly to minimize
time to market, while at the same time ensuring flexibility, scalability, and
availability.
The IBM BladeCenter unit can support Enterprise infrastructure through:
File and print: For organizations with decentralized/departmental file and
print servers that need to reduce the cost of ownership, increase reliability
and provide flexibility for growth.
Collaboration: For customers needing a cost-effective and reliable corporate
solution for e-mail, calendar, and other collaboration capabilities.
The IBM BladeCenter unit can be used by customers with compute-intensive
applications needing highly available clustered solutions to achieve significantly
higher degrees of scalability and performance, all managed at a low cost.
®
Application Servers, WebSphere
Chapter 1. Introducing the BladeCenter unit
5