Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

Dell OpenManage Deployment Toolkit Version 5.4 Command Line Interface Reference Guide

PDF

Setting Environment Variables

The following table lists the RAIDCFG options, parameters, and pre-defined arguments for setting the CLI environment.

Table 1. Setting EnvironmentThe following table describes the RAIDCFG options, parameters, and pre-defined arguments for setting the CLI environment.
Mandatory Options and Arguments Optional Parameters Valid Parameters Arguments Description
-se -envn=<string>

-envc=<function>

or

setenvironment envname=<string> envcommand=<function>

NA NA

Sets a user-defined environment variable to the value returned from the getcontrollerslots function call. This option combination is mandatory.

Example:

A:>raidcfg -se -envn=CNTRL -
envc=getcontrollerslots
CNTRL=0 1 2
RAIDCFG Command successful!

-se -envn=<string>

-envc=<function>

or

setenvironment envname=<string>

envcommand=<function>

-f or filename <filename>

Captures the environment output to the given filename. This option either appends the information to an existing file or creates a new file.

-se -envn=<string>

- envc=<function> -c=id

or

setenvironment envname=<string>

envcommand=<function>

controllerid=id

NA NA

Sets a user-defined environment variable to the value returned from the getfirmware, getcontrollertype, getadisks, getadiskcount, getfreeadisks,getfreeadiskcount, getfreeadisksize, or gethotspares function call. This option combination is mandatory.

Example:

A:>raidcfg -se -envn=FIRMWARE
-envc=getfirmware -c=2
FIRMWARE=531T
RAIDCFG Command successful!

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\