Ich habe zwei netzwerkkarten verbaut. Am schluss ist das ziel alle mit Bonding zu betreiben. Leider kriege ich eine netzwerkkarte nicht zum laufen.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 | martin@u-server:~$ uname -a Linux u-server 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux martin@u-server:~$ lspci -nnk | grep -i net -A2 04:00.0 Ethernet controller [0200]: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) [8086:1096] (rev 01) Subsystem: Intel Corporation Intel S5000PSLSATA Server Board [8086:3476] Kernel driver in use: e1000e -- 04:00.1 Ethernet controller [0200]: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) [8086:1096] (rev 01) Subsystem: Intel Corporation Intel S5000PSLSATA Server Board [8086:3476] Kernel driver in use: e1000e -- 09:00.0 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller [8086:105e] (rev 06) Subsystem: Intel Corporation PRO/1000 PT Dual Port Server Adapter [8086:125e] Kernel driver in use: e1000e -- 09:00.1 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller [8086:105e] (rev 06) Subsystem: Intel Corporation PRO/1000 PT Dual Port Server Adapter [8086:125e] Kernel driver in use: e1000e martin@u-server:~$ martin@u-server:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp4s0f0 iface enp4s0f0 inet dhcp auto enp4s0f1 iface enp4s0f1 inet dhcp auto enp9s0f0 iface enp4s0f0 inet dhcp auto enp4s0f1 iface enp4s0f1 inet dhcp martin@u-server:~$ ifconfig -a enp4s0f0 Link encap:Ethernet Hardware Adresse 00:15:17:64:83:7c inet Adresse:192.168.100.45 Bcast:192.168.100.255 Maske:255.255.255.0 inet6-Adresse: fe80::215:17ff:fe64:837c/64 G�ltigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1 RX-Pakete:2520 Fehler:0 Verloren:0 �berl�ufe:0 Fenster:0 TX-Pakete:300 Fehler:0 Verloren:0 �berl�ufe:0 Tr�ger:0 Kollisionen:0 Sendewarteschlangenl�nge:1000 RX-Bytes:298196 (298.1 KB) TX-Bytes:35260 (35.2 KB) Interrupt:18 Speicher:ba820000-ba840000 enp4s0f1 Link encap:Ethernet Hardware Adresse 00:15:17:64:83:7d inet Adresse:192.168.100.36 Bcast:192.168.100.255 Maske:255.255.255.0 inet6-Adresse: fe80::215:17ff:fe64:837d/64 G�ltigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1 RX-Pakete:2130 Fehler:0 Verloren:0 �berl�ufe:0 Fenster:0 TX-Pakete:11 Fehler:0 Verloren:0 �berl�ufe:0 Tr�ger:0 Kollisionen:0 Sendewarteschlangenl�nge:1000 RX-Bytes:249396 (249.3 KB) TX-Bytes:1718 (1.7 KB) Interrupt:19 Speicher:ba800000-ba820000 enp9s0f0 Link encap:Ethernet Hardware Adresse 00:15:17:bf:f6:e0 BROADCAST MULTICAST MTU:1500 Metrik:1 RX-Pakete:0 Fehler:0 Verloren:0 �berl�ufe:0 Fenster:0 TX-Pakete:0 Fehler:0 Verloren:0 �berl�ufe:0 Tr�ger:0 Kollisionen:0 Sendewarteschlangenl�nge:1000 RX-Bytes:0 (0.0 B) TX-Bytes:0 (0.0 B) Interrupt:27 Speicher:bac60000-bac80000 enp9s0f1 Link encap:Ethernet Hardware Adresse 00:15:17:bf:f6:e1 BROADCAST MULTICAST MTU:1500 Metrik:1 RX-Pakete:0 Fehler:0 Verloren:0 �berl�ufe:0 Fenster:0 TX-Pakete:0 Fehler:0 Verloren:0 �berl�ufe:0 Tr�ger:0 Kollisionen:0 Sendewarteschlangenl�nge:1000 RX-Bytes:0 (0.0 B) TX-Bytes:0 (0.0 B) Interrupt:29 Speicher:bac20000-bac40000 lo Link encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 inet6-Adresse: ::1/128 G�ltigkeitsbereich:Maschine UP LOOPBACK RUNNING MTU:65536 Metrik:1 RX-Pakete:176 Fehler:0 Verloren:0 �berl�ufe:0 Fenster:0 TX-Pakete:176 Fehler:0 Verloren:0 �berl�ufe:0 Tr�ger:0 Kollisionen:0 Sendewarteschlangenl�nge:1 RX-Bytes:13392 (13.3 KB) TX-Bytes:13392 (13.3 KB) |
Das modul e1001e ist vorhanden
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 | martin@u-server:~$ lsmod Module Size Used by ipmi_ssif 24576 0 coretemp 16384 0 kvm_intel 172032 0 kvm 544768 1 kvm_intel lpc_ich 24576 0 irqbypass 16384 1 kvm input_leds 16384 0 i5000_edac 20480 0 serio_raw 16384 0 edac_core 53248 2 i5000_edac shpchp 36864 0 8250_fintek 16384 0 i5k_amb 16384 0 mac_hid 16384 0 ipmi_si 57344 0 ipmi_msghandler 49152 2 ipmi_ssif,ipmi_si ib_iser 49152 0 rdma_cm 49152 1 ib_iser iw_cm 45056 1 rdma_cm ib_cm 45056 1 rdma_cm ib_sa 36864 2 rdma_cm,ib_cm ib_mad 49152 2 ib_cm,ib_sa ib_core 106496 6 rdma_cm,ib_cm,ib_sa,iw_cm,ib_mad,ib_iser ib_addr 20480 2 rdma_cm,ib_core iscsi_tcp 20480 0 libiscsi_tcp 24576 1 iscsi_tcp libiscsi 53248 3 libiscsi_tcp,iscsi_tcp,ib_iser scsi_transport_iscsi 98304 4 iscsi_tcp,ib_iser,libiscsi autofs4 40960 2 xfs 970752 4 btrfs 987136 0 drbg 32768 1 ansi_cprng 16384 0 xts 16384 1 gf128mul 16384 1 xts algif_skcipher 20480 0 af_alg 16384 1 algif_skcipher dm_crypt 28672 1 raid10 49152 0 raid456 110592 0 async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 async_pq,raid456,async_xor,async_memcpy,async_raid6_recov xor 24576 2 btrfs,async_xor raid6_pq 102400 4 async_pq,raid456,btrfs,async_raid6_recov libcrc32c 16384 2 xfs,raid456 raid1 36864 0 raid0 20480 0 multipath 16384 0 linear 16384 0 amdkfd 131072 1 amd_iommu_v2 20480 1 amdkfd radeon 1515520 1 i2c_algo_bit 16384 1 radeon ttm 94208 1 radeon drm_kms_helper 155648 1 radeon syscopyarea 16384 1 drm_kms_helper sysfillrect 16384 1 drm_kms_helper hid_generic 16384 0 sysimgblt 16384 1 drm_kms_helper fb_sys_fops 16384 1 drm_kms_helper e1000e 237568 0 ahci 36864 0 usbhid 49152 0 pata_acpi 16384 0 ptp 20480 1 e1000e hid 118784 2 hid_generic,usbhid psmouse 131072 0 libahci 32768 1 ahci drm 364544 4 ttm,drm_kms_helper,radeon 3w_9xxx 45056 2 pps_core 20480 1 ptp fjes 28672 0 |
Was mich erstaunt ist
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 | martin@u-server:~$ systemctl status networking.service * networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Drop-In: /run/systemd/generator/networking.service.d `-50-insserv.conf-$network.conf Active: failed (Result: exit-code) since Son 2017-04-30 11:34:57 CEST; 50min ago Docs: man:interfaces(5) Process: 1181 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Process: 1169 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle Main PID: 1181 (code=exited, status=1/FAILURE) Apr 30 11:34:46 u-server systemd[1]: Starting Raise network interfaces... Apr 30 11:34:46 u-server sh[1169]: Unknown interface enp9s0f0 Apr 30 11:34:46 u-server ifup[1181]: /sbin/ifup: waiting for lock on /run/network/ifstate.enp4s0f0 Apr 30 11:34:56 u-server ifup[1181]: /sbin/ifup: waiting for lock on /run/network/ifstate.enp4s0f1 Apr 30 11:34:57 u-server ifup[1181]: Unknown interface enp9s0f0 Apr 30 11:34:57 u-server systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE Apr 30 11:34:57 u-server systemd[1]: Failed to start Raise network interfaces. Apr 30 11:34:57 u-server systemd[1]: networking.service: Unit entered failed state. Apr 30 11:34:57 u-server systemd[1]: networking.service: Failed with result 'exit-code'. martin@u-server:~$ |
Muss die rules.d/70-persistent-net.rules von hand kreieren oder giebt es einen besseren weg?
