El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.

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
Help Center/ Bare Metal Server/ User Guide/ Network/ Enhanced High-Speed Network/ Configuring an Enhanced High-Speed NIC (Red Hat, CentOS, Oracle Linux, and EulerOS)

Configuring an Enhanced High-Speed NIC (Red Hat, CentOS, Oracle Linux, and EulerOS)

Updated on 2022-09-16 GMT+08:00

This section uses CentOS 6.9 (x86_64) as an example to describe how to configure an enhanced high-speed NIC of a BMS.

NOTE:

The configuration methods of Red Hat, Oracle Linux, EulerOS, and CentOS are similar.

Add a NIC

Use a key or password to log in to the BMS as user root. Run the following command:

blkid | grep config-2

If the command output is empty, use Method 2. If the command output shown in the following figure is displayed, use Method 1.

  • Method 1
  1. Use a key or password to log in to the BMS as user root.
  2. On the BMS CLI, run the following command to check the NIC information:

    ip link

    Information similar to the following is displayed.

    NOTE:

    eth0 and eth1 bear the VPC, and eth2 and eth3 bear the enhanced high-speed network.

  3. Run the following command to check whether the /etc/udev/rules.d/ directory contains the 80-persistent-net.rules file:

    ll /etc/udev/rules.d/ | grep 80-persistent-net.rules

    • If yes, and the file contains all NICs except bond0 and lo obtained in step 2 and their MAC addresses, go to step 6.
    • If no, go to step 4.

  4. Run the following command to copy the /etc/udev/rules.d/70-persistent-net.rules file and name the copy as /etc/udev/rules.d/80-persistent-net.rules.

    cp -p /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/80-persistent-net.rules

    NOTE:

    If the /etc/udev/rules.d/70-persistent-net.rules file does not exist, create it with the content in the following format:

    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="4c:f9:5d:d9:e8:ac", NAME="eth0"
    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="4c:f9:5d:d9:e8:ad", NAME="eth1"

  5. Configure the udev rules:

    Write the MAC addresses and names of NICs except eth0 and eth1 obtained in step 2 (those not contained in the /etc/udev/rules.d/70-persistent-net.rules file) to the /etc/udev/rules.d/80-persistent-net.rules file so that the names and sequence of NICs do not change after the BMS is restarted.

    NOTE:

    Ensure that NIC MAC address and name are lowercase letters.

    vi /etc/udev/rules.d/80-persistent-net.rules

    The modification result is as follows:

    After the modification, press Esc, enter :wq, save the configuration, and exit.

  6. Run the following commands to copy the network configuration file /etc/sysconfig/network-scripts/ifcfg-bond0 to generate the /etc/sysconfig/network-scripts/ifcfg-bond1 file, and copy the /etc/sysconfig/network-scripts/ifcfg-eth0 file to generate the /etc/sysconfig/network-scripts/ifcfg-eth2 and /etc/sysconfig/network/ ifcfg-eth3 files:

    cp -p /etc/sysconfig/network-scripts/ifcfg-bond0 /etc/sysconfig/network-scripts/ifcfg-bond1

    cp -p /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth2

    cp -p /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth3

  7. Run the following commands to edit the /etc/sysconfig/network-scripts/ifcfg-eth2 and /etc/sysconfig/network-scripts/ifcfg-eth3 files:

    • vi /etc/sysconfig/network-scripts/ifcfg-eth2

      Edit the eth2 network configuration file as follows:

      USERCTL=no
      MTU=8888
      NM_CONTROLLED=no
      BOOTPROTO=static
      DEVICE=eth2
      TYPE=Ethernet
      ONBOOT=yes
      MASTER=bond1
      SLAVE=yes

      Change the value of BOOTPROTO to static, that of DEVICE to the network device name eth2, and that of MASTER to the port name of the enhanced high-speed NIC bond (bond1). Retain values of other parameters.

    • vi /etc/sysconfig/network-scripts/ifcfg-eth3

      Edit the eth3 network configuration file as follows (similar to eth2):

      USERCTL=no
      MTU=8888
      NM_CONTROLLED=no
      BOOTPROTO=static
      DEVICE=eth3
      TYPE=Ethernet
      ONBOOT=yes
      MASTER=bond1
      SLAVE=yes

  8. Run the following command to edit the /etc/sysconfig/network-scripts/ifcfg-bond1 file:

    vi /etc/sysconfig/network-scripts/ifcfg-bond1

    Edit the file as follows:

    MACADDR=40:7d:0f:52:e3:a5
    BONDING_MASTER=yes
    USERCTL=no
    ONBOOT=yes
    NM_CONTROLLED=no
    BOOTPROTO=static
    BONDING_OPTS="mode=1 miimon=100"
    DEVICE=bond1
    TYPE=Bond
    IPADDR=10.10.10.101
    NETMASK=255.255.255.0
    MTU=8888

    Where,

    • Change the value of MACADDR to the MAC address of eth2 or eth3.
    • Change the value of BOOTPROTO to static.
    • Change the value of DEVICE to bond1.
    • Change the value of IPADDR to the IP address to be allocated to bond1. If the IP address planned for the enhanced high-speed network does not conflict with the VPC network segment, you can plan the IP address as needed, only to ensure that BMSs communicating through the enhanced high-speed network are in the same network segment as the enhanced high-speed network. An example value is 10.10.10.101.
    • Set the value of NETMASK to the subnet mask of the IP address configured for enhanced high-speed network bond1.

    Retain values of other parameters.

    After the modification, press Esc, enter :wq, save the configuration, and exit.

  9. Run the following commands to enable port group bond1 of the enhanced high-speed network:

    Run the following commands to start enhanced high-speed NICs eth2 and eth3:

    ifup eth2

    ifup eth3

    ifup bond1

  10. Perform the preceding operations to configure other BMSs.
  11. After all BMSs are configured, ping the IP address in the same network segment as the enhanced high-speed network of other BMSs from each BMS.

  • Method 2
  1. Use a key or password to log in to the BMS as user root.
  2. On the BMS CLI, run the following command to check the NIC information:

    ip link

    Information similar to the following is displayed.

    NOTE:

    The NIC whose MAC address starts with fa:16 is a network device that carries the VPC network, for example, eth0 and eth1. The NIC whose MAC address is that displayed in View Enhanced High-Speed NICs is a network device that carries the enhanced high-speed network, such as eth6 and eth7.

  3. Run the following commands to edit the /etc/sysconfig/network-scripts/ifcfg-eth6 and /etc/sysconfig/network-scripts/ifcfg-eth7 files:

    • vi /etc/sysconfig/network-scripts/ifcfg-eth6

      Edit the eth6 network configuration file as follows:

      USERCTL=no
      MTU=8888
      NM_CONTROLLED=no
      BOOTPROTO=static
      DEVICE=eth6
      TYPE=Ethernet
      ONBOOT=yes
      MASTER=bond1
      SLAVE=yes

      Change the value of BOOTPROTO to static, that of DEVICE to the network device name eth6, and that of MASTER to the port name of the enhanced high-speed NIC bond (bond1). Retain values of other parameters.

    • vi /etc/sysconfig/network-scripts/ifcfg-eth7

      Edit the eth7 network configuration file as follows (similar to eth6):

      USERCTL=no
      MTU=8888
      NM_CONTROLLED=no
      BOOTPROTO=static
      DEVICE=eth7
      TYPE=Ethernet
      ONBOOT=yes
      MASTER=bond1
      SLAVE=yes

  4. Run the following command to edit the /etc/sysconfig/network-scripts/ifcfg-bond1 file:

    vi /etc/sysconfig/network-scripts/ifcfg-bond1

    Edit the file as follows:

    MACADDR=00:2e:c7:e0:b2:37
    BONDING_MASTER=yes
    USERCTL=no
    ONBOOT=yes
    NM_CONTROLLED=no
    BOOTPROTO=static
    BONDING_OPTS="mode=1 miimon=100"
    DEVICE=bond1
    TYPE=Bond
    IPADDR=10.10.10.101
    NETMASK=255.255.255.0
    MTU=8888

    Where,

    • Change the value of MACADDR to the MAC address of eth6 or eth7.
    • Change the value of BOOTPROTO to static.
    • Change the value of DEVICE to bond1.
    • Change the value of IPADDR to the IP address to be allocated to bond1. If the IP address planned for the enhanced high-speed network does not conflict with the VPC network segment, you can plan the IP address as needed, only to ensure that BMSs communicating through the enhanced high-speed network are in the same network segment as the enhanced high-speed network. An example value is 10.10.10.101.
    • Set the value of NETMASK to the subnet mask of the IP address configured for enhanced high-speed network bond1.

    Retain values of other parameters.

    After the modification, press Esc, enter :wq, save the configuration, and exit.

  5. Run the following commands to enable port group bond1 of the enhanced high-speed network:

    Run the following commands to start enhanced high-speed NICs eth6 and eth7:

    ifup eth6

    ifup eth7

    ifup bond1

  6. Perform the preceding operations to configure other BMSs.
  7. After all BMSs are configured, ping the IP address in the same network segment as the enhanced high-speed network of other BMSs from each BMS.

To configure a VLAN, perform the following steps:

  1. Configure the corresponding VLAN sub-interfaces based on the VLAN to be configured. Assuming that the VLAN ID is 316, run the following command to edit the /etc/sysconfig/network-scripts/ifcfg-bond1.316 file:

    vi /etc/sysconfig/network-scripts/ifcfg-bond1.316

    Edit the file as follows:

    USERCTL=no
    ONBOOT=yes
    NM_CONTROLLED=no
    BOOTPROTO=static
    DEVICE=bond1.316
    TYPE=Ethernet
    IPADDR=10.10.0.101
    NETMASK=255.255.255.0
    VLAN=yes
    PHYSDEV=bond1

    Where,

    • Change the value of DEVICE to the name of the new bond sub-interface.
    • Change the value of IPADDR to the IP address to be allocated to bond1.316. If the IP address planned for the VLAN sub-interface of the enhanced high-speed NIC does not conflict with the VPC network segment, you can plan the IP address as needed, only to ensure that the BMSs communicating with each other through the VLAN sub-interface of the enhanced high-speed NIC are in the same network segment as the VLAN sub-interface of the enhanced high-speed NIC. An example value is 10.10.0.101.
    • Set the value of NETMASK to the subnet mask of the IP address configured for enhanced high-speed NIC bond1.316.

    Retain values of other parameters.

    After the modification, press Esc, enter :wq, save the configuration, and exit.

  2. After all BMSs are configured, ping the IP address in the same network segment as the enhanced high-speed network VLAN sub-interface of other BMSs from each BMS.

Delete a NIC

  1. Obtain the IP address of the bonded enhanced high-speed NIC to be deleted.
  2. Use a key or password to log in to the BMS as user root.
  3. Locate the bond network device and run the following command to stop and delete the device: If the bond has VLAN sub-interfaces, they will be automatically deleted.
    [root@bms-centos ~]# ifdown eth2
    [root@bms-centos ~]# ifdown eth3
    [root@bms-centos ~]# ifdown bond1
    [root@bms-centos ~]# ip link delete bond1
    [root@bms-centos ~]# ip link
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 8888 qdisc mq master bond0 state UP qlen 1000
        link/ether fa:16:00:6d:80:29 brd ff:ff:ff:ff:ff:ff
    3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 8888 qdisc mq master bond0 state UP qlen 1000
        link/ether fa:16:00:6d:80:29 brd ff:ff:ff:ff:ff:ff
    4: eth2: <BROADCAST,MULTICAST> mtu 8888 qdisc mq state DOWN qlen 1000
        link/ether 40:7d:0f:52:e3:a5 brd ff:ff:ff:ff:ff:ff
    5: eth3: <BROADCAST,MULTICAST> mtu 8888 qdisc mq state DOWN qlen 1000
        link/ether 40:7d:0f:52:e3:a6 brd ff:ff:ff:ff:ff:ff
    6: bond0: <BROADCAST,MULTICAST,PROMISC,MASTER,UP,LOWER_UP> mtu 8888 qdisc noqueue state UP 
        link/ether fa:16:00:6d:80:29 brd ff:ff:ff:ff:ff:ff
  4. Run the following commands to delete network configuration files /etc/sysconfig/network-scripts/ifcfg-eth2, /etc/sysconfig/network-scripts/ifcfg-eth3, and /etc/sysconfig/network-scripts/ifcfg-bond1:

    rm -f /etc/sysconfig/network-scripts/ifcfg-eth2

    rm -f /etc/sysconfig/network-scripts/ifcfg-eth3

    rm -f /etc/sysconfig/network-scripts/ifcfg-bond1

    If a VLAN sub-interface exists, delete network configuration file /etc/sysconfig/network-scripts/ifcfg-bond1.vlan, where vlan indicates the VLAN ID of the VLAN sub-interface, for example, 316.

    rm -f /etc/sysconfig/network-scripts/ifcfg-bond1.316

Utilizamos cookies para mejorar nuestro sitio y tu experiencia. Al continuar navegando en nuestro sitio, tú aceptas nuestra política de cookies. Descubre más

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback