Device identification data error



HP BladeSystem

Device Bay Status tab

Selecting a specific blade within the enclosure opens the Device Bay Information, the Bay xx page, where xx is the bay selected. Information provided on this screen includes tabs for Status, Information, Virtual Buttons, Boot Options, and IML Log.

The Server Management section of the page contains links to aid the management of the server blade in the device bay.

Device Identification Data

Information such as model name, part number, serial number, and other information used to identify the device is checked. This data is also referred to as FRU data. If the data is not present or not readable by the Onboard Administrator, then a device identification data error appears. Possible values are OK or Error.

Status of the iLO. Possible values are OK or Error.

Temperature is above the warning threshold. Possible values are OK or Temperature Warning.

Temperature is above the danger threshold. Possible values are OK or Critical temperature threshold reached.

Device bay configuration is incorrect. If a storage blade is partnered with a full-height server blade, and the server blade does not have the correct mezzanine card, then an invalid I/O configuration results. Possible values are OK or I/O mismatch detected.

Power Allocation Request

There is insufficient power to adequately power this server blade. Possible values are OK or Insufficient enclosure power.

There is an insufficient number of fans to properly cool this server blade, or the fan configuration is incorrect. Possible values are OK or Insufficient fans for enclosure cooling.

The server blade has been placed in the wrong slot in the enclosure according to the current fan configuration. Possible values are OK or Incorrect location for proper device cooling.

Device has failed. Status was not requested by the Onboard Administrator. Possible values are OK or Error.

Device has failed. Status was requested by the Onboard Administrator. Possible values are OK or Error.

Detects an iLO network configuration problem. Possible values are OK or iLO network configuration problem, check connectivity to iLO default gateway. If the problem continues, then attempt to reset iLO using the iLO GUI or the Onboard Administrator CLI HPONCFG command to send a script command to reset iLO.

A memory error occurred on the server blade. Follow the instructions listed to correct the error.

Displays status of the mezzanine card, if installed. Possible values are OK or Error.

Duplicate IP Address

A check to see if a duplicate IP address exists on the network during assignment. Possible values are OK or an informational message indicating there is a duplicate IP address on the network.

Enclosure Dynamic Power Capping

A warning that communication with iLO has been lost and power capping cannot be set.

Partner Device Link

Possible values are OK or Inappropriate device in adjacent bay. If the server blade is not partnered with a storage blade, this information does not appear.

Virtual Connect Configured

Possible values are Configured for Virtual Connect or Not configured for Virtual Connect. When the server blade is Not configured for Virtual Connect, an informational icon with an Other status appears. Go to the Virtual Connect Manager to configure the server blade profile.

Читайте также:  Android google play services version error

Low Power Request

The blade reported an abnormally low power requirement. The blade was powered off and did not release all of the power. The blade will continue to operate properly but a service representative needs to be contacted to correct the issue.

The storage blades has a disk tray that extends from the blade housing. Possible values are Open or Closed.

Temperature sensors

Location of sensor in the device

This is the status of the temperature sensor. The status matches the graphic presentation of the temperature.

Graphic presentation of temperature

The iLO for the server blade in the device bay is available by clicking iLO. The server-generated iLO page appears, which is separate from Onboard Administrator.

The Onboard Administrator provides a one-time login (login bypass) to ProLiant iLO management processors. The iLO access levels are mapped by the Onboard Administrator privilege level (user must have access to the bay):

Onboard Administrator Administrator—Administer User Accounts, Remote Console Access, Virtual Power and Reset, Virtual Media, Configure iLO settings.

Onboard Administrator Operator—Remote Console Access, Virtual Power and Reset, Virtual Media.

A temporary iLO user is created when an Onboard Administrator user launches the iLO Web Interface or an iLO remote console. The Onboard Administrator can create up to a maximum of three temporary accounts for each iLO. If three or more temporary Onboard Administrator accounts are already on an iLO, then the Onboard Administrator deletes the oldest temporary users in iLO user databases.

Port Mapping Information

For information regarding port mapping for all devices in the device bay, click Port Mapping Information.

Firmware

Firmware information for devices in the device bay is available by clicking Firmware.

The device bay within the enclosure

The model number of the device

The component for which the firmware information is provided

The version of the firmware installed on the component

Firmware ISO Version

The latest version of firmware available for installation on the component

NOTE: A letter included after the firmware version indicates a smart component release note revision. This revision is not a functional firmware update.

NOTE: If the blade firmware does not match the DVD ISO firmware after a server is discovered or updated, an informational icon is displayed.

Firmware log

This log displays detailed information for the last Enclosure Firmware Management operation executed on the server. This log is specific for the server, and is cleared any time a new Enclosure Firmware Management operation is started on the server. This log is also cleared when the server is removed from the enclosure.

The firmware log is the most useful resource to determine the progress of an Enclosure Firmware Management operation on a particular server.

Session Log

This log displays detailed information for the last Enclosure Firmware Management operation executed on the server and logs the entire session to the iLO VSP. This log is specific for the server, and is cleared anytime a new Enclosure Firmware Management operation is started on the server. This log is also cleared when the server is removed from the enclosure.

Источник

Device identification data error

Принесли на корректировку русского языка N95 слайдер, тело новое и
работает без проблем но при этом инфинити рпл с неё не бэкапит хотя
девайс ид определяет вроде как . лог процессов ниже:

==== log opened: [04.11.2007 15:52:11] ====
Application: C:\Program Files\InfinityBox\ChineseMiracle\ChineseMiracle.ex e
Loading data, wait.
[Infinity Box] v1.63
S/N: хххх:хххх
Wait.
Device: Autodetect 6205-6227 NOR
Done
COM6 [Serial2] selected
Device: Autodetect 6205-6227 NOR
Checking data, wait.
advanced flash detection active
Action: read NOR flash
Boot.
Press and HOLD Power button now !
baud autodetection active
19200
Connecting, wait.
Initializing[6226:8A02:8A01].
high speed disabled
boot step size: 0002
Release Power button now !
Boot Done
Initialize.
detecting chip #00 in region #00.
flash: EC257E25082501:29EA0000000000
flash: Samsung AMD/Fujitsu std [D 0008×002000 00FEx010000 0008×002000] 16Mb
number of flash chip/regions detected: 01/01
Initialize Done
Set baud.
921600
Set baud Done
Identification.
device parameters autodetection in progress..
detecting chip #00 in region #00.
flash: EC257E25082501:29EA0000000000
flash: Samsung AMD/Fujitsu std [D 0008×002000 00FEx010000 0008×002000] 16Mb
number of flash chip/regions detected: 01/01
total flash region size: 01000000
detect device identification, method #1.
detection phase #1.
detect device parameters finished
structure: 2nd [enhanced] (or higher) generation
identification data damaged, recalculation required
identification detection finished
device-id: 7C76681E
protocol ver: 04
ver. sw1: N618_PCB01_GPRS_MT6227_S01.BIN
ver. sw2: N618.1
ffs offset/size: 00E00000/00200000
detecting eeprom area in 1 chip(s).
flash: EC257E25082501:29EA0000000000
checking area[00000000]: 00000000-00FFFFFF.
eeprom found near: 00E00000
detecting eeprom size.
eeprom size: 00200000
eeprom chip: 00
eeprom area: 00000000:00E00000-00FFFFFF
detecting languages.
.
language parameters detected
detected languages: Ru En Vn
reading [flash[N618_PCB01_GPRS_MT6227_S01.BIN]].
file saved: backup_flash[N618_PCB01_GPRS_MT6227_S01.BIN]_20071104-155847.B0M.bin
Finished, time used: 270 sec
Remove/Install battery now !
COM6 [Serial2] selected
Device: Autodetect 6205-6227 NOR
Checking data, wait.
advanced flash detection active
Action: read eeprom
Boot.
Press and HOLD Power button now !
baud autodetection active
19200
Connecting, wait.
Initializing[6226:8A02:8A01].
high speed disabled
boot step size: 0002
Release Power button now !
Boot Done
Initialize.
detecting chip #00 in region #00.
flash: EC257E25082501:29EA0000000000
flash: Samsung AMD/Fujitsu std [D 0008×002000 00FEx010000 0008×002000] 16Mb
number of flash chip/regions detected: 01/01
Initialize Done
Set baud.
921600
Set baud Done
Identification.
device parameters autodetection in progress..
detecting chip #00 in region #00.
flash: EC257E25082501:29EA0000000000
flash: Samsung AMD/Fujitsu std [D 0008×002000 00FEx010000 0008×002000] 16Mb
number of flash chip/regions detected: 01/01
total flash region size: 01000000
detect device identification, method #1.
detection phase #1.
detect device parameters finished
structure: 2nd [enhanced] (or higher) generation
identification data damaged, recalculation required
identification detection finished
device-id: 7C76681E
protocol ver: 04
ver. sw1: N618_PCB01_GPRS_MT6227_S01.BIN
ver. sw2: N618.1
ffs offset/size: 00E00000/00200000
detecting eeprom area in 1 chip(s).
flash: EC257E25082501:29EA0000000000
checking area[00000000]: 00000000-00FFFFFF.
eeprom found near: 00E00000
detecting eeprom size.
eeprom size: 00200000
eeprom chip: 00
eeprom area: 00000000:00E00000-00FFFFFF
detecting languages.
.
language parameters detected
detected languages: Ru En Vn
reading [eeprom[N618_PCB01_GPRS_MT6227_S01.BIN]].
file saved: backup_eeprom[N618_PCB01_GPRS_MT6227_S01.BIN]_20071104-160040.B0E.bin
Finished, time used: 62 sec
Remove/Install battery now !
COM6 [Serial2] selected
Device: Autodetect 6205-6227 NOR
Checking data, wait.
advanced flash detection active
Action: read/check detailed information
Boot.
Press and HOLD Power button now !
baud autodetection active
19200
Connecting, wait.
Initializing[6226:8A02:8A01].
high speed disabled
boot step size: 0002
Release Power button now !
Boot Done
Initialize.
detecting chip #00 in region #00.
flash: EC257E25082501:29EA0000000000
flash: Samsung AMD/Fujitsu std [D 0008×002000 00FEx010000 0008×002000] 16Mb
number of flash chip/regions detected: 01/01
Initialize Done
Set baud.
921600
Set baud Done
Identification.
device parameters autodetection in progress..
detecting chip #00 in region #00.
flash: EC257E25082501:29EA0000000000
flash: Samsung AMD/Fujitsu std [D 0008×002000 00FEx010000 0008×002000] 16Mb
number of flash chip/regions detected: 01/01
total flash region size: 01000000
detect device identification, method #1.
detection phase #1.
detect device parameters finished
structure: 2nd [enhanced] (or higher) generation
identification data damaged, recalculation required
identification detection finished
device-id: 7C76681E
protocol ver: 04
ver. sw1: N618_PCB01_GPRS_MT6227_S01.BIN
ver. sw2: N618.1
ffs offset/size: 00E00000/00200000
warning: invalid identification, ask/rpl calculation reqired
error: rpl file not found: C:\Program Files\InfinityBox\ChineseMiracle\id.7C76681E._N618 _PCB01_GPRS_MT6227_S01.BIN_040A1DE7_.rpl
file saved: id.7C76681E.[N618_PCB01_GPRS_MT6227_S01.BIN_040A1DE7].ask
ASK file created Ok
Probably identification data damaged,
device id: 7C76681E
firmware version:
N618_PCB01_GPRS_MT6227_S01.BIN_040A1DE7
RPL file must be in folder: C:\Program Files\InfinityBox\ChineseMiracle\
You can create RPL from ASK via client/server right now and press YES.

Do you want to write RPL file now ?
RPL file declined by user
detecting eeprom area in 1 chip(s).
flash: EC257E25082501:29EA0000000000
checking area[00000000]: 00000000-00FFFFFF.
eeprom found near: 00E00000
detecting eeprom size.
eeprom size: 00200000
eeprom chip: 00
eeprom area: 00000000:00E00000-00FFFFFF
detection phase #3.
. .
done
detecting structure pass 1.
.
detect standard fat location pass #1.
. .
detect extended fat location pass #1.
. ..
detect standard fat offset pass #1.
detect standard fat data.
fat layout detection complete
eeprom element #1 detected ok
detecting languages.
.
language parameters detected
detected languages: Ru En Vn
Finished, time used: 103 sec
Remove/Install battery now !
Action: read information
Model: Autodetect 6205-6227 NOR
Checking data, wait.
Phone should be Switched ON !
Connecting, wait.
Phone detected, wait.
Hardware version: MT6226, E02
Hardware version: N618_HW
Software version: N618_En_Vie_Ru.1″
Software date: 2005.04.12
Barcode: MT012345678901234567
imei: 353368007359650
Finished, time used: 5 sec
Power off phone now !

Хотелось бы прояснить что не так с этом телом — это новая неизвестная
программе версия прошивки в которой пока невозможно определить
по какому адресу бэкапить рпл или что-то иное ?

И как я понимаю инфинити при прошивке подобных китов бэкапит а
после записи возвращает область рпл в тело и соответственно это
тело даже при установленной галке смарт врайт после прошивки
имеет все шансы накрыться ?

Собственно несовсем понятно почему обязательно надо бэкапить и
возвращать в тело рпл если мы хотим перелить не фулл а только
область где находятся языковые ресурсы ?

Источник

Оцените статью
toolgir.ru
Adblock
detector