Page 1 ® Intel NetStructure™ MPCMM0001 Chassis Management Module Software Technical Product Specification April 2005 Order Number: 273888-007 Download from Www.Somanuals.com. All Manuals Search And Download.
Page 2 Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order. Copies of documents which have an ordering number and are referenced in this document, or other Intel literature may be obtained by calling 1-800-548-4725 or by visiting Intel's website at http://www.intel.com.
Page 3: Table Of Contents
Contents Contents Introduction............................ 16 Overview..........................16 Terms Used in this Document .................... 16 Software Specifications ......................... 18 Red Hat* Embedded Debug and Bootstrap (Redboot) ............18 Operating System ....................... 18 Command Line Interface (CLI) ................... 18 SNMP/UDP......................... 18 Remote Procedural Call (RPC) Interface................19 RMCP ..........................
Page 4 Contents Late-BIST..........................33 QuickBoot Feature......................34 4.6.1 Configuring QuickBoot................... 34 Event Log Area and Event Management................35 OS Flash Corruption Detection and Recovery Design ............35 4.8.1 Monitoring the Static Images ................. 35 4.8.2 Monitoring the Dynamic Images ................36 4.8.3 CMM Failover ......................
Page 5 Contents Process Integrity Executable (PIE) ..................54 Configuring pms.ini ......................55 6.9.1 Global Data ......................55 6.9.2 Process Specific Data.................... 56 6.9.3 Process Definition Section of pms.ini..............58 6.10 Process Integrity Executable (PIE) Specific Data Config ........... 64 6.10.1 PIE Section Name ....................64 6.10.2 Process Integrity Executable .................
Page 6 Contents Resetting the Password......................... 99 Resetting the Password in a Dual CMM System ..............99 Resetting the Password in a Single CMM System ............100 Sensor Types ..........................101 10.1 CMM Sensor Types ......................101 10.2 Threshold-Based Sensors ....................101 10.2.1 Threshold-Based Sensor Events .................
Page 7 Contents 13.3.3 Resetting a Board ....................128 Electronic Keying Manager......................129 14.1 Point-to-Point EKeying......................129 14.2 Bused EKeying .........................129 14.3 EKeying CLI Commands ....................129 CDMs and FRU Information ......................130 15.1 Chassis Data Module......................130 15.2 FRU/CDM Election Process .....................130 15.3 FRU Information .......................130 15.4 FRU Query Syntax......................131 Fan Control and Monitoring ......................132 16.1...
Page 8 Contents 17.4 SNMP Trap Utility ......................160 17.4.1 Configuring the SNMP Trap Port ................. 160 17.4.2 Configuring the CMM to Send SNMP v3 Traps ........... 160 17.4.3 Configuring the CMM to Send SNMP v1 Traps ........... 160 17.5 Configuring and Enabling SNMP Trap Addresses............160 17.5.1 Configuring an SNMP Trap Address ..............
Page 9 Contents 20.5 RMCP Session Activation ....................191 20.6 RMCP Port Numbers ......................192 20.7 IPMB Slave Addresses .....................193 20.8 CMM RMCP Configuration ....................193 20.9 IPMI Commands Supported by CMM RMCP ..............194 20.10 Configuring IPMI Command Privileges ................196 20.10.1 Sample cmdPrivillege.ini file ................197 20.11 Completion Codes for the RMCP Messages ..............197 Command and Error Logging ......................199 21.1...
Page 10 Contents 23.17.1 Required Setup....................215 23.17.2 Update Procedure....................215 Updating Shelf Components......................217 IPMI Pass-Through........................218 25.1 Overview........................... 218 25.2 Command Syntax and Interface ..................218 25.2.1 Command Request String Format ............... 218 25.2.2 Response String ....................219 25.2.3 Usage Examples....................219 25.3 SNMP ..........................
Page 11 28.3.1 SNMP Trap Control .....................256 28.3.2 System Events— SEL Support ................256 28.3.3 Configuring SEL Format ..................257 Warranty Information ........................259 ® 29.1 Intel NetStructure™ Compute Boards and Platform Products Limited Warranty ...259 29.2 Returning a Defective Product (RMA) ................259 29.3 For the Americas ......................260 29.3.1 For Europe, Middle East, and Africa (EMEA) ............260...
Page 12 Contents 32.4 Taiwan Class A Warning Statement ................. 266 32.5 Japan VCCI Class A ......................266 32.6 Korean Class A......................... 266 32.7 Australia, New Zealand..................... 266 Safety Warnings .......................... 267 33.1 Mesures de Sécurité......................268 33.2 Sicherheitshinweise ......................270 33.3 Norme di Sicurezza ......................
Page 13 Contents 24 Dataitem Keywords for All Locations Except System ..............80 25 Dataitem Keywords for All Locations Except Chassis and System ..........81 26 Dataitem Keywords for Chassis Location ................... 85 27 Dataitem Keywords for Cmm Location ..................86 28 Dataitem Keywords for System Location..................92 29 Dataitem Keywords for FantrayN Location .................
Page 14 Contents 74 [FanTray/pem]FruTable/[fanTray/pem]FruEntry (1.3.6.1.4.1.343.2.14.2.10.[5/6].53.1) ... 157 75 [FanTray/pem]FruTargetTable/[fanTray/pem]FruTargetEntry (1.3.6.1.4.1.343.2.14.2.10.[5/6].54.1) ..................158 76 SNMP v3 Security Fields For Traps ..................162 77 SNMP v3 Security Fields For Queries ..................162 78 CMM State Transition Events and Event IDs ................166 79 CMM Status Sensor Data Bits ....................167 80 Error and Return Codes for the RPC Interface.................
Page 15 Contents Revision History Date Revision Description April 2005 Firmware version 5.2 August 2004 Firmware version 5.1.0.757 Version 5.1 TPS April 2004 Added Re-Enumeration Section Added Process Monitoring Section January 2004 004.1 Version 4.1 TPS MPCMM0001 Chassis Management Module Software Technical Product Specification Download from Www.Somanuals.com.
Page 16: Introduction
AdvancedTCA* PICMG* 3.0 platforms. This document details the software features and specifications of the CMM. For information on hardware features for the CMM refer ® to the Intel NetStructure™ MPCMM0001 Hardware Technical Product Specification. Links to specifications and other material can be found in Appendix B, “Data Sheet Reference.”...
Page 17 Introduction Table 1. Glossary (Sheet 2 of 2) Acronym Description IPMI Intelligent Platform Management Interface Light Emitting Diode Management Information Base RFC1213 - A standard Management Information Base for Network MIB II Management Power Entry Module PICMG PCI Industrial Computer Manufacturers’ Group RMCP Remote Management Control Protocol Remote Procedural Calls...
Page 18: Software Specifications
Under normal circumstances, Redboot runs through the standard diagnostics, memory setup, decompresses the OS kernel, and boots into that kernel. Operating System Linux* 4.0 on an Intel ® 80321 The CMM runs a customized version of embedded BlueCat ® ®...
Page 19: Remote Procedural Call (Rpc) Interface
Software Specifications Remote Procedural Call (RPC) Interface In addition to the console command-line interface, the CMM can be administered by custom remote applications via remote procedure calls (RPC). RPC is covered in Section 19, “Remote Procedure Calls (RPC)” on page 174.
Page 20: Clearing The Sel
Software Specifications Where location is one of {cmm, blade[1-14], fantray1, PEM[1-2]}. Even though the CMM uses a single flat SEL for system events, the ‘cmmget’ command will filter the SEL and only return events associated with the provided location. Also, some individual FRUs may keep their own local SELs (i.e., blades).
Page 21: Redundancy, Synchronization, And Failover
Redundancy, Synchronization, and Failover Redundancy, Synchronization, and Failover Overview The CMM supports redundant operation with automatic failover in a chassis using redundant CMM slots. In systems where two CMMs are present, one acts as the active shelf manager and the other as standby.
Page 22: Cmm Synchronization
Redundancy, Synchronization, and Failover failover is forced before all priority 1 data items are synchronized to the standby CMM, the standby CMM can still become the active CMM but may not be able to properly manage the FRUs in the chassis.
Page 23: Heterogeneous Synchronization
Redundancy, Synchronization, and Failover Table 2. CMM Synchronization (Sheet 2 of 2) File(s) or Data Description Path Priority Issues files Issues files Ethernet Recovery Action and escalation action for all /usr/local/cmm/temp/pmssync.ini the monitored processes except monitor Ethernet process Recovery action and escalation action for /usr/local/cmm/temp/pmsshadowsync.ini Ethernet monitor process...
Page 24: Synchronization Requirements
Redundancy, Synchronization, and Failover upgrade: Synchronizes user scripts only when the other CMM has a newer firmware version. downgrade: Synchronizes user scripts only when the other CMM has an older firmware version. always: Synchronizes user scripts irrespective of version differences. 3.3.2.2 Retrieving User Scripts Sync Configuration Flag To retrieve the value of the Scripts Synchronization configuration flag, the following CMM...
Page 25: Datasync Status Sensor
Redundancy, Synchronization, and Failover Datasync Status Sensor A sensor named “Datasync Status” exists in order to make the Datasync state information available to the user. This sensor tracks the status of the Datasync module and will make its status available through the various CMM interfaces.
Page 26 Redundancy, Synchronization, and Failover There is Priority 2 data to sync. No Data Synchronization problems known. Initial Data Synch Incomplete, Pri 1 Data Synced, Pri 2 Data Not Synched The current value is 0x0003 Initial Data Synchronization is not complete. Priority 1 data is synced.
Page 27: Sel Event
Redundancy, Synchronization, and Failover Priority 2 data is synced. Data Synchronization has encountered a problem in synchronizing data. Data Sync becomes normal after Data Sync failure The current value is 0x000f Initial Data Synchronization is complete. Priority 1 data is synced. Priority 2 data is synced.
Page 28: System Health
Redundancy, Synchronization, and Failover • When initial data synchronization is complete, the following SNMP trap is generated: [Month] [Date] [Time] [hostname] snmptrapd[xxxxx]: [IP Address]: Enterprise Specific Trap (25) Uptime: [Time], SNMPv2- SMI::enterprises.343.2.14.1.5 = STRING: "Time : [Day] [Month] [Date] [Time] [Year], Location : [location] , Chassis Serial # : [xxxxxxxx], Board : CMM[x] , Sensor : CMM[x]:Datasync Status , Event : Initial Data Synchronization is complete.
Page 29: Manual Failover
Redundancy, Synchronization, and Failover The active CMM will failover to the standby CMM if the active CMM cannot ping its first SNMP trap address (SNMPTrapAddress1) over any of the available Ethernet ports, but the standby CMM can. The trap address is set using the command: cmmset –l cmm –d snmptrapaddress1 –v [ip address] Only a ping failure of the first SNMP trap address (SNMPTrapAddress1) can cause a failover.
Page 30: Cmm Ready Event
Redundancy, Synchronization, and Failover CMM Ready Event The CMM Ready Event is a notification mechanism that informs the user when all CMM modules are fully up and running. The CMM is ready to process any request after receiving this event. The CMM uses the "CMM Status"...
Page 31: Built-In Self Test (Bist)
Built-In Self Test (BIST) Built-In Self Test (BIST) The CMM provides for a Built-In Self Test (BIST). The test is run automatically after power up. This test detects flash corruption as well as other critical hardware failures. Results of the BIST are displayed on the console through the serial port during boot time. Results of BIST are also available through the CLI if the OS successfully boots.
Page 32: Bist Flow Chart
Built-In Self Test (BIST) Figure 1. BIST Flow Chart Jump to run from RB image pass RB image FPGA image RB image fail Run from and backup and backup Power Up/ backup RB image FPGA image Reset checksum checksum backup FPGA NOT (backup image pass...
Page 33: Boot-Bist
Built-In Self Test (BIST) Boot-BIST The codes in Boot-BIST are executed at the very early stage of the RedBoot bootstrap, which is just before the FPGA programming and memory module initialization. Boot-BIST performs checksum checking over the RedBoot image and the FPGA image. A checksum error will be detected if there is a mismatch between the calculated checksum and the stored checksum in FIS directory.
Page 34: Quickboot Feature
Built-In Self Test (BIST) Figure 2. Timing of BIST Stages HAL initialization (processor, cache, serial port) Boot-BIST FPGA programming Memory parameters initialization Early-BIST Module initialization (flash, zlib, ide) Mid-BIST Module initialization (ethernet interface) Late-BIST Display copyright banner, and execute boot script Done QuickBoot Feature This feature will skip all the diagnostics tests in the mid-BIST and late-BIST, once it has been...
Page 35: Event Log Area And Event Management
Built-In Self Test (BIST) Execute extended memory test: true OS image checksum at boot: true Update RedBoot non-volatile configuration - are you sure (y/n)? y The default 'Enable QuickBoot during BIST' is true. When 'Enable QuickBoot during BIST' set to false, there will be two additional options displayed in the configuration menu.
Page 36: Monitoring The Dynamic Images
Built-In Self Test (BIST) 4.8.2 Monitoring the Dynamic Images For monitoring the dynamic images, the CMM leverages the corruption detection ability from the JFFS(2) flash file system. At OS start-up, the CMM executes an initialization script to mount the JFFS(2) flash partitions (/etc and /home). If a flash corruption is detected, an event is logged to the CMM SEL.
Page 37: Fpga Version Check
Built-In Self Test (BIST) value to the first test offset. It is then verified that the initial data value is still stored at every other power-of-two offset. If a location is found, other than the one just written, that contains the new data value, there is a problem with the current address bit.
Page 38: Ipmb Bus Busy/Not Ready Test
Built-In Self Test (BIST) 4.9.9 IPMB Bus Busy/Not Ready Test • The objective of the test is to identify any potential FPGA lockup before loading the BlueCat. When the FPGA is detected to be locked up, an event indicating which bus actually failed is logged into the Event log.
Page 39: Re-Enumeration
Re-enumeration Re-enumeration Overview The Chassis Management Module has the ability to re-enumerate devices in the chassis in the event that the chassis loses and then regains CMM management. This allows the CMM to query information on all devices in the chassis on startup if there are no active CMMs in that chassis already containing that information from which it can receive via a regular synchronization.
Page 40: Re-Enumeration Of M5 Fru
Re-enumeration Re-enumeration of M5 FRU If, during re-enumeration, the CMM discovers that a FRU is requesting for deactivation (State M5), it denies the request and informs the FRU to go back to Active (M4) state if there is no frucontrol script present (refer to Section 18.5, “FRU Control Script”...
Page 41: Process Monitoring And Integrity
Process Monitoring and Integrity Process Monitoring and Integrity Overview The Chassis Management Module monitors the general health of processes running on the CMM and can take recovery actions upon detection of failed processes. This is handled by the Process Monitoring Service (PMS). Upon detecting unhealthy processes, the PMS will take a configurable recovery action.
Page 42: Process Integrity Monitoring
Process Monitoring and Integrity watchdog monitoring is relatively lightweight and can be done every second, although, the process being monitored may dictate a (much) lower frequency depending on how often it is capable of feeding the watchdog. 6.1.3 Process Integrity Monitoring The Process Integrity Executable (PIE) will be responsible for determining the health of process or processes.
Page 43: Process Monitoring Dataitems
Process Monitoring and Integrity • PmsGlobal Target for PMS global data • PmsProc[#] Target for each process monitored • PmsPie[#] Target for each PMS PIE Use the following CLI command to view the targets for the processes being monitored. cmmget -l cmm -d listtargets The particular processes being monitored will be listed (e.g., PmsProc23, PmsProc100).
Page 44: Snmp Mib Commands
Process Monitoring and Integrity SNMP MIB Commands SNMP commands are implemented in the CMM mib for Process Monitoring. The list of new commands can be found in the CMMs MIB file or in Section 17, “SNMP” on page 140. Process Monitoring CMM Events The “Process Monitoring Service”...
Page 45: Failure Scenarios And Eventing
Process Monitoring and Integrity ProcessSeverity=3 Note: The recovery action and escalation action should not be set to "no action" for the xinetd process. This process is involved in data synchronization between the CMMs. Note: When a user tries to change the recovery action for cmd_hand or BPM to values other than allowed via the CLI API, the error string displayed is: "Recovery action not allowed for this target."...
Page 46: Successful Restart Recovery
Process Monitoring and Integrity Table 6. No Action Recovery Description Event String Assert Severity Process existence fault; PMS detects a faulty process. The attempting recovery or mechanism (existence, thread Thread watchdog fault; attempting watchdog, or integrity) used to detect Assert Configure recovery the fault will determine which of the...
Page 47: Successful Failover/Restart Recovery
Process Monitoring and Integrity 6.7.3 Successful Failover/Restart Recovery In this scenario PMS detects a process fault. The configured recovery action is: failover to the standby CMM and then restart the failed process. The PMS is able to successfully recover the process by restarting it.
Page 48: Successful Failover/Reboot Recovery
Process Monitoring and Integrity 6.7.4 Successful Failover/Reboot Recovery In this scenario, PMS detects a process fault. The configured recovery action is: failover to the standby CMM and upon successfully executing the failover, reboot the now standby CMM. The recovery actions are successful. Table 9.
Page 49: Failed Failover/Reboot Recovery, Critical
Process Monitoring and Integrity Table 10. Failed Failover/Reboot Recovery, Non-Critical Description Event String Assert Severity Process existence fault; PMS detects a faulty process. The attempting recovery or mechanism (existence, thread Thread watchdog fault; attempting watchdog, or integrity) used to detect Assert Configure recovery or...
Page 50: Excessive Restarts, Escalate No Action
Process Monitoring and Integrity Table 11. Failed Failover/Reboot Recovery, Critical Description Event String Assert Severity Process existence fault; PMS detects a faulty process. The attempting recovery or mechanism (existence, thread Thread watchdog fault; attempting watchdog, or integrity) used to detect Assert Configure recovery or...
Page 51: Excessive Restarts, Successful Escalate Failover/Reboot
Process Monitoring and Integrity Table 12. Existence Fault, Excessive Restarts, Escalate No Action (Sheet 2 of 2) Description Event String Assert Severity PMS detects that the process has Recovery failure due to excessive Configure been restarted excessively. restarts PMS attempts to execute the escalated recovery action.
Page 52: Excessive Restarts, Failed Escalate Failover/Reboot, Non-Critical
Process Monitoring and Integrity 6.7.9 Excessive Restarts, Failed Escalate Failover/Reboot, Non- Critical In this scenario PMS detects a process fault. The severity of the process is configured to a value that is not critical. The configured recovery action is: restart the process. However, the PMS also detects that the process has exceeded the threshold for excessive process restarts.
Page 53: Process Administrative Action
Process Monitoring and Integrity recovery action is unsuccessful (standby is not available, etc.). The process being monitored is of critical severity and therefore the reboot of the CMM will still be executed even though the CMM is still active. Table 15. Excessive Restarts, Failed Escalate Failover/Reboot, Critical Description Event String Assert...
Page 54: Excessive Failover/Reboots, Administrative Action
Process Monitoring and Integrity 6.7.12 Excessive Failover/Reboots, Administrative Action Prior to executing any failover/reboot the PMS will determine if the failover/reboot threshold has been exceeded. If it has, the PMS will be operationally disabled. When PMS is disabled, all process monitoring is halted.
Page 55: Configuring Pms.ini
Process Monitoring and Integrity Configuring pms.ini The pms.ini file is the Process Monitoring Service (PMS) and Process Integrity Exectuable (PIE) configuration file. It contains all of the non-volatile configuration data for the service. This file can be found in the /etc/cmm directory on the CMM. It is an ASCII based text file that can be edited with vi or any other text editor.
Page 56: Process Specific Data
Process Monitoring and Integrity ExcessiveRebootOrFailoverInterval = 21600 6.9.2 Process Specific Data This data applies to a specific process running on the CMM. There will be one set of this data for each process. The following information describes each of the fields in the process specific section. 6.9.2.1 Process Section Name The section name MUST follow the pattern "PmsProcessXXX"...
Page 57 Process Monitoring and Integrity space separated with the program name being the first entry in the string. If an individual argument contains spaces, the argument must be encapsulated in quotation marks. The program name and arguments will uniquely identify the entry. This means if the same program is started multiple times with different arguments, each of them will require a separate entry.
Page 58: Process Definition Section Of Pms.ini
Process Monitoring and Integrity 6.9.2.10 Process Severity An indicator for the importance of a given process. This severity will determine at what level SEL entries are generated and when reboots should occur on an active CMM. Values: 1 = minor, 2 = major, 3 = critical. Default: 1. ProcessSeverity = 1 6.9.2.11 Recovery Action...
Page 59 Process Monitoring and Integrity [PmsProcess002] UniqueID = 2 CommandLine = ./PmsMonitor shadow StartCommandLine = ./PmsMonitor shadow AdminState = 1 ProcessExistenceInterval = 2 ThreadWatchdogRetries = 5 ProcessRampUpTime = 5 ProcessSeverity = 2 RecoveryAction = 2 ProcessRestartEscalationAction = 1 ProcessRestartEscalationNumber = 10 ProcessRestartEscalationInterval = 4800 6.9.3.2 Monitor Process...
Page 60 Process Monitoring and Integrity 6.9.3.3 Chassis Wrapper Process [PmsProcess023] UniqueID = 23 CommandLine = ./WrapperProcess 23 StartCommandLine = ./WrapperProcess 23 AdminState = 1 ProcessExistenceInterval = 2 ProcessRampUpTime = 10 ProcessSeverity = 2 RecoveryAction = 2 ProcessRestartEscalationAction = 2 ProcessRestartEscalationNumber = 4 ProcessRestartEscalationInterval = 5400 6.9.3.4 CMM Wrapper Process...
Page 61 Process Monitoring and Integrity 6.9.3.5 SNMP [PmsProcess051] UniqueID = 51 CommandLine = /usr/sbin/snmpd -c /etc/snmpd.conf StartCommandLine = /usr/sbin/snmpd -c /etc/snmpd.conf AdminState = 1 ProcessExistenceInterval = 2 ProcessRampUpTime = 30 ProcessSeverity = 2 RecoveryAction = 2 ProcessRestartEscalationAction = 2 ProcessRestartEscalationNumber = 4 ProcessRestartEscalationInterval = 5400 6.9.3.6 CLI Server...
Page 62 Process Monitoring and Integrity as valid recovery actions for cmd_hand. The default recovery action for cmd_hand process is 4 (failover and reboot) and that cannot be changed to anything else. A recovery action of 1 (No Action) is also not allowed because of the severity of the process. In the event that cmd_hand process terminates unexpectedly, and the default recovery action kicks in, there is 2-3 minute delay before the CMM actually reboots.
Page 63 Process Monitoring and Integrity ProcessRestartEscalationAction = 2 ProcessRestartEscalationNumber = 5 ProcessRestartEscalationInterval = 300 6.9.3.9 Dynamic Wrapper Process 0-39 [PmsProcessXYZ] UniqueID = XYZ ChassisApplicability = MPCHC0001, ZT5091, MPCHC5091 CommandLine = /usr/local/cmm/bin/WrapperProcess N StartCommandLine = /usr/local/cmm/bin/WrapperProcess N AdminState = 1 ProcessExistenceInterval = 0 ProcessRampUpTime = 10 ProcessSeverity = 2 RecoveryAction = 2...
Page 64: Process Integrity Executable (Pie) Specific Data Config
Process Monitoring and Integrity ProcessSeverity = 2 RecoveryAction = 2 ProcessRestartEscalationAction = 2 ProcessRestartEscalationNumber = 5 ProcessRestartEscalationInterval = 300 6.9.3.11 Syslog Daemon [PmsProcess102] UniqueID = 102 CommandLine = /sbin/syslogd StartCommandLine = /sbin/syslogd AdminState = 1 ProcessExistenceInterval = 2 ProcessRampUpTime = 5 ProcessSeverity = 1 RecoveryAction = 2 ProcessRestartEscalationAction = 2...
Page 65: Process Integrity Executable
Process Monitoring and Integrity 6.10.2 Process Integrity Executable The name, including its path and command line arguments, of the PIE to be executed periodically. This is used to start the program and may, in the future, be used to monitor the program and therefore must be an exact match to how the program is represented in the OS.
Page 66: Process Integrity Interval
Process Monitoring and Integrity 6.10.5 Process Integrity Interval This is the interval in seconds between executions of the PIE. Values: 0 - 65535, where 0 indicates that the PIE only gets executed once. Default: 3600. ProcessIntegrityInterval = 3600 6.10.6 Chassis Applicability This is a list of chassis types on which this particular Pie should be run.
Page 67: Wp/Bpm Pie
Process Monitoring and Integrity 6.11 WP/BPM PIE The command line usage of PmsPieWp is: PmsPieWp [-s] [-d[NumberOfDynamicWrappersPerRun]] [-f SuccessiveFailureNumber] where: -s: check static wrappers (optional) -d: check dynamic wrappers and bpm threads (optional) Number of dynamic wrappers and bpm threads to check on each run (optional) Values: 0 - 100.
Page 68: Power And Hot Swap Management
Power and Hot Swap Management Power and Hot Swap Management The CMM is responsible for the management of FRU hot-swap activities. The CMM listens to FRU hot-swap SEL messages from IPMI devices and distributes power to each FRU after negotiating with the respective IPMI device fronting the FRU. The CMM also manages the shelf- wide power budget.
Page 69: Surprise Fru Extraction/Ipmi Failure
Power and Hot Swap Management Surprise FRU Extraction/IPMI Failure The CMM detects a surprise FRU extraction or a failure of the IPMI device fronting the FRU if a device previously in one of the M2-7 states reports a transition to the M2 state. If this scenario is detected, the CMM assumes one of three things has happened: •...
Page 70: Pinging Ipmi Controllers
Power and Hot Swap Management Pinging IPMI Controllers The following lists the values of time to delay and number of pings that the CMM uses to determine the state of a FRU. Table 18. Time to Delay and Number of Attempts Variable Description Value...
Page 71: The Command Line Interface (Cli)
Use Telnet to log into the CMM over an Ethernet connection, or use a terminal application or serial console over the RS-232 interface. See the Intel® NetStructure™ MPCMM0001 Hardware Technical Product Specification for electrical pinouts of the above interfaces.
Page 72: Initial Setup- Logging In For The First Time
The Command Line Interface (CLI) Initial Setup— Logging in for the First Time Logging in for the first time must be done through the serial port console to properly configure the Ethernet settings and IP addresses for the network. The username for the CMM is root. The default password is cmmrootpass. At the login prompt, enter the username: root When prompted for the password, enter: cmmrootpass The root password can be changed using the passwd command.
Page 73 The Command Line Interface (CLI) gateway, and thereby eth1:1, uncomment the two lines under the eth0 section of /etc/pump.conf and comment the two lines under the eth1 section of that file. Save the file and run the /etc/rc.d/ network reload script. Note: It is recommended that both CMMs use static IP addresses for all interfaces.
Page 74: Setip Interface Assignments When Bootproto="Static
The Command Line Interface (CLI) Table 19. SETIP Interface Assignments when BOOTPROTO=”static” Interface SETIP=1 SETIP=2 SETIP=Both Other Previous eth1 STATICIP1 STATICIP2 STATICIP1 Value eth1:1 disabled disabled STATICIP2 disabled 5. Add the NETMASK1 variable and set it to the appropriate netmask for STATICIP1 for your network.
Page 75: Setting A Hostname
The Command Line Interface (CLI) 4. Add the NETMASK2 variable and set it to the appropriate netmask for STATICIP2 for your network. The NETMASK2 variable needs to be correct to allow for true redundant operation. 5. Add the GATEWAY1 variable and set it to the appropriate value for the gateway for STATICIP1.
Page 76: Setting The Date And Time
The Command Line Interface (CLI) 8.3.4 Setting the Date and Time On the active CMM, use the date command in the CLI to view the current date and time for the CMM. To set the date and time on the CMM use the setdate command. The setdate command should use the following syntax: setdate “mm/dd/yyyy [timezone] hh:mm:ss”...
Page 77: Cli Command Line Syntax And Arguments
The Command Line Interface (CLI) CLI Command Line Syntax and Arguments The command line interface on the CMM supports two types of commands: cmmget and cmmset. cmmget is used to query for information, whereas cmmset is used to write information. There are man pages available on the CMM for these two commands.
Page 78: Target Parameter: -T
The Command Line Interface (CLI) Table 21. Location (-l) Keywords Keyword Function chassis Chassis specific information. The system fantray where N is the number of the fantray. For example, fantray1 refers to the single fantray in the MPCHC0001 shelf. fantrayN NOTE: fantray1 may also be referred to as blade15 in a 14 slot chassis or blade17 in a 16 slot chassis.
Page 79: Cmm Targets
The Command Line Interface (CLI) The following table shows the values target can be for the CMM location. Table 22. CMM Targets Keyword Description Brd Temp Board Temperature CPU Temp CPU Temperature FilterTrayTemp[1,2] Filter Tray Temperature Sensors CPU Core V CPU Core Voltage VBAT Battery Voltage...
Page 80: Dataitem Parameter: -D
The Command Line Interface (CLI) 8.4.5 Dataitem Parameter: -d The dataitem is the parameter, identified by target and/or location, that the user is getting or setting. The dataitem must be given for every CLI command. 8.4.5.1 Location Dataitem lists Table 23 through Table 29 list the valid dataitems for each location when no target is specified.
Page 81 The Command Line Interface (CLI) Table 25. Dataitem Keywords for All Locations Except Chassis and System (Sheet 1 of 4) Dataitem Description Get/Set CLI Get Output Valid Set Values "GetDeviceID: < interpreted string without label> Device ID = <Device ID> SDR Support = <device provides Device SDRs>...
Page 82 The Command Line Interface (CLI) Table 25. Dataitem Keywords for All Locations Except Chassis and System (Sheet 2 of 4) Dataitem Description Get/Set CLI Get Output Valid Set Values Set the FRU payload to do things like Cold Reset, Warm Reset, etc.
Page 83 The Command Line Interface (CLI) Table 25. Dataitem Keywords for All Locations Except Chassis and System (Sheet 3 of 4) Dataitem Description Get/Set CLI Get Output Valid Set Values Retrieves and sets power state of a blade. Get: This is used to find out the powered on/off or offline state of a blade Set: To reboot, shutdown and...
Page 84 The Command Line Interface (CLI) Table 25. Dataitem Keywords for All Locations Except Chassis and System (Sheet 4 of 4) Dataitem Description Get/Set CLI Get Output Valid Set Values Metallic Test Bus Pair #1: Token Owned: Yes/No Owner's IPMBAddress: IPMBAddress Metallic Test Bus Pair #2: Token Owned: Yes/No Owner's IPMBAddress: IPMBAddress...
Page 85 The Command Line Interface (CLI) Table 26. Dataitem Keywords for Chassis Location dataitem Description Get/Set CLI Get Output Valid Set Values A numerical value between 0 and 100 Used to get or set the fan (i.e., “70”), speed of all fans in the “localcontrol”, or The percentage of the max speed, chassis.
Page 86 The Command Line Interface (CLI) Table 27. Dataitem Keywords for Cmm Location (Sheet 1 of 7) Get/ dataitem Description CLI Get Output Valid Set Values All possible locations in the shelf e.g. “cmm blade1 blade2 blade3 blade4 blade5 blade6 blade7 Used to find out all the blade8 locations that can be queried.
Page 87 The Command Line Interface (CLI) Table 27. Dataitem Keywords for Cmm Location (Sheet 2 of 7) Get/ dataitem Description CLI Get Output Valid Set Values Retrieve or set the state of the Telco Alarm cutoff. When enabled, it silences the Telco alarm for active events and 1 = Set cut off blinks the event LEDs on the...
Page 88 The Command Line Interface (CLI) Table 27. Dataitem Keywords for Cmm Location (Sheet 3 of 7) Get/ dataitem Description CLI Get Output Valid Set Values "Front" or "Rear" or "Backplane". For example, bash-2.04# cmmget -d cmm1ethernetA cmm1ethernetA: front Used only with the CMM cmm1EthernetA bash-2.04# cmmget -d location to change the eth0/...
Page 89 The Command Line Interface (CLI) Table 27. Dataitem Keywords for Cmm Location (Sheet 4 of 7) Get/ dataitem Description CLI Get Output Valid Set Values 1=Enable 0=Disable Used to set or query SNMP snmpenable Both SNMP traps are <enabled/disabled>. trap enabled status. enable disable Get or Set the machine’s IP...
Page 90 The Command Line Interface (CLI) Table 27. Dataitem Keywords for Cmm Location (Sheet 5 of 7) Get/ dataitem Description CLI Get Output Valid Set Values Gets/Sets whether the LED syncuserledstate state is synced between the Both "Yes" or "No" “Yes” or “No” active and standby CMM.
Page 91 The Command Line Interface (CLI) Table 27. Dataitem Keywords for Cmm Location (Sheet 6 of 7) Get/ dataitem Description CLI Get Output Valid Set Values Used to set or query the adminstrative state of the PMS as a whole or an individual monitored process.
Page 92 The Command Line Interface (CLI) Table 27. Dataitem Keywords for Cmm Location (Sheet 7 of 7) Get/ dataitem Description CLI Get Output Valid Set Values Used to request to reboot the 1 - Request to standbycmmreboot standby CMM from the active reboot the standby CMM.
Page 93 The Command Line Interface (CLI) Table 29. Dataitem Keywords for FantrayN Location Get/ dataitem Description CLI Get Output Valid Set Values Any value between Used to set or query the the normallevel and minorlevel Both minorlevel for the fantray. the majorlevel of the fantray.
Page 94 The Command Line Interface (CLI) Table 30. Dataitem Keywords Used with the Target Parameter (Sheet 1 of 4) Get/ dataitem Description CLI Get Output Valid Set Values Listing of all valid data items that can Lists the available dataitems for listdataitems be issued for the specified location that target.
Page 95 The Command Line Interface (CLI) Table 30. Dataitem Keywords Used with the Target Parameter (Sheet 2 of 4) Get/ dataitem Description CLI Get Output Valid Set Values Used to configure user-defined actions when events occur. This dataitem is used with a target (–t) parameter specified sensor and a value (-v) parameter.
Page 96 The Command Line Interface (CLI) Table 30. Dataitem Keywords Used with the Target Parameter (Sheet 3 of 4) Get/ dataitem Description CLI Get Output Valid Set Values "<ledtarget> is in <LEDmode> mode <function message>" where <LEDMode> is one of localcontrol/ override/ lamptest Gets or Sets a FRU LED’s state.
Page 97: Value Parameter: -V
The Command Line Interface (CLI) Table 30. Dataitem Keywords Used with the Target Parameter (Sheet 4 of 4) Get/ dataitem Description CLI Get Output Valid Set Values Get/Set the field in the CDM regarding the max external available current. Only used with the feedN target.
Page 98 The Command Line Interface (CLI) The filename should refer to a file that is in a valid directory (i.e. /home/cmmdump.txt).The file can then be retrieved off the CMM using FTP (see Section 8.3.7, “FTP into the CMM” on page 76). MPCMM0001 Chassis Management Module Software Technical Product Specification Download from Www.Somanuals.com.
Page 99: Resetting The Password
It may become necessary at some point to reset the CMM password to its default of cmmrootpass. The CMM has one on board dip switch labeled S2-1 to perform this action. Refer to the Intel® NetStructure™ MPCMM0001 Hardware Technical Product Specification for the location of the switch.
Page 100: Resetting The Password In A Single Cmm System
Resetting the Password Resetting the Password in a Single CMM System For nonredundant systems that contain only a single CMM, resetting the password will require removing the CMM. This will cause any boards that are power controlled by the CMM become unmanaged.
Page 101: Sensor Types
For more information on sensors and sensor types, refer to the “Intelligent Platform Management Interface Specification v1.5”, available on http://www.intel.com. 10.2 Threshold-Based Sensors Threshold-based sensors are sensors that generate or change an event status based on comparing a current value to a threshold value for a given hardware monitor device.
Page 102: Cmm Voltage/Temp Sensor Thresholds
Sensor Types 10.3 CMM Voltage/Temp Sensor Thresholds Table 31 shows the threshold sensors present on the CMM with the Upper Non-Recoverable, Upper Critical, Upper Non-Critical, Lower Non-Critical, Lower Critical, and Lower Non- Recoverable thresholds for each sensor. UseTable 34 on page 109 to determine the severity for an event that crosses a specific threshold on a sensor.
Page 103: Discrete Sensor Events
Sensor Types 10.4.1 Discrete Sensor Events Discrete sensors can generate events on state changes for various sensors in the system. The severity of the event is determined by the CMM. MPCMM0001 Chassis Management Module Software Technical Product Specification Download from Www.Somanuals.com. All Manuals Search And Download.
Page 104: Health Events
Health Events Health Events This section describes the health events that are associated with CMM events and includes the syntax and severity of these strings. Refer to Section 10, “Sensor Types” on page 101 for more information on the different type of sensors. Note: For this section, “health event”...
Page 105: Sel Sensor Types
Health Events \t[SDR Sensor Name]\t[Health Event String]: [Event Type]\n\n • Timestamp is in the format: [Day] [Month] [Date] [HH:MM:SS] [Year]. For example, Thu Dec 11 22:20:03 2003 • SDR Sensor Name is the name given to the sensor in the Sensor Data Record (SDR). •...
Page 106: Sensor Targets
Health Events • Timestamp is in the format: [Day] [Month] [Date] [HH:MM:SS] [Year]. For example, Thu Dec 11 22:20:03 2003 • ChassisLocation is the chassis location information recorded in the chassis FRU. • ChassisSN is the chassis serial number records in the chassis FRU. •...
Page 107: Healthevents Queries
Health Events Table 33. Sensor Targets (Sheet 2 of 2) Sensor Target Description Air Filter Air Filter Sensor Filter Tray Filter Tray Sensor Filter Run Time Filter Tray Run Time Sensor BIST BIST Sensor CMM Status CMM Status Sensor DataSync Status Datasync Sensor FRU Hot Swap FRU Hot Swap Sensor...
Page 108: Healthevents Queries For All Sensors On A Location
Health Events 11.3.2 HealthEvents Queries for All Sensors on a Location Executing a healthevents query on the “cmm” location in the CLI without a target specified (cmmget -l cmm -d healthevents) returns all the healthevents for all CMM sensors in a concatenated string.
Page 109: All Locations
Health Events The table for threshold-based sensors is common to other threshold-based sensors on other components, e.g., voltage, temp, current). 11.4.1 All Locations Table 34. Threshold-Based Sensors: Voltage, Temp, Current, Fan Event Code Event String Event Severity Decimal "Lower non-critical going low asserted" 0x010 Minor "Lower non-critical going high asserted "...
Page 110 Health Events Table 35. Hot Swap Sensor: Filter Tray HS, FRU Hot Swap Event Code Event String Event Severity Decimal “[FRU] transitioned from [M0-M7] to [M0-M7] Due to Normal State Major (if M0-M0) Change: [Asserted,Deasserted]” else OK “[FRU] transitioned from [M0-M7] to [M0-M7] Due to Unknown Major (if M0-M0) Reasons: [Asserted,Deasserted]”...
Page 111 Health Events Table 37. System Firmware Progress Event Strings (System Firmware Progress) Event Code Event String Event Severity Decimal "System Firmware Error: Unspecified error occurred" 0x050 "System Firmware Error: No system memory installed" 0x251 Major "System Firmware Error: No usable system memory found" 0x252 Major "System Firmware Error: Unrecoverable hard disk/ATAPI/IDE...
Page 112 Health Events Table 37. System Firmware Progress Event Strings (System Firmware Progress) Event Code Event String Event Severity Decimal "System Firmware Progress: Enabling docking station” 0x26F "System Firmware Progress: Docking station ejection” 0x270 "System Firmware Progress: Disabling docking station” 0x271 "System Firmware Progress: Calling OS wake-up vector”...
Page 113 Health Events Table 37. System Firmware Progress Event Strings (System Firmware Progress) Event Code Event String Event Severity Decimal "System Firmware Hang: User-initiated system setup” 0x465 1125 Major "System Firmware Hang: USB resource configuration” 0x466 1126 Major "System Firmware Hang: PCI resource configuration” 0x467 1127 Major...
Page 114 Health Events Table 38. Watchdog 2 Sensor Event Strings (Sheet 2 of 2) Event Code Event String Event Severity Decimal "None interrupt type BIOS FRB2 timer” 0x355 "None interrupt type BIOS/POST timer” 0x356 "None interrupt type OS Load timer” 0x357 "None interrupt type SMS/OS timer”...
Page 115: Cmm Location
Health Events 11.4.2 CMM Location Table 39. CMM Redundancy Event Code Event String Event Severity Decimal "Regained" 0x0D0 "Established" 0x0D1 "Lost due to switch failure" 0x0D2 Major "Lost due to unhealthy signal" 0x0D3 Major "Lost due to CMM removal" 0x0D5 Major "Lost due to CMM reboot or halt"...
Page 116 Health Events Table 41. CMM Failover (Sheet 2 of 2) Event Code Event String Event Severity Decimal “Failover cannot occur because the other CMM is not 0x0E3 responding over its management bus.” “Failover cannot occur because the critical items have not been 0x0E4 synced.”...
Page 117 Health Events Table 42. CMM Synchronization (Sheet 2 of 2) Event Code Event String Event Severity Decimal “Could not copy the FRU manager information to the standby 0x0FB CMM.” “Could not copy the IPMB state information to the standby 0x0FC CMM.”...
Page 118 Health Events Table 43. BIST Event Strings (Sheet 2 of 2) Event Code Event String Event Severity Decimal “Update of /etc failed.” 0x0A4 Critical “Restore of /etc files failed.” 0x0A5 Critical “Software update failed.” 0x0A6 Critical “FPGA re-programmed 2 times and no further lockup detected.” 0x0B4 Minor “FPGA re-programmed 3 times and no further lockup detected.”...
Page 119 Health Events Table 46. CMM Status Event Strings (CMM Status) Event Code Event String Event Severity Decimal “CMM is Active” 0x402 1026 “CMM is Standby” 0x403 1027 “CMM ready timed out” 0x404 1028 Minor Table 47. Process Monitoring Service Fault Event Strings (PMS Fault) Event Code Event String Event Severity...
Page 120: Chassis Location
Health Events Table 48. Process Monitoring Service Info Event Strings (PMS Info) Event Code Event String Event Severity Decimal "Take no action specified for recovery" 0x0179 User-Configurable "Attempting process restart recovery action" 0x017A User-Configurable "Attempting process failover & restart recovery action" 0x017B User-Configurable "Attempting process failover &...
Page 121: Configuring Ipmi Error Completion Codes
Health Events Table 50. IPMI Error Completion Codes and Enumerations Code Error Message “Node Busy” “Invalid Command” "Command Invalid for Given LUN" "Timeout while processing command" “Out of space” "Reservation Canceled or Invalid Reservation ID" "Request Data Truncated" "Request Data Length Invalid" "Request Data Field Length Limit Exceeded"...
Page 122 Health Events "IMB ERROR Completion Code Error" When “IMBErrorCodeReporting” is set to 1 in /etc/cmm.cfg, then the following message will be displayed: IMB ERROR Completion Code Error: [IPMI Error Code] : [Error String] Where: IPMI Error Code: Ascii String of the IPMI error code returned in the IPMI response. The IPMI codes are listed in Table 50, “IPMI Error Completion Codes and Enumerations”...
Page 123: Front Panel Leds
• One CMM HotSwap State LED • Four User-Definable LEDs (A-D) For more information on CMM LEDs refer to the Intel® NetStructure™ MPCMM0001 Hardware Technical Product Specification. 12.1 LED Types and States The CMM can retrieve and, in some cases, set values for LEDs on the CMM, fan trays, PEMs, and blades in the chassis.
Page 124: Health Led
Front Panel LEDs 12.1.2 Health LED Each CMM maintains a single health LED ( ) to provide the status of the CMM. Table 52. CMM Health LED States Color Description No power to CMM Solid Green Normal operation, power okay Blinking Green CMM in standby mode Solid Red...
Page 125: Retrieving The State Of Leds
Front Panel LEDs 12.4 Retrieving the State of LEDs The state of an LED on a location can be retrieved using the command: cmmget -l [location] -t [LED] -d ledstate 12.5 Setting the State of the User LEDs The state of the User LEDs on the CMM or other FRUs can be changed using the ledstate set command.
Page 126: Led Boot Sequence
Front Panel LEDs 12.6 LED Boot Sequence During the boot process, the user LEDs will change in a pattern, as described in Table 55, “LED Event Sequence”, to indicate boot progress. The user LEDs will be off by the time the CMM software is fully loaded.
Page 127: Node Power Control
Node Power Control Node Power Control The CMM controls power to the nodes of a chassis. The CMM can power up, power down, and reset a board in a particular slot and can be used to query the operational state of a board at any time.
Page 128: Resetting A Board
Node Power Control 13.3.3 Resetting a Board The following command will reset a board: cmmset -l bladeN -d powerstate -v reset N is the number of the physical slot where the blade to be reset resides. Once issued, the command will ask for confirmation by entering “y”...
Page 129: Electronic Keying Manager
Electronic Keying Manager Electronic Keying Manager Electronic Keying (EKeying) is used in the AdvancedTCA* architecture to dynamically implement a specific fabric interconnect in a fabric agnostic backplane. The PICMG* 3.0 specification calls out two types of EKeying: point-to-point and bused. 14.1 Point-to-Point EKeying Point-to-point EKeying is used to set up a specific fabric interconnect and protocol between two...
Page 130: Cdms And Fru Information
CDMs and FRU Information CDMs and FRU Information 15.1 Chassis Data Module There are two chassis data modules (CDMs) in a chassis for redundancy.Each CDM has 2 EEPROMs containing the FRU information for the chassis. The CDM FRU data is also cached on the CMMs at boot time.
Page 131: Fru Query Syntax
CDMs and FRU Information 15.4 FRU Query Syntax The format for querying the FRU of a particular location is: cmmget -l [location] -t fru -d [dataitem] Where location is the component for which the FRU information is to be retrieved from, and dataitem is the field(s) of the FRU which will be retrieved.
Page 132: Fan Control And Monitoring
Fan Control and Monitoring Fan Control and Monitoring The CMM controls the fan speeds and the fan tray LEDs. In a healthy state (no events), the LED is driven to green color. If any of the fan tray sensors (temperature, voltages, fan tachs) are in an unhealthy state, the LED is driven to red or amber (red by default).
Page 133: Cmm Cooling Table
Fan Control and Monitoring statuses. At any moment the Cooling Manager can only operate at one temperature status, it is called the current temperature status. The four temperature statuses are normal, minor, major and critical. The Cooling Manager changes its current temperature status depending on what, if any, temperature events it has received.
Page 134: Control Modes For Fan Trays
Fan Control and Monitoring The number of the fan tray being addressed. These values will take effect immediately after they are entered. That means that if fantrayN’s current temperature status is normal and the user sets the normallevel the current cooling level will change immediately.
Page 135: User Initiated Mode Change
Fan Control and Monitoring modes. The user may change to this mode with the following command: cmmset –l fantrayN -d control –v emergencyshutdown Where: The number of the fan tray being addressed. 16.6.4 User Initiated Mode Change To change the control mode of a fantray, the user may use the command: cmmset –l fantrayN -d control –v [ CMM | fantray | EmergencyShutdown | defaultcontrol] The number of the fan tray being addressed.
Page 136: Fantray Properties
Fan Control and Monitoring 16.8 Fantray Properties There are also commands to retrieve the fantray’s settings. These properties are maximum cooling level, minimum cooling level and recommended cooling level. The cooling manager gets the fan speed properties by performing an IPMI get fantray properties call on the fantray. This method is defined by the PICMG 3.0 specification.
Page 137: Default Cooling Values
Fan Control and Monitoring 16.11 Default Cooling Values The CMM determines the fan tray cooling values from the /etc/cmm/fantray.cfg file. The CMM uses the defaults from the file in the following order of precedence: 1. User Defaults 2. Vendor Defaults 3.
Page 138: Structure Of /Etc/Cmm/Fantray.cfg
Fan Control and Monitoring 16.11.2 Structure of /etc/cmm/fantray.cfg All default values will persist in the /etc/cmm/fantray.cfg file. These will be stored in key=value pairings. These are the formats of those entries in the /etc/cmm/fantray.cfg file. Example 2. Sample /etc/cmm/fantray.cfg file 0157.870.minorlevel=76 0157.870.normallevel=72 0157.870.control=fantray...
Page 139: Chassis Vs. Fantray
Fan Control and Monitoring it can determine when a firmware upgrade/downgrade would affect the user defaults. When a fan tray is inserted into the chassis the Cooling Manager checks the /etc/cmm/fantray.cfg to see if there are recorded minimum and maximum values for that fan tray at that location. It will compare the recorded minimum and maximum to the minimum and maximum values that the inserted fan tray returns.
Page 140: Snmp
SNMP SNMP The CMM supports v1 and v3 of the Simple Network Management Protocol (SNMP). The CMM can support SNMP queries and send SNMP traps in either v1 or v3. The SNMP interface on the CMM very closely mirrors that of the CLI in both syntax and function. Note: Like the CLI, SNMP commands should be issued to the active CMM.
Page 141: Cmm Mib
Table 58. MIB II Objects - System Group Object Syntax Access Value “Linux mpcmm0001 2.4.2-1 #156 [DATE] armv5” sysDscr DisplayString read-only Date is the actual current date. iso(1).org(3).dod(6).internet(1).private(4).e OBJECT nterprises(1).intel(343).products(2).Server- sysObjectID read-only IDENTIFIER Management(10).Chassis- Management(3).mpcmm0001(2) sysContact DisplayString read-write max. 128 bytes sysName DisplayString read-write Default:”mpcmm0001”...
Page 142: Cmm Mib Objects
SNMP Figure 4. CMM Custom MIB Tree CMM Custom MIB Tree iso(1) org(3) dod(6) internet(1) directory(1) mgmt(2) experimental(3) private(4) security(5) snmpV2(6) enterprises(1) Intel (343) products(2) chassisManagement(14) mpcmm0001(2) sensorLocation(10) system(1) pems(6) shelf(2) cmm(3) fanTrays(5) blades(4) blade1(1) blade2(2) ..blade16(16) 17.2.2 CMM MIB Objects All the objects below can be found in the mpcmm0001.mib file.
Page 143 SNMP Table 60. System Location (1.3.6.1.4.1.343.2.14.2.10.1) Object Syntax Access Value Health information about a particular systemHealth INTEGER read-only location. This will be one of the following: (0-OK, 1-Minor, 2-Major, 3-Critical) Used with the System location to find out systemUnhealthyLocation DisplayString read-only what blades are having problems.
Page 144 SNMP Table 61. Shelf Location (Equivalent to Chassis) (1.3.6.1.4.1.343.2.14.2.10.2) Object Syntax Access Value Used to find out what targets are shelfListTargets DisplayString read-only available on a location. (e.g., Getting the list of sensors in the chassis). Used to find out what data items are shelfListDataItems DisplayString read-only...
Page 145 SNMP Table 62. ShelfTable/shelfEntry (1.3.6.1.4.1.343.2.14.2.10.2.50.1) (Sheet 2 of 2) Object Syntax Access Value Used to read the Board Manufacture shelffruBoardManufactureDate DisplayString read-only Date from the FRU. Used to read the Product Description shelffruProductDescription DisplayString read-only from the FRU. Used to read the Product shelffruProductManufacturer DisplayString read-only...
Page 146 SNMP Table 63. Cmm Location (1.3.6.1.4.1.343.2.14.2.10.3) (Sheet 1 of 3) Object Syntax Access Value softwareVersion DisplayString read-only The version of the CMM software. cmmRedundancy DisplayString read-only cmm redundancy information. Enable or disable the RMCP Service: rmcpEnabled INTEGER read-write disable(0), enable(1) Get the Ekeys that have been granted cmmGrantedBoardEkeys DisplayString read-only...
Page 147 ATCA-defined M state of the location. Settable value:reset, poweron, poweroff cmmFeedCount DisplayString read-only Get the power feed count This is an Intel extension command for PICMG 3.0. Used to notify the Shelf cmmFRUExtractionNotify INTEGER write Manager that a FRU has been extracted from the shelf.
Page 148 SNMP Table 63. Cmm Location (1.3.6.1.4.1.343.2.14.2.10.3) (Sheet 3 of 3) Object Syntax Access Value Perform the CMM firmware update. The set value is in the following format: cmmUpdate DisplayString write <cmm image location> ftp:<hostname or IP address>:username:password. This allow the user to set the runtime to cmmResetAirFilterRuntime INTEGER write...
Page 149 SNMP Table 64. CmmTable/cmmEntry (1.3.6.1.4.1.343.2.14.2.10.3.51.1) (Sheet 1 of 2) Object Syntax Access Value cmmTarget DisplayString none index cmmCurrent DisplayString read-only The current value of a sensor. cmmThresholdsAll DisplayString read-only All thresholds of a sensor. cmmUpperCritical DisplayString read-only Upper critical thresholds cmmUpperNonCritical DisplayString read-only...
Page 150 SNMP Table 64. CmmTable/cmmEntry (1.3.6.1.4.1.343.2.14.2.10.3.51.1) (Sheet 2 of 2) Object Syntax Access Value Used to read the Product Serial cmmfruProductSerialNumber DisplayString read-only Number from the FRU. cmmfruProductManufactureD Used to read the Product Manufacture DisplayString read-only Date from the FRU. Used to read the Product Model from cmmfruProductModel DisplayString read-only...
Page 151 SNMP Table 65. CmmFruTable/cmmFruEntry (1.3.6.1.4.1.343.2.14.2.10.3.52.1) Object Syntax Access Value cmmFruNumber INTEGER none index Retrieve the hot swap state of the FRU from the CMM’s internally known hot cmmFruHotSwapState DisplayString read-only swap states. Returns M state number (0-7) cmmFruLedProperties DisplayString read-only Find out what LEDs the FRU supports.
Page 152 SNMP Table 67. CmmPmsTable/cmmPmsEntry (1.3.6.1.4.1.343.2.14.2.10.3.54.1) (Sheet 2 of 2) Object Syntax Access Value The process escalation action defines how cmmPmsEscalationActio a faulty process that fails to restart will be DisplayString read-write recovered. Possible values: 1-No Action, 2- Failover and Reboot. Display the monitored process' name and cmmPmsProcessName DisplayString read-only...
Page 153 SNMP Table 68. Blade# Location (1.3.6.1.4.1.343.2.14.2.10.4.[1-16]) Object Syntax Access Value b#TotalFrus DisplayString read-only Displays the total number of FRUs Used to send any IPMI command to this b#IPMICommandRequest DisplayString read-write location. Used to read the response to the above b#IPMICommandResponse DisplayString read-write IPMI command.
Page 154 SNMP Table 69. Blade#TargetTable/blade#TargetEntry (1.3.6.1.4.1.343.2.14.2.10.4.[1-16].51.1) (Sheet 2 of 2) Object Syntax Access Value Used to read the Product Description b#fruProductDescription DisplayString read-only from the FRU. Used to read the Product Manufacturer b#fruProductManufacturer DisplayString read-only from the FRU. Used to read the Product Part Number b#fruProductPartNumber DisplayString read-only...
Page 155 SNMP Table 71. Blade#FruTargetTable/blade#FruTargetEntry (1.3.6.1.4.1.343.2.14.2.10.4.[1-16].53.1) Object Syntax Access Value b#FruNumber INTEGER none Index 1 b#Target DisplayString none Index 2 Finds out what colors are supported b#FruLedColorProps DisplayString read-only by the LED. b#FruLedState DisplayString read-write Get/Set the FRU LED state. Table 72. [FanTray/pem]Table/[fanTray/pem]Entry (1.3.6.1.4.1.343.2.14.2.10.[5/6].51.1) Object Syntax Access...
Page 156 SNMP Table 72. [FanTray/pem]Table/[fanTray/pem]Entry (1.3.6.1.4.1.343.2.14.2.10.[5/6].51.1) Object Syntax Access Value fanTrayMaximumSetting DisplayString read-only The fantray's maximum setting. fanTrayRecommendedSetting DisplayString read-only The fantray's recommended setting. fanTrayCurrentFanLevel DisplayString read-only The fantray's current fan level. Table 73. [FanTray/pem]TargetTable/[fanTray/pem]TargetEntry (1.3.6.1.4.1.343.2.14.2.10.[5/ 6].52.1) (Sheet 1 of 2) Object Syntax Access...
Page 157 SNMP Table 73. [FanTray/pem]TargetTable/[fanTray/pem]TargetEntry (1.3.6.1.4.1.343.2.14.2.10.[5/ 6].52.1) (Sheet 2 of 2) Object Syntax Access Value [fanTray/ Used to read the Product Description DisplayString read-only pem]fruProductDescription from the FRU. [fanTray/ Used to read the Product DisplayString read-only pem]fruProductManufacturer Manufacturer from the FRU. [fanTray/ Used to read the Product Part DisplayString...
Page 158: Snmp Agent
SNMP Table 75. [FanTray/pem]FruTargetTable/[fanTray/pem]FruTargetEntry (1.3.6.1.4.1.343.2.14.2.10.[5/6].54.1) Object Syntax Access Value [fanTray/pem]Number INTEGER none index 1 [fanTray/pem]FruNumber INTEGER none index 2 [fanTray/pem]Target DisplayString none index 3 Finds out what colors are supported [fanTray/pem]FruLedColorProps DisplayString read-only by the LED. [fanTray/pem]FruLedState DisplayString read-write Get/Set the FRU LED state. 17.3 SNMP Agent The SNMP agent (snmpd) listens to SNMP v1 queries (gets/sets) by default, evokes the...
Page 159: Configuring The Agent Back To Snmp V1
SNMP 3. Look for the snmpd process. There may be more than one, so use the lowest process ID, which is the first instance of the process. The listing will look similar to this: 121 ? 0:00 /usr/sbin/snmpd -c /etc/snmpd.conf 4.
Page 160: Snmp Trap Utility
SNMP 3. Restart SNMP agent Method 2: Use the 'snmpusm' utility from a Redhat* Linux* host which has net-snmp packet install. You can find the usage under http://www.net-snmp.org. 17.4 SNMP Trap Utility The SNMP trap utility is utilized by the CMM Management software to send SNMP trap messages to a remote application regarding any abnormal system events.
Page 161: Configuring An Snmp Trap Address
SNMP 17.5.1 Configuring an SNMP Trap Address To configure an SNMP trap address, issue the command: cmmset -l cmm -d SNMPTrapAddressN -v [IP address] where N is the number of the trap address from 1 to 5 that is being set, and IP address is the IP address of the trap receiver.
Page 162: Snmp Security
SNMP 17.6 SNMP Security 17.6.1 SNMP v1 Security SNMP version 1 utilizes the community name for authentication. If the SNMP manager/client sends a request message containing the community name that doesn’t match the community name set in the SNMP Agent, the SNMP agent will respond with the authentication failure message. This community name is not encrypted during transmission.
Page 163: Snmpd.conf File
SNMP 17.8 Snmpd.conf File For more information regarding SNMP configuration and the snmpd.conf file, please visit: http://www.net-snmp.org/man/snmpd.conf.html MPCMM0001 Chassis Management Module Software Technical Product Specification Download from Www.Somanuals.com. All Manuals Search And Download.
Page 164: Cmm Scripting
CMM Scripting CMM Scripting 18.1 CLI Scripting In addition to calling the CLI directly, commands can easily be called through scripts using “bash” shell scripting. These scripts could be tailored to create a single command from several CLI commands or to give more detailed information. For example, you may want to display all of the fans and their speeds on the server.
Page 165: Listing Scripts Associated With Events
CMM Scripting Script is the script file or executable in the /home/scripts directory to be run including parameters to be sent to the script. The script and parameters should be enclosed in quotes. The script parameter should not include the /home/scripts path. Note: If applicable, remember to set a script for when a sensor returns to normal (NormalAction).
Page 166: Setting Event Action Scripts
CMM Scripting 18.3.2 Setting Event Action Scripts Setting event action scripts can be done using any of the standard CMM interfaces (CLI, SNMP, RPC). The format for the CLI command is as follows: cmmset -l [location] -t [Sensor Name] -d EventAction -v [Event Code]:[script to be run] This setting gets written to the actionscripts.cfg file and is synced to the standby CMM.
Page 167: Retrieving The Value Of The Data Sensor Bits
CMM Scripting Table 79. CMM Status Sensor Data Bits Bit Name Explanation Set when the Active/Standby election has taken place, and reset at a RUNNING restart of the CMM. ACTIVE Set when CMM is Active bENUMERATION Set when the initial blade discovery is finished WRAPPERS Set when the WrapperProcesses are running SNMP...
Page 168: Cmmreadytimeout Value
CMM Scripting 18.4.3 CMMReadyTimeout Value The CMMReadyTimeout value is a 16 bit unsigned value signifying the number of seconds in which the CMM should become Ready after becoming Active. If the CMM takes longer than this amount of time, a CMM Ready timed out event will be asserted. This is a health related event. The CMMReadyTimeout value will be set and queryable from the CLI using the “CMM Status”...
Page 169: Fru Control Script
CMM Scripting Figure 5. CMM Status State Diagram 18.5 FRU Control Script The CMM will check for a file in /home/scripts called frucontrol before it activates or deactivates any FRU. If that file does not exist, the CMM automatically activates or deactivates all FRUs. If it does exist, the CMM attempts to execute the program, and that is all.
Page 170: Command Line Arguments
# by estoppel or otherwise, to any intellectual property rights is granted # this document. The Software is subject to change without notice, and should # not be construed as a commitment by Intel Corporation to market, license, # sell or support any product or technology. Unless otherwise provided for...
Page 171 # Software license, no part of the Software may be reproduced, stored in a # retrieval system, transmitted in any form, or distributed by any means without # the express written consent of Intel Corporation. # Command line arguments passed to this script # $1 = IPMB address # $2 = FRU ID # $3 = Previous state (1 - M1, 2 - M2, ...)
Page 172 CMM Scripting *) echo Invalid device IPMB address >> /var/log/debug.log esac # ACTIVATION date >> /var/log/frucontrol.log if [ "$4" = "2" ] ; then echo activating device $DEVICE >> /var/log/frucontrol.log while true cmmset -l $DEVICE -d fruactivation -v 1 if [ $? -eq 0 ] ; then break done echo done activating device $DEVICE >>...
Page 173 CMM Scripting break done echo done deactivating device $DEVICE >> /var/log/frucontrol.log date >> /var/log/frucontrol.log MPCMM0001 Chassis Management Module Software Technical Product Specification Download from Www.Somanuals.com. All Manuals Search And Download.
Page 174: Remote Procedure Calls (Rpc)
Note: System Event Log (SEL) information is currently not available through the RPC interface. 19.1 Setting Up the RPC Interface Before you can use RPC calls in a custom application, you must obtain the following RPC source code files (contact your Intel representative): • rcliapi.h •...
Page 175: Getauthcapability()
Remote Procedure Calls (RPC) 19.2.1 GetAuthCapability() The following is the calling syntax for GetAuthCapability(): int GetAuthCapability( char* pszCMMHost, char* pszUserName, char* pszPassword Parameters pszCMMHost:[in] IP Address or hostname of CMM pszUserName:[in] A valid CMM user name pszPassword:[in] Password corresponding to pszUserName Return Value >0 Authentication successful.
Page 176 Remote Procedure Calls (RPC) Parameters pszCMMHost [in] IP Address or DNS hostname of CMM. nAuthCode[in] Authentication code returned by GetAuthCapability(). uCmdCode[in] The command to be executed (CMD_GET or CMD _SET as defined in cli_client.h). pszLocation[in] The location that contains the data item that uCmdCode acts upon, such as system, CMM, or blade1.
Page 177 Remote Procedure Calls (RPC) Table 80. Error and Return Codes for the RPC Interface (Sheet 1 of 4) Code #: Error Code String Error Code Description E_SUCCESS Success E_BPM_BLADE_NOT_PRESENT Blade isn't in the chassis. ECMM_SVR: Unsupported Command E_ECMM_SVR_COMMAND_UNSUPPORTED Error. E_CLI_MSG_SND CLI Send Message Error.
Page 178 Remote Procedure Calls (RPC) Table 80. Error and Return Codes for the RPC Interface (Sheet 2 of 4) Code #: Error Code String Error Code Description An IPMI request returned with a non E_IMB_COMPCODE_ERROR successful completion code. User should try the command again. Invalid IPMI response.
Page 179 Remote Procedure Calls (RPC) Table 80. Error and Return Codes for the RPC Interface (Sheet 3 of 4) Code #: Error Code String Error Code Description E_SFS_NO_MEMORY Internal CMM Error. E_SFS_UNSUPPORTED_DEVICE Internal CMM Error. E_SFS_RESPONSE_LENGTH Internal CMM Error. E_SFS_RESPONSE_DATA Internal CMM Error. E_SFS_POWER_SUPPLY_FRU Internal CMM Error.
Page 180 Remote Procedure Calls (RPC) Table 80. Error and Return Codes for the RPC Interface (Sheet 4 of 4) Code #: Error Code String Error Code Description E_SNMP_CMD_UNSUPPORTED Internal CMM Error. E_SNMP_ERROR Internal CMM Error. E_SNSR_VALUE_OUT_OF_RANGE Internal CMM Error. E_SNSR_AUTH_ERROR Internal CMM Error. E_WP_INITIALIZE_LIBS Internal CMM Error.
Page 181: Chassismanagementapi() Threshold Response Format
Remote Procedure Calls (RPC) 19.2.3 ChassisManagementApi() Threshold Response Format The following table documents the format of ChassisManagementApi() queries that return data of type DATA_TYPE_ALL_THRESHOLDS. Table 81. Threshold Response Formats Dataitem Return format Example Data is returned in the THRESHOLDS_ALL structure as defined in cli_client.h.
Page 182 Remote Procedure Calls (RPC) Table 82. String Response Formats (Sheet 2 of 5) Dataitem Return Format Example List of human-readable health events. Lines are separated by linefeeds with a null-terminator at the end. "(null)” or "" if there are no healthevents Minor Event: +3.3 V Upper non-critical healthevents Refer to...
Page 183 Remote Procedure Calls (RPC) Table 82. String Response Formats (Sheet 3 of 5) Dataitem Return Format Example Human readable powerstate information containing the target blade powerstate information. Lines are separated by linefeeds with a null-terminator at the Board is present end.
Page 184 Remote Procedure Calls (RPC) Table 82. String Response Formats (Sheet 4 of 5) Dataitem Return Format Example Null-terminated string showing the version of SNMP traps the CMM is currently set for. snmptrapversion Syntax: [v1 or v3] /0 Human-readable unhealthy blade, cmm and/or chassis information, containing a list of blades, cmms and/or chassis with a health status of Critical, Major, and Minor.
Page 185: Chassismanagementapi() Integer Response Format
Remote Procedure Calls (RPC) Table 82. String Response Formats (Sheet 5 of 5) Dataitem Return Format Example Used to set or query the process restart escalation action. This is only valid for a EscalationAction "1:No Action", "2:Failover and Reboot" target of "PmsProc[#]. Where "#" is the unique number for the process.
Page 186: Fru String Response Format
Remote Procedure Calls (RPC) 19.2.6 FRU String Response Format Querying an individual FRU field returns a null terminated string with a single linefeed. Table 84. FRU Data Items String Response Format Data Item Description Null-terminated string containing all FRU information for the location. Null-terminated string containing all board area FRU information for the boardall location.
Page 187: Rpc Sample Code
Remote Procedure Calls (RPC) 19.3 RPC Sample Code Sample code for interfacing with the CMM through RPC is available in the file cli_client.c. The sample code compiles into a command-line executable for use with Linux or a .o file for use with VxWorks.
Page 188 Remote Procedure Calls (RPC) Table 85. RPC Usage Examples (Sheet 2 of 3) ChassisManagementApi() Example ChassisManagementApi() [out] Parameters [in] Parameters uReturnType: DATA_TYPE_INT pszCMMHost: localhost ppvbuffer: Integer value denoting health state Get the uCmdCode: CMD_GET 0 = OK overall system pszLocation: system 1 = Minor health.
Page 189 Remote Procedure Calls (RPC) Table 85. RPC Usage Examples (Sheet 3 of 3) ChassisManagementApi() Example ChassisManagementApi() [out] Parameters [in] Parameters pszCMMHost: localhost uReturnType: not used uCmdCode: CMD_SET Reset a ppvbuffer: not used pszLocation: blade[1-19] blade. The return code from ChassisManagementApi() pszDataItem: powerstate indicates success or failure.
Page 190: Rmcp
RMCP RMCP The RMCP (Remote Management Control Protocol) section of the Alert Standard Format Specification version 2.0 section 3.2.1 allocates two UDP ports for the RMCP server, ports 623 (the Primary RMCP port) and 664 (the Secondary RMCP or Secure port). This implementation of the RMCP server listens for the RMCP packet from the Ethernet interface on only on port 623.
Page 191: Rmcp User Privilege Levels
RMCP 20.3 RMCP User Privilege Levels There are five privilege levels defined in the IPMI1.5 spec. 1. Callback level 2. User level 3. Operator level 4. Administrator level 5. OEM Proprietary level Callback Level has the most restricted privileges, and OEM Proprietary Level has the least restricted privilege.
Page 192: Rmcp Port Numbers
RMCP returned by the Get Channel Authentication Capabilities command. The response packet will contain a challenge string and a Session ID. 3. The RMCP client activates the session by issuing an Activate Session request. The Activate Session packet is typically authenticated. For message-digest algorithms, the packet includes a signature (AuthCode) that is a hash of the challenge, the Session ID, the password, and the message data using one of the supported algorithms from the Get Channel Authentication Capabilities command.
Page 193: Ipmb Slave Addresses
RMCP 20.7 IPMB Slave Addresses In the current RMCP server implementation in the BMC, embedded ‘IPMI message’ within a RMCP message is bundled with IPMB protocol. The ‘slave address’ required by this protocol should be set to 20h to address the BMC. The RMCP client may use any of the address shown in the range specified below as its slave Address.
Page 194: Ipmi Commands Supported By Cmm Rmcp
RMCP 20.9 IPMI Commands Supported by CMM RMCP The following IPMI commands are supported via RMCP by the CMM. To configure privileges for the commands see Section 20.10, “Configuring IPMI Command Privileges” on page 196 below. Table 89. IPMI Commands Supported by CMM RMCP (Sheet 1 of 3) Command Type Defined In Command...
Page 195 RMCP Table 89. IPMI Commands Supported by CMM RMCP (Sheet 2 of 3) Command Type Defined In Command Get Device SDR Info Get Device SDR Reserve Device SDR Repository Get Sensor Hysteresis Sensor Device Commands IPMI 1.5 Spec Get Sensor Threshold Get Sensor Event Enable Re-arm Sensor Events Get Sensor Event Status...
Page 196: Configuring Ipmi Command Privileges
RMCP Table 89. IPMI Commands Supported by CMM RMCP (Sheet 3 of 3) Command Type Defined In Command Get PICMG Properties Get Address Info Get Shelf Address Info Set Shelf Address Info FRU Control Get FRU LED Properties Get LED Color Capabilities Set FRU LED State AdvancedTCA™...
Page 197: Sample Cmdprivillege.ini File
RMCP [Net Function1..n]: TheIPMI Net Function in hex of the corresponding command. [Net Function Name 1..n]: The name used to identify its corresponding subsection. Y: The max number of commands defined in the subsection plus 1. [Command Bye 1..(Y-1)]: The command byte of the Net Function defined in this section. Privilege Level: The privilege given to that command byte defined as follows: —...
Page 198 RMCP Table 90. RMCP Message Completion Codes Code Description Success Busy Invalid Command Command invalid for a given LUN Request data length invalid Requested data field length limit exceeded. (too long) Requested Offset (in the data) Out of Range Not Found Invalid field in the Request Illegal Command RMCP Session/User Authentication Failed...
Page 199: Command And Error Logging
Command and Error Logging Command and Error Logging 21.1 Command Logging All CMMSET commands from all of the CMM interfaces (CLI, RPC, and SNMP) are logged by the CMM in the file /var/log/user.log. The size of the user.log file is 500 KBytes. When the command log becomes full, the log file is compressed and archived using gzip, then stored in / home/log.
Page 200: Cmmdump Utility
Command and Error Logging 21.3 Cmmdump Utility The cmmdump utility is a script that dumps the current system state of the CMM, the value of several configuration and log files, and the output of several cmmget commands. This utility is currently designed to be executed from a command prompt on the CMM.
Page 201: Application Hosting
The CMM allows applications to be hosted and run locally. This is useful as a method for adding small custom management utilities to the CMM. 22.1 System Details ® The CMM runs a customized version of embedded BlueCat* Linux* 4.0 on an Intel 80321 with ® ® Intel XScale microarchitecture.
Page 202: Ram Constraints
Application Hosting 22.3.1.2 Flash Memory Map Below is the list of images on CMM flash with flash address ranges and the size of the images. Table 91. Flash #1 Image Name Flash Address Range Image Size Backup RedBoot image 0xF0000000 - 0xF003FFFF 256KB RedBoot image 0xF0040000 - 0xF007FFFF...
Page 203: Interrupt Constraints
Application Hosting 22.3.3 Interrupt Constraints User applications should not use interrupts. All interrupts are reserved for use by the CMM firmware. 22.4 RAM Disk Directory Structure The following directories are stored on a RAM-disk. These directories store information critical to the CMM and are size constrained.
Page 204: Updating Cmm Software
Updating CMM Software Updating CMM Software When new CMM updates are available, they are packaged in a zip file and posted to the Intel developer web site located at: http://www.intel.com/design/network/products/cbp/atca/mpcmm0001.htm Please follow the instructions provided with the software update package to perform the update.
Page 205: Critical Software Update Files And Directories
/etc/cmm/update.log successfully. 23.4 Update Package The update package is available at: http://www.intel.com/design/network/products/cbp/atca/mpcmm0001.htm It contains the components listed in Table 96 on the following page. MPCMM0001 Chassis Management Module Software Technical Product Specification Download from Www.Somanuals.com. All Manuals Search And Download.
Page 206: Update Package File Validation
Updating CMM Software Table 96. Contents of the Update Package File Name Description CMM_RB.bin Redboot image to be stored in flash CMM_FPGA.bin FPGA image CMM_FFS.bin /etc image CMM_OS.bin OS image README Text file containing release notes for the update package Update_Metadata File containing info on the update package and how it should be installed on the CMM Utilities...
Page 207: Update Firmware Package Version
Updating CMM Software 23.4.2 Update Firmware Package Version The firmware update package has a firmware version associated with the entire package. This firmware version is the same version that can be retrieved using the CLI command: cmmget -l cmm -d version To determine if the update is a new, old or same version, the update package will contain a version_history file which contains a list of all software builds that have occurred, listed in sequential order.
Page 208: Update Mode
Updating CMM Software Table 97. SaveList Items and Their Priorities File Priority /etc/passwd /etc/shadow /etc/cmm/sel_* /etc/cmm/cmm_sel /etc/snmp*.conf /etc/ifcfg-eth* /etc/HOSTNAME /etc/ftp* /etc/group /etc/profile /etc/versions* /etc/issue /etc/issue.net /etc/pump.conf /etc/*.cfg /etc/cmm/sensors.ini /etc/cmm/fantray.cfg Note: Performing an update to an earlier version of the firmware will cause a loss of some configuration data (such as SNMP trap address configuration which is stored in /etc/cmm.cfg) because files with a priority of 2 are not synchronized on updates to earlier versions.
Page 209: Update_Metadata File
Updating CMM Software 23.7 Update_Metadata File The Update_Metadata file included in the update package is used by the update process to determine the platform, firmware package version, files, sequence, update method, location, and any other data required to update the individual components in the update package. 23.8 Firmware Update Synchronization/Failover Support The following CMM versions and corresponding update directions will include support for...
Page 210: Setting Failover Configuration Flag
Updating CMM Software even if the failover configuration flag is marked "manual", if any of the above condition is met, automatic failover may occur. 23.9.1 Setting Failover Configuration Flag To set the value of the failover configuration flag, the following CLI command can be used: cmmset -l cmm -d failoveronredundancy -v [manual/automatic] Where: Manual: Upon establishing redundancy between the two CMM’s, failover does NOT occur...
Page 211: Hooks For User Scripts
Updating CMM Software [overwrite] [ftp:server:user:password]” Where: Update Package path and filename - The path and file name of the update package file without the .zip or .md5 extension. For example: “usr/local/cmm/temp/CMM_P00.09f” force - Optional argument that causes all components to update regardless of version. This option cause the environment variable FORCE_UPDATE to be set to TRUE.
Page 212: Data Restore User Scripts
Updating CMM Software 23.13.2 Data Restore User Scripts The update process will also execute user scripts following the update of the new /etc file system to flash. The update process will execute any user scripts that match the following pattern: /home/ update/scripts/S*.
Page 213: Update Process
Updating CMM Software direction=$2 if [ "$direction" = "forward" ] ; then cp /home/stagingarea/myScript.new /home/scripts/myScript elif [ "$direction" = "backward" ] ; then cp /home/stagingarea/myScript.old /home/scripts/myScript exit $? When the update process executes, and the Data Restore User Scripts are executed (during the update of the /etc partition), then the script S10updateMyScript will be executed and /home/script/ myScript will be updated accordingly.
Page 214 Updating CMM Software — Exit if error occurs 7. Validate that .zip file matches checksum in .md5 file — Exit if no match 8. Unzip the .zip file in the package directory on ramdisk 9. Validate that all files in the unzipped package match the md5 checksum in the validationFile. —...
Page 215: Update Process Status And Logging
Updating CMM Software 23.15 Update Process Status and Logging During the update process, status is sent to stdout as it executes. Output will also be appended to the file /usr/local/cmm/temp/update/update.log. This file will be copied to /etc/cmm/update.log at the completion of the update process. Status output will be of the format: MM/DD/YY HH:MM:SS [process[pid]]: [Message String] 23.16...
Page 216 Updating CMM Software 1. Extract the contents of the .zip file into a folder (e.g. "C:\CMM\") on the host PC. 2. Open a DOS Command Line Prompt on the Windows* PC and change directory to the above folder (e.g., C:\CMM). 3.
Page 217: Updating Shelf Components
® refer to the Intel NetStructure™ MPCBL0001 Technical Product Specification. These documents and the firmware for these components can be found on the Intel web site at: http://www.intel.com/design/network/products/cbp/index.htm MPCMM0001 Chassis Management Module Software Technical Product Specification Download from Www.Somanuals.com. All Manuals Search And Download.
Page 218: Ipmi Pass-Through
IPMI Pass-Through IPMI Pass-Through 25.1 Overview The IPMI Pass-through feature allows IPMI commands to be sent directly to any device in the chassis through the CMM without being processed by lower layers of the CMM software stack. This allows local or remote devices such as other SBCs in the platform to send unfiltered IPMI commands directly to other devices in the platform through the CMM.
Page 219: Response String
IPMI Pass-Through The request string will only be validated for the format and ranges specified above. Any further validation of the command or data is left up to the receiver. If the range or format validation fails the error code of E_CLI_INVALID_SET_DATA will be returned. Note: Please refer to the IPMI Specification for further details on IPMI commands and the values described above.
Page 220 IPMI Pass-Through # snmpget […] […].cmmIPMICommandRequest […].cmmIPMICommandRequest=”” # snmpget […] […].cmmIPMICommandResponse […].cmmIPMICommandResponse=”” # snmpset […] […].cmmIPMICommandRequest s “6 1” # snmpget […] […].cmmIPMICommandRequest […].cmmIPMICommandRequest=”6 1” # snmpget […] […].cmmIPMICommandResponse […].cmmIPMICommandResponse=”0 32 129 5 2 81 255 87 1 0 65 8 0 0 0 0 # 6 1” MPCMM0001 Chassis Management Module Software Technical Product Specification Download from Www.Somanuals.com.
Page 221: Fru Update Utility
FRU Update Utility FRU Update Utility 26.1 Overview This utility is intended to be used to update any FRU information in an AdvancedTCA* or CompactPCI chassis. It will be able to update functional system FRU information with a FRU provided in the update package; or it can be used to repair damaged FRU information. It can also view all FRU information in the chassis.
Page 222: Fru Update Process
FRU Update Utility 26.3 FRU Update Process The FRU update process is controlled by the configuration file (not including forced FRU recovery). The configuration file is capable of querying the system and user for information. The configuration file can be modified to adjust how the FRU update proceeds. Because the update process is controlled by a user modifiable file, the utility will perform a three part update process to ensure a proper update is performed.
Page 223: Fru Verification
FRU Update Utility 26.5 FRU Verification FRUs will be verified twice during the update process, once before any action is taken on the FRU, and once more after all bytes have been written to the FRU. If the verification fails when first reading the FRU from the system, the FRU will not be modified, and the update process will exit.
Page 224: Using The Location Switch
FRU Update Utility Table 100. FruUpdate Utility Command Line Options Argument Parameter Description (Short Name) (Required/Optional) Name of the configuration file to use for the Specifies the update configuration file to Update (u) update process. (Required) use. Specifies the name of the FRU file to use for a forced recovery.
Page 225: Updating The Fru
FRU Update Utility 26.10 Updating the FRU The “update” (u) switch is used to update a FRU. This argument requires a configuration file to be specified. The update will then be performed according to the contents of the configuration file. Example: LD_LIBRARY_PATH=.
Page 226 FRU Update Utility the maximum size of the FRU device and write the entire contents. The user must also specify a location to get using the ‘location’ switch. The contents of the FRU are not validated as they are read. Example: LD_LIBRARY_PATH=.
Page 227: Fru Update Configuration File
FRU Update Configuration File FRU Update Configuration File 27.1 Configuration File Format This section specifies the format for the configuration file used to assist in determining the configuration of the product. The configuration for a product consists of information about the product that can be used to select appropriate Field Replaceable Unit (FRU) information to be loaded into non-volatile storage areas.
Page 228: Numeric Constraints
FRU Update Configuration File • As the configuration file is parsed, on each line the correct number of quotes is checked and when incorrect, flagged as an error prior to checking for the correct number of arguments. • White space is defined as space, tab, and Carriage Return-Line Feed characters (CR-LF). 27.4 Numeric Constraints •...
Page 229: Else
FRU Update Configuration File Additionally there is wild card support for numbers in a tag string. When the ‘#’ character is used in the tag string following an IFSET statement, it will match any number found in that position of any of the tags previously saved in the tag string link list.
Page 230: Clear
FRU Update Configuration File 27.6.5 CLEAR The CLEAR command removes a tag to the master list to be checked by IFSET commands. If the tag does not exist in the list, nothing happens. If multiple tags exist, all are deleted. Example: CLEAR “tag”...
Page 231: System
FRU Update Configuration File Table 101. Probe Command Parameters Probe Type Parameter Description of Parameter *any* Error, invalid command, too few arguments SYSTEM System ID string to compare equal too FRUVER Version strings to check ranges for BMCVER Version strings to check ranges for 27.7.2 SYSTEM When the “SYSTEM”...
Page 232: Bmcver
FRU Update Configuration File 27.7.4 BMCVER Probing the BMC version is used to determine if a compatible version of firmware exist on the system. The version that is queried is the controller at IPMB address 0x20. The probe will get the BMC operational code version from the system and compare it to the list of versions that follow in the parameters.
Page 233: Update Commands
FRU Update Configuration File 27.8 Update Commands The configuration file allows the user to update the FRUs by specifying a target source file. And allow more customization of how the update should proceed with more commands. If the load utility fails at any of the updates, it should exit immediately and report the error. The update commands do not support path names;...
Page 234: Fruaddress
FRU Update Configuration File FRUFIELD “S#” “@STDIN:ASCII” 27.8.2 FRUADDRESS The FRUADDRESS command specifies an alternate address to program the FRU file to, by default the address in the file is used. If the SYSTEM FRU name is used, this is required by the user to correct outcome.
Page 235: Multirec
FRU Update Configuration File Table 102. FRU Area String Specifications FRU Area ASCII Strings “HEADER” “INTERNALUSE” “CHASSIS” “BOARD” “PRODUCT” “MULTIREC” The HEADER area is not selectable for writing; it is listed as an option to allow future use for comparisons. The internal use area is unique in that it has no fields, and can only be modified as a whole.
Page 236: Frufield
FRU Update Configuration File Table 103. Multi-Record Selection Parameters Parameter Parameter Value Description Number APPEND, INSERT, REMOVE, Operation to perform for the selected record. REPLACE Method to use for selecting the source and destination "PICMG_ID", "RECORD_ID" records. Number Destination record ID to be selected. Number Destination record count to be selected, 1 is the first record.
Page 237 FRU Update Configuration File Table 104. FRU Field First String Specifications FRU Field First String Description ASCII String Chassis Type (Chassis Area) The input string must represent a number. Regardless of the input type specified in the configuration file. This is because the chassis type field is an “CT”...
Page 238 FRU Update Configuration File Table 105. FRU Field Maximum Allowed Lengths (Sheet 2 of 2) Chassis Part Number 17h bytes Chassis Serial Number 1Fh bytes Chassis Custom Fields (AMx) 1Fh bytes Product Asset Tag 1Fh bytes Whether entering information by way of STDIN, an environment variable, or from a file, if an input length of zero is entered, then the utility will treat it the same as an empty string.
Page 239 FRUAREA CHASSIS FRUFIELD S# // gets the value from the MPCHC001.FRU file FRUAREA BOARD FRUFIELD MN “Intel” // puts ‘Intel’ in the field FRUFIELD S# “@stdin:ascii” // user types in the value FRUAREA PRODUCT // Gets the value from an environment variable “prod_ser_num”.
Page 240: Input Of Data
FRU Update Configuration File 27.8.6 Input of Data When taking in data from a file, an environment variable or from standard in, the input type is always ASCII. If in the configuration file, the type is specified as something other than ASCII, then it will be read in as ASCII and converted to the correct type.
Page 241: Display
FRU Update Configuration File 27.9.1 DISPLAY The Display command displays a line of text to the user. If the text is more than one word, it must be encapsulated in double quotes. In order to display a CR-LF, you must use two separate DISPLAY commands.
Page 242: Menutitle
FRU Update Configuration File MENU “cpci” “Compact PCI” MENU “unknown” MENUPROMPT IFSET atca // do atca stuff ENDIF IFSET cpci // do cpci stuff ENDIF IFSET unknown // quit the update with an error ERRORLEVEL21 ENDIF 27.9.5 MENUTITLE The MENUTITLE command displays a line of text before displaying the options for the menu. This command is optional, and if this command is used it must immediately precede a MENU command.
Page 243: Yes
FRU Update Configuration File 27.9.8 The YES command requires that a PROMPT or NO command directly precedes it. It defines what tag is to be set when the user answers yes to the previous PROMPT. If preceded by a NO command, that NO command must be preceded by a PROMPT command.
Page 244 FRU Update Configuration File Table 108. Command Quick Reference (Sheet 2 of 3) Processes and executes the commands between the ELSE and the matching ENDIF ELSE command if the matching IFSET command failed to find all the tags in the master tag list. ENDIF Indicates the end of the matching IFSET or ELSE command’s affect.
Page 245 FRU Update Configuration File Table 108. Command Quick Reference (Sheet 3 of 3) FRUFIELD Specifies what field of the selected FRU area to modify and what or where the data is. ASCII String FRU field name, see Table 104, “FRU Field First String Specifications” on page 237.
Page 246: Example Configuration File
FRU Update Configuration File Table 109 gives a brief overview of the various PROBE arguments and their expected inputs. All arguments in this table follow the PROBE command on the same line in the file. Table 109. Probe Arguments Quick Reference Probe Arguments Description Format 1: 1+ arguments.
Page 247 FRU Update Configuration File IFSET SYS_CORRECT // Skip the else for the wrong system ELSE DISPLAY"Incorrect platform for FRU update" // This will exit the file ERRORLEVEL 14 ENDIF ************************************************************************* // Validate the current version of the FRU is something we know about, if // exit the update process with instructions on how to go from here.
Page 248 FRU Update Configuration File DISPLAY "CDM FRU version is earlier than all known versions, no update can be performed." ERRORLEVEL 15 ENDIF ************************************************************************* PROBE FRUVER "103" FOUND FRUVER_CORRECT PROBE FRUVER "" FOUND FRUVER_NEEDED IFSET FRUVER_CORRECT DISPLAY "CDM FRU information is up to date, no update will be performed" // error level 0 will exit now with successful return code ERRORLEVEL 0 ELSE...
Page 249: Chassis Update Version 1
FRU Update Configuration File FRUFIELD "ID" // replace the first picmg power distribution record FRUAREA "MULTIREC” REPLACE PICMG_ID 0x11 1 0x11 1 // remove the 2nd picmg power record FRUAREA "MULTIREC" REMOVE PICMG_ID 0x11 2 // replace the shelf power management record FRUAREA "MULTIREC"...
Page 250 FRU Update Configuration File ERRORLEVEL 14 ENDIF ************************************************************************* // Validate the current version of the FRU is something we know about, if // exit the update process with instructions on how to go from here. // Later version than current update PROBE FRUVER "108+"...
Page 251 FRU Update Configuration File PROBE FRUVER "103" FOUND ALL_UPDATES PROBE FRUVER "104-105" FOUND IPMB_LINK_UPDATE // the update of the FRU to version 107 requires a power record update for versions 104 and later IFSET IPMB_LINK_UPDATE SET POWER_UPDATE ENDIF // To go from 106 to 107, we need to update the power distribution records PROBE FRUVER "106"...
Page 252 FRU Update Configuration File // replace the first picmig power distribution record FRUAREA "MULTIREC" REPLACE PICMG_ID 0x11 1 0x11 1 // append the new record after the first one FRUAREA "MULTIREC" APPEND PICMG_ID 0x11 1 0x11 2 // replace the shelf power management record FRUAREA "MULTIREC"...
Page 253: Unrecognized Sensor Types
Unrecognized Sensor Types Unrecognized Sensor Types 28.1 System Events Overview When a System Event is recorded in the CMM’s System Event Log (SEL), it contains 16 bytes. Below is an overview of the meaning of the bytes. For more information see Table 26-1 in the IPMI 1.5 specification.
Page 254: System Events- Snmp Trap Support
Unrecognized Sensor Types Event Data 2 and 3 – (2 bytes) Event data field contents which varies depending on how Event Data 1’s high nibble is set. The CMM uses the above 16 bytes of data from a SEL entry to produce human readable output. There are two general categories that an event can fall into: 1) data that the CMM code base recognizes, and 2) data that is unrecognized by the CMM.
Page 255: Snmp Trap Raw Format
Unrecognized Sensor Types Raw Hex : [ 12 34 56 78 9A … (16 bytes hex) ] 28.3 SNMP Trap Raw Format SNMPTrapFormat, in the cmm.cfg file controls whether the “text” portion or the “raw” portion of a trap is sent along with the “header”. The header is always sent. If the SNMPTrapFormat variable is equal to 1 (text) the output is header plus text.
Page 256: Snmp Trap Control
Unrecognized Sensor Types 28.3.1 SNMP Trap Control To assist with backward compatibility a variable exists called SNMPSendUnrecognizedEvents. This controls whether the CMM should not send SNMP traps for unrecognized SEL events (a value of 0) or begin sending SNMP traps for unrecognized events (a value of 1). The default value is 0.
Page 257: Configuring Sel Format
Unrecognized Sensor Types provides the text interpretation of the event. Its format is shown below: \tSDRSensorName\tHealthEventString Where: • SDRSensorName is the name given to the sensor in the Sensor Data Record (SDR). • HealthEventString is the CMM’s translation of the event. 28.3.2.3 SEL Raw Format The final portion that SEL display might contain is the “raw”...
Page 258 Unrecognized Sensor Types 28.3.3.4 System Events – SEL Display Control In older firmware, the CMM always displays events for recognized events and never displays unrecognized events. To assist with backward compatibility a new configuration variable has been added, SELDisplayUnrecognizedEvents, that controls whether the CMM should continue with the old behavior (a value of 0) or begin displaying unrecognized events as well (a value of 1).
Page 259: Warranty Information
If the product is found to be otherwise defective, Intel, at its option, will replace or repair the product at no charge except as set forth below, provided that you deliver the product along with a return material authorization (RMA) number (see below) either to the company from whom you purchased it or to Intel.
Page 260: For The Americas
Direct Return Authorization (DRA) repair requests e-mail address: uspss.repair@intel.com DRA on-line form: http://support.intel.com/support/motherboards/draform.htm Intel Business Link (IBL): http://www.intel.com/ibl Telephone No.: 1-800-INTEL4U or 480-554-4904 Office Hours: Monday - Friday 0700-1700 MST Winter / PST Summer 29.3.1 For Europe, Middle East, and Africa (EMEA) Return Material Authorization (RMA) e-mail address - emea.fs@intel.com...
Page 261 If the Customer Support Group verifies that the product is defective, they will have the Direct Return Authorization/Return Material Authorization Department issue you a DRA/RMA number to place on the outer package of the product. Intel cannot accept any product without a DRA/RMA number on the package. Limitation of Liability and Remedies...
Page 262: Customer Support
30.2 Technical Support and Return for Service Assistance For all product returns and support issues, please contact your Intel product distributor or Intel Sales Representative for specific information. 30.3 Sales Assistance If you have a sales question, please contact your local Intel NetStructure Sales Representative or the Regional Sales Office for your area.
Page 263: Certifications
Certifications Certifications ® The Intel NetStructure MPCMM0001 Chassis Management Module has the following approvals: • UL/cUL 60950 • EN/IEC 60950 • EN55022 Class A • EN55024 • FCC CFR47 Part 15 Class A • VCCI • AS/NZS3548 • BSMI MPCMM0001 Chassis Management Module Software Technical Product Specification...
Page 264: Agency Information
(1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. For questions related to the EMC performance of this product, contact: Intel Corporation 5200 N.E. Elam Young Parkway Hillsboro, OR 97124...
Page 265: Safety Instructions (English And French-Translated Below)
Agency Information 32.3 Safety Instructions (English and French-translated below) 32.3.1 English CAUTION: This equipment is designed to permit the connection of the earthed conductor of the d.c. supply circuit to the earthing conductor at the equipment. See installation instructions. If this connection is made, all of the following conditions must be met: -This equipment shall be connected directly to the DC supply system earthing electrode conductor or to a bonding jumper from an earthing terminal bar or bus to which the DC supply system...
Page 266: Taiwan Class A Warning Statement
Agency Information 32.4 Taiwan Class A Warning Statement 32.5 Japan VCCI Class A 32.6 Korean Class A 32.7 Australia, New Zealand MPCMM0001 Chassis Management Module Software Technical Product Specification Download from Www.Somanuals.com. All Manuals Search And Download.
Page 267: Safety Warnings
Safety Warnings Safety Warnings Caution: Review the following precautions to avoid personal injury and prevent damage to this product or products to which it is connected. To avoid potential hazards, use the product only as specified. Read all safety information provided in the component product user manuals and understand the precautions associated with safety symbols, written warnings, and cautions before accessing parts or locations within the unit.
Page 268: Mesures De Sécurité
Safety Warnings Warning: Avoid electric shock: Do not operate in wet, damp, or condensing conditions. To avoid electric shock or fire hazard, do not operate this product with enclosure covers or panels removed. Warning: Avoid electric shock: For units with multiple power sources, disconnect all external power connections before servicing.
Page 269 Safety Warnings Pour les systèmes C.A., utilisez uniquement un câble d'alimentation avec une prise de terre et établissez toujours les connexions à une prise secteur mise à la terre. Chaque câble d'alimentation doit être connecté à un circuit terminal dédié. Pour les systèmes C.C., la protection de cette unité...
Page 270: Sicherheitshinweise
Safety Warnings ventilateur ou les conduits de l'unité. Des boucliers ou des panneaux de gestion de l'air doivent être installés dans les connecteurs inutilisés du châssis. Les spécifications environnementales peuvent varier d'un produit à un autre. Veuillez-vous reporter au manuel de l'utilisateur pour déterminer les exigences en matière de flux d'air et d'autres spécifications environnementales.
Page 271 Safety Warnings Das Gehäuse verfügt über einen eigenen Erdungs-Verbindungsbolzen. Stellen Sie die Erdungsverbindung her, ehe Sie das Stromkabel oder Peripheriegeräte anschließen, und trennen Sie die Erdungsverbindung niemals, so lange Strom- und Peripherieverbindungen angeschlossen sind. Um die Gefahr eines durch ein Telefon oder Ethernet*-System bedingten elektrischen Schlags zu verringern, schließen Sie das Stromkabel des Geräts an, ehe Sie diese Verbindungen einrichten.
Page 272: Norme Di Sicurezza
Safety Warnings Vorsicht: Lithiumbatterien. Bei unsachgemäßem Austausch oder Umgang mit Batterien besteht Explosionsgefahr. Zerlegen Sie die Batterie nicht und laden Sie diese nicht wieder auf. Entsorgen Sie die Batterie nicht durch Verbrennen. Beim Auswechseln der Batterie muss dasselbe oder ein der Händlerempfehlung gleichwertiges Modell verwendet werden (CR2032).
Page 273 Safety Warnings NORME DI SICUREZZA PER LE UNITÀ MONTATE IN UN RACK. Questa unità può essere alloggiata in modo permanente in un rack. Il montaggio in rack deve essere conforme ai requisiti di resistenza fisica delle norme NEBS GR-63-CORE e NEBS GR 487.Prima di installare o rimuovere l'unità...
Page 274: Instrucciones De Seguridad
Safety Warnings 33.4 Instrucciones de Seguridad Examine las instrucciones sobre condiciones de seguridad que siguen para evitar cualquier tipo de daños personales, así como para evitar perjudicar el producto o productos a los que esté conectado. Para evitar riesgos potenciales, utilice el producto únicamente en la forma especificada. Lea toda la información relativa a seguridad que se incluye en los manuales de usuario de los distintos componentes y procure familiarizarse con los distintos símbolos de seguridad, advertencias escritas y normas de precaución antes de manipular las distintas piezas o secciones de la unidad.
Page 275 Safety Warnings Advertencia: Evite sobrecargas eléctricas, calor y riesgos de descarga eléctrica o incendio: Conecte el sistema sólo a un circuito de alimentación que tenga el régimen apropiado, según lo especificado en el manual de usuario del producto. No realice conexiones con terminales cuya capacidad no se ajuste al régimen especificado para ellos.
Page 276: Chinese Safety Warning
Safety Warnings 33.5 Chinese Safety Warning MPCMM0001 Chassis Management Module Software Technical Product Specification Download from Www.Somanuals.com. All Manuals Search And Download.
Page 277 Example CLI Commands Example CLI Commands The following table shows examples of most CLI operations. Note: The variable “N” (as in bladeN or fantrayN) represents the chassis slot number of the device being acted on (such as Blade5 or fantray1). Please refer to chassis documentation for slot, fan, fan tray, and power supply location and information.
Page 278 Example CLI Commands Table 111. Example CLI Commands (Sheet 2 of 3) Use Case CLI Command Return LED support information: Query what LEDs are Blade5 has control of hsled, led1, cmmget -l blade5 -d ledproperties supported by a FRU led2, Blade5 support 0 user leds Information on the colors supported by an LED:...
Page 279 Example CLI Commands Table 111. Example CLI Commands (Sheet 3 of 3) Use Case CLI Command Return cmmset -l bladeN -d frucontrol -v [0-3] Where: 0 = Cold reset Exercise control over Success or Failure the FRU payload 1 = Warm reset 2 = Graceful reboot 3 = Issue diag.
Page 280 ® Intel IOP312 Processor Chipset For more information about the Intel ® IOP310 Processor Chipset, see the following Web site: http://developer.intel.com/design/iio/docs/iop310.htm MPCMM0001 Chassis Management Module Software Technical Product Specification Download from Www.Somanuals.com. All Manuals Search And Download.
Page 281 Technical Support and Return for Service Assistance For all product returns and support issues, please contact your Intel product distributor or Intel Sales Representative for specific information. Sales Assistance If you have a sales question, please contact your local Intel NetStructure Sales Representative or the Regional Sales Office for your area.
Page 282 Free Manuals Download Website h p://myh66.com h p://usermanuals.us h p://www.somanuals.com h p://www.4manuals.cc h p://www.manual-lib.com h p://www.404manual.com h p://www.luxmanual.com h p://aubethermostatmanual.com Golf course search by state h p://golﬁngnear.com Email search by domain h p://emailbydomain.com Auto manuals search h p://auto.somanuals.com TV manuals search h p://tv.somanuals.com...

Intel NetStructure MPCMM0001 Software Instructions

Introduction

Software Specifications

Redundancy, Synchronization, and Failover

Built-In Self Test (BIST)

Re-Enumeration

Process Monitoring and Integrity

Power and Hot Swap Management

The Command Line Interface (CLI)

Resetting the Password

Sensor Types

Health Events

Front Panel Leds

Node Power Control

Electronic Keying Manager

Cdms and FRU Information

Fan Control and Monitoring

Snmp

CMM Scripting

Remote Procedure Calls (RPC)

Rmcp

Quick Links

Related Manuals for Intel NetStructure MPCMM0001

Summary of Contents for Intel NetStructure MPCMM0001