16.6 Discovering and Promoting Servers

Discovering and adding servers can be performed separately or as part of the host discovery. When a host is promoted, it triggers the discovery and auto promotion of the server supporting the host. See Discovering and Adding Host and Non-Host Targets for more about discovery, promotion, and the steps to promote a host.

To discover and promote an ILOM server, see the following:

To change the display name after you have discovered an ILOM server, see Change the Display Name of a Discovered ILOM Server.

Note:

To auto-promote targets, deploy the EM Agent with sudo privileges or manually install and run the root.sh script.

A Systems Infrastructure Server is displayed with the ILOM server name if the ILOM is discovered before the host, and if the HMP package is installed on the host. Otherwise, the Systems Infrastructure Server is displayed with the name "<host name>/server".

For some servers, a minimum firmware version is recommended to improve performance.

Note:

For SPARC M6-32 servers, system firmware 9.4.2.E or higher is recommended.

16.6.1 Discover an ILOM Server Using the User Interface

To discover an ILOM server, perform the following steps:

  1. From the Setup menu, select Add Target.

  2. Click Add Targets Manually.

  3. Click Add Using Guided Process listed under Add Non-Host Targets Using Guided Process.

    The Add Using Guided Process window is displayed with the list of Guided Discovery and Discovered Target Types.

  4. Select Systems Infrastructure Server ILOM from the list in the Add Using Guided Process window and click Add.

  5. For Target, enter the following details:

    1. Target Name: Enter the name of the ILOM server.

    2. Server ILOM DNS Name or IP Address: Enter the Server DNS Name or IP Address.

  6. For Monitoring Agents, enter the following details:

    1. Enter the Monitoring Agent EMD URL.

    2. (Optional): Enter the Backup Agent EMD URL.

  7. For Monitoring Credentials, enter the following SSH monitoring credentials:

    1. Select the Credential type as ILOM SSH Credentials.

    2. Enter the root user name in the Username field.

    3. Enter the root password in the Password and Confirm Password fields.

  8. For SNMP v1 and v2 configurations, enter the following credential parameters:

    1. Select the Credential type as SNMP V1/V2 Credentials.

    2. Enter your community string in the Community String and Confirm Community String fields.

  9. For SNMP v3 configurations, enter the following parameters:

    1. User name

    2. User password

    3. Confirm user password

    4. Authorization protocol, either MD5 or SHA

    5. Privacy password

    6. Confirm privacy password

  10. Click Add.

A confirmation window appears when the target is successfully added.

Note:

The user needs at least to provide a SNMP V1/V2 community string even if he wants to explicitly disable the SNMP configuration to occur on the ILOM server.

For disabling the SNMP Monitoring Configuration, type true in the Skip SNMP Subscription field.

16.6.2 Discover an ILOM Server Using the Command Line Interface

You can discover a server using the emcli command line tool. You must configure the command line interface before you can issue commands. For more information, click the Setup menu, then click Command Line Interface. Follow the Download and Deploy instructions.

To discover a server using the emcli, perform the following steps:

  1. Open your command line on the host where OMS is running.
  2. Login to emcli using command emcli login –username=<Your user name>.
  3. Type the password when prompted.
  4. Execute command emcli sync.
  5. Discover a new server using the emcli add_target command and define the following options:

    • -name=Name of the server to be displayed within Enterprise Manager

    • -type=oracle_si_server_map

    • -host=Host name from which you discover the server target for monitoring

    • -access point name=Access point name to be displayed within EM

    • -access_point_type=oracle_si_server_ilom

    • -properties=key:ILOM IP address that will be used in discovery. For example, -properties='dispatch.url=ilom-ssh://<ILOM_IP_ADDRESS>'.

    • -subseparator=properties with sub separator string, For example, you can use = as a separator between key value pairs. Alternatively, you can use the -separator option when there are multiple properties (key value pairs) that need to be separate.

    • -monitoring_cred=The credentials of the server ILOM to be discovered

Example 16-1 SNMP Credential-based Configuration

The user will have to provide "snmpv1v2_v3" monitoring credentials, specifying the SNMPV1Creds and the desired SNMP Community string as shown in the example below:

emcli add_target -name=<target name> -type=oracle_si_server_map -host=<EM Agent>  -access_point_name=<ILOM Access Point Name> -access_point_type=oracle_si_server_ilom -subseparator=properties== -properties=dispatch.url=ilom-ssh://<ILOM server host name> '-monitoring_cred=ilom_creds_set;oracle_si_server_ilom;ilom_creds;username:<ILOM user name>;password:<ILOM user password>' '-monitoring_cred=snmp_v1v2_v3;oracle_si_server_ilom;SNMPV1Creds;COMMUNITY:<SNMP Community string>'

Example 16-2 Legacy Community String Property-based Configuration

Despite the fact that this not encouraged, it is still possible to perform the ILOM discovery using a SNMP community string as a property as in the example below:

emcli add_target -name=<target name> -type=oracle_si_server_map -host=<EM Agent> -access_point_name=<ILOM server Access Point name>  -access_point_type=oracle_si_server_ilom -subseparator=properties== '-properties=SNMPCommunity=<SNMP Community String>;dispatch.url=ilom-ssh://<ILOM Server host name>' '-monitoring_cred=ilom_creds_set;oracle_si_server_ilom;ilom_creds;username:<ILOM user name>;password:<ILOM User password>'

Example 16-3 Discovery without SNMP subscription

 As with the UI discovery flow, the user can disable the automatic SNMP rules configuration on the ILOM server by setting the "SkipSnmpSubscription" property to "true" as shown below:

emcli add_target -name=<target name> -type=oracle_si_server_map -host=<EM Agent> -access_point_name=<ILOM server Access Point name>  -access_point_type=oracle_si_server_ilom -subseparator=properties== '-properties=SkipSnmpSubscription=true;dispatch.url=ilom-ssh://<ILOM Server host name>' '-monitoring_cred=ilom_creds_set;oracle_si_server_ilom;ilom_creds;username:<ILOM user name>;password:<ILOM User password>'

Example 16-4 SNMP V3 Monitoring configuration

The user needs to provide the "snmp_v1v2_v3" monitoring credentials configuration to perform SNMP V3 subscription on the ILOM server. The following parameters will be configured:

  • authUser

  • authPwd

  • authProtocol, either MD5or SHA

  • privPwd, which is optional

emcli add_target -name=<target name> -type=oracle_si_server_map -host=<EM Agent> -access_point_name=<ILOM server Access Point name> -access_point_type=oracle_si_server_ilom -subseparator=properties== -properties=dispatch.url=ilom-ssh://<ILOM Server host name> '-monitoring_cred=ilom_creds_set;oracle_si_server_ilom;ilom_creds;username:<ILOM User name>;password:<ILOM User password>' '-monitoring_cred=snmp_v1v2_v3;oracle_si_server_ilom;SNMPV3Creds;authUser:<SNMP Authorization User>;authPwd:<SNMP Authorization User password>;authProtocol:MD5;privPwd:<SNMP privacy password>

16.6.3 Change the Display Name of a Discovered ILOM Server

You can change the display name of a discovered server using the CLI by running the emcli command to modify the target name. For example:

emcli modify_target -name="Server Target Name" -type="oracle_si_server_map" -display_name="New Display Name"