summaryrefslogtreecommitdiff
path: root/doc/UserGuide
diff options
context:
space:
mode:
Diffstat (limited to 'doc/UserGuide')
-rw-r--r--doc/UserGuide18
1 files changed, 10 insertions, 8 deletions
diff --git a/doc/UserGuide b/doc/UserGuide
index 8205c46..6f46cd7 100644
--- a/doc/UserGuide
+++ b/doc/UserGuide
@@ -1,6 +1,6 @@
IPMIUTIL USER GUIDE
- VERSION 3.0.0
+ VERSION 3.0.1
An easy-to-use IPMI server management utility
@@ -191,14 +191,15 @@ Key Strengths = supports any IPMI server platforms,
detection, portability,
incorporates fixes and new features quickly
Target Market = Administrators, Developers, and OEMs
-OS Support = Linux, Windows, Solaris, and FreeBSD
- (supports Windows natively for remote or local interface)
+OS Support = Linux, Windows, Solaris, FreeBSD, and MacOSX
+ (supports Windows natively for local or remote interface)
License = BSD
Drivers = For Linux: openipmi, imb, valinux ipmikcs, lan, lanplus,
- landesk, and driverless direct KCS & SSIF
+ landesk, and driverless direct KCS or SSIF
For Windows: Intel IMB and Microsoft IPMI drivers
For Solaris: bmc
For FreeBSD: openipmi, driverless KCS or SSIF
+ For MacOSX: remote only
LEDs = Show/set ATCA LEDs, set identify LED, Intel Telco Alarm LEDs
health = show overall health and product information
discovery = find all IPMI LAN servers on a given subnet
@@ -4764,16 +4765,17 @@ ipmiutil lan, completed successfully
----------------------------------------------------------------
Suppose there are a number of IPMI servers that need to have their
-BMC LAN interface configured. Shell access to the servers
+IPMI LAN interface configured. Shell access to the servers
(via ssh or similar) is assumed.
-BMC LAN, Simple case, password is not changed:
+IPMI LAN, Simple case, password is not changed, default user:
[ssh connection]
# ipmiutil lan -e
[ssh exit]
-BMC LAN, Complex case, assuming that a password needs to be set and
+IPMI LAN, Complex case, assuming that a password needs to be set and
that the session text (or script) must encrypt the password.
+Assumes that we are setting a non-default user named 'admin' below.
So, using the gnupg.org utilities with public/private keys
would look something like this:
[ Set up list (or db) of encrypted passwords & key by nodename.
@@ -4784,7 +4786,7 @@ would look something like this:
# gpg --import mykey.file
# mynode=`uname -n`
# my_enc_psw=`grep $mynode mylist.file |cut -f2`
-# ipmiutil lan -e -p `gpg --decrypt $my_enc_psw`
+# ipmiutil lan -e -u admin -p `gpg --decrypt $my_enc_psw`
[ssh exit]
----------------------------------------------------------------