HP Insight Management 7.3 Support Matrix
Table Of Contents
- HP Insight Management 7.3 Support Matrix
- Contents
- 1 New and deprecated support
- 2 Management servers
- 3 Management servers in a high-availability environment
- 4 Managed systems hardware
- Public cloud providers
- Supported HP BladeSystem enclosures
- Supported servers
- Supported storage products
- Supported hardware network products
- HP Virtual Connect Enterprise Manager hardware
- Other supported hardware
- 5 Managed system firmware
- 6 Managed systems software
- 7 Managed systems agents and providers
- 8 Support and other resources
- Information to collect before contacting HP
- How to contact HP
- Security bulletin and alert policy for non-HP owned software components
- Registering for software technical support and update service
- HP authorized resellers
- New and changed information in this edition
- Related information
- Typographic conventions
- 9 Documentation feedback
- A Hardware requirements and supported capabilities for Insight Control power management
- B Hardware requirements and caveats for Insight Control server migration
- Storage controllers that Insight Control server migration supports
- Converged network adapters that Insight Control server migration supports
- Network interface cards that Insight Control server migration supports
- File system types that Insight Control server migration supports
- Caveats for Linux server migrations
- Supported storage adapters for manual boot of a destination virtual machine
- Additional Insight Control server migration information
- C Hardware requirements and caveats for Insight Control server provisioning
- D HP-UX CMS requirements
- Acronyms and abbreviations
- Index
Table 21 Supported databases (continued)
Supported
as a remote
database
Supported
as a local
database
Database name and version
1
✓✓Microsoft SQL Server 2012 Standard SP1
2
✓✓Microsoft SQL Server 2012 Enterprise SP1
2
✓✓Microsoft SQL Server 2012 Business Intelligence SP1
2
✓✓Microsoft SQL Server 2012 Web SP1
2
Oracle
✓✓
4
Oracle 11g Enterprise Edition Release 2
HP PolyServe Software
✓
4
HP PolyServe Software for Microsoft SQL Server
1
A clustered CMS requires a clustered instance of Microsoft SQL Server 2008 R2 Enterprise SP2, SQL Server 2012
Enterprise SP1 or SQL Server 2012 Standard SP1 edition. The instance may run in the CMS cluster or in another cluster
that is a member of the same domain as the CMS cluster.
2
Supports up to 5,000 systems and 50,000 events.
3
Supports up to 500 systems and 5,000 events.
4
Only Systems Insight Manager supports this database.
Supported CMS configurations in a Microsoft Windows domain
HP recommends that you adhere to the following guidelines for your single-server CMS configuration:
• Do not install Insight Management on domain controllers.
• If one server is in a workgroup, make sure that each server has a local account with the same
name and password (both for services and database credentials).
• Do not install Insight Control server deployment and the HP ProLiant Server OS Deployment
Toolkit for Microsoft System Center Configuration Manager (part of HP Insight Control for
Microsoft System Center) in the same subnet. Both of these provide their own separate PXE
boot services, and networking issues can arise if both are installed on the same subnet at the
same time.
• Do not install Insight Control server deployment and an HP Ignite-UX server on the same subnet.
• Matrix OE uses Microsoft Windows Single Sign-On (SSO) authentication for the Matrix OE
services/processes database connectivity. HP recommends that you use the same Microsoft
Windows domain account credentials for both the Systems Insight Manager installation, the
Matrix OE installation, and the database access.
A CMS configuration can contain two separate databases, which can be local or remote:
• A CMS database for the CMS to store information about all managed devices
• A deployment server database that stores the inventory and state information about managed
systems (if you install the Insight Control server deployment software)
The databases can be local to the CMS or can be located on a remote system. The CMS and the
SQL Server database servers can either be in the same domain or in a trusted domain.
NOTE: This release of Insight Management also supports the configuration of the CMS as a
two-node failover cluster. For more information about a CMS configuration in a high-availability
environment, see “Management servers in a high-availability environment” (page 23).
20 Management servers