Discussion:
[Ipmitool-devel] SOL thru port forwarding
Martin Hamant
2011-12-30 11:34:12 UTC
Permalink
Hi !!!

I have a BMC configured with a local IP adress (192.168.X.X) listening
on default port (623).

I want to access it from the outside world. For that I have set a port
forwarding rules on the router to the port 623 of this local IP.

every ipmitool commands works well BUT not SOL.

# ipmitool -I lanplus -p (external_port) -U (...) -P (...) -H (external
IP) sol activate

I get the message: "Error: BMC requests SOL session on different port"

I'm not sure to understand exactly what it means ? What I need to do to
make this work ?

Thanks !!
Martin Hamant
2011-12-30 12:27:25 UTC
Permalink
Hi Hank,

Thanks for you reply, but I'm still not sure we speak about the same
thing :/

I also have discovered in ipmi_sol.c / ipmitool :

(...)
/* NOTE: the spec does allow for SOL traffic to be sent on
* a different port. we do not yet support that feature. */
if (intf->session->sol_data.port != intf->session->port)
{
/* try byteswapping port in case BMC sent it incorrectly */
uint16_t portswap = BSWAP_16(intf->session->sol_data.port);

if (portswap == intf->session->port) {
intf->session->sol_data.port = portswap;
}
else {
lprintf(LOG_ERR, "Error: BMC requests SOL session on
different port");
return -1;
}
}
(...)

the comment seems to explains why I get this message...
The RMCP server can use any UDP port it wants to for a SOL session.
Some implementations use port 623. If you have more than two SOL
sessions open on a single RMCP server at least one will be on a port
other than 623. Each of the SOL sessions may be encrypted differently
using separate cipher suites(or none at all).
Hank
JBlade
Hi !!!
I have a BMC configured with a local IP adress (192.168.X.X) listening
on default port (623).
I want to access it from the outside world. For that I have set a port
forwarding rules on the router to the port 623 of this local IP.
every ipmitool commands works well BUT not SOL.
# ipmitool -I lanplus -p (external_port) -U (...) -P (...) -H (external
IP) sol activate
I get the message: "Error: BMC requests SOL session on different port"
I'm not sure to understand exactly what it means ? What I need to do to
make this work ?
Thanks !!
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a
complex
infrastructure or vast IT resources to deliver seamless, secure
access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI
infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Al Chu
2011-12-30 15:41:44 UTC
Permalink
I think this is what Hank is talking about. SOL connects at port 623,
but it may communicate over a different port later in the session.

However, ipmitool doesn't support communication over any port other than
623. So if SOL works for you w/o port forwarding, then this isn't your
issue.

Al
Post by Martin Hamant
Hi Hank,
Thanks for you reply, but I'm still not sure we speak about the same
thing :/
(...)
/* NOTE: the spec does allow for SOL traffic to be sent on
* a different port. we do not yet support that feature. */
if (intf->session->sol_data.port != intf->session->port)
{
/* try byteswapping port in case BMC sent it incorrectly */
uint16_t portswap = BSWAP_16(intf->session->sol_data.port);
if (portswap == intf->session->port) {
intf->session->sol_data.port = portswap;
}
else {
lprintf(LOG_ERR, "Error: BMC requests SOL session on
different port");
return -1;
}
}
(...)
the comment seems to explains why I get this message...
The RMCP server can use any UDP port it wants to for a SOL session.
Some implementations use port 623. If you have more than two SOL
sessions open on a single RMCP server at least one will be on a port
other than 623. Each of the SOL sessions may be encrypted
differently using separate cipher suites(or none at all).
Hank
JBlade
Hi !!!
I have a BMC configured with a local IP adress (192.168.X.X) listening
on default port (623).
I want to access it from the outside world. For that I have set a port
forwarding rules on the router to the port 623 of this local IP.
every ipmitool commands works well BUT not SOL.
# ipmitool -I lanplus -p (external_port) -U (...) -P (...) -H (external
IP) sol activate
I get the message: "Error: BMC requests SOL session on different port"
I'm not sure to understand exactly what it means ? What I need to do to
make this work ?
Thanks !!
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't
need a complex
infrastructure or vast IT resources to deliver seamless,
secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI
infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
--
Albert Chu
***@llnl.gov
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory
Martin Hamant
2011-12-30 16:06:18 UTC
Permalink
I'm lost.
Let me formulate what I understand:

ipmitool is a tool to connect to any (most?) baseboard management
controller, to get/set system settings.
ipmitool with default settings connects on port 623/UDP

This was the easiest part :D And to this point all is going well WITH or
without PNAT (I can use "chassis" commands etc)

now SOL. Something different is happening when ipmitool ask a SOL
session. (thru lanplus interface)

Do I have to understand that ipmitool "sol" arg simply doesn't take the
given command line "-p <port>" arg into account ?


I tried to read IPMI specification but I have to say this is a little
complex to eat it like this, at least for me :)

If someone can briefly explain me what's happen when asking a SOL
session thru IPMI (what is "this" trying to connect to "that", on which
(random) port)


Maybe I could find a workaround then (other than SOLProxy ^^ ) to get to
my BMC interface / console redirection from the internet

Thanks again !!

-
Post by Al Chu
I think this is what Hank is talking about. SOL connects at port 623,
but it may communicate over a different port later in the session.
However, ipmitool doesn't support communication over any port other than
623. So if SOL works for you w/o port forwarding, then this isn't your
issue.
Al
Post by Martin Hamant
Hi Hank,
Thanks for you reply, but I'm still not sure we speak about the same
thing :/
(...)
/* NOTE: the spec does allow for SOL traffic to be sent on
* a different port. we do not yet support that feature. */
if (intf->session->sol_data.port != intf->session->port)
{
/* try byteswapping port in case BMC sent it incorrectly */
uint16_t portswap = BSWAP_16(intf->session->sol_data.port);
if (portswap == intf->session->port) {
intf->session->sol_data.port = portswap;
}
else {
lprintf(LOG_ERR, "Error: BMC requests SOL session on
different port");
return -1;
}
}
(...)
the comment seems to explains why I get this message...
The RMCP server can use any UDP port it wants to for a SOL session.
Some implementations use port 623. If you have more than two SOL
sessions open on a single RMCP server at least one will be on a port
other than 623. Each of the SOL sessions may be encrypted
differently using separate cipher suites(or none at all).
Hank
JBlade
Hi !!!
I have a BMC configured with a local IP adress (192.168.X.X)
listening
on default port (623).
I want to access it from the outside world. For that I have
set a port
forwarding rules on the router to the port 623 of this local IP.
every ipmitool commands works well BUT not SOL.
# ipmitool -I lanplus -p (external_port) -U (...) -P (...)
-H (external
IP) sol activate
I get the message: "Error: BMC requests SOL session on
different port"
I'm not sure to understand exactly what it means ? What I
need to do to
make this work ?
Thanks !!
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't
need a complex
infrastructure or vast IT resources to deliver seamless,
secure access to
virtual desktops. With this all-in-one solution, easily
deploy virtual
desktops for less than the cost of PCs and save 60% on VDI
infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Andy Cress
2011-12-30 18:47:56 UTC
Permalink
Martin,

Have you established that SOL works locally (without the port forwarding)?
This would rule out a firmware bug or firmware c
Al Chu
2011-12-31 16:26:19 UTC
Permalink
Hi Martin,

Sorry, it can be confusing to new folks.

With 99% of IPMI over LAN, the communication is always through port 623.

With SOL, it can be slightly different. The series of events is:

1. Client connects to server/BMC over port 623.
2. Client authenticates w/ server/BMC.
3. server/BMC informs client what port to communicate for SOL.
4a. If server/BMC tells client to use port 623, SOL session continues
under the current connection/session
4b. If server/BMC tells client to use port XXX, client should
disconnect and reconnect under port XXX.

To my knowledge, the disconnect/reconnect under non-port-623 is not
supported in ipmitool. If this is happening with your motherboard, it
would explain your problem.

Al
Post by Martin Hamant
I'm lost.
ipmitool is a tool to connect to any (most?) baseboard management
controller, to get/set system settings.
ipmitool with default settings connects on port 623/UDP
This was the easiest part :D And to this point all is going well WITH or
without PNAT (I can use "chassis" commands etc)
now SOL. Something different is happening when ipmitool ask a SOL
session. (thru lanplus interface)
Do I have to understand that ipmitool "sol" arg simply doesn't take the
given command line "-p <port>" arg into account ?
I tried to read IPMI specification but I have to say this is a little
complex to eat it like this, at least for me :)
If someone can briefly explain me what's happen when asking a SOL
session thru IPMI (what is "this" trying to connect to "that", on which
(random) port)
Maybe I could find a workaround then (other than SOLProxy ^^ ) to get to
my BMC interface / console redirection from the internet
Thanks again !!
-
Post by Al Chu
I think this is what Hank is talking about. SOL connects at port 623,
but it may communicate over a different port later in the session.
However, ipmitool doesn't support communication over any port other than
623. So if SOL works for you w/o port forwarding, then this isn't your
issue.
Al
Post by Martin Hamant
Hi Hank,
Thanks for you reply, but I'm still not sure we speak about the same
thing :/
(...)
/* NOTE: the spec does allow for SOL traffic to be sent on
* a different port. we do not yet support that feature. */
if (intf->session->sol_data.port != intf->session->port)
{
/* try byteswapping port in case BMC sent it incorrectly */
uint16_t portswap = BSWAP_16(intf->session->sol_data.port);
if (portswap == intf->session->port) {
intf->session->sol_data.port = portswap;
}
else {
lprintf(LOG_ERR, "Error: BMC requests SOL session on
different port");
return -1;
}
}
(...)
the comment seems to explains why I get this message...
The RMCP server can use any UDP port it wants to for a SOL session.
Some implementations use port 623. If you have more than two SOL
sessions open on a single RMCP server at least one will be on a port
other than 623. Each of the SOL sessions may be encrypted
differently using separate cipher suites(or none at all).
Hank
JBlade
Hi !!!
I have a BMC configured with a local IP adress (192.168.X.X)
listening
on default port (623).
I want to access it from the outside world. For that I have
set a port
forwarding rules on the router to the port 623 of this local IP.
every ipmitool commands works well BUT not SOL.
# ipmitool -I lanplus -p (external_port) -U (...) -P (...)
-H (external
IP) sol activate
I get the message: "Error: BMC requests SOL session on
different port"
I'm not sure to understand exactly what it means ? What I
need to do to
make this work ?
Thanks !!
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't
need a complex
infrastructure or vast IT resources to deliver seamless,
secure access to
virtual desktops. With this all-in-one solution, easily
deploy virtual
desktops for less than the cost of PCs and save 60% on VDI
infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
--
Albert Chu
***@llnl.gov
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory
Hank Bruning
2012-01-03 03:00:45 UTC
Permalink
Hi Martin,

I think part of the confusion is that the code snippet you provided does
not implement the IPMI standard. The line
lprintf(LOG_ERR, "Error: BMC requests SOL session on different port");
is not an IPMI error and the BMC is preforming it's intended function. IPMI
does allow the different port. Infact that line should be replaced by a
huge amount of logic. IPMI allows the allocation of the SOL session on any
existing RMCP session(IPMI 2.0, Section 24.1 Activate Payload Command,
page 330. All references in this email are to the IPMI 2.0 version dated
June 12, 2009) or the creation of a new RMCP session.
Since IPMITool does not track multiple existing RMCP sessions it appears
that it just prints the error.

Al Chu provided a very concise and correct overview of the SOL session
creation.

If you want some more detail here is a web page but there are two things to
note.
1) This is a programming reference page for a Java library. Since you are
looking at IPMItool internals it not much of a stretch. The links that
begin with "IPMI 2.0" are especially useful. All our software has links
back to the IPMI spec to the page number of relevant decisions.
2) Full disclosure. The web page is for a library called Hemi that my
company provides which replaces IPMItool for high end system managers
implemented in Java.

This is the page
http://www.jblade.com:8080/jbpublic/products/hemi/doc/programmers/HemiSol.html

I'm not sure there is a solution to your problem but try these options to
keep the SOL session using port 623

1) Make sure that Table 26-5, SOL Configuration Parameters, parameter 2,
bits 6 and 7 are not set.
2) Make sure that the Table 24-2 Activate Payload Command page 332 sent by
IPMITool does not have bits in field 3:6, byte 1, bits 6 and 7 set.

Another approach. This may not meet your needs but abandon the NAT as a
method of security and change to use IEEE 802.1q VLAN as documented in IPMI
2.0 Table 23-4, LAN Configuration Parameters, parameter #25 and send the
VLAN to an encryption/decryption device before forwarding the UDP stream to
the unsecured network.

Hank
JBlade
Post by Al Chu
Hi Martin,
Sorry, it can be confusing to new folks.
With 99% of IPMI over LAN, the communication is always through port 623.
1. Client connects to server/BMC over port 623.
2. Client authenticates w/ server/BMC.
3. server/BMC informs client what port to communicate for SOL.
4a. If server/BMC tells client to use port 623, SOL session continues
under the current connection/session
4b. If server/BMC tells client to use port XXX, client should
disconnect and reconnect under port XXX.
To my knowledge, the disconnect/reconnect under non-port-623 is not
supported in ipmitool. If this is happening with your motherboard, it
would explain your problem.
Al
Post by Martin Hamant
I'm lost.
ipmitool is a tool to connect to any (most?) baseboard management
controller, to get/set system settings.
ipmitool with default settings connects on port 623/UDP
This was the easiest part :D And to this point all is going well WITH or
without PNAT (I can use "chassis" commands etc)
now SOL. Something different is happening when ipmitool ask a SOL
session. (thru lanplus interface)
Do I have to understand that ipmitool "sol" arg simply doesn't take the
given command line "-p <port>" arg into account ?
I tried to read IPMI specification but I have to say this is a little
complex to eat it like this, at least for me :)
If someone can briefly explain me what's happen when asking a SOL
session thru IPMI (what is "this" trying to connect to "that", on which
(random) port)
Maybe I could find a workaround then (other than SOLProxy ^^ ) to get to
my BMC interface / console redirection from the internet
Thanks again !!
-
Post by Al Chu
I think this is what Hank is talking about. SOL connects at port 623,
but it may communicate over a different port later in the session.
However, ipmitool doesn't support communication over any port other
than
Post by Martin Hamant
Post by Al Chu
623. So if SOL works for you w/o port forwarding, then this isn't your
issue.
Al
Post by Martin Hamant
Hi Hank,
Thanks for you reply, but I'm still not sure we speak about the same
thing :/
(...)
/* NOTE: the spec does allow for SOL traffic to be sent on
* a different port. we do not yet support that feature. */
if (intf->session->sol_data.port != intf->session->port)
{
/* try byteswapping port in case BMC sent it incorrectly */
uint16_t portswap = BSWAP_16(intf->session->sol_data.port);
if (portswap == intf->session->port) {
intf->session->sol_data.port = portswap;
}
else {
lprintf(LOG_ERR, "Error: BMC requests SOL session on
different port");
return -1;
}
}
(...)
the comment seems to explains why I get this message...
The RMCP server can use any UDP port it wants to for a SOL session.
Some implementations use port 623. If you have more than two SOL
sessions open on a single RMCP server at least one will be on a port
other than 623. Each of the SOL sessions may be encrypted
differently using separate cipher suites(or none at all).
Hank
JBlade
Hi !!!
I have a BMC configured with a local IP adress (192.168.X.X)
listening
on default port (623).
I want to access it from the outside world. For that I have
set a port
forwarding rules on the router to the port 623 of this local
IP.
every ipmitool commands works well BUT not SOL.
# ipmitool -I lanplus -p (external_port) -U (...) -P (...)
-H (external
IP) sol activate
I get the message: "Error: BMC requests SOL session on
different port"
I'm not sure to understand exactly what it means ? What I
need to do to
make this work ?
Thanks !!
------------------------------------------------------------------------------
Post by Martin Hamant
Post by Al Chu
Post by Martin Hamant
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't
need a complex
infrastructure or vast IT resources to deliver seamless,
secure access to
virtual desktops. With this all-in-one solution, easily
deploy virtual
desktops for less than the cost of PCs and save 60% on VDI
infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
--
Albert Chu
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory
Martin Hamant
2012-01-13 14:00:48 UTC
Permalink
Hi and thanks for all the infos.
I have to add that I am not a "real" dev, in the way that my
understanding is somehow "limited" for now.

It makes me think of FTP active-mode relative tortuous mechanisms
........ compared to the initial "simple" need which is "I want to
transfer files!" :D
There are reasons for this but it's always a little frustrating !!

I finished complaining :D

we haven't choosed NAT for security purpose, but because our customer
were too short in public IPs , etc
And so... a bunch of port forwarding rules everywhere.
For each Dell server, there is a BMC interface configured with static
private IP. (means the server side is somehow "hardcoded", I can't act
on server behavior).

Then I was asked if there was a way to not bounce/log on servers within
the local network to get to any other server console with ipmitool. So I
suggested the "NAT" solution (and pointed to security issues it implies. )

I thank you for the suggestions and documentation pointers btw. I have
to find the most trivial solution :D

About what you suggested:

1) Make sure that Table 26-5, SOL Configuration Parameters, parameter 2,
bits 6 and 7 are not set.
2) Make sure that the Table 24-2 Activate Payload Command page 332 sent
by IPMITool does not have bits in field 3:6, byte 1, bits 6 and 7 set.

How do I do that ?
If there is no simple solution to that
"SOL-thru-DellBMC-farm-behind-the-NAT-router", I will simply explain
that to my customer.

Thanks !!
Post by Al Chu
Hi Martin,
I think part of the confusion is that the code snippet you provided
does not implement the IPMI standard. The line
lprintf(LOG_ERR, "Error: BMC requests SOL session on different port");
is not an IPMI error and the BMC is preforming it's intended function.
IPMI does allow the different port. Infact that line should be
replaced by a huge amount of logic. IPMI allows the allocation of the
SOL session on any existing RMCP session(IPMI 2.0, Section 24.1
Activate Payload Command, page 330. All references in this email are
to the IPMI 2.0 version dated June 12, 2009) or the creation of a new
RMCP session.
Since IPMITool does not track multiple existing RMCP sessions it
appears that it just prints the error.
Al Chu provided a very concise and correct overview of the SOL session
creation.
If you want some more detail here is a web page but there are two
things to note.
1) This is a programming reference page for a Java library. Since you
are looking at IPMItool internals it not much of a stretch. The links
that begin with "IPMI 2.0" are especially useful. All our software has
links back to the IPMI spec to the page number of relevant decisions.
2) Full disclosure. The web page is for a library called Hemi that my
company provides which replaces IPMItool for high end system managers
implemented in Java.
This is the page
http://www.jblade.com:8080/jbpublic/products/hemi/doc/programmers/HemiSol.html
I'm not sure there is a solution to your problem but try these options
to keep the SOL session using port 623
1) Make sure that Table 26-5, SOL Configuration Parameters, parameter
2, bits 6 and 7 are not set.
2) Make sure that the Table 24-2 Activate Payload Command page 332
sent by IPMITool does not have bits in field 3:6, byte 1, bits 6 and
7 set.
Another approach. This may not meet your needs but abandon the NAT as
a method of security and change to use IEEE 802.1q VLAN as documented
in IPMI 2.0 Table 23-4, LAN Configuration Parameters, parameter #25
and send the VLAN to an encryption/decryption device before forwarding
the UDP stream to the unsecured network.
Hank
JBlade
Hi Martin,
Sorry, it can be confusing to new folks.
With 99% of IPMI over LAN, the communication is always through port 623.
1. Client connects to server/BMC over port 623.
2. Client authenticates w/ server/BMC.
3. server/BMC informs client what port to communicate for SOL.
4a. If server/BMC tells client to use port 623, SOL session continues
under the current connection/session
4b. If server/BMC tells client to use port XXX, client should
disconnect and reconnect under port XXX.
To my knowledge, the disconnect/reconnect under non-port-623 is not
supported in ipmitool. If this is happening with your motherboard, it
would explain your problem.
Al
Post by Martin Hamant
I'm lost.
ipmitool is a tool to connect to any (most?) baseboard management
controller, to get/set system settings.
ipmitool with default settings connects on port 623/UDP
This was the easiest part :D And to this point all is going well
WITH or
Post by Martin Hamant
without PNAT (I can use "chassis" commands etc)
now SOL. Something different is happening when ipmitool ask a SOL
session. (thru lanplus interface)
Do I have to understand that ipmitool "sol" arg simply doesn't
take the
Post by Martin Hamant
given command line "-p <port>" arg into account ?
I tried to read IPMI specification but I have to say this is a
little
Post by Martin Hamant
complex to eat it like this, at least for me :)
If someone can briefly explain me what's happen when asking a SOL
session thru IPMI (what is "this" trying to connect to "that",
on which
Post by Martin Hamant
(random) port)
Maybe I could find a workaround then (other than SOLProxy ^^ )
to get to
Post by Martin Hamant
my BMC interface / console redirection from the internet
Thanks again !!
-
Post by Al Chu
I think this is what Hank is talking about. SOL connects at
port 623,
Post by Martin Hamant
Post by Al Chu
but it may communicate over a different port later in the session.
However, ipmitool doesn't support communication over any port
other than
Post by Martin Hamant
Post by Al Chu
623. So if SOL works for you w/o port forwarding, then this
isn't your
Post by Martin Hamant
Post by Al Chu
issue.
Al
Post by Martin Hamant
Hi Hank,
Thanks for you reply, but I'm still not sure we speak about
the same
Post by Martin Hamant
Post by Al Chu
Post by Martin Hamant
thing :/
(...)
/* NOTE: the spec does allow for SOL traffic to be sent on
* a different port. we do not yet support that feature. */
if (intf->session->sol_data.port != intf->session->port)
{
/* try byteswapping port in case BMC sent it
incorrectly */
Post by Martin Hamant
Post by Al Chu
Post by Martin Hamant
uint16_t portswap =
BSWAP_16(intf->session->sol_data.port);
Post by Martin Hamant
Post by Al Chu
Post by Martin Hamant
if (portswap == intf->session->port) {
intf->session->sol_data.port = portswap;
}
else {
lprintf(LOG_ERR, "Error: BMC requests SOL session on
different port");
return -1;
}
}
(...)
the comment seems to explains why I get this message...
The RMCP server can use any UDP port it wants to for a SOL
session.
Post by Martin Hamant
Post by Al Chu
Post by Martin Hamant
Some implementations use port 623. If you have more than two SOL
sessions open on a single RMCP server at least one will be
on a port
Post by Martin Hamant
Post by Al Chu
Post by Martin Hamant
other than 623. Each of the SOL sessions may be encrypted
differently using separate cipher suites(or none at all).
Hank
JBlade
On Fri, Dec 30, 2011 at 6:34 AM, Martin
Hi !!!
I have a BMC configured with a local IP adress
(192.168.X.X)
Post by Martin Hamant
Post by Al Chu
Post by Martin Hamant
listening
on default port (623).
I want to access it from the outside world. For
that I have
Post by Martin Hamant
Post by Al Chu
Post by Martin Hamant
set a port
forwarding rules on the router to the port 623 of
this local
Post by Martin Hamant
Post by Al Chu
Post by Martin Hamant
IP.
every ipmitool commands works well BUT not SOL.
# ipmitool -I lanplus -p (external_port) -U (...)
-P (...)
Post by Martin Hamant
Post by Al Chu
Post by Martin Hamant
-H (external
IP) sol activate
I get the message: "Error: BMC requests SOL session on
different port"
I'm not sure to understand exactly what it means ?
What I
Post by Martin Hamant
Post by Al Chu
Post by Martin Hamant
need to do to
make this work ?
Thanks !!
------------------------------------------------------------------------------
Post by Martin Hamant
Post by Al Chu
Post by Martin Hamant
Ridiculously easy VDI. With Citrix VDI-in-a-Box,
you don't
Post by Martin Hamant
Post by Al Chu
Post by Martin Hamant
need a complex
infrastructure or vast IT resources to deliver
seamless,
Post by Martin Hamant
Post by Al Chu
Post by Martin Hamant
secure access to
virtual desktops. With this all-in-one solution, easily
deploy virtual
desktops for less than the cost of PCs and save 60%
on VDI
Post by Martin Hamant
Post by Al Chu
Post by Martin Hamant
infrastructure
costs. Try it free!
http://p.sf.net/sfu/Citrix-VDIinabox
Post by Martin Hamant
Post by Al Chu
Post by Martin Hamant
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
--
Albert Chu
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory
Hank Bruning
2011-12-30 12:12:26 UTC
Permalink
The RMCP server can use any UDP port it wants to for a SOL session. Some
implementations use port 623. If you have more than two SOL sessions open
on a single RMCP server at least one will be on a port other than 623. Each
of the SOL sessions may be encrypted differently using separate cipher
suites(or none at all).
Hank
JBlade
Post by Martin Hamant
Hi !!!
I have a BMC configured with a local IP adress (192.168.X.X) listening
on default port (623).
I want to access it from the outside world. For that I have set a port
forwarding rules on the router to the port 623 of this local IP.
every ipmitool commands works well BUT not SOL.
# ipmitool -I lanplus -p (external_port) -U (...) -P (...) -H (external
IP) sol activate
I get the message: "Error: BMC requests SOL session on different port"
I'm not sure to understand exactly what it means ? What I need to do to
make this work ?
Thanks !!
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Loading...