From: Radhai Ezhil Murugan <radhaiezhil.murugan@hcl.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: New User added ,not able to access through LAN with ipmitool lanplus command
Date: Wed, 20 Dec 2023 06:06:20 +0000 [thread overview]
Message-ID: <SEZPR04MB6320987EB7D35EF2A314BBD0EE96A@SEZPR04MB6320.apcprd04.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3443 bytes --]
Hi,
I have added new user with administator privilege and ipmi =on
D Name Callin Link Auth IPMI Msg Channel Priv Limit
1 root false true true ADMINISTRATOR
2 operator1 true true true ADMINISTRATOR
3 true false false NO ACCESS
4 true false false NO ACCESS
5 true false false NO ACCESS
6 true false false NO ACCESS
7 true false false NO ACCESS
8 true false false NO ACCESS
9 true false false NO ACCESS
10 true false false NO ACCESS
11 true false false NO ACCESS
12 true false false NO ACCESS
13 true false false NO ACCESS
14 true false false NO ACCESS
15 true false false NO ACCESS
and acess level for both root user and LAN user are same
radhai@radhai-ThinkPad-T495:~$ ipmitool -C 17 -H 192.168.1.211 -I lanplus -U root -P 0penBmc channel getaccess 1 2
Maximum User IDs : 15
Enabled User IDs : 2
User ID : 2
User Name : operator1
Fixed Name : No
Access Available : call-in / callback
Link Authentication : enabled
IPMI Messaging : enabled
Privilege Level : ADMINISTRATOR
Enable Status : enabled
radhai@radhai-ThinkPad-T495:~$ ipmitool -C 17 -H 192.168.1.211 -I lanplus -U root -P 0penBmc channel getaccess 1 1
Maximum User IDs : 15
Enabled User IDs : 2
User ID : 1
User Name : root
Fixed Name : No
Access Available : callback
Link Authentication : enabled
IPMI Messaging : enabled
Privilege Level : ADMINISTRATOR
Enable Status : enabled
but new user not able to establish connection with ipmitool lanplus command
radhai@radhai-ThinkPad-T495:~$ ipmitool -C 17 -H 192.168.1.211 -I lanplus -U operator1 -P password1234 power status
Error: Unable to establish IPMI v2 / RMCP+ session
I need establish LAN access for new user
Please advise
Thank you ,
Radhai
::DISCLAIMER::
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
________________________________
[-- Attachment #2: Type: text/html, Size: 15737 bytes --]
reply other threads:[~2024-01-02 22:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SEZPR04MB6320987EB7D35EF2A314BBD0EE96A@SEZPR04MB6320.apcprd04.prod.outlook.com \
--to=radhaiezhil.murugan@hcl.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).