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

What’s new in this release?, What is the architecture?, What CIM operations are supported?

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 148 highlights

What's new in this release? SMI-S 1.3 Array Provider support introduced in T230 (passes 100% CTP 1.3 tests): • Support for Block Server Performance subprofile • 20x-30x performance improvements • HP SIM 6.3 subscribe to WBEM events functionality is supported (TS230 and above) • Fixed removal of indication subscription • Fixed: Performance of associator commands is slower than the previous provider. • Fixed: Memory leak causes SMI-S to restart. • Fixed: Value/ValueMaps are not implemented via getClass. TS210 support for SMI-S 1.3 Array Provider (passed 85% of CTP 1.3 tests): • Support for LUN masking and mapping extrinsic methods (ExposePaths, HidePaths, CreateStorageHardwareID, DeleteStorageHardwareID) • SFCB v1.3.7 CIMOM with v2.22.1 MOFs • Support for Server profile • Fixed: Property lists do not return correct list. TS200/201 support for SMI-S 1.3 Array Provider (passed 65% of CTP 1.3 tests): • Alert Indications with events sent back to the client using HTTP. • Support for Extent Composition subprofile • Support for iSCSI and SAS Target Port subprofiles • Support for Masking and Mapping subprofile (monitor only) • SLP v2 Discovery • Performance Improvement • SFCB v1.3.7 CIMOM with v2.22.1 MOFs TS100 (February 2010) - SMI-S 1.3 Array Provider: • SFCB v1.3.5 CIMOM with v2.22.1 MOFs What is the architecture? The architecture requirements for the embedded SMI-S Array provider are to work within the MC architecture, use limited disk space, use limited memory resources and be as fast as a proxy provider running on a server. The provider is an MC application and works by making MC CLI requests. An SMI-S cache caches these requests for 30 to 60 seconds. The disk space used is about 3 MB without qualifiers and 8 MB with qualifiers. The CIMOM (Common Information Model Object Manager) used is the open source SFCB (Small Footprint CIM Broker) 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. What CIM operations are supported? SFCB provides a full set of CIM operations including GetClass, ModifyClass, CreateClass, DeleteClass, EnumerateClasses, EnumerateClassNames, GetInstance, DeleteInstance, CreateInstance, ModifyInstance, EnumerateInstances, EnumerateInstanceNames, InvokeMethod (MethodCall), ExecQuery, Associators, AssociatorNames, References, ReferenceNames, GetQualifier, SetQualifier, DeleteQualifier, EnumerateQualifiers, GetProperty and SetProperty. Is the product CTP-certified? We are working towards being CTP 1.3 certified and may pass the CTP 1.3 tests at the time TS230 is released. 148 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
148
Using SMI-S
What’s new in this release?
SMI-S 1.3 Array Provider support introduced in T230 (passes 100% CTP 1.3 tests):
•
Support for Block Server Performance subprofile
•
20x-30x performance improvements
•
HP SIM 6.3 subscribe to WBEM events functionality is supported (TS230 and above)
•
Fixed removal of indication subscription
•
Fixed: Performance of associator commands is slower than the previous provider.
•
Fixed: Memory leak causes SMI-S to restart.
•
Fixed: Value/ValueMaps are not implemented via getClass.
TS210 support for SMI-S 1.3 Array Provider (passed 85% of CTP 1.3 tests):
•
Support for LUN masking and mapping extrinsic methods (ExposePaths, HidePaths,
CreateStorageHardwareID, DeleteStorageHardwareID)
•
SFCB v1.3.7 CIMOM with v2.22.1 MOFs
•
Support for Server profile
•
Fixed: Property lists do not return correct list.
TS200/201 support for SMI-S 1.3 Array Provider (passed 65% of CTP 1.3 tests):
•
Alert Indications with events sent back to the client using HTTP.
•
Support for Extent Composition subprofile
•
Support for iSCSI and SAS Target Port subprofiles
•
Support for Masking and Mapping subprofile (monitor only)
•
SLP v2 Discovery
•
Performance Improvement
•
SFCB v1.3.7 CIMOM with v2.22.1 MOFs
TS100 (February 2010) - SMI-S 1.3 Array Provider:
•
SFCB v1.3.5 CIMOM with v2.22.1 MOFs
What is the architecture?
The architecture requirements for the embedded SMI-S Array provider are to work within the MC
architecture, use limited disk space, use limited memory resources and be as fast as a proxy provider
running on a server. The provider is an MC application and works by making MC CLI requests. An SMI-S
cache caches these requests for 30 to 60 seconds. The disk space used is about 3 MB without qualifiers
and 8 MB with qualifiers. The CIMOM (Common Information Model Object Manager) used is the open
source SFCB (Small Footprint CIM Broker) 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
.
What CIM operations are supported?
SFCB provides a full set of CIM operations including GetClass, ModifyClass, CreateClass, DeleteClass,
EnumerateClasses, EnumerateClassNames, GetInstance, DeleteInstance, CreateInstance, ModifyInstance,
EnumerateInstances, EnumerateInstanceNames, InvokeMethod (MethodCall), ExecQuery, Associators,
AssociatorNames, References, ReferenceNames, GetQualifier, SetQualifier, DeleteQualifier,
EnumerateQualifiers, GetProperty and SetProperty.
Is the product CTP-certified?
We are working towards being CTP 1.3 certified and may pass the CTP 1.3 tests at the time TS230 is
released.