As far as I can tell, the Sun workarounds are generic in ELOM and ILOM,
and haven't been fixed in the current versions.  I have x4100 with ILOM
1.0 and 2.0, x2200M2 with ELOM 2.0, and x4200m2 and x4500 with ILOM 2.0.
All seem to need the workarounds, and have the latest firmware apart
from ILOM 1.0.

I think this change to the text makes it clearer, and it's worth keeping
the Sun bits together.

By the way, ELOM is EOLed -- we're stuck with its problems on most of
our kit, sigh -- but there is an ILOM 3 in the works; perhaps that fixes
the bugs, and I'll try to check if other people here get newer kit with
it on.

2009-06-09  Dave Love  <f...@gnu.org>

	* common/man/manpage-common-workaround-text.man: Tweak the Sun
	stuff.

*** manpage-common-workaround-text.man	08 Apr 2009 21:47:05 +0100	1.6
--- manpage-common-workaround-text.man	09 Jun 2009 14:40:00 +0100	
***************
*** 41,54 ****
  "username invalid" or "k_g invalid" errors to occur.  In order to work
  around this issue, the "authcap" workaround must be specified.
  .LP
! Sun ILOM 2.0: The session sequence numbers returned for IPMI 1.5
! sessions are the wrong endian on some systems running ILOM 2.0.  The
  incorrect endian depends on the service processor endianness.  This
  will likely cause "session timeout" errors to occur.  In order to work
! around this issue, the "endianseq" workaround must be specified.  This
! problem is reported to be fixed in a later release.
  .LP
! Sun Fire X4150/X4450: The motherboard does not properly report
  username capabilities.  This will likely cause "username invalid"
  errors to occur.  In order to work around this issue, the "authcap"
  workaround must be specified.
--- 41,63 ----
  "username invalid" or "k_g invalid" errors to occur.  In order to work
  around this issue, the "authcap" workaround must be specified.
  .LP
! Sun ILOM 1.0 and 2.0: The session sequence numbers returned for IPMI 1.5
! sessions are the wrong endian on some systems running ILOM 1.0 and 2.0
! (at least up to 2.0.2.5).  The
  incorrect endian depends on the service processor endianness.  This
  will likely cause "session timeout" errors to occur.  In order to work
! around this issue, the "endianseq" workaround must be specified.
! .\" This problem is reported to be fixed in a later release.
  .LP
! Sun ILOM (at least up to 2.0.2.5) with IPMI 2.0:
! There are several Sun IPMI 2.0 bugs.  These
! problems may cause "password invalid" or "bmc error" errors to occur.
! They can be worked around by specifying the "sun20" workaround.  The
! workarounds include handling invalid lengthed hash keys and invalid
! cipher suite records.
! .LP
! Sun ELOM (seen on at least X2200/X4150/X4450): The motherboard does
! not properly report
  username capabilities.  This will likely cause "username invalid"
  errors to occur.  In order to work around this issue, the "authcap"
  workaround must be specified.
***************
*** 68,79 ****
  cause "password invalid" errors to occur.  These compliance bugs are
  confirmed to be fixed on newer firmware.
  .LP
- Sun Fire 4100 with ILOM: There are several Sun IPMI 2.0 bugs.  These
- problems may cause "password invalid" or "bmc error" errors to occur.
- They can be worked around by specifying the "sun20" workaround.  The
- workarounds include handling invalid lengthed hash keys and invalid
- cipher suite records.
- .LP
  Inventec 5441: The privilege level sent during the Open Session stage
  of an IPMI 2.0 connection is used for hashing keys instead of the
  privilege level sent during the RAKP1 connection stage.  This may
--- 77,82 ----
_______________________________________________
Freeipmi-devel mailing list
Freeipmi-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/freeipmi-devel

Reply via email to