CIM agent classes, methods, and SMI-S profiles supported

The CIM agent classes are the building blocks of the Common Information Model (CIM) agent and use functions such as storage configuration, Copy Services, and logical unit number (LUN) masking. The Storage Management Initiative Specification (SMI-S) is based on a number of existing technologies that include the CIM.

The CIM agent with Azure Site Recovery protects applications through replication coordination services and physical (or virtual) machine recovery. You can replicate data from your data center to a hosting service provider. (This way you do not have to build and manage a secondary location.) The CIM Agent and Azure Site Recovery uses replication features through SMI-S to use site protection and it starts SMI-S APIs within the service profile.

This integration provides:

Protection
Failover
Reverse protection
Test failover

The CIM Agent and Azure Site Recovery can also replicate data to or from (or between) virtual machines. This replication ability includes replicating data from on-premises Hyper-V host servers that are located in a VMM cloud to a secondary VMM server in a remote data center.

To view the complete Managed Object Format (MOF) documentation of these classes and methods, select the documentation information from the following website:

https://datacentersupport.lenovo.com/

This table identifies the SMI-S profiles that the CIM agent supports for the system.

Table 1. SMI-S profiles and subprofiles that are supported by CIM.
SMI-S profiles and subprofiles that are supported by CIM
Profiles	Subprofiles
SNIA:Storage Virtualizer Storage virtualizers act in a manner similar to RAID arrays but can use storage that is provided by systems that are external to the storage virtualizer and local disks. A storage virtualizer system combines both remote and local storage to create a seamless pool. The virtualization system allocates volumes from the pool for host systems to use. The basic virtualizer system profile provides a read-only view of the system. The various subprofiles extend this description and also enable configuration.	SNIA:Storage Virtualizer:Access Points
	SNIA:Storage Virtualizer:Block Server Performance
	SNIA:Storage Virtualizer:Block Services
	SNIA:Storage Virtualizer:Thin Provisioning
	SNIA:Storage Virtualizer:Cascading
	SNIA:Storage Virtualizer:Copy Services
	SNIA:Storage Virtualizer:Replication Services
	SNIA:Storage Virtualizer:Disk Drive Lite
	SNIA:Storage Virtualizer:Disk Sparing
	SNIA:Storage Virtualizer:Extent Composition
	SNIA:Storage Virtualizer:FC Initiator Ports
	SNIA:Storage Virtualizer:FC Target Ports
	SNIA:Storage Virtualizer:Health
	SNIA:Storage Virtualizer:iSCSI
	SNIA:Storage Virtualizer:Location
	SNIA:Storage Virtualizer:Masking and Mapping
	SNIA:Storage Virtualizer:Multiple Computer System
	SNIA:Storage Virtualizer:Physical Package
	SNIA:Storage Virtualizer:RAID
	SNIA:Storage Virtualizer:Software
SNIA:Server The server profile is mandatory for all compliant SMI-S servers. The object manager part of the model defines the capabilities of a CIM object manager based on the communication mechanisms that it supports.	SNIA:Server:Profile Registration
	SNIA:Server:Indication
	SNIA:Server:Object Manager Adapter