当前位置: 澳门新濠3559 > 服务器运维 > 正文

也能够在数十秒到几分钟的时间内完成部件的更

时间:2019-10-06 18:42来源:服务器运维
服务器远程监控系统是很多网管员都需要学习并且掌握的,今天我们以DELL服务器远程监控系统为例,来详细的讲述一下服务器远程监控系统。 众所周知,过去几年数字化转型已席卷全

服务器远程监控系统是很多网管员都需要学习并且掌握的,今天我们以DELL服务器远程监控系统为例,来详细的讲述一下服务器远程监控系统。

众所周知,过去几年数字化转型已席卷全球,随着新技术的广泛应用,新的机会和价值正在不断被发现和创造。数据显示,到2020年,全球数字化转型相关的行业增加值将达到10万亿美元,全球1000强企业中的67%、中国1000强企业中的50%都把数字化转型作为企业的战略核心。

模块化、免工具、易拆装,这是我对曾经造访实验室的戴尔PowerEdge服务器的总体印象。

公司有多个分部,且机房没有专业值班,机房等级不够。在这种情况下,又想实时监控机房环境,于是使用IPMI方式来达到目的。由于之前已经部署了Zabbix监控系统,本次将结合Zabbix自带的IPMI,完成服务器温度及风扇转速等的监控。

Dell PowerEdge M1000e 模块化刀片服务器机箱和4片Dell PowerEdge M600刀片服务器,是有史以来评测室中最为“重量级”的产品,一大堆大大小小的箱子吓人一跳,开箱后也是一个10U身材的大家伙。机箱上有一张挺有意思的贴纸,用搬抬机箱的两个小人来标明Dell PowerEdge M1000e 的重量:空配50KG,刀片全配齐时重量183KG!(想偷走都不容易……)

澳门新濠3559 1

实验室曾经收到过的戴尔服务器算起来已经不少,从2U主流机架PowerEdge 2950、R805、R710,再到四路的AMD平台R905,乃至更加复杂的大块头刀片机箱M1000e,还有新进的R810,这些产品虽然定位、结构、配置各不相同,但有一点是共有的,也是值得称赞,那就是堪称“精巧”的模块化设计。

1.环境说明

被监控端服务器型号:Dell PowerEdge R510
也能够在数十秒到几分钟的时间内完成部件的更换澳门新濠3559,IT自动化管理成为企业在数字化转型过程中重点关注的方向。规划分配的IPMI地址: 10.103.1.100

从Dell PowerEdge M1000e 的体重和体积可以看出,一旦在机房中安置妥当,就轻易不会挪地方了。Dell PowerEdge M1000e全部配置部署后总共是16个半高刀片,要部署或者系统管理都会是相当麻烦的工作,哪个管理员都不愿意频繁的进出机房,忍受低温只为了敲下键盘的任意键,这时候KVM和远程管理工具就显得尤其重要了。

不过,正如一枚硬币的两面那样,虽然数字化转型可以为企业带来竞争优势,但随着越来越多企业级客户的应用部署范围从数据中心扩展至公有云、私有云和混合云多种模式,应用服务的复杂性和多样性也在快速上升,企业的IT基础设施变得越加庞杂,企业的IT管理面临一系列的挑战。

为何用这样的形容词?外形巨大而刻板的服务器,好像无论如何也和这个词沾不上边。不过当你尝试过不需借助工具——甚至是一把简单的螺丝刀,将一台由数十个部件组成的大家伙拆到零散,而又能轻易的像搭积木似的迅速组装起来后,想必会体会到“精巧”这个词并不为过。

2.Zabbix监控平台说明

Zabbix版本: 3.2.1,在安装时,未使用--with-openipmi
Zabbix网络接口可以连通10.103.1.100

Dell PowerEdge M1000e 机箱背板上集成了iKVM以及相关的远程管理工具。Chassis Management Controller机箱管理控制器简称CMC,通过每个刀片服务器上集成的Dell 远程访向控制器 (Remote Access Controller,iDRAC),完全可以对Dell PowerEdge M1000e中的每个刀片系统以及机箱进行远程监控和管理。Dell PowerEdge服务器的iDRAC功能让IT工作人员坐在舒适的办公室中就可以轻松地查看、监控和管理刀片服务器,配合CMC的远程管理与电源控制功能,从而简化各种管理任务释放更多的人力资源。

所以,IT自动化管理成为企业在数字化转型过程中重点关注的方向。目前,大部分企业都认同实现业务流程自动化可以节约时间和资金,让企业组织更加高效,更有创新能力。

这些设计看上去似乎和服务器的性能没有直接的关系,不过,它们确实能够让服务器的拆装、维护、升级等操作不再成为一件恼人的事情,并且能够让这些操作更加快速——管理员不必再去研究该用哪些工具,或者担心更换部件的时间太长,即使是首次拆开机箱,根据机箱背板的图示,也能够在数十秒到几分钟的时间内完成部件的更换,这听上去确实是件不错的事情。

3.前置学习

见 http://www.linuxidc.com/Linux/2017-05/143523.htm

现在小编就为各位解析下Dell PowerEdge的iDRAC如何工作。

但关于IT自动化,很多人却有着:“需要投入多少时间和精力?自动化是否会抢走我的饭碗?”等诸如此类的疑虑,导致部分企业在推进IT自动化方面不积极作为。那么,真正高效和敏捷的IT自动化,要如何选择和开始呢?

澳门新濠3559 2
全模块化设计的戴尔PowerEdge R810

4.配置IPMI

澳门新濠3559 3 

实现高效企业,IT自动化先行

从图片来看,这款戴尔PowerEdge R810似乎没什么特别。常见的2U机架设计,而前面板的保护罩也像“佐罗的面具”,虽然让R810显得不那么刻板,但也掩盖住了大部分的前面板细节。不过所谓“内有乾坤”,当打开前面板和机箱顶盖后,R810在设计上的独特价值,才能一览无余。

4.1.配置IPMI地址

可以参考前置推荐中的《Managing Dell PowerEdge Servers Using IPMItool》在服务器启动时进行IPMI地址的配置,并开启IPMI Over LAN。
也可以使用Dell的iDRAC开启IPMI功能,具体可以查看文章最后的参考资料。

澳门新濠3559 4

M1000e机箱后左上和右上的插槽就是CMC卡所为的位置,中间的位置iKVM。两片配齐的情况下也是以主从热备的方式工作,其中亮蓝色灯的主卡。

我们知道,数字化转型并不仅仅是IT转型,但离开了IT,企业的数字化转型将无从谈起。可以说,IT不仅是数字化转型的基石,更是驱动力。然而,来自Gartner的一项调查显示,59%的受调查IT专业人员认为他们的IT组织没有为未来两年的数字化业务做好准备。

提到戴尔R810首先不得不介绍一下英特尔的多路新平台至强7500。今年3月,英特尔推出了“Nehalem-EX”至强7500多路新平台,至强7500对于英特尔来说是今年、甚至近年最为重头的产品之一。采用Nehalem微构架的至强7500具有一些足够炫耀的新特性:如采用QuickPath互联架构、具有四条高达6.4GT/s的QPI总线,集成四通道DDR3内存控制器,使内存和I/O带宽得到前所未有的提升。

4.2.获取传感器信息

登录Zabbix服务器,通过ipmitool远程访问Dell服务器传感器信息

# ipmitool -I lan -H 10.103.1.100 -U root -P calvin -L user sensor list
# ipmitool -I lan -H 10.103.1.100 -U root -P calvin -L user sensor get "FAN MOD 1B RPM"

澳门新濠3559 5

澳门新濠3559 6

澳门新濠3559 7 

事实上,随着数字化转型的加速,IT行业不断地生产新技术和新工具,一方面为企业带来了竞争优势,另一方面也为企业的IT管理带来了难题。对于技术人员而言,传统的批量处理和静态脚本已经不再可行了,这些旧的、“可确定的”自动化方法无法支持诸如云计算这样的技术所呈现的巨大规模。

至强7500曾被誉为“史上最强的x86处理器”,它不再满足于x86市场,而是将目光头像了更为高端的RISC小型机市场。对此,至强7500具有两个资本,高扩充性和移植自安腾平台的RAS特性。从扩展性上看,至强7500每颗处理器可支持16根内存,那么四路系统内存可支持1TB,并且至强7500不通过节点控制器即可扩展到8路系统。另外,至强7500引入了移植自安腾平台的RAS特性,使之应用范围可以扩展到关键任务领域。

4.3.安装IPMItool软件包

# yum -y install OpenIPMI OpenIPMI-devel ipmitool freeipmi

比起刀片服务器,CMC卡的形状更象是刀,一把专业的菜刀。

据informationWeek关于IT运维的调查显示,只有30%的企业认为他们的IT是非常敏捷和灵活的。而在Forrester发布的“Foresights预算和优先事项跟踪调查”中显示,IT运维将近70%的时间用在维护现有IT环境上;高达75%的宕机时间是由手动和分离式的IT流程造成的。

在至强7500平台发布后,戴尔发布了基于至强7500的新产品,包括2U四路设计的R810、4U四路的R910以及M910刀片服务器。其中戴尔R910是具有最高扩展能力的四路服务器,具备出色的可靠性和性能;戴尔M910是新一代四路刀片,具有最高的计算密度;而戴尔R810可以说是介于两者之间的“折衷”解决方案,2U四路的设计让R810同样具备了很高的计算密度,并且兼顾扩展能力,具备32个内存插槽和4个千兆以太网接口,特别适合虚拟化应用。

4.4.配置Zabbix

注:为了支持IPMI,需要在zabbix server/proxy安装时增加--with-openipmi参数

服务器端配置zabbix IPMI pollers
zabbix_server.conf/zabbix_proxy.conf

# sed -i '/# StartIPMIPollers=0/aStartIPMIPollers=5' zabbix_server.conf
# service zabbix-server restart

澳门新濠3559 8 

澳门新濠3559 9

实验室曾经收到过的戴尔服务器算起来已经不少,从...

4.5.导入监控模板

下面提供DELL的2个型号的IPMI模板:
template-ipmi-dell-poweredge-r510
template-ipmi-dell-poweredge-2950
添加监控主机,关联上本模板,并在IPMI页面,设置Authentication algorithmDefault,Privilege levelUser, Usernamesensor, Passwordsensor_pass,保存即可。
使用此种方法获取数据的结果就是效率很差,基本没什么数据。

CMC的界面:

实际上,企业迫切需要的实际上是一种更加系统化的自动化形式——这种IT自动化的方式应当能够充分利用云计算等新技术的功能,同时还应当增强业务敏捷性。据IDG预测,那些未在其转型路线图中纳入IT自动化的企业在2019年将出现25%的客户保留率下降。

5.使用Zabbix External checks自定义IPMI

本来是选择nagios的IPMI插件:check_ipmi_sensor,文件是:check_ipmi_sensor_v3-v3.9.tar.gz
具体使用方法详见:

Dell PowerEdge M1000e机箱上自带一块LCD液晶的控制面板,在通电后就可以在上面设置CMC以及每一个刀片服务器的IP地址等基本信息,通过LAN的浏览器就可以以WEB的方式浏览CMC的图形界面。

此外,在一项Forrester的调查中,所有受调查的组织都报告了由于IT自动化而带来的一项或多项技术和业务优势。其中,最常提到的好处是更高的系统可靠性,更快的部署/服务交付以及更高效的IT人员配置,使IT部门能够更快地交付产品更新,从而使客户满意。

5.1.安装perl-IPC-Run模块

yum -y install perl-IPC-Run perl-Getopt-Long

澳门新濠3559 10 

澳门新濠3559 11

5.2.使用check_ipmi_sensor查看效果

但是发现报错。

# ./check_ipmi_sensor -f ipmi.cfg -H 10.103.1.100 -vvv
------------- debug output for sel (-vvv is set): ------------
  /usr/sbin/ipmi-sel was executed with the following parameters:
    /usr/sbin/ipmi-sel -h 10.103.1.100 --config-file ipmi.cfg --driver-type=LAN_2_0 --output-event-state --interpret-oem-data --entity-sensor-names
  output of FreeIPMI:
ID  | Date        | Time     | Name                                        | Type                     | State    | Event
1   | Apr-08-2011 | 06:42:13 | System Board SEL                            | Event Logging Disabled   | Nominal  | Log Area Reset/Cleared
2   | Jan-01-1970 | 08:00:31 | System Board Intrusion                      | Physical Security        | Critical | General Chassis Intrusion ; Intrusion while system Off
3   | Jan-01-1970 | 08:00:36 | System Board Intrusion                      | Physical Security        | Critical | General Chassis Intrusion ; Intrusion while system Off
4   | Aug-15-2011 | 23:09:53 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Critical | Drive Fault ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
5   | Aug-16-2011 | 11:38:25 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
6   | Aug-16-2011 | 11:38:25 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Critical | Drive Fault ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
7   | Aug-16-2011 | 11:38:55 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
8   | Jun-10-2012 | 22:41:13 | System Board Ambient Temp                   | Temperature              | Warning  | Upper Non-critical - going high ; Sensor Reading = 45.00 C ; Threshold = 45.00 C
9   | Jun-11-2012 | 02:53:53 | System Board Ambient Temp                   | Temperature              | Nominal  | Upper Non-critical - going high ; Sensor Reading = 43.00 C ; Threshold = 45.00 C
10  | Nov-05-2012 | 21:56:42 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Critical | Drive Fault ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
11  | Nov-14-2012 | 21:53:58 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
12  | Nov-14-2012 | 21:53:58 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Critical | Drive Fault ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
13  | Nov-14-2012 | 21:54:19 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
14  | Nov-15-2012 | 16:12:03 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Critical | Drive Fault ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
15  | Nov-17-2012 | 17:14:34 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
16  | Nov-17-2012 | 17:14:34 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Critical | Drive Fault ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
17  | Nov-17-2012 | 17:15:40 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
18  | Nov-19-2012 | 20:47:57 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
19  | Nov-19-2012 | 20:50:04 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
20  | Jan-01-1970 | 08:00:33 | System Board Intrusion                      | Physical Security        | Critical | General Chassis Intrusion ; Intrusion while system Off
21  | Jan-01-1970 | 08:00:38 | System Board Intrusion                      | Physical Security        | Critical | General Chassis Intrusion ; Intrusion while system Off
22  | Jun-27-2014 | 17:27:38 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
23  | Jun-27-2014 | 17:27:53 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
24  | Jan-01-1970 | 08:00:31 | System Board Intrusion                      | Physical Security        | Critical | General Chassis Intrusion ; Intrusion while system Off
25  | Jan-01-1970 | 08:00:36 | System Board Intrusion                      | Physical Security        | Critical | General Chassis Intrusion ; Intrusion while system Off
26  | Oct-31-2016 | 05:48:35 | System Board Ambient Temp                   | Temperature              | Warning  | Lower Non-critical - going low ; Sensor Reading = 8.00 C ; Threshold = 8.00 C
27  | Oct-31-2016 | 09:00:38 | System Board Ambient Temp                   | Temperature              | Nominal  | Lower Non-critical - going low ; Sensor Reading = 10.00 C ; Threshold = 8.00 C
------------- debug output for sensors (-vvv is set): ------------
  script was executed with the following parameters:
    ./check_ipmi_sensor -f ipmi.cfg -H 10.103.1.100 -vvv
  check_ipmi_sensor version:
    3.9
  FreeIPMI version:
    ipmi-sensors - 1.2.9
  FreeIPMI was executed with the following parameters:
    /usr/sbin/ipmi-sensors -h 10.103.1.100 --config-file ipmi.cfg --quiet-cache --sdr-cache-recreate --interpret-oem-data --output-sensor-state --ignore-not-available-sensors --driver-type=LAN_2_0 --output-sensor-thresholds
  FreeIPMI return code: 0
  output of FreeIPMI:
Record ID | Sensor Name | Sensor Group | Monitoring Status | Sensor Units | Sensor Reading
5 | Ambient Temp | Temperature | Nominal | C | 28.000000
7 | CMOS Battery | Battery | Nominal | N/A | 'OK'
8 | VCORE PG | Voltage | Nominal | N/A | 'State Deasserted'
9 | VCORE PG | Voltage | Nominal | N/A | 'State Deasserted'
10 | 0.75 VTT PG | Voltage | Nominal | N/A | 'State Deasserted'
11 | 0.75 VTT PG | Voltage | Nominal | N/A | 'State Deasserted'
12 | CPU VTT PG | Voltage | Nominal | N/A | 'State Deasserted'
13 | 1.5V PG | Voltage | Nominal | N/A | 'State Deasserted'
14 | 1.8V PG | Voltage | Nominal | N/A | 'State Deasserted'
15 | 5V PG | Voltage | Nominal | N/A | 'State Deasserted'
16 | MEM CPU2 FAIL | Voltage | Nominal | N/A | 'State Deasserted'
17 | 5V Riser PG | Voltage | Nominal | N/A | 'State Deasserted'
18 | MEM CPU1 FAIL | Voltage | Nominal | N/A | 'State Deasserted'
19 | VTT CPU2 FAIL | Voltage | Nominal | N/A | 'State Deasserted'
20 | VTT CPU1 FAIL | Voltage | Nominal | N/A | 'State Deasserted'
21 | 0.9V PG | Voltage | Nominal | N/A | 'State Deasserted'
22 | CPU2 1.8 PLL PG | Voltage | Nominal | N/A | 'State Deasserted'
23 | CPU1 1.8 PLL PG | Voltage | Nominal | N/A | 'State Deasserted'
24 | 1.1 FAIL | Voltage | Nominal | N/A | 'State Deasserted'
25 | 1.0 LOM FAIL | Voltage | Nominal | N/A | 'State Deasserted'
26 | 1.0 AUX FAIL | Voltage | Nominal | N/A | 'State Deasserted'
27 | Heatsink Pres | Entity Presence | Nominal | N/A | 'Entity Present'
28 | iDRAC6 Ent Pres | Entity Presence | Critical | N/A | 'Entity Absent'
29 | USB Cable Pres | Entity Presence | Nominal | N/A | 'Entity Present'
31 | Riser Presence | Entity Presence | Nominal | N/A | 'Entity Present'
32 | FAN MOD 1A RPM | Fan | Nominal | RPM | 3480.000000
34 | FAN MOD 2A RPM | Fan | Nominal | RPM | 3480.000000
36 | FAN MOD 3A RPM | Fan | Nominal | RPM | 3480.000000
39 | FAN MOD 4A RPM | Fan | Nominal | RPM | 3480.000000
40 | Presence | Entity Presence | Nominal | N/A | 'Entity Present'
41 | Presence | Entity Presence | Nominal | N/A | 'Entity Present'
42 | Presence | Entity Presence | Nominal | N/A | 'Entity Present'
43 | Presence | Entity Presence | Nominal | N/A | 'Entity Present'
44 | Presence  | Entity Presence | Nominal | N/A | 'Entity Present'
45 | Status | Processor | Nominal | N/A | 'Processor Presence detected'
46 | Status | Processor | Nominal | N/A | 'Processor Presence detected'
47 | Status | Power Supply | Nominal | N/A | 'Presence detected'
48 | Current | Current | Nominal | A | 0.400000
49 | Current | Current | Nominal | A | 0.400000
50 | Voltage | Voltage | Nominal | V | 218.000000
51 | Voltage | Voltage | Nominal | V | 218.000000
52 | Status | Power Supply | Nominal | N/A | 'Presence detected'
53 | Status | Cable/Interconnect | Nominal | N/A | 'Cable/Interconnect is connected'
54 | OS Watchdog | Watchdog 2 | Nominal | N/A | 'OK'
56 | Intrusion | Physical Security | Nominal | N/A | 'OK'
57 | PS Redundancy | Power Supply | Nominal | N/A | 'Fully Redundant'
58 | Fan Redundancy | Fan | Nominal | N/A | 'Fully Redundant'
60 | System Level | Current | Nominal | W | 168.000000
61 | Power Optimized | OEM Reserved | Nominal | N/A | 'Good'
62 | Drive | Drive Slot | Nominal | N/A | 'Drive Presence'
65 | Cable SAS A | Cable/Interconnect | Nominal | N/A | 'Cable/Interconnect is connected'
66 | Cable SAS B | Cable/Interconnect | Nominal | N/A | 'Cable/Interconnect is connected'
67 | DKM Status | OEM Reserved | N/A | N/A | 'OEM Event = 0000h'
119 | FAN MOD 5A RPM | Fan | Nominal | RPM | 3480.000000

--------------------- end of debug output ---------------------
IPMI Status: Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 759.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 759.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 759.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 759.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 759.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 759.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 759.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 759.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 759.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 759.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 737.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 738.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 749.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in concatenation (.) or string at ./check_ipmi_sensor line 750.
Use of uninitialized value in string ne at ./check_ipmi_sensor line 759.
Critical [iDRAC6 Ent Pres = Critical ('Entity Absent'), System Board Intrusion = Critical (Physical Security), System Board Intrusion = Critical (Physical Security), Disk Drive Bay 1 Drive 2 = Critical (Drive Slot), Disk Drive Bay 1 Drive 2 = Critical (Drive Slot), System Board Ambient Temp = Warning (Temperature), Disk Drive Bay 1 Drive 2 = Critical (Drive Slot), Disk Drive Bay 1 Drive 2 = Critical (Drive Slot), Disk Drive Bay 1 Drive 2 = Critical (Drive Slot), Disk Drive Bay 1 Drive 2 = Critical (Drive Slot), System Board Intrusion = Critical (Physical Security), System Board Intrusion = Critical (Physical Security), System Board Intrusion = Critical (Physical Security), System Board Intrusion = Critical (Physical Security), System Board Ambient Temp = Warning (Temperature)] | 'Ambient Temp'=28.000000;:;: 'FAN MOD 1A RPM'=3480.000000;:;: 'FAN MOD 2A RPM'=3480.000000;:;: 'FAN MOD 3A RPM'=3480.000000;:;: 'FAN MOD 4A RPM'=3480.000000;:;: 'Current'=0.400000;:;: 'Current'=0.400000;:;: 'Voltage'=218.000000;:;: 'Voltage'=218.000000;:;: 'System Level'=168.000000;:;: 'FAN MOD 5A RPM'=3480.000000;:;:
Ambient Temp = 28.000000 (Status: Nominal)
CMOS Battery = 'OK' (Status: Nominal)
VCORE PG = 'State Deasserted' (Status: Nominal)
VCORE PG = 'State Deasserted' (Status: Nominal)
0.75 VTT PG = 'State Deasserted' (Status: Nominal)
0.75 VTT PG = 'State Deasserted' (Status: Nominal)
CPU VTT PG = 'State Deasserted' (Status: Nominal)
1.5V PG = 'State Deasserted' (Status: Nominal)
1.8V PG = 'State Deasserted' (Status: Nominal)
5V PG = 'State Deasserted' (Status: Nominal)
MEM CPU2 FAIL = 'State Deasserted' (Status: Nominal)
5V Riser PG = 'State Deasserted' (Status: Nominal)
MEM CPU1 FAIL = 'State Deasserted' (Status: Nominal)
VTT CPU2 FAIL = 'State Deasserted' (Status: Nominal)
VTT CPU1 FAIL = 'State Deasserted' (Status: Nominal)
0.9V PG = 'State Deasserted' (Status: Nominal)
CPU2 1.8 PLL PG = 'State Deasserted' (Status: Nominal)
CPU1 1.8 PLL PG = 'State Deasserted' (Status: Nominal)
1.1 FAIL = 'State Deasserted' (Status: Nominal)
1.0 LOM FAIL = 'State Deasserted' (Status: Nominal)
1.0 AUX FAIL = 'State Deasserted' (Status: Nominal)
Heatsink Pres = 'Entity Present' (Status: Nominal)
iDRAC6 Ent Pres = 'Entity Absent' (Status: Critical)
USB Cable Pres = 'Entity Present' (Status: Nominal)
Riser Presence = 'Entity Present' (Status: Nominal)
FAN MOD 1A RPM = 3480.000000 (Status: Nominal)
FAN MOD 2A RPM = 3480.000000 (Status: Nominal)
FAN MOD 3A RPM = 3480.000000 (Status: Nominal)
FAN MOD 4A RPM = 3480.000000 (Status: Nominal)
Presence = 'Entity Present' (Status: Nominal)
Presence = 'Entity Present' (Status: Nominal)
Presence = 'Entity Present' (Status: Nominal)
Presence = 'Entity Present' (Status: Nominal)
Presence = 'Entity Present' (Status: Nominal)
Status = 'Processor Presence detected' (Status: Nominal)
Status = 'Processor Presence detected' (Status: Nominal)
Status = 'Presence detected' (Status: Nominal)
Current = 0.400000 (Status: Nominal)
Current = 0.400000 (Status: Nominal)
Voltage = 218.000000 (Status: Nominal)
Voltage = 218.000000 (Status: Nominal)
Status = 'Presence detected' (Status: Nominal)
Status = 'Cable/Interconnect is connected' (Status: Nominal)
OS Watchdog = 'OK' (Status: Nominal)
Intrusion = 'OK' (Status: Nominal)
PS Redundancy = 'Fully Redundant' (Status: Nominal)
Fan Redundancy = 'Fully Redundant' (Status: Nominal)
System Level = 168.000000 (Status: Nominal)
Power Optimized = 'Good' (Status: Nominal)
Drive = 'Drive Presence' (Status: Nominal)
Cable SAS A = 'Cable/Interconnect is connected' (Status: Nominal)
Cable SAS B = 'Cable/Interconnect is connected' (Status: Nominal)
FAN MOD 5A RPM = 3480.000000 (Status: Nominal)不过根据它的提示(其实插件也是调用如下命令),可以使用

/usr/sbin/ipmi-sel -h 10.103.1.100 --config-file ipmi.cfg --driver-type=LAN_2_0 --output-event-state --interpret-oem-data --entity-sensor-names执行结果是:

# /usr/sbin/ipmi-sel -h 10.103.1.100 --config-file ipmi.cfg --driver-type=LAN_2_0 --output-event-state --interpret-oem-data --entity-sensor-names
ID  | Date        | Time     | Name                                        | Type                     | State    | Event
1   | Apr-08-2011 | 06:42:13 | System Board SEL                            | Event Logging Disabled   | Nominal  | Log Area Reset/Cleared
2   | Jan-01-1970 | 08:00:31 | System Board Intrusion                      | Physical Security        | Critical | General Chassis Intrusion ; Intrusion while system Off
3   | Jan-01-1970 | 08:00:36 | System Board Intrusion                      | Physical Security        | Critical | General Chassis Intrusion ; Intrusion while system Off
4   | Aug-15-2011 | 23:09:53 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Critical | Drive Fault ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
5   | Aug-16-2011 | 11:38:25 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
6   | Aug-16-2011 | 11:38:25 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Critical | Drive Fault ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
7   | Aug-16-2011 | 11:38:55 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
8   | Jun-10-2012 | 22:41:13 | System Board Ambient Temp                   | Temperature              | Warning  | Upper Non-critical - going high ; Sensor Reading = 45.00 C ; Threshold = 45.00 C
9   | Jun-11-2012 | 02:53:53 | System Board Ambient Temp                   | Temperature              | Nominal  | Upper Non-critical - going high ; Sensor Reading = 43.00 C ; Threshold = 45.00 C
10  | Nov-05-2012 | 21:56:42 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Critical | Drive Fault ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
11  | Nov-14-2012 | 21:53:58 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
12  | Nov-14-2012 | 21:53:58 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Critical | Drive Fault ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
13  | Nov-14-2012 | 21:54:19 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
14  | Nov-15-2012 | 16:12:03 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Critical | Drive Fault ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
15  | Nov-17-2012 | 17:14:34 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
16  | Nov-17-2012 | 17:14:34 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Critical | Drive Fault ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
17  | Nov-17-2012 | 17:15:40 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
18  | Nov-19-2012 | 20:47:57 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
19  | Nov-19-2012 | 20:50:04 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
20  | Jan-01-1970 | 08:00:33 | System Board Intrusion                      | Physical Security        | Critical | General Chassis Intrusion ; Intrusion while system Off
21  | Jan-01-1970 | 08:00:38 | System Board Intrusion                      | Physical Security        | Critical | General Chassis Intrusion ; Intrusion while system Off
22  | Jun-27-2014 | 17:27:38 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
23  | Jun-27-2014 | 17:27:53 | Disk Drive Bay 1 Drive 2                    | Drive Slot               | Nominal  | Drive Presence ; OEM Event Data2 code = 01h ; OEM Event Data3 code = 02h
24  | Jan-01-1970 | 08:00:31 | System Board Intrusion                      | Physical Security        | Critical | General Chassis Intrusion ; Intrusion while system Off
25  | Jan-01-1970 | 08:00:36 | System Board Intrusion                      | Physical Security        | Critical | General Chassis Intrusion ; Intrusion while system Off
26  | Oct-31-2016 | 05:48:35 | System Board Ambient Temp                   | Temperature              | Warning  | Lower Non-critical - going low ; Sensor Reading = 8.00 C ; Threshold = 8.00 C
27  | Oct-31-2016 | 09:00:38 | System Board Ambient Temp                   | Temperature              | Nominal  | Lower Non-critical - going low ; Sensor Reading = 10.00 C ; Threshold = 8.00 C

CMC是热插拔系统管理硬件和软件控制器,设计用于为Dell PowerEdge M1000e刀片服务器提供远程管理和电源控制。它配有自己的处理器和内存,并从模块化刀片服务器机箱中获取电源。它的主要特性包括:

调查还发现,尽管很多公司都认为自己实现了IT自动化,但真实的情况是,他们中的大多数并不是真正的自动化。原因在于,虽然大部分企业都在某种程度上实现了IT自动化,但很少有公司能够充分发挥服务器自动化的潜力,具体来说:

5.3编写Zabbix外部检查(External checks)脚本

# pwd
/usr/local/zabbix/share/zabbix/externalscripts
# cat check_ipmi

下面是脚本内容

#!/bin/bash
#用于检测ipmi相关信息
#Create on 2016-011-18
#@author: Chinge_Yang

args="$*"
echo $(date  %F-%T) $args >> /tmp/check_ipmi.debug

check_ipmi_dir=/usr/local/zabbix/shell/check_ipmi_sensor
check_ipmi_bin=$check_ipmi_dir/check_ipmi_sensor

ipmi_sensors=/usr/sbin/ipmi-sensors
ipmi_cfg=$check_ipmi_dir/ipmi.cfg

#$check_ipmi_bin -f $ipmi_cfg -v $args
#${ipmi_sel} $args --config-file $ipmi_cfg --driver-type=LAN_2_0 --output-event-state --interpret-oem-data --entity-sensor-names 
options="--quiet-cache --sdr-cache-recreate --interpret-oem-data --output-sensor-state --ignore-not-available-sensors --driver-type=LAN_2_0 --output-sensor-thresholds"

function usage(){
    echo "Usage: `basename $0` options (-h HOST|-n NAME)"
}

function check(){
    result=$($ipmi_sensors -h $host --config-file $ipmi_cfg $options|grep "$name"|awk -F"| " '{print $NF}')

    printf "%.4fn" $result
}

if [ $# -lt 4 ]  
then
    usage
    exit 55     
fi  

# 用法: scriptname -options
# 注意: 必须使用破折号 (-) 
# 参数后接冒号,表示必须接值
while getopts ":h:n:" Option;do
  case $Option in
    h)
    host=$OPTARG
    ;;
    n)
    name=$OPTARG
    ;;
    *)
    usage
    ;;   # 默认情况的处理
  esac
done

shift $(($OPTIND - 1))
#  (译者注: shift命令是可以带参数的, 参数就是移动的个数)
#  将参数指针减1, 这样它将指向下一个参数.
#  $1 现在引用的是命令行上的第一个非选项参数,
#  如果有一个这样的参数存在的话.

check

exit 0

添加执行权限

chmod a x check_ipmi

•支持Microsoft Active Directory身份验证:目录服务,如Microsoft Active Directory维护常规的信息数据库,它是控制网络用户和资产所必需的;使用Active Directory的机构可以使用该数据库访问CMC。管理员可以将CMC用户ID和密码放到使用标准架构或者扩展架构的Active Directory中进行集中管理。

第一,没有真正自动化的可信服务器管理任务。调查显示,虽然大多数组织认为自己在自动化方面取得了“好”或“优秀”的进步,但在Forrester列举的9个服务器管理任务中,只有不到50%的人认为其自动化的效率只有一个比自己手动更高效。

5.4新建自定义模板

这里就不详细介绍内容了,其实就是改改上文中的模板而来,一张图看完内容:

澳门新濠3559 12

给2张图看看效果:

澳门新濠3559 13

澳门新濠3559 14

好吧,最后发现,就算是自定义脚本,仍然是获取数据艰难,脚本执行ipmi的命令都timeout。

本文永久更新链接地址:http://www.linuxidc.com/Linux/2017-05/143529.htm

澳门新濠3559 15

•全面监控:CMC提供系统信息的使用以及各种组件的状态,如刀片服务器、电源供给、风扇和温度感应器。

第二,配置请求仍取决于IT参与。我们知道,在数字经济时代,业务面临着快速交付的压力,然而调查显示,仍有半数的公司通过手动配置资源而没有自助服务功能,有52%的调查用户表示需要几天来配置这些资源,仅有24%的调查用户可以在几个小时内完成基础架构的调配。

•访问系统事件日志:对于机箱上发生的各种事件,CMC都会生成硬件日志,其中包括严重程度、时间和活动的描述。管理员可以查看、保存文本文件,并从CMC界面清除硬件日志。

澳门新濠3559 16

•Automated alerts:自动告警:管理员可以将CMC配置为发送电子邮件或者简单网络管理协议(SNMP)陷井,提供与温度、硬件错误配置、断电、风扇转速等等有关的警告或者错误提示。

不难看出,IT自动化不仅可以帮助企业更有效率,而且通过自动化操作常规作业的日常流程或易出错的部分,企业可以节省出时间更专注于环境中需要修复、改进或升级的业务,从而帮助企业在眼下快节奏的市场中更有效地竞争。可以这样说,在数字经济时代,要实现企业的高效率运营,IT自动化管理必须先行。

澳门新濠3559 17 

拥抱Dell EMC,实现服务器自动化

Dell PowerEdge M1000e共有9个冗余风扇,CMC可以提供所有风扇的实时运转状态和转速。

那么,要从何处入手,才能打响企业实现IT自动化管理的第一枪呢?没错,从拥抱戴尔易安信,实现IT服务器基础架构的自动化开始。

澳门新濠3559 18 

戴尔易安信自主研发了一套IT系统管理解决方案Dell EMC OpenManage,其中包括了一系列的管理软件与硬件,该产品组合不仅提供了直观、易于使用的工具,消除了基础架构管理的复杂性,帮助实现强大的可编程性,并更大限度地减少人为错误。除此之外,OpenManage工具还可帮助组织提高安全性、节约时间。

电源部分,Dell PowerEdge M1000e一共备有6个电源,其中3用于供电另外3个做热备。在CMC中也给出了电源的信息。

不过,OpenManage最为强大之处,在于能够帮助IT管理员更高效地管理IT环境中的服务器、存储、网络、客户端以及软件,为客户将来的自动化打下坚实基础,可以从三个层面来解读:

澳门新濠3559 19

首先,在管理层面,戴尔易安信OpenManage Enterprise让设备管理变得更加简单、方便、高效。戴尔易安信OpenManage Enterprise是全新的虚拟化企业系统管理控制台,它部署快速、配置方便且功能强大,可大大提高机房运维人员的工作效率,有助于企业领先于快速变化的业务环境。它覆盖所有PowerEdge平台,包括机架式、塔式和模块化服务器,可以让用户能够轻松地监视和控制系统、组件和虚拟机的性能。

当然,CMC的最为重要的功能是能监控Dell PowerEdge M1000e中所有的刀片服务器。以刀片服务器SLOT插槽顺序为识别,也可以自己定义服务器的名称。点击左侧列表中的服务器,右边就会展示其具体的信息,如:电源运行情况,服务器型号及序列号还有重要的各自的iDRAC控制器的IP信息。

澳门新濠3559 20

...

过去,以传统方式部署一套集中监控管理平台,架构复杂、规模庞大不说,还需要几台专门的服务器,分别安装配置监控管理软件、储存信息的数据库甚至中间件等,另外还有在每台被监控的服务器上安装代理软件的步骤——整个监控管理平台,从部署到真正投入使用,没有十天半个月是下不来的。

现在,将OpenManage Enterprise导入虚拟化环境中,然后批量导入被监控设备列表——只需10分钟,一套集中监控管理平台就可投入使用。

澳门新濠3559 21

其次,在运维层面,通过集成式Dell EMC远程访问控制器iDRAC (Integrated Dell EMC Remote Access Controller),可自动执行从部署到更新再到监视、维护和补救在内的管理任务,提高了服务器远程管理效率和生命周期管理效率,进而提高IT效率。

澳门新濠3559 22

简单来说,iDRAC本身是一个集成式的戴尔远程控制卡,相当于是附加在服务器上的一台小电脑,通过与服务器主板上的管理芯片BMC进行通信,监控与管理服务器的硬件状态信息,它不仅是OpenManage产品组合的一项基础技术,而且是许多自动化功能背后的“大脑”。

管理人员可通过配备iDRAC Quick Sync2.0模块的机箱,加上安装有OpenManage Mobile 2.0的苹果/安卓手机/Pad,通过蓝牙或WiFi连接服务器,对PowerEdge服务器进行监测、管理,从而实现对服务器便捷快速的巡检、故障检测与定位。

澳门新濠3559 23

而且iDRAC 还带有组管理(Group manager)功能,管理员无需额外工具,无需其他设置,只需启用该功能,即可通过主iDRAC管理多达100台的服务器集群。更为强大的是,即便在服务器处于关机的状态,系统管理员也可以通过iDRAC 管理并更新服务器。

值得一提的是,目前戴尔易安信已率先推出了支持“嵌入式管理自动化”的一系列服务器产品,每一台PowerEdge 服务器中都嵌入了iDRAC 。

澳门新濠3559 24

最后,对于需要同时管理物理和虚拟基础架构的管理员来说,Dell EMC还提供了OpenManage Integration for VMware vCenter可一致地管理非百分之百虚拟化的环境,进而帮助实现智能自动化管理。该工具精简了与Dell EMC PowerEdge服务器的管理和部署相关的工具和任务,大大地降低复杂性,加快部署,并更大限度地减少IT运营中的风险。

澳门新濠3559 25

由此可见,拥抱Dell EMC不仅意味着可通过统一管理控制台以远程的方式对虚拟和物理IT环境进行管理,也意味着从部署到更新再到监视、维护和补救在内的管理任务无缝自动化管理,最终释放IT资源降低维护成本并延长系统正常运行时间以确保服务持续可用。

为企业数字化转型保驾护航

值得一提的是,在戴尔易安信的帮助下,如今越来越多的企业成功实现了服务器基础架构自动化管理。

举例来说,法国兴业银行(Societe Generale)是法国最大的商业银行集团之一,也是欧洲主要的金融服务集团之一,支持着全球3100万的个人、专业人士、公司和机构投资者。他们面临一项挑战,就是在提供卓越客户服务的同时,遵守新的管理法规和不断变化的安全保护规则。

澳门新濠3559 26

以前,法兴银行采用一种“回应请求”的运营模式,即IT以手动方式答复并满足请求。以这种方式运营意味着部署一台新服务器需要数月时间。该集团需要一种更快的自动化的运营模式,以便集团IT部门能够自行调配虚拟机、存储和连接,更为关键的是,必须改善响应时间,以遵守快速变化的行业管理法规和安全条例。

为提高他们的响应速度和总体效率,法兴银行转向采用Dell EMC PowerEdge服务器,从手动模式转变为自动化模式。通过实现此流程自动化,IT基础设施不仅通过更低的延迟改善了性能,还能够实时根据需求自行调配计算服务,并且将部署新服务器的时间从两个月缩短到30分钟,使IT运维人员能够将时间和资源投入到其他可增加价值的任务上。

澳门新濠3559 27

毫无疑问,戴尔易安信不仅帮助用户实现了最根本的需求,也为企业的业务发展起到了最为坚实的支撑作用,时刻为企业的数字化转型保驾护航。

总的来说,客户的需求正随着新技术的深入应用而不断的改变,而戴尔易安信在服务器领域的创新,正是戴尔易安信在数字化转型时代不断探索的具体体现。当然,也正是这种洞察和创新,让戴尔易安信始终“快人一步”,并一直处在数字化转型的领跑者行列之中。

编辑:服务器运维 本文来源:也能够在数十秒到几分钟的时间内完成部件的更

关键词: 澳门新濠3559