Specifications
QSSC-S4R Technical Product Specification BMC Messaging Interfaces
293
25.8.2.2.2 Hex-ASCII Commands
The
BMC
suppor
t
s
t
he
I
PM
I
binary
commands
speci
f
ied
in
t
his
documen
t.
The
BMC
suppor
t
s
t
he
privilege
level
scheme
f
or
t
erminal
mode
t
ex
t
commands
.
25.8.2.3 Bridging
The
BMC
suppor
t
s
t
he
op
t
ional
bridging
f
unc
t
ionali
t
y
described
in
t
he
I
n
t
elligen
t
Pla
tf
orm
Managemen
t
I
n
t
er
f
ace
Speci
f
ica
t
ion
Second
Genera
t
ion
v2
.
0
.
25.8.2.4 Invalid Passwords
If
t
hree
successive
invalid
Ac
t
iva
t
e
Session
commands
are
received
on
t
he
EMP in
t
er
f
ace
,
t
he
BMC
delays
30
seconds
be
f
ore
accep
t
ing
ano
t
her
Ac
t
iva
t
e
Session command
.
25.9 LAN Interface
The
BMC
implemen
t
s
bo
t
h
t
he
I
PM
I
1
.
5
and
I
PM
I
2
.
0
messaging
models
.
These provide
ou
t
-o
f
-band
local
area
ne
t
work
(LAN)
communica
t
ion
be
t
ween
t
he
BMC
and
t
he
ne
t
work
.
See
t
he
I
n
t
elligen
t
Pla
tf
orm
Managemen
t
I
n
t
er
f
ace
Speci
f
ica
t
ion
Second
Genera
t
ion v2
.
0
f
or
de
t
ails
abou
t
t
he
I
PM
I
-
over-LAN
pro
t
ocol
.
Run-
t
ime
de
t
ermina
t
ion
o
f
LAN
channel
capabili
t
ies
can
be
de
t
ermined
bo
t
h
by s
t
andard
I
PM
I
de
f
ined
mechanisms
.
25.9.1 IPMI 1.5 Messaging
The
communica
t
ion
pro
t
ocol
packe
t
f
orma
t
consis
t
s
o
f
I
PM
I
reques
t
s
and
responses encapsula
t
ed
in
an
I
PM
I
session
wrapper
f
or
au
t
hen
t
ica
t
ion
,
and
wrapped
in
an RMCP
packe
t,
which
is
wrapped
in
an
I
P
/
UDP
packe
t.
Al
t
hough
au
t
hen
t
ica
t
ion
is provided
,
no
encryp
t
ion
is
provided
,
so
adminis
t
ra
t
ing
some
se
tt
ings
,
such
as
user passwords
,
t
hrough
t
his
in
t
er
f
ace
is
no
t
advised
.
Session
es
t
ablishmen
t
commands
are
I
PM
I
commands
t
ha
t
do
no
t
require au
t
hen
t
ica
t
ion
or
an
associa
t
ed
session
.
The
BMC
suppor
t
s
t
he
f
ollowing
au
t
hen
t
ica
t
ion
t
ypes
over
t
he
LAN
in
t
er
f
ace
.
x
None
(no
au
t
hen
t
ica
t
ion)
x
S
t
raigh
t
password
/
key
x
MD5
25.9.2 IPMI 2.0 Messaging
I
PM
I
2
.
0
messaging
is
buil
t
over
RMCP+
and
has
a
di
ff
eren
t
session
es
t
ablishmen
t
pro
t
ocol
.
The
session
commands
are
de
f
ined
by
RMCP+
and
implemen
t
ed
a
t
t
he RMCP+
level
,
no
t
I
PM
I
commands
.
Au
t
hen
t
ica
t
ion
is
implemen
t
ed
a
t
t
he
RMCP+ level
.
RMCP+
provides
link
payload
encryp
t
ion
,
so
i
t
is
possible
t
o
communica
t
e priva
t
e
/
sensi
t
ive
da
t
a
(con
f
iden
t
iali
t
y)
.
The
BMC
suppor
t
s
t
he
f
ollowing
cipher
sui
t
es
:
Table 198. Supported RMCP+ Cipher Suites
I
D
Au
t
h
e
n
t
ic
a
t
i
on
I
n
t
e
g
r
i
t
y
C
on
f
i
d
e
n
t
i
a
li
t
y
0
1
RAKP-none
None
None
1
RAKP-HMAC-SHA1
None
None
2
RAKP-HMAC-SHA1
HMAC-SHA1-96
None
3
RAKP-HMAC-SHA1
HMAC-SHA1-96
AES-CBC-128
6
RAKP-HMAC-MD5
None
None
7
RAKP-HMAC-MD5
HMAC-MD5-128
None
8
RAKP-HMAC-MD5
HMAC-MD5-128
AES-CBC-128
11
RAKP-HMAC-MD5
MD5-128
None
12
RAKP-HMAC-MD5
MD5-128
AES-CBC-128
Note:
1.
Cipher
suite
0
defaults
to
callback
privilege
for
security
purposes.
This
may
be
changed
by any
administrator.
For
user
au
t
hen
t
ica
t
ion
,
t
he
BMC
can
be
con
f
igured
wi
t
h
‘null’
user
names
,
whereby password
/
key
lookup
is
done
based
on
‘privilege
level
only’
,
or
wi
t
h
non-null
user names
,
where
t
he
key
lookup
f
or
t
he
session
is
de
t
ermined
by
user
name
.