Lik`s forum

SMCIPMITool is a command line interface utility for the Supermicro SuperBlade and IPMI device.

The most useful feature which I have found handy for myself is to spawn KVM launcher directly from the CLI. Thus, no need to use web interface or launch additional applications (IPMIview, for example).
Download and unpack it to the destination directory:

Code: Select all

wget "https://www.supermicro.com/wdl/utility/SMCIPMITool/Linux/SMCIPMITool_2.27.0_build.220824_bundleJRE_Linux_x64.tar.gz"

Start KVM launcher:
# java -jar SMCIPMITool.jar 10.1.1.2 ADMIN ADMINPASS ukvm
Starting iKVM Process...Done
Please wait for ...

Found useful for myself the following CLI utility: column.
Just compare the user friendliness of the following output:
# cat /proc/mounts
rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
udev /dev tmpfs rw,nosuid,relatime,size=10240k,mode=755 0 0
devpts /dev/pts devpts rw,relatime,gid=5,mode=620 0 0
/dev/sdb3 / ext4 rw,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
tmpfs /run tmpfs rw,nosuid,nodev,relatime,mode=755 0 0
rc-svcdir /lib64/rc/init.d tmpfs rw,nosuid,nodev,noexec,relatime,size=1024k,mode=755 0 0
configfs /sys/kernel/config configfs rw,nosuid,nodev,noexec,relatime 0 0 ...

Load Averages


CloudLinux has a modified way to calculated load averages, as processes can wait on CPU because of LVE limits, and not because of lack of CPU resources. Previously, our LA algorithm was ignoring uninterruptable processes. You can now switch to another LA algorithm that accounts for uninterruptable processes by running:

Code: Select all

echo N > /sys/module/lve/parameters/lve_unint_hack

This line can be added to /etc/rc.local to make sure it is executed on startup ...

http://dnssec-debugger.verisignlabs.com/
http://dnsviz.net/

IPMI update instructions for Supermicro X9SCL/X9SCM:

1. Download firmware update on your local PC:

Code: Select all

wget -O SMT_X9_164.zip "http://www.supermicro.com/support/resources/getfile.aspx?ID=1743"

2. Print and backup current IPMI settings:

Code: Select all

ipmitool lan print 1

3. Disable IPMI driver (OpenIPMI or FreeIPMI) on the server and keep it so during the process of firmware update:

Code: Select all

service ipmi stop
service ipmievd stop

4. Log into IPMI web interface.
5. Go to the tab 'Maintenance' and click on 'Firmware Update'.
6. Click on ...

In case if IPMI interface isn't accessible after update you will have to do the following:

1. Upload IPMICFG tool to the server (you will find required binaries inside the archive):

Code: Select all

wget "ftp://ftp.supermicro.com/utility/IPMICFG/IPMICFG_1.25.0_build.160715.zip"

2. Unload(if any) IPMI driver (OpenIPMI or FreeIPMI) on the server:

Code: Select all

/etc/init.d/ipmi stop
/etc/init.d/ipmievd stop

3. Run the following commands:

Reset to the factory defaults:

Code: Select all

./ipmicfg-linux.x86_64 -fd

Disable the DHCP:

Code: Select all

./ipmicfg-linux.x86_64 -dhcp off

Set IP (format:###.###.###.###):
./ipmicfg-linux.x86_64 -m <IP which should be ...

http://www.root-servers.org/
http://www.root-dnssec.org/
http://www.securitylab.ru/contest/355930.php

http://cache.nevkontakte.com/

To recompile internal cPanel PHP with Curl/CurlSSL support which may be required for additional cPanel plugins/addons one should adjust internal PHP profile first.
Let`s check current settings set in the profile:

Code: Select all

# grep -i curl /var/cpanel/easy/apache/profile/makecpphp.profile.yaml
Cpanel::Easy::PHP4::Curl: 0
Cpanel::Easy::PHP4::CurlSSL: 1
Cpanel::Easy::PHP5::Curl: 0
Cpanel::Easy::PHP5::CurlSSL: 1
Cpanel::Easy::PHP5::Curlwrappers: 0


Modify profile for your needs (in this particular case enable Curl/CurlSSL):

perl -i -pe 's/Cpanel::Easy::PHP4::Curl: 0/Cpanel::Easy::PHP4::Curl: 1/g' /var/cpanel/easy/apache/profile/makecpphp.profile.yaml
perl -i -pe 's/Cpanel::Easy::PHP4::CurlSSL: 0/Cpanel::Easy::PHP4::CurlSSL: 1/g' /var/cpanel/easy/apache/profile/makecpphp.profile.yaml
perl ...

Members of dmraid arrays (block and software RAID devices) contain metadata signatures which are used to discover/assemble target RAID sets.

To remove them and release undelying block devices one should erase metadata signatures.

Discover all software RAID devices supported on your system, eg:
# dmraid -r
/dev/dm-46: hpt45x, "hpt45x_chidjhaiaa-0", striped, ok, 320172928 sectors, data@ 0
/dev/dm-50: hpt45x, "hpt45x_chidjhaiaa-0", striped, ok, 320172928 sectors, data@ 0
/dev/dm-54: hpt45x, "hpt45x_chidjhaiaa-1", striped, ok, 320172928 sectors, data@ 0
/dev/dm-58: hpt45x, ...