Download Shelf Manager User Guide

Pigeon Point Shelf Manager User Guide
The option -c removes (clears) the HPDL data or SDRs, respectively, from the target FRU
Information.
For example, the following commands can be used to update the Shelf FRU Information with new
versions of HPDL data and SDRs on a shelf where the Shelf FRU Information is stored in two
redundant EEPROMs on the backplane, accessed locally by the Shelf Manager:
#clia
#clia
#clia
#clia
frudataw
frudataw
frudataw
frudataw
-d
-s
-d
-s
20
20
20
20
1
1
2
2
std14slot.hpdl.bin.gz
std14slot.sdr.bin.gz
std14slot.hpdl.bin.gz
std14slot.sdr.bin.gz
3.6.4.4 Placing HPDL Data and SDRs in the FRU Information for Specific
FRUs
This section addresses placing HPDL data and SDRs into the FRU Information for a specific FRU
(e.g. a fan tray). This information is used by the Shelf Manager to amend the attributes of that FRU
from the attributes for that FRU that are specified in the HPDL chassis definition.
The following information about the FRU is supplied in the chassis definition and cannot be
redefined by the HPDL data in the FRU:
 FRU site type and number
 Presence signal definition.
Device selection definitions can be redefined by the HPDL data in the FRU; however a problem
arises when several slots exist in the chassis for the same type of the FRU, and addresses of
devices of the FRU are different between different slots. In that case, it is not possible to define
device location information on the FRU level; it is possible to do that only on the chassis level. This
consideration limits the possibilities of redefining device information on the FRU level.
It is not necessary to have both HPDL data and SDRs in a given FRU Information area; only HPDL
data or only SDRs may be present. For example, to change the power consumption of the FRU, it
is sufficient to have only HPDL data. To change certain sensor attributes (e.g. the conversion
formula, default threshold values or default hysteresis), it is sufficient to have only SDRs.
One problem with using HPDL data in a specific FRU is how to correlate the sensor numbers in the
description to the actual sensor numbers. The sensor numbers are assigned within an IPM
controller, not within a specific FRU, so the same sensors on different FRUs of the same type have
different numbers; and it is typically not known in advance in which slot a specific FRU is going to
be placed. This problem is solved in the following way: the sensor numbers in the HPDL/SDR data
for a specific FRU have relative numbers, and these numbers are correlated to the actual numbers
in ascending order.
For example, assume that the replacement SDRs describe sensors 1, 2, 3 and 4, and the sensor
numbers for the corresponding FRU in the HPDL chassis definition are 124, 208, 209 and 210. In
that case, the replacement SDR for sensor 1 applies to sensor 124; the replacement SDR for
sensor 2 applies to sensor 208, and so on.
Release 3.5.1
123
August 17, 2015