You are on page 1of 30

567 Enterprise Dr.

Westerville, OH 43081
Toll Free: 800-818-4525
Phone: 614-846-6175
Fax: 614-846-4450
www.tracewellsystems.com

Tracewell Systems
AdvancedTCA CO14 Shelf

Software Reference Guide for M100

Revision:

1.0

Revision History
Rev
1.0

Date
Mar 12th, 2006

Author
Vadim Isakov

Description
Initial version

Copyright Notice
This material is proprietary of Tracewell Systems. Copying, compilation, modification, distribution
or any other use whatsoever of this material is strictly prohibited without written permission of
Comtel Electronics GmbH.
The information in this document is subject to change without notice and should not be
construed as a commitment by Comtel Electronics. Neither Comtel Electronics, nor there agents
assume any responsibility for the use or reliability of this document or the described software.
Copyright© 2005 by Comtel Electronics GmbH. All rights reserved.
The Comtel logo is a trademark of Comtel Electronics GmbH.a

Page 2 of 30

Table of contents
REFERENCES................................................................................................................................................................... 7
SPECIAL TERMS AND ACRONYMS ........................................................................................................................... 7
1

INTRODUCTION .................................................................................................................................................... 9
1.1
1.2

2

ABOUT THIS DOCUMENT .................................................................................................................................... 9
BRIEF SHELF MANAGER FUNCTIONALITY DESCRIPTION ..................................................................................... 9

ETHERNET ADDRESSES.................................................................................................................................... 10
2.1
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.2
2.2.1
2.2.2
2.3
2.4

LOGGING ON TO THE SHELF MANAGER EXTERNALLY ..................................................................................... 10
Default hardware IP address of the ShMC1............................................................................................... 10
Username and password ............................................................................................................................ 10
Default hardware IP address of the ShMC2............................................................................................... 10
Default virtual IP address of the active Shelf Manager ............................................................................. 10
Default virtual IP address of the standby Shelf Manager .......................................................................... 10
LOGGING ON TO THE SHELF MANAGER OVER BACKPLANE .............................................................................. 11
Default IP addresses .................................................................................................................................. 11
Planes......................................................................................................................................................... 11
CHANGING THE IP ADDRESSES ......................................................................................................................... 11
CROSS-CONNECT IMPLEMENTATION ON TRACEWELL CO14 SHELF ....................................................................... 12

3

DIRECTORY STRUCTURE ON M100............................................................................................................... 13

4

I2C ADDRESSES OF THE FRUS IN CO14 SHELF .......................................................................................... 13

5

STANDARD IPMI COMMANDS ........................................................................................................................ 14
5.1
COMMAND SYNTAX ......................................................................................................................................... 14
5.2
USEFUL COMMANDS ....................................................................................................................................... 16
5.2.1
FRU Control............................................................................................................................................... 16
5.2.2
IPMB State ................................................................................................................................................. 16
5.2.3
Set FRU Activation Policy.......................................................................................................................... 16
5.2.4
Set Power Level .......................................................................................................................................... 16
5.2.5
Get Fan Level ............................................................................................................................................. 17
5.2.6
Set Fan Level.............................................................................................................................................. 17
5.2.7
Set Event Receiver ...................................................................................................................................... 17
5.2.8
Get Device SDR.......................................................................................................................................... 17
5.2.9
Get Sensor Threshold ................................................................................................................................. 17
5.2.10
Get Sensor Reading ............................................................................................................................... 17
5.3
IPMI TEST ........................................................................................................................................................ 17

6

HPI COOLING....................................................................................................................................................... 18
6.1
6.2
6.3
6.4
6.4.1
6.4.2
6.4.3
6.4.4
6.5
6.5.1
6.5.2

7

COOLING CONTROL MODES .............................................................................................................................. 18
COOLING ZONES ............................................................................................................................................... 18
COOLING LEVEL ............................................................................................................................................... 18
INTERNAL CONTROL MODE COOLING ALGORITHM ........................................................................................... 18
Startup ........................................................................................................................................................ 18
Hot Swap event handling............................................................................................................................ 19
Temperature event handling....................................................................................................................... 19
Difference temperature handling ............................................................................................................... 19
EXTERNAL CONTROL MODE ............................................................................................................................. 20
Startup ........................................................................................................................................................ 20
Setting cooling level ................................................................................................................................... 20

HPI COMMANDS.................................................................................................................................................. 21
7.1
SUPERVISOR STATUS ........................................................................................................................................ 21
7.2
UTILITIES ......................................................................................................................................................... 21
7.2.1
Hpifan......................................................................................................................................................... 21
Page 3 of 30

...............................................................2.............................................18 7...........................2 Alarm Sensors FRU ID 1.......................................... 27 9..................................................................................................................3 7................................ 27 Data ................................1.................................................................................................................................... 24 Hpiship ..................................2.....6 7. 26 8......................................................................................................................................................................... 24 Hpisettime ............................................ 27 9................2.........................................................10 7...................................................... 27 9.................................2....................... 25 Hpiuserinfoarea ....................1 FAN TRAYS ...................................13 7............... 23 Hpireset3..............2.............................................................................................................................................................2......................................................15 7................... 27 10 SHELF FRU INFORMATION .........7 7.......................................................................................2 Fan Tray RTM Sensors FRU ID 1............................. 27 9.................... 26 8............. 21 Hpievents....................................................................1...........2....................2 PEMS.....................................................................................................................................................................................................................................................2................. 25 SOFTWARE UPGRADE.............2.2...........2 7....1 swupgrade ..........................................................................................................................1.................................9 7.....................................................................................................................................................................2........................................................... 21 Hpievent ................................................23 8 Hpicooling.. 26 8....................................22 7.......................................................2 Hpiupgrade........................................................................2.........................................................................................................2...................7.........................................2......................8 7. 27 10....................1 Fan Tray Main board Sensors FRU ID 0.................................. 23 Hpisel ..................................... 26 9 SDRS IN TRACEWELL FRUS ................................................................................................................................. 27 9................................12 7.............................................................2.......4 7....................................... 27 9.........19 7...... 23 Hpisensor ................................................................................................................................................................................................. 22 Hpihotswap...................................................................................................... 26 8......................................................................................1............................................................................... 26 8.....2.....................................................................2........................ 27 Page 4 of 30 .........................................2.............. 23 Hpiredundancy................1...........5 7....................................................................................... 21 Hpifruactivation .............................................................................................sh ............................................... 22 Hpiinv........ 24 Hpishaddr.. 23 Hpiresid............................................................... 22 Hpipoweronseq.................................................1 FIRMWARE UPGRADE..........................................................................................................1 Power Sensors FRU ID 0 .................................. 26 8.............................. 24 Hpithres..........................11 7.............................. 23 Hpiseledit ..................................................................................................................................17 7......2.................2...........................................................................................................................................1 10....................................................................................16 7.........1 fw_upgrade........20 7.......... 25 Hpiupgrade ..........................................................................2..................21 7..............2...............................................................................................................................................................................2...............................2 Hpiupgrade.............................................................................2............................................................................................................................................... 22 Hpilog .....................................................................................................................................................14 7.... 22 Hpiled ..........................................................................................1...............................................2 SOFTWARE UPGRADE ON THE M100.............................................................. 24 Hpitestredundancy ........................................2................2 Repository........................................2...................................

..............................List of figures Figure 1 – Field Replaceable Unit IP Text .......................... 11 Figure 2 – Shelf Manager Ethernet Port Cross-Connect Implementation ................................................................... 12 Page 5 of 30 .........

.... 12 Table 4 – I2C Addresses Reference ............................................................................................................................................................................. 11 Table 3 – Cross-connect implementation on Tracewell Backplanes ...................................................................................................................................................................................... 19 Table 9 – Fan Tray main sensors FRU ID 0 ............... 16 Table 8 – Cooling levels .......... 27 Table 12 – PEM RTM sensors FRU ID 0...................................................................... 27 Table 10 – Fan Tray RTM sensors FRU ID 1 ............................................................................... 13 Table 5 – I2C Addresses Reference ....................................List of tables Table 1 – Information available on M100 ..............................0 IPMI commands........................................................................................................................................................... 27 Table 11 – PEM main sensors FRU ID 0 ............................................................. 14 Table 6 – Supported IPMI commands ....................................................... 9 Table 2 – Default IP addresses of M100................................................................................................................. 15 Table 7 – Supported PICMG3....................................................... 27 Page 6 of 30 ...............................................

intel.com/ Feb 20. 2002 www.com/ AE Feb 2005 www.org/ Mar 12. 2002 2.motorola.0 Date Dec 30.org/ .1 Nov 28.5 ATCA-M100: reference guide ATCA-M100: Control via IPMI reference guide Special Terms and Acronyms Abbreviation AdvancedTCA API Description Advanced Telecommunications Computing Architecture Application Programming Interface CO CPU Central Office Central Processing Unit FRU Field Replaceable Unit HPI Hardware Platform Interface I2C IP IPMB IPMC IPMI Inter-Integrated Circuit Internet Protocol Intelligent Platform Management Bus Intelligent Platform Management Controller Intelligent Platform Management Interface LED Light Emitting Diode M100 Motorola Shelf Manager OOS OutCOfCService PEM PICMG Power Entry Module PCI Industrial Computer Manufacturers Group ShMC SNMP Shelf Management Controller Simple Network Management Protocol TBD TPE To Be Defined Twisted Pair Ethernet VIP Virtual IP Adress Page 7 of 30 Website www.2 IPMI 1.com/ AG Feb 2005 www.0 ECN002 Tracewell Systems User Manual Rev 2.picmg.0 1.tracewell systems.com/ Motorola Motorola Intelligent Platform Management Interface 1.motorola. 2006 www.0 AdvancedTCA Base Specification PICMG 3. 2005 www.picmg.References For further information please refer to the following sources: Committee/Company Document PICMG 3.

Page 8 of 30 .

its handle has to be pressed.2 Brief Shelf Manager functionality description During start up of the system the FRUs go through a power cycle. The software version of the Shelf Manager can be read off by reading the content of the file shm-version located in the directory /etc. The Shelf Manager boards provide the following information: Feature Provide sensor data records Provide FRU inventory Provide system event log Event generator SDR repository Available Yes Yes Yes Yes Yes Table 1 – Information available on M100 1. Page 9 of 30 . the other one standby. the active Shelf Manager will activate this FRU automatically. power consumption and connectivity of the FRUs in the system. For details on the additional IPMI commands that can be used on the Shelf Manager please refer to the IPMI Specification Version 1. In order for Shelf Manager to start the power up sequence. If both have ACT on it could mean there are two different versions of software on the shelf managers or other discrepancy.1 Introduction 1.5. If there are two Shelf Managers in the system one of them becomes active. Shelf Manager is responsible for processing events generated by the FRUs in the system. This data contains information about the amount. while the states are controlled by the Shelf Manager. located at the address 0x14 in Tracewell AdvancedTCA systems at FRU ID =1. If handle is released during the operation. In the normal operation mode. If all the FRU data on the FRU is correct and SDRs are defined correctly. As well it offers a summary of most commonly used IPMI and HPI commands using the M100 Shelf Manager. location. If these are temperature events arriving from the ATCA boards in the front or rear cooling zones. one of the Shelf Managers is active and the other one in the standby mode. Shelf Manager copies Shelf FRU data from the configuration board. It provides a detailed description of default values of FRU information and sensor data records (SDRs) contained in the Tracewell CO14 ATCA shelf. It is handled on the high platform level by HPI. which can be observed on the LEDs: the active Shelf Manager has orange (ACT) and green (OK) and the standby only green (OK). if that is present in the system. the Shelf Manager will blink to indicate the released handle and after a while will switchover automatically to the standby Shelf Manager.1 About this document This document is provided for the use of systems integrators and development engineers who are using the Tracewell CO14 AdvancedTCA® shelf with Motorola M100 Shelf Manager. they will be handled by controlling the speed of the fans.

0.168. regardless which one is right or left hand at the following address: 192.168.0.168.100 Netmask: 255.0.0. In order to connect to the Shelf Manager using TCP/IP the local computer has to be defined in the local network of the Shelf Manager.9 2. 2.0 Gateway: 192.255.1. in order to connect externally to the address 192.1.1 Logging on to the Shelf Manager Externally 2.0.2 Username and password Under any address to log on to the Shelf Manager the following username and password: username: root password: root 2.168. Two are connected to the Backplane (eth1 and eth2) and the third is the Out of Band connection (eth0) allowing direct connection through RJ45 cable onto Shelf Manager.3 Default hardware IP address of the ShMC2 The left-hand Shelf Manager can be accessed with RJ45 from the computer by external RJ45 port at the following address: 192.5 Default virtual IP address of the standby Shelf Manager It is possible to log on to the virtual address of the standby Shelf Manager.4 Default virtual IP address of the active Shelf Manager It is possible to log on to the virtual address of the active Shelf Manager.8 the computer can be defined as following: IP: 192.171 Please note that stopping the HPI causes this address to disappear.8 2.1. therefore firmware upgrade using fw_upgrade.168.168.181 Page 10 of 30 .1 Default hardware IP address of the ShMC1 In order to connect with RJ45 from the computer to the external RJ45 port on the right-hand Shelf Manager via TCP/IP the following address shall be used: 192.0 2.168. regardless which one is right or left hand at the following address: 192.sh script is not possible.0.1. For example.1.2 Ethernet Addresses M100 Shelf Manager has three Ethernet channels.0.255.

0.17.18.18.3 Changing the IP addresses Shelf FRU data defined Base IP addresses for the Backplane and Out of Band connections.0.0.1 Default IP addresses M100 has two planes on the Backplanes with different default addresses. as defined in ECN001 of the AdvancedTCA specification rev1.0.8 172.17.2.2 Logging on to the Shelf Manager over Backplane 2.8 Left-hand ShMC 0x12 172. and described in the following section.8 172.0.16.9 172. This could be done using HPI commands hpishaddr and hpiship which alter only the first 3 octets.2.0.9 172.2.9 Table 2 – Default IP addresses of M100 2. 2. If the change of 4th octet is required.16.2 Planes There is available connection on the Backplane between Shelf Manager 1 to Switch 2 and between Shelf Manager 2 to Switch1. In order to change the default IP addresses Shelf FRU data stored in FRU ID 254 on the Shelf Manager shall be edited. Tracewell written procedure FRUIT is recommended to update the addresses in the Shelf FRU data. as described in the following table: I2C address Plane A Plane B Virtual Plane Right-hand ShMC 0x10 172. Figure 1 – Field Replaceable Unit IP Text Edit Page 11 of 30 .

2. Same is applicable for Shelf Manager 2 connected to dedicated Switch2 slot and over the secondary channel with Switch1. The pinout of the P23 connector on the Backplane is implemented accordingly.4 Cross-connect implementation on Tracewell CO14 Shelf The ECR 001 2004 11 171 adds an option for dual 10/100BASE-TX links from each Base Hub to both Dedicated ShMC slots. as shown in the following figure: Shelf Manager (Active) ShMC Port1 ShMC Port 2 Shelf Manager (Backup) Eth port 1 Eth port 2 Eth port 1 Eth port 2 ShMC ShMC Redundant IPMB-0 on Backplane ab cd ef gh ShMC Port with Crossconnect IPMC IPMC ShMC port 1 ShMC port 2 ShMC port 1 ShMC port 2 Base Hub A Base Hub B IPMC IPMC ATCA Board ATCA Board Figure 2 – Shelf Manager Ethernet Port Cross-Connect Implementation Page 12 of 30 . as described in the following table: Row # 5 Interface Designation ShMC Port with ShMC Crossconnects AB CD Tx1+ Tx1Rx1+ Rx1Primary ShMC Cross-connect EF GH Tx2+ Tx2Rx2+ Rx2Secondary ShMC Cross-connect Table 3 – Cross-connect implementation on Tracewell Backplanes This means Shelf Manager1 is connected to the dedicated Switch1 slot over the primary channel (rows ABCD) and to dedicated Switch2 slot over the secondary cross-connect channel.

/etc – contains configuration files and information about the M100.file system includes all payload applications and configurations. In the following table described I2C addresses for the physical notation of the slots: I2C Address 0x82 0x84 0x86 0x88 0x8A 0x8C 0x8E 0x90 0x92 0x94 0x96 0x98 0x9A 0x9C 0xC0 0xC2 0xC4 0xC6 0xC8 0xCA 0xCC 0xCE 0x10 0x12 0x20 0x14 0x16 Resource Slot1 Slot2 Slot3 Slot4 Slot5 Slot6 Slot7 Slot8 Slot9 Slot10 Slot11 Slot12 Slot13 Slot14 PEM1 PEM2 Fan Tray1 Fan Tray2 Fan Tray3 Fan Tray4 Fan Tray5 Fan Tray6 Right-hand Shelf Manager ShMC1 Left-hand Shelf Manager ShMC1 Active Shelf Manager Shelf FRU data board Telco Alarm board Table 4 – I2C Addresses Reference It is possible to access these FRUs using M100 over IPMB bus. ShMC version /etc/shm-version.conf – IPMI over LAN configuration /usr/etc/openhpi/openhpi. /usr/etc/ipmi_lan. There are two different notations of the slots: logical and physical. By the definition. as described in the following section.conf – Simple Network Management configuration /usr/local – persistent file support. /bin – contains executables for the operating system 4 I2C Addresses of the FRUs in CO14 Shelf The hardware addresses of the slots are defined on the backplane. Any files stored in this directory are persistent. messages in /var/log/messages /usr/etc – user defined configuration files. multiplying with 2 provides the I2C address of the FRU. It is stored as a compressed RAM disk on the flash and extracted into the RAM after the kernel has booted. Page 13 of 30 .3 Directory Structure on M100 /root . /var/log – log files.conf – HPI configuration /usr/etc/snmp/snmp. All changes in the disk file system will be lost after the shelf manager powers down.

For PICMG 3. This section provides information on which IPMI commands are supported. 5. Parameters – request parameters specific for every command. For a request command. NetFn is according to the following table: NetFn Request 0x06 0x06 0x06 0x0A 0x0A 0x0A 0x04 0x00 0x2c NetFn Response Function Classification 0x07 Global IPMI commands 0x07 System interface commands 0x07 Watchdog commands 0x0B SEL device commands 0x0B SDR repository commands 0x0B FRU inventory commands 0x05 Sensor device commands 0x01 Chassis device commands 0x2d PICMG 3. the NetFn is always even. NetFn – This contains the network function of the message. This is usually 0.5 Standard IPMI Commands The IPMC is fully compliant to the Intelligent Platform Management Interface v. Channel = 0. Channel = f. For further reading on the parameters of the commands please refer to the IPMI specification 1.0 commands the links to the parameters tables are summarized in the chapter 3.1. and <I2C_address> is omitted I2C_Address – as described in section 3 No.5. Channel – to access IPM controllers outside of the Shelf Manager No. Channel> <I2C_Address> <No.0 commands Table 5 – NetFn Assignment CMD – Command number as defined by IPMI or AdvancedTCA specification and summarized in the following table. LUN> <NetFn> <CMD> <Parameters>” smi 0 Where the variables are defined as described below: No. The most interesting commands are described further in this chapter with the required parameters. defines which unit is meant to respond to the message (see the IPMI specification for further definition).2 Command Assignments.10. Page 14 of 30 .1 Command syntax Format of the IPMI command implemented on the M100 Shelf Manager is as following: ipmicmd –k “<No. LUN – Logical Unit Number. Of particular interest is NetFn 2Ch (Request) and 2Dh (Response) for the commands stated in the AdvancedTCA specification.5 according to the references in the table. to access the local IPM controller No. The IPMI and IPMB specifications define the legal NetFns.

2 23.12 27.5 21.4 18.11 27.9 21.11 22.7 29.4 25.11 29.1 22.2 28.9 25.12 .1 23.5 25.2 25.2 29.17 28.14 23.3 29.7 25.3 18.10 25.13 27.13 29.15 27.3 22.7 18.4 29.8 18.2 22.Command CMD NetFn Request Get Device ID 0x01 0x06 Get Self Test Result 0x04 0x06 Master Write-Read 0x52 0x06 Set BMC Global Enables 0x2E 0x06 Get BMC Global Enables 0x30 0x06 Clear Message Flags 0x31 0x06 Get Message Flags 0x32 0x06 Enable Message Channel Receive 0x31 0x06 Get Message 0x33 0x06 Send Message 0x34 0x06 Read Event Message Buffer 0x35 0x06 Get BT Interface Capabilities 0x36 0x06 Reset Watchdog Timer 0x22 0x06 Set Watchdog Timer 0x24 0x06 Get Watchdog Timer 0x25 0x06 Get SEL Info 0x40 0x0A Get SEL Allocation Info 0x41 0x0A Reserve SEL 0x42 0x0A Get SEL Entry 0x43 0x0A Add SEL Entry 0x44 0x0A Delete SEL Entry 0x46 0x0A Clear SEL 0x47 0x0A Get SEL Time 0x48 0x0A Set SEL Time 0x49 0x0A Get SDR Repository Info 0x20 0x0A Get SDR Repository Allocation 0x21 0x0A Reserve SDR Repository 0x22 0x0A Get SDR 0x23 0x0A Add SDR 0x24 0x0A Partial Add SDR 0x25 0x0A Delete SDR 0x26 0x0A Clear SDR Repository 0x27 0x0A Get SDR Repository Time 0x28 0x0A Get FRU Inventory Area 0x10 0x0A Read FRU Data 0x11 0x0A Write FRU Data 0x12 0x0A Get Device SDR Info 0x20 0x04 Get Device SDR 0x21 0x04 Reserve Device SDR Repository 0x22 0x04 Get Sensor Hysteresis 0x25 0x04 Set Sensor Threshold 0x26 0x04 Get Sensor Threshold 0x27 0x04 Set Sensor Event Enable 0x28 0x04 Get Sensor Event Enable 0x29 0x04 Rearm Sensor Events 0x2A 0x04 Get Sensor Event Status 0x2B 0x04 Get Sensor Reading 0x2D 0x04 Set Event Receiver 0x00 0x04 Get Event receiver 0x01 0x04 Platform Event 0x02 0x04 Get Chassis Capabilities 0x00 0x00 Get Chassis Status 0x01 0x00 Chassis Control 0x02 0x00 Set System Boot Option 0x08 0x00 Get System Boot Option 0x09 0x00 Get POH Counter 0x0F 0x00 Table 6 – Supported IPMI commands Page 15 of 30 See Parameters in IPMI section 17.3 22.8 25.1 28.6 18.4 18.10 29.6 25.8 29.5 18.9 27.3 25.1 18.3 29.2 18.6 21.10 18.10 27.9 29.1 17.14 27.11 27.12 29.10 22.16 27.

0 IPMI commands Get PICMG Properties Get Address Info Get Shelf Address Info Set Shelf Address Info FRU Control Get FRU LED Properties Get FRU LED Color Set FRU LED State Get FRU LED State Set IPMB State Set FRU Activation Policy Get FRU Activation Policy Set FRU Activation Get Device Locator Record ID Set Port State Get Port State Compute Power Properties Set Power Level Get Power Level Renegotiate Power Get Fan Speed Properties Set Fan Level Get Fan Level Bused Resource Get IPMB Link Info See Parameters in ATCA Table 3-10 3-9 3-15 3-16 3-25 3-27 3-28 3-29 3-30 3-65 3-19 3-20 3-18 3-35 3-54 3-55 3-77 3-79 3-78 3-86 3-81 3-83 3-82 3-57 3-63 5.2.2 Useful Commands 5.2 IPMB State Bus A disabled: Bus B disabled: M100 bus A disabled: M100 bus B disabled: 5.1 FRU Control Cold reset: Warm reset: Graceful Reboot: Diagnostic Interrupt: ipmicmd –k “0 ipmicmd –k “0 ipmicmd –k “0 ipmicmd –k “0 <I2C_Address> 0 2C 4 0 0 0” smi 0 <I2C_Address> 0 2C 4 0 0 1” smi 0 <I2C_Address> 0 2C 4 0 0 2” smi 0 <I2C_Address> 0 2C 4 0 0 3” smi 0 ipmicmd –k “0 ipmicmd –k “0 ipmicmd –k “f ipmicmd –k “f <I2C_Address> 0 2C 9 0 0 1” smi 0 <I2C_Address> 0 2C 9 0 1 0” smi 0 0 2C 9 0 0 1” smi 0 0 2C 9 0 1 0” smi 0 5.2.Command CMD NetFn Request 0x00 0x2C 0x01 0x2C 0x02 0x2C 0x03 0x2C 0x04 0x2C 0x05 0x2C 0x06 0x2C 0x07 0x2C 0x08 0x2C 0x09 0x2C 0x0A 0x2C 0x0B 0x2C 0x0C 0x2C 0x0D 0x2C 0x0E 0x2C 0x0F 0x2C 0x10 0x2C 0x11 0x2C 0x12 0x2C 0x13 0x2C 0x14 0x2C 0x15 0x2C 0x16 0x2C 0x17 0x2C 0x18 0x2C Table 7 – Supported PICMG3.3 Set FRU Activation Policy Clear lock bit: Set lock bit: ipmicmd –k “0 <I2C_Address> 0 2C A 0 0 1 0” smi 0 ipmicmd –k “0 <I2C_Address> 0 2C A 0 0 1 1” smi 0 5.2.4 Set Power Level Set power off: ipmicmd –k “0 <I2C_Address> 0 2C 11 0 0 0 1” smi 0 Page 16 of 30 .2.

To log on to this utility in Shelf Manager shell type in: ipmitest /INTER ICMB Addr: 0 Channel: 0 The I2C address: <I2C_Address> To proceed the commands are chosen from the main menu.5 Get Fan Level Get fan level: ipmicmd –k “0 <I2C_Address> 0 2C 16 0 0” smi 0 5.2.2.10 Get Sensor Reading Get sensor reading: ipmicmd –k “0 <I2C_Address> 0 4 2D <Number>” smi 0 5.9 Get Sensor Threshold Get sensor threshold: ipmicmd –k “0 <I2C_Address> 0 4 27 <Number>” smi 0 5.8 Get Device SDR Get device SDR info: ipmicmd –k “0 <I2C_Address> 0 4 21” smi 0 5.6 Set Fan Level Set fan level: ipmicmd –k “0 <I2C_Address> 0 2C 15 0 0 <Fan_Level>” smi 0 Fan_Level – between 0x23 to 0x64 Shut fan down: ipmicmd –k “0 <I2C_Address> 0 2C 15 0 0 FE” smi 0 5.2. Page 17 of 30 .5.3 IPMI test All the IPMI commands available on M100 are summarized in the utility ipmitest in the interactive form.2.7 Set Event Receiver Stop events: Enable events: ipmicmd –k “0 <I2C_Address> 0 4 0 FF 0” smi 0 ipmicmd –k “0 <I2C_Address> 0 4 0 20 0” smi 0 5.2.2.

It can be set from 0. The cooling level has cooling zone scope. This means all events are handled but no set operations are executed. In the current configuration all resources are stored in one cooling zone.. There is no cooling management record that defines which resources are put into which cooling zone.4 Internal control mode cooling algorithm 6. This is the default mode and its algorithm is described below . A cooling zone can be considered as one virtual fan. If a fan is not found or it is in active state then the cooling level of its cooling zone is set to 100 .2 Cooling zones The cooling management splits an ATCA system into cooling zones.Discover all fan resources.4. The cooling management distinguishes the following cooling levels: .Scan and store all possible fan slots .3 Cooling level The cooling level determines how strong a system needs to be cooled. The current cooling level and the current fan level is identical.Basic cooling level: The cooling algorithm does not adapt this value. The control mode can be changed via HPI control as follows: hpicooling –m 1 for internal control mode hpicooling –m 2 for external control mode 6. Each cooling zone has a specified number of fans and is responsible for a set of FRUs to be managed.External control mode. 6.Get the basic cooling level from the openhpi config file and apply it to all fans Page 18 of 30 . This value cannot be under-run .Event cooling level: This is the cooling level dependent on the severity of asserted events ..1 Cooling control modes The cooling management can be switched to the following modes: . An external application is responsible for cooling management.1 Startup During startup of the system the fan run with its internal default fan level. The fan level can be set according to the current cooling level. A cooling zone can also own an inlet and outlet sensor to monitor and control the temperature difference. The fan level is set to its default value until the external application takes control If the cooling mode is set to other than internal control the internal cooling management is not turned off but monitors the system only. If the internal cooling management has control again it executes all necessary cooling actions according to the actual state of the system. All fans within the cooling zone run at the same fan level. If the cooling management becomes active the following actions are executed: .Internal control mode. 6.100 and can be expressed in percent.Current cooling level: The current cooling level is calculated as follows: basic cooling level + event cooling level 6.6 HPI Cooling The ATCA-M100 Shelf Manager provides a managed cooling functionality for the Tracewell ATCA systems.

conf) upper major assertion event +30% yes (openhpi. 6. Thus cooling level is increased dynamically to ensure proper cooling of the system. 6.2. Page 19 of 30 .4. Before decreasing the cooling level the algorithm checks if another FRU needs the current cooling level.conf) upper critical assertion event +50% yes (openhpi.Upper major .2 Deassertion temperature event If a deassertion event is received from a resource the cooling algorithm decreases the cooling level every 60sec by 10.4.After startup the cooling management waits and reacts on hotswap and temperature events from FRUs located in the ATCA boards or RTM zones. Type Cooling level Modifiable basic 30% yes (openhpi.2 Extraction event If the extraction event is generated from a fan resource the cooling level is set to100.3.2 Hot Swap event handling 6. 6.2.3.4 Difference temperature handling There is no monitoring of inlet and outlet sensors and therefore no cooling management based on temperature difference. If this is the case the cooling management sets the fan level of its cooling zone to the current cooling level.4.4.Upper minor .3 Temperature event handling The cooling reacts on the following temperature events: .4.1 Assertion temperature event If an assertion upper event is received from a resource the cooling level is increased as specified in Table1. If a deassertion event is not received within a given time (set 30sec) the cooling level will be increased by 10.conf) Table 8 – Cooling levels 6. If it is generated from a FRU and this FRU has temperature events asserted the cooling algorithm reevaluates the current cooling level and set the fan level based on the basic cooling level and the event cooling level.Upper critical 6. 6. The cooling management checks if all fans are present and in state active now.conf) upper minor assertion event +10% yes (openhpi.4. Thus cooling level is decreased dynamically if no assertion events are pending to ensure noise reduction.1 Insertion event An insertion event is only handled if it is generated from a fan resource.4.

5 External control mode 6. In this mode the cooling management does not react on hotswap and temperature events from FRUs. 6. it is possible to change the speed of the fans to another level. When the Shelf Manager becomes active and in the previous run HPI cooling has been set to the external mode.1 Startup During startup of the system the fans run with the internal default fan level.5.5.6.2 Setting cooling level The cooling level for the external control mode can be changed via HPI as follows: hpifan –s <Fan_Level> For example the cooling level of the fans can be set to 80% as follows: hpifan –s 80 Page 20 of 30 .

hpievents Page 21 of 30 . To get a listing of all the available hpi utilities on the Shelf Manager type hpi and click twice on Tab. one Shelf Manager becomes active another becomes standby. Internal cooling: hpifan –m 1 External cooling: hpifan –m 2 7. 7.3 Hpievent Get HPI events. 7.7 HPI Commands 7. The syntax of the command is as following: hpifan –s <Fan_Level> Fan_Level – between 40 to 120 (depends on thresholds of the fan speed set on the Fan Trays) Please note: setting fan level is possible in case that HPI cooling policy is set to external as described in previous section.1 Hpifan Get and set fan level of the Fan Trays. Discovers and displays the events on the screen as they are recognized by M100. To find out whether the Shelf Manager is active in the M100 shell type in: sv_status On the active Shelf Manager HPI is running.2.4 Hpievents Get sensor SDRs and wait for the HPI events and interpret them.2 Hpicooling Sets the cooling policy as described in previous section.2. therefore the reply shall be: openhpid is active On the standby Shelf Manager HPI is stopped.2. therefore the reply shall be: openhpid is inactive If a single Shelf Manager plugged into the system or the handle on the other Shelf Manager is released and it has reached M1 state the reply shall be: openhpid is running alone 7. hpievent 7. Please note: in bold are written commands and options.2.2 Utilities To get help for all the utilities type the name of the utility and -h.1 Supervisor status When the system powers up if Shelf FRU data is correct.

to activate.5 Hpifruactivation Get FRU activation and set FRU activation. hpihotswap [options] -n <LED_number> -l -o -t -1 <on_duration> -0 <off_duration> number of the LED to set the state LED local control mode LED override mode LED test mode LED on duration [0-255] LED off duration [0-255] Page 22 of 30 .2.2.2. hpiinv 7.8 Hpiinv This commands presents FRU inventory information of all the FRUs in the system.9 Hpiled This command gets LED state and sets LED state.2.2. It also tests for incorrect checksums or inconsistence.7. hpihotswap [options] -s -a -d -i -e show hotswap resources activate resource ID deactivate resource ID insert resource ID extract resource ID 7.7 Hpihotswap This commands allows to show hotswap resources.6 Hpipoweronseq Get power on sequence and set power on sequence. hpifruactivation [options] -e <Entity_Path> -d <Delay> use explicit Entity_Path for FRU activation (get using hpihotswap) set delay before next power on to Delay/10 [sec] 7. insert and extract resource ID. deactivate. hpipoweronseq [options] -e <Entity_Path> -a <Time> -s <Res_ID_List> use explicit Entity_Path (get using hpihotswap) set allowance for FRU activation readiness to Time [sec] set power on sequence as specified in Res_ID_List 7.

hpilog [options] -s <log_number> -i -w number of logging to set log severity info severity warning 7.12 Hpireset3 Resets HPI resource. used in combination with either –d or –r clear SEL delete record with <Record_ID> show new records and delete record Page 23 of 30 . hpiredundancy [options] -e <Entity_Path> -i -g use explicit Entity_Path initiate switchover get redundancy state 7.2.2. hpiresid 7.13 Hpiresid Get own resource ID.10 Hpilog Gets and sets log levels for different facilities of the Shelf Manager.11 Hpiredundancy Gets and sets log levels for different facilities of the Shelf Manager.15 Hpiseledit Displays content of the SEL (event locator) and allows to edit the entries. hpiseledit [options] -r <Resource_ID> -d -n -c -k <Record_ID> -s use explicit Resource ID use domain event log newest first.2.2.7.2. hpireset3 [options] -r <Resource_ID> use explicit Resource ID (get RID by typing hpireset3 without parameters) 7.14 Hpisel Displays content of the SEL (event locator). hpisel 7.2.

0.7.171 compared to the default 172.36.8.16 Hpisensor Get all sensors and read all the sensor thresholds.16. hpishaddr [options] -e <Entity_Path> set root Entity_Path For example: hpishaddr –e “{RACK.86.171 This sets the base Backplane address to: 172. This changes the third octet of the record.171 This sets the base Out of Band address to: 192.2.171 compared to the default 192. This changes the first two octet of the IP record.171.0.1}” This sets the third octet to 1: 192.1.0.19 Hpiship This command allows to get and set Shelf base IP address.2.36.2.0} {ADVANCEDTCA_CHASSIS.168.0.18 Hpishaddr This command allows to get and set Shelf base address. hpisensor [options] -t -x show thresholds show extra debug messages 7.168.0.2.168. hpiship [options] -n <Shelf_IP_record_number> -i <IP_address> -g <Gateway> -m <Sub_mask> Shelf IP record number (Backplane and Out of Band records) the new IP the new gateway the new mask For example: hpiship –n 1 –i 172.2. 7. hpiship –n 0 –i 192.8 compared to the default 192. hpisettime [options] -d -t -x date in mm/dd/yyyy format time of the date in 24 hour format show extra debug messages 7. hpitestredundancy Page 24 of 30 . 7.20 Hpitestredundancy Test redundancy of the FRUs.0.17 Hpisettime This command allows to set SEL time.171.86.0.

hpiupgrade [options] -s <num> -u <url> -f <filename> -d -l -i -k -b -m -a -vu -vk -vi -vm Resource number (use hpiupgrade without parameters) To download the upgrade image in case of the remote upgrade Filename of the upgrade file download (copy file to the Shelf Manager) upload (copy file from the Shelf Manager) flash filesystem image (of the Shelf Manager. hpithres 7. used only for M100 software upgrade) flash firmware image (used for firmware upgrade of the FRUs or M100) abort current upgrade process show u-boot version (boot section of the Shelf Manager) show kernel version (kernel section of the Shelf Manager) show initrd version (file system section of the Shelf Manager) show firmware version (IPMC firmware) For example: hpiupgrade -s 14 -f fw_fan. Allows getting firmware version of the FRUs and upgrade of the FRUs. 7.21 Hpithres Get thresholds of the FRUs.23 Hpiuserinfoarea Get User Info Area and set the content of User Info Area.2.2. used only for M100 software upgrade) flash boot image (of the Shelf Manager. used only for M100 software upgrade) flash kernel image (of the Shelf Manager.7. upgrade software of the Shelf Manager.hex –m This command upgrades one Fan Tray corresponding to number 14 with the image. hpiuserinfoarea [options] -e <Entity_Path> -s <String> -x use explicit Entity_Path of the User Info Area write <String> to user info area display user info area as hexadecimal numbers Page 25 of 30 .2.22 Hpiupgrade Gets software version of the Shelf Manager.

In case of an error or inconsistency of the information the script will quit upgrade. kernel and directory structure) or the current ShMC by running the following commands with <resource_number> of the Shelf Manager: hpiupgrade -s < resource_number> -b <boot_image > hpiupgrade -s < resource_number> -k <kernel_image > hpiupgrade -s < resource_number> -i <root_image > Page 26 of 30 . As well versions are presented for verification.sh script and hpiupgrade using HPI. 8.1 Firmware Upgrade There are two possible firmware upgrade options: fw_upgrade. clear the lock bit: ipmicmd –k “0 <I2C_Address> 0 2C A 0 0 1 0” smi 0 Please note that Shelf Manager cannot upgrade own firmware.1 swupgrade This script has the following options: swupgrade -b <boot_image> swupgrade -k <kern_image > swupgrade -r <root_image > 8.1. ATCA boards or the other Shelf Manager) with image <image> please find out the resource number by typing hpiupgrade.2 Hpiupgrade It is possible to upgrade the software (boot. as long as IP address of the active Shelf Manager is set outside of the firewall.2.1 fw_upgrade. 8.8 Software Upgrade Software upgrade can be performed remotely. PEMs. For further details please refer to previous section for details on hpiupgrade. The latter one is recommended since the script is no longer supported. After the upgrade FRU goes to M1 state. 8.1. thus it can upgrade the second one. 8.2 Hpiupgrade To upgrade FRU (Fan Trays.sh <I2C_Address> a <image> a upgrade all available instances in the image It verifies the Get device ID properties of the upgraded FRU and compares with the image.2 Software upgrade on the M100 8.sh This script has the following options: fw_upgrade. To activate it.2. Then type in the shell of the Shelf Manager: hpiupgrade -s < resource_number> -f <firmware_image> –m It should take about 2 minutes to upgrade the FRU depending on the image.

1 Fan Tray Main board Sensors FRU ID 0 Name Fan HotSwap IPMB 0 Status FW Revision ISC Fan_MTBF Tracewell Fan Board Fan Speed M1 Fan Speed M2 Main Temp.B FAN MCU 13U FT (FRU ID 0) Number (DEC) Number (HEX) 132 0x84 133 0x85 136 0x88 1 0x01 0 0x00 2 0x02 3 0x03 6 0x06 7 0x07 1 0x01 Table 9 – Fan Tray main sensors FRU ID 0 LUN (HEX) 0 0 0 0 0 0 0 1 1 3 9.1.A Main Temp. FAN MCU 13U FT (FRU ID 1) Number (DEC) Number (HEX) 132 0x84 133 0x85 136 0x88 1 0x01 0 0x00 4 0x04 5 0x05 8 0x08 1 0x01 Table 10 – Fan Tray RTM sensors FRU ID 1 Page 27 of 30 LUN (HEX) 0 0 0 0 0 0 0 1 3 .1 Fan Trays 9.1.9 SDRs in Tracewell FRUs 9.2 Fan Tray RTM Sensors FRU ID 1 Name Fan HotSwap IPMB 0 Status FW Revision ISC Fan_MTBF Tracewell Fan Board Fan Speed R1 Fan Speed R2 RTM Temp.

0 Board Temp.1 Power Sensors FRU ID 0 13U PEM FRU ID0 (power) Name HotSwap IPMB 0 Status Shelf Voltage A Shelf Current A Shelf Power A Shelf Voltage B Shelf Current B Shelf Power B Board Temp.2 PEMs While the PEM is a single FRU it has two functions. 9.2.1 PEM Board Number (HEX) 0x84 0x85 0x02 0x03 0x04 0x05 0x06 0x07 0x00 0x01 0x01 Table 11 – PEM main sensors FRU ID 0 LUN (HEX) 0 0 0 0 0 0 0 0 1 1 3 9.2.2 Alarm Sensors FRU ID 1 13U PEM FRU ID 1 (alarms) Name Critical Alarm Alarm Major Alarm Minor Power Alarm Reset Major Reset Minor User defined Alarm 3 User defined Alarm 4 User defined Alarm 5 Number (HEX) 0x08 0x09 0x0A 0x0B 0x0C 0x0D 0x0E 0x0F 0x10 Table 12 – PEM RTM sensors FRU ID 0 Page 28 of 30 LUN (HEX) 0 0 0 0 0 0 0 0 0 . Power has the Entity ID of 0x15 and is accessed at FRU ID 0 at the appropriate IPMI address derived from the hardware address.9. Alarms have the Entity ID of 0xF3 and are accessed at FRU ID 1 at the same IPMI address. Power input and filtering and alarm contact.

An additional shelf FRU data IPMC can be fitted if required to provide two static and two dynamic shelf FRU data copies. • • • • Chassis Information per IPMI section 10 Backplane (board) Information per IPMI section 11 Product Information per IPMI section 11 o To these areas we add custom information fields for ECN and Firmware versions Multirecord areas per IPMI section 16 and PICMG 3. 0x0E.Inc.1.2 Data The following shelf data is stored in FRU ID 1 in the configuration board at the I2C address 0x14. 10.0 are as follows: o IP address o Address area o Power area o Activation record o Base channel connectivity o Update channel connectivity o Fabric channel connectivity o Force defined User Info Area using Force OEM ID 0x48. 10. 0x00 A copy of a typical shelf record stored at the I2C address 0x14 is as following: FRU ID: 1 FRU size is 0 Chassis info area Chassis type: 17 Chassis Part Number: 30702844 Chassis Serial Number: 0509624194000004 Board info area Manufacturing date: 511fba Board Manufacturer: Tracewell Systems. one fixed copy and two dynamic shelf manager copies. Inc.1 Repository Shelf FRU data is stored in a private controller with the same structure as a field replaceable unit.1.10 Shelf FRU Information Shelf FRU information contains the essential information for correct operation of the Shelf. Board Product Name: CO 14 DS L3 U3 M1 P1 Board Serial Number: 0509624194000004 Board Part Number: 30702844 Board FRU File ID: Product info area Manufacturer name: Tracewell Systems. the shelf is also a field replaceable unit.) Data is read from the IPMC and stored in the shelf managers so there are always triple copies stored in the system. (Essentially. Product Name: ATCA 13U 14 slot shelf Page 29 of 30 .

eolver 0x2) PICMG specific record Shelf Manager IP Connection Record Record type: 0xc0 (length 17. eolver 0x2) PICMG specific record Shelf Activation and Power Management Record Record type: 0xc0 (length 227. eolver 0x2) PICMG specific record Address table Record type: 0xc0 (length 17. eolver 0x2) PICMG specific record Shelf Power Distribution Record Record type: 0xc0 (length 147. eolver 0x2) PICMG specific record Backplane Point-to-Point Connectivity Record Record type: 0xc0 (length 227.Product Part Number: 30702844 Product Version: 0001 Product Serial Number: 0509624194000004 Asset Tag: Product FRU File ID: Manufacturing date: 511fba Multirecord area Record type: 0xc0 (length 114. eolver 0x2) PICMG specific record Backplane Point-to-Point Connectivity Record Record type: 0xc0 (length 23. eolver 0x2) PICMG specific record Backplane Point-to-Point Connectivity Record Record type: 0xc0 (length 101. eolver 0x82) Force specific record user info area record Value is : USER INFO AREA Page 30 of 30 . eolver 0x2) PICMG specific record Backplane Point-to-Point Connectivity Record Record type: 0xc0 (length 251. eolver 0x2) PICMG specific record Shelf Manager IP Connection Record Record type: 0xc0 (length 130.