Update Monitoring User of an Already Discovered SI Target

Follow these steps to update the monitoring user for a System Infrastructure Remote Host target that is already discovered:

  1. Place the following command in the sudoers file on the remote host:

    <non-root-username> ALL=(ALL) /usr/sbin/sminfo,/usr/bin/ipmitool,/bin/cat
    /etc/iscsi/iscsid.conf,/sbin/fdisk,/sbin/vgs,/sbin/pvs,/sbin/lvs,/sbin/
    dmsetup,/usr/sbin/dbmcli,/sbin/service,/sbin/initctl,/opt/oracle.cellos/
    compmon/exadata_mon_hw_asr.pl,/usr/local/bin/imageinfo,/usr/sbin/
    exadata.img.hw,/usr/sbin/ibnetdiscover,/usr/sbin/smartctl
  2. Use EMCLI to add an access point using a non-root user to the already discovered remote host. Specify the dispatch URL as sudo-ssh://<TARGET_IP/HOST_NAME>:22 by running the following EMCLI command:

    emcli add_target -name=<REMOTE_HOST_NAME> 
    -type=oracle_si_host_remote -host=<AGENT_HOST_NAME>
    -monitoring_cred=ssh_creds_set;oracle_si_host_remote_ssh;ssh_creds;username:<USER_NAME>;userpass:<PASSWORD>;
    -subseparator=properties== -properties=dispatch.url=sudo-ssh://<TARGET_IP/HOST_NAME>:22 
    -access_point_name=<ACCESS_POINT_NAME> -access_point_type=oracle_si_host_remote_ssh

    Note:

    Provide a REMOTE_HOST_NAME name which is different from the existing one. The new name is ignored and the already monitored target is automatically identified and attached to the access point. The new name will not be used.

  3. Verify that the new access point is added to the existing System Infrastructure Remote Host target.

  4. Once the new access point is verified to be running, remove the old access point which is using the root user for monitoring. Go to Access point overview page to remove the access point.