From owner-freebsd-hackers@freebsd.org Mon Apr 30 19:28:29 2018 Return-Path: Delivered-To: freebsd-hackers@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-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD 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