White Paper ServerView Agents Retrieving System Status via SNMP This paper describes how to retrieve the general system status on Fujitsu s PRIMERGY and PRIMEQUEST servers by using SNMP commands directed at the SC2 MIB, the OS MIB and the status MIB agents. As a prerequisite ServerView Agents for Windows or Linux have to be installed on the queried server. Table of contents SC2 MIB Information 1 Getting the overall system status summary 2 Getting boot status details 2 Getting the power supply status 3 Getting detailed temperature status 3 Getting detailed fan component status 4 Getting voltage status 4 Getting the CPU status 5 Getting detailed memory module status 5 Getting the system event log (SEL) table 6 OS MIB Information 7 Status MIB Information 8 Tips and tricks 9 SC2 MIB Information The ServerView SC2 MIB is located at the OID 1.3.6.1.4.1.231.2.10.2.2.10: snmptranslate 1.3.6.1.4.1.231.2.10.2.2.10 FSC-SERVERCONTROL2-MIB::fscServerControl2 This MIB contains many tables and object groups which extensively describe PRIMERGY and PRIMEPOWER server properties. For example it contains information about hardware and sensors, environment, system status, maintenance, deployment, recovery, driver monitoring and much more. The focus of this paper is to describe how to get the overall and detailed system status via SNMP. Therefore the following chapters show only a subset of all the information available in this MIB. Page 1 of 9
Getting the overall system status summary To get the overall system status summary issue the following command: snmptable -Cb -Cl -v 1 -c public localhost sc2statuscomponenttable snmptable -Cb -Cl -v 1 -c public localhost sc2statuscomponenttable SNMP table: FSC-SERVERCONTROL2-MIB::sc2StatusComponentTable UnitId StatusOverall StatusBoot StatusPowerSupply StatusTemperature StatusFans StatusVoltages StatusCpu... 1 ok ok ok ok ok ok ok snmptranslate -On FSC-SERVERCONTROL2-MIB::sc2StatusComponentTable.1.3.6.1.4.1.231.2.10.2.2.10.8.2 The following command line options were used: Cb for brief table headers. When not using this option then all table headers will be preceded with the text sc2. Cl for aligning the column data to the left v 1 for SNMP version 1 c public for the community public On for numerical output as OID Please note that although the option -Cb for brief table headers was used this table is too wide to fit onto the page and the column StatusMemoryModule was omitted. In the following sections you can find how to get more detailed information for each of the overall statuses shown above. Getting boot status details To get boot status details type in the following command: snmptable -Cb -Cl -v 1 -c public localhost sc2servertable snmptable -Cb -Cl -v 1 -c public localhost sc2servertable SNMP table: FSC-SERVERCONTROL2-MIB::sc2ServerTable UnitId PhysicalMemory LastBootResult CurrentBootStatus ShutdownCommand ShutdownDelay... 1 4096 os-boot-successful os-running unknown 0 snmptranslate -On FSC-SERVERCONTROL2-MIB::sc2ServerTable.1.3.6.1.4.1.231.2.10.2.2.10.4.1 Again this table is too wide to fit onto the page and so the columns UUID, PhysicalMemoryOs, UUIDWireFormat, OsPlatform and BiosVersion were omitted. Page 2 of 9
Getting the power supply status To get the power supply status type in the following command: snmptable -Cb -Cl -v 1 -c public localhost sc2powersupplytable An example output of this command is shown below: snmptable -Cb -Cl -v 1 -c public localhost sc2powersupplytable SNMP table: FSC-SERVERCONTROL2-MIB::sc2PowerSupplyTable psunitid pspowersupplynr PowerSupplyDesignation... PowerSupplyStatus pspowersupplyload pspowersupplynominal 1 1 "PSU" ok 24 300 snmptranslate -On FSC-SERVERCONTROL2-MIB::sc2PowerSupplyTable.1.3.6.1.4.1.231.2.10.2.2.10.6.2 Please note that this table is too wide to fit onto the page also and the column PowerSupplyIdentifier in the middle was omitted. Getting detailed temperature status To get the detailed temperature status type in the following command: snmptable -Cb -Cl -v 1 -c public localhost sc2temperaturesensortable snmptable -Cb -Cl -v 1 -c public localhost sc2temperaturesensortable SNMP table: FSC-SERVERCONTROL2-MIB::sc2TemperatureSensorTable UnitId SensorNr SensorDesignation SensorIdentifier SensorStatus CurrentTemperature WarningLevel 1 1 "Ambient" "Ambient" temperature-normal 26 37 1 2 "Systemboard" "Systemboard" temperature-normal 30 75 1 3 "CPU" "CPU" temperature-normal 37 95 1 4 "MEM A" "MEM A" temperature-normal 27 78 1 5 "MEM B" "MEM B" not-available 0 78 1 6 "PSU Inlet" "PSU Inlet" temperature-normal 27 60 1 7 "PSU" "PSU" temperature-normal 35 80 1 8 "BBU" "BBU" not-available 0 50 1 9 "RAID Controller" "RAID Controller" not-available 0 110 snmptranslate -On FSC-SERVERCONTROL2-MIB::sc2TemperatureSensorTable.1.3.6.1.4.1.231.2.10.2.2.10.5.1 Page 3 of 9
Getting detailed fan component status To get the detailed fan component status type in the following command: snmptable -Cb -Cl -v 1 -c public localhost sc2fantable snmptable -Cb -Cl -v 1 -c public localhost sc2fantable SNMP table: FSC-SERVERCONTROL2-MIB::sc2FanTable UnitId Nr Designation Identifier Status CurrentSpeed Quality FailReaction FailShutdownDelay CoolingDeviceType 1 1 "FAN1 SYS" "" ok 4560 102 continue 98 fan 1 2 "FAN2 SYS" "" ok 4440 98 continue 90 fan 1 3 "FAN3 SYS" "" ok 4980 101 continue 90 fan 1 4 "FAN4 SYS" "" ok 5160 98 continue 90 fan 1 5 "FAN PSU" "" ok 2640 100 continue 90 fan snmptranslate -On FSC-SERVERCONTROL2-MIB::sc2FanTable.1.3.6.1.4.1.231.2.10.2.2.10.5.2 Getting voltage status To get the detailed sensor voltage status type in the following command: snmptable -Cb -Cl -v 1 -c public localhost sc2voltagetable An example output of this command is shown below: snmptable -Cb -Cl -v 1 -c public localhost sc2voltagetable SNMP table: FSC-SERVERCONTROL2-MIB::sc2VoltageTable vounitid vosensornr VoltageDesignation VoltageStatus VoltageCurrentValue... VoltageMinimumLevel... 1 1 "BATT 3.0V" ok 3190 2020 1 2 "STBY 3.3V" ok 3330 3030 1 3 "irmc 1.8V STBY" ok 1780 1670 1 4 "irmc 1.5V STBY" ok 1500 1390 1 5 "irmc 1.0V STBY" ok 980 930 1 6 "MAIN 12V" ok 12540 11100 1 7 "MAIN 5V" ok 5210 4600 1 8 "MAIN 3.3V" ok 3330 3030 1 9 "MEM 1.35V" ok 1350 1250 1 10 "PCH 1.05V" ok 1040 970 1 11 "MEM VTT 0.68V" ok 670 630 snmptranslate -On FSC-SERVERCONTROL2-MIB::sc2VoltageTable.1.3.6.1.4.1.231.2.10.2.2.10.6.3 Again this table is too wide to fit onto the page and so the columns VoltageNominalValue, VoltageMaximumLevel and VoltageCurrentLoad were omitted. Page 4 of 9
Getting the CPU status To get the CPU status type in the following command: snmptable -Cb -Cl -v 1 -c public localhost sc2cputable snmptable -Cb -Cl -v 1 -c public localhost sc2cputable SNMP table: FSC-SERVERCONTROL2-MIB::sc2CPUTable UnitId Nr Designation Status ModelName Manufacturer Step CurrentSpeed... 1 1 "CPU" ok "Intel(R) Xeon(R) CPU E3-1280 v3 @ 3.60GHz" "Intel" "3" 3600 snmptranslate -On FSC-SERVERCONTROL2-MIB::sc2CPUTable.1.3.6.1.4.1.231.2.10.2.2.10.6.4 This table is much too wide also and therefore the columns NumberLogicals, CacheL1Size, CacheL2Size, CacheL3Size, NumberCores Family, EnabledCores, MultithreadingEnabled, ConfigurationStatus, MCDRAMSize, MCDRAMSpeed, MCDRAMMode, MCDRAMCacheSize and MCDRAMMemoryModel were omitted. Getting detailed memory module status To get the memory module status type in the following command: snmptable -Cb -Cl -v 1 -c public localhost sc2memorymoduletable snmptable -Cb -Cl -v 1 -c public localhost sc2memorymoduletable SNMP table: FSC-SERVERCONTROL2-MIB::sc2MemoryModuleTable UnitId ModuleNr ModuleDesignation ModuleStatus... ModuleCapacity... ModuleForm ModuleType... 1 1 "DIMM-2A" not-present -1 "" "" 1 2 "DIMM-1A" ok 4096 "UDIMM" "DDR3 / UDIMM" 1 3 "DIMM-2B" not-present -1 "" "" 1 4 "DIMM-1B" not-present -1 "" "" snmptranslate -On FSC-SERVERCONTROL2-MIB::sc2MemoryModuleTable.1.3.6.1.4.1.231.2.10.2.2.10.6.5 Page 5 of 9
Getting the system event log (SEL) table To get the system event log table type in the following command: snmptable -Cb -Cl -v 1 -c public localhost sc2messagetextlogtable An example output of this command is shown below: snmptable -Cb -Cl -v 1 -c public localhost sc2messagetextlogtable SNMP table: FSC-SERVERCONTROL2-MIB::sc2MessageTextLogTable UnitId Language SeqNr Timestamp Message... Severity... 1 1041 423 1484558819 "'DIMM-1A': Non Fujitsu Memory Module detected" minor 1 1041 424 1484558826 "BMC clock synchronized with system clock" informational 1 1041 425 1484562426 "BMC clock synchronized with system clock" informational 1 1041 426 1484562100 "ACPI Power State: soft-off (S5 - by override)" informational 1 1041 427 1484578819 "Operating system graceful shutdown" informational 1 1041 428 1484578826 "Operating system boot 16-Jan-2017 15:00:26" informational 1 1041 429 1484582426 "Boot from hard drive completed" informational 1 1041 430 1484582428 "BMC clock synchronized with system clock" informational 1 1041 431 1484591123 "BMC clock synchronized with system clock" informational 1 1041 432 1484591125 "BMC clock synchronized with system clock" informational 1 1041 433 1484602345 "BMC clock synchronized with system clock" informational 1 1041 434 1484603027 "'DIMM-1A': Non Fujitsu Memory Module detected minor 1 1041 435 1484613115 "BMC clock synchronized with system clock" informational 1 1041 436 1484613117 "BMC clock synchronized with system clock" informational 1 1041 437 1484624556 "'DIMM-1A': Non Fujitsu Memory Module detected minor 1 1041 438 1484624558 "BMC clock synchronized with system clock" informational 1 1041 439 1484624955 "BMC clock synchronized with system clock" informational... snmptranslate -On FSC-SERVERCONTROL2-MIB::sc2MessageTextLogTable.1.3.6.1.4.1.231.2.10.2.2.10.7.4 This table is again too wide and therefore the columns ErrorCode and CSSComponent have been omitted. It is usually also a very long table with over 1000 entries and the above ones only represent some example entries. Page 6 of 9
OS MIB Information The ServerView OS MIB is located at the OID 1.3.6.1.4.1.231.2.10.2.5.5: snmptranslate 1.3.6.1.4.1.231.2.10.2.5.5 SERVERVIEW-OPERATING-SYSTEM-MIB::svOperatingSystem This MIB contains tables and object groups which describe operating system specific properties. The following list gives an overview about the most important tables and their entries: svosagentinfo group: 1.3.6.1.4.1.231.2.10.2.5.5.1 A group of discrete objects containing information about the OS MIB agent itself, like agent ID, company name, version and build date svosinfotable: 1.3.6.1.4.1.231.2.10.2.5.5.2.2 Operating system designation, name, platform, manufacturer, version and kernel svospropertytable: 1.3.6.1.4.1.231.2.10.2.5.5.2.3 System time, start time, uptime, number of CPUs, available memory and number of processes svosclusterinfotable: 1.3.6.1.4.1.231.2.10.2.5.5.3.1 Wether this system is member of a cluster, the cluster name, IP address and the number of nodes svosclusternodetable: 1.3.6.1.4.1.231.2.10.2.5.5.3.2 List of cluster nodes containing their node number, name, state, description and IP addresses svosprocesstable: 1.3.6.1.4.1.231.2.10.2.5.5.4.1 List of operating system processes containing their process ID, name, description, path and version To get the contents of these tables you can again use the snmptable command. Here is an example output for the svosinfotable: snmptable -Cb -Cl -v 1 -c public localhost svosinfotable SNMP table: SERVERVIEW-OPERATING-SYSTEM-MIB::svOsInfoTable PartitionNumber Designation Name Platform Manufacturer VersionDesignation... 1 "Red Hat Enterprise Linux Server 6.8" linux x86-64 "Red Hat, Inc." "6.8" And again this table is too wide for the page, so some columns have been omitted again. Page 7 of 9
Status MIB Information The ServerView Status MIB is located at the OID 1.3.6.1.4.1.231.2.10.2.11: snmptranslate 1.3.6.1.4.1.231.2.10.2.11 SERVERVIEW-STATUS-MIB::sieStatusAgent It contains tables and object groups which describe the overall system status and the detailed status of subsystems and components. The following list gives an overview about the most important tables and their entries: siestagentinfo group: 1.3.6.1.4.1.231.2.10.2.11.1 A group of discrete objects containing information about the status MIB agent itself, like agent ID, company name, version and build date siestsystemstatus group: 1.3.6.1.4.1.231.2.10.2.11.2 A group of discrete objects showing the overall system status, last error message, list of subsystems and system identify LED status siestsubsystemtable: 1.3.6.1.4.1.231.2.10.2.11.3.1 A table containing all the subsystems with their subsystem name, status, last error message, list of components and display name siestcomponenttable: 1.3.6.1.4.1.231.2.10.2.11.4.1 A table containing the monitored system components with their component name, status, last error message and display name To get the contents of these tables you can again use the snmptable command. Here is an example output for the siestsubsystemtable: snmptable -Cb -Cl -v 1 -c public localhost siestsubsystemtable SNMP table: SERVERVIEW-STATUS-MIB::sieStSubsystemTable Number Name StatusValue... Components DisplayName 1 "Environment" ok "SvFans SvFanConfig SvTempSensors" "Environment Subsystem" 2 "PowerSupply" ok "SvPowerSupplies SvPowerLevel..." "Power Supply Subsystem" 3 "MassStorage" ok "SvMassStorageAdapters SvRaidAura..." "Mass Storage Subsystem" 4 "Systemboard" ok "SvVoltages SvMemModules SvCPUs SvBIOS..." "System Board Subsystem" 5 "Deployment" unknown "SvRemoteDeploy" "Deployment" 6 "Network" ok "SvNetworkAdapters" "Network" 7 "DrvMonitor" ok "SvMonitoredComponents" "Driver Monitor" This table is again too wide for the page, so some columns and list elements have been omitted again. Page 8 of 9
Tips and tricks If you want to work with SNMP OIDs rather than with symbolic names then you can use the command snmptranslate. For example if you want to translate the overall system status summary sc2statuscomponenttable into the respective OID and back you can do it as follows: snmptranslate -On FSC-SERVERCONTROL2-MIB::sc2StatusComponentTable.1.3.6.1.4.1.231.2.10.2.2.10.8.2 snmptranslate.1.3.6.1.4.1.231.2.10.2.2.10.8.2 FSC-SERVERCONTROL2-MIB::sc2StatusComponentTable The command line option On specifies that the output should be a numerical OID. Contact FUJITSU Fujitsu Technology Solutions GmbH Address: Mies-van-der-Rohe-Staße 8, 80807, Munich, Germany Phone: +49 (89) 62060-2981 Fax : +49 (89) 62060-49-2981 E-mail: Ken.Teuchler@ts.fujitsu.com Website: All rights reserved, including intellectual property rights. Technical data subject to modifications and delivery subject to availability. Any liability that the data and illustrations are complete, actual or correct is excluded. Designations may be trademarks and/ or copyrights of the respective manufacturer, the use of which by third parties for their own purposes may infringe the rights of such owner. For further information see ts.fujitsu.com/terms_of_use.html Copyright 2018 FUJITSU LIMI TED Page 9 of 9