No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Huawei Server Maintenance Manual 09

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Failed to Bring Up Network Ports on a KunLun 9000 Series Server

Failed to Bring Up Network Ports on a KunLun 9000 Series Server

Problem Description

Table 5-259 Basic information

Item

Information

Source of the Problem

KunLun 9016

Intended Product

All servers

Release Date

2018-04-04

Keyword

FCoE, Intel 82599 LOM, RHVH 4.1

Symptom

The KunLun 9016 is configured with four 4-socket physical partitions. After RHVH 4.1 is installed on three physical partitions, the network ports of the three partitions cannot be brought up.

Key Process and Cause Analysis

The analysis and verification process is as follows:

  1. No alarm is generated in the hardware logs of the device, and the network ports of the three physical partitions have the same problem. Therefore, the fault is not caused by hardware faults.
  2. Run the systemctl command to restart the network service. The network ports cannot be brought up. The OS messages logs show that the ens8f1 network port is brought down immediately after being brought up, and no error information is generated.

  3. Check the configuration file of the network port. No exception is found.

  4. Check the compatibility. The compatibility of RHVH 4.1 on the KunLun server is not tested. The OS and the LOM driver may have a compatibility problem with the KunLun server. Use Toolkit to start the server and configure the network ports. Run the ifconfig command to check the network port status.

    Run the ifconfig command to bring up the network ports. The network ports are still down.

    Run the ethtool command to check the network port status. The command output shows that the network ports are not connected.

    According to the preceding check results, the external environment may cause the problem.

    1. The faulty optical modules or faulty optical fiber connections of the network ports may cause the problem. (The problem occurs on three physical partitions, and this cause is unlikely.)
    2. The network ports on the switch are abnormal, or the settings of the networks ports are abnormal.
  5. Check the optical modules and the cable connections on-site. The optical modules and the cable connections are normal.
  6. Check the switch.

    The switch logs are analyzed by the customer's network engineers.

    The switch logs show that the network ports of the KunLun server send FCoE packets to the switch, but the switch does not support FCoE due to lack of a license. The switch automatically disables the network ports after the FCoE packets are received. As a result, the network ports cannot be brought up. The customer requires that the FCoE function be disabled to resolve this problem.

  7. Locate the source of the FCoE packets.

    The KunLun server is configured with two 10GE 82599 LOMs. The LOM chipset is Intel 82599. Intel confirms that the 82599 chipset supports FCoE, but the 82599 LOM does not automatically send FCoE packets, and the source of the FCoE packets is the OS. The LOMs are used only for data transparent transmission. The OS stops sending FCoE packets after the lldpad service on the OS is disabled.

Conclusion and Solution

Conclusion:

The FCoE function of the RHVH 4.1 OS is enabled by default, and the OS uses the network ports to send FCoE packets. The switch does not have a FCoE license, and automatically disables the network ports after the FCoE packets are received. As a result, the network ports on the server cannot be brought up.

Solution:

  1. Run the following commands on the OS to disable the lldpad service and stop the OS from sending FCoE packets:

    systemctl stop lldpad

    systemctl disable lldpad

  2. Bring up the network ports on the switch.
  3. After the preceding operations, the network ports are brought up, and the network is recovered.

Note

None

Translation
Download
Updated: 2019-02-25

Document ID: EDOC1000041338

Views: 71362

Downloads: 3786

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next