Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Why Is the NIC Not Working?

Updated on 2025-01-10 GMT+08:00

Symptom

The NIC equipped on a D1 or H1 ECS does not work.

Possible Causes

The NIC driver has not been correctly installed.

Solution

D1 and H1 ECSs use passthrough NICs to improve network performance. You must install the passthrough NIC driver on the ECSs or the image that is used for creating the ECSs.

NOTE:

If you mount the CD/DVD-ROM driver over a VPN, ensure that the VPN bandwidth is greater than 8 Mbit/s.

To install the passthrough NICE driver, do as follows:

  1. Obtain the passthrough NIC driver.

    Passthrough NIC driver versions vary depending on the OS. For details, see Table 1.

    Table 1 NIC driver versions and OSs

    NIC Driver Version

    OS

    How to Obtain

    ixgbevf 2.16.4

    CentOS 7.2 64bit

    https://sourceforge.net/projects/e1000/files/ixgbevf%20stable/2.16.4/

  2. Log in to the ECS.
  3. Install the passthrough NIC driver on the ECS. In this procedure, CentOS 7.2 64bit is used as an example.

    1. Configure the passthrough NIC.
      Not all ECS OSs identify passthrough NICs using the standard NIC naming rule of ethx, where x is a number. If this is the case, you must configure the ECS so that it can identify the passthrough NIC. The procedure is as follows:
      1. Run the following command to view all NICs on the ECS and identify the passthrough NIC:

        ifconfig -a

      2. Run the following command to switch to the directory where configuration files are stored:

        cd /etc/sysconfig/network-scripts/

      3. Run the following command to create a configuration file for the passthrough NIC:

        cp ifcfg-eth0 ifcfg-NIC_name

        In the preceding command, NIC_name specifies the name of the passthrough NIC.

      4. Use the vi editor to edit this configuration file:

        vi ifcfg-NIC_name

      5. Set the DEVICE parameter in the configuration file to the name of the passthrough NIC. The following is an example configuration:
        DEVICE="NIC_name"
        BOOTPROTO="dhcp"
        ONBOOT="yes"
        STARTMODE="onboot"
      6. Run the following command to restart the network service and allow the configuration to take effect:

        service network restart

    2. Upload the obtained passthrough NIC driver to a directory on the ECS, for example, /home.
    3. Switch to user root on the ECS CLI and open the target directory.

      In this example, the passthrough NIC driver is stored in the /home directory. Run the cd /home command to switch to the target directory.

    4. Run the following command to decompress the software package.

      tar -zxvf ixgbevf-2.16.4.tar.gz

    5. Run the following command to switch to the generated src directory:

      cd ixgbevf-2.16.4/src

    6. Run the following commands to install the driver:

      make

      make install

    7. Run the following command to restart the ECS to make the drive take effect:

      reboot

    8. Switch to user root on the ECS CLI and open the src directory, for example, by running the cd /home/ixgbevf-2.16.4/src command. Then, run the following commands to check whether the driver has been installed:

      rmmod ixgbevf

      insmod ./ixgbevf.ko

      ethtool -i NIC_name

      In the preceding command, NIC_name specifies the passthrough NIC name, for example, ens5.

      NOTE:
      • After you run the rmmod ixgbevf command, the system may display an error message. This message does not affect the installation of the passthrough NIC driver and can be ignored.
      • NIC_name specifies the passthrough NIC name, for example, ens5.
    9. Check the driver status based on the displayed information.

      In this example, the driver is installed if driver is ixgbevf and version is 2.16.4.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback