From owner-freebsd-questions@FreeBSD.ORG Mon Feb 6 20:02:03 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7D1F106566B for ; Mon, 6 Feb 2012 20:02:03 +0000 (UTC) (envelope-from vrwmiller@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 630988FC17 for ; Mon, 6 Feb 2012 20:02:02 +0000 (UTC) Received: by wibhn14 with SMTP id hn14so7131362wib.13 for ; Mon, 06 Feb 2012 12:02:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=+7z7ebLLKFmwOafJqjVn25ARxgAtYcXAfTmNcyRwJbo=; b=UtXJtnn1ts91WFtVkqFEXOUNllunE//axkNcPgEafGt/Dy5PHWqBA+k2TZSHErKCKq pEMFeq+AsCyjn8dsKN+/NB5lK8V+SpQzBjk4Z/Myn86lxtW6HaEe38lhAYQmMiwsGQiR NuNiL1+/GnsY57avezlXRx/t1OUnVCCFmc6aQ= MIME-Version: 1.0 Received: by 10.180.102.35 with SMTP id fl3mr11996695wib.22.1328558522085; Mon, 06 Feb 2012 12:02:02 -0800 (PST) Sender: vrwmiller@gmail.com Received: by 10.227.143.140 with HTTP; Mon, 6 Feb 2012 12:02:01 -0800 (PST) In-Reply-To: <4F300391.2020002@locolomo.org> References: <4F2FF7D3.2030707@locolomo.org> <4F300391.2020002@locolomo.org> Date: Mon, 6 Feb 2012 15:02:01 -0500 X-Google-Sender-Auth: svahJWqSqQrNKCFt2fr-AS-FbEs Message-ID: From: Rick Miller To: =?ISO-8859-1?Q?Erik_N=F8rgaard?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-questions@freebsd.org Subject: Re: pxeboot.bs and vlan tagging X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2012 20:02:04 -0000 We have determined that it has failed after loading pxeboot.bs and before loading the kernel. Therefore, the kernel is not the problem. I have also determined that vlan tagging is not the problem as it has failed with vlan tagging disabled. I don't believe it is the content because it works in 3 out of 4 different environments. In fact, in the 4th environment in recent tests, it worked a handful of times before failing again. Suspecting network configurations at this point, but thanks for the input provided thus far. It has been immensely helpful. On Mon, Feb 6, 2012 at 11:45 AM, Erik N=F8rgaard wr= ote: > On 06/02/2012 17:33, Rick Miller wrote: >>>> >>>> 2) do you fetch the kernel successfully? >>>> >>>> When using tftp, The kernel and kernel modules are fetched before the >>>> memory >>>> file system, so do pxeboot fetch the kernel but not the mfsroot? >>>> >>>> The reason for these questions is that your problem may be with the >>>> kernel >>>> and kernel modules and not pxeboot. Just to be sure. >>> >>> >>> I see what you are saying. =A0We will have to look at the packet >>> captures to make that determination. >> >> >> The target system loads pxeboot.bs and consequently requests the >> following files: >> >> /boot/boot.4th (which it does not find) >> /boot/loader.rc >> /boot/loader.4th >> /boot/support.4th >> /boot/defaults/loader.conf >> /boot/device.hints >> /boot/loader.conf >> >> It is at this point where the failure occurs. =A0The contents of loader.= conf >> are: >> >> mfsroot_load=3D"YES" >> mfsroot_type=3D"mfs_root" >> mfsroot_name=3D"/boot/mfsroot" >> >> Does this seem consistent with what you were theorizing that it's the >> kernel that has the problem with vlan tagging and not pxeboot.bs? > > > See the other mail, the way pxeboot works IIRC, is that first the pxeboot= is > fetched using tftp, the pxeboot is given the next server and will fetch t= he > kernel, modules and other files from /boot/ on that server, (path respect= ive > to the root of the tftp dir). > > The kernel loads and will then fetch the mfsroot file. As mentioned, by > default this is done using nfs, and nfs is assumed if the kernel supports > nfs, even if it only fetches one file. This I understand has to be this w= ay > since the network configuration set with dhcp does not specify the protoc= ol. > > So, if your kernel supports nfs it will not use tftp and hence fail. > > The details are somewhat distant to me, it's been some time since I messs= ed > arround with this. > > hope this helps. > > BR, Erik > -- > M: +34 666 334 818 > T: +34 915 211 157 --=20 Take care Rick Miller