VMware replicated intact Linux directory after NIC operation

Directory

• VMware replicated intact Linux directory after NIC operation
  • Modify/etc/udev/rules.d/70-persistent-net.rules
  • Modifying the network card configuration file
  • Restart view

VMware replicated intact Linux directory after NIC operation

In order to reduce the workload, it is now necessary to replicate the Linux that has the system installed. The use of direct replication directory, then there will be a network adapter configuration conflicts, then how to solve it?

OS version:

[[email protected] ~]# lsb_release -aLSB Version:    :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarchDistributor ID: OracleServerDescription:    Oracle Linux Server release 6.9Release:    6.9Codename:   n/a

Modify/etc/udev/rules.d/70-persistent-net.rules

• To view an existing IP address

[[email protected] ~]# ifconfig eth1      Link encap:Ethernet  HWaddr 00:50:56:38:CC:A3            inet addr:192.168.1.115  Bcast:192.168.1.255  Mask:255.255.255.0          inet6 addr: fe80::250:56ff:fe38:cca3/64 Scope:Link          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1          RX packets:205 errors:0 dropped:0 overruns:0 frame:0          TX packets:75 errors:0 dropped:0 overruns:0 carrier:0          collisions:0 txqueuelen:1000           RX bytes:49848 (48.6 KiB)  TX bytes:13452 (13.1 KiB)lo        Link encap:Local Loopback            inet addr:127.0.0.1  Mask:255.0.0.0          inet6 addr: ::1/128 Scope:Host          UP LOOPBACK RUNNING  MTU:65536  Metric:1          RX packets:0 errors:0 dropped:0 overruns:0 frame:0          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0          collisions:0 txqueuelen:0           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

• Modify a file

[[email protected] ~]# vi /etc/udev/rules.d/70-persistent-net.rules # This file was automatically generated by the /lib/udev/write_net_rules# program, run by the persistent-net-generator.rules rules file.## You can modify it, as long as you keep each rule on a single# line, and change only the value of the NAME= key.# PCI device 0x8086:0x100f (e1000)SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0c:29:f0:2d:c6", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"# PCI device 0x8086:0x100f (e1000)SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:56:38:cc:a3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

Comment The above eth0 line and change the name of Eth1 to Eth0, record MAC address: 00:50:56:38:CC:A3

Modifying the network card configuration file

DEVICE=eth0TYPE=EthernetONBOOT=yesNM_CONTROLLED=yesBOOTPROTO=noneHWADDR=00:50:56:38:cc:a3IPADDR=192.168.1.20PREFIX=24GATEWAY=192.168.1.1DEFROUTE=yesIPV4_FAILURE_FATAL=yesIPV6INIT=noNAME="System eth0"

Remove the UUID and change the MAC address to the recorded Mac.

Restart view

VMware replicated intact Linux directory after NIC operation