Ethernet driver log messages, Retrieving ethernet driver log messages, Table 4-5 – Dell Emulex Family of Adapters User Manual

Page 957

Advertising
background image

Emulex Drivers Version 10.2 for Linux User Manual

P010081-01A Rev. A

4. Troubleshooting

Log Messages

957

Ethernet Driver Log Messages

Retrieving Ethernet Driver Log Messages

Ethernet driver messages are logged in the /var/log/messages file. This log file is an

ASCII text file and can be viewed and searched with a text editor such as vim. A log file

automatically rotates as it gets larger. Rotated log files are named messages.x, where

“x” is an integer.
To search the log file for error messages, at the command prompt type:

# cd /var/log

# vim messages

A message is displayed similar to the following:

Aug 15 09:57:48 S74 kernel: Invalid MTU requested. Must be between

256 and 8974 bytes

Ethernet Driver Log Messages and their Descriptions

When reporting an issue with the adapter, check the kernel message log using the

dmesg command or the /var/log/messages file, and report any of these entries that

may be present.
There are three types of Ethernet log messages: error, information, and warning.
Ethernet driver warning messages logged by an adapter start with “be2net <BID>”,

where <BID> is the PCI bus identifier string. For example:

be2net 0000:0d:00.1: MTU must be between 256 and 9000 bytes.

Note: In the following table, <D>, <DD>, or <DDD> refers to decimal values that

appear in the log messages, and <S> refers to strings.

Table 4-5 Ethernet Driver Log Messages of Type

Ethernet Log Message

Description

Type

<S> initialization failed

Initialization of the adapter or allocation of a
resource for initializing the driver failed. In most
cases, this message is accompanied by a more
specific error message. Try rebooting the system
after power cycling. If the issue persists, this could
be a symptom of a hardware issue or corrupted
firmware.

Error

<S>: Physical link <S>

This is an informational message about a change in
physical link status.

Information

Adapter busy, could not reset

FW. Reboot server to activate

new FW

After flashing firmware on the adapter, the adapter
is busy activating the new firmware. Reboot the
machine for the new firmware to be active.

Error

Can't load BE3 UFI on BE3R

The UFI image can only be flashed on the OCx111xx
chip but not on the OCx111xxR chip.

Information

cmd to write to flash rom

failed

The firmware command to install the latest
firmware version on the adapter failed.

Error

Advertising