Users Guide

NOTE: During CMC discovery, the servers, and IOM and storage modules (configured with IP and SNMP set to "public"
as community string), residing on CMC are also discovered and are onboarded. If you enable trap reception during CMC
discovery, the OpenManage Enterprise is set as the trap destination on all the servers and not on the chassis.
NOTE: During CMC discovery, FN I/O Aggregators in Programmable MUX (PMUX) mode are not discovered.
Onboarding devices
Onboarding enables servers to be managed, rather than just be monitored.
●
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.
● Proxied: Available only for MX7000 chassis. Indicates that the device is discovered through an MX7000 chassis and not
directly.
If you want to onboard devices with a different user account apart from the account specified for discovery, or re-attempt
onboarding because of a failure in onboarding during discovery, do the following:
NOTE:
● All devices that have been onboarded through this wizard remain onboarded through this user account and is not
substituted by the discovery user account during future discoveries against these devices.
● For the already discovered devices, if the SNMP trap destination is 'manually' set in iDRAC as OpenManage Enterprise,
the alerts are received and processed by the appliance. However, the device's Managed State displayed on the All
Devices page remains the same as its initial discovered state of 'Monitored,' 'Managed' or 'Managed with Alerts.'
● The All Devices page displays the Managed State of all the onboarded chassis as "Managed" irrespective of which
chassis user-role credentials were used at the time of onboarding. If the chassis was onboarded with credentials of a
"read-only" user, then there may be a failure during update activities performed on chassis. Hence, It is recommended to
onboard chassis with credentials of a chassis Administrator to perform all activities.
● To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based
OpenManage Enterprise user privileges on page 14.
1. From the OpenManage Enterprise menu, under Devices, click All Devices.
A Donut chart indicates status of all devices in the working pane. See the Donut chart. The table lists the properties of
devices selected along with their following onboarding status:
● Error: Device cannot be onboarded. Try by logging in by using the recommended privileges. See Role-based
OpenManage Enterprise user privileges on page 14.
● Managed: Device successfully onboarded, and can be managed by the OpenManage Enterprise console.
● Monitored: Device does not have management option (such as the one discovered by using SNMP).
● Managed with alerts: Device is successfully onboarded, and the OpenManage Enterprise console has successfully
registered its IP address with the device as a trap destination during discovery.
2. In the working pane, select a check box corresponding to the device(s), click More Actions > Onboarding.
Ensure that you select only the device types from the All Devices page that are supported for onboarding. You can search
for suitable 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 and only iDRAC and CMC are supported.
Ensure that you select onboarding option for the supported device type.
3. In the Onboarding dialog box, enter the WS-Man credentials—username and password.
4. In the Connection Settings section:
a. In the Retries box, enter the number of repeated attempts that must be made to discover a server.
b. 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.
108 Discovering devices for monitoring or management