From owner-freebsd-questions@FreeBSD.ORG Fri Apr 13 18:54:24 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 31632106566C for ; Fri, 13 Apr 2012 18:54:24 +0000 (UTC) (envelope-from kes-kes@yandex.ru) Received: from forward13.mail.yandex.net (forward13.mail.yandex.net [IPv6:2a02:6b8:0:801::3]) by mx1.freebsd.org (Postfix) with ESMTP id 1EED18FC08 for ; Fri, 13 Apr 2012 18:54:23 +0000 (UTC) Received: from smtp12.mail.yandex.net (smtp12.mail.yandex.net [95.108.131.191]) by forward13.mail.yandex.net (Yandex) with ESMTP id AD09C140CAB; Fri, 13 Apr 2012 22:54:21 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1334343261; bh=FNV3ZS/KkXBUnTsQwuaL5m2719dG4KuNaBob8EYzzaY=; h=Date:From:Reply-To:Message-ID:To:CC:Subject:In-Reply-To: References:MIME-Version:Content-Type:Content-Transfer-Encoding; b=cpPtpkN1UN4MWV5otAXJwrANqBwKe9VepRdVEsl64if2siRy0A5qc1ZPmuIaEgCBj 7GXYpNUo/6IwCySNFlMLz5NE1eGjjHKT6nDXp0P+lzmuQ02JTPAXGchKlJTSogxfHd zjp89CPba1+ZHv5Geo2YV2D0bAn3vudG1PVOWeeg= Received: from smtp12.mail.yandex.net (localhost [127.0.0.1]) by smtp12.mail.yandex.net (Yandex) with ESMTP id 89E4D16A0557; Fri, 13 Apr 2012 22:54:21 +0400 (MSK) Received: from unknown (unknown [77.93.52.20]) by smtp12.mail.yandex.net (nwsmtp/Yandex) with ESMTP id sHNWXPqm-sLN8xrjP; Fri, 13 Apr 2012 22:54:21 +0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1334343261; bh=FNV3ZS/KkXBUnTsQwuaL5m2719dG4KuNaBob8EYzzaY=; h=Date:From:X-Mailer:Reply-To:Organization:X-Priority:Message-ID:To: CC:Subject:In-Reply-To:References:MIME-Version:Content-Type: Content-Transfer-Encoding; b=ABV4J2OisYwmcFN7V40O7IF/8zclotDT7GksMXWMzSlzDLUfDM+j14C96ir9Y/uGT ok8kW/b4ep06d9jAdCZChLyouPY3u1m0CdjXTo/Oz9F4WQ9ojpd3hKDUZ47ttqCkLo DtUWA9y62Bkyz9LEsGMX398AHRrSeO82XtWcZ5lg= Date: Fri, 13 Apr 2012 21:54:17 +0300 From: =?koi8-r?B?68/O2MvP1yDl18fFzsnK?= X-Mailer: The Bat! (v4.0.24) Professional Organization: =?koi8-r?B?/vAg68/O2MvP1ywgRnJlZUxpbmU=?= X-Priority: 3 (Normal) Message-ID: <1133680770.20120413215417@yandex.ru> To: Damien Fleuriot In-Reply-To: References: <505981334167684@web133.yandex.ru> <26203474.20120412233549@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Cc: "freebsd-questions@freebsd.org" , KES Subject: Re[4]: Problem with vlans on igb (was: fsck problem FreeBSD 8.3) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?koi8-r?B?68/O2MvP1yDl18fFzsnK?= List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2012 18:54:24 -0000 Здравствуйте, Damien. Вы писали 13 апреля 2012 г., 4:42:31: DF> Yes, I suggest you try with "-vlanhwtag" as well. DF> If that stops your unwanted reboots, you may want to remove it and see DF> if the situation changes. igb0: flags=8843 metric 0 mtu 1500 options=400b8 ether a0:36:9f:00:66:a4 media: Ethernet autoselect (1000baseT ) status: active igb1: flags=8843 metric 0 mtu 1500 options=400b8 ether a0:36:9f:00:66:a5 media: Ethernet autoselect (1000baseT ) status: active igb2: flags=8843 metric 0 mtu 1500 options=400b8 ether a0:36:9f:00:66:a6 media: Ethernet autoselect (1000baseT ) status: active igb3: flags=8843 metric 0 mtu 1500 options=400b8 ether a0:36:9f:00:66:a7 media: Ethernet autoselect (1000baseT ) status: active vlan407: flags=8843 metric 0 mtu 1500 ether a0:36:9f:00:66:a4 inet xxxxxxxx netmask 0xfffffff8 broadcast xxxxxxxx media: Ethernet autoselect (1000baseT ) status: active vlan: 407 parent interface: igb0 vlan408: flags=8843 metric 0 mtu 1500 ether a0:36:9f:00:66:a5 inet xxxxxxxxx netmask 0xfffffff8 broadcast xxxxxxxxxxx media: Ethernet autoselect (1000baseT ) status: active vlan: 408 parent interface: igb1 vlan492: flags=8843 metric 0 mtu 1500 ether a0:36:9f:00:66:a5 inet xxxxxxxxxxxx netmask 0xfffffff8 broadcast xxxxxxxxx media: Ethernet autoselect (1000baseT ) status: active vlan: 492 parent interface: igb1 vlan70: flags=8843 metric 0 mtu 1500 ether a0:36:9f:00:66:a7 inet xxxxxxxx netmask 0xfffffe00 broadcast xxxxxx media: Ethernet autoselect (1000baseT ) status: active vlan: 70 parent interface: igb3 vlan71: flags=8843 metric 0 mtu 1500 ether a0:36:9f:00:66:a7 inet xxxxxxxxxxx netmask 0xfffffe00 broadcast xxxxxxx media: Ethernet autoselect (1000baseT ) status: active vlan: 71 parent interface: igb3 vlan72: flags=8002 metric 0 mtu 1500 ether 00:00:00:00:00:00 vlan: 0 parent interface: vlan73: flags=8843 metric 0 mtu 1500 ether a0:36:9f:00:66:a7 inet xxxxxxxxx netmask 0xfffffe00 broadcast xxxxxxxxx media: Ethernet autoselect (1000baseT ) status: active vlan: 73 parent interface: igb3 vlan74: flags=8002 metric 0 mtu 1500 ether 00:00:00:00:00:00 vlan: 0 parent interface: vlan75: flags=8002 metric 0 mtu 1500 ether 00:00:00:00:00:00 vlan: 0 parent interface: vlan76: flags=8843 metric 0 mtu 1500 ether a0:36:9f:00:66:a7 inet xxxxxxxxxxx netmask 0xfffffe00 broadcast xxxxxxx media: Ethernet autoselect (1000baseT ) status: active vlan: 76 parent interface: igb3 vlan100: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan101: flags=8843 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 inet xxxxxxxxxx netmask 0xffffff00 broadcast xxxxxxxxxxx media: Ethernet autoselect (1000baseT ) status: active vlan: 101 parent interface: igb2 vlan102: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan103: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan104: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan105: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan106: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan107: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan108: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan109: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan110: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan111: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan112: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan113: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan114: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan115: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan: 0 parent interface: vlan115: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: With this config no 'REBOOT' happen When just assign vlan100, 102-115 to igb2 and add IPs to those interfaces (no any traffic on those vlans yet) server starts to reboot. In evening time =) You sugestion to disable 'vlanhwtag' I will try after holidays. Do not want to risk now =). One more question: I must disable vlanhwtag on all igbs, or only on igb2? (this is four head LAN) -- С уважением, Коньков mailto:kes-kes@yandex.ru