American Megatrends MegaRAC G4, Руководство пользователя

Страница: 54 / 66

MegaRAC® G4 User’s Guide 44
Introduction:
What is SMASH:
Most server rooms and data centers subscribe to the maxim that more is better –
more
servers that is.
According to a survey by market research firm Novo1 Inc., the average data center has
230 servers. That number is rising 10 percent to 20 percent each year. Further, these data
centers typically host a diverse mixture of boxes from HP, Dell, IBM and others. As a
result, managing servers can be a time-consuming activity.
Server management is currently done on a ‘per server’ basis while IT services are offered
across a constellation of servers. So there is an inherent disconnect between offering IT
services and managing them. Standards become a way to tear down that wall.
Accordingly, the Distributed Management Task Force (DMTF, has issued a standard
known as Systems Management Architecture for Server Hardware (SMASH). Some of
the benefits of SMASH include reducing the management burden of server hardware,
cutting the cost of server administration, improving the reach of system administrators to
remotely located servers and standardizing the management of heterogeneous
environments.
In a nutshell, SMASH makes it much easier to manage servers regardless of the vendor.
It does away with a lot of time spent searching through manuals to figure out how to do
different tasks on the various servers in the data center.
The reason SMASH is so simple and so straightforward is found on an earlier DMTF
project – the Common Information Model (CIM) – which is now built into most existing
servers. SMASH leverages the richness of CIM to simplify what’s needed in a SMASH
script.
DMTF characterizes it as CIM having a lexicon of nouns, which SMASH harnesses to
reduce its commands down to a couple of verbs.
As well as managing servers as a whole, SMASH addresses individual components. A
server, for example, may have multiple processors, sensors, network cards, logical
devices and cooling systems. SMASH can be directed at specific processors, components
and subcomponents. Therefore, you can set up a script to periodically check the
temperature sensors on all machines so you can see how your power and AC needs can
be adjusted during the day or night to avoid overheating of equipment, or reduce the
electric bill safely.
SMASH CLP Architecture:
The SMASH CLP architecture requires a Telnet or an SSH client to communicate with
the SMASH server residing within the management controller. The SMASH has 11
commands and predefined targets specified in the SMASH CLP specification document.