Quantcast
Channel: ProLiant Servers (ML,DL,SL) topics
Viewing all articles
Browse latest Browse all 10362

Set ilo2 Custom Group Via SSH

$
0
0

Using SSH into a iLO2 device, I can setup almost everything including my Directory Authenication.  However I cannot find where to set the custom groups.  I cannot see it in /map1 or /system1 anywhere.  This includes looking on a system that I manually configured via the web UI.

iLO2 Custom Group

 

Looking on a iLO3 system I see the following available

</map1>hpiLO-> show oemhp_dircfg1

/map1/oemhp_dircfg1
  Targets
    oemhp_keytab1
  Properties
    oemhp_dirauth=Directory Default Schema
    oemhp_localacct=Yes
    oemhp_dirsrvaddr=LDAP.CORP.net
    oemhp_ldapport=636
    oemhp_dirdn=
    oemhp_usercntxt1=OU=Users and Groups,DC=corp,DC=net
    oemhp_usercntxt2=OU=God Accounts,OU=Users and Groups,DC=corp,DC=net
    oemhp_group1_name=Administrators
    oemhp_group2_name=Authenticated Users
    oemhp_group3_name=CN=iLO-RW,OU=God Accounts,OU=Users and Groups,DC=corp,DC=net
    oemhp_group4_name=CN=iLO-RO,OU=Users and Groups,DC=cardinalhealth,DC=net
    oemhp_group1_priv=login,oemhp_rc,oemhp_vm,oemhp_power,config,admin
    oemhp_group2_priv=login
    oemhp_group3_priv=login,oemhp_rc,oemhp_vm,oemhp_power,config,admin

Seeing the oemhp_group1 on the ilo3 I attempted the following on iLO2:

 

</map1/oemhp_dircfg1>hpiLO-> create oemhp_group1 name=CN=iLO-RW,OU=God Accounts,OU=Users and Groups,DC=corp,DC=net
status=2
status_tag=COMMAND PROCESSING FAILED
error_tag=COMMAND ERROR-UNSPECIFIED
Invalid target.</map1/oemhp_dircfg1>hpiLO-> set oemhp_group5 name=CN=iLO-RW,OU=God Accounts,OU=Users and Groups,DC=corp,DC=net
status=2
status_tag=COMMAND PROCESSING FAILED
error_tag=COMMAND ERROR-UNSPECIFIED
Invalid property.

 

 

It appears that the iLO3 targets are not valid on iLO2., so where does the customgroup1 get saved at on the iLO2?


Viewing all articles
Browse latest Browse all 10362

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>