RedHat6.5 Nic problem summary

Source: Internet
Author: User
Problem description: Prepare to use RedHat6.5 to install Oracle12cRAC. After the system environment is ready, find that the configuration of the new RedHat Nic is not the same as before. The problem and solution are summarized as follows: 1, can not find the eth0 file in the use of RedHat6.5, the new installed system, found no eth0 Nic, the default first Nic is the Auto-eth0 [root @ rac01 ~] # Cat/etc/sysconfig/network-scripts/ifc

Problem description: Prepare to use RedHat6.5 to install Oracle 12c RAC. After the system environment is ready, find that the configuration of the new RedHat Nic is not the same as before. The problem and solution are summarized as follows:

1. The eth0 file cannot be found.

In the use of RedHat6.5, the new installed system, found that no eth0 Nic, the default first Nic is the Auto-eth0

[Root @ rac01 ~] # Cat/etc/sysconfig/network-scripts/ifcfg-Auto_eth0

TYPE = Ethernet

BOOTPROTO = none

IPADDR = 10.10.10.110

PREFIX = 24

GATEWAY = 10.10.10.111

DEFROUTE = yes

20174_failure_fatal = yes

IPV6INIT = no

NAME = eth0

UUID = 86dda-60-4579-48cc-b85b-219a206ca37c

ONBOOT = yes

HWADDR = 00: 50: 56: 95: 09: 76

LAST_CONNECT = 1411004329

 

Solution:

Directly renamed the ifcfg-Auto_eth0 file to eth0, restart the network card will find that the network card name has changed to eth0

[Root @ rac01 ~] # Service network restart

Bringing up loopback interface: [OK]

Bringing up interface eth0: Active connection state: activated

 

2. ifconfig finds that the NIC service name has not changed

[Root @ rac01 ~] # Ifconfig

Auto_eth0 Link encap: Ethernet HWaddr 00: 50: 56: 95: 09: 76

Inet addr: 10.10.10.110 Bcast: 10.10.10.111 Mask: 255.255.255.0

Inet6 addr: fe80: 250: 56ff: fe95: 976/64 Scope: Link

Up broadcast running multicast mtu: 1500 Metric: 1

RX packets: 484 errors: 0 dropped: 0 overruns: 0 frame: 0

TX packets: 57 errors: 0 dropped: 0 overruns: 0 carrier: 0

Collisions: 0 FIG: 1000

RX bytes: 40095 (39.1 KiB) TX bytes: 6271 (6.1 KiB)

Solution:

Each time you change the RedHat Nic information, RedHat automatically records the MAC address of the nic and the service name of the corresponding Nic in/etc/udev/rules. in d/70-persistent-net.rules, modify the corresponding service name.

 

[Root @ rac01 ~] # Vim/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 0x15ad: 0x07b0 (vmxnet3)

 

SUBSYSTEM = "net", ACTION = "add", DRIVERS = "? * ", ATTR {address} =" 00: 0c: 29: 1e: f6: ad ", ATTR {type} =" 1 ", KERNEL = "eth *", NAME = "eth0"

 

After modification, restart the system and check that the NIC service name has been changed.

[Root @ rac01 ~] # Ifconfig

Eth0 Link encap: Ethernet HWaddr 00: 50: 56: 95: 09: 76

Inet addr: 10.109.67.81 Bcast: 10.109.67.255 Mask: 255.255.255.0

Inet6 addr: fe80: 250: 56ff: fe95: 976/64 Scope: Link

Up broadcast running multicast mtu: 1500 Metric: 1

RX packets: 985 errors: 0 dropped: 0 overruns: 0 frame: 0

TX packets: 61 errors: 0 dropped: 0 overruns: 0 carrier: 0

Collisions: 0 FIG: 1000

RX bytes: 74395 (72.6 KiB) TX bytes: 6527 (6.3 KiB)

3. After the network adapter eth0 is deleted, the newly added network adapter is eth1. How can we start with eth0?
 

[Root @ rac01 ~] # Ifconfig

Eth1 Link encap: Ethernet HWaddr 00: 50: 56: 95: 09: 76

Inet addr: 10.10.10.110 Bcast: 10.10.10.111 Mask: 255.255.255.0

Inet6 addr: fe80: 250: 56ff: fe95: 976/64 Scope: Link

Up broadcast running multicast mtu: 1500 Metric: 1

RX packets: 830 errors: 0 dropped: 0 overruns: 0 frame: 0

TX packets: 57 errors: 0 dropped: 0 overruns: 0 carrier: 0

Collisions: 0 FIG: 1000

RX bytes: 63700 (62.2 KiB) TX bytes: 6259 (6.1 KiB)

 

Eth2 Link encap: Ethernet HWaddr 00: 0C: 29: 1E: F6: B7

Inet addr: 10.10.10.120 Bcast: 10.10.111mask: 255.255.255.0

Inet6 addr: fe80: 20c: 29ff: fe1e: f6b7/64 Scope: Link

Up broadcast running multicast mtu: 1500 Metric: 1

RX packets: 777 errors: 0 dropped: 0 overruns: 0 frame: 0

TX packets: 11 errors: 0 dropped: 0 overruns: 0 carrier: 0

Collisions: 0 FIG: 1000

RX bytes: 54938 (53.6 KiB) TX bytes: 746 (746.0 B)

 

 

 

Solution:

Similar to problem 2, you can manually modify the 70-persistent-net.rules file, change the corresponding MAC address and nic serial number to the desired one, or delete the file directly. After the system is restarted, redHat automatically creates the file and starts counting from 0.

Delete files and restart the system

[Root @ rac01 ~] # Mv/etc/udev/rules. d/70-persistent-net.rules/etc/udev/rules. d/7

0-persistent-net.rules.bak

[Root @ rac01 ~] # Reboot

Check again and you will find that it has started from eht0

[Root @ rac01 ~] # Ifconfig

Eth0 Link encap: Ethernet HWaddr 00: 50: 56: 95: 09: 76

Inet addr: 10.109.67.81 Bcast: 10.109.67.255 Mask: 255.255.255.0

Inet6 addr: fe80: 250: 56ff: fe95: 976/64 Scope: Link

Up broadcast running multicast mtu: 1500 Metric: 1

RX packets: 206 errors: 0 dropped: 0 overruns: 0 frame: 0

TX packets: 68 errors: 0 dropped: 0 overruns: 0 carrier: 0

Collisions: 0 FIG: 1000

RX bytes: 19282 (18.8 KiB) TX bytes: 7215 (7.0 KiB)

 

Eth1 Link encap: Ethernet HWaddr 00: 0C: 29: 1E: F6: B7

Inet addr: 10.109.67.83 Bcast: 10.109.67.255 Mask: 255.255.255.0

Inet6 addr: fe80: 20c: 29ff: fe1e: f6b7/64 Scope: Link

Up broadcast running multicast mtu: 1500 Metric: 1

RX packets: 131 errors: 0 dropped: 0 overruns: 0 frame: 0

TX packets: 11 errors: 0 dropped: 0 overruns: 0 carrier: 0

Collisions: 0 FIG: 1000

RX bytes: 8736 (8.5 KiB) TX bytes: 746 (746.0 B)

4. Every time you restart the NIC, always prompt

Active connection path:/org/freedesktop/NetworkManager/ActiveConnection/9

At this time, the network adapter can communicate normally, because the NetworkManager management tool developed by RedHat is not synchronized with the/etc/sysconfig/network-scripts/ifcfg-ethx configuration.

Solution:

To eliminate this prompt, close the NetworkManager service:

[Root @ rac01 ~] # Service network restart

Shutting down loopback interface: [OK]

Bringing up loopback interface: [OK]

Bringing up interface eth0: Active connection state: activated

Active connection path:/org/freedesktop/NetworkManager/ActiveConnection/2 [OK]

Bringing up interface eth1: Active connection state: activated

Active connection path:/org/freedesktop/NetworkManager/ActiveConnection/3 [OK]

 

Disable the NetworkManager service

[Root @ rac01 ~] # Service NetworkManager stop

Stopping NetworkManager daemon: [OK]

 

Restart the NIC again

[Root @ rac01 ~] # Service network restart

Shutting down loopback interface: [OK]

Bringing up loopback interface: [OK]

Bringing up interface eth0: [OK]

Bringing up interface eth1: [OK]

5. A prompt is displayed when you restart the NIC:
Bringing up interface eth0: Determining if ip address 10.109.67.81 is already in use for device eth0...
[OK]
Bringing up interface eth1: Determining if ip address 10.109.67.83 is already in use for device eth1...
[OK]


This warning is generally caused by arp resolution by the NIC. You can add the ARPCHECK = NO parameter to the NIC configuration file to block this check.
[Root @ rac01 ~] # Cat/etc/sysconfig/network-scripts/ifcfg-eth0
TYPE = Ethernet
BOOTPROTO = none
IPADDR = 10.109.67.81
PREFIX = 24
GATEWAY = 10.109.67.254
DEFROUTE = yes
20174_failure_fatal = yes
IPV6INIT = no
NAME = eth0
UUID = 86dda-60-4579-48cc-b85b-219a206ca37c
ONBOOT = yes
HWADDR = 00: 50: 56: 95: 09: 76
LAST_CONNECT = 1411004329
ARPCHECK = no

Enable the NIC again. Everything is normal.
[Root @ rac01 ~] # Service network restart
Shutting down interface eth0: [OK]
Shutting down interface eth1: [OK]
Shutting down loopback interface: [OK]
Bringing up loopback interface: [OK]
Bringing up interface eth0: [OK]
Bringing up interface eth1: [OK]

For more information about RedHat, see RedHat topic page http://www.linuxidc.com/topicnews.aspx? Tid = 10

This article permanently updates the link address: Http://www.linuxidc.com/Linux/2014-11/109536.htm

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.