HP Insight Management 7.3 Update 1 Support Matrix

Table 6 CMS management capabilities (continued)
Maximum configuration on an x64 CMSItem
Capacity Advisor Data Collection
• Capacity planning data collected for 1,500 nodes
• Automated recommendations for 500 workloads in <15 minutes
• Detailed reports for 150 systems in <15 minutes
• Summary reports for 1,000 systems in <10 minutes
Up to 250 single or multi-enclosure domains, up to a total of 1,000 BladeSystem c-Class
enclosures
Virtual Connect Enterprise Manager
domains
CMS firmware
Table 7 Recommended firmware requirements for Insight Management
Recommended firmware versionItem
2014.02Service Pack for ProLiant
4.11Onboard Administrator (OA) on the following HP BladeSystem
enclosures:
• c3000
• c3000 Tower enclosure
• c7000
• c7000 Platinum enclosure
4.10Virtual Connect for BladeSystem c-Class
NOTE: To download Virtual Connect firmware only, go to the following website:
http://h18004.www1.hp.com/products/blades/components/vc-
For Virtual Connect firmware compatible with the Virtual Connect Enterprise Manager, see the HP Virtual Connect Enterprise
Manager User Guide at the following website:
http://www.hp.com/go/insightmanagement/sim/docs
2.23HP iLO 2 for ProLiant BladeSystem
1.70HP iLO 3 Advanced for ProLiant BladeSystem
1.40HP iLO 4 Advanced for ProLiant BladeSystem
5.38Baseboard Management Controller (BMC) Firmware
6.20HP Smart Update Manager (HP SUM)
NOTE: OA 4.11 should be used for enclosures with ProLiant, Integrity, or a mix of ProLiant and
Integrity server blades.
Insight Control server provisioning hardware
Insight Control server provisioning is a VM appliance that runs on a separate VMware vSphere
(ESXi) or Microsoft Hyper-V host. It requires two IP addresses; a management address that is used
to connect to the appliance web interface and REST API, and a deployment IP that is used for
communicating with the target servers. The appliance can be configured in either single NIC
configuration where the two IPs share the same NIC, or a dual NIC configuration where each IP
is on a separate NIC.
In a single NIC configuration, both IP addresses must be in the same subnet and must have
connectivity to the target servers, the target server iLOs, and the media server. In a dual NIC
configuration, NIC1 is considered the management NIC and is used to connect to the appliance.
NIC2 is considered the deployment NIC and must have connectivity to the deployment NIC on
Hardware and firmware 13