Upon device discovery, iDRAC based PowerEdge servers and MX7000 chassis are automatically onboarded. Onboarding jobs can be used to update management credentials of devices when the device credentials differ from what was used during discovery. If internal iDRAC credential management is enabled and the iDRAC is eligible, the onboarding operation also creates an appliance-managed service account on the target.
About this task
Onboarding enables servers to be managed, rather than monitored.
Onboarding tasks only support iDRAC, and MX7000 chassis-based devices that are not in a managed state of proxy.
If administrator-level credentials are provided during discovery, the servers are onboarded (the device status is displayed as
Managed in the All Devices view).
If lower privileged credentials are provided during discovery, the servers are not onboarded (the status is displayed as
Monitored in the All Devices view).
If the console is also set as a trap receiver on the servers, then their Onboarding status is indicated as
Managed with Alerts.
Error indicates an issue in onboarding the device.
The
Proxied status is available only for the MX7000 chassis. It indicates that the device is discovered through an MX7000 chassis and not directly. For the supported and unsupported actions on the proxied sleds, see
Supported and unsupported actions on proxied sleds.
If you want to change the credentials of a device or reattempt onboarding because of a failure in onboarding during discovery, use the following steps.
NOTE:
All devices that have been onboarded through this wizard remain onboarded through this user account. The discovery user account does not replace this user account during future discoveries of the device.
For the already discovered devices, if the SNMP trap destination is manually set on iDRAC as OpenManage Enterprise, the appliance receives and processes alerts. However, the state of the device that is displayed on the
All Devices screen remains the same as its initial discovered state.
The
All Devices screen lists all onboarded chassis as
Managed despite the chassis user-role credentials that were used during onboarding. If the chassis was onboarded with credentials of a
Read-Only user, then update activities on the chassis may fail. Hence, It is recommended to onboard chassis with the credentials of a chassis administrator to perform all activities.
To perform any tasks on OpenManage Enterprise, you must have the necessary user privileges. See
Role and scope-based access.
Steps
Click
Devices > All Devices.
A Donut chart indicates the status of all devices in the working pane. See the
Donut chart. The table lists the properties of devices that are selected along with their following onboarding status:
Error: The device cannot be onboarded. Try by logging in by using the recommended privileges. See
Role and scope-based access.
Managed: The device has been successfully onboarded. The OpenManage Enterprise console can manage it.
Monitored: The device does not have management options. Devices that are discovered through SNMP may show this status.
Managed with alerts: The device is successfully onboarded. The OpenManage Enterprise console has successfully registered its IP address with the device as a trap destination during discovery.
In the working pane, select a check box corresponding to the devices, click
Discovery > Onboarding.
Ensure that you select only the device types from the
All Devices screen that are supported for onboarding. You can search for devices in the table by clicking
Advanced Filters, and then select, or enter onboarding status data in the filter box.
NOTE:All devices that are discovered are not supported for onboarding - iDRAC and MX7000 are supported. Any device that is selected that does not support onboarding, the onboarding option is not available. If you choose devices using the
Across all pages option, the onboarding action is accessible. However, if any devices that are selected on other pages lack onboarding support, the onboarding job is not generated. This limitation arises from the UI caching the device capabilities, limited to the current view (up to 25 devices at a time).
In the
Onboarding dialog box, enter the WS-Man credentials—username and password.
In the
Connection Settings section:
In the
Retries box, enter the number of repeated attempts that must be made to discover a server.
In the
Timeout box, enter the time after which a job must stop running.
NOTE:If the timeout value entered is greater than the current session expiry time, you are automatically logged out of OpenManage Enterprise. However, if the value is within the current session expiration timeout window, the session is continued and not logged out.
In the
Port box, enter the port number that the job must use to discover.
[Optional field] Select
Enable Common Name (CN) check.
[Optional field] Select
Enable Certificate Authority (CA) check and browse to the certificate file.
Click
Finish.
NOTE: The
Enable trap reception from the discovered check box is effective only for servers that are discovered by using their iDRAC interface. Trap reception does not impact other servers like operating system-discovered servers.
Data is not available for the Topic
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: <>()\