HP MSA 1040 HP MSA 1040 SMU Reference Guide (762784-001, March 2014) - Page 168

SMI-S implementation, SMI-S architecture, About the MSA 1040 SMI-S provider

Page 168 highlights

• Software Inventory subprofile • Block Server Performance subprofile • Copy Services subprofile • Job Control subprofile • Storage Enclosure subprofile (if expansion enclosures are attached) • Disk Sparing subprofile • Object Manager Adapter subprofile The embedded SMI-S provider supports: • HTTPS using SSL encryption on the default port 5989, or standard HTTP on the default port 5988. Both ports cannot be enabled at the same time. • SLPv2 • CIM Alert and Lifecycle indications • Microsoft Windows Server 2012 Server Manager and System Center Virtual Machine Manager SMI-S implementation SMI-S is implemented with the following components: • CIM server (called a CIM Object Manager or CIMOM), which listens for WBEM requests (CIM operations over HTTP) from a CIM client, and responds. • CIM provider, which communicates to a particular type of managed resource (for example, MSA 1040 storage systems), and provides the CIMOM with information about them. In theory, providers for multiple types of devices (for example, MSA 1040 storage systems and Brocade switches) can be plugged into the same CIMOM. However, in practice, all storage vendors provide the CIMOM and a single provider together, and they do not co-exist well with solutions from other vendors. These components may be provided in several different ways: • Embedded agent: The hardware device has an embedded SMI-S agent. No other installation of software is required to enable management of the device. • SMI solution: The hardware or software ships with an agent that is installed on a host. The agent needs to connect to the device and obtain unique identifying information. SMI-S architecture The architecture requirements for the embedded SMI-S Array provider are to work within the Management Controller (MC) architecture, use limited disk space, use limited memory resources and be as fast as a proxy provider running on a server. The CIMOM used is the open source SFCB CIMOM. SFCB is a lightweight CIM daemon that responds to CIM client requests and supports the standard CIM XML over http/https protocol. The provider is a CMPI (Common Management Protocol Interface) provider and uses this interface. To reduce the memory footprint, a third-party package called CIMPLE (www.simplewbem.org) is used. For more information on SFCB go to sblim.cvs.sourceforge.net/sblim/sfcb/README?view=markup. About the MSA 1040 SMI-S provider The GL105 provider is a SMI-S 1.5 provider which passes CTP 1.5 tests. Full provisioning is supported. The MSA 1040 SMI-S provider is a full-fledged embedded provider implemented in the firmware. It provides an industry-standard WBEM-based management framework. SMI-S clients can interact with this embedded provider directly and do not need an intermediate proxy provider. The provider supports active management features such as RAID provisioning. MSA 1040 and SAS systems are supported. The classes for HP are HP_XXX. The device namespace for HP is /root/hpq. The embedded CIMOM can be configured either to listen to secure SMI-S queries from the clients on port 5989 and require credentials to be provided for all queries, or to listen to unsecure SMI-S queries from the clients on port 5988. This provider implementation complies with the SNIA SMI-S specification version 1.5.0. 168 Using SMI-S

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190

168
Using SMI-S
Software Inventory subprofile
Block Server Performance subprofile
Copy Services subprofile
Job Control subprofile
Storage Enclosure subprofile (if expansion enclosures are attached)
Disk Sparing subprofile
Object Manager Adapter subprofile
The embedded SMI-S provider supports:
HTTPS using SSL encryption on the default port 5989, or standard HTTP on the default port 5988. Both ports
cannot be enabled at the same time.
SLPv2
CIM Alert and Lifecycle indications
Microsoft Windows Server 2012 Server Manager and System Center Virtual Machine Manager
SMI-S implementation
SMI-S is implemented with the following components:
CIM server (called a CIM Object Manager or CIMOM), which listens for WBEM requests (CIM operations over
HTTP) from a CIM client, and responds.
CIM provider, which communicates to a particular type of managed resource (for example, MSA 1040 storage
systems), and provides the CIMOM with information about them. In theory, providers for multiple types of
devices (for example, MSA 1040 storage systems and Brocade switches) can be plugged into the same
CIMOM. However, in practice, all storage vendors provide the CIMOM and a single provider together, and
they do not co-exist well with solutions from other vendors.
These components may be provided in several different ways:
Embedded agent: The hardware device has an embedded SMI-S agent. No other installation of software is
required to enable management of the device.
SMI solution: The hardware or software ships with an agent that is installed on a host. The agent needs to connect
to the device and obtain unique identifying information.
SMI-S architecture
The architecture requirements for the embedded SMI-S Array provider are to work within the Management Controller
(MC) architecture, use limited disk space, use limited memory resources and be as fast as a proxy provider running
on a server. The CIMOM used is the open source SFCB CIMOM.
SFCB is a lightweight CIM daemon that responds to CIM client requests and supports the standard CIM XML over
http/https
protocol. The provider is a CMPI (Common Management Protocol Interface) provider and uses this
interface. To reduce the memory footprint, a third-party package called CIMPLE (
www.simplewbem.org
) is used. For
more information on SFCB go to
sblim.cvs.sourceforge.net/sblim/sfcb/README?view=markup
.
About the MSA 1040 SMI-S provider
The GL105 provider is a SMI-S 1.5 provider which passes CTP 1.5 tests. Full provisioning is supported.
The MSA 1040 SMI-S provider is a full-fledged embedded provider implemented in the firmware. It provides an
industry-standard WBEM-based management framework. SMI-S clients can interact with this embedded provider
directly and do not need an intermediate proxy provider. The provider supports active management features such as
RAID provisioning.
MSA 1040 and SAS systems are supported. The classes for HP are
HP_XXX
. The device namespace for HP is
/root/hpq
.
The embedded CIMOM can be configured either to listen to secure SMI-S queries from the clients on port 5989 and
require credentials to be provided for all queries, or to listen to unsecure SMI-S queries from the clients on port 5988.
This provider implementation complies with the SNIA SMI-S specification version 1.5.0.