Installation of LSI SMI-S Provider

1. Download the latest LSI SMI-S provider for AIX® from the LSI website. It will download as AIX_Installer_*.tar.
2. Place the tar in a relevant directory on your AIX machine. This example uses the /download directory.
3. Untar the tar ball, as shown below:

   cd /downloads tar –xvf AIX_Installer_*.tar

   
   

   Untarring will result in the following files being created in the /download directory.

   • EngenioProvider-10*.bff
   • install
   • deinstall
4. Install the LSI SMI-S Provider. Ensure that sufficient space exists in /usr and /opt. Installation takes about five minutes.

   chmod a+x install ./install

   
   
5. LSI SMI-S Provider installs in /opt/engenio.
6. If you wish to deinstall the LSI SMI-S Provider, do the following:

   chmod a+x deinstall ./deinstall

   
   

Back to top

Configuring Provider

Prevent port conflicts with IBM Systems Director

In this article, the Provider is installed on the same machine that has IBM Systems Director V6.1.2 installed. Director uses ports 5988 and 5989 as its http and https ports, respectively. By default, Provider is also configured to use 5988 and 5989 as its http and https ports. In order to avoid port conflicts, change the ports used by Provider from 5988 and 5989 to 15988 and 15989, or some other ports which are free, as shown below:

	cd /opt/engenio/SMI_SProvider/bin
	vi portInfo.properties
	CIM-XML=15988
	HTTPS=15989

Save portInfo.properties. You need to stop and restart Provider for the changes to take effect:

	./launch stop
	./launch start

Authentication between Provider and IBM Systems Director

Provider by default comes with no authentication enabled; all users with or without the necessary privileges can communicate between Director and Provider. This is not recommended for security purposes. To enable requisite authentication between Director and Provider, do the following:

	cd /opt/engenio/wbemservices/cimom/bin
	vi cimom.properties

The list below shows the defaults in cimom.properties:

org.wbemservices.wbem.cimom.pswdprov=org.wbemservices.wbem.cimom.security.
UnsecureUserPasswordProvider

#org.wbemservices.wbem.cimom.pswdprov=cimprovider.security.BasicUserPasswordProvider

#org.wbemservices.wbem.cimom.pswdprov=cimprovider.security.
CredentialsBasedPasswordProvider

Change cimom.properties to:

#org.wbemservices.wbem.cimom.pswdprov=org.wbemservices.wbem.cimom.security.
UnsecureUserPasswordProvider

org.wbemservices.wbem.cimom.pswdprov=cimprovider.security.BasicUserPasswordProvider

#org.wbemservices.wbem.cimom.pswdprov=cimprovider.security.
CredentialsBasedPasswordProvider

When BasicUserPasswordProvider authentication is enabled, only local users are allowed to authenticate. Root user and passwords of the AIX machine can be used as one local user credentials for authentication. This article uses the root user.

CredentialsBasedPasswordProvider initially allows all users. To secure the user, additional steps are required that are beyond the scope of this article.

Save cimom.properties. Stop and start Provider for the changes to take effect:

	./launch stop
	./launch start

Back to top

Addition of Storage Subsystems to Provider

LSI SMI-S Provider comes with a default script that can be used for adding storage subsystems to Provider, ProviderUtil present in /opt/engenio/SMI_SProvider/bin.

Run the script as follows:

	cd /opt/engenio/SMI_SProvider/bin
	./ProviderUtil
	CIMOM username: <root>
	CIMOM Password: <root’s password>
	Input CIMOM Port [5988]:15988
	Input operation:
	'add' for AddDevice,
	'rem' for RemoveDevice: add
	Input IP or hostname for array: <Storage Controller IP>
	Input Array password: <Storage Subsystem password>

The CIMOM port should be the port number that you entered in portInfo.properties (as mentioned earlier, 15988 in this article's case). Input IP can be the storage subsystem hostname or any one storage controller's IP. Using ProviderUtil with one storage controller IP automatically adds even the other storage controller's IP to the Provider. If the storage does not have a password, then just click Enter. Having a storage password is essential for any storage modification functions but just querying will even work if no storage password is entered.

Back to top

Discovery of the SMI-S Provider using IBM Systems Director console

IBM Systems Director requires a profile to be created for Provider discovery. Profile creation is not currently supported from Director CLI.

Profile creation using the Director Console

1. From the Director Console left pane, select Inventory -> Advanced System Discovery. Click on Create in the Advanced System Discovery that opens in the right pane.
2. Provide a profile name (for example, SMI-S) and select he System Type as Operating System. Click Next.
   
   Figure 1. Profile properties
   
   
   
3. Select the protocol as Storage Management Initiative Specification (SMI-S) Discovery and then click Next.
   
   Figure 2. Protocol selection
   
   
   
4. Select Direct Connection with the following properties:
   • Hardware Type as IBM System Storage DS3000/DS4000
   • Protocol as http
   • IP address as the AIX machine hostname or IP address
   • Port as 15988

   Click Next.

   
   
   Figure 3. SMIS-S configuration
   
   
   
5. Select Use the following user ID and password with the user ID and password of the AIX machine. Click Next.
   
   Figure 4. Access request
   
   
   
6. Select Automatically collect inventory, using the default inventory profile. Click Next.

1. Click Finish.

Troubleshooting tips if Provider is not discovered by Director

If Provider is not discovered by Director, check to ensure that Provider is registered with SLP using slp_query from the OpenPegasus SLP utility, which is found in the /opt/freeware/cimom/pegasus/bin directory.

Using slp_query:

slp_query --type=service:wbem 
–address=<ip_of_your_provider_host> --port=15988

If you do not find the service listing at 15988, then start slpd.

/opt/engenio/SMI_SProvider/aix51/slpd= of provider to get provider registered with slp.

Running Advanced System Discovery

After the profile is created, in the same Advanced System Discovery pane of the Director console, select the SMI-S profile (or the name of profile just created) and click Run. In the pop-up window, click OK.

Discovery, via the profile, can also be done using Director CLI. From the AIX machine command prompt run:

smcli discover –p <profile name>

Navigate resources

To verify if the Provider and the storage box have been discovered by Director, select Navigate Resources from the left pane of the Director console. In the Navigate Resources window that opens in right pane follow the path Groups by System Type -> Storage Systems. Clicking on SMI-S Provider displays all discovered Providers. Clicking on Storage Subsystems and Volumes displays the storage boxes added to Provider.

Using Director CLI verification can be done by:

smcli lsgp -N 'SMI-S Providers' -A GroupMembers

The previous command returns list of all SMI-S Providers discovered.

To display all storage systems that are discovered:

smcli lssys –o –t StorageSubystem

Remove Provider from Director

Since Provider is installed on the same machine as Director, removing the Provider by selecting it in Navigate Resources and deleting from there does not work.

In Navigate Resources, after navigating to the SMI-S Providers as described in the previous section, click on the SMI-S Provider which is to be removed. Click on the Inventory tab. In the Collected Items pane expand Network node. Click on Remote Service Access Point. Select the row with access type as SMI-S and click on Actions->Remove.

Back to top

Brief description of Director Storage-related commands

1. Getting storage subsystems OID

   smcli lssys –o –t StorageSubsystem

   
   
2. Collecting storage volumes inventory

   smcli collectinv -p "All Inventory" -i <Controller_IP> or smcli collectinv -p "All Inventory" -n <StorageSubsystem_OID>

   
   
3. Detailed list of storage subsystems, which includes its access state, status, and other properties.

   smcli lssys –l –t StorageSubsystem or

   
   

   smcli lsnssys gives output in XML.

4. Query storage volumes (output in XML)
   • Query all volumes of a storage box

     smcli lsnsvol –n <StorageSubsystem_OID>

     
     
   • Query specific storage volume

     smcli lsnsvol –n <StorageSubsystem_OID> -A nsvol="<StorageVolumeName>"

     
     
5. Query storage alerts

   smcli lsevtlog –l –t StorageSubsystem

   
   

Resources

Learn

• The AIX and UNIX developerWorks zone provides a wealth of information relating to all aspects of AIX systems administration.
  
  
• developerWorks technical events and webcasts: Stay current with developerWorks technical events and webcasts.
  
  
• Podcasts: Tune in and catch up with IBM technical experts.
  
  
• Managing and configuring storage includes information on the IBM Systems Director features, SMI-S providers, and external storage applications.
  
  
• LSI provider settings
  
  
• SMI-S tutorial link
  
  

Discuss

• Get involved in the My developerWorks community.
  
  
• Participate in the AIX and UNIX forums:
  • AIX Forum
  • AIX Forum for developers
  • Cluster Systems Management
  • IBM Support Assistant Forum
  • Performance Tools Forum
  • Virtualization Forum
  • More AIX and UNIX Forums
  
  

About the authors

Comments (Undergoing maintenance)

Back to top

Trademarks  |  My developerWorks terms and conditions

Table of contents

• Installation of LSI SMI-S Provider
• Configuring Provider
• Addition of Storage Subsystems to Provider
• Discovery of the SMI-S Provider using IBM Systems Director console
• Brief description of Director Storage-related commands
• Resources
• About the authors
• Comments

Local resources

• IBM Innovation Center - Austin, TX
• IBM Innovation Center - Chicago, IL
• IBM Innovation Center - Dallas, TX
• IBM Innovation Center - San Mateo, CA
• IBM Innovation Center - Waltham, MA
• Technical Briefings in North America

My developerWorks community

Dig deeper into AIX and UNIX on developerWorks

Calling all developers

Download no charge Lotus Domino Designer

Special offers