installing a new network card from command line in CentSO

[RimBlock]

Hi,

I have enabled a passthrough network card on my ESXi server to my CentOS guest. How do I go about finding it and setting it up from the CentOS command line ?

The Nic is an Intel ET dual port and should not need any special drivers. A new install sets it up without any issue but using it in an existing install I can't seem to find too much information on.

Thanks
RB

 

[RimBlock]

lspci -v sees the controller...

03:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
Subsystem: Intel Corporation Gigabit ET Dual Port Server Adapter
Physical Slot: 160
Flags: bus master, fast devsel, latency 64, IRQ 18
Memory at d2420000 (32-bit, non-prefetchable) [size=128K]
I/O ports at 4000
Memory at d2400000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] MSI-X: Enable+ Count=10 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 90-e2-ba-ff-ff-00-0f-76
Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
Kernel driver in use: igb
Kernel modules: igb

I just have no idea on how to connect to it so I can use it.

I have tried creating a new ifcfg-eth1 file and setting the HWADDR to match the MAC address of the nic but no good.

more /proc/net/dev gives

Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
lo: 1692 31 0 0 0 0 0 0 1692 31 0 0 0 0 0 0
eth2: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
eth0: 4435076 46233 0 0 0 0 0 112 42591714 72833 0 0 0 0 0 0
sit0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

If I change the ifcfg-eth1 to eth2 and fix the eth1 references inside and restart networking I get an error about the MAC address not matching.

 

[RimBlock]

Hmm, removing the hardware address seems to have cleared it and now it is working.

Oh well, hopefully this may be of some use to someone else if they get stuck in this position.

RB