[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Freeipmi-users] Requesting suggestions to resolve an bmc/ipmi issue
From: |
Ravi DevPro |
Subject: |
Re: [Freeipmi-users] Requesting suggestions to resolve an bmc/ipmi issue |
Date: |
Tue, 5 Sep 2017 14:35:18 +0530 |
Hi All,
Never mind, I found how install 1.4.9. version on Ubuntu 14.04. I also was
able to issue bmc-config commands with '--lan-channel-number=3' without any
issues.
Thanks for the support Albert Chu.
FYI steps to install 1.4.9 on Ubuntu 14.04
wget -O- http://neuro.debian.net/lists/trusty.us-ca.libre | sudo tee
/etc/apt/sources.list.d/neurodebian.sources.list
sudo apt-key adv --recv-keys --keyserver hkp://pool.sks-keyservers.net:80
0xA5D32F012649A5A9
sudo apt-get update
sudo apt-get install freeipmi-tools
sudo apt-cache madison ^freeipmi-tools
freeipmi-tools | 1.4.9-1~nd14.04+1 | http://neurodeb.pirsquared.org/
trusty/main amd64 Packages
freeipmi-tools | 1.1.5-3ubuntu3.3 | http://in.archive.ubuntu.com/ubuntu/
trusty-updates/main amd64 Packages
freeipmi-tools | 1.1.5-3ubuntu3 | http://in.archive.ubuntu.com/ubuntu/
trusty/main amd64 Packages
Regards,
Ravi
On Tue, Sep 5, 2017 at 10:08 AM, Ravi DevPro <address@hidden> wrote:
> Hi FreeIPMI team,
>
> At the moment, apt-get install freeipmi-tools (on Ubunut 14.04) installs
> v1.1.5
> by default. Is there any way of us getting freeipmi-tools v1.4.9 (or
> beyond) installed on Ubuntu 14.04? Albert Chu, suggested that '*invalid
> channel number' *issue was fixed in v1.4.9.
>
> I tried downloading freeipmit-tool source code and build bmc-config
> binary. However I wasn't able to run the command,
>
> ~/freeipmi-1.5.7$ cd ./ipmi-config/
> ~/freeipmi-1.5.7/ipmi-config$ bmc-config --version
> /usr/local/sbin/ipmi-config: error while loading shared libraries:
> libfreeipmi.so.17: cannot open shared object file: No such file or directory
>
>
> Any pointers/ideas will be greatly appreciated.
>
> Thanks for considering and taking time for my queries and requests.
> Ravi
>
>
>
> On Fri, Sep 1, 2017 at 8:16 AM, Ravi DevPro <address@hidden> wrote:
>
>> Hi FreeIPMI Team,
>>
>> I have been struggling with an issue for couple of days now. I am using
>> an open source tool called MAAS (v1.9) for provisioning OS on physical
>> servers. This tool primarily relies uses bmc-config commands.
>>
>> Target hardware is some proprietary Intel based server (not HP/Dell)
>> which has BMC chip on it. It also has multiple LAN channels (1,2,3) where 1
>> & 2 being an in band NIC and channel 3 being dedicated BMC interface. Eth
>> interfaces of Channel 1 and Channel 3 are connected in a common broadcast
>> domain and get the IPs from a common DHCP server.
>>
>> The following are the set of bmc-config commands that gets triggered by
>> MAAS on the host (on which OS will be installed).
>>
>> bmc-config, --checkout, --key-pair=Lan_Conf:IP_Address_Source
>> bmc-config, -L
>> bmc-config, --checkout, --key-pair=User2:Username
>> bmc-config, --checkout, --key-pair=User3:Username
>> bmc-config, --checkout, --key-pair=User4:Username
>> bmc-config, --checkout, --key-pair=User5:Username
>> bmc-config, --checkout, --key-pair=User6:Username
>> bmc-config, --checkout, --key-pair=User7:Username
>> bmc-config, --checkout, --key-pair=User8:Username
>> bmc-config, --checkout, --key-pair=User9:Username
>> bmc-config, --checkout, --key-pair=User10:Username
>> bmc-config, --checkout, --key-pair=User11:Username
>> bmc-config, --checkout, --key-pair=User12:Username
>> bmc-config, --checkout, --key-pair=User13:Username
>> bmc-config, --checkout, --key-pair=User14:Username
>> bmc-config, --checkout, --key-pair=User15:Username
>> bmc-config, --commit, --key-pair=User6:Username=maas
>> bmc-config, --commit, --key-pair=User6:Password=DYJuTLXmrljoGl
>> bmc-config, --commit, --key-pair=User6:Enable_User=Yes
>> bmc-config, --commit, --key-pair=User6:Lan_Privilege_Limit=Administrator
>> bmc-config, --commit, --key-pair=User6:Lan_Enable_IPMI_Msgs=Yes
>> bmc-config, --checkout, --key-pair=User6:Username
>> bmc-config, --checkout, --key-pair=User6:Lan_Privilege_Limit
>> bmc-config, --checkout, --key-pair=User6:Lan_Enable_IPMI_Msgs
>> bmc-config, --checkout, --key-pair=Lan_Conf:IP_Address
>>
>>
>> All of these commands gets executed successfully however on *Lan Channel
>> 1 interface*. I* want this to be set to IP address assigned to Lan
>> Channel 3* (i.e Dedicated BMC interface). Thats my objective because
>> MAAS tool uses Lan_Conf:IP_Address for provisioning OS & it achieves this
>> over couple of power cycles of target host. The problem is that, since
>> *Lan_Conf:IP_Address
>> *is pointing to the IP on Lan Channel 1, that IP would not be available
>> once the server is switched off and that blocks the provisioning workflow.
>>
>> So I have tried following so far,
>>
>> I tried appending '*--lan-channel-number=3*' on those bmc-config
>> commands (listed above) & got '*invalid channel number*' in response.
>>
>> But when i execute *ipmitool -H 10.6.0.21 -U tocp -P tocp lan print 3*
>> Set in Progress : Set Complete
>> Auth Type Support : MD5 PASSWORD
>> Auth Type Enable : Callback : MD5 PASSWORD
>> : User : MD5 PASSWORD
>> : Operator : MD5 PASSWORD
>> : Admin : MD5 PASSWORD
>> : OEM :
>> IP Address Source : DHCP Address
>> IP Address : 10.6.0.21
>> Subnet Mask : 255.255.255.0
>> MAC Address : a4:bf:01:03:94:bb
>> SNMP Community String : public
>> IP Header : TTL=0x00 Flags=0x00 Precedence=0x00 TOS=0x00
>> BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Disabled
>> Gratituous ARP Intrvl : 0.0 seconds
>> Default Gateway IP : 10.6.0.1
>> Default Gateway MAC : 00:00:00:00:00:00
>> Backup Gateway IP : 0.0.0.0
>> Backup Gateway MAC : 00:00:00:00:00:00
>> 802.1q VLAN ID : Disabled
>> 802.1q VLAN Priority : 0
>> RMCP+ Cipher Suites : 0,1,2,3,4,6,7,8,9,11,12,13,15,16,17,18
>> Cipher Suite Priv Max : caaaaaaaaaaaaaa
>> : X=Cipher Suite Unused
>> : c=CALLBACK
>> : u=USER
>> : o=OPERATOR
>> : a=ADMIN
>> : O=OEM
>>
>>
>> *ipmitool -H 10.6.0.21 -U tocp -P tocp lan print 1*
>> Set in Progress : Set Complete
>> Auth Type Support : MD5 PASSWORD
>> Auth Type Enable : Callback : MD5 PASSWORD
>> : User : MD5 PASSWORD
>> : Operator : MD5 PASSWORD
>> : Admin : MD5 PASSWORD
>> : OEM :
>> IP Address Source : DHCP Address
>> IP Address : 10.6.0.14
>> Subnet Mask : 255.255.255.0
>> MAC Address : a4:bf:01:03:94:b9
>> SNMP Community String : public
>> IP Header : TTL=0x00 Flags=0x00 Precedence=0x00 TOS=0x00
>> BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Disabled
>> Gratituous ARP Intrvl : 0.0 seconds
>> Default Gateway IP : 10.6.0.1
>> Default Gateway MAC : 00:00:00:00:00:00
>> Backup Gateway IP : 0.0.0.0
>> Backup Gateway MAC : 00:00:00:00:00:00
>> 802.1q VLAN ID : Disabled
>> 802.1q VLAN Priority : 0
>> RMCP+ Cipher Suites : 0,1,2,3,4,6,7,8,9,11,12,13,15,16,17,18
>> Cipher Suite Priv Max : caaaaaaaaaaaaaa
>> : X=Cipher Suite Unused
>> : c=CALLBACK
>> : u=USER
>> : o=OPERATOR
>> : a=ADMIN
>> : O=OEM
>>
>> *bmc-config -h 10.6.0.21 -u tocp -p tocp --checkout
>> --key-pair=Lan_Conf:IP_Address*
>> Section Lan_Conf
>> ## Give valid IP address
>> IP_Address 10.6.0.14
>> EndSection
>>
>>
>>
>>
>>
>> Any kind of pointers/suggestions would be greatly appreciated.
>>
>> Thank you for your time & consideration.
>> Ravi
>>
>
>