similar to: How to change NIC alias?

I have two servers with identical hardware ... TYAN i3210w system boards with dual intel gigabit interfaces, and a PCI intel gigabit nic. I'm running Centos 5.4, x86_64, 2.6.18-164.6.1.el5 Every other time I reboot, the nics initialize in a different order. anaconda had setup /etc/modprobe.conf with alias lines for the cards: alias eth0 e1000 alias eth1 e1000e alias eth2 e1000e However,

Right, I understand that part. However I believe I'm now in the realm of making this specific to this machine as I have no guarantee that another identical machine will pop up with those same bus IDs. Maybe for the internal ports, but I don't know if the same will happen for the PCIe bus. Would that be correct? On Thu, May 14, 2015 at 6:21 PM, Kahlil Hodgson < kahlil.hodgson at

Actually, I know what the MAC is for the builtin Port1 and 2. Those are listed in the BIOS. But ultimately I don't want to rely on them as I want the same kickstart file to work for other machines, so hardcoding those in the kickstart file wouldn't quite work, unless I start writing multiple kickstart files, one per machine. Anyway, lspci reports this: 00:19.0 Ethernet controller: Intel

Hello, I've got a very strange problem. Lately I've been setting up my linux servers for network (layer2) redundancy with a bridge interface containing two ethernet interfaces connecting to two switches. So far I didn't have any problems with it, but now a very strange thing happens with a new server I'm installing. The server is an ibm x346 having two onboard BCM5721 cards, the

I'm running 7.0-RELEASE-i386 on Jetway's NC92-N230 mainboard. The board has one integrated RTL8168/8111 gigabit NIC as well as an expansion board with three RTL8168/8111 NICs. Why would the three NICs work while the onboard NIC does not? none2@pci0:1:0:0: class=0x020000 card=0x816810ec chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device

On 03/27/2017 04:03 PM, Kevin Stange wrote: > On 03/25/2017 02:35 PM, Sarah Newman wrote: >> On 03/16/2017 04:22 PM, Kevin Stange wrote: >> >>>> I still can't rest assured the NIC issue is fixed, but no 4.4 or 4.9 >>>> server has yet had a NIC issue, with some being up almost a full month. >>>> It looks promising! (I'm knocking on all the

I have a hardware here with 9 NICs (8 of them on-board) and I want to set up 8 NICs as real network interfaces, one for each xen domain. The 9th NIC should be Domain-0 which is working well. Currently I have only set up one domain which is running in bridged mode at the moment. I am currently trying to set up a second domain which uses eth2 but I didn''t succeed. I want to get the

Hello All, I have one CentOS 6 KVM virtualization server that I built around a year ago (best I can tell it was in October 2012) at which time I would have been installing 6.3 [0]. That particular install used the Consistent Network Device Naming [1] conventions (PCIe NICs are p1p1, p1p2). I started to build out a new KVM virt server (kickstarting a 6.4 install now as compared to 6.3 back then)

On Tue, Apr 11, 2017 at 08:09:01AM -0400, Pete Orrall wrote: > > And *why* random NIC names? Quick, you've got servers from 5 > > manufacturers, of different ages... what's the NIC going to be called? Do > > names like enp5s0 offer any convenience to *anyone* not a hardware > > engineer? > > As someone else had stated, it's not related to SystemD but >

Hi All, Long time no chat ;-) Asterisk 1.0.9 (sometimes) won't authenticate IAX phones after re-boot of SuSE 9.3 box I've traced the problem to be with the firewall and the fact that I have 2 NICs in the box. Now that I have opened port 4569 on both interfaces, asterisk seems happy *but* does anyone know how to force SuSE 9.3 to always bring up a specific NIC before the otherone? On

When I was working on this last time (with the r8169 driver), someone on this list provided the following script which is what "fixed" the issue at the time by creating a new 70-persistent-net.rules file with the devices enumerated in order. However, this no longer works now. echo "[KICKSTART] Binding eth interfaces to the expected MAC address in UDEV" echo "## Created by

Hi all, I just noticed that my two nics that are bonded via mode 0 are showing the same mac addy in ifconfig. Is this normal? In syslog I keep getting; kernel: pbond0: received packet with own address as source address Some guidance is appreciated before I dive in and troubleshoot. If I don't list the mac addy in my ifcfg-th# files, only one of the 2 nic comes up during boot.

Hello all, I'm not able to install CentOS in a motherboard with a onboard 3Com gigabit nic (3c904/Syskonnect). Although there's a device driver for the Syskonnect (sk98lin) in the linux kernel, the installation program is asking for this interface module. I tried to create a device disk, but without success. Maybe I'm missing some information about the modules detection by the

I just yum-installed the 2.6.9-34 kernel RPMs and rebooted, and lo and behold, my other onboard NIC is now detected, after a fashion. /etc/sysconfig/hwconf now has entries for: device: eth0 driver: forcedeth desc: "nVidia Corporation CK804 Ethernet Controller" device: eth2 driver: sky2 desc: "Marvell Technology Group Ltd. 88E8053 Gigabit Ethernet Controller" The device/desc

The gigabit NIC on my mainboard died, and I am currently running on a PCI 10/100 nic. I want to get a gigabit NIC installed as soon as possible, preferably a PCI-Express one, but I am not sure what will and won''t work with the native xen kernel, and I don''t really want to custom build my own kernel because I have yet to successfully compile a xen kernels in spite of the fact

I was given the challenge recently of creating a LAN-LAN bridge between two buildings several hundred metres from each other, using only existing Cat 3 wiring and without having to resort to an expensive and finicky 5 Ghz wireless link. I was able to create a 90 megabit link for about $3,000 Cdn with new PC's, CentOS 4.1, and the newly avaliable Black Box VDSL Ethernet Extender, which

On Mon, Jan 10, 2011 at 12:08 PM, Rudi Ahlers <Rudi at softdux.com> wrote: > On Mon, Jan 10, 2011 at 11:49 AM, compdoc <compdoc at hotrodpc.com> wrote: >> I love realtek - the resources they use tend not to conflict with other >> cards or hardware, they don't use much cpu time, the drivers are mature, and >> they don't cost much. What could be better? There

Setting up bonding in active-backup mode 1 (using ARP monitoring) on a server, it looked OK, but pulling the active link cable didn't actually work, it didn't fail over. Eventually with manual playing around with modprobe, ifconfig, ifenslave, etc., a solution was stumbled upon: enslave the eth1 device before eth0, and all is good. Why this should matter is a puzzle - I could not find

Digium's site now lists the Dell 1850 as a potential problem server, as it uses the intel ee1000 Ethernet chipset (as do a majority of servers in the market!). To my knowledge, ALL dell servers with Gigabit interfaces now use the same chipset. Does this mean the Digium cards can't be used in Dell servers unless you disable the onboard ethernet? I don't want to disable the onboard

Dear All, I have an onboard Realtek RTL8111/8168B NIC. from lspci -vv : 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) It is detected, but why the speed is always 100Mbps, already change cable but still no luck. I use ethtool and from the output it seems that system know that this NIC support gigabit speed : ???????