HP P2000 HP P2000 G3 MSA System SMU Reference Guide - Page 144

SMI-S implementation, About the P2000 G3 MSA System SMI-S provider

Get HP P2000 PDF manuals and user guides View all HP P2000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 144 highlights

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 actually communicates to a particular type of managed resource (for example, HP MSA arrays), and provides the CIMOM with information about them. In theory, providers for multiple types of devices (for example, HP MSA arrays 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. About the P2000 G3 MSA System SMI-S provider The P2000 G3 MSA System 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. NOTE: Active management features such as RAID provisioning are not supported in this release. The embedded CIMOM listens to SMI-S queries from the clients only on port 5989 and requires that the credentials be provided for all queries. This provider implementation complies with the SNIA SMI-S specification version 1.3.0. The namespace details are given below. • Implementation Namespace - root/hpq • Interop Namespace - root/interop The embedded provider set includes the following providers: • Instance Provider • Association Provider • Method Provider • Indication Provider The embedded provider supports the following CIM operations: • getClass • enumerateClasses • enumerateClassNames • getInstance • enumerateInstances • enumerateInstaneceNames • associators • associatorNames • references • referenceNames • invokeMethod 144 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
144
Using SMI-S
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 actually communicates to a particular type of managed resource (for example, HP
MSA arrays), and provides the CIMOM with information about them. In theory, providers for multiple
types of devices (for example, HP MSA arrays 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.
About the P2000 G3 MSA System SMI-S provider
The P2000 G3 MSA System 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.
NOTE:
Active management features such as RAID provisioning are not supported in this release.
The embedded CIMOM listens to SMI-S queries from the clients only on port 5989 and requires that the
credentials be provided for all queries. This provider implementation complies with the SNIA SMI-S
specification version 1.3.0.
The namespace details are given below.
•
Implementation Namespace -
root/hpq
•
Interop Namespace -
root/interop
The embedded provider set includes the following providers:
•
Instance Provider
•
Association Provider
•
Method Provider
•
Indication Provider
The embedded provider supports the following CIM operations:
•
getClass
•
enumerateClasses
•
enumerateClassNames
•
getInstance
•
enumerateInstances
•
enumerateInstaneceNames
•
associators
•
associatorNames
•
references
•
referenceNames
•
invokeMethod