VMware Red Hat 5.3 system after replication NIC configuration

Source: Internet
Author: User

After the Linux virtual machine is duplicated on the VMware Workstation, the network card will always automatically get the address from the Net8 after using manual configuration, unable to complete its own configured address

[[email protected] ~]# ifconfig
eth0      Link encap:ethernet  HWaddr 00:0C :29:5c:5c:4a 
          inet addr:192.168.83.134  bcast :192.168.83.255  mask:255.255.255.0
          up broadcast RUNNING multicast  mtu:1500  metric:1
          RX packets:84 errors:0 dropped:0 overruns:0 frame:0
          TX packets:69 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:9911 (9.6 KiB)   TX bytes:7415 (7.2 KiB)
          interrupt:177 Base address:0 x1400

lo        Link encap:local loopback 
           inet addr:127.0.0.1  mask:255.0.0.0
           up LOOPBACK running  mtu:16436  metric:1
           RX packets:1725 errors:0 dropped:0 overruns:0 frame:0
           TX packets:1725 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
          RX bytes:98764 (96.4 KiB)   TX bytes:98764 (96.4 KiB)

[Email protected] ~]# Cat/etc/sysconfig/network-scripts/ifcfg-eth0
# advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE]
Device=eth0
Bootproto=static
Onboot=yes
hwaddr=00:0c:29:5c:5c:4a
ipaddr=192.168.83.11
netmask=255.255.255.0
gateway=192.168.83.1

Modify all network card device names backed up under the NIC directory eth0

[Email protected] ~]# cd/etc/sysconfig/network-scripts/
[[email protected] network-scripts]# ls
Ifcfg-eth0 ifdown-isdn Ifup-eth ifup-routes
Ifcfg-eth0.bak ifdown-post IFUP-IPPP Ifup-sit
IFCFG-ETH0.BAK2 IFDOWN-PPP ifup-ipsec IFUP-SL
Ifcfg-lo ifdown-routes Ifup-ipv6 Ifup-tunnel
Ifdown ifdown-sit ifup-ipx ifup-wireless
IFDOWN-BNEP IFDOWN-SL ifup-isdn Init.ipv6-global
Ifdown-eth Ifdown-tunnel Ifup-plip Net.hotplug
IFDOWN-IPPP ifup Ifup-plusb network-functions
Ifdown-ipsec ifup-aliases ifup-post Network-functions-ipv6
Ifdown-ipv6 IFUP-BNEP IFUP-PPP
[Email protected] network-scripts]# VI Ifcfg-eth0.bak

# advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE]
device=eth00
Bootproto=static
Hwaddr=00:0c:29:23:ca:c5
Onboot=yes
ipaddr=192.168.204.10
netmask=255.255.255.0
gateway=192.168.204.1

The modified effect

[[email protected] ~]# ifconfig
eth0      Link encap:ethernet  HWaddr 00:0C :29:5c:5c:4a 
          inet addr:192.168.83.11  bcast :192.168.83.255  mask:255.255.255.0
          up broadcast RUNNING multicast  mtu:1500  metric:1
          RX packets:437 errors:0 dropped:0 overruns:0 frame:0
          TX packets:330 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:41000 (40.0 KiB)   TX bytes:43033 (42.0 KiB)
          interrupt:177 Base Address : 0x1400

Lo Link encap:local Loopback
inet addr:127.0.0.1 mask:255.0.0.0
Up LOOPBACK RUNNING mtu:16436 metric:1
RX packets:2101 errors:0 dropped:0 overruns:0 frame:0
TX packets:2101 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:120432 (117.6 KiB) TX bytes:120432 (117.6 KiB)

Principle: The device Udev under Linux has a relationship with dynamic management and UUID numbers

Someone on the Web modified

Vi/etc/modprobe.conf

Someone else changed it.

Rm-f/etc/udev/rules.d/70-persistent-net.rules

Some people first remove the network card, and then add the network card to solve the problem

But 5.3 of cases are

[[email protected] rules.d]# ls
05-udev-early.rules 51-hotplug.rules 60-pcmcia.rules 90-alsa.rules 95-pam-console.rules
40-multipath.rules 60-net.rules 60-raw.rules 90-dm.rules 98-kexec.rules
50-udev.rules 60-net.rules.bak 85-pcscd_ccid.rules 90-hal.rules bluetooth.rules

Without 70-persistent-net.rules this file, the last thought is to backup the NIC to modify the device name to solve the problem. Graphical interface can be in the management of network card, delete copy generated network card, restart Web services.

Hope to be helpful to everyone

This article is from the "Test" blog, so be sure to keep this source http://33205687.blog.51cto.com/6173537/1621130

VMware Red Hat 5.3 system after replication NIC configuration

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.