First successful deployment of dual NIC Bindings

Yesterday before work installed CentOS 5.11, today came to the company began to do.

Since this Dell R420 server is a standby machine, the configuration information that binds the dual NIC is fully referenced to the master server. The configuration is complete, ping intranet is not a problem, however, after configuring the DNS address, always can not ping the DNS address, naturally you can not ping the extranet.

After the leadership took over, check my dual network card configuration file, unplug the network cable switch test, and then directly configured to Eth0 and then ping the outside network, are not.

　　The error output of the "ping 8.8.8.8" command was "Connect:network is unreachable", which made the leader confused and why there was such a hint.

Some of the information on the Internet, said to be such a hint, is because the network adapter configuration problem, can not find the network card and so on.

In the afternoon, the leader decided to reload the server.

When I first installed this server yesterday afternoon, I followed the "minimize" installation principle in the 1th lesson of Oldboy, selecting only the following 7 packages:

Base

Editors

Development Librarys (Development Library)

Development tools (development tools)

X Software Development

System Tools

Dialup Networking support "optional"

I'm not sure if it's about too few packages, but the second time I install CentOS in the afternoon, I don't want to take that risk anymore. During the installation process, the large class of packages selected is "Desktop-gnome".

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/5A/1B/wKioL1T2xN2icay6AAGgMnDg4W4708.jpg "title=" Install the large class. png "alt=" wkiol1t2xn2icay6aaggmndg4w4708.jpg "/>

　　The specific software package, only the graphics, sound card, game, printer-related software packages have been canceled, the other packages are not moving.

After the installation of CentOS 5.11, only 4 files were edited:

[Email protected] ~]# cat/etc/sysconfig/network-scripts/ifcfg-bond0 device=bond0type=ethernetonboot=yesuserctl= nobootproto=staticipaddr=172.16.30.122netmask=255.255.255.0network=172.16.30.0broadcast=172.16.30.255gateway= 172.16.30.1dns1=8.8.8.8

[Email protected] ~]# cat/etc/sysconfig/network-scripts/ifcfg-eth0# Broadcom Corporation netxtreme BCM5720 Gigabit Ethernet Pciedevice=eth0bootproto=statichwaddr=b0:83:fe:bf:ba:ebonboot=yesuserctl=nomaster=bond0slave=yes

[Email protected] ~]# cat/etc/sysconfig/network-scripts/ifcfg-eth1# Broadcom Corporation netxtreme BCM5720 Gigabit Ethernet Pciedevice=eth1bootproto=nonehwaddr=b0:83:fe:bf:ba:econboot=yesuserctl=nomaster=bond0slave=yes

[Email protected] ~]# cat/etc/modprobe.conf alias eth0 tg3alias eth1 tg3alias scsi_hostadapter megaraid_sasalias scsi_ho Stadapter1 ahci## #bonding # # #alias bond0 bondingoptions bond0 miimon=100 mode=1 primary=eth0

After configuring DNS1 's address "dns1=8.8.8.8" in the/etc/sysconfig/network-scripts/ifcfg-bond0 configuration file, the following/etc/resolv.conf configuration file restarts the network "/etc/ Init.d/network Restart "is automatically written to the DNS address. Therefore, I did not move the/etc/resolv.conf file.

[Email protected] ~]# Cat/etc/resolv.confnameserver 8.8.8.8

Perform the "/etc/init.d/network restart" command to restart the network service.

At this point, the result of the ping command is normal.

[[email protected] ~]# ping www.baidu.comping www.a.shifen.com  (111.13.100.91)  56 (+)  bytes of data.64 bytes from 111.13.100.91: icmp_seq=1 ttl =52 time=18.0 ms64 bytes from 111.13.100.91: icmp_seq=2 ttl=52 time= 17.8 ms64 bytes from 111.13.100.91: icmp_seq=3 ttl=52 time=17.9 ms---  www.a.shifen.com ping statistics ---3 packets transmitted, 3 received ,  0% packet loss, time 2001msrtt min/avg/max/mdev = 17.858/17.957/ 18.078/0.142 ms[[email protected] ~]# ping 8.8.8.8ping 8.8.8.8  (8.8.8.8)  56 (+)  bytes of data.64 bytes from 8.8.8.8: icmp_seq=1 ttl=40  time=80.9 ms64 bytes from 8.8.8.8: icmp_seq=2 ttl=40 time=75.8  ms64 bytes from 8.8.8.8: icmp_seq=3 ttl=40 time=77.2 ms64 bytes from 8.8.8.8:  ICMP_SEQ=4 TTL=40 TIME=77.4 MS--- 8.8.8.8 ping statistics ---4 packets  transmitted, 4 received, 0% packet loss, time 3003msrtt min/avg/ Max/mdev = 75.845/77.864/80.922/1.869 ms

I use the Oldboy installation method, the virtual machine has been used many times, has never had a problem. This is the 2nd time that the production environment is actually used. Full reference to his package requirements, this is the 1th time.

I don't know if the 1th time problem is related to the choice of too few packages. If there is a chance, I will continue to test this thing on other machines.

I want to say that the final thing is to complete the leadership arrangement, not to dwell on some short-term details.

This article is from the "Dark-matter" blog, make sure to keep this source http://gagarin.blog.51cto.com/1056957/1617281

First successful deployment of dual NIC Bindings