- Notes, cautions, and warnings
- Revision history
- Preface
- Overview
- Deployment
- Getting started
- System configuration
- Configure network settings
- Manage users, roles, and scopes
- Ending user sessions
- Directory services integration
- Login using OIDC providers
- Security certificates
- Manage console settings
- Set the login security properties
- Customize the alert display
- Configure SMTP, SNMP, and Syslog
- Manage incoming alerts
- Manage warranty settings
- Configure remote commands and scripts
- OpenManage Mobile settings
- Enable or disable alert notifications for OpenManage Mobile
- Enable or disable OpenManage Mobile subscribers
- Delete an OpenManage Mobile subscriber
- View the alert notification service status
- Notification service status
- View information about OpenManage Mobile subscribers
- OpenManage Mobile subscriber information
- Troubleshooting OpenManage Mobile
- Discovering devices
- Server-initiated discovery
- Create a device discovery job
- Protocol support matrix for discovering devices
- View device discovery job details
- Edit a device discovery job
- Run a device discovery job
- Stop a device discovery job
- Discover multiple devices by .csv import
- Global exclusion of ranges
- Specify a discovery mode for server discovery
- Create a custom discovery job for servers
- Specify discovery mode for chassis discovery
- Create a custom discovery job for the chassis
- Specify discovery mode for Dell storage discovery
- Specify discovery mode for network switch discovery
- Create a custom discovery job for HTTPS storage devices
- Create a custom discovery job for SSH devices
- Create a custom discovery job for SNMP devices
- Specify the discovery mode for multiple discovery jobs
- Delete a device discovery job
- Managing devices and device groups
- Organize devices into groups
- Create a custom static or query group
- Create a static device group
- Create a query device group
- Edit a static group
- Edit a query group
- Rename a static or query group
- Delete a static or query device group
- Clone a static or query group
- Add devices to a new group
- Add devices to existing group
- Refresh health on group
- All Devices screen device list
- All Devices screen actions
- Delete devices from OpenManage Enterprise
- Exclude devices from OpenManage Enterprise
- Run inventory on devices
- Update the device firmware and drivers by using baselines
- Refresh the device health of a device group
- Refresh health on devices
- Roll back an individual device's firmware version
- Export the single device inventory
- Performing more actions on chassis and servers
- Hardware information displayed for MX7000 chassis
- Export data
- View and configure individual devices
- Organize devices into groups
- Managing device inventory
- Managing device firmware and drivers
- Managing device deployment templates
- Create a deployment template from a reference device
- Create a deployment template by importing a template file
- View a deployment template information
- Edit a server deployment template
- Edit a chassis deployment template
- Edit IOA deployment template
- Edit network properties of a deployment template
- Deploy device deployment templates
- Deploy IOA deployment templates
- Clone deployment templates
- Auto deploy device configuration before discovery
- Create auto deployment targets
- Delete auto deployment targets
- Export auto deployed target details
- Overview of stateless deployment
- Define networks
- Edit or delete a configured network
- Export VLAN definitions
- Import network definitions
- Managing device warranty
- Managing alerts
- Managing MIB files
- Configuring profiles
- Configuration compliance
- Using jobs for device control
- Monitoring audit logs
- Monitoring reports
- Back up, restore, or migrate
- Updating the console and plugins
- Managing plugins
- Troubleshooting
- Troubleshooting connectivity
- Firmware and DSU requirements for HTTPS
- Firmware schedule reference
- Firmware baseline field definitions
- Supported and unsupported actions on proxied sleds
- Schedule job field definitions
- Alert categories after EEMI relocation
- Token substitution in remote scripts and alert policy
- Catalog Management field definitions
- Devices with unknown compliance status
- Device rediscovery running for a long time after deleting iDRAC service account
- Dell Connectivity Service : Failed with exception: Unable to get access token from DCS
OpenManage Enterprise 4.0.x User's Guide
OpenManage Enterprise hardware requirements
The section provides recommended hardware requirements for OpenManage Enterprise running with and without plug-ins in small and large deployments. For more specific information about plug-in hardware requirements, see the User's Guide of the respective OpenManage Enterprise plug-in.
Maximum recommended hardware configuration
Starting from the OpenManage Enterprise 4.0 version, the appliance is shipped with the maximum recommended hardware requirements to provide you a hassle-free deployment and installation of the appliance and plug-ins respectively. However, if your environment does not require the maximum hardware configuration, see Manage hardware requirements to determine the appropriate hardware resources required for your specific requirements. The following table lists recommended hardware requirements for installing OpenManage Enterprise and all of its plugins.
| Hardware | Configuration |
|---|---|
| RAM | 64 GB |
| Processor cores | 8 |
| Hard drive space | 830 GB 1 |
Manage memory and CPU requirements based on deployment size
If your environment does not require the maximum hardware configuration, review the following table to determine the appropriate hardware resources required for your specific requirements.
| OpenManage Enterprise appliance and plugins | Minimum RAM 2 | Minimum cores |
|---|---|---|
| OpenManage Enterprise | 32 GB | 8 |
| Additional requirements for each plug-in | ||
| CloudIQ plug-in (Default plug-in) | +4 GB | |
| Services (Default plug-in) | +8 GB | |
| Power Manager | +8 GB | |
| Update Manager | +1 GB | |
| OpenManage Enterprise Integration for VMware vCenter (OMEVV) | +5 GB | |
| Operations Manager (Integration for Microsoft SCOM) | +3 GB | |
| VMM and Configuration Manager (Integration for Microsoft SCVMM and MCM) | +1 GB | |
| Total recommended hardware configuration with all plug-ins installed | 64 GB | 8 CPU cores |
| OpenManage Enterprise appliance and plugins | Minimum RAM 3 | Minimum cores |
|---|---|---|
| OpenManage Enterprise | 16 GB | 4 |
| Additional requirements for each plug-in | ||
| CloudIQ plug-in (Default plug-in) | +2 GB | |
| Services (Default plug-in) | +8 GB | |
| Power Manager | +3 GB | |
| Update Manager | +1 GB | |
| OpenManage Enterprise Integration for VMware vCenter (OMEVV) | +5 GB | |
| Operations Manager (Integration for Microsoft SCOM) | +3 GB | |
| VMM and Configuration Manager (Integration for Microsoft SCVMM and MCM) | +1 GB | |
| Total recommended hardware configuration with all plug-ins istalled | 40 GB | 4 CPU cores |
1
- OpenManage Enterprise appliance is configured with two VDs, each with an initial storage space of 415 GB. The primary VD is leveraged for the core application and database while the secondary VD is required for additional features and supporting plugins. However, even without the secondary VDs selected during deployment, the appliance can still boot up for TUI configuration using only the primary VHDX.
- Ensure that your hypervisor storage has enough free space to support the recommended virtual disk size of the appliance, and enough overhead to support snapshots and future expansion of the virtual disk.
- Ensure that the primary disk and the secondary disk are identical in size always.
2
NOTE:If you want to migrate from an OpenManage Enterprise 3.10.x appliance to a later version, while deploying the OpenManage Enterprise 4.0.x version, ensure that you allocate the minimum required memory (required for the migration of both OpenManage Enterprise and its plug-ins from 3.10.x) even if you plan to decline the installation of default plug-ins during the migration process. Else, migration will not be allowed.
3
NOTE:If you want to migrate from an OpenManage Enterprise 3.10.x appliance to a later version, while deploying the OpenManage Enterprise 4.0.x version, ensure that you allocate the minimum required memory (required for the migration of both OpenManage Enterprise and its plug-ins from 3.10.x) even if you plan to decline the installation of default plug-ins during the migration process. Else, migration will not be allowed.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\