Project

General

Profile

Actions

action #90920

closed

Restore IPMI access to malbec.arch.suse.de

Added by mkittler over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
Start date:
2021-04-09
Due date:
% Done:

0%

Estimated time:

Description

The IPMI command as documented in workerconf.sls doesn't work:

ipmitool -I lanplus -C 3 -H fsp1-malbec.arch.suse.de -P admin sol activate
Error: Unable to establish IPMI v2 / RMCP+ session

I assume it worked before and can somehow be restored.

Actions #1

Updated by nicksinger over 3 years ago

you can login over SSH onto the host and issue ipmitool lan print 1 to get the IP of the BMC which is 10.161.60.189 in the case of malbec. With dig -x 10.161.60.189 +short it shows that the BMC currently has some autogenerated DNS name: c445.arch.suse.de. I assume this is due to a recent switch to cobbler in the arch network. However, with the right IP also SOL works:

selenium ~ » ipmitool -I lanplus -C 3 -H 10.161.60.189 -P admin sol activate                                       1 ↵
[SOL Session operational.  Use ~? for help]

malbec login: 
Actions #2

Updated by okurz over 3 years ago

  • Status changed from New to Workable
  • Priority changed from Normal to High
  • Target version set to Ready
Actions #3

Updated by okurz over 3 years ago

  • Status changed from Workable to In Progress
  • Assignee set to okurz
Actions #4

Updated by mkittler over 3 years ago

  • Description updated (diff)
Actions #5

Updated by okurz over 3 years ago

  • Description updated (diff)
  • Due date set to 2021-05-07
  • Status changed from In Progress to Blocked

The actual host should be "fsp1-malbec.arch.suse.de" but the error is the same.

https://infra.nue.suse.com/SelfService/Display.html?id=187768

Actions #6

Updated by okurz over 3 years ago

  • Description updated (diff)
Actions #7

Updated by okurz over 3 years ago

https://infra.nue.suse.com/SelfService/Display.html?id=187768#txn-2857054 called it done but it only works for IPv4. There is an AAAA record which does not resolve to a valid IP so reopened.

Actions #8

Updated by okurz over 3 years ago

  • Due date deleted (2021-05-07)
  • Status changed from Blocked to Resolved

MC was reset by gschlotter, now both addresses are reachable. I verified and it looks good.

Actions

Also available in: Atom PDF