11
29
Fork
You've already forked ipmitool
33

Multiple connection result in Error: Unable to establish IPMI v2 /RMCP+ session #30

Closed
opened 2024年02月29日 15:11:48 +01:00 by manolo-mm · 1 comment

Describe the bug
Sending requests to multiple BMCs via LAN results in error message "Error: Unable to establish IPMI v2 /RMCP+ session". The same occurred if I try to use multiple instances of IMPItool.

IPMITOOL Version

1.8.19

To Reproduce
I'm using a script to open a connection via lanplus e.g. ipmitool -I -H -U -P power

Doing this on one only on BMC IP is working fine. If I use this script on multiple IPs or with multiple instances of the script it will result in "Error: Unable to establish IPMI v2 /RMCP+ session". I tried to use the script with timeouts so no that the command won't have collisions or won't hit internal timeouts but ultimately it won't work either.

Expected behavior
A possibility to run IMPItool to multiple endpoints via LAN connection.

**Describe the bug** Sending requests to multiple BMCs via LAN results in error message "Error: Unable to establish IPMI v2 /RMCP+ session". The same occurred if I try to use multiple instances of IMPItool. **IPMITOOL Version** 1.8.19 **To Reproduce** I'm using a script to open a connection via lanplus e.g. ipmitool -I -H <ip> -U <user> -P <PW> power <command> Doing this on one only on BMC IP is working fine. If I use this script on multiple IPs or with multiple instances of the script it will result in "Error: Unable to establish IPMI v2 /RMCP+ session". I tried to use the script with timeouts so no that the command won't have collisions or won't hit internal timeouts but ultimately it won't work either. **Expected behavior** A possibility to run IMPItool to multiple endpoints via LAN connection.

ipmitool itself can not communicate to multiple targets at once. When you run the program it performs its task and ends completely, with all its resources freed by the OS kernel. There is no way one invocation of ipmitool can affect subsequent invocations.

Hence, the problem you're experiencing doesn't sound like an ipmitool bug. Sorry.

`ipmitool` itself can not communicate to multiple targets at once. When you run the program it performs its task and ends completely, with all its resources freed by the OS kernel. There is no way one invocation of `ipmitool` can affect subsequent invocations. Hence, the problem you're experiencing doesn't sound like an `ipmitool` bug. Sorry.
Sign in to join this conversation.
No Branch/Tag specified
master
bugfix/43-Fix-timezone-and-DST-in-SEL
pages
bugfix/fix-ci-builds
feature/refactor-sdr-name-handling
cleanup/nm
feature/add-support-for-boot-mailbox
codefactor
bugfix/26
IPMITOOL_1_8_19
IPMITOOL_1_8_18
IPMITOOL_1_8_17
IPMITOOL_1_8_16
IPMITOOL_1_8_15
IPMITOOL_1_8_15RC1
IPMITOOL_1_8_14
IPMITOOL_1_8_14RC2
IPMITOOL_1_8_14RC1
ipmitool
IPMITOOL_1_8_13
IPMITOOL_1_8_13RC1
IPMITOOL_1_8_12
IPMITOOL_1_8_9
IPMITOOL_1_8_8
IPMITOOL_1_8_7
IPMITOOL_1_8_6
IPMITOOL_1_8_5
IPMITOOL_1_8_0
IPMITOOL_S10_U1
IPMITOOL_1_6_1
IPMITOOL_1_6_0
IPMITOOL_1_5_9
IPMITOOL_1_5_8
IPMITOOL_1_5_7
IPMITOOL_1_5_6
IPMITOOL_1_5_4
IPMITOOL_1_4_1_1
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
IPMITool/ipmitool#30
Reference in a new issue
IPMITool/ipmitool
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?