Rename the NIC name in SuSE Linux 10

A few times ago, I encountered the NIC rename problem in SuSE Linux. It was necessary to install RAC on the Virtual Machine and copy the virtual machine. Different from RedHat Linux and oralce Linux, we will record it for your reference.

1. network configuration of the new node # No IP configuration information after the node is started. bo2dbp :~ # Ifconfig 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: 16436 Metric: 1 RX packets: 174 errors: 0 dropped: 0 overruns: 0 frame: 0 TX packets: 174 errors: 0 dropped: 0 overruns: 0 carrier: 0 Collisions: 0 txqueuelen: 0 RX Bytes: 11471 (11.2 KB) TX Bytes: 11471 (11.2 KB) 2. Use yast2/newcard to delete the previous Nic and add IP addresses and routes for the new Nic. Machine name # The following is the deleted Nic and IP address is configured, bo2d information after route BP :~ # Ifconfig eth3 link encap: Ethernet hwaddr 00: 0C: 29: 99: DF: 0f Inet ADDR: 192.168.7.71 bcast: 192.168.7.255 mask: 255.255.255.0 inet6 ADDR: fe80: 20c: 29ff: fe99: df0f/64 scope: link up broadcast running Multicast MTU: 1500 Metric: 1 RX packets: 10 errors: 0 dropped: 0 overruns: 0 frame: 0 TX packets: 4 errors: 0 dropped: 0 overruns: 0 carrier: 0 Collisions: 0 txqueuelen: 1000 RX Bytes: 2387 (2.3 kb) TX Bytes: 328 (328.0 B) eth4 link encap: Ethernet hwaddr 00: 0C: 29: 99: DF: 19 Inet ADDR: 10.10.7.71 bcast: 10.10.7.255 mask: 255.255.255.0 inet6 ADDR: fe80: 20c: 29ff: fe99: df19/64 scope: link up broadcast running Multicast MTU: 1500 Metric: 1 RX packets: 7 errors: 0 dropped: 0 overruns: 0 frame: 0 TX packets: 3 errors: 0 dropped: 0 overruns: 0 carrier: 0 Collisions: 0 txqueuelen: 1000 RX Bytes: 1607 (1.5 kb) TX Bytes: 238 (238.0 B) lo link en Cap: local loopback Inet ADDR: 127.0.0.1 mask: 255.0.0.0 inet6 ADDR ::: 1/128 scope: Host up loopback running MTU: 16436 Metric: 1 RX packets: 206 errors: 0 dropped: 0 overruns: 0 frame: 0 TX packets: 206 errors: 0 dropped: 0 overruns: 0 carrier: 0 Collisions: 0 txqueuelen: 0 RX Bytes: 13803 (13.4 KB) TX Bytes: 13803 (13.4 KB) 3. Disable the network bo2dbp :~ # Rcnetwork stop shutting down network interfaces: eth3 device: Intel Corporation 82545em Gigabit Ethernet controller (copper) (Rev 01) eth3 configuration: eth-bus-pci-0000: 02: 00.0 eth3 done eth4 device: intel Corporation 82545em Gigabit Ethernet controller (copper) (Rev. 01) eth4 configuration: eth-bus-pci-0000: 02: 02.0 eth4 done shutting down service network ............. done4, edit the configuration file # Comment out the original eth0 and eth1 # and change the new MAC address entry to eth0 and eth1 bo2dbp :~ # Vi/etc/udev/rules. d/30-net_persistent_names.rules # subsystem = "Net", Action = "add", sysfs {address} = "00: 0C: 29: 8A: 6C: C8 ", import = "/lib/udev/rename_netiface % K eth0" # subsystem = "Net", Action = "add", sysfs {address} = "00: 0C: 29: 8A: 6C: D2 ", import ="/lib/udev/rename_netiface % K eth1 "subsystem =" Net ", Action =" add ", sysfs {address} = "00: 0C: 29: 99: DF: 0f", import = "/lib/udev/rename_netiface % K eth0" subsys TEM = "Net", Action = "add", sysfs {address} = "00: 0C: 29: 99: DF: 19 ", import = "/lib/udev/rename_netiface % K eth1" 5. Use the rename_netiface command to rename the network interface bo2dbp :~ # Cd/lib/udev bo2dbp:/lib/udev #. /rename_netiface eth3 eth0 interface = eth0 devpath =/eth0 renamed = Yes bo2dbp:/lib/udev #. /rename_netiface eth4 eth1 interface = eth1 devpath =/eth1 renamed = yes6. Restart the network bo2dbp:/lib/udev # rcnetwork start hint: you may set mandatory devices in/etc/sysconfig/Network/config setting up Network Interfaces: lo IP Address: 127.0.0.1/8 IP Address: 127.0.0.2/8 checking for N Etwork time protocol daemon (ntpd): unused lo done eth0 device: Intel Corporation 82545em Gigabit Ethernet controller (copper) (Rev 01) eth0 configuration: eth-bus-pci-0000: 02: 00.0 eth0 IP Address: 192.168.7.71/24 checking for Network Time Protocol daemon (ntpd): unused eth0 done eth1 device: Intel Corporation 82545em Gigabit Ethernet controller (copper) (Rev 01) eth1 configuration: eth-bus-pci-00 00:02:02. 0 eth1 IP Address: 10.10.7.71/24 checking for Network Time Protocol daemon (ntpd): unused eth1 done setting up service network .............. done7, check result bo2dbp:/lib/udev # ifconfig eth0 link encap: Ethernet hwaddr 00: 0C: 29: 99: DF: 0f Inet ADDR: 192.168.7.71 bcast: 192.168.7.255 mask: 255.255.255.0 inet6 ADDR: fe80: 20c: 29ff: fe99: df0f/64 scope: link up broadcast running Multicast MTU: 1500 Metric: 1 RX packets: 754 errors: 0 dropped: 0 overruns: 0 frame: 0 TX packets: 12 errors: 0 dropped: 0 overruns: 0 carrier: 0 Collisions: 0 txqueuelen: 1000 RX Bytes: 136187 (132.9 KB) TX Bytes: 936 (936.0 B) eth1 link encap: Ethernet hwaddr 00: 0C: 29: 99: DF: 19 Inet ADDR: 10.10.7.71 bcast: 10.10.7.255 mask: 255.255.255.0 inet6 ADDR: fe80: 20c: 29ff: fe99: df19/64 scope: link up broadcast running Multicast MTU: 1500 Metric: 1 RX packets: 752 errors: 0 dropped: 0 overruns: 0 frame: 0 TX packets: 12 errors: 0 dropped: 0 overruns: 0 carrier: 0 Collisions: 0 txqueuelen: 1000 RX Bytes: 136065 (132.8 KB) TX Bytes: 936 (936.0 B) 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: 16436 Metric: 1 RX packets: 206 errors: 0 dropped: 0 overruns: 0 frame: 0 TX packets: 206 err ORS: 0 dropped: 0 overruns: 0 carrier: 0 Collisions: 0 txqueuelen: 0 RX Bytes: 13803 (13.4 KB) TX Bytes: 13803 (13.4 KB) In fact, you can set the NIC to a meaningful interface name, such as lan0, lan1, public0, and public1. Author: Robinson blog: http://blog.csdn.net/robinson_0612

More references

Passing variables between Linux/Unix shell SQL statements
Linux/Unix shell scripts call SQL and RMAN scripts
 

For more information about user-managed backup and recovery, see

Oracle cold backup

Oracle Hot Backup

Concept of Oracle backup recovery

Oracle instance recovery

Oracle recovery based on user management

System tablespace management and Backup Recovery

Sysaux tablespace management and recovery

Oracle backup control file recovery (unsing backup controlfile)

 

For information on RMAN backup recovery and management, see

RMAN overview and architecture

RMAN configuration, Monitoring and Management

Detailed description of RMAN backup

RMAN restoration and recovery

Create and use RMAN catalog

Create RMAN storage script based on catalog

Catalog-based RMAN backup and recovery

RMAN backup path confusion (when using plus archivelog)

 

For the Oracle architecture, see

Oracle tablespace and data files

Oracle Password File

Oracle parameter file

Oracle online redo log file)

Oracle Control File)

Oracle archiving logs

Oracle rollback and undo)

Oracle database instance startup and Shutdown Process

Automated Management of Oracle 10g SGA

Oracle instances and Oracle databases (Oracle Architecture)