Supported SMI-S Levels by Release
Table 11 Supported SMI-S Levels by Release
HP 3PAR OS
Release/ SMI-S
Version
Profile
Server Profile
2.3.1/
1.1.0
Array Profile
Subprofile/.Package
x
Profile Registration
Software
Block Services
Physical Package x x
Masking & Mapping x
FC Target Ports
FC Initiator Ports
Location
Mulitple Computer
System x x x x
Disk Drive Lite iSCSI Target Ports
Block Server
Performance
Copy Services
Job Control x x x x x
Thin Provisioning
Replication Services
SAS Initiator Ports
Indication x x
3.1.1/ 1.4.0
3.1.2/ 1.4.0
3.1.3/ 1.5.0
x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x
3.2.1/ 1.5.0
x x x x x x x x x x x x x x x x x x x x
Discovery Service
The first step in managing an SMI-S enabled SAN is to discover its available resources (such as the CIM servers). SMI-S defines Service Location Protocol v2 (SLPv2) as the discovery mechanism.
CIM clients use SLP to query for available CIM servers. CIM servers answer with generic information about what services they provide and the URL at which these services reside.
Server Profile
A CIM Server is anything that supports the CIM-XML protocol and supports the basic read functional profile as defined by the CIM Operations over HTTP specification. After a CIM client has discovered a CIM server within a SAN, it then needs to determine the services provided by that server. The
Server Profile defines the capabilities of the CIM Server. This includes the communication mechanisms the CIM Server supports, the CIM namespaces that it manages, and the SMI-S profiles and subprofiles that are supported.
For a complete discussion on the Server Profile model, please refer to SMI-S at http://www.snla.org
.
Server Profile 17
