From owner-freebsd-amd64@freebsd.org Sun Apr 29 03:09:13 2018 Return-Path: Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE2F4FC2563; Sun, 29 Apr 2018 03:09:13 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 37AAB713BD; Sun, 29 Apr 2018 03:09:13 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: by mail-wm0-x241.google.com with SMTP id a137so6139734wme.1; Sat, 28 Apr 2018 20:09:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+0CR1fLqjfJ+zlBubMJwAfCujjl+6K1jE4ikdRfOIlU=; b=aFynqDQwSALWg6acHFWupAHrsOYISvQz7KqJ0hpxjSXyaDTtpFfd/WsUrwXFNZqNJy vJ/1auv/En1M7PHzqfOvBGKTvbJdZ9/votbsTQ9heTp0r4EJsfurWhK5Ny/fCcuMNeG6 FhCFWgFVRzcyvI3QCTTDE6AEkyDYRwwjpqZal89R38ea1hLyK4934bS327q8sPNsg6tE Vd6zsg29xOXUwQAxF3g5nnWobBuDacHmJdIDJt7INsQlXhcMCfJkJR+xEYQeYbkbGN19 aa6gGaa0EaZVpn0oHiOuoCPdVvIcWF6EpBPtET/K6CvXd6xzlQBwqjKqOnhkLWtAY9IA vWxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+0CR1fLqjfJ+zlBubMJwAfCujjl+6K1jE4ikdRfOIlU=; b=F9IMtV+lc3mWe5qsflrU3I5nqP/shM/qZ+OnAV//WwzyVkNKEKWldmnmEYGetgIAQ7 TmQ3diRj+b+J2XYk4g/tCKS6qd8fjkka1mabgdMTXdFq34073LoxTCBaT3DnzX6OUT3Z ZPMIZtBgvi4BWUPrdBeix/bAuwNUZkPRe719e9JQLaflW13tc3XEcOAfQgMZVddm7Lt5 3EmvDc5n8RMvmrsrxa8FhLBjab2ZzYHdCdPTjwOQdBduCuKTfqlq1VT9DGsYOGoAesfw QQLpHRImKr/Jag28nXLRy8m6lIgDVe+GeQsazFA3/bGHHhFaAONbhBEoEq7msqxWbRMF SZcw== X-Gm-Message-State: ALQs6tD/nlZ+ll6CAEGZkJaFdWPCH+pEZ/ERyUbEG7omE692agC+rVEy I+Xzc6l98RsTGWF1VAPjnryby0ih9SnmCi0GcY4= X-Google-Smtp-Source: AB8JxZqy2xU16D13mElxfuR+XQKA5vqdfGEaj9E7Udeif36cwwauxpBm7oc+TxohjRzXi+zS5/AbVSnHjvdtgeMu8Ic= X-Received: by 10.28.190.15 with SMTP id o15mr4745987wmf.104.1524971352113; Sat, 28 Apr 2018 20:09:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.171.232 with HTTP; Sat, 28 Apr 2018 20:08:31 -0700 (PDT) In-Reply-To: References: <5eca3020-4b9c-dd43-8cf0-066d63a92521@disroot.org> From: "Jack L." Date: Sat, 28 Apr 2018 20:08:31 -0700 Message-ID: Subject: Re: Can we please finally solve Dell's racadm for FreeBSD? Advice needed To: Nicolas Embriz Cc: "Peter G." , FreeBSD Hackers , freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 03:09:14 -0000 I manage a variety of Dell servers running FreeBSD, only 610 and 1950s work with racadm but everything that can be done with racadm can also be done with ipmitool. I just use ipmitool to get around instead of their proprietary racadm stuff. What functionality do you need from racadm and maybe I can give you an ipmitool equivalent? On Sat, Apr 28, 2018 at 6:54 AM, Nicolas Embriz wrote: > Regarding this topic I have a Dell Power 2900 that I could donate for > testing more in detail this issues. > > If interested please PM. > > Regards. > > On Sat, Apr 28, 2018 at 3:39 PM, Peter G. wrote: > >> Dear everybody, >> >> regarding: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201799 >> >> would somebody knowledgeable be kind enough to advice and/or help with >> bringing Dell racadm client/tools to FreeBSD? What is the problem with >> ipmi enumeration Dan mentioned on his commit? What is in the first place >> desired is local access to local hardware via standard racadm client. >> Local management is the "big kahuna" here. >> >> There were several attempts over the years, yet everything waned away >> without any solid results. Dell hardware is constantly mentioned on the >> lists or in the forums, so clearly many of us use it. I myself manage >> several Dell servers. The lack of local racadm for FreeBSD is daring. >> >> On my own and out of my pocket I will offer 50 EUR in Bitcoin to anybody >> who will solve the problem, i.e. provide a working racadm client which >> can access and manage local hardware. Of course anybody else is welcome >> to chime in. I am willing to put that in escrow with a trusted member of >> the community. Please let me know what to do. >> >> Many thanks! >> -- >> PG >> >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-amd64@freebsd.org Sun Apr 29 14:28:18 2018 Return-Path: Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 865E9FAE2C3; Sun, 29 Apr 2018 14:28:18 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: from knopi.disroot.org (knopi.disroot.org [178.21.23.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 215C27DD49; Sun, 29 Apr 2018 14:28:17 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id 1FD0629661; Sun, 29 Apr 2018 16:28:10 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1525012090; bh=3da/vyZVt3DoKosDOv8yNZ6N2ytCYsoGiadblrQPqhM=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=i18h2DNm4PMch6WX8jyjHltzhOLrVSMsmvkjM0wzWb5OiBLHwVDCnsA6YEy32mHJf oYraOcjoSVsaFkXcHFP97P0i5M1sSN8F1tW50U8fumRE9dsG3maEwHas3TAemmh4Bu +DOBnrCbL0+lUyKEgeksNfAt48DST/MEqY1IGQ+YgoDx9vfdThxeKSCW2JNmhlqT6T EKi4DdqFXDT5H13FP+gynguHOXjV9MNt+eM4yUAe261Tp4CxdsyyG7l2Nw0Wq7Cc78 PVnM7FBgGwEYAQ3rcyeexKMy5tODqvQMLNJaE/nNLZ6AhGsjRN8A8+q6ThL+8tXlKs LAq4FrDzFKcJw== X-Virus-Scanned: Debian amavisd-new at disroot.org Received: from knopi.disroot.org ([127.0.0.1]) by localhost (mail01.disroot.lan [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F5xE5zeMqGGP; Sun, 29 Apr 2018 16:28:08 +0200 (CEST) Subject: Re: Can we please finally solve Dell's racadm for FreeBSD? Advice needed DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1525012088; bh=3da/vyZVt3DoKosDOv8yNZ6N2ytCYsoGiadblrQPqhM=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=GMexQlyDWAW7/Etoi0xRaOF/O2uTgBmQEqwCbZvR2qG5Ub5J3aJjC1A4D9T08Lr8Z v2hEqLgeoe9I7mPNLwHiCbRvmmzpOiJP3dqU3Cb83DK1zxXLUa25UNBW+YNH7je4k1 w8GED1FLBt3r5inWfl12mHzyfzBLEre5YvLFf/OYl/Vq4yEXz8OYF6C9gaqDlEucj5 RZWs9Ny7Plu7zqUOOy6avq8XQy30WPlskmo7l2aYkCrW54OhJFopPPqbzM9Q0aBgQ6 NJLQGqVKhjdbFgE8C3sxomWOQIAqC4n/EQLOSQ2JTef2bG/2poOzIAXFGowZwQvivX uqwggiOrBTHtg== To: xxjack12xx@gmail.com Cc: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org References: <5eca3020-4b9c-dd43-8cf0-066d63a92521@disroot.org> From: "Peter G." Message-ID: Date: Sun, 29 Apr 2018 16:28:06 +0200 Mime-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 14:28:18 -0000 On 29/04/2018 05:08, Jack L. wrote: > I manage a variety of Dell servers running FreeBSD, only 610 and 1950s > work with racadm but everything that can be done with racadm can also > be done with ipmitool. I just use ipmitool to get around instead of > their proprietary racadm stuff. What functionality do you need from > racadm and maybe I can give you an ipmitool equivalent? It seems I may missed the ipmi angle altogether assuming it was only remote. Only now following Dan's comments I am realizing how racadm works talking to local hardware. You mean using this impi(4) as a local device and talking to it via local tool allowing coms with the device? Oh, that would do nicely. I need this for scripting mostly, e.g. monitoring what the intrusion sensor shows. Can you please describe your setup? What other kernel modules and 3rd party software do you employ? Any tricks with device.hints are needed? I have a small R220 at hand for testing, but it's lacking impi(4) altogether. Will have to rebuild. -- PG From owner-freebsd-amd64@freebsd.org Mon Apr 30 19:28:29 2018 Return-Path: Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 209A7FB4704; Mon, 30 Apr 2018 19:28:29 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8E4A970016; Mon, 30 Apr 2018 19:28:28 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: by mail-wr0-x230.google.com with SMTP id p18-v6so9059479wrm.1; Mon, 30 Apr 2018 12:28:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lqDxgS6LEk2217+ZmszifI7YY3uRNOnfBe7WmYQaJKI=; b=JOSqI70zsQ0pwHwXGhEitI5bfGqQ7GuVqAhuVn63R8Dp8zeGNpQgYVopytOYcbH0jw YccdD89CZxNGDp93K+UF6U7TgFtq+t7TzT93Noo9pLfI8O7Amf9L6ShL08EP6kNfyEA9 pmrl/NeZRrP9/xK4EzHxwM60AYOnue18n1LqU7Azlwc4R8QY8smRxkKrPS6g321igT4u rzkLp4xJyst/bvjwRenwbBymy1NfaS2NTop2CHSxyEQuLR5heTU+DV3gNzt6Kt32yKLW unm0eiVB6QFk4T26sIHNYWSFQg6xqUdGrwV9HeE7jsZlpuQY68uNkElAXTzGJa+Q/h7q PUiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lqDxgS6LEk2217+ZmszifI7YY3uRNOnfBe7WmYQaJKI=; b=pKq6N0zhDzJFj/TWUmRzwxUBja+tLzAEnCnBRh+ictAmRo5iZKeNw1OaWWW4cpECWf S/+txNlFmO5WQw8jcsXjouxbc7Gk/+PC9nANNM7yWwa22oQr9SNsVbUa8s6QggBvJEID G+NBXODjrTpulObKUkkXIiDrtXviah79MBZkZxqLcMVQVzScqFiSB+InsPSwa+VRJXp7 PYrQENbom8tPetGGwV+p0oi4J1FsuOekABc+GPs3AKRrurG+iofvc4S/5IEgFajrnQj6 NjbBMkWxGJLbyPn2W5MoPHVAtS6HLiUr1S8yZ/aFVYg6ZMrxXJM4QFcTUHuKCpgdQ+Nl 0NLw== X-Gm-Message-State: ALQs6tCIwdR5qIZGZZzD6hVdYFaz5QfqvUH5dKkX8uKMc2Zy519RJtwX lUXLyR0b2h+J1NhTmx4hzmupTHZI/x1gIdVt3craOw== X-Google-Smtp-Source: AB8JxZr5TXGCcVrW4LJzyTPWE7CoZc6HtdWozEAZn22h0wyUx4N/0aV3CDNhdNqQih9WeL44lm29UZEO4jktROYPwMc= X-Received: by 2002:adf:c4a6:: with SMTP id m35-v6mr9705429wrf.103.1525116507333; Mon, 30 Apr 2018 12:28:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.171.232 with HTTP; Mon, 30 Apr 2018 12:27:46 -0700 (PDT) In-Reply-To: References: <5eca3020-4b9c-dd43-8cf0-066d63a92521@disroot.org> From: "Jack L." Date: Mon, 30 Apr 2018 12:27:46 -0700 Message-ID: Subject: Re: Can we please finally solve Dell's racadm for FreeBSD? Advice needed To: "Peter G." Cc: FreeBSD Hackers , freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2018 19:28:29 -0000 I have device ipmi in my kernel config (or you can just kldload ipmi). Install ipmitool, and most of the dell cmds are the usual ipmi commands. Some commands might have to be sent via raw or delloem and you can't soft reset the drac, only hard reset it via the tool. On Sun, Apr 29, 2018 at 7:28 AM, Peter G. wrote: > On 29/04/2018 05:08, Jack L. wrote: >> I manage a variety of Dell servers running FreeBSD, only 610 and 1950s >> work with racadm but everything that can be done with racadm can also >> be done with ipmitool. I just use ipmitool to get around instead of >> their proprietary racadm stuff. What functionality do you need from >> racadm and maybe I can give you an ipmitool equivalent? > > It seems I may missed the ipmi angle altogether assuming it was only > remote. Only now following Dan's comments I am realizing how racadm > works talking to local hardware. > > You mean using this impi(4) as a local device and talking to it via > local tool allowing coms with the device? Oh, that would do nicely. I > need this for scripting mostly, e.g. monitoring what the intrusion > sensor shows. > > Can you please describe your setup? What other kernel modules and 3rd > party software do you employ? Any tricks with device.hints are needed? I > have a small R220 at hand for testing, but it's lacking impi(4) > altogether. Will have to rebuild. > > -- > PG