Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

jsmith62

7 Posts

28772

February 3rd, 2010 09:00

SM-CLP "set" verb support in iDrac6

Has anyone had any luck using the SM-CLP "set" verb on an iDRAC6 (Firmware v 1.30) to set the IP Address, Subnet Mask etc. for the DRAC?

The documentation at:

http://support.dell.com/support/edocs/software/smdrac3/idrac/idrac10mono/en/ug/html/racugc1e.htm#wp46449

implies that this should be possible.

Whilst other verbs seem to work OK e.g.

show -d properties=IPv4Address system1/sp1/ipendpt1

returns the IPv4 address OK. However trying to:

set system1/sp1/ipendpt1 IPv4Address=192.168.nn.nn

Gives a command syntax error and doing a

show -d verbs system1/sp1/ipendpt1

does not list "set" as a supported verb.

Looks to me like "set" is not supported despite what the docs claim or am I using the wrong target?

Help appreciated.



Scott Hanson

342 Posts

February 3rd, 2010 13:00

I get the same thing when I try on a system in the lab with 1.3 FW. I've pinged some people on the back end to find out if there's any special privs - I'm using default root/calvin.

I'll let you know what I find.

jsmith62

7 Posts

February 4th, 2010 07:00

Should have said I'm connecting over SSH using plink with defined admin user and PPkey exchange: I always delete the default root /calvin admin. This should not make any difference regarding priveleges.

cvanrij

4 Posts

February 4th, 2010 20:00

The SM-CLP syntax is .. a little convoluted, it took me a while (and far too many very abstract DMTF documents) to get a working assignment.

To enable DHCP while connected to the iDRAC6 on an R410
(ssh, root, calvin), you need the 'object' you want to manage,
on the R410 this turns out to be:

/admin1-> show /admin1/system1/sp1/lanendpt1
properties
ElementName = LAN Endpoint
MACAddress = 0026B958D937
targets
enetport1

The target is the actual ethernet port:

/admin1-> show /admin1/system1/sp1/lanendpt1/enetport1
properties
DeviceID = iDRAC
ElementName = Ethernet Port
NetworkAddresses[0] = 0026B958D937

after dumping the entire /admin1/ tree with show -l all /admin1 I found:

/admin1-> show /admin1/system1/sp1/settings1/ipsettings1
elementsettingdata :
ManagedElement = /admin1/system1/sp1/ipendpt1
SettingData = /admin1/system1/sp1/settings1/ipsettings1
targets
dnssettings1
staticipsettings1

That looks like it manages the Object I want to change, but instead of settings1 I want:

/admin1/system1/sp1/settings1/ipsettings2/dhcpsettings1
properties
AddressOrigin = 4 (DHCP)
ElementName = DHCP Setting Data

So, assign the ipsettings2 to the ManagedElement with the SettingData:

/admin1-> set /admin1/system1/sp1/ipendpt1=>ElementSettingData=>/admin1/system1/sp1/settings1/ipsettings2 IsCurrent=1

And yes.. DHCP is now Enabled. Almost too easy..

cvanrij

4 Posts

February 8th, 2010 09:00

It's probably also worth pointing out that it's still possible to get into racadm from the '/admin1->' SM-CLP prompt.
This doesn't appear to be mentioned anywhere but works on my R410s,

# ssh root@192.168.0.120
/admin1-> racadm help serveraction
serveraction -- perform system power management operations

View More

View All

No Events found!

Top