yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
main
doc-exports/docs/bms/umn/en-us_topic_0112790033.html
Zaoxu, Li 1655d41c64 bms_umn_0208 
Reviewed-by: Pristromskaia, Margarita <margarita.pristromskaia@t-systems.com>
Co-authored-by: Zaoxu, Li <lizaoxu@huawei.com>
Co-committed-by: Zaoxu, Li <lizaoxu@huawei.com>
2024-09-20 14:27:56 +00:00

22 KiB
Raw Permalink Blame History

Configuring a NIC (Ubuntu)

This section uses Ubuntu 16.04 LTS (Xenial Xerus x86_64) as an example to describe how to configure a NIC added to or deleted from a BMS.

  • The configuration methods of other Ubuntu OSs are similar to that of Ubuntu 16.04 LTS (Xenial Xerus x86_64).
  • If the network is disconnected after a NIC is added and the BMS is restarted, run the following command:

    ifup bond0.vlan

    vlan indicates the VLAN used by the NIC.

    If the network is still disconnected, add the NIC again.

Add a NIC

  1. Obtain information about the NIC to be added.
    Table 1 NIC information

    Parameter

    Description

    Example Value

    VLAN and MAC address

    Specifies the VLAN information and MAC address of the NIC. To obtain them, perform the following operations:

    1. In the BMS list, click the name of the target BMS.
    2. Click the NICs tab, locate the row that contains the NIC to be added, and click to expand details.
    3. Obtain the values of VLAN and MAC Address.

    2847

    fa:16:3e:a2:aa:65

    Gateway

    Specifies the gateway address of the NIC. To obtain them, perform the following operations:

    1. On the NIC details page in 2, obtain the subnet information.
    2. On the BMS details page, click the link following VPC to switch to the VPC list.
    3. Click the name of the VPC to which the BMS belongs to go to the VPC details page.
    4. Click the Subnets tab and obtain the gateway address of the subnet in 1.

    192.168.1.1
  2. Use a key or password to log in to the BMS as user root.
  3. Check whether the /etc/network/interfaces.d/ directory contains the /etc/network/interfaces.d/70-cloud-init.cfg file.
    • If yes, go to step 5.
    • If no, go to step 4.
  4. Run the following commands to generate the /etc/network/interfaces.d/70-cloud-init.cfg file and set the file permissions:

    touch /etc/network/interfaces.d/70-cloud-init.cfg

    chmod 644 /etc/network/interfaces.d/70-cloud-init.cfg

  5. Run the following command to edit the /etc/network/interfaces.d/70-cloud-init.cfg file and add information about the NIC to be added to the file:

    vim /etc/network/interfaces.d/70-cloud-init.cfg

    Edit the file as follows:

    auto bond0.2847
iface bond0.2847 inet dhcp
mtu 8888
hwaddress fa:16:3e:a2:aa:65
vlan-raw-device bond0

    The required information has been obtained in step 1.

    • bond0.2847: indicates the name of the NIC to be added. bond0 is a fixed value and the number following it is the VLAN information of the NIC.
    • hwaddress: indicates the MAC address of the NIC to be added.
    • vlan-raw-device: The default value bond0 is used.

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

  6. Run the following command to start the added NIC:

    ifup bond0.vlan

    For example, to start bond0.2847, run the ifup bond0.2847 command.

  7. Run the following command to check the status of the NIC device:

    ip link

  8. Ping the gateway from the new network device to check whether the network connectivity is normal.

    Use the gateway address obtained from 1.

Delete a NIC

  1. Obtain the VLAN and MAC address of the VPC NIC to be deleted.
  2. Use a key or password to log in to the BMS as user root.
  3. Locate the network device based on the VLAN information and run the following commands to stop and delete the device:
    root@ubuntu:~# ip link | grep 2847
9: bond0.2847@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8888 qdisc noqueue state UP mode DEFAULT group default qlen 1000
root@ubuntu:~# ifconfig bond0.2847 down
root@ubuntu:~# ip link delete bond0.2847
  4. Check whether the BMS OS has been reinstalled after the NIC is added to the BMS.
    • If no, go to step 5.
    • If yes, go to step 9.
  5. Run the following command to copy the /etc/network/interfaces.d/70-cloud-init.cfg file to generate the /etc/network/interfaces.d/70-cloud-init.cfg.bak file to back up the network configuration:

    cp -p /etc/network/interfaces.d/70-cloud-init.cfg /etc/network/interfaces.d/70-cloud-init.cfg.bak

  6. Run the following command to edit /etc/network/interfaces.d/70-cloud-init.cfg, locate the NIC to be deleted based on the VLAN and MAC address obtained from 1, and delete the NIC information from the file:

    vim /etc/network/interfaces.d/70-cloud-init.cfg

    # The following information needs to be deleted:
auto bond0.2847
iface bond0.2847 inet dhcp
mtu 8888
hwaddress fa:16:3e:a2:aa:65
vlan-raw-device bond0

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

  7. After the NIC is deleted, if the /etc/network/interfaces.d/70-cloud-init.cfg file contains no NIC information, run the following command to delete the /etc/network/interfaces.d/70-cloud-init.cfg file:

    rm /etc/network/interfaces.d/70-cloud-init.cfg

  8. Check whether other NICs run properly. If they run properly, run the following command to delete the /etc/network/interfaces.d/70-cloud-init.cfg.bak file:

    rm /etc/network/interfaces.d/70-cloud-init.cfg.bak

  9. Run the following command to copy the /etc/network/interfaces.d/50-cloud-init.cfg file to generate the /etc/network/interfaces.d/50-cloud-init.cfg.bak file to back up the network configuration:

    cp -p /etc/network/interfaces.d/50-cloud-init.cfg /etc/network/interfaces.d/50-cloud-init.cfg.bak

  10. Run the following command to edit /etc/network/interfaces.d/50-cloud-init.cfg, locate the NIC to be deleted based on the VLAN and MAC address obtained from 1, and delete the NIC information from the file:

    vim /etc/network/interfaces.d/50-cloud-init.cfg

    # The following information needs to be deleted:
auto bond0.2847
iface bond0.2847 inet dhcp
mtu 8888
hwaddress fa:16:3e:a2:aa:65
vlan-raw-device bond0

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

  11. Check whether other NICs run properly. If they run properly, run the following command to delete the /etc/network/interfaces.d/50-cloud-init.cfg.bak file:

    rm /etc/network/interfaces.d/50-cloud-init.cfg.bak

Parent topic: VPC
<script language="JavaScript"> </script>