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
Unsupported items in a CMS cluster configuration
• Brocade Network Advisor, HP P6000 Command View Software, HP Operations Orchestration,
VMware vCenter Server, and similar applications are not permitted in a CMS cluster
• Multi-site Windows cluster: a CMS cluster is a single site cluster.
Matrix KVM Private Cloud in a HA environment
The Matrix KVM Admin Console appliance can be configured as a single-site, two-node physical
server RHEL KVM 6.3 or RHEL KVM 6.4 cluster to create a highly-available environment.
Four networks are required for the cluster Management hosts and Matrix KVM Admin Console
appliance:
Table 24 Matrix KVM Private Cloud clustering network requirements
DescriptionNetwork
A public network for user management and Matrix OE
access.
Matrix Operating Environment Access network (Private
subnet for instances) and Matrix KVM Private Cloud
Production network (Cloud connectivity subnet)
1
A private network for the Matrix KVM Private Cloud to
communicate with the OpenStack managed KVM hosts.
Matrix KVM Private Cloud Management network (Host
management subnet)
A private Matrix OE network for deployment of operating
systems on the physical KVM hosts.
Matrix Operating Environment Deployment network
A private network for the cluster communication and
heartbeat.
Cluster Heartbeat network
1
The two networks can be separate if isolation is needed.
NOTE: After deploying the management KVM Host operating system onto each of the cluster
nodes, the Matrix OE Deployment network connection is repurposed to become one of the
connections in the Cluster Heartbeat network bonded pair.
Three pieces of storage are used in the cluster:
• Matrix KVM Private Cloud root storage
• Glance OS image storage
• Cluster quorum disk
Matrix KVM Private Cloud in a HA environment 25