How to quickly identify the corresponding relationship between the network card ID and the physical network card (that is, the Ethtool command) when multiple NICs are under Linux

The general purchase of the server has 4 network cards, this time after the installation of the server, configure the IP when it is depressed

As a wave 8560m2 server installed Redhat after the network card display:

[Email protected] ~]# ifconfig-a

Eth0 Link encap:ethernet HWaddr 00:e0:ed:2d:0f:58

inet addr:192.168.4.10 bcast:192.168.4.255 mask:255.255.255.0

Up broadcast RUNNING multicast mtu:1500 metric:1

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

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

collisions:0 txqueuelen:1000

RX bytes:3413500 (3.2 MiB) TX bytes:44521 (43.4 KiB)

memory:faee0000-faf00000

eth1 Link encap:ethernet HWaddr 00:e0:ed:2d:0f:59

Broadcast Multicast mtu:1500 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:1000

RX bytes:0  (0.0 b) TX bytes:0 (0.0 b)

memory:fae60000-fae80000

Eth2 Link encap:ethernet HWaddr 00:25:90:5a:15:b6

Broadcast Multicast mtu:1500 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:1000

RX bytes:0  (0.0 b) TX bytes:0 (0.0 b)

memory:fafe0000-fb000000

Eth3 Link encap:ethernet HWaddr 00:25:90:5a:15:b7

Broadcast Multicast mtu:1500 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:1000

RX bytes:0  (0.0 b) TX bytes:0 (0.0 b)

memory:faf60000-faf80000

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:10 errors:0 dropped:0 overruns:0 frame:0

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

collisions:0 txqueuelen:0

RX bytes:660 (660.0 b) TX bytes:660 (660.0 b)

When I moved down from a computer room, I forgot to mark it. At this time still want to modify eth0 as communication port. But a plug and pull more trouble, so I think there is a good way, after all, Linux is not as intuitive as windows, open the network connection can be seen. This is the time to use the Ethtool command, the command is explained as follows:

Command Description:

Ethtool is a command for querying and setting network card parameters.

ETHX is the name of the Ethernet card, and the Linux system names the first Ethernet card detected as eth0, and the second block is eth1,.......。

Usage Summary:

Ethtool ethx//Query ETHX network port basic settings, where x is the number of the corresponding network card, such as eth0, eth1, etc.

ETHTOOL–H//Show command Help for Ethtool

Ethtool–i EthX//query EthX information about the network port

Ethtool–d EthX//Query EthX network Port registration information

Ethtool–r EthX//Reset EthX mesh to Adaptive mode

Ethtool–s EthX//Query EthX network Port receipt Package statistics

Ethtool–s EthX [Speed 10|100|1000] [duplex half|full] [Autoneg On|off]//Set the network port rate 10/100/1000m, set the network port half/full duplex, set the network port self-negotiation

Ethtool [-A |-c |-G |-i |-d |-k |-r |-S |] EthX

Ethtool [-A] EthX [Autoneg on|off] [rx On|off] [TX on|off]

Ethtool [-c] EthX [Adaptive-rx on|off] [adaptive-tx on|off] [rx-usecs n] [rx-frames n] [rx-usecs-irq n] [RX-FRAMES-IRQ n] [Tx-usecs N] [Tx-frames N] [Tx-usecs-irq N] [Tx-frames-irq N] [Stats-block-usecs N] [Pkt-rate-low N] [Rx-usecs-low N] [Rx-frames-low N] [Tx-usecs-low N] [Tx-frames-lown] [Pkt-rate-high N] [Rx-usecs-high N] [Rx-frames-high N] [Tx-usecs-high N] [Tx-frames-high N] [Sample-interval N]

Ethtool [-G] EthX [rx n] [rx-mini n] [Rx-jumbo n] [TX n]

Ethtool [-e] EthX [raw on|off] [offset n] [length N]

Ethtool [-e] EthX [magic n] [offset n] [value n]

Ethtool [-K] EthX [rx On|off] [TX on|off] [SG On|off] [TSO On|off]

Ethtool [-P] ethX [N]

Ethtool [-T] EthX [Offline|online]

Ethtool [-S] ethX [speed 10|100|1000] [duplex half|full] [Autoneg on|off] [Port tp|aui|bnc|mii] [Phyad N] [XCVR internal|e Xternal]

[Wol p|u|m|b|a|g|s|d ...] [Sopass XX:YY:ZZ:AA:BB:CC] [Msglvl N]

Sign

-A	Check the status of the Receive Module RX, transmit module TX, and Autonegotiate module in the network card: start on or deactivate off
-A	Modify the status of the Receive Module RX, transmit module TX, and Autonegotiate module in the NIC: Start on or deactivate off
-C	Display the coalesce information of the specified Ethernet card
-C	Change the coalesce setting of the specified Ethernet card
-G	Display the Rx/tx ring parameter information of the specified Ethernet card
-G	Change the Rx/tx ring setting of the specified Ethernet card
-I.	Display network card driver information, such as the name of the driver, version, etc.
-D	Register dump information is displayed and some NIC drivers do not support this option
-E	Display EEPROM dump information, partial NIC driver does not support this option
-E	Modify the NIC Eeprom byte
-K	Displays the status of the NIC offload parameter: On or off, including rx-checksumming, tx-checksumming, and so on.
-K	Modifying the status of the NIC offload parameter
-P	Used to distinguish the physical location of different ethx corresponding network card, the common method is to make the network card on the port of the LED constantly flashing; n indicates the duration of the network card Flash, in seconds.
-R	If the status of the Auto-negotiation module is on, the restarts auto-negotiation
-S	Displays the statistical parameters of the Nic-and driver-specific, such as the number of bytes received/sent by the NIC, the number of broadcast packets received/sent, etc.
-T	To have the NIC perform self-detection, there are two modes: offline or online
-S	Modify some of the network card configuration, including network card speed, simplex/full duplex mode, MAC address, etc.

Reference: http://blog.sina.com.cn/s/blog_71f38909010128yf.html

The point is that I use the following command here:

[Email protected] ~]# ethtool-p eth0

At this point you will see the corresponding physical mouth a light is flashing, right. This is the network card that we see in the system called Eth0. It's that simple.

This article is from the "Flying Pig" blog, make sure to keep this source http://thinkpig007.blog.51cto.com/971471/1436694