- Community Home
- >
- Software
- >
- HPE OneView
- >
- Typical Deployment Scenarios
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2022 08:32 AM
03-22-2022 08:32 AM
Typical Deployment Scenarios
I'm researching HPE OneView and trying to determine what are typcial deployment scenarios.
In a enterprise with mulitple datacenters, would one virtual appliance be deployed per datacenter? Are there parent-child relationships with multiple OneView deployments?
- Tags:
- deployment
- OneView
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2022 09:55 PM
03-22-2022 09:55 PM
Re: Typical Deployment Scenarios
Hello, OneView has two basic functions: To monitor or to manage.
If you only want to monitor your servers, you may only use 1 appliance, following the limits in regards to the maximun amount of devices. For example, version 6.3 can monitor up to 1024 servers.
But if you want OneView to manage your devices, then it'll be better to have one appliance per datacenter.
And then, you have other option, OneView Global Dashboard, so all the OV appliances you may deploy will report into one central console, hence the name Global Dashboard.
Also, OV offers different "Partner Integrations" or plugins for VMware and Microsoft, such as:
HPE OneView for VMware vCenter (OV4VC)
HPE OneView for VMware vRealize Operations (OV4VROPS)
HPE OneView for VMware vRealize Orchestrator (OV4VRO)
HPE OneView for Microsoft System Center (OV4SC)
HPE OneView for Microsoft Azure Log Analytics (OV4ALA)
But it all depends on what exactly are you looking for from this appliance.
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2022 02:44 AM
03-23-2022 02:44 AM
Re: Typical Deployment Scenarios
We have multiple geographically dispersed data centers. We run three OneView instances with a few of the smaller datacenters reporting to the closest instance. We run our systems in managed mode. We also have a OneView global dashboard setup, but honestly I never use it. Sure it is good for giving you an overall picture, but it can't really do anything. You have to go to the controlling OneView instance to actually do something to that remote server. I open a vnc session to a gui server at each datacenter where we have a OneView instance then bring up OneView in that vnc session.
I think the biggest thing that OneView gives us is uniformity within a datacenter among like server models. That is, for example, we create a server profile template for all DL380 Gen10's in datacenter X. It defines all of the BIOS and iLO settings and firmware bundle to apply to all DL380 Gen10's. That way they are all set the same and we don't have to worry about anyone forgetting a setting or making a typo.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2022 07:44 AM
03-23-2022 07:44 AM
Re: Typical Deployment Scenarios
Thanks for the replies.
I like the remote support functions as well as the ability to update/report on the firmware of servers in it.
I think I'll look at the one deployment per datacenter model and go on from there.