02a2 bmc system error log sel full

Сообщения без ответов | Активные темы

Автор	Сообщение
	Заголовок сообщения: Нужна помощь IT специалиста Добавлено: 01 окт 2013, 17:32
Любитель медалек и прочей навесной шелухи Зарегистрирован: 20 дек 2009, 18:38 Сообщения: 3064 Откуда: ЮВАО	Проблема в следующем: сервер HP ProLiant ML150. В BIOS-е есть параметр Server Asset Text, в качестве значения пустое текстовое поле. Если оставляю его пустым, прописываю произвольные символы или вписываю SERVER, то в любом случае при загрузке появляется ошибка: O2A2:BMC System Error Log (SEL) Full. Какое значение нужно указать в этом поле? Заранее благодарю за помощь! _________________ 我問不問愚蠢的問題
Вернуться к началу

Планета	Заголовок сообщения: Re: Нужна помощь IT специалиста Добавлено: 01 окт 2013, 21:23
Зарегистрирован: 19 ноя 2010, 22:05 Сообщения: 866
Вернуться к началу

e2-e4	Заголовок сообщения: Re: Нужна помощь IT специалиста Добавлено: 01 окт 2013, 22:26
Зарегистрирован: 20 дек 2009, 18:38 Сообщения: 3064 Откуда: ЮВАО
Вернуться к началу

AiD	Заголовок сообщения: Re: Нужна помощь IT специалиста Добавлено: 02 окт 2013, 08:24
Зарегистрирован: 21 дек 2009, 19:13 Сообщения: 462
Вернуться к началу

e2-e4	Заголовок сообщения: Re: Нужна помощь IT специалиста Добавлено: 02 окт 2013, 09:49
Зарегистрирован: 20 дек 2009, 18:38 Сообщения: 3064 Откуда: ЮВАО	AiD писал(а): Вот это уже ближе к истине Хотя я уже и сам разобрался. Оказывается параметр Server Asset Text к имеющейся ошибке O2A2:BMC System Error Log (SEL) Full никакого отношения не имеет. В BIOS-е стоял запрет на очистку системного лога, лог переполнился и выдавал ошибку записи. _________________ 我問不問愚蠢的問題
Вернуться к началу

Darkcat	Заголовок сообщения: Re: Нужна помощь IT специалиста Добавлено: 02 окт 2013, 13:31
Зарегистрирован: 26 янв 2010, 13:48 Сообщения: 492	Ммм… Странно что у айтишника с английским туго… Запрет очистки лога стоит по умолчанию, обычно стандартного лога хватает на весь срок службы. Если лог переполнен — сервер в 90% случаев едет на помойку. Или на переборку. _________________ Нет, только не кошки. Не верь им. Их глаза. Их глаза. Они знают слишком много. В-751 «Стрелец»
Вернуться к началу

e2-e4	Заголовок сообщения: Re: Нужна помощь IT специалиста Добавлено: 02 окт 2013, 15:27
Зарегистрирован: 20 дек 2009, 18:38 Сообщения: 3064 Откуда: ЮВАО	Darkcat писал(а): Ммм… Странно что у айтишника с английским туго… Это ты про кого? _________________ 我問不問愚蠢的問題
Вернуться к началу

Darkcat	Заголовок сообщения: Re: Нужна помощь IT специалиста Добавлено: 03 окт 2013, 15:34
Зарегистрирован: 26 янв 2010, 13:48 Сообщения: 492	Ну если не айтишник тогда ладно =) _________________ Нет, только не кошки. Не верь им. Их глаза. Их глаза. Они знают слишком много. В-751 «Стрелец»
Вернуться к началу

Troubleshooting BMC issues

Troubleshooting

Problem

Troubleshooting BMC issues on IBM System x and BladeCenter servers

Resolving The Problem

To begin troubleshooting the Baseboard Management Controller (BMC), check the following top issues. If your issue is listed, select the link, otherwise proceed to step 2.

Check the operator information panel on the front of the server. If the information LED is lit, it indicates that information about a suboptimal condition in the server is available in the BMC log or in the system-error log. Proceed to step 3.

Note: If the system-error LED is lit, refer to your system’s Hardware Maintenance Manual (HMM) for light path diagnostics.

Access the BMC log.

Check the system-error log and the BMC log for messages indicating the cause of the error. Take the action indicated before replacing a CRU or FRU. When troubleshooting an error, make sure to clear the BMC log so that you can more easily find current errors.

If these steps have not solved your problem, refer to your system’s Hardware Maintenance Manual (HMM),
or refer to «Need more help?»

Newer IBM eServer xSeries systems (e.g. xSeries 236, 306, 346, 366) have a BMC log which is the default «service processor» if the optional RSA2 is not installed. The BMC log and the system-error log contain messages that were generated during POST and all system status messages from the service processor. The BMC log contains a large number of information, error, and warning messages. The POST error log contains the three most recent error codes and messages that were generated during POST.

• The BMC log is limited in size and is designed so that when the log is full, new entries will not overwrite existing entries; therefore, you must periodically clear the BMC log from the Configuration/Setup Utility program (the menu choices are described in the User’s Guide).
• When troubleshooting an error, make sure to clear the BMC log so that you can find current errors more easily.
• Entries written to the BMC log early in the POST procedure will show an incorrect date as the default timestamp; however, the date and time will correct itself as POST continues.
• Each BMC log entry appears on its own page; to display all the data for an entry, use the up arrow and down arrow or the Page Up and Page Down keys. To move from one entry to the next, move the cursor to the Get Next Entry or Get Previous Entry line; then, press Enter.
• The log indicates an Assertion Event when an event has occurred. It indicates a Deassertion Event when the event is no longer occurring.
• Some of the error codes and messages in the BMC log are abbreviated.
• Viewing the BMC log through the web interface of the optional Remote Supervisor Adapter II SlimLine allows all messages to be translated.

Example BMC log entry:

You can view the contents of the POST error log, the BMC log, and the system-error log from the Configuration/Setup Utility program. You can also view the contents of the BMC log from the diagnostic programs. The BMC log contains the same information whether it is viewed from the Configuration/Setup Utility program or from the diagnostic programs.

Note: When troubleshooting PCI-X slots, note that the error logs report the PCI-X buses numerically. The numerical assignments vary depending on the configuration. You can check the assignments by running the Configuration/Setup Utility program.

To view the error logs from the Configuration/Setup Utility:

Turn on the server.

When the prompt «Press F1 for Configuration/Setup» appears, press F1. If you have set both a power-on password and an administrator password, you must type the administrator password to view the error logs.

Use one of the following procedures:

To view the POST error log, select Error Logs, and then select POST Error Log.

To view the BMC log, select Advanced Settings, select Baseboard Management Controller (BMC) settings, and then select BMC System Event Log.

To view the BMC log from diagnostics:

If the server is running, turn off the server and all attached devices.

Turn on all attached devices; then, turn on the server.

When the prompt «F2 for Diagnostics» appears, press F2.

Note: If you have set both a power-on password and an administrator password, you must type the administrator password to run the diagnostic programs.

From the top of the screen, select Hardware Info.

Источник

Cisco UCS Faults and Error Messages Reference

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Title

Cisco UCS Faults and Error Messages Reference

Baseboard Management Controller Messages

View with Adobe Reader on a variety of devices

Results

Chapter: Baseboard Management Controller Messages

Baseboard Management Controller Messages

The Baseboard Management Controller (BMC) provides the interface to the System Event Log (SEL). The SEL can be accessed from the system side as well as from other external interfaces. The BMC uses a message handler to route messages between the different interfaces. It also monitors and manages the system board, including temperatures and voltages.

The following sections are included:

•SEL Device

•Sensor Data Record Device

•Event Receiver Device

•BMC Commands

•SEL Record Examples

SEL Device

The SEL is a nonvolatile repository for system events. The SEL device is separate from the event receiver device and accepts commands to manage the contents.

This section includes the following topics:

•SEL Event Record Format

•Sensor Initialization Agent

SEL Event Record Format

The SEL messages are logged as a 16 byte string that contains the information about the change that triggered the message.

•Byte 1 and 2 is the record ID.

•Byte 3 is the record type.

•Bytes 4, 5, 6, and 7 is the timestamp

•Bytes 8 and 9 is the generator ID.

•Byte 10 is the version of the event message format.

•Byte 11 is the sensor type.

•Byte 12 is the sensor number.

•Byte 13 is either the event dir (assertion/deassertion event) or the event type.

•Byte 14, 15, and 16 are links to the event data field contents and determines whether the sensor class is about threshold, discrete, or original equipment manufacturer (OEM) settings.

Sensor Initialization Agent

The Sensor Initialization Agent is not a logical device, but a collection of functions and services specific to handling SDR information. The Sensor Initialization Agent works directly with the content of SDRs, in particular, with the sensor data records and the device locator records.

The agent uses the SDR information for sensor and IPMB device initialization during system startup. The agent interprets sensor data records and is directed by the init required fields to load thresholds to sensors that have the threshold initialization required bit set in the SDR records. Other bits in the record direct the agent to enable sensors and devices that come up with sensors, events, or both disabled.

The agent function runs at system power-up and at any system hard resets. We recommend that you run the agent function when the BMC first receives standby power.

In systems that implement power management, the system management software takes additional steps to restore intermediate settings after the system has powered up.

Sensor Data Record Device

The Sensor Data Record (SDR) device provides the interface to the sensor data records. A set of commands store and retrieve sensor data records. The SDR device provides a set of commands for discovering, configuring, and accessing sensors.

This section includes the following topics:

•SDR Repository Interface

•Modal and Nonmodal SDR Repositories

SDR Repository Interface

The SDR repository holds sensor, device locator, and entity association records for all sensors in the platform management subsystem. The BMC provides this interface to the SDR repository. The sensor data records can be accessed by using SDR commands.

Modal and Nonmodal SDR Repositories

There are two SDR repository implementations: modal and nonmodal.

A modal SDR repository is only updated when the controller is in SDR repository update mode. SDR information is kept in nonvolatile storage devices. Lengthy write operations during update can be required, which can interfere with other controller operations. For example, the SDR repository can be stored in a flash device that also holds a portion of the management controller code. A modal SDR repository implementation allows the functions associated with that code to be temporarily unavailable during the update process.

A nonmodal SDR repository can be written to at any time. Writing to the SDR does not impact the operation of other commands in the management controller.

Event Receiver Device

Event messages are special messages sent to management controllers when they detect significant or critical system management events. This includes messages for events such as temperature threshold exceeded, voltage threshold exceeded, power fault, and so on. The device generating an event message notifies the system by sending the message to the event receiver device.

Messages from the event receiver device are directly written into the system event log. The appropriate Add SEL Entry command is sent directly to the SEL device.

BMC Commands

SEL, SDR, and event commands are designed so that the devices that implement those command sets are isolated from the contents of the message. The devices do not interpret the messages. The event receiver device receives and routes event messages. The SEL devices retrieve and store log entries. The SDR devices retrieve and store sensor data records.

This section includes the following topics:

•SEL Device Commands

•SDR Repository Device Commands

•Event Receiver Commands

SEL Device Commands

These are the available SEL device commands:

•Get SEL Info

•Get SEL Allocation Info

•Reserve SEL

•Get SEL Entry

•Add SEL Entry

•Partial Add SEL Entry

•Delete SEL Entry

•Clear SEL

•Get SEL Time

•Set SEL Time

•Get Auxiliary Log Status

•Set Auxiliary Log Status

Get SEL Info

This command returns the number of entries in the SEL, the SEL command version, and the timestamp for the most recent entry and delete or clear.

Get SEL Allocation Info

This command returns the number of possible allocation units, the amount of usable free space (in allocation units), the allocation unit size (in bytes), and the size of the largest contiguous free region (in allocation units). The allocation unit size is the number of bytes in which storage is allocated. For example, if a 16 byte record is to be added, and the SEL has a 32 byte allocation unit size, the record takes up 32 bytes of storage.

Reserve SEL

This command sets the present owner of the SEL, as identified by the software ID or by the requester slave address from the command. The reservation process provides a limited amount of protection at repository access from the Intelligent Platform Management Interface (IPMB) when records are being deleted or incrementally read.

Get SEL Entry

This command retrieves entries from the SEL. The record data field in the response returns the 16 bytes of data from the SEL event record.

Add SEL Entry

This command enables the BIOS to add records to the system event log. Normally, the SEL device and the event receiver service are incorporated into the same management controller. In this case, BIOS or the system SMI handler adds its own events to the SEL by formatting an event message and sending it to the SEL device rather than by using this command.

Partial Add SEL Entry

This command is a version of the Add SEL Entry command. It allows the record to be incrementally added to the SEL. This command must be preceded by a Reserve SEL command. The first partial add must be to offset 0000h, and subsequent partial adds must be done sequentially, with no gaps or overlap between the adds.

Delete SEL Entry

This command deletes the specified entry in the SEL.

Clear SEL

This command erases the SEL contents. This process can take several seconds, based on the type of storage device. The command also shows the status of the erasure.

Get SEL Time

This command returns the time from the SEL device,which uses it for event timestamps.

Set SEL Time

This command initializes the time setting in the SEL device, which uses it for event timestamps.

Get Auxiliary Log Status

This command allows remote software to know whether new information has been added to machine check architecture (MCA) log. The MCA log is a storage area that can be implemented in Intel Itanium-based computer systems and holds information from an MCA handler running from system firmware.

Set Auxiliary Log Status

This command can be used by system software or firmware to set the status returned by the Get Auxiliary Log Status command. Some implementations mght use a private mechanism to set this status, in which case this command can not be provided even if the Get Auxiliary Log Status command is provided.

SDR Repository Device Commands

The following commands control the SDR repository device actions:

•Get SDR Repository Info

•Get SDR Repository Allocation Info

•Reserve SDR Repository

•Get SDR

•Add SDR

•Partial Add SDR

•Delete SDR

•Clear SDR Repository

•Get SDR Repository Time

•Set SDR Repository Time

•Enter SDR Repository Update Mode

•Exit SDR Repository Update Mode

•Run Initialization Agent

Get SDR Repository Info

This command returns the SDR command version for the SDR repository. It also returns a timestamp for the last add, delete, or clear commands.

Get SDR Repository Allocation Info

This command returns the number of possible allocation units, the amount of usable free space (in allocation units), the allocation unit size (in bytes), and the size of the largest contiguous free region (in allocation units). The allocation unit size is the number of bytes in which storage is allocated. For example, if a 20 byte record is to be added, and the SDR repository has a 16 byte allocation unit size, then the record would take up 32 bytes of storage.

Reserve SDR Repository

This command sets the present owner of the repository, as identified by the software ID or the requester slave address from the command. The reservation process provides a limited amount of protection on repository access from the IPMB when records are being deleted or incrementally read.

Get SDR

This command returns the sensor record specified by the record ID. The command also accepts a byte range specification that allows a selected portion of the record to be retrieved (incremental read). The Reserve SDR Repository command must be issued first for an incremental read to an offset other than 0000h. (The Get SDR Repository Info command should be used to verify the version of the SDR repository before sending other SDR repository commands. The command format and operation could change between versions.)

Add SDR

This command adds the specified sensor record to the SDR repository and returns its record ID. The data passed in the request must contain all of the SDR data.

Partial Add SDR

This command is a version of the Add SDR command that allows the record to be incrementally added to the repository. This command must be preceded by a Reserve SDR Repository command. The first partial add must be to offset 0000h, and partial adds must be done sequentially, with no gaps or overlap between the adds.

Delete SDR

This command deletes the sensor record specified by record ID. The requester ID and the reservation ID must also match the owner of the SDR repository.

Clear SDR Repository

This command clears all records from the SDR repository and reinitializes the SDR repository subsystem. The requestor ID and reservation ID information must match the present owner of the SDR repository. We recommend that this command not be used within your utilities and system management software.

Get SDR Repository Time

This command returns the time setting from the SDR repository device, which the SDR repository devices uses for tracking when changes to the SDR repository are made.

Set SDR Repository Time

This command initializes the time setting in the SDR repository device, which the SDR repository devices uses for tracking when changes to the SDR repository are made.

Enter SDR Repository Update Mode

This command enters a mode that allows a subset of normal commands. Available commands are Get Device ID , Get SDR , Add SDR , Partial Add SDR and Clear SDR Repository .

Exit SDR Repository Update Mode

This command exits the SDR repository update mode and restores normal use of all commands.

Run Initialization Agent

This command runs the initialization agent and can also check the status of the agent.

Event Receiver Commands

The following commands can be executed on the event receiver device:

•Set Event Receiver

•Get Event Receiver

•Platform Event Message

Set Event Receiver

This is a global command to tell a controller where to send event messages. The slave address and LUN of the event receiver must be provided. A value FFh for the event receiver slave address disables the generation of event messages.

Get Event Receiver

This is a global command to retrieve the present setting for the event receiver slave address and LUN.

Platform Event Message

This command is a request for the BMC to process event data that the command contains. The data is logged to the SEL.

SEL Record Examples

Examples that are reported to the SEL Repository are provided here. The raw record contains 16 bytes and are dislayed in the examples as hexadecimal values. Following the arrow is the translation of the data. The |-pipes are separators for ease of reading the translation.

The following topics are included:

•Device Presence Changes

•LED Color Changes

•Voltage Changes

•Temperature Changes

Device Presence Changes

These are examples of presence assertions. This shows a boot-up process.

LED Color Changes

These are examples of LED color changes written into the SEL Repository.

Voltage Changes

These are examples of SEL messages when voltage thresholds are crossed.

Temperature Changes

These are examples of SEL messages when temperature thresholds are crossed.

Источник

Модераторы: Trinity admin`s, Free-lance moderator`s