Scale-out LC System Event Log Collection Tool

https://www-304.ibm.com/support/customercare/sas/f/lopdiags/scaleOutLCdebugtool.html

Scale-out LC Service and Support

• Start
• Installation
• Usage
• Reference Information

• IBM OpenBMC tool
• Scale-out LC system VPD update tool
• SNMP Trap enablement

[ Last updated: 01 June 2018 ]

Start

If a Linux partition is up and running then the standard sosreport should be collected in addition to running the plc.pl data collection script.

The sosreport needs to be run by root user, the script will prompt for additional information and when complete will show the location of the output file.

To collect the data from the BMC, the plc.pl script file (contained in the plc.zip package below) should be used by the customer to collect additional data.

Back to top

Installation

For MT 8348-21C, 8335-GCA, 8335-GTA, and 8335-GTB systems:
plc.zip

For MT 8001-12C, 8001-22C, 8005-12N, 8005-22N, 7063-CR1, 9006-22P, 9006-22C, and 5104-22C systems:
plc.zip

Prerequisites

• The Linux system used to perform the data collection must have the following tool packages installed:
  • ipmitool
  • perl
  • sshpass - For POWER8 based systems only (8001, 8005, 7063, 8348, 8335-GTA GTB GCA)
• The Linux system must have network connectivity to the BMC.

Installation steps

1. Copy the pic.zip package to a Linux system that has network connectivity to the BMC of the Scale-out LC server you need to collect data from.
2. Unzip the pic.zip file into a directory of your choice.
   Note: The files generated by this script will be saved in the same directory as the script is run from.
   unzip plc.zip
3. The directory should now contain the following directories:
   P8-ppc64le
   P8-x86_64
   P9-ppc64le
   P9-x86_64

Back to top

Usage

usage: plc.pl { -b bmc_address | -i } [-a admin_pw] [-s sysadmin_pw] [-h host -u user -p password] [-f]

Flags:

-b BMC hostname or IP address
-a BMC ADMIN password if changed from default (admin)
-s BMC sysadmin password if changed from default (superuser)
-i Interactive mode
-f Collect BMC firmware image
-h Linux host address: Only on POWER8 Systems
-u Linux host user ID: Only on POWER8 Systems
-p Linux host password: Only on POWER8 Systems

Errors

• If sshpass is not found on the system then the plc.pl script will print "sshpass is required and not found on this system" and will exit with return code 1, for POWER8 based systems.
• If the BMC is not reachable via ping then the plc.pl script will print, "Unable to ping bmchostname/IPaddress" and will exit with return code 2.
• If a "command not found" error is returned when running the plc.pl command, try running the command by prepending the command with ./ so that the command is ./plc.pl

Back to top

Reference Information

This section is intended as additional reference information.

Installing Requisite Packages

Note: The linux server that is going to be used for running data collection script can be running any version of Linux on any type of server. It is not related to the Scale-out LC server or the version of Linux running on the Scale-out LC server.

• Linux distributions have their own way to search, download and install packages such as the required ipmitool and sshpass programs.
• If using a graphical front end, an easy to use GUI utility is provided that allows you to search the Linux repository (usually on the internet unless a local repository has been set up), select, download and install the required packages and any prerequisites they may have.
• From the command line, different Linux distributions have different command line tools. You will need to be root user to run these commands.
  For example: sudo apt-get install ipmitool

We would expect the administrator to be familiar with installing packages and files on their Linux environment.

Back to top

Managing software

Task	apt (deb) Debian, Ubuntu	zypp (rpm) openSUSE	yum/dnf (rpm) Fedora, CentOS	urpmi (rpm) Mandriva, Mageia
Install new software from package repository	apt-get install pkg	zypper install pkg	yum install pkg	urpmi pkg
Install new software from package file	dpkg -i pkg	zypper install pkg	yum localinstall pkg	urpmi pkg
Update existing software	apt-get install pkg	zypper update -t package pkg	yum update pkg	urpmi pkg
Remove unwanted software	apt-get remove pkg	zypper remove pkg	yum erase pkg	urpmi pkg

Back to top

IBM OpenBMC tool

The IBM OpenBMC tool is used to interact with the new OpenBMC on the 8335-GTG, 8335-GTC, 8335-GTW, 8335-GTH, and 8335-GTX products.

Pre-requisites:

• python 3
• python 3 requests

For RHEL distributions:
openbmctool-1.0-4.noarch.rpm

For other operating systems:
openbmctool.zip

Note: For Windows OS support, version 1.04 or greater of the tool is needed.

RHEL

• To install, run the following as root:
  yum install ./<rpm downloaded above>

Other operating systems

To install, complete the following:

1. Extract the contents of the zip file.


2. It is recommended to add a link to this file in your path.
   
   For example:
   ln -s -f /opt/ibm/ras/bin/openbmctool.py /usr/bin/openbmctool


3. After extracting the contents, operating systems other than Linux will require you to add 'python' at the beginning of each command:
   
   For example:
   python openbmctool.py -H <bmc IP> or <bmc hostname> -U <username> -P <password> chassis power status

Execution

1. To get help on a command:
   openbmctool -H <bmc IP> or <bmc hostname> -U <username> -P <password> chassis power -h


2. To view log entries:
   openbmctool -H <bmc IP> or <bmc hostname> -U <username> -P <password> sel print


3. To collect service data from the BMC:
   openbmctool -H <bmc IP> or <bmc hostname> -U <username> -P <password> collect_service_data

Back to top

Scale-out LC system VPD update tool

The Scale-out LC system VPD update tool is used to make VPD modifications to POWER Systems from the host OS of the machine.

For Ubuntu distributions: 
ophtk-lht_20160128-1.ub14.04_ppc64el.deb

For RHEL distributions:
ophtk-lht-20160128-1.el7.ppc64le.rpm

Petitboot Plugin:

Ubuntu

• To install, run the following:
  sudo dpkg -i <deb downloaded above>
• If you encounter a dependency error when installing the tool, run the following to install dependencies and complete the install:
  sudo apt-get -f install

RHEL

• To install, run the following as root:
  yum install ./<rpm downloaded above>

Petitboot Plugin:

• To install, the plugin from a usb key:
  pb-plugin install /path/to/vpdupdate-1.3.pb-plugin

Note: /path/to needs to be substituted with the actual path to the petitboot plugin. For example, pb-plugin install /var/petitboot/mnt/dev/sda/vpdupdate-1.3.pb-plugin

To install the plugin from a network location from the petitboot shell:
pb-plugin install http://mystorage.com/path/to/vpdupdate-1.3.pb-plugin

Execution

1. To update the machine serial number:
   sudo /opt/openpower/lht/bin/updateserial <1234567>
   Note: <1234567> to be replaced with your seven character Serial Number

From Petitboot shell:
/var/lib/pb-plugins/bin/updateserial <1234567>



2. To update the machine model:
   sudo /opt/openpower/lht/bin/updatemodel <8335-GTA>
   Note: <8335-GTA> to be replaced with your system model

From Petitboot shell:
/var/lib/pb-plugins/bin/updatemodel <8335-GTA>



3. For MT 8001-12C, 8001-22C, 8005-12N, 8005-22N, and 7063-CR1 systems, run the following command to save changes:
   ipmitool -I lanplus - U <username> -P <password> -H <bmcIP> raw 0x3a 0x1c 
   
   

   Note: This may take about 30 seconds to complete. Run the following command to check status and continue after it returns a value of 0.
   ipmitool -I lanplus -U <username> -P <password> -H <bmcIP> raw 0x3a 0x1d

For MT 8348-21C, 8335-GCA, 8335-GTA, and 8335-GTB: Reinstall or upgrade the PNOR firmware for the changes to take effect.



4. Reboot the system to petitboot or the host OS to ensure the changes take effect.



Note: For 8348-21C, to verify that is the machine type and model, you will need to look at FRU ID 2 via the GUI or ipmitool fru print 3. For all other Machine Types: To verify that is the machine type and model, you will need to look at FRU ID 3 via GUI or ipmitool fru print 3.

Back to top

SNMP Trap enablement

For MT 8348-21C, 8335-GCA, 8335-GTA, and 8335-GTB systems:

1. Log into the BMC WebGUI
2. From the Configuration menu, click "PEF"
3. Click "LAN Destination"
4. Within the displayed table, click on a row, then click Add for a new entry
5. From the Destination type drop-down, select "SNMP Trap". Populate the Destination Address field with the IPv4 Address of the system where the SNMP client resides. Click "Save".
6. This completes the BMC setup for sending SNMP Traps. The MIB table below can be used with your client for interpreting the traps.
   
   • MIB file for SNMP traps: The MIB file contains the most of the generic sensor events possible defined in the IPMI spec. This is an opensource MIB file:
     http://ipmiutil.sourceforge.net/docs/bmclanpet.mib

For MT 8001-12C, 8001-22C, 8005-12N, 8005-22N, and 7063-CR1 systems:

1. Log into the BMC WebGUI
2. From the Configuration menu, click "Alerts"
3. Within the displayed table, click on a row, then click "Modify"
4. From the "Event Severity" drop-down, pick the level of alerts you want to receive. Populate the Destination IP field with the IPv4 Address of the system where the SNMP client resides. Click "Save".
5. This completes the BMC setup for sending SNMP Traps. The MIB table below can be used with your client for interpreting the traps.
   
   • MIB file for SNMP traps:
     IPMI-PET-Trap_PPC.zip

Back to top

Translate this page

Select LanguageGermanSpanishFrenchItalianJapaneseKoreanPortugueseRussianChinese SimplifiedChinese Traditional