T081 - Dell PowerVault ML6000 Maintenance Manual

T081

T081 - Incorrect Module Brand
Description
Detection Scenarios
Root Causes
Service Resolution
Steps
PowerVault ML6000 Maintenance Guide
GUI Description: The library detected an incompatible module brand that
does not match the library configuration.
Explanation:
The branding of a system is accomplished in two different ways. The firmware
uses information saved on the compact flash to determine what brand the
firmware and GUIs will present to the user. There is also physical branding of
the system in the form of different cosmetic skins, badging, paint, external
labels, and so forth, each module. In addition, each module has a machine-
readable barcode label that carries a module serial number and branding
information that should match the physical branding of the module. The library
manufacturing process should install a machine-readable barcode label that
matches the external, user- visible branding of the module.
Because the library robot can read this barcode label, it can check the
branding of the physical modules against the branding of the firmware and
GUIs. This RAS ticket is a defensive tool used to notify the user that there is a
mismatch in the branding mechanisms. The root cause of a mismatch can be
manufacturing defects, logistical errors (shipping the wrong spare part), or
user errors such as moving parts between systems. The parts would
mechanically fit together, but the system would recognize the mismatch.
At library bootup time, the robot attempts to scan all module barcode labels.
When the OID number on each label is read, the embedded branding
information is compared to persisted data on the system compact flash.
• Various manufacturing defect errors, mislabeling, or part mix-ups.
• Spare part logistics error where wrong module FRU or compact flash FRU
is sent to a customer site.
• End users or Service personnel mixing and matching hardware from multiple
systems of different branding in the field.
• Malicious intent, where customers attempt to buy and combine hardware
from different sources.
• Barcode reader is not scanning the labels correctly.
1 Perform DR040 - Resolve Incompatible Module Branding
2 Clear the RAS ticket. Upgrade the library firmware to 400G or later and run
the IVT - Picker test using the Library Tests option accessed through the
operator panel. If the test passes reboot the unit and see if the RAS ticket
persists.
Note: IVT is optimized for library firmware versions 520G and above and
libraries built after July 1, 2008 (serial numbers with last four digits 8602 and
above).
• If your library was built on or before July 1, 2008, and you are running
firmware version 520G or later, you will not be able to run the IVT test, even
though the selection is available.
• If your library was built on or before July 1, 2008, and you are running
firmware version 500G or earlier, you can run the test, but it is not
recommended because it may produce erroneous results.
on page 385.
281