How to support SMI-S 5.2.6 P2 and above

Applies to

•  NetApp Storage Management Initiative Specification (SMI-S) Provider 5.2.6 P2 and above (Released on Nov 2024)
• Common Information Model Object Manager (CIMOM)
• Common Information Model (CIM) Server 

Description

• NetApp SMI-S provider is a tool that enables you to manage and monitor NetApp Storage systems to
  • Manage LUNs and Volumes,
  • CIMOM configuration settings
  • and CIM Server Users
• SMI-S is a command based interface that supports System Center 2016,2019,2022

SMI-S consists of 3 components 

• CIMOM

  This is the foundation for NetApp SMI-S Provider. CIMOM collects, validates, and authenticates each application request and then responds to the application. It becomes a conduit for each request by invoking the appropriate provider to handle each request.

• Provider objects

  When a host issues a command or query to SMI-S Provider, CIMOM loads a shared library object, invokes it to handle a request, and returns the resulting information to the host.

• Repository

  CIMOM uses a flat-file database for its repository. It stores persistent data required at the CIM level.

Procedure

How NetApp SMI-S provider interacts with a Host

When a client application on a host discovers the CIMOM server by using SLP (CIM-XML encoding over HTTP), the client then queries the CIMOM for shared objects (objects modeled in the CIM language). The CIMOM loads shared objects and queries the storage system by using device-specific APIs for the requested information.

The following illustration shows how NetApp SMI-S Provider interacts with a WBEM management client when SMI-S Provider receives a query or command.

What is the deployment workflow 

Before you can manage and monitor your storage systems using SMI-S Provider, you must install the SMI-S Provider software and validate your preliminary configuration.

Installation is done on a Windows server and where the path of installment is C:\Program Files (x86)\NetApp\smis\pegasus

How to verify if the installation was done correctly

1. Log in as Administrator on Windows.

2. Access NetApp SMI-S Provider by navigating to the directory where the executables reside:

   If you are using…​	Then do this…​
   Command prompt (with elevated administrative privileges)	Navigate to C:\Program Files (x86)\NetApp\smis\pegasus\bin
   Start > Programs menu	Right-click NetApp SMI-S Provider and select Run as Administrator.

3. View the CIM server status:

   smis cimserver status

   If the CIM server has been started, the following message is displayed:

   NetApp SMI-S Provider is running.

Add a CIM server User

1. Create a local user account. (Local users and groups)

2. Add the user to the Administrators group.

   For more information, see System documentation.

3. Add a CIM server user:

   cimuser -a -u user_name

   For example, to add a CIM server user named “chris”:

   cimuser -a -u chris

4. When prompted, enter and reenter the password.

Adding a storage system to SMI-S

For ONTAP, you must specify a management IP address for an SVM, not a cluster IP address, and you must provide the credentials for a vsadmin user.

SMI-S Provider does not support cluster IP addresses or node management IP addresses, nor does it support node admin or node SVMs.

1. Add at least one storage system to the CIMOM repository:

   To add a storage system with an…​	Enter this command…​
   HTTP connection between the provider and the storage system	smis add storage_sys storage_sys_user
   HTTPS connection between the provider and the storage system	smis addsecure storage_sys storage_sys_user

   The command waits for up to 15 minutes for the provider to update the cache and respond.

2. Verify the output for the following commands:

   For this command…​	Verify that…​
   smis list	The number of items matches the number of storage systems being managed.
   smis disks	The number of disks matches the total number of disks on all storage systems.
   smis luns	The number of LUNs matches the total number of LUNs on all storage systems.
   smis pools	The number of ONTAP_ConcretePools matches the total number of aggregates on all storage systems.
   smis volumes	The number of volumes matches the total number of volumes on all storage systems.

How to manage a CIM server (stop start services)

Complete one of the following actions:

Troubleshooting SMI-S Provider

• A extensive list of troubleshooting are allready defined by Engineering and these can be found on the doc page, in the troubleshooting section.
• Also a lab exists in Lab On Demand (270) for Hyper-V with SMI-S provider installed on the jumphost

Where error messages are logged and how to collect the logs files1

By default, all system messages are logged. In addition, by default, the system message logs are located in the logs directory in the directory in which NetApp SMI-S Provider is installed. You can change the location of and the level of system messages that are written to the CIM server log. For example, you can choose to have logs stored in a directory that you specify and have only fatal system messages written to the CIM server log.
Before you begin

1. 1. 1. Access NetApp SMI-S Provider.

      2. Complete one of the following actions:

         Action	Command	Additional information
         Change the system message logging level	cimconfig -s logLevel=new_log_level -p	If you wanted to change the logging level to “INFORMATION”, for example, you would input this command: cimconfig -s logLevel=INFORMATION -p
         Change the system message log directory	cimconfig -s logdir=new_log_directory -p If the new_log_directory contains space, you must enclose it in quotation marks ("new log directory").	If you wanted to change the log directory to “serverlogs”, for example, you would input this command: cimconfig -s logdir=serverlogs -p

      3. Restart the CIM server:

         smis cimserver restart

• Document logs that can and should be used to confirm the operation of the product and troubleshoot technical issues.
  • Document common log content (with examples) of what a TSE should expect to see.

You can specify the types of messages that are logged (for example, you want only fatal system messages to be logged).

You can configure the logging level to one of the following:

• • • TRACE

      Saves trace messages in the cimserver_standard log.

    • INFORMATION

      Logs all (informational, warning, severe, and fatal) system messages.

    • WARNING

      Logs warning, severe, and fatal system messages.

    • SEVERE

      Logs severe and fatal system messages

    • FATAL

      Logs only fatal system messages.

• • Where are the logs stored?
    •  by default, the system message logs are located in the logs directory in the directory in which NetApp SMI-S Provider is installed

  • How can the logs be viewed?

    • Logs can be viewed from the mentioned directory in txt format

Additional Information

• TOI on Confluence for SMI-S 5.2.6P2
• SMI-S data provider documentation
• Lab On Demand (270) for Hyper-V with SMI-S provider installed on the jumphost