Cisco Cisco UCS B250 M2 Extended Memory Blade Server 白書
White Paper
June 2016
© 2016 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public information.
Page 3
Imagine your IT department adapting
easily to rapidly changing business needs.
In contrast to vendors of traditional
approaches, we deliver a state-of-the-art
architecture that makes your dream a reality.
Chassis Compromises
The problem with traditional blades and with the PowerEdge M1000e architecture
begins with the blade chassis itself. Rack-in-a-box blade architecture takes all
the complexity of a rack (top-of-rack [ToR] switches, management modules, etc.)
and squeezes it into every blade chassis. When you replicate this complexity
multiple times per rack, you get even more complexity. In fact, you get far more
complexity than a rack full of traditional servers with ToR switches. The PowerEdge
M1000e architecture turns each chassis into an individual island that doesn’t
allow bandwidth to be shared outside each chassis. Changing applications or
scaling resources requires you to reconsider the way that all components in the
chassis are connected, leading to a cabling mess and networking errors that
prolong deployments. Customers must determine when a new Dell switch module
is necessary and what kinds of I/O adapters are used on each affected blade.
Changing networking modules or updating blades to take advantage of new
Intel architecture requires administrators to continually rethink and manage each
infrastructure island. Dell’s aging architecture limits flexibility and innovation in
several ways:
begins with the blade chassis itself. Rack-in-a-box blade architecture takes all
the complexity of a rack (top-of-rack [ToR] switches, management modules, etc.)
and squeezes it into every blade chassis. When you replicate this complexity
multiple times per rack, you get even more complexity. In fact, you get far more
complexity than a rack full of traditional servers with ToR switches. The PowerEdge
M1000e architecture turns each chassis into an individual island that doesn’t
allow bandwidth to be shared outside each chassis. Changing applications or
scaling resources requires you to reconsider the way that all components in the
chassis are connected, leading to a cabling mess and networking errors that
prolong deployments. Customers must determine when a new Dell switch module
is necessary and what kinds of I/O adapters are used on each affected blade.
Changing networking modules or updating blades to take advantage of new
Intel architecture requires administrators to continually rethink and manage each
infrastructure island. Dell’s aging architecture limits flexibility and innovation in
several ways:
• Multiple local management modules are necessary, and an external software
overlay is required to present these individual components under a common
interface.
interface.