Sunteți pe pagina 1din 540

IBM Systems

IBM Systems Director Commands Reference

Version 6.1.2

GC30-4170-04

IBM Systems IBM Systems Director Commands Reference Version 6.1.2 GC30-4170-04
IBM Systems IBM Systems Director Commands Reference Version 6.1.2 GC30-4170-04
IBM Systems IBM Systems Director Commands Reference Version 6.1.2 GC30-4170-04
IBM Systems IBM Systems Director Commands Reference Version 6.1.2 GC30-4170-04

IBM Systems

IBM Systems Director Commands Reference

Version 6.1.2

GC30-4170-04

Note Before using this information and the product it supports, read the information in “Notices”

Note Before using this information and the product it supports, read the information in “Notices” on page 523.

Note Before using this information and the product it supports, read the information in “Notices” on

© Copyright IBM Corporation 1999, 2009. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

About this publication

 

.

.

.

.

.

.

.

.v

Conventions and terminology

 

.

.

.

.

.

.

.

.v

How to read syntax diagrams

.

.

.

.

.

.

.

.v

Publications and related information .

.

Web resources

.

.

.

.

.

 

.

.

.

.

.

.

.

.

. vi

. ix

. How to send your comments

 

.

.

.

.

.

.

.x

Chapter 1. smcli - Systems management command-line interface

.1

Language specifications for smcli commands .

 

.

.

5

. CLILEGACY environment variable .

Port configuration for smcli

.

.

.

.

.

.

 

.

.

.

.

.6

.6

Alphabetical listing of all smcli commands .

.

.

.6

lsbundle command .

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 14

System commands .

.

.

.

.

.

. 15

accesssys command

.

.

.

.

.

. 17

chsys command .

.

.

.

.

.

. 22

lssys command .

.

.

.

.

.

. 27

pingsys command .

.

.

.

.

.

. 33

rmsys command

.

.

.

.

.

. 38

rpower command .

Web interface commands .

.

.

.

.

.

.

.

.

.

.

. 42

. 47

endSession command .

.

.

.

.

.

.

.

.

. 47

Group commands .

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 49

chgp command .

.

.

.

.

.

. 50

lsgp command .

.

.

.

.

.

. 55

mkgp command

.

.

.

.

.

. 62

rmgp command

.

.

.

.

.

. 67

Discovery and inventory commands .

 

.

.

.

.

. 70

discover command

.

.

.

.

.

.

.

.

. 71

collectinv command

.

.

.

.

.

.

.

.

.

. 74

lsinv command .

. Configuration plans and templates commands.

.

.

.

.

.

.

.

.

 

.

.

. 79

. 85

Configuration plan commands

.

.

.

.

. 85

Configuration template commands

.

.

.

.

. 93

Status commands

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 102

chled command

.

.

.

.

. 103

lsled command

.

.

.

.

. 107

lsstatus command

Resource monitor commands .

.

.

.

.

.

.

.

.

. 110

. 116

Resource monitor commands .

.

.

.

.

. 117

Resource-monitor threshold commands

 

126

Resource-monitor recording commands

146

Process monitor commands

.

.

.

.

.

.

. 165

lsps command

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 165

mkpmtask command .

.

.

.

.

. 169

rmpmtask command .

.

.

.

.

. 172

Event and event automation plan commands. Event, event log and event action history

.

commands

.

.

.

.

.

.

.

 

.

.

. 174

. 177

. Event automation plan commands .

 

.

.

.

. 200

Event action commands .

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 222

Event filter commands

Remote access commands .

.

.

.

.

.

.

.

.

. 239

. 249

dconsole command

.

.

.

.

. 249

dsh command .

. Tasks and scheduled jobs commands

.

.

.

.

.

.

.

.

.

.

.

.

.

. 252

. 257

lstask command

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 259

runtask command .

.

.

. 267

lsjob command .

lsjobhistory command

.

.

.

.

. 272

. 279

rmjob command .

rmjobhistory command .

.

.

.

.

. 283

. 285

runjob command .

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 288

Update commands

checkupd command .

.

.

.

.

. 291

. 292

cleanupd command .

.

.

.

.

.

.

.

.

. 297

lsupd command

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 300

lsver command .

importupd command .

.

.

.

.

. 306

. 307

installupd command .

.

.

. 310

uninstallupd command .

.

.

.

.

.

.

.

. 317

Security commands .

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 322

authusergp command

.

.

. 323

cfgcred command .

.

.

. 325

chaudit command .

.

.

. 328

chcred command .

.

.

. 329

chusergp command .

.

.

. 331

lsaudit command .

.

.

.

.

.

.

.

.

.

. 335

lsauditlogs command .

.

.

.

.

.

.

.

.

. 336

lscred command

.

.

.

.

.

.

.

.

.

.

. 338

lsuser command

.

.

.

.

.

.

.

.

.

.

. 340

. rmauditlogs command .

lsusergp command

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 345

. 349

rmcred command .

.

.

.

.

.

.

.

.

.

. 351

rmusergp command .

.

.

.

.

.

.

.

.

. 353

Users .

.

.

.

.

.

.

.

.

.

.

.

.

.

. 356

chuser command .

.

.

.

.

.

.

.

.

.

. 356

lsuser command

.

.

.

.

.

.

.

.

.

.

. 360

. chrole command .

Roles .

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 365

. 365

lsperm command .

.

.

. 369

lsrole command

mkrole command .

.

.

.

.

. 372

. 377

rmrole command .

SNMP device commands

.

.

.

.

. 379

. 382

SNMP get command .

SNMP getbulk command

.

.

.

.

. 384

. 386

SNMP getnext command

.

.

. 387

SNMP inform command .

.

.

.

.

.

.

.

. 389

.

.

SNMP walk command .

SNMP set command .

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 391

SNMP trap command

.

.

. 393

.

.

. 395

Storage commands

. Storage-configuration settings . Network storage hosts commands

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 397

. 398

. 401

Network storage path commands . Network storage systems commands

.

.

.

.

. 409

. 429

Network storage volumes commands .

.

.

. 435

Virtualization commands

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 452

chvrtauth command .

.

.

. 455

chvrthost command .

.

.

.

.

.

.

.

.

. 459

chfarm command .

.

.

.

.

.

.

.

.

.

. 464

chvs command

.

.

.

.

.

.

.

.

.

. 467

lsvrtsys command .

.

.

.

.

.

.

.

.

.

. 471

lsvrtcap

command

.

.

.

.

.

.

.

.

. 477

. mkrelocatetask command .

mkfarm

command

.

.

.

.

.

.

.

.

.

.

.

.

.

. 482

. 484

mkvs command

.

.

.

.

.

.

.

.

.

.

. 487

Chapter 2. Management server and agent commands

 

491

cfgdbcmd command

.

.

dirinstall.server command .

.

.

.

.

.

.

.

. 491

changePassword command

.

.

.

.

.

.

. 495

cimsubscribe command

.

.

.

.

.

.

.

. 495

configAgtMgr command

.

.

.

.

.

.

.

. 500

.

.

.

.

.

.

.

. 502

getfru command .

.

.

.

.

.

.

.

.

.

.

. 503

smexport command .

.

.

.

.

.

.

.

.

.

. 503

smimport command .

.

.

.

.

.

.

.

.

.

. 505

smreset command .

.

.

.

.

.

.

.

.

.

.

. 507

smrestore command .

.

.

.

.

.

.

.

.

.

. 509

smsave command .

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 511

smstart command .

.

.

.

.

.

.

. 513

.

.

.

.

.

.

.

.

.

.

. 514

smstatus command smstop command .

. Supported IBM Director v5.20 commands .

.

.

.

.

.

.

.

 

.

.

.

.

. 515

. 515

Appendix. Discontinued commands

517

Discontinued dircli commands

.

 

.

.

.

.

.

. 517

Discontinued dircmd commands .

.

.

.

.

.

. 519

Discontinued management-server and agent

 

commands

.

.

.

.

.

.

.

.

.

. 522

Notices .

.

.

.

.

.

.

.

.

.

.

.

523

Trademarks .

.

.

.

.

.

.

.

.

.

.

.

.

. 524

About this publication

This book provides reference information for commands available in IBM ® Systems Director 6.10. These commands fall into two broad categories:

v

Commands used to configure, start, or stop IBM Systems Director. These commands are entered directly on the command line when the action should be performed.

v

Commands used to perform IBM Systems Director tasks. These commands are implemented using the IBM Systems Director command-line interface, smcli.

Conventions and terminology

These notices are designed to highlight key information:

Note: These notices provide important tips, guidance, or advice.

Important: These notices provide information or advice that might help you avoid inconvenient or difficult situations.

Attention: These notices indicate possible damage to programs, devices, or data. An attention notice appears before the instruction or situation in which damage can occur.

How to read syntax diagrams

Review the conventions used in syntax diagrams to understand the command descriptions.

Syntax diagrams consists of options, option arguments, and operands.

Options Options indicate input that affects the behavior of the base command (for example, -l specifies long output) or required input that you can specify in different ways (for example, you can target objects using either -n name OR -N groupname OR -ac objectclass ). Options consist of either a hyphen and single letter (for example, -h) or two hyphens and multiple letters (for example, --help ). The single letter format is the short form of the multiple letter format, and the two formats are functionally interchangeable when issuing a command.

Option arguments Some options are followed by one or more option arguments that specify a value for the option. For example, with -file file_name , file_name specifies the name of the file on or with which to take action.

Operands Operands are parameters at the end of a command that specify required user input.

Syntax diagrams adhere to the following conventions:

v Options and operands that are enclosed in brackets ( []) are optional. Do not include these brackets in the command.

v

Options and operands that are enclosed in braces ( {}) are required. Do not include these braces in the command.

v

Options and operands that are not enclosed in either brackets or braces are required.

v

Operands and option arguments that are italicized must be replaced with actual values.

v

The names of options are case sensitive and must be typed exactly as shown.

v

Options preceded by two dashes ( --) must be specified in their entirety.

v

A pipe ( | ) character signifies that you can or must, depending on the enclosing characters, choose one option or the other. For example, [a | b] indicates that you can choose either a or b, but not both. Similarly, {a | b} indicates that you must choose either a or b.

v

An ellipsis (

) signifies that you can repeat the operand and option argument

on the command line.

v

A dash ( - ) represents standard output.

Publications and related information

You can view the same content in the IBM Systems Director Information Center as PDF documents. To view a PDF file, you need Adobe Acrobat Reader, which can be downloaded for free from the Adobe Web site at www.adobe.com/products/ acrobat/readstep.html.

Information centers and topic collections

v

IBM ® Systems

View the IBM ® Systems information center which provides integrated information for multiple IBM ® Systems products, including operating systems, hardware, storage, and software. This information center also contains scenarios to help you use multiple IBM ® Systems products in the same environment.

v

IBM Systems Director

Updated periodically, the IBM Systems Director topic collection contains the most up-to-date documentation available for IBM Systems Director.

v

IBM Systems Director plug-ins

View the IBM ® Systems information center for information about to install and use plug-ins that extend the functionality of IBM Systems Director.

v

IBM Systems Director Upward Integration Modules (UIMs)

publib.boulder.ibm.com/infocenter/systems/topic/uims/fqs0_main.html

Read the IBM Systems Director Upward Integration Modules (UIM) topic collection to learn about how to install and use upward integration modules and management packs that enable non-IBM ® workgroup and enterprise- management products to interpret and display data that is provided by Common Agent and Platform Agent.

v

IBM Systems Director API Licensing

View the license information regarding use of IBM Systems Director APIs and their associated documentation. Fill out the form to request API access. After your information is reviewed, you will be contacted with additional information regarding access to and use of the APIs.

Publications

Release Notes 6.1 , Release Notes 6.1.1 , and Release Notes 6.1.2 Provides information about hardware requirements for running IBM Systems Director components, supported IBM Systems Director hardware, operating systems, databases, and workgroup and enterprise systems-management software.

Hardware and Software Support Guide Provides information about hardware requirements for running IBM Systems Director components, supported IBM Systems Director hardware, operating systems, databases, and workgroup and enterprise systems-management software.

Planning, Installation, and Configuration Guide for AIX ® Provides detailed instructions to install and configure each component of IBM Systems Director on system running AIX using the standard installation option.

Planning, Installation, and Configuration Guide for IBM i Provides detailed instructions to install and configure each component of IBM Systems Director on system running IBM i using the Standard installation option.

Planning, Installation, and Configuration Guide for Linux on Power Systems Provides detailed instructions to install and configure each component of IBM Systems Director on system running Linux for Power Systems using the Standard installation option.

Planning, Installation, and Configuration Guide for Linux on x86 Provides detailed instructions to install and configure each component of IBM Systems Director on system running Linux for System x ® using the Standard installation option.

Planning, Installation, and Configuration Guide for Linux on System z ® Provides detailed instructions to install and configure each component of IBM Systems Director on system running Linux for System z using the Standard installation option.

Planning, Installation, and Configuration Guide for Windows Provides detailed instructions to install and configure each component of IBM Systems Director on system running Windows using the Standard installation option.

Systems Management Guide Provides detailed instructions for using the Web interface and managing systems and resources in your environment.

Troubleshooting Guide Provides information about problems and how to solve them, and strategies for troubleshooting common problems.

Events Reference Provides information about IBM Systems Director events, including the event type, description, severity, and extended attributes.

Commands Reference Provides detailed information about the systems management command-line interface (smcli) commands, and other commands that can be run directly from the command line, including configuring the database, and starting and stopping IBM Systems Director.

Hardware Command Line User's Guide Provides information about installing and using the Hardware Command Line (formerly known as the IBM ® Management Processor Command-Line Interface). Command output in this release might vary from command output in previous releases.

White papers and briefs

v

IBM Systems Director

This paper provides a detailed overview of the changes in IBM Systems Director V6.1, including the new Web interface, security features, operating system agents, integrated plug-ins and additional plug-ins that can be separately installed.

v

Value Proposition for IBM Systems Director

This paper describes the challenges of operational management for enterprise server installations and the value provided IBM Systems Director.

v

Managing IBM Power Servers with IBM Systems Director 6.1

Provides information about managing the virtualization and consolidation on Power systems using IBM Systems Director.

v

IBM Systems Director 6.1 Migration Tips

Provides information about migrating data when upgrading your environment from IBM Director V5.20 to IBM Systems Director V6.1.

IBM ® Redbooks ® publications

You can also search this Web page for documents that focus on IBM Systems Director and specific IBM hardware; such documents often contain systems-management material. The following book is available for IBM Systems Director V6.1:

Tip: Be sure to note the date of publication and to determine the version of IBM Systems Director software to which the Redbooks publication refers.

Web resources

Listed here are the Web sites and information center topics that relate to IBM Systems Director.

Web sites

v

IBM Systems Director

View the IBM Systems Director Web site on ibm.com ® which provides links to downloads and documentation for all currently supported versions of IBM Systems Director.

v

IBM Systems Director Downloads

View the IBM Systems Director Downloads Web site on ibm.com which provides links to download code IBM Systems Director, IBM Systems Director plug-ins, and IBM Systems Director upward integration modules.

v

IBM Systems Director Documentation and Resources

View the IBM Systems Director Documentation and Resources Web site on ibm.com which provides links to product documentation, redbooks, redpapers, white papers, and learning modules related to IBM Systems Director, IBM Systems Director plug-ins, and IBM Systems Director upward integration modules.

v

IBM Systems Director Upward Integration

View the IBM Systems Director Upward Integration Web site on ibm.com which provides more information about IBM Systems Director upward integration modules created by IBM ® and other companies. IBM Systems Director UIMs enable third-party workgroup and enterprise systems-management products to interpret and display data that is provided by IBM Systems Director Platform-Agent managed system.

v

IBM ® Servers

View the IBM ® Servers Web site to learn about IBM ® Systems server and storage products.

v

IBM ® ServerProven ®

View the IBM ® ServerProven Web site to learn about hardware compatibility of IBM ® System x and BladeCenter ® systems with IBM ® applications and middleware, including IBM Systems Director.

Forums

v

IBM Systems Director

View the IBM Systems Director forum Web site on ibm.com to discuss product-related issues pertaining to IBM Systems Director, IBM Systems Director UIMs, and IBM Systems Director extensions. This Web site includes a link for obtaining the forum using a Rich Site Summary (RSS) feed.

v

IBM Systems Director SDK

View the IBM Systems Director SDK forum Web site to discuss issues pertaining to the IBM Systems Director Software Development Kit (SDK). This Web site includes a link for obtaining the forum using a Rich Site Summary (RSS) feed.

v IBM ® Systems

View the IBM ® Systems forums Web site on ibm.com to learn about various forums that are available to discuss technology-related and product-related issues pertaining to IBM ® Systems hardware and software products. This Web site includes a link for obtaining the forum using a Rich Site Summary (RSS) feed.

How to send your comments

Your feedback is important in helping to provide the most accurate and highest quality information.

If you have any comments about this book or any other IBM Systems Director publication, go to the IBM Systems Director information center Web site at

There you will find the feedback page where you can enter and submit comments.

Chapter 1. smcli - Systems management command-line interface

From the systems management command-line interface (called smcli ), you can specify options that are not associated with any command.

Syntax

smcli

[-h

|

-?

|

--help]

smcli [-c] [-prompt] [-user user_name] [-pw password] command_string

smcli

-d

Description

Prerequisite: Management servers running Windows XP, Windows 2000, or Windows 2003 require msvcr80.dll to run smcli . You can obtain the dynamic link library (DLL) by installing vcredist_x86.exe. For information about downloading and installing this file, see https://www.microsoft.com/downloads.

You can run smcli commands locally from the management server or remotely by accessing the management server using a remote-access utility, such as secure shell (SSH) or Telnet.

Starting with IBM Systems Director 6.1.1, you can execute up to 17 concurrent smcli or dircli threads simultaneously. The 17 concurrent threads are executed in the sequence in which you issue them as 17 independent commands. Obtaining a thread for final execution is dependent on the availability and priority of the thread.

Notes:

v

Ensure that logging is set to capture sufficient data for future debugging.

v

Thread scheduling is handled in the thread pool and is based on the assigned priority of the thread.

v

With the exception of CSM, you must manually execute concurrent commands that require the completion of or data from previously-launched threads. This will ensure that the first command completes execution before the command that depends on it starts execution.

v

To initialize the commands, a security check is done at the launch of each command.

v

If you ran multiple CLI commands with success in the past, your sequencing might be modified.

v

Authorization for each thread is not passed from one thread to another. The authorization of the command execution is done at the initial level, so there is no security check at the pool level. The role-based access levels that are defined for each type of user are passed along when a user executes a command.

If the management server runs on AIX or Linux and you do not specify the -prompt , -user , and -pw options, specifying smcli is optional. If you do specify one

or more of those options, you must also specify smcli . If the management server runs on Windows, specifying smcli is required.

IBM Systems Director authenticates and authorizes command requests using a Lightweight Directory Access Protocol (LDAP) server. You must specify user credentials (user name and password) for authentication and authorization every time that you run a command. You can specify the user credentials in one of these ways:

v

Include the user credentials with the command using the -user and -pw options.

v

Set up a prompt, using the -prompt option or the CLIPROMPT environment variable.

v

Create a persistent copy of the user name and encrypted password, using the smcli -c command. After the user name and password are saved, the saved credentials are used each time you run a command; you do not need to specify user credentials with the smcli commands until you delete the persistent copy, using the smcli -d command.

If you do not specify the -prompt , -user , and -pw options, IBM Systems Director uses the value of the CLIPROMPT environment variable (if set) to determine whether to prompt for the user name and password. You can set this variable to true (prompt) or false (no prompt).

If the CLIPROMPT environment variable is not set or is set to false , and you do not specify the -prompt , -user and -pw options with the command, IBM Systems Director uses the persistent copy of the user name and encrypted password; it then authorizes and authenticates using the operating-system authentication mechanisms.

Important:

v

The password is protected from being displayed only when you are prompted for the password or when IBM Systems Director uses the persistent copy of the encrypted password. When you specify the password using the -pw option, the characters for the password are displayed as plain text.

v

When you specify user credentials from the command line using the -user and -pw options, there is a fraction of a second during which the command (including the user name and password) can be seen by listing the processes on the system.

v

In previous releases of IBM Systems Director, the CLI was called dircli . The dircli command is supported in this release for compatibility with earlier versions. You can run all smcli commands using dircli .

Using the latest smcli commands is recommended; however, dircli commands are supported in this release for compatibility with IBM Systems Director version 5.20 and earlier. To use a dircli command with the same name as an smcli command, you must define the CLILEGACY environment variable and set it to a value of 1 .

Operands

None

Flags

-c Creates a persistent copy of the specified user name and password. The password in the persistent copy is encrypted.

If the CLIPROMPT environment variable is not set or is set to false , and you do not specify the -prompt , -user and -pw options with the command, IBM Systems Director uses the persistent copy of the user name and encrypted password; it then authorizes and authenticates using the operating-system authentication mechanisms.

If you do not specify the -user or -pw options, IBM Systems Director prompts you for the user name or password.

Tips:

v

After you create a persistent copy of the user name and password, you no longer have to provide the user name and password for subsequent commands.

v

If you specify this option, you must also specify a valid command.

-d

Deletes the persistent copy of the user name and encrypted password.

Important: For security reasons, you should always run the smcli -d command when you finish using the CLI.

-h | -? Displays the syntax and a brief description of smcli .

Tips:

v

If you specify additional options, the options are ignored.

v

If you want to display the syntax and brief description of a specific command, specify the command name before the -h | -? option.

--help Displays detailed information about smcli , including the syntax, a description of smcli , a description of the options and operands, error codes, and examples.

Tips:

v

If you specify additional options, the options are ignored.

v

If you want to display the detailed information about a specific command, specify the command name before the --help option.

v

(AIX and Linux only) You can also display detailed help in the form of man pages using the man command_name command.

-prompt Prompts you for a user name and password.

Tips:

v

This option protects the display of the password. When you are prompted for the password, no characters are displayed.

v

Specifying the -prompt option overrides all other mechanisms for prompting, including the CLIPROMPT environment variable.

v

If you specify this option with the -user and -pw options, the -prompt option is ignored.

-pw password Specifies the password for the user name.

Important: The password is displayed as plain text when you specify the -pw option. Using this form of authentication could cause a security exposure.

Tip: If you specify this option without the -prompt or -user options, you will be prompted for the user name.

-user user_name Specifies a valid user name with administrative privileges to be authenticated by the IBM Systems Director Server.

Tip: If you specify this option without the -prompt or -pw options, you will be prompted for the password.

command_string Runs the specified command and options.

Exit status

The following table contains the codes returned by this command.

v

0 : The operation completed successfully.

v

1 : A usage error occurred.

v

2 : The command or bundle was not found.

v

3 : The command was not performed because either authentication failed or you are not authorized to perform the action.

v

8 : The exit code is out of range (0 to 255).

v

29 : The specified locale is not valid or not supported.

v

10 : A file-processing error occurred.

v

125 : An internal error occurred.

Examples

1. Create a user session

This example illustrates how to create a user session that uses the persistent copy of the user name and password. The PROMPT environment variable is set to yes , so the user is prompted for the password.

smcli

password:

-c

-user

Admin1

Tip: No characters are displayed when you type the password.

2. Authenticate using the specified user name and password

This example illustrates how to list the IBM Systems Director users using the specified user name and password for authentication.

smcli

-user

Admin1

mysystem\Admin1

mysystem\Admin2

-pw

passw0rd

lsuser

3. Authenticate by prompting for user name and password

This example illustrates how to list the IBM Systems Director users and prompt for the user name and password to use for authentication.

smcli

user:

password:

-prompt

Admin1

lsuser

mysystem\Admin1

mysystem\Admin2

4. Display help for the smcli command

This example displays help for the smcli command. The information displayed is identical to the content of this topic.

smcli

-?

5. Create a credentials file

This example illustrates how to create a persistent copy of the user name and encrypted password that can be used to authenticate the user when running future commands. The PROMPT environment variable is set to yes , so the user is prompted for the password. This example also lists all smcli commands and bundles.

smcli

password:

-c

-user

Administrator

lsbundle

6. Delete the credentials file

This example illustrates how to delete the credentials file.

smcli

-d

Language specifications for smcli commands

IBM Systems Director provides various language-specification methods that can be used with smcli commands.

Although you can use the -L | --lang option in the command syntax to specify the language for commands that run in smcli, you can also define the default language by setting the DIR_LANG environment variable or by retrieving language information from the operating-system language settings. The language-specification methods are applied in the following order:

v

-L | --lang language option in the smcli command syntax

Specifying the language explicitly for a smcli command using the -L | --lang language option overrides all other mechanisms for specifying the language, including the DIR_LANG environment variable and operating-system settings.

v

DIR_LANG environment variable

If the smcli command does not specify the language explicitly using the -L | --lang language option, the value of the environment variable DIR_LANG (if set) is used to specify the language.

v

Operating-system language settings

For Windows, the language is specified using the Regional and Language Options setting.

For AIX and Linux, the values of these variables are used in the following order:

– LC_ALL

– LANG

– LC_LANG

Tip: For messages returned by the smcli command itself, the language is taken from the System language setting for Windows and or the LANG variable for AIX and Linux.

These languages can be specified for the -L | --lang option and DIR_LANG environment variable:

v

de : German

v

en : English

v

es : Spanish

v

fr : French

v

it : Italian

v

ja : Japanese

v

ko : Korean

v

pt_BR : Brazilian Portuguese

v

zh_CN : Simplified Chinese

v

zh_TW : Traditional Chinese

Tips:

v

If you specify the language using the format language_country , where language is

a supported language but country is a not a supported country code for that

language (for example, en_US), then the specified language is used (for example,

in this case en would be used). An error will not be displayed.

v

If

you specify a language that is not supported, irrespective of country code, the

default language is used and an error message will be displayed.

Port configuration for smcli

By default, smcli uses port 2044 to communicate with the IBM Systems Director Server. You can optionally configure the port.

To configure the port, create in the home directory on the management server a file named smcliconfig.prop with the necessary level of access protection. This file contains the port attribute, using the following format:

port=port_number

Create smcliconfig.prop in the appropriate home directory location for your operating system:

v

On Windows, create smcliconfig.prop in My Documents.

v

On AIX or Linux, create smcliconfig.prop in /root/ .

CLILEGACY environment variable

You must set the CLILEGACY environment variable to run the IBM Director v5.20 dircli commands from smcli .

Using the latest smcli commands is recommended; however, dircli commands are supported in this release for compatibility with IBM Systems Director version 5.20 and earlier. To use a dircli command with the same name as an smcli command, you must define the CLILEGACY environment variable and set it to a value of 1 .

Tips:

v

Setting the CLILEGACY environment variable to 1 is useful if you have scripts must run commands using the dircli syntax.

v

The smcli command syntax is displayed when you use the help options ( -? , -h , or --help ) even when the CLILEGACY environment variable to 1. For information about the dircli commands, see the commands reference in the IBM Director v5.20 information center at publib.boulder.ibm.com/infocenter/eserver/

If you do not define CLILEGACY or if you set it to a value of 0, the current command syntax is used.

Alphabetical listing of all smcli commands

The IBM Systems Director smcli commands are grouped in the documentation by function; use this alphabetical listing for quick access to a specific command.

A

accesssys Use the accesssys command to request secured access to systems.

authusergp Use the authusergp command to authorize an existing user group to access the IBM Systems Director Server.

C

cfgcred

Use the cfgcred command to configure credentials for systems managed by IBM Systems Director.

chaudit

Use the chaudit command to modify audit settings.

chcred Use the chcred command to change credentials for systems managed by IBM Systems Director.

checkupd Use the checkupd command to check for new, changed, and superseding updates.

chevtautopln Use the chevtautopln command to change an existing event-automation plan.

chfarm

Use the chfarm command to add a host to or remove a host from a virtual farm or change a virtual farm's attributes.

chgp Use the chgp command to modify groups, including changing membership, modifying attributes, and processing change-specification files.

chled Use the chled command to modify the light-path-diagnostic LED attributes on one or more systems. You can change the status and polling interval.

chnshost Use the chnshost command to change the Storage Area Network (SAN) configuration of one or more system hosts, or detach one or more system hosts from the SAN and optionally remove the volumes.

chnspath Use the chnspath command to set the zoning configuration such that only one path exists between the specified system hosts and the specified storage volumes. You can also use this command to unisolate the system hosts.

chnssys

Use the chnssys command to change the host-type identifier and auto-logical drive transfer (ADT) status on a network-storage system.

chnsvol

Use the chnsvol command to change the name of a logical volume on a network-storage system.

chresmonthresh Use the chresmonthresh command to change the settings of one or more resource monitor thresholds. You can also use this command to activate or deactivate thresholds using this command.

chrole Use the chrole command to change the properties of a role.

chsys Use the chsys command to change the attributes of a system.

chuser Use the chuser command to change the attributes and access settings for a specific user.

chusergp Use the chusergp command to change attributes and access privileges for a user group.

chvrtauth Use the chvrtauth command to authorize one or more platform managers or host systems by setting or revoking authorization credentials.

chvrthost Use the chvrthost command to change the attributes of one or more virtual-server host.

chvs

Use the chvs command to change the attributes of one or more virtual servers.

cleanupd Use the cleanupd command to clean (that is, delete) update files and information in the update library.

collectinv Use the collectinv command to collect data about hardware and software resources that are currently installed on specified systems and to update the database.

D

dconsole Use the dconsole command to run a remote serial console from the IBM Systems Director Server CLI with the purpose of opening the serial console to IBM Power managed systems. This command runs on IBM Systems Director Server for AIX V6.1F or later.

discover Use the discover command to discover resources on networks that are connected to the management server.

dsh

Use the