ViPR SRM 3.6 – SolutionPack for IBM LPAR Summary Sheet

Table of Contents

Overview

Learn how to install and configure the SolutionPack for IBM LPAR. The SolutionPack for IBM LPAR collects Inventory details about IBM's Power-Servers managed by Hardware Management Console (HMC) and displays the data in easy-to-use reports in ViPR SRM.

With this SolutionPack, you can generate reports to highlight key relationships in the virtual environment such as:

Capacity reports, such as File System Usage, help you to improve the availability of business critical applications and services by ensuring that applications have the storage resources they need to operate effectively.

SolutionPack for IBM LPAR

SolutionPack for IBM LPAR

Back to Top

Technical Specifications

Main reports

HMC Dashboard

LPAR/VIO Client Information and details

VIO Server basic details

Host Capacity Reports: Usable Capacity by FileSystem, Volume Manager Summary, Chargeable Capacity by Service Level, Disk Inventory

Topology end to end maps for VIOS/VIOC

Note Image

ViPR SRM Release 3.5 and earlier: Topology maps for VIOC will be reported only if the respective VIOS is discovered.

ViPR SRM Releases after 3.5: Topology maps for VIOC will be reported regardless of VIOS discovery.


Supported collection interfaces

For information about supported collection interfaces, refer to the ViPR SRM Support Matrix.

Back to Top

Where to find the latest SolutionPack software

Install the latest core software update for your product suite. SolutionPacks distributed with core software have a 30-day free evaluation period. If you plan to use the software longer than 30 days, you must install a SolutionPack license before the trial period ends.

This 30-day free evaluation only applies to new installations and is not available for upgraded installations. If you upgrade the core software and want to try a new SolutionPack, you must request a license for that SolutionPack.

Back to Top

Configuring VIO for discovery

The user credentials of VIO Server & VIO Clients should be configured in Discovery Center > Host Configuration.

ViPR SRM requires non-root user credentials or a SSH public/private key pair (keys can be created for root / non-root users) to discover VIO Servers and VIO Clients.

When the VIOS Server is installed, the padmin user is automatically created and this user provides restricted shell access. The ViPR SRM host data collection mechanism does not work in the restricted shell environment, so you must create a non-root user and configure the non-root user via Sudo or PowerBroker to elevate the privileges to run certain commands as root. Provide the non-root user credentials to ViPR SRM while discovering the VIO Server.
Note Image
ViPR SRM does not require padmin credentials to discover the VIO server.

There are many tools available to elevate the privileges of a non-root user to run commands as root, but ViPR SRM 3.6 supports only Sudo and Powerbroker.


Prepare VIO Server and VIO Client hosts for discovery

VIO Server and VIO Client hosts can be discovered in the following ways:

Back to Top

Configuring sudo for VIO Server and VIO Client host discovery

To discover VIO Server/Client hosts and collect data from these hosts you have to elevate privileges for the non-root user via sudo because some commands used in the data collection require root privileges.

Before you begin

Supported sudo versions
Linux Fedora distribution: sudo-1.8.6 and above
Other operating systems: any version of sudo

Procedure

  1. Include the path of sudo command in the environment variable $PATH for the sudo user.
    The variable $PATH can be set either in /etc/environment or /etc/default/login or any other OS specific file.
  2. Include the paths of OS commands in the environment variable $PATH for sudo user.
    By default, most of the command files have the following location: /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
  3. Verify that the $PATH is correct.
    1. Log in as sudo user
    2. Type which sudo.
  4. Ensure that the sudoers file is available.
    By default, the sudoers file is available in /etc or /opt/sfw/etc/ or /usr/local/etc/sudoers
  5. Add the following line to the defaults section of the sudoers file:

    Defaults !requiretty #for all users

    or

    Defaults : SRMADMIN !requiretty #for a specific user

  6. For AIX hosts, if inq gives partial information, add the following line:
    Defaults env_keep += "ODMDIR"
  7. Ensure that the sudo user has root privilege to run the following commands on a given host.

    Ensure the absolute path to the packages are provided in sudoers file.

    It is recommended to use visudo to edit sudoers file.

    Some packages are not installed by default.

    AIX
    sar, inq, powermt, vxdisk, swap, kdb (kdb is only for VIO Clients)
    Linux
    sar, inq, powermt, vxdisk, dmidecode, lvdisplay, pvs, vgs, multipath

    Sample sudoers file for Linux OS

Back to Top

Configuring PowerBroker for VIO Server and VIO Client discovery

PowerBroker for UNIX & Linux allows system administrators to delegate UNIX and Linux privileges and authorization without disclosing passwords for root or other accounts. Administrators can add specific commands in the configuration/policy files to enable ViPR SRM to execute those commands and collect host information.

Procedure

  1. Include the path of the pbrun command in the environment variable $PATH for the powerbroker submit/run host.
  2. Include the paths of the OS commands in the environment variable $PATH for the pbrun user. By default, most of the command files have the following location:
    /usr/local/:sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
  3. Verify that the $PATH is correct.
    1. Log in to the submit/run host.
  4. Type "which pbrun".
  5. The configuration/policy files exist on the master host and they must include the pbrun user name and the associated commands for host discovery. The following screenshot displays the policy files for a configuration in which the master/submit/run host is on the same host:
    In this screenshot, the RootUsers variable includes "cmguser", which is the submit user (the ViPR SRM user used for discovering the host details) and the RootProgs variable includes the various commands required by ViPR SRM to discover the host. Note that the commands mentioned in the section about configuring sudo apply here as well.
Back to Top

Generating a public and private key pair for SSH key based authentication

For the SSH key method of discovering UNIX hosts, you must generate a valid public and private key pair. You can choose any key generation tool to generate a valid public and private key pair.

Before you begin

Before you begin host discovery, you must have a public key present on all the UNIX hosts that are to be discovered using the private key. You can create SSH keys in any Unix environment and import them onto the ViPR SRM collector. EMC recommends that you create public-private SSH keys on ViPR SRM collectors (Linux VMs) where host discovery will be initiated.

These steps describe the procedure to generate a public and private key pair for UNIX hosts using the ssh-keygen tool.

Note Image
The public key is to be added to the authorized_keys file on the target hosts intended for discovery and the private key is to be imported to the collector VMs where discovery is triggered.

Procedure

  1. A Public-Private key can be generated using the following command:
    ssh-keygen -t rsa -f <location_of_the_private_key/name_of_ private_key_file> -N ""

    For example: ssh-keygen -t rsa -f /root/.ssh/id_rsa -N ””

  2. Ensure that the public and private key pair that is generated has the following permissions:
    • chmod 600 /root/.ssh/id_rsa
    • chmod 644 /root/.ssh/id_rsa.pub
    The private key file is id_rsa.
    The public key file is id_rsa.pub.
  3. To make the key pair functional, append the public key to <user's home directory>/.ssh/authorized_keys in the target UNIX host using the command cat <location_of_the_public_key/name_of_public_key_file>>> /<user's home directory>/.ssh/authorized_keys
    For example: cat /root/.ssh/id_rsa.pub >> /<user's home directory>/.ssh/authorized_keys
    Next, import the private key to the Collector used for discovery.
Back to Top

Importing a private key into the Collector

Procedure

  1. Place the generated private key in the RSC conf folder /opt/APG/Collecting/Remote-Shell-Collector/<instance_of_collector>/conf
  2. Type chown apg:apg <private_key_file>
    This command changes the owner.
    The host is now ready for successful data collection.
Back to Top

Verify adapter IDs in NPIV configuration

In the NPIV configuration if a VFC Server Adapter is created on the VIOS and a VFC Client Adapter on the VIOC, ensure correlation between the Physical HBA ports and the Virtual FC Client Adapter ports.

Procedure

  1. On an HMC, go to the Virtual Adapters tab in the partition Properties of the VIOS/VIOC on which the VFC Server/Client Adapter are created.
  2. Verify that a match exists between the Adapter ID of VFC Server Adapter and the Adapter ID of VFC Client Adapter.
Back to Top

Installing the SolutionPack

Before you begin

Procedure

  1. Click Administration.
  2. Click Centralized Management.
  3. Click SolutionPacks.
  4. Click SolutionPack Center.
  5. Select the SolutionPack in the Browse and Install SolutionPacks window.
  6. Click Install.
  7. Type the instance name.
  8. Assign a server for each component.
    In a typical four server deployment, the recommended servers are selected automatically.
  9. Click Next.
    The window displays data collection details.
  10. From the Data collection drop-down menu, select existing settings that have been specified for other components, or select Add a new data collection.
    If you select Add a new data collection, type information about the data collection. In Hostname or IP address to send data to, use localhost on port 2020, which is the Collector host where the Load Balancer Connector is installed.
  11. Click Do you want to configure advanced settings if you want to change the default HMC polling interval.
  12. Click Next.
    The window displays reports settings.
  13. In Administration Web-Service Instance, select an existing instance or create a custom instance.
  14. Click Install.
  15. Click Ok when the installation is complete.
  16. Click Discovery Center > Devices Management.
  17. Click IBM LPAR.
  18. Click Add new device.
  19. Select the server and collector instance where you want to store the configuration details for this device, and then enter the hostname or IP address of the host, supply the login credentials, and specify the appropriate configuration settings.
  20. Click Test to validate the credentials.
  21. Click OK.
  22. Click Save.

Results

The SolutionPack for Physical Hosts will collect data from Physical Host/LPAR/VIO Servers. You can configure script block from SolutionPack for Physical Hosts on multiple collector VMs where you intend to discover hosts/LPAR/VIO server. Based on your deployment plan, you can distribute host discovery on multiple collector VMs.

Back to Top

Using Discovery Center to discover the VIO Servers and Clients

Procedure

  1. From the User Interface, click Administration.
  2. Click Discovery Center.
  3. Under Device Type, click Host configuration.
  4. Click Add new device.
  5. In Server, select the collector VM where script block from SolutionPack for Physical Hosts is installed.
  6. Enter the VIO Server/Client configuration details and click Ok.
  7. Add a new device for each VIO Server and Client that will be discovered.
  8. Select the Authentication Type as:
    Option Description
    Password based Authenticates with password.
    Public key base Authenticates with SSH public private key.
  9. Provide username (root or sudo user):
    1. Provide the password of the host for password based authentication
    2. Provide the location of the private key for public key based authentication ( /opt/APG/Collecting/Remote-Shell-Collector/ <instance-of-collector> /conf/ <name-of-private-key>)
  10. Click Ok.
  11. Select the device added and click Save.
  12. Add a new device for each VIO Server and client that will be discovered.
Back to Top

Using Discovery Center to discover an HMC

Procedure

  1. From the User Interface, click Administration.
  2. Click Discovery Center.
  3. Under Device Type, click IBM LPAR configuration.
  4. Click Add new device.
  5. Enter the HMC hostname, username and password.
  6. Click Ok.
  7. Select the device added and click Save.
  8. Add a new device for each HMC that will be discovered.
Back to Top

SolutionPack Reconfiguration

If you wish to change the answers that were provided during SolutionPack installation the first time through, you could change them by reconfiguring the SolutionPack.

Procedure

  1. Click Administration.
  2. Under Centralized Management.
    1. Click SolutionPacks > Independent SolutionPackBlocks and select generic-rsc.
      The SolutionPackReconfiguration dialog box appears.
    2. Click SolutionPacks > Infrastructure > IBM LPAR and select the instance for LPAR.
  3. Change the configuration as desired.
  4. Click Reconfigure.
Back to Top

Confirming report creation

After you install a SolutionPack, you can view its reports.

To view the reports:

Procedure

  1. Go to User Interface > Report Library.
  2. Click the SolutionPack to view its reports.

Results

It may take up to an hour to display all relevant information in these reports.

Back to Top

Troubleshooting

Report display problems

Back to Top

What to do if data does not appear in any reports

Procedure

  1. After the completion of at least three collection cycles, verify if data is populating into the reports. If there is still no data in the reports, continue to the next step.
  2. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to the next step.
  3. To view the log files for errors, go to Centralized Management and click Collecting > Collector-Manager::<instance name> > Log Files.
Back to Top

Running a scheduled task to import data into reports

After you push a new configuration into a collector, a scheduled task runs and populates the reports with new data. You can manually run the scheduled task to import the data more quickly.

Before you begin

Allow at least three polling cycles to pass before manually running the scheduled task.

Procedure

  1. Click Administration.
  2. Click Centralized Management.
  3. Expand Scheduled Tasks.
  4. Click Database.
  5. Select the import-properties-Default task.
  6. Click Run Now.
  7. Confirm success in running the task in the Last Result and Last Result Time columns.
Back to Top

What to do if data does not appear in some reports

Procedure

  1. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to step 2.
  2. Search for the metric in the database.
  3. To view the log files for errors, go to Centralized Management and click Collecting > Collector-Manager::<instance name> > Log Files.
Back to Top

Searching for metrics in the database

You can verify that a metric is being collected and used for reporting when you search and find the metric in the database.

Procedure

  1. Go to the Administration page.
  2. Under Modules, click Management of Database Metrics.
  3. On the Metric Selection page, create the filter, type the number of results, and select the properties to display for the metric.
    For example, to list up to 100 results of the Capacity metric with the properties of device and IP, type name=='Capacity' in the Filter field, 100 in the Maximum results field, and select device and IP for the Properties to show.
  4. Click Query.
    A list of the metric results appears. If nothing displays, the metric is not being collected.
Back to Top

Viewing collector errors in the Collector-Manager log files

Review the Collector-Manager log files to troubleshoot problems with data collection.

Procedure

  1. Click Administration.
  2. Click Centralized Management.
  3. Expand Collecting.
  4. Click the Collector-Manager for your collector instance.
    Collector-Manager::<Collector-Manager instance> - <host_ID>
  5. Expand Log Files and click the View File icon to review the configuration error messages.
Back to Top