IBm System Director

IBM Systems
IBM Systems Director Systems Management Guide
Version 6.3

IBM Systems
Version 6.3
Note
Before using this information and the product it supports, read the information in “Notices” on
page 697.
© Copyright IBM Corporation 1999, 2013.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this publication . . . . . . . . ix Groups . . . . . . . . . . . . . . . 88
Conventions and terminology . . . . . . . . ix Creating a criteria-based dynamic group. . . . 93
Publications and related information . . . . . . ix Creating a static group . . . . . . . . . 96
Web resources. . . . . . . . . . . . . . xi Editing a group . . . . . . . . . . . . 97
How to send your comments . . . . . . . . xiii Deleting a group . . . . . . . . . . . 98
Adding a resource to an existing group . . . . 99
Terminology changes . . . . . . . . xv Exporting a group . . . . . . . . . . . 100
Importing a group. . . . . . . . . . . 101
Finding and starting tasks . . . . . . . . . 102
Chapter 1. Overview of IBM Systems Finding a task . . . . . . . . . . . . 102
Director . . . . . . . . . . . . . . . 1 Starting tasks . . . . . . . . . . . . 103
Accessibility . . . . . . . . . . . . . . 1 Launched tasks . . . . . . . . . . . . 104
License information . . . . . . . . . . . . 1 Using External Application Launch . . . . . 117
IBM Systems Director technical overview . . . . . 5 Using Advanced External Application Launch 135
IBM Systems Director components . . . . . . 6 Scheduling tasks . . . . . . . . . . . . 136
Manageable resource types . . . . . . . . 10 Noninteractive tasks . . . . . . . . . . 137
Manageable systems and system types . . . . 11 Jobs and job instances . . . . . . . . . 137
User interfaces . . . . . . . . . . . . 12 Scheduling a task . . . . . . . . . . . 138
Base function and extensible plug-ins. . . . . 13 Scheduling a task from a selected system . . . 140
Upward integration. . . . . . . . . . . 19 Viewing active and scheduled job information 142
Viewing information about scheduled jobs . . 143
Chapter 2. Using the IBM Systems Determining target systems that are affected by
Director Web interface . . . . . . . . 21 a job . . . . . . . . . . . . . . . 144
Logging into IBM Systems Director Server . . . . 21 Viewing job-instance records . . . . . . . 145
Logging out of IBM Systems Director Server . . . 22 Viewing job-instance logs . . . . . . . . 146
Enabling multisession support . . . . . . . . 22 Copying a scheduled job . . . . . . . . 147
Navigating the Web interface . . . . . . . . 22 Editing a scheduled job . . . . . . . . . 148
The Web interface . . . . . . . . . . . 23 Running a scheduled job immediately . . . . 149
Customizing the Web interface . . . . . . . 24 Suspending and resuming a scheduled job . . 150
Managing and closing open pages in the Web Canceling a running job . . . . . . . . . 151
interface . . . . . . . . . . . . . . 26 Deleting a job . . . . . . . . . . . . 151
Viewing help in the Web interface . . . . . . 26 Encrypting interprocess communication . . . . 152
The Welcome banner area . . . . . . . . . 27 Encryption . . . . . . . . . . . . . 152
Navigating IBM Systems Director by way of the Enabling encryption . . . . . . . . . . 154
Home page . . . . . . . . . . . . . . 27 Disabling encryption . . . . . . . . . . 155
IBM Systems Director Home page . . . . . . 27 Changing the encryption algorithm . . . . . 156
System severity states . . . . . . . . . . 36 Resending the encryption key to systems . . . 157
Starting work in IBM Systems Director . . . . 36 Creating a new encryption key . . . . . . 157
Learning about the product . . . . . . . . 37
Checking IBM Systems Director readiness . . . 37 Chapter 3. Discovering systems and
Viewing updates. . . . . . . . . . . . 38 collecting inventory data . . . . . . 159
Viewing tutorials . . . . . . . . . . . 39 Discovery . . . . . . . . . . . . . . 159
Viewing the IBM Systems Director Server System discovery . . . . . . . . . . . 160
summary . . . . . . . . . . . . . . 40 Discovery protocols . . . . . . . . . . 167
Finding and navigating resources . . . . . . . 42 Choosing which discovery method to use . . . . 169
Resource views . . . . . . . . . . . . 43 Viewing the discovery manager summary . . . . 171
Finding systems and other resources . . . . . 55 Renaming discovered systems automatically . . . 173
Viewing resources in the topology perspective. . 56 Discovering systems with system discovery . . . 174
Working with tables . . . . . . . . . . 60 Performing a system discovery . . . . . . 174
Working with topology maps . . . . . . . 71 Discovering systems that use a mirrored image 176
Working with properties . . . . . . . . . 82 Managing systems that have duplicate SSH keys 181
Setting navigation preferences . . . . . . . 84 Discovering IMMs for managing and updating
Renaming a resource . . . . . . . . . . 86 physical servers . . . . . . . . . . . 183
Removing a resource . . . . . . . . . . 87 Discovering VIOS servers managed by an HMC 184
Managing groups . . . . . . . . . . . . 88
© Copyright IBM Corp. 1999, 2013 iii

Discovering the operating systems that have Editing configuration plans. . . . . . . . 230
vCenter installation . . . . . . . . . . 184 Exporting a configuration plan . . . . . . 230
Viewing system discovery results. . . . . . 185 Importing a configuration plan . . . . . . 231
Managing discovery profiles . . . . . . . . 187 Deleting configuration plans . . . . . . . 232
Creating a discovery profile . . . . . . . 187 Managing activation keys by using Feature
Editing, copying, and deleting discovery profiles 188 Activation Manager . . . . . . . . . . . 233
Permanently excluding IP addresses from
discovery . . . . . . . . . . . . . . 189 Chapter 5. Monitoring system status
Collecting and viewing inventory data . . . . . 190 and health. . . . . . . . . . . . . 235
Inventory data and collection profiles . . . . 191
System status and health . . . . . . . . . 235
Creating an inventory collection profile. . . . 192
Viewing the status manager summary . . . . . 238
Managing inventory collection profiles . . . . 193
Viewing the performance summary . . . . . . 239
Collecting inventory . . . . . . . . . . 194
Using the Health Summary task to view the status
Comparing fixes installed on IBM i systems . . 196
of your environment . . . . . . . . . . . 240
Viewing inventory. . . . . . . . . . . 196
Scoreboard . . . . . . . . . . . . . 241
Inventory collection metadata file (twguser.ini) 197
Dashboard . . . . . . . . . . . . . 242
Exporting inventory data . . . . . . . . 198
Health summary . . . . . . . . . . . 242
Connecting to IT Registry and Context Menu
Using the scoreboard to identify issues . . . . 242
Service databases . . . . . . . . . . . . 199
Adding a graphical monitor to the dashboard 245
External connections with IT Registry and
Removing a graphical monitor from the
Context Menu Service databases . . . . . . 201
dashboard . . . . . . . . . . . . . 245
Adding systems to the health summary . . . 246
Chapter 4. Configuring systems . . . 203 Removing a group from the health summary 248
Configuration settings . . . . . . . . . . 203 Using Resource Explorer to view the status of a
Configuration templates . . . . . . . . . . 204 specific resource . . . . . . . . . . . . 248
Predefined configuration template . . . . . 205 Scenarios: Using custom monitor views, thresholds,
Configuration plans . . . . . . . . . . . 205 and event automation plans . . . . . . . . 249
The Automatically deploy feature . . . . . 206 Scenario: Using a custom monitor view in an
Predefined configuration plans . . . . . . 206 event automation plan to report disk data by
Configuration-setting license entitlement . . . . 206 using drive letter names . . . . . . . . . 249
Monitoring the deployment of configuration plans Scenario: Using a custom monitor view in an
and configuration templates . . . . . . . . 207 event automation plan to report cluster drive
Managing system configuration . . . . . . . 208 data using drive letter names . . . . . . . 251
Viewing configuration settings . . . . . . 209 Monitors and thresholds. . . . . . . . . . 254
Editing configuration settings . . . . . . . 209 Monitor views . . . . . . . . . . . . . 255
Saving configuration settings as configuration AIX Monitors view . . . . . . . . . . 255
templates . . . . . . . . . . . . . . 210 All Monitors view . . . . . . . . . . . 258
Saving configuration settings to a configuration Column Management Monitors view . . . . 258
plan . . . . . . . . . . . . . . . 211 Common CIM Monitors view . . . . . . . 258
Backing up configuration settings for a device 212 Common Monitors view. . . . . . . . . 259
Restoring configuration settings for a device . . 212 SNMP Monitors view . . . . . . . . . 261
Managing configuration templates . . . . . . 213 IBM i Monitors view . . . . . . . . . . 261
Creating configuration templates . . . . . . 213 VIOS Monitors view . . . . . . . . . . 266
Creating a configuration template from an Managing monitors . . . . . . . . . . . 269
existing one . . . . . . . . . . . . . 214 Viewing a monitor . . . . . . . . . . 269
Viewing configuration templates . . . . . . 216 Creating a monitor view. . . . . . . . . 270
Editing configuration templates . . . . . . 217 Editing a monitor view . . . . . . . . . 271
Adding configuration templates to a Deleting a monitor view. . . . . . . . . 271
configuration plan . . . . . . . . . . . 218 Graphing a monitor . . . . . . . . . . 271
Deploying configuration templates . . . . . 219 Managing thresholds . . . . . . . . . . . 272
Viewing deployed targets . . . . . . . . 220 Viewing a threshold . . . . . . . . . . 272
Exporting a configuration template . . . . . 221 Creating a threshold . . . . . . . . . . 272
Importing a configuration template . . . . . 222 Editing a threshold . . . . . . . . . . 273
Deleting configuration templates . . . . . . 223 Activating a threshold . . . . . . . . . 273
Managing configuration plans . . . . . . . . 224 Deactivating a threshold. . . . . . . . . 274
Creating configuration plans . . . . . . . 224 Deleting a threshold . . . . . . . . . . 274
Creating a configuration plan from an existing Managing status set entries . . . . . . . . . 274
one . . . . . . . . . . . . . . . . 226 Viewing a specific status set entry . . . . . 275
Deploying configuration plans. . . . . . . 227 Viewing status set entries for a specific resource 276
Viewing configuration plans . . . . . . . 228 Viewing status set entries for a group of
Viewing deployment history . . . . . . . 229 resources . . . . . . . . . . . . . . 276
iv IBM Systems Director Systems Management Guide

Activating a status set entry . . . . . . . 277 Copying an event filter . . . . . . . . . 340
Deactivating a status set entry . . . . . . . 277 Viewing event filter properties . . . . . . 340
Deleting a status set entry . . . . . . . . 278 Viewing predefined filter criteria . . . . . . 341
Deleting a Power Systems status set entry . . . 279 Deleting an event filter . . . . . . . . . 341
Managing the event log . . . . . . . . . . 279 Exporting and importing event automation plans,
Changing backup event log preferences . . . 280 event filters, and event actions . . . . . . . 342
Changing event log preferences . . . . . . 280 Migrating and importing event automation data
Creating an event filter from an event . . . . 280 from a previous version . . . . . . . . . . 342
Deleting an event . . . . . . . . . . . 281 Using command automation . . . . . . . . 343
Replying to an IBM i inquiry message event . . 281 Creating or editing a command definition . . . 343
Viewing events . . . . . . . . . . . . 281 Running a command definition . . . . . . 345
Viewing SNMP device attributes . . . . . . . 282 Restricting anonymous command execution . . 345
Managing MIB files . . . . . . . . . . . 282
Compiling a MIB file . . . . . . . . . . 283 Chapter 7. Updating systems . . . . 347
Loading MIB files into memory . . . . . . 283 Planning to update systems . . . . . . . . 348
Managing process monitors . . . . . . . . 283 Supported update tasks . . . . . . . . . 348
Viewing process monitors . . . . . . . . 284 Supported updates and systems . . . . . . 349
Creating and configuring a process monitor . . 284 Version considerations for updating IBM
Removing process monitors . . . . . . . 284 Director and IBM Systems Director . . . . . 351
Recording resource-monitor statistics . . . . . 285 Update considerations for specific operating
lsresmonrec . . . . . . . . . . . . . 285 systems and platforms . . . . . . . . . 352
mkresmonrec . . . . . . . . . . . . 285 Determining the installed IBM Systems Director
rmresmonrec . . . . . . . . . . . . 285 version . . . . . . . . . . . . . . 362
stopresmonrec . . . . . . . . . . . . 285 Starting to monitor and update systems . . . . 362
Configuring update manager . . . . . . . . 364
Chapter 6. Automating tasks . . . . . 287 Updating IBM Systems Director . . . . . . . 365
Events, filters, and actions in event automation Updating without an Internet connection . . . 366
plans . . . . . . . . . . . . . . . . 288 Acquiring and installing updates . . . . . . . 367
Events. . . . . . . . . . . . . . . 288 Acquiring and installing updates with the IBM
Event filters . . . . . . . . . . . . . 294 Systems Director Web interface . . . . . . 368
Event actions . . . . . . . . . . . . 298 Acquiring and installing updates with the
Monitoring operating-system specific events . . 314 installneeded command . . . . . . . . 396
Mapping SNMP traps to Systems Director events 314 Keeping systems in compliance . . . . . . . 399
Viewing the automation manager summary . . . 319 Compliance policies . . . . . . . . . . 400
Managing event automation plans . . . . . . 321 Adding updates to a compliance policy . . . 401
Copying an event automation plan . . . . . 321 Create and configure compliance policies . . . 401
Creating an event automation plan . . . . . 322 Identifying systems that are out of compliance 403
Deactivating and activating an event automation Resolving compliance issues . . . . . . . 404
plan . . . . . . . . . . . . . . . 323
Deleting an event automation plan . . . . . 324 Chapter 8. Remotely accessing
Editing an event automation plan . . . . . 324 systems and resources . . . . . . . 405
Suspending and resuming event automation
Remote access facilities . . . . . . . . . . 405
plans . . . . . . . . . . . . . . . 325
Distributed Command . . . . . . . . . 405
Viewing event automation plans associated with
File management . . . . . . . . . . . 406
a resource . . . . . . . . . . . . . 325
Launch Web browser . . . . . . . . . . 406
Viewing event automation plan properties. . . 326
Remote Command Line . . . . . . . . . 406
Managing event actions . . . . . . . . . . 326
Remote control tasks . . . . . . . . . . 407
Creating an event action. . . . . . . . . 326
Remote Xen Console . . . . . . . . . . 408
Editing an event action . . . . . . . . . 327
Serial Console . . . . . . . . . . . . 409
Copying an event action. . . . . . . . . 327
Running remote access functions . . . . . . . 409
Testing an event action . . . . . . . . . 328
Using the Distributed Shell . . . . . . . . 409
Deleting an event action . . . . . . . . . 329
Managing files on a remote system . . . . . 412
Saving and not saving an event-action history 329
Establishing command-line access to a remote
Viewing an event-action history . . . . . . 330
system . . . . . . . . . . . . . . 413
Refreshing entries in an event-action history log 331
Launching a Web browser . . . . . . . . 414
Deleting entries from an event-action history log 332
Configuring Microsoft Windows Remote
Viewing event action properties . . . . . . 332
Desktop Connection . . . . . . . . . . 414
Event-data-substitution variables . . . . . . 333
Establishing Remote Desktop Connection . . . 415
Managing event filters . . . . . . . . . . 336
Establishing Virtual Network Computing
Creating, editing, or copying an event filter . . 336
communications . . . . . . . . . . . 415
Editing an event filter . . . . . . . . . 339
Contents v
Establishing IBM BladeCenter or RSA Viewing the management summary . . . . . . 460
communication . . . . . . . . . . . . 416 Downloading and activating I/O module plug-ins 460
Launching the Hyper-V Virtual Machine Configuring integrated management modules . . 461
Connection Tool . . . . . . . . . . . 417 Integrated management module task support
Launching a VMware ESX or ESXi hypervisor and features . . . . . . . . . . . . . 462
virtual machine connection . . . . . . . . 417 Configuring dynamic UEFI settings . . . . . 462
Establishing a remote Xen console session . . . 417 Changing the integrated management module
Accessing POWER managed systems or IP address by way of the server resource . . . 463
x86-based systems by using the serial console . 418 Changing the network port on an integrated
management module . . . . . . . . . . 464
Chapter 9. Managing agents . . . . . 421 Configuring integrated management module
Common agent services . . . . . . . . . . 421 security . . . . . . . . . . . . . . 464
Resource manager . . . . . . . . . . . 421 Configuring the Try DHCP setting for integrated
Agent manager . . . . . . . . . . . . 422 management module . . . . . . . . . . 464
Common agent . . . . . . . . . . . . 423 Enabling Secure Sockets Layer after discovery 465
Logging Platform Agent . . . . . . . . . . 424 Enabling Secure Sockets Layer before discovery 465
Importing agent packages . . . . . . . . . 430 Discovering scalable systems that have multiple
Installing agents using the Agent Installation nodes . . . . . . . . . . . . . . . . 466
Wizard . . . . . . . . . . . . . . . 431 Discovering a scalable BladeCenter system with
Restarting agents . . . . . . . . . . . . 434 multiple nodes . . . . . . . . . . . . 466
Restarting Common Agent . . . . . . . . 435 Discovering a scalable System x system . . . 467
Restarting Platform Agent . . . . . . . . 436 Changing the password for the Remote Supervisor
Setting the agent manager for IBM Systems Adapter or management module . . . . . . . 467
Director Server . . . . . . . . . . . . . 438 Enabling hardware events . . . . . . . . . 468
Viewing the agent manager properties . . . . 438 Managing power state settings on IBM BladeCenter
Adding a new agent manager . . . . . . . 439 and System x servers . . . . . . . . . . . 470
Setting the active agent manager . . . . . . 440 Power On/Off task support using out-of-band
Deleting an agent manager . . . . . . . . 440 communication . . . . . . . . . . . . 470
Using a remote agent manager with IBM Power On/Off task support using Wake on
Systems Director . . . . . . . . . . . 441 LAN technology on System x . . . . . . . 471
Managing the agent manager used by a Power On/Off task support by way of the
Common Agent . . . . . . . . . . . 442 operating system on System x and blade servers 471
Securing Common Agent managed systems . . . 445 Changing the power state on System x and IBM
Changing the agent registration password . . . 445 BladeCenter hardware . . . . . . . . . 472
Migrating common agents to a different agent Enabling collection of SNMP-based inventory by
manager . . . . . . . . . . . . . . . 447 way of management modules . . . . . . . . 473
Binding Platform Agent to specific IP addresses 448 Hardware-log information using out-of-band and
Changing the Common Agent IP address . . . . 449 in-band communication . . . . . . . . . . 473
Critical services for monitoring Platform Agent Viewing hardware-log information . . . . . 474
hardware . . . . . . . . . . . . . . . 449 Refreshing hardware-log information . . . . 475
Configuring Platform Agent for SELinux policies 451 Clearing the hardware-log information . . . . 476
Disabling IBM Systems Director agents . . . . . 452 Providing hardware-log information. . . . . 477
Using locator LED settings on IBM Flex System
Managercompute nodes, IBM BladeCenter, and
Chapter 10. Managing IBM
System x servers . . . . . . . . . . . . 478
BladeCenter, IBM Flex System Locator LEDs and out-of-band and in-band
Manager compute nodes and System communication . . . . . . . . . . . . 478
x systems . . . . . . . . . . . . . 453 Identifying hardware with the locator LED . . 478
Service processor communication. . . . . . . 453 Solving hardware problems by using
In-band communication requirements . . . . 453 light-path-diagnostic LEDs . . . . . . . . . 479
Out-of-band communication requirements . . . 454 Light-path-diagnostic LED information . . . . 479
Out-of-band communication and the standard Changing the resource for viewing
TCP Command Mode protocol . . . . . . 456 light-path-diagnostics LED information . . . . 482
Out-of-band communication and the secure TCP Turning Off the Check Log LED . . . . . . 482
Command Mode protocol . . . . . . . . 457 Viewing light-path-diagnostics status . . . . 482
Out-of-band communication and the standard Viewing detailed light-path-diagnostics
CIM protocol . . . . . . . . . . . . 458 information . . . . . . . . . . . . . 483
Out-of-band alert-forwarding strategies. . . . 458 Configuring templates . . . . . . . . . . 484
Out-of-band event monitoring in a redundant Password security levels for IBM BladeCenter
environment. . . . . . . . . . . . . 459 management modules and System x service
Service processors and resource types . . . . 459 processors . . . . . . . . . . . . . 484
vi IBM Systems Director Systems Management Guide

Configuring the boot sequence for a blade Viewing the System z Management summary page 561
server in an IBM BladeCenter chassis . . . . 486 Discovering systems and collecting inventory data
Configuring an IBM BladeCenter management for System z . . . . . . . . . . . . . . 562
module . . . . . . . . . . . . . . 487 Managing power state settings for Linux on
Configuring network resources for IBM System z servers . . . . . . . . . . . . 563
BladeCenter blade servers . . . . . . . . 504 Power On/Off task support by way of the
Configuring SNMP agent community operating system on System z servers . . . . 563
information . . . . . . . . . . . . . 505 Changing the power state on System z servers 564
Configuring the IP address pool for IBM
BladeCenter systems and System x servers . . 506 Chapter 13. Managing and configuring
Configuring System x service processors . . . 507 storage . . . . . . . . . . . . . . 565
Configuring switch protocol information . . . 519
Planning for storage management . . . . . . 565
Configuring switch virtual LAN information 523
Storage management in real time and using
Configuring users and passwords for an IBM
configuration templates . . . . . . . . . . 566
BladeCenter chassis . . . . . . . . . . 526
Managing SMI-S providers . . . . . . . . . 566
Managing network-configuration information 526
SMI-S providers for IBM Systems Director. . . 567
Managing system-account information . . . . 529
Installing SMI-S Providers . . . . . . . . 571
Setting asset information . . . . . . . . 532
Configuring SMI-S providers . . . . . . . 576
Managing activation keys by using Feature
Discovering and collecting inventory for storage
Activation Manager . . . . . . . . . . . 534
devices . . . . . . . . . . . . . . . 579
Running Discovery and unlocking storage
Chapter 11. Managing IBM Power devices using SMI-S providers. . . . . . . 579
Systems . . . . . . . . . . . . . 537 Running Direct Connection discovery and
New terms for Power Systems users in IBM unlocking storage devices using SMI-S
Systems Director . . . . . . . . . . . . 537 providers . . . . . . . . . . . . . . 580
Managing Power Systems running AIX . . . . . 538 Running System Discovery for multiple SMI-S
Managing Power Systems running IBM i . . . . 539 providers using multicast and broadcast . . . 582
Managing systems controlled by HMC and IVM 540 Collecting inventory for devices managed by
Viewing the Power Systems Management summary 541 IBM Tivoli Storage Productivity Center . . . . 583
Monitoring for IBM i message queue events . . . 542 Working with external storage applications . . . 584
Managing power state settings on IBM Power Installing and configuring external storage
systems . . . . . . . . . . . . . . . 544 applications . . . . . . . . . . . . . 584
Changing the power state on IBM Power Launching an external storage management
systems . . . . . . . . . . . . . . 545 application . . . . . . . . . . . . . 588
Managing storage using shared storage pools . . 545 IBM Systems Director Storage Control 4.2.4 . . 590
Shared storage pools . . . . . . . . . . 545 Viewing storage devices . . . . . . . . . . 592
Requirements for creating and managing shared Storage Management Summary . . . . . . 592
storage pools with IBM Systems Director . . . 548 Viewing storage systems using storage groups 594
Installing the shared storage pool VIOS Displaying attached storage for a given system 595
subagent . . . . . . . . . . . . . . 549 Viewing storage volumes . . . . . . . . 595
Creating a shared storage pool . . . . . . 549 Viewing the health and status of storage devices 596
Viewing the shared storage pool dashboard . . 551 Storage topology perspective . . . . . . . 597
Viewing the storage pool dashboard. . . . . 551 Managing storage in real-time . . . . . . . . 598
Adding physical volumes to a storage pool . . 551 Managing IBM BladeCenter and System x
Replacing physical volumes in a shared storage storage devices . . . . . . . . . . . . 598
pool . . . . . . . . . . . . . . . 552 Adding IBM BladeCenter Integrated Storage
Editing a storage pool threshold . . . . . . 554 devices to a server. . . . . . . . . . . 602
Adding VIOS virtual servers to a shared storage Provisioning storage from an existing storage
pool . . . . . . . . . . . . . . . 554 subsystem . . . . . . . . . . . . . 603
Removing VIOS virtual servers from a shared Managing storage volumes in real time. . . . 604
storage pool . . . . . . . . . . . . . 555 Configuring iSCSI components in real time . . 608
Deleting a shared storage pool . . . . . . 556 Configuring IBM BladeCenter SAS zone
Removing the shared storage pool VIOS connectivity in real time . . . . . . . . . 613
subagent . . . . . . . . . . . . . . 556 Managing storage with configuration templates 615
Viewing storage configuration templates . . . 615
Chapter 12. Managing IBM System z Changing storage configuration templates . . . 616
systems. . . . . . . . . . . . . . 557 Creating a configuration template for a storage
volume . . . . . . . . . . . . . . 616
System z virtualization . . . . . . . . . . 557
Managing IBM BladeCenter SAN configuration
Basics about the z/VM operating system . . . . 557
mapping . . . . . . . . . . . . . . 617
z/VM manageability access point and agent . . . 561
Contents vii
Configuring iSCSI components using Managing shared credentials . . . . . . . 667
configuration template . . . . . . . . . 621 Managing mappings . . . . . . . . . . 672
Managing IBM BladeCenter SAS zone Configuring the authentication registry . . . . 675
configuration . . . . . . . . . . . . 626 Managing targeted credentials . . . . . . . 676
Managing access . . . . . . . . . . . . 681
Chapter 14. Managing virtual Accessing a secured system with request access 681
environments . . . . . . . . . . . 631 Accessing a secured system with configure
access . . . . . . . . . . . . . . . 683
Configuring access to CIM using X509
Chapter 15. Security . . . . . . . . 633 certificates . . . . . . . . . . . . . 684
Authenticating users to IBM Systems Director . . 634 Revoking access to a secured system . . . . 685
User authentication . . . . . . . . . . 634 Managing access to agentless managed systems 685
Users and user groups in IBM Systems Director 635 Accessing a managed system with configure
Authenticating IBM Systems Director users system credentials . . . . . . . . . . . 685
stored in the local operating system . . . . . 637 Configuring access to agentless managed
Authenticating IBM Systems Director users systems using sudo utility and key-pair
stored in the Microsoft Active Directory domain. 638 authentication . . . . . . . . . . . . 686
Authenticating IBM Systems Director users Managing auditing . . . . . . . . . . . 687
stored in LDAP. . . . . . . . . . . . 639 Audit records . . . . . . . . . . . . 687
Editing user properties . . . . . . . . . 651 Setting server-auditing preferences . . . . . 689
Authorizing users to IBM Systems Director . . . 651 Viewing the audit log . . . . . . . . . 690
User authorization. . . . . . . . . . . 652 Deleting the audit log . . . . . . . . . 690
Roles . . . . . . . . . . . . . . . 652 Communication protocols and supported
Permissions and roles required to run smcli encryption algorithms . . . . . . . . . . 691
commands . . . . . . . . . . . . . 654
Authorizing users to manage resources . . . . 658
Appendix. Accessibility features for
Assigning a role to a user or user group . . . 659
Copying a role to another user . . . . . . 660 IBM Systems Director . . . . . . . . 693
Creating a role . . . . . . . . . . . . 660 Accessibility options in IBM Systems Director . . 693
Removing a role from a user . . . . . . . 661 Keyboard navigation in IBM Systems Director . . 694
Removing a role from a group. . . . . . . 662 Using a screen reader with IBM Systems Director 695
Managing roles . . . . . . . . . . . . 662
Ending the session for another user . . . . . 664 Notices . . . . . . . . . . . . . . 697
Changing the time interval between consecutive Trademarks . . . . . . . . . . . . . . 699
resynchronize calls . . . . . . . . . . 664
Managing user groups in IBM Systems Director 664 Glossary . . . . . . . . . . . . . 701
Managing credentials in IBM Systems Director . . 666
viii IBM Systems Director Systems Management Guide

About this publication
This publication provides instructions for using IBM® Systems Director for
systems-management tasks. IBM Systems Director consists of the following tools to
meet your systems-management needs:
v IBM Systems Director Web interface is the graphical user interface (GUI) for IBM
Systems Director Server. Using IBM Systems Director Web interface, you can
conduct comprehensive systems management using either a drop-and-drag
action or a single click.
v IBM Systems Director command-line interface (dircli) is the command-line
interface for IBM Systems Director Server. You can use a command-line prompt
to access, control, and gather information from IBM Systems Director Server.
This documentation also provides planning and implementation information for

event management.
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.
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 http://get.adobe.com/reader/.
Information centers and topic collections

v IBM Systems
http://publib.boulder.ibm.com/eserver/
View the IBM Systems information center landing page, which provides
integrated information for multiple IBM Systems products.
v IBM Systems Director
publib.boulder.ibm.com/infocenter/director/pubs/index.jsp
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
http://publib.boulder.ibm.com/infocenter/director/pubs/topic/extensions/
extensionparent.html
View the IBM Systems information center for information about how to install
and use plug-ins that extend the functionality of IBM Systems Director.
© Copyright IBM Corp. 1999, 2013 ix

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
http://publib.boulder.ibm.com/infocenter/director/devsdk/index.jsp
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.3.3
Provides an easy reference to planning, install and troubleshooting
information for IBM Systems Director
IBM Systems Director Planning Guide
Provides planning information, including hardware requirements for
running IBM Systems Director components, supported IBM Systems
Director hardware, operating systems, databases, and workgroup and
enterprise systems-management software.
PDF files for installing IBM Systems Director Server
Provides detailed instructions to prepare for, install, and configure the IBM
Systems Director Server.
PDF files for installing IBM Systems Director agents
Provides detailed instructions to prepare for and install IBM Systems
Director agents on your managed systems, as well as, prepare for agentless
managed systems.
PDF files for upgrading and migrating IBM Systems Director Server
Provides detailed instructions to upgrade and migrate the IBM Systems
Director Server.
PDF files for upgrading and migrating IBM Systems Director agents
Provides detailed instructions to upgrade and migrate IBM Systems
Director agents.
Provides detailed instructions for using the Web interface and managing
systems and resources in your environment.
IBM Systems Director Troubleshooting Guide
Provides information about problems and how to solve them, and
strategies for troubleshooting common problems.
IBM Systems Director Events Reference
Provides information about IBM Systems Director events, including the
event type, description, severity, and extended details.
IBM Systems Director 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.
x IBM Systems Director Systems Management Guide

White papers and briefs
ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03006usen/
XBW03006USEN.PDF
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
ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03007usen/
XBW03007USEN.PDF
This paper describes the challenges of operational management for enterprise
server installations and the value provided IBM Systems Director.
v Performance Tuning and Scaling Guide for IBM Systems Director 6.3
Hardware requirements for running IBM Systems Director Server
Provides information about how to plan, implement, configure, and use an IBM
Systems Director Server to manage a large configuration with optimal
performance. The Performance Tuning and Scaling Guide also contains
information about the following topics:
– Running IBM Systems Director plug-ins, such as IBM Systems Director Active
Energy Manager® and IBM Scalable Systems Manager
– Integration with Tivoli® products
– Implementing high availability
IBM Redbooks® publications
www.ibm.com/redbooks/
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:
Implementing IBM Systems Director 6.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.
Further information
See Searching knowledge bases for more resources for further information about
IBM Systems Director.
Web resources
Listed here are the websites and information center topics that relate to IBM
Systems Director.
Websites
www.ibm.com/systems/management/director/
About this publication xi

View the IBM Systems Director website on ibm.com® which provides links to
downloads and documentation for all currently supported versions of IBM
Systems Director.
v IBM Systems Director Downloads
www.ibm.com/systems/management/director/downloads/
View the IBM Systems Director Downloads website 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
www.ibm.com/systems/management/director/resources/
View the IBM Systems Director Documentation and Resources website on
ibm.com which provides links to product documentation, Redbooks, redpapers,
white papers, and learning modules that are related to IBM Systems Director,
IBM Systems Director plug-ins, and IBM Systems Director upward integration
modules.
v IBM Systems Director Upward Integration
www.ibm.com/systems/software/director/downloads/integration.html
View the IBM Systems Director Upward Integration website on ibm.com which
provides more information about IBM Systems Director upward integration
modules that are 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 Systems Director Best Practices Wiki
https://www.ibm.com/developerworks/mydeveloperworks/wikis/
home?lang=en#/wiki/W3e8d1c956c32_416f_a604_4633cd375569/page/Best
%20Practices
View updated documentation and best practices for IBM Systems Director on
various systems.
v IBM Servers
www.ibm.com/servers/
View the IBM Servers website to learn about IBM Systems server and storage
products.
v IBM ServerProven®
www.ibm.com/servers/eserver/serverproven/compat/us/
View the IBM ServerProven website 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 Forum (System x, System z®, Power Systems™)
www.ibm.com/developerworks/forums/forum.jspa?forumID=759
View the IBM Systems Director Forum website on ibm.com to discuss
product-related issues that pertain to IBM Systems Director, IBM Systems
Director UIMs, and IBM Systems Director extensions. This website includes a
link for obtaining the forum by using a Rich Site Summary (RSS) feed.
v IBM Systems Director 6.x SDK Forum
www.ibm.com/developerworks/forums/forum.jspa?forumID=1852&start=0
xii IBM Systems Director Systems Management Guide

View the IBM Systems Director 6.x SDK Forum website to discuss issues that
pertain to the IBM Systems Director Software Development Kit (SDK). This
website includes a link for obtaining the forum by using a Rich Site Summary
(RSS) feed.
v IBM Systems Forums
www.ibm.com/developerworks/forums/dw_esforums.jsp
View the IBM Systems Forums website on ibm.com to learn about various
forums that are available to discuss technology-related and product-related
issues that pertain to IBM Systems hardware and software products. This
website includes a link for obtaining the forum by 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
publib.boulder.ibm.com/infocenter/director/pubs/index.jsp. There you will find
the feedback page where you can enter and submit comments.
About this publication xiii

xiv IBM Systems Director Systems Management Guide
Terminology changes
Several terms changed between IBM Director v5.x and IBM Systems Director v6.x.
Deprecated terms New terms Description

IBM Director Agent Common Agent Common Agent provides a rich set of
security, deployment, and management
function. The function available for
Common-Agent managed systems varies
based on operating system and hardware,
and includes the following tasks: discover
systems; collect comprehensive platform
and operating system inventory data;
monitor health and status; manage alerts;
remotely deploy and install Common
Agent; perform remote access, including
transferring files; perform power
management function; more event support;
monitor processes and resources, and set
critical thresholds that send notifications
when triggered; manage operating system
resources and processes.
IBM Director Core Platform Agent Platform Agent provides a lighter footprint
Services and fewer management functions than the
Common Agent. The function available for
Platform-Agent managed systems is limited
to the following tasks, and varies based on
operating system and hardware: discover
systems, collect limited platform inventory
data, monitor health and status, manage
alerts, remotely deploy and install Common
Agent, perform limited remote access, and
perform limited restart capabilities.
Level-2 managed Common Agent A system on which Common Agent is
object managed system installed
Level-1 managed Platform Agent A system on which Platform Agent is
object managed system installed
Level-0 managed Agentless managed A system that does not have an agent that is
object system installed but can be discovered by IBM
Systems Director using Secure Shell (SSH),
Distributed Component Object Model
(DCOM), or Simple Network Management
Protocol (SNMP).
The function available to

Agentless-managed systems is limited to the
following tasks, and varies based on
systems, collect limited operating-system
inventory data, remotely deploy, and install
Common Agent and Platform Agent,
perform limited remote access, and perform
limited restart capabilities
© Copyright IBM Corp. 1999, 2013 xv

Deprecated terms New terms Description
Managed object System A hardware endpoint that can be discovered
and managed by IBM Systems Director. For
example, storage devices, network devices,
physical servers, virtual servers, and virtual
farms are systems.
Extension Plug-in Free or for-fee software that is downloaded
and installed on top of IBM Systems
Director to provide more function.
Job activation Job instance A specific occurrence of a job that is
running or is finished.
Event action plan Event automation A user-defined plan that determines how
plan IBM Systems Director automatically handles
certain events. An event action plan
comprises one or more event filters and one
or more customized event actions.
Hardware control Platform manager Software that manages one or more host
point systems and their associated virtual servers
and operating systems. Platform managers
can be started from the IBM Systems
Director web interface. For example, IBM
BladeCenter Management Module, IBM
Hardware Management Console (HMC),
IBM Integrated Virtualization Manager
(IVM), and VMware VirtualCenter are
platform managers.
Configuration profile Configuration plan A collection of templates that are used to
configure hardware and operating systems.
Component Template A stored version of definition parameters
for the configuration of a specific system.
Remote session Remote command A command-line interface to a remote
line system.
xvi IBM Systems Director Systems Management Guide

Chapter 1. Overview of IBM Systems Director
You can read an overview of IBM Systems Director, including supported hardware
and software requirements, technical overview, web resources, and what is new in
this release.
Accessibility
IBM strives to provide products with usable access for everyone, regardless of age
or ability.
The reference topic Accessibility features for IBM Systems Director provides details
about the accessibility support, tips, and workarounds of the product.
To learn about IBM Systems Director accessibility of the information center

interface, see the topic Keyboard navigation in IBM Systems Director
Note: For technical details about the accessibility support in IBM Systems Director,
see the Voluntary Product Accessibility Templates (VPATs). You can request VPATs
from the web at http://www.ibm.com/research/accessibility/requests/
accvpat.nsf/bidxjs?OpenForm.
License information
Before deploying this product, ensure that you have the necessary licenses.
IBM Systems Director
The IBM Systems Director program contains Management Server (Manager)

components, Agent components, and application programming interfaces (APIs), as
further described in the documentation.
You are authorized to use Management Server and Agent components only on IBM
machines.
Notwithstanding the foregoing, the IBM Systems Director program includes a

license for up to 20 installations of the Agent component on non-IBM x86 systems.
These 20 licenses for non-IBM x86 systems are not transferable and cannot be
combined or aggregated. For example, if you buy two IBM machines and install
the IBM Systems Director program on only one of them, you are entitled to install
the Agent component on only 20 non-IBM x86 systems. If you install the IBM
Systems Director program on both IBM machines, your entitlement is limited to
managing 20 non-IBM x86 systems. To install additional Agent components on
non-IBM x86 systems, you must obtain additional Agent component licenses from
IBM.
Authorization for IBM Systems Director for Power Systems
Processor is a unit of measure by which the IBM Systems Director for Power
Systems program can be licensed. Processor (commonly called a processor core or
CPU) is a functional unit within a computing device that interprets and executes
instructions. A processor consists of at least an instruction control unit and one or
more arithmetic or logic unit. With multi-core technology, each core is considered a
© Copyright IBM Corp. 1999, 2013 1

processor. Authorization for the IBM Systems Director for Power Systems program
is based on the total number of activated processors (including any temporary
processors) on the machines running the IBM Systems Director for Power Systems
program and the total number of activated processors (including any temporary
processors) on the machines being managed by the IBM Systems Director for
Power Systems program.
Authorization for IBM Systems Director for IBM x86 servers
Server is a unit of measure by which the IBM Systems Director for IBM x86 servers
program can be licensed. A Server is a physical computer that is comprised of
processing units, memory, and input/output capabilities and that executes
requested procedures, commands, or applications for one or more users or client
devices. Where racks, blade enclosures, or other similar equipment is being
employed, each separable physical device (for example, a blade or a rack-mounted
device) that has the required components is considered itself a separate server.
The IBM Systems Director for IBM x86 servers program uses a per Server charging
metric. An authorization is required for each server running the IBM Systems
Director for IBM x86 servers program and for each server being managed by the
IBM Systems Director for IBM x86 servers program.
Terms applicable to API use
The IBM Systems Director program includes APIs called Representational State
Transfer (REST) APIs and Advanced External Application Launch (AEAL) function.
The IBM Systems Director REST APIs and AEAL function are described in the
documentation, available through the IBM Systems Director Information Center. If
you own or separately develop an interface to hardware that provides similar
function or feature as the REST APIs or AEAL function, or if the Licensee offers
hardware that provides similar function or feature as the REST APIs or AEAL
function, the following terms apply:
v You may develop applications using the Program's REST APIs and/or AEAL
function solely for testing and deployment within your Enterprise and only in
connection with your internal business purposes. An Enterprise is any legal
entity (such as a corporation) and the subsidiaries it owns by more than 50
percent.
v You may not rent, lease, loan, sell or otherwise distribute applications or
derivative works created using the IBM Systems Director REST APIs and/or
AEAL function to third party end users external to your Enterprise unless you
have entered into a written contract with IBM for this purpose.
Warranty
The IBM Systems Director program contains Upward Integration Modules (as
described in the documentation) for third party system management products to
manage IBM hardware platforms with Common Agent components. There is no
warranty or support service available for the Upward Integration Modules when
you use a third party system management product.
Special terms for the Software Update component
When you use the Software Updates navigation link of the IBM Systems Director
program to request software updates, the Management Server component collects
information about the release level of certain software products installed on your
2 IBM Systems Director Systems Management Guide

machine ("Software Information") and electronically sends that Software
Information to IBM. Software Information does not include business data such as
your financial, statistical and personnel data regarding your business. You agree
that IBM (including subcontractors and consultants under contract to IBM) may
store and use Software Information for purposes of software maintenance and
support, and that such Software Information (including any contact information
provided by you) may be transferred to such entities in any country whether or
not a member of the European Union.
Software Updates Licensee receives are covered by this Agreement. If any

additional or different terms apply to any such Software Update, such terms will
be included with the Software Update.
Supporting program details - IBM DB2®
The following applies to use of IBM DB2 Enterprise Server Edition.

Use Limitations: Use by Principal Program
"Use by Principal Program" means that neither you nor any application,
program, or device external to the Principal Program is authorized to
directly use or access the services of IBM DB2 Enterprise Server Edition in
any way. The IBM DB2 Enterprise Server Edition program is provided
exclusively for use by the Principal Program. You may access IBM DB2
Enterprise Server Edition only to perform administrative functions, such as
backup, recovery, and authorized configuration but may not directly use
the IBM DB2 Enterprise Server Edition program for any productive use.
Program details - IBM Systems Director Active Energy Manager
IBM Systems Director Active Energy Manager contains monitor function and
management function. The terms of this license apply to your use of the monitor
function. The management functions may be used for internal evaluation, testing,
or demonstration purposes for 90 days without a valid License Key. After 90 days
the management function will not operate without a valid License Key. If you want
to continue to use the management function to manage your systems after 90 days,
you must then obtain a valid License Key. Active Energy Manager uses a
per-processor or per-server charging metric, depending on platform.
Power Systems servers
For Power Systems servers, a processor license is required for every
processor on every Power Systems server being managed by the program.
Servers are categorized as small, medium, or large based on criteria such
as server model. Authorization for IBM Systems Director Active Energy
Manager is based on the total number of activated processors (including
any temporary processors) on the machine(s) running the program and the
activated processors (including any temporary processors) on the
machine(s) being managed by the program.
If you want to use the management function to manage IBM x86 servers,
you must obtain an authorization for IBM Systems Director Active Energy
Manager for IBM x86 or IBM Systems Director Standard Edition for IBM
x86. If you want to use the management function to manage IBM System
zservers, you must obtain an authorization for IBM Systems Director
Standard Edition for Linux on System z.
System x servers
For System x servers, a license is required for every IBM x86 server being
managed by IBM Systems Director Active Energy Manager. An
Chapter 1. Overview 3
authorization is required for each server running IBM Systems Director
Active Energy Manager and for each server being managed by IBM
Systems Director Active Energy Manager.
If you want to use the management function to manage Power Systems,
you must obtain an authorization for IBM Systems Director Active Energy
Manager for Power Systems, IBM Systems Director Standard Edition for
Power®, or IBM Systems Director Enterprise Edition for Power. If you want
to use the management function to manage IBM System z servers, you
must obtain a valid license key for IBM Systems Director Standard Edition
for Linux on System z.
Program details - IBM Systems Director VMControl
IBM Systems Director VMControl contains life cycle management functions, image
manager functions, and system pools functions. The terms of this license apply to
your use of the life cycle management functions. The image manager and system
pools functions may be used for internal evaluation, testing, or demonstration
purposes for 90 days without a valid License Key. After 90 days the image
manager and system pools functions will not operate without a valid License Key.
If you want to continue to use the image manager functions and/or the system
pools functions to manage IBM Power Systems after 90 days, you must obtain a
valid license key.
Power Systems servers
Authorization for IBM Systems Director VMControl Enterprise Edition for
Power Systems and IBM Systems Director VMControl Standard Edition for
Power Systems is based on the total number of activated processors
(including any temporary processors) on the machine(s) being managed.
If you want to move the authorization to manage a Power Systems
machine which has a higher authorization requirement or manage
additional Power Systems machines, you agree to notify IBM or its reseller
and agree to acquire the required authorization. If you want to use the
image manager functions and/or system pools functions to manage IBM
x86 servers, you must obtain an authorization for IBM Systems Director
VMControl Enterprise Edition for IBM x86. If you want to use the image
manager functions to manage IBM System z servers, you must obtain an
authorization for IBM Systems Director Standard Edition for Linux on
System z.
System x servers
An authorization is required for each server being managed by IBM
Systems Director VMControl Enterprise Edition for IBM x86.
If you want to use the image manager functions to manage IBM Power
Systems or IBM System z servers, you must obtain an authorization for
IBM Systems Director Standard Edition for Power, IBM Systems Director
VMControl Standard Edition, or IBM Systems Director Standard Edition
for Linux on System z. If you want to use the system pools functions to
manage IBM Power Systems servers, you must obtain an authorization for
IBM Systems Director Enterprise Edition for Power or IBM Systems
Director VMControl Enterprise Edition for Power.

IBM Systems Director technical overview
IBM Systems Director is a platform-management foundation that streamlines the
way you manage physical and virtual systems across a heterogeneous
environment. By using industry standards, IBM Systems Director supports multiple
operating systems and virtualization technologies across IBM and non-IBM x86
platforms.
IBM Systems Director provides consistent views for viewing managed systems,
determining how these systems relate to one another, and identifying their
statuses. You can use these views to correlate your technical resources with your
business needs. A set of common tasks included with IBM Systems Director
provides many of the core capabilities required for basic management. Use these
tasks to achieve instant business value. These common tasks include discovery,
inventory, configuration, system health, monitoring, updates, event notification,
and automation across managed systems.
The web and command-line interfaces in IBM Systems Director provide a

consistent interface that is focused on driving these common tasks and capabilities:
v Discovering, navigating, and visualizing systems on the network with the
detailed inventory and relationships to the other network resources
v Notifying users of problems that occur on system and ability to drill down to
the source of the problem
v Notifying users when systems need updates and distributing and installing
updates on a schedule
v Analyzing real-time data for systems and setting critical thresholds that notify
the administrator of emerging problems
v Configuring settings of a single system and creating a configuration plan that
can apply those settings to multiple systems
v Updating installed plug-ins to add new features and function to the base
capabilities
v Managing the lifecycle of virtual resources
IBM Systems Director is designed to manage simple and complex environments,

with multiple operating systems and platforms, up to 5 000 managed systems. It
supports the management of IBM and non-IBM hardware and drives common
tasks through the following platform management plug-ins and virtual resources:
v IBM Power Systems management
– HMC, IVM, and VIOS appliances
– Power servers, Power blades, and LS41 and QS21 blade servers
– AIX®, IBM i, and Linux on POWER® operating systems
v IBM BladeCenter chassis management
– IBM BladeCenter chassis components, such as switch modules and server
blades
– VMWare virtual servers
v IBM System x management
– System x systems and blade servers
– Windows and Linux operating systems on System x
v IBM System z management
– z/VM® hypervisor
– Linux on System z operating system installed on z/VM virtual servers
– Linux on System z running on a partition without z/VM
v IBM System Storage® management
– Integrated RIA controller (such as LSI)
– Network storage, such as DS3000, DS4000®, DS5000, and DS6000™
– Storage switches, such as IBM BladeCenter SAS, Brocade, QLogic, Nortel, and
Cisco
v Some IBM Flex System hardware.
IBM Systems Director integrates with robust workgroup and enterprise

management software from IBM (such as Tivoli software), Computer Associates,
Hewlett-Packard, Microsoft, NetIQ, and BMC Software.
IBM Systems Director components

IBM Systems Director includes IBM Systems Director Server and two
operating-system agents: Common Agent and Platform Agent.
IBM Systems Director Server provides a central point of control for aggregating
and managing discovered systems based on a service-oriented architecture. It can
be installed on one or more systems, called management servers. Systems that
connect to the IBM Systems Director web interface on the management server
through a web browser are called browser systems.
The operating-system agents serve as the control point for accessing operating
system and host information that might not be accessible through an out-of-band
interface (such as remote supervisor adapter (RSA), Baseboard Management
Control (BMC), and BladeCenter Management Module). These agents run on
operating-system-based and hardware-based endpoints, called systems, that can be
discovered and managed by IBM Systems Director. The level of system
management depends on the agent that is installed on the system: Common Agent
or Platform Agent. Each agent provides a different footprint size, level of
performance, and set of management functions.
IBM Systems Director can discover and manage some systems on which neither of
these operating-system agents is installed, but the level of management is limited.
This figure shows where the IBM Systems Director Server and operating-system
agents are installed in a basic IBM Systems Director environment.

Management server
Systems Director installed includes:

- Management Server
- Web Interface
- Command-line Interface
- Common Agent
- Platform Agent
- Service and Support Manager
- Active Energy Manager
- VMControl
HTTPS TCP/IP Various protocols
Browser system SNMP devices

- no Systems Director Agentless managed systems Agentless managed systems
code installed - no Systems Director code - no Systems Director code
installed installed
Platform managed systems

- Platform Agent installed
on each
Common managed systems

- Common Agent installed
FQM0553-0
on each
Figure 1. Software in an IBM Systems Director environment
Management server
The management server is a system that has IBM Systems Director Server installed.
It provides a central point of control for aggregating and managing discovered
systems based on a service-oriented architecture.
IBM Systems Director Server stores data about discovered systems, their attributes,
and their relationships to other resources in a relational database. You can access
information that is stored in this database even when the managed systems are not
available. IBM Systems Director Server includes a default database, the managed
IBM DB2 database, although you can choose to use any supported database.
IBM Systems Director Server includes two interfaces that the system administrator
can use to manage their environment: a web user interface and a command-line
interface. The system that you use to interact with these interfaces is called the
browser system.
Tip: When you install IBM Systems Director Server, the Common Agent is
installed automatically on that system. The Common Agent provides a rich set of
security, deployment, and management function.
Common Agent
Common Agent provides a rich set of security, deployment, and management
function.
Common Agent is available for all Power Systems, System x, IBM BladeCenter,
System z systems, and some non-IBM systems, when the system is running a
supported operating system.
Notes:
v Systems running AIX require Common Agent to be installed. These systems
cannot be managed with Platform Agent.
v For a detailed list of operating systems that are supported for Common Agent,
see the Planning information.
Common Agent replaces Level 2: IBM Director Agent version 5.20. IBM Systems
Director 6.x supports agent systems running either Common Agent version 6.x or,
depending on the platform, the older Level 2: IBM Director Agent version 5.20.
The functionality that is available for Common Agent managed systems varies
based on the operating system and hardware in an environment, and includes the
following items:
v Discover systems
v Collect comprehensive platform and operating system inventory data
v Monitor health and status
v Manage alerts
v Remotely deploy and install Common Agent
v Perform remote access, including transferring files
v Perform power management function
v Additional event support
v Monitor processes and resources, and set critical thresholds send notifications
when triggered
v Manage operating system resources and processes
v Manage updates
Additionally, using Common Agent instead of Platform Agent provides enhanced
scalability through asynchronous system management, which reduces the demands
on IBM Systems Director Server. Firewall management is simplified, too, because
Common Agent requires that you keep fewer ports open.
For a detailed list of functionality that is supported by Common Agent managed

systems, see the Planning information.
Note: Throughout the IBM Systems Director documentation, the term Common
Agent (with both words capitalized) refers to the IBM Systems Director Common
Agent, which includes subagents that provide specific management capabilities for
IBM Systems Director. IBM Systems Director can also discover and perform limited
management on other common agents that use the common agent services (CAS)
architecture. When referring to these common agents generically, lowercase text is
used.

For information about resource managers and agent managers, see “Common
agent services”.
Platform Agent
Platform Agent is suited for environments that require a smaller footprint without
sacrificing a high level of manageability. It provides a subset of Common Agent
function used to communicate with and administer the managed systems,
including hardware alerts and status information.
Platform Agent is available for all IBM Power, System x and IBM BladeCenter, and
System z, IBM System Storage systems, and some non-IBM systems.
For IBM i, Platform Agent is part of the IBM Universal Manageability Enablement
for i Licensed Program Product that ships with the base operating system.
Platform Agent replaces Level 1: IBM Director Core Services version 5.20. IBM
Systems Director Server 6.x supports agent systems running either Platform Agent
6.x or, depending on the platform, IBM Director Core Services version 5.20.
Note: The version level of Platform Agent might not match the version levels of
IBM Systems Director Server or Common Agent.
The function available for Platform Agent managed systems is limited to the
following tasks, and varies based on operating system and hardware.
v Discover systems
v Collect limited platform inventory data
v Monitor health and status
v Manage alerts
v Remotely deploy and install Common Agent
v Perform limited remote access
v Perform limited restart capabilities
For a detailed list of function that is supported by Platform Agent managed

systems, see the Planning information in the information center at.
Agentless managed systems

IBM Systems Director provides a set of manageability functions for managed
systems that do not have Common Agent or Platform Agent installed. These
Agentless managed systems are best for environments that require small footprints
and are used for specific tasks, such as one-time inventory collection, firmware and
driver updates, and remote deployment.
Agentless managed systems must support the Secure Shell (SSH) or Distributed
Component Object Model (DCOM) protocol, or the Simple Network Management
Protocol (SNMP) interface. IBM Systems Director discovers Agentless managed
systems by verifying the IP addresses on your network and scanning the ports of
those addresses using the SSH or DCOM protocols. By default, IBM Systems
Director uses the range of addresses that are in the IP domain of the management
server. You can discover a specific IP address or range of IP addresses using the
IBM Systems Director Web interface.
When an Agentless managed system is discovered, it is locked by default. You can

unlock the system by requesting access to it through IBM Systems Director.
Agentless managed systems are suited for one-time collection of inventory, and can
be used for updating firmware and drivers, and remotely deploying and running it
through SSH or DCOM services.
Note: No persistent data is stored on Agentless managed system.
The function available to Agentless managed systems is limited to the following

tasks, and varies based on operating system, platform, and hardware.
v Discover systems
v Collect limited operating-system inventory data
v Remotely deploy and install Common Agent and Platform Agent (root access
required)
v Perform limited remote access
v Perform limited restart capabilities
For a detailed list of function that is supported by Agentless managed systems, see
the “Planning for IBM Systems Director” section in the information center at
publib.boulder.ibm.com/infocenter/director/pubs/topic/
com.ibm.director.plan.helps.doc/fqm0_r_planning.html.
Database application
IBM Systems Director uses a database to store information that it collects from the
endpoints that it manages.
You can configure a custom database to use with IBM Systems Director or you can
use the managed IBM DB2 database that is included with IBM Systems Director
Server 6.3.x.
Managed IBM DB2 database
The managed IBM DB2 database is packaged and installed with IBM Systems
Director Server 6.3.x. It is the default database for IBM Systems Director Server
6.3.x. You can store data only from IBM products, such as IBM Systems Director
and Storage Control, in the managed IBM DB2 database.
The managed IBM DB2 database is a subset of IBM DB2 Database Enterprise
Server Edition version 9.7 with fix pack 4. It includes the necessary JDBC driver
and the command-line interface. It does not include the IBM DB2 Control Center.
Unlike a regular IBM DB2 database, IBM Systems Director installs the managed
IBM DB2 database on the same server as IBM Systems Director Server. If you use a
regular IBM DB2 database, you can install and run IBM DB2 on the same server or
on a different server as IBM Systems Director Server.
It is possible to install and run the managed IBM DB2 database on the same server
as another IBM DB2 database that is used for another purpose. However, to reduce
the complexity of managing your resources, do not run multiple IBM DB2
databases on the same server. Instead, run the managed IBM DB2 database on one
server and the other IBM DB2 database on a different server.
Manageable resource types

A resource is a generic term for anything that IBM Systems Director can manage.
For example, systems, slots, cards, groups, and updates are all resources.

From the web interface, you can use the Find a Resource task to find resources.
You can also use the Resource Explorer task to view and work with these
resources.
Manageable systems and system types

A system is one type of resource that IBM Systems Director manages. It is an
operating-system-based or hardware-based resource that has an IP address and
host name and can be discovered and managed by IBM Systems Director. From the
Resource Explorer page in the IBM Systems Director Web interface, you can view
the All Systems group to work with all discovered systems.
Operating-system-based systems
Operating-system-based systems (referred to as operating systems) consist
of the operating system image, agent, drivers, applications, and
configuration settings. From the Resource Explorer page in the IBM
Systems Director Web interface, you can view the All Operating Systems
group to work with these types of systems.
Hardware-based systems
Hardware-based systems are the physical and virtual systems, such as
servers, virtual servers, storage systems, and network devices. Physical
systems can host multiple operating systems and virtual servers, either by
using a dual-boot feature or by way of a hypervisor. From the Resource
Explorer page in the IBM Systems Director Web interface, you can use the
All Network Systems, All Storage Systems, or All Systems groups to work
with the physical aspects of a system, determine how many virtual servers
a physical system contains, and determine how many operating systems
are running on a physical system.
To view the relationships between systems, view the topology map view for a
system by selecting the system and then clicking Actions > Topology Perspectives.
A submenu of applicable perspectives is displayed.
To view resources associated with a system, select the system and then click
Actions > Related Resources. A submenu of applicable related resources is
displayed.
IBM Systems Director manages the following types of systems:

Chassis
A physical resource that encloses other resources and provides definable
functions. Example types include a desktop, processing node,
uninterruptible power supply, disk or tape storage, or a combination of
these types.
Cluster
A computer system that is composed of two or more computer systems
that operate together to increase performance, reliability, availability, and
serviceability.
ComputerSystem
A single component that runs one operating system, or multiple
components that are controlled by one or more operating systems.
GenericNetworkDevice
A computer system that has an unknown device type.
HardwareManagementConsole
A computer system that controls managed systems. This includes the
management of logical partitions and the use of Capacity on Demand.
OperatingSystem
Software that is responsible for the formation of an execution environment
and allocations of resources for software programs on a computer.
PassThroughModule
A Pass-Thru module.
Server A single node computer system such as a desktop, mobile device, or
NetPC. The Server class type is derived from the ComputerSystem class
type.
StorageSubsystem
A computer system that is dedicated to acting as a storage server.
Switch
A computer system that is dedicated to acting as a switch for network
traffic.
SystemChassis
A computer system that represents a modular enclosure that contains one
or more blades.
You can use the lssys -I command to obtain a list of valid system types for
commands such as discover.
With virtualization, you can hide the physical characteristics of your servers to
consolidate servers, optimize resource usage, and improve IT flexibility and
responsiveness. Using virtualization, you can create multiple discoverable virtual
servers from a single physical server or create a single discoverable virtual server
from multiple physical servers. Each virtual server has an independent operating
environment and can have functions or features that are not available in its
underlying physical resources.
Tip: Virtual servers running on IBM systems are often referred to as logical
partitions or virtual machines.
After IBM Systems Director discovers a physical server, it continues the discovery
process to find all associated virtual servers. Each IBM system offers virtualization
technologies to help you consolidate systems, optimize resource utilization, and
improve IT flexibility and responsiveness.
User interfaces
There are several methods for managing an IBM Systems Director environment: a
web interface and a command-line interface (smcli).
Web interface
You can use the IBM Systems Director Web interface to conduct comprehensive
systems management through a graphical user interface. Data is securely
transferred between the web browser and web interface through HTTPS.
The system on which you logged in to the IBM Systems Director Web interface is
referred to as the browser system. You log in to the IBM Systems Director through a
supported web browser with the following URL:
http://System_Name:Port_Number/ibm/console

where System_Name is the name of the system on which IBM Systems Director
Server is installed and Port_Number is the first (lower) of two consecutive port
numbers that you specified for the Web server to use. The default ports for the
Web server are 8421 and 8422. If you use port 8422, make sure that you specify
https to indicate a secure port.
Command-line interfaces
You can use the systems management command-line interface interactively using
the smcli utilities. This command-line interface (CLI) is an important primary
interface into IBM Systems Director and can be used either as an efficient way to
accomplish simple tasks directly or as a scriptable framework for automating
functions that are not easily accomplished from a graphical user interface. For
security reasons, the CLI runs only on the management server.
The command-line interface follows the GN/POSIX conventions.
Tips:
v The IBM Systems Director smcli supports most commands that were available in
previous releases through the discontinued dircli utility.
v For security, the CLI runs only on the management server. You can run the CLI
remotely using a remote-access utility, such as Secure Shell (SSH) or Telnet.
Base function and extensible plug-ins

Base plug-ins in IBM Systems Director provide core function to manage the full
lifecycle of IBM servers, storage, network, and virtual servers. Plug-ins that
provide advanced function or function that is tailored to a particular environment
can be downloaded and installed on top of IBM Systems Director.
Basic user interface, security, and agent management functions include:

v Finding and viewing resources and resource information, including relationships
and properties
v Organizing logical sets of resources into groups
v Starting, stopping, and scheduling tasks in IBM Systems Director
v Integrating third-party management software and other programs into the IBM
Systems Director Web interface
v Managing auditing
v Encrypting interprocess communication
v Managing Common Agent registration and authentication
v Authenticating users through a configured user registry available from the
operating system, Lightweight Directory Access Protocol (LDAP), or domain
controller
v Creating roles and authorizing users and user groups to access certain systems,
groups, and tasks
v Managing credentials to support single sign-on authentication, even when
services span different systems
v Installing, upgrading, and promoting agents
Discovery manager
Discovery manager performs physical and virtual system discovery and inventory
of related resources on the network.
You can use the discovery manager plug-in to:
v Discover systems and other resources (such as physical and virtual servers,
storage systems, and network devices) in a heterogeneous environment. Discover
resources by using a single IPv4 or IPv6 address, a single host name, a range of
IP addresses, or use a discovery profile to discover systems of different types
across multiple subnets.
v Collect inventory data about hardware and software that is installed on systems.
Inventory data is information about physical, logical, and virtual hardware (such
as virtual systems, virtual servers, and farms), software applications, operating
systems, middleware, firmware and BIOS, diagnostic information, and network.
v Manage inventory profiles that you can use to discover a group of resources or
collect inventory data based on a set of criteria.
v View systems, inventory data, and relationships among systems in the network
by using Resource Explorer.
v Request access to manage security credentials for discovered systems.
Status manager
Status manager provides an at-a-glance view of the health of your managed
resources (including systems, operating systems, applications, processes, and
security).
The status of discovered systems is automatically retrieved and displayed, and this
display can be customized in several ways: using one of the system status and
health tasks, navigating to a specific resource, or by using the command-line
interface.
You can use the status manager plug-in to:

v Use the Status Manager Summary page to view the status of discovered systems
and a summary of tasks that help you manage the status, problems, and events
for systems.
v Determine the health, compliance, and performance of managed systems in your
environment by using the health summary, scoreboard, and dashboard. The
health summary shows the overall health of your managed systems. The
scoreboard summarizes the hardware state, event state, and compliance state for
all managed systems. The dashboard shows performance information for specific
managed systems.
v View the event log.
v Identify problems and find the root cause by viewing detailed information about
the problems and inspecting the event log.
v Monitor dynamic properties of resources by defining monitors and thresholds.
v Monitor applications on a specific system by defining process monitors.
v Automatically send notifications when devices and services on a specific system
reach or exceed a particular setting by defining thresholds.
Configuration manager
Configuration manager is used to integrate new hardware into your environment,
configure systems after installation, or do one-off configurations for problem
resolution. Configuration manager uses a set of well-defined templates that can be
applied to servers, storage, and network resources even if the resources are
composed of different technologies.
You can use the configuration manager plug-in to:

v Use the Configuration Manager Summary page to view system configuration
status and a summary of tasks that help you configure your systems.
v Initially configure one or more systems (hardware and operating systems) to a
point where they can be deployed, allocated, and powered on.
v Automatically configure newly discovered systems by using the
automatic-deploy capability of a configuration plan.
v Reconfigure systems to prepare for redeployment, reallocation, or reprovisioning
(for example, as a result of an event or as part of a workflow that the
configuration needs to be support).
v Manage configuration templates and plans. A configuration template is a collection
of settings and values that define the configuration of a system. A configuration
plan is a set of templates that can be applied to one or more systems in a specific
order.
Automation manager
Automation manager provides tools to notify an administrator or run a predefined
task automatically when a certain event occurs.
You can use the automation manager plug-in to:

v Use the Automation Manager Summary page to view the status of jobs and
automation plans and a summary of tasks that help you automate tasks.
v Create custom event-automation plans used to automate tasks and other
responses to situations that occur in your environment.
v Create and manage event filters that allow the event automation plans to target
specific events.
v Create and manage event actions that identify tasks or commands to run or
notifications to send. These actions include starting a noninteractive task or
program on the management server or the system on which the event was
generated, or sending an email notification over the Internet or to a mobile
phone.
Update manager
Update manager provides tools for maintaining current versions of operating
systems, device drivers, firmware, and BIOS, and IBM Systems Director agent and
server code on managed systems without an upgrade or migration of the installed
product.
You can use the update manager plug-in to:

v Use the Update Manager Summary page to view update status and a summary
of tasks that help you manage updates on your systems.
v View update history and status of targeted systems.
v Identify updates available for your systems.
v Create customized update groups for your company's certified list of updates.
v Detect and view out-of-date systems.
v Get a notification when systems are in need of updates and which updates are
needed.
v Download, distribute, and install available and requisite updates in a single
request without repackaging or performing each step in the process separately.
v Download and review update information, such as prerequisites, readme files,
Release Notes, content letters, and associated collateral.
Remote access manager
Remote access manager provides tools that support running and monitoring
applications and services running on remote systems.
You can use the remote access manager plug-in to:

v View and interact with applications on a system remotely by displaying the
screen image of the system by using remote control tools, including Virtual
Network Computing (VNC), Remote Desktop (RDP), and web-based remote
control for IBM BladeCenter and RSA.
v Run command-line programs through a remote session. The remote session
creates less network traffic and uses fewer system resources than the remote
control applications and, therefore, is useful in low-bandwidth situations.
v Manage files on a remote system.
v Open console windows to one or more POWER managed systems.
v Run a command on one or more managed systems in parallel.
Network Management
Network Management provides management functions for network devices,
including discovery, inventory, health and status monitoring, and configuration.
You can use Network Management to:

v Discover network devices in your environment.
v Review your network device inventory.
v Monitor the health and status of network devices.
v View network device configuration settings, and apply templates to configure
devices.
v Run network diagnostics tools like ping and traceroute.
Chassis management
Chassis management provides lifecycle management of your IBM BladeCenter
chassis and related resources, including discovery, health and status monitoring,
configuration, updates, and virtualization. It also provides platform-specific
functions.
You can use this plug-in to:

v Change power settings
v Manage hardware logs
v Identify hardware by using the locator LED
v View light-path diagnostic LEDs
IBM System x management

IBM System x management provides lifecycle management of your modular IBM
System x systems and related resources, including discovery, health and status
monitoring, configuration, updates, and virtualization. It also provides
platform-specific functions.
You can use this plug-in to:

v Change power settings
v Manage hardware logs
v Identify hardware by using the locator LED
v View light-path diagnostic LEDs
IBM System z management

IBM System z management provides the capability to discover System z hosted
virtual servers, and to access status information about them.

This plug-in provides functions to discover, monitor status, configure, and update
these virtual servers. It also generates information that is used in the Welcome
panel summary view and includes support for Linux on System z and z/VM
systems that are running on IBM System z mainframes.
IBM Power Systems management

IBM Power Systems management provides lifecycle management of your IBM
Power systems, and platform managers such as Hardware Management Console
(HMC) and Integrated Virtualization Manager (IVM) platform managers, including
discovery, health and status monitoring, configuration, updates, and virtualization.
It also provides platform-specific functions.
You can use the IBM Power Systems management plug-in to:
v Manage the following Power Systems environments that might include servers
with any supported processor versions that are running AIX, IBM i, or Linux:
– Power Systems managed by the Hardware Management Console
– Power Systems managed by the Integrated Virtualization Manager
– A Power Systems server with a single image (a nonpartitioned configuration)
– A Power Architecture® BladeCenter server under the control of a BladeCenter
management module
v Perform management tasks on systems that are under the control of HMC and
IVM, including managing power, creating virtual serves, editing virtual server
resources, and relocating virtual servers between host systems.
v Perform management tasks that are available from the IBM Systems Director
Web interface for supported versions of AIX and IBM i.
IBM System Storage management

IBM System Storage management provides lifecycle management of your physical
and virtual storage systems, including discovery, health and status monitoring,
configuration, updates, and virtualization. It also provides platform-specific
functions.
You can use the IBM System Storage management plug-in to:
v Add storage systems to IBM Systems Director using a proxy provider
v Configure storage systems
v Manage storage devices
v Update a SAN configuration profile
v Start storage management applications
v Use integrated SCM features to manage integrated RAID Controllers, IBM
BladeCenter SAS modules, and BC-S RAID SAS modules
v Use embedded management interfaces, IBM Systems Director Storage Control
4.2.4, or IBM Tivoli Storage Productivity Center to manage storage devices. See
the following topic for details: Supported storage devices.
v Support for automation plans based on events and event actions from storage
resources
v Support for IBM System Storage Area Network products
Additional IBM Systems Director plug-ins

Additional IBM Systems Director plug-ins can be downloaded and installed on top
of IBM Systems Director to provide advanced function or function that is tailored
to a particular environment.
For a complete list of available plug-ins and for information about how to
download and install the plug-ins, see the IBM Systems Director website at
www.ibm.com/systems/management/director/plugins/.
Active Energy Manager plug-in
The Active Energy Manager plug-in helps you to monitor and manage the power
and cooling needs of IBM servers and IBM BladeCenter systems. Non-IBM systems
can also be monitored by using metering products, such as power distribution
units (PDU), sensors, and integration with facility software. You can use Active
Energy Manager to:
v Allocate less power and cooling infrastructure to your IBM servers.
v Reduce power usage on select IBM servers.
v Plan for the future by viewing trends of power usage over time.
v Determine power usage for all components of a rack.
Active Energy Manager is a licensed plug-in that supports Windows, Linux on
Power Systems, and Linux on System x platforms.
Service and Support Manager plug-in
The Service and Support Manager plug-in, which includes the Electronic Service
Agent™ tool, identifies and reports hardware problems and service information
automatically to IBM for service and support. All information sent to IBM is stored
in a secure IBM database and used for improved problem determination. You can
use Service and Support Manager to:
v Place service calls to IBM automatically if the system is under a service
agreement or warranty.
v Collect and send scheduled system inventory and diagnostic inventory to an
IBM database. This inventory information is available to IBM support
representatives when they are solving your problem.
v Communicate with IBM using a secure Internet connection by using encryption
and authentication.
Service and Support Manager is a free plug-in that is supported on the following
operating systems when installed on the IBM Systems Director management
server:
v Windows for 32–bit and 64–bit systems
v Linux on System x for 32–bit and 64–bit systems
v Linux on Power Systems
v Linux on System z
v AIX
IBM Systems Director Network Control plug-in
The Network Control plug-in provides facilities to discover, inventory, and monitor
network devices, start vendor applications for configuration of network devices,
and see groups of network devices.
Note: IBM Systems Director Network Control V1.1 is not supported on IBM
Systems Director. When you install or upgrade to IBM Systems Director V6.2, the
Manage page displays Network Management in place of IBM Systems Director
Network Control.

IBM Systems Director Storage Control 4.2.4
With the Storage Control plug-in, you can manage an expanded set of storage
subsystems and Fibre Channel switches.
You can use Storage Control to discover and collect inventory, and monitor device
health. These subsystems include the IBM DS8000® family (DS8100, DS8300,
DS8700, DS8800), the SAN Volume Controller, the IBM Storwize® V7000, and the
Brocade Fibre Channel switches.
Important: If you are not using IBM DB2 managed by Systems Director, then you
must use one of these versions of IBM DB2 as the local database application for
Systems Director to use Storage Control:
v IBM DB2 Enterprise Edition v. 9.7
v IBM DB2 Enterprise Edition v. 9.7 with fix pack 4
v IBM DB2 Enterprise Edition v. 9.7 with fix pack 6 (or above)
That is, the correct version of DB2 must be installed on the same system as
Systems Director. Storage Control is not supported on any other databases.When
you configure Systems Director, specify the database administrator user ID as the
database runtime user ID. In other words, when you configure Systems Director
with the external DB2 database, set the DB2 administrator user ID for the
DbmsUserId property in the cfgdbcmd.rsp file.
IBM Systems Director VMControl plug-in
The VMControl plug-in is designed to simplify the management of workloads in

your IT environment. Use IBM Systems Director VMControl Express Edition, IBM
Systems Director VMControl Standard Edition, and IBM Systems Director
VMControl Enterprise Edition to manage virtual servers, virtual appliances,
workloads, and system pools across multiple hardware platforms and
virtualization environments from one location.
IBM PowerVM® Workload Partition Manager for AIX plug-in
IBM PowerVM Workload Partition Manager for AIX (WPAR Manager) is a plug-in
for IBM Systems Director that provides a centralized point of control for managing
workload partitions (WPARs) across a collection of managed systems that are
running AIX. Workload Partition Manager can manage heterogeneous
environments of managed systems at different AIX technology levels. However, to
use full management capabilities, update the Workload Partition Manager agent to
the latest version. The following features are supported on all AIX technology
levels: Cross-system management of WPARs, including lifecycle management
Global load balancing with application mobility web-based administration of basic
WPAR operations and advanced management tasks Monitoring and reporting of
WPAR performance metrics.
Upward integration
With IBM Systems Director, you can make the most of your existing enterprise
management structure by upwardly integrating with many workgroup and
enterprise-management products.
IBM Systems Director upward integration modules (UIMs) and management packs
enable non-IBM workgroup and enterprise-management products to interpret and
display data that is provided by Common Agent and Platform Agent. IBM Systems
Director UIMs and management packs provide enhancements to the
enterprise-management products that you can use to collect inventory data, view
IBM Systems Director event notifications, and for some UIMs, distribute IBM
Systems Director software packages.
With the IBM Systems Director UIMs and management packs, you can use your
enterprise-management software to manage systems that have Platform Agent or
Common Agent software installed on them.
You can use Platform Agent software to:

v Gather detailed inventory information about your systems, including operating
system, memory, network adapters, and hardware.
v Track your systems with features such as power management, event log, and
system monitor capabilities.
Platform Agent uses some of the latest systems-management standards, including

Common Information Model (CIM), Web-Based Enterprise Management (WEBM)
and Extensible Markup Language (XML), to provide compatibility with your
existing enterprise-management software.
For more information about upward integration modules, see IBM Systems
Director Upward Integration Modules.
You can also configure IBM Systems Director Server to forward alerts (such as
SNMP) to higher-level enterprise managers, including CA Unicenter NSM, HP
OpenView NNM, HP OpenView Operations for Windows, Tivoli NetView®, Tivoli
Management Framework, Microsoft Systems Center Operations Manager, and
Microsoft Systems Management Server.

Chapter 2. Using the IBM Systems Director Web interface
IBM Systems Director provides the Web interface through which you can view
resources and use tasks in your systems-management environment. This section
provides information about the Web interface, including the Home page, the
different ways to view resources, and how to work with tables and topology maps
that are used in these different views; how to find resources; how to create and
work with groups of resources; how to find and start tasks; how to schedule tasks,
and much more.
In addition to these fundamental tasks, IBM Systems Director provides the

following tasks and features through plug-ins that are already installed or can be
separately installed. For information about available plug-ins, see “Installation.”
v Discovery and inventory collection (see “Discovering systems and collecting
inventory data”)
v Configuring systems (see “Configuring systems”)
v System status, health, event logs, and active status events (see “Monitoring
system status and health”)
v Event automation plans, event filters, and event actions (see “Automating
tasks”)
v Management and installation of updates to existing software products and
firmware, external network and storage switches, as well as external storage
servers (see “Updating systems”)
v A number of security features that include authentication and
user-administration options (see “Security”)
Related concepts:
Security
Related tasks:
Automating tasks
Configuring systems
Discovering systems and collecting inventory data
Monitoring system status and health
Updating systems
Logging into IBM Systems Director Server

You can log into IBM Systems Director Server by way of the Web interface to use
the features and functions that IBM Systems Director provides.
To log into IBM Systems Director Server, complete the following steps:
1. Point your browser to the following URL:
http://System_Name:Port_Number/ibm/console
where System_Name is the name of the system on which IBM Systems Director
Server is installed and Port_Number is the first (lower) of two consecutive port
numbers that you specified for the Web server to use. The default ports for the
Web server are 8421 and 8422. If you use port 8422, make sure that you specify
https to indicate a secure port.
2. Type the user ID and password that correspond to an authorized IBM Systems
Director administrator user ID and password.

3. Click Log in.
Note: A security alert window might be displayed before logging in. This is
due to incorrect configuration of the Secure Sockets Layer (SSL) certificate. For
information see “Configuring Secure Sockets Layer (SSL) between IBM Systems
Director and the Web browser client.”
Note: Logging in to IBM Systems Director will be slower with SSL enabled.
Note: For optimal performance, it is recommended that no more than 30 users log
on to IBM Systems Director Server at one time.
Related tasks:
Logging out of IBM Systems Director Server
Configuring SSL between IBM Systems Director and the Web browser client

When you are finished using IBM Systems Director, you can log out. To log off of
IBM Systems Director Server, in the Web interface, click Logout in the upper-right
corner.
Related tasks:
Enabling multisession support

An authorized user can access multiple user sessions.
To enable multisession support, follow these steps:

1. Log out of the IBM Systems Director Server by clicking Logout in the
upper-right corner of the IBM Systems Director Web interface.
2. Open the <Director root>/lwi/runtime/isc/consoleProperties.xml file.
3. Update the ENABLE.CONCURRENT.LOGIN property to true:
<consoleproperties:console-property id="ENABLE.CONCURRENT.LOGIN" value="true">
4. Save the file.
5. Log back into the IBM Systems Director Server.
When a user is logged on more than once, you will see a number, such as (2), next
to the user's state on the Users page.
Related tasks:
Authorizing users
Navigating the Web interface

Navigating in the Web interface, you can access tasks, resources, and data in IBM
Systems Director. The interface also provides ways to customize itself as well as
help information.

Related tasks:
Navigating by way of the Welcome page
The Web interface

IBM Systems Director provides tasks and unique views to help you manage your
systems-management environment. You can access all tasks available in IBM
Systems Director and you can launch tasks in several other management tools. You
can access your resources using Resource Explorer.
Figure 2. Web interface
Navigation area
The navigation area of IBM Systems Director Web interface provides
categories of tasks that can vary depending on your IBM Systems Director
installation. The navigation provides links to tasks you can perform on
your resources. Examples of typical tasks might include Resource Explorer,
Inventory, Health Summary, and Automation and Settings.
Content area
When you open the Web interface, by default you see the Home page for
IBM Systems Director in the content area. The content area changes
depending on the item you select in the navigation area. You can
customize aspects of the content area using the Navigation Preferences. For
more information, see “Setting navigation preferences.”
Chapter 2. Using the Web interface 23

View list
In the navigation area, this list provides the following alternate view
selections:
All tasks
Displays all the tasks that are available in your IBM Systems
Director installation. This is the default view.
My tasks
Displays a customized list of tasks. For more information, see
“Customizing the Web interface.”
Displays only IBM Systems Director tasks.
Select Action list

This list provides the following ways to work with task pages:
My Startup Pages
Customizes the pages that are started automatically when you log
in to IBM Systems Director, the page that is displayed first of these
automatically started pages, and the default navigation area view.
For more information, see “Customizing the Web interface.”
Manage Open Pages
Provides a way to manage and close one or more open pages.
Close Page
Closes the page that you are viewing.
Help
Displays the help system.
Logout
Logs out of IBM Systems Director.
Related concepts:
The Welcome page
Related tasks:
Setting navigation preferences
Customizing the Web interface
Managing and closing open pages in the Web interface
Viewing help in the Web interface

The IBM Systems Director Web interface provides settings that you can use to
customize the Web interface to meet your specific needs. The My Tasks feature
provides a way to customize the tasks that are displayed in the navigation area. By
saving task pages to My Startup Pages, you can set one or more pages to open
automatically when you log in to IBM Systems Director, including a setting for the
default page that is displayed first among all of the automatically started pages.
Also, you can set the view that is displayed in the navigation area.
Note: In addition to these settings, you can customize navigation preferences for
table and topology views. For information see “Setting navigation preferences.”
To customize the Web interface, complete the following steps:

1. In the IBM Systems Director navigation area, select My tasks from the View
list.
2. In the IBM Systems Director navigation area, click Edit 'My tasks'.
3. On the My Tasks page, select the tasks that you want to display in the
navigation area.
4. Click Apply. The selected tasks are displayed in the navigation area.
5. In IBM Systems Director, open a task page that you want to start
automatically when you log in to IBM Systems Director.
6. In the IBM Systems Director Web interface, click My Startup Pages from the
Select Action list.
7. On the Add to My Startup Pages page, click OK to save the selected page.
8. To add any other task pages that you want to start automatically, repeat steps
5 - 7.
9. To view your saved task pages, click My Startup Pages in the IBM Systems
Director navigation area. On the My Startup Pages page, the saved tasks are
displayed in the table.
10. Click Default to set the default page to display first among all of the
automatically started task pages.
11. If you decide that you do not want a page to start automatically, select that
task and click Remove.
12. To set your My tasks selections as the default navigation area view, select My
Tasks from the Console navigation default view list. You always can change
the navigation area view by using the View list. Select All Tasks to see all
IBM Systems Director tasks.
13. When you are satisfied with your settings, click OK to save the settings and
close the page. To save the setting but not close the page, click Apply. To close
the page without saving the settings, click Cancel.
Any changes take effect the next time you log in to IBM Systems Director.
Related concepts:
The Web interface
Related tasks:
Changing the welcome message on the login screen

The default herald contains the welcome message that displays with the login
prompt for all users. Users with Administrator authority can change the welcome
message using the dircli CLI command.
1. Create a UTF-8 file on the system. The file will contain the welcome message
and must be named loginMessage.properties.
2. Edit the file and add the following line, substituting your custom text:
loginMessage=This is the text that will appear on the login page.
Note: When creating loginMessage.properties, characters need to be specified

with valid ISO 8859-1 Unicode-escape sequences.
3. Save and exit the file.
4. On the host system, run the following command:
dircli chgloginmsg -f C:\loginMessage.properties

The C:\loginMessage.properties file is copied to the install root in the following
path:
<Director root>/lwi/runtime/isc/loginMessage
The new message appears immediately for future login attempts, you do not need
to restart the server.
Related reference:
“Command-task file parameters” on page 119

The IBM Systems Director Web interface provides several ways to manage and
close open pages.
The Web interface provides page controls in the upper-right corner in the Select
Action list. Also, when you have more page tabs that can be displayed in the
width of the Web interface, an arrow is displayed that you can click to view the
additional tabs.
Figure 3. Select Action list
To manage and close open pages, complete any of the following steps:
v In the IBM Systems Director Web interface, click Manage Open Pages from the
Select Action list that is located in the upper-right corner of the Web interface
content area. On the Manage Open Pages page, you can close all pages by
clicking Close All Pages, close selected pages by selecting one or more pages
and clicking Close Page, or view a selected page by clicking the page link.
v To close a page that you are viewing, click Close Page from the Select Action
list.
v To close a page, click X on the page tab.
v When applicable, click the OK or Cancel buttons on the page.
Related concepts:
The Web interface
Related tasks:

The IBM Systems Director Web interface provides several ways to view help.
To view help, complete any of the following steps:

v In the IBM Systems Director Web interface, click Help in the upper-right corner.
The IBM Systems Director help system opens in a new Web browser window.
v In a task page, click ? in the upper-right corner of the page.
v In a task window or wizard, click ? in the upper-right corner of the window or
wizard.
v When applicable, click the Help button on the page.

Related concepts:
The Web interface
Related tasks:
The Welcome banner area

Starting with IBM Systems Director version 6.2, the Welcome banner area provides
links to the Active Status (compliance) page, where you can view the active
compliance issues for all discovered systems and the Problems page, where you
can view the active problems for all discovered systems.
In the Welcome banner area, you can get a quick view of system status by viewing
the following icons next to Compliance or Problems:
v Warning
v Critical
For more detailed information, click Compliance, to view the Active Status
(compliance) page or click Problems to view the Problems page.
Navigating IBM Systems Director by way of the Home page

Using the IBM Systems Director Home page, you can navigate to first-time setup
steps, make sure IBM Systems Director and its plug-ins are setup and configured,
manage your environment from plug-in summary pages, and access tutorials and
Information Center topics to expand your skills with IBM Systems Director.
Related tasks:
Finding and navigating resources
Managing groups
Finding and starting tasks
Scheduling tasks
IBM Systems Director Home page

Use the IBM Systems Director Home page to complete first-time setup steps, view
and activate IBM Systems Director plug-ins, and access information center topics
and tutorials to expand your skills with IBM Systems Director.
Figure 4. The Home page displaying the Initial Setup, Additional Setup, Plug-ins, and Learn tabs
The following links are available at the top of the Home page:

Update IBM Systems Director
Checks for and displays any updates that are available from the product
web site that are required by the IBM Systems Director Server.
Information Center
Opens a link to the corresponding IBM Systems Director Information
Center in a separate browser tab.
Related concepts:
System severity states
Related tasks:
Starting work in IBM Systems Director
Learning about the product
Checking IBM Systems Director readiness
Viewing updates
Viewing tutorials
Viewing the IBM Systems Director Server summary
The Initial Setup tab

Provides the tasks to set up IBM Systems Director for the first time. A user must
have the AllPermission permission to view this page; otherwise, it is not displayed.

Figure 5. The Home page interface displaying the Initial Setup tab
The following tasks are provided on the Initial Setup tab.

Obtain and install updates for IBM Systems Director. When the updates
begins, the current status of the update appears under this step. As part of
the update, you will need to restart the IBM Systems Director Server. A
timestamp of the update appears once the update successfully completes.
System Discovery
Discover systems by using a single IP address or host name, a range of IP
addresses, or a discovery profile.
Request Access
Request access to systems that IBM Systems Director has no access to using
either the request access task or the configure access task.
Collect Inventory
Collect the most current inventory from a resource or view the inventory
of a resource.
Resource Explorer
Provides a link to the Resource Explorer page to start managing the
resources in your environment.

Health Summary
Provides a link to the Health Summary page where you can quickly view
and monitor resources that are important to you.
Related concepts:
“System discovery” on page 160
The Plug-ins tab
The Additional Setup tab
The Learn tab
Security
Related tasks:
“Updating IBM Systems Director” on page 365
“Collecting inventory” on page 194
Home page: Additional Setup tab

Provides additional steps to make IBM Systems Director more productive after the
steps on the Initial Setup tab are complete. A user must have the AllPermission
permission to view this page; otherwise, it is not displayed.
Actions
The Additional Setups tab consists of the typical next steps for setting up IBM
Systems Director. These steps include:
v Registering IBM Systems Director.
v Setting up Electronic Service Agent to collect and send hardware problem
information to Support.
v Creating thresholds and event automation plans
v Checking for updates on discovered systems
v Installing Common Agent on systems
v Setting up user security
v Configuring your systems

Figure 6. The Home page interface displaying the Additional Setup tab
Related concepts:
The Plug-ins tab
The Learn tab
The Plug-ins tab

Provides information that you can use to determine whether IBM Systems Director
and its plug-ins are ready to use. From this page, you can view, activate, and
deactivate additional plug-ins, along with importing license keys for your plug-ins.
The message associated with each plug-in changes based on whether the plug-in is
ready to use. The links provided for each plug-in include the plug-in summary
page on which you have quick access to your environment's data and applicable
tasks. If a plug-in is not ready to use, this page provides links to the applicable
tasks that you must perform to complete setup or configuration of the plug-in.
The Plug-ins tab includes an icon that is displayed if any problems exist with one
or more plug-ins.
Note: The Plug-ins tab displays only the plug-ins that the user is authorized to
use. If a user is not authorized to use any plug-ins, the Plug-ins tab is not
displayed.
Figure 7. The Plug-ins tab with the Information icon

The icon displayed is tied to the plug-in states that are displayed on the Plug-ins
tab:
If one or more plug-ins are in an Error state, the Error-connecting icon is

displayed on the Plug-ins tab.
If one or more plug-ins are in the Setup-required state, the Setup-required

icon is displayed on the Plug-ins tab.
No icon
If all plug-ins are in the ready state or collecting-data state ,

then no icon is displayed on the Plug-ins tab.

Figure 8. The Home page interface displaying the Plug-ins tab

Plug-in title
Click the plug-in title to display the plug-in summary page. The summary
page provides tasks and information that you typically use in that plug-in.
Readiness icons
Each plug-in title has one of the following icons next to its name denoting
whether the plug-in is ready for use:
Ready
The plug-in is correctly installed and configured.
Collecting data
The process to determine whether a plug-in is ready to use has
started and might take a long time. To determine when the plug-in
is ready, click Refresh (located at the bottom of the page) and if
the plug-in is ready the status icon will change.
Setup required
The plug-in is not set up correctly or the set up is currently
incomplete. A message and additional links are displayed
providing information about any required setup, such as additional
configuring, enabling of firewall support, identifying applicable
types of servers required by that plug-in, or other setup activities.
Error connecting
The plug-in has failed to connect to the applicable destination,
which might be the management server, a Web site, or another
destination.
Plug-in links
Each plug-in section provides links that you can use to complete any
configuration or setup activities.
Refresh
Click to refresh the ready-for-use information. It also reports that last time
the information was refreshed.
Additional plug-ins to activate

Displays any additional plug-ins with links to activate them. The name of
each plug-in is a link to launch a new browser window with information
about the plug-in.
Import License Key

From the Additional plug-ins to activate box, click Import License Key to
open the Import License Key page where you can import permanent
license keys.

Related concepts:
The Learn tab
Importing license keys:
You can import permanent license keys through the IBM Systems Director Web
interface from the Plug-ins tab of the Home page. You can only use the Web
interface to import license packs for license key management. For installation
instructions, as well as information about compatability, planning, management,
and so on, see the documentation for each plug-in. For detailed licensing and
pricing information, or to obtain media with license keys, contact your IBM
marketing representative or business partner.
For a complete list of available IBM Systems Director plug-ins and for links to the
documentation for each plug-in, see the IBM Systems Director Web site at
www.ibm.com/systems/management/director/plugins/.
The Learn tab

Provides a list of available tutorials and other information center links. If the link
is to a tutorial, the link opens a tutorial section in the “Learning and tutorials”
section of the IBM Systems Director information center. Hover help for each link
provides a description for that tutorial.
Figure 9. The Home page interface displaying the Learn tab
This page provides the following information:

Tutorial links
Provides links to available tutorials for installed plug-ins.
Tip: The tutorials are launched from the Internet. You must have access to
the Internet to view them. For more information about e-learning and
tutorials, see “Learning and tutorials.”
Hover help
Provides a description for each tutorial.

Related concepts:
The Plug-ins tab

Systems with Common Agent or Platform Agent installed on them generate events
that numerically indicate their health status to IBM Systems Director Server. The
numeric values indicated by the event correspond to one of three severity levels in
IBM Systems Director: critical, warning, or informational.
Each applicable IBM Systems Director system generates a numeric value that aligns
it with one of the following three severity levels:
Critical
A system that has generated an event with a severity of 5 or 6 is the most
severe and is identified in IBM Systems Director as being in a Critical state.
These systems have already lost or will imminently lose data, have had
system down time, or are on the verge of losing some other services.
System operation might be impacted if the problem is left uncorrected.
Warning
A system that has generated an event with a severity of 3 or 4 is identified
in IBM Systems Director as being in a Warning state. These systems can
escalate to a Critical state if left uncorrected. System operation might not
be impacted and normal use of the hardware can continue.
Informational
A system that has generated an event with a severity of 1 or 2 is identified
in IBM Systems Director as being in an Informational state. These systems
are operating normally and typically, no action is required.
Related concepts:
The Home page
Related tasks:
Viewing updates
Viewing tutorials

Before IBM Systems Director can manage your systems, the systems must be
discovered. Using the Home page, you can set up IBM Systems Director for use for
the first time.
To get started with IBM Systems Director, complete the following steps:
1. If this is the first time using IBM Systems Director, the Home page is displayed
automatically. Otherwise, in the IBM Systems Director navigation area, click
Home.
2. On the IBM Systems Director Home page, view the tasks on the Initial Setup
tab. This section provides the steps to update IBM Systems Director, discover
systems, request access to system, and collect inventory.

3. View the steps on the Additional Setup tab. This section provides typical tasks
for setting up IBM Systems Director, including registering the product, creating
thresholds and event automation plans, checking for updates, installing
Common Agent on systems, setting up security, and configuring your systems.
Related concepts:
The Home page
Related tasks:
Viewing updates
Viewing tutorials

There are several ways to learn about IBM Systems Director.
You can learn more about IBM Systems Director in the following ways:
v In the IBM Systems Director navigation area, click Home. On the Home page,
click the Learn tab. View the available tutorials to expand your skills with IBM
Systems Director.
v On the Home page, click the Plug-ins tab. For each plug-in, click the plug-in
section heading to view its summary page.
v Go to the IBM Systems Director information center at publib.boulder.ibm.com/
infocenter/director/pubs/index.jsp to review scenarios and other information
resources.
v Go to the IBM Systems Director customer forum. For more information, see
“Accessing the IBM Systems Director customer forum.”
v To familiarize yourself with other information resources available on the Web,
click Related Web Resources.
Related concepts:
The Home page
Related tasks:
Viewing updates
Viewing tutorials

You can determine whether the plug-ins in your IBM Systems Director installation
are ready for use by viewing the Home page.
To determine whether plug-ins are ready for use, complete the following steps:
1. In the IBM Systems Director navigation area, click Home.
2. On the Home page, click the Plug-ins tab.

3. Browse the Plug-ins page to determine the plug-ins that are in your IBM
Systems Director installation and whether they are ready for use. Each plug-in
has one of the following icons beside its name denoting whether the plug-in is
ready for use or requires additional setup or configuration:
Ready
The plug-in is correctly installed and configured.
Collecting data
The process to determine whether a plug-in is ready to use has started
and might take a long time. To determine when the plug-in is ready,
click Refresh (located at the bottom of the page) and if the plug-in is
ready the status icon will change.
Setup required
The plug-in is not set up correctly or the set up is currently incomplete.
A message and additional links are displayed providing information
about any required setup, such as additional configuring, enabling of
firewall support, identifying applicable types of servers required by
that plug-in, or other setup activities.
Error connecting
The plug-in has failed to connect to the applicable destination, which
might be the management server, a Web site, or another destination.
4. If a plug-in reports that it has a problem, click the displayed links to complete
the setup and configuration.
5. Complete the setup tasks listed for the plug-in.
6. On the Plug-ins page, click Refresh. IBM Systems Director checks the plug-in.
The affected plug-in is now ready to use and its status is updated.
Related concepts:
The Home page
Related tasks:
Viewing updates
Viewing tutorials
Viewing updates
You can view updates that you can choose to apply to your IBM Systems Director
environment.
To view updates, in the IBM Systems Director navigation area, click Home to view
the Home page and complete any of the following steps:
v In the left-hand navigation, click Release Management > Updates. The Updates
page is displayed.
v Click Acquire updates.

1. On the Acquire Updates page, select the option to check for updates, then
select the types of updates for which you want check and click OK. Using
the Acquire Updates page, you can start managing updates in the following
ways:
– Select the systems to keep in compliance with the latest updates.
– Configure a connection to the Internet.
– Run or schedule a check for updates.
2. In the Launch Job window, click OK to start Check for Updates immediately.
IBM Systems Director checks for any updates that are available. A message is
displayed stating that the Check for Updates has run.
3. Click Show and Install Updates. The Show and Install Updates page is
displayed.
v On the Home page, click the Plug-ins tab. On the Plug-ins tab, click Acquire
Updates under the Update Manager section. The Acquire Updates page
described in the preceding step is displayed.
Related concepts:
The Home page
Related tasks:
Viewing tutorials
Viewing tutorials
You can view tutorials to learn quickly how to use tasks and feature provided by
To view tutorials, complete the following steps:

2. On the Home page, click the Learn tab. The Learn tab is displayed with the
available tutorials for the installed plug-ins. Hover help provides a description
for each tutorial.
3. Click the tutorial link for the task about which you want to learn.
Tip: The tutorials are launched from the Internet. You must have access to the
Internet to view them. For more information about e-learning and tutorials, see
“Learning and tutorials.”
If you have trouble viewing a tutorial, make sure that you install version 8.0 or
later of Adobe Flash Player from www.adobe.com/downloads/ and ensure that
your browser security settings are not preventing the interactive content from
displaying. Also, make sure that the system on which you install the IBM Systems
Director components meets the defined hardware requirements.

Related concepts:
The Home page
Learning and tutorials

Related tasks:
Viewing updates

You can view a summary of all activity within the past 30 days that is associated
with IBM Systems Director Server and the server on which it is running
(management server). Note that information on this page is refreshed automatically
when there are any changes.
To view the IBM Systems Director Server summary, complete the following steps:
3. On the Plug-ins tab, scroll to the IBM Systems Director Server section of the
page and click the IBM Systems Director Server section heading. The IBM
Systems Director Server summary is displayed.
4. View the IBM Systems Director status section. This section provides the
following information:
v The management server name. Click the name to view the properties page
for the server.
v The current status for IBM Systems Director Server and, if applicable, its last
restart date and time. The Status field displays a local system health rating
that warns you when the IBM Systems Director Server is experiencing
problems that could jeopardize performance or stability. If a problem is
detected, a message ID is also provided. When you can click on the message
ID, a new window opens with a recommended operator response.
v The number of systems discovered. Click this link to display the discovered
systems.
v The type of authentication used.
v The known ports that are in use. Click All possible ports to view
information about ports that IBM Systems Director might use.
Note: This link opens the IBM Systems Director information center and
requires Internet access.
v The location of any trace and error logs.
v The database version number and driver that is installed.
v The current management server statistics including processor use, memory
use, storage use, and the number of active users.
v In the Common tasks area, the following links are provided:
System discovery
Click System discovery to discover systems by specifying a single IP
address, host name, or IP address range or by using a discovery
profile.
Collect and view inventory
Click Collect and view inventory to open the View and Collect
Inventory task, with which you can collect the most current
inventory from a resource or view the inventory of a resource.
Find a task
Click Find a task to quickly and easily find any task. Then, you can
run the selected task.
Find a resource
Click Find a resource to quickly and easily find a particular resource.
Resource Explorer
Click Resource Explorer to view, work with, and navigate among
resources in your systems-management environment, including view
and manage discovery options on an individual resource level.
5. View the Users and roles section. This section provides the following
information:
v The number of users that do not have access to any resources. Click this link
to view the Users page that displays the affected users.
v The number of users that are defined in your IBM Systems Director Server
environment. Click this link to view the Users page that displays the defined
users.
v The number of roles that are defined in your IBM Systems Director Server
environment. Click this link to view the Roles page.
Manage Users
Click Manage Users to specify basic properties for each authorized
user and assign access to each user using roles.
Manage Roles
Click Manage Roles to create, edit, or delete roles that are used to
assign access to users.
Add a role
Click Add a role to create a role.
You also can reach the summary page by using Find a Task. For more information,
see “Finding a task.”

Related concepts:
The Home page
Related tasks:
Finding systems and other resources
Finding a task
Authorizing users
Viewing updates
Viewing tutorials
Related reference:
All possible ports

The IBM Systems Director Web interface provides many ways to navigate
resources. This section includes information about finding resources; the available
ways to view resources and resource information, including topology maps and
Topology Perspectives; working with resources in tables; and working with
resources in topology maps.
Topology Perspectives is a powerful navigation feature. When you select this

action, you can view a resource and its relationships to other resources in a
graphical display. For more information, see “Topology Perspectives views,”
“Viewing resources in the topology perspective,” and “Working with topology
maps.”
The Web interface also provides navigational actions for resources by way of the
Actions menu and the complementary pop-up menu that is displayed when you
right-click a resource. These actions vary depending on the resource. When you
click a resource, the default navigational task occurs; the default task, too, can vary
depending on the resource. For example, if you click a group, the members of that
group are displayed. When you right-click a group, the first navigational action
provided in the pop-up menu is View Members, which displays the members of
the group. If you click a resource, the Properties page for that resource is
displayed. When you right-click a resource, Properties is provided at the bottom of
the pop-up menu.
The menu also provides the following navigational actions:

v When you select a resource, the Related Resources menu item provides a list of
any and all resources that are related to the currently selected resource.
v When you view members of a group, the menu provides group-specific actions.
For example, while viewing a member of the group called All My Linux Servers,
you can click Actions > All My Linux Servers to view a submenu of
appropriate actions for that group.
As you navigate from one resource to another or drill down from a resource to its
subcomponents, a breadcrumb path is displayed at the top of the page as a
navigational signpost. The breadcrumb path is extended each time you drill down.

If you navigate to a related resource, the breadcrumb path is updated to the
current location. The last link in the path identifies your current location in the
resource navigation. If you right-click on this last link, a menu is displayed. This
menu provides the same options as the Actions menu at this current location. The
following examples illustrate specific resources and the pop-up menus that are
displayed when you right-click the breadcrumb path:
v When you view members of a group, the breadcrumb path displays the menu
associated with that group.
v When you view blade servers in a chassis, the breadcrumb path displays the
menu associated with the chassis.
v When you view a resource in a topology map, the breadcrumb path displays the
menu associated with that resource.
Related tasks:
Navigating by way of the Home page
Managing groups
Scheduling tasks
Related reference:
lsgp command
accesssys command
Resource views
The IBM Systems Director Web interface provides a number of ways to view
information about your resources as well as manage the resources. The most
typical ways are through tables and the properties view. Most tasks and plug-ins
provide information and function using tables, although the amount of information
and function varies depending on the task or plug-in. In this section, Resource
Explorer is used to describe navigating tables in general.
Information and functions also are provided using the properties view. The
properties view is always available for any resource by selecting the resource and
clicking Actions > Properties.
Some tasks and plug-ins, most notably Resource Explorer, also provide Topology
Perspectives. When you select this feature, you can view a collection of related
resources, such as systems and their storage, and see the relationships among the
resources using a topology map. You also can toggle from the map view to a
resource view or relationship view.

Related tasks:
Viewing resources in the topology perspective
Working with tables
Working with topology maps
Working with properties
Renaming a resource
Removing a resource
Table view
The table view can display a list of the resources or tasks. Tables are the basic way
that information is displayed in IBM Systems Director.
Use the following example and descriptions to learn about the table view.
Figure 10. Table view
Breadcrumb path
Provides a collection of links that show the navigation path to the current
view. You can click any of these links to go back in the path.
Toolbar
Provides frequently used tasks as buttons. Available buttons vary,
depending on the task page. In this example, the Create Group button is
provided, but on other task pages, the Create Group button might not be.
Actions
Opens a list of available actions. These actions include those that are

provided in the toolbar and elsewhere on the page as well as actions that
are common to all tables. For common table actions, see “Table navigation
in IBM Systems Director.”
Search the table

Searches the table with the string or phrase provided. When you type a
string in this field, any matching strings in the currently displayed table
are highlighted. Additionally, if you click Search, all of the pages of a table
are searched for the provided string; only the rows that contain the string
are displayed in the table.
Resource area
Displays the content of the resource area depending on the resources that
you have chosen to view. To see the members of a group, click on a group
in the table. The view drills down to view the group members in the table
and another step is added to the breadcrumb path. For example, if you
click Common-Agent systems in the table, all systems in your
environment that have Common Agent installed are displayed. The
resource view functions in the same way regardless of the resources that
you have chosen to view.
To perform an action on a resource in the view, right-click the resource and
select an action.
Table state information

Provides navigation between pages of the table. The table view displays a
limited number of entries on a single page. To move to the next page, click
the arrow button at the bottom left portion of the table. The table view
indicates the number of pages of data that is being displayed, for example,
Page 1 of 3. It displays the count of resources or relationships currently
shown, filtered, and the number selected. To change the number of entries
that are displayed in the table, change the Rows per table setting in the
Navigation Preferences page. For more information see “Setting navigation
preferences.”
Tip: To got to a specific page, type a number in the provided entry field
and press Enter. If you specified an number that is not valid, the page in
the table does not change.
Related concepts:
Properties view
Topology Perspectives views
Related tasks:
Navigating tables
Properties view
The properties view displays a list of properties and other detailed information
associated with the selected resource. Using the properties view, you can access
troubleshooting information and other important details about a resource from
anywhere in the IBM Systems Director Web interface. This view is available for all
resources from the Actions menu and from the resource's pop-up menu.
Depending on the selected resource, the properties view can provide information
about any configuration settings, jobs, thresholds, or event automation plans that
can affect the resource as well as dynamic troubleshooting information such as

active status, inventory, and event log. Also, the properties view provides access to
any tasks that can be performed on the selected resource by way of the Actions
menu.
You can access the properties view from any view by selecting a resource and
clicking Actions > Properties.
Use the following example and descriptions to learn about the properties view.
Figure 11. Properties view
Breadcrumb path
Actions
Contains actions that are applicable to the resource displayed in the
Properties view.
Additional properties
If present, this area provides links to customized properties views provided
by the plug-in.
Resource area
Displays the content of the resource area that varies depending on the
resource that you have chosen to view. While the General page is always
displayed by default, the following additional pages can be provided
depending on the resource type:

General
Displays the basic resource properties. This page is displayed by
default.
Active Status
Displays any problems, compliance concerns, and other issues.
Applied Activities
Displays any jobs, thresholds, software packages, activations, or
event automation plans that are associated with the resource.
Configuration
Displays any configuration settings that can be edited immediately
or saved as a template for later deployment. For more information,
see “Configuring systems.”
Event Log
Displays any event log data that might be associated with the
resource. For more information, see “Managing the Event Log.”
Inventory
Displays any inventory data that might be associated with the
resource. For more information, see “Collecting and viewing
inventory data.”
Service and Support
Displays whether Service and Support Manager is monitoring the
resource for problems that can be reported automatically to IBM
support. This page is displayed only if you have installed and
activated the Service and Support Manager plug-in. For more
information, see “Service and Support Summary.”
Related concepts:
Table view
Related tasks:
Configuring systems
Collecting and viewing inventory data
Managing the event log

After you select Resource Explorer from the navigation area, you can drill down to
see relationships among your resources using Topology Perspectives. Select a
resource or group of resources and click Actions > Topology Perspectives > Basic.
The Basic selection provides a topology map that shows key resources that are
related to the selected resource. When viewing a collection of related resources,
you can toggle among the map view, resource view, or relationship view to
manage your resources.
Resource Explorer provides the basic topology perspective that is described in this
section. Other plug-ins available for IBM Systems Director might provide
additional perspectives on this menu. These additional perspectives can provide
specific topological views of resource information:
All Provides a topology map that shows all resources that are related to the
selected resource.
Network
Provides a topology map that shows network-specific resources that are
related to the selected resource, including servers, routers, and network
cards.

For information about additional topology perspectives, see the following topics:
v “Storage topology views”
v “The update topology perspective”
v “Viewing resources in virtualization perspectives”
Note: The properties view is always available for any resource; select the resource
and click Properties.
Related concepts:
Storage topology perspective
Table view
Properties view
Map view:
The map view shows a graphical view of your resources and their relationships.
You can drill down and view the relationships among these resources and other
resources in your environment. You can also view and edit resource properties.
You can click on any displayed system icon or on any relationship line to select a
resource or relationship; then right-click on that selected resource to display a list
of available actions.
You can access the topology map view by selecting one or more resources and then
clicking Actions > Topology Perspectives > Basic. After you have entered the map
view, you can change to the resource view or relationship view. You can access the
map view from the resource view or relationship view by clicking Actions > Map
View.
Use the following example and descriptions to learn about the map view.

Figure 12. Map view
Breadcrumb path
Toolbar
The toolbar contains the following toolbar buttons and menu:
Table 1. Toolbar buttons and menu
Icon Name Description
Actions menu Contains actions for the topology as a whole, as well as pop-up menu items
for resources currently selected in the topology. For example, to display the
properties of the currently selected resource, click Actions > Properties.
Search the map Searches the map for resources that have a name containing the word or
phrase provided.
Select Selects resources in the topology.
Zoom Area Selects the part of the topology that you want to increase or decrease in size.
Pan Provides a way for you to drag the topology map to reposition it in the
topology viewport.
Hover Help Displays detailed information about a resource or relationship line when a
mouse hovers over it.
Zoom Out (F2) Incrementally reduces the total area of the topology you want to view.

Table 1. Toolbar buttons and menu (continued)
Icon Name Description
Zoom In (F3) Incrementally enlarges the total area of topology you want to view.
Zoom To Fit (F4) Scales the entire topology to fit into the topology viewport.
Print Graph Prints the entire topology. A Web browser window opens containing a JPEG
image of the graph. You can either print the graphic using your Web-browser
print feature or save the graphic as a local image.
Note: Be sure the Web browser option to block pop-up windows is turned off
for the URL that you use to log in to the IBM Systems Director Web interface.
Print Viewport Prints only the current resources and relationships that are displayed in the
topology viewport. This view might be only a portion of the overall topology.
A Web browser window opens containing a JPEG image of the graph. You can
either print the graphic using your Web-browser print feature or save the
graphic as a local image.
Note: Be sure the Web browser option to block pop-up windows is turned off
for the URL that you use to log in to the IBM Systems Director Web interface.
Hide Palette View Hides the support area that displays the palettes.
Show Palette View Shows the support area that displays the palettes.
Map area
Enables you to drill down and view the relationships between resources in
a graphical format. You can right-click on a resource to display a list of
available actions. You can perform mouse actions on the topology map
such as scrolling, repositioning, and resizing. You also can use the
Overview palette to easily reposition the resources and relationships that
are displayed in the map.
Support area
Contains the Overview, Details, and Filter palettes. Click Hide Palette
View on the navigation toolbar to close the support area. Click Show
Palette View on the navigation toolbar to open the support area. See
“Navigating topology maps” for more information.
Overview palette
Provides a view of the entire topology map with a rectangle surrounding
the portion of the map displayed in the map viewport. You can click and
drag within the Overview palette to reposition the topology. See
“Reordering, minimizing, and hiding palettes” for more information.
Details palette
Provides a way to work with the properties of your resources. When you
select a resource or relationship in the topology, all of its properties appear
in the properties page within the Details palette. To change editable
properties, click Edit to open the Edit Properties window, change the
property, and click OK. See “Viewing properties and details” for more
information.

Filter palette
Provides a way to select the resources that you want to see in the topology
map. You can filter your selections by status and by resource type. When
filtered, the affected resources and relationships are grayed out in the map.
The Filter palette also provides a Results page that displays the results of
searching the map view. See “Filtering the topology map” for more
information.

Displays the count of resources or relationships currently shown, the
number selected, and the number filtered. A Depth menu is displayed to
indicate the number of relationships from the root node to the object that is
farthest away from that node. Using this menu, you can select the depth of
related resources that you want to view in the topology.
Related concepts:
Resource view
Relationship view
Related tasks:
Navigating topology maps
Reordering, minimizing, and hiding palettes
Viewing properties and details
Filtering the topology map
Changing between resource views
Changing the default resource view
Resource view:
The resource view displays a list of the resources in the current topology map
view.
You can access the resource view from the map view or relationship view by
clicking Actions > Resource View.
Use the following example and descriptions to learn about the resource view.

Figure 13. Resource view
Breadcrumb path
Actions
Map View
Click to change to the topology map view of the selected resource
and its related resources.
Resource View
The currently selected view, it displays the resource view of the
selected resource and its related resources.
Relationship View
Click to change to the selected resource, its related resources, and
their relationships.
Depth Indicate the number of relationships from the root node to the
object that is farthest away from that node. Using this menu, you
can select the depth of related resources that you want to view in
the table.
Search the table


Resource area
The content of the resource area depends on the resources that you have
chosen to view. To see the members of a group, click on a group in the
table. The view drills down to view the group members in the table and
another step is added to the breadcrumb path. For example, if you click
Common-Agent systems in the table, all systems in your environment that
have Common Agent installed will be displayed. The resource view
functions in the same way regardless of the resources that you have chosen
to view.
To perform an action on a resource in the view, right-click the resource and
select an action.

preferences.”
Related concepts:
Map view
Relationship view
Related tasks:
Navigating tables
Viewing resources in the resource view
Relationship view:
The relationship view shows the relationships among the resources in the current
topology map view. You can see the name of each resource, its type of relationship
to another resource, and the related resource. Before you can access the
relationship view, you must enter Topology Perspectives.
You can access a relationship view from the map view by clicking Actions >
Relationship View.
Note: After you enter the map view, there are two additional alternate views: the
relationship view and the resource view. Having entered the map view you can
change among the three alternate views.
Use the following example and descriptions to learn about the relationship view.

Figure 14. Relationship view
Breadcrumb path
Actions
Contains actions for the selected resource and its related resources in a
relationship view.
Map View
Click to change to the topology map view of the selected resource
and its related resources.
Resource View
Click to change to the resource view of the selected resource and
its related resources.
Relationship View
The currently selected view, it displays the selected resource, its
related resources, and their relationships.
Depth Indicate the number of relationships from the root node to the
object that is farthest away from that node. Using this menu, you
can select the depth of related resources that you want to view in
the table.
Search the table


Relationship area
The content of the relationship area depends on the resources that you
have chosen to view. For example, if you click Virtual Servers and Hosts,
the relationships that pertain to your virtual systems and hosts will be
displayed in the relationship view. A relationship between two resources is
displayed in each row. The relationship view functions in the same way
regardless of the types of relationships you have chosen to view.
To perform an action on the resources in the relationship view, right-click
the resource name in a row. The pop-up menu provides a submenu for
each resource in the relationship. Select an action for the resource you want
to affect. The action you select is performed on the selected resource within
the relationship.

preferences.”
Related concepts:
Map view
Resource view
Related tasks:
Navigating tables
Viewing resources in the relationship view

A system-management environment can include a large number of systems and
other resources. While you can expand and navigate through groups from the
Resource Explorer page or within other task tables to find a particular resource,
you also can quickly and easily find a particular resource using Find a Resource.
To locate resources quickly, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, click Find a
Resource.

2. In the Find a Resource field, type the name of the system and click Find. The
first 10 results of the search are displayed below the field. If there are more
than 10 results, More is displayed.
3. Optional: If there are more than 10 results, you can refine the search results.
4. Optional: To view all the search results, click More. A table is displayed with
the search results.
Related concepts:
Resource views
Related tasks:
Working with tables
Renaming a resource
Removing a resource
Related reference:
lssys command
accesssys command

Using topology perspectives, you can view a collection of resources and see their
relationships among each other in multiple ways. If a task provides topology
perspectives, the Topology Perspectives action is available from the Actions menu.
After you enter the topology map view, you can access the resource view and the
relationship view. These views provide alternate ways to view the resources and
relationships that are displayed in the map view.
Note: Do not confuse the resource view and relationship view with the navigation
tables that are used throughout the IBM Systems Director Web interface. These
views display only the resources and relationships that you selected to display in
the topology perspective.
Related concepts:
Resource views
Related tasks:
Working with tables
Renaming a resource
Removing a resource
Viewing resources in the map view

The map view shows a graphical view of your resources and their relationships. If
a resource provides the topology map view as an alternate view, Topology
Perspectives is available in the Actions menu.
To view a topology map, complete the following steps:

1. On a task page, navigate to a resource with relationships that you want to see
in a topology map view and select it.
2. Click Actions > Topology Perspectives > Basic.
3. View the map area. Use the map to drill down and view the relationships
between resources in a graphical format. You can right-click on a resource to
display a list of available actions.
4. Use your mouse to scroll, reposition, resize, and select resources and
relationships, as well as open context menus for resources. Relationships
between resources are displayed as lines, and the direction of the relationship is
shown by the direction of the arrow attached to each line. For information
about determining the type of relationship that a line indicates, see
“Determining a relationship type.” For more information about relationship
lines, see “Topology-relationship descriptions.” For more information about
mouse actions in a topology map, see “Navigating topology maps.”
5. View the Overview palette in the Support area. This palette provides a view of
the entire topology map with a rectangle surrounding the portion of the map
displayed in the map viewport. You can click and drag within the Overview
palette to reposition the topology.
6. View the Details palette in the Support area. This palette provides a way to
work with the properties of your resources. When you select a resource or
relationship in the topology, all of its properties appear in the properties page
within the Details palette. To change editable properties, click Edit to open the
Edit Properties window, change the property, and click OK. See “Viewing
properties and details” for more information.
7. View the Filter palette in the Support area. This palette provides a way to select
the resources that you want to see in the topology map. You can filter your
selections by status and by resource type. When filtered, the affected resources
and relationships are grayed out in the map. The Filter palette also provides a
Results page that displays the results of searching the map view. For more
information, see “Filtering the topology map.”
Related concepts:
Map view
Related tasks:
Determining a relationship type

The resource view displays a list of the resources in the current topology map
view.
To view and use the resource view, complete the following steps:
1. In a topology map or relationship table, click Actions > Resource View.
2. In the table view, click a resource in the list to drill down and see more
resources and their relationships.

3. If you want to perform tasks or other actions on your resources, select one or
more resources; then, click Action and click a task.
Tips:
v You also can right-click the resource and select a task from the pop-up menu.
v You can run some tasks on multiple resources simultaneously. To perform an
action on multiple resources, select the resources, right-click on one of the
selected resources, and select a task from the pop-up menu.
Related concepts:
Resource view
Related tasks:
Navigating tables

The relationship view shows the relationships among the resources in the current
topology map view. You can see the name of each resource, its type of relationship
to another resource, and the related resource. Before you can access the
relationship view, you must enter Topology Perspectives.
To view and use the relationship view, complete the following steps:
1. In a topology map or resource view, select a resource and click Actions >
Relationship View. The resource view shows a list of the relationships among
your resources. A relationship between two resources is displayed in each row.
The resource view provides the following information about the relationships:
From In the resource view, the resource that is the starting point of a
relationship. For example, if System A is the host for Virtual Server 1,
then System A is the starting point of the relationship.
Relationship type
The type of relationship between two resources. Relationships might be
physical to physical, physical to virtual, or virtual to virtual. Consider
the following examples:
v A physical to physical relationship might be an IBM Power system to
a disk unit.
v A physical to virtual relationship might be a host system to a virtual
server.
v A virtual to virtual relationship might be a virtual server connected
to a virtual LAN.
To In the resource view, the resource that is the ending point of a
relationship. For example, if System A is the host for Virtual Server 1,
then Virtual Server 1 is the ending point of the relationship.
2. To perform actions on a resource in a relationship, select a relationship row.
Then, click Actions, select either the To or From resource, and click a task.
Tips:
v You also can right-click the resource and select a task from the pop-up menu.
v Use the pop-up menu or the Actions menu to perform actions on either of
the resources represented in the relationship.

Related concepts:
Relationship view
Related tasks:
Navigating tables
Filtering table information

After you have entered the topology map view, you can change to alternate views
of the resources and relationships that you chose to view in the topology map
view.
You first must enter the topology map view before you can change to the
relationship table or resource table views. If a task provides the topology map
view, the Topology Perspectives action is available in the Actions menu.
After you enter the topology map view, you can change to the relationship view or
the resource view and then return to the map view. All views are available in the
Actions menu and the view that you are currently using is checked.
Also, the properties view is always available from the Actions menu. Select a
resource and then click Actions > Properties.
When selecting a view, consider the following information:

v In the map view, you can view related resources of multiple types, including
their status information. Also, you can control the levels of resources that you
view. For example, if you choose to view three levels, the map displays all
resources that are up to three levels away from the primary resource, such as a
server, its RAID controller, and any attached RAID physical drives.
v In the resource view, you can view all the resources from the map view, but in a
table that is easier to filter and sort.
v In the relationship view, you can view the types of relationships that exist
between the resources in the map view.
v In the properties view, you can view all the troubleshooting information for a
resource in one place.
Related tasks:

You can customize the view that you want displayed when you open a resource in
the topology map. This setting is provided for accessibility requirements and
screen reader support; the setting affects only the view that is shown when the
resource is opened. After you have opened the resource, you can switch to a
different view. By default, this option is not selected; therefore, the topology view
is the default view. When this setting is selected, the topology view is not initially
displayed when you select Topology Perspectives.

To set the default resource view, complete the following steps:
1. In the IBM Systems Director Web interface navigation area, expand Settings
and click Navigation Preferences.
2. On the Navigation Preferences page, select or clear Use the resource table view
as the default view for topology maps.
the page without saving the settings, click Cancel. To reset the settings to the
system-defined values, click Restore Defaults. You still must click OK or
Apply to save the restored settings.
Related tasks:
Working with tables

Working with tables and table information is a common task in the IBM Systems
Director Web interface. In addition to navigating tables, you can filter, sort, search,
export, and print table information. You can add resources to your Favorites view
that you use frequently. Also, you can customize your table navigation preferences
and adjust table columns.
Related concepts:
Resource views
Related tasks:
Renaming a resource
Removing a resource
Navigating tables
Navigating tables is a common task in IBM Systems Director. Most resources and
information are displayed in tables.
To navigate in tables, complete the following steps:

1. Open a task, such as Resource Explorer, that uses tables for navigating
resources.
2. Click a resource or group in the task table. Depending on the resource or group
that you click, the following information is displayed:
v If you click an individual resource that contain other resources, its
subsystems or related resources are displayed. For example, you can drill
down to view disks related to a server or fans related to a BladeCenter
chassis. Depending on the resource, there might be several levels through
which you can drill down. You can continue to click or drill down on
resources to see lower-level subsystems or resources.
v If you click a resource that does not contain other resources, then that
resource's properties are displayed. Depending on the pages provided for the

resource, you can access information such as inventory and event status;
configuration settings; and information about the jobs, thresholds, software
packages, activations, or event automation plans that are associated with the
resource. For information about the Properties page, see “Viewing
properties.”
v If you click a group, a list of the included systems and resources is
displayed.
3. If you want to change the number of rows that are displayed in the table,
change the Rows per table setting in the Navigation Preferences page. For more
information see “Setting table-navigation preferences.”
4. If you want to navigate to an earlier part of your path in the table, click the
applicable part of the breadcrumb path located above the table. As you drill
down through related resources or to properties pages, the breadcrumb path is
extended to reflect the path you have taken.
5. Continue to click or drill down through resources to see lower-level subsystems
or resources.
The Actions menu also provides alternative ways to navigate the resources in
the table. Clicking Actions > Related Resources provides a list of resources that
are related to your selected resource. Select a related resource from the list to
navigate quickly to it. If applicable, alternate views might be available from the
Actions menu. Clicking Actions > Topology Perspectives displays a map of
resources and their relationships starting from the selected resource. For
information about Topology Perspectives, see “Topology Perspectives views.”
6. If you want to perform tasks or other actions on your resources, select one or
more resources. Then, you can either right-click the resource or click the
Actions menu. Both menus provide tasks and actions that are available for the
selected resources. These tasks and actions fall into the following categories:
v Actions that provide navigational alternatives. Related Resources provides a
list of resources that are related to the selected resource. Using this list, you
can navigate quickly to any related resource. If applicable, alternate views
also might be available. For example, the Topology Perspectives view
displays a map of resources and their relationships starting from the selected
resource. For information about Topology Perspectives, see “Topology
Perspectives views.”
v Specific tasks or actions that are applicable to a selected resource in the table.
For example, if you select a system in a table, these actions might include
Create Group, Power On, Access Control, Encryption Key Reset, and others.
v Globally available tasks and actions. For example, these tasks might include
Create and Create Like if they are applicable to a resource.
v Actions that are specific to tables such as filtering, sorting, exporting, and
adjusting columns.

Related concepts:
Table view
Related tasks:
Viewing properties
Sorting table information
Searching table information
Printing tables
Exporting table information
Adding resources to your Favorites view
Adding a group of resources to the Health Summary
Setting table-navigation preferences
Setting table-column preferences
Viewing properties
For information about viewing properties in a topology map view, see “Viewing
properties and details.”
To view properties for a resource in a table, complete the following steps:

1. In the table, select a resource.
2. Click Actions > Properties. On the Properties page, the resource area displays
one or more pages. The number of pages and the types of information they
include vary depending on the resource. The General page is displayed by
default.
3. View the properties displayed on the General page. Some properties are
editable. For information about editing properties, see “Editing properties.”
4. Optional: If additional pages are available, click them to view additional
properties information and troubleshooting information. Depending on the
pages provided for the resource, you can access information such as inventory
and event status; configuration settings; and information about the jobs,
thresholds, software packages, activations, or event automation plans that are
associated with the resource.

Related concepts:
Properties view
Related tasks:
Editing properties
Navigating tables
Printing tables

Within any IBM Systems Director Web interface table, you can use the filtering
options that are available from the Action button. After you have completed
filtering resources in the table view, you can see the rows that match your filter
criteria in the table.
Note: Filtering is not persistent; filter settings are not remembered for subsequent
uses of the list.
To filter information in any table, complete the following steps:
1. Click Actions > Show Filter Row. An additional row at the top of each column
is displayed. This row contains Filter links.
2. Click Filter to open the selectable filtering criteria for a column.
Note: The available filter conditions vary depending on the column.

3. In the Filter window, select the condition on which you want to filter the
column. The conditions available vary depending on the type of information
that the column contains:
Textual information, such as name and description
The Filter window provides the following settings, as well as an option
to match the case:
v Contains
v Starts with
v Ends with
Type information, such as resource type
The types present in this column determine the settings available for
filtering. For example, if the column contains hosts, platform managers,
physical processors, and storage systems, then those types are available
as filter selections. However, if the column contains only one type, for
example, only servers, then filtering is disabled for that column.
Health and compliance information
The Filter window provides settings that are applicable to the specific
information reported in the column. For example, the following settings
are used for health information:
v Critical

v Fatal
v Minor
v Warning
v Informational
v Unknown
v OK
Status information
are for access status:
v None
v Partial
v Full
Enumeration
The Filter window provides a list of settings that are applicable to the
specific information reported in the column.
Numeric information
The Filter window provides the following settings when applicable,
where x is a specified number and y is another specified number:
v All numbers
v Numbers less than x
v Numbers less than or equal to x
v Numbers greater than x
v Numbers greater than or equal to x
v Numbers equal to x
v Numbers not equal to x
v Numbers between x and y
v Numbers between and including x and y
Date, time, or date and time information
are used for the date:
v All dates
v Dates until
v Dates from
v Dates between
Boolean information
The Filter window provides information that can be filtered by Yes and
No selections.
4. Optional: To refine your filtering, you can edit the filter settings for additional
columns.
5. When you are satisfied with your filter settings, click OK. If you want to clear
all of your filter settings, click Actions > Clear All Filters.
6. When you finish filtering your table information, click Actions > Hide Filter
Row.

Related tasks:
Navigating tables
Viewing properties
Printing tables

Within any IBM Systems Director Web interface table, you can use the sorting
options that are available in the table column headers and from the Action menu.
To sort information in any table, complete the following steps:

1. If you want to sort all the rows by the values in one column, you can click the
Up Arrow and the Down Arrow in the applicable column heading. For
example, if you want to sort the rows by name, click the arrow in the Name
column for the sort direction that you want. If you want to sort the rows by
type, click the arrow in the Type column.
You can control the sorting of a column by a series of clicks on the column
heading:
v The first click sorts the rows in ascending order (Z-A).
v The second click reverses the sort, that is, to descending order (A-Z).
v The third click removes the sort altogether.
2. If you want to all the rows by the values of more than one column, click
Actions > Edit Sort. For example, you might want to sort all the rows by type
but, within type, you want the rows sorted by name.
3. In the Edit Sorts window, a list is displayed for each available column on
which you can sort. In the First Sort list, select the column that contains the
data you want sorted first. Also, select the order of the sort: Ascending (Z-A) or
Descending (A-Z).
4. Optional: If you want to sort the table information on additional columns,
continue to make selections in the additional sort lists.
5. When you are satisfied with your sort settings, click OK.
6. If you want to clear all of your sort settings, click Actions > Clear All Sorts.

Related tasks:
Navigating tables
Viewing properties
Printing tables

Within any IBM Systems Director Web interface table, you can search for a specific
string in the table information.
To search any table, complete the following steps:

1. Type a string in the Search the table field. Any matching strings in the
currently displayed table are highlighted.
2. Click Search. All of the pages in the table are searched for the provided string
and any rows that contain the string are displayed in a new table.
Related tasks:
Navigating tables
Viewing properties
Printing tables
Printing tables
If a table is only one page long (that is, you can view the entire table on the page),
you can use your Web browser to print the table information. Otherwise, to print
tables that are more than one page long, you can export the table data to a CSV
file that you can subsequently import into a spreadsheet program and print using
that program.
Note: Be sure the Web browser option to block pop-up windows is turned off for
the URL that you use to log in to the IBM Systems Director Web interface.
If you want to increase the number of table rows that are displayed on one page,
see “Setting table-navigation preferences” for information.
To print a multiple-page table, see “Exporting table information.” To print a

one-page table, complete the following steps:
1. In your Web browser, click File > Print.

2. In the Print window for your Web browser, click the option to print the
selected frame. Selecting this option will print only the IBM Systems Director
Web interface content area and not the navigation area.
3. Optional: Adjust your orientation setting to landscape so that the table width
can be printed. Typically, this is a printer setting and must be changed in the
printer properties.
4. In the Print window, click OK.
Related tasks:
Navigating tables
Viewing properties

Within any IBM Systems Director Web interface table, you can export the table
data to a CSV file that you can subsequently import into a spreadsheet program.
To export data from any IBM Systems Director Web interface table, complete the
following steps:
1. Click Actions > Export.
2. In the file download window for your Web browser, click Save to Disk and
then click OK.
3. If your Web browser requires a location selection, provide it and click Save.
The data is exported and a CSV file is saved in the location that you provided.
Tip: You can print a multiple-page table using a CSV file. Import the CSV file into
a spreadsheet program and use the program's print feature.

Related tasks:
Navigating tables
Viewing properties
Printing tables

You can save resources that you refer to frequently into a special location: your
Favorites view. Having all these resources in one location makes managing your
system-management environment easier.
You can add a resource to your Favorites from many places in the IBM Systems
Director Web interface. Whenever the Actions menu or a pop-up menu provides
the Add to > Favorites selection, you can add the resource to your Favorites. To
add a resource to your Favorites, complete the following steps:
1. In an IBM Systems Director Web interface table, navigate to the resource that
you want to save.
2. Optional: If you want to add multiple resources to your Favorites at once,
select each resource in the table that you want to save.
3. Right-click the resource (or a selected resource) and then click Add to >
Favorites. A confirmation message is displayed.
To view your Favorites, navigate to the Health Summary page. In the IBM Systems
Director Web interface navigation area, expand System Status and Health and
click Health Summary. Favorites - userid, where userid is your user ID, is
displayed in the Health Summary page.
Related tasks:
Using the Health Summary task to view the status of your environment
Navigating tables
Viewing properties
Printing tables

You can save a group of resources in the Health Summary for easy reference. The
resources must be in a group. On the Health Summary page, a thumbnail of the

group contents is displayed. You can add a resource to the Health Summary
whenever the Actions menu or a pop-up menu provides the Add to > Health
Summary selection.
The resources must be in a group. If the resources are not in an appropriate group,
use the Create Group wizard to create a group. For information, see “Managing
groups.”
To add a resource to the Health Summary, complete the following steps:

1. In a table, select the group that you want to save in the Health Summary.
2. Click Actions > Add to > Health Summary. A confirmation message is
displayed.
To view the Health Summary, navigate to the Health Summary page. In the IBM
Systems Director navigation area, expand System Status and Health and click
Health Summary.
Related tasks:
Managing groups
Navigating tables
Viewing properties
Printing tables

You can customize your preferences for navigating in the table view. These
preferences include table accessibility, your preferred navigation view, and more.
To set the preferences, complete the following steps:

2. On the Navigation Preferences page, you can set the following preferences that
affect the table view:
Enable tables for accessibility
Select this option to turn off table features that are not accessible in the
interface, such as fixed column width. By default this option is not
selected.
Play sound when data on the page changes
Select this option to turn on a notification sound that is played when
the graphical user interface is refreshed. Examples of situations that can
cause a notification sound include a page refreshing dynamic data, a
user selection that displays additional controls or options, a table
completes a sort, or a user starts a page refresh. By default this option
is not selected.

Use the resource table view as the default view for topology maps
Select the view that you want displayed when you open a resource in
the topology map. This setting affects only the view that is shown
when the resource is opened. After you have opened the resource, you
can switch to a different view. By default, this option is not selected;
the topology view is the default view.
Rows per table
Specify the number of rows to display on a page in the table view for
Resource Explorer and other navigation tables in IBM Systems Director.
The default number of rows is 15.
Rows per embedded table
Specify the number of rows to display in an embedded table in the
table view for Health Summary and other navigation tables in IBM
Systems Director. The default number of rows is 10.
Related tasks:
Navigating tables
Viewing properties
Printing tables

You can customize your preferences for the table columns used in Resource
Explorer and all other tables used in the IBM Systems Director Web interface.
These preferences include the available columns that are displayed in the table,
how the columns are ordered (except for Name, which is always the first column),
and the width for each column. Note that you also can adjust the column width by
dragging the column handles in the table-column header.
Note: These settings affect tables in the following ways:

v If you are viewing a group when you open the Column Preferences window, the
preferences are saved with the group. The preferences are saved specifically for
your use; group column preferences for other users are not affected.
v If you are viewing a set of resources of the same type when you open the
Column Preferences window, the preferences are saved for any time you view
that same resource type.
To set the table-column preferences, complete the following steps:

1. In the IBM Systems Director Web interface task table, click Actions > Columns.

2. In the Columns window on the Order page, select the columns that you want
to display. Use the Add and Remove buttons to move columns between the
Available columns list and the Selected columns list.
3. To adjust the order in which the columns are displayed, select the column from
the Selected columns list and use Up and Down to adjust the order.
Note: You cannot adjust the Name column; it is always the first column.
4. Click the Width tab. The Width page provides an adjustable width setting (in
pixels) for each column displayed in the table.
Note: You also can adjust column width by dragging the column handles in
the table-column header.
5. If you want to change the settings on the page to the system-defined default
values, click Restore Defaults.
The table is adjusted to display using the new column settings.

Related tasks:
Navigating tables
Viewing properties
Printing tables

The topology map view shows a graphical view of your resources and their
relationships. In addition to navigating maps, you can filter, search, export, and
print topology maps. Also, you can customize your topology map palettes and
map preferences.

Related concepts:
Resource views
Related tasks:
Working with tables
Renaming a resource
Removing a resource

You can navigate topology maps to view resources and their relationships to each
other in a graphical view.
To navigate in topology maps, complete the following steps:

1. Open a task that provides the topology map view as an alternate view.
Resource Explorer is one of these tasks.
2. On the task page, navigate to a resource that you want to view in a topology
map and select it. The selected resource will be the root node in the topology
map.
3. Click Actions > Topology Perspectives > Basic. The topology map displays
scalable topology graphs that you can manipulate using the following mouse
actions:
Table 2. Mouse actions in the topology map
Interaction Description
Scrolling and Topologies are often much larger than the topology-map viewing area. Therefore, you might
repositioning want to reposition the map to see specific resources.
You can reposition the topology map in the following ways:

v Use the eight scroll controls to scroll in eight directions. The scroll controls are displayed
as white arrows on all four sides and all four corners of the topology map. Click the
arrows to move the topology horizontally, vertically, and diagonally in small increments.
v Go to the Overview palette to reposition the topology map. A blue rectangle indicates the
viewable area of the topology map. Click and drag to move the blue rectangle around the
topology thumbnail. When the Overview rectangle is moved, the topology is repositioned
in the topology map.
v Click the Pan toolbar icon
to load the mouse with the Pan cursor, then click and drag inside the topology map.
v Press the Ctrl and arrow keys on the keyboard to scroll in four directions.
Resizing A resizing function is provided to enlarge the topology map. Click and drag the small gray
triangle in the lower right portion of the topology map to resize the viewable area in the
topology map. Dragging the small gray triangle only resizes the size of the viewable area; it
does not resize the topology.
Note: Resizing the topology map causes the entire page to resize within the interface.
Select a resource Click the resource icon or a resource label.
Select multiple To select two or more resources at the same time, click the first resource. Then press the Ctrl
resources key while using the mouse to select as many resources as you want.

Table 2. Mouse actions in the topology map (continued)
Interaction Description
Deselect resources Click the resource again, or click on the background within the topology map. Alternatively,
select the deselect action from the Actions menu.
Select a relationship Click the relationship line.
Select multiple To select two or more relationships at the same time, click the first relationships. Then, hold
relationships the Ctrl key down using the mouse to select as many relationships as you want.
Deselect a Click the relationship line again, or click on the background within the topology map.
relationship
Open a pop-up menu Right-click the icon or label.
for a resource Note: The pop-up menu items that are displayed are based on the icon or label that is
selected.
Open a pop-up menu Right-click the background within the topology map.
for the topology
Perform an action on Right-click the icon to access the pop-up menu and then select a menu action. Alternatively,
a resource select the icon or label and then select an action from the Actions menu.
Perform an action on Select multiple resources, and right-click any of the selected resources to access the pop-up
multiple resources menu; then select a menu action. Alternatively, select the icon or label and then select an
action from the Actions menu.
4. For large topology maps, use the Overview palette to view of the entire
topology map with a rectangle surrounding the portion of the map displayed
in the map viewport. You can click and drag within the Overview palette to
reposition the topology.
5. Optional: If you want to perform tasks or other actions on your resources,
select one or more resources. Then, you can either right-click on the resource or
click the Actions menu. Both menus provide tasks and actions that are
available for the selected resources. These tasks and actions fall into three
categories:
v Specific tasks or actions that are applicable to a selected resources in the
map. For example, if you select a system in a map, these actions might
include Create Group, Power On, Access Control and Encryption Key Reset.
If applicable, alternate views might be available. For example, Relationship
View displays a table of a selected resource and its related resources, and
lists their relationships.
v Globally available tasks and actions. For example, these task might include
Create and Create Like if they are applicable to a resource.
v Actions specific to maps such as graph mode, zoom, and layout.
6. If you want to navigate to an earlier part of your path, click the applicable part
of the breadcrumb path located above the map.

Related concepts:
Map view
Related tasks:
Searching the topology map
Printing topology maps
Exporting topology maps
Setting topology-navigation preferences

You can view properties and detailed information about a selected resource in a
topology map. Depending on the selected resource, the properties view also
provides dynamic troubleshooting information such as active status, inventory, and
event log.
To view properties and details, complete the following steps:

1. In the topology map, click a resource or relationship line.
2. View the Details palette for the properties information. If you selected a
relationship line, a relationship table is displayed. If you selected a resource, a
properties table is displayed.
Note: If you want to reorder or adjust the size of the palette, see “Reordering,
minimizing, and hiding palettes.”
3. To view all of the resource properties information, click Actions > Properties.
On the Properties page, the resource area displays one or more pages. The
number of pages and the types of information they include vary depending on
the resource. The General page is displayed by default.
4. View the properties displayed on the General page. Some properties are
editable. For information about editing properties, see “Editing properties.”
5. Optional: If additional pages are available, click them to view additional
properties information and troubleshooting information. Depending on the
pages provided for the resource, you can access information such as inventory
and event status; configuration settings; and information about the jobs,
thresholds, software packages, activations, or event automation plans that are
associated with the resource.
6. When you are done viewing the properties, click OK to return to the topology
map view.
You also can change editable properties. For more information, see “Editing
properties.”

Related concepts:
Properties view
Related tasks:
Editing properties
Related reference:
Topology-relationship descriptions

Topology maps display relationships between resources using lines. A line can
indicate one of many relationship types. There are several ways that you can
determine the type that a line indicates.
You can determine the type of relationship that a line indicates in any of the
following ways:
v In the topology map, click a relationship line. Then, view the Details palette. The
relationship type is listed in the Details palette.
v In the topology map, right-click a resource at either end of the relationship line
and then click Relationship View. The relationship table view is displayed. The
information is listed in the Relationship Type column.
v On the topology map toolbar, click the Hover Help icon . Then, move the
mouse pointer over the relationship line to view information about the
relationship, including the relationship type.
For information about each relationship type, see “Topology-relationship

descriptions.”
Related tasks:
Related reference:

Within any topology map, you can use the filtering options that are available from
the Filter palette. Use this palette to select the resources that you want to see in the
topology map. You can filter your selections by status and by resource type. When
filtered, the affected resources and relationships are grayed out in the map. The
Filter palette also provides a Results page that displays the results of searching the
map view.
To filter a map, complete the following steps:

1. View the Filter palette in the Support area. The palette has two pages: Filter
and Results. On the Filter page, the palette provides two types of settings on
which you can filter: status and resource type.
2. If you want to filter by resource status, go to the Status Items group and clear
the selections that you want to filter from the topology map. Any resource in
the topology map that has a status matching a cleared selection is grayed out in
the topology map. For example, if you clear the OK check box, any resources
that have a status of OK are grayed out in the topology map.
3. If you want to filter by resource type, go to the Resource Types group and
clear the selections that you want to filter from the topology map. Any resource
of a type that matches a cleared selection is grayed out in the topology map.
For example, if you clear the Server check box, any resources that are a server
resource type are grayed out in the topology map.
4. Click the Results tab. The Results page displays a table of information about
the resources that are not grayed out in the topology.
Note: Filtering is not persistent; filter settings are not remembered for subsequent
uses of the map.
Related tasks:
Related reference:

You can search for a specific resource name in a topology map. Any resources in
the map that do not match the specified string are greyed out in both the large
topology map and the thumbnail topology map in the Overview palette.
To search a map, complete the following steps:

1. Type a string in the Search the map field.
2. Click Search. The name field is searched for the specified string. Any resources
in the map that do not match the specified string are greyed out in both the
large topology map and the thumbnail topology map in the Overview palette.
The search results also are displayed in the Filter palette on its Results page.

Related tasks:
Related reference:

You can choose to print the entire topology or only a portion of the overall
topology.
To print a topology map, complete the following steps in the topology map view:
1. To print the entire topology, click the Print Graph icon from the toolbar. A
Web browser window opens containing a JPEG image of the graph.
2. You can either print the graphic using your Web-browser print feature or save
the graphic as a local image.
3. To print only the current resources and relationships that are displayed in the
topology map view, click the Print Viewport icon from the toolbar. The
currently displayed resources and relationships might be only a portion of the
overall topology. A Web browser window opens containing a JPEG image of the
graph.
4. You can either print the graphic using your Web browser print feature or save
the graphic as a local image.
Related tasks:
Related reference:

You can export the topology-map data to a CSV file that you can subsequently
import into a spreadsheet program.

To export data for an entire topology map, complete the following steps in a
topology map view:
then click OK.
Related tasks:
Related reference:

The topology map view provides palettes that display overview and detailed
information as well as filtering options. You can reorder the position of the palettes
to meet your preferences, you can minimize one or more palettes, or you can
completely hide the support area that displays the palettes.
Each palette has arrow icons on the title bar as applicable. For example, if a palette
is the top palette in the support area, its title bar includes only a down arrow. The
middle palette include both up and down arrow icons. To reorder a palette, click
the applicable up or down arrow icons until the palette is in the order that you
prefer. To save the new palette order to use whenever you use the topology map
view, select Remember palette state in Navigation Preferences. For more
information, see “Setting topology-navigation preferences.”
To minimize or hide palettes, complete the following steps in the topology map
view:
v To minimize a palette, click the Minimize icon on the palette title bar to the
right. The palette minimizes and only the palette title bar is displayed.
v To maximize the palette, click the Maximize icon on the palette title bar to the
right. The palette maximizes and is fully displayed.
v To completely hide all of the palettes, click the Hide Palette View icon on
the navigation toolbar. The support area is closed.
v To show the support area and the palettes, click the Show Palette View icon
on the navigation toolbar. The support area is displayed.

Related tasks:
Related reference:

You can customize your preferences for navigating in the topology map view.
These preferences include the way that topology map palettes are displayed, the
default topology and table sizes, your preferred navigation view, and more.
To set the preferences, complete the following steps:

2. On the Navigation Preferences page, you can set the following preferences that
affect the topology map view:
Show palettes on initial view
Select to display the Overview, Details, and Filter palettes in the
topology map view. If you deselect this setting, you will see the
topology map without the palettes; you can show the palettes again by
clicking the Show Palette View icon on the navigation toolbar.

This option is selected by default.
is not selected.
Remember palette state
Select to make sure that the state of your palettes persists even as you
navigate away from the topology map view, change to another page in
the overall IBM Systems Director Web interface, or log off from the IBM
Systems Director Web interface. For example, you can customize the
topology map view by minimizing or reordering the Overview, Details,
and Filter palettes. By selecting Remember palette state, you maintain
the customized view of your palettes even after you log out of the IBM
Systems Director Web interface. This option is selected by default.

Topology map size
Specify the dimensions to use for the topology map view.
Remember last size used
Specify that you want to save the dimensions of the current
topology map view and use these dimensions at the next
startup. This option is selected by default.
Custom size (pixels)
Specify custom dimensions for the topology map view. The
following dimensions are the defaults:
v Width: 500 pixels
v Height: 500 pixels
Preferred size for topology map icons (pixels)
Specify the size of icons in the topology map when the map is
displayed initially. The default value is 50.
Related tasks:
Related reference:
Relationships between different resources are displayed as lines, and the direction
of the relationship is shown by the direction of the arrow attached to each line. As
you work with the topology map, it is important to understand that relationship
types are differentiated by the lines.
The following relationships are available:

Table 3. Types of relationship lines in the topology map
Type Description
Accessed via Shows that a resource is accessed from, or accesses another resource.
For example, a system accesses an image repository.
Advertises Shows that a certain capability is available on a system. For example,
if a system offers a Web service, it might advertise that Web service
capability.
Allocated from Shows that a resource is allocated from or allocates another resource.
For example, a storage volume is allocated from a storage pool.
Applies to Shows that a resource applies to another resource. For example, a
software product can be applied to a system.

Table 3. Types of relationship lines in the topology map (continued)
Type Description
Assigned to Shows that a resource is assigned to, or assigns another resource. For
example, a DVD drive is assigned to a virtual server.
Binds to Shows that a setting is bound to a specific resource. For example, a
specified IP address was bound to the given TCP/IP port.
Boots from Shows the link between an operating system and the file system from
which it is loaded.
Configured using Shows the settings that have been used to configure a specific
resource.
Configures Shows that a resource template was used to configure an instance of a
resource. For example, a software instance is one of the instances that
were configured during of a general Software Installation.
Connected to Shows that a resource is connected to another resource. For example, a
system is connected to a network through a particular port.
Contains Shows that a resource is contained by or contains another resource. For
example, a host contains a physical processor or a rack contains a
chassis..
Controls/ Shows that a resource is controlled by, or controls another resource.
controlled by For example, a platform manager controls a host or a virtual farm.
Controls access to Shows a resource that controls access of another resource. For example,
a Role controls the access rights of a particular user.
Defined using Shows that a resource was defined using another resource. For
example, a template was defined using specific configuration settings.
Federates Shows a logical relationship between two resources. Resources that
exist independently are federated by a separate entity to create a
logical contain relationship. For example, hosts are federated by a
virtual farm.
Fixes Shows the resource that fixes another resource. For example, a
firmware update fixes a system.
Hosts/hosted by Shows that a resource is hosted by or hosts another resource. For
example, a virtual server is hosted by a host.
Installed as Shows that a software module was used and installed as a specific
software resource.
Installed on Shows the relationship between an operating system, software, or fix,
and a computer system. For example, an operating system is installed
on a server.
Latest for This relationship represents that the given Software Module is the
latest for the given computer system.
Located at Shows that the given physical resource or system is located at the
provided Location.
Member of Shows membership of a group or other container. For example, a blade
server is a member of a BladeCenter chassis.
Needs Shows that a Software Module is missing from the System and must
be applied to it. For example, an update might be needed by an
operating system.
Performs Shows the entity that performs a service. For example, a set of
processes perform a service, or a system performs a particular role,
such as a domain name server.
Plugs into Shows that the given resource plugs into the provided Slot.

Table 3. Types of relationship lines in the topology map (continued)
Type Description
Provides Shows that this Service is provided by the System.
Realizes/realizes Shows that one resource provides the physical reality of another
by resource. For example, a host processor realizes a virtual processor
allocation.
Recommended for Shows that the given Software Module is recommended for the given
System.
Represents Shows that the given Software Module is considered represented
within the Software Installable.
Requires Shows that a resource requires or is required by another resource. For
example, an update might have three requisite updates that must be
installed at the same time.
Runs on Shows that a resource runs on another resource.
Supersedes Shows that a Software Resource is considered to be a superset of
another Software Resource and is therefore superseding it. For
example, an update might be more recent than another and therefore
supersedes it.
Uses/used by Shows that a resource is used by another resource. For example, a
virtual server uses a processor allocation.
Related tasks:


Related concepts:
Resource views
Properties view
Related tasks:
Working with tables
Renaming a resource
Removing a resource
Editing properties
If a resource property is editable, you can edit it in the properties view.
To edit a property, complete the following steps:

1. Navigate to the resource that you want to view and edit.
2. Right-click the resource and click Properties. The General page is displayed by
default in the properties view.
3. Click Edit at the bottom of the General page. The Edit window opens and
displays the properties. The properties vary depending on the resource. Only
some of the properties are editable. The editable properties are displayed in
fields and lists.
4. Edit one or more of the editable properties.
5. When you are satisfied with your changes, click OK to save the changes.
Related tasks:
Viewing activities that affect a resource
Editing location information for a resource
Editing location information for a group
Related reference:
chsys command

A resource can potentially be affected by a number of applied activities, such as
jobs, thresholds, software packages, activations, or event automation plans. You can
determine applied activities that affect a specific resource in the properties view.
To view the applied activities associated with a resource, complete the following
steps:
1. Select the resource for which you want to view the applied activities.
2. Click Actions > Properties.
3. On the Properties page, click the Applied Activities tab.
The Applied Activities page displays a list of any jobs, thresholds, software
packages, activations, and event automation plans that are associated with the
resource.

Related tasks:
Editing properties

You can edit the location information that you have provided for an individual
resource. You can edit location information only if you have installed and activated
the Service and Support Manager plug-in or the Active Energy Manager plug-in.
To edit the location information for a resource, complete the following steps:
1. On the Properties page, if the General page is not displayed, click the General
tab to view the General page.
2. In the Additional Properties area, click Location.
3. Click Edit.
4. In the Edit Properties window, make the updates to the location information.
5. Click OK.
Related tasks:
Editing properties

You can edit the location information that you have provided for a group of
systems. You can edit location information only if you have installed and activated
the Service and Support Manager plug-in or the Active Energy Manager plug-in.
To edit the location information for all of the systems in a group, complete the
following steps:
1. In Resource Explorer, right-click the group that you want to update.
2. Click Edit Location.
3. In the Edit Location window, select the boxes next to the information that you
want to update.
Note: Only the information in the fields that you select will be updated.
Changes made to other fields will not be saved.
4. Make the updates to the location information.
5. Click OK.
Related tasks:
Editing properties

You can customize your preferences for navigating in IBM Systems Director. These
preferences include the way that topology map palettes are displayed, the default
topology and table sizes, your preferred topology icon size, and more.
To set the navigation preferences, complete the following steps:

2. On the Navigation Preferences page, you can set the following preferences:
Show palettes on initial view
Select to display the Overview, Details, and Filter palettes in the
topology map view. If you deselect this setting, you will see the
topology map without the palettes; you can show the palettes again by
clicking the Show Palette View icon on the navigation toolbar.

This option is selected by default.
Remember palette state
Select to make sure that the state of your palettes persists even as you
navigate away from the topology map view, change to another page in
the overall IBM Systems Director Web interface, or log off from the IBM
Systems Director Web interface. For example, you can customize the
topology map view by minimizing or reordering the Overview, Details,
and Filter palettes. By selecting Remember palette state, you maintain
the customized view of your palettes even after you log out of the IBM
Systems Director Web interface. This option is selected by default.
Enable tables for accessibility
Select this option to turn off table features that are not accessible in the
interface, such as fixed column width. By default this option is not
selected.
is not selected.
Topology map size
Specify the dimensions to use for the topology map view.
Remember last size used
Specify that you want to save the dimensions of the current
topology map view and use these dimensions at the next
startup. This option is selected by default.
Custom size (pixels)
Specify custom dimensions for the topology map view. The
following dimensions are the defaults:
v Width: 500 pixels
v Height: 500 pixels
Rows per table
Specify the number of rows to display on a page in the table view for
Resource Explorer and other navigation tables in IBM Systems Director.
The default number of rows is 15.

Rows per embedded table
Specify the number of rows to display in an embedded table in the
table view for Health Summary and other navigation tables in IBM
Systems Director. The default number of rows is 10.
Preferred size for topology map icons (pixels)
Specify the size of icons in the topology map when the map is
displayed initially. The default value is 50.
Related concepts:
Resource views
Related tasks:
Working with tables
Renaming a resource
Removing a resource
Renaming a resource
You can rename a resource in the IBM Systems Director database. If the name that
was set for the resource when it was discovered is not easily usable for you, you
can rename the resource.
To rename a resource in the IBM Systems Director database, complete the

following steps:
1. Navigate to the resource that you want to rename.
2. Select the resource. Then, click Actions > Rename.
3. In the name field, type the new resource name.
4. In the Rename window, click OK.
The selected resource is renamed in the IBM Systems Director database.
Note: Consider how renaming a resource might affect other aspects of your
managed environment. For example, changing the name of a managed resource
that an event filter specifies as an event sender causes any associated event
automation plan to fail unless you update the sender name in the event filter.

Related concepts:
Resource views
Related tasks:
Working with tables
Removing a resource
Related reference:
chsys command
Removing a resource
You can remove a resource from the IBM Systems Director database. Removing a
resource from the database also removes any additional resources that are
associated with it but does not affect the actual resources. However, removing a
resource from the database is useful when you are removing a resource from your
systems-management environment.
Resources have a properties that determines whether they can be removed. If the
property does not permit removal, this task is not available for the resource.
To remove one or more resources from the IBM Systems Director database,
complete the following steps:
1. Navigate to the resource that you want to remove.
2. Select the resource. Then, click Actions > Remove.
3. In the Remove window, OK.
4. A confirmation message is displayed. Click OK.
The selected resource is removed from the IBM Systems Director database.

Related concepts:
Resource views
Related tasks:
Working with tables
Renaming a resource
Related reference:
rmsys command
Managing groups
You can use IBM Systems Director to organize logical sets of resources into groups.
Depending on the type of group that you create, you can use groups to easily
identify and categorize new resources when they are discovered. You can schedule
tasks to run on groups of resources. Using an event automation plan, you can
automatically run tasks on groups of resources. You can create, edit, import, and
export customized groups of resources. Groups are displayed in Resource Explorer,
Health Summary, wizards, and throughout the IBM Systems Director Web
interface.
Groups
You can use IBM Systems Director to organize logical sets of resources into groups.
Groups have the following general characteristics:

v Groups can include resources.
v Groups can include other groups.
v Resources can belong to multiple groups.
v You can perform tasks on groups in order to perform the task on every group
member.
v When you select a group in Resource Explorer, the resources that are members
of that group are displayed.
Related concepts:
Manageable systems
Related tasks:
Creating a criteria-based dynamic group
Creating a static group
Editing a group
Deleting a group
Adding a resource to an existing group
Exporting a group
Importing a group
Related reference:
Group commands
Group types
You can create dynamic and static groups in IBM Systems Director.

Dynamic groups
Dynamic groups are based on specified system criteria. You can create a
dynamic group by specifying criteria that the attributes and properties of
the systems must match. IBM Systems Director automatically adds or
removes systems to or from the group when their attributes and properties
change and affect their matches to the group criteria.
For example, a dynamic group might contain all systems that have Linux
installed.
Note: You cannot edit or delete static default groups.

Static groups
Static groups contain a specified list of systems. IBM Systems Director
Server does not automatically update the contents of a static group. The
members of a static group are fixed unless you change them using the IBM
Systems Director Web interface, the dircli chgp command, or an event
automation plan. You also can copy the members of any dynamic group to
a static group.
For example, a static group might contain all the systems that are
physically located in a particular server room.
Related concepts:
Default or predefined groups
Group member types

When you start Resource Explorer, the discovered resources are categorized and
displayed in default groups. You can click a group to view subgroups that further
categorize the resources for ease-of-use.

All Systems
All discovered systems in IBM Systems Director, including servers, chassis,
operating systems, switches, blades, and storage systems.
All Operating Systems
All operating systems that can be managed in the IBM Systems Director.
Groups by System Type
Systems categorized into subgroups by hardware and operating system
platform. The available subgroups vary, depending on the plug-ins that
you have installed in your IBM Systems Director environment.
v BladeCenter Systems
– BladeCenter Chassis
– BladeCenter Chassis and Members
– Power Systems Blade Servers
Note: The JS21 and JS22 blade servers are not displayed in this
group. They are displayed in the Power Systems group that is
contained in the IBM Power Systems group.
– x86 Blade Servers
– BladeCenter Servers
– BladeCenter Ethernet Switches
– BladeCenter Fibre Channel Switches
– BladeCenter InfiniBand Switches
– BladeCenter SAS Switches

– BladeCenter InfiniBand Switches to Ethernet Bridges
– BladeCenter InfiniBand Switches to Fibre Channel Bridges
– BladeCenter Pass-Through Modules
v Operating Systems
– Windows Systems
– Linux Systems
– AIX Systems
– IBM i Systems
– z/OS® Systems
v System x
– System x Servers
– Servers with Service Processors
– VMware Hosts
– Scalable Systems
- Scalable Virtual Servers and Members
- Scalable Systems and Members
v System z
– Hardware Management Console and Managed System z Servers
– z/VM Hosts
– z/VM Virtual Servers
– Linux on System z
– z/VM Manageability Access Points
v IBM Power Systems
– Hardware Management Console and Managed Power Systems Servers
– IVM and Managed Power Systems Servers
– Virtual I/O Server Appliances
– Power Systems
Note: The JS21 and JS22 blade servers are displayed in this group
also.
– AIX/Linux Virtual Servers
– IBM i (formerly i5/OS™) Virtual Servers
– Virtual I/O Server Appliances
– Isolated Workloads and Hosts
– AIX Workload Partitions (WPAR)
– Linux Containers
v Storage Systems
All groups provided by Storage Management. For information, see
“Storage groups.”
– Systems and Volumes
– Storage Subsystems and Volumes
– SMI-S Providers
– Internal RAID
– Network Storage
– BladeCenter Storage
– Generic Systems
Groups by Agent
Systems categorized into subgroups by the degree of management
capability available in the IBM Systems Director systems-management
environment. This default group provides the following subgroups:
v Systems with No Agent
v Systems with Platform Agent
v Systems with Common Agent

Groups by Status
Dynamic groups that contain systems for which there are unresolved
hardware status events. This default group provides the following
subgroups:
v Systems with Problems
v Systems not in Compliance
Groups by Access
Dynamic groups that contain systems depending on their current access
state. This default group provides the following subgroups:
v Systems with No Access
v Systems with Partial Access
v Systems with Full Access
Groups with Thresholds
Any groups to which you have applied a threshold.
Note: If you have migrated event automation plans from versions of IBM
Director earlier than version 6.1, event automation plans that use threshold
values are migrated to this group.
Personal Groups
Any groups that you have created or are exclusively associated with your
IBM Systems Director user ID. These subgroups include the Favorites
group.
Other Groups
Group definitions migrated from versions of IBM Director earlier than
version 6.1.
Update Groups
All groups provided by update manager. For information, see “Update
groups.”
Virtualization Groups
All virtualization groups.
Related concepts:
Group types
Group member types
Service and Support groups:
These predefined groups are available only if you have installed and activated the
Service and Support Manager plug-in. Service and Support Manager categorizes
systems into subgroups based on their service monitoring status.
This default group provides the following dynamic subgroups:

Excluded Systems
Contains resources that are ineligible for monitoring by Service and
Support Manager. The eligibility of a resource depends on many factors,
such as the type of resource, machine type, manufacturer, model, and serial
number.
Systems with Service Requests
Contains resources for which a service request has been opened with IBM
Support.

Monitored Systems
Contains resources that are being monitored by Service and Support
Manager.
Unknown Systems
Contains resources for which Service and Support Manager eligibility is
undetermined. The eligibility of a resource depends on many factors, such
as the type of resource, machine type, manufacturer, model, and serial
number. Service and Support Manager has not been able to determine the
resources' eligibility because the resource information is not available.
For more information on Service and Support Manager groups, see “Service and
Support Manager.”
Storage groups:
These predefined storage groups are shipped with IBM Systems Director so that
you can start working on storage configuration quickly, and can understand which
systems have which storage devices attached.
Do not delete or make changes to these predefined storage groups. Instead, make a
copy of one that you want to change and make changes to the copy.
BladeCenter Storage
Contains all systems that have IBM BladeCenter S SAS RAID Controller
Module storage for IBM Systems Director. This group is used to define
discovered storage contained within the IBM BladeCenter S SAS RAID
Controller Module itself. IBM BladeCenter S SAS RAID Controller Module
storage is included in this group as well as in the Network Storage group.
Local Storage
Contains all systems that have Internal RAID Controllers installed. They
could be systems with traditional adapter cards, or IBM BladeCenter
systems with RAID daughter cards.
Network Storage
Contains all discovered external storage systems. These are the SAN
systems. They could be Fibre Channel, SAS storage systems, or iSCSI
systems. IBM BladeCenter S SAS RAID Controller Module storage is
included in this group as well as in the BladeCenter Storage group.
SMI-S Providers
Contains all systems that have SMI-S providers installed and running.
An example is a system that has installed the SMI-S Provider for IBM
Storage System DS4000.
Storage Subsystems and Volumes
Storage subsystem volume to computer system volume topology.
Systems and Volumes
Computer system volume to storage subsystem volume topology.
Update groups:
Update groups can be static or dynamic. Both types can be used in compliance
policies.
Static update groups
Contain individual updates that were explicitly chosen. Once established,

the membership changes only when you manually add or delete updates.
Static update groups can be used as a baseline for future comparison or
update deployment.
Dynamic update groups
Automatically contains updates based on selected update types. The
membership of this group changes as update information changes.
It is important to note that the membership of an update group is not resolved at

the time that a task using the group is scheduled. The membership of the update
group is resolved at the time that the task runs.
If you add a system group or an update group to an existing system group or

update group, this new, nested group will not be considered when the parent
system or update group is used for validation of compliance policies.
Groups member types

In IBM Systems Director, groups have a member type that restricts the kind of
resource that can be a member of the group. For example, if a group is assigned
the member type Server, then only resources that are servers can be members of
the group.
The following member types are available:

Any Contains all resources.
Group Contains other groups.
Note: This member type is not available for dynamic groups.

Managed System
Contains resources that are managed in IBM Systems Director by way of
Common Agent or Platform Agent. Agentless-managed systems are also
included.
Update
Contains software and firmware updates.
Related concepts:
Group types

Dynamic groups are based on specified system criteria. You can create a dynamic
group by specifying criteria that the attributes and properties of the systems must
match. IBM Systems Director automatically adds or removes systems to or from
the group when their attributes and properties change and affect their matches to
the group criteria.
The criteria available for selection are derived from inventory. For example, you
can quickly group existing systems by creating a dynamic group using the criterion
Windows operating system. You can further refine the systems that can be in the
dynamic group by using logical AND with an additional criterion selection of
“Windows systems with critical problems.” Then, create an event automation plan
to notify you when these systems have problems. You also can schedule tasks to
run on all systems that match a certain criterion, such as Collect AIX Inventory
on a group called AIX systems.

To create a dynamic group, complete the following steps:
1. In the IBM Systems Director navigation area, click Resource Explorer.
2. In Resource Explorer, click Create Group.
3. In the Group Editor wizard, the Welcome page is displayed. Click Next.
4. On the Name page, type a unique descriptive name for the group that you are
creating. Optionally, you also can type a description of the group. Click Next.
5. On the Type and Location page, select Dynamic from the Group type list.
6. From the Member type list, select the type of member that you want included
in the group. A member type acts like a filter. Only resources of the specified
type can be part of the group you are creating.
Any Group membership is unlimited. Any resource can be in the group,
including systems, software, and management applications.
Managed System
Group membership is limited to system types such as different type of
servers, fabric, farms, hardware control points, controllers, operating
systems, chassis, switches, and storage.
Update
Group membership is limited to updates types such as for firmware,
IBM Systems Director, and operating systems.
7. From the Location list, select the parent group to contain the group that you
are creating. In Resource Explorer, a parent group is created and is located
under Personal Groups.
8. Click Next.
Option Description
If you selected Any or Managed System The Define page is displayed. Continue to
the next step.
If you selected Update The Updates page is displayed. Go to step
15 on page 95.
9. On the Define page, click Add. The Add Criterion window is displayed.
10. Refine the criteria from which you can select.
Option Description
If you selected Any 1. In the Resource category list, select the
type of resource with the criteria that
you want to evaluate.
2. In the Type of device to add list, select
the device type to further refine the
available criteria.
If you selected Managed System In the Type of system to add list, select the
system type to further refine the available
criteria.
a. In the Select criteria to refine group contents list, expand the tree and
select a criterion for the dynamic group to evaluate. Your selection is
displayed below the list.
b. Click Operators to select how you want the criterion evaluated by the
value you provide.

c. Click Value to select the value by which you want to evaluate the
criterion. If you want to specify a custom value, select Use entry from
below and type the custom value in the field.
Important: The custom value must match the value stored in the IBM
Systems Director Server database. Partial matches are not accepted. If the
value does not match, nothing is returned for this criterion.
d. Click OK. On the Define page, the criterion is displayed in the Criteria
preview field.
11. If you want to add additional criteria, click Add and repeat step 9 on page 94.
After adding another criterion, the Define page displays the logical AND and
the logical OR selections. These selections determine how the criterion that
you create now will affect the criterion you created previously.
You can use the logical AND only if your selected criteria belongs to the same
resource type or managed system type. For example, a criteria of
(Battery.description=’Sony’) AND (DiskDrive.NeedsCleaning=’true’) is
never true because a resource cannot be both a disk drive and a battery.
Therefore, if your criteria contain different resource types or managed system
types, the selection is set to logical OR and cannot be changed. If you do
select logical AND and subsequently add another criterion, the Add Criterion
window automatically displays the criteria that are valid for the resource type
or managed system type that you already selected.
12. If you want to change a criterion, select the criterion from the Criteria list and
click Edit. The Edit Criterion window is displayed with the settings for the
selected criterion. Change the settings and click OK.
13. If you want to delete a criterion, select the criterion from the Criteria list and
click Delete. A confirmation window is displayed; click Delete and the
selected criterion is deleted from the list.
14. Click Next and go to step 17.
15. On the Updates page, in the Available update types list, select the updates
that you want to add to the group and click Add. To make multiple selections,
press the Ctrl key and click your selections; then, click Add.
16. Click Next.
17. On the Summary page, verify the details of the group. If you need to make
changes, click Back; otherwise, click Finish.
The dynamic group is created and is displayed in Resource Explorer. A

confirmation message about the group creation is displayed also.

Related concepts:
Groups
Related tasks:
Editing a group
Deleting a group
Exporting a group
Importing a group
Related reference:
mkgp command

To make working with a set of resources easier, you can create a static group. For
example, you can create a static group for all the servers that you are responsible
for in your systems-management environment. Groups also can contain other
groups. For example, you can have a group called Development Systems that
contains three groups: one group for each development team.
To create a static group, complete the following steps:

2. In Resource Explorer, click Create Group.
3. In the Group Editor wizard, the Welcome page is displayed. Click Next.
4. On the Name page, type a unique descriptive name for the group that you are
creating. Optionally, you also can type a description of the group. Click Next.
5. On the Type and Location page, select Static from the Group type list.
6. From the Member type list, select the type of member that you want included
in the group. A member type acts like a filter. Only resources of the specified
type can be part of the group you are creating.
Any Group membership is unlimited. Any resource can be in the group,
including systems, software, and management applications.
Managed System
Group membership is limited to system types such as different type of
servers, fabric, farms, hardware control points, controllers, operating
systems, chassis, switches, and storage.
Update
Group membership is limited to updates types such as for firmware,
IBM Systems Director, and operating systems.
Group Group membership is limited to other existing groups.
7. From the Location list, select the parent group to contain the group that you
are creating. In Resource Explorer, a parent group is created and is located
under Personal Groups.
8. Click Next.
9. On the Define page, select one or more groups of resources from the
Available list and click Add. You also can drill down into a group and select
one or more resources. If you want to remove a group or resource, select it
from the Selected list and click Remove.
Notes:

a. You cannot add a group's parent to itself. For example, if you define the
parent group location for Group1 to be Personal Groups, then you cannot
add Personal Groups to Group1.
b. If you select a resource to add, but the Add button is unavailable, then the
selected resource is not a valid selection due to its member type.
10. Click Next.
11. On the Summary page, verify the details of the group. If you need to make
changes, click Back; otherwise, click Finish.
The static group is created and is displayed in Resource Explorer. A confirmation

message about the group creation is displayed also.
Related concepts:
Groups
Related tasks:
Editing a group
Deleting a group
Exporting a group
Importing a group
Related reference:
mkgp command
Editing a group
You can edit a group to change its name and description. If you are editing a static
group, you can edit the members of the group. If you are editing a dynamic group,
you can edit the membership criteria.
Note: You cannot edit default or predefined groups.
To edit a group, complete the following steps:

2. Click Actions > Edit.
3. In the Group Editor wizard, you can edit the name and description of the
group. If you are editing a static group, you can edit the members of the group.
If you are editing a dynamic group, you can edit the membership criteria.
4. On the Summary page, verify your changes to the group. If you need to make
changes, click < Back; otherwise, click Finish.
The group is updated with your changes and is displayed in the Resource
Explorer. A confirmation message about the group change is displayed also.

Related concepts:
Groups
Related tasks:
Deleting a group
Exporting a group
Importing a group
Related reference:
chgp command
chusergp command
Deleting a group
When a group is no longer useful, you can delete it.
To delete a group, complete the following steps:

2. Select the group that you want to delete.
3. Click Actions > Delete.
Attention: The group will be deleted for all IBM Systems Director users.
4. A confirmation message is displayed. Click Delete to delete the group.
The group is deleted and is no longer displayed in the Resource Explorer.
While you can delete the Favorites and Health Summary groups, the next time you
open Health Summary, the groups are recreated. However, they will not have any
members.
If you delete a group that was used when scheduling a job, the job remains and is
active, but it does not run because it does not have a target system against which
to run.

Related concepts:
Groups
Related tasks:
Editing a group
Exporting a group
Importing a group
Related reference:
mkgp command

You can add one or more resources to an existing static group. This is useful when
new systems or resources are added to your systems-management environment
and you want to include them in groups that are already serving your needs.
To add one or more resources to an existing static group, complete the following
steps:
2. Navigate to the resource or resources that you want to add to a static group.
3. Select one or more resources. Then, click Actions > Add to > Existing Group.
4. In the Add to Existing Group window, select one or more groups from the
Available list and click Add >. You also can drill down into a group and select
a subgroup. If you want to remove a group or resource, select it from the
Selected list and click < Remove.
Note: If the Add > button is unavailable, you cannot add your selected
resource to the selected group because of one of the following reasons:
v The selected group is a dynamic group. You can select only a static group.
v The selection is not a group, but an individual resource.
v The resource might already be a member of that group.
5. Click OK.
The selected resources are added the static group. A confirmation message about
the addition is displayed. Click View Group to view the affected group
immediately.

Related concepts:
Groups
Related tasks:
Navigating tables
Editing a group
Deleting a group
Exporting a group
Importing a group
Related reference:
chgp command
chusergp command
Exporting a group
You can export a group to archive or back up the criteria that define a group. After
a group is exported, you can distribute it to a new instance of IBM Systems
Director Server by importing the group through the IBM Systems Director Web
interface.
Before using Internet Explorer to export a group, complete the following steps:
1. In Internet Explorer, click Tools > Internet Options.
2. From the Security tab, click Custom level.
3. In the Settings list, scroll to the Downloads section.
4. Enable the Automatic prompting for file downloads setting.
5. Click OK.
6. A warning dialog displays. Click Yes to confirm the settings change.
7. Click OK to close the Internet Options window.
To export a group, complete the following steps:

2. Select one or more groups that you want to export.
3. Click Actions > Export Groups.
4. In the file download window for your Web browser, click Save to disk and
then click OK.
5. Optional: If your Web browser requires a location selection, provide it and click
Save.
The group is exported and an XML file is saved to the location that you provided.

Related concepts:
Groups
Related tasks:
Editing a group
Deleting a group
Importing a group
Related reference:
lsgp command
Importing a group
You can import a previously exported group so that you can distribute that group
to a new instance of IBM Systems Director Server.
Note: To import groups from versions prior to IBM Systems Director 6.1, make
sure you use Group Export to export the group in the earlier version of IBM
Director.
To import a group, complete the following steps:

2. Click Actions > Import Groups.
3. In the Group Import page, click Browse to navigate to the exported group file
that you want to import. Or, type the file name in the Select the file that you
want to import field.
4. Click OK. A progress indicator is displayed.
When the import is completed, a confirmation message is displayed and the group
is displayed in the Personal Group in Resource Explorer. If you want to view the
imported group in another group than Personal Group, select the imported group
and click Actions > Add to Existing Group.

Related concepts:
Groups
Related tasks:
Editing a group
Deleting a group
Exporting a group
Related reference:
mkgp command

The IBM Systems Director Web interface provides many tasks and many ways to
start these tasks. This section provides information about finding tasks as well as
how to start tasks. It also includes information about how to integrate external
tasks into IBM Systems Director Web interface.
Related tasks:
Navigating by way of the Home page
Managing groups
Scheduling tasks
Finding a task
IBM Systems Director provides a wealth of tasks that you can use to manage your
system-management environment. While many tasks can be found in the IBM
Systems Director Web interface navigation area, the Actions menu, or in pop-up
menus, you can quickly and easily find any task using Find a Task. Then, you can
run the selected task. If it is a targeted task, a list of available target systems is
provided.
To find a task, you must be authorized to use that task. If it is a targeted task, you
must also have authorization to access the systems. For more information see
“Security.”
To find tasks quickly in the IBM Systems Director Web interface, complete the
following steps:
1. In the IBM Systems Director Web interface navigation area, click Find a Task.
The Find a Task page opens and displays an alphabetical list of all available
tasks in your IBM Systems Director installation.
2. If you do not know the name of the task you want, go through the Find a Task
pages and view the descriptions of the tasks until you recognize the task that
you want. If you know all or part of the name of the task you want to find,
type the task name in the Search the table field and click Search. All of the
table columns are searched for the word that you typed. Any task that has the
entered word in any of its columns is displayed.
3. Click the task that you wanted to find to start it.

4. If the task requires a resource on which to work, the task will request the
resource. If the task does not require a resource, then the task opens
immediately.
Related concepts:
Security
Launched tasks
Related tasks:
Starting tasks
Related reference:
lstask command
Starting tasks
You can choose from several methods of starting tasks in the IBM Systems Director
Web interface.
Start a task from the IBM Systems Director Web interface navigation area in any of
the following ways:
v Click Find a Task. On the Find a Task page, you can search for and start a
specific task. For more information, see “Finding a task.”
Note: You can select a noninteractive task and click Actions > Run to schedule
the task to start immediately or at a later time. For more information, see
“Scheduling tasks.”
v Expand the sections in the navigation pane to view and click available tasks.
v Expand Task Management and click External Application Launch. You can
configure other applications to run from the IBM Systems Director Web
interface. For more information, see “Integrating external applications.”
v Click My Startup Pages. Any pages that you have saved to your Startup page
are displayed here. A saved page includes any tasks that can be run from that
page. For more information, see “Customizing the Web interface.”
v Click any of the tasks available in the navigation area.
Start a task from the IBM Systems Director Web interface content area in any of the
following ways:
v In a table view, right-click a resource and select a task.
Tip: You can run some tasks on multiple resources simultaneously. To perform a
task on multiple resources, select one or more resources. Then, right-click one of
the selected resources and select a task.
v In a table or topology map view, select one or more resources. Then, click
Actions and click a task.
v In the topology map view, right-click a resource and select a task.
v In the topology map view, select the resource. Then, in the Details palette,
right-click the resource and select a task.
v For applicable tasks, you can select Run Now or Schedule. You can schedule a
task to start immediately or at a later time. For more information, see

Related concepts:
Launched tasks
Related tasks:
Scheduling tasks
Finding a task
Integrating external applications
Related reference:
runtask command
Launched tasks
IBM Systems Director provide some tasks that start outside of the IBM Systems
Director Web interface. These tasks are launched tasks and are identified on menus
by the Launched tasks icon .
When you select a launched task, the task can be displayed in one of the following
ways:
v In another instance of your Web browser. The task provides its own Web
interface.
v As a separate program on your system desktop.
Note: Launched tasks require an installation of Java™ Web Start (JWS). For more
information, see “Downloading Java Web Start.”
Related tasks:
Downloading Java Web Start
Finding a task
Starting tasks
Related reference:
Troubleshooting for launched tasks

If you want to start tasks outside of the IBM Systems Director Web interface, the
Java Web Start (JWS) software must be installed on your browser system. JWS is
required on your browser system to enable launched tasks in IBM Systems
Director.
To download JWS, complete the following steps:

1. If your browser system requires JWS, a message window is displayed.
Complete the following applicable steps.
Option Description
For Windows and AIX Click Download Now.
For Linux 1. Select the applicable (Java Runtime
Environment) JRE for your browser
system.
2. Click Download Now.
2. Select to save the file to your hard disk drive or open and run the file
immediately, as applicable for your operating system.

3. When the JWS installation is complete, retry the launched task that you wanted
to use.
Related tasks:
Configuring Web browsers to use JWS
Configuring Web Browsers to use Java Web Start

To launch tasks, Web browsers must use a Java Web Start program, such as the one
that is installed with the Java Runtime Environment (JRE).
Related tasks:
Updating the Firefox Web browser to use the Java Web Start program:
To launch tasks that start outside the IBM Systems Director Web interface, the
Firefox Web browser must use the Java Web Start program that is installed with
the Java Runtime Environment (JRE).
To update the Firefox Web browser, version 3.6.13, to use the Java Web Start
program, complete the following steps:
1. In the Web browser, click Tools > Options.
2. In the Options window, click Applications from the toolbar.
3. Select the JNLP content type.
Note: If the JNLP file type is not available, see "Associating the JNLP file type
with the Java Web Start program (Firefox)".
4. In the Action column for the JNLP content type, select Use Java WebStart
Executable. If Java WebStart Executable is not available, select Use other... and
click Browse.
5. Navigate to the Java Web Start program, javaws.exe, located in the JRE
directory.
6. In the bin directory, select the javaws.exe program and click Open.
7. In the Options window, click OK. The Java Web Start program and the JRE are
now configured for use with launched tasks.
Related tasks:
Associating the JNLP file type with JWS (Firefox)
Associating the JNLP file type with the Java Web Start program (Firefox):
If, while updating the Firefox Web browser to use the Java Web Start program, you
determine that the JNLP file type is not available for configuration by way of the
Firefox Web browser, you must associate the JNLP file type with the Java Web Start
program.
To associate the JNLP file type with the Java Web Start program, complete the
following steps:
1. Click the IBM Systems Director task that required Java Web Start.
2. In the Opening launch.jnlp window that displays, click Open with and select
Other.
3. On the Choose Helper Application dialog, click Browse and navigate to the
Java Web Start program, javaws.exe, located in the JRE directory.

5. In the Opening launch.jnlp window, click Do this automatically for files like
this from now on.
6. Click OK. The task launches.
Related tasks:
Updating Firefox to use IBM JWS
Updating the Microsoft Internet Explorer Web browser to use the Java Web Start
program:
To launch tasks that start outside the IBM Systems Director Web interface, the
Microsoft Internet Explorer Web browser must use the Java Web Start program that
is installed with the Java Runtime Environment (JRE).
To update the Microsoft Internet Explorer Web browser, versions 6.0, 7.0, or 8.0, to
use the Java Web Start program, complete the following steps:
1. Start the Windows Explorer program.
2. Click Tools > Folder Options.
3. In the Folder Options window, click the File Types tab.
4. On the File Type page, select the JNLP file type and view the information in
the Details area.
Note: If the JNLP file type is not available, see “Associating the JNLP file type
with the Java Web Start program (MSIE).”
5. If the Details area reports that the JNLP file type has customized behavior,
a. Click Restore. The default behavior for JNLP files, opening with the Java
Web Start executable, is restored.
b. Click Advanced.
6. In the Edit File Type window, click Edit.
7. In the Editing action for type window, click Browse.
directory.
10. In the Editing action for type window, add the following string to the end of
the information in the Application used to perform action field: "%1"
Note: Be sure to type a space between the information and the new string.
11. Click OK.
12. In the Edit File Type window, click OK.
13. In the Folder Options window, click Close. The Java Web Start program and
the JRE are now configured for use with launched tasks.
Related tasks:
Associating the JNLP file type with JWS (MSIE)
Associating the JNLP file type with the Java Web Start program (MSIE):
If, while updating the Microsoft Internet Explorer Web browser to use the Java
Web Start program, you determine that the JNLP file type is not available for
configuration, you must associate the JNLP file type with the Java Web Start
program.

To associate the JNLP file type with the Java Web Start program, complete the
following steps:
1. Start the Windows Explorer program.
2. Click Tools > Folder Options.
3. In the Folder Options window, click the File Types tab.
4. On the File Types page, click New.
5. In the File Extension field, type jnlp and click OK.
6. On the File Types page, select JNLP in the Registered file types list and click
Advanced.
7. In the Edit File Type window, clear the Confirm open after download check
box and click New.
8. In the New Action window, select the Use DDE check box.
9. In the Action field, type &Launch.
10. In the Application field, type javaws.
11. In the Topic field, type System.
12. Click Browse.
directory.
15. Add "%1" to the end of the information in the Application used to perform
action field. Be sure to type a space between the information and the new
string.
16. Click OK.
17. In the Edit File Type window, click OK.
18. In the Folder Options window, click Close. The Java Web Start program and
the JRE are now configured for use with launched tasks.
Related tasks:
Updating MSIE to use IBM JWS
Configuring Secure Sockets Layer between IBM Systems

Director and the Web browser client
IBM Systems Director Server provides, by default, a Secure Sockets Layer (SSL)
certificate that supports HTTPS connections between IBM Systems Director Server
and the web browser client. To ensure server authentication, data privacy, and data
integrity, you must replace the default certificate. Replace the default certificate
with either a self-signed certificate or a certificate that is signed by a certificate
authority (CA). You must also change the keystore password.
It is not required that you use SSL to secure the network traffic between your
management server and client browser. However, configuring SSL ensures data
integrity and data confidentiality between the management server and web
browser client. This protection is especially important if you access the IBM
Systems Director from outside your network or if you use the launched tasks
feature of the IBM Systems Director Web interface.
Note: Logging in to IBM Systems Director is slower with SSL enabled.
Note: Make sure that the host name you specify in the Common Name field of the
SSL certificate matches the host name that you specify in the URL that you use to
access the web interface. For example, if you specify a long name for the host
name in the Common Name field of the certificate, you must specify a long name

in the URL. If these host names do not match, you might receive errors when you
try to open the web interface or start launched tasks. Follow the instructions in the
following procedure to make sure that you specify the correct host name in the
Common Name field of the certificate.
Note: When the SSL certificate that supports HTTPS connections between IBM
Systems Director Server and the web client expires or is not valid, you must
replace the certificate. If a client receives a web browser message that indicates that
the certificate is untrusted, expired, or not yet valid, then:
1. View the IBM Systems Director Server certificate.
2. Verify whether the certificate has expired.
If the certificate has expired, follow Step 1 - Step 5 to replace the certificate.
To replace the default certificate with a new certificate and to change the keystore
password for SSL, complete the following steps:
1. Delete the default certificate. For information see, “Deleting the default
certificate.”
2. Create a certificate. You can create either a self-signed certificate or request and
receive a CA signed certificate.
v To create a self-signed certificate, see “Creating a self-signed certificate.”
v To request and receive a CA signed certificate, see “Requesting a CA signed
certificate” and “Receiving a CA signed certificate.”
3. Update the web container properties. For information see, “Updating the web
container properties.”
4. Update the web browser with the new certificate. For information see,
“Updating the web browser with the new certificate.”
5. If you make any changes to the key store or trust store files by using any
application other than IBM Systems Director, you must restart IBM Systems
Director. If you use IBM Systems Director to make the changes, then IBM
Systems Director does not need to be restarted.
Related tasks:
Configuring Web browsers to use JWS
Deleting the default certificate:
IBM Systems Director Server provides, by default, a Secure Sockets Layer (SSL)
certificate that supports HTTPS connections between IBM Systems Director Server
and the Web browser client. You must delete this default certificate before you can
replace it with either a self-signed certificate or a CA signed certificate. Also, you
must change the keystore password.
Note:
v Back up any files before you edit them.
v In addition to this procedure, you can delete the default certificate by using the
rmcert -a lwiks command. For more information, see "rmcert command".
To delete the default certificate, complete the following steps:

1. Stop IBM Systems Director Server by completing the applicable steps:

Option Description
For Linux Type the following command: smstop
For Windows 1. Right-click My Computer and select
Manage.
2. In the Computer Management window,
expand Services and Applications >
Services.
3. In the Services pane, right-click IBM
Systems Director Server and select Stop.
4. Exit from the Computer Management
window.
2. Start the IBM Key Management program by typing the applicable command.
Option Description
For Linux install_root/jre/bin/ikeyman
For Windows install_root\jre\bin\ikeyman.exe
where install_root is the root directory of your IBM Systems Director

installation. Note that this path uses the backslash (\) to delimit the directory;
depending on the system that you are using, you might be required to enter
the path using the forward slash (/).
3. To open the default keystore file, click Key Database File > Open.
4. In the Key database type list, select JKS.
5. Click Browse and navigate to the applicable default keystore file:
Option Description
For Linux install_root/data/security/keystore/
ibmjsse2.jks
For Windows install_root\data\security\keystore\
ibmjsse2.jks

6. Select the default keystore file and click Open; then, click OK.
7. In the Password Prompt window, specify the default password for the default
keystore file and click OK. The default keystore file password for IBM Systems
Director is ibmpassw0rd.
8. In the Key database content pane, select the default personal certificate named
lwiks and click Delete.
9. If you make any changes to the key store or trust store files using any
application other than IBM Systems Director, you will need to restart IBM
Systems Director. If you use IBM Systems Director to make the changes, then
IBM Systems Director does not need to be restarted.
Next, you must create a new certificate.

v If you want to create a self-signed certificate, go to “Creating a self-signed
certificate.”
v If you want to request a CA signed certificate, see “Requesting a CA signed
certificate.”

Related tasks:
Creating a self-signed certificate
Requesting a CA signed certificate
rmcert command
Creating a self-signed certificate:
Self-signed certificates are certificates that you create yourself for private use. After
you create a self-signed certificate, you can use it immediately. Because anyone can
create self-signed certificates, they are not considered publicly trusted certificates.
Therefore, use self-signed certificates only on a temporary basis while you test
your environment. You can replace the default certificate with a self-signed
certificate.
Before you complete this procedure, you must delete the default certificate. For
information see “Deleting the default certificate.”
Notes:
1. Back up any files before you edit them.
2. Messages and settings might differ depending on your Web browser and the
version of Java Web Start that you are running.
3. Instead of the steps 10-12 to change the keystore password, you can also use
the cfgappcred command. See "cfgappcred command."
Important: If you want to request a CA signed certificate, do not perform this

procedure. Instead, see “Requesting a CA signed certificate.”
To create a self-signed certificate, complete the following steps:

1. In the IBM Key Management program, click Create > New Self-Signed
Certificate.
2. In the Create New Self-Signed Certificate window, in the Key Label field,
specify a label for the new certificate, for example, DirServer.
3. In the Version list, select X509 V3.
4. In the Key Size field, accept the default value.
5. In the Common Name field, specify the fully-qualified host name of the
server for which you are creating the certificate.
Note: This host name must match the host name that appears in the URL you
specify in your Web browser to reach IBM Systems Director Server. In most
cases, you must specify the fully-qualified host name. However, if you use a
short name in your URL, you must specify a short name for the Common
Name.
6. In the Organization field, type the name of your organization.
7. In the Country or region list, accept the default value.
8. In the Validity Period field, specify the lifetime of the certificate in days or
accept the default value.
9. Click OK.
10. To change the default keystore file password, click Key Database File >
Change Password.
11. In the Change Password window, specify and confirm a new password and
click OK.
12. To exit the IBM Key Management program, click Key Database File > Exit.

Next, you must update the Web container properties. Go to “Updating the Web
Related tasks:
Deleting the default certificate
Updating the Web container properties
cfgappcred command
Requesting a CA signed certificate:
You can request a digital certificate from a certificate authority (CA). Because
certificate authorities are public entities that issue certificates to identify other
entities, CA signed certificates provide a level of public trust. Therefore, this type
of certificate is better suited for your production environment.
Before you complete this procedure, you must delete the default certificate. For
information see “Deleting the default certificate.”
Important: If you are creating a self-signed certificate, do not perform this

procedure.
You must create a certificate-signing request (CSR) to request a digital certificate

from a CA. To create a certificate-signing request, complete the following steps:
1. In the IBM Key Management program, click Create > New Certificate Request.
2. In the Create New Key and Certificate Request window, in the Key Label field,
type a label for the new certificate, for example, DirServer.
3. In the Key Size field, accept the default value.
4. In the Common Name field, specify the fully-qualified host name of the server
for which you are creating the certificate.
Note: This host name must match the host name that appears in the URL you
specify in your Web browser to reach IBM Systems Director Server. In most
cases, you must specify the fully-qualified host name. However, if you use a
short name in your URL, you must specify a short name for the Common
Name.
5. In the Organization field, type the name of your organization.
6. In the Country or region list, accept the default value.
7. In the Enter the name of a file in which to store the certificate request field,
type a file name or click Browse to select a file in which to store the certificate
request, for example, DirServerSecPubCertreq.arm.
8. Click OK.
9. Send the certificate-signing request file to the CA. See the CA Web site for
specific instructions about requesting a new certificate. You can request either a
test certificate or a production certificate from the CA. However, in a
production environment, you must request a production certificate.
Next, you must receive the CA signed certificate. Go to “Receiving a CA signed

certificate.”

Related tasks:
Deleting the default certificate
Receiving a CA signed certificate
Receiving a CA signed certificate:
After the certificate authority (CA) accepts the certificate-signing request, the CA
processes the request and verifies your identity. The CA sends the signed certificate
back to you by way of e-mail. You must receive and save the new certificate in the
default keystore file.
Before you complete this procedure, you must create and submit a
certificate-signing request. For information see “Requesting a CA signed
certificate.”
Notes:
1. Back up any files before you edit them.
2. Instead of the following steps, you can also use the importcert and cfgappcred
commands. For more information, see "importcert command" and "cfgappcred
command."
3. Messages and settings might differ depending on your Web browser and the
4. This procedure documents how to receive a signed certificate with a file
extension of .arm from a CA into the IBM Key Management program. If your
certificate has a different file extension, see the IKeyMan User's Guide. Go to the
IBM Support and Download Web site at www.ibm.com/support/us and search
using the document number SC23-6510-00.
Important: If you are creating a self-signed certificate, do not perform this

procedure.
To receive a CA signed certificate, complete the following steps:

1. If the CA sends the new certificate to you as part of an e-mail message, you
must cut and paste the certificate from the e-mail message and save it in a
certificate file, for example, DirServerSecPubCert.arm.
Note: The e-mail message from the CA might include supplemental text in
front of the certificate and after the certificate. For example, you might see the
text BEGIN CERTIFICATE in front of the certificate and END CERTIFICATE after
the certificate. In this case, make sure that you cut and paste the supplemental
text along with the certificate text.
2. Save the certificate file in the applicable directory:
Option Description
For Linux install_root/data/security/keystore
For Windows install_root\data\security\keystore

3. Start the IBM Key Management program by typing the applicable command.

Option Description
For Linux install_root/jre/bin/ikeyman
For Windows install_root\jre\bin\ikeyman.exe

4. To open the default keystore file, click Key Database File > Open.
5. In the Key database type list, select JKS.
6. Click Browse and navigate to the applicable default keystore file:
Option Description
For Linux install_root/data/security/keystore/
ibmjsse2.jks
For Windows install_root\data\security\keystore\
ibmjsse2.jks

7. Select the default keystore file and click Open; then, click OK.
8. In the Password Prompt window, specify the default password for the default
keystore file and click OK. The default keystore file password for IBM
Systems Director is ibmpassw0rd.
9. In the Key database content pane, select Personal Certificates from the list.
10. Click Receive.
11. In the Receive Certificate from a File window, in the Data type list, select
Base64-encoded ASCII data.
12. In the Certificate file name field, specify the name of the certificate file that
you created when you received the certificate from the CA, for example,
DirServerSecPubCert.arm.
13. In the Location field, specify the applicable directory path:
Option Description
For Linux install_root/data/security/keystore
For Windows install_root\data\security\keystore

14. Click OK.
15. In the Enter a Label window, specify a label for the certificate, for example,
DirServerSec.
16. Click OK.
17. Optional: Add the public version of the CA signed certificate to the Web
browser's truststore file.
The public version of the certificate contains all identifying information as
well as the public key associated with the certificate. This optional step can
provide additional security within your SSL configuration. The Web browser

can determine whether the server presents a certificate that is signed by a
trusted signer. If the browser determines that the certificate is not signed by a
trusted signer, the browser displays a warning which alerts you to a possible
security breach. Configuring SSL for the browser is browser-specific. See your
browser documentation for instructions.
18. To change the default keystore file password, click Key Database File >
Change Password.
19. In the Change Password window, specify and confirm a new password and
click OK.
20. To exit the IBM Key Management program, click Key Database File > Exit.
Next, you must update the Web container properties. Go to “Updating the Web
Related tasks:
Updating the Web container properties:
Because you changed the keystore or truststore password, you must update the
Web container properties with the new keystore or truststore password.
Before you perform this procedure, you must create a new certificate. You can
create either a self-signed certificate or request and receive a CA-signed certificate:
v To create a self-signed certificate, see “Creating a self-signed certificate.”
v To request and receive a CA signed certificate, see “Requesting a CA signed
certificate” and “Receiving a CA signed certificate.”
To update the Web container properties, you do not edit properties directly within
the webcontainer.properties file. Instead, you must create a file named sslconfig in
the same directory, edit the properties in the sslconfig file, and restart IBM Systems
Director Server. The process of restarting IBM Systems Director Server encrypts the
new password in the Web container properties.
Notes:
v Back up any files before you edit them.
v Messages and settings might differ depending on your Web browser and the
To update the Web container properties for a new keystore or truststore, complete
the following steps:
1. Stop IBM Systems Director Server.
2. Change to the applicable directory:
Option Description
For Linux install_root/lwi/conf
For Windows install_root\lwi\conf
where install_root is the root directory of your IBM Systems Director Server
installation.
3. Change the name of the webcontainer.properties file to
webcontainer.properties.bak.

4. In the same directory, create a file named sslconfig and copy the contents of
webcontainer.properties.bak into the sslconfig file.
5. Using a text editor, edit the sslconfig file.
Note: Specify only plain text values for the passwords in the sslconfig file.
6. Specify the new keystore or truststore password with the following text in the
sslconfig file:
keystore
com.ibm.ssl.keyStorePassword.secure_port=new_password
truststore
com.ibm.ssl.trustStorePassword.secure_port=new_password
Where
v secure_port is the secure port that IBM Systems Director Server uses. Use
the secure port value indicated in your properties file.
v new_password is the password that you set in one of the following steps:
– Step 11 on page 110 in “Creating a self-signed certificate”
– Step 19 on page 114 in “Receiving a CA-signed certificate”
7. Delete the line sslEnabled=true from the sslconfig file.
8. Save the sslconfig file.
Important: Ensure the sslconfig file is created without the .txt extension. If the
file is created with the .txt extension, remove it. Otherwise, the IBM Systems
Director Server will not start.
9. Restart IBM Systems Director Server by completing the applicable steps.
Option Description
For Linux Type the following command: smstart
For Windows 1. Right-click My Computer and select
Manage.
2. In the Computer Management window,
expand Services and Applications >
Services.
3. In the Services pane, right-click IBM
Director Server and select Start.
4. Exit from the Computer Management
window.
When you restart IBM Systems Director Server, the sslconfig file is used to
automatically create a new webcontainer.properties file and encrypt the new
password in this file. After the new webcontainer.properties file has been
created, IBM Systems Director Server deletes the sslconfig file because it is no
longer needed.
10. After you start and connect to IBM Systems Director Server, you can delete
the webcontainer.properties.bak file manually.
11. If you are using LDAP over SSL, then you must modify the keystore or trust
store password:
v If you used the cfguserreg command to configure LDAP, then you must
modify the keystore or trust store password using cfguserreg.

v If you modified the securityLDAP.properties file to configure LDAP, then
you must modify the keystore or trust store password in that file. See
Authenticating IBM Systems Director users stored in LDAP for more
information.
Next, you must update the Web browser with the new certificate. Go to “Updating
the Web browser with the new certificate.”
Related tasks:
Creating a self-signed certificate
Receiving a CA signed certificate
Updating the Web browser with the new certificate
cfgappcred command
Updating the Web browser with the new certificate:
You must update your Web browser with the new certificate.
Before you perform this procedure, you must update the Web container properties.
For information see “Updating the Web container properties.”
To update the Web browser with the new self-signed certificate, complete the
following steps.
Note: If you performed step 17 on page 113 in “Receiving a CA signed certificate”

or if the public version of the CA signed certificate is already stored in the browser
truststore file, go to step 11 on page 117. Some browsers contain the public version
of well known CA signed certificates.
1. In a Web browser, type the following URL to point to IBM Systems Director
Server: http://server_name:port_number/ibm/console, where server_name is
the host name of IBM Systems Director Server and port_number is the port for
IBM Systems Director Server. The default port is 8421.
Option Description
For Microsoft Internet Explorer A Security Alert window is displayed, for
example, you might see the following
message: The security certificate was
issued by a company you have not chosen
to trust. View the certificate to
determine whether you want to trust the
certifying authority. Continue to step 2.
For Firefox A Website Certified by an Unknown
Authority window is displayed. Click
Accept this certificate permanently and
then click OK. You Web browser is updated
with the new certificate.
2. In the Security Alert window, click View Certificate.

3. In the Certificate window, click Install Certificate.
4. In the Certificate Import Wizard, on the Welcome page, click Next.
5. On the Certificate Store page, select the way that you want to store the
certificate and click Next.
6. On the Summary page, click Finish. A Security Warning window is displayed.

7. In the Security Warning window, click Yes.
8. In the Certificate Import Wizard window, click OK.
9. In the Certificate window, click OK.
10. In the Security Alert window, click Yes.
11. When you use a launched task in the IBM Systems Director Web interface, the
following message is displayed: The application's digital signature has
been verified. Do you want to run the application? Be sure to select
Always trust content from this publisher and click Yes.
Related tasks:
Using External Application Launch

Use External Application Launch to integrate third-party management software
and other programs into the IBM Systems Director Web interface user interface.
Before you can start an external application from IBM Systems Director Web
interface, you must configure the external application so that it is recognized by
To integrate an external application into IBM Systems Director, complete the

following steps:
1. Define the external-application task by creating a command-task file. For
information see “Creating a command-task file.”
2. Optional: Specify a national-language task title for the command-task file. For
information see “Specifying national-language task titles.”
3. Copy the command-task file and any resource-bundle files to the management
server (where IBM Systems Director Server is installed) in the
install_root/classes/extensions directory.
4. If you intend to integrate the external applications into an instance of IBM
Systems Director Web interface that is not running on the management server,
configure the remote IBM Systems Director Web interface for
external-application tasks. For more information, see “Configuring
external-application tasks for browser systems.”
5. Refresh the external applications. For more information, see “Refreshing
external-application tasks in the IBM Systems Director Web interface.”
6. Select and start an external application. For more information, see “Starting
external-application tasks in the IBM Systems Director Web interface.”
You can restrict the use of the external-application task to specific users. For more
information, see “Authorizing users to IBM Systems Director.”
Related tasks:
Authorizing users
Finding a task
External-application tasks
External-application tasks are user-defined tasks that are displayed in the IBM
Systems Director Web interface. They can start a command, process, or application
that is external to IBM Systems Director and runs on the browser system or
management server.
External-application tasks are defined in IBM Systems Director using a

combination of Java resources including command-task files and Java resource
bundles that you create. These resources specify the application to be started, the

task title, and the way that the task is started in the IBM Systems Director Web
interface. External Application Launch tasks also have resources for each supported
language defined in the command-task file.
External-application tasks can be targeted, untargeted, or both.
Targeted and untargeted tasks:
All IBM Systems Director tasks (including native IBM Systems Director tasks, tasks
added by installing plug-ins, and external application tasks) are either targeted,
untargeted, or both, depending on how the task can be started.
Targeted tasks
Targeted tasks are tasks for which a resource is specified when the task is
started. Targeted tasks are started by right-clicking a resource and selecting
the task. Typically, a targeted task performs an action on the resource
specified as the target. Examples of targeted tasks are Remote Session and
SNMP Browser.
When an external application is started as a targeted task, information
about the specified target is provided. If one or more system attribute
names are configured, the available values for each target are passed to the
application using environment variables. If no system attributes are
configured, the IP address, MAC address, and computer name are passed
to the application by way of environment variables.
Untargeted tasks
Untargeted tasks are tasks for which no resource is specified when the task
is started. Untargeted tasks are started in the following ways:
v By selecting the task in the IBM Systems Director Web interface
navigation pane
v By selecting the task from the Actions menu or pop-up menu
Untargeted tasks perform actions that are not specific to a targeted
resource, perform actions that apply to all resources, or provide their own
interface for selecting resources on which to perform actions.
Tasks that are both targeted and untargeted
A task can be both a targeted task and an untargeted task, with behavior
reflecting the manner in which the task is started. The Inventory task is an
example of such a task: if started from a resource’s pop-up menu, it
displays information for that resource only; if started from the IBM
Systems Director Web interface navigation pane, it displays information for
all resources.
Related reference:
Command-task file location and naming conventions
Command-task file parameters
Considerations for command-string parameters
Environment variables
Managed-resource types
Sample command-task files
Command-task file location and naming conventions:
All command-task files must meet specific file-location and naming-convention

requirements.

v Command-task files must reside on the management server in the
classes/extensions directory, under the directory in which IBM Systems Director
Server is installed. Command-task files that are not in this directory are ignored.
v Command-task file names must end with the .CMDExt extension, which is not
case-sensitive.
v The file name and extension are not case sensitive.
v Do not use underscores in file names. IBM Systems Director uses the file name
to sort the external-application tasks in the IBM Systems Director Web interface.
The sort function replaces spaces in the file name with underscores. File names
that are identical with the only variant being spaces and underscores are
considered duplicates, and only one will be displayed as an external-application
task in the IBM Systems Director Web interface.
Related concepts:
Targeted and untargeted tasks
Related reference:
Command-task file parameters:
The Command-task parameters table lists the parameters that can be specified in a
command-task file. Parameters are listed here in alphabetical order.
Important: Consider the following information when working with command-task

file parameters:
v Both parameter names and values are case sensitive.
v Each parameter must be defined on a separate line.
v If the same parameter is specified more than once, the last parameter value in
the file is used by IBM Systems Director.
v If a command-task file includes parameters that are no longer supported, the
affected parameters are ignored.
v You must use ISO 8859-1 character encoding when editing the command-task
file. Characters that cannot be represented directly in the ISO 8859-1 character
set can be specified with valid ISO 8859-1 Unicode-escape sequences.
v Command-task files use Java-properties-file formatting; therefore, any backslash
(\) or forward slash (/) character must be coded as a double backslash (\\) or
forward slash (//) (for example, dir c:\\tmp\\backup1 /s).
v Environment-variable values must have only one backslash or forward slash.
v Windows-based systems use backslashes (\) to delimit directories in a directory
path. AIX-based systems and Web addresses use forward slashes (/) as
delimiters. This information uses backslashes (\) to delimit directories in paths
that apply to all operating systems; depending on the system that you are using,
you might have to enter the directory path differently than shown.
v No error-checking is performed on command-task files, so you must be careful
when editing them. Parameter names that do not exactly match expected
parameters are ignored.
v For information about setting a task title using a national-language string, see
“Specifying national-language task titles.”

Table 4. Command-task parameters
Parameter name Description Allowed values
CheckFileExistsNow.Unix The attribute that shows or hides the Possible values are:
CheckFileExistsNow.Windows external-application task in the IBM true If the file specified
Systems Director Web interface based on by the FileExists
the result of the applicable FileExists parameter exists on
parameter (FileExists.Windows or the browser
FileExists.Unix). system, then IBM
Systems Director
Web interface
displays the task. If
the file does not
exist, then IBM
Systems Director
Web interface hides
the task.
false IBM Systems
Director Web
interface always
displays the task.
Client.x.Resource The fully qualified Java class name of a A valid resource name for a
valid target type for the managed-resource type in
external-application task. The target type IBM Systems Director. For
identifies the type of resources for which the list of managed-resource
the external-application task can be types, see
targeted. “Managed-resource types
Important: To use this parameter, you for the Client.x.Resource
must set the Targeted parameter to a valid parameter.”
value other than none; one, multi,
none|one, and none|multi are valid values.
To define multiple targets, replace x with a

unique non-negative integer for each target
class. For example, the following two lines
specify that the external-application task
can use either a physical platform or a
logical platform as a target:
Client.0.Resource=OperatingSystem
Client.1.Resource=Server

Table 4. Command-task parameters (continued)
CommandString The command string to be run on a UNIX, A valid command line for
CommandString.Linux Linux, VMware, or Windows (including an external application
CommandString.Unix Windows 2003, Windows XP, and Windows running on a browser
CommandString.VMware Vista) browser system. system.
CommandString.Windows Note:
CommandString.Windows2003 v You can specify both
CommandString.WindowsXP CommandString.Server and
CommandString.WindowsVista CommandString parameters if you want
to specify a browser system and
management server synchronized task in
which both a noninteractive task and an
interactive task are launched at the same
time.
v If you specify more than one
CommandString parameters that apply
to the same operating system, IBM
Systems Director uses the most specific
parameter. For example, if you specify
CommandString.Windows and
CommandString.Windows2003
parameters, IBM Systems Director uses
the CommandString.Windows2003
parameter.
CommandString.Server The command string to be run on a UNIX, A valid command line for
CommandString.Server.Linux Linux, VMware, or Windows (including an external application on a
CommandString.Server.Unix Windows 2003, Windows XP, and Windows management server.
CommandString.Server.VMware Vista) management server.
CommandString.Server.Windows Note:
CommandString.Server.Windows2003 v You can specify both
CommandString.Server.WindowsXP CommandString.Server and
CommandString.Server.WindowsVista CommandString parameters if you want
to specify a browser system and
management server synchronized task in
which both a noninteractive task and an
interactive task are launched at the same
time.
v If you specify more than one
CommandString.Server parameters that
apply to the same operating system, IBM
Systems Director uses the most specific
parameter. For example, if you specify
CommandString.Server.Windows and
CommandString.Server.Windows2003
parameters, IBM Systems Director uses
the CommandString.Server.Windows2003
parameter.

Cwd The path name of the directory on a UNIX, A valid directory on the
Cwd.Linux Linux, VMware, or Windows (including browser system.
Cwd.Unix Windows 2003, Windows XP, and Windows
Cwd.VMware Vista) browser system from which the
Cwd.Windows external-application task must be started.
Cwd.Windows2003 Specify this parameter only if the
Cwd.WindowsXP command needs to start in a specific
Cwd.WindowsVista directory.
Note: If you specify more than one Cwd
parameters that apply to the same
operating system, IBM Systems Director
uses the most specific parameter. For
example, if you specify Cwd.Windows and
Cwd.Windows2003 parameters, IBM
Systems Director uses the
Cwd.Windows2003 parameter.
Cwd.Server The path name of the directory on a UNIX, A valid directory on the
Cwd.Server.Linux Linux, VMware or Windows (including management server.
Cwd.Server.Unix Windows 2003, Windows XP, and Windows
Cwd.Server.VMware Vista) management server from which the
Cwd.Server.Windows external-application task must be started.
Cwd.Server.Windows2003 Specify this parameter only if the
Cwd.Server.WindowsXP command needs to start in a specific
Cwd.Server.WindowsVista directory.
Note: If you specify more than one
Cwd.Server parameters that apply to the
same operating system, IBM Systems
Director uses the most specific parameter.
For example, if you specify
Cwd.Server.Windows and
Cwd.Server.Windows2003 parameters, IBM
Cwd.Server.Windows2003 parameter.
FileExists Specify a qualified path or name for a file The path and name of an
FileExists.Windows that must exist on the browser system existing file on the browser
FileExists.Unix before launching the task. If IBM Systems system.
Director does not find the specified file, a
message is displayed and the external
application does not launch.
If you do not specify a directory in the

FileExists parameter, the default path is
temp/.ibm/lic where temp is the
operating-system-specific temp directory
on the browser system.

ShellRequired A flag that indicates whether you want to Specify one of the following
start a persistent shell on the management values:
console in which to start the external
true Start the
application. Set this parameter if the
external-application
application requires an interactive window
task in a persistent
or advanced command-line syntax, such as
shell.
wildcard expansion.
false Do not start the
The shell is started using one of the external-application
following commands: task in a persistent
Windows shell. This is the
start cmd.exe /k default value.
.
UNIX or Linux
bash –c
If this parameter is omitted or set to false,
the command string is issued without
starting a persistent shell. If this parameter
is set to true, any command output to the
shell is displayed in a command window
that you can scroll and later close.
ShellRequired.Server A flag that indicates whether you want to Specify one of the following
start a persistent shell on a managed values:
system in which to start the external
true Start the
application. Set this parameter if the
external-application
application requires an interactive window
task in a persistent
or advanced command-line syntax, such as
shell.
wildcard expansion.
false Do not start the
The shell is started using one of the external-application
following commands: task in a persistent
Windows shell. This is the
start cmd.exe /k default value.
UNIX or Linux
bash –c
If this parameter is omitted or set to false,
the command string is issued without
starting a persistent shell. If this parameter
is set to true, any command output to the
shell is displayed in a command window
that you can scroll and later close.

System.Property.x A requested system property (as defined in A system property
the managed resource) that is specified for associated with one of the
each managed resource property required Client.x.Resource target
by the command. Each property is passed types.
as an environment variable at launch time,
for each targeted system chosen. Each
property is assigned a unique environment
variable name, and these environment
variable names can be used in the
CommandString or can be accessed by a
script launching the application. For
example, to pass the computer name of the
targeted system, set the parameter to:
System.Property.x=Name
where x is the index number assigned to

the system property.

Table 5. Command-task parameters, cont.
Targeted A flag that specifies whether the Specify one of the following values:
external-application task can be
none An untargeted task. The task
started as a targeted task, an
can be opened by selecting it
untargeted task, or both. If this
in the IBM Systems Director
parameter is omitted, the value is set
Web interface navigation
to one.
pane, from the Actions
menu, or from the pop-up
menu.
one A targeted task. The task can
be started by selecting a
target system and
right-clicking the task. This
is the default value.
none|one
Tasks that are both targeted
and untargeted. The task can
be opened by selecting it in
the IBM Systems Director
menu, from the pop-up
menu, or can be started by
selecting a target system and
multi A targeted task. The task can
be started by selecting a
target system and
none|multi
Tasks that are both targeted
and untargeted. The task can
be opened by selecting it in
the IBM Systems Director
menu, from the pop-up
menu, or can be started by
selecting a target system and

Related concepts:
Related tasks:
Specifying national-language task titles
Related reference:
Considerations for command-string parameters:
When using command strings in command-task files, there are specific

considerations that you must review.
v Testing the command strings from a command line to ensure that they run
successfully outside of the command-task file can reduce debugging efforts. It is
your responsibility to ensure that the environment is properly configured for the
desired behavior. For example, if the application requires an interactive window
or advanced command-line syntax (such as wildcard expansion), you must set
the ShellRequired parameter. For information about the ShellRequired parameter,
see “Command-task file parameters.”
v Only a single command can be specified for the CommandString value. Do not
chain any commands or use pipes or redirection. You can, however, define a
shell script or batch file on the browser system. For information about the
CommandString parameter, see “Command-task file parameters.”
Note: Only some commands will accept parameters at invocation as they are
seen by the server as two separate commands. This is a limitation of the
operating system or application.
v When the external-application task is defined on the management server (the
system running IBM Systems Director Server), the task title is displayed on all
instances of the IBM Systems Director Web interface. To start the application
successfully, the necessary applications, files, and any resources that are required
by the application must reside on the browser system from which you want to
start the task.
v For information about passing target attributes to the external application, see
“Environment variables for external-application tasks.” When using the
CMDTASK_IP_ADDRESSn and CMDTASK_MAC_ADDRESSn environment variables in a
command string, always remember to append a number at the end of the
variable name to specify which TCP/IP address or MAC address will be
returned.
v Because command-task files are Java properties files, the backslash (\) must be
represented by a double backslash, as in dir c:\\*exe /s.
v An interactive task runs on the local system (the system from which you are
activating it). To create an interactive task that runs on the management server
or browser system, you must specify both a CommandString parameter and a
CommandString.Server parameter. Use environment variables to pass system
attributes to the external application.
v A noninteractive task runs on the system on which IBM Systems Director Server
is installed. To create a noninteractive task, you must specify a
CommandString.Server parameter. Use environment variables to pass system

attributes to the external application. If the task requires that system attributes
be passed in the environment, ensure that the system attributes are named
correctly.
Note: These tasks must not invoke IBM Systems Director commands.
v A console/server synchronized task runs an interactive task and a noninteractive
task. You would create a synchronized task when an interactive task depends on
a noninteractive task running simultaneously in order to function. The
noninteractive task is started first. The interactive task is started after a
successful launch of the noninteractive task. Because both tasks are required to
provide function to a user, they are considered to be one console/server task.
To create a console/server synchronized task, specify both a
CommandString.Server parameter and a CommandString parameter. The
CommandString.Server value is launched as a noninteractive task (on the
management server) and its CommandString counterpart is launched as an
interactive task (on the browser system). Use environment variables to pass
system attributes to the external applications.
v To create a group heading to serve as a parent for group of related
external-application tasks in IBM Systems Director Web interface, create an
interactive task without a CommandString or CommandString.Server parameter.
Related concepts:
Related reference:
Environment variables for external-application tasks:
When an external-application task is started against a target, IBM Systems Director

passes system-property information about the selected target to the external
application by setting the values of environment variables on the browser system.
Note: You are responsible for ensuring the validity and functionality of your
environment variables.
To pass system-property values when starting an external application, the

external-application task must be targeted (that is, it must have at least one
Client.x.Resource parameter specified). The system properties that are available
depend on the target type (Client.x.Resource object). Each target type provides a
set of system properties, each of which has a key and a value. If you specify more
than one target type, the list of available system properties is the union of all
available system properties for those target types. Some system properties (such as
computer name) are available for all target types. For information about the
Client.x.Resource or System.Property parameter, see “Command-task file
parameters.”
Tip: Only specify the environment variables that are necessary to start the external
application. This is especially true if the external-application task targets multiple
resources.

You can access the value associated with a system property using the echo
command. The following table provides an example.
Table 6. Examples of using the echo command
Operating system Command example
Linux echo $CMDTASK_IPV4ADDRESS0_0
Windows echo %CMDTASK_IPV4ADDRESS0_0%
The following table lists system properties. Note that this might not be a complete
list.
Table 7. System properties
System property Environment variable name
AgentDate CMDTASK_AGENTDATE_x
AgentType CMDTASK_AGENTTYPE_x
AgentVer CMDTASK_AGENTVER_x
Architecture CMDTASK_ARCHITECTURE_x
ComputerName CMDTASK_COMPUTERNAME_x
CurrentTimeZone CMDTASK_CURRENTTIMEZONE_x
DisplayName CMDTASK_DISPLAYNAME_x
EncryptionEnabled CMDTASK_ENCRYPTIONENABLED_x
EndpointType CMDTASK_ENDPOINTTYPE_x
HasLicense CMDTASK_HASLICENSE_x
ImageSet CMDTASK_IMAGESET_x
IPHosts CMDTASK_IPHOSTv_x
IPv4Address CMDTASK_IPV4ADDRESSv_x
IPXaddress CMDTASK_IPXADDRESSv_x
Locked CMDTASK_LOCKED_x
LPARID CMDTASK_LPARID_x
MACAddress CMDTASK_MACADDRESSv_x
MachineTypeModel CMDTASK_MACHINETYPEMODEL_x
Manufacturer CMDTASK_MANUFACTURER_x
OperatingSystem CMDTASK_OPERATINGSYSTEM_x
OSArchType CMDTASK_OSARCHTYPE_x
OSMajVer CMDTASK_OSMAJVER_x
OSMinVer CMDTASK_OSMINVER_x
Ping CMDTASK_PING_x
Protocols CMDTASK_PROTOCOLSv_x
SecuredClient CMDTASK_SECUREDCLIENT_x
SecureSupport CMDTASK_SECURESUPPORT_x
SerialNumber CMDTASK_SERIALNUMBER_x
SSHFingerprint CMDTASK_SSHFINGERPRINT_x
SSHPort CMDTASK_SSHPORT_x
SSHVersion CMDTASK_SSHVERSION_x

Table 7. System properties (continued)
System property Environment variable name
Task CMDTASK_TASKv_x
URL CMDTASK_URL_x
WBEMPort CMDTASK_WBEMPORT_x
Related concepts:
Related reference:
Managed-resource types for the Client.x.Resource parameter:
Managed-resource types are used to specify targets for the external application task
with the Client.x.Resource parameter. For information about this parameter, see
“Command-task file parameters.”
Valid managed-resource types include those listed in Table 8.
Note: The information provided in this table is for reference only, and might not
include third-party managed-resource types or resource types supported in future
versions of IBM Systems Director.
Table 8. IBM Systems Director resources and managed-resource types
Managed-resource type Resource
OperatingSystem com.tivoli.twg.engine.TWGNativeManagedObject
com.tivoli.twg.tier.TieredManagedObject
SystemChassis com.ibm.sysmgt.chassis.bcchassis.BCChassisManagedObject
Server com.ibm.sysmgt.platform.LogicalPlatform
com.ibm.sysmgt.platform.PhysicalPlatform
com.ibm.sysmgt.platform.Platform
com.ibm.sysmgt.spm.server.partition.Partition
Chassis com.ibm.sysmgt.spm.server.rioe.RIOEnclosure
GenericNetworkDevice com.tivoli.twg.rmon.TWGRMONDevice
com.tivoli.twg.snmp.TWGSNMPDevice
Cluster com.ibm.sysmgt.spm.server.complex.Complex
Switch com.tivoli.twg.snmp.TWGSNMPDevice
PassThroughModule com.tivoli.twg.snmp.TWGSNMPDevice
Printer com.tivoli.twg.snmp.printer.SNMPPrinter
StorageSubsystem com.ibm.sysmgt.storage.StorageManagedObject

Related concepts:
Related reference:
Sample command-task files:
The sample command-task files are provided to assist advanced users and vendors
who want to create command-task files.
Telnet to managed system (Telnet.CMDExt)
This example shows a command task to open a Telnet session and hold the
window open while a user types the user ID and password. With the –hold option,
you also receive an error message if the Telnet command is not performed
successfully.
# Parameters for all operating systems:
Targeted=one
ShellRequired=true
# Parameters for UNIX and Linux:

CommandString.Unix = xterm –hold –e telnet $CMDTASK_IP_ADDRESS0
# -hold gives you an error message if telnet fails
# Parameters for Windows:

CommandString.Windows = telnet %CMDTASK_IP_ADDRESS0%
Map a managed system to a Windows network drive (NetUse.CMDExt)
This example shows a command task to create a Windows network-drive

connection to the targeted system using the next available drive letter.
Targeted=one
ShellRequired=false
# Parameters for UNIX or Linux:

CommandString.Unix =
# Empty command string specified; no action occurs
# Parameters for Windows:

CommandString.Windows = net use * \\\\%CMDTASK_COMPUTERNAME%\\c$ /u:userid pwd
# note: \\ for each \
Launch a noninteractive application (MyServerApp.CMDExt)
This example shows a command task to launch a noninteractive application on the

IBM Systems Director Server and specify both the manufacturer and the machine
type model of the target for the application.
#On Windows:
CommandString.Server.Windows = myServerApp.exe %CMDTASK_MO_MFG_0%
%CMDTASK_MO_MACHINETYPEMODEL_0%

Related concepts:
Related reference:
Creating a command-task file

Command-task files are Java properties files that define external-application tasks for
IBM Systems Director. You can create a command-task file that is used to integrate
third-party management software and other programs with IBM Systems Director.
To create a command-task file, complete the following steps:

1. Create a file with the .CMDExt extension. For information about specifying file
names, see “Command-task file location and naming conventions.”
2. Open the file using a text editor. Each line that you create in this file must be
either a comment beginning with a number sign (#) or a parameter definition
in the form parameter_name=value, for example:
# This line is a comment. The following line sets a parameter for Windows:
CommandString.Windows = telnet %CMDTASK_IPV4ADDRESS0_0%
For information about the parameters that you can use, see “Command-task file
parameters.”
3. Define the task that you want to run using one of the CommandString
parameters or define a group heading. For important considerations about
specifying the command-string parameter, see “Considerations for
command-string parameters.” For information about the CommandString
parameter, see “Command-task file parameters.”
4. Optional: Define other parameters as needed.
5. Save and close the file.
Related concepts:
Related tasks:
Configuring external-application tasks for browser systems
Refreshing external-application tasks
Starting external-application tasks
Deleting external-application tasks

Command-task files can reference Java resource bundles to apply
national-language titles to the external application task. You can create and modify
External Application Launch resource bundles using an editor. It is your
responsibility to ensure the accuracy of Java resource bundles that you create.
National-language task titles are specified by using the Unicode or UTF8 character
set. Characters are typed in the code page in which the user is working.
The IBM Systems Director Web interface supports the code pages listed in the
following table.

Table 9. Code pages supported by the IBM Systems Director Web interface
Language Code page
Brazilian Portuguese 850
English 850
French 850
German 850
Italian 850
Spanish 850
Japanese UTF8
Korean UTF8
Simplified Chinese UTF8
Traditional Chinese UTF8
Because the IBM Systems Director Web interface supports multiple code pages,
users cannot directly type characters in their current code page for all supported
languages. National-language titles for English, French, German, Italian, Brazilian
Portuguese, and Spanish can all be typed directly in code page 850, but to specify
characters in another code page, complete the following steps:
Important: You are responsible for ensuring that the data in the resource bundles
is valid for the intended purpose.
1. Create at least two properties files for resources (one default file and one
English file). For example, if you created a command-task file with the file
name “apple”, create two resource-bundle files named
appleResources.properties and appleResources_en.properties. For each
additional non-English title you must create additional resource bundles for
each locale that you defined. For example, if you provide French and Spanish
titles as well, you must create the appleResources_fr.properties and
appleResources_es.properties files. In the properties file, use the keyword
TitleKey to define the title, and, optionally, DescriptionKey to define a
description of the task. For example:
TitleKey=title
DescriptionKey=description
where title is the translated title of the task and description is a translated string
that describes the task. The description string is displayed in the Description
column on the External Application Launch page.
2. Using the translation services available to you, obtain translations of the title
text in all the languages that you intend to support. Translators will require
code page information if they are contracted to provide translated character
strings.
Note: If your translation service will translate the resource bundles you are
using, no subsequent steps should be necessary.
3. Copy the resource-bundle files to the applicable directory on the management
server.
Table 10. Location of resource-bundle files by operating system
Windows \Program Files\IBM\Director\classes\CmdTask\resources
installation

Table 10. Location of resource-bundle files by operating system (continued)
Linux /opt/IBM/director/classes/CmdTask/resources
installation
where resources represents the directory that contains resource files for a specific
external-application task.

External-application tasks are initially created only on the management server.
Additional preparation is required to start external-application tasks on your
browser system (the system running the IBM Systems Director Web interface)
when the browser system is not the management server.
The following prerequisites apply to this procedure:

v One or more external-application tasks must be created on the management
server.
v The external-application task must be tested to make sure that it starts
successfully on the management server.
To configure the browser system to start an external-application task, complete the

following steps:
v Make sure that the application to be started by the external-application task, as
well as any resources required by the application, is present on the browser
system. If necessary, install the application on the browser system.
v Make sure the path and file name for the application that is installed on the
browser system is the same as the path and file name on the management
server, as specified in the .CMDExt file associated with the external-application
task.
v Make sure that Java Web Start is installed on the browser system.
Related concepts:
Related tasks:
Refreshing external-application tasks in the IBM Systems

Director Web interface
In the IBM Systems Director Web interface, you can refresh the list of available
external-application launch tasks that you can use.
To refresh the list of external-application tasks, complete the following steps:

1. Restart the IBM Systems Director Server to pick up new command definitions.
2. Log back in to the IBM Systems Director Web interface.
3. In the IBM Systems Director Web interface navigation area, expand Task
Management and click External Application Launch.
4. On the External Application Launch page, click Refresh. The list of available
external applications is refreshed.

Related concepts:
Related tasks:
Related reference:
External Application Launch page
Starting external-application tasks in the IBM Systems Director

Web interface
After you integrate an external-application task and it is displayed in the IBM
Systems Director Web interface, you can start the task in the same ways as any
other IBM Systems Director task.
Important:
v When the external-application task is defined on the management server (the
system running IBM Systems Director Server), the task title is displayed on all
instances of the IBM Systems Director Web interface. To start the application
successfully, the necessary applications, files, and any resources that are required
by the application must reside on the browser system from which you want to
start the task.
v When you start an external-application task, the resulting application runs
according to the settings that are present on the system where the application is
started. You can change settings by defining system attributes within the
command-task file. For information about the System.Attribute parameter, see
“Command-task file parameters.”
v You can restrict the use of the external-application task to specific users. For
more information, see “Authorizing users to IBM Systems Director.”
To start an external-application task, use one of the following methods. Depending

on the task type, some methods might not be available.
v Right-click a resource and select the task.
v Select the task from the Actions menu.
v Select the task in the IBM Systems Director Web interface navigation pane.
v In the IBM Systems Director Web interface navigation area, expand Task
Management and click External Application Launch. Then, select and start an
application from the External Application Launch page.

Related concepts:
Related tasks:
Authorizing users
Related reference:
Deleting an external-application task

You can delete an external-application task that is displayed in IBM Systems
Director Web interface.
Attention: The command-task file for the selected external-application task is

permanently deleted on the management server.
To delete an external-application task, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, expand Task
Management and click External Application Launch.
2. On the External Application Launch page, select one or more tasks that you
want to delete.
3. Click Delete. The selected command-task files are deleted on the management
server. They are permanently deleted.
Related concepts:
Related tasks:
Related reference:
Using Advanced External Application Launch

Use Advanced External Application Launch to integrate Web-based third-party
management software and other Web-based programs into the IBM Systems
Before you can launch an external Web-based application from IBM Systems
Director, you must register the external application using a template file. Once
registered, the external application launch points will be visible as either targeted
or untargeted tasks within IBM Systems Director, depending on the launch point

definitions. The vendor instructions, as well as the template file, should provide
more information about the names of the tasks as they will be displayed in IBM
Systems Director.
To integrate an external Web-based application into IBM Systems Director,

complete the following steps.
1. Obtain the external application launch point template file from the vendor
providing the Web-based application.
2. Review the comments section of the template file and follow the vendor
instructions for customizing any information in the template file prior to
registration.
3. Run the following command: importextlps -f <filename>, where <filename>
is the fully qualified path and filename of the template file. If the template file
contains custom tags, use the -c option and specify the appropriate substitution
values.
4. Optional: Run the following command: listextlps -A <applicationID>, to
verify the external application launch points registered successfully (where
<applicationID> is the application ID from the template file).
To remove an external Web-based application registered with IBM Systems

Director, complete the following steps:
1. Run the following command: removeextlps -A <applicationID>, where
<applicationID> is the application ID from the template file.
2. Optional: Run the following command: listextlps -A <applicationID>, to
verify the external application launch points unregistered successfully (where
<applicationID> is the application ID from the template file).
Related tasks:
Finding tasks
Starting tasks
Scheduling tasks
You can use Scheduler (also called the Launch Job window) to schedule
noninteractive tasks to be run at an exact date and time. You can define a schedule
to repeat a task automatically at a given interval, such as every Saturday at 2:00
a.m. You can define a specific number of repeats, such as every Saturday at 2:00
a.m. for the next 6 weeks. Scheduler also provides automatic notification for job
status and task completion.

Related concepts:
eLearning: Scheduling tasks

Related tasks:
Navigating by way of the Welcome page
Managing groups
Related reference:
Tasks and scheduled jobs commands
Noninteractive tasks
Noninteractive tasks, such as inventory collection or system identification, do not
depend on immediate user input and can be scheduled to occur on multiple
systems at any time. Interactive tasks, such as remote control and file transfer,
cannot be scheduled because they directly interact with only one client at a time.
Related concepts:
Jobs and job instances
Related tasks:
Scheduling a task
Scheduling a task from a selected system
Viewing active and scheduled job information
Viewing information about scheduled jobs
Determining target systems that are affected by a job
Viewing job-instance records
Viewing job-instance logs
Copying a scheduled job
Editing a scheduled job
Running a scheduled job immediately
Suspending and resuming a scheduled job
Deleting a job

A scheduled task is called a job.
A job has the following characteristics:

v Noninteractive tasks that are to be run
v Specified dates and times the tasks are to be run
v Target systems on which the scheduled tasks are run
v A history that provides summary details about the job run
v A log that provides step-by-step details about the job run
You also can create jobs without assigning a schedule and manually run the job at
any time.
Because you can run a job more than once, there is a record called a job instance
that represents each execution of the job. For example, you might have a job that is

scheduled for every day at noon. You could view the results for a specific
execution of the job, such as the Tuesday run as opposed to the Monday run, by
viewing the job instance record.
Related concepts:
Related tasks:
Scheduling a task
Deleting a job
Scheduling a task
When you create a job, you can schedule one or more noninteractive tasks to run
on one or more target systems.
To schedule a task, complete the following steps:

1. In the IBM Systems Director navigation area, click Find a Task.
2. On the Find a Task page, right-click a noninteractive task that you want to
schedule and click Run.
If the task is an interactive task, you cannot schedule it and the Launch Job
window will not appear. For information on the difference between interactive
tasks and noninteractive tasks, see “Noninteractive tasks.”
3. The Launch Job window opens and the Target page is displayed. Select one or
more systems or groups of systems on which you want to schedule the task to
run.
Note: If you select a dynamic group, be aware that the group members used
for the scheduled task are those members present in the group when you create
this scheduled job. Subsequent changes in dynamic group membership are
ignored. For example, if you schedule to collect inventory by using a dynamic
group and the group membership changes, the target systems originally part of
the group are used for the inventory collection. The changed group
membership is ignored.
Important:
Although you can select multiple target systems when you create, edit, or copy
the job, the Scheduler does not evaluate the following criteria until the task is
actually run:
v Whether the target systems support the task that you are scheduling
v Whether the task is appropriate for multiple systems

If the scheduled job fails any of these criteria, an error is logged in the job
instance record. Each job instance record provides detailed status information
about the History page and a log file that you can view from the Log page. For
more information, see “Viewing job-instance records” and “Viewing
job-instance logs.”
4. Click the Schedule tab. On this page, you can choose to run the job
immediately or schedule the job to run at a later time.
a. A job name is required and the Name field provides a unique default name.
To change the default name, type a job name in the field.
b. To run the job immediately, click Run Now and go to step 7. Otherwise,
click Schedule.
c. In the Schedule list, select how frequently you want the job to run. The
default setting is Once. Other values are Hourly, Daily, Weekly, Monthly,
Yearly, or Custom. Also, you can specify whether to run the job on the
weekend.
d. Select the date and time to run the job for the first time.
e. Select the time range for the job to repeat.
5. Rarely, a task might require setting additional parameters and the Parameters
page is provided. Click the Parameters tab. If the task provides default values,
they are displayed on this page. If the settings are blank, you must enter all the
settings; otherwise, the Scheduler cannot save the job.
6. Click the Notification tab. On this page you can customize a notification that is
sent by e-mail.
a. Select from the available criteria to customize when the mail notification is
sent. You can specify that the mail be sent when one of the following
criteria is met:
v When the job begins.
v When the job completes successfully.
v When the job fails. You can further customize this criterion by setting
either the percentage of target systems on which the job had errors or the
number of systems on which the job had errors. Therefore, if the job runs
on five systems, the job has errors on two systems, and you set the
criterion threshold to 50%, the notification is not sent.
v When the job receives any error.
b. Type your mail address, mail server, and mail server port.
Tip: You can provide only one mail address.

7. Click the Options tab. On this page you can select additional options for the
job behavior.
a. Select whether you want the job to run according to your management
server's time or the target system's time.
Tip: Make sure that you know the time and time zone to which the
respective systems' clocks are set.
b. Select whether you want the job to fail if a system is offline or if you want
the job to run when the system is online again.
8. Click OK to save the job.
Click Cancel to exit from the Launch Job window without saving the job.
If the job is created successfully, a message is displayed on the page from
which you started the Scheduler. If the job creation fails, a message is displayed
in the Launch Job window so that you can correct the job.

Note: Scheduled jobs retain the locale in which they were created. For example,
if you create a scheduled job in German and then switch to English, the job will
still appear with German titles.
The job is displayed on the Active and Scheduled Jobs page.

Related concepts:
Related tasks:
Deleting a job

When viewing systems, you can select a noninteractive task and schedule it to run
on one or more systems.
To schedule a task from a selected system, complete the following steps:

1. In Resource Explorer or any table that displays systems, select one or more
systems on which you want to perform a noninteractive task.
2. Click Actions and click a noninteractive task that you want to schedule. The
Launch Job window is not displayed if one of the following conditions is true:
v One or more of the selected systems does not support the selected task.
v The task is an interactive task. You cannot schedule an interactive task and
the Launch Job window is not displayed. For more information, see
“Noninteractive tasks.”
3. The Launch Job window opens and the Schedule page is displayed. On this
page, you can choose to run the job immediately or schedule the job to run at a
later time.
b. To run the job immediately, click Run Now and go to step 7 on page 139.
Otherwise, click Schedule.
weekend.
4. Rarely, a task might require setting additional parameters and the Parameters
page is provided. Click the Parameters tab. If the task provides default values,

they are displayed on this page. If the settings are blank, you must enter all the
settings; otherwise, the Scheduler cannot save the job.
sent by e-mail.
criteria is met:

job behavior.
Note: Scheduled jobs retain the locale in which they were created. For example,
if you create a scheduled job in German and then switch to English, the job will
still appear with German titles.
The job is displayed on the Active and Scheduled Jobs page.

Related concepts:
Related tasks:
Scheduling a task
Deleting a job

You can view quick, high-level information about active and scheduled jobs,
including a progress indicator for each job. The progress indicator is useful for
tracking the progress of instances of long-running jobs.
To view information about active and scheduled jobs, complete the following steps:
1. In the IBM Systems Director navigation area, expand Task Management and
click Active and Scheduled Jobs.
2. On the Active and Scheduled Jobs page, scan for the job that you want. For
each job, the following information provided:
Name The name of the job.
Status The current status of the job. The following list describes the available
job states:
Active Indicates that the job has run once and is scheduled to run
again.
Scheduled
Indicates future scheduled runs of the job and the number of
systems affected by the job. This is a job's initial state.
Inactive
Indicates that the job has been disabled and scheduled
instances will not be run. Use this state to prevent a job from
running without deleting the job. Neither the job nor its history
is deleted.
Running
Indicates that the job is currently running and the number of
affected systems. This state can be transitory and, therefore, not
observable for some jobs. If a job is running, you cannot change
its state to Inactive.
Complete
Indicates that no future runs of the job are scheduled, that the
job has run at least once, and the number of affected systems.
Progress
If a job is in the Running state, a progress indicator is displayed in the
column.

Description
A description of when the job is scheduled to run.
Next Run
The date when the job will run next.
Last Run
The date when the job ran most recently.
Task The name of the task that the job runs.
Created By
The user ID of the person that created the job.
Related concepts:
Related tasks:
Scheduling a task
Deleting a job
Related reference:
lsjob command

You can view information (properties) about any job. This information includes
what tasks are included in each job and, if a job has a repeating schedule, when
the job has run before and when it will run next.
To view job information, complete the following steps:

2. On the Active and Scheduled Jobs page, select the job that you want to view
and click Actions > Properties.
3. On the Properties page, the General page is displayed by default. On this page
you can view the following general information about the job:
v The name of the job that was originally given by the user who created the
job.
v The current status of the job.
v A progress indicator that reports the progress of the job if it is running when
you view the job properties.
v The description of when the job run and repeats. You can click on this status
to view the log of the last run.
v The date that the job last ran.
v The date that the job will run next.

v The name of the task that the job runs.
v The name of the job's creator.
4. If you are finished viewing this information, you can return to previous views
using the breadcrumb links at the top of the Properties page.
Also on the Properties page, you can perform applicable tasks on the selected job.
Click Actions to view the available tasks that you can perform.
Related concepts:
Related tasks:
Scheduling a task
Deleting a job
Related reference:
lsjob command

You can view a list of the target systems that are affected by a selected scheduled
job.
To view the target systems, complete the following steps:

3. On the Properties page, click the Target tab. On this page you can view the list
of target systems on which the job will run.
Tip: You also can find this information by selecting a system and viewing its
Properties. On the Properties page, click the Applied Activities page to view
information about any jobs that are associated with the system.

Related concepts:
Related tasks:
Scheduling a task
Deleting a job

You can view a record for each instance of a scheduled job that has already run,
including detailed information about the status of a particular instance.
To view job-instance records, complete the following steps:

3. On the Properties page, click the History tab. On this page you can view the
history of previous times that this job has run. A record is created for each
instance of the job as soon as it starts running. This page provides the
following historical information in each record:
Date Provides the date and time for the record
Status Indicates whether the job instance has completed.
Scheduled
Indicates future scheduled runs of the job and the number of systems
affected by the job. This is a job's initial state.
Inactive
Indicates that the job has been disabled and scheduled instances will
not be run. Use this state to prevent a job from running without
deleting the job. Neither the job nor its history is deleted.
Running
Indicates that the job is currently running and the number of affected
systems. This state can be transitory and, therefore, not observable for
some jobs. If a job is running, you cannot change its state to Inactive.
Complete
Indicates that no future runs of the job are scheduled, that the job has
run at least once, and the number of affected systems.
Failed Indicates that a job instance failed on the specified number or
percentage of systems, and the number of affected systems.
Unavailable
Indicates that a job instance did not run because a target system was
offline and the number of affected systems.

Skipped
Indicates that a job instance did not run because a target system was
offline and the number of affected systems.
Related concepts:
Related tasks:
Scheduling a task
Deleting a job
Related reference:
lsjobhistory command
rmjobhistory command

You can view logs for each job instance that has already run. These logs can
include error messages that you can use to determine why a job instance failed.
To view job-instance logs, complete the following steps:

3. On the Properties page, click the Logs tab. On this page you can view a log for
each record. For each job instance record, the page displays the date and time,
as well as one of the following status:
Running
Indicates that the job instance is currently running. This state might be
transitory and, therefore, not observable for some job instances.
Running with errors
Indicates that the job instance is currently running, but with errors.
This state might be transitory and, therefore, not observable for some
job instances.
Waiting
Indicates that the job instance is waiting for a resource to become
available.

Waiting with errors
Indicates that the job instance is waiting for a resource to become
available, but has already logged some errors.
Complete
Indicates that the job instance has successfully finished its execution.
Errors Indicates that the job instance has finished its execution, but with
errors.
4. Right-click a record and click Show logs. The log is displayed below the table.
If the record state indicates errors, view the log for error messages that can help
you troubleshoot the problem.
Note: You can use the Message Filter dropdown list to limit the type of
messages to display from the selected job log.
Related concepts:
Related tasks:
Scheduling a task
Deleting a job
Related reference:
lsjobhistory command

Copy a job when you want to create a new scheduled job that is similar to a
existing job.
To copy a scheduled job, complete the following steps:

2. On the Active and Scheduled Jobs page, select the job that you want to copy.
3. Click Create Like. The Create Like window is displayed with the settings of the
job that you copied.
4. Type a new job name for this job.
5. Navigate through the Create Like window and edit the applicable job settings.
6. When you are satisfied with your edits, click OK.

The new job is saved and is displayed on the Active and Scheduled Jobs page.
Related concepts:
Related tasks:
Scheduling a task
Deleting a job
Related reference:
Active and Scheduled Jobs
Launch Job window

Edit a job to change its settings. You can edit only jobs that have not run.
Attention: To avoid a potential error, check to make sure that the job that you
want to edit is not scheduled to run during the time that you want to edit it. Check
the Next Run column to make sure the job will not run during the time you intend
to edit it.
Important: You can edit only jobs that have not run. If a job has run once or more,
you cannot edit it. To edit a job that has already run, you can copy the job, edit the
new copy, then remove the original version of the job. Alternatively, you can create
a new job with the properties you need and then delete the original job.
To edit a scheduled job, complete the following steps:

2. On the Active and Scheduled Jobs page, select the job that you want to edit.
3. Click Edit. The Edit window is displayed with the job settings of the job that
you want to edit.
4. Navigate through the Edit window and edit the applicable job settings. For
detailed information, see “Scheduling a task.”
5. When you are satisfied with your edits, click OK.
Note: If the job was executed while you were editing it, the edited job is not
saved. If this occurs, an error message is displayed stating that the job has run
already and cannot be replaced.
The edited job is saved and is displayed on the Active and Scheduled Jobs page.

Related concepts:
Related tasks:
Scheduling a task
Deleting a job

You can run a job immediately. This action does not affect any scheduled instances
of the job.
To run a scheduled job immediately, complete the following steps:

2. On the Active and Scheduled Jobs page, select the job that you want to run.
3. Click Run Now. On the Active and Scheduled Jobs page in the Status column,
the state is changed to Running. This state can be transitory and, therefore, not
observable for some jobs. The state might appear to change to Complete
without changing to Running first. The Last Run column is updated also.

Related concepts:
Related tasks:
Scheduling a task
Deleting a job
Related reference:
runjob command

You can stop a job from running any of its scheduled instances without deleting
the job. Neither the job nor its history is deleted. Then, you can resume the
running of the job. While the job will run its future scheduled instances, it will not
run any past instances that were missed during its suspension.
Note: You cannot suspend most job instances that are currently running.
Right-clicking on the job will show if the job supports suspending currently
running jobs or not. If you suspend the job, the suspension will affect only the job
instances that have yet to run.
To suspend and resume a scheduled job, complete the following steps:

2. On the Active and Scheduled Jobs page, right-click on the job that you want to
suspend or resume.
3. Click Suspend. On the Active and Scheduled Jobs page in the Status column,
the state is changed to Inactive.
4. When you want to resume the job, select the job and click Resume. The job is
resumed. On the Active and Scheduled Jobs page in the Status column, the
state is changed from Inactive to Scheduled. A message is displayed on the
page stating that the job was resumed successfully.

Related concepts:
Related tasks:
Scheduling a task
Deleting a job
Related reference:
runjob command
Canceling a running job

You can cancel a currently running job using the Cancel Running Job Instance task.
Restriction: The Cancel Running Job Instance task only applies to jobs that
support cancellation, such as Discovery.
To cancel a currently running job, complete the following steps:

2. On the Active and Scheduled Jobs page, select the job that you want to cancel.
Note: The Last Run Status column will display Running for currently running
jobs.
3. Click Cancel Running Job Instance. A confirmation window opens.
4. Click OK to confirm cancelation of the job. On the Active and Scheduled Jobs
page, in the Last Run Status column, the state is changed to Complete.
Deleting a job
Delete a existing job when you no longer need it.
To delete a job, complete the following steps:

2. On the Active and Scheduled Jobs page, select one or more jobs that you want
to delete.
3. Click Delete.
4. In the confirmation window, click OK.
The job is deleted and is no longer displayed on the Active and Scheduled Jobs
page.

Related concepts:
Related tasks:
Scheduling a task
Related reference:
rmjob command
Encrypting interprocess communication

Encryption is enabled for interprocess communication by default using the
Advanced Encryption Standard (AES). You can change the encryption algorithm,
disable and enable encryption, and manage encryption keys. This encryption
feature implementation is available only for IBM Director, versions 5.20.3 and
earlier.
Restriction:
v Only IBM Director 5.20 servers support encryption of the IPC layer between 5.20
servers and 5.20 agents.
v Additionally, the following limits exist for the supported interprocess
communication (IPC) encryption between 5.20 servers and agents:
1. 5.20 agents do not support encryption of the IPC layer with Netware
systems.
2. 5.20 agents do not support encryption of the IPC layer with 64-bit Windows
systems.
Related reference:
Encryption Preferences page
Encryption
IBM Systems Director contains a security feature that encrypts all data in
interprocess communications, except transport-layer datagrams used during
discovery. This encryption feature implementation is available only for IBM
Director, versions 5.20.3 and earlier.
Restriction:

systems.
systems.
This encryption feature provides automatic key management. You can select an
encryption algorithm from the provided libraries:
v IBM Java Cryptography Extension (JCE)
v OpenSSL
JCE provides ciphers for all Java-based platforms, including IBM i and Linux;
OpenSSL provides ciphers for 32-bit Windows operating systems.
Encryption is disabled by default. To encrypt data transmitted between IBM

Director Agent version 5.20, managed systems and IBM Systems Director Server,
you must enable encryption on both IBM Systems Director Server and IBM
Director Agent version 5.20, managed systems.
When you install IBM Systems Director Server, you can select one of the following
encryption algorithms:
v Advanced Encryption Standard (AES)
v Data Encryption Standard (DES)
v Triple DES
IBM Systems Director Server automatically generates a key, based on the
encryption algorithm selected. IBM Systems Director Server stores the key in
memory and presents it to IBM Systems Director Server or IBM Director Agent
version 5.20, each time that IBM Systems Director Server or IBM Director Agent
version 5.20, is started, using the Diffie-Hellman key exchange. It is not necessary
for a key to be stored on each managed system.
The following table outlines how data is transmitted between IBM Systems
Director Server and IBM Director Agent version 5.20, managed systems, depending
on whether encryption is enabled.
Table 11. Encryption state and data transmitted between IBM Systems Director Server
andIBM Director Agent version 5.20
IBM Director Agent version IBM Director Agent version
5.20 (encryption enabled) 5.20 (encryption disabled)
IBM Systems Director Encrypted Unencrypted
Server (encryption enabled)
IBM Systems Director No data transmission Unencrypted
Server (encryption disabled) possible
If you have more than one management server in your environment, make sure
you consider the following situation:
v Two management servers have discovered each other and each are displayed in
the other's IBM Systems Director Web interface as systems.
v One management server (server A) has encryption enabled.
v The other management server (server B) either has encryption disabled or has
encryption enabled now but had it disabled when it was discovered and the
communication has not ended since the discovery.

In this situation, unencrypted transmissions sent by server B to server A will
continue until the previous communication is ended. This occurs because server A
(in its role as a management server) is already communicating with server B (in its
role as system) in plain text.
You can delete each system from the Web interface of the other to end the
unencrypted communication. If you run multiple management servers that can
discover each other, you can enable encryption on both management servers before
they are started or before they can discover each other. You can also use the dircli
lsmo command to check for previous communication. For more information, see
“System commands.”
Notes:
v Encryption is not supported on systems running NetWare or systems running
64-bit versions of Windows.
v Neither out-of-band communications nor communication used by Internet tools,
such as Telnet or File Transfer Protocol (FTP), are encrypted.
v There is a performance penalty when you enable encryption. Encrypting data
packets and exchanging encryption keys has an effect on the speed with which
IBM Systems Director completes management operations. When either the
management server or the systems are restarted, keys are regenerated and
exchanged. Consequently, an unsecured managed system might seem to be
unmanageable for a period of time.
Related tasks:
Enabling encryption
Disabling encryption
Changing the encryption algorithm
Resending the encryption key to systems
Creating a new encryption key
Related reference:
System commands
Enabling encryption
You can enable encryption on the management server. This encryption feature
implementation is available only for IBM Director, versions 5.20.3 and earlier.
Restriction:
systems.
systems.
To enable encryption on IBM Director Agent, versions 5.20.3 and earlier, complete
and click Encryption Preferences.
2. On the Encryption Preferences page, select the Enable encryption of data check
box.
3. Click Apply.
4. The Save Encryption Settings window opens. Click OK to confirm enabling the
encryption algorithm and synchronizing the keys. The keys are sent to all
affected systems. A confirmation message is displayed.
5. Click OK to save the change and close the page.
Related concepts:
Encryption
Related tasks:
Related reference:
You can disable encryption on the management server. Encryption must be enabled
previously. This encryption feature implementation is available only for IBM
Director, versions 5.20.3 and earlier.
Restriction:
systems.
systems.
To disable encryption on IBM Director Agent, versions 5.20.3 and earlier, complete
2. On the Encryption Preferences page, clear the Enable encryption of data check
box.
3. Click Apply to save the change.
4. The Save Encryption Settings window opens. Click OK to confirm disabling the
encryption algorithm.
5. A confirmation message is displayed. Click OK to save the change and close
the page.

Related concepts:
Encryption
Related tasks:
Enabling encryption
Related reference:

You can change the algorithm used to encrypt communications between IBM
Director Server, versions 5.20.3 and earlier, and IBM Director Agent, versions 5.20.3
and earlier. When you change the algorithm, new encryption keys are sent to all
systems running IBM Director Agent, versions 5.20.3 and earlier. Encryption must
be enabled previously. This encryption feature implementation is available only for
IBM Director, versions 5.20.3 and earlier.
Restriction:
systems.
systems.
To change the encryption algorithm for systems running IBM Director Agent,
versions 5.20.3 and earlier, complete the following steps:
2. In the Select data encryption standard list, select the encryption algorithm that
you want to use.
3. Click Apply.
4. The Save Encryption Settings window opens. Click OK to confirm changing the
encryption algorithm and synchronizing the keys. The keys are sent to all
affected systems. A confirmation message is displayed.
5. Click OK to save the change and close the page.

Related concepts:
Encryption
Related tasks:
Enabling encryption
Related reference:

You can resend the existing encryption keys to systems running IBM Director
Agent. This encryption feature implementation is available only for IBM Director,
versions 5.20.3 and earlier.
Restriction:
systems.
systems.
To resend encryption keys to all systems running IBM Director Agent, versions
5.20.3 and earlier, complete the following steps:
2. On the Encryption Preferences page, click Resend Keys.
3. In the Resend Encryption Keys window, click Resend to resend the keys. When
the operation is completed, the confirmation message is displayed.
4. To close the page, click OK.
Related concepts:
Encryption
Related tasks:
Enabling encryption
Related reference:

You can generate a unique encryption key for a system running IBM Director
Agent. This encryption feature implementation is available only for IBM Director,
versions 5.20.3 and earlier.
Restriction:

systems.
systems.
Encryption must be enabled.
To set a new encryption key for one system running IBM Director Agent, versions
5.20.3 and earlier, complete the following steps:
1. In the IBM Systems Director Web interface navigation area, click Resource
Explorer.
2. On the Resource Explorer page, navigate to the managed system for which you
want to reset the encryption key.
3. Right-click the system and click Encryption Key Reset.
Note: You can select more than one system to reset encryption keys.
4. In the Encryption Key Reset window, click Reset to reset the key.
IBM Systems Director Server generates a new, unique key for the managed system
and displays a confirmation message.
Related concepts:
Encryption
Related tasks:
Enabling encryption
Related reference:

Chapter 3. Discovering systems and collecting inventory data
To manage a resource within an environment or view inventory data about it, that
resource must first be discovered and, after access is granted, an inventory must be
collected. The resource is recognized and added to the comprehensive list of native
resources and native attributes for the system. Discovery and inventory collection
are the two primary tasks that are used to connect to supported network resources
and collect information about them.
If you are discovering and collecting inventory on Power Systems compute nodes,
make sure that SCP is installed on the Power Systems compute nodes before
running Discovery or Inventory Collection from the FSM so that the network
adapters are discovered and inventoried by the FSM. For more information about
installing SCP, which is available with the OpenSSH software tools, see the
following website:
OpenSSH and Kerberos Version 5 support

Related concepts:
Discovery manager
Related tasks:
Discovering and collecting inventory for storage devices
Discovery
Discovery is the process by which IBM Systems Director Server identifies and
establishes connections with network-level resources that IBM Systems Director can
manage, such as computers, switches, or printers. Use system discovery to identify
resources within your environment, collect data about those resources, and
establish connections with them.
Before you can use IBM Systems Director to manage a device, that resource must
be discovered by IBM Systems Director Server. After a resource is discovered, it
becomes a system that IBM Systems Director can manage.
Note: The discovery process discovers only systems and other types of resources
that can be managed by IBM Systems Director. In other words, just because you
can "ping" a resource does not mean that IBM Systems Director can discover it.
After a system is discovered, it is displayed on the Resource Explorer page. You

can drill down in the groups of systems within IBM Systems Director to manage
and view information about the systems that have been discovered.
You can view discovery and inventory information and perform discovery and
inventory tasks on the Initial Setup tab of the Home page or by using the
Discovery Manager plug-in. As the discovery process runs, the pie chart on the
Discovery Manager summary page updates to indicate the number of system types
discovered.

Related concepts:
Related tasks:
Collecting inventory
System discovery
System discovery enables you to discover a resource for a single IPv4 or IPv6
address or host name or many resources of the same type that occur in a densely
populated single range of IP addresses. You can also use a discovery profile to
discover more specific categories of resource types, specify multiple ranges of IP
addresses, or automatically request access to or collect inventory for discovered
resources.
System discovery provides the following functions:

v Discovery based on a single IPv4 or IPv6 address
v Discovery based on a single host name
v Discovery based on one range of IPv4 or IPv6 addresses
v Discovery based on a discovery profile
Using discovery based on a single IP address or host name or a range of IP

addresses is useful when the following conditions apply:
v You are managing a single subnet (or only a few subnets) and you want to
manage all resources that are on the subnet or all resources of a given type.
v The subnet is a densely populated single range of IP addresses for a single
resource type that you want to discover at one time.
Using discovery based on a discovery profile is useful when the following

conditions apply:
v Your resources span many subnets.
v A specific type of resource occurs in multiple IP address ranges.
v You want to automatically request access to or collect inventory for the
discovered resources.
v You need to discover various types of resources by using targeted discovery
profiles.
System discovery is able to detect the same kinds of resources as the Default
getting started discovery profile, but also is able to discover the following types of
resources:
v Chassis by way of a management module or an advanced management module
v eServer™ 325, 326, and 326m model servers discovered by way of an ISMP
service processor1
v IBM Flex System Enterprise Chassis
v IBM Power servers with service processors
v IBM Power systems being managed by Hardware Management Console (HMC)
v IBM Power systems being managed by Integrated Virtualization Manage (IVM)
v IBM Tivoli Storage Productivity Center (TPC) storage resource groups
v Metering products such as power distribution units (PDU) and uninterruptible
power supplies
v Printers, switches, and bridges enabled for SNMP2
v Sensor hubs and sensor networks for energy and environmental management

v Storage devices, including TPC storage resource groups
v System x servers with service processors
v System x servers discovered by way of an integrated management module,
integrated management module II, or IPMI baseboard management controller
(BMC)
v System x server discovered by way of a Remote Supervisor Adapter or Remote
Supervisor Adapter II
v System z servers being managed by (HMC)
v Systems that are cloned or that use a mirrored image3
v VMware vCenter systems
1. Although the service processor in the eServer 325, 326, and 326m models is
called an ISMP, it is a BMC.
2. Pass-through modules do not provide SNMP support.
3. To discover a system that uses a mirrored image, the system must be
properly configured. For more information, see “Discovering systems that
use a mirrored image.”
The discovery process discovers only systems and other types of resources that can
be managed by IBM Systems Director. In other words, just because you can "ping"
a resource does not mean that IBM Systems Director can discover it.
Discover only those resources that you intend to manage with IBM Systems
Director. For example, if the management interfaces of your networking equipment
are on a single subnet, yet you do not intend to manage your networking
equipment with IBM Systems Director, do not discover devices on that subnet.
As system discovery runs, the System Discovery page refreshes the list of
discovered resources in the Discovered Manageable Systems table. You also can
view the results of this discovery by using the Discovery jobs task to examine the
associated job. You can view all discovered systems on the Resource Explorer page.
While the discovery process is active, the System Discovery page also displays
additional elements:
v An icon and text message that states whether the discovery process is running
or stopping
v A Stop button that enables you to stop the discovery process that is updating
the Discovered Manageable Systems table
v A New discovery button that enables you to run another system discovery in
addition to the one that is currently active. If you run a new discovery, the new
discovery updates the Discovered Manageable Systems table. When you run a
new discovery, you must use the Discovery jobs task to view the results of the
current discovery.
Note: The time it takes for discovery to finish processing varies depending on
such factors as network performance and the number of systems that are
discovered. Avoid managing newly discovered resources for a time after the
discovery task finishes, because associated processing continues to run.
Chapter 3. Discovering systems and collecting inventory data 161

Related concepts:
Default getting started discovery profile
Related tasks:
Discovering systems with system discovery
Discovering systems that use a mirrored image
Using system discovery to view current results
IP addresses
System discovery can use a single IP address, a single host name, or a single range
of IP addresses to discover manageable resources. When using a discovery profile,
you have options to specify multiple IP addresses and address ranges and import
IP address information in a text file. You can also exclude individual IP addresses,
IP address ranges, or entire subnets from discovery.
System discovery in IBM Systems Director version 6.2 supports both the IPv4 and
IPv6 protocols. Whether you specify a single IP address on the System Discovery
page or import a list of IP addresses, discovery requires that IP addresses adhere to
the following rules:
v The maximum permitted range of IP addresses is 256.
v For IP address ranges, the specified starting address must be less than the
ending address, where only the last piece of the starting and ending addresses
are unique. The following examples are valid patterns: a.a.a.b-a.a.a.c for an IPv4
address or a:a:a:a:a:a:a:b-a:a:a:a:a:a:a:c for an IPv6 address, where for each
example b is less than c.
v All addresses in a valid IPv4 address range must occur in the same Class C
subnet.
v When the interface allows (for example, when using the Discovery Profile
wizard), IPv6 address compression might be used to replace one or more
consecutive instances of 0 in an address. For example, when using address
compression, this address DD01:0:0:0:0:0:0:1C would be written as DD01::1C.
v Using the IPv6 loopback address (0:0:0:0:0:0:0:1 or ::1) is not supported.
v Using prefix-length for IPv6 addresses is not supported.
When discovering a range of IP addresses, use the smallest range possible.

v IPv4 example: Assume that you have a subnet 10.1.1.0 - 10.1.1.255, but all of
your systems are within the first 100 addresses. In this case, you would use
10.1.1.1-10.1.1.100 as the range instead of 10.1.1.1-10.1.1.255.
v IPv6 example: Assume that you have a subnet E290::51D2:9008:C01D:6420 -
E290::51D2:9008:C01D:651F, but all of your systems are within the first 100
addresses. In this case, you would use E290::51D2:9008:C01D:6420-
E290::51D2:9008:C01D:6484 as the range instead of E290::51D2:9008:C01D:6420-
E290::51D2:9008:C01D:651F.
Import IP address file format

When you have many IP addresses that you want to discover, consider using a
discovery profile to import one or more files that list the addresses to include in
and exclude from the discovery. An imported file can specify multiple single IP
addresses or address ranges to include and exclude. Discovery supports both IPv4
and IPv6 protocols.
Note: After creating the file, import it at the time you configure a discovery
profile. To create a discovery profile, click Create new profile on the System
Discovery page. For more information, see “Discovery profiles.”

Importing a file that lists IP addresses to include and exclude applies only to the
current discovery. To permanently exclude IP addresses from discovery, specify
that IBM Systems Director permanently ignore the IP addresses. Excluding IP
addresses in this way means that Systems Director does not communicate with or
manage resources by using the excluded IP addresses. For more information, see
“Permanently excluding IP addresses from discovery.”
To import a file, the file must meet the following criteria:

v The file must be a simple ASCII text file. The file extension does not matter.
v The file must be located on the system that is running the web browser that you
are using to create or edit the profile.
v Case does not matter.
v Do not use host names.
v Each line of the file can contain only one IP address or one IP address range.
v Write an IP address range as <start>-<end> where <start> is the starting IP
address of the range and <end> is the ending IP address of the range. For
example, this entry includes the specified IP address range:
10.42.104.0-10.42.104.200
v To exclude a single IP address or IP address range, begin the line with exclude=.
For example, both ExcluDe=9.22.3.114 or exclude=e290::51D2:9008:C01d:6420-
E290::51d2:9008:c01D:6484 are valid entries.
Related tasks:
Permanently excluding IP addresses from discovery
IPv6 restrictions for discovery

Starting with version 6.2, adds support for using IPv6 addresses to discover and
manage resources. Keep in mind the following IPv6 considerations, whether you
discover resources by specifying a single IP address, host name, or IP address
range or by using a discovery profile to specify multiple IP addresses and address
ranges.
IPv6 in-band restrictions
The following restriction applies when using IPv6 in-band for agentless-managed
systems, Platform Agent managed systems, and Common Agent managed systems.
Restriction: All discoverable operating systems that version 6.2 can manage by
using IPv4 can also be managed by using IPv6 in-band, except for Windows 2003
and Windows XP. Microsoft does not officially support DHCPv6 client with
Windows 2003 or Windows XP, and so neither is fully IPv6 compliant.
IPv6 out-of-band restrictions
The following restrictions affect discovery when using IPv6 out-of-band.
Restriction:
v IPv6 support for managing IBM BladeCenter servers out-of-band requires
Advanced Management Module Firmware v3.54 (BPET54B) or higher.
v IPv6 support for managing IBM Power Systems servers out-of-band through
Hardware Management Console (HMC) requires HMC V7R350 SP1, V7 R710 or
higher.

v IPv6 support for managing Power Systems servers out-of-band through
Integrated Virtualization Manager (IVM) requires IVM/Virtual I/O Server
(VIOS) 2.1.3 or higher.
v IPv6 support for managing Power Systems servers out-of-band using Flexible
Service Processor (FSP) is currently not available. This restriction does not apply
to Power Systems managed with IVM or HMC.
v IPv6 support for managing IBM System x servers out-of-band using Integrated
Management Module (IMM) is not available.
v IPv6 support for managing IBM System x servers out-of-band using Integrated
Management Module(IMM) II is available.
For more information about IBM Systems Director support for IPv6, see “IPv6
compliance”.
Related reference:
IPv6 compliance
Discovery profiles
System discovery can use a discovery profile to discover manageable resources. A
discovery profile is a group of discovery settings that are saved on IBM Systems
Director Server. Settings for the profile include the type of resources to be
discovered, and whether to automatically request access to or collect inventory for
discovered resources. IBM Systems Director includes several default profiles that
you can use, or you can create profiles to suit your specific requirements.
Several options exist for working with discovery profiles. You can use the System
Discovery page to run an existing profile or create a unique profile. Use the
Manage Discovery Profiles page to create, copy, edit, delete, or run discovery
profiles. Choosing to create or edit a discovery profile launches the Discovery
Profile wizard, which helps you configure the profile.
Typically, a default discovery profile searches the primary subnet for the specified
target resources. Default profiles automatically use the IP address range of the
current subnet, as determined by the last start of the IBM Systems Director Server.
You can also create a profile that you base on a default profile. Simply changing
the IP addresses might be sufficient to create a profile that suits your needs.
When discovering a large number of resources, network traffic associated with the
discovery process might cause timeouts that result in some discoverable resources
remaining undiscovered. To help prevent this problem, use one or more discovery
profiles. Using a discovery profile enables you to target specific resources and limit
the number of communication protocols used during discovery. Limiting the
number of communication protocols used when discovering a large number of
resources helps avoid problems caused by network traffic collisions and timeouts.
IBM Systems Director includes the following default profiles:

Default agentless discovery
Discovers agentless-managed systems running AIX, Linux, or Windows1.
Default Common Agent discovery
Discovers systems on the local subnet that have IBM Director Agent,
versions 5.10 and 5.20, or Common Agent, version 5.0 or later, installed.2, 3
Default getting started discovery

Discovers a wide range of managed resources on the local subnet. For
more information, see “Default getting started discovery profile”.

Default HMC managing IBM Power Systems discovery
Discovers IBM Power Systems and System z servers on the local subnet
that are under the control of Hardware Management Console (HMC) or
Integrated Virtualization Manager (IVM).
Default IBM BladeCenter discovery
Discovers IBM BladeCenter systems, by way of either a management
module or an advanced management module.
Default IBM Power Systems Servers with service processors discovery
Discovers IBM Power Systems servers with service processors.
Default IBM System x Servers with service processors discovery
Discovers IBM System x servers with service processors.
Default Platform Agent and agentless discovery
Discovers IBM Systems Director Platform Agent , version 6.1 or later,
managed systems; IBM Director Core Services, versions 5.10 and 5.20,
managed systems; and agentless-managed systems running AIX, Linux, or
Windows.4, 5
Footnotes:
1. Default agentless discovery profile does not discover agentless-managed systems enabled for SNMP.
2. Discovery of IBM Director Agent, versions 5.10 and 5.20 is provided only as a step toward upgrading discovered
agents to a more recent version. IBM Systems Director version 6.2 does not support managing IBM Director
Agent, version 5.10. For more information, see “Version compatibility of IBM Systems Director components.”
3. IPv6 is not supported for IBM Director Agent, versions 5.10 and 5.20. Common Agent version 6.2 includes
support for IPv6. but previous versions do not support IPv6 addresses.
4. Discovery of IBM Director Core Services, versions 5.10 and 5.20, is provided only as a step toward upgrading
discovered agents to a more recent version. IBM Systems Director version 6.2 does not support managing IBM
Director Core Services, version 5.10. For more information, see “Version compatibility of IBM Systems Director
components.”
5. IPv6 is not supported for IBM Director Core Services, versions 5.10 and 5.20. Platform Agent version 6.2 includes
support for IPv6. but previous versions do not support IPv6 addresses.
When you need to create a unique profile, the Discovery Profile wizard assists you
in identifying the type (and subtype) of resource that you want to discover and
configuring the necessary protocols. For more information about creating, editing
and deleting profiles, see “Managing discovery profiles”.
Related concepts:
Discovery protocols
Related tasks:
Creating a discovery profile
Managing discovery profiles
Related reference:
Version compatibility of IBM Systems Director components across releases
Default getting started discovery profile:
The Default getting started discovery profile discovers a range of manageable

resources on your local subnet.

The Default getting started discovery profile discovers the following types of
managed resources on the local subnet:
v Systems that are managed by using the following agents or services:
– IBM Systems Director Common Agent, version 6.1 or later1
– IBM Systems Director Platform Agent, version 6.1 or later1
– IBM Director Agent, versions 5.10 and 5.202, 3
– IBM Director Core Services, versions 5.10 and 5.202, 3
v Any existing infrastructure being managed with Tivoli Common Agent Services
v Agentless-managed systems enabled for Simple Network Management Protocol
(SNMP)
v Agentless-managed systems running AIX or Linux4
v Agentless-managed systems running Windows4
v Operating systems enabled for SNMP
v VMware ESX and ESXi hosts
1. IPv6 is not supported for IBM Director Agent, versions 5.10 and 5.20 or IBM
Director Core Services, versions 5.10 and 5.20.
2. Discovery of IBM Director Agent, versions 5.10 and 5.20, and IBM Director
Core Services, versions 5.10 and 5.20, is provided only as a step toward
upgrading the discovered agents to a more recent version. IBM Systems
Director version 6.2 does not support managing IBM Director Agent, version
5.10 or IBM Director Core Services, version 5.10. For more information, see
“Version compatibility of IBM Systems Director components.”
3. IPv6 is not supported for IBM Director Agent, versions 5.10 and 5.20 or IBM
Director Core Services, versions 5.10 and 5.20.
4. For more information about preparing or configuring agentless-managed
system so that IBM Systems Director can discover and manage them, see
“Preparing agentless managed systems.”
The Default getting started discovery profile attempts to discover systems by using
all agent-related discovery protocols on the local subnet. This inefficiency might
cause the management server to time out on one or more discovery requests,
resulting in a small percentage of discoverable resources remaining undiscovered.
The Default getting started discovery profile does not discover every type of
managed resource. For more information about how to discover other types of
managed resources, see “System discovery.”

Related concepts:
System discovery
Related tasks:
Viewing the discovery manager summary
Preparing agentless managed systems

Related reference:
Discovery protocols
A discovery protocol is any network communication protocol that IBM Systems
Director Server uses during the discovery process to discover a resource. The
Default getting started discovery profile uses a predetermined list of protocols.
When you specify a single IP address, a single host name, or a single range of IP
addresses, system discovery uses one or more protocols based on the selected
target resource type. Using a discovery profile enables you to refine the target
resource type and configure specific protocols that you want to use.
The communication protocols that IBM Systems Director Server uses during
discovery depend on the protocols used by the target resource type. You need to
decide about the different protocols only when you create or edit a discovery
profile. The Discovery Profile wizard helps you select and configure the correct
protocol for the type of resource that you want to discover.
When discovering a large number of resources, network traffic associated with the
discovery process might cause timeouts that result in some discoverable resources
remaining undiscovered. To help prevent this problem, use one or more discovery
profiles. Using a discovery profile enables you to target specific resources and limit
the number of communication protocols used during discovery. Limiting the
number of communication protocols used when discovering a large number of
resources helps avoid problems caused by network traffic collisions and timeouts.
By default, IBM Systems Director supports the following discovery protocols:

Agent manager discovery
Agent manager discovery specifically targets the discovery of Tivoli
common agents. In the Tivoli paradigm, Service Location Protocol (SLP) is
not supported and management servers contact an agent manager that
knows about the agents in their environment. You can select the agent
managers that you want to use in discovery.
Common Agent Services (CAS) discovery
CAS discovery utilizes Service Location Protocol (SLP) discovery, with
which clients can locate servers and other services on the network.
Common Information Model (CIM) discovery
CIM discovery utilizes the Service Location Protocol (SLP) for discovery.
With CIM discovery, clients can locate servers and other services on the
network.
Interprocess communication (IPC) discovery
IPC is the process by which programs send messages to each other.
Sockets, semaphores, signals, and internal message queues are common
methods of interprocess communication. IPC is also a mechanism of an

operating system that enables processes to communicate with each other
within the same computer or over a network. IPC leverages services that
IBM Systems Director provides that components use to communicate with
each other. By using these services, a server task can communicate with an
agent task running on a target.
Secure shell (ssh) discovery
Secure shell is a Unix-based command interface and protocol for securely
accessing a remote computer. With ssh discovery, you can specify either a
single IP address or a range of IP addresses upon which to run discovery.
Note: IBM Systems Director does not support the ssh protocol on ESXi.
Simple Network Management Protocol (SNMP) discovery
SNMP is a network management standard widely used in TCP/IP
networks. SNMP performs management services by using a distributed
architecture of management systems and agents. SNMP provides a method
of managing network hosts such as workstation or server computers,
routers, bridges, and hubs from a centrally-located computer running
network-management software.
Storage Management Initiative Specification (SMI-S) discovery
With SMI-S discovery, clients can locate servers and other services on the
network. It is a design specification developed by the Storage Networking
Industry Association (SNIA) that specifies a secure and reliable interface
with which storage management systems (SMSs) can identify, classify,
monitor, and control physical and logical resources in a storage area
network (SAN). The interface integrates the various devices to be managed
in a storage area network (SAN) and the tools used to manage them.
Windows Distributed component object model (DCOM) discovery
Use Windows DCOM (an extension of the Microsoft Component Object
Model (COM) to support objects distributed across a network)
configuration to specify either a single IP address or a range of IP
addresses upon which to run discovery.
Note: Additional discovery protocols are routinely created by vendors. For more
information about communicating with a device that uses a protocol that is not
listed here, contact the manufacturer or software provider for that device.

Related concepts:
IP addresses
Discovery profiles
Related tasks:
Performing system discovery
Choosing which discovery method to use

Discovering your resources in the most efficient manner means deciding which
method best suits your needs. Each method has advantages and disadvantages to
consider.
Table 12. Recommended use for each discovery method
Discovery method When this discovery method is appropriate
Specifying a single IP v You are managing a single subnet (or only a few subnets) and you want to manage
address or host name, or all resources that are on the subnet or all resources of a given type.
a range of IP addresses
v The subnet is a densely populated single range of IP addresses for a single resource
type that you want to discover at one time.
Using the Default getting v Your management server (the system running IBM Systems Director Server) and all
started discovery profile managed resources reside on a single subnet, for example, small and medium
business (SMB) and small office or home office (SOHO) environments.
v The subnet is densely populated with many types of agents or resources.
v Efficiency is not required. For example, discovering a sparsely populated subnet by
processing the entire subnet range takes longer because many requests that use many
protocols must complete.
Using a discovery profile v Your resources span many subnets.
(other than Default
v A specific type of resource occurs in multiple IP address ranges.
getting started)
v You want to automatically request access to or collect inventory for the discovered
resources.
v You need to discover various types of resources by using targeted discovery profiles.
Each discovery method has advantages and disadvantages. Understanding this

information can help you decide which discovery method is best for your

Table 13. Advantages and disadvantages of discovery methods
Discovery method Advantages Disadvantages
Specifying a single IP v Single-step task that can discover all v Discovers one system or IP address range
address or host name, systems without requiring information by using the protocols associated with the
or a range of IP about what type of resource is located at specified resource type. This method of
addresses each IP address. discovery might be inefficient because all
Note: Discovery the discovery protocols for the specified
v Discovers a specific system by using an IP
supports IPv4 and IPv6 resource are used on each IP address. This
address or host name.
protocols. inefficiency might cause the management
v Discovers multiple systems by using a
server to time out on one or more
range of IP addresses.
discovery requests, resulting in a small
v Can limit discovery based on the resource percentage of discoverable resources
type. remaining undiscovered.
v Schedules to run discovery on a recurring
basis
Using the Default Easy to use. v Discovers only agents in the local subnet.
getting started Agents include:
discovery profile – IBM Systems Director Common Agent,
version 6.1 or later1
– IBM Systems Director Platform Agent,
version 6.1 or later1
– IBM Director Agent, versions 5.10 and
5.202, 3
– IBM Director Core Services, versions
5.10 and 5.202, 3
– Agentless-managed systems
v An inefficient form of discovery because it
attempts all agent-related discovery
protocols on the local subnet. This
inefficiency might cause the management
server to time out on one or more
discovery requests, resulting in a small
percentage of discoverable resources
remaining undiscovered.
Using a discovery v Provides various default discovery v Does not provide a progress indicator for
profile (other than profiles. discovery completion. Instead, use the job
Default getting started progress indicator on the Active and
v Provides a wizard that helps you create a
profile) Scheduled Jobs page.
profile.
v Provides finer categories of resource types v Cannot discover multiple resource types
for selection. in a single discovery profile.
v Discovers multiple systems by using a v Takes more time and system knowledge
range of IP addresses. to configure due to extensive options and
settings.
v Provides discovery-protocol selection that
enables the most efficient discovery of
target resources and reduces the chance
for network timeouts.
v Discovers multiple ranges of IP addresses.
v Schedules to run discovery on a recurring
basis.
v Imports a list of IP addresses to discover.
v Provides an option to automatically
request access to discovered resources.
v Provides an option to automatically collect
inventory for discovered resources.

Table 13. Advantages and disadvantages of discovery methods (continued)
Discovery method Advantages Disadvantages
1. Common Agent version 6.2 and Platform Agent version 6.2 include support for IPv6. Previous versions of these
agents do not support IPv6 addresses.
2. Discovery of IBM Director Agent, versions 5.10 and 5.20, and IBM Director Core Services, versions 5.10 and 5.20,
is provided only as a step toward upgrading the discovered agents to a more recent version. IBM Systems
Director version 6.2 does not support managing IBM Director Agent, version 5.10 or IBM Director Core Services,
version 5.10. For more information, see “Version compatibility of IBM Systems Director components.”
3. IPv6 is not supported for IBM Director Agent, versions 5.10 and 5.20 or IBM Director Core Services, versions
5.10 and 5.20.
Related concepts:
System discovery
Discovery profiles
Related reference:
Viewing the discovery manager summary

You can view a summary of all activity within the past 30 days that is associated
with discovery, including discovered systems, collected inventory data, system
access, and system authentication. The information on the summary page is
refreshed automatically when there are any changes.
To view the discovery manager summary, complete the following steps:

2. On the Home page, click the Plug-ins tab. A list of available summary pages is
displayed.
3. On the Plug-ins tab, scroll to the Discovery manager section heading and click
it. The discovery manager summary for the past 30 days is displayed.
4. View the Discovery and Inventory section. This section provides the following
information:
v A pie chart and corresponding list that indicate the number of discovered
systems for which inventory was collected, broken down into the following
three categories:
– Systems with no agent (agentless)
Note: Agentless pertains to a type of data collection that is accomplished

without installing additional agents. Data is obtained by using software
that is already installed on the resource.
– Systems with a platform agent
– Systems with a common agent
Click any of the category list items to see a breakdown of the systems in that
category.
v The number of discovered systems for which no inventory was collected.
Note: A system that has not been discovered does not show up anywhere on
this page.

System Discovery
Use the System Discovery page to run a discovery. Discover specific
types of resources for a single IP address or host name or a single IP
address range, or you can use a discovery profile to customize the
discovery settings.
Collect and view inventory
Use the View and Collect Inventory page to collect the most current
inventory from a resource or view the inventory of a resource.
Resource Explorer
Use the Resource Explorer page to view and manage discovery
options on an individual resource level.
5. View the Access and Authentication section. This section provides the
v The number of systems that are accessible.
v A pie chart and corresponding list that indicate the access levels of the
systems, broken down into the following three categories:
Systems with no access
IBM Systems Director is not authenticated to these systems and is
unable to perform any tasks on them.
Systems with partial access
IBM Systems Director has full access to some remote service access
points for these systems but no access to others.
Note: A system with partial access has multiple access points, but
not all these access points are accessible. To gain full access, you
must configure credentials to authenticate with each of the access
points. For more information, see “Accessing a secured system with
configure access” and “Accessing a secured system with request
access”.
Systems with full access
IBM Systems Director is fully authenticated and, barring other
inhibitors, able to perform tasks on these systems.
category.
Request access for 'no access' systems
Use the Request access for 'no access' systems page to view the list of
systems that are in the no access state. Also use this page to request
access, with a user ID and password, for any of the listed 'no access'
systems.
Manage Credentials
Use the Manage Credentials page to manage all your shared
credentials.

Related concepts:
System discovery
Related tasks:
Finding a task
Accessing a secured system with request access
Accessing a secured system with configure access
Managing credentials
Renaming discovered systems automatically

You can configure IBM Systems Director to automatically rename each discovered
system by using a customized template.
Following discovery, IBM Systems Director assigns a name to each discovered

system, which might not suitable for your environment. To help better organize
your systems and ensure consistency among system names, you can rename each
system to follow a convention. You can use Resource Explorer to rename each
system individually, but this can be time consuming when you have many
discovered systems. An easier and more efficient option is to configure IBM
Systems Director to rename each discovered system by using a customized
template.
To automatically rename discovered systems, complete the following steps:

and then click Auto Rename. The Auto Rename page opens.
2. On the Auto Rename page, select the profile that you want to customize for
automatic renaming and click Edit. The Edit Template page opens.
3. Customize the template to be used when systems are automatically renamed
and enable the auto rename task:
a. Decide which variable should be displayed first in the name of each
resource and select it from the list, which varies depending on the resource
type that is selected.
Note: To specify text to be inserted into the name template, select

%TEXT%, then enter the text.
b. Click Insert.
c. Select each subsequent variable and click Insert after each one.
d. Select Yes to enable auto rename.
4. Click OK. The template is displayed in the table.
5. To set up targets and options for your auto rename task, click Rename. The Job
Launcher page opens. Make your selections, then click OK. The auto rename
task runs or is scheduled to run.

Related concepts:
Discovery profiles

Use the system discovery task to discover one or more resources based on a
specific IP address, host name, or range of IP addresses or by using a discovery
profile. You can also use system discovery to discover properly configured systems
that use mirrored images. View the results of the current system discovery or a
system discovery that ran previously.
Related concepts:
IP addresses
Discovery profiles
Discovery protocols
Related tasks:
Choosing which discovery to use
Performing a system discovery

Use the System Discovery task to discover one or more resources by specifying a
single IP address, single host name, or a single range of IP addresses, or by using a
discovery profile.
To perform a system discovery, complete the following steps:
Note:
v Discover only those resources that you intend to manage with IBM Systems
Director. For example, if the management interfaces of your networking
equipment are on a single subnet, yet you do not intend to manage your
networking equipment with IBM Systems Director, do not discover devices on
that subnet.
v When discovering a large number of resources, network traffic associated with
the discovery process might cause timeouts that result in some discoverable
resources remaining undiscovered. To help prevent this problem, use one or
more discovery profiles. Using a discovery profile enables you to target specific
resources and limit the number of communication protocols used during
discovery. Limiting the number of communication protocols used when
discovering a large number of resources helps avoid problems caused by
network traffic collisions and timeouts.
1. Open the System Discovery page as follows:
v From the Initial Setup tab on the Home page, click System discovery.
The System Discovery page is displayed.
2. Select one of the following discovery methods:

Table 14. System discovery methods
To do this task: Complete these steps:
Use a single IPv4 or IPv6 address 1. Select Single IPv4 address or Single
IPv6 address from the Select a discovery
option field.
2. In the IP address field, type the IP
address of the system that you want to
discover.
3. If you want to discover only a specific
resource type, select it from the Select
the resource type to discover list.
Use a range of IPv4 or IPv6 addresses 1. Select Range of IPv4 addresses or Range
of IPv6 addresses from the Select a
discovery option field.
2. For the IP address range that contains
the systems that you want to discover,
type the complete low-end IP address in
the Starting IP address fields and the
last piece of the high-end IP address in
the Ending IP address field.
Use the host name of a system 1. Select Single host name from the Select
a discovery option field.
2. In the Host name field, type the host
name of the system that you want to
discover.
Use an existing discovery profile 1. Select Select a discovery profile to run
from the Select a discovery option field.
2. Select the profile that you want to use
from the Discovery profile to run field.
Create and use a discovery profile 1. Click Create new profile under
Advanced Tasks.
2. Use the Discovery Profile wizard to
create a discovery profile. After saving
the profile, the System Discovery page
display automatically, and the profile
you created is already selected.
3. Run the discovery.

v Click Discover Now if you want to run the discovery immediately.
v Click Schedule if you want to schedule the discovery to run at a specific
time. The Job Launcher page is displayed. Use the Job Launcher page to
configure the Schedule, Notification, and Options settings for the discovery
task.
The System discovery page updates in the following ways:
v A message displays information about the job under which the discovery
task runs.
v When the discovery task runs immediately, a status icon and text message
indicate the status of the discovery process.

v As the process discovers manageable resources, the Discovered Manageable
Systems table displays them. The Discovered Manageable Systems table
displays the resources that are discovered during the current discovery and
those resources that were discovered previously.
v The Discover Now and Schedule buttons are deactivated and the Stop and
New Discovery buttons appear.
4. Optional: If you want to stop the discovery process, click Stop. If you want to
run a new discovery while the current discovery continues to run, click New
Discovery. When you choose to run a new discovery, the Discovered
Manageable Systems table displays results for the new discovery only. To view
the results of the current discovery, use the Discovery jobs task.
As the process discovers manageable resources, the Discovered Manageable

Systems table displays them, including those resources that were discovered
previously.
Note: After a resource is discovered, the virtual systems that are associated with
that resource are also discovered.
v To view the results of a specific discovery that ran at a previous time or a
discovery that is scheduled to run at a later time, use the Discovery jobs task.
v To view all discovered resources, use the Resource Explorer task.
When the discovery process completes, the status icon and text message disappear
and the Discover Now and Schedule buttons become active again.
Related concepts:
System discovery
IP addresses
Discovery profiles
Related tasks:
Choosing which discovery to use
Related reference:
Discovering systems that use a mirrored image

Systems that are cloned (or use a mirrored image) and managed by must be
correctly configured to ensure their successful discovery.
To discover cloned systems, they must be configured in the following ways:

v All cloned systems must have a unique identifier (UID).
v Each cloned Common Agent managed system must have a globally unique
identifier (GUID).

v Any cloned system that uses Secure Shell (SSH) must have a unique Secure Shell
(SSH) host key.
To discover cloned systems, perform the following steps before discovering them.
If you have previously discovered the cloned systems, remove the managed
systems and their operating systems from Systems Director before proceeding.
Note: On AIX you can also use the reset_diragent_keys command to perform
these steps automatically. See “reset_diragent_keys command” for information.
1. For the specified mirrored systems, view and compare the UID entries on the
host and the mirrored system to ensure that the UID entries are unique. For
Common Agent managed systems, perform a similar comparison for the Tivoli
GUID entries.
Important: Common Agent contains a platform agent. Therefore, if you have

a common agent, you need to complete the common agent and the platform
agent steps.
For instructions to search for existing resources, see the topic “Finding systems
and other resources”.
Platform Instructions
AIX, Linux For Platform Agent managed systems, run the following command:
od -t x1 /etc/ibm/director/twgagent/twgagent.uid
For Common Agent managed systems, run the following

command:
v For AIX: LANG=C;/usr/tivoli/guid/tivguid -Show
v For Linux: LANG=C;/opt/tivoli/guid/tivguid -Show
IBM i (formerly Note: Some characters are not readable. For Platform Agent
i5/OS) managed systems, run the following command: DSPF
STMF(’/etc/ibm/director/twgagent/twgagent.uid’)
For Common Agent managed systems, run the following

command: DSPF STMF(’/etc/TIVGUID’)
Note: Alternatively, use the following command to create a
spoolfile that contains the viewable TIVGUID: SBMJOB CMD(CALL
PGM(QCASNATIVE/GUID) PARM(’-show’)) JOBD(QCPMGTDIR/QCPMGTDIR)
Windows For all mirrored systems, compare the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
ComputerName\ComputerName\TWGMachineID
Note: The UID is displayed in reverse byte order.
For Common Agent managed systems, from the \Program

Files\tivoli\guid directory, run tivguid.exe -Show.
2. For all mirrored systems, remove the UID entry that might have been
duplicated. For instructions to remove a resource, see the topic "Removing a
resource".
AIX, Linux Run the following command: rm -f /etc/ibm/director/twgagent/
twgagent.uid
IBM i (formerly Remove the following file: /etc/ibm/director/twgagent/
i5/OS) twgagent.uid

Windows For all mirrored systems, delete the following value in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
ComputerName\ComputerName key
Value: TWGMachineID
3. For Agentless managed systems, proceed to step 4 on page 179. For Common
Agent managed systems generate a new Tivoli GUID and a new UID. For
Platform Agent managed systems, generate a new UID:
AIX, Linux Run the following command:
v For AIX: /opt/ibm/director/bin/genuid
v For Linux: /opt/ibm/platform/bin/genuid
And, for Common Agent managed systems, also run the following
commands:
1. /opt/ibm/director/agent/runtime/agent/bin/endpoint.sh
stop
2.
v For AIX: LANG=C;/usr/tivoli/guid/tivguid -Write -New
v For Linux: LANG=C;/opt/tivoli/guid/tivguid -Write -New
3. /opt/ibm/director/agent/runtime/agent/bin/endpoint.sh
start
4. Delete these files:
/opt/ibm/director/agent/data/collectioncache.txt
/opt/ibm/director/agent/data/providercache.txt
/opt/ibm/director/agent/conf/.settings/instancecache/*
/opt/ibm/director/agent/data/instancecache/*
IBM i For Platform Agent managed systems, restart the platform agent.
For Common Agent managed systems, perform the following

steps:
1. Run the following command to stop the Platform Agent:
ENDTCPSVR SERVER(*CIMOM)
2. Run the following command to stop the Common Agent:
ENDTCPSVR SERVER(*HTTP) HTTPSVR(CAS)
3. Run the following commands:
a. SBMJOB CMD(CALL PGM(QCASNATIVE/GUID) PARM(’-Remove’))
JOBD(QCPMGTDIR/QCPMGTDIR)
b. SBMJOB CMD(CALL PGM(QCASNATIVE/GUID) PARM(’-Create’))
JOBD(QCPMGTDIR/QCPMGTDIR)
4. Use the following command to start the Platform Agent:
STRTCPSVR SERVER(*CIMOM)
5. Use the following command to start the Common Agent:
STRTCPSVR SERVER(*HTTP) HTTPSVR(CAS)

Windows For Common Agent managed systems, run the following
commands:
v From the C:\Program Files\tivoli\guid\ directory, run
tivguid.exe -Write -New
v From the C:\Program Files\IBM\Director\bin\ directory, run
GENUID.exe
For Platform Agent managed systems, from the C:\Program
Files\IBM\Director\bin\ directory, run GENUID.exe
4. If the mirrored system does not use SSH, go to step 10 on page 180.
5. If you must determine the SSH key, run the following command: ssh-keygen
-lf /etc/ssh/ssh_host_rsa_key.pub.
6. If the mirrored system uses SSH, stop ssh:
AIX Run the following command: stopsrc -s sshd
Linux Run one of the following commands:
v /etc/init.d/sshd stop
v service sshd stop
IBM i The command you must run depends on which version of the
operating system you are running. For more information, see IBM
Portable Utilities for i.
Windows Consult the documentation for the SSH client that you are using.
7. Delete the SSH host keys:
AIX, Linux Run the following commands:
1. rm /etc/ssh/ssh_host_key
2. rm /etc/ssh/ssh_host_rsa_key
3. rm /etc/ssh/ssh_host_dsa_key
IBM i The command syntax depends on which version of the operating
system you are running. For more information, see IBM Portable
Utilities for i.
Windows Delete the following files:
v C:\Program Files\OpenSSH\etc\ssh_host_rsa_key
v C:\Program Files\OpenSSH\etc\ssh_host_dsa_key
8. If your SSH client requires that you explicitly regenerate the SSH host keys,
run the commands to regenerate them.
Note: Some SSH clients require that you run specific commands to regenerate
the SSH host keys, but some regenerate the SSH host keys when you restart
SSH.

AIX, Linux Run the following commands:
Note: In the following commands, " represents two single
quotation mark characters (').
1. /usr/bin/ssh-keygen -f /etc/ssh/ssh_host_key -N ’’ -t
rsa1
2. /usr/bin/ssh-keygen -f /etc/ssh/ssh_host_rsa_key -N ’’ -t
rsa
3. /usr/bin/ssh-keygen -f /etc/ssh/ssh_host_dsa_key -N ’’
-t dsa
IBM i How you regenerate the SSH host keys depends on which version
of the operating system you are running. For more information, see
IBM Portable Utilities for i.
Windows Determine if you must manually regenerate the SSH host keys by
consulting the documentation for the SSH client that you are using.
9. Restart the SSH service:
AIX Run this command: startsrc -s sshd
Linux Run one of the following commands:
v /etc/init.d/sshd start
v service sshd start
IBM i The command syntax depends on which version of the operating
system you are running. For more information, see IBM Portable
Utilities for i.
Windows Consult the documentation for the SSH client that you are using.
10. For Agentless managed systems, go to the next step.

For Common Agent managed systems, follow these steps:
a. Stop Common Agent Services by running by running the appropriate
command:
Windows: <install_directory>\IBM\Director\agent\runtime\agent\
bin\endpoint.bat stop
Linux: /opt/ibm/director/agent/runtime/agent/bin/endpoint.sh stop
b. Stop IBMSA and tier1slp by running net stop ibmsa. Respond Yes to the
prompt that asks to stop tier1slp.
c. Start IBMSA by running net start ibmsa.
d. Start tier1slp by running net start tier1slp.
e. Start Common Agent Services by running the appropriate command:
Windows: <install_directory>\IBM\Director\agent\runtime\agent\
bin\endpoint.bat start
Linux: /opt/ibm/director/agent/runtime/agent/bin/endpoint.sh
start
11. Run system discovery to discover the cloned system:
a. In the IBM Systems Director Web interface, click Inventory > System
Discovery.
b. Specify either the IP address or the host name of the cloned system, then
click Discover Now.

12. If the endpoint was incorrectly mirrored previously, you must reauthenticate
to the newly mirrored system and any other endpoints that might have been
merged with it.
Related concepts:
Discovery protocols
Related tasks:
Removing a resource
Related reference:
reset_diragent_keys command
Managing systems that have duplicate SSH keys

For IBM Systems Director to identify a managed system, the system must provide
unique keys. However, sometimes the SSH key on AIX systems is not unique. If
possible, use the reset_diragent_keys command to change the SSH keys to make
them unique. If you cannot change the SSH keys, follow these instructions.
Important:
v If a managed system duplicates the SSH key for the operating system that hosts
Systems Director server, do not follow these steps. Do not reset the SSH keys or
UID on the Systems Director server, and do not remove the operating system
from Systems Director. If this happens, contact Support.
v If you ran discovery and did not follow these steps first, Systems Director
discovers the systems with duplicate SSH keys, but treats them as one system.
To fix this, follow the steps in “Getting rid of duplicate entries” on page 182.
For Systems Director to manage an AIX system that has duplicate SSH keys,
complete these steps:
v Set the universal ID (UID) for the Systems Director agent to a unique value.
v Omit the SSH protocol when discovering the AIX system.
Follow these steps to reset the agent UID and discover the system without the SSH
protocol:
1. Run this command to display the UID: od –t x1 /etc/ibm/director/
twgagent/twgagent.uid.
2. If the UID is duplicated with the IBM Systems Director Server Server or
another server that is managed by Systems Director, run these commands to
remove and reset it:
rm –f /etc/ibm/director/twgagent/twgagent.uid
/opt/ibm/director/bin/genuid
3. Register the system to Systems Director by using one of these methods. It must
be registered without discovering the SSH protocol.
v Run the configure.sh command from the system as follows. Specify the
following on one line:
/opt/ibm/director/runtime/agent/toolkit/bin/configure.sh
-amhost agent_manager
-passwd agent_registration_password
-force
The variables have the following values:

agent_manager
IP address or network name of the system where the agent manager
is installed. This is typically the Systems Director management
server.
agent_registration_password
The password that was specified when the configAgtmgr.sh
command was run.
v Use a customized Systems Director discovery profile to add the system to
Systems Director without SSH protocol discovery.
There are several pre-defined discovery profiles, including Default Common
Agent discovery. These profiles are set up to run discovery on the subnet
that Systems Director is installed on. To specify a different IP address, copy
and edit the profile. See “Editing, copying, and deleting discovery profiles”
for details.
Related tasks:
Editing, copying, and deleting discovery profiles
Getting rid of duplicate entries

To determine whether this issue exists, list the discovered operating systems in
Resource Explorer. If it lists IP addresses for an operating system that are
associated with a different system, run the following commands. These commands
are further described in “Agent Manager Toolkit Usage”.
1. Remove all duplicated operating system resources from Systems Director. For
instructions, see “Removing a resource”.
Important:
v If a managed system duplicates the SSH key for the operating system that
hosts Systems Director server, do not follow these steps. Do not reset the
SSH keys or UID on the Systems Director server, and do not remove the
operating system from Systems Director. If this happens, contact Support.
v If you ran discovery and did not follow these steps first, Systems Director
discovers the systems with duplicate SSH keys, but treats them as one
system. To fix this, follow the steps in “Getting rid of duplicate entries.”
2. Log in as root or Administrator, navigate to AgentManager_Home/toolkit/bin
and run this command:
./RetrieveAgents.sh –toolkitPassword password
The toolkit password is the Resource Manager password that was defined
when the configAgtmgr.sh command was run during the Systems Director
install.
A list of all agents is shown.
3. Look for agents that have the wrong IP addresses for the hostname. These
agents need to be removed.
4. Run the LogicallyDeleteAgents command for each agent that needs to be
removed. This command sets the identified agents to be expired:
./LogicallyDeleteAgents.sh –toolkitPassword password -me management_element_ID
The management element ID is listed in the RetrieveAgents output.

install.
5. Run the PurgeAgents command for each agent that needs to be removed. This
command removes the expired agent from the Agent Manager:

./PurgeAgents.sh –toolkitPassword password
install.
6. Follow the steps in the previous section to reset the ssh key or UID on all
duplicate servers.
7. Follow the steps in the previous section to rediscover and re-access each
managed system.
Discovering IMMs for managing and updating physical servers

If it has been discovered correctly, an integrated management module (IMM) can
be used to update a target physical server. If these steps are not done correctly, you
cannot use the IMM to update the target endpoints.
A VMWare operating system installed on the physical server has a separate IP

address and must be discovered separately. Therefore, to manage all virtual and
physical components within a physical server managed by an IMM, you must
perform two separate discoveries: one for the IMM and another for the operating
system.
Note: The order of discovery does not matter, but the System Discovery task has
to be run once for each of the IP addresses.
Follow these steps to discover the operating system first. To discover the IMM first,
use the information in “Viewing system discovery results”. After discovering the
IMM, discover the virtual operating system as usual.
1. Discover the operating system-managed endpoint by using its IP address.
For example, if you have an ESXi VMware operating system, this is the address
that you use to contact ESX.
2. Log in with an ID that has administrator privileges and request access to the
operating system. Ensure that the operating system is unlocked completely.
Additionally, the physical server-managed endpoint access status should be
“OK”.
3. Collect inventory. Before continuing, ensure that the inventory is collected
without errors.
4. Use the IMM IP address to discover the IMM. This IP address should be
different from the operating system’s IP address.
5. Use the IMM credentials to unlock the physical server from step 2.
6. Collect inventory for the IMM.
The IMM is now listed with a machine type of “Integrated Management
Module”. It can now be used to send updates.
Note: In all, there are at most three managed endpoints:

v Operating system.
v Physical server. This is also the server managed endpoint for the IMM.

Related tasks:
Viewing system discovery results
Discovering VIOS servers managed by an HMC

Follow these steps to discover and access VIOS servers that are managed by a
Hardware Management Console (HMC).
Important: Do not manually discover a VIOS that is managed by an HMC. Doing

so might cause problems, for example, Systems Director might not be able to
access the VIOS correctly.
Follow these steps to discover the HMC and VIOS servers:

1. Ensure that your HMC is enabled for discovery. For instructions, see
“Preparing Hardware Management Console devices for discovery with IBM
Systems Director”.
2. In the IBM Systems Director interface, click Inventory > System Discovery.
3. Specify the appropriate information to discover the HMC. When the HMC is
discovered, the name is displayed in the Discovered Systems table, with “No
access” listed.
4. Right-click the name of the HMC and select Security > Request access.
5. Enter the user ID and password for the HMC and click Request access.
The requested HMC is now displayed with the Access value of OK. Next,
Systems Director automatically discovers the VIOS servers that the HMC
manages.
6. Run inventory on the HMC.
Related tasks:
Preparing HMC devices for discovery
Discovering the operating systems that have vCenter

installation
Follow the steps to discover the operating systems that have vCenter installation.
To discover the operating systems where vCenter is installed, complete the

following steps:
1. Ensure that the vCenter service is running on the operating system
2. In the IBM Systems Director interface, click Inventory > System Discovery.
3. Specify the appropriate information to discover the operating system. When the
operating system is discovered, the name is displayed in the Discovered
Systems table with No access.
4. Right-click the name of the system and select Security > Request access.
5. Enter the user ID and password for the OS and click Request access. The
operating system is now displayed with the Access value set to OK. The IBM
Systems Director automatically discovers and requests access to the host servers
that VCenter manages.
You can check whether the vCenter is discovered. To ensure that the vCenter is
discovered, right click the Operating System Management endpoints, select

Security > Config Access to check the Remote Service Access Points (RSAP). The
RASP shows a vCenter in the list, and the URL of RSAP is like https://ip:port’.
By default, the port is 443.

Viewing the systems and other resources discovered during and after discovery is
an important aspect of performing system discovery.
Generally, use the System discovery page to view results of a running discovery
task and use the Discovery jobs task to view results of a previous discovery task.
When you are viewing results of a system discovery, keep in mind the following
points:
v The discovery process discovers only systems and other types of resources that
can be managed by IBM Systems Director. In other words, just because you can
"ping" a resource does not mean that IBM Systems Director can discover it.
v Some results indicate multiple IP addresses on the same discovered resource that
might represent separate operating systems, components, or other items.
Consider the following examples:
– Results indicate two IP addresses for a particular server that uses an
integrated management module (IMM). In this case, one IP address represents
the external IP of the IMM and the other IP address is a USB network
connection. Both discovered resources are valid.
– Results indicate multiple operating systems for a particular server that uses
more than one network interface card. In this case, successfully requesting
access to the discovered resources removes multiple occurrences of the
operating system.
v The discovery process might create an operating system resource for any device
that supports the Secure Shell (SSH) protocol. For example, discovery results
might show a IBM BladeCenter chassis resource and an operating system
resource for a single managed resource (the chassis). If that managed resource is
not an operating system (for example, a switch, storage device, or BladeCenter
chassis), then the associated operating system resource is invalid. Either ignore
or remove the associated operating system resource. Requesting access to such
an invalid operating system resource might lead to errors and further confusion.
Using system discovery to view current results

Use the System Discovery task to view a table that contains the results of your
current system discovery task.
To use the System Discovery task to view the system discovery results as you
discover systems, complete the following steps:
2. Discover systems by using one of the available methods.
3. View systems as they are discovered in the Discovered Manageable Systems
table.
Note: When you are viewing results of a system discovery, consider the
following items:
v Displayed results include resources discovered by other IBM Systems
Director users who are accessing the same management server to perform
discoveries. So the Discovered Manageable Systems table displays results
that might include additional resources that are not located at the target IP
addresses or host names that you expect.
v When you click New Discovery to run a new discovery while a previous
discovery is still running, the Discovered Manageable Systems table does
not include results for the previous discovery. To view results for the
previous discovery, you must use the Discovery Jobs task or the Active and
Scheduled Jobs task.
After the discovery process completes, all the discovered manageable systems are
displayed in the Discovered Manageable Systems table. The table maintains the
information until you close the Systems Discovery page, at which time it is cleared.
Note: Any discovered manageable system also is listed in one or more groups on
the Resource Explorer page.
Related concepts:
System discovery
Related tasks:
Using discovery jobs to view previous results

Use the Discovery Jobs task to view the results of a specific system discovery task
that ran previously or one that is running. For IBM Systems Director to retain the
results of a specific system discovery task, the job under which the task ran must
still exist.
To use the Discovery Jobs task to view the results of a specific system discovery
task, complete the following steps:
2. Under Advanced Tasks, click Discovery jobs. The Active and Schedule Jobs
page displays. The entries in the Discovery jobs table include only those jobs
under which system discovery tasks ran.
Note: By using the Discovery Jobs task, the Active and Scheduled Jobs page
displays the Discovery jobs table, which displays only discovery-related jobs. If
you use the Active and Scheduled Jobs task, the resulting Active and
Scheduled Jobs table lists all jobs, including those jobs that are not related to
system discovery.
3. In the Discovery jobs table, click the job that represents the system discovery
for which you want to view the results. The properties page for the selected
entry displays.
4. Click the Discovered Systems tab to view the Discovered Manageable
Systems table, which contains results for the system discovery task.
Each system discovery task runs under a specific job. If that job is not deleted, you
can use the Discovery jobs task to view results for the associated system discovery.
Note: Typically, it is easier to use the System Discovery page to view the results of
a currently running system discovery task. However, when you click New
Discovery on the System Discovery page to run another discovery while the
previous discovery is still running, you must use the Discovery Jobs task (or the
Active and Scheduled Jobs task) to view results for the previous discovery.
Related concepts:
Related tasks:
Managing discovery profiles

Use the Managing Discovery Profiles page to create a unique discovery profile,
create a profile based on an existing profile, edit an existing profile, or delete one
or more profiles.
Related concepts:
System discovery
Discovery profiles

Use the Manage Discovery Profiles page to create a discovery profile. You can
create a unique profile or you can create a profile that you base on an existing
profile.
Before you start creating a profile, determine if a profile exists that at least in part
suits your needs. For example, IBM Systems Director for 6.2 includes several
default profiles created to find specific types of resources. To examine a default
profile more closely, on the Manage Discovery Profiles page, select the profile that
you want to examine, then click Edit. (Using Edit on a default profile enables you
to examine all the profile settings, but it does not allow you to change any of
them.)
To create a discovery profile, complete the following steps:

2. Under Advanced Tasks, click Manage discovery profiles. The Manage
Discovery Profiles page is displayed.
3. On the Manage Discovery Profiles page, use one of the following methods to
start the Discovery Profile wizard.
v To create a unique discovery profile, click Create.
v To create a profile that is based on an existing profile, select the profile that
you want to copy, then click Create Like.
You can use Create Like with a default profile to easily alter the IP addresses
settings to find specific resources at new addresses that you specify.
4. Use the Discovery Profile wizard to create and save your discovery profile.
After you exit the Discovery Profile wizard, the new discovery profile appears in
the Discovery Profiles table on the Manage Discovery Profiles page and in the list
of available profiles to run on the System Discovery page.

Related concepts:
System discovery
Discovery profiles
Related tasks:

Use the Manage Discovery Profiles page to create a unique discovery profile, create
a discovery profile like an existing profile, edit a profile, or delete a profile.
To edit or delete a discovery profile, or to create a profile based on an existing

profile, a discovery profile must exist. You can also use this page to create a unique
discovery profile that you then can manage. See “Creating a discovery profile” for
instructions.
To edit or delete a discovery profile, or to create a profile based on an existing

profile, complete the following steps:
2. Under Advanced Tasks, click Manage discovery profiles. The Manage
Discovery Profiles page is displayed.
3. On the Manage Discovery Profiles page, select one of the following actions.
Note: When working with discovery profiles, you can select one or more
profiles at a time. If you select multiple profiles, you have only the options of
running them or deleting them.
Table 15. Discovery profile actions
Create a discovery profile based on an 1. Select the profile on which you want to
existing profile base the new discovery profile.
2. Click Create Like. The Discovery Profile
wizard is displayed. The profile name
defaults to Copy of (original profile name),
but the remaining fields retain the same
values and selections as the original
profile.
3. Edit the profile properties as needed,
clicking Next to continue through the
wizard.
4. Click Finish to exit the wizard. The new
discovery profile appears in the
Discovery Profiles table on the Manage
Discovery Profiles page and in the list of
available profiles to run on the System
Discovery page.
Edit an existing discovery profile 1. Select the profile that you want to edit.
2. Click Edit. The Discovery Profile wizard
is displayed.
wizard.
4. Click Finish.

Table 15. Discovery profile actions (continued)
Delete an existing discovery profile 1. Select the profile that you want to delete.
2. Click Delete. A confirmation message is
displayed.
3. Click OK in the confirmation message
box to delete the selected profile. The
deleted profile no longer appears in the
Discovery Profiles table on the Manage
Discovery Profiles page or in the list of
available profiles to run on the System
Discovery page.
Note: Any scheduled event that uses a
deleted profile continues to run as
scheduled. When the scheduled event tries
to run the deleted profile, the event fails.
Related concepts:
System discovery
Discovery profiles
Related tasks:
Permanently excluding IP addresses from discovery

Attempting to discover resources at IP addresses that you do not want to discover
or cannot manage takes extra time and can negatively affect discovery
performance. When you have many IP addresses that you want all future
discoveries to permanently ignore, consider updating IP preferences for the
management server. Updating the IPPreference.properties file causes all future
discoveries to ignore the specified IP addresses, but also prevents IBM Systems
Director from communicating with or managing the IP addresses.
Note: Before editing the IPPreference.properties file, consider carefully whether

you want to prevent Systems Director from communicating with or managing the
specified IP addresses. If you want only the discovery process to ignore the IP
addresses without disrupting the ability of Systems Director to communicate with
the IP addresses, use a discovery profile to exclude the IP addresses. You can
configure a discovery profile to import a file that specifies the IP addresses to
exclude. By using the imported file, discovery ignores the excluded IP addresses
only when running the associated profile. For more information, see “Import
address file”.
Consider having Systems Director permanently ignore IP addresses only if at least

one of the following conditions applies:
v The specified IP address or address range represents one or more multiple
network interface cards that you want to prevent communicating withSystems
Director
v The specified IP address or address range represents one or more resources
thatSystems Director cannot manage or resources that you do not want Systems
Director to manage
v The specified subnet is not one that Systems Director uses to manage resources

You can exclude one or more individual IP addresses, an address range, or an
entire subnet. For example:
v When a managed resource has multiple network interface cards, exclude all but
the IP address that Systems Director uses to communicate with the resource.
v When managed resources are on more than one subnet, exclude the subnet that
Systems Director does not use to manage resources.
To permanently exclude IP addresses, perform the following steps:

1. Use a text editor to open an empty file named IPPreference.properties in the
following location: install_path/data/IPPreference.properties
where
install_path is the path where you installed IBM Systems Director Server.
Note: If the /data/IPPreference.properties file exists, open the file with a text
editor, then go to the next step.
2. Type the IP addresses that you want to exclude:
com.ibm.director.endpoint.excluded.ip.prefix=<IP_addresses>
where IP_address is one or more IPv4 or IPv6 addresses or address ranges that
you want to exclude.
v To exclude one or more individual IP addresses, use a comma character (,) to
separate the IP addresses:
com.ibm.director.endpoint.excluded.ip.prefix=192.168.53.1,192.168.53.22
v To exclude an IP address range:
com.ibm.director.endpoint.excluded.ip.prefix=192.168.53.1-192.168.53.150
v To exclude a subnet, use the asterisk character (*) as a wildcard:
com.ibm.director.endpoint.excluded.ip.prefix=192.168.*
Note:
v All entries in the IPPreference.properties file must be on the same line.
v To insert a comment, begin the line with a number (#) character.
3. Save and close the file.
For Systems Director to ignore the excluded IP addresses, you must restart the
management server.
Related concepts:
IP addresses
Import IP address file format
Collecting and viewing inventory data

Inventory collection is the process by which IBM Systems Director Server establishes
connections with network-level resources, such as computers, switches, or printers,
that have already been discovered and collects data about the hardware and
software that is currently installed on those resources. Use the View and Collect
Inventory task to view and manage an extended set of resources and relationships
for network-level resources that have already been discovered.
Before you can collect inventory for a resource and view the inventory data, you
must discover the resource by using System Discovery and also have access to it.

Related tasks:
Related reference:
Inventory troubleshooting
Inventory data and collection profiles

IBM Systems Director uses inventory collection profiles to collect inventory data
from discovered resources.
After you collect inventory, you can view the inventory items, their attributes, and
the values of those attributes by using the Refresh View option. The inventory
items that are displayed include physical, logical, and virtual hardware; software
applications, operating systems, middleware, firmware, BIOS, and diagnostic
information; network information; and system-contained resources.
Note: You must discover a management module, such as CMM, before inventory
items can be displayed. You cannot use SNMP to retrieve the information.
Inventory data comprises three parts: inventory item, inventory attribute, and
inventory value.
Inventory item
A distinct part of a resource that makes up the whole. The inventory item
might fall into the following categories: basic system information,
hardware inventory, or software inventory. For example, hardware
inventory might include a physical card as an inventory item.
Inventory attribute
The details about an inventory item, for example, the attributes for a
physical card might include the name, the date it was last changed, a
description, FRU number, manufacturer date, physical element
manufacturer, physical element model, physical element serial number, and
more.
Inventory value
The data associated with the inventory attribute, for example, the name of
a physical card, or the serial number of the physical card.
IBM Systems Director uses profiles to manage the inventory collection tasks that
you create and run. An inventory collection profile is a group of settings that are
saved on IBM Systems Director Server that indicate the type of resources collected
during the collection process. Using IBM Systems Director Web interface, you can
run an inventory collection profile on specific systems (targets), and you can
schedule a profile to run at specific times or in response to specific events.
Inventory profiles make it possible to collect only a subset of all available
information, which reduces network traffic and speeds up collection.
By default, IBM Systems Director includes the following inventory collection

profiles:
All Inventory
This profile collects inventory from all resources and encompasses all the
other inventory collection profiles.

Note: The All Inventory profile is the one you must run if you intend to
use update manager.
All Hardware Inventory
This profile collects inventory from physical and virtual devices.
All Software Inventory
This profile collects inventory from software resources.
Basic System Information
This profile collects inventory from system resources.
These profiles are read-only. They cannot be deleted or edited. They can, however,
be copied. You can use the existing profiles to create your own profiles by using
the Create like option. Or you can create your own inventory collection profile
without any preconfigured settings by using the Create option.
Related concepts:
Update manager
Creating an inventory collection profile

Use the Create Inventory Profile wizard to create an inventory collection profile.
If you do not want to use any of the profiles that are shipped with IBM Systems
Director, you must create and configure a profile that meets your needs before
collecting or viewing inventory.
To create an inventory collection profile, perform the following steps:

1. Open the View and Collect Inventory page as follows:
v On the Home page, click Collect inventory.
The View and Collect Inventory page is displayed.
2. Click Manage Profiles. The Manage Inventory Profiles page is displayed,
listing the existing inventory collection profiles.
3. Click Create. The Create Inventory Profile wizard opens.
4. In the Profile Name field, type a descriptive name to identify the profile.
5. In the Profile Description field, optionally type a brief description for the
profile.
6. Click Next. The Inventory Selection page displays a hierarchical tree of the
types of resources for which IBM Systems Director can collect inventory.
7. Navigate to and select the group or resource type that you want to add.
Note: You can add an entire group of resource types or you can select them
individually.
8. Click Add.
9. Continue adding resource types to the profile as needed.
10. Click Next. Either the Discovery Service page or the Options page is
displayed. If the Discovery Service page is displayed, proceed to the next step.
If the Options page is displayed, proceed to step 16 on page 193.
11. Select the option that reflects your decision about whether you want to
configure the discovery services or have the system choose the services for
you, then click Next.
v If you select Let me manually configure the discovery services, the Module
Selection page is displayed. Proceed to the next step.

v If you select Let the system choose the discovery services, the Options
page is displayed. Proceed to step 16.
12. Select the discovery modules that you want to configure to discover
additional attributes on your resources.
13. Click Next. Pages for each of the discovery modules that you selected are
displayed.
14. Complete the pages for each discovery module.
15. Click Next. The Options page is displayed.
16. In the Timeout period field, type the number of minutes that you want to
allot before an inventory collection event terminates. From the Inventory
Collection Profile list, select the inventory collection profile that you want to
use. The timeout value indicates the length of time to wait for a response to
inventory collection communications that are sent to systems. If the timeout
value elapses before the response is received from the destination, no
inventory data is collected from that target.
17. In the Maximum simultaneous collections field, type the maximum number
of agents from which IBM Systems Director Server can simultaneously collect
inventory.
Note: To help reduce network traffic, specify the lowest possible number of
agents.
18. To instruct IBM Systems Director Server to automatically try again after failed
collection attempts, select Retry failed agents.
19. Click Next. The Summary page is displayed.
20. Click Finish.
After creating an inventory collection profile, you can run it from the View and
Collect Inventory page.
Related concepts:
Related tasks:
Managing inventory collection profiles

Use the Manage Inventory Profiles page to copy, edit, or delete inventory collection
profiles.
To copy, edit, or delete an inventory collection profile, the profile must already
exist. You can also use this page to create a new inventory collection profile that
you can then manage. See “Creating an inventory collection profile” for
instructions.
To copy, edit, or delete an inventory collection profile, complete the following

steps:
2. Click Manage Profiles. The Manage Inventory Profiles page is displayed,
listing the existing inventory collection profiles.
3. On the Manage Inventory Profiles page, select one of the following actions.

Note: When working with inventory collection profiles, you can select one or
more profiles at a time. If you select multiple profiles, you have only the
options of running them or deleting them.
Table 16. Inventory collection profile actions
Copy an existing inventory collection profile 1. Select the profile that you want to copy.
2. Click Create like. The Create Like
Inventory Profile wizard is displayed.
The profile name defaults to Copy of
(original profile name), but all the rest of
the fields are populated with the same
entries and selections as is in the original
profile.
wizard.
4. Click Finish. The new profile based on
the original profile will appear in the
table on the View and Collect Inventory
page.
Edit an existing inventory collection profile 1. Select the profile that you want to edit.
2. Click Edit. The Edit Inventory Profile
wizard is displayed.
wizard.
4. Click Finish.
Delete an existing inventory collection 1. Select the profile that you want to delete.
profile 2. Click Delete. A confirmation message is
displayed.
3. Click OK in the confirmation message
box. The selected profile is deleted and is
no longer displayed in the table on the
View and Collect Inventory page.
Note: Any scheduled event that uses a
deleted profile will continue to run until it
tries to run the deleted profile, at which
point the event will fail.
Related concepts:
Related tasks:
Performing system discovery
Use the View and Collect Inventory task to collect inventory data for systems that
have already been discovered and accessed by IBM Systems Director Server.
Before you can view inventory for a resource, you must discover that resource
using System Discovery. Inventory collection uses inventory collection profiles. You
can use an existing profile to collect inventory for a system. If the inventory

collection profile does not exist for the type of inventory data you want to collect,
you must first create the inventory collection profile and make sure that it contains
the appropriate settings.
Note: Inventory is displayed for only those systems that are in a state other than
no access. To change the access state, select the system or systems and click
Actions > Security > Request Access.
To collect inventory for one or more systems, perform the following steps:
2. In the Target Systems list, select the system for which you want to view or
collect inventory data. If the target system that you want to view is not in the
target systems list, perform the following steps to add the system to the list.
a. Click Browse to open the Context Chooser. The Context Chooser displays a
list of system groups.
b. In the list of groups, drill down to the individual target system for which
you want to view inventory data in the group that contains that target
system.
Note: You can select the entire group or you can drill down to select
individual target systems as targets within a group.
c. Select one or more target systems that you want to add.
d. Click Add. The selected target systems are displayed in the Selected list.
e. Click OK.
3. In the View by list, select the inventory profile that you want to use.
4. Click Collect Inventory. The Run - Collect Inventory page is displayed.
5. Use the Run - Collect Inventory page to set up optional functions and options
of your inventory collection task:
Schedule
Use the Schedule tab to set the inventory collection task to run
immediately or at a specified time and date in the future. You can also
schedule the task to repeat at a specified frequency.
Notification
Use the Notification tab to specify options for an email notification that
you can receive as the inventory collection process progresses.
Options
Use the Options tab to specify the time to use for the system time and
how to handle unavailable systems.
6. When you are finished with the Run - Collect Inventory page, click OK. An
inventory collection job is created and an informational message is displayed
about the job.
Note: Click Display Properties if you want to view the properties of the job.
The Active and Scheduled Jobs page is displayed and provides information
about the job including status, progress, a list of targets, a history, and error
logs.
When inventory collection is completed, you can view the inventory data list and
table by clicking Refresh View.

Tip: To improve the performance of inventory collection and keep the system
resource usage to manageable levels, see the “Performance Tuning and Scaling
Guide for IBM Systems Director 6.3”.
Related concepts:
Related tasks:
Viewing inventory
Related reference:
Performance Tuning and Scaling Guide for IBM Systems Director 6.3
Comparing fixes installed on IBM i systems

You can select an IBM i system and compare its installed fixes to the fixes that are
installed on other IBM i systems. The result is exported as an HTML file.
The following steps use these terms:

Source system
The system that you want to compare to other systems.
Target systems
One or more systems that you want to compare the source system's fixes
to.
Follow these steps to compare the installed fixes:

1. Turn off any software to block pop-up windows in your web browser.
2. In Resource Explorer, select the source IBM i system.
3. Right click and select Inventory > Compare Installed Fixes.
4. From the Available list, select one or more target systems. Click Add to add
them to the Selected list. Click OK.
5. The system generates a report of differences between the source system's and
the target systems' installed fixes. The report is displayed in a new tab in your
browser.
Related reference:
cmpptfs command
Viewing inventory
Use the View and Collect Inventory task to view and manage an extended set of
resources and relationships for systems that have already been discovered. The
inventory that is displayed includes physical, logical, and virtual hardware;
software applications, operating systems, middleware, firmware, BIOS, and
diagnostic information; network information; and system-contained resources. Also,
IBM Systems Director displays the inventory data for the inventory items that are
collected.
Before you can view inventory data for a resource, you must collect the inventory
data for that resource.

Note: Inventory is displayed for only those systems that are in a state other than
no access. To change the access state, select the system or systems and click
Actions > Security > Request Access.
To display inventory data for a resource, complete the following steps:

2. In the Target Systems list, select the system for which you want to view or
collect inventory data. If the target system that you want to view is not in the
target systems list, perform the following steps to add the system to the list.
a. Click Browse to open the Context Chooser. The Context Chooser displays a
list of system groups.
b. In the list of groups, drill down to the individual target system for which
you want to view inventory data in the group that contains that target
system.
Note: You can select the entire group or you can drill down to select
individual target systems as targets within a group.
c. Select one or more target systems that you want to add.
d. Click Add. The selected target systems are displayed in the Selected list.
e. Click OK.
3. In the View by list, select the inventory profile that you want to use.
4. Click Refresh View. The inventory data for the selected resource is displayed.
Note: If you click Refresh View before any inventory has been collected by IBM
Systems Director Server, an empty table is displayed and the Last collected
value will be none. Before you try to view inventory, make sure that you
discover the applicable resources and collect the inventory for them.
Related concepts:
Related tasks:
Inventory collection metadata file (twguser.ini)

Use inventory collection metadata to more easily group inventory data collected
from managed resources. You can specify inventory collection metadata on only
managed resources that are running a supported version of the Windows operating
system and that have common agent services (CAS) installed. The twguser.ini file
contains the inventory collection metadata.
The plain text file twguser.ini resides in the install_root/agent/data directory, where
install_root is the root directory of your IBM Systems Director installation. Use a
plain text editor to make changes to the twguser.ini file.
Using inventory collection metadata makes it easier to view, organize, and search
collected inventory. For example, using metadata allows you to associate collected
inventory for a system with a particular user, email address, building, or country.
To see inventory collection metadata, make sure to collect inventory for the
affected system after you update the twguser.ini file.

The following lists show the available metadata entries that are available in the
twguser.ini file and specifies the character length restrictions.
Important: Exceeding the character length restriction for even one entry prevents
inventory collection from using (and displaying) any of the metadata.
Table 17. User metadata entries and character length restrictions
User metadata entry Maximum number of characters
FIRST_NAME 256 total, including MIDDLE_NAME and
LAST_NAME
MIDDLE_NAME See FIRST_NAME
LAST_NAME See FIRST_NAME
EMPLOYEE_ID 128
TITLE 256
DEPT_NAME 128
DEPT_NUMBER 64
DIVISION 64
WORK_PHONE 25
CELLULAR_PHONE 25
FAX_NUMBER 25
PAGER_NUMBER 25
PAGER_TYPE 32
EMAIL_ADDRESS 512
HOME_PHONE 25
Table 18. Location metadata entries and character length restrictions

Location metadata entry Maximum number of characters
CITY 64
STATE 32
ZIPCODE 16
COUNTRY 32
BUILDING 64
FLOOR 32
ROOM_NUMBER 32
LATITUDE 16
LONGITUDE 16
USER_DATA1 Unsupported; do not use
USER_DATA2 Unsupported; do not use
Related tasks:
Viewing inventory
Exporting inventory data

You can export collected inventory data to a file in comma-separated value (CSV),
HTML, or XML format.
Be sure to turn off the Web browser option to block pop-up windows for the URL
that you use to log in to the IBM Systems Director Web interface.
Complete the following steps to export your collected inventory data:

2. Make sure to collect and view the inventory data that you want to export. For
more information about collecting and viewing inventory data, see “Collecting
inventory” and “Viewing inventory”.
3. Click Export All. The browser either opens a file download window or it
displays the exported data.
4. Save the file.
v If the Web browser opens a file download window, save the file. If the Web
browser requires a location selection, provide it and click Save.
v If the Web browser displays the exported inventory data, from the File
menu, click Save As, navigate to the location where you want to save the
file, then click Save.
Note: You can save the file only to a file system that is accessible from the
system running IBM Systems Director Server.
Related tasks:
Viewing inventory
Connecting to IT Registry and Context Menu Service databases

Connect to preexisting IT Registry and Context Menu Service centralized databases
to enable IBM Systems Director to accept external connections so that it can share
tasks and resources with external applications such as Tivoli products.
The IT Registry and Context Menu Service databases to which you want to connect
must already exist.
Using the IT Registry and Context Menu Service Registration page in the IBM
Systems Director Web interface, you can register with either or both an IT Registry
or Context Menu Service database. After initial registration, if you want to remove
the capability of products to start IBM Systems Director tasks, you can unregister
to remove all connection settings and previously registered data for tasks and
resources for the currently connected IT Registry and Context Menu Service
databases. You can also register again to connect to different IT Registry and
Context Menu Service databases.
Note: The Context Menu Service does not support using the IBM DB2 server that
is installed and managed by Systems Director. Using IBM DB2 as the target
database for Context Menu Service requires a separate installation of IBM DB2.
1. Set up the JDBC jars for the database that you are using.
a. Obtain the JDBC jars by using one of the following two methods:
v Copy the JDBC jars from the installed instance of the database.
v Download the JDBC jars from the website for IBM DB2, Microsoft SQL
Server, or Oracle® Database.

b. Place the jars into the /lib directory of the appropriate plug-in for your
database:
Note: If you are using the same DBMS type for the Systems Director
database, the jars already exist in the plug-in, so you do not need to copy
them.
v com.ibm.lwi.database.drivers.db2_8.1.0.0-LWI
v com.ibm.lwi.database.drivers.oracle_8.1.0.0-LWI
v com.ibm.lwi.database.drivers.sqlserver_8.1.0.0-LWI
The plug-ins are located under install_root/lwi/runtime/database/
eclipse/plugins, where install_root is the root directory of your IBM
Systems Director installation.
c. Open the MANIFEST.MF file in the META-INF directory of the plug-in and
ensure that the Bundle-Classpath entry in that file contains the exact name
of the JDBC jars placed in the /lib directory. If the Bundle-Classpath entry
is incorrect, edit MANIFEST.MF to include those jar names, then save the
changes.
2. In the IBM Systems Director Web interface, navigate to Settings -> IT Registry
and CMS Registration.
3. On the IT Registry and Context Menu Service Registration page, complete the
steps for the action that you want to take:
Register with IT Registry and Context Menu Service databases for the first
time Complete the following steps to register with IT Registry and Context
Menu Service databases for the first time.
Note: You must register an application on all servers that will use it.
a. Complete all of the required fields with the connection settings for
the IT Registry database and the Context Menu Service database.
b. Click Test Connections to test if the connection settings that you
entered are valid. If the connection test fails, check your entered
values.
c. Click Register to apply the connection settings to register with the
targeted IT Registry and Context Menu Service databases.
Unregister with IT Registry and Context Menu Service databases
If you are already registered with IT Registry and Context Menu
Service databases but want to unregister, click Unregister. Clicking
Unregister removes all connection settings and previously registered
data for tasks and resources for the currently connected IT Registry and
Note: The fields already contain the connection settings for the
connection databases with which you are currently registered.
Register with different IT Registry and Context Menu Service databases
If you are already registered but want to change and connect to
different IT Registry and Context Menu Service databases, you can
register again by using the values for the new databases. You do not
need to unregister with the initial IT Registry and Context Menu
Service databases before reregistering.
Complete the following steps to register with different IT Registry and

Notes:
v The fields already contain the connection settings for the connection
databases with which you are already registered.
v Reregistration completes for both databases, regardless of whether
you changed values for either one.
a. Replace the contents of each applicable field with the connection
settings for the new IT Registry and Context Menu Service
databases.
b. Click Test Connections to test if the new connection settings that
you entered are valid. If the connection test fails, check your entered
values.
c. Click Register to apply the connection settings to register with the
new targeted IT Registry and Context Menu Service databases.
After IBM Systems Director registration is complete and the other product is also
enabled to use IT Registry and Context Menu Service, the IBM Systems Director
tasks will appear in the context menus of the other product and can be launched
by selecting that menu item.
Related reference:
Installing the IBM DB2 Driver for JDBC and SQLJ
Oracle JDBC/UCP Download Page
Microsoft SQL Server JDBC Driver 2.0
External connections with IT Registry and Context Menu

Service databases
IT Registry and Context Menu Service are databases with which IBM Systems
Director can register so that it can accept external connections and therefore share
tasks and resources with external applications such as Tivoli products.
After IBM Systems Director registration is complete and the other product is also
enabled to use IT Registry and Context Menu Service, the IBM Systems Director
tasks will appear in the context menus of the other product and can be launched
by selecting that menu item.
IT Registry
When you register with the IT Registry, entries are added to the IT Registry
database for resources that IBM Systems Director has discovered.
Context Menu Service
The Context Menu Service, which is a component of the Tivoli Integrated Portal
(TIP), facilitates launch-in-context capability between products. The
launch-in-context capability enables one application to invoke a function or launch a
user interface that is provided by another application while also passing in data
that the function or user interface can immediately process. Context Menu Service
enables launch-in-context by allowing a product to register launch points for itself
and locate launch points for other products. Launch points provide information that
allows an application to invoke a function or user interface from another
application.

When you register with the Context Menu Service, entries are added to the
Context Menu Service database so that other programs can start IBM Systems
Director tasks outside of IBM Systems Director.

Chapter 4. Configuring systems
Using configuration manager, you can configure both hardware devices and
systems so that they will work together and meet the needs of your environment.
Note: To use configuration manager, you must have smadmin authority.
In order for your configuration settings to take effect, they must be deployed to the
appropriate managed resource (device or system). When you deploy a
configuration plan, the configuration settings contained in all templates contained
by the plan are applied to the resource. In Current Configuration, you can list
configuration settings for one resource, make some or no changes to the settings,
then deploy it to a different resource.
You must understand the following terms to effectively configure systems using .
Configuration setting
a real-time value associated with one aspect of a device that can be saved
as a configuration template or plan. For example, login information or
SNMP options.
You can save configuration settings from a system and convert them into
configuration templates or configuration plans. You also can create
configuration settings from scratch.
Configuration template
A version of configuration settings that are not on a given system, but are
stored for future deployment.
You can deploy a configuration template on a system even if it is not a
member of a configuration plan.
Configuration plan
A set of configuration templates used to configure a system.
Configuration settings
A particular system's configuration can be accessed and viewed. Changes can be
made if necessary, and the configuration setting for an individual resource can be
stored as a configuration template or as a configuration plan.
Configuration settings for a whole system can be stored as a set of configuration

templates, which can then be placed in a configuration plan.
All specific configuration settings are described in the documentation for their
specific devices. As an example, the configuration settings for IBM BladeCenter
and System x are described in the documentation for IBM BladeCenter and System
x. The configuration settings for storage devices are described in the IBM Systems
Director Storage Systems documentation.

Related tasks:
Configuring templates
Managing storage with configuration templates
Configuration templates
A configuration template is a stored version of device parameters and settings,
which can be reused or deployed later.
You can create, view, edit, delete, deploy, and schedule configuration templates to
be deployed on a target resource.
Target types
A target type is the type of system on which a configuration template is deployed.
A configuration template can have one of the following target types. However, the
listed types might vary, depending on the installed settings in your environment:
BladeCenter chassis
BladeCenter H chassis
BladeCenter HT chassis
BladeCenter S chassis
BladeCenter T chassis
Ethernet Switch
Fibre Switch
IBM Flex System Enterprise Chassis
InfiniBand Switch
Operating System
Operating System (using CIM protocol)
Server (using CIM protocol)
Stand alone server
Storage Platform
Storage Switch
Tips:
v When you change a configuration template that is already contained in one or
more configuration plans, the changes apply to these configuration plans.
v If you want to delete a configuration template that is contained in one or more
configuration plans, remove that configuration template from all associated
configuration plans first, and then delete the configuration template.
You can delete a configuration template that is in one or more configuration
plans, but deleting the template generates a warning message.
v When you create a configuration plan, you can determine the order of the
configuration templates within the configuration plan. This order is not checked
at creation time to determine whether certain resources require that other
resources are defined first.
If an inappropriate order is chosen, errors might be issued when the
configuration plan is deployed. When you deploy a configuration plan, check
the status to determine whether it succeeded and analyze any errors received.

v You can automatically deploy certain types of templates. The order that they are
deployed in is specified in the automatic deploy sequence list for each template
type. This list can be modified at any time. Additionally, the list is modified
automatically when templates that specify automatic deployment are added (by
modifying the properties or creation of a new template), or deleted.
Note: You cannot automatically deploy network templates, and this extends to
the network plans that contain them.
Predefined configuration template

IBM Systems Director provides a predefined configuration template to help you
quickly configure a BladeCenter chassis resource.
Do not delete or modify the predefined configuration template. To modify the

predefined configuration template, use the Create Like task to make a copy, and
then change the copy.
Configuration plans
A configuration plan is used to configure systems and resources. A configuration
plan is a group of configuration templates that are deployed in a sequence.
A configuration plan has a name, a description, a plan target type, an indicator of

automatic deployment status, plan creation information, and plan modification
information. A configuration plan contains one or more configuration templates.
The configuration templates in a configuration plan can be specified in an order,
and will be deployed in this order when the configuration plan is deployed.
Some configuration plans can be set up to be automatically deployed when a new

resource of that type is discovered. You can also specify the order in which the
configuration templates in a configuration plan are deployed, for situations in
which some resources must be defined before others.
Note: You cannot automatically deploy network templates, and this extends to the
network plans that contain them.
Types
A type is the category of resource associated with a configuration plan. These are
the types for a configuration plan. All configuration templates within a given
configuration plan must also be of the same type as the configuration plan.
Chassis
Devices such as management modules and switches
Network
Network components
Server Server components
Storage
Storage devices and other related resources
Operating System
Operating system components
Chapter 4. Configuring systems 205

The Automatically deploy feature
This feature is used to automatically deploy a configuration plan or configuration
template when system changes, such as the addition or removal of hardware, are
detected by IBM Systems Director.
Note: You cannot automatically deploy network templates, and this extends to the
network plans that contain them.
An entire configuration plan or individual configuration templates can be
designated as automatically deploy. If an entire configuration plan is designated as
automatically deploy, whenever IBM Systems Director detects a new system or
device of that type, this entire configuration plan is automatically deployed on that
system or device.
There can be only one active configuration plan designated as automatically

deploy for each configuration plan type at any given time.
For example, assume that configuration plan plan1 and configuration plan plan2
are of the same plan type. If plan1 is already set to automatically deploy, and you
then designate plan2 as automatically deploy, plan2 will become designated as
automatically deploy for this plan type, and plan1 will no longer be designated as
automatically deploy. A warning will be displayed in this situation.
For an individual configuration template, automatically deploy means that

whenever IBM Systems Director detects a new device of the configuration template
type, the configuration template is automatically deployed on that device.
In addition to automatic deployment for a new device that is added to a system,

automatic deployment can also take place if a device is changed or removed. In
this case, automatic deployment is dependent on the values in the configuration
template or configuration plan that have been designated for automatic
deployment.
Predefined configuration plans

IBM Systems Director provides a predefined configuration plan to facilitate
configuration of some of the most popular resources and systems.
Do not delete these predefined configuration plans. Do not edit or change them. To
modify them, use the Create Like task, make a copy, and then change the copy. Do
not delete or modify the predefined configuration templates within the predefined
configuration plans.
Chassis Predefined Plan
This predefined configuration plan is for an IBM BladeCenter Chassis. It has one
predefined configuration template named Boot Sequence Predefined Template. To
see all relevant attributes, view this configuration plan and configuration template
from the IBM Systems Director Configuration Manager Summary page.
Configuration-setting license entitlement

Some configuration settings might be associated with a license entitlement. In
order to use the setting, and therefore any template or plan that contains that
setting, the license must be valid, that is, not expired. Not only must a
configuration setting have a valid license, but some licenses also require a license
for the system for which the configuration setting is intended.

If a license is expired, you will be prevented from using the affected configuration
setting. If a license is required for systems, you can be prevented from using the
affected configuration settings on unlicensed systems. If you have an expired
license, the following items are subject to these restrictions:
v Current configuration settings that have a license entitlement
v Configuration templates that contain a license entitlement configuration setting
v Configuration plans including at least one template containing a license
entitlement configuration setting
If one of these items contains a license entitlement setting that has expired, the
item can be deleted. If you attempt to edit, deploy, or use the template in any way,
a message is displayed notifying you to purchase a license.
Monitoring the deployment of configuration plans and configuration

templates
To monitor when a configuration plan or configuration template is deployed, use
an event automation plan.
To create the event automation plan, complete the following steps:

1. In the IBM Systems Director navigation pane, expand Automation and click
Event Automation Plans.
2. On the Event Automation Plans page, click Create.
3. The Event Automation Plan wizard displays the Welcome page. Click Next.
4. On the Name and description page, type a descriptive name for the event
automation plan that you are creating. Optionally, you also can type a
description of the plan. Click Next.
5. On the Targets page, select the systems that you want the event automation
plan to monitor for the configuration manager events. Select the systems in
the Available table and click Add to move them to the Selected list. Click
Next.
6. On the Events page, select Advanced event filters from the Events list.
7. Click Create to create an event filter.
8. The Create Event Filter wizard displays the Welcome page. Click Next.
9. On the Filter Name page, type a descriptive name for the event filter that you
are creating. Optionally, you also can type a description of the filter. Click
Next.
10. On the Filter Type page, select Simple event filter from the Filter type list.
11. On the Event Type page, select Custom from the Types of events to include
list. The Available Event Types table is displayed.
12. In the Available Event Types table, click Systems Director Program > System
Configuration. The table displays the available configuration manager events.
13. Select the applicable configuration manager event:
Option Description
To monitor for the deployment of Click Configuration Template, then select
configuration templates Deployed.
To monitor for the deployment of Click Configuration Plan, then select
configuration plans Deployed.
14. On the Event Type page, click Next.

15. On each of the remaining pages of the Create Event Filter wizard, until the
Summary page displays, accept the default selection and click Next.
16. On the Summary page, verify that the information is correct and click Finish.
The Events page displays the new filter.
17. On the Events page, make sure that the new filter is selected, then click Next.
18. On the Event actions page, click Create.
19. In the Create Actions window, select an event action, for example, Send an
e-mail (Internet SMTP) .
20. Click OK.
21. Complete the fields for the event action that you selected. For some event
action types, you can include event-specific information as part of the text
message. Including event information is referred to as event-data substitution.
You can use event-data-substitution variables to customize event actions. For
more information, see “Event-data-substitution variables.”
22. When you are satisfied with the settings, click OK.
23. On the Event Actions page, make sure that the new event action is selected,
then click Next.
24. On the Time range page, select the time over which you want to collect the
events. Select All the time (24 x 7) so that the plan is active all the time.
25. When you are satisfied with the specified time ranges, click Next.
26. On the Summary page, verify the details of the event automation plan. If you
want to change the settings, click Back.
27. When you are done editing the event automation plan, click Finish.
The Event Automation Plans page displays the new event automation plan.
Related concepts:
“The Automatically deploy feature” on page 206
“Configuration templates” on page 204
“Configuration plans” on page 205
Related tasks:
“Viewing configuration templates” on page 216
“Viewing configuration plans” on page 228
Managing system configuration

Manage your system configuration by viewing and making updates to
configuration settings. These configuration setting can be stored into configuration
templates, which can be grouped into configuration plans.
Note: Before changing the feature activation manager configuration on a switch,

for example, if you inventory, install, or remove license keys, you must specify
TFTP information on the IBM BladeCenter Update Settings page. For instructions,
see the topic “Specifying IBM BladeCenter update setting” in the information
center.

Related concepts:
“Configuration settings” on page 203
Viewing configuration settings

The configuration settings for a particular system contain detailed information
about the system, such as definitions, options, and attached devices.
To view the configuration setting for a particular system, complete the following
steps:
1. From the Resource Explorer area, select a system.
2. Click Actions > Properties to view the current properties of the system:
v If the system has resources that can be configured by IBM Systems Director,
a Configuration tab will be present.
v If the system does not have resources that can be configured by IBM Systems
Director, there will be no Configuration tab. You cannot perform any of the
remaining steps in this procedure.
v The communication state such as: online or offline, and access state such as
locked or unlocked will also determine if the configuration tab is displayed
for a system.
3. Click Configuration to see the configuration settings for this system.
As an alternative, you can start this task from the navigator area by selecting
System Configuration > Current Configuration
Related concepts:
Related tasks:
“Editing configuration settings”
“Saving configuration settings as configuration templates” on page 210
“Saving configuration settings to a configuration plan” on page 211
“Creating configuration templates” on page 213
“Creating a configuration template from an existing one” on page 214
Editing configuration settings

Edit the configuration setting for a particular system so that they remain current
and are kept up to date with hardware and software changes.
1. From the Resource Explorer area, select a system.
2. Click Actions > Properties to view the current properties of the system:
v If the system does not have resources that can be configured by IBM Systems
Director, there will be no Configuration tab. You cannot perform any of the
remaining steps in this procedure.

v The communication state such a: online or offline, and access state such as
for a system.
4. Select the configuration setting to be edited.
5. Click Edit. A page with the configuration setting information is displayed.
6. Make any necessary changes.
7. Click Deploy. The changes are applied, and you are returned to the list of
configuration settings for the system.
8. Click Close.
As an alternative, you can start this task from the navigator area by selecting
System Configuration > Current Configuration
Related concepts:
Related tasks:
“Viewing configuration settings” on page 209
“Saving configuration settings as configuration templates”
Saving configuration settings as configuration templates

In order to have the configuration setting for a particular device applied to another
resource, possibly one located on another system, you must save the configuration
setting as a configuration template.
To save a configuration setting as a configuration template, complete the following

steps:
1. From the Resource Explorer section, select a system.
2. Click Actions > Properties to view the current properties of the system.
v If the system does not have resources that can be configured by IBM
Systems Director, there will be no Configuration tab. You cannot perform
any of the remaining steps in this procedure.
v The communication state such a: online or offline, and access state such as
for a system.
4. Select the configuration setting to be saved as a configuration template.
5. Click Actions > Save as Configuration Template. The Save as Configuration
Template page is displayed.
6. Type a name for the new configuration template.
7. Type a description for the new configuration template.
8. Click Open configuration template list when finished saving if you want to
see the list of existing configuration templates while the save is taking place.

Although you will be taken to the Configuration template table, deploying
this newly-created configuration template from this table will require you to
select a target.
9. Optional: If you want to add the new configuration template to an existing
configuration plan of the same type, choose one from the list of configuration
plans. You are given the choice of configuration plans of the correct type.
10. Click Save. The Configuration Progress Indicator keeps you informed of the
progress of this task.
Related concepts:
Related tasks:
“Editing configuration settings” on page 209
“Adding configuration templates to a configuration plan” on page 218
“Saving configuration settings to a configuration plan”
Navigating tables
Saving configuration settings to a configuration plan

Use this procedure to save configuration settings to a configuration plan.
When you save configuration settings to a configuration plan, configuration

templates are created to contain the configuration settings. The configuration plan
that is produced is no different than one created starting with configuration
templates.
To save configuration settings to a configuration plan, complete the following

steps:
1. Click System Configuration > Current Configuration. A list of systems is
displayed.
2. Select a system.
3. Click Actions > View. A table of configuration settings for the chosen system is
displayed.
4. Select those configuration settings that you want saved to a configuration plan.
5. Click Save to Configuration Plan. The Save to Configuration Plan page is
displayed.
6. Choose the configuration plan for the configuration settings.
v Add selected configuration settings to an existing configuration plan. A list of
existing configuration plans is displayed. Choose one from this list.
v Add selected configuration settings to a new configuration plan. Type a
name and description for the new configuration plan.
7. Click Save.

The configuration settings added to the configuration plan might not be in the
order that you would want them to be deployed on a system. From any table that
displays the configuration plan, click Actions > Edit to change the order of the
configuration templates.
Related concepts:
Related tasks:
“Editing configuration settings” on page 209
Navigating tables
“Creating configuration plans” on page 224
“Viewing configuration plans” on page 228
Backing up configuration settings for a device

Follow these steps to back up a supported devices configuration settings.
Supported devices include IBM Flex System Enterprise Chassis with Chassis
Management Module (CMM) and x86 Blade systems with Integrated Management
Module (IMMv2). You can save all of the settings or a subset of the settings as a
configuration template, a CLI file, or a text file.
1. In the IBM Systems Director navigation panel, click Resource Explorer > All
systems.
2. Right click the system you want to work with and select System Configuration
> Backup and Restore.
3. The Backup and Restore window opens. Select the appropriate task and fill out
the panels as required.
Restoring configuration settings for a device

Follow these steps to restore configuration settings for a supported device.
Supported devices include IBM Flex System Enterprise Chassis with Chassis
Management Module (CMM) and x86 Blade systems with Integrated Management
Module (IMMv2). These settings can exist in a text file, or from a file created by
using the IBM Systems Director user interface.
1. In the IBM Systems Director navigation panel, click Resource Explorer > All
systems.
2. Right click the system you want to work with and select System Configuration
> Backup and Restore.
3. The Backup and Restore window opens. Select the appropriate task and fill out
the panels as required.
Note: User groups or accounts created on a resource after a configuration template

is deployed are not removed from the resource if you restore the configuration
settings by using the configuration template.

Managing configuration templates
You manage configuration templates by creating and updating them. They can be
deployed to a system, or grouped into configuration plans.
Related concepts:
Creating configuration templates

Create a configuration template to hold specific user-defined settings for a
configuration which can then be applied to relevant managed endpoints.
Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”
To create a configuration template, complete the following steps:

1. From the Configuration manager summary page, click Create a Configuration
Template. The Configuration Templates page is displayed.
2. Click Actions > Create.
3. Choose a target type in the Template type field.
4. Choose a value in the Configuration to create a template.
5. Type a unique name for the new configuration template. The name must be
unique and have a maximum length of 100 characters. The name of the
configuration template cannot contain the following XML special characters:
v The ampersand character (&)
v The apostrophe or single quotation mark character (')
v The double quotation mark character (")
v The greater-than character (>)
v The less-than character (<)
v The vertical bar character (|)
v The back slash character (\)
v The slash character (/)
v The asterisk character (*)
v The colon character (:)
v The question mark character (?)
v The percent character (%)
6. Type a meaningful description for the new configuration template. The
maximum length is 500 characters. The description of the configuration
template cannot contain the following XML special characters:
7. Optional: If you want this configuration template to be run automatically
when a new device with a type that matches this configuration template is
added or removed, or when an event related to this type of device occurs,
select Automatically deploy this configuration template when notified of a
matching resource.

Note: You cannot automatically deploy network templates, and this extends
to the network plans that contain them.
If you enable automatic deploy, the template is appended to the end of the
automatic deploy sequence list for the relevant type. To re-order the list, go to
Actions > Automatic Deploy Sequence.
8. Click Continue. The Configuration Settings page is displayed.
9. Enter configuration information.
10. Click Save to create the new configuration template. The new configuration
template will be displayed in the configuration template table.
Related concepts:
Related tasks:
“Creating a configuration template from an existing one”
“Editing configuration templates” on page 217
“Deploying configuration templates” on page 219
“Viewing deployed targets” on page 220
“Exporting a configuration template” on page 221
“Importing a configuration template” on page 222
“Deleting configuration templates” on page 223
Navigating tables
Creating a configuration template from an existing one

You can create a configuration template using an existing configuration template as
a model.
To create a configuration template from an existing one, complete the following

steps:
1. From the Configuration Manager Summary page, click Create a Configuration
Template. The Configuration Templates page is displayed.
2. Select one configuration template to use as a model for the creation a new one.
3. Click Actions > Create Like. Information from the selected configuration
template is placed in the panels that follow.
4. Type a unique name for the new configuration template. The name must be
unique and have a maximum length of 100 characters. The name of the
configuration template cannot contain the following XML special characters:
v The vertical bar character (|)
v The back slash character (\)
v The slash character (/)
v The asterisk character (*)
v The colon character (:)
v The question mark character (?)
v The percent character (%)
5. Type a meaningful description for the new configuration template. The
maximum length is 500 characters. The description of the configuration
template cannot contain the following XML special characters:
6. Optional: If you want this configuration template to be run automatically when
a new device with a type that matches this configuration template is added or
removed, or when an event related to this type of device occurs, ensure that
Automatically deploy this configuration template when notified of a
matching resource is selected.
If you enable automatic deploy, the template is appended to the end of the
automatic deploy sequence list for the relevant type. To re-order the list, go to
Actions > Automatic Deploy Sequence.
7. Click Continue. The Configuration Settings page is displayed.
8. Enter configuration information. You cannot change the values in the Template
type and Configuration to create a template fields.
9. Click Save. The new configuration template is created, and will be displayed in
the configuration template table.

Related concepts:
Related tasks:
“Viewing configuration templates”
Navigating tables
Viewing configuration templates

The properties of a configuration template include the name, a description, the
target type, automatic deployment status, and the dates and ID of users who
created and edited the configuration template.
To view a configuration template, complete the following steps:

1. From the Configuration manager summary page, click View Configuration
Templates. The Configuration templates page is displayed.
2. Select the configuration template you want to view.
3. Click Actions > Properties. A page containing the configuration template's
properties is displayed.
4. Click Cancel when you are finished viewing the information.

Related concepts:
Related tasks:
“Editing configuration templates”
Navigating tables
“Monitoring the deployment of configuration plans and configuration templates”
on page 207
Editing configuration templates

You can change some attributes of a configuration template after it is created.
Using the edit function, you can change some of the settings that the configuration
template defines. You cannot change the target type of the configuration template.
Changing template settings does not modify any settings that were deployed to a
system before modifying the template, but it does affect settings that are deployed
by using the modified template.
To edit a configuration template, complete the following steps:

Templates. The Configuration Templates page is displayed.
2. Select a configuration template to edit.
3. Click Actions > Edit Template. The Configuration Settings page is displayed.
4. Make all necessary changes.
Note: Depending on the template settings (which are preset), you might not be
able to change the template name and the automatic deployment setting.
For a template that supports automatic deployment, if you enable that function,
and it was not already enabled, the template is appended to the automatic
deploy sequence list. If you disable that function and it was previously enabled,
the template is removed from the list. To reorder the list, go to Actions >
Automatic Deploy Sequence.

5. Click Save. The changes are applied to the configuration template.
Tip: You also can select Actions > Properties to examine and change configuration
template attributes.
Related concepts:
Related tasks:
“Adding configuration templates to a configuration plan”
Navigating tables
Adding configuration templates to a configuration plan

When changes are made to your systems, it can be necessary to add new
configuration templates to a configuration plan.
To add a configuration template to a configuration plan, complete the following

steps:
2. Select one or more configuration templates to add to a configuration plan.
3. Click Actions > Add to Configuration Plan. The Add to Configuration Plan
pop-up is displayed.
4. Choose a configuration plan:
v Click Add selected templates to this plan to select an existing configuration
plan.
v Click Add selected template to a new plan and specify the appropriate
values to create a new configuration plan.
5. Optional: If you do not want to see the list of configuration plans when you are
finished, clear Open Configuration Plan list when done saving.
6. Click Save. The configuration template will be added to the configuration plan.

Related concepts:
Related tasks:
“Deploying configuration templates”
Navigating tables
Deploying configuration templates

You can deploy a configuration template even without having the configuration
template as part of a configuration plan. However, if you want to deploy the
configuration templates in a particular order, create a configuration plan to specify
the configuration templates in the desired order.
Each configuration template has a target type. Each system has a set of resources.
When a configuration template is deployed to a system, the configuration template
is deployed only on those resources that are of the same type as the configuration
template.
To deploy a configuration template to a target resource, complete the following

steps:
2. Select a configuration template to deploy.
3. Click Actions > Deploy. The Deploy Configuration Templates Job page
opens.
4. Select a system from the Available list. Use the Add and Remove buttons to
move items between the Available list and the Selected list.
5. Select as many systems as you want, and review the Selected list to ensure
accuracy.
6. Optional: Use the Browse button if you need information about the systems in
order to make your choice.
7. Optional: Click the Schedule tab. The Schedule page is displayed.
8. Optional: Enter job information.
9. Choose Run Now or Schedule.
10. Click OK when ready to run.

11. A message at the top of the Configuration Templates page indicates if the
deploy task has completed or not. Click on Display Property to see the job
status.
12. Optional: In order to see the log information about the configuration template
deploy, complete these steps:
a. Click Display Property. The properties of the job are displayed.
b. Click the Active and Scheduled jobs tab. The Active and Scheduled jobs
page is displayed.
c. View the job status in the General task section.
d. Click the Logs tab. A table of job logs is displayed.
e. Select the configuration template deployment job, and right click on its
name, and select the Show logs option. A list of job logs is displayed.
f. In the Activations logs text box at the bottom of the screen, you can see
details about the deployment of the configuration template. If the
deployment has failed, the reason for the failure is displayed in the
Activation log.
Related concepts:
Related tasks:
“Viewing deployed targets”
Navigating tables
Viewing deployed targets

You can view the devices and systems on which a configuration template has been
deployed, to determine where changes are required.
To view the list of devices and systems on which a configuration template has
been deployed on, complete the following steps:
2. Select a configuration template.
3. Click Actions > View Deployed Targets. A list of devices and systems on
which the configuration template has been deployed is displayed.

Related concepts:
Related tasks:
“Exporting a configuration template”
Navigating tables
Exporting a configuration template

A configuration template can be exported to an XML file on the local system.
Exporting is useful for moving a configuration template from one IBM Systems
Director system to another.
To export a configuration template, complete the following steps:

2. Select the configuration template that you want to export. Only one
configuration template can be exported to any given file.
4. Type the name of the file to receive the exported data.
5. Click Save.

Related concepts:
Related tasks:
“Importing a configuration template”
Navigating tables
Importing a configuration template

An XML file containing a configuration template can be imported to your list of
To import an XML file containing a configuration template, complete the following

steps:
2. Click Actions > Import.
3. Select the XML file to be imported from the local system.
4. Click Open.
5. The information in the file is verified to ensure that it contains a valid
configuration template. If the configuration template is valid, it is added to the
Configuration templates page.
If there is already a configuration template with the same name as the one you are
trying to import, a message is displayed and the configuration template is not
imported. For the import to succeed, rename the existing configuration template.
If the configuration template being imported specifies <autoApply>true</

autoApply>, the template is appended to the end of the automatic deploy
sequence list for the relevant type after it is imported.

Related concepts:
Related tasks:
“Deleting configuration templates”
Deleting configuration templates

You can delete those configuration templates that are no longer needed in order to
save space and prevent them from being used.
To delete a configuration template, complete the following steps:

2. Select one or more configuration templates to delete.
3. Click Delete. A pop-up will prompt you to confirm the deletion.
4. Ensure that you have chosen the correct configuration templates to be deleted.
v Click OK to perform the delete.
v Click Cancel to cancel the delete.
If you delete a template that has automatic deploy enabled, it is removed from the
automatic deploy sequence list.

Related concepts:
Related tasks:
Managing configuration plans

A configuration plan is used to configure hardware and operating systems.
Manage configuration plans by creating and updating them. They can be deployed
to a live system or set to be automatically deployed when a new system of
matching type is added.
Related concepts:
Configuration settings
Configuration plans
Related reference:
Configuration plans and templates
Creating configuration plans

A configuration plan consists of a set of configuration templates. Configuration
plans can also be used to automate, to an extent, the configuration process.
If you have not already done so, create configuration templates before creating a
configuration plan. You can also create configuration templates based on a target
resource when a list of these resources is displayed.
To create a configuration plan, complete the following steps:

1. From the Configuration manager summary page, click Create a Configuration
Plan. The Configuration plans page is displayed.
2. Click Create. The Configuration Plan wizard starts.

3. Optional: Clear Show this Welcome page next time if you do not want to see
the Welcome page the next time that this wizard starts.
4. Read the text on this page and click Next. The Name and Type page is
displayed.
5. Type a unique name for the new configuration plan in the Name field.
6. Type a description for the configuration plan in the Description field.
7. Select a target type for the configuration plan. The configuration templates in
the configuration plan must all be the same type. Only one type can be
selected.
8. Check Automatically deploy to indicate that this configuration plan is
automatically deployed whenever IBM Systems Director detects a new
resource of the same type. Only one configuration plan of any given type can
be designated to automatically deploy at any given time. If there is already a
configuration plan designated to automatically deploy, that plan will no
longer have that capability; instead, the new configuration plan will
automatically deploy. A message is issued in this situation.
Note: Because network templates do not support automatic deployment, the

automatic deploy button it is not available for network plans.
9. Click Next. The Configuration Templates page is displayed. This page is used
to select configuration templates to add to the plan. You can also add new
configuration templates based on a target resource.
10. Choose how you want to customize the Available table contents:
v Click Show existing templates to fill the table with all the existing
v Click Show templates based on a target to choose a target system. Its
configuration settings will fill the table.
Click Browse if you would like more details about the choice of systems.
If you select this option, you must click Refresh after selecting the target
system, in order to display the list of available configuration templates for
that system.
v You can effectively use both features by clicking Show existing templates,
selecting some configuration templates, and adding them to the Selected
table. You then click Show templates based on a target, select configuration
templates from a target system, and add them to the Selected table.
You cannot change the values associated with an individual configuration
template while you are using this wizard.
11. Select each configuration template to be included in the configuration plan.
12. Click Add to move the configuration template to the Selected table.
13. Optional: Click Remove to delete configuration templates selected in error.
14. Select the order in which the configuration templates are to be deployed on a
target system when the configuration plan is deployed:
a. Select each configuration template whose order is to be changed.
b. Click Move Up or Move Down to change the order of the configuration
templates.
c. When the order is correct, click Next.
The Summary page is displayed.
15. Examine the information on this page.
v If you want to change information, click Back to return to the previous
page.

v To return to a particular page to make corrections, click its entry in the
navigation pane.
v If all information on this page is correct, click Finish. The new
configuration plan will be created.
v To terminate the wizard without creating a new configuration plan, click
Cancel.
Related concepts:
Related tasks:
Creating a configuration plan from an existing one
Deploying configuration plans
Viewing configuration plans
Viewing deployment history
Editing configuration plans
Exporting a configuration plan
Importing a configuration plan
Deleting configuration plans
Navigating tables
Related reference:
mkcfgplan command

An existing configuration plan can be used as a model for creating a new one.
To create a configuration plan with the same characteristics as an existing one,

complete the following steps. You can later edit this new configuration plan.
1. From the Configuration Manager Summary page, click Create a Configuration
Plan. The Configuration plans page is displayed.
2. Select one configuration plan to use as a model for the new configuration plan.
3. Click Create Like. The new configuration plan is created and added to the list.
The new name is the selected configuration plan's name with the prefix Copy of
appended.
4. The Configuration Plan wizard starts. Make any necessary changes.
5. Change the name of the newly-created plan.

Related concepts:
Configuration plans
Related tasks:
Navigating tables
Related reference:
mkcfgplan command

A configuration plan can be deployed on one or more systems.
Deploy a configuration plan on one or more systems from the Configuration Plan
page, or by using the automatically deploy feature. Configuration plans can also be
deployed using automation manager with an event action plan.
To deploy a configuration plan on a target system, complete the following steps:

Plans. The Configuration plans page is displayed.
2. Select the configuration plan.
3. Click Actions > Deploy. The Deploy Configuration Plans Job page is
displayed.
4. Select a system from the Available list. Use the Add and Remove buttons to
move items between the Available list and the Selected list.
5. Select as many systems as you want, and review the Selected list to ensure
accuracy.
6. Optional: Use the Browse button if you need information about the systems in
order to make your choice.
7. Click Next. The Schedule page is displayed.
8. Enter the job information.
9. Click OK when you are ready to run the job.
10. A message at the top of the Configuration Plans page indicates whether the
deploy task has completed. Click on Display Property to see the full status.
11. Optional: In order to see the log information about the deploy task, complete
these steps:
a. Click Display Property. The properties of the job are displayed.

b. Click the Active and Scheduled jobs tab. The Active and Scheduled jobs
page is displayed.
c. View the job status in the General task section.
d. Click the Logs tab. A table of job logs is displayed.
e. Select the configuration plan deployment job, and right click on its name.
f. Click Show logs. A list of job logs is displayed.
g. In the Activations logs text box at the bottom of the screen, you can see
details about the deployment of the configuration plan. If the deployment
has failed, the reason for the failure is displayed in the Activation log.
Related concepts:
Configuration plans
Related tasks:
Navigating tables
Related reference:
mkcfgplan command

The properties of a configuration plan include the name, description, target type,
whether it can be automatically deployed, and dates and ID of users who created
and edited the configuration plan.
To view a configuration plan, complete the following steps:

2. Select the configuration plan whose information you wish to view.
3. Click Actions > Properties. A page containing the configuration plan's
properties is displayed.
4. Click Cancel when you are finished viewing the information.

Related concepts:
Related tasks:
Navigating tables
“Monitoring the deployment of configuration plans and configuration templates”
on page 207
Related reference:
lscfgplan command

Follow these steps to view a list of the attempts to deploy configuration plans and
templates to a system. This option is only available on the context menu for a
system that has been discovered and unlocked. If no templates or plans have been
deployed to the system, this list is empty.
1. From the Resource Explorer area, select a system that is not locked.
2. Click Actions > System Configuration > Deployment History. The
Deployment History page is displayed.
3. View the Type column to determine whether the attempt was an attempt to
deploy a configuration plan or an attempt to deploy a configuration template.
4. A list of the attempts to deploy a configuration plan or a configuration
template to the system is displayed. The date and time of the attempt, and the
status of the attempt, are also displayed. The most recent attempt is listed first.
5. When done, click Close.

Related concepts:
Configuration plans
Related tasks:
Related reference:
lscfgplan command

The attributes of a configuration plan can be changed after it is created.
To edit a configuration plan, complete the following steps:

2. Select the configuration plan to be edited.
3. Click Actions > Edit. The Configuration Plan wizard starts, using the existing
information about the configuration plan.
4. Proceed through the wizard making any necessary changes. This process is the
same as if you were creating a new configuration plan, except that you cannot
change the plan type.
Related concepts:
Configuration plans
Related tasks:
Navigating tables

A configuration plan can be exported to an XML file on the local system. This is
useful to move a configuration plan from one IBM Systems Director system to
another.

Exporting a configuration plan will not export the contained configuration
templates. Only the names of the contained configuration templates will be listed
in the exported configuration plan. You will have to export the configuration
templates separately.
To export a configuration plan, complete the following steps:

2. Select the configuration plan that you want to export. Only one configuration
plan can be exported to any given file.
4. Type the name of the file to receive the exported data.
5. Click Save.
Related concepts:
Configuration plans
Related tasks:
Navigating tables
Related reference:
lscfgplan command

An XML file containing a configuration plan can be imported to your list of
configuration plans.
To import and XML file containing a configuration plan, complete the following
steps:
2. Click Actions > Import.
3. Select the XML file to be imported from the local system.
4. Click Open.
5. The information in the file is verified to ensure that it contains a valid
configuration plan. If so, it is added to the configuration plans page.

If there is already a configuration plan with the same name as the one that you are
trying to import, a message is displayed and the configuration plan is not
imported. You are advised to rename the existing one in order for the import to
succeed.
The import of a configuration plan will not create the configuration templates
listed in the configuration plan file. The configuration plan import assumes that
the configuration templates listed in the plan are already present on the target
system. If a configuration template that is listed in the configuration plan file exists
in the database, it will be associated to the imported configuration plan.
Related concepts:
Configuration plans
Related tasks:
Related reference:
mkcfgplan command

You can delete those configuration plans that are no longer needed, in order to
save space and prevent them from being used.
Complete the following steps to delete a configuration plan:

2. Select the configuration plans to be deleted.
3. Click Delete. A confirmation panel is displayed.
4. Ensure that you have chosen the correct configuration plans to be deleted.
v Click OK to perform the delete.
v Click Cancel to cancel the delete.
Deleting a configuration plan does not delete the configuration templates that are
included in that configuration plan.

Related concepts:
Configuration plans
Related tasks:
Deleting configuration templates
Navigating tables
Related reference:
rmcfgplan command
Managing activation keys by using Feature Activation Manager

Use the Feature Activation Manager to activate (or unlock) Features on Demand
options that are integrated in a managed resource. The feature is in the firmware
or software but is locked until you install the activation key. The Feature
Activation Manager consists of the Feature Activation Configuration page and the
Feature Activation wizard. Ensure that the resource that you want to configure
supports feature activation.
The Feature Activation Manager provides the capability to activate a feature on a

resource with a software key that is referred to as an activation key. For example,
when you purchase a server and a Features on Demand option, the activation key
can be installed on the server so that the Features on Demand function is ready for
you to use when you receive the server. Also, an available Features on Demand
option can be ordered anytime after your initial product purchase.
The feature is activated in one of the following ways:

v When you purchase a feature as part of a server or chassis order, the IBM
factory or IBM Business Partner enables the feature as part of the configuration
and testing of the server or chassis. You can begin using the feature when you
receive the server or chassis.
v When you purchase a Features on Demand option or upgrade that is separate
from the server or chassis order, you must complete the feature activation when
you install the option. In this case, an authorization code with instructions for
activating the feature is mailed to you.
v When you successfully retrieve an authorization code from the IBM Key
Management System Features on Demand web portal (https://www.ibm.com/
systems/x/fod/index.wss), an authorization code and instructions are contained
in a PDF that is e-mailed to you.
v When you already have the activation key, use the Feature Activation
Configuration wizard to upload the key.
An authorization code is a 22-character alphanumeric string that is the proof of
purchase and entitlement to upgrade one or more units with a particular feature.
The authorization code and instructions for requesting an activation key are on a
printed document that is mailed to you. If you order directly from IBM, the
authorization code and instructions can also be sent to your email address.
To use the Feature Activation Configuration wizard to obtain, upload, install, or

activate keys, complete the following steps:
Note: Before viewing, installing, or adding feature activation keys for a switch, be
aware of the following Switch considerations.
1. On the Plug-ins tab of the Home page, click Configuration Templates under
Configuration Manager. On the Configuration Templates page, click Create.
2. In the Create window, select the Template type that you want to create, then
select (if available) Feature Activation Manager Configuration.
3. Type a Configuration template name, then click Continue. The Feature
Activation Configuration wizard is displayed.
4. Complete the Feature Activation Configuration wizard to add the activation
key for your resource.
Switch considerations:
v For switches that use either SNMPv1 or SNMPv2c, configure the Write
Community String.
v For switches that use SNMPv3, configure the feature key management privilege
for the specified user.
v For a IBM System Networking or a Mellanox switch, make sure to use the
Update Manager Configure settings task (on the System x and IBM BladeCenter
tab) to specify which server you want to use as the Trivial File Transfer Protocol
(TFTP) server. The TFTP server is used to inventory or install feature activation
keys on the switch.
Use the Feature Activation Configuration page to view information about installed
feature activation keys, add and remove keys, and reboot the specified device on
which a feature activation key is installed or removed. To access the Feature
Activation Configuration page, right-click the resource that you want to examine,
then select System Configuration > Configuration Settings > Feature Activation
Manager.

Chapter 5. Monitoring system status and health
IBM Systems Director provides a set of tools that you can use to monitor and
manage the status and health of resources in your environment from a single
interface.
Related tasks:
Automating tasks
Related reference:
System status and health troubleshooting
System status and health

IBM Systems Director automatically retrieves and displays the status of systems
that have been discovered. You can display this information using one of the
System Status and Health tasks, by navigating to a specific resource in IBM
Systems Director, or by using the command-line interface.
Use this topic to learn about the following:

v “About system status and health”
v “Working with system status and health”
v “System status and health summary” on page 236
v “System status and health tasks” on page 236
v “Viewing older events” on page 238
About system status and health
Before you can view the status of any resources, IBM Systems Director must first
discover and be able to access those resources. After a system has been discovered,
IBM Systems Director automatically monitors the system and its resources.
The status of an entire system reflects the status of the component on the system
that has the most severe status. For example, if a component within a system has a
status of critical, the entire system will have a status of critical, even if the critically
impacted component is not critical to the system.
IBM Systems Director provides several tools and views to monitor and manage the
resources within your environment. See the section ““System status and health
summary” on page 236 for details.”
Working with system status and health
The approach you use to manage resources depends on how you prefer to view
them and what you are looking for when checking their statuses. Examples of
approaches that you can use for different situations are as follows:
v After connecting a new hardware device to your network, you might want to
check the status of the hardware. Rather than navigate to the Health Summary
page, you can drill down from the Resource Explorer page and navigate directly
to the new hardware to view its status.

v If there is a problem with your network and you do not know the resource that
is causing the problem, it might be quickest to navigate to the Health Summary
page to identify the problem areas and drill down to the resources that are
causing the problem.
System status and health summary
There are several ways to view the system status and health summary:
Banner
The banner on the upper-right of the IBM Systems Director web interface
displays this information for all Systems Director managed systems:
v The total number of “critical”, “warning”, or “minor” health status
issues
v The total number of “out of compliance” issues
System Status and Health > Scoreboard
The scoreboard displays the total number of endpoints with active problem
reported. This total includes the following:
v The number of Systems Director managed systems with active problems
reported.
v The number of Systems Director managed systems that are not in
compliance with their configured compliance policies.
System Status and Health > Active Status
The 'Active Status' page displays all active events reported on Systems
Director managed systems. The table lists “information” events and
compliance events as well as “critical” and “warning” issues. Therefore, the
number of entries in the Active Status table can be greater than the number
of problems listed on the banner count.
Problems (Active Status)
The Problems (Active Status) table lists all active “critical”, “warning”, or
“minor” events reported on Systems Director managed systems. The
banner count should match this count.
Power Systems Management
This page lists the number of Systems Director managed IBM Power
resources with “critical”, “warning”, or “informational” events. This
number includes the endpoints on which all or some alerts have been
ignored.
System status and health tasks
The System Status and Health tasks simplify your work as a system administrator
by providing consolidated views of the health and status of your entire
environment. Specifically, the Health Summary task displays information about the
resources that IBM Systems Director has discovered. You can customize the content
that is displayed on the System Status and Health pages with information that is
specific to your business processes and organizational structure. In addition, you
can view detailed real-time data by adding monitors to the dashboard.
Use the System Status and Health tasks to perform the following functions:
v Determine the health and performance of resources in your environment.
v Identify the causes behind changes in the health of a resource.
v Display charts that indicate real-time usage data for resources.

v Set thresholds to quickly determine whether the resources are in an abnormal
state.
v Run tasks on resources in response to status changes or system management
needs.
v Take action to resolve issues for resources.
v Launch the event log viewer.
Use the following System Status and Health tasks to view the system's status:
Performance Summary
The Performance Summary task displays available monitors with which
you can examine the servers, virtual servers, or operating systems that you
specify. Use this page to dynamically view, monitor, and work with
processor pools, memory pools, networks, and other critical areas of your
environment.
Health Summary
The Health Summary task displays several resource-monitoring tools on a
single page. Together, these tools provide a single, consolidated interface
with which you can quickly view the status of important areas of your
environment, monitor critical resources, and view the contents of
user-defined health summary groups.
Monitors
The Monitors task provides the tools that you need to retrieve real-time
status and quantitative data for specific properties and attributes of
resources in your environment. You can also set thresholds for the
monitors, graph the data that monitors retrieve, and drill down to quickly
view the status of resources for each system and the name of the monitor
so that you can view its properties.
Thresholds
The Thresholds task offers a consolidated view of all the thresholds that
you have created to monitor the dynamic properties of your resource. This
task saves you from searching for them all in the Monitors task.
Problems
The Problems task lists only those elevated status set entries that are
problem status set entries that have been reported to IBM Systems Director
Server. The data listed here is a subset of what is listed on the Active
Status page. From the Problems page, you can navigate to, display, and
manage these status set entries. You can also ignore entries to prevent IBM
Systems Director Server from collecting them or delete the entries to
remove them from the list until they occur again.
Active Status
The Active Status task lists all of the status set entries, including problems
and compliance issues, that have been reported to IBM Systems Director
Server. From the Active Status page, you can navigate to, display, and
Systems Director Server from collecting them or delete the entries to
remove them from the list until they occur again.
Event Log
An event is an occurrence of significance to a task or resource. Examples of
events include operation completion, hardware component failure, or a
processor threshold being exceeded. The Event Log task displays all events
that the management server receives from any resource for which you can
view events.
Chapter 5. Monitoring system status and health 237

SNMP Browser
The SNMP Browser task enables you to display, inspect, and perform
certain actions on SNMP-compliant resources, including selecting the
targets on which an SNMP job will run.
Viewing older events
In System Settings, you can specify how many events to keep in the event log.
When the event log is full and a new event is received, the oldest event is moved
to the backup event log. When the backup event log is full, a new one is created.
The old one might be deleted, depending on the backup event log preferences.
To view events in the backup event log, open data/eventLogBackup_n.log, where n

is incremented every time a new backup event log file is created.
See “Changing backup event log preferences” for more information.

Related tasks:
Changing backup event log preferences
Viewing the status manager summary

You can view a summary of the current activity that is associated with status,
including the status of the systems in your environment, the number of recordings
and thresholds, and detailed status. The information on the summary page
refreshes automatically when there are any changes.
To view the status manager summary, complete the following steps:

displayed.
2. On the Plug-ins tab, select Status manager. The status manager summary is
displayed.
3. View the Status section. This section provides the following information:
There are four status categories, represented by icons:
v A pie chart and corresponding list that indicates the number of systems that
fall into each of the following four status categories:
Critical
Warning
Informational
OK
category.
v In the Status tasks area, the following links are provided:
Health summary
Use the Health Summary page to quickly view the status of
important areas of your environment, monitor critical resources, and
view the contents of user-defined health summary groups.
View problems
Use the Problems page to view the elevated status for categories that
are part of the problems composite category and ignore or delete the

entries. The problems composite category includes all categories,
such as hardware status and threshold status, except compliance and
LED.
View active and ignored status
Use the Active Status page to view all status set entries for resources
in your environment and ignore or delete the entries.
Groups by status
Use the Groups by status page to view a list of groups that represent
resources grouped by status.
4. View the Management section. This section provides the following information:
v The number of thresholds that are active and not active. Click the link to
view the Thresholds page
Monitors
Use the Monitors page to create and work with monitors.
Thresholds
Use the Thresholds page to work with thresholds.
Event log
Use the Event Log page to view events according to filters that you
select.
Viewing the performance summary

Use the Performance Summary task to examine performance information selected
from available monitors for the resources that you specify.
Selecting the target resources populates the rows of Performance Summary table.
The available monitors for each target resource determine the columns (attributes)
that you can display.
The Performance Summary page displays multiple pages. Which pages display
depends on your IBM Systems Director installation. A base installation displays at
least a Processor page and a Memory page.
To view performance information for a target resource, complete the following

steps:
1. In the IBM Systems Director Web interface navigation area, expand System
Status and Health, then click Performance Summary.
2. Specify one or more target resources (servers, virtual servers, or operating
systems) for which you want to examine the performance information. Click
Browse if you want to search for a resource. The Performance Summary table
is created and populated with the targets that you specified.
3. Specify the type of performance information that you want to display in each
column. Each column represents an attribute reported by an available monitor.
a. Click Select Column Monitors
b. In the Columns window, select one or more entries from the Available
Columns list, then click Add to move them to the Selected Columns list.
c. If you want, select one or more entries from the Selected Columns list, then
click Remove to remove them from the list.
d. Click OK to save your changes.
The updated table displays performance data in the columns that you specified.
4. One way to work with the table entries is to right-click a target, then select
Column Monitors to choose a monitor that you want to use.

5. Select the performance data that you want to examine, then select how you
want to interact with the data:
a. Select Activate Threshold to display the Threshold page, where you specify
how to activate the threshold.
b. Select Graph to display the Graph page, where you can view a graphical
rendering of the data.
c. Select Add To Dashboard to add a graphical rendering of the data to your
dashboard. Specify a name for the monitor view and select the type of
graph that you want to display.
Related concepts:
Dashboard
Related tasks:
Managing monitors
Activating a threshold
Working with tables
The Health Summary task displays several resource-monitoring tools on a single
page. Together, these tools provide a single, consolidated interface with which you
can quickly view the status of important areas of your environment, monitor
critical resources, and view the contents of user-defined health summary groups.
discover and be able to access those resources.
IBM Systems Director provides multiple ways to check the status of a specific
resource in your environment. Use the Health Summary page to see a consolidated
view of the health and status of your system resources, storage resources, and
thresholds. These indicators help to identify areas within your environment that
might have problems or issues that you need to resolve. You can view the status of
several resources and quickly view details for those resources that are causing a
problem.
The Health Summary page contains the following sections:

v Scoreboard
v Dashboard
v Health Summary
By displaying a consolidated view of the health of your systems, storage resources,
and thresholds, these panels provide the information and tools that you can use to
monitor and manage systems and resources across multiple platforms from a
single interface.
Note: You are not required to first collect inventory for a resource for it to be
displayed on the Health Summary page.
The health summary task provides the following functions:

v Retrieves and displays the status and health of resources that you specify.
v Displays charts that indicate real-time data for resources and thresholds.
To view the status and health of your environment resources from the centralized
location of the Health Summary page, complete the following steps:

displayed.
2. On the Plug-ins tab, click Health Summary under Status manager.
3. Choose an item and drill down to view its details.
Related tasks:
Managing groups
Scoreboard
The scoreboard displays a table in which each row represents an area or category
of information. Each element of the table, including column headers, row headers,
and cell data, is potentially clickable and displays specific data. Each column
header in the scoreboard identifies a severity status associated with the
corresponding categories. At the intersection of each row and column is a number
that represents the number of resources that adhere to the conditions of both the
row and the column that intersect. Each resource is counted only once, regardless
of the number of issues it has. Clicking the number displays the resources. Only
the systems to which you have access are displayed on the scoreboard.
The scoreboard displays the status of important areas of your environment by

using three severity levels; critical, warning, and informational. A system that
reports multiple severities is always grouped under the highest severity. For
example, if a system has both critical and warning events, it is shown under
critical and is not listed under warning. From the totals, icons, and category names
in the scoreboard, you can drill down to view various details about the systems
that are reporting system health and performance issues.
In order for IBM Systems Director to monitor the vital signs related to the health
and performance of a target system, the target system must have Common Agent
or Platform Agent installed on it. Agentless managed systems are also counted if
they are configured to report performance issues and if they have one of the
following protocols installed:
v Secure shell (ssh)
v Distributed Component Object Model (DCOM), an extension of the Microsoft
Component Object Model (COM) to support objects distributed across a
network.
v Simple Network Management Protocol (SNMP)
Examples of agentless-managed systems are management modules and Remote
Supervisor Adapters (RSAs).
By default, IBM Systems Director counts and displays the totals for the following
status categories:
Compliance
Identifies software-update and compliance-related status issues. The
compliance status category is populated only when a compliance policy is
re-validated due to a variety of different events.
Problems
Includes all types of issues including hardware, software, inventory, and
power-related status issues.
LED Status
Identifies the aggregate state of all hardware LEDs. Each LED identifies the

state of a related hardware component. LED status is updated when any
hardware LED changes. For example, if there is a CPU LED fault, then the
CPU LED is lit and LED status is “Critical”.
Dashboard
The Dashboard section of the Health Summary page displays a real-time, graphical
representation of resource status based on the measurable properties for the
resource that you have set. You can display this data in various formats to help
monitor resources. Use the Monitors task to add items to the dashboard.
To display information in the dashboard, you must first set up and configure the
monitors to indicate the information that you want retrieved. By default, the
dashboard is initially empty. To add charts to the dashboard, you must use the
Monitors task to display existing monitors and target systems. From the Monitors
page, you can find the appropriate monitors and then add them to the dashboard.
You can add only one monitor to the dashboard for each graph. Additionally, you
can add only bar and line graphs for group monitor thumbnails in the dashboard.
Health summary
The Health Summary section of the Health Summary page displays selected
resources that you have chosen to watch closely. With this section, you can quickly
view and monitor the resources that are most important to you. You can perform
actions on a resource by using the Actions menu. You can also drill down to
display the properties and other details for each resource. To display information
in the health summary, you must first set up and configure the groups that you
want to display.
To view the health summary, expand System Status and Health in the IBM
Systems Director Web interface navigation pane and click Health Summary. The
scoreboard, dashboard, and health summary display the status and health of your
environment.
The Favorites group and the Systems with Problems group both appear in the
health summary by default. You can add or remove groups of resources from the
health summary. You can also create new health summary groups.
After you have discovered applicable resources, use the Health Summary Group
Editor wizard to add the most important or critical systems in your environment to
a health summary group. After a health summary group has been created, you can
add the group to the health summary.
Using the scoreboard to identify issues

From the Health Summary page, you can select items in the scoreboard and drill
down to details that help locate and identify issues within your environment.
The scoreboard counts and then displays only those systems that have been
discovered and are accessible, and have reached a critical, warning, or
informational level. Before you can view the status of any resources, IBM Systems
Director must first discover and be able to access those resources.
The scoreboard is a table that comprises columns, rows, and individual totals in
cells. You can drill down from the icons (column headers), category names (row

headers), or totals (in the cells) to view various details about the systems that are
reporting system health and performance issues.
Totals If you click a totals number in the scoreboard, you are presented with a list
of entries that contains the number of systems in the list equal to the
number on which you clicked. For example, if two systems in your
environment have a combined total of five critical problems, the number 2
is displayed in the scoreboard to represent those two systems. When you
click the 2, you see all five critical problems.
Icons When there is a number in the scoreboard, the severity icon above that
number becomes a clickable link. When selected, the link displays all the
entries with that severity from every category. For example, if two systems
in your environment have five critical problems and three critical
compliance issues between them, the number 2 is displayed under the
Critical icon for the Problems category and the number 2 is displayed
under the Critical icon for the Compliance category. The Critical icon at the
top of the scoreboard is enabled. If you click the Critical icon, you are
presented with a list of eight items: five critical problems and three critical
updates.
Categories
When there is a number in the scoreboard for a category, that category
name in the scoreboard becomes a clickable link. When selected, the link
brings up all the entries for all severities for that category. For example, if
two systems have five critical problems, four other systems have a total of
four warning problems, and one other system has one informational
problem, then there are three numbers in the scoreboard for the Problems
category: 2, 4, and 1, which represent numbers of systems with each type
of problem. When you click the Problems category, you see a list of ten
items, which are all the problems across all the systems.
Note: If there are no resources with a particular status for a category, the
intersecting cell will display a hyphen (-) instead of a number.
To use the scoreboard to identify problems, complete the following steps:

displayed.
2. On the Plug-ins tab, click Health Summary under Status manager. The
scoreboard, dashboard, and health summary display the status and health of
your environment.
3. In the scoreboard, select one of the following filtering methods:

Table 19. Filtering methods
Filter based on severity status In the scoreboard, click the icon for one of
the following severity status values:
Critical A system that has generated an
event with a severity of 0 or 1 is
the most severe and is identified in
IBM Systems Director as being in a
critical state. These systems have
already lost or will imminently lose
data, have had system downtime,
or are on the verge of losing some
other services. Leaving the problem
uncorrected might have an impact
on system operation.
Warning
A system that has generated an
event with a severity of 2 or 3 is
identified in IBM Systems Director
as being in a warning state. These
systems can escalate to a critical
state if left uncorrected. Leaving the
problem uncorrected might not
have an impact on system
operation, so normal use of the
system can probably continue.
Informational
A system that has generated an
event with a severity of 4 is
identified in IBM Systems Director
as being in an informational state.
These systems are operating
normally and typically, so no action
is required.
Note: A system that has generated an event
with a severity of 5 is in an unknown state.
The unknown state is not included in most
IBM Systems Director tasks.
The resources with the selected severity

level are displayed in the Resource Explorer
table.
Filter based on type of issue In the scoreboard, click one of the listed
categories. The resources with the selected
issue type are displayed in the Resource
Explorer table.
Filter based on both status and issue Click the number in the scoreboard that
corresponds to the severity level and the
type of issue that you want to be displayed.
For example, if two systems have critical
problems, the number 2 would be displayed
under the critical icon on the Problems
category. If you click that number, those
resources with a critical severity level for the
problems type of issue are displayed.

4. Navigate to the resource that you want to view and click it to view its
subsystems or related resources. The number of pages and the types of
information that these subsystems or related resources include vary depending
on the resource.
5. Click through the pages until you find the resource that has caused the
problem.
Related concepts:
Adding a graphical monitor to the dashboard

Monitors are dynamic in nature and can be easily monitored graphically by
configuring IBM Systems Director to display the information. When you select
Add to Dashboard for an individual monitor on the Monitors page, a graphical
representation of that monitor is added to the dashboard.
Before you can display any graphical monitors on the dashboard, IBM Systems
Director must first discover the systems that you want to monitor. After you have
discovered the applicable systems, you can add them to a group. You can then add
individual monitors to the dashboard.
To configure the dashboard to display the monitors you want, complete the
following steps:
displayed.
3. In the dashboard, click Show Monitors. The Monitors page is displayed.
4. To select one or more target resources, click Browse. The Context Chooser is
displayed.
5. Use the Context Chooser to add one or more resources or groups of resources
as a target:
a. To add a group, select the group that you want to add as a target. To add a
single resource, drill down from the group that includes the resource that
you want to add and select the resource.
b. Click Add.
c. Continue selecting groups or resources as needed.
d. When you are finished adding targets, click OK.
6. From the Monitor selection page, select the monitor view that you want to be
displayed for the targets that you selected.
7. Click Show Monitors. The Monitor View page listing monitors for the targets
that you selected is displayed.
8. Right-click the monitor that you want to be displayed on the dashboard and
select Add to dashboard.
After adding a monitor to the health summary, navigate to the Health Summary
page to verify that the monitor is displayed in the dashboard.
Removing a graphical monitor from the dashboard

From the Health Summary page, you can remove charts from the dashboard.
To remove a chart from the dashboard, complete the following steps:

displayed.
3. In the dashboard, right-click the title of the chart that you want to remove and
click Remove.
Adding systems to the health summary

The health summary displays selected systems that you have chosen to watch
closely. Use this panel to quickly view and monitor the systems that are most
important to you.
By default, the health summary displays the status of systems that belong to the
health summary favorites group and the Systems with Problems group. To add
additional systems to the health summary, choose one of the following methods:
v Add additional systems to the health summary favorites group.
v Add additional systems to another group and add that group to the health
summary using either the Resource Explorer task or the Actions menu in the
health summary.
Using the health summary favorites group to add and remove

systems in the health summary
Use the Health Summary task to add and remove systems in the favorites group
and display them in the health summary.
Before you can add or remove a system from the health summary favorites group,
IBM Systems Director must discover that system.
By default, the health summary displays the status of systems that belong to the
health summary favorites group.
Note: The health summary also displays the Systems with Problems group by
default.
To add or remove systems in the health summary favorites group to be displayed
in the health summary, complete the following steps:
displayed.
your environment.
3. In the health summary, right-click Favorites and select Edit. The Group Editor
Wizard opens and the Welcome page is displayed.
4. Click Next. The Name page is displayed and the Name and Description fields
are filled out for your favorites group.
5. Leave the Name and Description fields as they are and click Next. The Type
page is displayed. You cannot change any values on this page.
6. Click Next. The Define page is displayed.
7. To add systems to the group, select the systems or criteria in the list on the
left and click Add.
8. To remove systems from the group, select the systems or criteria in the list on
the right and click Remove.
9. Continue modifying resources or criteria as needed.

11. Click Finish.
Using the Actions menu to add systems to the health summary

Use the Actions menu on the health summary to add any group to the health
summary.
To add a group to the health summary using the Actions menu on the health
summary, complete the following steps:
displayed.
your environment.
3. In the health summary, click Actions > Edit. The Group Editor wizard opens.
4. In the Name field, type a descriptive name of the health summary group that
you want to create.
5. In the Description field, type a brief description for the group.
6. Click Next. The Type page is displayed.
7. In the Type list, select one of the following options:
Static Static groups contain a specified list of systems. The members of a
static group are fixed unless you change them.
Dynamic
Dynamic groups are based on specified system criteria. IBM Systems
Director prompts you to specify the criteria that the system attributes
and properties must match. Then, when system attributes or system
properties change, its match to the group criteria changes and IBM
Systems Director automatically adds or removes the system to or from
the group.
8. In the Member list, select the type of members to add to the group.
9. Click Next.
10. In the left area, select the resources or criteria to use for the group, and click
Add.
11. Continue adding resources or criteria as needed.
12. Click Finish.
After adding a group to the health summary, navigate to the Health Summary
page to verify that the group is displayed. You can configure the columns that are
displayed in the health summary to make it easy to quickly identify the status of
the resources that you are monitoring. As a best practice, ensure that the columns
that are related to health and status are always displayed in the health summary.
Using Resource Explorer to add systems to the health summary

Use the Resource Explorer task to select the resource groups that you want to be
displayed on the health summary.
To add a resource group to the health summary, complete the following steps:
Explorer.
2. Navigate to the group that you want to add to the health summary.
Note: If the group that you want to add does not exist, create it.

3. From the Resource Explorer table, right-click the group that you want to add to
the Health Summary page and select Add to > Health Summary. The Navigate
Resources table is displayed.
Note: If you right-click a system instead of a group, you can add that system
to either the Favorites group or another group of your choosing. Adding the
system to the favorites group will automatically add it to the health summary.
However, if you add the system to another group of your choosing, ensure that
that group is added to the health summary if you want the system to appear
there.
After adding a group to the health summary, navigate to the Health Summary
page to verify that the group is displayed.
Removing a group from the health summary

The health summary displays the status of systems that belong to the health
summary favorites group and other groups that you have added to it. You can use
the Health Summary task to remove a group from the health summary.
To remove a group from the health summary, complete the following steps:
displayed.
your environment.
3. In the health summary, right-click the group that you want to remove and click
Remove. A confirmation message is displayed.
4. Click Remove. The group is removed.
Using Resource Explorer to view the status of a specific resource

Use Resource Explorer when you want to view the status of only one resource and
you know exactly which resource it is. Using the Resource Explorer task, you can
navigate to a specific resource and drill down to view detailed status information.
discover and be able to access those resources.
To view the status of a specific resource using the Resource Explorer task in IBM
Systems Director, complete the following steps:
1. In the IBM Systems Director Web interface navigation pane, click Resource
Explorer.
Note: If you know the name of the resource that you want to view, use the
Find a Resource task to navigate to it even more quickly.
2. In the Groups column, click the type of resource that you want to find.
3. Click the name of the resource you want to view. The table displays the state,
problems, and compliance status of the resource.

Related tasks:
Managing groups
Scenarios: Using custom monitor views, thresholds, and event

automation plans
These example scenarios illustrate ways to use monitors, thresholds, and event
automation plans to report when important or critical disk drive conditions occur.
Each scenario creates a custom a monitor view, activates thresholds for the
monitors in the view, and uses the view and thresholds in an event automation
plan. When reported by the automation plan, the results from each example
indicate the affected disk drives by the letter name given to them on the system.
The scenarios do not specify which action the automation plan automatically
performs, but possible actions include notifying an administrator by phone or
email or running a remote command to correct the reported condition.
Scenario: Using a custom monitor view in an event

automation plan to report disk data by using drive letter
names
This example scenario describes how to create a monitor view and use that
monitor view in an event automation plan. The scenario assumes that you want to
create an event automation plan that monitors the percentage of disk drive space
used by specific disk drives. Additionally, the event automation plan must report
information about the disk drives by using the letter names given to the drives on
the system.
All tasks for this scenario occur within the IBM Systems Director Web interface, so
the scenario assumes some familiarity with browsing the interface and using it to
perform tasks. Also, each of the following steps describes only one way to perform
the action, even if an alternative method exists.
For this scenario, the letter names for the disk drives to monitor are drive c, drive
d, and drive e.
To create a custom monitor view for disk drives and use it within an event
automation plan, perform the following steps:
1. Select the resources that you want to monitor:
a. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
b. Drill down to select the resources that you want to monitor, and select
them.
c. Click Actions > System Status and Health > Monitors. If System Status
and Health > Monitors is not a choice available to you, one or more of the
resources you selected are not eligible for monitoring. Make sure to select
only resources that can be monitored.
The Monitors task is displayed with the systems that you specified in step 1b
already selected.
2. Start creating a monitor view by clicking Actions > Create. The Create View
page is displayed.

3. On the Create View page, in the Name field, type a name for the monitor
group that you are creating.
4. From the Show list, select Selected Resources.
5. Select the monitors for the individual disk drives that you want to monitor:
a. In the Selected Resources table, select SystemName > Director Agent >
Disk Monitors, where SystemName is the name of the system that contains
disk drives that you want to monitor. Monitor information for the disk
drives is displayed.
b. In the Selected Resources table, select the monitors that you want to
include in this monitor group. For example, select Drive C: % Space Used,
Drive D: % Space Used, and Drive E: % Space Used.
c. After selecting the monitors, click Add to add them to the monitor group,
then click OK.
Note: If you want to monitor drives on more than one system, for each system
that contains drives that you want to monitor, repeat step 5a through step 5c.
The Monitors page is displayed, and the Monitor Views table includes the
monitor view that you created.
6. Click the name of the monitor view that you created. The Monitor View page is
displayed.
7. Activate thresholds for the monitors. For each monitor for which you want to
create a threshold, perform the following actions:
a. Right-click the name of the monitor, then select Activate Threshold. The
Threshold page is displayed.
a. On the Threshold page, specify the threshold values and options that you
want to use, then click OK. The Monitor View page is displayed, and the
table shows that the new thresholds are active.
8. Create an event filter to be activated by the thresholds that you created
previously:
a. In the IBM Systems Director Web interface navigation area, click
Automation > Event Filters. The Event Filters page is displayed.
b. Click Create to create the filter. The Create Event Filter wizard is displayed.
c. On the Welcome page, click Next. The Filter Name page is displayed.
d. On the Filter Name page, type the name you want to give this event filter,
then click Next. The Filter Type page is displayed.
e. On the Filter Type page, select a filter type of Threshold event filter, then
click Next. The Event Type page is displayed.
f. On the Event Type page, select an event type of Custom. This scenario
assumes that the event filter does not include IBM i message queue events.
g. In the Event Types table, click Director > Director Agent (Component
Category) > Disk Monitors. The Event Types table displays the disk drive
event types.
h. Click the appropriate disk drive event component category, for example,
Drive C: % Space Used (Component Category). The Event Types table
displays thresholds for the specified disk drive.
i. Select the thresholds that you want to activate the event filter, click Add.
j. After you add all the necessary thresholds, click Next.
k. On all subsequent pages (until the Summary page is displayed), accept the
default values or specify the values that you want to use, then click Next.

l. On the Summary page, review the settings for the event filter. Click Back if
you want to change any settings. When you are satisfied with the settings,
click Finish to create the event filter.
9. Create the event automation plan that uses the event filter you created in the
previous step:
Automation > Event Automation Plans. The Event Automation Plans page
is displayed.
b. Click Create to create the event automation plan. The Create Event
Automation Plan wizard is displayed.
c. On the Welcome page, click Next. The Name and Description page is
displayed.
d. On the Name and Description page, type a name for the event automation
plan, then click Next. The Targets page is displayed.
e. On the Targets page, use the Show list and the Available table to select the
target systems that you want to be affected by the event automation plan.
For each target system that you select, click Add.
f. After you add all the targets, click Next. The Events page is displayed.
g. On the Events page, from the Events list, select Advanced Event Filters.
The Event Filters table is displayed.
h. From the Event Filters table, select the event filter that you created
previously, then click Next. The Event Actions page is displayed.
i. On the Event Actions page, select one or more event actions that you want
to occur when this event automation plan is triggered, then click Next. The
Time Range page is displayed.
j. On the Time Range page, specify the time range that determines when the
event automation plan is active, then click Next. The Summary page is
displayed.
k. On the Summary page, review the settings for the event automation plan.
Click Back if you want to change any settings. When you are satisfied with
the settings, click Finish to create the event automation plan.
When triggered, the event automation plan reports the percentage of space used on
the disk drives, which it identifies by the associated letter names.
Scenario: Using a custom monitor view in an event

automation plan to report cluster drive data using drive letter
names
This example scenario describes how to create a monitor view and use that
monitor view in an event automation plan. The scenario assumes that you want to
create an event automation plan that monitors the percentage of disk drive space
used on specific cluster drives. Additionally, the event automation plan must
report information about the disk drives by using the letter names given to the
drives on the system.
All tasks for this scenario occur within the IBM Systems Director Web interface, so
the scenario assumes some familiarity with browsing the interface and using it to
perform tasks. Also, each of the following steps describes only one way to perform
the action, even if an alternative method exists.
For this scenario, the letter names for the cluster drives to monitor are drive m and
drive n.

To create a custom monitor view for cluster drives and use it within an event
automation plan, perform the following steps:
1. Select the resources that you want to monitor:
a. In the IBM Systems Director Web interface navigation area, click Resource
Explorer.
b. Drill down to select the resources that have the cluster drives that you want
to monitor, and select them.
c. Click Actions > System Status and Health > Monitors. If System Status
and Health > Monitors is not a choice available to you, one or more of the
resources you selected are not eligible for monitoring. Make sure to select
only resources that can be monitored.
The Monitors task is displayed with the systems that you specified in step 1b
already selected.
2. Start creating a monitor view by clicking Actions > Create. The Create View
page is displayed.
3. On the Create View page, in the Name field, type a name for the monitor
group that you are creating.
4. From the Show list, select Selected Resources.
5. Select the monitors for the individual cluster drives that you want to monitor:
a. In the Selected Resources table, select SystemName > Director Agent >
Windows Performance Monitors > LogicalDisk > DriveName, where
v SystemName is the name of the system that contains the cluster drives
v DriveName is the letter name of the cluster drive that you want to
monitor
Monitor information for the cluster drive is displayed.
b. In the Selected Resources table, select the monitors that you want to
include in this monitor group. In this scenario, the monitor must report the
percentage of disk space used, but no available monitor for that
measurement exists. Select % Free Space, for which a threshold can be set
to report the percentage used.
c. After selecting the monitor, click Add to add it to the monitor group, then
click OK.
Note: If you want to monitor drives on more than one system, for each system
that contains drives that you want to monitor, repeat step 5a through step 5c.
The Monitors page is displayed, and the Monitor Views table includes the
monitor view that you created.
6. Click the name of the monitor view that you created. The Monitor View page is
displayed.
7. Activate thresholds for the monitors. For each monitor for which you want to
create a threshold, perform the following actions:
a. Right-click the name of the monitor, then select Activate Threshold. The
Threshold page is displayed.
b. On the Threshold page, specify the threshold values and options that you
want to use, then click OK.
Tip: In this scenario, the maximum threshold value must be a high value of
75% or more disk space used. The monitor reports only the percentage of
free space. To report when the disk has 75% or more disk space used, the

threshold must be set for a low value of 25% or less free disk space.
The Monitor View page is displayed, and the table shows that the new
thresholds are active.
8. Create an event filter to be activated by the thresholds that you created
previously:
Automation > Event Filters. The Event Filters page is displayed.
b. Click Create to create the filter. The Create Event Filter wizard is displayed.
c. On the Welcome page, click Next. The Filter Name page is displayed.
d. On the Filter Name page, type the name you want to give this event filter,
then click Next. The Filter Type page is displayed.
e. On the Filter Type page, select a filter type of Threshold event filter, then
click Next. The Event Type page is displayed.
f. On the Event Type page, select an event type of Custom. This scenario
assumes that the event filter does not include IBM i message queue events.
g. In the Event Types table, click Director > Director Agent (Component
Category) > Windows Performance Monitors > Logicaldisk > DriveName
> % Free Space (Component Category), where DriveName is the name of
the cluster drive that you want to monitor. The Event Types table displays
the cluster drive event types.
h. Click Low Warning, then click Add.
Remember: To report a high value for the percentage of disk space used,
the threshold is set to report a low value for the percentage of disk space
free.
The selected event type is added to the Selected list.
i. After you add all the necessary thresholds, click Next.
j. On all subsequent pages (until the Summary page is displayed), accept the
default values or specify the values that you want to use, then click Next.
k. On the Summary page, review the settings for the event filter. Click Back if
you want to change any settings. When you are satisfied with the settings,
click Finish to create the event filter.
9. Create the event automation plan that uses the event filter you created in the
previous step:
Automation > Event Automation Plans. The Event Automation Plans page
is displayed.
b. Click Create to create the event automation plan. The Create Event
c. On the Welcome page, click Next. The Name and Description page is
displayed.
d. On the Name and Description page, type a name for the event automation
plan, then click Next. The Targets page is displayed.
e. On the Targets page, use the Show list and the Available table to select the
target systems that you want to be affected by the event automation plan.
For each target system that you select, click Add.
f. After you add all the targets, click Next. The Events page is displayed.
g. On the Events page, from the Events list, select Advanced Event Filters.
The Event Filters table is displayed.
h. From the Event Filters table, select the event filter that you created
previously, then click Next. The Event Actions page is displayed.

i. On the Event Actions page, select one or more event actions that you want
to occur when this event automation plan is triggered, then click Next. The
Time Range page is displayed.
j. On the Time Range page, specify the time range that determines when the
event automation plan is active, then click Next. The Summary page is
displayed.
k. On the Summary page, review the settings for the event automation plan.
Click Back if you want to change any settings. When you are satisfied with
the settings, click Finish to create the event automation plan.
When triggered, the event automation plan reports the percentage of free space on
the cluster drives. (In this case, the measurement desired is the percentage of space
used on the cluster drives, which you have to manually compute from the known
free space.) The data reported by the event automation plan identifies the cluster
drives by their associated letter names.
Monitors and thresholds

Monitors provide the means to retrieve and visually observe real-time changes in
system resources. Activating thresholds on monitors offers a way to trigger events
or report problems when the monitored resource exceeds the threshold. IBM
Systems Director includes monitor views, which are groups of monitors that
belong to a specific category. Examples of monitor views are AIX monitors and
SNMP monitors. Create custom monitor views that contain collections of monitors
that you find useful. Combine monitors, thresholds, and automation plans to
automate troubleshooting or corrective actions in response to reported warnings or
critical situations.
Monitors
Use monitors to observe changes in system resources on physical servers, virtual

servers, supported operating systems and hardware, and Virtual I/O Servers
(VIOS). The IBM Systems Director Web interface offers various locations where you
can use monitors. For example, on the Health Summary page, display one or more
specified monitors as graphs on the dashboard. View lists of monitors on the
Monitor page or see real-time data in columns on the Virtual Servers and Hosts
page. The Performance Summary page has a number of tabs, each of which offers
a selection of monitor columns. Additionally, some other resource tables offer the
ability to add or remove monitor columns, which provides an easy way to visually
monitor a variety of system resources within the table.
Monitor views are groups of commonly supported monitors. Some monitors that
are included in a monitor view might be unavailable to you because the managed
resource does not support them. Several factors determine which monitors are
available to use. Determining factors might include the operating system, hardware
configuration, and software configuration of the managed resource. Creating a
custom monitor view might make available to you additional monitors not
included in the default monitor views.
Thresholds
A threshold is a high or low limit that you do not want the monitored system
resource to exceed. For both the high threshold and the low threshold, you have
the option of specifying a warning value and a critical value. For example, the

high threshold for a monitor that measures the percentage of used space on a disk
drive might have a warning value of 80 and a critical value of 90.
Activating a threshold includes setting options that include specifying whether to

generate an event when the threshold is exceeded and determining the amount of
time the threshold waits before resending the information. When the monitored
resource exceeds the specified value for any threshold limit, the monitor displays
the appropriate icon for a warning or critical notification.
The next step in using monitors and thresholds is to combine them with one or
more event actions in an event action plan, making it possible to automate
troubleshooting and corrective responses to predetermined events. For more
information, see “Events, filters, and actions in event automation plans.”
Related concepts:
Events, filters, and actions in event automation plans
Related tasks:
Managing monitors
Managing thresholds
Monitor views
Use the Monitors task to monitor critical system resources on your managed
systems. IBM Systems Director arranges available monitors in groups called
monitor views. Each view represents a list of the most commonly available
monitors in a category, for example, monitors that are supported by AIX. Use
existing monitor views or create your own views that contain the selections of
individual monitors that you find useful.
Several factors determine the availability of individual monitors in a monitor view.

Determining factors might include the operating system, hardware configuration,
or software configuration of the managed resource. Depending on those factors,
some monitors included in a view might be unavailable in your environment.
Note: The monitor views described in the following topics are only those views
that ship with Systems Director. Installing an advanced plug-in might install one or
more additional monitor views that are not described here. For more information,
see the documentation for that plug-in.
When you create a monitor view, the Create View page presents all the available
monitors in each category, not just the most common monitors. Creating your own
monitor view makes available additional monitors that are not in the commonly
used sets of monitors included in the default monitor views.
Polling intervals (or how often data collection is performed) for monitors depend
on the managed system or device. In general, using the default settings, data
collections occur every 5 - 10 seconds, and the display refreshes every 10 - 20
seconds. Polling intervals affect the minimum granularity and timeliness of any
thresholds applied to a monitor.
AIX Monitors view

The AIX Monitors view contains some of the monitors most commonly reported by
installed versions of AIX as being available to IBM Systems Director. When you
create your own monitor view, additional individual AIX monitors might be
available.

The following table lists some of the most commonly available monitors from the
AIX Monitors view and the data that each monitor retrieves.
Note: Several factors determine the availability of the individual monitors listed in
the following table. Determining factors might include the operating system,
hardware configuration, or software configuration of the managed resource.
Depending on those factors, some monitors listed in the following table might be
unavailable to you, and some monitors that are not listed might be available.
Table 20. Monitors commonly available in the AIX Monitors view
Monitor name Data retrieved
™
Active Memory Sharing Enabled Whether memory sharing is enabled.
Possible values are:
v TRUE
v FALSE
Active Time of /dev/hdisk0 for processing The percentage of time that the physical disk
request (%) is active (bandwidth utilization for the
drive) or, in other words, the total time disk
requests are outstanding.
Active Virtual Memory (4K Pages) Active virtual memory in (4K page units)
Available Space of /dev/hdisk0 (MB) Amount of available space (in megabytes)
on the specified disk drive
Available Space of Filesystem / (MB) Amount of available disk space (in
megabytes) for the specified filesystem
Available Space of Filesystem /home (MB) Amount of available disk space (in
Available Space of Filesystem /opt (MB) Amount of available disk space (in
Available Space of Filesystem /tmp (MB) Amount of available disk space (in
Available Space of Filesystem /usr (MB) Amount of available disk space (in
Available Space of Filesystem /var (MB) Amount of available disk space (in
Capacity of /dev/hdisk0 (MB) Total capacity (in megabytes) of the specified
disk drive
CPU Computing Unit (%) A percentage that represents the average
time that the processor spends in the user
mode, system mode, idle state, and wait
state divided by the length of time being
measured
CPU Utilization The percentage of CPU capacity being used.
For uncapped partitions, this can be larger
than 100%, potentially much larger.
Uncapped partitions use all available
capacity in the shared processor pool.
Ethernet Kilobytes Received Rate of en0 Rate of data received (in kilobytes per
(KB/sec) second) by way of Ethernet connection
Ethernet Kilobytes Received Rate of lo0 Rate of data received (in kilobytes per

Table 20. Monitors commonly available in the AIX Monitors view (continued)
Ethernet Kilobytes Throughout Rate of en0 Rate of successful data communication
(KB/sec) (receipt and transmission, in kilobytes per
second) by way of Ethernet connection
Ethernet Kilobytes Throughout Rate of lo0 Rate of successful data communication
Ethernet Kilobytes Transmitted Rate of en0 Rate of data transmitted (in kilobytes per
Ethernet Kilobytes Transmitted Rate of lo0 Rate of data transmitted (in kilobytes per
Ethernet Packets Received Rate of en0 Rate of data received (in kilobytes per
(Packets/sec) second) by way of Ethernet connection
Ethernet Packets Received Rate of lo0 Rate of data received (in packets per second)
(Packets/sec) by way of Ethernet connection
Ethernet Packets Transmitted Rate of en0 Rate of data transmitted (in packets per
Ethernet Packets Transmitted Rate of lo0 Rate of data transmitted (in packets per
Memory Mode The memory mode
Memory Page Fault (Pages/sec) Rate of page faults (in pages per second)
Memory Page Steal (Pages/sec) Rate of page steals (in pages per second)
Memory Usage Memory being used (in megabytes)
Paging Space Remaining (MB) Amount of remaining paging space (in
megabytes)
Paging Space Reserved (MB) Amount of reserved paging space (in
megabytes)
Paging Space Total (MB) Total amount of paging space (in megabytes)
Paging Space Used (MB) Amount of used paging space (in
megabytes)
Time for Servicing Transfers in relation to The percentage of time that the physical disk
Active Time of /dev/hdisk0 (%) is busy servicing a transfer request
compared to the time the disk is active (the
time when transfer requests are outstanding)
Total Space of Filesystem / (MB) Amount of total disk space (in megabytes)
for the specified filesystem
Total Space of Filesystem /home (MB) Amount of total disk space (in megabytes)
Total Space of Filesystem /opt (MB) Amount of total disk space (in megabytes)
Total Space of Filesystem /tmp (MB) Amount of total disk space (in megabytes)
Total Space of Filesystem /usr (MB) Amount of total disk space (in megabytes)
Total Space of Filesystem /var (MB) Amount of total disk space (in megabytes)
Used Space of Filesystem / (MB) Amount of disk space used (in megabytes)

Table 20. Monitors commonly available in the AIX Monitors view (continued)
Used Space of Filesystem /home (MB) Amount of disk space used (in megabytes)
Used Space of Filesystem /opt (MB) Amount of disk space used (in megabytes)
Used Space of Filesystem /tmp (MB) Amount of disk space used (in megabytes)
Used Space of Filesystem /usr (MB) Amount of disk space used (in megabytes)
Used Space of Filesystem /var (MB) Amount of disk space used (in megabytes)
Note:
v These monitors gather data that is supplied by the agent.
v IBM Systems Director monitor and threshold memory values are measured in megabytes
(1024*1024 bytes). Some applications measure memory in millions of bytes. For example,
the memory value for 2 GB is the number of megabytes, or 2048 (1024*2).
All Monitors view

The All Monitors view contains all of the available individual monitors from the
other predefined views that ship with IBM Systems Director. Also, any individual
monitor not in the All Monitors view that is encountered while creating a monitor
view is added to the All Monitors view.
Note: Deleting a custom monitor view does not remove the individual monitors
from the All Monitors view.
When you create a monitor view, the Create View page presents all the available
monitors in each category, not just the most common monitors. Creating your own
monitor view makes available additional monitors that are not in the commonly
used sets of monitors included in the default monitor views.
For more information about available monitors, look at the information for the
specific view in which you are interested.
Column Management Monitors view

The Column Management Monitors view contains a selection of monitors offered
as resource table columns by the installed plug-ins. This monitor view is the only
view that ships with IBM Systems Director that you can edit, which means you
can add monitors that you want to use as columns in resource tables.
For example, when viewing a list of resources (not groups) on the Resource
Explorer page, click Actions > Columns to add columns to or remove columns
from the table. Some of the available columns to add or remove are monitors that
are included in the Column Management Monitors view.
Common CIM Monitors view

The Common CIM (Common Information Model) Monitors view contains some of
the most common CIM monitors. When you create your own monitor view,
additional individual CIM monitors might be available.

Common CIM Monitors view and the data that each monitor retrieves.
Notes:
v Linux for Power does not provide CIM-based metric profile metrics.
v Several factors determine the availability of the individual monitors listed in the
following table. Determining factors might include the operating system,
Depending on those factors, some monitors listed in the following table might
be unavailable to you, and some monitors that are not listed might be available.
Table 21. Monitors commonly available in the CIM Monitors view
CPU Utilization Rate at which the CPU is running
Disk % Space Available Percentage of available disk space
Disk Space Remaining (MB) Amount of remaining (available) disk space
(in megabytes)
Memory Usage (MB) Memory being used (in megabytes)
Packet received rate Number of IP packets received/second
Packet transmitted rate Number of IP Packets sent/second
Note:
v Linux for Power does not provide CIM Base Metrics Profile (DMTF Standard DSP1053)
based metrics.
following table. Determining factors might include the operating system, hardware
configuration, or software configuration of the managed resource. Depending on those
factors, some monitors listed in the following table might be unavailable to you, and
some monitors that are not listed might be available.
Common Monitors view

The Common Monitors view contains some of the most common monitors for
operating systems that are supported by IBM Systems Director. When you create
your own monitor view, additional individual operating systems monitors might
be available.
Common Monitors view and the data that each monitor retrieves.
Note:
following table. Determining factors might include the operating system,
Depending on those factors, some monitors listed in the following table might
be unavailable to you, and some monitors that are not listed might be available.
v The “CPU % Utilization monitor” is different from the “CPU Utilization %”
virtualization monitor. For more information about the “CPU Utilization %”
monitor, see the topic: “Virtualization Monitors view”.

Table 22. Monitors commonly available in the Common Monitors view
Active Processors Number of available processors
CPU Utilization Rate at which the CPU is running
Disk 0 Workload Workload managed by disk 0
Disk % Space Used Percentage of space used on the disk
Disk Space Used (MB) Amount of space used on the disk (in
megabytes)
Locked Memory (MB) Amount of memory locked (in megabytes)
megabytes)
megabytes)
megabytes)

Table 22. Monitors commonly available in the Common Monitors view (continued)
Note:
SNMP Monitors view

The SNMP (Simple Network Management Protocol) Monitors view contains
monitors supported by SNMP devices.
The SNMP (Simple Network Management Protocol) Monitors view contains

several monitors, such as the Network Bytes Transferred monitor, which retrieves
the total number of bytes (using SNMP) transmitted or received by the resource,
and monitors that require data collection from Remote Network MONitoring
(RMON).
Note: In some instances, SNMP monitors data will not be available for a
device. The capabilities of the SNMP device determine which monitors will
display data in the SNMP Monitors view.
IBM i Monitors view

Use these instructions to view and configure available IBM i CIM monitors. Doing
so helps you quickly start monitoring IBM i systems. Before starting, ensure that
you followed the instructions in the CIM section in the topic “Using IBM i
resources with an IBM Systems Director Server”.
The IBM i Monitors view shows some of the most common monitors reported by
installed versions of platform agent on IBM i as being available to IBM Systems
Director. When you create your own monitor view, more individual IBM i
monitors might be available.
To view IBM i monitors, follow these steps:

1. From the navigation pane, expand System Status and Health, then select
Monitors.
2. From the Monitors window, select IBM i Monitors and click Show Monitors.
Available Monitors
Following are some of the most commonly available monitors from the IBM i
Monitors view and the data that each monitor retrieves.
v For a more complete list of monitors that can be added to a custom view, see “
IBM i resource-monitor attributes”.
v For more information about CIM, see “Common Information Model”.
v For more information about monitors, see “IBM i System Metrics Providers”.
Note: Several factors determine monitor availability. Some factors include the
operating system, hardware configuration, and software configuration of the
managed resource. Depending on those factors, some monitors might not retrieve
the appropriate data and would then display “No Data Available”.

Table 23. Commonly available monitors in the IBM i Monitors view
Active Virtual Processors of Computer Average number of active virtual processors
System
Average disk active time percentage Average disk active time percentage
Average disk space utilization Average disk space utilization
Average interactive jobs transaction rate Average transaction rate of interactive jobs
Average interactive response time Average transaction response time of
interactive jobs
Average jobs transaction rate Average transaction rate of jobs
Average user pool faults Average user pool faults
Batch jobs logical database IO rate Database IO operations rate of all batch jobs
CPU % Utilization Percentage of defined CPU capacity that is
used by this system
CPU Consumption Index CPU time used, divided by the available
CPU time for this operating system
CPU External View Total of Operating External view CPU percentage. This is the
System (%) percentage of this partition CPU time used.
CPU External View User Mode of Operating External view user mode percentage
System (%)
CPU Internal View Idle of Operating System Idle percentage, as seen from within the
(%) operating system
CPU Internal View Total of Operating User mode percentage from the perspective
System (%) of the operating system
CPU Internal View User Mode of Operating User mode percentage as seen from within
System (%) the operating system
Free Physical Memory of Operating System Kilobytes of unused, available physical
(Kilobytes) memory
Free Space in Page Files of Operating Kilobytes of memory that can be mapped
System (Kilobytes) into the operating systems’ paging files
Free Virtual Memory of Operating System Kilobytes of unused, available virtual
(Kilobytes) memory
Interactive jobs CPU percentage Percentage of CPU used for interactive jobs
Maximum disk active time percentage Maximum disk active time percentage
Maximum disk space utilization Maximum disk space utilization
Maximum interactive response time Maximum transaction response time of
interactive jobs
Maximum user pool faults Maximum user pool faults
Number of Users of Operating System Number of user sessions for which the
operating system is storing state information
Page In Rate of Operating System/sec Number of pages that are paged in per
second
Process Count Number of processes that are currently
loaded on the operating system
Total CPU Time of Operating System Total CPU time, sum of KernelModeTime
(Milliseconds) and UserModeTime, on operating system
level

Table 23. Commonly available monitors in the IBM i Monitors view (continued)
Unused Global CPU Capacity of Computer Milliseconds of CPU time that are not used
System (Milliseconds) on the global server level
Unused Partition CPU Capacity of Reserved but unused capacity for this
Computer System (Milliseconds) operating system container
User Mode Time of Operating System Time in user mode, in milliseconds, on
(Milliseconds) operating system level
Related reference:
Common information Model
IBM i System Metrics Providers
IBM i resource-monitor attributes

These are some of the most commonly used resource-monitor attributes for the
IBM i operating system.
Resource
monitor Attributes
File Notes:
1. File-monitor attributes can be files or directories.
2. For compatible file system types, the “Directory exists” or “File exists”
attribute (depending on which is applicable) is always valid data.
3. If there are more directories, additional subelements are displayed.
4. A directory can contain hundreds of subelements. If it does, a directory
might take 5 seconds or longer to open.
5. QSYS.LIB can contain thousands of subelements. If a timeout occurs,
reopening the directory after a timeout increases the timeout value, and
might increase the timeout value sufficiently for the operation to
complete.
v Directory
– Directory exists
– Last modified
– Directory attributes
– Directory owner
– Directory size (bytes)
– Object type
v File
– Checksum
– File exists
– Last modified
– File attributes
– File owner
– File size (bytes)
– Object type

Resource
monitor Attributes
File system Note: The file system monitor attributes for specific directories are provided
for typical IBM i directories. If one of these directories does not exist, the
attribute is not displayed.
v /
v /bin
v /dev
v /etc
v /home
v /lib
v /tmp
v /usr
v /var
List of v Directory attributes
directory v Directory exists
contents v Directory owner
v Directory size (bytes)
v Last modified
v Object type
Process Note: The number of applications or executable files that a process monitor
checks can vary. The IBM Systems Director user configures the processes
that are monitored using the Process Monitor task in the IBM Systems
Director Web interface. Each of the process-monitor attributes is displayed
for each executable file that is monitored.
v Current active processes
v Maximum running at once
v Maximum running yesterday
v New executions counted
v Times failed to start
v Time started
v Time stopped
v Total execution time
v Execution time yesterday
I/O v Auxiliary IOP Use %
processors v IOP All Comm. Use %
v IOP Disk Use %
v IOP LAN Use %
v IOP Memory Free (KB)
v IOP Operational Status
0 = The status field does not apply to this resource or could not be
determined.
1 = Operational; the resource is operational.
2 = Inoperative; the resource is not operational.
3 = Not detected; the presence of the resource could not be detected.
v IOP Optical Use %
v IOP SDLC Use %
v IOP System Function Use %
v IOP Tape Use %
v IOP Twinaxial Use %
v IOP X.25 Use %
v Primary IOP Use %
Job queues v Job Queue Status
0 = Released; the queue is released.
1 = Held; the queue is held.
v Jobs in Queue

Resource
monitor Attributes
Job statistics v Batch Jobs Ended, Output Waiting
v Batch Jobs Ending
v Batch Jobs Held on Job Queue
v Batch Jobs Held while Running
v Batch Jobs on Held Job Queue
v Batch Jobs on Unassigned Job Queue
v Batch Jobs Running
v Batch Jobs Waiting for Messages
v Batch Jobs Waiting to Run
v Jobs on System
NetServer v Average Response Time (Milliseconds)
statistics v File Opens/Minute
v Kbytes Received per Minute
v Kbytes Sent per Minute
v Password Violations
v Print Jobs Queued/Minute
v Session Starts/Minute
Physical v Disk Arm Utilization %
disks v Disk Average Queue Length
v Disk Mirroring Status
0 = Not mirrored
1 = Active
2 = Resuming
3 = Suspended
v Disk Operational Status
0 = The status field does not apply to this resource or could not be
determined.
1 = Operational; the resource is operational.
2 = Inoperative; the resource is not operational.
3 = Not detected; the presence of the resource could not be detected.
v Disk Processor Utilization %
v Disk Read Commands/Minute
v Disk Read Kbytes/Minute
v Disk Space Free (MB)
v Disk Space Used %
v Disk Write Commands/Minute
v Disk Write Kbytes/Minute
Storage v Active to Ineligible (Transitions/Minute)
pools v Active to Wait (Transitions/Minute)
v Database Faults per Second
v Database Pages per Second
v Non-database Faults per Second
v Non-database Pages per Second
v Wait to Ineligible (Transitions/Minute)
Subsystems v Subsystem % of Job Limit
v Subsystem Active Jobs
v Subsystem Status
0 = Inactive; the subsystem is not running.
1 = Active; the subsystem is running.
System v CPU Utilization %
statistics v Current Temp Storage Used (MB)
v Max Temp Storage Used (MB)
v Permanent Addresses Used %
v System ASP Used %
v Temporary Addresses Used %

Resource
monitor Attributes
User v Users Disconnected
statistics v Users Signed Off, Output Waiting
v Users Signed On
v Users Suspended by Group Jobs
v Users Suspended by System Request
VIOS Monitors view

The VIOS (Virtual I/O Server) Monitors view contains the most common monitors
reported by VIOS as being available to IBM Systems Director. When you create
your own monitor view, additional individual VIOS monitors might be available.
The following table lists the monitors included in the VIOS Monitors view and the
data that each monitor retrieves.
Note: Several factors determine the availability of the individual monitors listed in
the following table. Determining factors might include the operating system,
Depending on those factors, some monitors listed in the following table might be
unavailable to you, and some monitors that are not listed might be available.
Table 24. Monitors commonly available in the VIOS Monitors view
Active Memory Sharing Enabled Whether memory sharing is enabled.
Possible values are:
v TRUE
v FALSE
Active Time of /dev/hdisk0 for processing The percentage of time that the physical disk
request (%) is active (bandwidth utilization for the
drive) or, in other words, the total time disk
requests are outstanding.
Active Virtual Memory (4 K Pages) Active virtual memory (in 4 K page units)
Available Space of /dev/hdisk0 (MB) Amount of available space (in megabytes)
on the specified disk drive
Available Space of Filesystem / (MB) Amount of available disk space (in
Available Space of Filesystem /home (MB) Amount of available disk space (in
Available Space of Filesystem /opt (MB) Amount of available disk space (in
Available Space of Filesystem /tmp (MB) Amount of available disk space (in
Available Space of Filesystem /usr (MB) Amount of available disk space (in
Available Space of Filesystem /var (MB) Amount of available disk space (in
Capacity of /dev/hdisk0 (MB) Total capacity (in megabytes) of the specified
disk drive

Table 24. Monitors commonly available in the VIOS Monitors view (continued)
CPU Computing Unit (%) A percentage that represents the average
time that the processor spends in the user
mode, system mode, idle state, and wait
state divided by the length of time being
measured
CPU Utilization Rate at which the processor is running
Ethernet Kilobytes Received Rate of en0 Rate of data received (in kilobytes per
(KB/sec) second) by way of ethernet connection
Ethernet Kilobytes Received Rate of lo0 Rate of data received (in kilobytes per
(KB/sec) second) by way of ethernet connection
Ethernet Kilobytes Throughout Rate of en0 Rate of successful data communication
Ethernet Kilobytes Throughout Rate of lo0 Rate of successful data communication
Ethernet Kilobytes Transmitted Rate of en0 Rate of data transmitted (in kilobytes per
Ethernet Kilobytes Transmitted Rate of lo0 Rate of data transmitted (in kilobytes per
Ethernet Packets Received Rate of en0 Rate of data received (in packets per second)
Ethernet Packets Received Rate of lo0 Rate of data received (in packets per second)
Ethernet Packets Transmitted Rate of en0 Rate of ethernet data transmitted (in packets
(Packets/sec) per second)
Ethernet Packets Transmitted Rate of lo0 Rate of data transmitted (in packets per
(Packets/sec) second) by way of Ethernet connection
Memory Mode The memory mode
Memory Page Fault (Pages/sec) Rate of page faults (in pages per second)
Memory Page Steal (Pages/sec) Rate of page steals (in pages per second)
megabytes)
megabytes)
megabytes)
Shared Ethernet Adapter ent4 Byte In Rate Rate at which the adapter is receiving data
(Kilobytes/sec) (in kilobytes per second)
Shared Ethernet Adapter ent4 Byte Out Rate Rate at which the adapter is transmitting
(Kilobytes/sec) data (in kilobytes per second)
Shared Ethernet Adapter ent4 Packet In/sec Rate at which the adapter is receiving data
(in packets per second)
Shared Ethernet Adapter ent4 Packet Rate at which the adapter is transmitting
Out/sec data (in packets per second)

Virtual Target Device vtscsi0 Read Rate Rate at which the specified device is reading
Virtual Target Device vtscsi0 Transfer Rate Rate at which the specified device is
(Count for transmission/sec) transferring data (in count for transmission
per second)
Virtual Target Device vtscsi0 Write Rate Rate at which the specified device is writing
per second)
per second)

Note:
Managing monitors
The Monitors task provides the tools that you need to retrieve real-time status and
quantitative data for specific properties and attributes of resources in your
environment. You can also set thresholds for the monitors, graph the data that
monitors retrieve, and drill down to quickly view the status of resources for each
system and the name of the monitor so that you can view its properties.
Note: For a list of items that you should consider while working with resource
monitors and event automation plans, see “Resource-monitor threshold settings
change unexpectedly”.
Related reference:
Resource-monitor threshold settings change unexpectedly
Viewing a monitor
Use the Monitors task to view the monitors you have set for your resource.
To view a monitor, complete the following steps:

1. Open the Monitors task as follows:
Explorer.
b. Either select a group or drill down to select a resource within a group.
c. Click Actions > System Status and Health > Monitors.
The Monitors task with a table listing applicable monitor views and
information about each monitor view is displayed.
2. To select one or more target resources, click Browse. The Context Chooser is
displayed.
3. Use the Context Chooser to add one or more resources or groups of resources
as a target:
a. To add a group, select the group that you want to add as a target. To add a
single resource, drill down from the group that includes the resource that
you want to add and select the resource.
b. Click Add.
c. Continue selecting groups or resources as needed.
d. When you are finished adding targets, click OK.

6. View the properties for the monitor in the table or click the monitor to view
additional properties and details.
Creating a monitor view

Use the Monitors task to create views of monitors.
Ensure that the resources on which you create the monitor views have the
appropriate level of agent running on them. Agent level requirements for creating
monitors are as follows:
v Common monitors are available only for systems running Common Agent or
IBM Director Agent version 5.20.
v Common CIM monitors are available for all Common Agent managed systems
(except for Linux on System x Common Agent managed systems), all Windows
Platform Agent managed systems, and Linux on System z Platform Agent
managed systems.
v No common monitors or common CIM monitors are available for Agentless
managed systems.
To create a monitor view, complete the following steps:

Explorer.
2. Click Create. The Create View page is displayed.
3. In the Name field, specify a name for the new monitor view.
4. Specify an optional description for the monitor view.
5. In the Show field, select Selected Resources to choose from existing monitored
resources or Monitor Views to choose from existing monitor views. For more
information about monitors that are shipped with Systems Director, see
“Monitor views.”
6. In the Available table, double-click a monitor to view and select all the
monitored resources that you want to add to your new monitor view.
For example, double-click Disk Monitors to view monitors that are available
for each hard disk drive present in a system.
7. Click Add.
Note: Add is activated only when an item that can be monitored, such as CPU
Utilization, is selected. If you select any items that cannot be monitored, Add
remains deactivated.
8. Click OK.
The new monitor view appears in the Monitor Views table.

Related reference:
Editing a monitor view

Use the Monitors task to edit monitor views.
To edit a monitor view, complete the following steps:

Explorer.
2. Select the monitor view that you want to edit.
3. Click Actions > Edit.
4. Modify the monitor view values as needed.
5. Click OK.
Deleting a monitor view

You can delete monitor views that you no longer need.
A monitor view must exist before you can delete it.
To delete a monitor view, complete the following steps:

Explorer.
2. Select the monitor view that you want to delete.
3. Click Actions > Delete.
4. Click Delete.
The monitor view will no longer appear in the Monitors Views table.
Graphing a monitor
Use the Monitor View task to view graphical representations of the monitors on
your resource.
To graph a monitor, complete the following steps:

Explorer.

2. Select the monitor for which you want to create a graph.
3. Click Actions > Graph. The Graph page is displayed.
4. Modify the options of the graph, including graph type and zoom level, as
needed.
Managing thresholds
The Thresholds task offers a consolidated view of all the thresholds that you have
created to monitor the dynamic properties of your resource. This task saves you
from searching for them all in the Monitors task.
Note: Although there are smcli resource-monitor thresholds commands, you must
use the user interface to manage thresholds for advanced managers.
Viewing a threshold
Use the Thresholds task to view thresholds that are set for the monitors on your
resources or use the Resource Explorer task to view thresholds for a specific
resource.
To view a threshold, complete the following steps that apply to the method that
you want to use:
1. View thresholds that are set for the monitors on your resources:
a. In the IBM Systems Director Web interface navigation area, expand System
Status and Health > Thresholds. The Thresholds page with a table listing
applicable thresholds and information about each threshold is displayed.
b. View the properties for the threshold in the table or click the threshold to
view additional properties and details.
2. View thresholds for a specific resource:
Explorer.
b. Navigate to the resource for which you want to view the threshold.
c. From the Resource Explorer table, right-click the resource and select System
Status and Health > Thresholds. The Thresholds page is displayed.
Creating a threshold
You can create a threshold by activating a threshold on a specific monitor.
A monitor must have a threshold status of None before you can create a threshold
for it.
Tip: You can configure an event automation plan to send an e-mail notification
when a specified resource reaches a predefined threshold.
To create a threshold for a specific monitor, complete the following steps:

Explorer.

4. Select the monitor for which you want to create a threshold.
5. Click Actions > Activate Threshold. The Threshold page is displayed.
6. Input and modify the threshold settings as needed.
7. Click OK.
The threshold status value in the Monitor View table will change from None to
Activated and the threshold settings will be displayed
Creating an event automation plan based on an existing

threshold
Use this method to create an event automation plan that uses the target system
and the event types that are specified by an existing active threshold. When
creating an event automation plan based on an existing threshold, you need to
specify only a few settings: the threshold levels that you want to monitor, the
event actions that you want the plan to include, and the time range that
determines when the plan is active.
1. From the Monitor View page or the Thresholds page in the IBM Systems
Director Web interface, select a monitor with an active threshold.
2. Click Create Event Automation plan. The Event Automation Plan wizard is
displayed.
3. Complete the wizard, then click Finish.
Related tasks:
“Creating an event automation plan” on page 322
Editing a threshold
Use the Thresholds task to edit thresholds that are set for the monitors on your
resource.
To edit a threshold, complete the following steps:

2. Select the threshold that you want to edit.
3. Click Actions > Edit Threshold. The Threshold page is displayed.
4. Modify the settings for the threshold as needed.
5. Click OK.
Activating a threshold
You can activate thresholds that have been previously deactivated.
A threshold must be in the deactivated (disabled) state before you can activate it.
To activate a threshold, complete the following steps:

2. Select the deactivated threshold that you want to activate.
3. Click Activate Threshold. The Threshold page is displayed.
4. Optional: Modify any settings for the threshold that you want to change.
5. Click OK.
The threshold status value in the thresholds table will change from deactivated to
activated.
Deactivating a threshold
You can deactivate thresholds that have been previously activated.
A threshold must be in the activated (enabled) state before you can deactivate it.
To deactivate a threshold, complete the following steps:

2. Select the deactivated threshold that you want to activate.
3. Click Actions > Deactivate Threshold.
4. Click OK.
The threshold status value in the thresholds table will change from Activated to
Deactivated.
Deleting a threshold
You can delete thresholds that you no longer want associated with your monitors.
A threshold must exist before you can delete it.
To delete a threshold, complete the following steps:

2. Select the threshold that you want to delete.
3. Click Actions > Delete Threshold.
4. Click Delete.
The threshold will no longer appear in the thresholds table.
Managing status set entries

The status set entries that are reported by resources that are managed by IBM
Systems Director help to indicate the overall health of your environment. By
managing and monitoring status set entries, which include problems and
compliance issues, you can help prevent undetected failures that cause network
interruptions and data loss.

Status set entries that are reported by resources in your environment are tracked
by IBM Systems Director. You can use IBM Systems Director to quickly navigate to
and display these entries. You can also control the entries that are displayed and
collected by IBM Systems Director.
The Health Summary task displays several resource-monitoring tools on a single

page. Together, these tools provide a single, consolidated interface with which you
can quickly view the status of important areas of your environment, monitor
critical resources, and view the contents of user-defined health summary groups.
You can also use other tasks in IBM Systems Director Web interface, such as
Resource Explorer and Find a Resource to quickly navigate to specific resources.
After you have located a specific resource, you can use the Actions menu to view
its status.
You can perform the following actions on status set entries that are tracked by IBM
Systems Director:
Delete Clears a status set entry. When a status set entry is deleted, the individual
status set entry is removed from IBM Systems Director tasks that might
display it; however, future occurrences of the entry are still tracked and
counted by IBM Systems Director.
Ignore Deactivates a status set entry. When a status set entry is deactivated for a
system or a specific entry type, the systems continues to generate that
entry and the entry still occurs. However, IBM Systems Director tracks its
status in only the event log. Future occurrences of the entry that occur for
the specified system are not displayed or counted by IBM Systems Director
unless you reactivate the status set entry.
Activate
Activates a status set entry that has been deactivated. When a status set
entry is activated, the individual status set entry and all future occurrences
of the entry are tracked and counted by IBM Systems Director.
Viewing a specific status set entry

by IBM Systems Director and displayed in the applicable health summary tasks
and panels. Use the System Status and Health tasks to view status set entries that
have been collected by IBM Systems Director.
You can view status set entries for only those resources to which you have access.
To view a specific status set entry, complete the following steps:

Status and Health and navigate to the type of status set entry that you want to
view:
v To navigate to a hardware or power-related status set entry, click Problems.
The Problems task lists only those elevated status set entries that are problem
status set entries that have been reported to IBM Systems Director Server.
The data listed here is a subset of what is listed on the Active Status page.
From the Problems page, you can navigate to, display, and manage these
status set entries. You can also ignore entries to prevent IBM Systems
Director Server from collecting them or delete the entries to remove them
from the list until they occur again.
v To navigate to all status set entries, including problems, click Active Status.

Systems Director Server from collecting them or delete the entries to remove
them from the list until they occur again.
A table listing applicable status set entries and information about each entry is
displayed.
2. View the properties for the status set entry in the table or click the status set
entry to view additional properties and details.
You can use the Ignore, Activate, and Delete actions to control the entries that are
displayed and collected.
Viewing status set entries for a specific resource

and panels. Use the Resource Explorer task to view status set entries for specific
resources.
To view the status information for a specific resource, complete the following steps:
Explorer.
2. In the table view, drill down to the resource that you want to view within the
group that contains that resource.
3. Select the resource that you want to view.
4. Click Actions > System Status and Health > Active Status. The active status
set entries are listed for the resource.
Note: In a targeted launch scenario, only status that applies to the target is
displayed.
Viewing status set entries for a group of resources

and panels. Use the Navigate Resources task to view status set entries for the
resources that belong to a specific group.
To view status set entries for a group of resources, complete the following steps:
1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
2. In the table view, select one or more groups from the list.
3. Click Actions > System Status and Health > Active Status. The active status
set entries are listed for the resources that belong to the selected group.

Note: In a targeted launch scenario, only status that applies to the targets is
displayed.
Activating a status set entry

You can activate (un-ignore) individual status set entries that have been
deactivated (ignored). Status set entries that are activated are tracked by IBM
Systems Director and are displayed in the applicable Health Summary tasks and
panels.
When status set entries are activated for a system or a specific entry type, IBM
Systems Director tracks them.
To activate a status set entry, complete the following steps:

view:
displayed.
2. Click Ignored Status.
3. Select the entry that you want to activate.
4. Click Activate.
Deactivating a status set entry

You can deactivate (ignore) individual status set entries that you do not want IBM
Systems Director to collect. Status set entries that are deactivated are ignored by
IBM Systems Director and are not displayed in the health summary tasks and
panels.
When a status set entry is deactivated for a system or a specific entry type, the
systems continue to generate that entry and the entry still occurs. However, IBM
Systems Director does not track its status. Future occurrences of the entry on the
specified system will not be displayed or counted.
To deactivate a status set entry, complete the following steps:

view:
displayed.
2. Select the entry that you want to deactivate.
3. Click Ignore.
4. In the Ignore Confirmation window, select the option that represents the
desired scope for the ignore operation:
v Selected resources only
v All resources
5. Click OK.
You can display entries that have been deactivated and then reactivate them. You
can also delete individual entries to clear the specific occurrence of the entry but
not future occurrences.
Deleting a status set entry

You can delete individual status set entries that you do not want IBM Systems
Director to collect. Status set entries that are deleted are not displayed in the health
summary tasks and panels.
When a status set entry is deleted, the individual status set entry is removed from
IBM Systems Director tasks that might display it; however, future occurrences of
the entry are still tracked and counted by IBM Systems Director.
To delete a status set entry, complete the following steps:

view:

displayed.
2. Select the entry that you want to delete.
3. Click Delete.
4. In the Delete Confirmation window, click Yes.
An entry is deleted for only that instance. If the entry occurs again in the future,
IBM Systems Director will collect it.
Deleting a Power Systems status set entry

When IBM Systems Director receives an event that needs to be listed as a problem
, it creates a status set entry for the event. Some Power Systems status set entries
are not automatically cleared. Follow the steps in this topic to manually close and
delete Power Systems status set entries.
You might have two different types of Power Systems status set entries:
Service status entries
For instructions to close and delete service status entries, see this topic:
“Manage Service and Support Manager events”
Hardware status entries
Hardware status entries are not deleted automatically. If you want to delete
them, follow these instructions:
1. In the IBM Systems Director left navigation pane, expand System Status and
Health and navigate to the Problems view or the Active Status view.
2. Select the entry that you want to delete and click delete. When you delete a
Power Systems status set entry, Systems Director removes the entry from every
view where it was visible.
3. In the confirmation window, click Yes.
Systems Director deletes only that instance. If the entry recurs, Systems Director
collects it again.
Related tasks:
Manage Service and Support Manager events
Managing the event log

An event is an occurrence of significance to a task or resource. Examples of events
include operation completion, hardware component failure, or a processor
threshold being exceeded. The Event Log task displays all events that the
management server receives from any resource for which you can view events.

Related concepts:
Events
Changing backup event log preferences

The event log preferences file specifies the backup event log maximum file size
and the maximum number of backup files to keep. Use these instructions to
change the event log preferences.
In System Settings, you can specify how many events to keep in the event log.
When the event log is full and a new event is received, the oldest event is moved
to the backup event log. When the backup event log is full, a new one is created.
The old one might be deleted, depending on the backup event log preferences.
To view events in the backup event log, open data/eventLogBackup_n.log, where n

is incremented every time a new backup event log file is created.
To change the preferences, follow these steps:

1. Modify this file: data/LogManagement.properties.
max_number_of_backup_files=1
Maximum number of backup files to keep. The file name is
eventLogBackup_n.
size_of_each_backup_file=1
Size of each backup file, in megabytes.
2. Restart IBM Systems Director Server.
Changing event log preferences

The Event Log Preferences task is used to configure the options for the events that
are retrieved and displayed in the event log. You can set the number of events that
are retrieved and the duration of time over which those events are retrieved (time
range).
Note: Use the server preferences settings page to set the maximum number of
events that are stored in the management server log file.
To change the event log preferences, complete the following steps:

and then click Event Log Preferences. The Event Log Preferences page is
displayed.
2. On the Event Log Preferences page, make the desired changes.
3. Click OK.
Creating an event filter from an event

You can create a simple event filter for use in an event automation plan from an
event in the Event Log.
To create an event filter, complete the following steps:

1. In the IBM Systems Director navigation area, expand System Status and
Health and click Event Log.
2. In the Events table, select the event that you want to use for an event filter.
3. Click Create Filter. The Create Filter window is displayed. At the bottom of the
window, the selected event type is displayed.

4. In the Event filter name field, type the name for the event filter.
5. Optional: In the Description field, type a description to help you identify this
event filter. The description is displayed in the Event Filter window.
6. Click OK.
When you create an event automation plan in the Event Automation Plan wizard,
on the Events page select Advanced Event Filters from the Events list. the Event
Filters table displays all available event filters, including the one created from the
event log.
Related concepts:
Event filters
Related tasks:
Managing event automation plans
Deleting an event
You can delete individual events that you do not want IBM Systems Director to
display in the event log.
To delete an event, complete the following steps:

1. Open the event log as follows:
Explorer.
c. Click Actions > System Status and Health > Event Log.
The event log table is displayed.
2. Select the event that you want to delete.
3. Click Delete.
4. In the Delete Confirmation window, click OK.
Replying to an IBM i inquiry message event

Follow these to reply to an individual IBM i inquiry message event displayed in
the event log.
1. In the IBM Systems Director navigation pane, expand System Status and
Health and click Event Log. The event log table opens.
2. Select the single inquiry message event that you want to reply to.
3. Click Reply. The Reply to Message window opens.
4. In the Reply field, enter your message.
5. Click OK.
Viewing events
Use the Event Log task to view events that are stored in the event log. The event
log includes all events that are received by the management server from any
resource to which you have authorization to view events.
You can view all events, events for a specific managed resource or group, or events
that are filtered using a specific criteria.
Note: The event log does not automatically refresh. To refresh the information in
the table, change the event filter or click Refresh.

To view events in the event log, complete the following steps:
1. Open the event log as follows:
Explorer.
c. Click Actions > System Status and Health > Event Log.
The event log table is displayed.
2. Click Event Filter and select the filter criteria that you want to use. The default
filter is All Events. The event log displays the events that have been received
by IBM Systems Director Server and that match the filter criteria.
Note: The number of events that are displayed is limited by the event-log
preferences settings. By default, the event log displays the last 500 events that
occurred over the last 24 hours. Use the Event Log Preferences page to change
the event log preferences.
3. View the properties for the event in the table or click the event to view
additional properties and details.
You can use the Delete action to control the events that are displayed.
Viewing SNMP device attributes

You can use the SNMP Browser task to view the attributes of SNMP devices, for
example, hubs, routers, or other management devices that are compliant with
SNMP. You can use the SNMP Browser for management based on SNMP,
troubleshooting, or monitoring the performance of SNMP devices.
To view SNMP devices, complete the following steps:

Status and Health, then click SNMP Browser.
2. In the SNMP Browser window, use the Target field or click Browse to select an
available target. The SNMP Systems table displays entries that represent the
collection of managed objects in the Management Information Base (MIB)
module.
3. To perform an action on an entry in the table, right-click the entry and select an
action.
The SNMP Systems table displays information about the SNMP resource,
including all the managed objects defined in the MIB module and the MIB itself.
You can inspect the objects or perform actions on them.
Note: To configure your SNMP devices, see “Accessing a secured system with
configure access”.
Related tasks:
Working with tables
Managing MIB files

You can import, remove, and compile Management Information Base (MIB) files
for SNMP-compliant resources.

Compiling a MIB file
You can compile Management Information Base (MIB) files that are located on the
IBM Systems Director Server.
The MIB files are located in the install_root\proddata\snmp directory, where

install_root is the root directory of your IBM Systems Director installation. Note that
this path uses the backslash (\) to delimit the directory; depending on the system
that you are using, you might be required to enter the path using the forward
slash (/).
When IBM Systems Director Server starts, it loads a default set of compiled MIB
files that are commonly used. If you have updated the list of MIB files to load,
your most recent selections are loaded.
MIB data is stored in its own persistent-storage file, name.mibdata, where name is
the MIB definition name. These files are located in the install_root\proddata\snmp
directory. By deleting these files and loadedmibs.dat, you can remove all MIB data
in IBM Systems Director but retain other persistent-storage data.
To compile a MIB file, complete the following steps:

and then click Manage MIBs.
2. On the Manage MIBs page, click Import MIB File.
3. On the Import MIB file page, click the File name field or click Browse to search
for an MIB file. (To compile successfully, the MIB file must be located on the
IBM Systems Director Server.)
4. Select the MIB file that you want to import, then click OK. Click Cancel to
close the page without importing a MIB file.
A message displays that indicates whether the compilation was successful. The
message provides a link to view logs.
Loading MIB files into memory

You can load Management Information Base (MIB) files into memory.
To load MIB files into memory, complete the following steps:

and then click Manage MIBs.
2. On the Manage MIB files page, in the Available MIB files list, select the MIB
files that you want to load into memory.
3. Click Add to transfer the selected MIB files to the Loaded MIB files list.
the page without saving the settings, click Cancel. To reset the selected MIB
files to the server default MIB installation, click Restore Defaults. You still
must click OK or Apply to save the restored settings.
Managing process monitors

You can use process monitors to generate events when an application process
starts, stops, or fails to start.

Viewing process monitors
You can view a list of the process monitors that exist on a managed system.
To view a list of the process monitors that exist on a managed system, complete
Explorer.
2. Navigate to the resource for which you want to view the process monitors.
3. Right-click the resource and select System Status and Health > Process
Monitors.
Note: The Process Monitors selection item displays for only those resources
that are operating systems.
The Process Monitors page, which lists all the process monitors created for the
selected resource, is displayed.
Creating and configuring a process monitor

To monitor a process, you must create and configure a monitor. This is supported
only on systems that have Common Agent installed.
To create and configure a process monitor, complete the following steps:

Explorer.
2. Navigate to the resource for which you want to create a process monitor.
Monitors.
4. On the Process Monitors page, click Create. The Create window is displayed.
5. In the Create window, type the executable file name of the application process
that you want to monitor.
6. Select any combination of the Start, Terminate, and Fail to start after reboot
check boxes, to specify the actions that you want to monitor. Selecting one or
more actions activates the process monitor. A process monitor does nothing
unless you select at least one action.
7. If you select Fail to start after reboot, type a timeout value. This value is the
number of seconds that the process monitor waits for the application process to
start before generating a fail event.
8. Click OK to save the process monitor.
The new process monitor is displayed in the Process Monitors table on the Process
Monitors page.
Removing process monitors

You can remove any number of existing process monitors from a managed
resource.
To remove one or more process monitors from a managed resource, complete the
following steps:

Explorer.
2. Navigate to the resource from which you want to remove one or more process
monitors.
Monitors.
4. Select one or more process monitors that you want to remove.
5. Click Delete to remove the selected process monitors and any associated
thresholds. A confirmation dialog displays.
6. Click OK. The selected process monitors and any associated thresholds are
removed and no longer appear in the Process Monitors table.
Related tasks:
Scheduling tasks
Recording resource-monitor statistics

You can view statistics about critical system resources, such as processor, disk, and
memory by recording resource-monitor statistics. Record resource-monitor statistics
for an individual managed system, multiple systems specified by IP addresses or
host names, or system groups by using the smcli resource-monitor recording
commands.
Use the commands to start or stop recording statistics (resource-monitor values),

and to export recordings to archive or review the statistics. You can export
recordings to a file in text, comma separated values (CSV), HTML, or XML
formats. You can also delete resource-monitor recordings.
Note: Because IBM Systems Director stores the recordings in binary format, you
must use the smcli resource-monitor recording commands to work with the
recordings.
lsresmonrec
Use the lsresmonrec command to list information about previously configured
resource-monitor recordings.
mkresmonrec
Use the mkresmonrec command to record resource-monitor values.
rmresmonrec
Use the rmresmonrec command to delete one or more resource-monitor recordings.
stopresmonrec
Use the stopresmonrec command to stop recording resource-monitor values.

Chapter 6. Automating tasks
By creating event automation plans and applying them to specific systems, you can
automate tasks and other responses to situations that occur in your
systems-management environment. For example, when a specified threshold is
reached or a specified event occurs, you can be notified by e-mail or phone. Or,
you can configure an event automation plan to start a program on a system or
change a system variable when a specific event occurs.
Important: If you are using predefined IBM Systems Director roles, you must have
SMAdministrator authority to use the automation tasks in the IBM Systems
IBM Systems Director provides the Event Automation Plan wizard as a quick and
simple way to create event automation plans that meet most systems-management
needs. Using the Event Automation Plan wizard, you can create plans that monitor
for the most typical situations in systems-management environments, including,
but not limited to, the following examples:
v Critical hardware events from all systems in your environment
v Processor (CPU) use in a specific group of systems, such as all servers running
Linux
v All Common Agent managed systems to determine whether Common Agent
goes offline
v The status of updates that are underway
v Disk space use in systems, such as those that store database data
Then, in response to the situations that you are monitoring, you can choose to send
a page or e-mail, or you can start a program on a system. For more information
about creating event automation plans and using the Event Automation Plan
wizard, see “Creating an event automation plan.”
The Event Automation Plan wizard also provides advanced event actions and
event filter options that you can use to create event automation plans that can
meet very specific needs in your systems-management environment.
Successful implementation of event automation plans requires planning and

consideration of how you will implement them. Providing thoughtful descriptions
for your event automation plans can be particularly helpful. For more information,
see “Planning for event automation plan implementations.”

Related concepts:
eLearning: Automating tasks

Related tasks:
Related reference:
Planning for events
Event and event automation plan commands
Events, filters, and actions in event automation plans

An event automation plan lets you automatically respond to a situation in your
IBM Systems Director environment. By creating event automation plans and
applying them to specific systems, you can be notified by e-mail, for example,
when a specified threshold is reached or a specified event occurs. Or, you can
configure an event automation plan to start a program on a system in response to
the event.
What is an event automation plan?
Event automation plans are composed of three components: a target list that
contains one or more system or group, a filter that specifies types of events; and
one or more actions, which are invoked in response to filtered events. The Event
Automation Plan wizard provides a quick and easy way to create event
automation plans for common situations. If you want to create sophisticated event
automation plans, it is important to understand the events that are generated in a
systems-management environment, the event filters that specify the triggering
events, and the event actions that can automate a response to the triggering event.
When you create an event automation plan, you include a filter and one or more
actions. Finally, you apply the event automation plan to an individual system,
several systems, or a group of systems.
How does IBM Systems Director Server use an event automation

plan?
When IBM Systems Director Server receives an event, the server determines
whether there is a plan for that type of event. If so, the server checks whether the
event source is in the list of targets in the plan. If it is in the plan, then the server
performs the action specified in the plan.
Events
An event is an occurrence of significance to a task or system, such as the
completion or failure of an operation. In a systems-management environment, IBM
Systems Director Server receives events from many sources.
These sources include, but are not limited to, the following programs and
protocols:
v Systems Director Program native events generated by the management server.
v Systems Director native events generated by Common Agent. For more
information, see “Common Agent.”

v Common Information Model (CIM) indications from the Common Information
Model Object Manager (CIMOM) that is installed as part of Common Agent and
Platform Agent.
v Microsoft Windows event log.
v Windows Management Instrumentation (WMI).
v SNMP traps through out-of-band communication, that is, communication that is
not through Common Agent or Platform Agent.
v Platform Event Traps (PET) through out-of-band communication with systems
that support Alert Standard Format (ASF) and Intelligent Platform Management
Interface (IPMI).
v Service processor notifications through out-of-band communication.
Alerts and resolutions
In Systems Director, an event can be in one of the following categories: alert and
resolution. Typically, an alert is the occurrence of a problem relating to a system. A
resolution is the occurrence of a correction or solution to a problem.
Related concepts:
“Event filters” on page 294
“Event actions” on page 298
Related reference:
CIM indications in IBM Systems Director
Mapping SNMP traps to Systems Director events

This topic explains how to modify the rules used to map SNMP traps to Systems
Director events. This customization provides greater flexibility in what information
gets presented to users and increases the event action plan filter options.
Introduction
Systems Director can manage SNMP traps. An SNMP trap is a notification sent
from the device acting as an SNMP agent; such as a switch, router, or printer, to
Systems Director. It processes incoming traps by mapping them to Systems
Director event format. The conversion process is called mapping. Systems Director
has default mappings for some traps. Users can also create mapping files to map
additional events.
Mapping SNMP traps to Systems Director allows you to do the following:

v Use the same event action plan tools for SNMP traps and Systems Director
events.
v Create homogenous information across multiple vendors supporting a trap.
v Customize information presented in the resulting Systems Director event.
There are two methods by which traps are converted: unmapped and mapped:
Unmapped traps
Use a generic set of rules, also called keys, to map the trap data to
properties within the Systems Director event. Any trap OIDs that are not
included in the mapping keys are considered unmapped and use the
default, generic keys.
Mapped traps
Have specific conversion keys defined for an SNMP OID or OID range.
Chapter 6. Automating tasks 289

Follow these steps to add or change mappings:
1. Open the .map file in one of these directories:
v Linux: /opt/ibm/director/data/snmp/
v Windows: C:\Program Files\ibm\director\data\snmp\
2. Modify the .map file as necessary. See the map file properties below.
3. Restart Systems Director services.
Mapping key syntax
The SNMP map file contains a series of map entries that consist of predefined
keys grouped into map entries for specific OIDs or range of OIDs. The equals sign
(=) is used to set a value and the double equals (==) is used to compare values as
equal to each other.
Predefined keys
The predefined keys describe how SNMP trap data should be converted to
Systems Director event format. Each key has this format: event.index.key
format.
Note: The predefined key usually does not need to be changed.

index Identifies which map the key entry belongs to. It must be unique
to the key entry in the map file. Follow these suggestions to avoid
duplication of index values:
v Use the specific trap type as a part of that index. In the
following example map entry, the trap type is 8217 and the
index was set to 18217.
v Systems Director uses index values through 14000, so choose
indexes above 14000. Check the existing .map files for additional
index values that are in use.
key The key property to be modified and the data associated with it.
Example:
The entry event.12000.severity=4 sets the severity to 4 for map 12000.

Map entries
A map entry contains two sections of keys. The first section, Director Alert
Definition, describes the organization and content of the Systems Director
event. The SNMP Trap Filter Section deals with how the trap information
is filtered and parsed.
Example map entry:

# - Director Alert Definition Section -
# Mappings from lsi-adaptersas.mib specific SNMP traps to the corresponding Director Event Format
# author: Author Name
# Warning! This file is case-sensitive
# SW traps
# Define the alert Family
event.18217.family=SNMP
# Define the alert Event Qualifiers
event.18217.keyword.0=Hardware
event.18217.keyword.1=Storage
event.18217.keyword.2=LSI
# Set the Severity
event.18217.severity=4
# Set the Category
event.18217.category=1

# Define the message to be displayed
event.18217.text=PD state changed on Adapter {0} Dev {1} Enc {2} Slot {3} from {4} to {5}
# - SNMP Trap Filter Section -
# OID of the trap to match
event.18217.oid=1.3.6.1.4.1.3582.4.1.8.0.8217
# Trap variable to parse for the alert message
event.18217.eventvar.0=1.3.6.1.4.1.3582.4.1.6.1001
event.18217.eventvar.1=1.3.6.1.4.1.3582.4.1.8.1201
event.18217.eventvar.2=1.3.6.1.4.1.3582.4.1.8.1202
event.18217.eventvar.3=1.3.6.1.4.1.3582.4.1.8.1203
event.18217.eventvar.4=1.3.6.1.4.1.3582.4.1.8.1205
event.18217.eventvar.5=1.3.6.1.4.1.3582.4.1.8.1204
event.18217.proceedwithnormaltrap=false
Mapping file syntax - Map entries, Director Alert Definition section
This section uses a set of keys to define which information is presented in the
Systems Director event. The following keys are pertinent to this section:
Table 25. Keys pertinent to the Director Alert Definition map entry section
Key Value Description
event.index.family SNMP Top-level qualifier: the family name
of event.
event.index.keyword.0 event.qualifier.sample1 This is the top level qualifier. This
value can be translated from the
language bundle specified by
event.bundle key.
event.index.keyword.1 event.qualifier.sample2 The next level qualifier. You can
create as many keywords. These
values form the event type hierarchy
within a family.
event.index.severity 0,1,2,3,4,5 0 - Fatal, 1 - Critical, 2 - Minor, 3 -
Warning (default), 4 –
Harmless/Informational, 5 -
Unknown
event.index.category 0 or 1 0 – resolution, 1 - alert (default)
event.index.text text1 This value can be translated from
event.bundle key.
event.index.version version number Version number of this event
definition (defaults to 1)
The event.index.family and event.index.keyword keys are used to define the

event type hierarchical structure that the resulting Systems Director event will
belong to. This grouping can be used as part of an event action plan event filter.
The family for mapped SNMP traps is always set to SNMP, while the rest of the
keywords in the hierarchy can be set to whatever best describes the Systems
Director event.
Example:
The example in “Mapping key syntax” on page 290 uses the following entries for
family and keywords:

These keys will produce a Systems Director event with the Event Type
SNMP.Hardware.Storage.LSI. The first two keywords define the component
category, and the last keyword becomes the component type. These are the values
as shown in the Systems Director event interface:
Component Type: LSI
Component Category: SNMP\Hardware\Storage
Additionally, you can select the event type on the Event Type page of the Event
Filter wizard. To see it, choose these:
Types of events to include: Custom
Show: Event Type
The next two keys in the example, event.18217.severity=4 and

event.18217.category=1, set the event severity to “Informational” and the category
to “Alert”. There are event categories:
Alert A problem has just occurred.
Resolution
A problem has been resolved.
The Director Alert Definition Section ends with the key that describes what event
text is produced. The example has the following entry:
Note: In the map file, this key is on a continuous line.

All information after event.18217.text= is in the event text as it is entered, except
the bracketed numbers such as {0}. These numbers represent the inclusion of
variable information specified in the SNMP Trap Filter Section of the map entry.
They can be assigned to any of the trap variables sent with the trap. This lets you
include trap variable data in the event text.
Mapping file syntax - Map entries, SNMP Trap Filter section
The SNMP Trap Filter Section of the map entry specifies how the SNMP trap is
filtered and parsed. The following keys are pertinent to this section:
Table 26. Keys pertinent to the SNMP trap filter map entry section
event.index.oid 1.3.6.1.4.1.3582.4.1.8.0.8217 (see the OID of incoming trap to be matched.
example map entry) Use an asterisk (*) as a wildcard
character to support fallback rules.
event.index.eventvar.0 Event variable This value can be used as a variable
in event.index.text.
event.index.eventvar.1 Event variable Use this to add a second variable if
necessary. You can add as many
variables as are needed.

Table 26. Keys pertinent to the SNMP trap filter map entry section (continued)
event.index.eventvar.index.0 Position based event variable. For Use this instead of
example, this value can be 1. (see the event.index.eventvar.n if you want
example map entry) a specific varbind (by position) value
to be used as an event variable. The
first occurring word index is a
number and the second word index
is an actual word. In the example
map entry, the value of first varbind
will be used as event variable {0}.
event.index.eventvar.index.1 Position based event variable. For Use this to add a second variable if
example, this value can be 2. necessary. You can add as many
variables as are needed. In this case,
the value of second varbind will be
used as event variable {1}.
event.index.proceedwithnormaltrap true/false If true, a normal SNMP trap event is
also generated. Currently, this value
is ignored.
The first key included in this section is event.index.oid. It defines the OID of the
trap that the map should be applied to. The example OID key is for the specific
trap type 8217.
event.18217.oid=1.3.6.1.4.1.3582.4.1.8.0.8217
Notice that the OID is in numeric format and identifies a specific trap. To indicate
a range of trap OIDs, end a branch with an asterisk (*), as shown here:
event.12000.oid=1.3.6.1.6.3.1.1.5.*
After the specified OID is found, the trap identification can be filtered further by
matching the trap variable information against predefined values. This can be done
by using one of these keys: event.index.eventvarbind or
event.index.eventvarbind.index. The primary difference between these two keys
is how the variable data is found.
After the OID and variable filters in the map entry identify a compatible trap,
Systems Director retrieves the variable trap information to be included in the
Systems Director event text. The SNMP trap variables can be parsed into the
Systems Director event text using the event.index.eventvar and
event.index.eventvar.index keys. In the example map entry, key entry for
event.index.event.var shows a request for the trap variable with OID
1.3.6.1.4.1.3582.4.1.6.1001 and assigns it to the Event Text variable {0}.
event.18217.eventvar.0=1.3.6.1.4.1.3582.4.1.6.1001
The event text variable {0} is replaced with the value of the trap variable’s OID in
the event.index.text key.
The complete set of variables in the example is mapped as follows.

event.18217.eventvar.0=1.3.6.1.4.1.3582.4.1.6.1001
event.18217.eventvar.1=1.3.6.1.4.1.3582.4.1.8.1201
event.18217.eventvar.2=1.3.6.1.4.1.3582.4.1.8.1202

event.18217.eventvar.3=1.3.6.1.4.1.3582.4.1.8.1203
event.18217.eventvar.4=1.3.6.1.4.1.3582.4.1.8.1205
event.18217.eventvar.5=1.3.6.1.4.1.3582.4.1.8.1204
Another commonly used key is event.index.proceedwithnormaltrap. For an SNMP

trap that is mapped, this key lets you decide whether Systems Director should
report the original SNMP trap. By default, Systems Director processes both the
SNMP trap and the mapped Systems Director event. This causes double event log
entries and possibly multiple event action plan triggers. Setting the
event.index.proceedwithnormaltrap key to false specifies that only the mapped
event is processed.
Example:
MIB trap used in the example map entry

Reference of trap from MIB used for this example.
pdtStateChange TRAP-TYPE
ENTERPRISE pdTraps
VARIABLES
{atAdpNumber,pdID,pdEncIndex,pdSlotNo, pdOldState, pdNewState}
DESCRIPTION "PD state changed on Adapter -$1 Dev -$2 Enc -$3 Slot -$4 from $5 to 6"
--#TYPE "LSI SAS Trap: PD state changed"

--#SUMMARY "PD state changed on Adapter -%d Dev -%d Enc -%d Slot -%d from %d to %d"
--#ARGUMENTS {0,1,2,3,4,5}
--#SEVERITY INFORMATIONAL
--#GENERIC 6
--#CATEGORY "Error Events"
--#STATE OPERATIONAL
::= 8217
Forwarding SNMP traps from IBM Systems Director Server to

any SNMP application
To forward SNMP trap events that come from IBM Systems Director to an external
SNMP application, import these Management Information Bases (MIBs) to the
external application.
MIBs:
SNMP-FRAMEWORK-MIB
IBM-REC-MIB.mib
IBM-Director-Alert-MIB.mib
On Windows systems, the MIBs are located here: C:\Program Files\IBM\Director\

proddata\snmp\.
On Linux systems, the MIBs are located here: /opt/ibm/director/proddata/snmp/.
After the MIBs are imported, the external SNMP application’s event data displays
the correct trap information.
Event filters
A filter specifies one or more events that you want your event automation plan to
process. The event automation plan ignores any event instances that do not meet
the specifications of the filter. Typically, you will use the common event filters that
are provided in the Event Automation Plan wizard. Occasionally there are
situations where you will want to create a sophisticated event filter. The event
filters described in this section are available for such implementations. Using these

filters, you can specify details for an event such that it covers very specific
problems and occurrences. To create filters quickly, default values are provided;
however, you can customize the settings.
You can use a filter to capture a single event or multiple events. When designing
an event filter, first determine whether the following criteria are met:
v Can all the target systems generate all the events that you want to filter?
If a system cannot generate the event that you want to filter, the filter will not be
effective on that system. In such instances, you can apply the event automation
plan to those systems, but it will have no effect. For example, if an event filter is
based on an event for BladeCenter products and that event automation plan is
applied to systems that do not include BladeCenter products, the event filter has
no events to filter, and therefore, no actions are performed. If you understand
this concept, you can create more complex event automation plans, and you can
reduce the number of event automation plans you must build and maintain.
v Can you use the same event actions for all targeted systems to respond to the
event?
v Are the other filter options besides the event type common for all targeted
systems? These settings include the number of times the filter is active, the
severity of the event, and other attributes.
In addition to selecting the event types to filter, you also can select from four types
of event filters: Simple, Duplication, Exclusion, and Threshold. Each filter offers
different options for processing the selected event types.
Related concepts:
“Events” on page 288
Related tasks:
“Managing event filters” on page 336
Events that are available for filtering

Using the Event Automation Plan wizard you can select from commonly used sets
of events. Occasionally, you might need to create a filter using specialized events.
The Event Automation Plan wizard provides a means to do this also. All currently
available event types are displayed in the tree on the Event Type page in the Event
Filter Builder window, except for the IBM i message queue events. The Event Type
page provides a way to specify the IBM i message queue events without using the
tree.
The default installation of IBM Systems Director and its default plug-ins publish
their events in the Event Type tree when one of the following software starts:
v IBM Systems Director Server
v Common Agent
v Platform Agent
However, optional plug-ins might vary in whether the events are published when
one of these software starts. When the events are published depends on how the
optional plug-ins are implemented.
If you add a plug-in to your IBM Systems Director installation, the plug-in might
publish its events either when it is added to the installation or when the plug-in
sends its first event. If the plug-in publishes when it sends its first event, only that
event is published.

Note: Events from the Windows event log are displayed in the Windows event log
tree in the Event Type Filter Builder. Events from WMI are displayed in the
Common Information Model (CIM) tree.
Simple event filter

Simple event filters are general-purpose filters; most event automation plans use a
simple event filter.
In addition to any simple event filters that you create, IBM Systems Director
provides the following predefined, read-only simple event filters in the Event
Filters page.
Note: You cannot change predefined event filters; they are read-only. However,
you can copy a predefined filter and change the copy. For more information, see
“Copying an event filter.”
All events
Processes any events that occur on any system, except for
Windows-specific and IBM i-specific events.
Common Agent offline
Processes only those events that are generated when any managed
operating system resource goes offline.
Critical events
Processes only those events that have a Critical severity.
Disk Use
Processes only those events that are generated when the currently available
hard disk space in a system changes with respect to availability.
Environmental sensor events
Processes only those events that are associated with the condition of a
system environment, such as voltage and temperature.
Fatal events
Processes only those events that have a Fatal severity.
Hardware Predictive Failure Analysis events
Processes only those events that are generated when a Predictive Failure
Analysis is detected for a hardware component.
Informational events
Processes only those events that have a Informational severity.
Memory use
Processes only those events that are generated when the currently available
memory in a system changes with respect to availability.
Minor events
Processes only those events that have a Minor severity.
Processor use
Processes only those events that are generated when the state of a
processor (CPU) has changed.
Security events
Processes only those events that are generated by specific security
protocols, for example, log on failed due to an undefined user ID, or
incorrect or expired password.
Storage events
Processes only those events that are generated by storage components,
such as RAID configurations, for example, when creating, modifying, or
destroying a storage volume or storage pool.
Unknown events
Processes only those events that have a Unknown severity.
Warning events
Processes only those events that have a Warning severity.

Some of these predefined filters use the severity of events to determine which
events can pass through; other filters target a specific type of event. Using one of
these predefined event filters ensures that the correct event type or event severity
is selected.
Related tasks:
Duplication event filter

In addition to the options that are available in the simple filters, duplication event
filters ignore duplicate events.
You can use this filter in two ways: with or without specifying the number of times
to ignore an event (Count).
To specify only a time range (Interval), the Count setting must be set to zero
(Count = 0). The first occurrence of an event that meets the filter criteria triggers
associated actions and starts a countdown of the interval. For example, if you
specify a 10-second interval, a 10-second timer starts when an event meets the
filtering criteria. Because Count is set to 0, all other instances of an event that
meets the criteria do not trigger associated actions during the interval.
If you also specify a number of times to ignore an event (Count), it applies within
the specified time range (Interval). After the first occurrence of an event that meets
the filtering criteria, the Count setting specifies the number of times an event must
meet the criteria again before associated actions are triggered.
For example, if you set Count to 9, an event meeting the criteria is allowed to
occur nine times within the interval. When an event meets the criteria for a tenth
time within the interval, the associated actions are triggered, the count is reset, and
the interval is reset.
For the duplication filter to trigger the associated event actions a second time, the
count must be exceeded within the reset interval. For example, if Count = 3 and
Interval = 5 minutes, the event action is invoked for the fourth occurrence of the
event that occurs within 5 minutes. Then, the count and interval are reset. A fourth
occurrence of the event must occur in a 5-minute interval again.
This filter is useful in managing the processing of frequently generated events. For
example, you can define a duplication filter to filter on the occurrence of an offline
event and define a corresponding event action to forward the event to IBM
Systems Director Server. Depending on the criteria that you define, only the first
event announcing that the system is offline is processed, and all other instances in
which an event meets the filtering criteria are discarded until the Count value is
exceeded during the specified interval.
Related tasks:
Exclusion event filter

In addition to the simple filter options, exclusion event filters exclude certain event
types. Using this filter, you define the criteria of the events to exclude. You can use
this filter to activate a group of events and then exclude some of the events in that
group. You can use this filter to exclude multiple event types.
This filter type is useful when you want to create a filter based on a severity or a
category of events, but you want to exclude some specific event types. Instead of

creating event filters for each event that you want to include, you can specify the
event types that you want to exclude. By using exclusion event filters, it is easier
to remove events that you do not want to monitor.
Example
You can monitor server events, but exclude security alerts such as
“SSHLogin_Failed” failures from a service processor or other SSH client. To change
the event filter, complete the following steps:
1. On the Event Filters page, select the event filter that you want to edit. Click
Edit. The Edit Event Filter wizard is displayed.
2. Change the filter type from 'Simple Event filter' to 'Exclusion Event filter'.
3. Click the 'Excluded Event Type' tab on the left. Select Custom and specify the
full path of the events to be excluded. For this example, browse to Managed
Resource > Managed System Resource > Logical Resource > System >
Computer System > Hardware Control Point > Service Processor.
Under Operational Condition, select SSH Login Failed.
4. Click Add.
Result
The client no longer receives email related to “SSHLogin_Failed for Service

Processor”.
Related tasks:
Recurring event filter

In addition to the simple filter options, a recurring event filter processes an event
after it has occurred a specified number of times within a specified interval.
An event triggers associated actions if, within the specified interval, the event
occurs the number of times specified in the Count field.
For example, you can define a recurring filter to monitor frequently occurring
heartbeat events and forward the event to IBM Systems Director Server only when
the heartbeat event is received for the 100th time during a specified amount of
time. Count is set to 100 and Interval is set to 5 minutes. When the specified event
is received for the 100th time within 5 minutes, the event actions are invoked, and
the Count and Interval settings are reset. To invoke the event actions a second
time, the specified event must be received 100 times within an interval of 5
minutes again. If only 90 events are received within the 5 minutes, the Count and
Interval settings are reset.
Another example is to create a recurring filter such that, if a user attempts to log
on with a bad password five times within five minutes, the event automation plan
will trigger associated event actions.
Related tasks:
Event actions
Event actions specify the action that IBM Systems Director takes in response to a
specific event or events. Using the Event Automation Plan wizard, you can easily
create an event automation plan that will send you an e-mail or pager notification

in response to an event. Additionally, the Event Automation Plan wizard provides
other advanced event actions that you can use in response to an event.
IBM Systems Director has several predefined types of event actions. With the
exception of “Add to the event log”, you must customize each action that you
want to use.
Note: When you upgrade from previous versions of IBM Director to IBM Systems
Director 6.1 or later, the following event actions will no longer be supported:
v Add a message to the console ticker tape
v Send a message to a management console user
If you migrate an event action plan from IBM Director, version 5.20 or earlier, to
IBM Systems Director 6.1 or later, these actions will be removed from the event
automation plan. If the resulting event automation plan has no event actions
remaining, the plan will be in a deactivated state.
Related tasks:
“Creating an event action” on page 326
“Editing an event action” on page 327
“Copying an event action” on page 327
“Deleting an event action” on page 329
“Saving and not saving an event-action history” on page 329
“Viewing an event-action history” on page 330
“Viewing event action properties” on page 332
Log to a log file

Logs information about the triggering event to a specified text file.
Requirements
None
Result The specified text is added to the log file. Also, applicable attributes of the
event are also logged, for example, severity, event type, date, time, and IP
address of the affected system. You can specify the filename and file
extension of the log file, as well as its maximum file size. If the log file
reaches its specified maximum size, it is renamed to filename.1, where
filename is the file name that you specified. Then, a new filename.extension
file is created, where extension is the file extension that you specified for
the log file. The log file is located on the management server in the
install_root\log directory, where install_root is the root directory of your
IBM Systems Director installation. Note that this path uses the backslash
(\) to delimit the directory; depending on the system that you are using,
you might be required to enter the path using the forward slash (/).
Example
Use this event action when you want to log information in a file after a
specified event is generated. You can log the following information:
v Standard information from the event.
v Custom information that you specify.
Tip: You can use event-data-substitution variables in the Log comment

field field. For more information, see “Event-data-substitution
variables.”

Related concepts:
“Event-data-substitution variables” on page 333
Modify an event and send it

Resends the event that originally triggered the event automation plan. Before
resending the event, the action modifies the event data, such as its text and
severity, to your specification.
Requirements
None
Result The triggering event and the event that this event action generates are both
logged in the Event Log. The event that this event action generates
contains the text and event type from the original triggering event.
Example
Use this event action when you want to send a secondary event that
contains information from the first event. You can change or add to the
event text. Also, you can change the event severity; for some events, this
capability is useful when you want to increase the severity level.
For example, by default an Topology Offline event has a severity of
informational. If you have created an event automation plan to filter
critical events and you want the Topology Offline event to be treated as
such, you can use this event action to change the severity of this event.
Create a simple filter for the Topology Offline event. Then, use the Modify
an event and send it event action to resend the event, but change the
severity to critical in the New event severity field. Now, the critical event
filter will catch the event and the event automation plan will perform the
prescribed action.
Note: You can use event-data-substitution variables to include event-data

information into the new event text. For more information, see
“Event-data-substitution variables.” The detail slot setting also accepts
event-data-substitution variables; however, using event-data-substitution
variables in the detail slot setting can cause errors if not done correctly.
Related concepts:
Post to a newsgroup (NNTP)

Posts a message to a newsgroup used by your organization. The newsgroup must
use Network News Transfer Protocol (NNTP) to send and receive information.
Requirements
Newsgroup service must be available.
Note: You cannot use this action to post a message to a secure news
server.
Result The specified message is posted to the newsgroup.
Example
This action can be useful as an additional logging mechanism outside of
IBM Systems Director. Use this event action when you want to send
information to a newsgroup after a specified event is generated. The
message might notify members of a technical support organization when a
critical server is having problems.

Note: You can use event-data-substitution variables to include event data
information into the newsgroup message. For more information, see
“Event-data-substitution variables.”
Related concepts:
Send a Tivoli Enterprise Console event

If IBM Systems Director Server receives an event, you can forward that event to a
specified Tivoli Enterprise Console® event server.
Requirements
This event action requires that Tivoli Enterprise Console server is installed
on the specified system.
Result The specified Tivoli Enterprise Console server receives an IBM Systems
Director event in the Tivoli Enterprise Console event format.
Note: If the Tivoli Enterprise Console server is unavailable, the Tivoli

Enterprise Console events are queued and delivered when the Tivoli
Enterprise Console server becomes available.
Example
When IBM Systems Director Server receives an event, you might want to
forward the event to a Tivoli Enterprise Console server.
Send an Internet (SMTP) e-mail

Sends a Simple Mail Transfer Protocol (SMTP) e-mail message. You also can send a
message to an e-mail enabled phone. Using this action, you can send more text
than when using Send an e-mail to a mobile phone.
Note: This event action can send e-mail messages to Lotus Notes® IDs.
Requirements
If you are concerned about the availability of the internal mail server,
consider using an outside SMTP provider.
Result The specified e-mail address receives the e-mail message.
Example
Use this event action to send a message to administrators that need to
track the status of a group of servers.

information in the subject and body of the e-mail message. For more
information, see “Event-data-substitution variables.”
Related concepts:
Related tasks:
“Testing an event action” on page 328
Send an e-mail to a mobile phone

Sends an e-mail message to a mobile phone. The e-mail message is shortened to
accommodate the limited display screen of a mobile phone. Using this action, you
can send less text than when using Send an e-mail (Internet SMTP) .
Requirements
This event action has the following requirements:
v The management server must be running Windows, AIX, or Linux.

v The mobile phone must be able to receive text messages.
Result The specified mobile phone receives the e-mail message. If you specified a
message body, that is all that the mobile phone receives. If you did not
specify a message body, the mobile phone receives the text of the
triggering event.
Example
Use this event action to send an e-mail message to service personnel when
a Redundant Array of Independent Disks (RAID) configuration fails.

information in the subject and body of the e-mail message. For more
Related concepts:
Related tasks:
Send an event to Tivoli Event Integration Facility probe

If IBM Systems Director Server receives an event, you can forward that event to a
specified Tivoli Event Integration Facility (EIF) probe.
Requirements
This event action requires that you have Tivoli Event Integration Facility
(EIF) probe installed on the specified system.
Result The specified EIF probe receives an IBM Systems Director event in the
Tivoli Event Integration Facility event format. The event includes the
following extra tokens:
source_moid
This token has a value of the managed object identifier (MOID) for
the source event system. For example, an IBM Director Server,
called dirserverA, discovers an IBM Director Agent, called
diragentB. When the events from diragentB occur, the source_moid
is the MOID of diragentB.
Note: For out-of-bind events, the system that is the source of the
events has no MOID.
source_app
This token has a value of “IBM_DIRECTOR”, which means that the
source application is IBM Systems Director.
source_app_version
This token has a value that corresponds to the version of IBM
Director Server that is currently installed.
managed_object_type
This token has a value that corresponds to the type of managed
object (in this case, the component type) that is associated with the
type of source event. Some examples of managed objects:
v managed_object_type="BCChassis"
v managed_object_type="UPD"
v managed_object_type="Fan"

http_port
This token has a value of an HTTP port number, such as
http_port=8421.
https_port
This token has a value of an HTTP secure port number, such as
https_port=8422.
Note: Note: If the EIF probe is unavailable, the Tivoli Event Integration
Facility events are queued and delivered when the probe becomes
available.
Example
When IBM Systems Director Server receives an event, you can forward the
event to a Tivoli Business Service Manager (TBSM) by using the EIF probe.
The event action sends the event to the probe. Then, the probe forwards
the event to Tivoli OMNIBus, and TBSM pulls the event from OMNIBus.
Any products that work with EIF probe can process the event action, so
TBSM represents only one potential consumer of this event action.
Note: OMNIBus is a prerequisite for running TBSM. You can install

OMNIBus as part of TBSM, and TBSM customers have the option of
connecting to an existing copy of OMNIBus.
Send an SNMP INFORM request to an IP host

Sends an SNMPv2 or SNMPv3 INFORM request to a specified IP address or host
name. SNMP INFORM is a special version of an SNMP trap with a response from
a destination. Optionally, SNMPv3 traps can be authenticated (by using either the
Message Digest 5 protocol or the Secure Hash Algorithm protocol) and encrypted
(by using either the Advanced Encryption Standard or the Data Encryption
Standard).
Requirements
This event action requires that an SNMP manager that can receive an
SNMP INFORM be installed on the specified system.
Result The specified system receives an SNMP INFORM.
Note: For SNMPv1 and SNMPv2, this event action supports all
implementations that follow the associated RFCs. For SNMPv3, this event
action supports implementations that follow the associated RFCs (like the
inform listener in Net-SNMP version 5.4.2.1). Keep in mind that different
SNMPv3 implementations offer varying degrees of support that might
produce different results.
Example
An SNMP INFORM is a type of SNMP communication. You can use this
event action to send an SNMP INFORM in response to the triggering
event. Typically, an SNMP INFORM is used for manager-to-manager
communication as a means of acknowledging receipt of a notification.
If you use SNMP to monitor your systems, use this action to send specified
critical events as SNMP INFORM notifications to your SNMP monitor. If
the SNMP INFORM is not received, the action completion status is set to
Failed and IBM Systems Director Server knows whether the SNMP
INFORM was delivered successfully.

Send an SNMP trap reliably to a NetView host
Generates an SNMP trap and sends it to a specified NetView host using a TCP/IP
connection to the host. If delivery of the SNMP trap fails, a message is posted in
the history log of the system.
Requirements
The NetView product must be installed on the specified system.
Result The specified NetView system receives the SNMP trap. If delivery of the
SNMP trap fails, a message is written to the specified system's history log.
The failure information can be retrieved from the management server
system log using the lsevtacthist command-line command. For more
information, see “lsevtacthist command.”
Example
If you are using the NetView product to monitor your systems, use this
event action to send or reroute specific events from IBM Systems Director
Server to your NetView host. Then, you can view these specific events on
your NetView console.
Related reference:
lsevtacthist command
SNMP trap details
Send an SNMP trap to an IP host

Generates an SNMPv1, SNMPv2, or SNMPv3 trap and sends it to a specified IP
address or host name. Optionally, SNMPv3 traps can be authenticated (by using
either the Message Digest 5 protocol or the Secure Hash Algorithm protocol) and
encrypted (by using either the Advanced Encryption Standard or the Data
Encryption Standard).
Requirements
This event action requires the availability of SNMP agent on the specified
system that is to receive the traps.
Result The specified system receives an SNMP trap.
Note: For SNMPv1 and SNMPv2, this event action supports all
implementations that follow the associated RFCs. For SNMPv3, this event
action supports implementations that follow the associated RFCs (like the
trap listeners in IBM AIX Version 6.1 or Net-SNMP version 5.4.2.1). Keep in
mind that different SNMPv3 implementations offer varying degrees of
support that might produce different results.
Example
If you use an SNMP application to monitor your systems-management
environment, you can use this action to send the events from IBM Systems
Director as traps to the SNMP application. If your systems-management
environment includes several installations of IBM Systems Director Server,
you can use this event action to configure each instance of IBM Systems
Director Server to send the events as traps to the SNMP application such
that the traps are consolidated in the SNMP application. In the SNMP
application, an administrator can view all of the events from all of the IBM
Systems Director Server installations.

Related reference:
SNMP trap details
Send events to Syslog server

When IBM Systems Director Server receives an event, you can forward that event
to a specified syslog server. To help ensure reliability, specify a secondary syslog
server that receives messages when the primary syslog server is unavailable. You
can also configure the primary and secondary syslog servers to forward messages
to another syslog server.
Requirements
This event action requires that you have a syslog server installed,
configured, and running on the specified system. When you create the
event action, you must specify the port number and the protocol used to
communicate with the syslog server. Verify that the management server
can successfully communicate with the syslog server.
Important: When using the UDP protocol, the event action handler
assumes that the port is open on the remote system if the event action does
not receive an ICMP unreachable message from the syslog server. For
example, the event action assumes that the remote UDP port is listening or
open when ICMP is disabled on a syslog server that is not pingable or
when the syslog server does not exist.
Result The specified syslog server receives the forwarded IBM Systems Director
event message. Configure the event action to forward messages from a
specific type of source (or facility) and to include different levels of detail
in the forwarded messages.
Note: When the primary syslog server is not available, a specified

secondary syslog server receives the message. If you did not specify a
secondary syslog server or if the secondary syslog server is not available,
the event action fails to start.
Facilities
The event action forwards messages generated by any one of the
following facilities:
Note: Some syslog servers might support only a subset of the

facilities. Forwarded messages for unsupported facilities might
exhibit unexpected results.
v AUTH: authorization system messages (including programs that
require user IDs and passwords)
v AUTHPRIV: security or authorization system messages
(including programs that require user IDs and passwords)
v CLOCKDAEMON: clock daemon messages
v CRON: cron daemon messages
v DAEMON: system daemon messages (daemons not specified by
other facilities)
v FTP: FTP daemon messages
v KERN: kernel messages
v LOCAL0 - LOCAL7: user-defined facility messages
v LOGALERT: authorization system messages (including programs
that require user IDs and passwords)

v LOGAUDIT: authorization system messages (including programs
that require user IDs and passwords)
v LPR: line printer subsystem messages
v MAIL: mail program messages
v NEWS: news subsystem messages
v NTP: NTP subsystem messages
v SYSLOG: syslog server messages
v USER: user-level messages
v UUCP: UUCP subsystem messages
Example
When IBM Systems Director Server receives an event, details about the
event are packaged into a message that is forwarded to a syslog server. For
example, the management server receives an event with a severity of 4
(Harmless). The Send events to Syslog server event action packages the
specified event data into a message with a corresponding syslog severity of
5 (Notice) and forwards the message to the syslog server. (The event also is
logged in the appropriate IBM Systems Director Server log.) When the
primary syslog server is not listening, the event action forwards the
message to the secondary syslog server (if a secondary server is specified).
Note: When the message sent to the syslog server is larger than 1024
bytes, the event action separates the message into two or more segments.
Each segment of the message is numbered, and the last segment is
identified.
Related reference:
The Syslog Protocol
Event data and severity mapping:
Select how much event data the Send events to Syslog server event action includes
in the forwarded messages. The severity level is always included in the forwarded
message. Use the severity mapping information to determine how the severity
level of the stored message on the syslog server corresponds to the severity level of
the original IBM Systems Director event.
Event data
Specify how much event data are included in messages forwarded to the syslog
server by selecting either Main event data or All event data.
Note: Main event data is the default selection.

Main event data
Main event data includes the following data:
v The management server IP address or host name
v The event ID
v The event message
v The name of the resource that generated the event
v The severity level of the event
v The localized date and time that represent when the event occurred
v The category of the event (Alert or Resolution)

v The fully qualified representation of the event type
v The component category
v The component instance
v The condition type
v The condition value
All event data
All event data includes the same data as main event data plus the
following data:
v The time zone of the management server
v The source application, which is IBM Systems Director
v The version of IBM Systems Director
v The name of the resource that sent the event, which might be different
from the source value when the event is forwarded or transmitted
through an intermediate system
v The unique ID of the event sender
v The unique ID of the event
v Any additional details, as available
Severity mapping
The Send events to Syslog server event action maps received IBM Systems Director
events of a given severity to a corresponding syslog severity level. The result of
this mapping is that the event in the IBM Systems Director log has a different
severity level than event in the syslog server log. Use the following table to
determine how the severity levels of IBM Systems Director events correspond to
severity levels of the corresponding events in the syslog server log.
Table 27. How IBM Systems Director events map to corresponding syslog server events
Severity of the corresponding event sent to
Severity of an IBM Systems Director event the syslog server
0 Fatal: The source of the event caused 1 Alert: Take action immediately
the program to fail; resolve before
restarting the program
1 Critical: The source of the event might 2 Critical: Critical condition
cause the program to fail; resolve
immediately.
2 Minor: The application that issued the 3 Error: Error condition
event assigned a severity level that
indicates that the source of the event
should not cause immediate program
failure; resolve
3 Warning: The source of the event 4 Warning: Warning condition
might not be problematic but warrants
investigation.
4 Harmless. The event was generated 5 Notice: Normal but significant
only for informational purposes. Most condition
events of this severity do not indicate
potential problems.
5 Unknown. The application that 6 Informational: Informational message
generated the event did not assign a
severity level; however, these events
might indicate potential problems.

Related reference:
Generating events (genevent command)
The Syslog Protocol (RFC 5424)
Set an event system variable

Sets a user-defined system variable to a new value or resets the value of an
existing system variable. IBM Systems Director provides user-defined system
variables to help you test and track the status of network resources according to
the needs of your organization. System variable names and values can be
referenced wherever event data substitution is allowed.
Note: This event action affects an IBM Systems Director-provided, user-defined

system variable, not an operating-system variable.
Requirements
None
Result The specified variable and value are added to the EventSysVar.prop file.
This file is located on the management server in the /opt/ibm/director/
data directory. in the install_root\data directory, where install_root is the
root directory of your IBM Systems Director installation. Note that this
path uses the backslash (\) to delimit the directory; depending on the
system that you are using, you might be required to enter the path using
the forward slash (/).
Example
Assume that you need to monitor a bottleneck in the network that can
cause network congestion. You can create an event automation plan to
specify an SNMP event that indicates network congestion, and initiate the
Set Event System Variable task when the event occurs. Assume that you
have specified the following settings:
v System variable name field: NetStatus
v New value field: Congested
v Reset value to use IBM Systems Director Server when restarts field:
Normal
v Time until automatic value reset field: 10
If 10 seconds elapse before IBM Systems Director Server receives the event
that triggers this action or before IBM Systems Director Server stops and
restarts, the NetStatus system variable is reset to normal.
Instead of using a specific event that signals that your NetStatus is
Normal, you have used a system variable that automatically resets to
normal when the events that cause this action to trigger are not received
within the interval. If IBM Systems Director Server continues to receive the
events before the interval expires, this action continues to trigger, signaling
that the network is congested. If the timer interval expires, NetStatus is
reset to Normal.
Note: You can use event-data-substitution variables to include event-data

information in the System variable name, New value, and the Reset value
to use IBM Systems Director Server when restarts fields of this event
action. For more information, see “Event-data-substitution variables.”

Related concepts:
Start a program on a system

Starts a program on a specified system. Programs can include command-line
commands that can start or stop programs on the system.
Requirements
v The specified system must have Common Agent installed.
v To work with this type of event action, the user must belong to the
smadmin group.
Result The program is started on the specified system.
Related concepts:
Related tasks:
“Migrating and importing event automation data from a previous version” on
page 342
Start a program on the management server

In response to an event, starts a program on the management server (the system
running IBM Systems Director Server) that received the event. Programs can
include command-line commands that can start or stop programs on the system.
Requirements
To work with this type of event action, the user must belong to the
smadmin group.
Result The program is started on the management server that is processing the
event and invoking the event automation plan.
Example
If your management server is configured with an audio card, you can start
an audio player and play a specified file to alert a technician about a
critical event. This implementation can be useful in large rooms with many
servers.
Tip: You can use event-data-substitution variables in the Program file

name field. For more information, see "Event-data-substitution variables."
Related concepts:
Related tasks:
page 342
Start a program on the system that generated the event

Starts a program on the system that generated the event that triggered the event
automation plan. Programs can include command-line commands that can start or
stop programs on the system.
Requirements
v The specified system must have Common Agent installed.

smadmin group.
Result The program is started on the system that generated the event.
Example
You might use the dakill.exe program that is provided with IBM Systems
Director, located in the support directory. You can use this program to stop
processes by providing the process name.
For example, if you want to stop the solitaire.exe program, you can create
an event automation plan using this event action and combine it with a
process monitor configured to generate an event when solitaire.exe starts
and the event automation plan will stop the solitaire.exe process on that
system.
Note: You cannot test this event action before including it in an event
automation plan. The Test menu item under the template menu is not
supported by this action.
Tip: You can use event-data-substitution variables in the Program file

name field. For more information, see “Event-data-substitution variables.”
Related concepts:
Related tasks:
page 342
Start a task on a specified system

Starts a noninteractive IBM Systems Director task on a specified system.
Noninteractive tasks are tasks that do not require user input.
Requirements
v The specified task must be a noninteractive task.
v The task that you want to use must be available in the IBM Systems
Director Web interface before you can specify the task for this action.
smadmin group.
Important: Some tasks have hardware or software requirements and

cannot be performed on a given system. Give careful consideration to an
event automation plan that uses this event action before associating it with
a given system or group. For example, not all power management
commands are available. For more information, see “Managing power state
settings on IBM BladeCenter and System x servers,” and “Power On/Off
task support for System z servers.”
Result The task is started on the specified system.
Example
Consider an environment where you have two physical systems and one of
the physical system is running three virtual servers. You can create an
event automation plan that detects a critical Predictive Failure Analysis
(PFA) event on a physical system. Using this action, you can run a
previously created noninteractive task that migrates the running workload
of the virtual servers hosted on the affected physical server to the second
physical server.

Note: You can create noninteractive tasks using the Command Automation
task.
Related tasks:
page 342
Start a task on the system that generated the event

Starts a noninteractive IBM Systems Director task on the system that generated the
event. Noninteractive tasks are tasks that do not require user input.
Requirements
v The specified task must be a noninteractive task.
v The task that you want to use must be available in the IBM Systems
Director Web interface before you can specify the task for this action.
Important: Some tasks have hardware or software requirements and

cannot be performed on a given system. Give careful consideration to an
event automation plan that uses this event action before associating it with
a given system or group. For example, not all power management
commands are available. For more information, see “Managing power state
settings on IBM BladeCenter and System x servers,” and “Power On/Off
task support for System z servers.”
Result The task is started on the system that generated the event.
Example
You can create an event automation plan to monitor systems for hardware
problems and, when the event automation plan detects a hardware
problem, you can set the locator LED on that system to flash by using this
event action.
Note: You cannot test this event action before including it in an event
automation plan. The Test menu item under the template menu is not
supported by this action.
Related tasks:
page 342
Static group: add or remove group members

Adds a defined set of systems to a specified static group or removes a defined set
of systems from the specified static group. Use this event action to initialize a set
of systems to process. Then the processing is triggered by an event that you
specify in your event filter.
Requirements
Both the source and target groups must be static groups.
Result The group member that generated the event is added to the specified static
group or removed from a specified static group, as applicable.
Example
Use this action to track systems that have been processed. When the
specified event is received, this event action moves a defined set of
systems to a static group. Then, as each system is processed, the system is
removed from the static group using the Static group: add or remove the
event-generating system event action.

For example, create a static group that contains all the systems that require
updating. After each system is updated, an event is generated. That event
can trigger this event action to remove the updated system from the static
group. When there are no more systems in the static group, you know all
systems have been updated.
Tip: You can use event-data-substitution variables for the target group
name or the new group name. For example, you can dynamically set the
target group to the static group that contains the system that generated the
event. For more information, see “Event-data-substitution variables.”
Related concepts:
Static group: add or remove the event-generating system

Adds the system that generated the event to a specified static group or removes
the system that generated the event from a specified static group, as applicable.
Requirements
Both the source and target groups must be static groups.
Result The system that generated the event is added to the specified static group
or removed from a specified static group, as applicable.
Example
You can use this event action to track systems for which IBM Systems
Director has processed an event. As a system generates the event that you
specified, that system is moved to a static group. Then, you can view the
members of that static group to see which system has generated the event.
Similarly, as a system generates the event that you specified, that system
can be removed from a static group.
Tip: You can use event-data-substitution variables for the target group
name or the new group name. For example, you can dynamically set the
target group to the static group that contains the system that generated the
event. For more information, see “Event-data-substitution variables.”
Related concepts:
Timed alarm that generates an event

Generates a defined alarm event only if IBM Systems Director does not receive a
specified event within a specified time range. This event action is useful for
monitoring for a loss of function, much like a heartbeat monitor.
Requirements
None
Result An event triggers an event automation plan that contains this event action.
The action is invoked and it starts a timer. If another event of the same
type is received before the timer expires, nothing further happens.
However, if the timer does expire, an alarm event is generated by this
action.
Example
You can use this action to make sure that something happens repeatedly or
within a given amount of time. After the timer expires and the alarm event
is sent, the monitoring process of this event action stops.

Note: In IBM Systems Director, versions 6.1.x and 6.2.x, when the
associated event is not received within the specified interval, the alarm
triggers the action only one time or generates only one event. This
behavior is different than in IBM Director 5.x, where the alarm continually
triggers the action during the specified interval until the event associated
with the action is received.
For example, you can monitor Common Agent to go offline on a system. If
Common Agent does not return online within a given amount of time, you
can power off that system.
Note: You also can stop the monitoring process by setting the timer value
to 0. This capability is useful if you want to stop the process without
deleting the event action or the event automation plan.
Tip: You can use event-data-substitution variables in the following fields:

Timed alarm ID, Program file name, and Working directory. For more
Related concepts:
Timed alarm that starts a program

Starts a specified program only if IBM Systems Director does not receive a
specified event within a specified time range. This event action is useful for
monitoring for a loss of function, much like a heartbeat monitor.
Requirements
To work with this type of event action, the user must belong to the
smadmin group.
Result An event triggers an event automation plan that contains this event action.
The action is invoked and it starts a timer. If another event of the same
type is received before the timer expires, nothing further happens.
However, if the timer does expire, this action starts a specified program on
the management server.
Example
You can use this action to make sure that something happens repeatedly or
within a given amount of time. After the timer expires and the program is
started, the monitoring process of this event action stops.
For example, you can monitor for a system to go offline. If the system does
not return online within a given amount of time, you can failover to a
backup system.
Note: You also can stop the monitoring process by setting the timer value
to 0. This capability is useful if you want to stop the process without
deleting the event action or the event automation plan.
Tip: You can use event-data-substitution variables in the following fields:

Timed alarm ID, Program file name, and Working directory. For more

Related concepts:
Related tasks:
page 342
Monitoring operating-system specific events

If you want to monitor Windows-specific or IBM i-specific events in the IBM
Systems Director environment, you must create an event automation plan in order
for IBM Systems Director to process these events. The predefined active event
automation plan in IBM Systems Director, Log All Events, does not monitor these
operating-system specific events.
Systems running Windows or IBM i can generate the following operating-specific

events.
Windows-specific event types
v Windows event log
v Windows services
v Windows registry
IBM i-specific event types
v Msgq
Even though these events are generated by their respective operating systems (or
an optional layer that is installed on the operating system), IBM Systems Director
does not process these events unless you create an event automation plan to do so.
When you install IBM Systems Director, it has one predefined active event
automation plan: Log All Events. However, this event automation plan does not
log these Windows-specific or IBM i-specific events. You must create an event
automation plan with a simple-event filter that contains the event types for one or
more of these events. Then, you must apply this event automation plan to the
systems running Windows or IBM i.
When Common Agent starts on a system running Windows, the twgescli.exe

program starts, too. This program listens for IBM Systems Director Server to send a
message to Common Agent that an event automation plan has been applied to that
system. If the event automation plan includes a simple-event filter that contains the
event types for any of the Windows-specific events, IBM Systems Director
appropriates these events for its own use. This process is called event subscription.
The twgescli.exe program subscribes to the event types that are specified in the
event automation plan and translates the Windows-specific events into an IBM
Systems Director event type. Then, the program forwards the events to the
management server from which the event automation plan was applied.
Mapping SNMP traps to Systems Director events

This topic explains how to modify the rules used to map SNMP traps to Systems
Director events. This customization provides greater flexibility in what information
gets presented to users and increases the event action plan filter options.
Introduction
Systems Director can manage SNMP traps. An SNMP trap is a notification sent
from the device acting as an SNMP agent; such as a switch, router, or printer, to
Systems Director. It processes incoming traps by mapping them to Systems

Director event format. The conversion process is called mapping. Systems Director
has default mappings for some traps. Users can also create mapping files to map
additional events.
Mapping SNMP traps to Systems Director allows you to do the following:

v Use the same event action plan tools for SNMP traps and Systems Director
events.
v Create homogenous information across multiple vendors supporting a trap.
v Customize information presented in the resulting Systems Director event.
There are two methods by which traps are converted: unmapped and mapped:
Unmapped traps
Use a generic set of rules, also called keys, to map the trap data to
properties within the Systems Director event. Any trap OIDs that are not
included in the mapping keys are considered unmapped and use the
default, generic keys.
Mapped traps
Have specific conversion keys defined for an SNMP OID or OID range.
Follow these steps to add or change mappings:

1. Open the .map file in one of these directories:
v Linux: /opt/ibm/director/data/snmp/
v Windows: C:\Program Files\ibm\director\data\snmp\
2. Modify the .map file as necessary. See the map file properties below.
3. Restart Systems Director services.
Mapping key syntax
The SNMP map file contains a series of map entries that consist of predefined
keys grouped into map entries for specific OIDs or range of OIDs. The equals sign
(=) is used to set a value and the double equals (==) is used to compare values as
equal to each other.
Predefined keys
The predefined keys describe how SNMP trap data should be converted to
Systems Director event format. Each key has this format: event.index.key
format.
Note: The predefined key usually does not need to be changed.

index Identifies which map the key entry belongs to. It must be unique
to the key entry in the map file. Follow these suggestions to avoid
duplication of index values:
v Use the specific trap type as a part of that index. In the
following example map entry, the trap type is 8217 and the
index was set to 18217.
v Systems Director uses index values through 14000, so choose
indexes above 14000. Check the existing .map files for additional
index values that are in use.
key The key property to be modified and the data associated with it.
Example:

The entry event.12000.severity=4 sets the severity to 4 for map 12000.
Map entries
A map entry contains two sections of keys. The first section, Director Alert
Definition, describes the organization and content of the Systems Director
event. The SNMP Trap Filter Section deals with how the trap information
is filtered and parsed.
Example map entry:

# Mappings from lsi-adaptersas.mib specific SNMP traps to the corresponding Director Event Format
# author: Author Name
# Warning! This file is case-sensitive
# SW traps
# Set the Severity
event.18217.severity=4
# Set the Category
event.18217.category=1
# - SNMP Trap Filter Section -
event.18217.oid=1.3.6.1.4.1.3582.4.1.8.0.8217
event.18217.eventvar.0=1.3.6.1.4.1.3582.4.1.6.1001
event.18217.eventvar.1=1.3.6.1.4.1.3582.4.1.8.1201
event.18217.eventvar.2=1.3.6.1.4.1.3582.4.1.8.1202
event.18217.eventvar.3=1.3.6.1.4.1.3582.4.1.8.1203
event.18217.eventvar.4=1.3.6.1.4.1.3582.4.1.8.1205
event.18217.eventvar.5=1.3.6.1.4.1.3582.4.1.8.1204
Mapping file syntax - Map entries, Director Alert Definition

section
This section uses a set of keys to define which information is presented in the
Systems Director event. The following keys are pertinent to this section:
Table 28. Keys pertinent to the Director Alert Definition map entry section
event.index.family SNMP Top-level qualifier: the family name
of event.
event.index.keyword.0 event.qualifier.sample1 This is the top level qualifier. This
value can be translated from the
event.bundle key.
event.index.keyword.1 event.qualifier.sample2 The next level qualifier. You can
create as many keywords. These
values form the event type hierarchy
within a family.
event.index.severity 0,1,2,3,4,5 0 - Fatal, 1 - Critical, 2 - Minor, 3 -
Warning (default), 4 –
Harmless/Informational, 5 -
Unknown
event.index.category 0 or 1 0 – resolution, 1 - alert (default)

Table 28. Keys pertinent to the Director Alert Definition map entry section (continued)
event.index.text text1 This value can be translated from
event.bundle key.
event.index.version version number Version number of this event
definition (defaults to 1)
The event.index.family and event.index.keyword keys are used to define the

event type hierarchical structure that the resulting Systems Director event will
belong to. This grouping can be used as part of an event action plan event filter.
The family for mapped SNMP traps is always set to SNMP, while the rest of the
keywords in the hierarchy can be set to whatever best describes the Systems
Director event.
Example:
The example in “Mapping key syntax” on page 315 uses the following entries for
family and keywords:
These keys will produce a Systems Director event with the Event Type
SNMP.Hardware.Storage.LSI. The first two keywords define the component
category, and the last keyword becomes the component type. These are the values
as shown in the Systems Director event interface:
Component Type: LSI
Component Category: SNMP\Hardware\Storage
Additionally, you can select the event type on the Event Type page of the Event
Filter wizard. To see it, choose these:
Types of events to include: Custom
Show: Event Type
The next two keys in the example, event.18217.severity=4 and

event.18217.category=1, set the event severity to “Informational” and the category
to “Alert”. There are event categories:
Alert A problem has just occurred.
Resolution
A problem has been resolved.
The Director Alert Definition Section ends with the key that describes what event
text is produced. The example has the following entry:
Note: In the map file, this key is on a continuous line.

All information after event.18217.text= is in the event text as it is entered, except
the bracketed numbers such as {0}. These numbers represent the inclusion of

variable information specified in the SNMP Trap Filter Section of the map entry.
They can be assigned to any of the trap variables sent with the trap. This lets you
include trap variable data in the event text.
Mapping file syntax - Map entries, SNMP Trap Filter section
The SNMP Trap Filter Section of the map entry specifies how the SNMP trap is
filtered and parsed. The following keys are pertinent to this section:
Table 29. Keys pertinent to the SNMP trap filter map entry section
event.index.oid 1.3.6.1.4.1.3582.4.1.8.0.8217 (see the OID of incoming trap to be matched.
example map entry) Use an asterisk (*) as a wildcard
character to support fallback rules.
event.index.eventvar.0 Event variable This value can be used as a variable
in event.index.text.
event.index.eventvar.1 Event variable Use this to add a second variable if
necessary. You can add as many
variables as are needed.
event.index.eventvar.index.0 Position based event variable. For Use this instead of
example, this value can be 1. (see the event.index.eventvar.n if you want
example map entry) a specific varbind (by position) value
to be used as an event variable. The
first occurring word index is a
number and the second word index
is an actual word. In the example
map entry, the value of first varbind
will be used as event variable {0}.
event.index.eventvar.index.1 Position based event variable. For Use this to add a second variable if
example, this value can be 2. necessary. You can add as many
variables as are needed. In this case,
the value of second varbind will be
used as event variable {1}.
event.index.proceedwithnormaltrap true/false If true, a normal SNMP trap event is
also generated. Currently, this value
is ignored.
The first key included in this section is event.index.oid. It defines the OID of the
trap that the map should be applied to. The example OID key is for the specific
trap type 8217.
event.18217.oid=1.3.6.1.4.1.3582.4.1.8.0.8217
Notice that the OID is in numeric format and identifies a specific trap. To indicate
a range of trap OIDs, end a branch with an asterisk (*), as shown here:
event.12000.oid=1.3.6.1.6.3.1.1.5.*
After the specified OID is found, the trap identification can be filtered further by
matching the trap variable information against predefined values. This can be done
by using one of these keys: event.index.eventvarbind or
event.index.eventvarbind.index. The primary difference between these two keys
is how the variable data is found.
After the OID and variable filters in the map entry identify a compatible trap,
Systems Director retrieves the variable trap information to be included in the
Systems Director event text. The SNMP trap variables can be parsed into the
Systems Director event text using the event.index.eventvar and
event.index.eventvar.index keys. In the example map entry, key entry for
event.index.event.var shows a request for the trap variable with OID
1.3.6.1.4.1.3582.4.1.6.1001 and assigns it to the Event Text variable {0}.
event.18217.eventvar.0=1.3.6.1.4.1.3582.4.1.6.1001
The event text variable {0} is replaced with the value of the trap variable’s OID in
the event.index.text key.
The complete set of variables in the example is mapped as follows.

event.18217.eventvar.0=1.3.6.1.4.1.3582.4.1.6.1001
event.18217.eventvar.1=1.3.6.1.4.1.3582.4.1.8.1201
event.18217.eventvar.2=1.3.6.1.4.1.3582.4.1.8.1202
event.18217.eventvar.3=1.3.6.1.4.1.3582.4.1.8.1203
event.18217.eventvar.4=1.3.6.1.4.1.3582.4.1.8.1205
event.18217.eventvar.5=1.3.6.1.4.1.3582.4.1.8.1204
Another commonly used key is event.index.proceedwithnormaltrap. For an SNMP

trap that is mapped, this key lets you decide whether Systems Director should
report the original SNMP trap. By default, Systems Director processes both the
SNMP trap and the mapped Systems Director event. This causes double event log
entries and possibly multiple event action plan triggers. Setting the
event.index.proceedwithnormaltrap key to false specifies that only the mapped
event is processed.
Example:
MIB trap used in the example map entry

Reference of trap from MIB used for this example.
pdtStateChange TRAP-TYPE
ENTERPRISE pdTraps
VARIABLES
{atAdpNumber,pdID,pdEncIndex,pdSlotNo, pdOldState, pdNewState}
DESCRIPTION "PD state changed on Adapter -$1 Dev -$2 Enc -$3 Slot -$4 from $5 to 6"
--#TYPE "LSI SAS Trap: PD state changed"

--#SUMMARY "PD state changed on Adapter -%d Dev -%d Enc -%d Slot -%d from %d to %d"
--#ARGUMENTS {0,1,2,3,4,5}
--#SEVERITY INFORMATIONAL
--#GENERIC 6
--#CATEGORY "Error Events"
--#STATE OPERATIONAL
::= 8217
Viewing the automation manager summary

You can view a summary of activity within the past 30 days that is associated with
automation, including event automation plans, scheduled and run jobs, event
management and Event Log, a list of systems with the most critical and warning
events, and a list of the most frequent received critical and warning events. Note
that information on this page is refreshed automatically when there are any
changes.
To view the automation summary, complete the following steps:


3. On the Plug-ins page, scroll to the Automation portion of the page and click
the Automation Manager section heading. The Automation manager summary
for the past 30 days is displayed.
4. View the Scheduled Jobs section. This section provides the following
information:
v The number of active scheduled jobs.
v The number of job activations that have completed successfully.
v The number of job activations that have failed.
v Up to three upcoming jobs that will run next. If more than one job will run
at the same time, all affected jobs are displayed.
v Up to three of the most recently run jobs. If more than one job ran at the
same time, all affected jobs are displayed.
v In the Job management area, a link to the Active and scheduled jobs page.
Using the Active and scheduled jobs page, you can create or edit jobs, view
job information, view job instance information, suspend and resume jobs,
and more.
5. View the Systems with the Most Frequent Critical or Warning Events section.
This section provides the following information:
v The five systems that have generated the most events with the following
event severities: fatal, critical, or warning. If there are more than five systems
that have generated the same number events, an ellipse (...) displayed
indicate that there are more systems.
v In the Event management area, a link to the Event log task page. On this
page you can view events that IBM Systems Director Server has received
along with event information that can help you troubleshoot problems in
your systems-management environment.
6. View the Most Frequent Critical or Warning Events section. This section lists
the five event types that have been generated the most with the event severity
of fatal, critical, or warning. If there are more than five event types that have
been generated in the same number of severities, an ellipse (...) displayed
indicate that there are more event types.
7. View the Event Automation Plans section. This section provides the following
information:
v The number of active event automation plans.
v The number of inactive event automation plans.
v In the Plan management area, the following links are provided:
Event automation plans
Use the Event Automation Plans page to create and work with event
automation plans.
Event actions
Use the Event Actions page to create and work with event actions
that specify the action to automate when an event automation plan is
triggered.
Event filters
Use the Event Filters page to create and work with event filters that
determine which events trigger an event automation plan.

Related tasks:
Finding a task
Scheduling tasks
Managing event automation plans

Use event automation plans to automate tasks in your system-management
environment. These plans are composed of event filters and event actions. The
plans are triggered by events. You can create, copy, edit, deactivate, activate, and
delete event automation plans. Also, you can view the Automation summary page.
Related concepts:
eLearning: Creating basic event automation plans
eLearning: Creating advanced event automation plans

Related tasks:
Monitoring for IBM i message queue events
Monitoring the deployment of configuration plans and configuration templates
Related reference:
Event automation plan commands
Exporting event automation plans (lsevtautopln command)
Generating events for testing purposes (genevent command)
Copying an event automation plan

Copy an event automation plan when you want to create a plan that is similar to a
preexisting plan.
To copy an event automation plan, complete the following steps:

1. On the Plug-ins tab of the Home page, click Event Automation Plans under
Automation Manager.
2. On the Event Automation Plans page, select the event automation plan that you
want to copy.
3. Click Create Like.
4. On the Name and description page, type a new descriptive name for the event
5. In the event automation plan wizard, navigate to the pages that you want to
edit and make your changes.
need to make changes, click < Back Make sure to specify whether you want to
apply the event automation plan as soon as you finish creating it.
The event automation plan is saved and is displayed on the Event Automation
Plans page.

Related reference:
mkevtautopln command
Creating an event automation plan

Create an event automation plan to automatically respond to a situation in your
IBM Systems Director environment. By creating event automation plans and
applying them to specific systems, you can be notified by e-mail or pager, for
example, when a specified threshold is reached or a specified event occurs. Or, you
can configure an event automation plan to start a program on a system in response
to the event.
Use this method to create an event automation plan by configuring all the possible
settings. For example, select one or more systems to apply the plan to, specify one
or more event types from the full range of available events, select or create the
associated thresholds, and so on.
Alternatively, you can follow these instructions: “Create an event automation plan
based on an existing threshold”.
Automation Manager.
2. On the Event Automation Plans page, click Create. The Event Automation Plan
Related tasks:
“Creating an event automation plan based on an existing threshold” on page 273
Monitoring for IBM ii message queue events
Monitoring the deployment of configuration plans and configuration templates
Related reference:
mkevtautopln command
Selecting the events that trigger an event action

The event automation plan uses event filters to monitor for the occurrence of one
or more specified events. When these events occur, your event automation plan
responds with one or more customized event actions.
The types of events that you can select and the ways that you can filter events are
broadly divided between the following categories:
v Common event filters
v Advanced event filters
Common event filters are predefined simple filters that monitor for events of
common interest in systems management. For example, the Disks event filter is
triggered by any hard disk events and the Fans event filter is triggered by any fan
events. The Event Automation Plan wizard provides several common event filters
so you can create typically required event automation plans quickly and easily. For
more information about event filters, see “Event filters.”
If you want to monitor specific events that are not included in the common event
filters, then you must select advanced event filters. You also can create more
sophisticated event filters that are triggered when duplicates of an event are
received, when events occur a specific number times over a range of time, or when

a specific event is received but you want to exclude another event. For more
information about event filters, see “Event filters.”
Related concepts:
“Event filters” on page 294
“Events that are available for filtering” on page 295
“Simple event filter” on page 296
“Duplication event filter” on page 297
“Exclusion event filter” on page 297
“Recurring event filter” on page 298
Related tasks:
Creating an event automation plan based on an existing

threshold
Use this method to create an event automation plan that uses the target system
and the event types that are specified by an existing active threshold. When
creating an event automation plan based on an existing threshold, you need to
specify only a few settings: the threshold levels that you want to monitor, the
event actions that you want the plan to include, and the time range that
determines when the plan is active.
1. From the Monitor View page or the Thresholds page in the IBM Systems
Director Web interface, select a monitor with an active threshold.
2. Click Create Event Automation plan. The Event Automation Plan wizard is
displayed.
Related tasks:
Deactivating and activating an event automation plan

You can deactivate an event automation plan such that the specified events do not
trigger the plan. When you want the event automation plan available for events to
trigger again, you can subsequently activate the event automation plan. By default,
event automation plans are activated.
Deactivating an event automation plan can be useful if you want to temporarily

turn off an event automation plan. For example, if you have an event automation
plan that notifies you of printer problems by sending a message to your mobile
phone, you can turn off the event automation plan while you are gone on vacation,
but turn it back on when you return.
To deactivate and then activate an event automation plan, complete the following
steps:
Automation Manager.
want to deactivate.
Note: You can deactivate more than one event automation plan at a time.
3. Click Actions > Deactivate. The event automation plan is deactivated. On the
Event Automation Plans page in the Status column, the state is changed from

Active to Inactive. A message is displayed on the page stating that the event
automation plan was deactivated successfully.
4. When you want to activate the event automation plan, select the plan and click
Actions > Activate. The event automation plan is activated. On the Event
Automation Plans page in the Status column, the state is changed from Inactive
to Active. A message is displayed on the page stating that the event automation
plan was activated successfully.
Related reference:
evtautopln command
Deleting an event automation plan

You can delete an event automation plan when it is no longer useful.
To delete an event automation plan, complete the following steps:

Automation Manager.
want to delete.
Note: You can delete more than one event automation plan at a time.
3. Click Delete.
4. In the confirmation window, click Delete.
The event automation plan is deleted and is no longer displayed on the Event
Automation Plans page. A message is displayed on the page stating that the event
automation plan was deleted successfully.
Related reference:
rmevtautopln command
Editing an event automation plan

Edit an event automation plan to change settings in a preexisting event automation
plan.
To edit an event automation plan, complete the following steps:

Automation Manager.
want to edit.
3. Click Edit.
4. In the event automation plan wizard, navigate to the pages that you want to
edit and make your changes.
need to make changes, click < Back Make sure to specify whether you want to
apply the event automation plan as soon as you finish creating it.
The event automation plan is saved and is displayed on the Event Automation
Plans page.

Related reference:
chevtautopln command
evtautopln command
Suspending and resuming event automation plans

You can suspend all event automation plans for a system (except for the Log All
Events plan) so that the specified events do not trigger the plans. When you want
the event automation plans available for events to trigger again, you can resume
all the event automation plans.
Suspending all event automation plans can be useful when you want to
temporarily turn off all event actions associated with the event automation plans.
For example, if you have automation plans that notify you when a server
encounters various problems, you can suspend all event automation plans while
you work on the server. After you resolve the problem, you can resume all event
automation plans for the server.
To suspend and then resume event automation plans, complete the following steps:
1. On the Initial Setup tab of the Home page, click Resource Explorer.
2. Navigate to the group that contains the resource for which you want to
suspend all the event automation plans.
3. Right-click the resource, then select Automation > Suspend Event Actions.
After you suspend event actions, no event triggers any event automation plan
for the selected resource, except the Log All Events plan. In the Suspended
Action Plans column for the specified resource, the state changes from False to
True.
Note: For more information about adding the Suspended Action Plans column
to the table, see “Setting table-column preferences”.
4. When you want to resume having event actions on the resource trigger event
automation plans, right-click the resource, then select Automation > Resume
Event Actions. After you resume event actions, event actions for the resource
again trigger event automation plans. In the Suspended Action Plans column,
the state changes from True to False.
Related tasks:
Viewing event automation plans associated with a resource

You can view the properties for a resource to determine whether that resource is
associated with any event automation plans.
To determine whether a resource is associated with any event automation plans,

1. Navigate to the resource and select it.
3. On the Properties page, click the Applied Activities tab.
On the Applied Activities page, you can view a list of any event automation plans
that can potentially affect the resource.

Viewing event automation plan properties
You can view the properties for an event automation plan for information about
the plan settings. This information is the same summary that you see when you
complete creating an event automation plan.
To view event automation plan properties, complete the following steps:

Automation Manager.
2. On the Event Automation Plans page, select the event automation plan whose
properties you want to view.
4. On the Properties page, view the settings for the event automation plan.
Note: The Actions button does not provide any event-filter specific actions
because there are none available on the Properties page.
Related reference:
lsevtautopln command
Managing event actions

Event actions specify the action that IBM Systems Director takes in response to a
specific event or events. You can create, copy, edit, test, and delete event actions as
well as view their properties. Also, you can record and view the history of an
event action.
Related reference:
Viewing event actions (lsevtact command)
Creating an event action

Create an event action to use in your event automation plans. You can create event
actions and test actions before using them in your event automation plans.
Typically, you create event actions in the Event Automation Plan wizard. However,
there might be times when you want to create an event action that you can use in
event automation plans at another time.
To create an event action, complete the following steps:

1. On the Plug-ins tab of the Home page, click Automation Manager. On the
Automation Manager summary page, click Event Actions under Plan
management.
2. On the Event Actions page, click Create.
3. In the Create Actions window, select an event action. For information about
event action types, see “Event actions.”
4. Click OK.
5. Type a name for the event action in the Action name field. Use a naming
convention that ensures the entries are grouped conveniently on the Event
Actions page. For example, if you want names to begin with the associated
action, an event action that sends a message to a pager or phone might start
with Pager or Phone.

6. Complete the remaining fields for the event action that you selected. For some
event action types, you can include event-specific information as part of the
text message. Including event information is referred to as event-data
substitution. You can use event-data-substitution variables to customize event
actions. For more information, see “Event-data-substitution variables.”
7. If the event action that you selected includes the Test button, you can
determine whether your settings are correct by clicking Test.
8. Click OK to save the event action. The new event action is displayed in the
Event action page.
Note: You can create and select more than one type of event action for your
event automation plan.
The event action is saved and is displayed on the Event Actions page.
Related concepts:
Related reference:
mkevtactemail command
mkevtactstpgm command
mkevtactsttask command
Editing an event action

Edit an event action to change settings in a preexisting event action.
To edit an event action, complete the following steps:

management.
2. On the Event Actions page, select the event action that you want to edit.
3. Click Edit.
4. Edit the settings that you want to change for the event action.
Event action page.
Copying an event action

Copy an event action when you want to create an event action that is like a
preexisting event action.
To copy an event action, complete the following steps:

management.

2. On the Event Actions page, select the event action that you want to copy.
3. Click Create Like.
4. Edit the settings that you want to change for the event action.
Event action page.
Related reference:
mkevtactemail command
mkevtactstpgm command
mkevtactsttask command
Testing an event action

You can test an event action to make sure that the settings perform as expected. It
is a best practice to test an event action before using it in an event automation plan
so you can avoid unexpected results.
The following event actions cannot be tested because critical information is not
available until a system generates the event and triggers an event automation plan:
v Start a program on the system that generated the event
v Start a task on the system that generated the event
v Update the status of the system that generated the event
To make sure that an event action can be tested, select the event action and click
Actions > Properties. The Properties page for the event action states whether the
event action can be tested.
To test an event action, complete the following steps:

management.
2. On the Event Actions page, select the event action that you want to test.
3. Click Actions > Test.
4. In the confirmation window, click Test. A message is displayed on the page
stating whether the event action was started successfully. If the selected event
action cannot be tested, a message also is displayed.
5. To view details about the test, select the event action and click Actions >
Properties. An example of the kind of detail you might want to view is
whether the action completed successfully.
6. On the Properties page, click the History tab to view details about the test.

Related concepts:
“Send an e-mail to a mobile phone” on page 301
“Send an Internet (SMTP) e-mail” on page 301
“Start a program on a system” on page 309
“Start a program on the management server” on page 309
“Start a task on a specified system” on page 310
Related reference:
testevtact command
Deleting an event action

You can delete an event action when it is no longer useful.
To delete an event action, complete the following steps:

management.
2. On the Event Actions page, one or more event actions that you want to delete.
3. Click Delete.
The event action is deleted and is no longer displayed on the Event Actions page.
A message is displayed on the page stating that the event action was deleted
successfully.
Related reference:
rmevtact command
Saving and not saving an event-action history

You can save useful information about an event action by saving the event-action
history. When you no longer want to save the event-action history, you can stop
saving it. By default, the event-action history is not saved. To view an event-action
history, see “Viewing an event-action history.”
Saving the history of an event action can provide useful information. For example,
an event automation plan can include an event action that reduces disk-space used
by running a program to remove temporary files. When you start saving the
history for this event-action, the following information is recorded:
v The date and time when the event action ran and, later, when the cleanup
program ran
v Whether the program ran successfully
v The event that triggered the event filter.
To start and then stop saving the history of an event action, complete the following
steps:
management.
2. On the Event Actions page, select the event action with the history that you
want to start saving.
Note: You can start saving the history for more than one event action at a time.

3. Click Actions > Start Saving History. The history of the event action is now set
to be saved. On the Event Actions page in the History column, the value is
changed from Not saved to Saved. A message is displayed on the page stating
that saving of the event-action history was started successfully.
4. When you want to stop saving the history for an event action, select the event
action and click Actions > Stop Saving History. The history of the event action
is set to no longer be saved. On the Event Actions page in the History column,
the value is changed from Saved to Not saved. A message is displayed on the
page stating that saving the event-action history was stopped successfully.
Related reference:
evtacthist command
Viewing an event-action history

You can view an event-action history for information about how an event action
ran in your systems-management environment.
Before you can view the history for an event action, you have to start saving the
history for that event action. For information, see “Saving and not saving an
event-action history.”
Saving the history of an event action can provide useful information. For example,
an event automation plan can include an event action that reduces disk-space used
by running a program to remove temporary files. When you start saving the
history for this event-action, the following information is recorded:
v The date and time when the event action ran and, later, when the cleanup
program ran
v Whether the program ran successfully
v The event that triggered the event filter.
To view the history for an event action, complete the following steps:
management.
2. On the Event Actions page, select the event action for which you want to view
the history.
4. On the Properties page, click the History tab to view the event-action history.
Each log entry in the history provides the following information about each
time the event action was used:
Date The date and time on which the event was generated.
Launch Status
Event action launch status, which indicates whether the action was
launched successfully. Possible values are successful and failed.
Completion Date
The date and time when the event action completed.
Completion Status
Event action completion status, which indicates whether the action ran
successfully. Possible values are successful, failed, and not performed.
The Not Performed status is specific to three event actions: Modify an
event and send it, Start a program on a system, and Start a task on a
specified system. If you do not configure any modifications to make to
an incoming event, the event is not sent again and the event action
status is considered not performed. For the latter two events, if the
specified system cannot be found when the event action is invoked,
then the action cannot be performed.
Managed Resource
Target system on which the event occurred.
Event Type
The type of event that was generated. The event types are categorized
by hardware, device, or software.
Category
The mode of the event. Possible categories are:
Alert A problem occurred.
Resolution
A problem was resolved and is no longer a problem.
Event Severity
The severity level of the event, which identifies potentially urgent
problems requiring immediate attention. Possible severity levels are:
Fatal The source of the event has already caused the program to fail
and needs to be resolved before the program is restarted.
Critical
The source of the event might cause program failure and needs
to be resolved immediately.
Minor The source of the event is not likely to cause immediate
program failure, but needs to be resolved.
Warning
The source of the event is not necessarily problematic, but
might warrant investigation.
Informational
The event was generated for information only. Most events of
this severity do not indicate potential problems. However,
offline events are categorized as informational, and these events
can indicate potential problems.
Unknown
The application that generated the event did not assign a
severity level.
Sender
The system that sent the event to IBM Systems Director Server. For
example, SNMP events list the IP address of the trap source. Because
most events are generated by IBM Systems Director Server, this field
typically contains the name of the management server.
Related reference:
lsevtacthist command
Refreshing entries in an event-action history log

You can refresh an event-action history log so that you can view the latest
available entries.
To refresh an event-action history log, complete the following steps:

management.
2. On the Event Actions page, select the event action for which you want to view
the history.
5. On the History page, click Refresh. The list of available log entries is refreshed.
Deleting entries from an event-action history log

You can delete log entries from an event-action history when the entries are no
longer useful.
To delete a log entry, complete the following steps:

management.
2. On the Event Actions page, select the event action whose history-log entries
you want to delete.
5. Select one or more log entries that you want to delete.
6. Click Delete.
The log entry is deleted and is no longer displayed on the History page. A
message is displayed on the page stating that the log entry was deleted
successfully.
Viewing event action properties

You can view the properties for an event action for information about the action
settings. Also, the Properties page lists the event automation plans that include the
event action.
To view event-action properties, complete the following steps:

management.
2. On the Event Actions page, select the event action whose properties you want
to view.
4. On the Properties page, view the settings for the event action. The settings vary
depending on the type of the event action.
Note: The Actions button does not provide any event-action specific actions

Related reference:
lsevtact command
Event-data-substitution variables
For some types of actions, you can include event-specific information as part of the
message text. Including event information is referred to as event-data substitution.
You can use event-data-substitution variables to customize the message text sent
by an action.
The following examples show how you can use event-data-substitution variables in
the message text associated with a customized event action:
v &severity - &text on &system
v Event &text received from &system at &time on &date
Tip: When you use event-data-substitution variables, do not use punctuation after
the variable, for example:
Event received from &system.
&system cannot be interpreted correctly because of the period.
You can use the following event-data-substitution variables.
Note: Any of the substitution variables can have a null value. In that case, the
localized version of the string “Not Applicable” is returned.
&date The localized date on which the event occurred.
Example: 7/23/2007
&ipaddr
The IP address of the system on which the event was generated. This is
either the IP address of the system running Common Agent or, for an
SNMP device, the TCP/IP address.
Example: 9.45.2.69
&iphost
The IP host name of the system on which the event was generated. This is
either the name of the system running Common Agent or, for an SNMP
device, the TCP/IP host name.
Example: moonlite.mycompany.com
&time The localized time at which the event occurred.
Example: 2:32 PM CDT

&text The event details, if they are supplied by the event.
Example: System moonlite is offline with errors.

&type The event-type criteria that were used to trigger the event. For example,
the event that is generated when a system goes offline is of type Topology
> Offline. This type corresponds to the entry on the Event Type page.
Example: ComputerSystem or Processor

&severity
The severity level of the event.
Example: Informational
&system
The system name of the system on which the event was generated. This is
either the name of the system running Common Agent or, for an SNMP
device, the TCP/IP address.
Example: moonlite
&sender
The name of the system that sent the event. This can be different from the
&system value if the event was forwarded or transmitted through an
intermediate system. This variable returns a null value if the name is
unavailable.
Example: moonlite
&group
The group to which the target system belongs and that is monitoring the
system. This variable returns a null value if the group is unavailable.
Example: TestHardwareGroup
&category
The category of the event, either Alert or Resolution. For example, if the
system goes offline, the category is Alert. If the system goes online, the
category is Resolution.
Example: Alert
&pgmtype
The fully qualified representation of the event type using internal type
strings (ComponentCategory.ComponentType).
Examples: Managed Resource > Managed System Resource > Logical

Resource > Logical Device > Processor
&timestamp
The long value timestamp of the time that the event occurred, in
milliseconds, since 1/1/1970 12:00 AM GMT.
Example: 1185219178228
&rawsev
The nonlocalized string of event severity. Non-localized string of the event
severity.
Example: Any of the following strings: “FATAL”, “CRITICAL”, “MINOR”,

“WARNING”, “INFORMATIONAL”, “UNKNOWN”.
&rawcat
The nonlocalized string of event category.
Example: Any of the following strings: “ALERT”, “RESOLUTION”.

&corr An internally generated correlation identifier for this event. This identifier

allows an alert event to be correlated with a resolution event, thereby
indicating that the problem that caused the alert has been corrected. The
length of this string can vary.
Example: 1883481972341237
&snduid
The unique ID of the event sender.
Example: 7F153619BA2D7861
&sysuid
The unique ID of the system that is associated with the event.
Example: 4309132478791324
&prop:file_name#property_name
The value of the property string property_name from property file file_name.
file_name can include the absolute directory path or the relative path to the
IBM\Director\classes directory.
Note: For IBM i, you must use the absolute directory path.
The properties file contains key=value pairs. property_name is the name of a
key in the properties file. The value of the specified property is returned.
The value can be any string, depending on the purpose and contents of the
properties file.
Examples:
&prop:logging.properties#SystemErr.level = INFO
&prop:encoding.properties#zh = UTF-8
&prop:security.properties#enableAuthentication = TRUE
&sysvar:variable_name
The string value of a variable, variable_name, previously set in the IBM
Systems Director sysvar file. Variables can be set in this file using the Set
an event system variable event action. The variable name and value can
be any string. This variable returns null if a value is unavailable. For
information about the event action, see “Set an event system variable.”
Examples:
&sysvar:DEBUG_SETTING = DEBUG_ON
&sysvar:IP = 9.3.44.150
&slotid:slot_id
The nonlocalized ID slot_id is the identifier of event details contained
within the event. An event might include any number of event details. This
substitution variable is used to retrieve those details. The user must know
the identifier of the event detail that they want. The value can be any
string as defined by the component that generates the event.
Example: &slotid:Suppressions = “3 instances of this condition have been

suppressed.”
&otherstring
If any other word is preceded by an &, it is treated the same as the slot_id

in the previous &slotid:slot_id variable. The otherstring string is used as an
identifier to locate event details contained with the event.
The value of the detail slot that has a localized label that matches
otherstring. A detail slot is a record in an event detail. For example, an event
might have one event detail that has an ID of key1 and a value of value1.
You could use the substitution variable &slotid:key1 to obtain the value
value1. You also can use &key1 to obtain the value value1. In the
description above, otherstring is a placeholder for the user-defined event
detail ID. However, if the passed ID is not found, the value Not
applicable is returned.
Example: &Suppressions = “3 instances of this condition have been

suppressed.”
Related concepts:
“Log to a log file” on page 299
“Modify an event and send it” on page 300
“Post to a newsgroup (NNTP)” on page 300
“Send an e-mail to a mobile phone” on page 301
“Send an Internet (SMTP) e-mail” on page 301
“Set an event system variable” on page 308
“Static group: add or remove group members” on page 311
“Static group: add or remove the event-generating system” on page 312
“Timed alarm that generates an event” on page 312
“Timed alarm that starts a program” on page 313
Managing event filters

A filter specifies one or more events that you want your event automation plan to
process. The event automation plan ignores any event instances that do not meet
the specifications of the filter. You can create, copy, edit and delete event filters.
Related reference:
Viewing event types (lsevttype command)
Creating, editing, or copying an event filter

Create an event filter to use in your event automation plan. Typically, you create
event filters in the Event Automation Plan wizard. You can use the Event Filter
wizard to create an event filter that you intend to use in an event automation plan
at another time. Also, you can edit an existing event filter or create one by copying
and modifying an existing filter.
You create event filters so that you can use them in your automation plans. As you
create or edit event filters, you specify the types of events and event characteristics
that you want to include in the filter. The filter is triggered when those included
events are encountered during the processing of an automation plan.
To create an event filter, edit an existing filter, or create a filter that is based on an
existing filter, complete the following steps:

Note: The Event Filter wizard determines which panels to display based on your
choices. Different panels display depending on the type of events and event
characteristics that you choose to include.
Automation Manager summary page, click Event Filters under Plan
management.
2. Perform only one of the following actions.
v If you want to create an event filter, click Create.
v If you want to edit an existing event filter, select the filter you want to edit,
then click Edit.
v If you want to create an event filter that is like an existing filter, select the
existing filter, then click Create Like.
3. On the Welcome page, click Next.
4. On the Filter Name page, type a name and description for the event filter,
then click Next. Although it is not required, a description does help you sort
and manage your event filters.
5. On the Filter Type page, select the type of filter that you want to create, then
click Next. For more information about the different filter types, see “Event
Filters”.
6. On the Event Type page, complete one of the following actions to select the
type of event that you want to include, then click Next.
v Select Default to include events of all types, except for Windows-specific
events. Optionally, you can include IBM i message queue events.
v Select Common to include the most common systems-management event
types, except for Windows-specific events. Optionally, you can include IBM
i message queue events. Click the name of an event type to see a
description and any additional settings. If an entry has additional settings,
make sure to select the event type and each setting that you want to
include.
v Select Custom to specify event types by category, type, and value.
Optionally, you can include IBM i message queue events. The Available
table is a hierarchical list of event types. Click an entry in the table or the
breadcrumbs above the table to navigate within the hierarchy. Select an
entry to include that entry and any entries in subsequent levels of the
hierarchy. (The table also lists available Windows-specific events.)
7. If the IBM i Event type page appears, specify IBM i messages that you want
to include. Otherwise, go to the next step.
a. Type each message that you want to include.
Note: Use the following format: library/message_queue.messageID, where,

for each specified event
v library is the library
v message_queue is the message queue
v messageID (optional) is the ID
The IBM i.Message Queue field automatically provides the common
message queue event prefix, which is OS/400.msgq. You type only the
unique portion of the message queue event. Consider the following
examples that assume the library is QSYS and the message queue is
QSYSOPR:
v To specify all message IDs, type QSYS/QSYSOPR.
v To specify a message ID of CPF1234, type QSYS/QSYSOPR.CPF1234.

v To specify any message ID that starts with the characters CPF:
– If the managed resource has 5770UME V1R3 and all the available
UME PTFs installed, type QSYS/QSYSOPR.CPF.
– Otherwise, type QSYS/QSYSOPR. Then, on the Event Text page of Event
Filter wizard, specify that you want to look for the characters CPF.
b. Click Add to add the message to the list of Selected IBM i event types.
c. When you are finished adding messages, click Next.
8. If the Excluded Event Type page appears, specify the event types that you
want to exclude, then click Next. Otherwise, go to the next step. Excluded
events do not trigger the filter. You specify the event types to exclude in the
same way that you specified the event types to include in step 6 on page 337
Optionally, you can exclude IBM i message queue events. To exclude available
Windows-specific events, select Custom.
9. If the Excluded IBM i Event Type page appears, specify the IBM i messages
that you want to exclude. Otherwise, go to the next step. Excluded events do
not trigger the filter. You specify the messages to exclude in the same way that
you specified the messages to include in step 7 on page 337
10. On the Severity and Category page, specify the severities and categories that
you want to include, then click Next. Select Default to include events of all
severities and categories. Select Custom to specify one or more severities and
categories.
11. On the Event Sender page, you can add any specific event senders that you
want to include in the filter. The filter is triggered when a specified sender
generates an event that you included in the filter. Choosing Default includes
events sent from any managed resource.
a. Select a sender from the Systems list, then click Add to add it to the
Selected senders list.
b. To add a sender that does not appear in the Systems list, type the name of
the sender in the Additional sender field, then click Add.
c. When you are finished adding senders, click Next.
Important: Remember to update any specified sender name if you rename

the associated resource (the sender). When a managed resource is renamed,
IBM Systems Director does not automatically update the associated sender
name in an event filter. Renaming the resource without updating the event
filter results in a mismatch between the sender name that is specified in
the event filter and the sender name that is specified in the incoming
event. The mismatch in sender names causes any event action plan that
includes the filter to fail.
12. On the Event Text page, specify the event text that you want to include in the
filter, then click Next.
v Select Default to include all event text.
v Select Custom to specify a word, separate words, or a phrase that you want
to include in the filter. The filter is triggered by only those events that you
include in the filter that also contain the specified text.
13. If the Frequency page appears, specify how often an event occurs before
triggering this filter. Otherwise, go to the next step.
v Select Default to trigger the filter any time an included event occurs.
v Select Custom to specify how many times an event must occur before
triggering the filter, called the matching event count. Optionally, you can
specify a time interval within which the event must occur.

14. If the System Variables page appears, specify the system variables that you
want to include, then click Next. Otherwise, go to the next step. The filter is
triggered when an included event occurs that has a specified keyword and
value pair with a given value.
v Select Default if you want to include all events, regardless of whether they
have system variables.
v Select Custom so that the filter is triggered only when included events also
contain one of the selected keyword and value pairs that has a specified
value.
15. On the Time Range page, specify when you want events to trigger the filter,
then click Next.
v Select All so that the filter is triggered any time that included events occur.
v Select Custom to specify that the filter is triggered only when included
events occur on a particular day of the week or within an identified time
range.
16. On the Summary page review your settings. If you want to modify any
settings, click Back to make changes. When you are satisfied with the event
filter, click Finish to save it.
The event filter is saved and is displayed on the Event Filters page.
Related concepts:
Related tasks:
“Viewing the automation manager summary” on page 319
Related reference:
Events Reference
Editing an event filter

Edit an event filter to change the settings in an event filter that you previously
created.
To edit an event filter, complete the following steps:

management.
2. On the Event Filters page, select the event filter that you want to edit.
Note: IBM Systems Director includes some predefined event filters that you
cannot edit. You can create an event filter that is like a predefined filter by
using Create Like, but you cannot directly edit it.
3. Click Edit. The Edit Event Filter wizard is displayed.
4. Use the Edit Event Filter wizard to edit the event filter. The Edit Event Filter
wizard uses the same panels as the Create Event Filter wizard. For more
information about using an Event Filter wizard to create or edit an event filter,

see “Creating an event filter”. After you finish using the Edit Event Filter
wizard to save the event filter, it is displayed on the Advanced Event Filters
page.
The edited event filter is saved and displayed on the Event Filters page.
Related concepts:
Related tasks:
Copying an event filter

Copy an event filter when you want to create an event filter that is like a
preexisting event filter.
To copy an event filter, complete the following steps:

management.
2. On the Event Filters page, select the event filter that you want to copy.
3. Click Create Like. The Copy Event Filter wizard is displayed.
4. Use the Copy Event Filter wizard to create an event filter based on the one that
you selected. The Copy Event Filter wizard uses the same panels as the Create
Event Filter wizard. For more information about using an Event Filter wizard
to create or edit an event filter, see “Creating an event filter”. After you finish
using the Copy Event Filter wizard to save the event filter, the filter is
displayed on the Advanced Event Filters page.
The new filter that is based on a preexisting filter is saved and displayed on the
Event Filters page.
Related concepts:
Related tasks:
Viewing event filter properties

You can view the properties for an event filter for information about the filter
settings. Also, the Properties page lists the event automation plans that include the
event filter.
To view event-filter properties, complete the following steps:

management.
2. On the Event Filters page, select the event filter whose properties you want to
view.
4. On the Properties page, view the settings for the event filter. The settings vary
depending on the type of the event filter.
Note: The Actions button does not provide any event-filter specific actions
Related tasks:
Related reference:
lsevtfltr command
Viewing predefined filter criteria

You can view the criteria used to define a predefined event filter.
Note: You cannot change predefined event filters; they are read-only. However,
you can copy a predefined filter and change the copy. For more information, see
“Copying an event filter.”
If you want to see what event filter criteria are included in a predefined event
filter, complete the following steps:
management.
2. On the Event Filters page, select the predefined filter that you want to view.
Related concepts:
Deleting an event filter

You can delete an event filter when it is no longer useful.
To delete an event filter, complete the following steps:

management.
2. On the Event Filters page, select the event filter that you want to delete.
Note: You can select to delete more than one event filter at a time.
3. Click Delete.
The event filter is deleted and is no longer displayed in the Event Filters page. A
message is displayed on the page stating that the filter was deleted successfully.

Related tasks:
Related reference:
rmevtfltr command
Exporting and importing event automation plans, event filters, and

event actions
Event automation plans, event filters, and event actions can be exported and
imported as an XML file on the management server.
Using CLI commands to export and import event automation plans, event filters,
and event actions makes it easier and faster to use multiple instances of your
plans, filters, and events. For example, you can export a set of event filters then
import them to other systems. Or, after exporting some event automation plans to
a development environment, you can modify and test them safely, then import
them to the systems in your production environment.
Use any XML editor to create or edit an XML file. Importing the XML file creates
the event automation plan, event filter, or event action, but does not update or
replace any existing plan, filter, or action. The import process checks and compares
the event automation plans, event filters, and event actions that you are importing
with the plans, filters, and events that reside on the management server. The
import process then reports any errors and conflicts.
The schema files used for exporting and importing automation data reside in
install_directory\proddata\schema\xml, where install_directory is the location where
IBM Systems Director is installed.
v When exporting XML files, using the -F option with the CLI commands creates a
copy of the schema in the same directory as the exported files, if the schema
does not exist in that location.
v When importing XML files, the schema file needs to be in the same directory as
the imported file. The CLI commands create a copy of the schema in the same
directory as the one to which the XML file is imported, if the schema does not
exist in that location.
Related tasks:
“Migrating and importing event automation data from a previous version”
Migrating and importing event automation data from a previous

version
When you update and migrate IBM Systems Director Server, the existing event
automation plans, event filters, and event actions are also migrated. You might also
choose to import automation data that was created by using a previous version of
Systems Director. A migrated or imported event automation plan that contains
certain event actions might need to be reviewed to ensure that any related
commands or tasks perform as expected.
In previous versions of Systems Director, a user could create or edit an event

action that runs a program or starts a task that might be beyond the authority
specified for that user. In Systems Director 6.3 and higher, the following event
actions are available only to users with SMAdministrator authority. That is, the
user must be a member of the smadmin group:
v Start a program on a system
v Start a program on the management server
v Start a program on the system that generated the event
v Start a task on a specified system
v Start a task on a system that generated the event
v Timed alarm that starts a program
After you migrate or import an event automation plan from a previous version of
Systems Director, the EventActionPlanRisk.log file identifies the plans that contain
event actions that are meant to be created by a user with SMAdministrator
authority. Review the identified event actions to ensure that the actions (and the
related commands or tasks) are valid.
Starting or restarting the management server generates the

EventActionPlanRisk.log file, which resides in install_root/logs directory, where
install_root is the root directory of your IBM Systems Director installation.
The following example shows how the log identifies an event action and the
related commands that you might want to examine. The log also identifies the
event automation plan and event filter in which the event action occurs.
Plan Name Filter Name Action Name Action Type
*********************************************************
p123 p123-Filter apg-sys Start a program on a system
p123 p123-Filter pgm on-ISD Start a program on the management server
p123 p123-Filter pgm on evt-sys Start a program on the system that generated the event
p123 p123-Filter start-task Start a task on a specified system
p123 p123-Filter run-task-evt-sys Start a task on a system that generated the event
p123 p123-Filter time-spg Timed alarm that starts a program
Related tasks:
“Exporting and importing event automation plans, event filters, and event actions”
on page 342
Using command automation

Use the Command Automation task to create, edit, copy, and delete command
definitions. A command definition specifies and configures a command-line
program that you want to run on a managed system. Anonymous command
restrictions apply to command definitions.
Notes:
v Users with SMAdmin roles are given unrestricted access to target systems. These
users always have “root” or “admin” access on IBM Systems Director - managed
systems when running command automation through IBM Systems Director.
This is regardless of what command-line context access the user has on the
target. If this causes a security violation, give users SMManager or other
customized roles that prevent them from accessing command automation.
Creating or editing a command definition

Use the command automation task to create and run a command definition, which
specifies the command-line program that you want to run on a managed system.
You can create a command definition, create one based on an existing command
definition, or edit an existing command definition.
Note:

v Command automation is supported only on systems on which Common Agent
is installed.
v Remember that anything a system-account user can do from a command line
can be done to the system, regardless of the user who is logged in to the
managed system.
To create or edit a command definition, perform the following steps:

1. In the IBM Systems Director Web interface navigation area, click Automation >
Command Automation.
2. Determine if you want to create a command definition, create a command
definition based on an existing one, or edit an existing command definition.
v If you want to create a command definition, click Create.
v If you want to create a command definition that is based on an existing
command definition, select a command definition from the table, then click
Create Like.
v If you want to edit an existing command definition, select a command
definition from the table, then click Edit.
3. In the Create Command Definitions window, specify information about the
command definition:
a. Accept the default name for the command definition or type a new name in
the Name field.
b. In the Command to run field, type the fully qualified file name and
command syntax. Consider the following information:
v For managed systems running IBM i, the command is run in the Qshell
environment. To run an IBM i system command (such as the call
command), specify the command similar to the following example:
system ’call mylib/myclpgm’
The command runs within the Qshell environment and enables you to
access the IBM i system commands.
v For managed systems running Windows, preface the command with the
following string to ensure that it runs in a Windows command-shell
window:
cmd /c
c. In the Timeout field, type a timeout value, in seconds. The timeout value
specifies the number of seconds to wait for the command either to return a
completion code or time out. Make sure that the timeout value is long
enough.
d. Select the Log check box if you want to log any output produced by the
command, for example, a directory listing.
e. Either accept the default user ID (or the existing user ID if you clicked Edit
or Create Like) or type a new user ID that has the required authority to
perform the command. If you want to run the process using an alternative
user account and override the default user ID, you can specify a user ID
and password in the Login group box.
Note: (Managed systems running IBM i only) Commands cannot be performed

using the default user ID that is shipped with IBM Systems Director. For a
command definition to run successfully on IBM i systems, the command
definition must specify a valid user ID and password, or the managed system
to which it is being run must be configured to specify a user that has the
authority to run the command definition. You can register that user in the IBM

Director Agent default user function ID on the managed system system using
Application Administration in Power Systems Navigator.
Note: You either must specify an alternative user ID or remove the default user
ID from the registered function and add a new default user ID that has the
required authority to perform the command.
4. Click OK to save the command definition.
The Command Automation page displays the new command definition.
Running a command definition

After creating a command definition, you can run it on one or more specific
managed resources. Run the command definition immediately, or schedule the
command to run at a specific time or at regular intervals.
As an alternative to using the Command Automation task in the IBM Systems

Director Web interface, you also can specify the command definition as an action
in an event automation plan.
Note:
v Command automation is supported only on systems on which Common Agent
is installed.
v Using the Command Automation task to start interactive programs, for example
notepad.exe, is not supported.
To run a command definition, perform the following steps:

1. In the IBM Systems Director Web interface navigation area, click Automation >
Command Automation.
2. Select the command definition that you want to run. The Command
Automation page is displayed.
3. Click Run. The Launch Job window displays.
4. Use the Launch Job window to specify one or more target resources on which
you want to run the command and determine when you want to run the
command. You can also specify other options, including notification settings.
5. After you finish specifying the configuration for this command definition in the
Launch Job window, click OK to use your settings to run the command
definition.
Restricting anonymous command execution

By default, commands are run on the managed system as either system account
(Windows) or root (Linux). You can restrict anonymous command execution by
disabling this function and always requiring a user ID and password.
Restricting anonymous command execution on Linux

You can restrict anonymous command execution on managed systems running
Linux.
To restrict anonymous command execution, complete the following steps:

1. Change to the directory in which Common Agent is installed. If you installed
IBM Systems Director in the default directory, the directory name is
opt/ibm/director/data.
2. From a command-line prompt, type the following string, and then press Enter:

vi ProcMgr.properties
3. Change the value of RestrictAnonCmdExe to True.
4. Save the file. The change takes effect immediately.
Restricting anonymous command execution on Windows

You can restrict anonymous command execution on managed systems running
Windows.
To restrict anonymous command execution, complete the following steps:

1. On a Windows system, type regedit at a command line and press Enter:
2. Navigate to the registry entry HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\
Director\CurrentVersion.
3. Double-click RestrictAnonCmdExec.
4. In the Value data field, change 0 to 1.
5. Click OK. The change takes effect immediately.

Chapter 7. Updating systems
Use the IBM Systems Director update manager to acquire, install, and manage
updates, as well as to monitor your systems to ensure that they remain current.
Update manager enables you to keep your systems at desired software or firmware
update levels by automatically checking for available updates and identifying
which systems need attention. It also provides you with the ability to monitor your
systems for needed updates and schedule the installation of updates at times that
are convenient for your network and users.
Update manager compares update information that is loaded into it with the
inventories of specified systems to determine whether updates are needed. To load
current information about available updates into update manager, you can use the
update manager Acquire updates task. Within that task, you can use either of the
following functions, both of which supply the same exact source for update
manager:
v Acquire updates: If an Internet connection is available, the acquire updates task
automatically contacts the update repository and downloads information about
the latest available updates into update manager.
Note: To acquire updates, the IBM Systems Director Server must have Internet
Protocol version 4 (IPv4) Internet access. This access can be through a direct
connection or through a Hypertext Transfer Protocol (HTTP) proxy that you
configure in the Settings task. (See “Changing update settings” for more
information.) If an IPv4 connection is unavailable, you can instead import the
updates for more information.
v Import updates from the file system: If no Internet connection is available, you
can manually download supported updates and then import them into update
manager.
Update manager then enables you to examine recently acquired updates and install
any that are needed.
Note: Because update manager determines needed updates by comparing

information about available updates with system inventories, the update
information must be current. To help keep update manager up to date, schedule a
recurring Acquire updates task that will regularly download update information
since the last acquire updates was run. Alternatively, you can regularly monitor
www.ibm.com/support/fixcentral/ and import updates that your systems might
need into update manager.
If your systems need updates, you can use update manager to manage the
installation.
Important: For update manager to determine which updates are needed, you must
ensure that the software inventory for monitored systems is collected and current.
Most update manager methods cannot determine the applicability of updates to a
system unless inventory was previously collected on the system.
To view a table of the updates needed by your systems, you can use the update
manager Show and install updates task. From this table, you can select which
updates to install.

Notes:
v Before update manager installs updates, it displays information about whether
system restarts are required. You can allow or disable automatic restarts. If
automatic restarts are allowed, update manager calculates the installation
sequence that minimizes the number of restarts. Alternatively, you can manually
control the restarts.
v During installation, update manager automatically downloads the update
installation files and distributes them across your network to complete the
installation. As with restarts, you can also manually control these steps to
minimize disruption.
To receive an automatic notification when updates are required to keep your

systems current or at a specified update level, you can use update manager to set
up compliance policies. These policies specify which systems are monitored and
which updates you must install to keep the systems in compliance. Update
manager uses these policies to check the status of your systems and notifies you
when systems need updates, and which updates are needed. To set up compliance
policies, you can use the update manager Create and configure compliance
policies task. After a compliance policy is set up, the compliance pie chart then
appears on the Update Manager summary page and you can use that to monitor
compliance status and take any necessary corrective action.
Note: As a best practice, plan to update to the latest update or patch for your
release of IBM Systems Director at least twice a year. Maintaining this schedule
will help to eliminate unnecessary exposure to problems that are already resolved
in more current updates and patches. Staying farther back on maintenance can also
inhibit the ability of your service representative to provide a formal fix without
first requiring the application of a more current update or patch.
Related tasks:
Installing agents
Planning to upgrade or update

Planning to upgrade or update
Related reference:
Update commands
Planning to update systems

Complete these planning steps before starting the actual update process to ensure
that the update process that you follow is successful and meets your needs.
Supported update tasks

You can use update manager to complete various update tasks, including
downloading and installing updates to existing software and setting up compliance
policies to monitor your systems. You can also use update manager to manage
individual updates or sets of updates that are known as update collections.
Update manager performs the following tasks:

v Manage and install updates to existing software products and firmware, external
network and storage switches, and external storage servers.
v Install updates to IBM Systems Director.
v Install updates to IBM Systems Director agents that have already been installed.

v Acquire and install an individual update or update collection with the following
sequence of tasks:
1. Downloading, which copies the installable files for an update to the
management server.
2. Installation staging, which copies the installable files for an update to an
appropriate location for eventual installation.
3. Installing, which installs an update.
4. Uninstalling, which removes an update.
Note: Not all updates support the uninstallation task.

v Manage compliance policies, which provide notification of when systems are in
need of updates and which updates are needed.
v Schedule a check for updates, which is a search for new updates of which
update manager is not currently aware. If any new updates are found, update
manager obtains the necessary information that is required to include these
updates.
v Provide details about a specific update, such as its documentation and
prerequisite requirements (requisite updates).
v Display information about updates that were installed by IBM Systems Director.
Note: Updates installed by other means are not displayed.
Update manager does not perform the following tasks:

v Install new software products.
v Install IBM Systems Director agents on systems that currently do not have an
agent.
Instead, install IBM Systems Director agents with the agent manager plug-in of
v Migrate to any version of IBM Systems Director from any version of IBM
Director.
v Migrate to IBM Director 5.2 from IBM Director 5.1.
v Perform actions on systems that are not accessible. You can perform update
actions on only those systems that are accessible.
Notes:
– If a system is not accessible, the update menu actions are not displayed for it.
You cannot select a system that is not accessible in any of the system selection
actions, for example on the System page in the Installation wizard, on the
Installation staging wizard, and so on.
– If you want to monitor update management and compliance status on any
systems that are not accessible, you must first run inventory collection on
them. Most update manager methods cannot determine the applicability of
updates to a system unless inventory was previously collected on the system.
v Update another, different instance of IBM Systems Director Server.
Supported updates and systems

This is a list of supported updates and the systems to which they apply. Unless
otherwise noted, the systems can be Agentless managed systems, Common Agent
managed systems, and Platform Agent managed systems.
v IBM Systems Director 6.3.x, as follows:
– Common Agent
Chapter 7. Updating systems 349

– Platform Agent
– IBM Systems Director Server
v IBM Systems Director 6.2.x and 6.1.x, as follows:
– Common Agent
– Platform Agent
v IBM Director V5.20.x, as follows:
– IBM Director Agent version 5.20
– IBM Director Core Services version 5.20
v Technology levels and service packs for AIX 5.3 TL6 SP5 and later. (IBM Systems
Director Server or Common Agent only)
v Technology levels and service packs for AIX 6.1 (IBM Systems Director Server or
Common Agent only)
v SUSE Linux
v Red Hat Enterprise Linux
v Cumulative PTF packages and PTF groups for IBM i (formerly i5/OS) 5.4 and
later
v Hardware Management Console systems at V7.3.3 SP2 or later
v Power Systems firmware for all systems that meet at least one of the following
criteria:
– Inband stand-alone (not managed by Hardware Management Console or
Integrated Virtualization Manager) Power Systems target systems running
AIX or Linux
Note: These systems must have the Common Agent installed.

– Out-of-band (managed by Hardware Management Console) target systems
Note: No Common Agent is required in this case because Secure Shell (SSH)
performs the update.
– Power Systems target systems managed by Integrated Virtualization Manager
and running Virtual I/O Server version 1.5.2.1-FP11.1 or later
Note: No Common Agent is required in this case because SSH performs the
update.
v Migration, fix packs, service packs, and interim fixes for Virtual I/O Server
version 1.5.2.1-FP11.1 or later
v Device driver and firmware updates, or UpdateXpress System Pack updates, for
System x servers running Linux or Windows
Notes:
– Support is provided for servers running all available agent and agentless
levels.
– Support is provided for the application of System x device driver and
firmware updates to IBM Director 5.20.x systems. This support includes IBM
Director 5.20.x versions of IBM Director Agent managed systems, IBM
Director Core Services managed agents, and Agentless managed systems.
– Support is not provided for the application of System x device driver and
firmware updates to IBM Director 5.10.x systems.
– Support is not provided for updating IMM V2 systems running IBM Director
Agent 5.x.
v IBM BladeCenter I/O Module Firmware

Notes:
– Applying IBM BladeCenter device driver and firmware updates to IBM
Director 5.20.x systems is supported.
Director 5.10.x systems is not supported.
– For these devices, inventory is provided by SNMP.
v IBM BladeCenter Management Modules, Advanced Management Modules, and
Passthrough Modules
Notes:
Director 5.20.x systems is supported.
Director 5.10.x systems is not supported.
– For these devices, inventory is provided by SNMP.
v External storage firmware, including IBM BladeCenter external storage firmware
for IBM BladeCenter S SAS RAID Controller Module and IBM BladeCenter SAS
Connectivity Module
v For the list of available System x and IBM BladeCenter systems that update
manager supports, see IBM ServerProven at www.ibm.com/servers/eserver/
serverproven/compat/us/.
Version considerations for updating IBM Director and IBM

Systems Director
The use of a configuration with mixed IBM Director 5.20 and IBM Systems
Director 6.1 or 6.2 systems is discussed here, as well as applying updates to IBM
Systems Director itself. Consider these points when applying updates to systems
that are at a level earlier than the current level of IBM Systems Director.
v You cannot use update manager to perform a migration to IBM Director 5.20
from IBM Director 5.10.
v You cannot use update manager to perform a migration to IBM Systems Director
6.x from any version of IBM Director 5.x. However, you can use agent manager
to upgrade an IBM Director Agent version 5.20 to a IBM Systems Director 6.1
Common Agent managed system.
v From IBM Systems Director 6.1, you can use update manager to update to IBM
Systems Director Server 6.1.2 and use agent manager to update to Platform
Agent 6.1.2.
v You cannot update Common Agent 6.1 to Common Agent 6.1.1, so you must
first uninstall Common Agent 6.1 and then use agent manager to install
Common Agent 6.1.1 and Platform Agent 6.1.2.
v To update to Common Agent 6.2.1, you must start with Common Agent 6.2.
v You cannot use update manager to perform a migration to IBM Systems Director
6.2 from any version of IBM Director 5.10 or 5.20. However, you can use agent
manager to upgrade IBM Director Agent version 5.20 to a IBM Systems Director
6.2 Common Agent managed system.
v IBM Systems Director supports the updating of systems that are at earlier
versions of IBM Director as long as the updates do not change the version or
release level. The following earlier version of IBM Director can be updated: IBM
Director 5.20, all modification levels.

Note: You cannot update a newer version of any IBM Director or IBM Systems
Director component to an older version of the same component. You need to first
uninstall the newer component and then install the older component.
Related tasks:
Managing agents
Managing agents
Installing agents
Update considerations for specific operating systems and

platforms
When you are installing updates for certain hardware and operating systems, there
are unique tasks to be performed and restrictions to consider.
Predefined update groups can be used to facilitate working with updates for a
particular platform or operating system.
Update considerations for AIX systems

Updating AIX systems with IBM Systems Director requires the use of Network
Installation Management (NIM) software and a Common Agent. IBM Systems
Director supports updating AIX 5.3 TL6 SP4 and later releases, as well as updating
AIX 6.1 and later releases.
Terms used for updating AIX
These are terms you will encounter when you are working with AIX updates:
Network Installation Manager (NIM) master
An AIX system that has been designated as a focal point to receive updates
and install them on other AIX systems, known as NIM clients.
Network Installation Manager (NIM) client
An AIX system that is installed from a NIM master.
Technology Level
The twice yearly AIX releases, which contain new hardware and software
features and service updates. The first of the twice yearly technology levels
is restricted to hardware features and enablement, as well as software
service. The second of the twice yearly technology levels includes
hardware features and enablement, software service, and new software
features.
Make sure that you install all parts of a technology level. Back up your
system before installing a technology level.
Service Pack
A collection of service-only updates (also known as PTFs) that are released
between Technology Levels to be grouped for easier identification. These
fixes address highly pervasive, critical, or security-related issues.
Maintenance Level
The service updates (fixes and enhancements) that are necessary to
upgrade the Base Operating System (BOS) or an optional software product
to the current release level.

Recommended level
The level of a service pack that is recommended for a given AIX
technology level. Not all technology levels have a recommended service
pack level.
Latest level
The most recent level of service pack or technology level.
Tips for updating AIX
Be aware of these tips and restrictions when you are working with AIX updates:
v Do not upgrade the AIX host operating system that IBM Systems Director Server
is running on. Doing so would break the connection between IBM Systems
Director agent and IBM Systems Director Server.
v Back up your system before installing a technology level.
v Updates can be installed only within a release of AIX. You cannot perform a
migration to a new version of AIX with update manager.
v You cannot perform a new overwrite installation of AIX with update manager.
v AIX 5.3 TL6 SP4 and later releases are supported, as well as AIX 6.1 and later
releases.
v To perform an installation or installation staging for AIX updates, your system
must adhere to the following requirements:
– Ensure that your AIX has a NIM master.
Note: During installation, IBM Systems Director automatically adds the target
AIX system as a NIM client of the NIM master.
– Ensure that your AIX has a NIM environment.
– Ensure that the AIX NIM master and the AIX managed systems (NIM clients)
contain Common Agent.
– Ensure that the NIM master is correctly initialized and configured.
– If you are updating an agentless or Platform Agent system, ensure that the
/tmp directory has full public read/write/execute permissions and enough
allotted disk space to accommodate the staged update.
v The updates will always be staged to a NIM master. IBM Systems Director
update manager creates a separate file system named /export/um_lpp_source if
it does not exist. The size is initially set to 1G, but IBM Systems Director update
manager will increase the size if the available space is not large enough to hold
the update files.
v Installation of an update that requires a license acceptance must be done
manually on the AIX target system. There are cases in which an update
contained in a technology level or a service pack can require license acceptance.
The ability to accept a license is not supported from the user interface and must
be performed by installing the file set through the System Management Interface
Tool (SMIT) interface and responding yes to the query ACCEPT new license
agreements?.
v If you plan to import updates on an AIX system, note that you can import only
those updates that contain descriptor files. Fix Central is typically the only
location from which you can obtain updates with descriptor files, so updates
obtained from the DVD might not properly import.
v Update manager cannot install AIX iFixes in the .EPKG.Z format. IBM Systems
Director can import and apply fixes on AIX only when the fix packages are

published on ECC (Electronic Customer Care) and include all supported files
such as the .sdd file. When such a fix package is available, you can install it with
the following command:
emgr -i -C package_name.epkg.Z
For more information about the emgr command and installing iFixes on AIX, see
emgr Command.
Update considerations for IBM BladeCenter I/O Modules and

Management Modules
Consider these factors when updating IBM BladeCenter I/O Modules and
Management Modules.
v You can use update manager to install updates to IBM BladeCenter, but you
cannot use update manager to uninstall or roll back IBM BladeCenter updates.
v Regarding updates to an S SAS RAID Controller Module:
– Before you can update the IBM BladeCenter S SAS RAID Controller Module,
you must discover the Storage Management Initiative Specification (SMI-S)
provider used to communicate with the module.
– The S SAS RAID R3 Controller Modules (for Linux and Windows) require
that the managed system has the following software installed:
- Platform Agent 6.3 or later
- The appropriate supported operating system:
v For the Linux module: Redhat Enterprise Linux 6.1 (32 bit) or SUSE
Linux Enterprise Server 11 SP1 (32 bit)
v For the Windows module: Windows Server 2008, Enterprise, Standard,
and Datacenter Editions R2
– On managed systems that have both SUSE Linux Enterprise Server 11 SP1 (32
bit) and the R2 module installed, updating Platform Agent from version 6.2.x
to version 6.3.3 automatically installs the R3 module. For other managed
systems, use the Install Agent wizard. For more information, see “Installing
the SMI-S provider for the IBM BladeCenter S SAS RAID Controller Module
on additional systems.”
v Before you can update out-of-band switches and IBM BladeCenter Management
Modules, you must create a configuration template for them.
v Updates to I/O modules, management modules, advanced management
modules, and pass through modules must be installed from a Trivial File
Transfer Protocol (TFTP) or File Transfer Protocol (FTP) server. Use the Settings
function to specify TFTP or FTP server properties.
Notes:
– If the staging server is an AIX system, ensure that you install the unzip
command on it if it is not already installed.
– If you use the management server as a TFTP server, ensure that port 69 on
the management server is open for inbound UDP communication.
v SNMP agents must be enabled in the IBM BladeCenter Management Module.
Otherwise, communication is not possible. You can enable this using IBM
Systems Director by creating a Management Module Network SNMP
Configuration template, and applying it to the IBM BladeCenter Management
Module.
v When creating the Management Module Network SNMP Configuration
template, the IBM BladeCenter Management Module must be configured to have
the SNMP Access Type with a value of SET, for the installation process to

succeed. Alternatively, you can use the Web-based interface for Advanced
Management Module or Management Module, under SMPv3 User Profile, to
change the Access Type to SET.
v SNMP Version 3 communication requires authentication (or credentials) as it is
more secure. When creating the Management Module Network SNMP
Configuration template, select SNMP Version 3, and fill in the appropriate
authentication settings.
v SNMP Version 3 credentials can also be obtained from the IBM BladeCenter
Management Module, if possible, when it is being unlocked. This normally
means that the privacy protocol is set to NONE for the User ID used to unlock
the IBM BladeCenter Management Module.
v SNMP credentials in the Management Module Network SNMP Configuration
template used by IBM Systems Director must match the SNMP credentials in the
IBM BladeCenter Management Module itself. Check these credentials.
Related tasks:
Installing the SMI-S provider for the BladeCenter S SAS RAID Controller
Module on additional systems
Update considerations for Hardware Management Console

systems
Hardware Management Console systems can have these items installed: updates,
upgrades, and interim fixes.
Note these restrictions and hints for working with Hardware Management Console
updates:
v Only Hardware Management Console Version 7 Release 3.3 SP2, and later
versions and releases, are supported.
v Only Virtual I/O Server Version 1.5.2.1 and later fix packs are supported.
v Hardware Management Console upgrades are not supported for the installation
staging task. If installation staging is attempted, a message is displayed with
instructions for creating and using a CD to manually perform this task.
v An ISO image is a disk image for an ISO 9660 file system, and contains the
installable files for a particular update or upgrade. A download is automatically
performed for the ISO image, and the files that are downloaded can be used for
installation on the management server. You must manually create a CD with this
ISO image and then install the update from the CD.
v Hardware Management Console upgrades are not supported for the installation
task. If you attempt an installation task, after having successfully performed a
manual installation staging task, a message is displayed with instructions for
installing the upgrades on each Hardware Management Console system. If you
attempt an installation task and installation staging has not been performed
manually, a message is displayed with the installation staging instructions using
CDs mentioned above.
v Uninstalling and rolling back Hardware Management Console updates,
upgrades, or interim fixes is not supported.
v Updating a Hardware Management Console system might remove existing CIM
indication subscriptions. To ensure that IBM Systems Director correctly registers
the CIM indication subscriptions and continues to accurately display the status
of the updated Hardware Management Console system, revoke and then
reinstate access to the system.

v Extended discovery or inventory discovery must be performed for the target
Hardware Management Console before using any Hardware Management
Console functions in update manager.
v Sometimes upgrades require that you install the media manually by storing the
obtained ISO image on a CD, for example, when there is no Hardware
Management Console update path to a new release. When a manual CD
installation is required, the upgrade ISO image must be downloaded using
update manager and stored in the
director install\data\updateslib\HMC\Update_ID
directory, where director install is the location of the IBM Systems Director
installation. Subsequently, if the Install task is chosen, installation instructions
are displayed to upgrade the Hardware Management Console manually using
the CD installation.
Update considerations for IBM i systems

Consider these factors when updating IBM i (formerly i5/OS) systems.
v Only IBM i Version 5 Release 4 and later releases are supported.
v To distribute and apply IBM i PTFs, a credential must be created authorizing the
user after IBM Systems Director has obtained access to the IBM i system. The
IBM i system must be an agentless-managed, platform-managed, or common
agent services managed system with access granted. Refer to the topic “Creating
single sign-on credentials” for instructions to create the credentials.
v Updates that are permanently installed on the system cannot be uninstalled.
v If an update requires a system restart, the administrator must perform the restart
manually. No automatic system restarts are performed for IBM i systems.
For more information about updating IBM i systems, see “Best practices for
working with updates for IBM i.”
Update considerations for Linux systems

Each Linux Distribution Partner provides updates for its specific Linux
distribution. To download updates and install them, you must have an Internet
connection and be registered with the Linux Distribution Partner.
Consider these factors when updating Linux systems.

v IBM Systems Director supports the application of updates only to Red Hat
Enterprise Linux versions 5.x and 6.x, SUSE Linux Enterprise Server 10 with any
of the applicable service packs, and SUSE Linux Enterprise Server 11.
v Only users with root authority can manage Common Agents.
v The target system must have network connectivity with the management server
and either direct or proxy connectivity with the Internet. The Internet connection
is needed to obtain the updates from the Linux Distribution Partner.
v To apply Linux updates, each system must be registered with the update server
for the appropriate Linux distribution's update service.
See these Web sites for more information:
– For Red Hat Enterprise Linux distributions, https://www.redhat.com or
https://rhn.redhat.com
– For SUSE Linux distributions, http://www.novell.com or
http://www.novell.com/customercenter
v Ensure that the following commands are installed on each system that is to
receive an update:

– zip
– gunzip
– rug (for SUSE Linux Enterprise Server 10 with the service pack)
– zypper (for SUSE Linux Enterprise Server 11)
– yum (for Red Hat Enterprise Linux versions 5.x and 6.x)
v Uninstalling updates and rolling back updates are not supported.
v The Linux system to receive updates must be a Common Agent managed
system.
v If you are updating an agentless or Platform Agent system, ensure that the /tmp
directory has full public read/write/execute permissions and enough allotted
disk space to accommodate the staged update.
Update considerations for IBM Power I/O firmware

Consider these factors when updating IBM Power I/O firmware.
v AIX is required on the target system to update IBM Power I/O firmware.
v Common Agent 6.2.1 is required on the target system to install IBM Power I/O
firmware.
v You must perform extended discovery or inventory collection for the target
system before working with IBM Power I/O firmware updates.
v If you will update a shared device, ensure that it is not used on other partitions.
v You cannot use update manager to downgrade or roll back an IBM Power I/O
firmware level.
v The IBM Systems Director Web interface allows you to select multiple criteria
values at the same time. If you select the criteria value of All, other selected
criteria values are ignored.
Update considerations for Power Systems firmware

Consider these factors when updating Power Systems firmware.
v You must perform extended discovery or inventory collection for the target
system before working with Power Systems firmware updates.
v If the target system is managed by Hardware Management Console or
Integrated Virtualization Manager, extended discovery or inventory collection
must be performed for the managing Integrated Virtualization Manager or
Hardware Management Console of the target system before using any Power
Systems firmware functions of update manager.
v For a stand-alone Power Systems server, the installation staging and installation
tasks require that the installed operating system (Linux or AIX) is available.
v The fix service provider will have only the firmware level 01SF240_338.201 for
POWER5 Power Systems firmware.
v All POWER6® firmware will be available from the fix service provider.
v Some POWER5 and POWER6 systems have BPC firmware to control each bulk
power unit in the central processor complex (CPC) and towers. This bulk power
is attached to the frame. These systems must be managed by a Hardware
Management Console. When the Power Systems firmware is updated for these
systems, the bulk power firmware might require updating as well. Update
manager for Power Systems firmware will automatically update this bulk power
firmware in this situation.
An example is if you upgrade your POWER5 or POWER6 Power Systems
firmware to a new level and that level requires an update to the bulk power

firmware. Update manager will automatically download and install this bulk
power firmware as part of the Power Systems firmware download and
installation tasks.
v Power Systems firmware updates can be obtained from www.ibm.com/support/
fixcentral/.
v Some levels of Power Systems firmware being installed on a system managed by
Hardware Management Console require that the Hardware Management
Console managing the system to be at a minimum Hardware Management
Console level. See the readme file for the Power Systems firmware. If you
attempt to update the Power Systems firmware when the Hardware
Management Console is not at the required level, the task will fail and log an
appropriate message.
v Uninstalling and rolling back Power Systems firmware updates or upgrades is
not supported.
These are the configurations supported for updating Power Systems firmware:
v Standalone POWER5 and later systems running Linux or AIX, with the Common
Agent installed
v POWER5 Power Systems and later systems managed by Hardware Management
Console and running Linux, AIX, or IBM i (formerly i5/OS)
v POWER5 Power Systems and later systems (POWER6 Power Systems, and so
on) managed by Integrated Virtualization Manager, with Virtual I/O Server
1.5.2.1 and later fix packs
Update considerations for System x systems

Consider these factors when updating System x systems.
v Before you attempt to update the firmware for a System x system, make sure
that the LAN over USB interface is enabled on the system.
v You can use update manager to install updates to System x systems, but you
cannot use update manager to uninstall or roll back System x system updates.
v System x and IBM BladeCenter firmware updates for UEFI and IMMv2, and
PBDSA firmware updates on IMMv2 systems, are available in an operating
system agnostic format. This means that you can install any of these types of
updates on any operating system that resides on a system with the applicable
machine type. To install these updates, which are not self-executable binary files,
you must use IBM UpdateXpress System Pack Installer (UXSPi). In IBM Systems
Director, ensure that the latest version of UXSPi is imported, then use the UXSPi
settings tab to view obtained operating system agnostic updates and manually
import new ones.
Note: You must also use UXSPi to run compliance checks on such System x and
IBM BladeCenter firmware updates. Ensure that the latest version of UXSPi is
imported before running compliance.
v The designated severity levels of System x system updates can dynamically
change depending on the updates that are already installed on the system. For
example, if no previous versions of an update exist on a system, the current
version of the update might have a higher level of severity than it would if a
previous version of the update existed.
Update considerations for Virtual I/O Server systems

Updating Virtual I/O Server systems with IBM Systems Director by using a
migration image requires the use of Network Installation Management (NIM)
software. The NIM server must be running AIX 6.1 or later.

A NIM master is not required when updating Virtual I/O Server systems with fix
pack, service pack, or interim fix updates.
Terms used for updating Virtual I/O Server
These are terms you will encounter when you are working with Virtual I/O Server
updates:
Network Installation Manager (NIM) master
An AIX system that has been designated as a focal point to receive updates
and install them on other Virtual I/O Server systems, known as NIM
clients.
Network Installation Manager (NIM) client
A Virtual I/O Server system that will use a NIM master for migration.
Fix pack
A fix pack updates your Virtual I/O Server release to the latest level. A fix
pack update can contain product enhancements, new functions, and fixes.
Service Pack
A Service Pack applies to only one Virtual I/O Server level. A Service Pack
contains critical fixes for issues found between fix pack releases. A Service
Pack does not update Virtual I/O Server to a new level, and it can only be
applied to the fix pack release for which it is specified.
Interim fix (iFix)
An interim fix (iFix) applies to only one Virtual I/O Server level and
provides a fix for a specific issue.
Migration image
A Migration image supports the upgrade from a Virtual I/O Server version
to a newer version.
Tips for updating Virtual I/O Server
Be aware of these tips and restrictions when you are working with Virtual I/O
Server updates:
v Only Virtual I/O Server 1.5.2.1-FP11.1 and later releases are supported.
v You cannot use IBM Systems Director update manager to perform a fresh
installation of Virtual I/O Server.
v To perform an installation or installation staging for the Virtual I/O Server
migration image, your system must meet the following requirements:
– A NIM environment is required.
– An AIX NIM master is required to migrate Virtual I/O Server to higher
release, such as from Virtual I/O Server 1.5.2.1-FP11.1 to 2.1.0.0.
– Do not update the NIM master when you are migrating Virtual I/O Server
using that NIM master.
– The operating system level for the NIM master must be AIX 6.1 or later.
v Do not migrate to Virtual I/O Server 2.1.0.0 directly from a lower version such
as 1.5.2.1-FP11.1 because Virtual I/O Server 2.1.0.0 is not officially supported by
IBM Systems Director. Install the fix pack or Service Pack for Virtual I/O Server
2.1.0.0 directly when you are migrating from a version earlier than Virtual I/O
Server 2.1.0.0. The update manager for Virtual I/O Server extension will
automatically install Virtual I/O Server 2.1.0.0 and the selected fix pack or
service pack for you.

Note: You also need a NIM environment because migrating to Virtual I/O
Server 2.1.0.0 is based on NIM operation
v If there are any LPARs managed by the Virtual I/O Server system, you must
close them before installing updates on the Virtual I/O Server system.
v Back up your system before migrating it to a higher release.
v When performing migration, the migration image will always be staged to a
NIM master. The image requires 16G of available space and will be put into a
separate file system named /export/um_lpp_source. If the file system does not
exist on the NIM master, IBM Systems Director update manager will create it. If
the file system does not have enough available space, IBM Systems Director
update manager will increase the size of the file system.
v For the installation of a fix pack, service pack, or iFix, 5G of available space is
required on the /opt file system of the target Virtual I/O Server system.
v The update manager for IBM Systems Director extension will automatically
accept the license if the update requires it.
v IBM Systems Director update manager does not support rollback for Virtual I/O
Server extensions.
v The size of some updates might exceed the file size limit of the system on which
IBM Systems Director Server is installed. Therefore, you should set the file size
limit to unlimited before proceeding. Refer to the system documentation for
information about checking and setting file size limits.
v If you distribute an update that is a migration image, the progress bar will reach
100% complete while the status is still running. The task will actually be
complete when the status is changed to Complete.
v Although the IBM Systems Director Web interface allows you to select multiple
criteria values at same time, only one of them will take effect:
– When the criteria value All is selected, other selected criteria values will be
ignored.
– When the criteria value All is not selected and the criteria value Latest
Upgrade is selected, only the latest upgrade takes effect. All other selected
criteria values will be ignored.
v Only migration tasks are staged to the NIM master. All other update tasks, such
as for firmware or fix packs, are staged directly to the managed server.
Update considerations for VMware ESXi systems

Consider these factors when updating VMware ESXi systems.
v The following firmware update types are supported when updating versions 5.0,
5.0 updates 1 and 2, 5.1, or 5.1 update 1 of either the standard VMware ESXi
(vSphere) product or an IBM customized version of VMware ESXi (vSphere):
Table 30. VMware ESXi supported firmware
Standard VMware ESXi IBM customized version of
Firmware update type (vSphere) VMware ESXi (vSphere)
Brocade N Y
Broadcom N Y
DSA Y Y
Emulex N Y
FPGA Y Y
IMM Y Y
QLogic CNA N Y

Table 30. VMware ESXi supported firmware (continued)
Standard VMware ESXi IBM customized version of
Firmware update type (vSphere) VMware ESXi (vSphere)
QLogic FC N Y
uEFI Y Y
v Updates are not supported on IBM customized VMware ESXi (vSphere) versions
4.0 or 4.1.
v To manage firmware updates for systems running standard VMware ESXi, you
must first discover and access both the OperatingSystem resource and the
related Server resource, which is, for example, an IMM.
Note: Discovering and accessing only the VMware ESXi OperatingSystem

resource will not create the correct Server resource because the OperatingSystem
resource and the Server resource are typically assigned different IP addresses.
See “Viewing system discovery results” for more information.
v To manage firmware updates for systems running the IBM customized version
of VMware ESXi, you need to discover only the OperatingSystem resource.
v Install updates to management modules from a server with SSH File Transfer
Protocol (SFTP), Trivial File Transfer Protocol (TFTP), or File Transfer Protocol
(FTP). If necessary, use the Settings function to specify TFTP or FTP server
properties.
Notes:
– If you are updating an IMM v1 system running standard VMware ESXi, TFTP
is the only supported protocol.
– If you are updating the IBM customized version of VMware ESXi, SFTP is the
only supported protocol.
v Use IBM ToolsCenter Bootable Media Creator (BoMC) or UpdateXpress System
Pack Installer (UXSPI) to update VMware ESXi versions that IBM Systems
Director does not support.
v Before updating firmware on an IBM customized version of VMware ESXi
(vSphere), ensure that you apply the latest VMware ESXi drivers and the latest
VMware ESXi IBM customized image patches to the ESXi system.
Related tasks:
Update considerations for multi-node systems

Consider these items before updating system firmware on multi-node systems.
In a multi-node system, also called a scalable system, update manager is

responsible for keeping the following four types of system firmware at the same
level on all physical servers across the system:
v DSA
v FPGA
v IMM
v UEFI
To achieve this, if any system firmware update is needed on the physical server,
update manager marks the needed relationship on the top level system, also called
the cluster system. Then, during installation, the update is applied to all the
physical servers in the multi-node system.

Consider the following items when updating the system firmware on multi-node
systems:
v Before starting any system firmware update processes, ensure that the
multi-node systems are discovered with both inband mode and OOB mode. See
Discovering a scalable BladeCenter system with multiple nodes for more
information about how to discover multi-node systems.
v When checking compliance, the system firmware is shown on the cluster
manageable endpoint of the multi-node system instead of on the physical server
system.
v The systems firmware updates are installed to all the physical server systems
when you install the update on the multi-node system. All the partition systems
are then rebooted after the installation.
Related tasks:
Discovering scalable systems that have multiple nodes
Determining the installed IBM Systems Director version

Before you update an installation of IBM Systems Director, determine the version
of the IBM Systems Director Server or agent that is installed.
To determine the installed version of IBM Systems Director Server:

v Console: Check the version number of the IBM Systems Director Server
managers on the Home page.
v CLI: Run the smcli lsver command.
To determine the installed version of IBM Systems Director agent:

v From IBM Systems Director Server:
– Console: Check the version number in the Agent MEP properties.
– CLI: Run the smcli lssys command, with the ManagementSoftware attribute.
For example: smcli lssys -A ManagementSoftware -i 9.22.103.245.
v (AIX only) From the IBM Systems Director agent:
– CLI: Run the lsagent.agent command.
Note: Maintenance is not delivered for every manager at each update or patch. For
example, the update for a particular version might be released for automation
manager without the release of a corresponding update for configuration manager.
Related tasks:
Planning to update
Updating the product
Related reference:
lssys command
lsver command
Starting to monitor and update systems

To monitor and update systems, you must set up update manager correctly,
including choosing the systems to monitor. You must also ensure that an Acquire
updates task is run on a recurring basis, and that someone is periodically checking
systems that have compliance issues. Lastly, you must install needed updates.

For systems that are to be monitored for update management and compliance
status, you must:
v Make sure that the systems are discovered and accessible.
v Collect inventory on the systems. Most update manager methods cannot
determine the applicability of updates to a system unless inventory was
previously collected on the system.
Tip: Use the IBM Systems Director Pre-Install Utility to scan systems and identify
potential problems that could prevent IBM Systems Director from updating
successfully.
Tip: To protect your system in the event of an unforeseen complication, ensure

that you back up your data before performing any update tasks.
1. From the Plug-ins tab on the IBM Systems Director Web interface Home page,
click Update Manager. The update manager summary page is displayed.
2. Click the Optional: Getting started link and complete the Getting Started
wizard. See “Getting started with updates” for more information.
3. Click the Configure settings link and complete the Settings task. See
“Changing update settings” for more information.
4. Optional: Create additional update groups to facilitate update management. See
“Managing update groups” for more information.
5. Acquire and install updates for the product or system that you want to update:
If you want to simply update IBM Systems Director, use “Update IBM
Systems Director” to let update manager take most defaults and run
most update tasks for you automatically. See “Updating IBM Systems
Director” for more information.
Update other systems
If you want to update other systems, or if you want to update IBM
Systems Director but have full control over the whole process, use the
various update manager tasks in the IBM Systems Director Web
interface or the installneeded command to update your systems. See
“Acquiring and installing updates” for more information.
6. Schedule an Acquire updates task to run periodically, at least once a week. See
“Acquiring new updates” for more information.
7. Review the Update Compliance section of the update manager summary page
to check if your systems meet your update specifications. See “Keeping systems
in compliance” for more information.
8. If some systems need updates, review the exact compliance issues and address
them by planning to install the needed updates.
9. Periodically, perform Steps 7 and 8, or create an Event Automation Plan to
perform this task and notify you of any systems that are in need of updates.
See “Creating an event automation plan” for more information.

Related tasks:
Configuring update manager
Acquiring and installing updates
Keeping systems in compliance
Managing update groups

Related reference:
Pre-Installation Utility

Before starting to manage updates, run the Settings function and the optional
Getting Started With Updates wizard to customize your configuration.
To specify settings, go to the Update Manager summary page, click Configure

settings and complete the various tabs for your configuration.
Then, use the optional Getting Started With Updates wizard to accomplish the
following tasks:
v Select a set of systems to monitor with compliance policies
v Create update groups for updates that are appropriate to the selected systems
v Configure Internet connectivity
v Run or schedule a check for updates
To run the Getting Started With Updates wizard, complete the following steps:
1. On the Update Manager summary page, click Optional: Getting started. The
Getting Started With Updates wizard displays a welcome panel.
2. Optional: If you do not want to see the Welcome page next time, clear Show
the welcome page next time.
3. Click Next. The Name and Description page is displayed.
4. Type a name and optional description for the update group that is to be
created. This group is initially empty but will acquire the updates for the
systems that were selected. It is also attached to these systems through a
compliance policy. Update manager will monitor the systems and indicate
when a system is missing a needed update from the group.
5. Click Next. The Systems page is displayed.
6. Optional: The IBM Systems Director Server is selected by default. Select it and
click Remove if you do not want monitoring of this system.
7. Select at least one system, which must be accessible, and click Add. These
systems will be automatically associated with an update group through
system compliance policies. If a selected system cannot be monitored, an error
message is displayed.
8. Click Next. The Connection page is displayed.
9. Indicate how the Internet is to be accessed to acquire updates:
v Click Use direct connection if a direct Internet connection exists and you
want it used.

v Click Use Proxy server if your proxy server requires authentication. A
proxy can be an HTTP proxy or a Hypertext Transfer Protocol Secure
(HTTPS) proxy, and must be configured and made available by your
organization.
a. Type the host name and port number of the proxy server.
b. Click Authenticate using the following credentials if you want to
access the proxy server with a user ID and password. Type the user ID
and password for the proxy server.
Note: To acquire updates, the IBM Systems Director Server must have Internet
connection or through a Hypertext Transfer Protocol (HTTP) proxy. If an IPv4
connection is unavailable, updates can be imported.
10. Optional: Click Test Connection if you want to test the connection settings
that you have specified.
12. This page lists the types of updates that will be added to the update group to
monitor the selected systems, and when a check for updates is run. Verify the
information on this page:
v If the information is correct, click Finish. The common launch-task window
is displayed to schedule an acquire updates for the selected systems.
Schedule this task to run on a recurring basis, not just once.
v If the information is incorrect, click Back to return to previous pages and
correct the information.
13. Specify notification and schedule settings for the task that is being launched.
In addition to launching a check for updates task, the wizard creates an
update group using the default update criteria for the systems that were
selected. A compliance check is created for each selected system to ensure that
it complies with this newly created group.
Related concepts:
Updates and applicable resources
Update considerations for specific operating systems and platforms
Compliance policies
Related tasks:
Navigating tables
Navigating tables
Related reference:
Update types
Updating IBM Systems Director

Use “Update IBM Systems Director” in the IBM Systems Director Web interface to
automatically obtain and install all types of updates for IBM Systems Director.
Consider these points when updating IBM Systems Director:

v Most update manager methods cannot determine the applicability of updates to
a system unless inventory was previously collected on the system.
v You must restart IBM Systems Director to activate installed updates.

To instruct update manager to take most defaults and update IBM Systems
Director almost automatically, complete the following steps.
Attention: Use this method instead of other methods, such as the Acquire
updates" method, to update IBM Systems Director. Other methods might allow you
to install only a partial set of updates, which can cause damage to the installed
image and prevent you from starting IBM Systems Director. Even if it does start,
you might find that not all required plug-ins are present, which could result in
undefined or unknown behavior of the updated image.
1. From the IBM Systems Director Web interface Home page, click Update IBM
Systems Director. When the acquire updates task completes, the updates
needed by the IBM Systems Director Server are displayed in the table.
2. Optional: If your management server does not have an IPv4 connection to the
Internet, you can download IBM Systems Director updates and then use update
manager to import and install the updates.copy the updates to the management
node. See “Updating without an Internet connection” for more information.
3. Click Download and Install to run or schedule the update.
4. After the installation is complete, restart IBM Systems Director to activate the
updates.
Related concepts:
Version considerations
Related tasks:
Disk space requirements for applying updates

Determining the installed version
Restarting the product

Related reference:
Update types
installneeded command
Updating without an Internet connection

If the management server does not have an Internet connection, you can manually
download IBM Systems Director update packages. After an update package has
been downloaded and extracted, you can use update manager to schedule when to
import and install the updates.
1. Download the necessary fix files from Fix Central. See “Getting fixes from Fix
Central” for more information.
2. Import and install the updates using either the command line or the IBM
Systems Director Web interface:
Command line
Run the following command to import and install the updates:
smcli installneeded -v -F /home/USERID
IBM Systems Director Web interface
Complete the following steps to import and install the updates:
a. From the IBM Systems Director Web interface Home page, click
Update IBM Systems Director.
b. On the Update IBM Systems Director page, click Stop to stop the
task that checks for new updates and instead display options for
downloading and importing updates.
c. In the Path field, either type the full local directory path and file
name of the downloaded update package zip file, or click Browse...
to manually search for and locate the file and then have the path
information entered into the field for you.
d. Click Import and Install to run or schedule the import and
installation of the updates.
3. After the installation is complete, restart IBM Systems Director to activate the
updates.
Related tasks:
Getting fixes from Fix Central

Downloading manual updates
Related reference:
Fix Central
Acquiring and installing updates

Use IBM Systems Director Web interface tasks or the installneeded command to
update your systems with update manager.
Note: If you are updating IBM Systems Director itself, see “Updating IBM Systems
Director”.
Tip: To download updates for multiple System x systems or all updates for a
given System x system, you can instead use UpdateXpress System Pack Installer.
See the readme that is included with the UpdateXpress System Pack Installer at
www.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-
XPRESS for further information and a link to the user guide.

Related concepts:
Related tasks:


Related reference:
Update types
Acquiring and installing updates with the IBM Systems

Director Web interface
Use the update manager tasks in the IBM Systems Director Web interface to
acquire updates, stage your installation, manage update groups, and install
updates on your systems.
Showing needed updates

Use the Show and install updates function to identify updates that are needed by
your systems.
This function does not show information for systems for which you have not
collected inventory.
This function can be used on systems or system groups. If you select a system
group, this task will display only those systems within the group that are in need
of updates.
The list of needed updates is produced by comparing the updates that IBM
Systems Director has knowledge of to the inventory on your systems. This task
does not list as needed any update that IBM Systems Director does not know
about. An important part of keeping your systems up-to-date is running the Show
needed updates function and reviewing the results.
To see a list of updates needed by a system, complete the following steps:

1. From the Update Manager summary page, locate the Updates section.
2. Click Show and install updates. The Show and install updates page is
displayed.
3. Select a system or system group in the Selected systems field. Click Browse to
see a list of systems to choose from.
4. Click Show and install updates. A table of needed updates is displayed.
5. Examine the table. There is one line for each update and details about the
update.

Notes:
v If you do not see an update that you expected to see, you can view all
updates that are available for installation on a system by selecting Show all
installable updates.
v Certain listed updates, for example UpdateXpress System Pack updates for a
IBM BladeCenter blade server or chassis, are actually update collections that
contain one or more member updates that are combined into one installable
image. To view the member updates within the update collection, right-click
on the update collection and select “Update”. For more information, see your
product documentation.
Update tasks such as Install can be done from this page by clicking Actions and
selecting an available task.
Related concepts:
The update topology perspective
Update relationships
Compliance policies
Related tasks:
Viewing update details
Navigating tables
Navigating tables
Related reference:
Showing all installable updates

Use the Show all installable updates function to identify all updates that are
available for installation on your systems.
This function does not show information for systems for which you have not
collected inventory.
This function can be used on systems or system groups. If you select a system
group, this task will display only those systems within the group that have
updates that are available for installation.
The list of all installable updates is produced by comparing the updates that IBM
Systems Director has knowledge of to the inventory on your systems. This task
does not list as installable any update that IBM Systems Director does not know
about.
To see a list of all updates that are available for installation on a system, complete
2. Click Show and install updates. The Show and install updates page is
displayed.
3. From the Show and install updates page, click Show all installable updates.
The Show All Installable Updates page is displayed.

update.
Update tasks such as Install can be done from this page by clicking Actions and
Related concepts:
Compliance policies
Related tasks:
Navigating tables
Navigating tables
Showing installed updates

Use the Show installed updates function to determine which updates are installed
on a particular system. This task shows those updates that were installed by IBM
Systems Director. Updates installed by other means are not displayed.
This function does not show information for systems whose inventory you have
not collected.
Update tasks such as Uninstall can be done from this page by clicking Actions and
To change which update properties are displayed on the table, their position in the
table, or the field sizes, click Actions > Columns.
To see a list of updates installed on a particular system, complete the following

steps:
1. From the Update Manager summary page, click Show installed updates. The
Show Installed Updates page is displayed.
3. Click Show Installed Updates. A table of installed updates is displayed.
update.

Related concepts:
Compliance policies
Related tasks:
Navigating tables
Navigating tables
Checking for new updates

Use the Acquire updates task to periodically load new updates into update
manager. Schedule a check for updates task to run frequently, at least once a week.
Note: To check for updates, the IBM Systems Director Server must have Internet
connection or through a Hypertext Transfer Protocol (HTTP) proxy. If an IPv4
connection is unavailable, updates can be imported.
To check for new updates, complete the following steps:

1. Select Acquire updates from the Updates section of the Update Manager
summary page. The Acquire updates page is displayed.
2. Select the option to check for new updates.
3. Select the types of updates for which you want to check.
4. Optional: Click Remove to remove any entries that have been selected in
error.
5. Click OK. A scheduling task is displayed
6. Optional: Type a job name.
7. Choose when to run the job:
v Click Run Now to run the job right away.
v Click Schedule and choose a date and time for the check for updates, as
well as the Repeat Options for running the task.
You are advised to schedule a repeating task, because it ensures that you
are aware of new updates as they become available. You are also advised to
choose a time when system load is light, so that the job will complete
quickly.
8. Click Notifications and enter notification options.
9. Click Options and enter other options.
10. Click OK.
11. If any new updates are found, update manager will be automatically made
aware of them. Examine any static update groups that you have created to see
if the new updates must be added.
This is an alternative, system-based approach. Go to the Resource Explorer area

and select a system or system group. Click Actions > Release Management >
Acquire Updates. This will scope the check for updates to just that type of system
or systems in the group.

Related concepts:
Compliance policies
Related tasks:
Related reference:
Update types
checkupd command
Update types:
The various operating systems and firmware that can be updated by IBM Systems
Director have unique update types. The update type is used when a check for
updates is scheduled, or when a compliance policy is created for a system.
Update types for AIX:
These update types are used for AIX systems.

All Request a specific Technology Level or Service Pack. This choice copies all
the technology level and service pack metadata to the management server.
Update to recommended level
Update to the recommended service pack level. When an AIX system is
chosen from the Getting Started wizard, this type is the default value. If
the newest technology level does not have a recommended service pack,
the AIX system will be updated to the newest technology level that does
have a recommended service pack.
Update to latest level
Remain on the same technology level, but update to the latest service pack
level.
Upgrade to recommended level
Upgrade the technology level to the recommended level. This is likely to
upgrade AIX to a new service pack on the new technology level.
Upgrade to latest level
Upgrade the technology level to the latest level. Typically, AIX is updated
to a new service pack on the new technology level.
Update types for System x servers and chassis:
These are the update types for System x servers and chassis.
System x servers and chassis

Categories
ASR Driver
Automatic Server Restart Driver
BIOS System BIOS updates
BMC/H8
BMC/H8 Updates
CD ROM / DVD
Chipset-INF
Server Chipset Device Drivers/INF files
Diagnostics
Diagnostic flash updates
Fibre Fibre Channel updates
Hard Disk Drive
Hard disk drive firmware updates
Hot Plug
Active PCI Device Driver updates
iSCSI Internet SCSI updates
Network
Network Device Driver and firmware updates
PLD Code
CPLD and FPGA firmware updates
RSA RSA Firmware updates
RSA II
RSA II firmware updates
SAS Serial Attached SCSI updates
SATA Serial Advanced Technology Attachment (SATA) updates
SCSI Small Compute Systems Interface (SCSI) updates
ServeRAID
ServeRAID updates
Service Pack Driver
Service Processor (including RSA and RSA II) Device Driver
updates
Tape Tape Drive firmware updates
UXSP UpdateXpress System Pack
Note: On a IBM BladeCenter blade server or chassis, UpdateXpress

System Pack updates are actually update collections that contain
one or more member updates combined into one installable image.
For more information about UpdateXpress System Packs, see
http://publib.boulder.ibm.com/infocenter/toolsctr/v1r0/index.jsp.
Video Video Device Driver updates
Severity
Initial Release
Critical
Suggested
Non-Critical
Note: The designated severity levels of System x system updates can

dynamically change depending on the updates that are already installed on
the system. For example, if no previous versions of an update exist on a
system, the current version of the update might have a higher level of
severity than it would if a previous version of the update existed.

When chosen from the Getting Started wizard, all System x updates are selected by
default.
Update types for Hardware Management Console:
These are the update types for Hardware Management Console systems.
All Used to request all updates.
Remain on the same version and release, but update to the recommended
modification level. This is the default when a Hardware Management
Console system is chosen from the Getting Started wizard.
Remain on the same version and release, but update to the latest
modification level.
Upgrade the version and release to the recommended level.
Upgrade the release to the latest level within the current version. For
example, if you are currently at V7R3.3.0M0 and you request Upgrade to
latest level, you might get an update to V7R4.0.0M0, but you will not get
one for V8.
Update types for IBM Systems Director and IBM Director:
These are the update types for IBM Systems Director and IBM Director.
5.20 IBM Director 5.20.x
6.1 IBM Systems Director 6.1.x
Update types for IBM i systems:
These are the update types for IBM i (formerly i5/OS) systems.
PTF Groups
Operating System PTF Groups
Include IBM DB2 UDB, High Impact or Pervasive and other PTF
Groups. The list of PTF groups varies depending on the IBM i
version being updated.
IBM WebSphere® Application Server PTF Groups
Includes updates for IBM WebSphere Application Server products
supported by IBM i. The list of PTF groups varies depending on
the IBM i version being updated.
Update types for Linux:
These are the update types for Linux systems.

Red Hat EL

Security
Fixes to defects that have the potential to compromise system,
network, or user security. They are categorized according to their
severity:
v Critical
v Important
v Moderate
v Low
Bug Fixes
Fixes to defects that do not compromise system, network, or user
security.
Enhancements
New features
Novell SUSE Linux Enterprise Server
Category
v Recommended
v Optional
v Security
Update types for IBM Power I/O firmware:
These are the update types for IBM Power I/O firmware.
modification level.
Update types for Power Systems firmware:
These are the update types for Power Systems firmware.

Remain on the same version and release, but update to the recommended
modification level. This is the default choice when Power Systems
firmware is chosen from the Getting Started wizard.
modification level.
Upgrade the version and release to the recommended level.
Upgrade the version and release to the latest level.
Update types for Virtual I/O Server systems:
These update types are used for Virtual I/O Server systems.
All Request all updates on FSP, including migration, fix packs, service packs,
and interim fixes.

Latest Update
Remain on the same release, but update to the latest fix pack, service pack
level, and interim fix.
Latest Upgrade
Request the latest release of Virtual I/O Server and the most current
interim fix on the latest release. When a Virtual I/O Server system is
chosen from the Getting Started wizard, this type is the default value.
Downloading updates
While the download of updates happens automatically as needed, you might want
to download updates when it is most convenient for your network, and to ensure
that the updates are available at the time of installation.
You can choose to download the installable files for the update to the management
server if you have interest in installing the update, and want to make the
installation process run faster when it is scheduled. Downloading the updates
ahead of installation ensures that the valuable time allocated for system
maintenance (when typically systems are not available to the users) is not spent on
tasks such as downloading, which does not require exclusive system access.
You are not required to run the download task. If the installable files for the
update have not been downloaded when the installation task is scheduled, the
download task is automatically be invoked before the installation task.

the time that a task using the groups is scheduled. The membership of the update
To download updates, complete the following steps:

1. From any panel where a list of updates is present, click Actions > Download.
2. You will see a summary panel explaining which updates are to be downloaded
to the management server. Click OK.
3. The task scheduler is displayed. Choose to either run the download now or
schedule it for later.
4. When the download task is used on a selection of updates that must be
manually downloaded, a message is issued stating that not all the updates can
be automatically downloaded. You can click Download manually to display
the manual download page. Follow the instructions on that page to complete
this process.
Related tasks:
Navigating tables
Navigating tables
Related reference:
importupd command
Downloading manual updates:
Some updates must be downloaded manually. An example of an update that

requires a manual download is an update that requires a licensing agreement.
There might be some updates that cannot be automatically downloaded due to

licensing restrictions. In this case, the downloaded column for the update will

contain the text No, manual download. When you try to download this type of
update, you will see instructions for a manual download.
When you select the download task on an update menu, a panel is displayed to
guide you through visiting the appropriate Web site, downloading the update, and
then copying the installable files for the update.
To perform a manual download of an update, complete the following steps:

1. From the update menu page, select Actions > Download. A panel with
instructions for each manual download is displayed.
2. Select one update and click Actions > Download. This launches a Web browser
to the appropriate Web site for downloading the installable files for the update.
3. If a licensing agreement is displayed, read it and any other information
presented to you. Accept the licensing agreement if you want to continue.
4. The download retrieves the installable files for the update. Make a note of their
location.
5. Close the browser for the download link. You will return to the Download
Updates page.
6. Put the location of the update installable files (from Step 4) in the Files to
import field.
7. Optional: Click Browse to browse the directory.
8. Repeat this step for each update that requires a manual download.
9. Click OK to import the updates you have downloaded.
After an update has been manually downloaded, it can be managed the same way
as any other update.
Related tasks:
Updating without an Internet connection
Importing updates
Use the Acquire updates import function to copy one or more updates from a
directory on the management server to the update library.
To import updates, complete the following steps:

1. From the Update Manger summary page, locate the Updates section.
2. Click Acquire updates.
3. Select the option to import updates.
4. In the Path field, either type the full directory path that contains the update
files on the management server, or click Browse... to manually search for and
locate the directory and then have the path information entered into the field
for you.
Notes:
v On Windows, the specified path must point to a local directory. You cannot
specify network mounted directories.
v You cannot select specific updates from the target directory. All eligible
updates found within the directory are copied to the update library.
v You can import only those updates that contain descriptor files. Fix Central is
typically the only location from which you can obtain updates with
descriptor files, so updates obtained from the DVD might not properly
import.

5. Click OK. The scheduler is displayed. You can then choose to run the task now
or to schedule it to run in the future.
Related reference:
importupd command
Exporting updates
Use the Export function to copy updates from the update library to a target
directory on the management server. The target directory must be accessible to the
management server.
To export updates, complete these steps:

1. From any list of updates, select the ones that you want to export.
2. Click Actions > Export updates.
3. Specify a location for the update files by typing or browsing for the path name
on the management server in the Path field.
4. Click OK. The scheduler is displayed. You can then choose to run the task now
or schedule it to run in the future.
Related reference:
lsupd command
Using the System x and IBM BladeCenter platform configuration

file to acquire updates to systems that are outside of your
environment
Use this procedure only in situations where the normal update tasks cannot be
performed. Customize the System x and IBM BladeCenter platform configuration
file so that you can acquire updates for systems that you have not discovered or
for which you have not collected inventory using IBM Systems Director.
To modify the System x and IBM BladeCenter platform configuration file for a
particular System x or IBM BladeCenter system, complete the following steps:
1. Open the file in a text editor. The System x and IBM BladeCenter platform
configuration file is named director install/data/xbc_platforms.cfg where director
install is the directory in which IBM Systems Director has been installed.
2. Using the guidelines in the file itself, add the machine type, operating system,
and architecture combination for the system that you want to manage.
3. Save the file.
Now this system will be listed by update manager and update tasks can be
performed for this system.
Related concepts:
The System x and BladeCenter platform configuration file
Related reference:
Sample System x and BladeCenter platform configuration file
The System x and IBM BladeCenter platform configuration file:
You can use a System x and IBM BladeCenter platform configuration file to specify
systems that you have not yet discovered or for which you have not yet collected
inventory with IBM Systems Director. This file is then used to perform update
tasks on the systems listed in the file.

This capability applies to System x and IBM BladeCenter systems. A blank System
x and IBM BladeCenter platform configuration file is created automatically on the
management server the first time that any System x or IBM BladeCenter update
criterion is displayed. You can customize this file for systems that have not been
discovered by IBM Systems Director so that their updates can be downloaded.
The System x and IBM BladeCenter platform configuration file has this name:
director install/data/xbc_platforms.cfg
where director install is the directory in which IBM Systems Director has been
installed.
System x and IBM BladeCenter platform configuration file format
In the System x and IBM BladeCenter platform configuration file, each entry is on
a separate line The file has these fields, separated by commas:
Machine type
The 4-digit machine type of the System x or IBM BladeCenter server.
Operating system
The operating system running on the System x or IBM BladeCenter server.
Architecture
The architecture of the operating system. This value will typically match
the architecture of the server, although it is possible to run 32-bit Windows
on an EM64T-based Server.
Attention: The values that you specify for Operating system and Architecture are
case sensitive. For these two fields, use an example entry as a basis for a new entry
to avoid errors.
Tasks used with the System x and IBM BladeCenter platform configuration file
Use the System x and IBM BladeCenter platform configuration file to select the
machine type and operating system criteria for an update group, or to control the
acquire updates task. For each of these update manager tasks, consider these
points:
Acquire updates (selected from the Update Manager summary)
If the System x and IBM BladeCenter platform configuration file contains
machine type and operating system entries, the Acquire updates panel will
display these values. You can use them as you would any other selection
on this page.
If an entry in the System x and IBM BladeCenter platform configuration
file contains a wildcard, all values that match the wildcard will be selected
when this entry is selected.
Acquire Updates (selected in the context of a system and then choosing Custom)
The System x and IBM BladeCenter platform configuration file is not
needed because the machine type and operating system information is
provided by the selected system.
Create an update group
The values in the System x and IBM BladeCenter platform configuration
file are displayed when you are creating update groups. Create a dynamic

update group and choose the entries from the System x and IBM
BladeCenter platform configuration file that you are interested in.
Sample System x and IBM BladeCenter platform configuration file:
This sample file can be used to download updates for systems that are not present
in your environment.
The entries are commented out. Remove the number sign (#) for each entry that
you want to use.
#Machine Type, Operating System, Architecture

#Operating System Choices:
#RHEL 3
#RHEL 4
#RHEL 5
#SLES 8
#SLES 9
#SLES 10
#AIX
#Windows 2000
#Windows 2003
#Windows XP
#Windows Vista
#Architecture Choices:
#blank indicates i386 or x86
#x64
#ppc
#For Out-of-Band updates specify NONE for both
#Operating System and Architecture
#Examples:
#8843,RHEL 3,
#8843,RHEL 3,x64
#8843,RHEL 4,
#8843,RHEL 4,x64
#8843,RHEL 5,
#8843,RHEL 5,x64
#8843,SLES 8,
#8843,SLES 8,x64
#8843,SLES 9,
#8843,SLES 9,x64
#8843,SLES 10,
#8843,SLES 10,x64
#8843,Windows 2000,
#8843,Windows 2003,
#8843,Windows 2003,x64
#8843,Windows XP,
#8843,Windows XP,x64
#8843,Windows Vista,
#8843,Windows Vista,x64
#8842,RHEL 3,ppc
#8842,RHEL 4,ppc
#8842,RHEL 5,ppc
#8842,SLES 8,ppc
#8842,SLES 9,ppc

#8842,SLES 10,ppc
#8842,AIX,ppc
#8852,NONE,NONE
Installation staging
Use installation staging to copy the files that comprise an update to an appropriate
location for eventual installation. That location might not be the system that the
update is to be installed on. This task is not required. If you skip this step, the
update is staged when it is needed. This task is provided to save time during
installation maintenance windows, in order to minimize system downtime and
unavailability.
The task of installation staging is accomplished by running the Installation staging

wizard on an update. The Installation staging wizard guides you through the task
of copying the installable files for an update from the management server to an
appropriate location for eventual installation.
If the installable files for an update have not been previously downloaded, a
download is run before the installation staging is performed.

To perform an installation staging for an update, complete the following steps:

1. Click Actions > Installation staging on the menus for an update or update
group. The page of the Installation staging wizard is displayed.
2. Clear the Show this welcome page next time box if you do not want to see
the Welcome page again.
3. Click Next. The Updates page is displayed. The Updates page is skipped if
the Installation staging wizard was invoked from an update or update group.
In this case, proceed to Step 5.
4. Select each update that you want. If an update that is part of an update
collection is chosen, a warning is issued because it is advisable to install the
update collection as a whole.
5. If you select updates that require a manual download, these updates cannot
be staged until you manually download them. The Downloads required panel
will be displayed.
a. Click Details to manually download updates.
b. Click Continue, the updates are now downloaded and ready when you
have completed the manual download.
c. Click Skip the updates which must be manually downloaded if you do
not want to manually download these updates, or the process has failed
for one or more of them. Those updates will be removed from the list and
will not be staged.
d. Click Next The Systems page is displayed.
6. You can stage updates for installation by selecting the systems or system
groups that the updates are to be installed on. Select the system or system
group name and click Add
Be aware that if you selected system groups, the list of individual systems in
these groups is not determined until the task runs. You are presented options
only for those systems that were individually selected. Group membership is
not determined until the task runs.

7. If some of the updates are for AIX or IBM BladeCenter systems, and you had
not already specified the necessary AIX or IBM BladeCenter options on the
Settings page, it is displayed so that you can choose these options.
8. Click Next. The Options page is displayed.
9. If you do not want updates that are required for the installation of the
selected updates to also be staged for installation, clear Automatically stage
missing required updates. Clearing this box is not advised. Missing
mandatory updates will cause the installation task to fail.
10. A table of the known update requirements for each selected update is
displayed.
a. Select a system from the list of systems to see its update requirements.
b. Review the required updates that will be installed when Automatically
stage missing required updates is selected. You cannot edit the required
updates here.
12. Review the information on this page.
v If it is correct, click Finish. A panel is displayed for you to specify
notification and schedule settings for the installation staging task being
launched by this wizard.
v If some information is incorrect, click Back to go to previous pages and
correct the information, or click Cancel to cancel the entire process.
After the installation staging task completes, the updates are staged in the
following locations:
v When staging to AIX, IBM i, and Linux systems, updates are staged to
/tmp/updatemanager/staging in all cases.
v When staging to Windows systems, updates are usually staged to
TEMP\updatemanager\staging, where TEMP usually resolves to C:\WINDOWS\TEMP
but can change depending on the resource type to which you are staging.
Note: To ensure that updates are staged to the Windows TEMP directory, specify
RELOAD_STAGING_LOCATION=true in the install_path\IBM\Director\lwi\
runtime\core\workspace\.metadata\.plugins\
com.ibm.director.mgr.updates.server\update.properties file.
To determine the exact staging path for a particular system, see the related entry in
the job log. To verify that the path has sufficient space, explicitly stage an update
to the target system and then verify the staging at that path.
Related tasks:
Navigating tables
Navigating tables
Related reference:
installupd command
Viewing information about updates

Information about updates and updates groups is often needed to decide whether
to install the update.

Related concepts:
Update groups
Related reference:
lsupd command
The update topology perspective:
The Updates topology perspective displays a topology view tailored to the

system's update-related resources.
From any place within update manager where you can display a system, click
Actions > Topology Perspectives.
By default, a topology perspective contains all resources related to the system. The
Updates perspective limits the resource types to update-related resources that are
installed on, needed by, or applicable to the system. The following resources types
are included in the Updates perspective:
v systems
v updates
v update collections
Click the displayed resources to see the relationships displayed in the Properties
table.
Relationships for updates and update collections:
Update relationships indicate how an update relates to other updates and target
systems. The Topology view is a good way to illustrate update relationships.
This is a list of all update relationships. To simplify this discussion, the term
'update' refers to either an individual update or an update collection, unless
otherwise noted.
appliesTo
Indicates systems that an update can be installed on at this time. You can
view updates that can be installed on a system by navigating the appliesTo
relationship from the system's Related Resources submenu.
federates
Specifies the individual updates that are contained in an update collection.
installedOn
Indicates systems where the update is currently installed. You can view
where a specific update is installed by following the installedOn
relationship from the update's context menu.
This displays the systems where the update is installed using a table view.
This table view can be switched to a topology map to display a graphical
layout instead of a topology. In the topology map, the installed on
relationships between the updates and the systems are displayed.
needs Indicates updates that a system needs.

Several updates might applyTo a system, but the system might only need
one of those updates. An example is the situation where one update
supersedes another.
You can see where an update is needed for installation by following its
needs relationship using the resource navigator.
When an update is acquired, the needs and appliesTo relationships for the
update and affected systems are automatically synchronized so that the
new update can be properly managed, and compliance policies remain
accurate.
This table view can be switched to a topology map to display a graphical
layout instead of a topology. In the topology map, the needs relationships
between the updates and the systems are displayed.
requires
Indicates that this update requires another update to be installed.
supersedes
Indicates that this update supersedes another update, meaning that the
other update is not needed if this one is installed.
Viewing properties, documentation, requirements, and other details for an

update:
You can obtain details about an update, such as general properties, installation
requirements, installable files, and documentation.
If an update has not been downloaded and you attempt to view the contents of an
associated documentation file, the download task will be run so that the files can
be read.
To view properties and documentation for an update, complete the following steps:
1. From any place where an update is displayed, click the update name. A page of
general information about the update is displayed, including: name, ID, size,
version, and so on.
2. Click the General tab to see general information about the update.
In this list, the term 'update' is used to refer to an update or update group.
Note: Certain listed updates, for example UpdateXpress System Pack updates
for a IBM BladeCenter blade server or chassis, are actually update collections
that contain one or more member updates that are combined into one
installable image. To view the member updates within the update collection,
right-click on the update collection and select “Update”. For more information,
see your product documentation.
Name The name of the update.
Description
A description of the update.
Acquired Date
The date that this update was acquired by update manager.
Build Date
The date that the update was built. An example is the date that the
source for the update was compiled.

Build Number
The build number of the update.
Category
The category of update.
Downloaded
Whether the update has been downloaded to the management server.
Filenames
The names of the files for the update.
Package Type
The package type of the update.
Platform
The hardware platform that the update applies to.
Product
The name of the product that the update applies to.
Restart Type
Whether a restart is required when the update is installed or
uninstalled, and what type of restart is required.
These are the possible values:
Restart immediately after update is installed
The restart must be performed before other updates can be
installed or uninstalled.
Restart after all updates are installed
The restart can be performed at the end of the install or
uninstall task.
None There is no restart indicated for the system or resource.
Severity
The severity of the update is one of the following values:
v Critical
v High
v Normal
v Low
v Not Applicable
Note: The designated severity levels of System x system updates can

dynamically change depending on the updates that are already
installed on the system. For example, if no previous versions of an
update exist on a system, the current version of the update might have
a higher level of severity than it would if a previous version of the
update existed.
Software ID
A character string or value that identifies the software or firmware that
needs the update.
Superseded
Whether this update has been superseded by another.
Total Size
The total size of all the update's files.

Uninstallable
Whether the update can be uninstalled.
Update ID
A unique identifier for the update.
Update Type
Whether the update is an individual update or an update collection.
Vendor
The manufacturer of the update.
Version
The software or firmware version that the update applies to.
3. Click the Documentation tab. A page of documentation files is displayed. Some
updates might not have documentation files.
4. Click the Requirements tab. A page of requirements that must be met in order
for the update to be installed is displayed. The type of information depends on
which software component is being updated, such as applicable operating
systems and levels.
5. Close this page by clicking the X on the page tab.
Related concepts:
Related tasks:
Viewing required updates
Viewing parent update collections
Viewing the supersede relationships for an update
Related reference:
lsupd command
Searching update documentation:
If there is a specific area of concern or detail that you are looking for, searching
update documentation can point you to the updates that you are most interested
in.
Only the latest documentation for an update in its supersede chain is displayed. If
you have a situation where update A supersedes update B, the documentation for
update A is displayed rather than the documentation for update B, since update A
is the most recent update in the supersede chain.
The Update Manager summary page contains a search field that searches the
documentation files of updates that are available for management. The search is
limited to updates that have been downloaded to the management server. For each
update, only those files that are human readable are available for searching.
To search update documentation, complete the following steps:

1. From the Update Manager summary page, locate the Search section.
2. In the Search local updates field, type the terms you want to search for.
3. Click Search. Search results are displayed in a separate table, sorted by
closeness to the search terms. Search results are not case-sensitive.

4. Optional: You can do various tasks from the search results page, such as
installing an update, viewing the properties, or adding it to an update group.
5. If you do not find what you are looking for, perform a check for updates to
ensure that you have all the most recent updates.
You can use operators in your searches to obtain more accurate search results. Here
are examples of the supported search operators and their meanings:
Linux Matches anything that contains Linux.
Linux*
Matches anything that begins with Linux.
Linux server
Matches anything that contains either Linux or server or both.
Linux OR server
Same as Linux server.
+Linux +server
Matches anything that contains both Linux and server.
Linux AND server
Same as +Linux +server.
+Linux -Blade
Matches anything that contains Linux and does not contain Blade.
clock~ Matches anything like clock, such as block, click, clocks, and so on.
(Linux OR server) AND Blade
Matches anything that contains Blade and also contains Linux or server or
both.
"Issues and Recommendations"
Matches anything with the exact phrase 'Issues and Recommendations'.
Related concepts:
Related tasks:
Navigating tables
Navigating tables
Related reference:
lsupd command
Viewing required updates:
When preparing to install an update, it might be necessary to first install another

update on a given system. These updates are called required updates or requisite
updates.
You can view the updates required by an update by navigating the requires
relationship on the update menu. The requires relationship navigation will display
the updates required by the currently selected update. The updates are displayed
in a navigator table view.

This table view can be switched by the user to a topology map to display a
graphical layout instead of a table. In the topology map, the required relationships
between the updates are displayed.
To view the required updates for a specific update, complete the following steps:
1. From any list of updates, select the update whose required updates you want
to display.
2. Click Actions > Related Resources > Needed Updates. A table of the needed
updates is displayed.
Related concepts:
Related tasks:
Navigating tables
Navigating tables
Related reference:
lsupd command
Viewing the contents of update collections:
An update collection is an update that contains other updates, such as a service

pack. They can be managed as a single unit, just like an individual update.
To determine if an update is a collection or an individual update, from any table

where a list of updates is displayed, view the Update Types field. A value of
'Collection' indicates that the update is an update collection. A value of 'Individual'
indicates that the update is not a collection, but an individual update.
To view update collections, complete the following steps:

1. From any list of updates, select an update collection.
2. Click Actions > Related Resources > Updates. A table of the member updates
is displayed.
Although you can view the member updates in an update collection, you are
advised not to install these individual members separately. Instead, install the
entire update collection.

Related concepts:
Related tasks:
Related reference:
lsupd command
Viewing the supersede relationships for an update:
One update supersedes another if installation of the one update will make the
other no longer needed.
The concept of supersede can be explained by this example. UpdateA supersedes

UpdateB if UpdateA contains all the information in UpdateB, or installing
UpdateA creates a situation where UpdateB is not needed. UpdateA can be said to
supersede UpdateB or be a supersede of UpdateB. UpdateB can be said to be
superseded by UpdateA.
You can see the updates that are superseded by a given update by selecting
supersedes on the Related Resources submenu at the top of the update menu. It is
possible that an update does not supersede any other. It is also possible that an
update is not superseded by any other
This table view can be switched by the user to a topology map to display a
graphical layout instead of a table. In the topology map, the superseded
relationships between the updates are displayed.
Related concepts:
Related tasks:
Related reference:
lsupd command
Viewing parent update collections:
For a given update, a parent update collection is an update collection that contains
this update, as well as possibly others. Not all updates will have a parent update
collection.
Parent update collections are updates themselves, and can be installed as an

update. These are similar in concept to service packs.
To view update collections, complete the following steps:

1. From any list of updates, select an update whose parent update collection you
want to view.

2. Click Actions > Related Resources > Update Collection. The update collection
that contains this update is displayed.
Although you can view the member updates in an update collection, you are
advised not to install these individual members separately. Install the entire update
collection.
Related concepts:
Related tasks:
Related reference:
lsupd command
Managing update groups

You can group updates to form an update group, which can then be managed as if it
were an individual update. The use of update groups can save time and limit the
complexity of the update tasks.
Related concepts:
Update groups
Related tasks:
Managing groups
Managing groups
Update groups:
Update groups can be static or dynamic. Both types can be used in compliance
policies.
Static update groups
Contain individual updates that were explicitly chosen. Once established,
the membership changes only when you manually add or delete updates.
Static update groups can be used as a baseline for future comparison or
update deployment.
Dynamic update groups
Automatically contains updates based on selected update types. The
membership of this group changes as update information changes.

If you add a system group or an update group to an existing system group or

update group, this new, nested group will not be considered when the parent
system or update group is used for validation of compliance policies.
Viewing update groups:
It is advisable to view the individual members of an update group so that you are
aware of the updates that are being used for compliance policies.

To view an update group, complete the following steps:

1. From the Update Manager summary page, click Show update groups. A table
of all defined update groups is displayed. This table shows all the update
groups in the group named Update Groups.
2. Click the name of the update group that you want to view. The members of the
group are displayed in a list.
Related concepts:
Update groups
Related tasks:
Creating update groups
Managing groups
Managing groups
Navigating tables
Navigating tables
Creating update groups:
Although there are predefined update groups, you might want to create and
manage update groups for your unique systems and their software.
To create an update group, complete the following steps:

1. From the Resource Navigator, click Create Group. The Group Editor wizard is
displayed.
2. If the Welcome page is displayed, click Next. The Name page is displayed.
3. Type a name and description for the new group and click Next. The Type and
Location page is displayed.
4. Select a Member type of Update.
5. In the Group type field, choose either a Static or Dynamic update group. The
Define page is displayed.
6. Select group members:
v If the group type is Static, select the individual updates and update collection
and click Add to move them to the Selected column.
v If the group type is Dynamic, select the types of updates and click Add to
move them to the Selected column. These values are like those on the
Acquire Updates page.
8. Review the choices for the new group carefully.
v If your choices are correct, click Finish to create the update group.
v If you want to change your choices, click Back to go to the previous page, or
choose the Group Editor wizard page from the navigation area.

Related concepts:
Update groups
Related tasks:
Viewing update groups
Managing groups
Managing groups
Installing updates on systems

Use the Install wizard to install updates on systems or groups of systems. If you
choose to install updates that have not been downloaded or staged for installation,
these tasks will be automatically performed as part of the installation task.
Note: The installation of updates on IBM i (formerly i5/OS) systems requires a

single sign-on credential that maps an IBM Systems Director Web interface user to
an IBM i user ID.
v For instructions to create credentials, see “Creating single sign-on credentials”.
v For more informations about credentials, see “Managing single sign-on
credentials”.
Tip: Use the IBM Systems Director Pre-Install Utility to scan systems and identify
potential problems that could prevent IBM Systems Director from updating
successfully.
Tip: To protect your system in the event of an unforeseen complication, ensure

that you back up your data before performing any update tasks.
To install updates, complete the following steps:

2. Click Show and Install Updates. The Show and Install Updates page is
displayed.
3. Select a system or system group in the Selected systems field. Click Browse
to see a list of systems to choose from.
4. Click Show and install updates. A table of needed updates is displayed.
5. Select each update that you want to install. Whole update collections, not
individual member updates, will be installed.
6. Click Install. The Install wizard Welcome page is displayed.
7. Clear Show this welcome page next time if you do not want to see the
Welcome page next time.
8. Click Next The Systems page is displayed.
9. If some of the updates are for AIX or IBM BladeCenter systems, and you had
not already specified the necessary AIX or IBM BladeCenter options on the
Settings page, it is displayed so that you can choose these options.
10. Click Next.
11. Optional: If you select updates that require a manual download, and this has
not already been done, you must manually download them. The Downloads
required page is displayed.
a. Click Details to perform the manual download.
b. Click Continue, the updates are now downloaded and ready when you
have completed the manual download.

c. Click Skip the updates which must be manually downloaded if you do
not want to download these updates, or the manual download process has
failed for one or more of them.
12. Click Next.
13. Optional: The Manual Installation Required page will be displayed if a
selected update must be manually installed by the user.
a. Click View under the Installation Instructions heading to see the manual
installation instructions.
b. Read the instructions and decide to install the updates now or later.
Updates that require manual installation will be removed from the list of
selected updates. If all the selected updates require manual installation, you
cannot continue; Next will be disabled.
14. Click Next. The Restarts page is displayed. All selected systems are displayed
in the table even if they do not require a restart. For each system, the highest
restart impact is listed. The systems are sorted in this table with those of
highest restart impact listed first.
15. Automatically restart as needed during installation is selected by default.
Clear this box if you do not accept the restart requirements. If you clear the
Automatically restart as needed during installation box and updates are
installed that have pending restarts, then the installation task will complete
with errors and some update installs might not be attempted if a dependent
update requires an immediate restart.
16. Click Yes in the Restarts Required column for a system to view all updates to
be installed on the system and their individual restart requirements. This view
is specific to the selected system. It shows all the updates that will be installed
on that system and the restart value for each. You cannot change the
information on this page. If you do not accept the restart requirement, click
OK to return to the Install wizard, click Back, and then remove systems or
updates.
If you have selected system groups as the target for the update installation,
the list of individual systems in these groups is not determined until the task
runs. You are presented options only for those systems that were individually
selected. Group membership is not determined until the task runs.
The restart must be performed before other updates can be installed
or uninstalled.
The restart can be performed at the end of the install or uninstall task.
v If it is correct, click Finish. A panel is displayed for you to specify
notification and schedule settings for the installation task.
Note: Even if the installation of your update is successful, the version numbers
that are displayed for a particular updated IBM Systems Director component might
not match across version displays. For example, after successfully updating
Platform Agent 6.2 to 6.2.1 and collecting inventory, the Platform Agent version

that is displayed in the file set remains as 6.2. Rebooting the system will fix the
version in some but not all instances of this issue. Regardless, this issue does not
impact functionality, though, and you can ignore it.
Related tasks:
Navigating tables
Navigating tables
Managing single sign-on credentials

Related reference:
Pre-Installation Utility
installupd command
Removing update files

When an update is no longer needed, you can remove its associated installable
files to save space.
If an update has not been downloaded, this task is not available. This task removes
the installable files for an update, but descriptive information about the update is
not removed. When this task completes, the update remains known to update
manager and is treated like any other update.
To remove the installable files from an update, complete these steps:

1. From any page where a list of updates is present, select the updates whose files
you want to delete.
2. Click Actions > Delete files.
3. Click Yes in the verification window to confirm the removal of the files.
To remove all information about an update, use the cleanupd command.

Related reference:
cleanupd command
Uninstalling updates
It might be necessary to remove an update from a system or group of systems. Use
the Uninstall updates task to do this. Not all updates support the uninstall task.
For updates that cannot be uninstalled, it might be possible to roll them back to an
earlier version by installing an older version on top of the current one.
To uninstall updates, complete the following steps:

1. From the Update Manager summary page, click Show installed updates. The
Show Installed Updates page is displayed.
3. Click Show installed updates. A table of installed updates is displayed.
4. Select each update that you want to uninstall.
5. Click Uninstall updates. The Uninstall wizard Welcome page is displayed.

6. Clear Show this welcome page next time if you do not want to see the
7. Click Next. The Updates page is displayed.
8. Select each update that you want to uninstall and click Add.
9. Click Next. The Systems page is displayed.
10. Select each system or system group from which you want to uninstall the
updates and click Add. All selected updates that are installed on these
systems will be uninstalled. If you select a system group, the updates are
uninstalled from those systems that are a member of the group at the time the
uninstallation task runs.
11. If some of the updates are for AIX systems, and you had not already specified
the necessary AIX options on the Settings page, it is displayed so that you can
choose these options.
12. Click Next.
13. Optional: The Manual Uninstall Required page might be displayed. It is
displayed only when an update selected for uninstallation must be manually
removed.
a. Click View under the Uninstallation Instructions heading to see the
manual instructions for each update to be uninstalled.
b. Read the instructions and decide to run them now or later.
14. Click Next. The Restarts page is displayed. All selected systems are displayed
in the table even if they do not require a restart. For each system, the highest
restart impact is listed. The systems are sorted in this table with those of
highest restart impact listed first.
15. Automatically restart as needed during installation is selected by default.
Clear this box if you do not accept the restart requirements. If you clear the
Automatically restart as needed during installation box and updates are
uninstalled that have pending restarts, then the uninstallation task will
complete with errors and some uninstalls might not be attempted if a
dependent update requires an immediate restart.
16. Click Yes in the Restarts Required column for a system to view all updates to
be uninstalled on the system and their individual restart requirements. This
view is specific to the selected system. It shows all the updates that will be
uninstalled on that system and the restart value for each. You cannot change
the information on this page. If you do not accept the restart requirement,
click OK to return to the Uninstall wizard, click Back, and then remove
systems or updates. If you have selected system groups as the target for the
uninstallation task, the list of individual systems in these groups is not
determined until the task runs. You are presented options only for those
systems that were individually selected. Group membership is not determined
until the task runs.
The restart must be performed before other updates can be installed
or uninstalled.
The restart can be performed at the end of the install or uninstall task.

v If the information is correct, click Finish. A panel is displayed for you to
specify notification and schedule settings for the task being launched by
this wizard.
If an update cannot be uninstalled, it might be possible to roll back the installed

update by installing an older version of the update. The older update can be
installed if the older update is applicable to the system.
Related tasks:
Navigating tables
Navigating tables
Related reference:
uninstallupd command
Acquiring and installing updates with the installneeded

command
Use this alternate update method if you want to use the command line to specify
some options and then let update manager automatically obtain and install all
types of updates for IBM Systems Director.
You can use the installneeded command line tool to simply update IBM Systems
Director servers and agents, or you can add optional parameters to install other
update types. The tool performs the entire update process from beginning to end
with a single command. The basic flow consists of collecting inventory on the
target system, acquiring updates, running compliance, installing needed updates,
then running inventory and compliance again.
This topic describes several high-level uses for the installneeded command. See
the installneeded command topic for more detailed information.
v To update IBM Systems Director Server from the FSP, issue the following
command:
smcli installneeded -v -F
This command will use the server on which it is run as the target. It will
automatically acquire IBM Systems Director Server updates from the FSP and
install them. The -v option specifies “verbose” and is useful for tracking
progress or seeing problems. The -F option specifies “force”, without which the
command will ask for confirmation before installing each update.
The following options and operands are also useful when updating IBM Systems
Director Server:
-I Installs updates that are already in the updates repository. For example:
smcli installneeded -v -I
import_path
Installs updates after you import them from the supplied path. For
example:
smcli installneeded -v c:\dirupdates
See the installneeded command topic for more detailed information about these
options and operands.

v To update Common Agent or Platform Agent with the latest update level from
the FSP, complete the following steps from an IBM Systems Director server:
1. Issue the following command to determine the OID of the system:
smcli lssys -o
The output will resemble this example:
netvj165, 0xa98
netvj165.vrow.netfinity.com, 0xa39
2. Issue the following command to update the agent:
smcli installneeded -v -n {system_oid | system_name} -F
For example:
smcli installneeded -v -n 0xa39 -F
smcli installneeded -v -n netvj165.vrow.netfinity.com -F
The following options and operands are also useful when updating Common
Agent or Platform Agent:
-I Installs updates that are already in the updates repository. Use the
following format for the command:
smcli installneeded -v -n {system_oid | system_name} -I
-i Specifies an IP address or host name to identify the system instead of
the system OID or system name. This could be useful if you are
using a script to update the system after using other CLI commands
to discover and request access to the system. If both the server MEP
and operating system MEP have the same IP address, you must use
another parameter along with the command to install the updates
without user intervention. Use the following format for the
command:
smcli installneeded -v -t system_type -i ip_address -F
For example:
smcli installneeded -v -t OperatingSystem -i 10.11.9.165 -F
Note: Use the lssys -T command to determine the valid system

types.
Note: You can use -i in combination with -I.

See the installneeded command topic for more detailed information about
these options and operands.
v To update Common Agent or Platform Agent with a specific update level,
complete the following steps from an IBM Systems Director server:
1. Download the desired updates from www.ibm.com/support/fixcentral/.
2. Issue the following command to import and install the updates:
smcli installneeded -v -n {system_oid | system_name} -F import_path
For example:
smcli installneeded -v -n 0xa39 -F c:\dirupdates
v To install other types of updates, complete the following steps:
1. Issue the following command to determine the update type or types to
specify:
smcli installneeded --list

2. Issue either of the following commands to install the updates:
– smcli installneeded -v -n {system_oid | system_name} -F -u
update_type
– smcli installneeded -v -t system_type -i ip_address -F -u
update_type
For example:
– Install System x and IBM BladeCenter updates from the FSP to the system
with a system OID of 0xa39:
smcli installneeded -v -n 0xa39 -F -u systemxandbc
– Install System x and IBM BladeCenter updates that were already acquired
from the FSP or imported previously to the system with a system name of
netvj165.netfinity.com:
smcli installneeded -v -n netvj165.netfinity.com -F -u systemxandbc -I
– Install Linux updates to the system with an IP address of 10.11.9.165:
smcli installneeded -v -t OperatingSystem -i 10.11.9.165 -F -u linux
Note: The default value for -u is “Director”, which is implied if -u is not

specified. That is why the previous command to update IBM Systems
Director Server was accurate even though the -u option was not included.
The -u option corresponds to the update ProviderType and specifies the
types of updates to acquire if -c is specified or implied when no other option
is given. The acquire updates task will only order updates using the default
criteria values that are supported by the target system or server if no target
system is provided.
To illustrate with an example, a user wants to update IBM Systems Director

Server on Linux and uses the following command to do so:
smcli installneeded -v -F
The user then discovers and accesses a Linux agent and plans to perform
Linux updates on the agent after the agent side setup is complete. There are
correct and incorrect commands to use for this action:
– Incorrect:
smcli installneeded -v -t OperatingSystem -i 10.11.9.165 -F -u linux -I
This command would find no updates to install. Even though the smcli
installneeded -v -F command already ran the acquire updates task on a
Linux server, -u was not specified and therefore defaulted to “-u
Director”. Only IBM Systems Director updates were acquired from the
FSP, and no Linux updates were placed in the repository for installation.
– Correct:
smcli installneeded -v -t OperatingSystem -i 10.11.9.165 -F -u linux
This command would complete an acquire updates task for Linux updates
from the FSP and install them.
See the installneeded command topic for more detailed information about
these options and operands.

Related concepts:
Related tasks:


Related reference:
Update types
lssys command

Use compliance policies to receive notification about systems that are missing
specific updates.
The Update Manager summary page provides a quick view of the number of
systems that are monitored by compliance policies and the number of systems that
are out of compliance. Review this information before viewing the more detailed
data that follows it.
Use the Update Manager summary page to view information about compliance
policies for your systems. All compliance policy tasks are initiated from the Update
compliance section on this page.
Note: Compliance status does not change on the monitored systems until an
acquire updates task is complete and compliance has completed. This status
change can take up to ten minutes after the acquire updates task completes.
Important: When using compliance for the first time, keep in mind the following
items:
v To check compliance for IBM BladeCenter and System x systems running Linux
or Windows, an applicable IBM UpdateXpress System Pack Installer (UXSPi) is
required. The UXSPi is downloaded automatically when you use update
manager to acquire updates from the internet. If the management server does
not have an internet connection, you must manually download and import an
applicable UXSPi.
Important: For UXSPi to work correctly on 64-bit Linux operating systems, you
must install the compatibility libraries compat-libstdc++-296-2.96.
v To check compliance for , Systems Director an applicable IBM UpdateXpress
System Pack Installer (UXSPi) is required. The UXSPi is downloaded
automatically when you use update manager to acquire updates from the
internet. If the management server does not have an internet connection, you
must manually download and import an applicable UXSPi.

Important: For UXSPi to work correctly on 64-bit Linux operating systems, you
must install the compatibility libraries compat-libstdc++-296-2.96.
v To efficiently balance impact on resources and improve reliability, consider
grouping your systems, for example by type or by level of operating system,
and then using a rollout or staged approach to attain currency.
v For important information about applying compliance on IBM BladeCenter and
System x systems specifically, refer to the Best Practice Firmware Update Guide -
IBM BladeCenter and System x at http://www.ibm.com/support/entry/portal/
docdisplay?lndocid=MIGR-5082923
v For important information about applying compliance on Systems Director, see
the Firmware Update Guide - IBM Flex System, at http://www.ibm.com/
support/entry/portal/docdisplay?lndocid=MIGR-5091991&brandind=5431802.
1. To view or edit update compliance policies, click Create and configure
compliance policies from the Update Manager summary page. A list of
systems is displayed.
2. Select a system from the list to edit its compliance policy.
You can create compliance policies on systems or system groups. When a policy is
created on a system group, all systems within the group inherit the compliance
policy. The group is displayed in the Inherited column when viewing the system
compliance policy.
Related concepts:
Compliance policies
Compliance policies
Use compliance policies to monitor your systems and inform you when systems
are missing specific updates.
The first section on the Update Manager summary page is the Update Compliance
section. This section provides a quick summary of the update health of your
systems and provides several system-related tasks.
Tips
v If you see the term Inherited Compliance Policy or an Inherited field in a table
when you are viewing this information, there is a compliance policy on the
parent group for the system. The policy can be removed from the system only
by removing it from the system parent group.
v The behavior of a compliance policy for an update group differs slightly
depending on whether the update group is static or dynamic:
Static update group
When a static update group is examined, each update contained within
the group that is applicable to the system must be found to be installed;
otherwise the compliance policy indicates an 'out of compliance'
situation. This situation is verified by examining the appliesTo
relationship on the update.
Dynamic update group
When a dynamic update group is examined, the compliance policy
indicates an 'out of compliance' situation only when updates that are

needed by the systems are not installed. This situation is verified by
examining the needs relationship on the update.
v If you add a system group or an update group to an existing system group or
update group, this new, nested group is not considered when the parent system
or update group is used for validation of compliance policies.
v If an update that is not applicable to a particular system is not installed, the
compliance policy does not indicate an 'out of compliance' situation.
Adding updates to a compliance policy

Updates can be added to a compliance policy to keep the compliance policy
current.
To add an update to the compliance policy for a system, complete the following
steps:
1. From any panel that has a list of updates displayed, click Add to >
Compliance Policy.
2. Select the system or system group to be monitored for the update.
3. Click OK. The selected update is added to the compliance policy for the
system.
4. Click Save to save the compliance policy.
Related concepts:
Compliance policies
Related tasks:
Create and configure compliance policies

Use the Create and configure compliance policies page to change compliance
policies.
The Create and configure compliance policies task is used to configure compliance
policies on systems that are monitored for missing updates. Each compliance check
is listed on a separate line.
The target system or system group is checked against its associated compliance
policy automatically when the system or update inventory changes.
To modify compliance policies, complete the following steps:

1. From the Update Manager summary page, click Create and configure
compliance policies. The Compliance Policy page is displayed.
2. Select a system or system group.
3. Optional: Click Browse to see a list of systems.
a. Click Add to add a system or system group.
b. Click Remove to remove a system or system group.
4. Click Show Compliance Policies.
5. Select one of the following policies to create or, if it already exists, configure it:
v Policy to ensure that the latest released updates are always applied
v Policy to ensure that specific version levels of updates are maintained

Important: If a policy already exists and you select and configure the other
policy, the existing policy and its compliance checks are removed when you
save the new policy.
If the chosen policy already exists, the table displays all associated compliance
checks. If the chosen policy does not already exist, the table is empty.
6. Choose a task to perform on the selected compliance policy:
v Create a new compliance check. Complete the following steps:
a. In the displayed table, click Add.... The Add... page is displayed.
b. In the Show: list, select the type of updates to display in the table.
Note: If you are adding a compliance check to the “Policy to ensure that
the latest released updates are always applied” policy, you can choose
from among only dynamic update groups. If you are adding a
compliance check to the “Policy to ensure that specific version levels of
updates are maintained” policy, you can choose from among only
individual updates or static update groups.
c. Choose the updates or update groups to include in the compliance policy.
d. Click OK to add the updates or update groups to the compliance policy.
v Remove a compliance check. Select a compliance check, then select Actions >
Remove.
7. Click Save to save the changes to the compliance policy. This will activate the
selected compliance policy and any compliance checks that you set up for it,
and will remove any previously existing compliance policies and compliance
checks.
Example
If you create a static update group where some of the updates supersede others,
the compliance policy verifies that the latest superseding update is installed. The
recommendation that comes from this type of compliance policy will be to install
the latest update in the supersede chain.
As an example, consider an update group with these attributes:

v It is a static update group.
v Group members are updates named UpdateA, UpdateB, and UpdateC.
v UpdateA supersedes UpdateB.
v UpdateB supersedes UpdateC.
When a compliance policy is created with this group, the compliance policy
verifies that the latest supersede update (UpdateA in this case) is installed, and, if
it is not, the recommended action is to install the latest update in the supersede
chain (UpdateA in this case). Even if both UpdateB and UpdateC are installed, the
compliance policy indicates 'out of compliance' unless UpdateA is installed. If
UpdateB and UpdateC are not found on the system, but UpdateA is present on the
system, the compliance policy indicates that the system is in compliance.

Related concepts:
Compliance policies
Related tasks:
Identifying systems that are out of compliance

Identify systems that are out of compliance so that you can take recommended
corrective action.
This function does not give you information about all your systems, just those that
are monitored by compliance policies.
The system-compliance status indicator represents the highest severity among all of
the compliance policy updates that are not installed on the system. There are five
compliance categories, represented by icons:
: Indicates a missing update severity of critical or high
: Indicates a missing update severity of medium or low
: Indicates a missing update severity that is not known or not

applicable
: Indicates systems that are in compliance; they have no missing

updates
: Indicates systems that are not accessible or do not have inventory

collected
To identify systems that are out of compliance according to an active compliance

policy, complete the following steps:
1. On the Update Manager summary page, find the Update Compliance section.
2. Examine the pie chart and icons to its right. The number of systems in each
compliance category is displayed.
Note: The compliance pie chart is visible only if you have already created a
compliance policy for your system.
3. If one or more system is in need of updates, click one of the systems links next
to the severity icons (which are next to the pie chart). This displays a table of
systems.
4. Optional: You can also click the View all issues link to the bottom right of the
pie chart to view all compliance issues for all systems that are in a policy and
are in need of updates.
5. Examine the Compliance column to find which systems are in need of updates.
The highest severity of all the missing updates is displayed.
6. Select one or more systems.
7. Click System Health > Compliance Issues The View All Issues page is
displayed.

Those systems that have the same compliance issues are grouped, and the total
number of systems is displayed.
8. Click a compliance issue to expand and filter the list of individual systems.
Otherwise, each system with each particular issue and recommendation is
listed.
Related concepts:
Compliance policies
Related tasks:
Changing compliance policies
Resolving compliance issues

When a compliance policy indicates that there are updates that are required on one
or more systems, examine the severity of the updates, and plan to install them
considering your system's availability, workload, and scheduling factors.
Use this procedure only if one or more of your systems is out of compliance, as
indicated by the Compliance column in the list of monitored systems, or as
indicated by the pie chart on the Update Manager summary page.
Note: The compliance pie chart is visible only if you have already created a
compliance policy for your system.
The Compliance column visually indicates that a system is not in compliance. The
status severity is the highest severity of all the updates needed by the system.
To correct an out-of-compliance situation, complete the following steps:

1. Click the compliance status in the Compliance column to see the Issues and
Recommendations panel.
2. Read the recommended action. Make sure that you understand the proposed
actions.
3. Choose the issues that you want to resolve and then click either Install or
Uninstall, according to the recommendation. The appropriate wizard starts.
You can choose to resolve all issues at once instead of resolving them
individually.
Related concepts:
Compliance policies
Related tasks:
Changing compliance policies
Navigating tables
Navigating tables

Chapter 8. Remotely accessing systems and resources
Using the IBM Systems Director remote access function, you can establish sessions
to a system and transfer files when you are logged into another system.
In order to use remote access, one or more discovered and accessible systems must
have support for at least one remote access task.
Remote access facilities

Remote access has facilities for file transfer and access to systems in both
full-screen and command-line modes.
Remote access consists of these access mechanisms:

Distributed Command
Executes a command on one or more managed systems in parallel.
File Transfer
Transfers files from one system to another.
Launch Web Browser
Opens a browser window for the selected system.
Remote Command line
Establishes command-line access to a remote system.
Remote Control
Establishes full-screen access to a remote system using these access
methods:
BladeCenter and RSA Remote control
Launches the Web interface to remotely control IBM BladeCenter or
Remote Supervisor Adapter (RSA) systems
Microsoft Windows Remote Desktop Connection
Launches this application for Windows systems
Virtual Network Computing
Launches Virtual Network Computing (VNC) for AIX and Linux
systems.
Remote Xen Console
Establishes command-line access to a remote Xen server.
Serial Console
Opens console windows to one or more POWER managed systems.
Distributed Command
The Distributed Command task launches the Distributed Shell.
Restriction: To use this task, you must be logged into IBM Systems Director Server
running on AIX. Otherwise, you will get an error message.
The Distributed Shell gives you the ability to execute a command on one or more
managed systems in parallel. The command is executed on each remote target and
the output from each system is returned to the IBM Systems Director Server.

The Operating System resource type is supported by the Distributed Command
task.
Related tasks:
Using the Distributed Shell
File management
Use the File Management task to manage files and directories on a remote system.
From the IBM Systems Director Web interface, you can use the File Management
task to manage files on a remote system. File management task operations include
rename, delete, upload, download, and the creation of new folders.
If you use the File Management task to perform an upload or download, you can
transfer individual files and directories between the following systems only:
v The browser system and the management server
v The browser system and a managed system
Transferring files directly between a management server and a managed system is

not supported. If you need to transfer a file from a management server to a
managed system (or the reverse, from a managed system to a management server),
you must transfer the file to a browser system first, and then transfer it from the
browser system to the managed system or the management server.
Launch Web browser

Use the Launch Web browser facility to access a system that has a Web server.
The IP address that IBM Systems Director has for the system is used to launch the
Web browser with http protocol.
Remote Command Line

The Remote Command Line task establishes command-line access to a remote
system.
The Remote Command Line task opens a non-graphical Remote Command Line
window in the IBM Systems Director Web interface. You can communicate with a
remote system by issuing its operating system's commands at the command-line
prompt in the window.
Generally, you can have multiple remote command-line sessions active at the same
time.
Restriction: You can have only one active remote command-line session through a
management server to a single Windows system at a time.
When you connect to a system that is running UNIX or Linux, Remote Command
Line uses the secure shell (ssh) protocol. If the ssh server on the system does not
respond, Remote Command Line attempts to connect using the Telnet protocol.
For a system running IBM i, Remote Command Line uses the Telnet protocol only.
The Remote Command Line function does not use SSH to connect to switches. For
switch resources, telnet is always used.

Remote control tasks
Remote control establishes a full-screen session to the remote system using a
remote control application.
If your system does not have one of the following applications installed, you must
first install and configure it on your browser system.
BladeCenter and RSA Remote Control
Launch the Web interface for remote control of IBM BladeCenter or Remote
Supervisor Adapter (RSA) systems.
Launch this application for Windows systems.
Launch Virtual Network Computing (VNC) for AIX and Linux systems.
Microsoft Windows Hyper-V Virtual Machine Connection Tool
Launch the Hyper-V Virtual Machine Connection Tool.
VMware ESX or ESXi hypervisor virtual machine
Launch a VMware ESX or ESXi hypervisor virtual machine connection.
Setting up remote control
As mentioned above, if your system does not have one of the above
applications installed, you must first install and configure it on your
browser system. To install and configure a remote control application:
1. From the Remote Access Summary page, click Set up remote control.
2. On the Setup Remote Control page, click the check box next to Use
Remote Desktop to control Window systems.
3. Complete required fields.
4. Click Apply and then OK.
Related concepts:
IBM BladeCenter and RSA Remote Control
Hyper-V Virtual Machine Connection Tool
VMware ESX or ESXi hypervisor virtual machine connection
Related tasks:
Running remote access functions

Use the IBM BladeCenter and Remote Supervisor Adapter (RSA) function to access
an IBM BladeCenter or RSA system.
Related tasks:
Establishing IBM BladeCenter or RSA communication

Use the Microsoft Windows Remote Desktop Connection to establish remote
control sessions to Windows systems from IBM Systems Director.
Before using Microsoft Windows Remote Desktop Connection, make sure to

configure it on your Windows system. There is no need to install or configure
anything on IBM Systems Director.
Chapter 8. Remotely accessing systems and resources 407

Related tasks:
Configuring Microsoft Windows Remote Desktop Connection
Establishing Remote Desktop Connection

Use the Virtual Network Computing (VNC) application to establish remote control
sessions to AIX and Linux systems from IBM Systems Director.
Virtual Network Computing must be installed first in order to use it with remote
control.
Follow these steps to install VNC:

1. Install the RealVNC viewer or another compatible VNC viewer on the Web
browser client.
2. Ensure that the Web browser client has network access to the agent.
3. Install and configure the VNC server on the agent, using a default port number
of 5091.
Important: When using VNC to establish remote control sessions on Linux

systems, you must also create the following script on your Web browser system
and associate it with the .vnc file type in the browser.
#!/bin/sh
VncViewer=vncviewer # (may need to be customized for your environment)
Conf=$1
Host=$( cat $Conf | grep ^Host= | cut -d= -f2 | tr -d ’\r’ )
Port=$( cat $Conf | grep ^Port= | cut -d= -f2 | tr -d ’\r’ )
Port=eval [ $Port - 5900 ]
which $VncViewer 1>/dev/null 2>&1 && $VncViewer $Host:$Port &
Related tasks:
Establishing Virtual Network Computing communications
Hyper-V Virtual Machine Connection Tool

The Microsoft Windows Hyper-V Virtual Machine Connection Tool can be
launched from IBM Systems Director using Remote control to display and provide
access to the video, keyboard, and mouse of Hyper-V virtual machines.
Related concepts:
Related tasks:
Launching the Microsoft Windows Hyper-V Virtual Machine Connection Tool
VMware ESX or ESXi hypervisor virtual machine connection

VMware ESX and VMware ESXi are platform-virtualization software that you can
launch from IBM Systems Director by using Remote control.
Related concepts:
Related tasks:
Launching a VMware ESX or ESXi hypervisor virtual machine connection
Remote Xen Console

The remote Xen console task manages a command-line interface to a remote Xen
server.

You can use the remote Xen console window to establish a fully active command
session with a remote Xen server or host. The remote Xen server or host must be
started and have access granted in order to establish communications. This session
is non-graphical, so a command line window opens when it is started.
Serial Console
The Serial Console task launches the serial console.
Restriction: To use this task, you must be logged into IBM Systems Director Server
running on AIX 6.1F or higher. Otherwise, you will get an error message.
The serial console gives you the ability to open console windows to one or more
IBM Power managed systems. Each window provides access to the system’s serial
console, accessed out-of-band.
The following resource types are supported by the Serial Console task:
v Server
v Virtual Server
v System
Related tasks:
Using the serial console
Running remote access functions

You can run the remote access functions from the Remote Access Summary page.
For the remote control functions, you do not choose which function to run. It is
chosen based on the target system.
Related concepts:
Remote access facilities
Related tasks:
Using the Distributed Shell

Use the Distributed Shell to execute a command on one or more managed systems
in parallel.
To use the Distributed Shell, you must be logged into IBM Systems Director Server
When you use the Distributed Shell to execute a command on one or more
managed systems in parallel, the command is executed on each remote target and
the output from each target is returned to the IBM Systems Director Server.
To use the Distributed Shell, complete the following steps:

1. From the Remote Access Summary page, click Distributed Command. The
Targets page is displayed.
2. Select one target for remote access. Use the Add and Remove buttons to move
items between the Available list and the Selected list.
3. Optional: Click Show to filter the targets, for example, to show only those
targets that support the Distributed Command task.

4. Click OK. The Distributed Shell page is displayed with a Selected Targets
pane that contains the list of targets selected.
5. Optional: To display a list of hidden options, click Show Additional Options.
The options include:
Shell The shell in which the remote command should be run. You can select
either ksh or csh.
Fanout
The maximum number of target systems to run command in parallel.
(1–16).
Timeout (sec)
The amount of time, in seconds, that can elapse before termination of
command execution. Zero can be used for unlimited timeout.
Output formatting
The format of output from the targets. You can select None, Group
output from each target together, or Compress identical output.
Send server locale information to targets
If you want to send server locale information to the targets, click the
check box next to this option.
Hide Additional Options
You can click Hide Additional Options to close the Show Additional
Options pane.
6. Optional: Click Save As to save the command so that it can be recalled later
using Browse Saved Commands ....
a. A Save command window is displayed with two fields: Name and
Description.
b. Required: Specify a name to save the specified command under in the
Name field. The command name is loaded in the Command field.
c. Optional: Specify a description of the command in the Description field.
7. Click Run. The command is executed on the selected targets.
8. Optional: If you click Browse saved commands ..., the Saved commands
window is displayed where you can select a previously saved command. The
commands are listed in the following format: Name – Description.
To execute a saved command:
a. Select a saved command from the Select saved command: pull-down menu.
b. Click Load . The command name is loaded in the Command field.
c. Click Run on the Distributed Shell page. The command is executed on the
selected targets.
In the Saved commands window, you can also select Delete, to delete a saved
command or Cancel, to close the Saved commands window.
After the command executes on the selected targets, the Command Output pane is
displayed in the Distributed Shell page to show the output of the command from
each target, as well as errors from those targets. Click Cancel to return to the
Distributed Shell page where you can run additional commands.
Remember:
v When specifying a name for the command, if another command is already saved
under the same name, an error message displays.
v The name you specify cannot contain spaces.

v The Name field is used to create a file of the same name.
v The created files will be stored in the /opt/ibm/sysmgt/dsm/saved_commands
directory.
Related concepts:
Distributed Command
Using the Distributed Shell to issue a command to several

targets
You can use the Distributed Shell to issue a command to several targets.
Before doing this task, a set of Operating System targets must be discovered and
you must request access to those targets.
Explorer.
2. Select the Operating System targets for which you want to run the command
by clicking on the box next to the target in the Select column.
3. Click Actions and select Distributed Command. The Distributed Shell page is
displayed.
4. Type the command name in the Command field. For example, date, for the
date command.
5. Click Run. The command is executed on the selected targets and the output is
displayed on the Command Output pane.
Using the Distributed Shell to issue a command to a group

You can use the Distributed Shell to issue a command to a group.
To use the Distributed Shell you must be logged into IBM Systems Director Server
you must have access to those targets.
Explorer.
2. Navigate to the group of type Operating Systems.
3. Right-click the group and select System Configuration > Remote Access >
Distributed Command. The Distributed Shell page is displayed.
4. Type the command name in the Command field. For example, date, for the
date command.
5. Click Run. The command is executed on all the members of the selected group
and the output is displayed on the Command Output pane.
Using the Distributed Shell to save a command for future

execution
You can use the Distributed Shell to save a command for future execution.

Explorer.
2. Navigate to a target.
3. Right-click the target and select System Configuration > Remote Access >
4. Click Save As.
5. Type the Name and Description for the saved command.
6. Click Save.
Using the Distributed Shell to execute a previously saved

command
You can use the Distributed Shell to execute a previously saved command.
Explorer.
2. Navigate to a target.
4. Click Browsed Saved Commands. The Saved Commands window is
displayed.
5. Select a command to execute.
6. Click Load. The Distributed Shell page is displayed with the command name
in the Command field.
7. Click Run to execute the command.
Managing files on a remote system

Use the File Management task to manage files on remote systems.
Important: Keep in mind the following important items when you use the File
Management task to transfer (upload or download) files:
v You can use the task with only one system at a time. You cannot transfer files to
multiple systems or to a group.
v Files are transferred in chunks through a queue on the management server and
the receiving Common Agent. If the chunk is not processed by the queue before
the timeout limit is reached, the transfer will fail. Such failures can occur when
other tasks are running on the same Common Agent, or when the queue is full.
Give careful consideration to transferring large files using file management.
v The transfer of large (5 MB or larger) files might take several or more minutes to
complete, during which time you might receive little or no indication that the
transfer is still running. If you try to initiate the transfer again while the original
transfer is still running, both transfers will fail. So, before trying to transfer a file
again, verify that the original transfer completed and failed.
To use the File Management task to manage files, complete the following steps:
1. From the Remote Access Summary page, click File Management. The Targets
page is displayed.

2. Select the targets for file management, using the Add and Remove buttons to
move a system from the left (Available) column to the right (Selected) column.
Note: The Choose Target window does not display locked systems.
3. Click OK. The File Management page is displayed.
4. Right-click on a file or directory and select a management operation: Rename,
Delete, New Folder, Upload File or Download File.
5. Optional: Alternatively, you can access the File Management page from the
Navigation pane by clicking System Configuration > Remote Access > File
Management.
6. Optional: Right-click on a file or directory and select Properties to view
properties not displayed in the default view of the File Management page, such
as Created, Type, and Attributes.
7. Optional: Click Actions > Columns to select additional properties to display on
the File Management page. Select the properties by using the Add and Remove
buttons to move a property from the left (Available) column to the right
(Selected) column.
Related concepts:
File management
Establishing command-line access to a remote system

Use Remote Command Line to run commands on a remote system.
To establish a remote command-line session, complete the following steps:

1. From the Remote Access Summary page, click Remote Command Line. The
2. Select a target for remote access, using the Add and Remove buttons to move a
system from the Available column to the Selected column. You can select only
one target.
targets that support remote command line.
4. Click OK. A Login dialog displays in front of the Remote Command Line
window.
5. Type the User name and Password for the remote system you are accessing.
6. Click OK. The Remote Command Line window is enabled for input.
Note: If the window is disabled for input after you click OK, you must ensure
that the server is in the browsers trusted zone. You can perform the following
steps for Internet Explorer:
a. Launch Microsoft Internet Explorer.
b. Select Tools > Internet Options > Security.
c. Select Trusted sites.
d. Click Sites. The Trusted sites window opens.
e. In the Add this website to the zone: field, type https://<server ip address>
for example, https://10.10.6.120. Click Add.
f. Click Close on the Trusted sites window and then click OK to close out the
Internet Options window.
Perform these steps for Mozilla Firefox:
a. Launch Firefox.
b. Select Tools > Options > Security.

c. Select Exceptions. The Allowed Sites - Add-ons Installation window opens.
d. In the Address of web site field, type https://<server ip address> for
example, https://10.10.6.120. Click Allow.
e. Click Close on the Allowed Sites - Add-ons Installation window and then
click OK to close out the Options window.
7. Optional: Alternatively, you can establish command-line access to a remote
system by using Resource Explorer to navigate to the system.
Explorer.
b. Navigate to the system on which you want to establish command-line
access.
c. Right-click the system and select System Configuration > Remote Access >
Remote Command Line
d. Follow steps 5 and 6 above.
8. After the Remote Command Line is enabled for input, you can communicate
with the remote system by issuing its operating system's commands.
9. When you are finished, close the Remote Command Line tab to terminate
command-line access.
Related concepts:
Remote command line
Launching a Web browser

Use the Launch Web browser task to access the default Web page for a system that
hosts a Web server.
When using this feature, you might see panels displaying various actions
performed by IBM Systems Director in order to accomplish this task. These panels
require no action from you and can be ignored.
Note: For more information about navigating and working with the Available
table, see “Navigating tables.”
To launch a Web browser for a system that hosts a Web server, complete the
following steps:
1. From the Remote Access Summary page, click Launch Web Browser. The
2. Select a target using the Add and Remove buttons to move a system from the
Available column to the Selected column. You can select only one target.
targets that support launching a Web browser.
4. Click OK. Using the IP address for the chosen system, a Web browser is
invoked.
5. View and communicate with this Web page.
6. When you are finished, close the Web browser session.
Related tasks:
Navigating tables
Configuring Microsoft Windows Remote Desktop Connection

You must configure Microsoft Windows Remote Desktop Connection on your
Windows system in order to use it with IBM Systems Director.

If you are using a web browser on a Linux system to connect to a Windows agent,
you will need to configure and use the tsclient application.
To configure Microsoft Windows Remote Desktop Connection on your Windows

system, go to the Web site at windows.microsoft.com/en-us/windows7/products/
features/remote-desktop-connection and follow the instructions.
Note: The Windows panel interfaces and text vary slightly depending on the
version of Windows that you are running.
You can ignore the section Connect your remote computer to the host computer;
this action is performed automatically by IBM Systems Director.
Related concepts:
Establishing Remote Desktop Connection

Use Microsoft Windows Remote Desktop Connection to communicate with
Windows systems.
If you are using a Linux browser, you must install and configure the tsclient
application.
To establish a Microsoft Windows Remote Desktop Connection communications

session, complete the following steps:
1. From the Remote Access Summary page, click Remote Control. The Targets
page is displayed.
2. Select the target for access, using the Add and Remove buttons to move a
system from the Available column to the Selected column.
3. Click OK. A window opens displaying a file; the file name is an IP address and
the file type is rdp.
4. Click Open. A Remote Desktop session is started.
5. Perform your work on this remote desktop.
6. When you are finished, close the page by clicking the X at the top.
Related concepts:
Establishing Virtual Network Computing communications

Use Virtual Network Computing (VNC) to communicate with systems with a
full-screen session.
The Web browser-client machine must install RealVNC viewer or a compatible

VNC viewer. The agent must be configured to run vncserver on the default port of
5901.
Important: The VNC Remote Framebuffer (RFB) protocol is not secure. However,
you can improve the security of a VNC session by using a Secure Shell (SSH)
tunnel. To create an SSH tunnel on Linux or Unix systems before you start VNC,
run the following command:
ssh -L local_port:local_hostname:destination_port -N -f
user_name@destination_hostname
where:

v local_port is any available local port on the local host system that is the source
of the tunnel
v local_hostname is the local host system that is the source of the tunnel
v destination_port is the remote port on the system that is the destination of the
tunnel
v user_name is the user ID that enables the SSH session to the VNC server (and
KVM host)
v destination_hostname is the host name of the system that is the destination of
the tunnel
The SSH session continues to run in the background and can be terminated after
the VNC session ends. Some VNC viewers will optionally create an SSH tunnel
and determine the available local port to use.
To establish a VNC session, complete the following steps:

page is displayed.
2. Select the target for VNC access, using the Add and Remove buttons to move a
system from the left (Available) column to the right (Selected) column.
3. Click OK. A window opens displaying a file; the file name is an IP address and
the file type is vnc.
4. Click Open. A VNC session is started.
5. Communicate with the target system by logging in and working as usual.
6. When you are finished, terminate the VNC communication by clicking the X at
the top of the window.
Important: When using VNC to establish remote control sessions on Linux

systems, you must also create the following script on your Web browser system
and associate it with the .vnc file type in the browser.
#!/bin/sh
VncViewer=vncviewer # (may need to be customized for your environment)
Conf=$1
Host=$( cat $Conf | grep ^Host= | cut -d= -f2 | tr -d ’\r’ )
Port=$( cat $Conf | grep ^Port= | cut -d= -f2 | tr -d ’\r’ )
Port=eval [ $Port - 5900 ]
which $VncViewer 1>/dev/null 2>&1 && $VncViewer $Host:$Port &
Related concepts:
Establishing IBM BladeCenter or RSA communication

Use IBM BladeCenter or Remote Supervisor Adapter (RSA) to communicate with
IBM BladeCenter or RSA systems with a full-screen session.
To establish an IBM BladeCenter or RSA communications session, complete the

following steps:
page is displayed.
2. Select an IBM BladeCenter or RSA target, using the Add and Remove buttons
to move a system from the Available column to the Selected column.
3. Click OK. The IBM BladeCenter or RSA system is displayed.
4. From the IBM BladeCenter Management Module, click Blade Tasks > Remote
Control in the left navigation area.
5. Communicate with the target system by logging in and working as usual.
6. When you are finished, close the browser window.
Related concepts:
Launching the Hyper-V Virtual Machine Connection Tool

Use Remote control to launch the Microsoft Windows Hyper-V Virtual Machine
Connection Tool.
To launch the Hyper-V Virtual Machine Connection Tool, complete the following
steps:
page is displayed.
2. Select the virtual server target for access, using the Add and Remove buttons
to move a virtual server from the Available column to the Selected column.
3. Click OK. The Hyper-V Virtual Machine Connection Tool is launched.
Related concepts:
Launching a VMware ESX or ESXi hypervisor virtual machine

connection
Use Remote control to launch a VMware ESX or ESXi hypervisor virtual machine
connection
To launch a VMware ESX or ESXi hypervisor virtual machine connection, complete

page is displayed.
2. Select the virtual server target for access, using the Add and Remove buttons
to move a virtual server from the Available column to the Selected column.
3. Click OK. A VMware ESX or ESXi hypervisor virtual machine connection is
launched.
Related concepts:
Establishing a remote Xen console session

Use remote Xen console to run commands on a remote Xen server.
When using this feature, you might see panels displaying various actions
performed by IBM Systems Director in order to accomplish this task. These panels
require no action from you and can be ignored.
Note: For more information about navigating and working with the Available
table, see “Navigating tables.”
To establish a remote Xen console session, complete the following steps:

1. From the Remote Access Summary page, click Remote Xen Console. The
2. Select a target using the Add and Remove buttons to move a system from the
Available column to the Selected column. You can select only one target.

targets that support remote Xen console.
4. Click OK. A window with a remote Xen console is displayed and enabled for
input.
5. Communicate with the remote Xen console.
6. Optional: You can select text within the remote command-line window and
click Edit > Copy to copy the selected text to the clipboard. You can also
import clipboard text into a remote command line window by clicking Edit >
Paste.
7. When you are finished, click File > Close to terminate the session.
Related tasks:
Navigating tables
Accessing POWER managed systems or x86-based systems

by using the serial console
Use the serial console to open console windows to one or more POWER managed
systems or x86-based systems.
To use the serial console, you must be logged in to IBM Systems Director Server
running on AIX 6.1F or higher. Otherwise, an error message is displayed.
Use the serial console to open windows to POWER managed systems or x86-based
systems. Each window provides access to the serial console of the system, which is
accessed out-of-band.
To use the serial console, complete the following steps:

1. From the Remote Access Summary page, click Serial Console. The Targets page
is displayed.
2. Select one target for remote access. Use the Add and Remove buttons to move
items between the Available list and the Selected list.
3. Optional: Click Show to filter the targets. For example, you can use the filter to
show only those targets that support the hardware command-line interface.
4. Click OK. A separate window is displayed for each selected target. The title of
each console window is the display name of the selected target.
Note: The defaults cannot be changed when the serial console is displayed
when the IBM Systems Director web interface is used.
Important: When you use the serial console connection to remotely access an
x86-based system, ensure that Windows Telnet server is installed on the x86
system. You must also start a Telnet service because by default a Telnet service is
not enabled. If the Telnet server is already installed, ensure that the serial over
LAN (SOL) settings are configured as a prerequisite. For details on the
configuration, see the Serial over LAN (SOL) Setup Guide.
Note: If an error indicates that an SSH or Telnet server is not configured, install
and enable the Telnet Server on the resource.

Related concepts:
Serial Console
Displaying a serial console to one server target

You can display a serial console to one server target from the IBM Systems
Director Resource Explorer page.
To use the serial console, you must be logged into IBM Systems Director Server
Before doing this task, you must have access to the target's managing hardware
control point.
Explorer.
2. Navigate to the target for which you want to display a serial console.
Serial Console. A separate window is displayed for the selected target.
4. Login to the console with the target's userid and password.
Displaying a serial console to several server targets in a group

You can display a serial console to several targets in a group from the IBM Systems
Director Resource Explorer page.
Before doing this task, you must have access to the target's managing hardware
control point.
Explorer.
2. Navigate to the group containing System type objects for which you want to
display a serial console.
3. Right-click the group and select System Configuration > Remote Access >
Serial Console. A separate window is displayed for the selected group.
4. Optional: You can also select multiple individual targets from Resource
Explorer. After you specify your targets, select System Configuration > Remote
Access > Serial Console from the Actions pull-down menu.
5. Login to each target using target's userid and password.
Closing the serial console

There are three ways to close the serial console.
Close the serial console by using one of three methods:

v File > Close
v X from the console title bar
v Ctrl-x

Chapter 9. Managing agents
You can use IBM Systems Director to deploy and manage agents (including
Common Agent and Platform Agent).
used.
Common agent services

IBM Systems Director uses the common agent services (CAS) architecture, which
provides a shared infrastructure for managing systems. This infrastructure, which
includes resource manager, agent manager, and common agent elements, is also
used by Tivoli Provisioning Manager products.
The goal of common agent services is to reduce infrastructure cost, complexity, and
redundancy by providing a common agent that can be used by multiple
management products instead of multiple separate agents that each provide
essentially the same functionality.
To achieve this goal, one or more resource managers (such as IBM Systems Director
Server) use an agent manager to communicate with the common agents that are
installed on managed resources. This architecture is illustrated in Figure 15.
IBM Systems
Director Server
Resource manager
Embedded agent Common agents

manager
Figure 15. The elements of common agent services in the default configuration for IBM Systems Director
Related information:
Tivoli Provisioning Manager documentation
Resource manager
Installed on the management server, the resource manager is the management
application that uses the agent manager for security and credential management.
IBM Systems Director Server is the resource manager for IBM Systems Director.

Multiple resource managers can use the same agent manager and manage the same
common agents.
v Each common agent can use exactly one agent manager.
v Each resource manager can use exactly one agent manager.
v Each resource manager can manage many common agents.
Agent manager
The agent manager provides authentication and authorization services for installed
common agents and resource managers. It also maintains a registry of
configuration information about Common Agent managed systems.
Note: Except for security and credential management, systems management

communications between IBM Systems Director Server and common agents do not
go through the agent manager.
IBM Systems Director uses only one active agent manager at a time to
communicate with common agents. If no agent manager is active, IBM Systems
Director is not able to manage common agents.
v Each agent manager can be used by many resource managers.
v Each agent manager can be used to manage many common agents.
As illustrated in Figure 15 on page 421, IBM Systems Director Server includes an

embedded agent manager. However, IBM Systems Director Server can use an agent
manager other than the one that is embedded locally. Using another agent manager
allows multiple instances of IBM Systems Director Server to manage the same
common agents. Installing your IBM Systems Director Server instance and the
agent manager on separate servers can also improve performance.
Notes:
v The agent manager that is embedded with IBM Systems Director Server can be
used by any number of instances of IBM Systems Director Server, but it is not
configured for use with other management application products.
v If you will use the locally embedded agent manager, you need to supply
credentials when you configure it that are used if you change agent managers.
These credentials depend on your operating system:
– On AIX or Linux, you can specify any credentials. You do not need to use the
root user ID or even an operating system user ID.
– On Windows, use the same administrator credentials that you used to install
The agent manager has the following parts:

agent manager service
The agent manager utilizes http servlets or Web services to manage agents
for IBM Systems Director and other products. The agent manager service
provides authentication and authorization using X.509 digital certificates
and the Secure Sockets Layer (SSL) protocol. It also processes queries
against its registry of configuration information about common agents and
resource managers. Resource managers and common agents must each
register with the agent manager before they can use its services to
communicate with each other.

The agent manager service provides the core agent manager functionality
with the following services:
Service catalog
Provides information about the location of the agent manager
service.
Credential manager
Enables the agent manager to act as a certificate authority and
issue security credentials and revocation lists to managed elements.
Agent registry
Retrieves information about the common agent resources.
Querying service
Enables the resource manager to query the agent registry for the
agent and resource manager information.
agent manager registry
The agent manager registry stores the following information in a database:
v The identity, digital certificates, and communication information for each
resource manager
v The identity, digital certificate, and status for each common agent
v Basic configuration information about each common agent including
information about the type and version of the hardware and operating
system
v The last error or, optionally, a configurable number of errors, reported by
each common agent
v Communication parameters for the common agent, including IP address,
the port or ports for which the common agent is configured, and the
supported protocol
Common agent
Installed on managed systems, the common agent reports information about the
managed system to the resource manager and performs tasks on the managed
system as directed by the resource manager.
used.
v Each common agent can be managed by one or more instances of IBM Systems
Director Server.
Note: All instances of IBM Systems Director Server must use the same agent
manager, and the common agent must be registered with that agent manager.
When you discover a system that has a common agent on it, the IBM Systems
Director Web interface will list the system with a protocol of 'CAS'. The system
will initially have no access, but you can register the agent with the agent manager
using one of the following two methods, depending on the mode you used to
install common agent services:
Chapter 9. Managing agents 423

Managed mode common agent services
Common agent services registers the common agent with the agent
manager during installation.
Unmanaged mode common agent services
Requesting and gaining access to the system registers the common agent
with the default agent manager that is configured with IBM Systems
Director Server.
Related concepts:
Common Agent
Logging Platform Agent

Use the PALog.INI configuration file to configure logging for Platform Agent. This
topic describes the property values and options to use with that file.
The PALog.INI file is located at the following paths:

v On Linux: PA_INSTALL_DIR/platform/data/PALog.INI
v On Windows: PA_INSTALL_DIR\cimom\data\PALog.INI
where PA_INSTALL_DIR is the Platform Agent installation path.
Example ITA properties file

# ITA Properties file written Sat Sep 04 19:43:00 2010
[PlatformAgent.Logging]
codeset_dir =
config_type = cclog
logging_type = ita_logdefault
nlspath =
start_logdaemon = none
use_logdaemon = false
[PlatformAgent.Logging.cclog]
PlatformAgent.organization = CompanyA
PlatformAgent.logger.className = ccg_pdlogger
PlatformAgent.logger.listenerNames = PlatformAgent.loggerfl PlatformAgent.ffdc
PlatformAgent.loggerfl.className = ccg_levelfilter
PlatformAgent.loggerfl.level = ALL
PlatformAgent.loggerfl.listenerNames = PlatformAgent.loggerhd
PlatformAgent.loggerhd.className = ccg_filehandler
PlatformAgent.loggerhd.fileName = agent.log
PlatformAgent.loggerhd.formatterName = PlatformAgent.fmt
PlatformAgent.loggerhd.maxFileBytes = 4096000
PlatformAgent.loggerhd.maxFiles = 3
PlatformAgent.fmt.className = ccg_basicformatter
PlatformAgent.ffdc.className = ccg_ffdc_filecopy_handler
PlatformAgent.ffdc.baseDir = PlatformAgent-FFDC
PlatformAgent.ffdc.filesToCopy = agent.log
PlatformAgent.ffdc.triggerFilter = PlatformAgent.lf
PlatformAgent.lf.className = ccg_levelfilter
PlatformAgent.lf.level = ERROR
PlatformAgent.tracer.className = ccg_pdlogger
PlatformAgent.tracer.listenerNames = PlatformAgent.trfl
PlatformAgent.trfl.className = ccg_levelfilter
PlatformAgent.trfl.level = OFF
PlatformAgent.trfl.listenerNames = PlatformAgent.trhd
PlatformAgent.trhd.className = ccg_filehandler
PlatformAgent.trhd.fileName = agent.trace
PlatformAgent.trhd.maxFileBytes = 4096000

PlatformAgent.trhd.maxFiles = 3
PlatformAgent.trhd.formatterName = PlatformAgent.trfmt
PlatformAgent.trfmt.className = ccg_basicformatter
PlatformAgent.fmt.className
Sets the format in which messages are logged. The following values are
accepted:
ccg_basicformatter
The text format in which the messages are logged.
ccg_xmlformatter
The XML format in which the messages are logged.
PlatformAgent.logger.className
Indicates the type of logging handle to use for the logger. The following
values are accepted:
ccg_basiclogger
A basic logger class, with support for localized and non-localized
messages. Loggers of this class do not automatically add any data
to the event except for the timestamp. ccg_basiclogger does not
show the LEVEL information. The following example shows what
the output might look like:
2010-09-04 20:04:43.671+05:30 PlatformAgent.Test | This is a test
message
ccg_pdlogger
An extended logger class with extra information for diagnosing
application problems. Loggers of this class automatically add the
names of the product, component, server, and organization to the
event, along with the timestamp. The following example shows
what the output might look like:
2010-09-24 08:14:39.663-04:00 18446744073559305104 7093 CompanyA
nettk125.trow.netfinity.com PlatformAgent | Start Logger
PlatformAgent.
Note: If the className value is set to NULL, a warning message does not
appear on the IBM Systems Director Web interface. It instead appears on
the agent console. A default logger with the name
PlatformAgent_default_message.log is created for logging the warning
message information.
PlatformAgent.logger.listenerNames
Specifies a list of names that procures events from the specified logger,
filter, or handler. Ensure that the names are the names of objects that are
defined in the same properties file. Separate the names in the list with
spaces. By default, Platform Agent supports two listeners: logger and
FFDC. To disable the FFDC, remove the PlatformAgent.ffdc entry.
PlatformAgent.loggerfl.className
Specifies the class name for the logging level filter. This property is not
configurable; do not change it.
PlatformAgent.loggerfl.level
Specifies the logging filters with log level values. The following values are
accepted:
ALL Enables all log levels.

FATAL
Instructs the filter to block all events that are at a level lower than
fatal.
ERROR
error.
WARNING
warning.
INFO Instructs the filter to block all events that are at a level lower than
info.
DEBUG_MIN
(Default log and trace value.) Sets the debugging log levels to the
minimum value and includes extra debugging information such as
method name, function name, and line numbers.
DEBUG_MID
Sets the debugging log levels to the median value and includes
extra debugging information such as method name, function name,
and line numbers.
DEBUG_MAX
Sets the debugging log levels to the maximum value and includes
extra debugging information such as method name, function name,
and line numbers.
OFF Disables logging and creates a log file that contains only a message
stating that the logger initialized. No other messages are logged.
When no log level is specified, a warning message appears. A default
logger with the name PlatformAgent_default_message.log is created for
logging the warning message information.
A default tracer with the name PlatformAgent_default_trace.log is created
for logging the trace information.
PlatformAgent.loggerfl.listenerNames
Assigns the logger handler that manages the logging properties that are
related to the log file. This property is not configurable; do not change it.
PlatformAgent.loggerhd.appending
Indicates whether to append or overwrite existing file handler output files.
The following values are accepted:
TRUE (Default value.) Causes existing files to open in append mode.
FALSE
Causes existing files to be overwritten.
PlatformAgent.loggerhd.className
Indicates the type of handler to use for the logger. The following values are
accepted:
ccg_filehandler
Logs the messages to a file.
ccg_consolehandler
Logs the messages to the IBM Systems Director Web interface. This
option is not supported.

PlatformAgent.loggerhd.fileName
Indicates the full path of the log file. If this property is set to blank, no log
file is created, a warning message appears, and no logging takes place.
Note: If a Windows path name is specified in a properties file, you must

double the back-slashes like in the following example:
fooHandler.baseDir: C:\\temp\\myApp\\
PlatformAgent.loggerhd.formatterName
Specifies the handle to the Platform Agent formatter, which takes care of
assigning a particular format for the log file. This property is not
configurable; do not change it.
PlatformAgent.loggerhd.maxFileBytes
Indicates the maximum file handler output file size (in bytes). When that
size is reached, the log file is closed and renamed, and an empty new log
file is opened. This property has no effect unless the set value of the
maxFiles property is greater than one.
Note: For the correct behavior, set this value higher than 10 KB. If it is set
to less than 10 KB, the maxFileBytes size of the rollover files cannot be
interpreted if the log messages are high.
Example: In the following example, the first rollover file is of size

agent.log and the next rollover files is of size maxFileBytes:
Size of the rollover files = if ( sizeofagent.log > maxfileBytes )
PlatformAgent.loggerhd.maxFiles
Indicates the maximum number of file handler output files that are created
before the oldest one is recycled. If this property is set to 1 or 0, the current
log file never closes and might grow without limit. A warning message
appears. The default value is 3.
PlatformAgent.organization
Displays the organization name as IBM in the log file.
Trace properties
The following trace properties are like their companion log properties.
Note: The default trace level is OFF.

v PlatformAgent.tracer.className
v PlatformAgent.tracer.listenerNames
v PlatformAgent.trfl.className
v PlatformAgent.trfl.level
v PlatformAgent.trfl.listenerNames
v PlatformAgent.trfmt.className
v PlatformAgent.trhd.className
v PlatformAgent.trhd.fileName
v PlatformAgent.trhd.formatterName
v PlatformAgent.trhd.maxFileBytes
v PlatformAgent.trhd.maxFiles
FFDC properties
PlatformAgent.ffdc.className
When set to ccg_ffdc_filecopy_handler, copies specified files to an

output directory whenever triggered by an event. This action
allows the creation of backup copies of files, the contents of which
might have been otherwise overwritten before examined.
PlatformAgent.ffdc.baseDir
Required value that designates the base directory into which all
FFDC output is placed. To conform to the Tivoli Serviceability
Imperative, this base directory must adhere to the following
format:
[install-Dir]/[log]/PlatformAgent-FFDC/
Whenever FFDC actions occur, daily subdirectories with the

following format are created under the base directory:
[baseDir]/[YYYY.MM.DD]/
where YYYY.MM.DD is the numeric year, month, and day from the
timestamp of the event that triggered the FFDC action.
By default, no base directory is specified, and no FFDC actions are

performed by an FFDC handler until the property is specified.
Instead, a warning is issued until the property is set.
Note: If a Windows path name is specified in a properties file, you

must double the back-slashes like in the following example:
fooHandler.baseDir: C:\\temp\\myApp\\
PlatformAgent.ffdc.filesToCopy
Specifies the files to copy. To copy multiple files on Windows,
enclose each file name in quotations and separate each one by a
space.
If you specify to log the ERROR level, FFDC is triggered and files
are copied into the directory that is specified by the
PlatformAgent.ffdc.baseDir property.
Every time FFDC is triggered, message files are appended.
PlatformAgent.ffdc.triggerFilter
Required value that designates the name of a CCLOG or CFFDC
filter to control which events trigger an FFDC action.
By default, no trigger filter is specified, and no FFDC actions are
performed by an FFDC handler until the property is specified.
Instead, a warning is issued until the property is set.
PlatformAgent.ffdc.triggerRepeatTime
Sets the minimum amount of time, in milliseconds, that it will take
the handler to respond to more triggering events after a triggering
event. Use this property to limit how rapidly a given FFDC action
is repeated. For example, it might not make sense for a given
application to take an AutoTrace snapshot less than 10 seconds
after the previous snapshot.
PlatformAgent.ffdc.maxDiskSpace
Sets the maximum disk space, in bytes, that is allotted to the FFDC
data. When the total space used by the FFDC data exceeds the
specified limit, a warning is issued and, depending on the quota
policy, actions are taken. Those actions might include the automatic

deletion of older files or the suspension of new FFDC actions until
more space is made available by the manual removal of files. By
default, the maximum disk space is 10 megabytes (10*1024*1024).
PlatformAgent.ffdc.quotaPolicy
Designates the policy that specifies what to do when the FFDC
directory exceeds the disk space limit. The following values are
allowed:
QUOTA_AUTODELETE
(Default value.) Automatically deletes FFDC files, in a
decreasing order of age, until the directory is below the
disk space limit.
QUOTA_IGNORE
Issues warnings but do not enforce the FFDC disk space
quota.
QUOTA_SUSPEND
Halts further FFDC actions until the FFDC directory is
manually cleaned up to below the disk space limit.
PlatformAgent.ffdc.firstWarning
A percentage of maximum disk space usage for the first warning.
A first warning is issued if the disk space usages exceeds this
value. Set this value to a floating-point value between 0.0 and 1.0.
The default first warning threshold is 0.75.
PlatformAgent.ffdc.secondWarning
Sets a maximum percentage of disk space usage for the second
warning. A second warning is issued if the disk space usages
exceeds this value. Set this value to a floating-point value between
0.0 and 1.0. The default second-warning threshold is 0.90.
PlatformAgent.lf.className
Sets the trigger filter for the FFDChandler ccg_level_filter, which
specifies that the FFDC trigger occurs, and then monitors the log
levels in the log file.
PlatformAgent.lf.level
Designates the FFDC trigger level value of the log levels in the
logging filters. The following values are accepted:
FATAL
Triggers the FFDC when a fatal error message is logged in
the log file.
ERROR
Triggers the FFDC when an error error message is logged
in the log file.
When no log level is specified, a warning message appears. A
default logger with the name PlatformAgent_default_message.log
is created for logging the warning message information.
A default tracer with the name PlatformAgent_default_trace.log is
created for logging the trace information.

PALog.INI and PALog.INI.bkp files
The PALog.INI.bkp file is created as a backup in case a process crashes while

updating the PALog.INI file.
When you modify any configuration, use PALog.INI.bkp to ensure that the
property ITA logging initialization File I/O takes place properly.
If both of these files are deleted, ITA fails to initialize the logger and throws an
error message. The location of the error file is ./tmp/italog_error.log on Linux
and %TEMP%/italog_error.log on Windows.
ITA logs only the initialization error messages in to the error log file.
If the PALog.INI is corrupted or invalid property values are assigned, no error

messages are logged to the italog_error.log file. No such error messages appear on
the IBM Systems Director Web interface.
PALog.INI is not recreated if it is corrupted. For every successful logger

initialization, PALog.INI.bkp is overwritten with the PALog.INI.
Importing agent packages

IBM Systems Director Server can import agent packages that have been
downloaded from the Web or obtained on physical media. These agent packages
then can be distributed to managed systems using the Agent Installation Wizard.
The agent packages that IBM Systems Director Server uses are Tivoli Provisioning
Manager automation packages with a file extension of .tcdriver for 6.1.x packages
and .jar for 6.2 packages.
Use the following procedure to import one or more agent packages for distribution
using the Agent Installation Wizard.
1. Download the installation package from the IBM Systems Director Downloads
Web Site at www.ibm.com/systems/management/director/downloads/.
2. Copy the package files to a directory on the management server.
3. In the IBM Systems Director navigation area, click Release Management >
Agents. The available agent and subagent package groups are listed.
Note: A subagent plugs in to a base agent and provides additional capabilities

to support IBM Systems Director plug-ins such as IBM Systems Director
VMControl. This documentation uses the collective term “agents” to refer to
both agents and subagents.
4. Click Import Agent. The Import Agent window opens.
5. Type the path on the management server where you copied the package files in
step 2, and then click OK.
All of the agent packages that are found in the specified path are imported, and a
confirmation message appears indicating that the packages were successfully
imported.
Note: The imported packages might not appear in the agent package groups list
immediately.

After the agent packages are successfully imported and appear in the agent
package groups, you can install the packages using the Agent Installation Wizard.
Related tasks:
“Installing agents using the Agent Installation Wizard”
"Developing automation" in the Tivoli Provisioning Manager Information

Center
Installing agents using the Agent Installation Wizard

You can use the Agent Installation Wizard to install agent packages on managed
systems.
IBM Systems Director Server requires a number of agent packages that can be
deployed to managed systems using the Agent Installation Wizard.The imported
agent packages are located in the dynamic group “Agent Package Groups” and can
be accessed by clicking Release Management > Agents in the navigation area. You
use the Agent Installation Wizard to select one of these agent packages to install
and one or more systems on which to install the agent package. Then, the wizard
creates an agent installation job that can run immediately or at a scheduled time.
Important: Ensure that the following requirements are met to enable use of the
Agent Installation Wizard to install and update agents:
v The root user account was used to initially request access to the managed
system.
v IBM Systems Director Server on non-Windows systems has SSH, and a
successful SSH connection exists in both directions between the server and the
agent.
v IBM Systems Director Server on Windows systems has DCOM, and a successful
DCOM connection exists in both directions between the server and the agent.
Complete the following steps to import the agent packages:

1. Download the remote agent packages from http://www.ibm.com/systems/
software/director/downloads/agents.html. Ensure that you choose packages
from the “Remote Deployment using Agent Installation wizard” section.
2. Copy the packages to a location of your choice on the IBM Systems Director
Server system.
3. Import the packages with the Agent Installation Wizard.
4. Make any required changes to the diragent.rsp and or platform.rsp response
files. See the topic for your operating system under “Installing Common Agent
manually” or “Installing Platform Agent manually” for instructions about how
to change the response files.
Complete the following steps to install agents using the Agent Installation Wizard:
1. Start the Agent Installation Wizard. You can start the wizard in multiple ways:
v From the Home page, click Additional Setup. Then, click Install agents on
systems > Deploy Agents.
v Right-click an agent package or a managed system and select Release
Management > Install Agent.
2. If the Agent Installation Wizard Welcome page appears, click Next.
3. In the Agent Installation Wizard Agents page, complete the following steps:

a. Select the agent or subagent package that you want to install in the
Available list.
Note: A subagent plugs in to a base agent and provides additional

capabilities to support IBM Systems Director plug-ins such as IBM Systems
Director VMControl. This documentation uses the collective term “agents”
to refer to both agents and subagents.
b. Click Add. The selected agent package is displayed in the Selected list.
Notes:
v Depending on how you started the Agent Installation Wizard, the
Selected list might already contain one or more agent packages.
v The Agent Installation Wizard can install only one agent package at a
time. If more than one agent package is displayed in the Selected list,
you will not be able to advance to the Systems page.
c. Click Next.
4. In the Agent Installation Wizard Systems page, complete the following steps:
a. Select the managed systems on which you want to install the agent package
in the Available list.
b. Click Add. The selected systems are displayed in the Selected list.
Notes:
v Depending on how you started the Agent Installation Wizard, the
Selected list might already contain one or more systems.
v Depending on the agent package that you are installing, some selected
systems are potentially not valid targets for installation. The wizard
checks the selected systems for some or all of the following criteria to
ensure that the systems are valid targets before allowing you to continue:
– Operating system family
– Operating system version
– Operating system distribution
– Operating system name
– Server architecture
c. Click Next.
5. In the Agent Installation Wizard Summary page, review the Selected Agents
and Selected Systems lists to ensure that they are correct.
v If the selections are not correct, click Back and make the necessary changes.
v If the selections are correct, click Finish.
After you click Finish, the Run - Install Agent window opens.
6. In the Run - Install Agent window, click the Schedule tab. On this page, you
can choose to run the job immediately or schedule the job to run at a later time.
b. To run the job immediately, click Run Now and go to step 7 on page 433.
Otherwise, click Schedule.
weekend.

sent by e-mail.
criteria is met:

job behavior.
The job created by the Agent Installation Wizard will transfer the agent
self-extracting script and the agent response file into the following directory,
which depends on your version and agent level, on the target system:
6.x Common Agent
/tmp/commonagent_tmp
6.x Platform Agent
/tmp/platformagent_temp
5.x Common Agent
install_root/SwDistPk
After the files are copied, the installation file sets are extracted into the /tmp
directory and installed. The files are then removed after a successful
installation. You need to ensure that there is sufficient space on the target
system to copy the self-extracting script and extract the file sets. Refer to the
space requirements as specified in “Hardware requirements for systems
running Common Agent or Platform Agent”.
If the agent deployment completes with errors, check the log file for your target
operating system for a possible root cause:
v AIX and Linux:
– Common Agent: /var/log/dirinst.log

– Platform Agent: /opt/ibm/platform/log/install.log
v Windows: %WINDIR%/diragentinst_timestamp.log or %WINDIR%/
platint_timestamp.log
Note: For more information about error log files, see “Information to provide
to the IBM Technical Support Center”.
Notes for AIX:

v Refer to “Installing Common Agent on AIX” for more detail on the
self-extracting script and the response file options.
v For AIX server and agents, it is less space consuming to remotely install
agents using NIM as explained in the IBM Systems Director Best Practices
wiki page “Installing IBM Systems Director Common Agent for AIX using
NIM” at http://www.ibm.com/developerworks/wikis/display/WikiPtype/
Installing+IBM+Systems+Director+Common+Agent+for+AIX+using+NIM.
Installing with NIM does not allow the use of a response file.
You can view the status of the agent installation job by clicking Task Management
> Active and Scheduled Jobs.
If you installed Platform Agent on Linux, enable SNMP Access and Trap
Forwarding by installing and configuring Net-SNMP. For instructions and
information, see http://www.net-snmp.org/.
Related tasks:
Install the product on the management server.

Log on, discover managed systems, and request access to them.
Verify that the systems meet the requirements for the agents you will install.
Preparing a common-agent managed system
Preparing a platform-agent managed system
Scheduling tasks
“Importing agent packages” on page 430
Related reference:
Hardware requirements for systems running Common Agent or Platform Agent
IBM Systems Director for Power Systems wiki
"Developing automation" in the Tivoli Provisioning Manager Information

Center
Restarting agents
The following topics contain information about stopping, starting, and checking
the status of Common Agent and Platform Agent.

Related tasks:
“Changing the Common Agent IP address” on page 449
Restarting Common Agent

Restarting Common Agent requires that you run a command to restart certain
processes and, for other processes, run one command to stop the processes and
then run another command to start them again.
Before you stop Common Agent, warn users to finish their work or stop the
processes that they are running.
To restart Common Agent, complete the following steps:

1. Stop the Common Agent processes.
v If you are running AIX, type the following command on a command line and
press Enter:
stopsrc -s cas_agent
v If you are running IBM i, type the following command on a command line
and press Enter:
ENDTCPSVR SERVER(*HTTP) HTTPSVR(CAS)
Note: The IBM i Common Agent an IBM i TCP server.

v If you are running Linux, type the following command on a command line
and press Enter:
install_root/agent/runtime/agent/bin/endpoint.sh stop

installation.
v If you are running Windows, type the following command on a command
line and press Enter:
install_root\agent\runtime\agent\bin\endpoint.bat stop
Note: If desired, you can use the following command instead:

net stop IBMTivoliCommonAgent0
Note: After the Common Agent processes are stopped, two events that
announce that the agent is stopped are immediately generated and recorded in
the IBM Systems Director Server event log. However, a third event, which
announces that the agent system is offline, is also recorded in the event log, but
at a later time. This third event is generated only after IBM Systems Director
Server next runs the Verify Connection task against the agent system. The
Verify Connection task runs according to a user-defined schedule, so the third
event is delayed and then recorded according to that same schedule.
2. Start the Common Agent processes.
press Enter:
startsrc -s cas_agent
and press Enter:
STRTCPSVR SERVER(*HTTP) HTTPSVR(CAS)
and press Enter:
install_root/agent/runtime/agent/bin/endpoint.sh start

installation.
install_root\agent\runtime\agent\bin\endpoint.bat start
Note: If desired, you can use the following command instead:

net start IBMTivoliCommonAgent0
3. Obtain the status of Common Agent to ensure that it started successfully.
press Enter:
lssrc -s cas_agent
and press Enter:
install_root/agent/runtime/agent/bin/endpoint.sh status

installation.
install_root\agent\runtime\agent\bin\endpoint.bat status

installation.
Restarting Platform Agent

Restarting Platform Agent requires that you run a command to restart certain
processes and, for other processes, run one command to stop the processes and
then run another command to start them again.
Before you stop Platform Agent, warn users to finish their work or stop the
processes that they are running.
To restart Platform Agent, complete the following steps:

1. Stop the Platform Agent processes.
press Enter:
stopsrc -s platform_agent
Note: Stopping Platform Agent does not also stop the CIM server. If you
want to stop the CIM server, type the following command and press Enter:
stopsrc -s cimsys
and press Enter:
paservices stop
Note: Alternatively, you can run the following command to stop and then
automatically start the Platform Agent services on Linux:
paservices restart
and press Enter:
ENDTCPSVR SERVER(*CIMOM)

Note: The IBM i Platform Agent is an IBM i TCP server.
v If you are running Windows, run the following command:
paservices.vbs stop
automatically start the Platform Agent services on Windows:
paservices.vbs restart
2. Start the Platform Agent processes.
press Enter:
startsrc -s platform_agent
Note: If it is not already running, the CIM server is automatically started by

Platform Agent.
and press Enter:
paservices start
automatically start the Platform Agent services on Linux:
paservices restart
and press Enter:
STRTCPSVR SERVER(*CIMOM)
v If you are running Windows, run the following command:
paservices.vbs start
automatically start the Platform Agent services on Windows:
paservices.vbs restart
3. Obtain the status of Platform Agent to ensure that it started successfully.
press Enter:
lssrc -s platform_agent
v If you are running Windows, go to the Services panel (Start Menu > Settings
> Control Panel > Administrative Tools > Services) and ensure that the
following services are running:
– Platform Agent Cimlistener Service
– Platform Agent SLP SA
– Platform Agent SLP Attributes Service
– Platform Agent WMI+A Service
– Platform Agent Watchdog Service (Platform Agent only)
Related reference:
paservices utility
Platform Agent Watchdog

Platform Agent Watchdog monitors Platform Agent 6.3.x services, such as
cimlistener and cimserver, on Windows, Linux on x86, and Linux Kernel-based
Virtual Machine (KVM).

When Platform Agent Watchdog notices that any monitored services have crashed
or otherwise become useless, it automatically restarts those services.
Note: If you want to stop certain services manually, ensure that you first stop the
Platform Agent Watchdog service.
Platform Agent Watchdog monitors a default set of services that depends on your
operating system:
Services monitored on Windows:
v cimlistener
v gatherwin
v ibmsa
v reposwin
v tier1slp
v wmicimserver
Services monitored on Linux on x86:
v cimlistenerd
v cimserverd
v gathererd
v paslpd
v tier1slpinst
Services monitored on Linux Kernel-based Virtual Machine (KVM):
v cim-listener
v gatherer
v slpd
v tier1slpinst
v tog-pegasus
Setting the agent manager for IBM Systems Director Server

By default, IBM Systems Director is configured to use its embedded agent
manager. However, you can configure IBM Systems Director Server to use a
different agent manager.
You can configure how IBM Systems Director interacts with the common agent
services architecture to secure your Common Agent managed systems and to
improve scalability and performance.
Important: Setting the agent manager incorrectly will prevent IBM Systems
Director Server from communicating with common agents.
Viewing the agent manager properties

Some basic properties of the agent manager can be displayed in the IBM Systems
To view information about the configured agent manager, use the following
procedure:
1. Click Settings > Agent Manager Configuration.
2. Optional: Click the name of a listed agent manager.

The following properties are displayed for agent managers in the IBM Systems
Director Web interface:
Active Whether the agent manager is the active agent manager for IBM Systems
Director Server.
CAS Version
The common agent services version of the agent manager.
IP Address
The IP address of the agent manager.
Name The globally unique identifier (GUID) of the system on which the agent
manager is installed.
Adding a new agent manager

You can configure IBM Systems Director to use additional agent managers in
addition to the default agent manager that is installed with IBM Systems Director
Server.
IBM Systems Director uses only one agent manager at a time; the agent manager in
use is the active agent manager. You can add other agent managers in the Agent
Manager Configuration page, but only the active agent manager is used for
communication with Common Agents.
Note: For descriptions of resource managers and agent managers, see “Common
agent services”.
Use the following procedure to add a new agent manager:

2. In the Agent Manager Configuration page, click Add.
3. In the Add a New Agent Manager window, type the requested information for
the agent manager you are adding, and then click OK.
Agent Manager host name or IP address
The host name or IP address of the agent manager you are adding.
Resource Manager Registration user name
The user name that is used to register IBM Systems Director Server
with the agent manager.
Resource Manager Registration password
The password that is used to register IBM Systems Director Server with
the agent manager.
Agent Registration password
The password that is used to register common agents with the agent
manager.
Catalogue service port
The port that is used for non-secure, or public, communications.
Note: The agent recovery service listens for registration failures on this
port number in addition to port 80.
Make the new agent manager active
If selected, this check box sets the new agent manager as the active
agent manager for IBM Systems Director Server.

Important: Changing the active agent manager in IBM Systems
Director migrates all of the common agents that are registered with the
previously active agent manager to the new active agent manager. This
has two implications:
v Depending on the number of common agents that are registered with
the previously active agent manager, the migration process could
take some time, during which some common agents might not be
available for management by IBM Systems Director.
v After the common agents are migrated to the new active agent
manager, they will no longer be able to be managed by any
management applications (including other installations of IBM
Systems Director) that use the agent manager from which they were
migrated. In order to manage the migrated common agents with
other management applications, the management applications must
be configured to use the new active agent manager.
Related concepts:
“Common agent services” on page 421
Setting the active agent manager

You can set the active agent manager from the Agent Manager Configuration page.
IBM Systems Director uses only one agent manager at a time to communicate with
common agents. This agent manager is the active agent manager. If no agent
manager is active, IBM Systems Director will not be able to manage common
agents.
Important: Changing the active agent manager in IBM Systems Director migrates
all of the common agents that are registered with the previously active agent
manager to the new active agent manager. This has two implications:
v Depending on the number of common agents that are registered with the
previously active agent manager, the migration process could take some time,
during which some common agents might not be available for management by
v After the common agents are migrated to the new active agent manager, they
will no longer be able to be managed by any management applications
(including other installations of IBM Systems Director) that use the agent
manager from which they were migrated. In order to manage the migrated
common agents with other management applications, the management
applications must be configured to use the new active agent manager.
To set the active agent manager, use the following procedure:

2. In the Agent Manager Configuration page, select the agent manager that you
want to activate, and then click Make Active.
3. In the confirmation prompt, click Yes.
Related tasks:
“Managing the agent manager used by a Common Agent” on page 442
Deleting an agent manager

You can remove an agent manager from the Agent Manager Configuration page.
Note: You cannot delete the active agent manager. If you need to delete the active
agent manager, you must first make a different agent manager active.

To delete an agent manager from the Agent Manager Configuration page, use the
following procedure:
2. In the Agent Manager Configuration page, select the agent manager you want
to delete, and then click Delete. The Delete Selected Agent Managers window
prompts you for confirmation.
3. Click OK in the Delete Selected Agent Managers window.
The agent manager is removed from the Agent Manager Configuration page, and
IBM Systems Director Server will no longer use the agent manager to communicate
with common agents.
Deleting an agent manager from the Agent Manager Configuration page does not
uninstall the agent manager or delete any agent manager data.
Using a remote agent manager with IBM Systems Director

There are several reasons why you might want to use an agent manager that is
remote to your IBM Systems Director Server instance instead of the agent manager
that is embedded within it.
For example, if you need to manage the same common agents with more than one
instance of IBM Systems Director Server, all of the instances of IBM Systems
Director Server must use the same agent manager.
Such situations are addressed by configuring one or more of the management

applications to use a remote agent manager, which is the agent manager embedded
in IBM Systems Director Server on a remote system.
Configure IBM Systems Director Server to use an agent manager other than the
locally embedded agent manager if you want to obtain any of the following goals:
v Manage the same common agent services agents with one or more IBM Systems
Director Server instances and one or more Tivoli applications
v Gain partial redundancy by detecting an agent manager failure condition and
then switching to a different agent manager
v Improve performance on IBM Systems Director Server by decoupling the agent
manager workload to a separate system
The agent manager can run under one of the following types of enterprise
application server environments:
IBM WebSphere Application Server
Agent manager can use an existing installation of a supported version of
IBM WebSphere Application Server. The agent manager applications can be
installed in the same application server as your other products, or it can be
in an application server that is dedicated to the agent manager.
lightweight runtime environment
The agent manager applications can be installed in the same lightweight
runtime instance as your other products, or it can use an instance that is
dedicated to the agent manager.
Note: The agent manager that is installed as an embedded component of

IBM Systems Director Server uses the lightweight runtime environment.

Using the embedded agent manager of a remote IBM Systems
Director Server
If your management environment uses IBM Systems Director exclusively, and if
your goal is to manage the same common agents with more than one instance of
IBM Systems Director Server, you can configure multiple instances of IBM Systems
Director Server to use the embedded agent manager of one of your IBM Systems
Director Server instances.
Ensure that you have the following information available before you configure IBM
Systems Director Server to use the agent manager:
v Host name or IP address of the agent manager that you will use
v User name and password of the IBM Systems Director user that you will use to
register IBM Systems Director Server with the agent manager
v Agent registration password that you will use to register common agents with
the agent manager
v Value of the public communications port that the agent manager will use
IBM Systems IBM Systems

Director Server Director Server
Resource manager Resource manager
Embedded agent Embedded agent

manager manager
Common agents
Managing the agent manager used by a Common Agent

A Common Agent managed system can be managed by only one agent manager at
a time. If that agent manager is not the agent manager that IBM Systems Director
uses, you must unregister the Common Agent in order to manage it with IBM
Systems Director.
Use the following procedures to:

v Identify the agent manager that is being used by a Common Agent managed
system
v Unregister the Common Agent from an agent manager, if needed
v Register the Common Agent with the agent manager that is being used by IBM
Systems Director
Notes:

v To manage a common agent with more than one instance of IBM Systems
Director Server, you must register all IBM Systems Director Server instances with
the same agent manager. For this purpose, you can use the agent manager that
is embedded in any of the IBM Systems Director Server instances.
v To manage a common agent with both IBM Systems Director Server and a
different management application, you must register both management
applications with the same agent manager. For this purpose, you can use the
agent manager that is embedded in IBM Systems Director Server.
v An alternative to changing the agent manager that is used by Common Agent is
to configure IBM Systems Director Server to use the agent manager that is used
by Common Agent. Doing so will configure all Common Agent managed
systems managed by that IBM Systems Director Server to use the new agent
manager. See “Setting the active agent manager”.
Related tasks:
“Setting the active agent manager” on page 440
Identifying the agent manager for a Common Agent managed

system
Use one of the following procedures to determine the agent manager for a
Common Agent managed system:
v On the Common Agent managed system: Ensure proper communication
between the Common Agent managed system and the management server, then
issue the following command (all on one line):
or Linux
/opt/ibm/director/agent/runtime/agent/bin/agentcli.sh configurator getConfig

Registration.Server.Host
Windows
install_root\agent\runtime\agent\bin\agentcli configurator getConfig

Registration.Server.Host
where install_root is the root directory of your IBM Systems Director installation.
The IP address of the agent manager is displayed.
v On the management server: Issue the following command (all on one line):
/opt/freeware/cimom/pegasus/bin/slp_query
--type=service:management-software.IBM:usma --address=agent_ip
Linux
If Platform Agent 6.2.1 is installed on the server:

/opt/ibm/icc/bin/slptool options
Where options are the options that you specify based on the information
in the slptool command topic.
Platform Agent 5.20.3x
/opt/ibm/icc/slp/bin/slp_query
Windows
\Program Files\Common Files\IBM\ICC\slp\bin\slp_query

where agent_ip is the IP address of the Common Agent managed system.

The agent manager is identified in the results by either of the following strings:

– manager=am_ip, which indicates that the agent manager is in managed mode,
where am_ip is either localhost or the IP address of the agent manager. For
example, this command might display the following information:
0
1
64
URL: service:management-software.IBM:usma://abcd.ibm.com
ATTR: (ip-address=9.10.11.12@9.10.11.12@192.168.71.82),(mac-address=0.0.4.8.fe.8
0),(tivguid=47FFE92E9BC611DD8E940063C0A84752),(uid=7f2f7642b4550606),(timezone-o
ffset=-360),(version=6.1),(port=9510),(manager=9.10.11.12)
– manager=unmanaged, which indicates that the agent manager is in unmanaged
mode.
Unregistering the agent manager for a Common Agent managed

system
If the agent manager for the Common Agent managed system is not the agent
manager that IBM Systems Director is using, you can unregister the agent manager
by unmanaging the Common Agent managed system with the incorrect agent
manager. You can then discover the Common Agent managed system with the
correct agent manager and set that agent manager as the one that IBM Systems
Director uses. Complete the following steps on the Common Agent managed
system to set is as unmanaged:
1. Issue the following command:
or Linux
install_root/agent/runtime/agent/toolkit/bin/configure.sh -unmanaged -force

Windows
install_root\agent\runtime\agent\toolkit\bin\configure.bat -unmanaged -force

installation.
2. Check the agent manager for the Common Agent managed system using the
procedure described in “Identifying the agent manager for a Common Agent
managed system” on page 443. The agent manager should now be unmanaged.
Registering a Common Agent managed system with the IBM

Systems Director agent manager
Before you register a Common Agent managed system with the IBM Systems
Director agent manager, ensure that the following circumstances exist:
v Ensure that no firewalls are blocking bidirectional communication between the
agent manager and the common agent.
v Ensure that the corresponding GMT times for the common agent and agent
manager are synchronized.
v Ensure that the common agent was not managed by another agent manager that
is not the default agent manager of IBM Systems Director Server.
1. In IBM Systems Director Web interface, remove the Common Agent managed
system if it has not already been removed.
2. Discover the Common Agent managed system.
3. Request access, or run this command to manage the system without requesting
access:
install_root/agent/runtime/agent/toolkit/bin/configure.sh -amhost
agentmanager_IP_address -passwd agentregistration_password -force

installation. The Common Agent managed system is now managed by the

agent manager used by IBM Systems Director. To verify this, use the procedure
described here: “Identifying the agent manager for a Common Agent managed
system” on page 443.
Securing Common Agent managed systems

When IBM Systems Director Server discovers Common Agent managed systems,
those systems are secured by the common agent services architecture. If you
suspect a breach of security, you can re-secure your Common Agent managed
systems to protect them from unauthorized management.
Changing the agent registration password

In some cases you might want to change the agent registration password.
The agent registration password serves these purposes:

v Validating the registration of common agents
v Locking the agentTrust.jks truststore file
To change the agent registration password, you first update the agent manager,
and then redistribute the agentTrust.jks truststore file to unregistered common
agents and to IBM Systems Director Server and any other resource managers that
remotely install common agents.
Use the following procedure to change the agent registration password.

1. Log on to the IBM Systems Director Server or agent manager server as the
user who runs the IBM WebSphere Application Server processes. This is
Administrator on Windows systems. On Linux systems, this is typically root
but can be changed after installing the agent manager.
2. Run the EncryptAMProps script. Type one of the following commands:
Agent manager type Command

Embedded agent manager on AIX or Linux ./install_root/lwi/runtime/agentmanager/
bin/EncryptAMProps.sh new_password
Embedded agent manager on Windows install_root\lwi\runtime\agentmanager\
bin\EncryptAMProps.bat new_password
where
v new_password is the new agent registration password.
v install_root is the root directory of your IBM Systems Director Server
installation. On AIX or Linux, this is typically /opt/IBM/Director. On
Windows, this is typically C:\Program Files\IBM\Director.
This script updates the value of the Registration.Agent.Access.Password
property in the AgentManager.properties file.
3. Start the IBM Key Management utility. Type one of the following commands:

Embedded agent manager on AIX or Linux ./install_root/jre/bin/ikeyman.sh
Embedded agent manager on Windows install_root\jre\bin\ikeyman.exe
where:

4. Open the agentTrust.jks truststore file.
a. In the IBM Key Management window, click Key Database File > Open.
b. In the Open window, set the Key database type to JKS, specify the file
name and location of the agentTrust.jks truststore file, and click OK. The
agentTrust.jks truststore file is located in one of the following directories:
Agent manager type Directory

Embedded agent manager install_root\lwi\runtime\agentmanager\
eclipse\plugins\cas_plugin_name\certs\
where:
Note: The specified directory path uses backslashes. On non-Windows,

systems, substitute forward slashes.
If the agentTrust.jks truststore file is missing or corrupted, you can copy
the agentTrust.jks file from a common agent or resource manager.
However, because the password for the file changes when the common
agent or resource manager registers, you must use the password that
unlocks the file on that system to open the truststore file in step 4c.
c. In the Password Prompt window, type the current agent registration
password and then click OK. The IBM Key Management window now
shows the agentTrust.jks file, which contains the signer certificate named
rootcert.
5. In the IBM Key Management window, click Key Database File > Change
Password.
6. In the Change Password window, enter and confirm the new password that
you specified in step 2 on page 445, and then click OK. The agentTrust.jks
truststore file is encrypted with the new password.
7. Click Key Database File > Exit to close the IBM Key Management window.
8. Redistribute the agentTrust.jks truststore file to any common agent or
resource manager that has not yet registered. If you created a copy of the
agent installation files or created an installed image for rapidly deploying
common agents, copy the new agentTrust.jks truststore file to that location.
Note: You do not need to redistribute the truststore file to common agents
and resource managers that have successfully registered.
9. Update the agent registration password that is stored in an encrypted format
in the endpoint.properties file.
Note: You do not need to change the endpoint.properties file on common

agents that have successfully registered.
To update the saved password, type one of the following commands:

Embedded agent manager on AIX or Linux ./install_root/lwi/runtime/agentmanager/
bin/EncryptPW.sh
agent_registration_password
Embedded agent manager on Windows install_root\lwi\runtime\agentmanager\
bin\
EncryptPW.batagent_registration_password

where:
v agent_registration_password is the new agent registration password.
10. If necessary, redistribute the agentTrust.jks truststore file to any IBM Systems
Director Server instances and any other resource managers that have not yet
registered. Typically, you will not have resource managers that are installed
but not registered.
11. Change the saved agent registration password for any resource manager that
uses it to deploy common agents.
12. Restart IBM Systems Director Server or the agent manager to start using the
new properties file and password.
13. Run the following command on IBM Systems Director Server: smcli
changeAMRegPassword<IPAddress of Agent Manager><New Password>
Note: To obtain the IP address of the agent manager, run smcli

getAgentManagers.
The agent registration password is now changed throughout your deployment.
Migrating common agents to a different agent manager

You can migrate a 6.2.1.2 or later common agent to a different 6.2.1.2 or later
management server.
In the following steps, MS_old is the management server that contains the common
agent that you want to migrate, and MS_new is the management server to which
you want to migrate the common agent.
Complete the following steps to migrate an agent from management server MS_old
to management server MS_new.
1. Ensure that IBM Systems Director Server is installed and running on both
management servers.
2. Complete the following steps to add the agent manager of MS_new to MS_old.
a. In the IBM Systems Director Web interface on MS_old, go to Settings >
Agent Manager Configuration . The Agent Manager Configuration page is
displayed.
b. Click Add to add a second agent manager. The Add a New Agent Manager
window is displayed.
c. Fill out the information for the agent manager of MS_new.
d. Do not select the Make the new agent manager active option.
e. Click OK. The Agent Manager Configuration page is displayed and the
agent manager from MS_new is added to the list of agent managers for
MS_old.
f. Select the newly added agent manager and click Make Active. The agent
manager for MS_new is activated on MS_old.
3. Complete the following steps to add the agent manager of MS_old to MS_new.
a. In the IBM Systems Director Web interface on MS_new, go to Settings >
Agent Manager Configuration . The Agent Manager Configuration page is
displayed.

b. Click Add to add a second agent manager. The Add a New Agent Manager
window is displayed.
c. Fill out the information for the agent manager of MS_old.
d. Do not select the Make the new agent manager active option.
e. Click OK. The Agent Manager Configuration page is displayed and the
agent manager from MS_old is added to the list of agent managers for
MS_new.
f. Select the newly added agent manager and click Make Active. The agent
manager for MS_old is activated on MS_new.
4. On the Agent Manager Configuration page on MS_new, select the agent
manager for MS_new and click Make Active. The original agent manager for
MS_new is activated, and the common agents that were managed with the
agent manager for MS_old are automatically migrated to use the agent manager
for MS_new.
Binding Platform Agent to specific IP addresses

Platform Agent supports multiple network interface card (multi-NIC) IP address
configurations for both Linux and Windows. However, only Windows supports the
act of binding to particular IP addresses for communication. On Linux, Platform
Agent defaults to bind to all interfaces, so there is no option to configure a
particular IP address.
Note: If you change the IP address or host name of any managed resource, either
discover and inventory the resource again or use configuration templates to update
the IP address or host name.
To specify a particular IP address on Windows and avoid binding Platform Agent

to all interfaces by default, complete the following steps:
1. Issue the following command to stop wmicimserver:
net stop wmicimserver
2. Wait until wmicpa stops or issue the following command to force it to stop:
taskkill /F /IM wmicpa.exe
3. Open the wmia.properties file, which is in %Program Files%\Common
Files\IBM\icc\cimom\data\, for editing.
4. Edit the following IPv4 and IPv6 properties as specified:
Table 31. Binding values to set for properties in wmia.properties
Property and value Result
httpBindAddress=IPv4_Address Will bind to IPv4_Address:5988, which is not
secure
httpsBindAddress=IPv4_Address Will bind to IPv4_Address:5989, which is
secure
httpIPV6BindAddress=IPv6_Address Will bind to IPv6_Address:5988, which is not
secure
httpsIPV6BindAddress=IPv6_Address Will bind to IPv6_Address:5989, which is
secure
5. Issue the following command to start the wmicimserver:

net start wmicimserver

Changing the Common Agent IP address
If necessary, you can change the Common Agent IP address.
Under certain circumstances, you might want or need to change a Common Agent
IP address. For example, if you change only the Common Agent host name, the
Common Agent IP address is not automatically also changed. IBM Systems
Director Server uses the new host name and old IP address until Common Agent
or the operating system next restarts. So, you must manually change the Common
Agent IP address.
Conversely, if you change only the Common Agent IP address, the Common Agent
host name is automatically also changed. In this case, IBM Systems Director Server
detects the IP address change, forces a check of the Common Agent host name,
and changes the host name accordingly.
Note: If you change the IP address or host name of any managed resource, either
discover and inventory the resource again or use configuration templates to update
the IP address or host name.
If you do change the Common Agent IP address, keep in mind the following
points:
v You need to restart Common Agent and Platform Agent after you change the
Common Agent IP address. For information about restarting the agents, see
“Restarting agents”.
v In an environment with multiple IP addresses, changing the IP address for
Common Agent might lead to some missing service access points. You can
retrieve the missing service access points by rediscovering, without first
removing, the managed server.
Related tasks:
“Restarting agents” on page 434
Critical services for monitoring Platform Agent hardware

The following services and processes are critical for monitoring Platform Agent
hardware on Windows.
Hardware monitoring stack overview
Platform Agent provides functionality to monitor the hardware of a managed

system. If the state of a monitored hardware component changes, the Platform
Agent WMI+A Service generates an indication that contains the event. The
Windows Management Instrumentation (WMI) CIM handler, which is a component
of the WMI+A Service, forwards the event to the Platform Agent CIM Listener. It
also informs the CIM Listener about the consumers that should receive the
notification of the event. The CIM Listener routes the event to the appropriate
consumer module.
The CIM Listener can send events to the following five consumers:
v SNMP
v Tivoli
v log
v email
Critical services
Windows Management Instrumentation (winmgmt)
This service, which is part of Windows, is the CIM Object Manager for
Windows. The WMI+A Service is a wrapper for the Microsoft service and
is therefore dependent upon it. WMI+A adheres to CIM standards set forth
by the Desktop Management Task Force (DMTF) and leverages Microsoft's
CIM implementation for the Windows platforms.
If this WMI service fails, the WMI+A Service is unavailable and therefore
fails to monitor the hardware.
For more information about WMI, see the MSDN documentation at
http://msdn.microsoft.com/en-us/library/aa394582%28v=vs.85%29.aspx.
If this service needs a recovery, run net stop winmgmt to stop the service,
then run net start winmgmt to restart it.
Platform Agent WMI+A Service (wmicimsv.exe, wmicpa.exe)
The corresponding process for this service is wmicimsv.exe. The process
handles requests and delivers responses to the client. It translates CIM
requests to WMI requests and receives responses from WMI and converts
that to a CIM response.
This service will also bring up several instances of the WMI CMPI
Provider Adapter, wmicpa. The wmicpa process is a WMI provider that
interfaces with IBM Systems Director providers that are written to the
CMPI standard. Instances of wmicpa are the keys to monitoring the
hardware and generating the hardware events. The wmicpa process is an
interface to WMI for CMPI providers and will load CMPI indication
providers. It is these providers that are responsible for monitoring
hardware and generating indications.
Providers that run in processes other than the process in which the CIM
server runs are now supported, so multiple wmicpa processes exist. This
means that, if one wmicpa crashes, others will function. You might lose
any hardware monitoring from the providers loaded by the crashed
wmicpa process.
If this service is stopped or fails to start, the hardware cannot be monitored
and no hardware event is generated. You might lose any hardware
monitoring from the providers that the crashed wmicpa process loaded.
If this service needs a recovery, run net stop wmicimserver to stop the
service, then run net start wmicimserver to restart it.
WMI CIM handler (wmihandl.dll)
WMI CIM handler is a part of the WMI+A Service. It listens for WMI
events and converts those events into CIM indications. Those indications
are then passed on to the CIM Listener Service based on the CIM
subscription.
The wmihandl module is loaded by wmicimsv.exe when the WMI CIM+A
Service starts. If the wmihandl module fails to load for some reason,
indications are not processed and forwarded to the CIM Listener Service.
Therefore, hardware events are not delivered to end consumers such as
If this module has a problem and needs a recovery, recover the WMI+A
Service, because the wmihandl module is loaded by wmicimsv.exe.

Platform Agent CIM Listener Service (cimlistener.exe)
This service receives the hardware event from the WMI CIM handler and
implements the code to deliver the event to end consumers.
If this service fails, the hardware event can be generated, but cannot be
delivered to end consumers.
If this service needs a recovery, run net stop cimlistener to stop the
service, then run net start cimlistener to restart it.
Recover the whole stack
In some situations, you need to recover the whole stack. This happens especially
when you cannot determine which service in the stack is the culprit of the
problem. To recover the whole stack, you need to restart all services in the stack,
and the order of stopping and starting the services matters.
Steps to stop all services
1. Run the following command to stop the Platform Agent CIM Listener
Service:
net stop cimlistener
2. Run the following command to stop the WMI CIM handler and
Platform Agent WMI+A Service:
net stop wmicimserver
3. Run the following command to stop Windows Management
Instrumentation:
net stop winmgmt
Steps to restart all services
1. Run the following command to start Windows Management
Instrumentation:
net start winmgmt
2. Run the following command to start the WMI CIM handler and
Platform Agent WMI+A Service:
net start wmicimserver
3. Run the following command to start the Platform Agent CIM Listener
Service:
net start cimlistener
Configuring Platform Agent for SELinux policies

You can configure Platform Agent on Red Hat Enterprise Linux to work with
SELinux in permissive or enforcing mode.
IBM Systems Director supports the use of SELinux policies with Platform Agent on
Red Hat Enterprise Linux 6.2 or 6.3. SELinux is disabled by default, so you need to
set it to the desired mode and then configure Platform Agent to work with it.
Complete the following steps to configure Platform Agent to work with SELinux
policies.
1. Run the following command to enable SELinux in permissive mode.
Note: If SELinux is already set to permissive mode and you want to set it to
enforcing mode, you can skip this step.
/opt/ibm/platform/bin/selinux/./dir_pa_setup_policy -permissive

If SELinux was not already set to permissive mode, this command will set the
SELINUX variable in the /etc/selinux/config file to permissive. The system
then reboots.
2. If enforcing mode is needed, run the following command to enable SELinux in
enforcing mode.
Note: SELinux must be set to permissive mode before you can set it to
enforcing mode.
/opt/ibm/platform/bin/selinux/./dir_pa_setup_policy -enforcing
If SELinux was not already set to enforcing mode, this command will set the
SELINUX variable in the /etc/selinux/config file to enforcing. The system
then reboots.
3. Verify that the correct SELinux mode is set.
v Run the following commands to determine the current runlevel and then
verify that the service is properly enabled in it:
runlevel
chkservice
v Run the following command and ensure that the installed policy appears in
the returned list to verify that the policy was properly loaded:
semodule -l
v Run the following command to verify that the system's SELinux status is set
to enabled and that its current mode is properly set to the desired value of
either permissive or enforcing:
sestatus
Disabling IBM Systems Director agents

Certain situations might require that you disable Common Agent or Platform
Agent on AIX.
To permanently disable Common Agent and Platform Agent on AIX, complete the
following steps:
1. Enter the following commands to stop and permanently disable the common
agent:
/opt/ibm/director/agent/runtime/agent/bin/endpoint.sh stop
/opt/ibm/director/agent/runtime/nonstop/bin/installnonstop.sh -uninstallservice
2. Enter the following command to stop the platform agent:
stopsrc -s platform_agent
3. Comment out the following line in the /etc/inittab file to permanently disable
the platform agent:
platform_agent:2:once:/usr/bin/startsrc -s platform_agent >/dev/null 2>&1
4. If there are no other applications depending on the cimserver, enter the
following command to stop the cimserver:
stopsrc -s cimsys
5. Comment out the following line in the /etc/inittab file to permanently disable
the cimserver:
cimservices:2:once:/usr/bin/startsrc -s cimsys >/dev/null 2>&1

Chapter 10. Managing IBM BladeCenter, IBM Flex System
Manager compute nodes and System x systems
IBM Systems Director provides specific tasks that can help you manage IBM
BladeCenter, IBM Flex System Manager, and System x systems.
Service processor communication

Hardware-based service processors, also known as management processors, work
with hardware instrumentation and systems management software and are
important for problem notification and resolution. You also can use them to
remotely manage your system. In an IBM Systems Director environment, service
processors send alerts to IBM Systems Director Server when error conditions occur
in a specific system; these alerts help you to managed your environment
effectively.
There are two pathways along which communication between IBM Systems
Director Server and the service processors present in scalable System x and xSeries
servers takes place: in-band communication and out-of-band communication.
In-band communication requirements

IBM Systems Director Server can communicate in-band with service processors in
systems that are running the required IBM Systems Director agent.
To enable in-band communication between IBM Systems Director Server and a

system that contains a service processor, the system must meet the following
criteria:
v One of the following agents must be installed:
– For Remote Supervisor Adapter, Remote Supervisor Adapter II, or Integrated
Systems Management Processor
- IBM Director Agent, version 5.20.3
– For all other Service Processors:
- Common Agent version 6.x or Level 2: IBM Director Agent, version 5.20.3
- Platform Agent 6.1.x (or later).
Note: Common Agent 6.1.1 supports systems running Platform Agent 6.1.x.
For more information, see “Installing.”
v The service-processor device driver must be installed, and possibly a shared
library to access the device driver. For more information, see “Preparing to
manage service processors with IBM Systems Director.” These agents use a
device driver to pass data to and from the service processor.
After these criteria are met, IBM Systems Director Server can discover the system
and you can request access to the system.
IBM Systems Director supports in-band communication for these service

processors:
v IPMI baseboard management controller (BMC)
v Remote Supervisor Adapter IBM Systems Director Server
v Remote Supervisor Adapter II
v Integrated system management processor (ISMP)
v Integrated Management Module (IMM)

Note: You can use only out-of-band communication with management modules.
Related concepts:
Out-of-band communication requirements
Service processors and resource types
Standard TCP Command Mode protocol
Related tasks:
Preparing to manage service processors with IBM Systems Director
Installing IBM Systems Director

Related reference:
Out-of-band alert-forwarding strategies

Data is transmitted between the service processor and IBM Systems Director Server
over a shared connection. The type of service processor present in a server
determines which paths out-of-band communication can take. These types of
communication are known as out-of-band communication because they take place
independent of an operating system.
To enable out-of-band communication between IBM Systems Director Server and a

service processor or management module, the following criteria must be met:
v You must configure the service processor or management module with a valid IP
address. For service processors, set the IP address using the Basic Input/Output
System (BIOS) of the server in which the service processor is installed. For
management modules, configure the IP address using crossover cables or the
Dynamic Host Configuration Protocol (DHCP) to maintain consistent IP
addresses for the service processors. For more information, see the appropriate
documentation:
– IBM Remote Supervisor Adapter User's Guide at http://www.ibm.com/systems/
support/supportsite.wss/docdisplay?lndocid=MIGR-4TZQAK
&brandind=5000008
– IBM RSA II SL and RSA II User's Guide, at http://www.ibm.com/systems/
support/supportsite.wss/docdisplay?lndocid=MIGR-57091
&brandind=5000008
– For machine types that include the Intelligent Peripheral Management
Interface (IPMI) baseboard management controller (BMC) and are not blade
servers, the System x hardware documentation
– For IBM BladeCenter products, the management module documentation
– User's Guide for Integrated Management Module from the Integrated
Management Module (IMM) messages - System x page (http://www-
947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-
5079339&brandind=5000008).
v IBM Systems Director Server must discover the server. In System Discovery,
provide the IP address for the service processor or management module.
Note: IBM Systems Director Server also can automatically discover the service
processor IP address that is used for out-of-band communication if you request
access to an agent that is supported by IBM Systems Director and is installed on
the system containing the service processor. For discovery to succeed, the service
processor device drivers must be installed correctly. For more information about
these agents and device drivers, see “In-band communication requirements.”
v The service processor or management module IP address can change only in the
following situations:

– Using the Configuration Templates task and the applicable templates: Service
Processor Network IP Configuration or the Management Module Network IP
Configuration
– Using the applicable Web interface for the service processor or management
module
In either of these situations, if events are configured correctly, when you change
the IP address an event is generated that updates the IP address information for
IBM Systems Director. For information about incorrect configuration, see
“Out-of-band events are not configured correctly.”
Data is transmitted between the service processor and IBM Systems Director Server
over a shared connection. The following shared connections can be used:
v A local area network (LAN), if the service processor has an integrated network
interface card (NIC) or access to a NIC shared with the server.
v An interconnect gateway. With this type of connection, data is passed from the
service processor to a second service processor. The second service processor
serves as a gateway between IBM Systems Director Server and the first service
processor.
Management modules communicate with IPMI BMC on blade servers by using
an interconnect gateway.
The following table lists the pathways that are available for out-of-band
communication:
Table 32. Out-of-band communication pathways
Pathways for out-of-band Possible gateway service processors if an
Type of service processor communication interconnect network is chosen
Management module LAN Not applicable
Advanced management module
IPMI BMC v LAN v Management module
v Over an interconnect network v Advanced management module
v Integrated management module
Remote Supervisor Adapter v LAN v Remote Supervisor Adapter
Remote Supervisor Adapter II v Over an interconnect network v Remote Supervisor Adapter II
ISMP1 Over an interconnect network v Remote Supervisor Adapter
v Management module
v Advanced management module
Integrated management module LAN Integrated management module
Integrated management module II Integrated management module II
1
Although the service processor in the eServer 325, 326, and 326m models is called an ISMP, it is a BMC. Use the
BMC information for this service processor.
See the documentation that came with the server for information about configuring
your service processor and interconnect network to ensure that IBM Systems
Director Server receives system alerts.
Notes:
1. For systems that do not have an integrated management module (IMM), only
the following systems management application can communicate with a service
processor:
Chapter 10. Managing IBM BladeCenter, IBM Flex System Manager compute nodes and System x systems 455
Advanced management modules with firmware version BPET23A or later are
an exception. They can be configured to permit multiple simultaneous
connections. For more information, see “Out-of-band communication and the
TCP Command Mode protocol.”
2. Not all scalable IBM System x and xSeries servers are supported by the
RXE-100 Remote Expansion Enclosure. If one of the following servers is
attached to an RXE-100 Remote Expansion Enclosure, you cannot use the
on-board Remote Supervisor Adapter as a gateway service processor:
v xSeries 360
v xSeries 365
v xSeries 440
v xSeries 445
v xSeries 455
The Remote Supervisor Adapter is dedicated to managing the RXE-100 Remote
Expansion Enclosure.
Related concepts:
Related reference:
Out-of-band events are not configured correctly
Out-of-band communication and the standard TCP Command

Mode protocol
IBM Systems Director Server can communicate out-of-band with service processors
and management modules using the standard TCP Command Mode protocol.
The following IBM service processors and management modules use the standard
TCP Command Mode protocol for communication:
v Management module
v Remote Supervisor Adapter
Advanced management modules also can communicate using the secure TCP
Command Mode protocol. For more information, see “Out-of-band communication
and the secure TCP Command Mode protocol.”
IBM Systems Director Server uses the standard TCP Command Mode protocol to
communicate with these service processors and management modules. Other IBM
programs use the standard TCP Command Mode protocol to communicate with
service processors and management modules also, for example:
v UpdateXpress
v Cluster Systems Management
v Active Energy Manager (Standalone edition)
When connecting to the advanced management mode through TCP command

mode, the ID used to connect to the advanced management module must be the
same ID that was used to unlock the system. To change the ID used to connect to
the system, follow these steps:
1. Revoke access to the system.

2. Request access to the system using the new user ID.
If IBM Systems Director Server cannot communicate with the service processor or
management module, it can cause problems with that system. You might get errors
such as these:
v Access requests fail
v Inventory collection fails
v Configuration manager fails to deploy plans or templates
If you use another program in your systems-management environment that

communicates using the standard TCP Command Mode protocol, close that
program so IBM Systems Director Server can use the connection to the service
processor or management module.
Important: Do not disable the standard TCP Command Mode protocol unless you
are changing the setting on an advanced management module that supports the
secure TCP Command Mode protocol and you are enabling that protocol.
If the affected system uses an advanced management module, you can increase the
number of connections permitted when using the standard TCP Command Mode
protocol. Log into the advanced management module Web interface and view the
Network Protocols page. On this page, the TCP Command Mode section provides
a setting that you can change to increase the number of connections. This setting is
available only for advanced management modules. The default setting for the
number of connections permitted can vary depending on the firmware version
installed. Check the TCP Command Mode section to determine the current default
setting.
Related tasks:
Revoking access to a secured system
Out-of-band communication and the secure TCP Command

Mode protocol
IBM Systems Director Server can use the secure TCP Command Mode protocol to
communicate with advanced management modules with firmware version 4.5 or
later. Other IBM programs, such as Active Energy Manager (Standalone edition),
can use the secure TCP Command Mode protocol to communicate with advanced
management modules also.
IBM Systems Director Server can connect to advanced management modules using
either the secure or standard TCP Command Mode protocol, but not both at the
same time. By default, IBM Systems Director Server tries to use the secure TCP
Command Mode protocol. If secure TCP Command Mode is not enabled on the
advanced management module, IBM Systems Director Server uses the standard
TCP Command Mode protocol.
To change the preference of using the secure TCP Command Mode protocol first,
1. Navigate to the install_root/lwi/runtime/data/asmDefinitions.properties file,
2. Edit the file and change the following setting to false:
mm.stcm.precedence = false
On the advanced management module, either standard TCP Command Mode

protocol or secure TCP Command Mode protocol must be enabled. You can enable
both protocols; however, do not disable both protocols. By default, advanced
management modules are enabled to use the standard TCP Command Mode
protocol. To enable the secure TCP Command Mode protocol, log in to the
advanced management module Web interface and view the Network Protocols
page. On this page, the TCP Command Mode section provides a setting to enable
the protocol.
Advanced management modules can support a maximum of 20 TCP Command

Mode protocol connections at a time. This includes both secure and standard
connections.
When connecting to the advanced management mode through secure TCP

command mode, the ID used to connect to the advanced management module
must be the same ID that was used to unlock the system. To change the ID used to
connect to the system:
2. Request access to the system using the new user ID.
Related tasks:
Out-of-band communication and the standard CIM protocol

IBM Systems Director Server can use the DMTF standard CIM-XML protocol to
communicate with integrated management modules.
Other IBM programs, such as these, also use the standard CIM-XML protocol to
communicate with integrated management modules:
v UpdateXpress
v Cluster Systems Management
By default, service processors are enabled to use the standard CIM protocol. When
connecting to the service processors through CIM, the ID used to connect to the
service processors is the same ID that was used to discover and unlock the system.
To change the ID used to connect to the system, follow these steps:
2. Use the other user ID to request access to the system.
When IBM Systems Director Server cannot communicate with the service
processor, you might have problems with that system, for example, access requests
might fail.

System x and xSeries service processors provide out-of-band support for
alert-forwarding strategies. The type of service processor determines the type of
alert-forwarding strategy that is available.
The following table contains information about possible alert-forwarding strategies.

Table 33. Out-of-band alert-forwarding strategies
Type of service processor Possible alert-forwarding strategies
Intelligent Peripheral Management Interface IPMI Platform Event Traps
(IPMI) baseboard management controller
(BMC)
Management module v IBM Systems Director comprehensive
Advanced management module v IBM Systems Director over modem
v SNMP over LAN
Remote Supervisor Adapter v IBM Systems Director comprehensive
Remote Supervisor Adapter II v IBM Systems Director over LAN
v IBM Systems Director over modem
v SNMP over LAN
v SNMP over point-to-point protocol (PPP)
v E-mail over LAN
v E-mail over PPP
v Pager (numeric or alphanumeric)
Integrated management module CIM Indications
Note: Newer service processors do not use IBM Systems Director over LAN. This
alert-forwarding strategy was replaced by IBM Systems Director comprehensive.
When both strategies are available, it is recommended that you use IBM Systems
Director comprehensive also.
Related concepts:
Out-of-band event monitoring in a redundant environment

A redundant environment helps you minimize enterprise downtime. If you are
using a redundant environment with IBM Systems Director, you can have two
Systems Director servers monitoring Out-of-Band IMM events.

Any System x server and BladeCenter unit that has a supported service processor
or management module can forward events to IBM Systems Director Server. When
IBM Systems Director Server generates event types in response to an event, the
target system of the specific event type can vary.
Note: If IBM Systems Director cannot determine the system type for any service
processor notification, IBM Systems Director identifies the source of the notification
using the IP address of the service processor that sent the notification to IBM
Systems Director Server. For example, this method might be used if a system is
configured to send notifications to IBM Systems Director Server, but IBM Systems
Director Server currently does not have a system type representing that system.
The following table lists the service processor type and its associated target
resource type.
Service processor type Target resource type
v Management module BladeCenter chassis

Systems with one of the following service Server
processors:
v Intelligent Peripheral Management
Interface (IPMI) baseboard management
controller (BMC)
v Integrated system management processor
(ISMP)
v Integrated management module II
Related concepts:
Related reference:
Viewing the management summary

You can view a summary of all management and configuration activity that is
associated with and x86-based and x64-based System x servers, including the
number of systems that are already discovered, have problems, and require
updates. It also provides information about required I/O module plug-ins.
Information on the summary page is refreshed automatically when there are any
changes.
To view the summary, complete the following steps:

2. Click the Plug-ins tab.
3. On the Plug-ins tab, scroll to the Chassis or System x section of the page and
click the section heading. The Chassis or System x management summary is
displayed.
4. Click the question mark (?) for help in understanding the information and links
provided.
Related concepts:
eLearning: Managing blade servers with IBM Systems Director

Related tasks:
Finding a task
Downloading and activating I/O module plug-ins

Obtain available plug-ins for chassis I/O modules to manage your device
configuration in IBM Systems Director.

Note: Before you complete this task, verify that the plug-in is available on the IBM
Systems Director Downloads web page under the “Partner plug-ins” section
(http://www.ibm.com/systems/software/director/downloads/integration.html). If
the plug-in is not available, do not complete this task. Contact IBM software
support.
To download and activate I/O module plug-ins, complete the following steps:
2. Click the Plug-ins tab.
3. On the Plug-ins tab, scroll to the Chassis section of the page and click the
section heading. The Chassis management summary is displayed.
4. In the Setup Additional Configuration Plug-ins section, click View I/O
module plug-ins. The I/O Module Plug-ins page is displayed.
5. View the I/O module plug-ins status in the table and determine which plug-ins
you want for your environment. The following values are available for the
Status column:
Not required
An I/O module plug-in is installed, but there currently is no
discovered switch that requires the plug-in.
Required – Not installed
An I/O module plug-in that is required by a discovered switch is not
installed.
Required – Installed with Errors
An I/O module plug-in that is required by a discovered switch is
installed, but the plug-in code cannot be loaded by the I/O module.
Required – Activation required
An I/O module plug-in that is required by a discovered switch is
installed without any error, but it is not registered with the
configuration manager plug-in. Registration activates the corresponding
switch features in configuration manager.
Active An I/O module plug-in that is required by a discovered switch is
installed without any error and is registered with the configuration
manager plug-in. Registration activates the corresponding switch
features in configuration manager.
6. Click Download Plug-ins. The website opens in a new window.
7. Locate and download the I/O module plug-ins that are required.
8. Manually install the downloaded plug-ins on the IBM Systems Director server.
For installation instructions, see the documentation for the plug-in.
9. Click Activate Installed Plug-ins. IBM Systems Director scans the newly
installed files for the I/O module plug-ins and activates the plug-ins. The
status for each plug-in is updated in the Status column.
Configuring integrated management modules

You can use configuration manager to configure most settings for integrated
management modules. However, some configuration tasks are currently not
supported.
For information about how IBM Systems Director communicates to the IMM using
LAN over USB to interface the IMM, see this topic in the IBM BladeCenter
information center: Using LAN over USB to interface the IMM.
Integrated management module task support and features
IBM Systems Director provides task support for integrated management modules.
However, a few tasks are not supported and you must use workaround support.
The following table lists configuration tasks that this version of IBM Systems
Director does not support for integrated management modules. The table also
observes alternate ways to provide the support to integrated management
modules.
Table 34. Affected configuration tasks and available workaround support
Affected configuration tasks Workaround support
SNMP configuration in configuration Configure SNMP using the
manager management-module web interface
SMTP configuration in configuration Configure SMTP using the
manager management-module web interface
Ports configuration in configuration manager Configure ports using the
does not provide network port reassignment management-module web interface
settings
Enhanced user login security configuration Configure security using the
is not provided in configuration manager management-module web interface
Service Processor configuration support
Service Processor configurations are not supported on IMM endpoints. Therefore,

those configurations are not shown for the IMM endpoint when getting the current
configuration. Additionally, you cannot deploy Service Processor configurations on
IMM endpoints.
Secure Socket Layer support
Integrated management modules support both secure socket layer (SSL) and
unsecure socket layer. By default, SSL is not enabled. If SSL is enabled, IBM
Systems Director will use SSL.
Configuring dynamic UEFI settings

You can configure the UEFI settings for your IMM-managed System x systems. The
available settings change dynamically, depending on the system selected. When
you change the settings, you can deploy them to a system, or save them as a
configuration template or configuration plan.
Notes:
v When you deploy these settings, they replace all of the UEFI configuration
settings on the system. If a setting is left blank, after deployment, the
corresponding value is blank on the system.
v Most settings do not take effect until after the system is restarted.
v The available settings vary by system.
v If you save these settings as a template or plan, they can be deployed to only
the same type of system.
To configure the UEFI settings for a system, follow these steps:

1. Select a System x server that is managed by IMM.
a. From Resource Explorer, expand All Systems.

b. Click the name of a System x server to open the Properties page.
c. On the General tab of the Properties page, look at the value for
Management Controller Type. If the value is Integrated Management
Module or Integrated Management Module II, the server is managed by
either an IMMv1 or an IMMv2.
2. On the Configuration tab of the Properties page, select Dynamic UEFI
Configuration, then click Edit. The UEFI settings are displayed.
Note: After you click Edit, it can take up to 3 minutes for the settings to load.
3. Click a group name to access the settings in that group. To change a setting,
click the setting name and specify the new value in the window that opens.
4. Save the new UEFI settings:
v To deploy the settings and save them as a configuration template or
configuration plan, complete the following steps:
a. Click Deploy.
b. After the task completes, return to the Configuration tab that you
accessed in step 2
c. Select Dynamic UEFI Configuration, then click Save as Configuration
Template or Save as Configuration Plan, as appropriate.
v To save the settings as a configuration template that is deployed to the
system later, complete the following steps:
a. Click Save As. The Save as Configuration Template window displays.
b. Complete the Save as Configuration Template window, then click Save.
The new UEFI settings are saved as a configuration template with the
name that you specified.
Note: The modified settings are not deployed to the system. You must
deploy them later.
Changing the integrated management module IP address by

way of the server resource
You can change the integrated management module IP address by way of the
server resource by using IBM Systems Director.
To change the IP address, complete the following steps:

1. In the IBM Systems Director Web interface, use the System discovery task to
discover the integrated management module by specifying its IP address. For
detailed information about discovery, see “Discovering systems with system
discovery.” After you discover the integrated management module, the
associated server resource is displayed in the IBM Systems Director Web
interface.
2. Request access to the server resource.
3. In configuration manager, create the Network Configuration (via CIM protocol)
template. For more information, see “Creating configuration templates.”.
4. In configuration manager, create the “Service Processor Network IP
Configuration” template. For more information, see “Configuring the network
IP for a System x service processor.”
5. Apply the template to the applicable server resource.
The server resource temporarily loses connectivity, but uses the new IP address
when it goes online.
Related tasks:
Creating configuration templates
Configuring the network IP for a service processor
Changing the network port on an integrated management

module
You can change the network port on an integrated management module by using
IBM Systems Director and the IBM management-module web interface.
To change the network port, complete the following steps:

interface.
2. In a web browser, access the management-module web interface by using the
IP address of the integrated management module.
3. Use the management-module web interface to log in to the integrated
management module.
4. Use the management-module web interface to change the applicable network
port settings.
The server resource temporarily loses connectivity during the system restart. When
the system is online again, the server resource uses the new port.
Related tasks:
Configuring integrated management module security

You can configure security for an integrated management module by using the
management-module web interface.
To configure security, complete the following steps:

management module.
3. Use the management-module web interface to set the advanced user security
settings.
The advanced user security is applied to the login profiles.
Configuring the Try DHCP setting for integrated management

module
You can configure the Try DHCP, and if that fails use static IP setting for an
integrated management module by using IBM Systems Director and the
management-module web interface.
To configure security, complete the following steps:

interface.
management module.
4. Use the management-module web interface to configure the Try DHCP, and if
that fails use static IP setting.
The server resource temporarily loses connectivity during the system restart. When
the system is online again, the server resource uses the new IP address.
Related tasks:
Enabling Secure Sockets Layer after discovery

You can enable Secure Sockets Layer (SSL) for the integrated management module
after you discover the resource in IBM Systems Director.
To enable SSL, complete the following steps:

interface.
2. In the IBM Systems Director Web interface, request access to the integrated
management module. IBM Systems Director communicates with the integrated
management module by using unsecured sockets layer.
management module.
5. Use the management-module web interface to enable SSL and generate a
self-signed certificate.
IBM Systems Director communicates with the integrated management module by

using SSL.
Related tasks:
Enabling Secure Sockets Layer before discovery

You can enable Secure Sockets Layer (SSL) for the integrated management module
before you discover the resource in IBM Systems Director.
To enable SSL, complete the following steps:

management module.
3. Use the management-module web interface to enable SSL and generate a
self-signed certificate.
4. To apply the settings, restart the system that contains the integrated
management module. In the IBM Systems Director Web interface, right-click the
system, then select Power On/Off > Restart.
interface.
6. In the IBM Systems Director Web interface, request access to the integrated
management module.
IBM Systems Director communicates with the integrated management module by

using SSL.
Related tasks:
Discovering scalable systems that have multiple nodes

Scalable (multiple node) systems can be discovered by using out-of-band support
(OOB) or inband support. Follow the steps in the appropriate topic to discover
your scalable system that has multiple nodes.
Discovering a scalable BladeCenter system with multiple

nodes
Before you can use your BladeCenter system with multiple nodes, you need to
discover it by using out-of-band and in-band communication. A scalable system
with multiple nodes is called a complex. Follow these steps to discover the system.
Before you begin
Access the Advanced Management Module (AMM) web console and verify that
the system has been configured correctly.
1. From the AMM web console, go to Scalable Complex > Configuration.
2. Find the appropriate system in the “Assigned Nodes” section. The value for
Mode must be Partition.
3. Correct the configuration, if necessary.
1. Use out-of-band communication to discover the system.
Important: If you do not complete these steps, the complex is not created.
a. Discover the BladeCenter chassis by using the AMM IP address. On the
System Discovery page, select BladeCenter as the resource type. Do not
select All.
b. Request access to the BladeCenter you just discovered. When the access
state of nodes are changed to “OK”, discovery is complete.
c. Verify that the access state for the complex and partition is “OK”.
2. Use in-band communication to discover the system.

Important: If you do not complete these steps, the operating system will not
work correctly.
a. Discover the IP address of operating system running on the partition on
which the platform agent is installed.
b. Request access to the managed resource on which the operating system is
installed.
3. Request access to the BladeCenter.
Discovering a scalable System x system

Before you can use your System x system with multiple nodes, you need to
discover it by using out-of-band and in-band communication. A scalable system
with multiple nodes is called a complex. Follow these steps to discover the system.
Before you begin
Access the Integrated Management Module (IMM) web console and verify that the
system has been configured correctly.
1. From the IMM web console go to Scalable Partitioning > Manage Partition(s).
2. Verify that these values are shown for the system:
Table 35. Values for a correctly configured system
System Partition Mode
Started Valid Multinode
3. Correct the configuration, if necessary.

1. Use out-of-band communication to discover the system.
Important: If you do not complete these steps, no relationship between the

node and partition is created.
a. Discover and request access to one node. The complex and partition are
created, but the access state of partition is “Partial access”.
b. Discover and request access to the other node. The access state of the
partition changes to “OK”.
2. Use in-band communication to discover the system.
Important: If you do not complete these steps, the operating system will not
work correctly.
a. Discover the IP address of operating system running on the partition on
which the platform agent is installed.
b. Request access to the managed resource on which the operating system is
installed.
3. Request access to the System x server.
Changing the password for the Remote Supervisor Adapter or

management module
You can change the password that you use to access a Remote Supervisor Adapter,
Remote Supervisor Adapter II, or management module.
Note: Integrated management module does not support changing passwords.
You must have access to the system to change the password. For information about
requesting access to a system, see “Requesting access to a secured system.”
To change the password, complete the following steps:

Explorer.
2. Navigate to the system that contains the Remote Supervisor Adapter, Remote
Supervisor Adapter II, or management module on which you want to change
the password.
3. Select the system. To change the password, you must select the system resource
representation of type Server, not Operating System.
4. Click Actions > Change Password.
5. In the Change Password window, type your user name, the old password, the
new password, and then confirm the new password.
6. Click OK.
The password is changed and a confirmation message is displayed.
Enabling hardware events

In order for IBM Systems Director to receive hardware events (or alerts) from IBM
System x and xSeries servers, the server must have an IPMI baseboard
management controller (BMC), a Remote Supervisor Adapter II, an Integrated
Management Module, or an Integrated Management Module II. When a system
has both a BMC and a Remote Supervisor Adapter II installed, IBM Systems
Director ignores the BMC.
Receiving hardware events from your server is called in-band communication. If you
want to enable Common Agent or Platform Agent for in-band communication, you
must install the appropriate software. Before you do so, you must answer the
following questions for each server in your system-management environment:
v What is the server model?
v Does the server include a BMC?
v Does the server include a Remote Supervisor Adapter II?
v Does the server include an Integrated Management Module or an Integrated
Management Module II?
v What operating system is installed on the server?
Your answers to these questions determine the software that you must download
and install on your systems.
If the server has a BMC only:
You must download and install the following applicable software.
Attention: The following software is specific to server models and

operating systems. Your server might not require some of this software.
Make sure that you download the correct software and device drivers for
your server model and operating system.
v The latest BIOS firmware update for the server model
v The latest firmware for the BMC
v The OSA IPMI device driver
v The IBM Mapping Layer software for OSA IPMI

v All of the latest device drivers for your operating system, including, but
not limited to, network, video, and USB device drivers. These device
drivers can affect the service processor. Also, out of date video device
drivers can cause Java exceptions.
v Any critical updates that might be available for that server
Note: The IPMI subsystem in a server consists of the BMC (the hardware
controller for the IPMI subsystem), sensors, buses, other controllers, and a
protocol for communication. The OSA IPMI device driver communicates
with all controllers in the IPMI subsystem.
If the server has a BMC and a Remote Supervisor Adapter II:
When a Remote Supervisor Adapter II is installed, IBM Systems Director
ignores the BMC. See the instructions for a server that has a Remote
Supervisor Adapter II.
If the server has a Remote Supervisor Adapter II or Remote Supervisor Adapter:
You must download and install the following software.

v The latest BIOS firmware update for the server model
v The latest Remote Supervisor Adapter II firmware
drivers can affect the service processor.
v If the server has a BMC, the OSA IPMI device driver. This driver is
required if you want to update the BMC firmware using the Software
Distribution task.
If the server has an Integrated Management Module or an Integrated
Management Module II:
You must download and install the following applicable software.

v The latest BIOS or UEFI firmware update for the server model
v The latest firmware for the Integrated Management Module or the
Integrated Management Module II
drivers can affect the service processor.
To make sure that you download and install all of the latest drivers and software
for your server, print out the Downloads and drivers list from the IBM Support
website. Use this page as a check list to make sure that you have the latest BIOS,
firmware, and device drivers. Complete the following steps:
1. Go to the IBM Support website at www.ibm.com/servers/eserver/support/
xseries/index.html.
2. In the Product family list, select your server model.
3. In the Type list, select the type if applicable.
4. In the Model list, select the model if applicable.
5. In the Operating system list, select your operating system installed on that
server.
6. Click Go.
7. Print the Software and device drivers Web page to use as a check list. You
might have to print more than one page.
Managing power state settings on IBM BladeCenter and System x

servers
Support for the Power On/Off task is provided by System x service processors and
IBM BladeCenter management modules that can communicate out-of-band, and by
servers that have the Wake on LAN feature enabled. The available power settings
vary, depending on the feature that IBM Systems Director uses on the affected
system.
Related reference:
rpower command
Power On/Off task support using out-of-band communication

These service processors support Power On/Off by using out-of-band
communication on System x servers, including scalable servers.
v Intelligent Platform Management Interface (IPMI) baseboard management
controller (BMC)
v Integrated Management Module (IMM)
v Integrated Management Module II (IMM2)
You can use the Power On/Off task to power on and power off scalable partitions
on scalable System x servers. Scalable partitions are systems that are the logical
equivalent of a physical platform. For example, when you choose to power on a
scalable partition, you do so through out-of-band communication with the service
processor in the primary node. Then, all the nodes (servers) that are part of the
scalable partition are powered on and the operating system is started on the
scalable partition. If Common Agent or Platform Agent is installed on the scalable
partition, it is started also.
Note: On scalable partitions, the service processors provide support for Power On,
Power Off Now, and Restart.
Table 36. Service processor support for power settings
Service processor Supported power settings
Blade servers that have an IPMI baseboard Power On, Restart Now, and Power Off
management controller Now
Blade servers that have an H8 controller Power On and Power Off Now
IMM Power On, Restart Now, and Power Off
Now
IMM2 Power On, Restart Now, Power Off Now,
Restart, and Shut Down and Power Off
IPMI baseboard management controllers in Power On, Restart Now, and Power Off
servers that are not blade servers Now

Table 36. Service processor support for power settings (continued)
Service processor Supported power settings
Remote Supervisor Adapter II Power On, Restart Now, and Power Off
Now
Remote Supervisor Adapter Power On, Restart Now, and Power Off
Now
For information about enabling out-of-band communication, see “Out-of-band

communication requirements.”
Related concepts:
Wake on LAN support
Operating system support
Related tasks:
Changing the power state on System x and BladeCenter hardware
Power On/Off task support using Wake on LAN technology on

System x
Some System x servers provide support for the Power On/Off task using Wake on
LAN technology. Wake on LAN technology provides Power On only.
In order to use power management provided by Wake on LAN technology, the

following criteria must be met:
v The system must include a network interface card (NIC) that can use Wake on
LAN technology.
v The system must be running an operating system that supports the Wake on
LAN feature. Wake on LAN is supported on 32-bit and 64-bit versions of
Windows and Linux, but not by VMware ESX Server or Microsoft Virtual Server.
v The Wake on LAN feature must be enabled.
v IBM Systems Director Server must be able to detect the MAC address of the
managed system.
v The system data (including the MAC address) must be included in IBM Systems
Director inventory tables.
Note: The Wake on LAN Power On command does not report failure or success.
To determine whether this command worked, you must verify that the affected
system was powered on as expected.
Related concepts:
Out-of-band support
Related tasks:
Power On/Off task support by way of the operating system on

System x and blade servers
Support for the Power On/Off task can be provided by the operating system on
System x and blade servers. Either Platform Agent or Common Agent must be
installed on the system also.
See the following table for more information.
Table 37. Power-state-setting support by operating systems running on System x servers;
IBM and third-party x86-based systems
Operating system Supported power settings
1
Windows (32-bit and 64-bit versions) Restart and Shutdown
1
Linux (32-bit and 64-bit versions) Restart
VMware GSX Server, versions 3.1 and 3.2, v (For Linux) Restart
guest operating systems v (For Windows) Restart and Shutdown
Microsoft Virtual Server (guest operating Restart and Shutdown
system)
1: If the server that the operating system runs on is also discovered and managed by OOB
means, the servers power tasks are mapped in the operating systems managed endpoint.
Therefore, more power tasks are supported for such operating systems.
Related concepts:
Out-of-band support
Wake on LAN support
Related tasks:
Changing the power state on System x and IBM BladeCenter

hardware
Use the Power On/Off tasks to remotely restart, power on, power off, or shutdown
a server in your systems-management environment. The available power states
vary depending on the feature that IBM Systems Director uses on the affected
server. For more information, see “Power On/Off tasks support using out-of-band
communication” and “Power On/Off task support by way of the operating
system.”
You must have access to the system to change the power state. For information
about requesting access to a system, see “Accessing a secured system with request
access.”
To change the power state, complete the following steps:

Explorer.
2. Navigate to the system on which you want to change the power state.
3. View the Access column to make sure that you can access the system. If Access
is set to No Access, you must request access to the system.
4. Right-click the system and click Power On/Off. Then, click the power state that
you want to apply. Depending on the feature that IBM Systems Director uses
for power management on the affected system, you can set the power to Power
On, Power Off, Restart, Restart Now, or Shutdown.
5. In the Launch Job window, click OK to change the power state immediately.
You also can schedule this task to run later. For more information, see

Related concepts:
Out-of-band support
Wake on LAN support
Related tasks:
Scheduling tasks
Enabling collection of SNMP-based inventory by way of management

modules
In order to collect SNMP-based inventory in IBM Systems Director by way of the
IBM BladeCenter management module or advanced management module, you
must configure the management module SNMPv1 and SNMPv3 settings.
Note: Management modules and advanced management modules permits you to

enable SNMPv1, SNMPv3 or both. If both protocols are enabled, IBM Systems
Director uses SNMPv3 to establish the connection for inventory collection.
To collect SNMP-based inventory, use the following setting considerations when

configuring the management module SNMP settings. See “Configuring SNMP
options for an IBM BladeCenter management module” on page 494 for detailed
steps for configuring SNMPv1 and SNMPv3 settings.
Table 38. Setting considerations for configuring management modules for SNMP-based
inventory collection
Protocol Setting considerations
SNMPv1 The trap destination must be specified as one of the following settings:
v The IP address of the system running IBM Systems Director Server.
v The IP address 0.0.0.0.
The Access type must be set to Get (or greater). This setting permits SNMP
access to the management module for the applicable trap destination:
v All incoming IP addresses with the correct community string
SNMPv3 v Management module firmware, version 3.5 or later, does not permit retrieval
of the Privacy protocol and Privacy password settings. To ensure SNMP
access, you can either:
– Use the Configure Access task to configure the SNMPv3 credentials.
– Leave these settings blank.
v Any IP address can be specified as a trap destination in the SNMPv3
configuration.
Related tasks:
Configuring SNMP options for a management module
Hardware-log information using out-of-band and in-band

communication
Hardware-log information is provided using in-band communication or
out-of-band communication, depending on your system hardware and
configuration.
You can access hardware logs from the following service processors and
management modules:
v Intelligent Peripheral Management Interface (IPMI) baseboard management
controller (BMC)
v Management module
The following table details the available hardware-log access paths for the service
processors and management modules.
Table 39. Available hardware-log access paths
Service processor Hardware-log access path
Management module Out-of-band communication directly with the management module or
Advanced management module advanced management module
Service processor in a System x server v Out-of-band communication directly with the service processor
v In-band communication with the service processor using Common Agent
or Platform Agent installed on the server
For information about enabling in-band communication, see “In-band

communication requirements.” For information about enabling out-of-band
communication, see “Out-of-band communication requirements.”
Related concepts:
Related tasks:
Viewing hardware-log information
Refreshing hardware-log information
Clearing the hardware-log information
Providing hardware-log information

The Hardware Log page displays information generated by service processors in
servers and by management modules and service processors in IBM BladeCenter
and IBM Flex System Manager products. The log contains information that you or
IBM service representatives can use to solve system hardware problems. This
information can include the source of hardware-related events, severity, date and
time, and text descriptions of the log entries.
To view hardware-log information using in-band communication, the system must

be online and you must have access. If you are using out-of-band communication,
hardware logs can be obtained from System x servers even when powered off. To
do so, the service processor must be online and you must have access.
To view hardware-log information, complete the following steps:

1. Navigate to the system that you want to view.
2. Select the applicable system resource.

Option Description
For in-band communication Select the system.
For out-of-band communication with a Click the system to view its components.
system Select the service processor.
For out-of-band communication with a Select the chassis.
BladeCenter chassis
3. Click Actions > System Status and Health > Hardware Log.
Notes:
v For log entries retrieved from Intelligent Peripheral Management Interface
(IPMI) baseboard management controllers (BMC), the value reported in the
Severity column is always Information because the BMC does not provide this
information.
v The format of the hardware log text can vary depending on the type of service
processor and whether the information was received using in-band or
out-of-band communication.
v If the hardware-log information cannot be retrieved using in-band
communication, the task will attempt out-of-band communication with the
system service processor to retrieve the hardware-log information.
On the Hardware Log page, you can view and work with the information in the
following ways:
v Filter the information. For more information, see “Filtering table information.”
v Sort the information. For more information, see “Sorting table information.”
v Export the information. For more information, see “Exporting table information.”
Related concepts:
Out-of-band and in-band communication
Related tasks:
Navigating tables

If some time has passed since you opened the Hardware Log page, you can refresh
the hardware-log information that is displayed on the page. Doing so will display
any log entries that have occurred since you opened the page or last refreshed the
page.
To view hardware-log information, the system must be online and you must have
access.
To refresh the hardware-log information, on the Hardware Log page, click Refresh.
Related concepts:
Related tasks:

A system might experience problems when the hardware log grows large. You can
clear the hardware-log information on the Remote Supervisor Adapter or
management module and therefore from the Hardware Log page. However,
because the hardware log might not be the source of the server problems, make
sure that you save the hardware-log information before you clear the hardware log.
You subsequently might need the log to solve the server problems.
Hardware log limitations vary depending on the service processor:

Remote Supervisor Adapter and Remote Supervisor Adapter II
The hardware log has a size limit. When the log is full, the entries wrap
rather than overflow.
IPMI baseboard management controller
The hardware log has a size limit. When the log is full, it no longer accepts
entries. If Common Agent or Platform Agent is installed on the affected
system, the log is erased automatically when it is full.
The service processor or management module generates a warning event when the
hardware log is almost full.
v For the Remote Supervisor Adapter and Remote Supervisor Adapter II, the event
is generated when the hardware log is 75% full.
v For the Intelligent Peripheral Management Interface (IPMI) baseboard
management controller (BMC), the threshold is programmed in the firmware
and can vary from BMC to BMC. Typically, the IBM BMC uses the following
values:
– 75% full generates a warning event
– 90% full generates a critical event
– 100% full generates an overflow event
To clear the hardware-log information, the system must be online and you must
have access.
Attention: Before you clear the hardware-log information, export the

hardware-log information so you can refer to it later or provide it to IBM service
representatives if necessary. For information about exporting, see “Exporting table
information.”
To clear the hardware-log information, complete the following steps:

1. On the Hardware Log page, click Clear.
2. In the confirmation window, click OK to confirm the request. The hardware-log
information is cleared from the table and from the service processor or
management module.

Related concepts:
Related tasks:
Navigating tables

The hardware log contains information that you or IBM service representatives can
use to solve system hardware problems. When you prepare to contact IBM, make
sure that you save the hardware-log information to a file so you can send the file
to IBM.
To save hardware-log information, the system must be online and you must have
access.
To save hardware-log information, complete the following steps:

1. Navigate to the system that is experiencing problems.
2. Select the applicable system resource.
Option Description
For in-band communication Select the system.
For out-of-band communication with a Click the system to view its components.
system Select the service processor.
For out-of-band communication with a Select the chassis.
BladeCenter chassis
3. Click Actions > System Status and Health > Hardware Log.
4. On the Hardware Log page, click Actions > Export.
then click OK.
Related concepts:
Related tasks:
Using locator LED settings on IBM Flex System Managercompute

nodes, IBM BladeCenter, and System x servers
IBM Flex System Managercompute nodes, IBM BladeCenter, and System x servers
provide a hardware feature called the locator LED. Use the locator LED to identify
one server within a rack of servers or other large group of servers, or one blade
server within a chassis. You also can use the locator LED to identify a server for a
service representative when you are viewing the server remotely in your
systems-management environment. You can change the locator-LED settings using
Locator LEDs and out-of-band and in-band communication

IBM Flex System Manager compute nodes, IBM BladeCenter, and System x servers
provide a hardware feature that is called the locator LED. Support is provided by
using either out-of-band and in-band communication.
Support for changing the locator-LED setting is provided by the following IBM
Flex System Manager compute nodes, IBM BladeCenter, and System x hardware:
v Intelligent Peripheral Management Interface (IPMI) baseboard management
controller (BMC)
Note: Not all BMCs support the locator LED. If it is not supported, the locator
LED settings are not displayed when you right-click the system and click
System Identification.
v Remote I/O enclosure
v Management module
v Integrated management module II
Support is available for both in-band communication and out-of-band
communication. For information about enabling in-band communication, see
“In-band communication requirements.” For information about enabling
out-of-band communication, see “Out-of-band communication requirements.”
Related concepts:
Related tasks:
Identifying hardware with the locator LED
Identifying hardware with the locator LED

Use the locator LED to identify one server within a rack of servers or other large
group of servers, or one blade server within a chassis. You also can use the locator

LED to identify a server for a service representative when you are viewing the
server remotely in your systems-management environment. You can turn on or off
the locator LED or set it to flash.
You must have access to the system to change the locator-LED setting. For
information about requesting access to a system, see “Requesting access to a
secured system.”
To set the locator LED to flash, complete the following steps:

Explorer.
2. Navigate to the system on which you want to change the locator-LED setting.
is set to None, you must request access to the system.
4. Right-click the system and click System Status and Health > System
Identification > LED Flash. You also can select LED On to identify the system.
5. In the Scheduler window, click OK to flash the locator LED immediately. You
also can schedule this task to run later. For more information, see “Scheduling
tasks.”
Related concepts:
Related tasks:
Scheduling tasks
Solving hardware problems by using light-path-diagnostic LEDs

Control and view the light-path-diagnostic LEDs in your systems. Use the
information from the light-path-diagnostic LEDs to help you troubleshoot and
resolve hardware problems.
Light-path-diagnostic LED information

Light-path-diagnostic LED information consists of the LED name and severity, its
state, color, location, and indicated conditions. For information about what
light-path-diagnostics LEDs are available on your hardware, see the hardware
documentation. Or, to list all available light-path-diagnostics LEDs and more, see
“Status commands.”
The light-path-diagnostic LED name is returned by the resource, such as a

management module or a service processor. If the resource cannot provide the
light-path-diagnostic LED name, the name is determined by the
light-path-diagnostic LED task. When the LED state is On, a specific severity is
indicated; however, this severity varies by LED name.
Table 40. LED name and associated severity
LED name Severity
Activity OK
Battery Critical
BMC Heartbeat OK
Channel x Critical
where x indicates a letter from A to H.
Table 40. LED name and associated severity (continued)
LED name Severity
CPU Critical
CPU x Critical
where x indicates a number from 1 to 8.

CPU mismatch Critical
DASD Critical
DASD x Critical

DIMM Critical
DIMM x Critical

Diagnostic card Critical
Fan Critical
Fan x Critical

Fault Critical
Identification Informational
Info Informational
Log Critical
NMI Informational
Non-optimal Informational
Non-redundant Critical
Over spec Critical
Over temp Critical
PCI Critical
PCI x Critical

Planar Fault Critical
POST OK Informational
Power OK
PS Critical
PS x Critical

RAID Critical
Riser1 Missing Informational
Riser2 Missing Informational
SAS Error Critical
SAS Missing1 Informational

Table 40. LED name and associated severity (continued)
LED name Severity
Scaling Port x Informational

Scaling Informational
Select CD OK
Select KVM OK
Service Processor Critical
Sleep OK
VRM Critical
VRM x Critical
Table 41. LED Indicated Conditions

Indication
Condition Details
Unknown cannot determine whether there is condition indicated.
Other IBM Systems Director cannot determine what condition is indicated.
Not Applicable The LED is currently not assigned an interpretation.
Location Indicates the locations of associated managed elements.
Attention Indicates that the associated managed elements requires the attention
of service personnel.
Activity Indicates that there is activity on the associated managed elements.
The type of activity indicated is specific to the associated managed
element.
Powered On Indicates that the associated managed elements are receiving power.
Fault Indicates that the associated managed elements are in a fault, error, or
otherwise degraded state.
LEDs can have the following states:

v Flashing
v On
v Off
The Flashing and On states indicate the severity associated with the LED (see
Table 40 on page 479).
LEDs can have the following colors. The colors do not impart information:
v Red
v Orange
v Yellow
v Green
v Blue
v Unknown
LEDs can be located in the following places:

v Front panel
v Light path card
v Planar
v FRU (field replaceable unit)
v Rear panel
v Unknown
Related reference:
Status commands
lsled command
chled command
Changing the resource for viewing light-path-diagnostics LED

information
You can change the resource for which you want to view detailed
light-path-diagnostics information.
To change the system, complete the following steps in the Light Path Diagnostic
Detailed Information window:
1. Above the table, select a resource from the list. You can select a recently viewed
resource from the list or you can click Browse to navigate to and select another
resource.
2. Click Verify LED Status. The LED information for the selected resource is
displayed.
Turning Off the Check Log LED

IMMv2 and CMM systems have a Check Log (also known as the Information or
Fault) LED. This LED indicates that there is a problem on hardware components
that do not have a field replacement unit (FRU) number. You might want to turn
off this LED if you are aware of the issue and are fixing it.
To turn off the Check Log LED, follow these steps:

1. From the Resource Explorer, navigate to the relevant managed endpoint.
2. Right-click the endpoint and select System Status and Health > Turn off the
Check Log LED.
The LED is turned back on by the hardware if there is another problem.
Viewing light-path-diagnostics status

You can view light-path-diagnostics status information to determine whether any
light-path diagnostic LEDs are reporting information.
To view light-path-diagnostics status information, the table must include the

column that displays light-path-diagnostics status. For information about selecting
the LED Status column for inclusion in the table, see “Setting table-column
preferences.”
To view the light-path-diagnostics status, complete the following steps:

1. Navigate to your system in Resource Explorer, System Status and Health, or
any other task with a table that displays these systems.
2. View the LED Status column. The available LED statuses are:

Critical
Indicates that the light-path-diagnostics LED for a device in critical
state is turned on.
Information
Indicates that there is a non-critical state that might need attention.
OK Indicates that the light-path-diagnostics LEDs are turned off.
Unknown
Indicates that there is a problem communicating with the resource to
obtain the LED state. If the resource does not support
light-path-diagnostics LEDs or if the state of the resource is such that
the LED state is unavailable, for example, No Access, the LED Status is
set to OK.
3. If the LED status is underlined, detailed light-path-diagnostics information is
available. Click the LED status to view this information.
Note: If the LED status is not underlined, try running the following CLI
command to obtain the information: smcli lsled.
Related tasks:
Viewing detailed light-path-diagnostics information

You can view detailed light-path-diagnostics information to determine whether any
light-path diagnostic LEDs are reporting information.
To view light-path-diagnostics status information, the table must include the

column that displays light-path-diagnostics status. For information about selecting
the LED Status column for inclusion in the table, see “Setting table-column
preferences.”
To view detailed light-path-diagnostics information, complete the following steps:

1. Navigate to your system in Resource Explorer, System Status and Health, or
any other task with a table that displays these systems.
2. Select a system and click Actions > System Status and Health > Lightpath.
Notes:
v The Light-path-diagnostic LEDs task is not displayed in any of these
situations:
– The LED status is not underlined
– The selected resource does not support light-path-diagnostic LEDs
– There is a problem communicating with the resource to obtain the LED
state
v If the Light-path-diagnostic LEDs task is not displayed, try running the
following CLI command to obtain the information: smcli lsled.
Any light-path-diagnostic LEDs associated with the selected resource are
displayed in the Light Path Diagnostic Detailed Information window.
3. For any LED with an LED state of On, resolve the hardware problem indicated
by the LED.
4. In the Light Path Diagnostic Detailed Information window, click Verify LED
Status. The detailed light-path-diagnostics information for the selected LED is
refreshed. If updated information is not displayed, the LED information
currently is not available for the resource. This might indicate any of the
following problems:
v A network connection error between the management server and the affected
resource
v A failure with the agent, Common Agent or Platform Agent, installed on the
resource
v A failure with IBM Systems Director Server
Configuring templates
You can configure templates for use in the Configuration Manager task. These
templates can configure IBM BladeCenter and IBM Flex System Manager products
and System x servers.
Related tasks:
Configuring systems
Password security levels for IBM BladeCenter management

modules and System x service processors
The available security levels, or password policies, are legacy, predefined high
security, or custom security. The chosen security level applies to all users logging
into the management module or service processor; you cannot specify different
security levels for individual users. Security-level settings can include expiration
date, retry count, password reuse settings, and more.
IBM Systems Director provides two predefined levels for password security:
Legacy and High. If neither of these levels meets your needs, you can define a
custom security level. For more information, see “Configuring security levels for an
IBM BladeCenter management module” and “Configuring security levels for a
System x service processor.”
Legacy Security Settings
Provides the lowest level of security:
v Login profiles can have blank passwords.
v Passwords do not expire.
v Users can reuse the same password.
v There is no limitation on the frequency of password change.
v Non-supervisor login profiles are locked for 2 minutes after 5 sequential
failed-login attempts.
v If a non-blank password is used, it must be at least 5 characters long
and contain at least one numeric character.
v No alerts are generated and no profiles are disabled due to inactivity.
High Security Settings
Provides the highest level of security:
v Blank passwords cannot be used for any login profile.
v The factory-default USERID account-password must be changed
immediately upon the next login.
v The password for any new login profile or a profile that has had its
passwords changed by another authorized user must be changed upon
first access.
v The password for each user expires after 90 days.
v The value of a password must be changed at least 5 times before the
same password value can be reused.
v A user must wait at least 24 hours before changing password again.

v Non-supervisor profiles are locked for 60 minutes after 5 sequential
failed-login attempts.
v New passwords must conform to the following rules and have at least 2
characters that are different from the previous password:
– Passwords must be a minimum of 8 characters long.
– Passwords must not be a repeat or reverse of the associated user ID.
– Passwords must use no more than 3 of the same character used
consecutively.
– Passwords must contain at least three of the following combinations:
- Alphabetic characters (At least one, lowercase alphabetic character)
- Alphabetic characters (At least one, upper-case alphabetic character)
- Numeric characters (At least one numeric character)
- Special characters (At least one special character)
v An alert is generated and the login profile is marked dormant when the
profile has been inactive for 120 days.
v Non-supervisor profiles are disabled after 180 days of inactivity.
Security settings available for IBM BladeCenter management

modules
The Legacy Security Settings and High Security Settings are described in the
following table.
Table 42. Legacy Security Settings and High Security Settings
Security fields Legacy Security Settings High Security Settings
User login password Disabled Enabled
required
Password expiration period 0 (no expiration) 90 days
Minimum password reuse Disabled 5
cycle
Maximum number of login 5 5
failures
Lockout period after 2 minutes 60 minutes
maximum login failures
Complex password rules Disabled Enabled
Minimum number of Not set 2
different characters in a
password
Default-account-password Disabled Enabled
expiration on first access
Require the user to change Disabled Enabled
the password on first access
Inactivity alert period 0 (disabled) 120 days
Inactivity alert and 0 (disabled) 180 days
deactivate period
Security settings available for System x service processors
The Legacy Security Settings and High Security Settings are described in the
following table.
Table 43. Legacy Security Settings and High Security Settings
Security fields Legacy Security Settings High Security Settings
User login password Disabled Enabled
required
Password expiration period 0 (no expiration) 90 days
Minimum-password-reuse Disabled 5
cycle
Maximum number of login 5 5
failures
Default-account-password Disabled Enabled
expiration on first access
Related tasks:
Configuring security levels for a service processor
Configuring security levels for a management module
Configuring the boot sequence for a blade server in an IBM

BladeCenter chassis
You can configure the boot sequence for the blade servers and associated boot
devices in an IBM BladeCenter chassis. Each blade server can have a different boot
sequence.
The boot sequence is the order of devices that will be brought up during the boot
of a blade server in an IBM BladeCenter chassis. You can specify a boot sequence
of as many as four devices, but no one device can be listed in the sequence more
than once. The default boot sequence is Network, CD-ROM, Diskette, and Hard Disk
Drive 0. The No Device setting must be at the end of the sequence, for example,
CD-ROM, Diskette, Hard Disk Drive 1, No Device.
You can use these templates for BladeCenter installations that include management
modules or advanced management modules. The settings provided by these
templates might be made by way of the management module, but actually might
affect other components in the BladeCenter environment. All settings might not be
applicable for the supported components.
To configure the boot sequence for a blade server within a chassis, complete the
following steps:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a configuration template.
2. On the Configuration Templates page, click Create.
3. In the Create Template window, select an appropriate target chassis from the
Template type list.
4. In the Configuration to create a template list, select Boot Sequence
Configuration.
5. Type a name in the Configuration template name field.
6. Optional: Type a description in the Configuration template description field.

7. Optional: If you want the template applied automatically, click Automatically
deploy this configuration template when notified of a matching resource.
8. Click Continue. The Blade Server Boot Sequence Configuration page is
displayed.
9. Click Create. The Blade Server Boot Sequence Configuration - Create window
is displayed.
10. In the Bay number field, select the bay number that corresponds to the blade
server for which you want to configure the boot sequence.
Note: If you select All, then all blade servers are configured with same boot
sequence order.
11. Select the first device in the Device 1 field.
12. Select the second device in the Device 2 field, and so forth for the third device
and the fourth device.
13. Click OK. Your changes for the selected bay are recorded on the Blade Server
Boot Sequence Configuration page.
14. Select the new configuration in the table.
15. Click Save to save the changes in the configuration template. If you are
updating the configuration in real time, click Deploy.
Important: If you close this page without clicking Save, no changes are made
to the template and the information that you entered is lost.
16. Optional: To return to the Templates page, click Cancel.
Related tasks:
Navigating tables
Configuring an IBM BladeCenter management module

Configuring the IBM BladeCenter management module or advanced management
module consists of providing configuration information for these areas:
management module networks, management module login, and management
module alerts.
Configuring login information for an IBM BladeCenter

management module
You can create a new user account to log into a management module. This user
account can be used to access the management module by different programs
across different interfaces, including the management module Web interface and
command-line interface, UpdateXpress, and more. You also can edit and delete the
user accounts.
Note: You can use these templates for BladeCenter installations that include
management modules or advanced management modules. The settings provided
by these templates might be made by way of the management module, but
actually might affect other components in the BladeCenter environment. All
settings might not be applicable for the supported components.
Creating a new account for the IBM BladeCenter management module:
To create a new account for a user of the management module, you must supply a
user name, password, and access type.
To create a new account of a user of the management module, complete the

following steps:
Template type list.
4. In the Configuration to create a template list, select Management Module
Login Configuration.
8. Click Continue. The Management Module Login Configuration page is
displayed.
9. Click Create Task. The Create Management Module Login window is
displayed.
10. In the Select a task list, select Create New Account.
11. If you do want to define user-account information, you can choose to click
Use an account configuration provided by a user-authentication template to
select previously created user-account information from a user-authentication
template. Then, go to step 16.
12. Otherwise, to specify the user-account information, click Use the specified
account configuration.
13. In the User name field, type the unique user name for the account.
14. In the Password field, type the password for the account. The password must
meet the following criteria:
v Alphanumeric characters only
v 5 - 15 characters
v At least 1 alphabetic character
v At least 1 numeric character
15. In the Confirmation password field, type the password again for the account.
If the passwords do not match, an error message is displayed.
16. In the User access list, select the user access permission for the account:
Administrator
The user is to have full administrator access to the management
module.
Read-only
The user cannot change any information on the management module.
17. Click OK. The Management Module Login Configuration page is displayed
with the new task.
Important: You must complete the following steps in this procedure or the
task will not run.
18. Select the tasks (including the task that you just created) that you want to run.
19. If you want the management module clock set to the same time as the
management server, select Set to the local time used by IBM Systems
Director Server.
20. To run the selected tasks and save the changes into the configuration template,
click Save. If you are updating the configuration in real time, click Deploy.

Important: If you close the page without making a selection and clicking
Save, no changes are made to the template and the information that you
entered is lost.
Related tasks:
Modifying an existing account for the management module
Deleting an account for a management module
Navigating tables
Modifying an existing account for the IBM BladeCenter management module:
For an existing user of the management module, you can modify the password or
access type.
To modify an existing account for a user of the management module, complete the
following steps:
Template type list.
6. Type a description in the Configuration template description field.
7. If you want the template applied automatically, click Automatically deploy
this configuration template when notified of a matching resource.
displayed.
displayed.
10. In the Select a task list, select Modify Existing Account.
11. To select previously created user-account information from a
user-authentication template, click Use an account configuration provided by
a user-authentication template and go to step 15. Otherwise, click Use the
specified account configuration.
12. Type the user name of the account to be modified.
13. If you are changing the password, type the new password to assign to this
user in the Password field. The password must meet the following criteria:
v 5 - 15 characters
14. If you are changing the password, type the new password in the Confirm
password field. If the passwords do not match, an error message is displayed.
15. If you are changing the user access type, select one of the following values:
Administrator
The user is to have full administrator access to the management
module.
Read-only
The user cannot change any information on the management module.
with the new task.
task will not run.
entered is lost.
19. To return to the Templates page, click Cancel.
Related tasks:
Creating a new account for the management module
Deleting an account for a management module
Navigating tables
Deleting an account for a IBM BladeCenter management module:
Delete accounts for the management module when they are no longer needed.
To delete an account for a user of the management module, complete the following
steps:
Template type list.
displayed.
displayed.
10. In the Select a task list, select Delete Account.
11. To select previously created user-account information from a
user-authentication template, click Use an account configuration provided by
a user-authentication template and go to step 13. Otherwise, click Use the
specified account configuration.
12. Type the user name of the account to be deleted.
with the new task.

task will not run.
entered is lost.
Related tasks:
Creating a new account for the management module
Modifying an existing account for the management module
Navigating tables
Configuring security levels for an IBM BladeCenter management

module
Configure security levels for a management module in order to control access to
the management module by users of IBM Systems Director. The available security
levels, or password policies, are legacy, predefined high security, or custom
security. The chosen security level applies to all users logging into the management
module or service processor; you cannot specify different security levels for
individual users. Security-level settings can include expiration date, retry count,
password reuse settings, and more.
Note: You can use this template for BladeCenter installations that include
advanced management modules only. Although some settings are supported by
firmware version BPET26B or later, to have support for all the settings in this
template, you must install firmware version BPET32D or later.
To specify the security level for a management module, complete the following
steps:
Template type list.
Security Level Configuration.
8. Click Continue. The Management Module Security Level Configuration page
is displayed.
9. In the Security level list, select a security level. For detailed information about
the password security levels, see “Password security levels for IBM
BladeCenter management modules and System x service processors.”
10. If you did not select Custom, click Save and do not complete any of the
remaining steps.
11. In the User login password required list, specify whether you want to require
passwords when users log in to the management module or service processor:
nothing selected
No selection has been made. If you save with this selection, the User
login password required property is not applied.
Activated
A password is required for user login.
Deactivated
A password is not required for user login.
12. Type the password expiration period, in days. Valid values are 0 - 365, where
0 indicates a password that will never expire.
13. Optional: Select the minimum password reuse cycle. Valid values are 1 - 5.
This field indicates the number of unique passwords that must be used before
a previously used password can be repeated. To indicate that there is no
password reuse cycle, select Disabled.
14. Optional: Select the complex password rules:
nothing selected
No selection has been made. If you save with this selection, the
Complex password rules property is not applied.
Activated
Performs checking to reject trivial passwords.
Deactivated
Does not perform checking to reject trivial passwords.
15. Optional: Select the minimum different characters in the password. This
option is disabled until the Complex password rules option is enabled and
the Minimum password reuse cycle has a value other than 0. Valid values are
between 1 and 15. It is the number of characters in the password that are not
the same. For example, a password of AAAAAA has zero different characters.
Select Disabled to indicate that there is no minimum different characters
requirement.
16. Optional: Select the maximum number of login failures. The number of times
that a user can attempt to log in with an incorrect password before the
account is locked for security reasons. Specify a number between 1 - 10. Select
Disabled to indicate that the account will not be locked out regardless of the
number of unsuccessful login attempts that are made. The default value is 5.
17. Type a value for the lockout period after the maximum number of login
failures. The value is the period of time in minutes that the account is locked
after the maximum number of login failures has been reached. Valid values
are numbers between 0 - 2880 (48 hours).
18. Optional: Select a setting to indicate whether the default account password
expires on the first access. The default account is the account with a user
named USERID.
nothing selected
Default-account-password expiration on first access property is not
applied.

Activated
The user is required to change the password of USERID at the time of
the first login.
Deactivated
The user is not required to change the password of USERID at the
time of the first login.
19. Optional: Select a setting to indicate whether the user will be forced to change
the password at the time of the first access:
nothing selected
Require the user to change the password on first access property is
not be applied.
Activated
The user is required to change the password on the first login.
Deactivated
The user is not required to change the password on the first login.
20. Type a value for the inactivity alert period. If a user does not log in within the
specified number of days, an alert is sent to SNMP, e-mail, or the system
recipient. Valid values are numbers between 0 - 365. Setting this value to 0
disables inactivity alert checking.
21. Type a value for the inactivity alert and deactivate period. If an account has
no login by a user within the specified number of days, an alert is sent to
SNMP, e-mail, or the system recipient and the account is deactivated. Valid
values are numbers between 0 - 365. Setting this value to 0 disables inactivity
alert and deactivation.
Related concepts:
Password security levels for management modules and service processors
Configuring the network IP for an IBM BladeCenter management

module
This template configures the Dynamic Host Configuration Protocol (DHCP) and
static IP addresses used to access the IBM BladeCenter management module.
To specify the network IP for an IBM BladeCenter management module, complete

Template type list.
Network IP Configuration.
8. Click Continue. The Management Module Network IP Configuration page is
displayed with these tabbed pages: IPv4 Configuration, IPv6 Configuration,
and DNS Configuration.
9. Specify the values on the appropriate pages.
Attention: If you close the page without making a selection and clicking
entered is lost.
Related tasks:
Configuring the IP address pool
Configuring SNMP options for an IBM BladeCenter management

module
Configure options used by IBM Systems Director so that Simple Network
Management Protocol (SNMP) v1 and v3 can be used to access the management
module.
To specify the SNMPv1 and SNMPv3 protocols for the management module,
Template type list.
Network SNMP Configuration.
8. Click Continue. The Management Module SNMP Configuration page is
displayed.
9. Optional: Specify additional SNMP settings.
Option Description
SNMPv1 settings See “Specifying SNMPv1 options for an IBM
BladeCenter management module”

Option Description
SNMPv3 settings See “Specifying SNMPv3 options for an IBM
BladeCenter management module”
Related tasks:
Enabling collection of SNMP-based inventory by way of management modules
Navigating tables
Specifying SNMPv1 options for an IBM BladeCenter management module:
Configure the options used by IBM Systems Director to access the management
module using the SNMPv1 protocol.
To specify the SNMPv1 protocol for a management module, complete the following
steps:
1. If you have not already done so, click the SNMPv1 tab on the Management
Module SNMP Configuration page. A table of SNMP communities is
displayed.
2. Select an SNMPv1 agent state:
nothing-selected
Nothing is configured if this field is left blank.
Activated
The SNMP agent is active.
Deactivated
The SNMP agent is not active.
3. In the Trap state list, select a status:
nothing-selected
Activated
SNMP agents can asynchronously provide important but unsolicited
information, such as extraordinary events.
Deactivated
The trap state is not being used. This setting is the default.
4. In the Contact information field, type the name of a person responsible for
the management module. This field accepts any ASCII words, such as a name,
e-mail address, and so forth.
5. In the Location field, type a description of the physical location of the
management module. This field accepts any ASCII words, such as a building
name or number, floor, column, geographic region, city, country, and so forth.
6. In the Community table, click Create. The Create New Community window is
displayed.
7. Select a community index. Valid values are 1, 2, or 3.
8. Select the access type:
Get All hosts in the community can receive traps and query Management
Information Base (MIB) objects. This value is the default.
Set All hosts in the community can receive traps, and query and set MIB
objects.
Trap All hosts in the community can receive traps.
9. Type a unique community name in the Community name field.
10. Type the value for the trap IP address or host name 1.
13. Click OK to record the changes in the SNMP communities table.
14. In the table, select the community that you created.
entered is lost.
16. If you want to specify SNMPv3 settings, see “Specifying SNMPv3 options for
an IBM BladeCenter management module” for the applicable steps.
Related tasks:
Specifying SNMPv3 options for a management module
Specifying SNMPv3 options for an IBM BladeCenter management module:
Configure the options used by IBM Systems Director to access the management
modules using the SNMPv3 protocol.
To specify the SNMPv3 protocol for a management module, complete the following
steps:
1. If you have not already done so, click the SNMPv3 tab on the Management
Module SNMP Configuration page.
nothing-selected
Activated
Deactivated
3. Select the trap state:
nothing-selected
Activated
Deactivated
4. Type a unique user ID in the User ID field. This user ID is one of the 12 user
IDs that the management module supports regardless of protocol and is
usable for non-SNMP access as well.
objects.
6. Type a unique profile name in the Profile name field.
7. In the Authentication settings area, complete the following steps:
a. Select the protocol. The following choices are valid:
None No encryption.
MD5 A type of message algorithm that converts a message of arbitrary
length into a 128-bit message digest. This algorithm is used for
digital signature applications where a large message must be
compressed in a secure manner.
SHA (Secure Hash Algorithm) An encryption method in which data is
encrypted in a way that is mathematically impossible to reverse.
Different data can possibly produce the same hash value, but there
is no way to use the hash value to determine the original data.
b. Type the password for the user in the Password field. The user ID and
password directly correspond to the user ID and password for non-SNMP
management module access. There is a maximum of 12 user accounts, and
those user accounts are used for SNMPv1 as well as for other access (for
example, Web access).
c. Type the same password in the Confirmation password field.
8. In the Privacy settings area, complete the following steps:
a. Select the protocol. Valid choices are none and DES (Date Encryption
standard).
b. Type the password for the user in the Password field.
c. Type the same password in the Confirmation password field.
9. Type the value for the trap IP address or host name.
entered is lost.
Related tasks:
Specifying SNMPv1 options for a management module
Configuring ports for an IBM BladeCenter management module

Use this task to configure the port numbers used to access the management
module with various network services.
applicable for the supported components. While management modules and
advanced management modules support a number of ports, they support the
configuration of only some of these ports.
Table 44. Ports supported for configuration
Management
Port module Advanced management module
FTP No Yes
FTP data No Yes
HTTP Yes Yes
HTTPS Yes Yes
Remote disk No Yes (firmware version BPET36M and earlier)
No (firmware version BPET42D and later)

Remote disk-on-card No Yes (firmware version BPET36M and earlier)

Remote KVM No Yes (firmware version BPET36M and earlier)

Remote presence No Yes (firmware version BPET42D or later)
Secure SMASH CLP No Yes
Secure TCP command mode No Yes (firmware version BPET46C and later)
No (firmware versions earlier than BPET46C)

SLP No Yes
SMASH CLP No Yes
SNMP agent Yes Yes
SNMP traps Yes Yes
SSH Yes Yes
Storage description service No Yes (firmware version BPET36M and earlier)

TCP command mode No Yes
Telnet Yes Yes
TFTP No Yes
Note: When this page is displayed for the first time, the default port numbers that
shipped with IBM Systems Director for each network service are displayed.
To change the port numbers for a management module, complete the following
steps:
Template type list.
Ports Configuration.

8. Click Continue. The Management Module Ports Configuration page is
displayed. On this page, the current port number for each network service is
displayed.
9. Make changes to these values as necessary. Valid port numbers are between 1
- 65535.
10. Optional: Click Restore Defaults to reset this page to the default values that
were shipped with IBM Systems Director.
11. Optional: Click Reset to remove any changes that you have made and restore
this page to the values it had the last time that Save was clicked or to the
default values if Save has never been clicked on this page.
Related concepts:
Standard TCP Command Mode protocol
Configuring alert settings and alert recipients

You can configure alert settings and indicate the people that receive the alert for an
IBM BladeCenter advanced management module and management module. These
settings determine that only the alerts that are important to your installation cause
notification to be sent to the alert recipient.
Alert settings and recipients for an IBM BladeCenter management module:
When an IBM BladeCenter management module detects a situation that is a

problem or might require attention, an alert is produced. An alert is a message or
other indication that signals an event or an impending event.
Alert notification is the process of sending information about the alert to an alert
recipient.
An alert recipient is a person or other target that is notified when an alert in a

category that has alert-notification enabled occurs. Alert recipient information
includes the target name, whether the recipient is to receive all alerts or only
critical alerts, and what notification mechanism to use.
Each type of alert has associated alert settings. Alert settings specify whether a
particular category of alert causes alert notifications to be sent to the alert
recipients and also other details about the alerts in the category. The other details
about the alerts for an IBM BladeCenter management module include retry limit,
delay time between retries, and whether to include a log file with the alert.
When an alert in a category that has alert notification enabled occurs, the alert
recipients are notified. Selecting the IBM Systems Director Comprehensive
notification type causes the enabled or disabled alert notification setting to be
ignored and everything to be sent to a specified recipient. In order for this process
to work, you must configure both alert recipients and alert settings.
If an alert recipient is to receive notification using e-mail, the event log can be
included. This feature is not available for alert recipients who receive notification
through other means.
For an IBM BladeCenter advanced management module with firmware version
BPET32D or later, legacy monitored-alert settings are used, which are similar to those
of the IBM BladeCenter management module.
For an IBM BladeCenter advanced management module with firmware version

BPET32D or later, enhanced monitored-alert settings are used, which include alerts for
additional situations and potential problems.
Alert settings can be configured in two ways:

Updating a configuration in real time
Alert settings are applied to the target device. When the alert settings are
displayed, the device is queried for the existing values. To apply these
changes to the target device, click Deploy.
Updating a configuration using a configuration template
Alert settings are applied to the configuration template for the target
device. When the alert settings are displayed, the values in the
configuration template are displayed. Click Save to save these changes to
the configuration template.
To apply the changes to the target device, first select the existing profile in
the configuration template and then select the related target device to
apply.
Alerts are classified according to severity:

Critical alerts
Alerts about situations or problems that are of a critical nature, such as
temperature that is too high.
Warning alerts
Alerts about situations or problems that are not as severe as critical alerts,
such as a log file running out of space.
System alerts
Alerts about situations or problems that affect only one system, or are not
problems at all but are notifications of routine events, such as remote login.
Related tasks:
Configuring alert settings for an advanced management module
Configuring alert recipients for a management module
Deleting alert recipients for an management module
Configuring alert settings for an IBM BladeCenter management module:
Configure alert settings for an IBM BladeCenter management module so that only
the alerts that are important to your installation cause notification to be sent to the
alert recipient. These alert settings apply to all alert recipients. You cannot specify
different settings for individual alert recipients.
Note: Enhanced monitored-alert settings are supported only by advanced

management modules with firmware version BPET32D or later. Legacy

monitored-alert settings are supported by advanced management modules with
firmware versions earlier than BPET32D and by management modules.
To specify alert settings, complete the following steps:

Template type list.
Alert Settings.
8. Click Continue. The Management Module Alert Settings page is displayed.
9. In the Remote-alert-retry limit list, select the number of times to permit
retrying a remote alert. If an alert notification is sent and it does not reach its
recipient, the alert notification will be sent again this number of times. Valid
values are 0 - 8. A value of 0 indicates that the remote alert will not be sent
again. This value applies only to e-mail and IBM Systems Director alerts.
SNMP alerts are attempted only once.
10. In the Delay between retries list, select a value in minutes for the delay time
between retries. If an alert notification is sent and it does not reach its
recipient, the alert notification will be sent again after this number of minutes
has elapsed until it has been retried the number of times specified in the
Remote-alert-retry limit list. Valid values are between 0.5 - 4.0, in half minute
intervals. The default is 0.5 minutes.
11. If you want the event log of the failing system sent with alert notification
when the alert recipient is using e-mail, select Include the event log with
e-mail alerts. Event logs cannot be sent to an alert recipient who uses any
notification mechanism other than e-mail.
12. If you are running in offline mode, select the type of monitored-alert settings:
Enhanced monitored-alert settings
Specifies an advanced management module with firmware version
BPET32D or later.
Legacy monitored-alert settings
Specifies an advanced management module with a firmware version
earlier than BPET32D or a management module.
If you are updating the configuration in real time, this selection is already
made for you by IBM Systems Director querying the firmware level of the
target device. In some cases, both legacy and enhanced monitored-alert
settings are displayed.
13. For each alert category (Critical, Warning, and System), select the alert
categories to enable for notification.
Related concepts:
Alert settings and recipients for a management module
Related tasks:
Configuring alert recipients for an IBM BladeCenter management module:
Alert recipients are those people or targets that are notified when an alert in a
category having alert notification enabled for an IBM BladeCenter management
module occurs.
Important: Only one alert recipient is permitted. If more than one management
server discovers and manages the management module, alerts might be lost.
To configure an alert recipient, complete the following steps:

Template type list.
Alert Recipient.
8. Click Continue. The Management Module Alert Recipient page is displayed.
9. Click Create. The Alert Recipient Creation page is displayed.
10. Type the name of the alert recipient in the Recipient name field.
11. Select the index for the recipient. Valid values are 1 - 12. You can define up to
12 unique recipients. Each link for an alert recipient is labeled with the
configured description for that particular recipient. If you have not configured
a recipient, the description of the link will be ~ not used ~.
12. In the Status list, select the status for the alert recipient:
Activate
Send alerts to this recipient.
Deactivate
Do not send alerts to this recipient. The Deactivate status is used to
temporarily omit a recipient from the list of those to receive alerts, for
example, a person on vacation.
13. Select whether all alerts or only critical alerts will cause this recipient to
receive notification.

14. Select the type of notification for this recipient:
v SNMP over LAN
v E-mail over LAN
Type the alert recipient's e-mail address in the form userid@hostname.
v IBM Systems Director (comprehensive)
Type the alert recipient's IP address or host name.
15. Click OK. The Management Module Alert Recipient page is displayed with
the new recipient in the table.
16. Select the recipient that you created.
Related concepts:
Related tasks:
Deleting alert recipients for an IBM BladeCenter management module:
Use this procedure to delete an alert recipient and associated user ID. When you
delete an alert recipient from the table, the recipient is removed from the
configuration template, but the user ID that has been created remains. To delete
this user ID, create a new task with the task name “Delete Account.”
To delete an alert recipient and the associated user ID, complete the following
steps:
Template type list.
Alert Recipient.
8. Click Continue. The Management Module Alert Recipient page is displayed.
9. Select the alert recipient that you want to delete.
10. Click Delete.
11. In the confirmation window, click OK to verify the deletion. The entry for this
user is deleted from the table.
12. Click Create.
13. In the Select a task list, select Delete Recipient.
14. Select an index for this recipient.
15. Click OK. The Management Module Alert Recipient page is displayed with
the new recipient in the table.
16. In the table, select the new Delete Account task to run.
Related concepts:
Related tasks:
Configuring network resources for IBM BladeCenter blade

servers
Use this template to configure the resources for those IBM BladeCenter
components that support external network access, including network interface card
(NIC) selection.
Note: You can use this template for BladeCenter installations that include
advanced management modules only. The settings provided by this template might
be made by way of the advanced management module, but actually affect HC10
and JS22 blade server models. All settings might not be applicable for the each
supported blade server.
To configure the network resources for a blade server, complete the following
steps:
Template type list.
4. In the Configuration to create a template list, select Management Network
Configuration.
8. Click Continue. The Management Network Configuration page is displayed.
9. Type the VLAN ID.
10. Type the Blade System Management Processor (BSMP) IP address range
(Starting IP address).
Note: IPv4 addresses are accepted.

11. Click Create. Management Network Configuration (page2) page is displayed.
12. Select the blade-server bay number. The available number of blade server bays
varies by IBM BladeCenter chassis model.
13. Select the bay width. Valid values are 1 - 4.

14. Select the NIC value. Valid values are 1 - (bay width setting x 8).
15. Indicate whether the NIC type is public or private secure.
16. In the Status list, specify whether the NIC is deactivated or activated. The
default is Activate.
17. In the VLAN ID status list, specify whether the VLAN ID is deactivated or
activated. The default is Activate.
18. Type the NIC VLAN ID.
19. Select your Dynamic Host Configuration Protocol (DHCP) setting from the
DHCP list.
20. Click OK. The Management Network Configuration page is displayed with
the new entry in the table.
entered is lost.
Related tasks:
Navigating tables
Configuring SNMP agent community information

You can configure the SNMP community information for SNMP agents installed on
System x servers and IBM BladeCenter blade servers.
Notes:
v This template provides the function that was previously provided in earlier
versions of IBM Director by the Configure SNMP Agent task.
v The settings in this template are applied to the system by way of the Common
Agent or Platform Agent.
v If you have installed the IBM Systems Director Linux Kernel-based Virtual
Machine (KVM) Platform Agent for Linux on x86-64, you cannot use the SNMP
Agent Configuration template to configure the operating system.
To configure the SNMP agent community information, complete the following

steps:
3. In the Create Template window, select Stand-alone server from the Template
type list.
4. In the Configuration to create a template list, select SNMP Agent
Configuration.
8. Click Continue. The SNMP Agent Configuration page is displayed.
9. Click Create. The Create SNMP Community window is displayed.
10. In the Community name field, type the community name to use for the
SNMP agent and click Add.
11. In the Trap destination field, type the trap destination to add to the Trap
destinations list. You can add one or more trap destinations.
12. To change a trap destination, type the new information in the Trap
destination field, select the affected trap in the Trap destination list, and then
click Update.
13. To remove a trap destination, select the affected trap in the Trap destination
list and click Remove.
14. When you are finished configuring the SNMP community information, click
OK. The SNMP community information is saved and is displayed on the
SNMP Agent Configuration page.
entered is lost.
Related tasks:
Navigating tables
Configuring the IP address pool for IBM BladeCenter systems

and System x servers
An IP address pool is a collection of static IP addresses that you can use when
configuring internal ports for IBM BladeCenter management modules and switch
modules, and for System x service processors.
To configure one BladeCenter chassis, you require a minimum of three IP

addresses. However, you might want to configure a larger pool of IP addresses so
that you can use the profile for future BladeCenter chassis configurations. The IP
addresses must be located on the same subnet on the management local area
network (LAN).
To configure the IP address pool, complete the following steps:

3. In the Create Template window, select an appropriate target from the
Template type list.
4. In the Configuration to create a template list, select IP Address Pool
Configuration.
7. Click Continue. The IP Pool Configuration page is displayed.
8. Fill in the values as appropriate, then click Add to add the address to the IP
address list.
9. Optional: If an address is incorrect, select it and either click Remove to delete
it from the IP address list or type the correct address in the applicable IP
address field and then click Update.

10. Optional: To reset the IP address list to the values that it had when the IP
Pool Configuration page was first displayed, click Reset.
11. Click Save to store the IP addresses in the IP address pool.
You now can use the IP address pool on configuration pages that provide the Get
IP address from IP address pool selection.
Related tasks:
Configuring the network IP for a BladeCenter management module
Configuring network resources for blade servers
Configuring the network IP for a service processor
Configuring network adapters
Configuring System x service processors

The configuration of System x service processors consists of providing
configuration information for these areas: login, security, networks, SNMP options,
ports, and alerts.
Configuring login information for a System x service processor

You can create a new user account to log into a service processor. This user
account can be used to access the service processor with different programs across
different interfaces, including the service-processor Web interface and
command-line interface, UpdateXpress, and more. You also can edit and delete the
user accounts.
Note: You can use this template for systems that include the following service
processors:
v Baseboard management controller (BMC)
This template is supported for scalable system partitions, as long as they use an
RSA service processor.
You can use this template for System x servers. The settings provided by this
template might be made by way of the service processor or the Common Agent or
Platform Agent, but the settings actually might affect other components in the
server. All settings might not be applicable for the supported components.
Related tasks:
Navigating tables
Creating a new account for a System x service processor:
To create a new account for a user of a service processor, you must supply a user
name, password, and access type.
To create a new account of a user of the service processor, complete the following
steps:
type list.
4. In the Configuration to create a template list, select Service Processor Login
Configuration.
8. Click Continue. The Service Processor Login Configuration page is displayed.
9. Click Create Task. The Create Service Processor Login window is displayed.
10. In the Select a task list, select Create New Account.
11. In the User name field, type the unique user name for the account.
12. In the Password field, type the password for the account. The password must
meet the following criteria:
v 5 - 15 characters
13. In the Confirmation password field, type the password again for the account.
If the passwords do not match, an error message is displayed.
14. In the User access list, select the user access permission for the account.
Administrator
The user is to have full administrator access to the service processor.
Read-only
The user cannot change any information on the service processor.
15. Click OK. The Service Processor Login Configuration page is displayed with
the new task.
task will not be run.
17. Click Save to run the selected tasks and save the changes into the
configuration template. If you are updating the configuration in real time,
click Deploy.
entered is lost.
Related tasks:
Modifying an existing account for a service processor
Deleting an account for a service processor
Navigating tables
Modifying an existing account for a System x service processor:
For an existing user of a service processor, you can modify the password or access
type.
To modify an existing account for a user of a service processor, complete the

following steps:

type list.
Configuration.
10. In the Select a task list, select Modify Existing Account.
11. Type the user name of the account to be modified.
12. If you are changing the password, type the new password to assign to this
user in the Password field. The password must meet the following criteria:
v 5 - 15 characters
13. If you are changing the password, type the new password in the Confirm
password field. If the passwords do not match, an error message is displayed.
14. If you are changing the user access type, select one of the following values:
Administrator
The user is to have full administrator access to the service processor.
Read-only
The user cannot change any information on the service processor.
the new task.
entered is lost.
Related tasks:
Creating a new account for a service processor
Deleting an account for a service processor
Navigating tables
Deleting an account for a System x service processor:
Delete accounts for a service processor when they are no longer needed.
To delete an account for a user of a service processor, complete the following steps:
type list.
Configuration.
10. In the Select a task list, select Delete Account.
11. Type the user name of the account to be deleted.
the new task.
entered is lost.
Related tasks:
Creating a new account for a service processor
Modifying an existing account for a service processor
Configuring security levels for a System x service processor

Configure security levels for a service processor in order to control access to the
service processor by users of IBM Systems Director. The available security levels,
or password policies, are legacy, predefined high security, or custom security. The
chosen security level applies to all users logging into the management module or
service processor; you cannot specify different security levels for individual users.
Security-level settings can include expiration date, retry count, password reuse
settings, and more.

You can use this template for System x servers and scalable system partitions that
include a Remote Supervisor Adapter II. The settings provided by this template
might be made by way of the Remote Supervisor Adapter II or the Common Agent
or Platform Agent, but the settings actually might affect other components in the
To specify the security level for a service processor, complete the following steps:
type list.
4. In the Configuration to create a template list, select Service Processor
Security Level Configuration.
8. Click Continue. The Service Processor Security Level Configuration page is
displayed.
9. In the Security level list, select a security level. For detailed information about
the password security levels, see “Password security levels for IBM
BladeCenter management modules and System x service processors.”
10. If you did not select Custom, click Save and do not complete any of the
remaining steps.
11. In the User login password required list, specify whether you want to require
passwords when users log in to the management module or service processor:
nothing selected
No selection has been made. If you save with this selection, the User
login password required property is not applied.
Activated
A password is required for user login.
Deactivated
A password is not required for user login.
12. Type the password expiration period, in days. Valid values are 0 - 365, where
0 indicates a password that will never expire.
13. Select the minimum password reuse cycle. Valid values are 1 - 5. This field
indicates the number of unique passwords that must be used before a
previously used password can be repeated. To indicate that there is no
password reuse cycle, select Disabled.
14. Select a setting to indicate whether the user will be forced to change the
password at the time of the first access:
nothing selected
Require the user to change the password on first access property is
not be applied.
Activated
The user is required to change the password on the first login.
Deactivated
The user is not required to change the password on the first login.
Related concepts:
Password security levels for management modules and service processors
Configuring the network IP for a System x service processor

Use this template to configure the Dynamic Host Configuration Protocol (DHCP)
and static IP addresses used to access a System x service processor.
processors:
To specify the network IP for a System x service processor, complete the following
steps:
type list.
Network IP Configuration.
7. Click Continue. The Service Processor Network IP Configuration page is
displayed.
8. Click Add. The Create Network IP Configuration window is displayed.
9. Select the type of node that you want to configure.
10. If you selected Secondary node, specify the index in the Index list. The
minimum value permitted is 1 and there is no maximum value.
11. Select the DHCP setting from the DHCP list.
Activated
DHCP is activated.

Deactivated
DHCP is deactivated; that is, the DHCP function will not be used. The
service processor will use a static IP address.
If DHCP fails, use static IP configuration
If DHCP is used and fails while running, use the static IP address
information.
12. Click OK.
13. On the Service Processor Network IP Configuration page, select the node that
you created.
entered is lost.
Related tasks:
Navigating tables
Configuring SNMP options for a System x service processor

Configure options used by IBM Systems Director so that Simple Network
Management Protocol (SNMP) v1 and v3 can be used to access the service
processor.
processors:
To specify the SNMPv1 protocols for the service processor, complete the following
steps:
type list.
Network SNMP Configuration.
7. Click Continue. The Service Processor SNMP Configuration page is displayed.
nothing-selected
Activated
Deactivated
9. In the Trap state list, select a status:
nothing-selected
Activated
Deactivated
10. In the Contact information field, type the name of a person responsible for
the management module. This field accepts any ASCII words, such as a name,
e-mail address, and so forth.
11. In the Location field, type a description of the physical location of the
management module. This field accepts any ASCII words, such as a building
name or number, floor, column, geographic region, city, country, and so forth.
12. In the Community table, click Create. The Create New Community window is
displayed.
13. Select a community index. Valid values are 1, 2, or 3.
objects.
15. Type a unique community name in the Community name field.
19. Click OK to record the changes in the SNMP communities table.
entered is lost.
Related tasks:
Navigating tables
Configuring ports for a System x service processor

Use this task to configure the ports numbers used to access the IBM BladeCenter
management module with various network services.

You can use this template for System x servers and scalable system partitions that
include a Remote Supervisor Adapter II. The settings provided by this template
might be made by way of the Remote Supervisor Adapter II or the Common Agent
or Platform Agent, but the settings actually might affect other components in the
Note: When this page is displayed for the first time, the default port numbers that
shipped with IBM Systems Director for each network service are displayed.
To change the port numbers for the service processor, complete the following steps:
type list.
4. In the Configuration to create a template list, select Service Processor Ports
Configuration.
7. Click Continue. The Service Processor Ports Configuration page is displayed.
On this page the current port number for each network service is displayed.
8. Make changes to these values as necessary. Valid port numbers are between 1
- 65535.
9. Optional: Click Restore Defaults to reset this page to the default values that
were shipped with IBM Systems Director.
10. Optional: Click Reset to remove any changes that you have made and restore
this page to the values it had the last time that Save was clicked or to the
default values if Save has never been clicked on this page.
Configuring alert recipients for a System x service processor

Alert recipients are those people or targets that are notified when an alert in a
category having alert notification enabled for a System x service processor occurs.
processors:
To configure an alert recipient, complete the following steps:
type list.
4. In the Configuration to create a template list, select Service Processor Alert
Recipient.
8. Click Continue. The Service Processor Alert Recipient page is displayed.
9. Click Create. The Alert Recipient Creation page is displayed.
10. Type the name of the alert recipient in the Recipient name field.
11. Select the index for the recipient. Valid values are 1 - 12. You can define up to
12 unique recipients. Each link for an alert recipient is labeled with the
configured description for that particular recipient. If you have not configured
a recipient, the description of the link will be ~ not used ~.
12. In the Status list, select the status for the alert recipient:
Activate
Send alerts to this recipient.
Deactivate
Do not send alerts to this recipient. The Deactivate status is used to
temporarily omit a recipient from the list of those to receive alerts, for
example, a person on vacation.
13. Select whether all alerts or only critical alerts will cause this recipient to
receive notification.
14. Select the type of notification for this recipient
IBM Systems Director over LAN

IBM Systems Director (comprehensive)

IBM Systems Director over modem
Type the phone number, user name, and password.
E-mail over LAN
Type the alert recipient's e-mail address in the form userid@hostname.
E-mail over PPP
For Point-to-Point Protocol (PPP), type the alert recipient's e-mail
address in the form userid@hostname, the user name, password, and
phone number.
Pager - numeric
Type the phone number and personal identification number (PIN) for
the pager service.

Pager - alphanumeric
Type the phone number and PIN for the pager service.
SNMP over LAN
This selection does not require any information.
SNMP over PPP
Type the alert recipient's user name, password, and phone number.
15. Click OK. The Service Processor Alert Recipient page is displayed with the
new recipient in the table.
16. Select the recipient that you created.
17. Click Save to run the selected tasks and save the changes into the
configuration template. If you are updating the configuration in real time,
click Deploy.
Related tasks:
Navigating tables
Deleting alert recipients for a System x service processor

Use this procedure to delete an alert recipient and associated user ID. When you
delete an alert recipient from the table, the recipient is removed from the
configuration template, but the user ID that has been created remains. To delete
this user ID, create a new task with the task name “Delete Account.”
To delete an alert recipient and the associated user ID, complete the following
steps:
type list.
Recipient.
8. Click Continue. The Service Processor Alert Recipient page is displayed.
9. Select the alert recipient that you want to delete.
10. Click Delete.
11. In the confirmation window, click OK to verify the deletion. The entry for this
user is deleted from the table.
12. Click Create.
13. In the Select a task list, select Delete Recipient.
14. Select an index for this recipient.
15. Click OK. The Service Processor Alert Recipient page is displayed with the
new recipient in the table.
16. In the table, select the new Delete Account task to run.
entered is lost.
Configuring alert settings for a System x service processor

Configure alert settings for a service processor so that only the alerts that are
important to your installation cause notification to be sent to the alert recipient.
These alert settings apply to all alert recipients. You cannot specify different
settings for individual alert recipients.
processors:
To specify alert settings, complete the following steps:

type list.
Settings.
8. Click Continue. The Service Processor Alert Settings page is displayed.
9. In the Remote-alert-retry limit list, select the number of times to permit
retrying a remote alert. If an alert notification is sent and it does not reach its
recipient, the alert notification will be sent again this number of times. Valid
values are 0 - 8. A value of 0 indicates that the remote alert will not be sent
again. This value applies only to e-mail and IBM Systems Director alerts.
SNMP alerts are attempted only once.
10. In the Delay between retries list, select a value in minutes for the delay time
between retries. If an alert notification is sent and it does not reach its
recipient, the alert notification will be sent again after this number of minutes
has elapsed until it has been retried the number of times specified in the
Remote-alert-retry limit list. Valid values are between 0.5 - 4.0, in half minute
intervals. The default is 0.5 minutes.

11. In the Delay between entries list, select a value in minutes to indicate the
number of minutes that the service processor waits between alert-forwarding
profiles, if multiple alert-forwarding profiles are configured. The service
processor runs each profile sequentially. Valid values are between 0.5 - 4.0, in
half minute intervals. The default is 0.5 minutes.
12. If you want the event log of the failing system sent with alert notification
when the alert recipient is using e-mail, select Include the event log with
e-mail alerts. Event logs cannot be sent to an alert recipient who uses any
notification mechanism other than e-mail.
13. For each category (Critical Alerts, Warning Alerts, System Alerts, and
Monitored Local Events), select the alert categories to enable for notification.
Configuring switch protocol information

Configuring the protocol settings for a switch consists of configuring login,
network protocols, SNMPv1 agents, and ports. This can be done for IBM
BladeCenter switch modules, as well as stand-alone switches.
applicable for the supported components. Both management modules and
advanced management modules provide applicable template settings for Ethernet
and Fibre Channel switch modules. Only advanced management modules provide
applicable template settings for SAS switch modules.
Note: All settings in a template might not be supported for a particular switch.
Vendor provided plug-ins are used to implement the configuration settings, and
either the plug-in or the switch might not support certain configuration settings.
For more information about vendor plugins, see "Downloading and activating
BladeCenter I/O module plug-ins" and "Downloading and activating
non-BladeCenter partner plug-in extensions".
To configure switch protocol information, follow these steps:

3. Select the appropriate value for Template type.
4. In the Configuration to create a template list, select Switch Protocol
Configuration, where Switch is the switch model with the protocols that you
want to configure.
8. Click Continue. The Protocol Configuration page is displayed.
9. Click Create. The Protocol Configuration page changes to display 4, or
possibly 5 tabs: Login Configuration, Network Protocols, SNMPv1 Agent, Port
Configuration, and possibly I/O Protected Mode.
10. Select the Login Configuration tab and specify the user name, password, and
other information necessary for IBM Systems Director to log in to the switch:
a. Select the chassis bay number. All is the default selection.
Note: This field is only shown if you chose a BladeCenter chassis for
Template type in step 3.
b. Optional: Click Reset to factory-default settings to reset the switch back to
initial factory settings and to use the switch’s factory-default user name
and password to log in to the switch.
c. If you do not want to define user-account information at this time, click
Do not define a new account configuration at this time.
d. If you do want to define user-account information, you can choose to click
Use an account configuration provided by a user-authentication template
to select previously created user-account information from a
user-authentication template. Otherwise, you can click Use the specified
account configuration:
1) Specify the user name that is used to log in to the switch. This user
name is validated by the vendor-provided plug-in. A default user ID of
USERID can be used for BladeCenter switch modules. Other switches
might have different default user IDs.
Note: On IBM System Networking switches, the default USERID is

admin and it cannot be changed; you can only change the password.
2) Type the password in the Password and Confirmation password
fields. Make sure that they are identical.
e. Optional: Click Set to the local time used by IBM Systems Director
Server if you want the switch module to use the local date and time of
11. Click the Network Protocols tab:
a. Select the static IP address configuration.
No IP address
Use the current switch IP address.
Get an IP address from the IP address pool
An address will be obtained by IBM Systems Director from the IP
address pool.
Use the specified IP address
You provide a specific IP address.
b. If your selection requires an IP address, select either to get an IP address
from the IP address pool or to specify an IP address. For information about
the IP address pool, see “Configuring the IP address pool for IBM
BladeCenter and System x servers.”
c. If you selected Get an IP address from the IP address pool, select an IP
address pool template.
d. If you selected Use the specified IP address, type the IP address, gateway,
and subnet mask.
Notes:

v IPv4 addresses are accepted for all switches. IPv6 addresses are accepted
for some switches. This depends on whether the vendor-provided
plug-in for the switch supports IPv6 addresses.
v For IPv6, the Subnet Mask field should contain the integer IPv6 subnet
prefix length, not a mask value.
e. In the HTTP list, select the type of access to grant to the switch when IBM
Systems Director uses the HTTP protocol:
nothing selected
Specifies no selection.
Activate_read_only
Enables using the HTTP protocol, but in read-only mode.
Activate
Enables the HTTP protocol on the switch.
Deactivate
Disables the HTTP protocol on the switch.
f. In the Telnet list, select the type of access to be granted to the switch when
IBM Systems Director uses the Telnet protocol.
nothing selected
Specifies no selection.
Activate_read_only
Enables using the Telnet protocol, but in read-only mode.
Activate
Enables the Telnet protocol on the switch.
Deactivate
Disables the Telnet protocol on the switch.
12. Click the SNMPv1 Agent tab. Follow these steps to create one or more
SNMPv1 community names:
a. Click Create. The Create New Community window is displayed.
b. Select the community index.
c. Select the type of access to grant the SNMPv1 agent:
nothing selected
Specifies that no selection is made.
Activate_read_only
Starts the SNMPv1 agent on the switch, but does not permit
changes to any of the configuration information.
Activate
Starts the SNMPv1 agent on the switch and permits changes to the
configuration information.
Deactivate
Stops the SNMPv1 agent on the switch.
d. Type the community name.
e. Type the IP address or host name for SNMP trap 1, SNMP trap 2, and
SNMP trap 3.
Note: IPv4 addresses and host names are accepted for all switches. IPv6
addresses are accepted for some switches. This depends on whether the
vendor-provided plug-in for the switch supports IPv6 addresses.
f. Click OK.
13. Optional: Click the SNMPv3 Agent tab. Follow these steps to create one or
more SNMPv3 User IDs and notifications:
a. On the SNMPv3 User IDs table, click Create. The Create User ID window
displays.
b. Enter an appropriate User ID.
c. For Authentication and Privacy settings, select the desired protocol to use.
If you select anything other than None, enter a Password and
Confirmation password for each.
d. Select the type of access to grant the SNMPv3 agent:
Read-only
The user will only have read-only access to SNMPv3 information,
as well as the ability to receive notifications.
Read/write
This user will have read and write access to SNMPv3 information,
as well as the ability to receive notifications.
e. Click OK to save the User ID.
f. On the SNMPv3 Notifications table, click Create. The Create Notification
window displays.
g. Enter the IP address or host name of the Destination IP address or host
name <#> field.
h. In the Assign User ID drop-down, select the appropriate User ID to
receive this notification.
i. Click OK to save this notification.
Note: Alternately, there is an option on the Create User ID window that lets
you create a user automatically. When selected, the other fields become
inactive and the IBM Systems Director Global ID and its default settings are
used to create a new SNMPv3 user. An associated notification destination that
uses the IBM Systems Director Server IP address is also created.
14. Click the Port Configuration tab.
a. In the External ports list, select the type of access to grant to the switch
when IBM Systems Director uses an external port:
nothing selected
Specifies that there is nothing configured
Activate_read_only
Enable external ports but do not permit changes to the port
configuration information
Activate
Enable external ports and permit changes to the port configuration
information
Deactivate
Disable external ports
15. If the I/O Protected Mode tab is visible, then the BladeCenter switch module
provides support for I/O protected mode. Click the I/O Protected Mode tab
to configure I/O Protected Mode settings.
16. In the Protected mode field, set the protected mode state to either Deactivate
or Activate.
17. Configure the Virtual Local Area Network (VLAN) settings.

a. In the VLAN ID field, type the new VLAN ID for the switch when it is in
protected mode. Valid values are 1 - 4095.
b. From the Interface number list, select the interface number for the new
VLAN when it is in protected mode.
c. Select the method of providing an IP address. To obtain an IP address from
the IP pool, click Get an IP address from the IP address pool. To provide
a specific IP address, Use the specified IP address.
d. If you selected Get an IP address from the IP address pool, select an IP
address pool template. For information about the IP address pool, see
“Configuring the IP address pool for IBM BladeCenter and System x
servers.”
e. If you selected Use the specified IP address, type the IP address, gateway,
and subnet mask.
Note: IPv4 addresses and host names are accepted for all switches. IPv6
addresses are accepted for some switches. This depends on whether the
vendor-provided plug-in for the switch supports IPv6 addresses.
f. In the External ports table, select at least one port.
18. Configure the switch I/O-protected-mode properties. The following settings
are available:
Activate_read_only
Starts the switch, but does not permit changes to any of the
configuration information on the switch
Activate
Starts the switch and permits changes to the configuration information
Deactivate
Stops the switch
a. Select the access type for the IP address parameters setting.
b. Select the access type for the External port access setting.
c. Select the access type for the External port management setting.
d. Select the access type for the Reset to factory-default settings setting.
entered is lost.
Related tasks:
Downloading and activating BladeCenter I/O module plug-ins
Downloading and activating non-BladeCenter partner plug-in extensions
Navigating tables
Configuring switch virtual LAN information

Run the VLAN configuration wizard to configure the virtual LAN (VLAN) settings
for a switch. This can be done for IBM BladeCenter switch modules as well as for
other (stand-alone) switches.
applicable for the supported components. Both the management modules and
advanced management modules provide settings for Ethernet and Converged
Enhanced Ethernet switches in these templates.
Note: All settings in a template might not be supported for a particular switch.
Vendor provided plugins are used to implement the configuration settings, and
either the vendor plugin or the switch might not support certain VLAN
configuration settings. For more information on vendor plugins, see “Downloading
and activating BladeCenter I/O module plug-ins” and “Downloading and
activating non-BladeCenter partner plug-in extensions”.
To configure the switch VLAN information, follow these steps:

3. In the Create Template window, select the appropriate value for Template
type.
4. In the Configuration to create a template list, select Switch VLAN
Configuration where Switch is the switch model with the VLAN that you
want to configure.
8. Click Continue. The VLAN Configuration wizard is displayed.
9. Optional: Clear Show this Welcome page next time if you do not want to see
the Welcome page the next time that you start this wizard.
10. On the Bay number page, select a bay number for the switch module. The
default value is All, which indicates that the profile applies to all chassis bays
that include a switch module of this type. If you select a specific bay number,
the profile will apply only to switch modules of the given type that are
installed in the specified bay.
Note: The Bay number menu is grayed out for stand-alone (non-BladeCenter)
switches.
11. Click Next.
12. On the VLAN configuration page, click Create to create one or more new
VLAN configurations. The Create VLAN Configuration window is displayed.
13. In the Select a task list, select Create a new VLAN configuration.
14. Type a unique VLAN name. Valid names can be 1 - 32 characters in length.
15. Type the VLAN ID. The ID is a unique number that identifies the VLAN.
Valid values range from 2 - 4094. A value of 1 is reserved for the default
VLAN.
16. Select a VLAN type.
Note: Only the settings supported by the switch are displayed.

permanent
Indicates that the VLAN is active and will remain so after the next
reset of the device. This selection is the default.
dynamic GVRP
Indicates that the VLAN is active and will remain so until removed by
GVRP.
other Indicates that the VLAN is active, but is not permanent or dynamic
GVRP.
17. Select the VLAN status of Activate or Deactivate.
18. Click OK to return to the VLAN configuration page. The new VLAN
configuration is displayed in the table.
19. Click Next.
20. On the VLAN egress configuration page, click Create to create one or more
new VLAN egress configurations.
21. In the Create VLAN egress configuration window, select a VLAN ID
associated with the configuration on the previous page.
22. Select the port number. Valid port values vary by switch type.
23. Select VLAN egress status.
No egress
Frames are not forwarded out of the port.
Tagged
Only tagged frames are forwarded out of the port.
Untagged
Only untagged frames are forwarded out of the port.
24. Click OK to return to the VLAN egress configuration table. The new VLAN
egress configuration is displayed in the table.
25. Click Next.
26. On the VLAN port configuration page, click Create to create one or more new
VLAN port configurations.
27. In the Create VLAN port configuration window, select the port number. Valid
port values vary by switch type.
28. Type the port VLAN ID.
29. Select the type of frames that the port accepts.
Note: Only the settings supported by the switch module are displayed.
Accept all
The port accepts both tagged and untagged frames.
Accept tagged
The port accepts only tagged frames.
Accept none
The port will not accept packets with this VLAN ID.
No support
The port does not support this functionality.
30. Select whether to activate the GARP VLAN Registration Protocol (GVRP)
status. GVRP dynamically adds VLANs to port egress lists across a domain.
31. Specify whether you want to activate the ingress filtering. Ports performing
ingress filtering discard any frame received that has a VLAN classification that
is not on the egress list of the port. Activate is the default setting.
32. Click OK to return to the VLAN port configuration table. The new VLAN
port configuration is displayed in the table.
33. Click Next.
34. On the Summary page, review your selections.
35. Optional: If you want to change any selections, click Back or select the page
from the wizard navigation area.
36. When you are satisfied with your selections, click Finish.
Related tasks:
Downloading and activating BladeCenter I/O module plug-ins
Downloading and activating non-BladeCenter partner plug-in extensions
Configuring users and passwords for an IBM BladeCenter

chassis
Use this page to specify users and their passwords for IBM BladeCenter chassis
access.
To configure a user to log into an IBM BladeCenter chassis, complete the following
steps:
Template type list.
4. In the Configuration to create a template list, select User Authentication
Configuration.
8. Click Continue. The User Authentication Configuration page is displayed.
9. Type a unique user ID in the User ID field. A user ID can contain only letters
and numbers and the length must be 1 - 8 characters.
10. Type a password for the user in the Password field. A password can contain
only letters and numbers and must contain at least one letter and one number.
Also, the password must be 8 characters long.
11. Type the password again in the Confirmation password field.
12. Click Save to save the changes in the configuration template.
Managing network-configuration information

Configuration manager provides network configuration tasks to view and edit
settings for Ethernet adapters, IP addresses, Domain Name System (DNS)
configurations, Windows Internet Naming Service (WINS) configurations, and
Windows domains and workgroups.
Notes:
versions of IBM Director by the Network Configuration task.


You can configure network adapters that are installed in System x servers and IBM
BladeCenter blade servers.
To configure network adapter, complete the following steps:

type list.
4. In the Configuration to create a template list, select Network Configuration.
7. Click Continue. The Network Configuration page is displayed.
8. On the Network Adapter page, select a network adapter and click Edit.
9. In the Network Adapter Configuration wizard, the Welcome page is
displayed. Click Next.
10. On the IP address page, specify whether you want to use full name (DHCP)
to obtain an IP address.
Option Description
Use DHCP to obtain an IP address 1. Select Activate in the DHCP list.
2. Go to step 13
Do not use DHCP to obtain an IP address 1. Select Deactivate in the DHCP list.
2. Go to step 11
11. If you want to obtain the IP address from the IP address pool, click Get an IP
address from the IP address pool and select an IP-address pool template.
Then, go to step 13. (For information about the IP address pool, see
“Configuring the IP address pool for IBM BladeCenter and System x servers.”)
12. If you want to specify the IP address, click Use the specified IP address and
type the IP address, gateway, and subnet mask.
13. Click Next.
14. On the DNS domain page, in the Suffix field, type the DNS domain for the
specified network adapter setting.
15. On the DNS server search order page, specify the DNS-server search order by
completing the following steps:
a. In the Server IP address field, type the DNS server IP address and click
Add. The IP address is added to the Server search order list.
b. To change the order of a server in the list, select the IP address and click
Up or Down to adjust the order.
c. To update an IP address, select the IP address to update in the Server
search order list, type the new information in the Server IP address field,
and click Update.
d. To remove an IP address, select the IP address and click Remove.
16. Click Next. If you are configuring network adapter settings for a system
running Windows, the WINS page is displayed. Otherwise, the Summary page
is displayed.
17. (Windows only) On the WINS page, type the IP address for the primary and
secondary servers. Then, click Next.
18. On the Summary page, verify the details of the configuration settings. If you
need to make changes, click Back.
19. When you are done editing the configuration settings, click Finish.
The configuration settings are saved and are displayed on the Network Adapter
page.
Related tasks:
Setting the search order for the DNS suffix
Configuring the domain or workgroup settings

You can set the search order for the DNS suffix for your network configuration.
To set the search order for the DNS suffix, complete the following steps:
1. On the Network Configuration page, click the DNS Suffix Search Order tab.
2. On the DNS Suffix Search Order page, specify the DNS server search order by
completing the following steps:
a. In the Suffix field, type the DNS server suffix and click Add. The IP
address is added to the Suffix search order list.
b. To change the order of a server in the list, select the suffix and click Up or
Down to adjust the order.
c. To update a suffix, select the suffix to update in the Suffix search order list,
type the new information in the Suffix field, and click Update.
d. To remove a suffix, select the suffix and click Remove.
3. When you are done editing the suffix order, click Save. If you are updating the
configuration in real time, click Deploy. To discard any changes you have
made, click Cancel. To reset the settings to the previously saved values, click
Reset. You still must click Save to save the restored settings.
Related tasks:

Use the Domain/Workgroup page to configure the managed system as a member
of a domain or workgroup. If the system is a domain member, you also can use
this page to give a user account permission to join the domain.
To configure the domain or workgroup settings, complete the following steps:

1. On the Network Configuration page, click the Domain/Workgroup tab.
2. On the Domain/Workgroup page, type the computer name of the affected
managed system.
Note: Only the Computer name field is valid for managed systems running
Linux or IBM i operating systems.

3. Specify whether you want the specified system to be a member of a domain or
a workgroup and type the domain name or workgroup name in the associated
field.
4. If you selected Domain, specify a user account permission to join the domain
by providing the user name and password of the account.
5. When you are finished editing the settings, click Save. If you are updating the
configuration in real time, click Deploy. To discard any changes you have
made, click Cancel. To reset the settings to the previously saved values, click
Reset and then click Save to save the restored settings.
Related tasks:
Managing system-account information

Configuration manager provides wizards that you can use to configure
system-account information for users or groups of users accessing either Windows
or Linux operating systems that are running on System x servers and IBM
Notes:
versions of IBM Director by the System Accounts task.
Configuring system-account information for users

You can add system-account information for users accessing either Windows or
Linux operating systems that are running on System x servers and IBM
Note: The settings in this template are applied to the system by way of the
Common Agent or Platform Agent.
To add a user account, complete the following steps:

type list.
4. In the Configuration to create a template list, select System Account
Configuration.
8. Click Continue. The System Account Configuration page is displayed.
9. Click Create.
10. In the System Account Configuration wizard, the Welcome page is displayed.
Click Next.
11. On the Operating-system type page, indicate whether the user account will be
used to access a system that is running the Windows, Linux, or IBM i
operating system. Click Next.
12. On the General page, provide the following information about the user:
Note: For IBM Systems Director 6.2.0 and higher agents, these Windows-only
fields are ignored:
User must change the password at next logon
User cannot change the password
Password never expires
Account is inactive
Home Folder drive
a. In the User name field, type the operating-system account user name.
b. Optional: In the Full name field, type the full name for the user of the
account.
c. Optional: (IBM i and Windows only) In the Description field, type a
description for the user account.
d. (Windows only) Specify whether the user account is locked out.
13. Click Next.
14. In the Available groups list on the Membership page, select one or more
system-account groups to which this user account belongs and click Add. The
selected groups are moved to the Selected groups list.
15. Click Next.
16. On the Profile page, provide the profile information for the applicable
operating system.
Option Description
For IBM i and Linux 1. In the Shell field, type the shell name
that the user will use after logging in, for
example, /bin/bash.
2. In the Home directory field, type the
home directory for the user profile.
For Windows 1. Optional: In the Path field, type the
configuration file path. Specify this value
if you want to use a user profile
configuration file. For example,
\\server_name\profiles_folder_name\
user_name.
2. In the Logon script field, type the logon
script.
3. In the Home Folder area, select Local
path to specify the local path for the
home folder; otherwise, complete the
following steps to assign a home folder
on a network server:
a. Click Connect and click a hard disk
drive from the list.
b. In the To field, type a network path,
for example, \\server\users\
username, where username is the user
name that you specified on the
General page.

17. Click Next.
18. On the Password page, type, and then confirm, the password for the user
account on the operating system.
19. If you are providing password information for a Linux-based user account, the
Password details page is displayed. On this page, provide the following
information.
Note: If you are updating the configuration in real time, the date and time
that the password was last changed is displayed.
a. Type the number of days to retain a password.
b. Type the number of days after which the password must be changed.
c. Type the number of days before the password expires to warn the user
that the password is preparing to expire.
d. Enter the number of days after which an account with an expired
password is disabled.
e. Set the password expiration date. Click the calendar icon to select a date
and click OK.
20. Click Next.
21. On the Summary page, verify the details of the user account. If you need to
change a setting, click Back.
22. When you are finished editing the user account, click Finish.
The user account is saved and is displayed on the Users page.

Related tasks:
Configuring system-account information for groups
Navigating tables
Configuring system-account information for groups

You can add system-account information for groups accessing either Windows or
Linux operating systems that are running on System x servers and IBM
Note: The settings in this template are applied to the system by way of the
Common Agent or Platform Agent.
To add a group account, complete the following steps:

type list.
4. In the Configuration to create a template list, select System Account
Configuration.
8. Click Continue. The System Account Configuration page is displayed.
9. On the System Account Configuration page, click the Groups tab.
10. On the Groups page, click Create.
11. In the System Account Configuration wizard, the Welcome page is displayed.
Click Next.
12. On the Operating-system type page, specify whether the group of accounts is
for accessing a system that is running the Windows, IBM i, or Linux operating
system. Click Next.
13. In the Name field on the General page, type the name for the group.
14. Optional: In the Description field, type a description for the group.
15. Click Next.
16. On the Membership page, select one or more user accounts to belong to this
new group. Click Next.
17. On the Summary page, verify the details of the group. If you need to change
any settings, click Back.
18. When you are done editing the group, click Finish.
The group is saved and is displayed on the Groups page.

Related tasks:
Configuring system-account information for users
Navigating tables
Setting asset information

You can configure asset information for a managed system, including information
about the system user, lease, and warranty; you also can provide data in up to five
user-defined fields. If you specify an end date for a lease or warranty, a warning
event is generated on that date.
Notes:
1. This template provides the function that was previously provided in earlier
versions of IBM Director by the Asset ID task.
2. This task is not supported if you have installed the IBM Systems Director Linux
Kernel-based Virtual Machine (KVM) Platform Agent for Linux on x86-64.
The information that you provide in this task is written to the EEPROM. For
systems that are not enabled for Enhanced Asset Information Area (EAIA), this
information is written to the asset.dat file in the data directory on the managed
system. The asset.dat file is deleted when IBM Systems Director is uninstalled.
The amount of information that you can store is limited. The task dynamically
calculates the amount of space that is remaining for storage and reports that
amount on each page.
The settings in this template are applied to the system by way of the Common
To set asset information, complete the following steps:

3. In the Create Template window, select Operating System from the Template
type list.
4. In the Configuration to create a template list, select Asset ID.

8. Click Continue. The Asset ID Configuration page is displayed.
9. View the System page. This page displays the following information for the
managed system.
Note: When setting configuration information using a configuration template,

Remote deployment manager profile is the only field displayed. When
setting configuration information in real time and IBM Systems Director can
detect and communicate with the system, all of the following fields are
displayed.
System name
Displays the system name.
MAC address
Displays the message authentication code (MAC) address of the
system.
Operating system
Displays the operating system that the system is running.
System GUID
Displays the system globally unique identifier (GUID) of the system.
Remote deployment manager profile
Displays the Remote Deployment Manager (RDM) profile associated
with the system, if applicable.
Note: This field is the only field you can edit.

10. Optional: In the Remote deployment manager profile field, type the profile
name associated with the system.
11. To set the user information, click the User tab. You can provide the following
information about the system user on the User page:
Name The name of the system user
Phone The phone number of the system user
Location
The location of the system user
Department
The department to which the system belongs
Position
The position held by the system user
12. To set the lease information, click the Lease tab. You can provide the following
information on the Lease page:
Lessor The name of the company from which you are leasing the system
Start date
The start date of the lease contract
End date
The end date of the lease contract
Note: If you specify an end date for the lease, a warning event is
generated when the lease ends.
Term The length in months of the contract
Lease rate factor (%)
A percentage that, when multiplied by the cost, gives the periodic
lease payment amount
Payment
The amount of money that results from multiplying the value by the
cost, lease rate factor, and term
Buyout
The amount of money required to purchase the leased property at the
end of the lease term
Future market value
The price a buyer will pay a seller for the leased property, as is
13. To set the asset information, click the Asset tab. You can provide the following
information on the Asset page:
Purchase date
The date the system was purchased
Last inventoried
The date the system was last inventoried
Asset number
The asset number assigned to the managed system
Note: If the system has a radio-frequency identification (RFID) number and

the system is detected and in communication with IBM Systems Director
Server, the RFID number is displayed on this page.
14. To configure custom data fields, click the Personalization tab. You can provide
custom information in up to five user-defined fields on the Personalization
page.
15. To configure warranty information, click the Warranty tab. You can provide
the following information on the Warranty page:
Duration
Accepts the length of the warranty, in days, months, or years
Cost Accepts the cost of the warranty
End date
Accepts the date that the warranty expires
Note: If you specify an end date for the warranty, a warning event is
generated when warranty expires.
The information that you specify on the Warranty page is collected during an
inventory collection. Use the View Inventory task to view the collected
information. You can manage the warranty information by creating a dynamic
group.
Managing activation keys by using Feature Activation Manager

Use the Feature Activation Manager to activate (or unlock) Features on Demand
options that are integrated in a managed resource. The feature is in the firmware
or software but is locked until you install the activation key. The Feature
Activation Manager consists of the Feature Activation Configuration page and the
Feature Activation wizard. Ensure that the resource that you want to configure
supports feature activation.

The Feature Activation Manager provides the capability to activate a feature on a
resource with a software key that is referred to as an activation key. For example,
when you purchase a server and a Features on Demand option, the activation key
can be installed on the server so that the Features on Demand function is ready for
you to use when you receive the server. Also, an available Features on Demand
option can be ordered anytime after your initial product purchase.
The feature is activated in one of the following ways:

v When you purchase a feature as part of a server or chassis order, the IBM
factory or IBM Business Partner enables the feature as part of the configuration
and testing of the server or chassis. You can begin using the feature when you
receive the server or chassis.
v When you purchase a Features on Demand option or upgrade that is separate
from the server or chassis order, you must complete the feature activation when
you install the option. In this case, an authorization code with instructions for
activating the feature is mailed to you.
v When you successfully retrieve an authorization code from the IBM Key
Management System Features on Demand web portal (https://www.ibm.com/
systems/x/fod/index.wss), an authorization code and instructions are contained
in a PDF that is e-mailed to you.
v When you already have the activation key, use the Feature Activation
Configuration wizard to upload the key.
An authorization code is a 22-character alphanumeric string that is the proof of
purchase and entitlement to upgrade one or more units with a particular feature.
The authorization code and instructions for requesting an activation key are on a
printed document that is mailed to you. If you order directly from IBM, the
authorization code and instructions can also be sent to your email address.
To use the Feature Activation Configuration wizard to obtain, upload, install, or

activate keys, complete the following steps:
Note: Before viewing, installing, or adding feature activation keys for a switch, be
aware of the following Switch considerations.
1. On the Plug-ins tab of the Home page, click Configuration Templates under
Configuration Manager. On the Configuration Templates page, click Create.
2. In the Create window, select the Template type that you want to create, then
select (if available) Feature Activation Manager Configuration.
3. Type a Configuration template name, then click Continue. The Feature
Activation Configuration wizard is displayed.
4. Complete the Feature Activation Configuration wizard to add the activation
key for your resource.
Switch considerations:
v For switches that use either SNMPv1 or SNMPv2c, configure the Write
Community String.
v For switches that use SNMPv3, configure the feature key management privilege
for the specified user.
v For a IBM System Networking or a Mellanox switch, make sure to use the
Update Manager Configure settings task (on the System x and IBM BladeCenter
tab) to specify which server you want to use as the Trivial File Transfer Protocol
(TFTP) server. The TFTP server is used to inventory or install feature activation
keys on the switch.
Use the Feature Activation Configuration page to view information about installed
feature activation keys, add and remove keys, and reboot the specified device on
which a feature activation key is installed or removed. To access the Feature
Activation Configuration page, right-click the resource that you want to examine,
then select System Configuration > Configuration Settings > Feature Activation
Manager.

Chapter 11. Managing IBM Power Systems
IBM Systems Director provides specific tasks that can help you manage Power
Systems and platform managers such as the Hardware Management Console and
the Integrated Virtualization Manager (IVM).
IBM Power Systems can all be completely managed by IBM Systems Director with
capabilities such as discovery, inventory, status, monitoring, power management,
and the functionality available with update manager, automation manager, and
virtualization manager.
IBM Systems Director can manage the following IBM Power environments that
might include POWER5 and POWER6 processor-based servers running AIX, IBM i
(formerly i5/OS), or Linux:
v Power Systems managed by the Hardware Management Console
v Power Systems managed by the Integrated Virtualization Manager
v A Power Systems server with a single image (a nonpartitioned configuration)
v A Power Architecture BladeCenter server under the control of a BladeCenter
management module
IBM Systems Director gives you an overall understanding of the Hardware

Management Consoles and Integrated Virtualization Managers in your
environment, as well as the hosts they manage and their associated virtual servers
(logical partitions). You can access and manage the logical partitions as you would
any other managed system.
In addition, IBM Systems Director provides a launch-in-context feature to access

additional tasks that are available from the Hardware Management Console and
the Integrated Virtualization Manager. From IBM Systems Director, you can also
access IBM i management tasks, as well as AIX management tasks.
New terms for Power Systems users in IBM Systems Director

IBM Systems Director introduces some terms that might be new to a Power
Systems user. Use this topic to understand new terms for familiar tasks and
concepts.
The following table lists terms used in IBM Systems Director, maps them to any
similar terms that exist in a Power Systems environment, and provides a definition
for the terms.
Power Systems term or

IBM Systems Director term concept Definition
host server, system, managed A physical server that
system contains physical processors,
memory, and I/O resources
and which is often
virtualized into virtual
servers, also known as
logical partitions.

Power Systems term or
IBM Systems Director term concept Definition
virtual server logical partition, partition The collection of processor,
memory and I/O resources
defined to run an operating
system and its applications.
utility virtual server Virtual I/O Server (VIOS) A virtual server that provide
virtualization capabilities for
a particular environment.
platform manager Hardware Management A platform manager
Console (HMC) and manages one or more hosts
Integrated Virtualization and their associated virtual
Manager (IVM) servers and operating
systems. For Power Systems,
the platform managers are
HMC and IVM.
power on activate (partition) Power Systems managed by
HMC and IVM, use the term
power on with respect to a
physical server or host. IBM
same term, power on, for
virtual servers, where Power
Systems has used the term
activate.
power off shut down (partition) Power Systems managed by
HMC and IVM, use the term
power off with respect to a
physical server or host. IBM
same term, power off, for
virtual servers, where Power
Systems has used the term
shut down.
live relocation partition mobility, Live Moving a running virtual
Partition Mobility server from one host to
another
static relocation inactive partition mobility, Moving a virtual server that
inactive mobility is powered off from one host
to another.
virtual farm N/A A virtual farm logically
groups like hosts and
facilitates the relocation task.
Managing Power Systems running AIX

IBM Systems Director provides a set of AIX management tasks that use
launch-in-context functionality to start the requested task in the IBM Systems
Director Console for AIX.
To utilize the features available in IBM Systems Director Console for AIX, you
must be running AIX, Version 6.1.0 or later.
Note: To access the AIX management tasks, ensure that you meet the following
requirements:

v You must have SMAdministrator authority for IBM Systems Director.
v You must have requested access to the AIX system, and configured credentials. If
the Access column for the AIX managed system lists something other than OK,
check these items to proceed with AIX management tasks.
For more information about the AIX tasks that you can perform, see the AIX
information in the IBM Systems Information Center.
To perform AIX management tasks, complete the following steps:

2. Navigate to the AIX system where you want to perform a management task.
3. Select the system, click Actions from the menu bar, and select AIX
Management > task_name, where task_name indicates the task that you want to
perform.
4. A new browser window opens to display the IBM Systems Director Console for
AIX set to the task that you want to perform.
Related tasks:
Creating single sign-on credentials
Related reference:
AIX Information Center
Managing Power Systems running IBM i

IBM Systems Director provides IBM i management tasks that use launch-in-context
functionality to start the requested task on the IBM i system.
Note: To use the launch-in-context features, you must be running IBM i Version
6.1.0 or later.
Launch-in-context enables you to complete many IBM i management tasks in the

following categories:
v Basic Operations
v Configuration and Service
v Database
v File Systems
v Integrated Server Administration
v Internet Configurations
v Journal Management
v Network
v Performance
v Security
v System
v Users and groups
v Work Management
Note: To access these tasks, you must have requested access to the IBM i system. If
the Access column for the IBM i managed system lists something other than OK,
check these items to proceed with IBM i management tasks.
To access these management tasks, complete the following steps:
Chapter 11. Managing IBM Power Systems 539

2. Navigate to a managed system running IBM i. Make sure that it is at Version 6
Release 1 or later.
3. Select the managed system running IBM i, click Actions from the menu bar,
and select IBM i Management.
Note: If the URL of the launch-in-context application has been changed after
you requested access to the IBM i managed system, use the Collect Inventory
task to collect inventory data for the managed system and then try the previous
steps again.
Related tasks:
Related reference:
IBM i Information Center
Managing systems controlled by HMC and IVM

In addition to the ability to perform management tasks on systems that are under
the control of Hardware Management Console (HMC) and Integrated
Virtualization Manager, IBM Systems Director provides launch-in-context capability
to extended tasks that are available in the HMC and IVM interfaces.
You can use IBM Systems Director to perform various management tasks on
systems that are under the control of HMC or IVM:
v Power management
v Creating virtual servers (logical partitions)
v Editing virtual server resources
v Relocating virtual servers between host systems
IBM Systems Director also includes a considerable amount of extended tasks that
are available in the HMC or IVM interfaces, and accessible by IBM Systems
Director through launch-in-context functionality. The following list includes some
examples of extended tasks that can be accessed in the HMC and IVM interfaces:
v Update Licensed Internal Code
v Work with system plans
v Manage TCP/IP settings
v Manage user profiles
v Manage serviceable events
v Manage Capacity On Demand
v Modify logical partition settings
Note: You should discover and manage an HMC from only one management
server. Managing an HMC from multiple management servers can cause
performance problems due to the amount of memory that is required.
Complete the following steps to start extended tasks in the HMC or IVM
interfaces:
Note: Ensure that you have requested access to your HMC or IVM, and that the
access status is displayed as Full Access or OK.

2. Click Group by System Type.
3. Click Power Systems.
4. Complete one of the following steps:
v To access HMC Management tasks:
a. Click HMC and Managed Power Systems Servers.
b. Select the HMC from which you want to perform the task, click Actions
> HMC Management, and select the task category that you want to
access.
c. The HMC interface opens in a new window, where you can complete the
task.
v To access IVM Management tasks:
a. Click IVM and Managed Power Systems Servers.
b. Select the IVM from which you want to perform the task, click Actions >
IVM Management, and select the task category that you want to access.
c. The IVM interface opens in a new window, where you can complete the
task.
Related tasks:
Creating a virtual server
Editing a virtual server
Relocating virtual servers
Viewing the Power Systems Management summary

You can view a summary of the resources managed by IBM Power Systems and
their status. You can also access common management tasks for managing your
Power Systems resources. Note that information on this page is refreshed
automatically when there are any changes.
To view the Power Systems Management summary, complete the following steps:
2. On the Home page, click Plug-ins, scroll to the Power Systems Management
portion of the page, and click the Power Systems Management section heading.
The Power Systems Management summary is displayed.
3. View the Power Systems Resource Status section. This section provides the
v A pie chart and corresponding list that indicate the number of virtual servers
with the following types of status:
Critical
Warning
Informational
OK
v Links to the following tasks that you can use to view and manage your
resources:
– Health summary
– Event log
– Problems

4. View the Manage Resources section. This section provides the following
information:
v The number of platform managers
– The number of Hardware Management Console platform managers
– The number of Integrated Virtualization Manager platform managers
v The number of Power Systems hosts (physical servers)
– The number of Power Systems servers
– The number of Power Systems BladeCenter servers
v The number of virtual servers (logical partitions) by logical partition type
– The number of AIX/Linux virtual servers
– The number of IBM i virtual servers
– The number of Virtual I/O Server virtual servers
v The number of operating systems
– The number of AIX operating systems
– The number of Linux operating systems
– The number of IBM i operating systems
– The number of Virtual I/O Server operating systems
v The shared storage pools
v Links to the following tasks that you can use to get started with Power
Systems Management:
– Create shared storage pool
– System discovery
– Monitors
– Thresholds
– Check for updates
– Create virtual server
– BladeCenter management
– System Planning Tool

To monitor for IBM i message queue events, create a customized event filter for
use in your event automation plans.
To create the event automation plan, complete the following steps:

1. 1. In the IBM Systems Director navigation pane, expand Automation and click
Event Automation Plans.
2. On the Event Automation Plans page, click Create. The Create Event
4. On the Name and description page, type a descriptive name for the event
5. On the Targets page, select the systems that the event automation plan will
monitor for the configuration manager events. Select the systems in the
Available list and click Add > to move them to the Selected list. Click Next.
6. On the Events page, select Advanced event filters from the Events list.
7. Click Create to create a new event filter. The Create Event Filter wizard is
displayed.
9. On the Filter Name page, type a name and description for the event filter,
then click Next. Although it is not required, a description does help you sort
and manage your event filters.

10. On the Filter Type page, select Simple event filter from the Filter type list,
then click Next.
11. On the Event Type page, select Include IBM i message queue events then
click Next.
12. On the IBM i Event Type page, specify the IBM i messages that you want to
include.
a. Type each message that you want to include.
Note: Use the following format: library/message_queue.messageID, where,

for each specified event:
v library is the library
v message_queue is the message queue
v messageID (optional) is the ID
The IBM i.Message Queue field automatically provides the common
message queue event prefix, which is OS/400.msgq. You type only the
unique portion of the message queue event. Consider the following
examples that assume the library is QSYS and the message queue is
QSYSOPR:
v To specify all message IDs, type QSYS/QSYSOPR.
v To specify a message ID of CPF1234, type QSYS/QSYSOPR.CPF1234.
v To specify any message ID that starts with the characters CPF:
– If the managed resource has 5770UME V1R3 and all the available
UME PTFs installed, type QSYS/QSYSOPR.CPF.
– Otherwise, type QSYS/QSYSOPR. Then, on the Event Text page of Event
Filter wizard, specify that you want to look for the characters CPF.
For more information on the Event Text page, see step 15 on page 544
b. Click Add to add the message to the list of Selected IBM i event types
c. When you are finished adding messages, click Next.
13. On the Severity and Category page, specify the severities and categories that
you want to include, then click Next. Select Default to include events of all
severities and categories. Select Custom to specify one or more severities and
categories.
14. On the Event Sender page, you can add any specific event senders that you
want to include in the filter. The filter is triggered when a specified sender
generates an event that you included in the filter.
a. Select a sender from the Systems list, then click Add to add it to the
Selected senders list.
b. To add a sender that does not appear in the Systems list, type the name of
the sender in the Additional sender field, then click Add.
c. When you are finished adding senders, click Next.
Important: Remember to update any specified sender name if you rename

the associated resource (the sender). When a managed resource is renamed,
IBM Systems Director does not automatically update the associated sender
name in an event filter. Renaming the resource without updating the event
filter results in a mismatch between the sender name that is specified in
the event filter and the sender name that is specified in the incoming
event. The mismatch in sender names causes any event action plan that
includes the filter to fail.

15. On the Event Text page, specify the event text that you want to include in the
filter, then click Next.
v Select Default to include all event text.
v Select Custom to specify a word, separate words, or a phrase that you want
to include in the filter. The filter is triggered by only those events that you
include in the filter that also contain the specified text.
16. On the Time Range page, specify when you want events to trigger the filter,
then click Next.
v Select All so that the filter is triggered any time that included events occur.
v Select Custom to specify that the filter is triggered only when included
events occur on a particular day of the week or within an identified time
range.
17. On the Summary page review your settings. If you want to modify any
settings, click Back to make changes. When you are satisfied with the event
filter, click Finish to save it. The new event filter is displayed on the Events
page.
18. On the Events page, select the new event filter, then click Next.
19. On the Event actions page, select one or more actions, or click Create to create
a new event action. These instructions assume you want to create a new event
action.
20. In the Create Action window, select an event action, for example, Send an
e-mail (Internet SMTP) .
21. Click OK.
22. Complete the fields for the event action that you selected. For some event
action types, you can include event-specific information as part of the text
message. Including event information is referred to as event-data substitution.
You can use event-data-substitution variables to customize event actions. For
more information, see “Event-data-substitution variables.”
23. When you are satisfied with the settings, click OK.
24. Select one or more event actions, then click Next.
25. On the Time range page, choose the period of time over which you want to
collect the events, then click Next. Select All the time (24 x 7) so that the plan
is active all the time. Select Custom to specify a particular day of the week or
a time range during which the plan is active.
need to make changes, click < Back. When you are done editing the event
automation plan, click Finish.
The event automation plan is saved and is displayed in the Event Automation
Plans page.
Related tasks:
Creating, editing, or copying an event filter
Creating an event action
Managing power state settings on IBM Power systems

Support for the Power On/Off task is provided by the operating systems on IBM
Power systems.

Changing the power state on IBM Power systems
Use the Power On/Off tasks to remotely restart a server in your
access.”

Explorer.
Managing storage using shared storage pools

With shared storage pools, you can create storage pools that can be accessed by
any Virtual I/O Server (VIOS) virtual servers that are members of the shared
storage pool. You can edit these shared storage pools by adding or removing VIOS
virtual servers. You can also edit the storage pool that is associated with the shared
storage pool by adding or replacing physical volumes, or changing the storage
pool threshold.
Shared storage pools

IBM Power VM Shared Storage Pools offer the ability to move beyond the current
Virtual I/O Server (VIOS) model of managing access to a storage pool on a single
IBM Power server. Shared storage pools extend storage virtualization to multiple
VIOS virtual servers on multiple Power servers.
This integrated storage virtualization provides several benefits over the current
model:
v Simplified management of virtual servers with integrated virtual server and
storage provisioning and management
v Reduced overall data center administrative workflow by server provisioning of
workloads without storage administrator action
v Ability to leverage both existing and new storage infrastructure
v Simplified adoption of Live Partition Mobility, Active Memory Sharing, and
Hibernation
The following diagram shows this shared storage pool.

To create a shared storage pool, you group VIOS virtual servers that share physical
volumes. A storage pool is created and shared by all VIOS virtual servers that are
members of the shared storage pool. This shared storage pool is composed of the
following components:
v VIOS virtual server members
The shared storage pool is composed of the VIOS virtual servers that can access
the repository disk and the physical volumes that make up the storage pool.
v Repository disk
This physical volume can be accessed by all the VIOS virtual servers that are
members of the shared storage pool. It is used to store metadata about the
shared storage pool.
v Storage pool associated with the shared storage pool
The storage pool is made up of physical volumes that can be accessed by every
VIOS virtual server that is a member of the shared storage pool. This storage is
used to create virtual disks or logical units (LUs).
Tasks
With IBM Systems Director Web interface, you can complete the following tasks:
v Create a shared storage pool
v View the VIOS virtual server members in a shared storage pool
v View the physical volumes in the storage pool associated with a shared storage
pool
v Add physical volumes to the storage pool
v Replace physical volumes in the storage pool
v Edit the threshold for a storage pool
v Add VIOS virtual servers to the shared storage pool
v Remove VIOS virtual servers from a shared storage pool
v Delete a VIOS shared storage pool

With IBM Systems Director smcli commands, you can perform the following tasks:
v mksharedstpool
Use the mksharedstpool command to create a Virtual I/O Server (VIOS) shared
storage pool.
v addsspviosvs
Use the addsspviosvs command to add Virtual I/O Server (VIOS) virtual servers
to a shared storage pool.
v lscandidatephysvol
Use the lscandidatephysvol command to list available physical volumes for a
Virtual I/O Server (VIOS) shared storage pool.
v lscandidaterepophysvol
Use the lscandidaterepophysvol command to list all the physical volumes
capable and available for use as a respository disk for a Virtual I/O Server
(VIOS) shared storage pool.
v lscandidateviosvs
Use the lscandidateviosvs command to list the Virtual I/O Server (VIOS)
virtual systems available to be added to a shared storage pool.
v lssharedstpool
Use the lssharedstpool command to list information about shared storage pools.
v lssspphysvol
Use the lssspphysvol command to list information about physical volumes in a
shared storage pool.
v lssspviosvs
Use the lssspviosvss command to list information about Virtual I/O Server
(VIOS) virtual servers that are in a shared storage pool.
v rmsspviosvs
Use the rmsspviosvs command to remove Virtual I/O Server (VIOS) virtual
servers from a shared storage pool.
v rmsharedstpool
Use the rmsharedstpool command to delete a shared storage pool.
v replacesspphysvol
Use the replacesspphysvol command to replace the physical volumes attached
to a storage pool.
v addsspphysvol
Use the addsspphysvol command to add a physical volume to a shared storage
pool.
v editspthreshold
Use the editspthreshold command to change the threshold alert level for a
storage pool. The storage pool threshold sets the percentage of total storage that
must be available in the storage pool. If the percentage of available storage
drops below this threshold, the IBM Systems Director Server will receive a
warning notification about low storage space availability. When created, a
storage pool has a threshold alert level of 35.
v lsaddphysvolcandidate
Use the lsaddphysvolcandidate command to list the physical volumes that are
available for assignment to a storage pool. The output of this command can be
used to get the necessary information required to add physical volumes to a
shared storage pool using the addsspphysvol command.
v lssspminidisksize

Use the lssspmindisksize command to list the minimum disk size required by
any physical volume assigned to any storage pool within a shared storage pool.
v lssspstoragepool
Use the lssspstoragepool command to list information about storage pools
associated with a shared storage pool.
For more information about these commands, see "Shared storage pools
commands."
You can perform additional tasks with Virtual I/O Server commands. For
information about these commands, see "Virtual I/O Server command
descriptions."
Related reference:
Shared storage pools commands
Virtual I/O Server command descriptions
Requirements for creating and managing shared storage

pools with IBM Systems Director
Before you can create and manage a shared storage pool with IBM Systems
Director 6.3.2 or later, you must ensure that your environment satisfies the
following requirements:
v The PowerVM Editions hardware feature is enabled on your system.
You enable PowerVM Editions by entering an activation code. You can use either
the Integrated Virtualization Manager (IVM) or the Hardware Management
Console (HMC) to enter the activation code.
For information about entering the activation code, see Entering the activation
code for PowerVM Editions with the Integrated Virtualization Manager or
Entering the activation code for PowerVM Editions using the HMC version 7.
v Virtual I/O Server (VIOS) Version 2.2.2.0 or later is installed and the license
activated on all virtual servers that you want to use in the shared storage pool.
Note: IBM Systems Director will not recognize shared storage pools on previous
versions of the Virtual I/O Server.
For information, see Installing the Virtual I/O Server manually by using the
HMC version 7, release 7.1, and later.
v VIOS virtual servers must be configured using a fully-qualified hostname.
v IBM Systems Director Common Agent is started. For information, see Restarting
Common Agent.
v The shared storage pool VIOS subagent is installed. For information, see
Installing the shared storage pool VIOS subagent.
v The VIOS operating system is discovered, active, and accessible in IBM Systems
Director.
For information, see Performing a system discovery.
v There are at least two SAN-based physical volumes that are accessible to every
VIOS virtual server that you want to use in the shared storage pool.
– One of these physical volumes, defined as the repository disk, is used to store
the metadata about the shared storage pool. The minimum disk space
requirement for the repository disk is 1 GB.

– At least one additional physical volume provides storage for the storage pool
that is associated with the shared storage pool. The minimum disk space
requirement for the physical volumes in the storage pool is 10 GB.
v Inventory is collected and current for the VIOS operating system that you want
to use in the shared storage pool.
Run Collect Inventory against All Inventory. For information, see Collecting
inventory.
Installing the shared storage pool VIOS subagent

The shared storage pool VIOS subagent is a subagent to the IBM Systems Director
Common Agent that is running on a Virtual I/O Server (VIOS) virtual server. It
enhances the IBM Systems Director agent to provide an interface for creating and
managing shared storage pools. It also provides the interface for the shared storage
pools image management capabilities exploited by IBM Systems Director
VMControl.
The minimum VIOS version that you can install this subagent on is Virtual I/O
Server (VIOS) Version 2.2.2.0 or later.
You must use IBM Systems Director to install the shared storage pool VIOS
subagent. The subagent installation procedure installs the following fileset on the
VIOS:
v vios.agent
Use IBM Systems Director to install the shared storage pool VIOS subagent on a
VIOS. This method is quick and easy, while allowing you to install on multiple
systems simultaneously.
To install the shared storage pool VIOS subagent on a VIOS, perform the following
steps:
1. From the IBM Systems Director web interface, expand Release management
and click Agents. The Agents window is displayed.
2. Select Common Agent Subagent Packages in the table.
3. Select the latest version of the CommonAgentSubagent Shared Storage Pool
VIOS sub-Agent package.
4. Click Install Agent. The installation window is displayed.
5. On the Welcome window, click Next.
6. On the Agents window, click Next.
7. On the Systems window, do the following:
a. Select the name of the system or systems on which you want to install the
shared storage pool VIOS subagent.
b. Click Add > Next > Finish.
8. Click OK to complete the installation.
Creating a shared storage pool

You use the Create Shared Storage Pool wizard to specify Virtual I/O Server
(VIOS) virtual servers and define a storage pool to create a shared storage pool.
Before you can create a shared storage pool, you must ensure that your
environment satisfies the following requirements:
v The PowerVM Editions hardware feature is enabled on your system.

You enable PowerVM Editions by entering an activation code. You can use either
the Integrated Virtualization Manager (IVM) or the Hardware Management
Console (HMC) to enter the activation code.
For information about entering the activation code, see Entering the activation
code for PowerVM Editions with the Integrated Virtualization Manager or
Entering the activation code for PowerVM Editions using the HMC version 7.
v Virtual I/O Server (VIOS) Version 2.2.2.0 or later is installed and the license
activated on all virtual servers that you want to use in the shared storage pool.
Note: IBM Systems Director will not recognize shared storage pools on previous
versions of the Virtual I/O Server.
For information, see Installing the Virtual I/O Server manually by using the
HMC version 7, release 7.1, and later.
v VIOS virtual servers must be configured using a fully-qualified hostname.
v IBM Systems Director Common Agent is started. For information, see Restarting
Common Agent.
v The shared storage pool VIOS subagent is installed. For information, see
Installing the shared storage pool VIOS subagent.
v The VIOS operating system is discovered, active, and accessible in IBM Systems
Director.
v There are at least two SAN-based physical volumes that are accessible to every
VIOS virtual server that you want to use in the shared storage pool.
– One of these physical volumes, defined as the repository disk, is used to store
the metadata about the shared storage pool. The minimum disk space
requirement for the repository disk is 1 GB.
– At least one additional physical volume provides storage for the storage pool
that is associated with the shared storage pool. The minimum disk space
requirement for the physical volumes in the storage pool is 10 GB.
inventory.
To create a shared storage pool, follow these steps:

1. On the IBM Power Systems management page, click the Create shared storage
pool task.
2. Follow the instructions in the Create Shared Storage Pool wizard. The wizard
guides you through selecting VIOS virtual servers to include in the shared
storage pool and selecting physical volumes to create an associated storage
pool.

Related concepts:
“Shared storage pools” on page 545
Related tasks:
Entering the activation code for PowerVM Editions by using HMC Version 7
Entering the activation code for PowerVM Editions with the Integrated
Virtualization Manager
Installing the Virtual I/O Server manually by using the HMC version 7, release
7.1, and later
Restarting Common Agent
Related reference:
mksharedstpool command
lscandidateviosvs command
lscandidatephysvol command
lscandidaterepophysvol command
lssspphysvol command
Viewing the shared storage pool dashboard

You can view a summary of the shared storage pool and its components.
To view the shared storage pool dashboard, follow these steps:

1. In the navigation pane, click Resource Explorer and navigate to the Groups by
System Type > Storage Systems > Shared Storage Pools and Members view.
2. Right-click the shared storage pool that you want to view and select System
Configuration > Shared Storage Pool Dashboard.
Viewing the storage pool dashboard

You can view a summary of the storage pool and its components.
To view the storage pool dashboard, follow these steps:

System Type > Storage Systems > Shared Storage Pools and Storage Pools
view.
2. Right-click the storage pool that you want to view and select System
Configuration > Storage Pool Dashboard.
Adding physical volumes to a storage pool

You can add storage to an existing shared storage pool by adding physical
volumes to the storage pool that is associated with the shared storage pool. The
physical volumes must be accessible to the Virtual I/O Server (VIOS) virtual
servers that are part of the shared storage pool.

Before you can add physical volumes to a shared storage pool, ensure that at least
one VIOS virtual server in the shared storage pool is active. The physical volumes
that you want to add to the shared storage pool must satisfy the following
requirements:
v The physical volumes are available to every VIOS in the shared storage pool.
v Physical volumes, backed by storage LUNs, are masked to the VIOS virtual
servers that you want to use in the shared storage pool.
v SCSI reserve is not set on the physical volumes.
v The physical volumes meet the minimum size requirement for the storage pool.
v The physical volumes are not part of another storage pool, or being used as
backing devices.
To determine if a physical volume is in use, run the following command:
prepdev -dev <physical volume name>
If the physical volume is in use, follow the instructions recommended by the
prepdev command to make the physical volume available. For example, you can
use the cleandisk command to make the physical volume available if it is in use
as a repository disk or as a storage pool disk.
– To remove a repository disk signature, run the following command:
cleandisk -r <physical volume name>
– To remove a storage pool disk signature, run the following command:
cleandisk -s <physical volume name>
CAUTION:
Ensure that the physical volume is no longer needed, as running the
cleandisk command results in loss of data on the physical volume.
To display the physical volumes that are not in use, run the following command:
lspv -free
For information about these requirements, contact your storage administrator.
To add physical volumes to a storage pool, follow these steps:

view.
2. Right-click the storage pool that you want to edit and select System
Configuration > Add Physical Volumes.
3. Follow the instructions in the Add Physical Volumes wizard to select physical
volumes to add to the selected storage pool.
Related concepts:
Related reference:
Replacing physical volumes in a shared storage pool

You can replace physical volumes in an existing shared storage pool by removing
any number of physical volumes from the storage pool and adding any number of
physical volumes whose combined capacity is equal to or greater than the
combined capacity of the physical volumes that are removed.

Note: You cannot replace the repository disk. You can replace only physical
volumes that are assigned to the storage pool.
Before you can replace physical volumes in a shared storage pool, ensure that at
least one VIOS virtual server in the shared storage pool is active. Any physical
volumes that you want to use for the storage pool must satisfy the following
requirements:
v The physical volumes are available to every VIOS in the shared storage pool.
v Physical volumes, backed by storage LUNs, are masked to the VIOS virtual
servers that you want to use in the shared storage pool.
v SCSI reserve is not set on the physical volumes.
v The physical volumes meet the minimum size requirement for the storage pool.
v The physical volumes are not part of another storage pool, or being used as
backing devices.
To determine if a physical volume is in use, run the following command:
prepdev -dev <physical volume name>
If the physical volume is in use, follow the instructions recommended by the
prepdev command to make the physical volume available. For example, you can
use the cleandisk command to make the physical volume available if it is in use
as a repository disk or as a storage pool disk.
– To remove a repository disk signature, run the following command:
cleandisk -r <physical volume name>
– To remove a storage pool disk signature, run the following command:
cleandisk -s <physical volume name>
CAUTION:
Ensure that the physical volume is no longer needed, as running the
cleandisk command results in loss of data on the physical volume.
To display the physical volumes that are not in use, run the following command:
lspv -free
For information about these requirements, contact your storage administrator.
To replace physical volumes to a storage pool, follow these steps:

view.
Configuration > Replace Physical Volumes.
3. Follow the instructions in the Replace Physical Volumes wizard to select
physical volumes to remove and then to add to the selected storage pool.

Related concepts:
Related reference:
Editing a storage pool threshold

When the amount of storage that is available drops below a certain percentage of
the total storage in the storage pool, a warning is displayed. This percentage is
called the storage pool threshold. You can specify this percentage for your
environment.
Before you can edit a storage pool threshold, ensure that at least one VIOS virtual
server in the associated VIOS shared storage pool is active.
To edit the storage pool threshold, follow these steps:

view.
Configuration > Edit Storage Pool Threshold.
3. In the Edit Storage Pool Threshold dialog, enter a value for the storage pool
threshold.
Related concepts:
Adding VIOS virtual servers to a shared storage pool

You can add Virtual I/O Server (VIOS) virtual servers to an existing shared storage
pool.
Before you can add a VIOS virtual server to a shared storage pool, you must
ensure that your environment satisfies the following requirements:
v The VIOS operating system is discovered and accessible in IBM Systems
Director.
inventory.
v At least one VIOS virtual server in the shared storage pool is active.
v The VIOS virtual server that you want to use in the shared storage pool is not a
member of another shared storage pool.
v Every VIOS virtual server that you want to add to the shared storage pool has
access to the repository disk and the physical volumes that make up the storage
pool associated with this shared storage pool. In addition, these physical
volumes must meet the minimum size requirement for the storage pool and not
be assigned to another VIOS virtual server or storage pool.
To add a VIOS virtual server to a shared storage pool, follow these steps:

view.
2. Right-click the shared storage pool that you want to edit and select System
Configuration > Add VIOS Virtual Servers.
3. Follow the instructions in the Add VIOS Virtual Servers dialog.
Related concepts:
Related tasks:
Related reference:
lscandidateviosvs command
addsspviosvs command
Removing VIOS virtual servers from a shared storage pool

You can remove Virtual I/O Server (VIOS) virtual servers from a shared storage
pool.
Before you can remove a VIOS virtual server from a shared storage pool, you must
ensure that your environment satisfies the following requirements:
v The VIOS operating system is discovered and accessible in IBM Systems
Director.
v At least one VIOS virtual server in the shared storage pool is active.
To remove a VIOS virtual server from a VIOS shared storage pool, follow these
steps:
view.
2. Right-click the VIOS shared storage pool that you want to edit and select
System Configuration > Remove VIOS Virtual Servers.
3. Follow the instructions in the Remove VIOS Virtual Servers wizard to select the
VIOS virtual server that you want to remove from the shared storage pool.
When you select a VIOS virtual server to remove, IBM Systems Director checks for
associations between the VIOS and client virtual servers. These associations are
displayed in the Virtual Storage Adapter Mappings table. Removing a VIOS with
such associations removes the path between the client virtual server and the
storage pool and could result in loss of running workloads. For information about
how to handle these client associations, see "Virtual storage adapter mappings."

Related concepts:
Related tasks:

Related reference:
lssspviosvs command
rmsspviosvs command
Deleting a shared storage pool

You can permanently delete a shared storage pool.
Before you can delete a shared storage pool, ensure that at least one VIOS virtual
server in the shared storage pool is active.
To delete a shared storage pool, follow these steps:

view.
2. Right-click the shared storage pool that you want to delete and select System
Configuration > Delete Shared Storage Pool
IBM Systems Director checks for associations between the VIOS virtual servers
in the shared storage pool and client virtual servers. These associations are
displayed in the Virtual Storage Adapter Mappings table. Deleting a shared
storage pool that has VIOS members with such associations removes the path
between the client virtual server and the storage pool and could result in loss
of running workloads. For information about how to handle these client
associations, see "Virtual storage adapter mappings."
3. Select Yes in the Delete Shared Storage Pool dialog when you are ready to
delete the shared storage pool.
Related concepts:
Related reference:
rmsharedstpool command
Removing the shared storage pool VIOS subagent

You can remove the shared storage pool VIOS subagent from your system with the
updateios command.
Using the updateios command will remove the following fileset:

v vios.agent
To remove the shared storage pool VIOS subagent fileset, run the following
command:
updateios -remove vios.agent

Chapter 12. Managing IBM System z systems
IBM Systems Director provides the capability to discover System z systems and
their associated virtual servers, and to access status information about them.
Related tasks:
System z virtualization
This topic provides information about the System z virtualization technologies.
System z provides two layers of virtualization:

System z LPAR hypervisor
A virtualization technology built into the System z hardware. With the
LPAR hypervisor, you can divide a System z mainframe into logical
partitions (LPARs). Each LPAR is assigned a dedicated portion of the
available physical memory (central storage, in System z terminology).
Storage devices, I/O channels, and processors can be shared across LPARs
or dedicated to a particular LPAR.
You can use the Integrated Facility for Linux (IFL) feature of the System z
hardware to set up LPARs that are restricted to Linux workloads. Such
LPARs have processors that cannot run operating systems other than Linux
and z/VM.
z/VM A System z operating system that acts as virtualization software.z/VM can
run in an LPAR. z/VM can virtualize all system resources, including
processors, memory, storage devices, and communication devices.
With z/VM, you can run hundreds of operating system instances
concurrently, all on the same System z hardware.
You can use a number of LPARs to concurrently run multiple instances of z/VM
while other LPARs run other mainframe operating systems. Each z/VM can run a
multitude of mainframe operating systems, including instances of z/VM itself.
Basics about the z/VM operating system

This topic gives a brief introduction to the z/VM operating system and provides a
reference for further information.
For more detailed information about the z/VM operating system, see the z/VM
Internet Library.
The z/VM control program
A core component of the z/VM operating system is the control program. The
control program (CP) is a virtualization layer that runs on the System z machine
architecture and efficiently provides multiple independent simulated System z
machines known as virtual servers (also known as virtual machines in z/VM
terminology). Any program that can run natively on a System z machine, such as
an operating system, can instead be run in a virtual server. To such a program, the

virtual server appears to be real System z hardware. The resources (processors,
memory, I/O devices, and so on) of each virtual server are provided by CP, using a
fraction of the real hardware resources. Each virtual server has a unique identifier
called the user ID.
An operating system running in a virtual server is called a guest operating system.

Users of a guest operating system typically use that operating system in the same
manner as if it were running natively on a System z machine.
Figure 1 shows several virtual servers running guest operating systems and the
virtual resources provided to them by CP.
Figure 16. z/VM virtual servers
The z/VM user directory
The z/VM operating system uses the z/VM user directory to keep track of its
virtual servers. For each virtual server, there is a directory entry with a number of
statements that define its characteristics.
For example, the directory entry defines the processing power, memory size
(virtual storage, in z/VM terminology), disk access permissions and other
privileges.
The directory is well-protected from general access. There are predefined z/VM
users that are privileged to perform administrative functions. Maintaining the
directory is among the tasks that require the highest privilege level in the z/VM
operating system. Many installations use a security manager in addition to this
built-in security.
Optionally, a program called a directory manager can be used to maintain the

directory. One such directory manager is the Directory Maintenance Facility
(DirMaint™), an optional component of z/VM.
Service machines
z/VM includes a number of service machines. Service machines are virtual servers
that provide specific services to other virtual servers. For example, there are service
machines that run programs required for communications or printing. Like any
other virtual server, a service machine is identified by the user ID.
The Systems Management Application Programming Interface
The Systems Management Application Programming Interface (API) is a facility in

z/VM that allows programs to perform a range of systems management functions

through one consistent interface. This interface has a client-server architecture in
which these programs are clients that communicate with a server that is provided
by z/VM. For more information, refer to z/VM Systems Management Application
Programming, SC24-6122 or SC24-6234.
Virtual networking
z/VM allows for a multitude of methods for communication between a guest

operating system and another guest operating system of the same z/VM, an
operating system instance elsewhere on the same System z mainframe, or a
networked operating system that runs on separate hardware. For a comprehensive
description of z/VM communications refer to z/VM Connectivity, SC24-6080 or
SC24-6174.
This section briefly introduces four methods that are particularly relevant to Linux
as a guest operating system:
v Direct connections from the z/VM virtual servers to an Open Systems Adapter
(OSA) card
v Guest LAN
v Virtual switch
v HiperSockets™
You can set up a virtual connection from each virtual server to an OSA card. The
OSA card provides a connection to a LAN outside the System z mainframe. All
virtual servers that are connected to the same OSA card can also communicate
with one another. Connecting in this context does not involve physical cables but
means issuing commands that define virtual connections.
Figure 17. z/VM virtual servers directly connected to an OSA card
You can also define a guest LAN. A guest LAN is a virtual LAN, emulated by the
z/VM operating system. Because a guest LAN does not use physical cables and is
contained entirely within the mainframe, it is fast and, if configured correctly,
highly secure.
Chapter 12. Managing IBM System z systems 559

Figure 18. z/VM virtual servers connected to a guest LAN
If you want to provide your virtual servers with a connection outside the z/VM
operating system, you can include a TCP/IP router in your guest LAN. The router
can be a virtual server with a Linux instance as the guest operating system or it
can be a TCPIP service machine.
You can also use a virtual switch to connect your virtual servers. Like a guest
LAN, a virtual switch does not use physical cables and can provide a fast and
highly secure connection.
Figure 19. z/VM virtual servers connected to a virtual switch
You can also connect your z/VM virtual servers using HiperSockets. Like a guest
LAN, HiperSockets provide a fast and secure network within the mainframe.
Linux Linux Linux Linux Linux

router
z/VM z/VM
LPAR A LPAR B
Hardware layer HiperSockets

OSA
System z9 or zSeries
LAN
Figure 20. z/VM virtual servers connected to a HiperSockets network
With HiperSockets you can span multiple LPARs on the same mainframe.
z/VM single system image feature
Introduced in z/VM 6.2, the optional z/VM single system image (SSI) feature
enables you to group up to four z/VM systems into a collection called a cluster.

The members of the cluster are then able to share certain resources in a
coordinated fashion. This feature is beneficial because it provides higher
availability of virtual servers, easier workload balancing, and simpler system
maintenance.
The cluster members share one common source z/VM user directory. In this
directory, each virtual server is defined with one of following configuration types:
Single-configuration
Single-configuration virtual servers can run on only one cluster member at
any given time.
Multiconfiguration
Multiconfiguration virtual servers can run on more than one cluster
member at any given time.
Note: As part of the definition of the multiconfiguration virtual server in

the z/VM user directory, you can define certain resources to be assigned to
the virtual server only when it is logged on to a specific member of the
cluster. IBM Systems Director recognizes such definitions, but you cannot
use IBM Systems Director functions to modify the defined resources.
An important capability provided by SSI is live guest relocation, which enables

you to move a single-configuration Linux virtual server from one cluster member
to another cluster member, all transparently and without disrupting its users.
Related reference:
z/VM Internet Library
z/VM manageability access point and agent

Common Information Model (CIM) is a standard related to systems management
defined by the Distributed Management Task Force. The z/VM manageability
access point is a virtual server (also known as a virtual machine in z/VM
terminology) that provides a CIM-based interface for managing z/VM.
The z/VM manageability access point is a managed resource that can be

discovered by IBM Systems Director. Each z/VM system that is to be managed by
IBM Systems Director must have exactly one manageability access point.
The manageability access point contains a Linux guest operating system with the
following IBM Systems Director components installed:
v Platform Agent
v z/VM Manageability Access Point Agent
The manageability access point uses the z/VM Systems Management API. The
Systems Management API server must be enabled and available.
Related tasks:
Installing the z/VM Manageability Access Point Agent
Viewing the System z Management summary page

You can view a summary of the resources managed by System z and their status.
You can also access common management tasks for managing your System z
resources. Note that information on this page is refreshed automatically when there
are any changes.

To view the System z summary, complete the following steps:
2. On the Home page, click Plug-ins, scroll to the System z Management portion
of the page, and click the System z Management section heading. The System
z Management summary is displayed.
3. View the System z Resource Status section. This section provides the following
information:
v A pie chart and corresponding list that indicate the number of System z
resources with the following types of status:
Critical
Warning
Informational
OK
v Links to the following common views that you can use to manage your
System z resources:
– Health summary
– Event log
– Problems
4. View the Manage Resources section. This section provides the following
information:
v System z Resources
– The number of System z platforms
– The number of Hardware Management Consoles (HMCs) and System z
servers
– The number of z/VM hosts
– The number of z/VM virtual servers
– The number of z/VM manageability access points
v Operating Systems
– The number of Linux on System z
v Links to the following tasks that you can use to get started with System z
Management:
– System discovery
– Monitors
– Thresholds
– Check for updates
– Set up z/VM manageability access points
Discovering systems and collecting inventory data for System z

In a System z environment, you can use IBM Systems Director to discover and
collect inventory data on the following types of resources: Linux on System z
servers, systems running the IBM z/VM Manageability Access Point Agent, and
the Hardware Management Console.
Linux on System z servers
Use IBM Systems Director to discover and request access to Linux on
System z servers, which are virtual servers associated with the z/VM
hypervisor or servers within System z logical partitions. For a virtual
server to be discovered, it must have an IP address and it must be running.

After IBM Systems Director discovers and requests access to a virtual
server, you can collect inventory to obtain additional information about the
virtual servers. The type of inventory information collected depends on
whether the system is an Agentless managed system, Platform Agent
managed system, or Common Agent managed system.
Systems running the IBM z/VM Manageability Access Point Agent
After IBM Systems Director discovers and requests access to a system
running the IBM z/VM Manageability Access Point Agent, you can view
information about the following resources:
v The Linux server in which the IBM z/VM Manageability Access Point
Agent is running
v The z/VM operating system
v The virtual servers defined for the z/VM system
After requesting access to the IBM z/VM Manageability Access Point
Agent, IBM Systems Director continues the discovery process for all the
virtual servers that are associated with the z/VM system. When virtual
servers are discovered, they are displayed in the Web interface.
After IBM Systems Director collects inventory on the IBM z/VM
Manageability Access Point Agent, you can view information about the
resources associated with the virtual servers defined on the z/VM system.
For example, you can view information about resources such as memory,
processors, network ports, and logical volumes.
Note: Inventory collection on the IBM z/VM Manageability Access Point

Agent can take a long time. It is recommended that you run inventory
collection on an IBM z/VM Manageability Access Point Agent no more
than once or twice per day.
Hardware Management Console (HMC)
If the HMC is running Simple Network Management Protocol (SNMP)
version 1 (v1) and a public profile, you can use the IP addresses to have
the System Discovery task discover the System z physical servers that are
managed by the HMC. However, if the HMC is not running SNMP v1 and
a public profile, then you must create a discovery profile to discover the
physical systems managed by the HMC.
Related tasks:
Managing power state settings for Linux on System z servers

Support for the Power On/Off task is provided by the operating systems on
System z servers.
Power On/Off task support by way of the operating system on

System z servers
Support for the Power On/Off task is provided by the operating system on System
z servers.
If either Platform Agent or Common Agent is installed, the Restart setting is

supported by the operating system. For details on the supported operating
systems, see "Supported operating systems".

Changing the power state on System z servers
Use the Power On/Off tasks to remotely restart a server in your
systems-management environment. For more information, see “Power On/Off task
support by way of the operating system on System z servers.”
access.”
Note: To power on a System z server, the server must be running within z/VM
and there must be an IBM z/VM Manageability Access Point Agent defined for it.
For details, see “Installing the IBM z/VM Manageability Access Point Agent”.

Explorer.
Related tasks:
Scheduling tasks
Installing the z/VM Manageability Access Point Agent

Chapter 13. Managing and configuring storage
IBM Systems Director provides facilities to manage and configure storage devices,
such as disks, switches, internal RAID controllers, and RAID subsystems. This
includes the use of IBM Systems Director features, SMI-S providers, and external
storage applications.
Planning for storage management

To manage most storage systems with IBM Systems Director, you need to install a
piece of management software from a third party. This is required for all storage
systems except IBM DS8000, XIV®, SAN Volume Controller, and V7000 storage
systems, which can be managed directly.
The management software has many different names: SMI-S CIM provider, storage
proxy, storage provider, or storage agent. It might also be referred to as the provider or
agent as well.
If your storage system requires an SMI-S CIM provider, print out this table and fill
out the information, then use it when installing the SMI-S CIM provider:
Table 45. Information to gather before installing an SMI-S CIM provider
Information needed Your information
Operating systems the SMI-S CIM provider can
run on, such as AIX or Windows
Review the storage system product information to

determine this.
Server that is running the supported operating
system
For example, this might be the server that is

running IBM Systems Director.
Ports for the SMI-S CIM provider to use
Determine whether the default CIM ports are in use.

The default ports are 5988 (HTTP) and 5989
(HTTPS).
v If the default ports are available, use default ports
when installing the SMI-S CIM provider.
v If the default ports are not available, use
non-default ports when you install the SMI-S-CIM
provider. A common practice is to add 1000 to the
port numbers. For example, you could specify
ports 6988 (HTTP) and 6989 (HTTPS).

Related concepts:
SMI-S providers
Related tasks:
Installing SMI-S Providers
Storage management in real time and using configuration templates

Storage is managed in two ways: in real time and with the use of configuration
templates. When managing storage in real time, changes become effective
immediately, or in some cases at the next restart if a restart is required to have the
changes take effect. When managing storage using configuration templates, you are
creating configuration templates that contain storage device definitions, but no
storage device is configured or altered. A configuration template must be deployed
in order to have its definitions take effect.
Many of the panels and their fields used to manage storage are similar whether
you are working with an actual storage device or a configuration template. When
providing detailed information about storage devices, you must be aware whether
you are changing a configuration template that can be used to deploy to the
storage device, or a making changes to the device itself in real time.
When working with a storage device in real time, the storage device is active and
connectivity to the device has been established. Also, the device has been
discovered and the system that the device is attached to is not locked or otherwise
unavailable. Changes made to the storage device, as it is displayed in the various
IBM Systems Director panels, become effective immediately when you click Apply
or Deploy. The device definitions are called configuration settings.
When working with configuration templates, you are providing definitions that
can be deployed on a storage device at some point in the future. Changes made in
the various IBM Systems Director panels, are really made to a configuration
template that contains the device definitions. When you click Save, the
configuration template is updated with your changes, but no storage device is
affected. If you want a configuration template to be deployed to a storage device,
you must do one of these things:
v Set up a configuration template or configuration plan to be automatically deploy,
which will then deploy when a device that matches it is discovered by IBM
Systems Director.
v Deploy the configuration template by selecting it from any panel that displays it,
and click Actions > Deploy.
Related concepts:
Related tasks:
Managing storage in real-time
Managing SMI-S providers

To use SMI-S providers with IBM Systems Director, you must install and configure
them. They are needed only for some devices.

SMI-S providers for IBM Systems Director
SMI-S providers must be installed and configured before IBM Systems Director can
manage certain storage devices.
Note: You cannot install the SMI-S providers on systems where the IBM Systems
Director Server or any agents are installed if the providers use ports that IBM
Systems Director Server uses. The default ports are 5988 and 5989 (http and https).
An SMI-S provider is a vendor-specific module that is used so that independent

management software, such as IBM Systems Director, can manage a vendor device
by using a standard interface that is based on the Common Information Model
(CIM) protocol.
Figure 21. SMI-S provider connection illustration
IBM Systems Director recognizes certain storage devices that comply with the
Storage Management Initiative Specification (SMI-S). SMI-S is an industry standard
that was developed by the Storage Networking Industry Association (SNIA).
IBM Systems Director communicates with the storage devices through their
respective SMI-S providers. Their Service Location Protocol (SLPv2) component
enables the devices to be discovered by IBM Systems Director, which looks for
SNIA-defined SLP service types. When the environment includes Chassis
Management Modules (CMM) or Integrated Management Modules (IMM), the
associated SMI-S providers are discovered by first discovering and collecting
inventory on the management modules. IBM Systems Director obtains information
about storage devices through the Common Information Model Object Manager
(CIMOM) component of the SMI-S provider. Communication occurs by using the
Distributed Management Task Force (DMTF) standard for Web-Based Enterprise
Management (WBEM) as required by SNIA. The information is organized
according to the DMTF standard for the Common Information Model (CIM), using
the profiles that are defined by SNIA.
When multiple SMI-S providers are installed on the same system, only one can use
the default port number. The other providers must be configured during
installation or be set up to use an alternative port number. When you add a
Chapter 13. Managing and configuring storage 567

storage device whose provider is using an alternative port number to the IBM
Systems Director environment, you must specify the port number.
The default port number for the SMI-S provider for the IBM BladeCenter S SAS
RAID Controller Module is displayed as 5988 regardless of what operating system
hosts the SMI-S provider. However, when this SMI-S provider is running on Linux,
the default port number is really 15988, and you must change the value to 15988 to
use the default port on Linux.
A storage provider is a module that performs the same tasks as an SMI-S provider,
but is not SMI-S compliant.
Storage devices that require an SMI-S provider

These storage devices require an SMI-S provider to work with IBM Systems
Director.
v Brocade 2G/4G/8G/16G Fibre Channel switch (IBM BladeCenter chassis and
external)
v EMC CLARiiON AX Series, AX4 Series, CX Series, CX3 Series, and CX4 Series
v EMC Symmetrix DMX Series and V-Max Series
v EMC VNX Series
v Hitachi Data Systems storage devices
v IBM System Storage DS3000 devices
v IBM System Storage N series N3600 devices
For the IBM Flex System Fabric CN4093 10 GB Converged Scalable switch, the
storage provider is embedded in the switch. There is no need to install anything.
When asked for the IP address of the SMI-S provider, use the IP address of the
switch itself.
For the QLogic 4 Gbit/sec Fibre Channel (IBM BladeCenter chassis and external)
switch, the storage provider is embedded in the switch. There is no need to install
or configure anything. When asked for the IP address of the SMI-S provider, use
the IP address of the switch itself.
Integrated RAID Controller devices use the IBM Systems Director Platform Agent
managed system. Run Inventory Collection on the Agent to get the Integrated
RAID Controller.
The IBM BladeCenter S SAS RAID Controller Module requires an SMI-S provider
in order for IBM Systems Director to discover and manage the attached SAS RAID
Controller Module storage. This provider is installed automatically with IBM
Systems Director Server on supported operating systems. This provider has one of
the following names:
v PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module R3
Linux
Windows
Linux
Windows

Linux
Windows
Note: For more information about updating or installing the controller modules,
see “Installing the SMI-S provider for the IBM BladeCenterS SAS RAID Controller
Module on additional systems.”
The provider for the IBM BladeCenter S SAS RAID Controller Module can work
with a maximum of four IBM BladeCenter chassis. This provider can be copied to
Platform Agent managed systems if the need arises, and each of these Platform
Agent managed systems can also manage a maximum of four IBM BladeCenter
chassis.
To learn more about storage device support, see this information center topic:
Supported storage devices.
Applicable standards
For information about the previously mentioned standards, see these websites:
SMI-S http://www.snia.org/forums/smi/tech_programs/smis_home
SNIA https://www.snia.org
DMTF
www.dmtf.org
WBEM
www.dmtf.org/standards/wbem/
CIM www.dmtf.org/standards/cim
Related concepts:
Where to obtain SMI-S providers
Related tasks:
Installing the SMI-S provider for the IBM BladeCenter S SAS RAID Controller
Configuring SMI-S providers

Use the following information to obtain SMI-S providers for any IBM System
Storage DS3000, DS4000, or DS5000 devices, and IBM System Storage N series
N3600 devices. You can also use the information to obtain providers for various
switches used to manage storage devices.
IBM System Storage DS3000, DS4000, or DS5000
The SANtricity SMI Provider from NetApp that complies with SMI-S
version 1.4 is required to enable discovery of IBM System Storage DS3000,
DS4000, or DS5000 devices. You can obtain this provider from the NetApp
SMI-S and VDS/VSS Providers for E-Series OEM Storage Systems website
at http://support.netapp.com/apbu/oemcp/protcd/ (registration
required). It is recommended to use the 10.19.GG.xx version of this
provider for this version of IBM Systems Director. Any other version might
not function as well.

Note:
v To access the previously specified NetApp web page, you must first
register as a Guest User on the NetApp site. After successfully
registering or signing in as a NetApp Guest User, click the previously
specified link to access the download page.
v You can manually add an IBM System Storage DS3000, DS4000, or
DS5000 device by using IBM Systems Director. To manually add those
devices, specify the IP address of the system where you installed the
SANtricity SMI Provider, not the IP address of the IBM System Storage
DS3000, DS4000, or DS5000 device itself.
IBM System Storage N series N3600
You can obtain the ONTAP SMI-S provider for the IBM System Storage N
series N3600 from NetApp Data ONTAP SMI-S Agent website at
http://www.netapp.com/us/company/leadership/industry-standards/
smi-s-agent.html. It is recommended to use the 3.0.2 version of this
provider for this version of IBM Systems Director. Any other version might
not function as well.
Note: To download the provider, you must first register as a Guest User
on the NetApp site. The NetApp Data ONTAP SMI-S Agent website
provides the necessary instructions.
Brocade switches
You can obtain the appropriate SMI-S version 1.2 provider for IBM Systems
Director from the Brocade SMI Agent Drivers & Downloads website at
www.brocade.com/support/SMIAGENT.jsp. It is recommended to use the
120.11.0 version of this provider for this version of IBM Systems Director.
Any other version might not function as well.
If you want to use Brocade Network Advisor, you can obtain more
information from the Brocade Network Advisor website at
http://www.brocade.com/products/all/management-software/product-
details/network-advisor/index.page. It is recommended to use the 11.1.x
version of this provider for this version of IBM Systems Director. Any
other version might not function as well.
QLogic switches
There is no need to obtain an SMI-S provider for the QLogic switches. The
SMI-S provider is embedded in the switch.
Related concepts:
Storage devices that require an SMI-S provider
Related tasks:
Use of IP addresses with SMI-S providers

When you use IP addresses with SMI-S providers, consult this table to determine if
both IPV4 format and IPV6 format addresses are acceptable, or if only IPV4 format
can be used.

Table 46. IP address formats used with SMI-S providers
SMI-S provider Devices controlled IP address format accepted
Brocade SMI-S provider 2 Gbit/sec Fibre Channel IPV4 and IPV6 (The API and
switch tools use only IPV4)
4 Gbit/sec Fibre Channel
switch
switch
switch
IBM IBM BladeCenter SAS IPV4
Connectivity Module
IBM IBM BladeCenter SAS RAID IPV4
Controller Module
IBM IBM Flex System Fabric IPV4
CN4093 10 GB Converged
Scalable switch
NetApp ESC SMI-S IBM System Storage IPV4 and IPV6
providers 10.10.G5.02, DS4000
10.19.GG.xx IBM System Storage
DS3200
IBM System Storage
DS3300
IBM System Storage
DS3400
QLogic 2 Gbit/sec Fibre Channel IPV4
switch
switch
switch

IBM Systems Director requires SMI-S version 1.1, 1.2, 1.3, or 1.4 providers to enable
discovery of those devices.
The SMI-S provider for the IBM BladeCenter SAS RAID Controller Module is
installed by default when the IBM Systems Director Server is installed. However,
discovery needs to be run for the IBM Systems Director Server, and it must be
unlocked in order to use this SMI-S provider.
Note: You cannot install the SMI-S providers on systems where the IBM Systems
Director Server or any agents are installed if the providers use ports that IBM
Systems Director Server uses. The default ports are 5988 and 5989 (http and https).
To install an SMI-S provider, complete the following steps:

1. Obtain and install the needed SMI-S provider onto a computer system in the
IBM Systems Director environment. For more information about how to obtain
SMI-S providers, see “Where to obtain SMI-S providers”.
2. Register the SMI-S provider with IBM Systems Director. Using System
Discovery, specify the IP address or host name of the system. The discovery
process uses SLP to locate the provider and query the relevant attributes.
3. Unlock the SMI-S provider, which requires a user ID and password.

4. After the SMI-S provider is unlocked, the storage devices that are being
managed by that provider become visible in IBM Systems Director as storage
systems.
5. Required when updating a provider: If you update a provider, you must
re-collect inventory on the managed storage subsystems after installing the new
provider.
Related concepts:
SMI-S providers
Related tasks:
Configuring the SMI-S provider for the IBM BladeCenter S SAS RAID Controller
Module
Installing the SMI-S provider for the IBM BladeCenter S SAS

RAID Controller Module on additional systems
The SMI-S provider for theIBM BladeCenter S SAS RAID Controller Module is
installed automatically with the IBM Systems Director Server on supported
operating systems. There is a limitation that this SMI-S provider on any one system
can manage only four IBM BladeCenter chassis. In order to manage additional
chassis, you can install this SMI-S provider on additional compatible Platform
Agent managed systems, and have these systems also perform storage
management tasks.
v IBM BladeCenter SAS RAID Controller Module R3 (Linux or Windows) is
compatible with IBM Systems Director Platform Agent 6.3.
compatible with IBM Systems Director Platform Agent 6.2 and 6.2.1.
compatible with IBM Systems Director Platform Agent 5.20.31.
The SMI-S provider for the IBM BladeCenter S SAS RAID Controller Module has
one of these operating-system dependent names:
Linux
v PlatformAgentSubagent IBM BladeCenterSAS RAID Controller Module R3
Windows
v PlatformAgentSubagent IBM BladeCenterSAS RAID Controller Module R2 Linux
Windows
v PlatformAgentSubagent IBM BladeCenterSAS RAID Controller Module R1 Linux
Windows
Important: Make sure that the managed system meets the following requirements:
v Before installing either R3 module, the managed system must have the following
software installed:
– Platform Agent 6.3
– The appropriate supported operating system:
- For the Linux module: Redhat Enterprise Linux 6.1 (32 bit) or SUSE Linux
Enterprise Server 11 SP1 (32 bit)

- For the Windows module: Windows Server 2008, Enterprise, Standard, and
Datacenter Editions R2
v Before installing either R2 module, ensure that you already installed Platform
Agent 6.2 or 6.2.1 on the managed system.
v Before installing either R1 module, ensure that you already installed Platform
Agent 5.20.31 on the managed system. It is possible to install the subagent
without this prerequisite, but the installation completes with errors and the
subagent cannot be used.
In this discussion, the system that currently has the SMI-S provider for the IBM
BladeCenter S SAS RAID Controller Module is called the source system and the
SMI-S provider on this system is called the source provider. The new system to
receive the provider is called the target system and the provider on it is called the
target provider. The source and target providers are identical software, but will be
configured to manage different storage systems.
To install the SMI-S provider for theIBM BladeCenter S SAS RAID Controller
Module on another system, complete the following steps:
Note: On managed systems that have both SUSE Linux Enterprise Server 11 SP1
(32 bit) and the R2 module installed, updating Platform Agent from version 6.2.x
to version 6.3 automatically installs the R3 module. For other managed systems,
use the following instructions.
1. Select the target system in the Resource Explorer area. Note: Collect inventory
on the target system before this step.
2. Click Actions > Release Management > Install Agent. The Install Agent
3. In the Install Agent wizard, choose the name of the SMI-S provider.
Important: You can install only an SMI-S provider on a compatible platform

agent. Incompatible installations either fail or do not work.
4. Verify that the correct target system is selected.
5. Click Run. The installation of the SMI-S provider onto the target system starts
to run.
6. Wait for this process to complete.
7. Configure the target provider so that it manages some of the storage systems
formerly managed by the source provider.
8. Configure the installed provider by following these steps:
a. Wait 5-7 minutes after installation, then rediscover the system.
b. The system will be partially locked, and you must request access again.
c. Follow the steps in this topic for instructions: “Configuring the SMI-S
provider for the IBM BladeCenter S SAS RAID Controller Module” on page
577.
9. If necessary, repeat these steps for additional target systems, until the source
system has a more reasonable workload.
If it is necessary to undo this task, you must manually remove the SMI-S provider
from the target system, and then configure the source provider to again manage
the storage systems that the target provider was managing.

Installing the NetApp SMI-S provider on Windows systems
The NetApp SMI-S provider is needed to manage IBM System Storage DS3000,
DS4000, and DS5000 storage systems. Use these instructions to install the NetApp
SMI-S provider on Windows systems.
To install the NetApp SMI-S provider on Windows systems, complete the following
steps:
1. Go to the NetApp website at http://support.netapp.com/apbu/oemcp/
protcd/.
Note: Registration is required to obtain the provider from NetApp.

2. Use the download links on the NetApp page to find and download the
appropriate SMI-S provider.
v Eagle4: 10.19.GG
v Eagle2: 10.10.G5
3. Extract the downloaded files and run the installation file. The InstallAnywhere
welcome page opens. Complete the installation wizard.
v On the Create/Edit ArrayHosts.txt file page, enter the IP addresses of
controllers in the IBM System Storage system. Your storage system might
have one or more controllers. Be sure to enter the IP address of every
controller.
Note: If the operating system reboots, start the CIM server manually.
4. Follow these steps to enable authentication: “Enabling Authentication for the
NetApp SMI-S provider” on page 578.
Related concepts:
SMI-S providers
Installing the NetApp SMI-S provider on AIX and Linux systems

The NetApp SMI-S provider is needed to manage IBM System Storage DS3000,
DS4000, and DS5000 storage systems. Use these instructions to install the NetApp
SMI-S provider on AIX and Linux systems.
1. Go to the NetApp website at http://support.netapp.com/apbu/oemcp/
protcd/.
Note: Registration is required to obtain the provider from NetApp.

2. Use the download links on the NetApp page to find and download the
appropriate SMI-S provider.
v Eagle4: 10.19.GG
v Eagle2: 10.10.G5
3. View the appropriate readme file for installation instructions.
Note: If the operating system reboots, start the CIM server manually.
4. After the installation is finished, you must enable authentication.

Related concepts:
SMI-S providers
Related tasks:
Enabling Authentication for the NetApp ESG SMI-S provider
Installing and configuring the Brocade SMI-S provider and SLP

service
Use this procedure to install and configure the SMI-S provider associated with the
Brocade switch, and the SLP service associated with the Brocade switch.
Installing and configuring the Brocade SMI-S provider:
Use this procedure to install and configure the SMI-S provider associated with the
Brocade switch. This switch connects to storage systems attached with the Brocade
2 Gbit/sec and 4 Gbit/sec Fibre Channel switches.
To install and configure the Brocade SMI-S provider, complete the following steps:
1. Run install.exe to start the installation wizard.
2. Complete the wizard.
a. On the “Proxy Connections Configuration” page, click Add. Enter these
values in the window that opens:
Proxy IP: The IP address of the Brocade switch
User name: The user ID used to access the Brocade switch
Password: The password used to access the Brocade switch
Protocol: RPC
No. of RPC Handles: 1
b. On the “Configuring and Starting as a Service” page, click Yes for Do you
want to start SMI Agent as a Service.
3. When the installation is complete, go to the next topic to install and configure
the SLP service.
Related concepts:
SMI-S providers
Related tasks:
Installing the SLP Service
Related reference:
Switch has unexpected status of Offline
Installing the SLP Service:
Use this procedure to install the SLP service. This provider is needed to use SLP
when running Discovery.
Make sure that you have installed and configured the Brocade SMI-S provider
before starting this task.
To install the SLP service, complete the following steps:

1. Stop the Brocade SMI Agent service by clicking Stop the service on the
Services (Local) page.
2. Open a command window.

3. Issue this command: cd root_install_directory\agent\bin where
root_install_directory is the full path name of the directory where Brocade SMI-S
provider is installed.
4. Issue this command: slpd -install. The message 'Service Location Protocol
installed' is displayed when the installation process completes.
5. Issue this command: slpd -start The message 'Service Location Protocol started'
is displayed.
6. Start the Brocade SMI Agent service by clicking Start the service on the
Services (Local) page.
Installing and configuring the IBM N series SMI-S provider on

Linux systems
The IBM System Storage N series SMI-S provider is needed to manage IBM System
Storage N series 3600 storage systems. Use these instructions to install the IBM N
series SMI-S provider on Linux systems.
First, obtain this SMI-S provider from the IBM Web site. For instructions, see
“Where to obtain SMI-S providers”.
To install the IBM System Storage N series SMI-S provider on your Linux system,
1. From the directory where you placed the tar file, perform the following actions:
a. Extract the contents of the SMI-S provider tar file by using the tar xvf
./smisagent-<version>.tar command.
b. Install the provider in /usr/ws by running the ./install_smisproxy /usr
command. You can run the remaining commands from any directory.
2. Start the SLP daemon by using the /usr/ws/bin/slpdservice -start command.
3. Start the SMI-S provider server by running the /usr/ws/server/cserver/bin/
start_server command.
4. For each N series storage subsystem that the SMI-S provider is to manage, run
the /usr/ws/bin/smis <Linux server ID> <Linux server password> add <N
series host name or IP address> <N series userID> <N series password>
command.
You have installed, configured, and started the IBM System Storage N series SMI-S
provider.
Related concepts:
SMI-S providers

SMI-S providers must be configured in order to work with your storage systems.
SMI-S providers are used to add or remove devices associated with the SMI-S
provider, from within IBM Systems Director.
Configuration information and requirements for specific SMI-S providers vary by

provider and release. They are found in the 'Readme' or similar files that ship with
the SMI-S provider. Read these files and set up your environment according to the
instructions. It is crucial for all of the specified requirements to be met, so that IBM
Systems Director can properly manage the storage devices.

Related concepts:
SMI-S providers
Related tasks:
Configuring the SMI-S provider for the IBM BladeCenter S SAS

RAID Controller Module
The SMI-S provider for the IBM BladeCenter S SAS RAID Controller Module must
be configured before it can be used.
On AIX systems, you must install the SMI-S provider before you perform this task.
Follow the instructions in the “Installing SMI-S Providers” topic.
On Microsoft Windows and Linux systems, the SMI-S provider for the IBM
BladeCenter SAS RAID Controller Module is installed by default when the IBM
Systems Director Server is installed. However, discovery needs to be run for the
IBM Systems Director Server, and it must be unlocked in order to use this SMI-S
provider. To configure the SMI-S provider for the IBM BladeCenter S SAS RAID
Controller Module, complete the following steps:
1. Click Resource Explorer > Groups > Groups by System Type > Storage
Systems. A table of storage groups is displayed.
2. Select the group named SMI-S Providers.
3. Click Actions > View Members. A list of systems is displayed.
4. Select a system that hosts an SMI-S provider for the IBM BladeCenter S SAS
RAID Controller Module.
5. Click Actions > System Configuration > SMI-S Provider Configuration. The
SMI-S Provider Configuration page is displayed.
6. Click Actions > Add Storage System.
7. Choose one of these options:
v Click Select a Storage System that has already been discovered and click
Browse to see a list of existing, discovered IBM BladeCenter chassis.
v Click Enter storage system information manually and type the IP addresses
for the primary and secondary controllers.
Note: When the device has two controllers (dual controller mode), you must
specify IP addresses for both the primary and the secondary controllers.
8. Type the user ID and password for the management port. The default user ID
and password are USERID1 and PASSW0RD (with a zero). Use the default user
ID and password unless they were changed.
9. Click OK to save the changes.
Related tasks:
Adding IBM BladeCenter Integrated Storage devices to a server
Configuring the SMI-S provider for IBM System Storage DS3000,

DS4000, and DS5000
The SMI-S provider for the IBM System Storage DS3000, DS4000, and DS5000 must
be configured before it can be used.
To configure this SMI-S provider, follow these steps:

1. Click Resource Explorer > Groups > Groups by System Type > Storage
Systems. A table of storage groups is displayed.
2. Select the group named SMI-S Providers.

3. Click Actions > View Members. A list of systems is displayed.
4. Select a system that hosts an SMI-S provider for the IBM System Storage
DS3000, DS4000, and DS5000 Controller Module.
5. Click Actions > System Configuration > SMI-S Provider Configuration > IBM
DS3000/4000/5000. The SMI-S Provider Configuration page is displayed.
6. Click Actions > Add Storage System.
7. Choose one of these options:
v Click Select a Storage System that has already been discovered, then click
Browse to see a list of existing, discovered IBM System Storage DS3000,
DS4000, and DS5000 storage systems.
v Click Enter storage system information manually and enter the IP addresses
for the primary and secondary controllers.
8. Specify the user ID and password for the management port. The user ID and
password were specified when you enabled authentication for the provider.
If you did not already enable authentication, see the following topic for
instructions: “Enabling Authentication for the NetApp SMI-S provider (Version
10.19.GG.xx)” on page 579.
9. Click OK to save the changes.
Enabling Authentication for the NetApp SMI-S provider

After this SMI-S provider is installed, review your authentication settings and
make any necessary changes.
This SMI-S provider is shipped with authentication disabled. It is available to be

enabled only if the SMI-S provider and CIMOM packages were installed together.
If you install the SMI-S provider into an existing CIMOM, this CIMOM is
responsible for authentication.
For authentication instructions, see the installation manual that is downloaded

with the provider.
Now that the authentication is enabled, you must verify this SMI-S provider.
Related concepts:
SMI-S providers
Verifying the NetApp SMI-S provider:
Once you have enabled authentication, verify the installation and configuration of
this SMI-S provider.
To verify the NetApp SMI-S provider, complete the following steps:

1. Open a command window.
2. Issue this command: cd C:\program files\EngenioProvider\wbemservices\
bin.
3. Issue this command: cimworkshop. The Login page is displayed.
4. Authentication is not enabled by default, so enter anything for the user ID
and password. A page with the /interop directory tree is displayed.
5. Change /interop to Isissi11:
6. Click Actions > Find Class. An Input pop-up is displayed requesting the
name of the class to find.
7. Type the name CIM_ComputerSystem.

8. Click OK.
9. Wait for the search to complete. A directory tree with the
CIM_ComputerSystem entry is displayed.
10. Right click on the entry LSISSI_StorageManagementSystem.
11. Click Show Instance. A list of instances is displayed.
12. If you see a list of instances, then the NetApp SMI-S provider has been
successfully installed and configured.
13. Optional: If you do not see any instances:
a. First retry the steps in this task carefully.
b. Check the IP addresses inside the arrayhosts.txt file in the
..\EngenioProvider\SMI_SProvider\bin directory, and make sure that
they are the IP addresses of the storage subsystem controllers.
c. If that does not resolve the problem, contact your service provider.
Enabling Authentication for the NetApp SMI-S provider (Version

10.19.GG.xx)
After this SMI-S provider is installed, review your authentication settings and
make any necessary changes.
To enable authentication, follow the procedure indicated in the documents that are
included with the provider. To download the provider, use the instructions listed
for IBM System Storage DS3000, DS4000, or DS5000 in Where to obtain SMI-S
providers.

Storage devices including disks, switches and storage controllers must be
discovered. The systems that these devices are attached to must have inventory
collection run.
Related concepts:
SMI-S providers
Related tasks:
Running Discovery and unlocking storage devices using

SMI-S providers
Run Discovery for your storage devices before you can view or make changes to
them. This topic describes a basic discovery procedure.
Note: Before you run discovery for your storage devices by using an SMI-S
provider, you must install and configure the provider. For more information about
storage devices that require SMI-S providers and for instructions about how to
install and configure the providers, see the related reference topic, Managing SMI-S
providers.
The procedure works by using an IP address for an SMI-S Provider, under the
assumption that systems that have access to the SMI-S Provider are those systems
that have the storage that the SMI-S Provider controls. To run System Discovery
for systems that have an SMI-S Provider, complete the following steps:

Note: If your environment includes Chassis Management Modules (CMM) or
Integrated Management Modules (IMM), before you discover storage devices that
have SMI-S providers, you must discover, request access to, and collect inventory
for the management modules. For more information, see “Discovering IMMs for
managing and updating physical servers.”
1. From the Initial Setup tab of the Home page click System Discovery. The
System Discovery page is displayed.
2. Click Single system (IP address).
3. Type the IP address of the storage provider in the IP address field.
4. Click Discover.
5. Wait for the task to complete. A table of systems that have this SMI-S Provider
is displayed.
6. Select a system. An entry for this system is displayed.
7. If the Access field indicates No Access:
a. Click the No Access link.
b. Type a user ID and password for the system. (The user ID and password
that are needed are most likely the same as the operating system user ID
and password.)
c. Click Request Access.
Access to the system is established.
8. From the Resource Navigator, a list of storage devices is displayed along with
the system that was discovered.
Related concepts:
SMI-S providers
Related tasks:
Related reference:
Running Direct Connection discovery and unlocking storage

devices using SMI-S providers
Discover storage devices by searching for systems that have the SMI-S provider for
that type of storage. This topic describes an advanced discovery procedure.
Note: Before you run discovery for your storage devices by using an SMI-S
provider, you must install and configure the provider. For information about
storage devices that require SMI-S providers and for instructions about how to
install and configure the providers, see the related topic, “Managing SMI-S
providers”.
The procedure works by using an IP address for an SMI-S provider, under the
assumption that systems that have access to the SMI-S provider are those systems
that have the storage that the SMI-S provider will access.
To run system discovery for systems that have an SMI-S provider, follow these
steps:
1. From the Initial Setup tab of the Home page, click System Discovery. The
System Discovery page opens.

2. Under Advanced Tasks, click Create new profile. The Discovery Profile wizard
starts. Specify the following values:
v On the Profile Properties page, for Resource type, select Operating System.
SMI-S providers are viewed as if they were operating systems.
v On the SMI-S Configuration page, specify these values:
– Select Direct Connection as the type of SMI-S discovery.
– Accept the default port number unless it is already in use.
Note: For some types of hardware, the port number might not be correct.
Review the following choices and correct the port number if necessary.
Table 47. Port numbers for hardware models
Operating system
that hosts the
Hardware model Protocol provider Port number
IBM BladeCenter S http Microsoft Windows 5988
SAS RAID Controller Server 2003
Module
Microsoft Windows
Server 2008
Linux 15988
Brocade Fibre http Microsoft Windows 5988
Channel switch Server 2003
https 5989
Microsoft Windows
Server 2008
Linux
IBM System Storage http Microsoft Windows 5988
DS3000, DS4000, and Server 2003
https 5989
DS5000
Microsoft Windows
Server 2008
Linux
IBM System Storage http All 5988
N3000
https 5989
For more information about the supported operating systems, see the
following topic: Supported storage devices.
3. The new profile is listed on the Discovery Profiles table.
4. Select the new profile and click Run. The Launch Job window opens. You can
run the task now or schedule it for later.
5. When you run the task, monitor its status. It could take a long time.
6. If you selected Request access later on the Access Request page in step 2,
access the systems after the task completes.
a. Open the SMI-S Providers storage group by clicking Resource Explorer >
Groups by System Type > Storage Systems > SMI-S Providers.
b. Select a system. The Access field indicates No Access. Click No Access.
c. Enter a user ID and password for the system.
d. Click Request Access.
Access to the system is established.

7. From the Resource Navigator, a list of storage devices is displayed along with
the system that was discovered.
Related concepts:
SMI-S providers
Related tasks:
Related reference:
Running System Discovery for multiple SMI-S providers using

multicast and broadcast
Using multicast and broadcast, multiple SMI-S providers can be discovered at the
same time.
The Service Location Protocol (SLP) is used for SMI-S multicast and broadcast
discovery. SLP is used for clients to locate servers and other services on the
network. This procedure uses two advanced SLP methods (multicast and
broadcast) to find all SMI-S providers, and it performs the following actions:
v Sends an SLP request to the default multicast group
v Sends an SLP request to the broadcast group
v Using these two functions, trys to find all your SMI-S providers
To run system discovery for multiple SMI-S providers by using multicast and
broadcast, complete the following steps:
1. From the Initial Setup tab of the Home page, click System discovery. The
System Discovery page is displayed.
2. In the Advanced Tasks area, click Create new profile. The Discovery Profile
3. If you see the Welcome page:
a. Clear Show this Welcome page next time if you do not want to see the
b. Click Next.
The Profile Properties page is displayed.
4. Type a name for the Discovery profile that you are creating.
5. Select a resource type of Operating System. SMI-S providers are viewed as if
they were operating systems.
6. Select a resource subtype of All.
7. Type a description of the new profile.
8. Click Next. The Protocol selection page is displayed.
9. Click Storage Management Initiative Specification (SMI-S) Discovery.
10. Click Next. The SMI-S Configuration page is displayed.
11. Select the type of discovery. Click Multicast and broadcast.
12. Click Enable multicast.
13. Click Enable general broadcast.
14. Choose a timeout period of 60 seconds.

15. Click Next. The Access Request page is displayed.
16. Optional: Click Request access later. Because multiple SMI-S providers are
discovered, it is not advisable to automatically request access to the
discovered systems. Unless all discovered SMI-S providers have the exact
same user ID and password, the access request fails.
17. Click Next. The Inventory Discovery page is displayed.
18. Click Discover (collect) inventory later.
20. Carefully examine the discovery information that is on the Summary page.
v If everything is correct, click Finish to create the profile.
v If something must be corrected, click Back or select the page to return to
from the navigation area.
A table of discovery profiles is displayed, with an entry for the new profile
that you created.
21. Select this profile and click Run. A scheduler window is displayed below the
table of profiles.
22. Choose to run the task now, or specify options for running later.
23. Click OK.
24. Monitor the status of this job. It could potentially take a long time.
25. To see the systems with SMI-S Providers as they are discovered, click
Resource Explorer > Groups > All Systems. As the systems with SMI-S
providers are discovered, they are added to the All Systems group.
Related concepts:
SMI-S providers
Related tasks:
Collecting inventory for devices managed by IBM Tivoli

Storage Productivity Center
Using IBM Tivoli Storage Productivity Center with IBM Systems Director makes it
easy to retrieve the latest inventory data for all devices that are managed by IBM
Tivoli Storage Productivity Center.
Discovering and running inventory against a Storage Farm (which represents the
IBM Tivoli Storage Productivity Center server) causes Systems Director to fully
populate all of the devices that are managed by IBM Tivoli Storage Productivity
Center, including Fibre Channel switches and storage subsystems. Running
inventory against the Storage Farm retrieves only the existing inventory
information from the IBM Tivoli Storage Productivity Center server. Collecting
inventory also discovers new devices after the data sources are added and removes
devices after the data sources are deleted.
Running inventory against a specific device uses an IBM Tivoli Storage

Productivity Center probe to retrieve the most current configuration changes for
the device. In this case, running inventory also updates both the associated
Systems Director inventory data and the IBM Tivoli Storage Productivity Center
server.

Any time configuration changes are made to managed devices outside of Systems
Director, you must run inventory on a specific device to update the associated
inventory.
Note: You can collect inventory for only one device in a Storage Farm at a time.
Collecting inventory at the same time for multiple devices that are managed by
IBM Tivoli Storage Productivity Center is not supported.
After a modifying the configuration for a device that is managed by IBM Tivoli
Storage Productivity Center, running inventory against that device causes the IBM
Tivoli Storage Productivity Center server to update the device configuration. (For
example, configuration modifications might be modifying a zoning configuration
on a fabric switch or creating a storage volume on a storage subsystem.) After that
process completes, Systems Director retrieves and displays the updated inventory
data.
1. Navigate to the device managed by IBM Tivoli Storage Productivity Center for
which you want to collect inventory.
2. Right-click the name of the device, then select Inventory > View and Collect
Inventory. The View and Collect Inventory page is displayed.
3. On the View and Collect Inventory page, make sure that the selected profile is
All Inventory, then click Collect Inventory. The View and Collect Inventory
page dynamically updates the information for the device.
Related reference:
collectinv command
Working with external storage applications

Use an external storage management application to configure, control, and
maintain certain storage devices and their connectivity to your network. If the
necessary external storage management applications are not already installed,
consult the appropriate documentation to acquire and install them.
The external storage management application to be run must be installed or

accessible. You must run inventory collection on the storage devices before you can
launch an external storage management application for those storage devices.
This list describes the application to be used for each storage device.
v IBM Tivoli Storage Productivity Center for SAN-attached devices
v DS4000 Storage Manager for IBM DS3000, DS4000, and DS5000 storage devices
v IBM System Storage N series N3600 features browser-based management, so no
application needs to be installed
v ServeRAID Manager for Internal RAID controllers
The External Storage Applications page is built based on the inventory of your
storage devices. The applications are displayed only if your inventory has storage
devices that can be managed by these applications.
All of the external storage applications except IBM Tivoli Storage Productivity
Center can be launched after you select a target resource.
Installing and configuring external storage applications

Storage systems management uses some storage applications, which must be
installed and configured prior to managing storage devices.

Related tasks:
Launching an external storage management application
Installing and configuring IBM Tivoli Storage Productivity Center

If you want to use IBM Tivoli Storage Productivity Center with IBM Systems
Director, IBM Tivoli Storage Productivity Center must be installed and properly
configured. You can either use an existing installation of IBM Tivoli Storage
Productivity Center or you can download IBM Tivoli Storage Productivity Center
Limited Edition.
Note: When you are running IBM Systems Director 6.3.2, it is recommended to use
IBM Tivoli Storage Productivity Center 4.2.2.143. A lower version is not
recommended, although any higher 4.2 version is compatible with Systems
Director.
To install and configure IBM Tivoli Storage Productivity Center, complete the
following steps:
1. Download IBM Tivoli Storage Productivity Center Limited Edition from the
Passport Advantage® web page.
Note: Your company must have a Passport Advantage contract to download

from Passport Advantage. If you are not enrolled, see this web page for
instructions: How to enroll.
2. For instructions on how to install IBM Tivoli Storage Productivity Center, see
the IBM TotalStorage Productivity Center Installation and Configuration Guide.
Notes:
v The directory to which you extract the IBM Tivoli Storage Productivity
Center code for installation and the directory where you choose to install
IBM Tivoli Storage Productivity Center both have a limit of 60 characters in
the path name.
v The source directory from which IBM Tivoli Storage Productivity Center is
installed cannot have a hyphen character (-) anywhere in the path name.
3. If IBM Tivoli Storage Productivity Center is installed on the same system as
IBM Systems Director Server, you must configure SNMP trap forwarding
between IBM Systems Director and IBM Tivoli Storage Productivity Center.
Configuring SNMP trap forwarding for IBM Tivoli Storage

Productivity Center
If IBM Tivoli Storage Productivity Center is installed on the same system as IBM
Systems Director, you must configure SNMP trap forwarding between IBM
Systems Director and IBM Tivoli Storage Productivity Center.
You do not need to configure SNMP trap forwarding if IBM Systems Director and
IBM Tivoli Storage Productivity Center are installed on different systems.
Complete the following steps to forward SNMP traps without modification:

1. Using a text editor, edit a file named SNMPServer.properties in the
IBM\Director\data\snmp directory.
2. To forward SNMPv1 traps:
a. Remove the # character at the beginning of this line:
#snmp.trap.v1.forward.address.1=

b. Type the IP address of the SNMPv1 trap destination after the equal sign (=).
This is the IP address of the local system where IBM Systems Director
Server and IBM Tivoli Storage Productivity Center are installed.
c. Remove the # character at the beginning of this line:
#snmp.trap.v1.forward.port.1=
d. Type the port number of the SNMPv1 trap destination after the equal sign
(=). It is recommended that you use port 22162.
3. To forward SNMPv2 traps:
a. Remove the # character at the beginning of this line:
#snmp.trap.v2.forward.address.1=
b. Type the IP address of the SNMPv2 trap destination after the equal sign (=).
This is the IP address of the local system where IBM Systems Director
Server and IBM Tivoli Storage Productivity Center server are installed.
c. Remove the # character at the beginning of this line:
#snmp.trap.v2.forward.port.1=
d. Type the port number of the SNMPv2 trap destination after the equal sign
(=). It is recommended that you use port 22162.
4. Save the file.
5. Stop and restart IBM Systems Director Server.
6. Using the tpctool command line, type the following command:
setdscfg -user id -pwd pw -url hostname:9550 -property SnmpTrapPort port
where hostname is the fully qualified host name of the system where the IBM
Tivoli Storage Productivity Center server is installed, id is a valid user name on
that system, pw is the password for that user, and port is the same port number
to which you configured IBM Systems Director Server to forward traps. It is
recommended that you use port 22162.
7. Stop and restart the IBM Tivoli Storage Productivity Center server.
Installing and configuring IBM DS Storage Manager for DS4000

To use the IBM System Storage DS4000 devices, you must obtain the latest version
of IBM DS Storage Manager for DS4000. This application can also be used for IBM
DS3000 and DS5000 devices.
Note: IBM DS Storage Manager is a software package that must be installed on a

compute node, and not on the IBM Flex System Manager management node.
To install and configure the IBM DS Storage Manager for DS4000, complete the
following steps:
1. Go to the DS4000 Storage Manager product Web site and download the IBM
DS Storage Manager for DS4000: Software and device drivers.
2. Configure IBM DS Storage Manager for DS4000 according to the instructions
found on the Web site, and any Readme or similar files that you find.

Related reference:
Fix Central for DS4800
Installing and configuring ServeRAID Manager

For some ServeRAID controllers, you must install ServeRAID Manager V9.2 or
higher. Follow these instructions to install and configure this software. IBM
Systems Director 6.3 supports only V9.2 or higher of ServeRAID Manager.
You must have an IBM ServeRAID Application CD V9.2 - Servers and

IntelliStation®. You might have received one with certain IBM products. If not, you
can download the most current version of the IBM ServeRAID Application CD -
System x and BladeCenter from the Software Matrix website at
http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008
&lndocid=MIGR-61707. Use this CD to install all necessary ServeRAID software.
When you view the contents of this CD, the following two features are needed:
v ServeRAID Manager Console
v ServeRAID Manager Agent
Other features on this CD are not needed by IBM Systems Director 6.3.
To install and configure ServeRAID Manager, complete the following steps:

1. Verify that you need the ServeRAID Manager. Only these ServeRAID
controllers need the ServeRAID Manager. If your ServeRAID controller is not
on this list, do not perform any remaining steps in this task. You do not need
to install or configure anything else.
v IBM ServeRAID-8i Serial Attached SCSI (SAS) controller
v IBM ServeRAID-8k and 8k-l
v IBM ServeRAID-8s
v IBM ServeRAID-7t SATA controller
v IBM ServeRAID-7k Ultra320 SCSI controller
v IBM ServeRAID-7e/8e (Adaptec HostRAID) controllers
v IBM ServeRAID-6i/6i+ Ultra320 SCSI controller
v IBM ServeRAID-6M Ultra320 SCSI controller
v IBM ServeRAID-4H/4M/4L/4Mx/4Lx Ultra160 SCSI controllers
2. Install IBM Systems Director 6.3 Platform or Common Agent on the system that
hosts the RAID adapter, if you did not already install one of the agents.
3. Navigate to the folder of ServeRAID Manager 9.2 or higher Application CD,
and install ServeRAID Manager Agent. Now on the system that hosts the RAID
adapter, the following features are installed:
a. Director Agent (shown as 'IBM Director Agent') and 'IBM Director Platform
Agent'.
b. 'ServeRAID Manager', the ServeRAID Manager Agent.
4. On the system that is running the web browser (IBM Systems Director Web
interface), navigate to the folder of ServeRAID Manager 9.2 or higher
Application CD, and install ServeRAID Manager Console. You need only the
Console, so do not install other components. The system needs to have IBM
JRE version 1.5 or later installed already.
5. Open a web browser connection to IBM Systems Director Server, discover the
system that hosts the RAID adapter, request access, and collect inventory. You

can now launch ServeRAID Manager as an External Storage Application or
from the Actions menu of a server of the system that hosts the RAID adapter.
Note: When you select and launch a discovered controller instance, the
controller instance is shown inside the launched ServeRAID application.
6. When you launch the ServeRAID Manager Console for the first time, you must
add managed system manually.
Launching an external storage management application

Use an external storage management application to configure, control, and
maintain certain auxiliary storage devices and their connectivity to your network.
To launch an external storage management application for a specific resource,

1. Select a storage resource from the Resource Navigator.
2. Depending on the type of device, choose the correct external storage
application:
v Click Actions > Launch IBM Storwize V7000 Element Manager for IBM
Storwize V7000 devices
v Click Actions > Launch IBM DS4000 Storage Manager for IBM DS3000,
DS4000, and DS5000 devices.
v Click Actions > Launch IBM N Series Data ONTAP.
v Click Actions > Launch ServeRAID Manager for Internal RAID controllers.
The external storage application starts, but you can perform only those tasks
that are related to the chosen resource.
Note: If you are trying to launch these tasks from the Mozilla Firefox web
browser and the task does not start, you might need to enable pop-up
windows.
a. Look for a message toward the top of the window that says “Firefox
prevented this site from opening a pop-up window.”
b. Click Options at the end of the message line.
c. Select Allow pop-ups for ip_address.
d. Launch the task again.
3. Log in to the application and complete all necessary tasks.
4. When you are finished with the application, close the application window.
As an alternative, you can launch the external storage applications without

selecting a target resource. From the IBM Systems Director Web interface, select
System Configuration > External Storage Applications. The External Storage
Applications page is displayed. Select the application from this page. This
alternative method is the only way to launch the IBM Tivoli Storage Productivity
Center.
Related tasks:
Installing and configuring external storage applications
Navigating tables
Requirements for IBM Tivoli Storage Productivity Center

These requirements must be met when using IBM Tivoli Storage Productivity
Center with IBM Systems Director.

IBM Tivoli Storage Productivity Center must be:
1. Release Limited Edition Version 3.1 or later
2. Launched from one of these operating systems: Windows, AIX, or Linux
Automatic installation is not supported.
For launching IBM Tivoli Storage Productivity Center in an untargeted fashion (for
example, from the External Storage Application page), IBM Tivoli Storage
Productivity Center must be installed on the same system that the user is running
the client browser session (the browser they are using to connect to IBM Systems
Director).
For more information, see the IBM Tivoli Storage Productivity Center Web site:
www-03.ibm.com/systems/storage/software/center/.
Requirements for IBM DS Storage Manager

These requirements must be met when using IBM DS Storage Manager with IBM
Systems Director.
IBM DS Storage Manager must meet these requirements:

v It must be launched from one of these operating systems: Windows, AIX, or
Linux.
v Only version 10.60.g5.16 or earlier is supported. To determine the recommended
version for each disk system, see the documentation for DS Storage Manager.
Note: If you already downloaded a later version of IBM DS Storage Manager

and cannot start it, see the troubleshooting topic "Cannot start an IBM DS
Storage Manager with version later than 10.6.x.x" in the IBM Systems Director
information center..
IBM DS Storage Manager must be installed on the same system that is running the
client browser session (the browser used to connect to IBM Systems Director).
Automatic installation is not supported.
IBM DS Storage Manager is used for DS5000, DS4000, and DS3000 disk systems.
If you try to invoke IBM DS Storage Manager and it is not found, you will see a
page with installation instructions.
For IBM DS Storage Manager, only version 10.60.g5.16 or earlier is supported. If

you have trouble launching a later version, refer to the appropriate troubleshooting
topic.
For more information, see the IBM Support Portal. Use the Quick find feature to
specify your disk system, then click the Documentation tab.
Requirements for ServeRAID Manager

These requirements must be met when using ServeRAID Manager with IBM
Systems Director.
v ServeRAID Manager can be launched only on a system running Windows or
Linux.

v You also can run the IBM Systems Director ServeRAID Manager plug-in on the
same system where you have installed the ServeRAID Manager application.
v If you try to invoke ServeRAID Manager and it is not found, you see a page of
installation instructions.
v Automatic installation is not supported.
v For External Application Launch to work, the IBM Systems Director Web
interface must have IBM JRE V1.5 or a higher level.
v ServeRAID Manager can be launched from an external storage applications link
or from a discovered ServeRAID Controller in IBM Systems Director.
v When ServeRAID Manager is launched from a discovered ServeRAID Controller,
the controller is automatically added to the launched ServeRAID Manager.
v If the client machine where the browser is launched to Director is authenticated
using a certificate, when ServeRAID Manager opens, a credential authentication
dialog opens.
IBM Systems Director Storage Control 4.2.4

With the Storage Control plug-in, you can manage an expanded set of storage
subsystems and Fibre Channel switches.
You can use Storage Control to discover, collect inventory, and monitor the health
of your storage devices. These subsystems include, but are not limited to, the IBM
DS3000, DS4000, and DS5000 families, the IBM DS8000 family (DS8100, DS8300,
DS8700, DS8800), the SAN Volume Controller, the IBM Storwize V7000, Storwize
V3700, Storwize V3500, IBM Flex System™ V7000 Storage Node, IBM XIV, QLogic 8
GB Fibre Channel switch, the Brocade Fibre Channel switches, and the McDATA
Sphereon and Intrepid switches. For the list of supported devices, see “Supported
storage devices.”
For more information about Storage Control, see IBM Systems Director Storage
Control 4.2.4 website.
For more information about licensing, and operating systems and software
requirements, see the following topics:
IBM Systems Director Storage Control 4.2.4 license information

IBM Systems Director Storage Control 4.2.4 comes with an evaluation license that
lasts for 90 days. At any time, you can update to a full product license.
Evaluation license
The evaluation license for Storage Control includes a 90-day trial period. You can
discover, monitor the health status of, and add and remove devices, starting on the
day that you install Storage Control. At the end of the trial period, the monitoring
functions remain operational. You can view the health and configuration of the
device and monitor its capacity and utilization, and remove the device from the
Systems Director inventory. If the permanent key is not acquired and installed after
the trial period, you cannot use Storage Control to discover and add new devices
to Storage Control.
Permanent license
To install the permanent product license for Storage Control, you import the
license key. To import the license key, navigate to the Plug-ins tab of the Home
page, and click Import License Key.

Note: The location of the license pack might vary, depending on how you installed
Storage Control.
v The version of Storage Control that is shipped on a product CD includes a
license pack. To install the license key, refer to the directions included for the
product you purchased.
v If you downloaded Storage Control, you can order a product license that
includes the license key. In this case, after the key is emailed to you, you can use
the Import License Key task to import it.
Operating system and software requirements for IBM Systems

Director Storage Control 4.2.4
Before you install Storage Control, ensure that your system meets these software
requirements.
Supported operating systems
The Storage Control plug-in supports most of the Red Hat Enterprise Linux,
Microsoft Windows, and AIX operating systems that Systems Director also
supports, with these exceptions: Red Hat Enterprise Linux on Power Systems, Red
Hat Enterprise Linux on System z systems, and SUSE Linux Enterprise.
The specified versions of the following operating systems are supported:

v AIX
AIX 5.3, POWER4, POWER5, and POWER6
AIX 6.1, POWER4, POWER5, POWER6, and POWER7®
AIX 7.1, POWER5, POWER6, and POWER7
v Linux RHEL Base and Advanced Platform 5 (x86-64)
v Linux RHEL Base and Advanced Platform 6 (x86-64)
v Windows
Windows 2003 Standard Edition and Windows 2003 Enterprise Edition (x86
and x86-64)
Windows 2008 Standard Edition and Windows 2008 Enterprise Edition (x86
and x86-64)
Windows 2008 R2 Standard Edition and Windows 2008 R2 Enterprise Edition
(x86-64)
For more information about the supported operating systems, see the following
web page: 4.2.x - Platform Support: Agents, Servers, and GUI.
Software requirements
IBM Systems Director 6.2.1 or higher is required in order to use Storage Control.
Important: If you are not using IBM DB2 managed by Systems Director, then you
must use one of these versions of IBM DB2 as the local database application for
Systems Director to use Storage Control:
v IBM DB2 Enterprise Edition v. 9.7
v IBM DB2 Enterprise Edition v. 9.7 with fix pack 4
v IBM DB2 Enterprise Edition v. 9.7 with fix pack 6 (or above)
That is, the correct version of DB2 must be installed on the same system as
Systems Director. Storage Control is not supported on any other databases.

Storage Control supports the same SMI-S providers that are supported by IBM
Tivoli Storage Productivity Center. For details, see the Help to Find the Supported
Products and Platforms Interoperability Matrix Links website.
Viewing storage devices

You can view storage devices from a number of different perspectives, such as
storage groups, the devices attached to a given system, a list of storage volumes, a
list of discovered storage devices, System status and health of storage systems, and
a topology view for a particular device.
Storage Management Summary

Your storage devices can be viewed and managed in one central location. The
Storage Management Summary page provides an introduction to your storage
systems. The Storage Management Summary is invoked from the Plug-ins tab of
the Home page.
The Storage Management Summary page gives high-level details about your
storage systems, and links to the tasks that provide more detail and administer the
storage devices. You can also install a trial version of IBM Systems Director Storage
Control 4.2.4 by following a link on this page.
Discovery and inventory collection must be run before you can display storage
systems. The Storage Management Summary page is divided into these areas:
Try IBM Systems Director Storage Control 4.2.4
For more information about Storage Control, see the IBM Systems Director
Storage Control 4.2.4 information center.
Capacity Summary
A pie chart represents your disk capacity in each of these categories.
Total configured capacity (to volumes)
Number of GB of the volumes that are assigned.
Total available capacity (for volumes)
Number of GB of disk pool size that is unassigned to volumes, but
are available for creating future new volumes.
This the space available for creating future new volumes. Total
available capacity represents the remaining total storage array or
storage pool space that could be used to create volumes. Initially,
when creating a storage array or pool, the configured capacity is
zero and the available capacity is the pool size. Creating additional
volumes decreases the amount of available capacity. Available
capacity is a measurement of the current quantity of usable
storage.
The capacity measurement is a snapshot created when inventory is
collected on the storage arrays. Inventory collection can be
configured to run on a schedule to periodically update the capacity
information if storage volumes and pools are created after the
initial inventory collection.
For Local Storage, capacity information collected for storage devices
attached to systems that are running IBM Director 5.20 is limited to the
Total raw capacity. The Total configured capacity and Total available
capacity are not included in the Capacity Summary for these storage
devices.

Storage tasks
Server to Storage Mapping View
Display a table that shows what storage resources are associated
with your virtual servers. After selecting this task, you will choose
the servers to view.
Storage to Server Mapping view
Display a table that shows the virtual server disks and which
storage pools contain them. After selecting this task, you will
choose the storage resources to view.
View and Manage Storage Volumes
Work with your currently-defined storage volumes to make
changes, add or delete them. Details about status and capacity are
also available.
This task is managing the assignment of network storage to
individual systems, from the context of a specific host system. You
can create a new volume from network storage to be assigned to a
selected host system, or delete a volume that is currently assigned
to a selected host system. The create volumes function simplifies
the allocation process by determining the best fit storage system,
and creating any necessary RAID arrays automatically.
View and Apply Storage Templates
Work with storage templates, which are predefined images for
certain storage devices. Storage templates are used to ensure
uniformity among common storage elements, as well as save time
and effort on repetitive tasks.
Storage templates can be used:
1. To clone the storage configuration of a system - save a storage
volume template from an existing server, and then later
applying a saved template to another system. This can be used
for duplication (clustering, or virtual server hosts) or for saving
the storage configuration for backup or disaster recovery
purposes.
2. As a starting point for creating additional volumes - start with
a base template and make changes as needed.
Capacity Details
For each type of storage, this table indicates the available capacity, usable
capacity, total capacity, number of systems, and number of disk drives. The
entries in this list correspond to storage groups having the same name. If
you select an entry, a table of storage subsystems that are members of the
selected group is displayed.
Local Storage
Storage that is local to only one system, and therefore dedicated to
only that system.
For the Local Storage row, capacity information collected for
storage devices attached to systems that are running IBM Director
5.20 is limited to the Total raw capacity. The Total usable capacity
and Total available capacity is not displayed for these storage
devices.

BladeCenter Storage
Storage accessible to all of your BladeCenter systems. Specifically,
this is BladeCenter S storage being managed by an IBM SAS
Controller Module.
From IBM Systems Director, BladeCenter Integrated storage can be
access through several paths: View and Manage Storage Volumes
from the Storage Management Summary page, the Configuration
tab of the Properties page of a host system, or by configuration
templates.
Network storage
Storage accessed with switches, adapters, and protocols such as
Fibre Channel, SAS, and iSCSI. Network storage (and BladeCenter
Integrated storage) is managed by IBM Systems Director (for
supported storage devices) and by native management applications
provided with the network storage device.
From IBM Systems Director, network storage management can be
access through several paths: View and Manage Storage Volumes
from the Storage Management Summary page, the Configuration
tab of the Properties page of a host system, or by configuration
templates.
Total Provides totals of all the columns.
Related tasks:
Viewing storage volumes
Viewing storage configuration templates
Navigating tables
Viewing storage systems using storage groups

Display a hierarchical view of the volumes mapped to each system, and from
which storage subsystem each volume is allocated.
Predefined storage groups are in these categories: IBM BladeCenter, Network,

Local storage, SMI-S providers, Storage Subsystems and Volumes, Systems and
Volumes. Ensure that you have run Discovery for all systems that have storage
attached, that these systems are not locked, and that you have run inventory
collection for these systems.
To view your storage systems using storage groups.

1. Click Resource Explorer. The Resource Explorer page is displayed.
2. Select Groups by System Type. A table of groups is displayed.
3. Select Storage Systems. A table listing the different categories of storage
4. Select Systems and Volumes.
v To view a table of systems and their associated volumes, select Systems and
Volumes. Note that the associated volumes for each system are displayed
directly below the row for the system.
v To view a table of storage subsystems and their volumes, select Storage
Subsystems and Volumes.
5. Choose and display other storage groups, depending on which ones are of
interest.

Related concepts:
SMI-S providers
Storage groups
Related tasks:
Navigating tables
Related reference:
lsnssys
Displaying attached storage for a given system

Display the current configuration for a given system, and view its existing storage
volumes and other storage devices. You can select to View or Edit this information.
The Storage Management Summary page contains some details about storage
devices. First, review this page to see if the information that you are looking for is
in either the Capacity Summary or Capacity Details sections.
To display the current configuration for a given system, complete the following
steps:
2. Select All Systems. A list of discovered systems is displayed.
3. Select a system from the list.
4. Click Actions > System Configuration > Current Configuration. A table of all
the configuration settings for this system is displayed.
5. Select Storage Provisioning.
6. Click Actions > Edit.. A table of existing storage volumes for the selected
system is displayed.
7. Optional: To create a new storage volume, click Actions > Create Volume. The
Create Volumes wizard is displayed.
8. Optional: To delete a storage volume, select the volume and click Actions >
Delete Volume. You are asked to confirm the deletion.
Notes:
1. When Storage Providers are discovered, the storage is automatically available.
2. On some storage devices, such as Advanced RAID Controller , IBM SAS RAID
Controller Module, or Integrated RAID Controller, the storage is available to be
viewed from the System Configuration menu.
Related concepts:
Related tasks:
Creating a configuration template for a storage volume
Provisioning storage from an existing storage subsystem
Managing storage volumes in real time
Navigating tables
Viewing storage volumes

This displays of a table of all storage volumes accessible to IBM Systems Director.
Note that a storage volume is similar to a logical volume.

To view detailed information about storage volumes, complete the following steps:
1. From the Storage Management Summary page, locate the Capacity Summary
area, and the Storage Tasks pane on the right.
2. Click View and Manage Storage Volumes. The Current Configuration page is
displayed.
3. Select a system. Storage details for the system are displayed.
4. Select Storage Provisioning Configuration. A list of storage volumes associated
with the selected system is displayed.
5. If you have not yet run inventory discovery, this table might be empty. Return
to the Storage Management Summary page and click Storage system not being
discovered? Learn more so that you can plan and run the necessary discovery
task.
Related concepts:
Related tasks:
Navigating tables
Viewing the health and status of storage devices

Use the System Status and Health summary of IBM Systems Director to view the
health and status of storage devices.
The following areas in the System Status and Health summary concern storage
devices and characteristics that are unique to storage systems:
Active status
The status for storage devices must be cleared manually if the cause of the
status change is resolved outside of IBM Systems Director. In this case,
either ignore, deactivate, or delete the status set to reset the status of a
storage system.
Event log
Storage events are recorded in this log.
Health summary
You can add storage systems for health summary, the same way that you
add other resources to be monitored.
To view the system status and health for storage devices, complete the following
steps:
1. In the IBM Systems Director navigation area, click Home. The Home page is
displayed.
2. On the Home page, click the Plug-ins tab. A list of available summary pages
is displayed.
3. On the Plug-ins tab, scroll to the Status Manager section heading and click it.
The Status Manager Summary page is displayed.
4. In the Status tasks area, click Health summary. The Health Summary page is
displayed.
5. Examine the storage systems, or if no storage system is present, use the
Health Summary Favorites Group to add them.
6. Click Cancel. The Status Manager Summary page is displayed.
7. In the Status tasks area, click View active and ignored status. The Active
status page is displayed.

8. Search this page for status information for your storage systems. If you do not
find a system that you want to be monitored, add it.
9. Click Cancel. The Status Manager Summary page is displayed.
10. In the Management Section, view the Common Tasks area.
11. Click Event Log. A list of event logs is displayed.
12. Choose an event log and view its contents, searching for storage-related
entries.
13. Click Cancel until you exit the status manager.
Related tasks:
Using the health summary favorites group to add and remove systems in the
health summary
Navigating tables
Storage topology perspective

The Storage topology perspective displays a topology view tailored to the
storage-related resources for a system or device.
Make sure that discovery has been run, inventory has been collected, and the
system that the storage devices are attached to is unlocked before trying to view
their topology map.
By default, a topology perspective contains all resources related to the device. The
Storage perspective limits the resource types to storage-related resources.
The topology view can be invoked wherever there is a table listing a particular
storage device. An example is to select a device, and then click Actions > Topology
Perspectives. Then, choose one of these storage-related views:
v Storage - Provides a topology map that shows logical relationships between
resources that are related to the selected resource, including hosts, host volumes,
storage systems, storage volumes, storage pools, and disk drives.
v Storage Area Network - Provides a topology map that shows physical
connections between resources that are related to the selected resource, including
hosts, switches, ports, physical connectors, and storage systems.
The topology view shows the devices and their connectivity. Arrows connect the
devices. The name of each device is listed whenever possible. Connectors are
represented by a connector icon.
The Depth option can be used to see a deeper view of the device connections, by
clicking Actions > Depth and then selecting a number.
You can display the graph in one of two layouts. Click Actions > Layout to choose
one of these layouts:
Radial Presents the display in a radial layout, having the display fan out from left
to right and top to bottom, as needed.
Tree Presents the display in a tree layout. The selected resource is on the first
level. The second level is the devices immediately attached to the selected
resource. The third level is attachments to the second level devices and so
forth, to the depth that has been selected with the Depth option.

The Overview area shows the graph without the details, and is used to zoom in to
see specific areas.
Related concepts:
Managing storage in real-time

You can manage storage systems in real-time, without the use of configuration
templates.
Related concepts:
Storage management in real time and using configuration templates
Managing IBM BladeCenter and System x storage devices

You can perform real time management of these storage systems, which are
attached to IBM BladeCenter or System x systems.
IBM Systems Director supports these storage systems that are attached to or
integrated with IBM BladeCenter and System x systems.
v Integrated RAID Controllers
v ServeRAID MR Controllers
v BladeCenter SAS Connectivity Modules
v IBM BladeCenter S SAS RAID Controller Modules
The systems to which these devices are attached must be discovered and have
access granted. Inventory must be collected so that IBM Systems Director will
know about the storage devices. If an SMI-S provider is involved, it must also be
discovered, unlocked, and configured.
Related concepts:
SMI-S providers
Related tasks:
Module
Navigating tables
Managing Integrated RAID Controllers and their attached storage

devices
IBM Systems Director can be used to select an Integrated RAID Controller (IRC)
attached to an IBM BladeCenter or System x system, and perform storage
management tasks for the attached devices.
The systems to which these storage devices are attached must be discovered and
have access granted. Inventory must be collected so that IBM Systems Director
knows about the storage devices. If an SMI-S provider is involved, it must also be
To manage storage devices attached to an IRC, complete the following steps:

1. From any area that displays the system and its attached storage devices, such
as Resource Explorer, select the system or the operating system that hosts the
IRC.

2. Click Actions > System Configuration > Storage. The Storage page is
displayed.
3. View the contents of this page and perform any necessary tasks associated with
storage volumes, such as creating and deleting volumes.
Note: The Volumes and Storage Pools pages do not support all the Action
menu choices. The Volume Page supports only Create Volumes and Delete
Volumes. The Storage Pools page supports only Create Storage Pool and Delete
Storage Pool. All other Action menu choices for those pages are not supported.
Managing ServeRAID MR Controllers and their attached storage

devices
IBM Systems Director can be used to select a ServeRAID MR Controller attached to
an IBM BladeCenter or System x system, and perform storage management tasks
for the attached devices.
Note: Do not use these instructions to manage an Integrated RAID Controller

(IRC) device. For more information about managing IRC devices, see "Managing
Integrated RAID Controllers and their attached storage devices" in Related Links at
the bottom of this page.
The systems to which these storage devices are attached must be discovered and
have access granted. Inventory must be collected so that IBM Systems Director will
know about the storage devices. If an SMI-S provider is involved, it must also be
To manage storage devices attached to a ServeRAID MR Controller, complete the

following steps:
1. From any area that displays the system and its attached storage devices, such
as Resource Explorer, select the system or the operating system that hosts the
ServeRAID MR Controller.
2. Click Actions > System Configuration > Storage. The Storage page is
displayed.
storage volumes and pools. For example, you can create, delete, and modify
volumes or pools, and assign and unassign global and dedicated spares and
local drives. You can also use the Drives tab to perform tasks on drives.
4. Click Actions > Task Management > Long Running Tasks. The Long Running
Tasks page is displayed.
5. Use the page to view long running tasks such as rebuilding pools and
initializing drives.
Related tasks:
Managing Integrated RAID Controllers and their attached storage devices
Managing BladeCenter SAS Connectivity Modules and their

attached storage devices
IBM Systems Director can be used to select a Serial Attached SCSI (SAS)
Connectivity Module attached to an IBM BladeCenter system, and perform storage
The IBM BladeCenter system to which these storage devices are attached must be
discovered and have access granted. Inventory must be collected so that IBM
Systems Director will know about the storage devices. The IBM BladeCenter SAS
Connectivity Module switch must be discovered and unlocked.

To manage storage devices attached to a SAS Connectivity Module, complete the
following steps:
1. From any area that the IBM BladeCenter system you are interested in is
displayed, select the chassis or SAS Connectivity module.
2. Click Actions > System Configuration > SAS Ports. This page shows all of the
internal (blade slot) and external ports on the switch, organized by type.
SAS ports, such as enable, disable, or view properties.
4. Click Actions > System Configuration > Set Date and Time. A page used to
set the date and time on the SAS switch is displayed.
5. View the contents of this page and set the date and time if necessary.
6. Click Actions > System Status and Health.
v Click Collect Support Data to collect support bundles for problem analysis.
v Click Device Log to display logging information for operations performed on
this specific storage device.
v Click Error Counters to view error counts and status messages from each
device on the switch.
7. View the displayed pages and perform all necessary tasks.
Related tasks:
Configuring IBM BladeCenter SAS zone connectivity in real time
Managing IBM BladeCenter S SAS RAID Controller Modules and

their attached storage devices
IBM Systems Director can be used to select a Serial Attached SCSI (SAS) RAID
Controller Module attached to an IBM BladeCenter system, and perform storage
Before running this task, perform these discovery tasks, in the order specified here:
1. The SMI-S provider for the IBM BladeCenter S SAS RAID Controller Module
must be discovered and unlocked. This SMI-S provider is installed by default
on the IBM Systems Director server. It can also be installed on a remote host by
using remote agent install.
See this topic for instructions to install by remote agent: Installing the SMI-S
provider for the IBM BladeCenter S SAS RAID Controller Module on additional
systems.
If the provider is on the same subnet as the IBM Systems Director server,
follow the instructions in this topic: System Discovery.
If they are on separate subnets, follow these instructions to create a “system
discovery” profile: Creating a discovery profile.
v On the Protocol Selection page, select Storage Management Initiative
Specification (SMI-S) Discovery.
v On the SMI-S Configuration page, specify the appropriate port, depending
on your operating system: 5988 for Windows or 15988 for Linux.
After creating the SMI-S discovery profile, click Run. After the discovery
completes successfully, you will see a host instance. After the provider is
configured to manage an IBM BladeCenter SAS RAID Controller, you will also
see a storage array instance.
All information about the storage system is obtained for Systems Director
through the SMI-S provider. After discovery, configure the SMI-S provider.
2. Discover and unlock the IBM BladeCenter chassis. The default userid and
password for the chassis are USERID and PASSW0RD (with a zero).

3. The switches are automatically discovered after the chassis is unlocked.
4. Unlock the attached SAS switches. The default userid and password for the
switches are USERID1 and PASSW0RD (with a zero).
5. Add the Storage System to the SMI-S provider configuration.
a. In the left navigation, click Resource Explorer.
b. In the Groups window table, choose Groups by System Type > Storage
Systems > SMI-S Providers.
c. Select the name of the provider, then select Actions > System Configuration
> SMI-S Provider Configuration > IBM SAS RAID Controller Module >
Add Storage System.
6. Run Inventory Collection against IBM BladeCenter SAS RAID Controller and
the Storage System. See this topic for instructions: Collecting inventory.
To manage storage devices attached to a SAS RAID Controller Module, complete

1. From any area that the IBM BladeCenter system and its attached storage
devices are displayed, such as Resource Explorer, select the IBM BladeCenter
chassis that contains the SAS RAID Controller Module, or an attached storage
subsystem.
2. Click Actions > System Configuration > Storage Resources. Note that this
page is displayed only if a IBM BladeCenter chassis has been selected. This
page is not used for attached storage subsystems. A page of storage resources,
with tabs for all major components, is displayed.
3. View the contents of this page and perform any necessary storage tasks.
set the date and time on the selected resource is displayed.
v Click Device Log to display logging information.
v Click Physical Resources to display attached physical resources.
8. Click Actions > Task Management > Long Running Tasks. A page used to
display tasks that have been running for a long time is displayed.
9. From any area that the IBM BladeCenter system and its attached storage
devices are displayed, such as Resource Explorer, select the SAS switch that
you are interested in.
10. Click Actions > System Configuration > SAS Ports. This page shows all of
the internal (blade slot) and external ports on the switch, organized by type.
11. View the contents of this page and perform any necessary tasks associated
with SAS ports, such as enable, disable, or view properties.
set the date and time on the SAS switch is displayed.
v Click Collect Support Data to collect support bundles for problem analysis.
v Click Device Log to display logging information.
v Click Error Counters to view error counts and status messages.
v Click Physical Resources to display attached physical resources.

Related tasks:
Configuring IBM BladeCenter SAS zone connectivity in real time
Module
Adding IBM BladeCenter Integrated Storage devices to a

server
To add a new IBM BladeCenter storage system, use the SMI-S provider that is
appropriate for the storage system. You can select from a list of storage systems
that have already been discovered, or enter all details about one that has not been
discovered.
Adding an IBM BladeCenter S SAS RAID Controller Module

storage system that has already been discovered
To add a storage system that has been discovered by IBM Systems Director, you
choose from a list of these storage systems.
To add an IBM BladeCenter S SAS RAID Controller Module that has already been
discovered, complete the following steps:
1. Discover and unlock a the system that you want to add the storage system to.
2. From any area that this system is displayed, such as the Resource Navigator,
click Actions > System Configuration > SMI-S provider Configuration The
Managed Storage Systems page is displayed.
3. Click Add Storage Systems. The Add Storage System page is displayed.
4. In the Storage System Selection area, click Select a storage system that has
already been discovered.
5. Click Browse to see a list of discovered storage systems. A context chooser with
a list of storage systems is displayed.
6. Select a storage system from the Available list.
7. Click OK when you are finished. The Add Storage System page is displayed
again.
8. In the Storage System Login area, type a user ID and password for the system
that is to access the storage that you just selected.
9. Click OK.
Adding an IBM BladeCenter S SAS RAID Controller Module that

has not been discovered
To add an IBM BladeCenter S SAS RAID Controller Module that has not been
discovered by IBM Systems Director, you must supply all necessary details.
When using an IBM BladeCenter S SAS RAID Controller Module, there are two
cards, a SAS card and a RAID card. Only the RAID card IP addresses are used in
this topic.

To add an IBM BladeCenter S SAS RAID Controller Module that has not been
discovered, complete the following steps:
1. Discover and unlock a the system that you want to add the storage system to.
2. From any area that this system is displayed, such as the Resource Navigator,
click Actions > System Configuration > SMI-S Provider Configuration The
Managed Storage Systems page is displayed.
3. Click Add Storage Systems. The Add Storage System page is displayed.
4. In the Storage System Selection area, click Enter storage system information
manually.
5. Type the Primary controller IP address.
6. Type the Secondary controller IP address.
7. In the Storage System Login area, type a user ID and password for the system.
8. Click OK.
Provisioning storage from an existing storage subsystem

The task can be performed only for an IBM BladeCenter SAS RAID Controller
Module. This task does not apply to other systems or devices. This procedure
entails: creating a storage pool, defining one or more volumes, creating a host
system, mapping volumes to the host system.
Locate the switch interface and make sure that the system is allowed (zoned) to
access the storage system on the SAN.
To provision storage from an existing storage subsystem, complete the following

steps:
2. Select Groups by System Type. A table of groups is displayed.
3. Select Storage Systems. A table listing the different categories of storage
4. Select the appropriate storage group (an example is BladeCenter storage). A list
of the members of this group is displayed.
5. Select the storage system.
6. Click Actions > System Configuration > Storage Resources. The Storage page
includes these tabs:
v Volumes
v Storage Pools
v Hosts
v Disk Drives
v Configurations
7. Click the Volumes tab.
8. Click Actions > Create Volumes. The Create Volumes wizard is displayed.
9. Go through all the wizard pages, entering the correct options. (Choose Method,
Create Storage Pool, Defined Volumes, Map Volumes, and Summary).

Related tasks:
Navigating tables
Managing storage volumes in real time

You can create and delete storage volumes in real time. These changes are applied
immediately.
Creating storage volumes

Use the Create Storage Volume wizard to create storage area network (SAN)
storage volumes for your managed servers that have Fibre Channel adapters.
The Create Storage Volume wizard guides you through the steps that are required
to create SAN storage volumes, including selecting a storage pool from which the
storage volumes are allocated and attached to the selected servers. The wizard also
provides the capability to create new zones and zone sets, if the zones or zone sets
were not configured previously.
Note: To create new zones or zone sets, the user must belong to a role that has the
fabric/zoning permission. (The option to create new zones is presented only when
the selected storage pool or additional server has a value of Available in the Zone
access column.) Otherwise, before you use the wizard, configure zoning so that the
associated storage pools are available for selection. (These storage pools have a
value of Zoned in the Zone access column.) Use the native switch control utility
(not the IBM Systems Director Web interface) to configure hard zoning on any
switch that is a member of the fabric.
Prerequisites for using the wizard include discovering and collecting inventory for
the server, switches, and storage devices. More information about the prerequisites
is available in the Create Storage Volume wizard and in the related links.
Note: If you prefer to use a command-line interface or if you must use scripting,
use the smcli commands mkstvol, lsstpool, and lsstvol. To detach and remove a
SAN volume, use the rmstvol command, a function that is not available by using
To start the Create Storage Volume wizard, right-click the server for which you
want to allocate SAN storage volumes, the select System Configuration > Create
Storage Volumes.

Related tasks:
Using Storage Control to discover storage

Related reference:
Supported storage devices
lsstpool command
lsstvol command
mkstvol command
rmstvol command
Creating a storage volume in real-time

For a specific active server, you can create storage volumes using the Resource
Navigator in real-time.
Make sure that the server and its storage devices must have been discovered and
unlocked.
You can use these definitions for IBM BladeCenter installations that include
might be made by way of the management module, but actually might affect other
components in the IBM BladeCenter environment, such as a blade server. All
To create a storage volume for a server, complete the following steps:

1. From the Resource Navigator, click System Configuration > Current
Configuration. A table with the current configuration is displayed.
2. Click Storage Provisioning Configuration. The Storage Volumes page is
displayed. If this server already has some storage volumes, they are displayed.
3. Click Actions > Create Volumes. The Create Volumes wizard is displayed.
4. Optional: If the Welcome page is displayed, click Do not show this Welcome
page next time if you do not want to see the Welcome page again.
5. Choose a method for creating the new storage volume:
v Click Create volume from scratch to create a new storage volume by
manually specifying all necessary parameters.
v Click Create volume from a template and then choose a configuration
template to create a storage volume that will have the same definitions as
those that are stored in the configuration template. You will be able to
change some but not all of these definitions.
6. Follow the instructions for the task that you have selected in the previous step.
7. After the new volumes have been created, click Deploy in the Storage Volume
page. A job scheduler is displayed.
8. Enter job information, then click OK.
9. Wait for the process to complete and review all messages.

Related tasks:
Navigating tables
Related reference:
lsnsvol
Creating a storage volume from scratch:
When creating a storage volume for a IBM BladeCenter server from scratch, you
must enter all necessary information about the storage volume.
To create a storage volume for an IBM BladeCenter blade server from scratch,
1. If you have not already done so, click Create volume from scratch from the
Choose Methods page. The Create from Scratch page is displayed.
2. Optional: Type a Volume name prefix. The volume name will be made by
appending a unique number to this prefix. This field must be ten or fewer
characters consisting only of letters, numbers, and the underscore character. If
this field is not specified, the first ten characters of the host name are used.
3. Click Identify this volume as the boot volume if you want this volume to be
the one that will be examined for the bootstrap code when a restart is
performed. You can choose this option only if the server currently has no
designated boot volume.
4. Specify the capacity of the storage volume in Gigabytes.
5. Specify the Volume RAID level:
v RAID 0
v RAID 1
v RAID 5
v RAID 0+1
6. Choose the Host operating system:
v AIX
v Linux
v Windows
7. Select a Storage type:
v Any
v Network - Serial-Attached SCSI (SAS)
v Network - Fibre Channel (FC)
v Network - Internet SCSI (iSCSI)
v IBM BladeCenter SAS
8. Select a Storage system:
v Click Let system choose to have IBM Systems Director choose the storage
system
v Click I will choose myself to choose from a table of storage systems that is
displayed. You can choose one or more entries from this table.
9. Click Next The Summary page is displayed.
10. Review the information on this page. If it is correct, click Finish. The Storage
Volume page is displayed, and the new volume is added into the volumes
table.

Related tasks:
Creating a storage volume from a configuration template
Navigating tables
Related reference:
mknsvol
Creating a storage volume from a configuration template:
When creating a storage volume for a BladeCenter blade server from a

configuration template, the definitions stored in the configuration template are
displayed, and you will be able to change some but not all of the attributes.
To create a storage volume for a BladeCenter blade server from a configuration

template, complete the following steps:
1. If you have not already done so, navigate to the Create Volumes page.
2. Click Create volume from a template and then choose a configuration
template. The Create from Template page is displayed. The Base Template
name field is the name of configuration template that you have chosen.
3. Optional: The host operating system can be changed by clicking on one of
these choices:
v AIX
v Linux
v Windows
4. Examine the Table of Volumes Definitions that have been retrieved from the
configuration template. You will be creating one storage volume with the
same definition as each entry in this table, unless you delete or alter the table
entries.
5. Decide what changes to make to these storage volume definitions:
v To remove one or more storage volumes, click Remove Volume.
v To change a storage volume, click Edit Volume. Repeat if you want to
change more than one.
v To add a storage volume, click Add Volume. Repeat if you want to add
more than one.
6. Optional: If you did not select to Add Volume or Edit Volume for one or
more storage volumes, proceed to Step 12.
7. Change or specify the Volume name prefix. The volume name will be made
by appending a unique number to this prefix. This field must be ten or fewer
characters consisting only of letters, numbers, and the underscore character. If
this field is not specified, the first ten characters of the host name are used.
8. Specify the capacity of the storage volume in Gigabytes.
9. Specify the Volume RAID level.
10. Select a Storage type.
11. Select a Storage system.
v Click Let system choose to have IBM Systems Director choose the storage
system
v Click I will choose myself to choose from a table of storage systems that is
displayed. You can choose one or more entries from this table.
12. Click Finish. The Storage Volume page is displayed, and the new volumes are
added into the volumes table.

Related tasks:
Creating a storage volume from scratch
Navigating tables
Related reference:
mknsvol
Deleting a storage volume in real time:
For a specific active server, you can delete a storage volume using the Resource
Navigator.
Make sure that the server and its storage devices have been discovered and
unlocked.
To delete a storage volume from a server, complete the following steps:

2. Select All Systems. A list of discovered systems is displayed.
3. Select an IBM BladeCenter blade server.
4. Click Actions > System Configuration > Current Configuration. A table of all
the configuration settings for this system is displayed.
5. Click Storage Provisioning Configuration. The Storage Volumes page is
displayed.
6. Select one or more storage volumes to be deleted.
7. Click Actions > Delete Volumes. A confirmation popup is displayed.
8. Examine your choices carefully, then click OK. The selected storage volumes
are deleted from the volumes table.
9. Click Deploy. A job scheduler is displayed.
10. Enter job information, then click OK.
11. Monitor the job to ensure that it completes and review any error messages.
Related tasks:
Navigating tables
Related reference:
rmnsvol
Configuring iSCSI components in real time

Configuring iSCSI components consists of configuring iSCSI initiators, iSCSI
targets, and their mappings. Both iSCSI V1 and iSCSI V2 are supported by IBM
Systems Director. At least one blade and one initiator must be configured. Make
sure that all the initiators are mapped to at least one target, except for initiators of
type ALL DHCP.
components in the IBM BladeCenter environment, such as blade servers. All
To configure Internet Small Computer System Interface (iSCSI) components in real

time, complete the following steps:

1. Click Resource Explorer > Groups > All Systems. A list of systems is
displayed.
2. Select a system and double-click its link. A list of attached devices is displayed.
3. Select a system that has attached iSCSI components.
4. Click Actions > System Configuration > Current Configuration. A list of the
current configuration for this system is displayed.
5. Select the entry whose Configuration Settings title is: iSCSI Configuration.
6. Click Edit.
7. Click Continue. The Blade Server iSCSI Configuration page is displayed.
8. Select each Step and enter all necessary information.
9. Click Deploy to save these changes to the iSCSI components.
Configuring iSCSI targets

An iSCSI target is responsible for responding to storage requests such as reads or
writes. Typically, the target is a storage controller containing disks that respond to
storage requests. Configuring iSCSI targets consists of providing a location and
means to access to the iSCSI target.
To configure iSCSI targets, complete the following steps:

1. If you have not already done so, click Define Targets on the Blade Server
iSCSI Configuration page. The Target page is displayed.
2. Click Actions > Create. The Create iSCSI Target page is displayed.
3. Type a descriptive name for the iSCSI target that you are configuring to
receive storage requests in the Target Description field. This name must be
unique from the other iSCSI targets.
4. Type the IP address of the iSCSI target in the IP Address field.
5. Type the port number that identifies the iSCSI target in the TCP Port field.
The value is a number between 0 and 65535.
6. Type the logical unit number (LUN) from which your iSCSI target will boot in
the Boot LUN field. LUN number has the format of XXXX-XXXX-XXXX-XXXX,
where X is hexadecimal digit.
7. Type the iSCSI Qualified Name (IQN) for the iSCSI target. The IQN can be in
IQN format or EUI format.
IQN format shows the address with a prefix of iqn. followed by a naming
identifier. An example is: iqn.this_is_my_node.
EUI format is a 16-digit hexadecimal value with a prefix of eui. An example
is: eui.0123456790ABCDEF.
8. Select the security type:
v None - No security is defined. This is the default option.
v One way - The target authenticates the initiator.
v Mutual - The initiator authenticates the target, and the target authenticates
the initiator.
9. If a Security type other than None was selected, type the Challenge
Handshake Authentication Protocol (CHAP) identifier to be used for iSCSI
communication in the CHAP ID field. The CHAP ID can have up to 16 ASCII
characters.
10. If a Security type other than None was selected, type the password that
corresponds to the CHAP ID in the Password field.
11. If a Security type other than None was selected, type the same password in
the Confirm Password field.

12. Click OK. The Target page is displayed again.
13. Verify the information on this page. If anything is incorrect, click Edit to make
changes.
14. Click OK. The Blade Server iSCSI Configuration page is displayed again.
15. Click the next step in the list.
Configuring iSCSI initiator DHCP settings

An iSCSI initiator is responsible for issuing storage requests such as reads or
writes. Typically the initiator is a server or client system requesting information
from an iSCSI target. Configuring iSCSI initiator Dynamic Host Configuration
Protocol (DHCP) settings consists of configuring various IP addresses and other
parameters.
To configure iSCSI initiator DHCP settings, complete the following steps:

1. If you have not already done so, click Define Initiators DHCP on the Blade
Server iSCSI Configuration page. The Initiator DHCP page is displayed.
2. Click Actions > Create. The Create iSCSI Initiator DHCP page is displayed.
3. Type a description of the iSCSI Dynamic Host Configuration Protocol (DHCP)
initiator that you want to configure in the Name field. This name must be
unique from other initiators.
4. Select the type of initiator:
v Hardware - iSCSI Host Bus Adapter (HBA), which is responsible for
protocol processing and uses dedicated ports as the transport media.
v Software - A device driver using TCP/IP on Ethernet network adapters to
send SCSI commands to issue storage requests, such as reads or writes.
5. Select the client ID from which IP parameters are obtained on the DHCP
server. Choose from the following options:
v Ethernet MAC - The IP parameters are obtained from the Ethernet MAC
address. This is the default.
v Scope/vendor ID - The IP parameters are obtained from the Scope/vendor
ID.
v Client Alternate ID - Type the client ID.
6. Optional: Type the Scope ID or the Vendor ID of the DHCP server from which
IP parameter information for the iSCSI DHCP initiator is to be obtained. This
field is optional, but provides more specific information for obtaining IP
parameters.
7. Click Custom DHCP Security to customize security and internet protocol for
your DHCP server. This overrides settings that might already exist on the
DHCP initiator.
8. If the DHCP server is on a virtual LAN (VLAN), type the VLAN identifier.
The VLAN ID is used for the initiator to access the iSCSI parameters from the
DHCP server on the VLAN.
9. Type the Challenge Handshake Authentication Protocol (CHAP) identifier to
be used for iSCSI communication in the CHAP ID field. The CHAP ID can
have up to 16 ASCII characters
10. Type the password that corresponds to the CHAP ID in the Password field.
11. Type the same password in the Confirm Password field.
12. Click Custom IP Settings to define specific IP settings for the iSCSI initiator.
13. Select the Discovery IP Address Usage. This is the type of discovery service
that iSCSI initiator is to use. You can choose from the following options:

v DHCP Server - Indicates that a DHCP server will be accessed by the
discovery IP address. This is the default option.
v SLP Server - Indicates that a Service Location Protocol (SLP) server will be
accessed by the discovery IP address.
v ISNS Server - Indicates that an Internet Storage Name Service (iSNS) service
will be accessed by the discovery IP address.
14. Type the IP address of the iSCSI initiator in the IP Address field.
15. Type the IP address of the specific DHCP server from which you want to
access iSCSI parameters in the Discovery IP Address field. This is an optional
field that is used for additional control during discovery.
16. Click OK. The Initiator DHCP page is displayed again.
changes.
Configuring iSCSI initiator VPD settings

from an iSCSI target. Configuring iSCSI initiator VPD settings consists of
specifying IP addresses and other parameters of iSCSI initiator that will be stored
in VPD and retrieved by the BIOS during startup.

1. If you have not already done so, click Define Initiators VPD on the Blade
Server iSCSI Configuration page. The Initiator VPD page is displayed.
2. Click Actions > Create. The Create iSCSI Initiator VPD page is displayed.
3. Type a description of the iSCSI Vital Product Data (VPD) initiator that you
want to configure in the Name field. This name must be unique from other
initiators.
5. Type the iSCSI Qualified Name (IQN) for the iSCSI initiator. The IQN can be
in IQN format or EUI format.
IQN format shows the address with a leading iqn. prefix followed by a
naming identifier. An example is: iqn.this_is_my_node.
EUI format is a 16-digit hexadecimal value with the leading prefix of eui. An
example is: eui.0123456790ABCDEF.
7. Type the Subnet mask for the local network in the Subnet Mask field.
8. Type the Gateway address for the iSCSI initiator in the Gateway field.
9. Type the virtual LAN ID that is used for iSCSI traffic within the subnet.
10. Click Use Boot LUN Information from the Target to indicate that the initiator
can access the target's boot LUN information.

14. Click OK. The Initiator VPD page is displayed again.
changes.
Configuring iSCSI initiator-to-target mappings

Mapping is the process of assigning iSCSI targets to iSCSI initiators. Each initiator
can be assigned up to two targets.
At least one blade and one initiator must be configured. Make sure that all the
initiators are mapped to at least one target, except for initiators of type ALL DHCP.
To configure iSCSI initiator-to-target mappings, complete the following steps:

1. If you have not already done so, click Define Mappings on the Blade Server
iSCSI Configuration page. The initiator-to-target mappings page is displayed.
2. Select the initiator from the table, then click Actions > Edit. A popup menu is
displayed for you to select targets.
3. Select the iSCSI target that you want the initiator to attempt to contact first in
the Target 1 field.
4. Type the number of times the initiator can attempt to contact this target in the
Retry Count field. Valid values are numbers 0 through 15.
5. In the Target 1 Timeout field, select from the following values for the number
of milliseconds (ms) that the initiator will attempt to contact the target before
timing out:
v 100 ms
v 200 ms
v 500 ms
v 2000 ms
v 20000 ms
6. Select the iSCSI target that you want the initiator to attempt to contact if it is
unable to access the first target, in the Target 2 field. Do not specify the same
target in both Target 1 and Target 2 fields.
7. Type the number of times that the initiator can attempt to contact this target
in the Retry Count field. Valid values are numbers 0 through 15.
timing out:
v 100 ms
v 200 ms
v 500 ms
v 2000 ms
v 20000 ms
9. Click OK. The initiator-to-target mappings page is displayed again.
changes.

Configuring iSCSI blade servers

Configuring iSCSI blade servers consists of specifying a name, bay, and other
information used to boot using the iSCSI protocol.
To configure iSCSI blade servers, complete the following steps:

1. If you have not already done so, click Define Blades on the Blade Server
iSCSI Configuration page. The Blade page is displayed.
2. Click Actions > Create. The Create iSCSI Blade page is displayed.
3. In the Name field, type something meaningful to describe the blade server
that you are configuring.
4. In the “Bay number” field, type the slot number of the blade that you are
configuring.
5. In each of the four Initiator Attempt fields, select an iSCSI initiator. These
initiators are used for boot attempts, and are tried in order from 1 to 4.
6. In each of the Port Attempt fields, select corresponding port for each of the
initiator boot attempts. Valid values are 0 through 3.
7. Click OK. The Blade page is displayed again.
changes.
10. Click Save to save your changes.
Configuring IBM BladeCenter SAS zone connectivity in real

time
You can change IBM BladeCenter SAS zone information by obtaining it from the
hardware, making changes, then copying the SAS zone information back to the
hardware.
advanced management modules only. The settings provided might be made by
way of the advanced management module, but actually affect the SAS switch.
To configure IBM BladeCenter SAS zone information in real time, complete the
following steps:
displayed.
2. Select a system and double-click its link. A list of attached devices is
displayed.
3. Select a IBM BladeCenter chassis.
current configuration for this chassis is displayed.
5. Select the entry whose Configuration Settings title is: SAS Module Zone
Configuration.
6. Click Edit.
7. Wait while IBM Systems Director gathers the information from the chassis.
The SAS Module Zone Configuration page is displayed with the current
information for this chassis.

8. Examine all the information on this page. Take note of the chassis type, I/O
module type, I/O modules, and which SAS configuration store is the Active
one.
9. Select the SAS configuration store that you want to change and click Actions
> Edit. Any of the SAS configuration stores can be edited, but changes made
to predefined SAS configuration stores must be saved in one of the four
user-defined SAS configuration stores. The Blades - External Ports page is
displayed.
10. Select a blade to permit access to an External SAS module port, by clicking on
the number beneath the blade icon. When access is not permitted, this is
indicated by a blank square instead of the number of the blade.
11. Select the SAS module ports that this blade can access, or click Select all to
select all ports for this blade.
12. Optional: If a port or blade is selected in error, click it again to remove it.
13. Optional: Repeat this process for each blade that you want to permit SAS
module port access.
14. Optional: If an I/O module type of SAS RAID Module is present:
a. Click the Blades - RAID tab.
b. Choose a blade and click the number below its icon.
c. Click the RAID subsystem icon to permit that blade to access the RAID
subsystem.
d. Repeat this process for any other blade that is to access the RAID
subsystem.
e. Click OK.
15. Optional: If an I/O module type of SAS Connectivity Module is present:
a. Click the Blades - Disks tab.
c. Choose the disks that you want to permit this blade to access by clicking
the disk icon.
d. Repeat this process for every blade that is to access the disks.
e. Click OK.
16. Optional: If at any time in this process you want to reset the SAS zone
configuration to the values that were first displayed when the information
was obtained from the chassis, click Reset.
17. Click OK. The Save Configuration page is displayed.
18. Select a SAS configuration store index. Valid values are 1, 2, 3, and 4. Only
these SAS configuration stores can be changed, because all the others are
predefined and cannot be modified.
v If you had been making changes to a predefined SAS configuration store,
you are asked to select one of the user-defined SAS configuration stores to
receive your changes.
v If you had been making changes to a user-defined SAS configuration store,
you cannot change the index of the SAS configuration store, but you can
change the Nickname and Description.
19. Type a Nickname whose length does not exceed 24 characters.
20. Type a Description whose length does not exceed 255 characters.
21. Click Deploy. The SAS Module Zone Configuration page is displayed again. If
you have made a change, all changed SAS configuration stores will have a
status of Pending.

22. Optional: If you want a store to become the Active one, select it and click
Actions > Activate.
23. If the changes that you have made are correct, click Deploy. A job scheduler is
displayed.
24. Enter job information.
25. Click OK.
26. Monitor the job to ensure that it completes and review any error messages.
Related tasks:
Managing IBM BladeCenter SAS zone configuration

Storage configuration templates are used to specify storage definitions, such as
storage volume definitions and SAS zoning. These configuration templates are
stored by IBM Systems Director and can then be deployed to the associated storage
devices. The configuration manager is used to create and manage these
Storage configuration templates can be created only for certain storage devices and
functions. When you create a storage configuration template, a list of choices is
displayed.
Related concepts:
Related tasks:
Navigating tables
Viewing storage configuration templates

You can view the details of a storage configuration template from the configuration
manager.
1. From the Configuration Summary page, locate the Configuration Tasks pane
and click View Configuration Templates. A table of configuration templates is
displayed.
2. Locate the storage configuration templates, which have one of these
configuration types:
v Storage Provisioning Configuration for storage volumes
v iSCSI Configuration for iSCSI devices
v SAN Configuration for SAN configuration mapping
v SAS Module Zone Configuration for SAS zoning
3. Select a configuration template.
4. Click Actions > Edit to see details.
5. Click Cancel when you are finished.

Related concepts:
Related tasks:
Navigating tables
Changing storage configuration templates

You can change the information in a storage configuration template from the
configuration manager.
1. From the Configuration Manager Summary page, locate the Configuration
Tasks pane and click View Configuration Templates. A table of configuration
templates is displayed.
2. Select the storage configuration template that you are going to change.
3. To see details, click Actions > Edit
4. Make changes to the configuration template, and click Save when you are
finished.
Related concepts:
Related tasks:
Navigating tables
Related reference:
mknsvol

A configuration template containing the definitions for a storage volume defined
on a IBM BladeCenterchassis is created using the configuration manager. One
configuration template can be used to define more than one storage volume.
You can use this configuration template for IBM BladeCenter installations that
include management modules or advanced management modules. The settings
provided by this configuration template might be made by way of the
management module, but actually might affect other components in the IBM
BladeCenter environment, such as blade servers. Some settings might not be
To create a configuration template for a storage volume, complete the following

steps:
and click Create a Template.
2. Choose the appropriate target type.
3. Enter a Name and Description for the new configuration template.
4. In the Configuration to create a template list, choose Storage provisioning.

5. Choose whether you want the Automatically Deploy feature.
6. Click Continue. The Storage Provisioning Configuration page is displayed.
7. Click Add Volume. The Create Storage Volumes page is displayed.
8. Fill in all necessary volume information.
9. When you are finished, click OK. The Storage Provisioning Configuration
page is displayed, with the new storage volume in the table.
10. Click Save to save this newly created template.
Related concepts:
Related tasks:
Navigating tables
Managing IBM BladeCenter SAN configuration mapping

You can modify the IBM BladeCenter Storage Area Network (SAN) mapping in
either real time or using configuration templates. You cannot modify the SAN
configuration itself using the IBM Systems Director Web interface, just the
mapping, which is the information about which blades are to have their SAN
configuration saved in the IBM Systems Director Server.
Related concepts:
Related tasks:
Related reference:
lsnshost
SAN Configuration profiles and SAN configuration mapping

SAN devices and SAN configuration profiles are used to ensure efficient sharing of
secondary storage devices among IBM BladeCenter servers. SAN configuration
mapping is used to determine which blades of an IBM BladeCenter will have their
SAN configuration saved in the IBM Systems Director Server.
The replace and remap function is used in case a blade fails. Its SAN configuration
(stored in the IBM Systems Director Server) is “re-mapped” before it replaces the
SAN configuration on the new blade. That is, the existing blade-specific
information in the SAN configuration is replaced with blade-specific information
about the new blade. The modified SAN configuration is then copied to the new
blade, and the SAN will be able to work with the new blade in the same way that
it worked with the original blade.
A Storage Area Network (SAN) is a network of shared storage devices. They are
shared by a number of servers (IBM BladeCenter blades in this case). Storage
devices contain many disk drives. The intent is to configure the servers to use as
much disk space as each server needs to do its intended job. A SAN can be
re-configured later if the needs of one or more of the servers change. A SAN can
become very complex. The IBM BladeCenter chassis contains devices that help
manage communication (for example, switches and management modules), and
provides for security. A user might be able to work only with a certain subset of
the hardware.

The configuration of a SAN from the viewpoint of an IBM BladeCenter server is
described by a SAN Configuration Profile, which resides on each IBM BladeCenter
server that is configured to participate in the SAN. This SAN Configuration Profile
describes which switches and storage devices are associated with this server. A
SAN Configuration Profile is a very complex description containing very long port
numbers. The typical datacenter has an extensive bank of IBM BladeCenter chassis
containing servers and storage arrays.
IBM Systems Director controls the SAN configuration using storage commands.
The IBM Systems Director Web interface does not manage the SAN configuration
itself. The IBM Systems Director Web interface does manage SAN configuration
mapping, which is used to implement the Replace and Remap function.
SAN configuration mapping is not the SAN Configuration profile itself. SAN
configuration mapping specifies which blades of the IBM BladeCenter will have
their SAN configuration information saved in the IBM Systems Director Server,
and which will not have their SAN configuration information saved in the IBM
Systems Director Server (most likely because there is no SAN or a particular blade
does not connect to it).
Replace and remap is used if one of the blades suffers a failure and must be
replaced, an another blade is inserted in place of the failing one. Replace and
remap is implemented this way:
1. The SAN Configuration Profiles for each configured IBM BladeCenter bay is
queried and a copy saved in the IBM Systems Director Server.
2. Because Automatically deploy is set (unless it was disabled), the IBM
BladeCenter chassis is notified of 'device removed' and 'device inserted' events
when the damaged hardware is removed and replaced with a working device.
a. When the damaged blade is removed, the 'device removed' event causes
this blade to be 'detached' from the SAN.
b. When a new blade is inserted, the 'device inserted' event causes the new
blade's information to be compared to the saved copy of the
damaged-blade's SAN Configuration Profile. The SAN Configuration Profile
would be updated with the new blade's hardware-specific information and
applied to the new blade.
c. The new blade would then work with the SAN in the same manner that the
failing one had worked.
If you want to work with a configuration template that contains SAN configuration
mapping, you must create one.
Related tasks:
Creating a SAN configuration mapping configuration template for an IBM
BladeCenter system
Modifying an existing IBM BladeCenter SAN configuration mapping and saving
the changes to a configuration template
Related reference:
lsnshost
Creating a SAN configuration mapping configuration template for

an IBM BladeCenter system
Create a Storage Area Network (SAN) configuration mapping configuration
template that can be deployed when replacing IBM BladeCenter devices. It is not

the SAN configuration itself that is saved in the configuration template, but an
indication of which blades will have their SAN configuration saved in the IBM
As part of creating a configuration plan for your IBM BladeCenter, you must
include a SAN Configuration mapping configuration template.
Note: If a switch has been configured to use security, the SAN configuration
template cannot be automatically deployed on blade deletion or insertion events.
BladeCenter environment, such as blade servers. All settings might not be
applicable for the supported components. Only advanced management modules
provide applicable settings for the following chassis models:
v IBM BladeCenter E chassis
v IBM BladeCenter H chassis
v IBM BladeCenter S chassis
To create a SAN configuration mapping configuration template, complete the

following steps:
and click Create a Template. The Configuration Templates page is displayed.
2. Click Create.
3. Choose a target type of BladeCenter Chassis, BladeCenter H Chassis, or
BladeCenter S Chassis.
4. Select SAN Configuration from the configuration template list.
5. Type a unique name and description for the new configuration template.
Note: If you deselect Automatically deploy this configuration template

when notified of a matching resource, this configuration will not be notified
when a relevant blade event occurs. Therefore, its intended function will not
be carried out.
6. Click Continue. The SAN Configuration page is displayed.
7. Select the bays that will have their SAN configuration saved to the IBM
v Select one or more bays.
v Click Select all bays to select all of them.
8. Optional: If you have selected a bay in error, click it again to remove it.
9. Click Save. The Configuration Templates page is displayed with the new
configuration template.
10. Select the new configuration template.
11. Click Actions > Add to Configuration Plan.
v Click Add selected configuration templates to an existing plan to put this
configuration template in an existing configuration plan. Choose the
configuration plan from the list.
v Click Add selected configuration templates to a new configuration plan to
create a new configuration plan with this configuration template as a
member. Type a name and description for the new configuration plan.

12. Optional: Click Open Configuration Plan list when done saving if you want
to go to the Configuration Plans page when this task is finished. If this is not
selected, you will be returned to the Configuration Templates page.
13. Click OK. The new SAN Configuration mapping configuration template is
added to the configuration plan.
While automatically deploy is active and a blade in a monitored bay is removed or

inserted, the SAN configuration will be automatically updated.
Related concepts:
SAN Configuration profiles and SAN configuration mapping
Related tasks:
Modifying an existing IBM BladeCenter SAN configuration mapping and saving
the changes to a configuration template
Related reference:
lsnshost
Modifying an existing IBM BladeCenter SAN configuration

mapping and saving the changes to a configuration template
If it becomes necessary to modify the SAN configuration mapping for an IBM
BladeCenter, use this procedure. Each IBM BladeCenter system is shipped with a
default SAN configuration mapping. There is no need to create one, but you might
want to change the default one to suit your needs.
You cannot obtain the current SAN configuration mapping, modify it, and then put
it back to the IBM BladeCenter. This is not supported. However, you can obtain the
current SAN configuration mapping, modify it, and then save the changes to a
configuration template. This configuration template can later be deployed on the
hardware, or used with the Automatically deploy feature.
components in the IBM BladeCenter environment, such as blade servers. All
settings might not be applicable for the supported components. Only advanced
management modules provide applicable settings for the following chassis models:
v IBM BladeCenter E chassis
v IBM BladeCenter H chassis
v IBM BladeCenter S chassis
To modify the SAN configuration mapping of an IBM BladeCenter system,

displayed.
2. Select a system and double-click its link. A list of attached devices is
displayed.
3. Select a IBM BladeCenter chassis.
current configuration for this IBM BladeCenter chassis is displayed.
5. Select the entry whose Configuration Settings title is: SAN Configuration.
6. Click Save as Configuration Template.
7. Type a unique name and description for the new configuration template.

8. Optional: If you want the new configuration template to be automatically
deployed, click Automatically deploy this configuration template when
notified of a matching resource.
9. Click Continue. The SAN Configuration page is displayed with the current
information for this IBM BladeCenter chassis.
10. Examine all the information on this page.
11. Select the bays that will be monitored for replace and remap:
v Select one or more bays.
v Click Select all bays to select all of them.
12. Optional: To reset the SAN configuration mapping to the values that were first
displayed when the information was obtained from the IBM BladeCenter
hardware, click Reset.
13. Optional: If you have selected a bay in error, click it again to remove it.
14. If the changes that you have made are correct, click Save. The Configuration
Templates page is displayed with the new configuration.
Related reference:
lsnshost
Configuring iSCSI components using configuration template

Configuring iSCSI components consists of configuring iSCSI initiators, iSCSI
targets, and their mappings. Both iSCSI V1 and iSCSI V2 are supported by IBM
Systems Director. At least one blade and one initiator must be configured. Make
sure that all the initiators are mapped to at least one target, except for initiators of
type ALL DHCP.
BladeCenter environment, such as blade servers. All settings might not be
To configure Internet Small Computer System Interface (iSCSI) components using a

configuration template, complete the following steps:
3. Type and Name and Description for the new configuration template.
4. In the Configuration to create a template list, choose iSCSI Configuration.
5. Click Continue. The Blade Server iSCSI Configuration page is displayed.
6. Select each Step and enter all necessary information.
7. Click Save to save these changes to the configuration template. If you exit this
page without clicking Save, your data is lost.

Related concepts:
Related tasks:
Configuring iSCSI targets

An iSCSI target is responsible for responding to storage requests such as reads or
writes. Typically, the target is a storage controller containing disks that respond to
storage requests. Configuring iSCSI targets consists of providing a location and
means to access to the iSCSI target.
To configure iSCSI targets, complete the following steps:

1. If you have not already done so, click Define Targets on the Blade Server
iSCSI Configuration page. The Target page is displayed.
2. Click Actions > Create. The Create iSCSI Target page is displayed.
3. Type a descriptive name for the iSCSI target that you are configuring to
receive storage requests in the Target Description field. This name must be
unique from the other iSCSI targets.
4. Type the IP address of the iSCSI target in the IP Address field.
5. Type the port number that identifies the iSCSI target in the TCP Port field.
The value is a number between 0 and 65535.
6. Type the logical unit number (LUN) from which your iSCSI target will boot in
the Boot LUN field. LUN number has the format of XXXX-XXXX-XXXX-XXXX,
where X is hexadecimal digit.
7. Type the iSCSI Qualified Name (IQN) for the iSCSI target. The IQN can be in
IQN format or EUI format.
IQN format shows the address with a prefix of iqn. followed by a naming
identifier. An example is: iqn.this_is_my_node.
EUI format is a 16-digit hexadecimal value with a prefix of eui. An example
is: eui.0123456790ABCDEF.
8. Select the security type:
v None - No security is defined. This is the default option.
v One way - The target authenticates the initiator.
v Mutual - The initiator authenticates the target, and the target authenticates
the initiator.
9. If a Security type other than None was selected, type the Challenge
Handshake Authentication Protocol (CHAP) identifier to be used for iSCSI
communication in the CHAP ID field. The CHAP ID can have up to 16 ASCII
characters.
10. If a Security type other than None was selected, type the password that
corresponds to the CHAP ID in the Password field.
11. If a Security type other than None was selected, type the same password in
the Confirm Password field.
12. Click OK. The Target page is displayed again.
changes.

Configuring iSCSI initiator DHCP settings
from an iSCSI target. Configuring iSCSI initiator Dynamic Host Configuration
Protocol (DHCP) settings consists of configuring various IP addresses and other
parameters.

1. If you have not already done so, click Define Initiators DHCP on the Blade
Server iSCSI Configuration page. The Initiator DHCP page is displayed.
2. Click Actions > Create. The Create iSCSI Initiator DHCP page is displayed.
3. Type a description of the iSCSI Dynamic Host Configuration Protocol (DHCP)
initiator that you want to configure in the Name field. This name must be
unique from other initiators.
5. Select the client ID from which IP parameters are obtained on the DHCP
server. Choose from the following options:
v Ethernet MAC - The IP parameters are obtained from the Ethernet MAC
address. This is the default.
v Scope/vendor ID - The IP parameters are obtained from the Scope/vendor
ID.
v Client Alternate ID - Type the client ID.
6. Optional: Type the Scope ID or the Vendor ID of the DHCP server from which
IP parameter information for the iSCSI DHCP initiator is to be obtained. This
field is optional, but provides more specific information for obtaining IP
parameters.
7. Click Custom DHCP Security to customize security and internet protocol for
your DHCP server. This overrides settings that might already exist on the
DHCP initiator.
8. If the DHCP server is on a virtual LAN (VLAN), type the VLAN identifier.
The VLAN ID is used for the initiator to access the iSCSI parameters from the
DHCP server on the VLAN.
12. Click Custom IP Settings to define specific IP settings for the iSCSI initiator.
13. Select the Discovery IP Address Usage. This is the type of discovery service
that iSCSI initiator is to use. You can choose from the following options:
v DHCP Server - Indicates that a DHCP server will be accessed by the
discovery IP address. This is the default option.
v SLP Server - Indicates that a Service Location Protocol (SLP) server will be
accessed by the discovery IP address.
v ISNS Server - Indicates that an Internet Storage Name Service (iSNS) service
will be accessed by the discovery IP address.

15. Type the IP address of the specific DHCP server from which you want to
access iSCSI parameters in the Discovery IP Address field. This is an optional
field that is used for additional control during discovery.
16. Click OK. The Initiator DHCP page is displayed again.
changes.
Configuring iSCSI initiator VPD settings

from an iSCSI target. Configuring iSCSI initiator VPD settings consists of
specifying IP addresses and other parameters of iSCSI initiator that will be stored
in VPD and retrieved by the BIOS during startup.

1. If you have not already done so, click Define Initiators VPD on the Blade
Server iSCSI Configuration page. The Initiator VPD page is displayed.
2. Click Actions > Create. The Create iSCSI Initiator VPD page is displayed.
3. Type a description of the iSCSI Vital Product Data (VPD) initiator that you
want to configure in the Name field. This name must be unique from other
initiators.
5. Type the iSCSI Qualified Name (IQN) for the iSCSI initiator. The IQN can be
in IQN format or EUI format.
IQN format shows the address with a leading iqn. prefix followed by a
naming identifier. An example is: iqn.this_is_my_node.
EUI format is a 16-digit hexadecimal value with the leading prefix of eui. An
example is: eui.0123456790ABCDEF.
7. Type the Subnet mask for the local network in the Subnet Mask field.
8. Type the Gateway address for the iSCSI initiator in the Gateway field.
9. Type the virtual LAN ID that is used for iSCSI traffic within the subnet.
10. Click Use Boot LUN Information from the Target to indicate that the initiator
can access the target's boot LUN information.
14. Click OK. The Initiator VPD page is displayed again.
changes.

Configuring iSCSI initiator-to-target mappings

Mapping is the process of assigning iSCSI targets to iSCSI initiators. Each initiator
can be assigned up to two targets.
At least one blade and one initiator must be configured. Make sure that all the
initiators are mapped to at least one target, except for initiators of type ALL DHCP.
To configure iSCSI initiator-to-target mappings, complete the following steps:

1. If you have not already done so, click Define Mappings on the Blade Server
iSCSI Configuration page. The initiator-to-target mappings page is displayed.
2. Select the initiator from the table, then click Actions > Edit. A popup menu is
displayed for you to select targets.
3. Select the iSCSI target that you want the initiator to attempt to contact first in
the Target 1 field.
4. Type the number of times the initiator can attempt to contact this target in the
Retry Count field. Valid values are numbers 0 through 15.
timing out:
v 100 ms
v 200 ms
v 500 ms
v 2000 ms
v 20000 ms
6. Select the iSCSI target that you want the initiator to attempt to contact if it is
unable to access the first target, in the Target 2 field. Do not specify the same
target in both Target 1 and Target 2 fields.
7. Type the number of times that the initiator can attempt to contact this target
in the Retry Count field. Valid values are numbers 0 through 15.
timing out:
v 100 ms
v 200 ms
v 500 ms
v 2000 ms
v 20000 ms
9. Click OK. The initiator-to-target mappings page is displayed again.
changes.
Configuring iSCSI blade servers

Configuring iSCSI blade servers consists of specifying a name, bay, and other
information used to boot using the iSCSI protocol.
To configure iSCSI blade servers, complete the following steps:

1. If you have not already done so, click Define Blades on the Blade Server
iSCSI Configuration page. The Blade page is displayed.
2. Click Actions > Create. The Create iSCSI Blade page is displayed.
3. In the Name field, type something meaningful to describe the blade server
that you are configuring.
4. In the “Bay number” field, type the slot number of the blade that you are
configuring.
5. In each of the four Initiator Attempt fields, select an iSCSI initiator. These
initiators are used for boot attempts, and are tried in order from 1 to 4.
6. In each of the Port Attempt fields, select corresponding port for each of the
initiator boot attempts. Valid values are 0 through 3.
7. Click OK. The Blade page is displayed again.
changes.
10. Click Save to save your changes.
Managing IBM BladeCenter SAS zone configuration

IBM BladeCenter Serial Attached SCSI (SAS) zone configuration can be performed
using configuration templates, or in real time. SAS zone information is used to
restrict the visibility of some devices by others; specifically to restrict disks and
external ports seen by blades.
advanced management modules only. The settings provided might be made by
way of the advanced management module, but actually affect the SAS switch.
Related concepts:
Related tasks:
SAS zoning and SAS configuration stores

Serial Attached SCSI (SAS) zoning is a way to limit which blades of an IBM
BladeCenter can access which disks and external ports. SAS zoning values are
maintained in SAS configuration stores on the SAS Connectivity Modules.
Before proceeding, review this information:

v This Web site has the IBM BladeCenter information pertaining to SAS zoning:
publib.boulder.ibm.com/infocenter/systems/topic/
com.ibm.bladecenter.8886.doc/dw1fs_r_integrated_storage_planning.html.
v Each IBM BladeCenter is shipped with SAS zoning information contained in a
set of SAS configuration stores. You do not need to create this information, but it
is advisable to review it to see that it matches your needs.
v You cannot alter the quantity of SAS configuration stores. Each SAS connectivity
module contains 14 SAS configuration stores. There are four user-defined
configurations in addition to the nine predefined configurations. However, only
those that are used to represent your particular server, switch, and attached
devices contain useful information, and are displayed by IBM Systems Director.
You will not see all of them for any configuration.

v You cannot alter the index number of the SAS configuration stores. They are
numbered 1 through 14. No configuration will display all of them at once. As an
example, a IBM BladeCenter H configuration has only SAS configuration stores 1
through 5.
v You cannot delete a SAS store or a set of them from the IBM BladeCenter
chassis.
v Only the user defined SAS configuration stores can be customized. All others are
predefined SAS configuration stores and cannot be changed. If you try to change
a predefined SAS configuration store, you are asked to save the changes in one
of the user-defined SAS configuration stores.
v The icons and hardware representation on these pages vary depending on the
exact hardware model being configured, and the types of storage attached to the
SAS switch.
v There is no separate View and Edit function for SAS zoning. Use the Edit
function to view the details, then click Cancel when you are finished.
When using configuration templates with SAS zoning, take note of the following:
v To manage SAS zones using a configuration template, you must create the
configuration template.
v When you create this configuration template for the first time, the user-defined
SAS stores are filled with the factory-supplied defaults.
v Although you can always delete a configuration template, there is no way to
delete SAS stores or the SAS zoning information on the IBM BladeCenter
system.
When changing SAS stores in real time, take note of the following:
v When managing SAS zoning in real time, you do not create this information.
Instead, you obtain it from the hardware and make any necessary changes. The
first time that you view the SAS zone information, the user-defined SAS
configuration stores are filled with the factory-supplied defaults, and the
predefined SAS configuration stores are filled with their predefined values.
Status values for a SAS store
A SAS store could have one or more status values. Every SAS store will not have a
status value at all times.
Active This is the currently active SAS store. Only one SAS store can be active on
an IBM BladeCenter SAS connectivity module at any time. This status is
available only when running in real time.
Activate
This SAS store has been designated to become the Active one. When
configuration changes are applied, the one that is currently Active will no
longer have the Active status. Only one store can have this status
(Activate) at any time.
Pending
This SAS store has been changed, but the changes have not yet been
applied to the IBM BladeCenter system. When the changes are applied, the
Pending status will be removed. A SAS store with the Active or Activate
status can also have a status of Pending.

Conflict
Indicates that the current configuration has two different active zones in
two SAS switches, which is not recommended. This status is available only
when there are two SAS switches.
An example is if the active zone on I/O module 3 is 1, and the active zone
on I/O module 4 is 2. This is a conflict. The I/O module 3 information is
used. This status is available only when running in real time.
Related tasks:
Configuring IBM BladeCenter SAS zone connectivity using configuration templates
Configuring IBM BladeCenter SAS zone connectivity using

configuration templates
Create a configuration template with the Serial Attached SCSI (SAS) zone
information.
To configure a SAS zoning configuration template, complete the following steps:

3. Type and Name and Description for the new configuration template.
4. In the Configuration to create a template list, choose SAS Module Zone
Configuration.
5. Click Continue. The SAS Module Zone Configuration page is displayed.
6. Select the I/O module type. There are different values depending on the IBM
BladeCenter model that you are working with.
v For IBM BladeCenter chassis, IBM BladeCenter H chassis, IBM BladeCenter
HT chassis, and IBM BladeCenter T chassis, choose Base SAS Module.
v For IBM BladeCenter S chassis with a SAS module attached to a RAID,
choose RAID SAS Module.
v For IBM BladeCenter S chassis with a SAS module not attached to a RAID,
choose Non-RAID SAS Module.
7. Select the I/O module to which the SAS zone configuration configuration
template will apply. Valid values are I/O module 3, I/O module 4, or I/O
modules 3 and 4. The latter can be chosen only with IBM BladeCenter S
systems.
8. Select the SAS configuration store that you wish to change and click Actions >
Edit. Any of the SAS configuration stores can be edited, but changes made to
predefined SAS configurations stores must be saved in one of the four
user-defined SAS configuration stores. The Blades - External Ports page is
displayed.
9. Select one of the blades to permit access to an External SAS module port, by
clicking on the blade number beneath the blade icon.
10. Select the SAS module ports that this blade can access, or click Select all to
select all ports for this blade.
11. Optional: If a port or blade is selected in error, click it again to remove it.
12. Optional: Repeat this process for each blade that you want to permit SAS
module port access.
13. Optional: If an I/O module type of SAS RAID Module was selected:
a. Click the Blades - RAID tab.

c. Click the RAID subsystem icon to permit that blade to access to the RAID
subsystem.
d. Repeat this process for all blades that are to access the RAID subsystem.
e. Click OK.
14. Optional: If an I/O module type of SAS Connectivity Module was selected:
a. Click the Blades - Disks tab.
c. Choose the disks that you want to permit this blade to access by clicking
the disk icon.
d. Repeat this process for all blades that are to access the RAID subsystem.
e. Repeat this process for all blades that are to access the disks.
f. Click OK.
15. Click OK. The Save Configuration page is displayed.
16. Select a SAS configuration store. Valid values are 1, 2, 3, and 4. Only these
SAS configuration stores can be changed, because all the others are predefined
and cannot be modified.
v If you had been making changes to a predefined SAS configuration store,
you are asked to select one of the user-defined SAS configuration stores to
receive your changes.
v If you had been making changes to a user-defined SAS configuration store,
you cannot change the index of the SAS configuration store, but you can
change the Nickname and Description.
17. Type a Nickname whose length does not exceed 24 characters.
18. Type a Description whose length does not exceed 255 characters.
19. Click OK. The SAS Module Zone Configuration page is displayed again.
20. Optional: If you want a store to become the Active one when this
configuration template is deployed, select it and click Actions > Activate.
21. Click Save to save the changes to the configuration template.
Related concepts:
SAS zoning and SAS configuration stores

Chapter 14. Managing virtual environments
As you monitor the health of your virtual environment, you can perform
additional virtualization management by activating the IBM Systems Director
VMControl plug-in. VMControl includes the function that was formerly available
as part of virtualization manager.
VMControl allows you to quickly respond to problems by creating additional

virtual servers, editing the resources that are allocated to existing virtual servers, or
relocating virtual servers to another host. You can also perform power
management tasks on your virtual servers. For more information, see "IBM
Systems Director VMControl."
Related concepts:
IBM Systems Director VMControl

Chapter 15. Security
IBM Systems Director offers a number of security features. With the provided
authentication and user administration options, system administrators can specify
user privileges for specific tasks and resources. User registry integration, integrity,
confidentiality, and secure sockets layer (SSL) supported secure data transmission
are other key elements of a basic security model.
IBM Systems Director is controlled by two interdependent processes: authentication

and authorization. Authentication is used to determine the identity of the user and
verify and validate that identity. Authorization checks the permissions of the
authenticated user and controls access to resources based on the roles that are
assigned to the user.
The IBM Systems Director Server uses a role-based access control (RBAC) service
with which an administrator can create custom sets of permissions, known as roles,
and assign them to individual users or groups. A set of task, command-line
interface (CLI), and application permissions that is applied to one or more
resources defines an authorization role. Each role can be applied to many users,
and each user can have many roles. Regulating user roles is an effective way to
control security for your system as it enables you to control access to every task
and CLI command.
Note: By default, the only user ID that is assigned to the SMAdministrator role
(the only one that can take any action right after installation) is the user ID that
was used to install IBM Systems Director. Even if you have other administrators
defined on the management server, a role is not assigned to them and they are
unable to administer IBM Systems Director. They will instead receive a message
telling them to contact their system administrator. To ensure that you are using the
correct user ID, before logging on to the IBM Systems Director Web interface,
ensure that you can use that same user ID and password to successfully log on to
the operating system on the management server.
Using the security features in IBM Systems Director, an administrator can perform
the following functions:
v Manage auditing
v View and manage authorized users and groups
v Assign roles and resources to users
v Manage user properties
v Create and modify roles
v Manage permissions that are grouped within a role
v Use roles to control access to a system
v Request access to a system
v Manage credentials and their associated mappings
To use IBM Systems Director to access or manage a system, the following steps are
taken:
1. A user authenticates to the IBM Systems Director Web interface using their user
ID and password, which are verified with the user ID and password stored in
the user registry that is configured by IBM Systems Director. The user registry
is configured by default on the local operating system, but it can also reside on

a domain controller, in an active directory, or on a Lightweight Directory
Access Protocol (LDAP) or OpenLDAP server. IBM Systems Director also finds
the user's group membership by associating their user ID with the user ID
contained in the group.
2. If the user ID and password that the user enters matches the user ID and
password stored in the registry on the target system, then the user is
authenticated to the target system.
3. When the user tries to perform a task, the authorization mechanism compares
their user ID or the group ID of the group to which they belong to the
associated role-based access control (RBAC) settings in IBM Systems Director. If
a role exists that contains the authorizations necessary for that task, then the
task is performed.
Related tasks:
Managing auditing
Related reference:
Security and requesting access troubleshooting
Security requirements
Authenticating users to IBM Systems Director

Authentication is the process that IBM Systems Director uses to determine if the
identity claimed by a user, a system, or an application is correct. The process of
authenticating users involves a user registry and an authentication mechanism.
With user authentication, you can access and manage resources with the IBM
Systems Director Web interface.
Note: Network Information Services is not supported by IBM Systems Director.

Related tasks:
Planning IBM Systems Director users and groups

Managing auditing
Related reference:
User authentication
User authentication is the security mechanism by which a user's credentials that
are used to access a system are verified. After authentication, a user can access the
system. However, to access a specific resource or perform a specific task, the user
must also have the appropriate authorization. Authentication prevents
unauthorized management servers or rogue managed-system applications from
accessing the resources.
To be authenticated, users are required to enter a user ID and password for the
system that they want to access. The authentication process uses the configured
user registry, which is from either the operating system, Lightweight Directory
Access Protocol (LDAP), or the domain controller.
The user accounts and groups that are created at the user registry level to log in to
a system are also used by IBM Systems Director. For example, to log in to IBM
Systems Director Web interface, a user must authenticate by logging in with a user

registry level account for the management server. To use IBM Systems Director
Web interface to access another system, the user must first have the appropriate
credentials to access that other system.
Related tasks:
Related reference:
Users and user groups in IBM Systems Director

In IBM Systems Director, users and user groups are based on users and groups
that are defined in the configured registry, which is associated with either the
operating system, Lightweight Directory Access Protocol (LDAP), or the domain
controller. IBM Systems Director uses the user and group information for
authentication and authorization.
IBM Systems Director does not provide the capability to create, update, or delete
users or groups in a user registry regardless of where the registry resides. You can
create new users, user groups, and chassis roles from the management software
web interface or command-line interface.To manage users or groups in the user
registry, you must instead use the appropriate tool associated with the registry in
which the users or groups are stored. IBM Systems Director does, however, give
you the ability to enter and edit information for each user or group that describes
each in the context of IBM Systems Director. If the user registry has a value for the
fullname property, then the user registry will always get the higher precedence
than the IBM Systems Director database. If the fullname property in the registry is
set to empty, then you will be able to edit the fullname in the context of IBM
Systems Director. This will be displayed until the fullname property is modified
directly in the user registry.
Access to particular resources or tasks is governed by restrictions based on the user

ID or user group membership and the roles that are defined for each user. For a
user to access IBM Systems Director Server, one of the following conditions must
exist:
v The user is a member of a user group that is authorized for IBM Systems
Director Server.
v The user has administrator privileges on the Windows management server or
Windows domain.
v The user is a root user on the AIX or Linux management server.
Users are specific to the systems on which they are created. Each system has its
own set of users that is independent of those on any other system in the network
or in accounts that are created in IBM Systems Director. The users are placed in
either predefined or user-created groups.
In a default IBM Systems Director Server installation scenario that uses the local
operating-system registry, the following IBM Systems Director user groups are
automatically created at the operating system level on the management server.
Note:
v Members of the root and Administrators group are authorized for all operations
on all resources.
Chapter 15. Security 635

v The only role that is automatically assigned is to the administrator user ID that
installed IBM Systems Director. So, initially, no other user is associated with a
role. That IBM Systems Director administrator must then associate the other
users with roles.
v If you want to use Lightweight Directory Access Protocol (LDAP) or another
tool that the registry supports, you might need to manually create all of these
user groups and assign users to them.
v IBM Systems Director does not support Network Information Services (NIS).
smadmin (Administrator group)
Members of the smadmin group are authorized for all operations. They
have administrative access to IBM Systems Director and can perform all
administrative tasks. These members can define the privileges available to
the smmgr, smmon, smuser, and groupread groups. The privileges
available to members of the smadmin group cannot be restricted.
Note: At the operating system level, the smadmin group maps to

SMAdministrator role. A best practice is to add or remove users from the
user groups but to not delete the system-defined user groups because IBM
Systems Director uses them in the IBM Systems Director Web interface to
authorize users to IBM Systems Director.
Important: If you add a user to this group, the user can modify or delete
all system-level resources and resources for all other users, including
operating-system and user files and processes. Before assigning a user to
this group, be sure that the user requires SMAdministrator authority.
smmgr (Manager group)
Members of the smmgr group can perform management operations, which
are a subset of the functions that a member of the smadmin group can
perform.
smmon (Monitor group)
Members of the smmon group can access those administrative functions
that provide read-only access, such as monitoring.
smuser (User group)
The smuser group includes all authenticated users. Members can perform
only basic operations.
You can also use the smcli authusergp command to authorize additional user
groups to access IBM Systems Director. These user groups are granted various
levels of authority in the form of privileges and tasks and resource access.

Related concepts:
Managing user groups
Related tasks:
Planning IBM Systems Director users and groups

Related reference:
authusergp
Authenticating IBM Systems Director users stored in the local

operating system
IBM Systems Director can authenticate user login requests to the registry for the
configured operating system. The local operating-system user registry is the one
that IBM Systems Director uses by default.
To create a local operating-system user account that has access to IBM Systems
Director Server, complete the following steps:
1. Create a user account in the user registry that is associated with the
management server. For instructions about creating a user account in the user
registry that is associated with the management server, see the documentation
for that management server.
2. Add the user as a member of one of the user groups defined for IBM Systems
Director at the user registry level. You can either use one of the predefined
groups or create your own.
Note: If you create a new custom group on the IBM Systems Director Server,
you will have to authorize it. To do so, log in to the IBM Systems Director Web
interface as an administrator and navigate to Security > Users > Authorize
Groups.... Enter the local group name in the wizard to authorize the new
group. You can also authorize the group from the command-line interface using
smcli authusergp.
3. Log in to IBM Systems Director Web interface as an administrator and navigate
to Security > Users. The users that you configured in the previous steps will be
displayed in the list.
After you authenticate to IBM Systems Director, you can authorize each user to
IBM Systems Director tasks and resources.
Related concepts:
User authentication
Users and groups
Managing SSL encryption for CIM

Encryption is enabled by default using Secure Sockets Layer (SSL) for Common
Information Model (CIM). Use the following procedure to disable or enable SSL for
CIM.
1. Run this command to get the current value of enableHttpsConnection:
cimconfig -g enableHttpsConnection
The current value of the enableHttpsConnection setting displays. If the current

value is true, SSL is enabled. If the current value is false, SSL is disabled.
2. If you want to disable SSL, run this command:
cimconfig -s enableHttpsConnection=false -p

3. If you want to enable SSL, run this command:
cimconfig -s enableHttpsConnection=true -p
4. Run this command to restart the CIM server:
/etc/init.d/cimserverd restart
The new SSL encryption setting takes effect once the server restarts.
Authenticating IBM Systems Director users stored in the

Microsoft Active Directory domain
IBM Systems Director can authenticate user login requests to a domain server.
The following procedure applies to IBM Systems Director that runs on Windows. If
IBM Systems Director runs on any other operating system, do not use this
procedure to authenticate users. Instead, use “Authenticating IBM Systems Director
users stored in LDAP” on page 639.
To create a Microsoft Active Directory user account that has access to IBM Systems
Director Server, complete the following steps:
1. Create a user account, or choose an existing user account, in the Active
Directory user registry. For instructions about creating a user account in the
domain server user registry, see the Active Directory documentation.
2. Add the Active Directory user to a defined Active Directory global security
group. You will have to create your own Active Directory group if a suitable
one does not exist.
3. Add the global group to an authorized local group of the IBM Systems Director
Server, such as, smadmin, smmgr, smmon, or smuser. For instructions, see the
product documentation of the Active Directory domain server.
Notes:
v Nested global groups are not supported in IBM Systems Director. This
applies to console authentication and requesting access to endpoints.
v For best practices, do not add Active Directory users directly to the local
groups of any IBM Systems Director Servers.
v IBM Systems Director works best with Active Directory when its users are
placed in global groups and then those global groups are placed within the
local groups of the IBM Systems Director Server (such as smadmin, smmgr,
smmon, smuser, or a custom local group that you authorize).
v Tip: One way that you might complete this task is complete the following
steps:
a. Log in to the Active Directory domain server.
b. Select the global group.
c. Right-click the global group and select Properties > Member Of. A list of
groups is displayed. The group that you selected in the previous step
belongs to the groups in this list.
d. Click Add.
e. Specify one of the following groups:
– Any of the authorized local groups, such smadmin, smmgr, smmon, or
smuser
– Any customized authorized group
v Alternatively, you can create a custom local group. If you create a new
custom local group on the IBM Systems Director Server, you will have to
authorize it. To do so, log in to the IBM Systems Director Web interface as an
administrator and navigate to Security > Users > Authorize Groups.... Enter
the local group name in the wizard to authorize the new group. You can also
authorize the group from the command-line interface using smcli
authusergp.
v If you want to authorize a domain group directly without adding it to the
local group, log in to the IBM Systems Director Web interface as an
administrator and navigate to Security > Users > Authorize Groups.... Enter
the domain group name in the wizard to authorize the new group. Ensure
that you include the domain name with the group name in NetBios style,
which is DomainName\GroupName. Domain names and group names are
case-sensitive. You can also authorize the group from the command-line
interface by using smcli authusergp.
to Security > Users. Active Directory users that are managed as a group will
not appear in the list. However, you should see the group listed. Users that are
local to the IBM Systems Director Server will show up on this list as they are
managed as individuals.
You can now assign additional roles to users to access specific IBM Systems
Director tasks and resources.
Related concepts:
User authentication
Users and groups
Authenticating IBM Systems Director users stored in LDAP

IBM Systems Director can authenticate user login requests to a Lightweight
Directory Access Protocol (LDAP) server.
LDAP is an open protocol that uses TCP/IP to provide access to directories that
support an X.500 model. Managing your user information with LDAP instead of
the local operating system is useful when you have many users who operate IBM
Systems Director. For IBM Systems Director user authentication, LDAP has several
advantages:
v Many companies have existing LDAP directories of employees. You can use
these existing directories for IBM Systems Director user authentication. When
you use these existing directories, you can save the time and effort that is
required to create new user accounts on the management server.
v An administrator can immediately modify or terminate the access of a user on
all instances of IBM Systems Director Server by completing one of the following
tasks:
– Change the LDAP group memberships of a user.
– Remove the LDAP entry of a user.
v Users need only one user ID and password, as opposed to multiple accounts for
each management server.
To create an LDAP user account that has access to IBM Systems Director Server,
After you authenticate to IBM Systems Director, you can authorize each user to
IBM Systems Director tasks and resources.

Related concepts:
User authentication
Users and groups
Related reference:
Handling LDAP authentication failures
Verifying the requirements and support for LDAP authentication

Ensure that your environment satisfies the support and requirements for
authenticating IBM Systems Director users that are stored in LDAP.
Operating system requirements and support
The operating system requirements and support for LDAP authentication are the
same as for IBM Director Server. To see the operating system requirements and
support for IBM Director Server, see Supported operating systems.
The type of operating system on which you install IBM Director Server does not
affect the LDAP authentication configuration. LDAP authentication works similarly
for each supported operating system.
Supported LDAP servers

v IBM Tivoli Directory Server
v Microsoft Active Directory Application Mode (ADAM)
v Microsoft Active Directory LDAP (AD LDAP)
v OpenLDAP
Because LDAP is a standard, other LDAP servers might work if you know the
correct property values to use in the properties file. However, remember that these
other LDAP servers are not supported.
Restrictions
Avoid using Pluggable Authentication Modules (PAM) software from third parties
to enable IBM Systems Director to use a Microsoft Active Directory LDAP server.
For example, avoid using software such as Centrify, Quest Authentication Services,
or other Linux packages for this purpose. Instead, enable the LDAP client that is
included with IBM Systems Director. This enablement eliminates the need to use
third-party software to enable IBM Systems Director to use a Microsoft Active
Directory LDAP server.
Completing the LDAP authentication worksheet

Use this worksheet to plan for configuring LDAP on IBM Systems Director. After
configuration, IBM Systems Director can authenticate user login requests to an
LDAP server.
To configure LDAP on IBM Systems Director, you must modify the contents of the
securityLDAP.properties file with the correct configuration values for your LDAP
server. To find the configuration information about your LDAP server, you can
browse its interface by using an LDAP tool such as ldapsearch, ldp, or Apache
Directory Studio.

The following tables show configuration attributes that are included in the
securityLDAP.properties file. For each attribute, the tables include a description of
the attribute, tips about which values to set for each attribute, and example values
to use.
Important:
v The sample security.ldap file (which you later rename to the
securityLDAP.properties file) contains more, and sometimes different,
information than what is contained in this worksheet. The sample file is generic
to the LDAP standard and not specific to configuring LDAP on IBM Systems
Director. This worksheet provides the specific configuration information that is
required for configuring LDAP on IBM Systems Director. When the information
and examples differ between the sample file and this worksheet, use this
worksheet to help you configure LDAP on IBM Systems Director.
v This worksheet contains information about the configuration attributes that are
required to configure LDAP on IBM Systems Director. Do not configure other
attributes unless directed by technical support.
v The securityLDAP.properties file is case-sensitive even if the LDAP server is
not.
Mandatory configuration attributes
The following table lists the LDAP configuration attributes that are required for
IBM Systems Director, a description of each attribute, and example values for each
attribute.
Table 48. Mandatory LDAP configuration attributes, descriptions, and examples
LDAP configuration attribute Your value
com.ibm.lwi.LDAPHost Custom value:
Examples:
The host name of the LDAP server.
v 9.10.11.12
You can specify the IP address or the fully qualified host v ldapserver.acompany.com
name of the server.
com.ibm.lwi.LDAPPort __ v 636
__ v 389
The listening port that is defined on the LDAP server.
Set this value to 636 if com.ibm.lwi.ldap.ssl.enable =

true.
Set this value to 389 if com.ibm.lwi.ldap.ssl.enable is

not set or is set to false.
Tip: Configure LDAP without using SSL and then
validate the configuration. After LDAP works successfully
without using SSL, then configure LDAP to use SSL. This
technique can isolate SSL configuration problems for
faster troubleshooting.

Table 48. Mandatory LDAP configuration attributes, descriptions, and examples (continued)
com.ibm.lwi.LDAPBase Custom value:
Examples:
The base (root) DN that is defined on the LDAP server.
v AD LDAP:
The LDAPBase value determines the location in the LDAP DC=MSADLDAP,DC=netfinity,DC=com
tree from which IBM Systems Director starts the search. v ADAM:
IBM Systems Director supports 1 search base. The groups, CN=ADAMLDAP,DC=netfinity,DC=com
and the users within those groups, that you configure in v OpenLDAP or IBM Tivoli Directory Server:
“Configuring the LDAP server” on page 647 must share a dc=ibm,dc=com
common base. If they do not share a common base, you
cannot log in. For example if the base is
dc=abc,dc=puzzle,dc=com then IBM Systems Director
finds CN=user1,dc=abc,dc=puzzle,dc=com but does not
find CN=user2,dc=puzzle,dc=com.
Choose the most restrictive LDAPBase value possible. Some

LDAP servers limit the amount of data that they return in
response to a search request. Therefore, be as specific as
possible without excluding the Admin user or any other
users or groups for which you intend to give login rights.
com.ibm.lwi.LDAPAdminUser Custom value:
Examples:
The administrator user name that is defined on the LDAP
v AD LDAP:
server. IBM Systems Director uses this user name to log
in to the LDAP server and search for the user IDs and CN=Administrator,CN=Users,CN=MSADLDAP, \
passwords of the users that log in to IBM Systems DC=netfinity,DC=com
Director. This attribute is required. v ADAM:
CN=administrator, CN=Users, CN=ADAMLDAP, \
This user can be any user that has the following rights: DC=netfinity, DC=com
v Rights to connect to the LDAP server v OpenLDAP or IBM Tivoli Directory Server:
v Rights to query the groups, including their contents CN=IBM Director Service Account,CN=Users, \
and attributes, that you configure in “Configuring the DC=systemx,DC=sc,DC=ibm,DC=com
LDAP server” on page 647
v Rights to query the users, including their contents and
attributes, that require access to IBM Systems Director
Tip: Choose a unique user name for this attribute. If you
use an existing IBM Systems Director user name, reading
the LDAP server logs can be confusing.
com.ibm.lwi.LDAPAdminPassword Custom value:
Example: sEcpas5w0rd
The encrypted password of the administrator that is
defined on the LDAP server. This attribute is required.
Enter the unencrypted password in the

securityLDAP.properties file. After you finish editing the
file, you encrypt all of the passwords by using the
lwiencoder command.

com.ibm.lwi.searchfilter Custom value:
Examples:
The user search-filter to use on the LDAP server.
v AD LDAP:
(&(sAMAccountName=%v)(objectcategory=user))
v ADAM:
(&(CN=%v)(objectclass=person))
v OpenLDAP or IBM Tivoli Directory Server:
(&(uid=%v)(objectclass=inetOrgPerson))
com.ibm.lwi.rolemanager.ldap.filters.usergroup Custom value:

Examples:
The filter string (LDAP) that is used to search the
v AD LDAP:
directory for group objects. The filter returns groups that
are searched for users. (|(objectCategory=group) \
(objectCategory=groupOfNames))
This value depends on the LDAP server that you use and v ADAM:
which attributes and object types are supported. (|(objectCategory=group) \
(objectCategory=groupOfNames))
Some LDAP servers limit the amount of data that they
return in response to a search request. Therefore, be as v OpenLDAP or IBM Tivoli Directory Server:
specific as possible without excluding any users or groups (|(objectclass=groupOfNames) \
for which you intend to give login rights. (objectclass=groupOfUniqueNames))
In general, you can use broad search filters for smaller These examples use broad search filters. To see an
LDAP environments, such as environments with example of more narrow search filters, see “Example of
hundreds of LDAP users. You can use more narrow narrow search filters for users and groups” on page 647.
search filters for larger LDAP environments, such as
environments with thousands of LDAP users.
com.ibm.lwi.rolemanager.ldap.filters.users Custom value:
Examples:
The filter string (LDAP) that is used to search the
v AD LDAP:
directory for user objects. The filter returns users that are
found within the LDAP server. (|(objectCategory=person)(objectCategory=user))
v ADAM:
The value depends on the LDAP server that you use and
(|(objectCategory=person)(objectCategory=user))
which attributes and object types are supported.
v OpenLDAP or IBM Tivoli Directory Server:
Some LDAP servers limit the amount of data that they (objectclass=inetOrgPerson)
return in response to a search request. Therefore, be as
specific as possible without excluding any users or groups These examples use broad search filters. To see an
for which you intend to give login rights. example of more narrow search filters, see “Example of
narrow search filters for users and groups” on page 647.
In general, you can use broad search filters for smaller
LDAP environments, such as environments with
hundreds of LDAP users. You can use more narrow
search filters for larger LDAP environments, such as
environments with thousands of LDAP users.

com.ibm.lwi.rolemanager.ldap.names.memberAttribute Default or custom value:
Example: member
The name of the member attribute of the role object in the
directory. This attribute is the LDAP group attribute that
determines whether a user is a member of a particular
group. If there is more than 1 property value, separate the
values by using commas.
The default value is member. However, the values uid or

memberuid are often used instead. The value depends on
the LDAP server that you use.
com.ibm.lwi.rolemanager.ldap.names.loginName Custom value:
Examples:
The name of the login name attribute of the user in the
v AD LDAP: sAMAccountName
directory. For example, if the user IDs are stored in LDAP
with DN, CN=id, CN=Users, CN=host, DC=xxx, and v ADAM: CN
DC=com, then set the value for loginName to CN. v OpenLDAP or IBM Tivoli Directory Server: uid
Users often log in using this name.

com.ibm.lwi.security.rolemanagers.ldap. \ Do not use.
getGroupsByUser.includeNested
IBM Systems Director does not support nested groups.

This attribute does not work.
Optional configuration attributes
The following table lists optional attributes for configuring LDAP on IBM Systems
Director, a description of each attribute, and example values for each attribute.
Table 49. Optional LDAP configuration attributes, descriptions, and examples
com.ibm.lwi.ldap.ssl.enable __ v true: Enable LDAP SSL communication.
__ v false: Disable LDAP SSL communication.
Enable or disable LDAP SSL communication. If you set
the value to true, you must set all of the
com.ibm.lwi.ldap.ssl.property attributes.
Tip: Configure LDAP without using SSL and then
validate the configuration. After LDAP works successfully
without using SSL, then configure LDAP to use SSL. This
technique can isolate SSL configuration problems for
faster troubleshooting.
com.ibm.lwi.ldap.ssl.keyStore Default or custom value:
Examples:
The client keystore file path. The path can be absolute or
v Relative path: /../../../data/security/keystore/
relative to the current LWI working directory, which is the
ibmjsse2.jks
LWI_Dir/runtime/core directory. This attribute must be set
if the com.ibm.lwi.ldap.ssl.enable attribute is set to This directory is relative to the current LWI working
true. directory (LWI_Dir/runtime/core)
v Absolute path for Linux: /opt/ibm/director/data/
The default value is director_install/data/security/ security/keystore/ibmjsse2.jks
keystore/ibmjsse2.jks.
v Absolute path for Windows: C\:\\Program
Files\\IBM\\Director\\data\\security\\keystore\\
ibmjsse2.jks

Table 49. Optional LDAP configuration attributes, descriptions, and examples (continued)
com.ibm.lwi.ldap.ssl.keyStorePassword Custom value:
Example: kEyst0r3p8d
The password of the keystore. This attribute must be set if
the com.ibm.lwi.ldap.ssl.enable attribute is set to true.

lwiencoder command.
com.ibm.lwi.ldap.ssl.trustStore Default or custom value:
Examples:
The client truststore file path. The path can be absolute or
v Relative path: /../../../data/security/keystore/
relative to the current LWI working directory, which is the
ibmjsse2.jts
LWI_Dir/runtime/core directory. This attribute must be set
if the com.ibm.lwi.ldap.ssl.enable attribute is set to This directory is relative to current LWI working
true. directory (LWI_Dir/runtime/core)
v Absolute path for Linux: /opt/ibm/director/data/
The default value is director_install/data/security/ security/keystore/ibmjsse2.jts
keystore/ibmjsse2.jts.
v Absolute path for Windows: C\:\\Program
Files\\IBM\\Director\\data\\security\\keystore\\
ibmjsse2.jts
com.ibm.lwi.ldap.ssl.trustStorePassword Custom value:
Example: tRust5t0r3p8d
The password of the truststore. This attribute must be set
if the com.ibm.lwi.ldap.ssl.enable attribute is set to
true.

lwiencoder command.
com.ibm.lwi.security.username.caseSensitive __ v true: Login names are case-sensitive. This is the
default value.
Indicates whether login names are case-sensitive. This __ v false: Login names are not case-sensitive.
setting applies to login names and the definitions of the
DNs of login names.
If you want to authorize both the uppercase and

lowercase versions of login names, set this attribute to
false.
More configuration attributes for OpenLDAP servers
The following table lists more attributes for configuring IBM Systems Director with
OpenLDAP servers, a description of each attribute, and example values for each
attribute.
Table 50. Additional LDAP configuration attributes, descriptions, and examples for OpenLDAP servers
com.ibm.lwi.rolemanager.ldap.names.groupName Custom value:
Example: cn
The group name attribute of the group object in the
directory. This attribute is similar to the login name for
the user.

Table 50. Additional LDAP configuration attributes, descriptions, and examples for OpenLDAP servers (continued)
com.ibm.lwi.rolemanager.ldap.names.groupID Custom value:
Example: gidNumber
The name of the group ID (number) attribute of the
group object in the directory.
com.ibm.lwi.rolemanager.ldap.names. \ Custom value:
userPrimaryGroupID Example: gidNumber
The name of the primary group ID (number) attribute of

the user object in the directory.
com.ibm.lwi.rolemanager.ldap.filters.usersByGroupId Custom value:
Example:
The search filter for users by primary group.
(&(gidNumber={x})(objectclass=person))
Restriction: Do not use this attribute with nested groups.
Where x is group ID number of the primary group. For
example, 35. The default is 0.
com.ibm.lwi.rolemanager.ldap.filters.groupsByMembers Custom value:
Example:
The search filter for groups by member or by group ID
(&(|(gidNumber={x})(memberUID={y})) \
number. (objectclass=posixGroup))
Restriction: Do not use this attribute with nested groups.
Where:
v x is group ID number. For example, 35. The default is
0.
v y is the member. For example, 27. The default is 1.
com.ibm.lwi.rolemanager.ldap.names. \ Custom value:
memberAttribute.isDN __ v true: The full DN is expected as the value of the
member attribute.
Indicates whether the full DN or the member login name __ v false: The member login name is expected as the
is expected as the value of the member attribute. value of the member attribute.
com.ibm.lwi.rolemanager.ldap.names.groupID Custom value:
Example: gidNumber
The name of the group ID (number) attribute of the
group object in the directory.
Example for AIX
The following example shows common settings for configuring LDAP on an IBM
Systems Director Server that runs on AIX and uses an IBM Tivoli Directory Server
or OpenLDAP server:
com.ibm.lwi.LDAPHost = host
com.ibm.lwi.LDAPPort = 389
com.ibm.lwi.LDAPAdminUser = cn=admin
com.ibm.lwi.LDAPAdminPassword = aiAzzk=}oyeo8UA/S70GKWYPaUjFAg==
com.ibm.lwi.LDAPBase = cn=aixdata
com.ibm.lwi.rolemanager.ldap.names.groupName = cn
com.ibm.lwi.rolemanager.ldap.filters.groupsByMembers = (&(memberUID={1}) \
(objectclass=posixGroup))
com.ibm.lwi.rolemanager.ldap.names.memberAttribute.isDN=false
com.ibm.lwi.searchfilter = (&(uid=%v)(objectclass=posixaccount))
com.ibm.lwi.rolemanager.ldap.filters.usergroup = (&(objectclass=posixgroup) \
(|(cn=smadmin)(cn=smmon)(cn=smuser)(cn=smmgr)))
com.ibm.lwi.rolemanager.ldap.filters.users = (objectclass=posixaccount)
com.ibm.lwi.rolemanager.ldap.names.memberAttribute = memberuid
com.ibm.lwi.rolemanager.ldap.names.loginName = uid

Remember: If you authorize any new groups, you must modify the
com.ibm.lwi.rolemanager.ldap.filters.usergroup attribute to include the new
groups. For example, you authorize a new group called foogroup. To include
foogroup, you set the com.ibm.lwi.rolemanager.ldap.filters.usergroup attribute
to the following value:
(&(objectclass=posixgroup)(|(cn=smadmin)(cn=smmon)(cn=smuser)(cn=smmgr) \
(cn=foogroup)))
Example of narrow search filters for users and groups
Some LDAP servers limit the amount of data that they return in response to a
search request. In larger LDAP environments, such as environments with
thousands of LDAP users, this limit can cause unexpected search results when you
use broad search filters. For example, an LDAP server contains 10,000 users, but
the server restricts queries to 1,000 users at a time. If you use a broad search filter
that matches the entire 10,000 users, the query returns only the first 1,000 users.
The remaining 9,000 users are not found even though they exist and match the
search filter. To ensure that your filters return the data that you expect, you can
use more narrow search filters. Narrow filters help keep your queries within the
search limits.
The following example shows more narrow search filters that might be used in
larger LDAP environments:
com.ibm.lwi.searchfilter = (&(sAMAccountName=%v)(objectcategory=user))
com.ibm.lwi.rolemanager.ldap.filters.usergroup = (|(CN=smadmin)(CN=smmgr) \
(CN=smuser)(CN=smmon))
com.ibm.lwi.rolemanager.ldap.filters.users =
(|(memberOf=CN=smadmin,DC=puzzle,DC=com)(memberOf=CN=smmgr,DC=puzzle,DC=com) \
(memberOf=CN=smuser,DC=puzzle,DC=com)(memberOf=CN=smmon,DC=puzzle,DC=com))
In this example:
v The LDAP server is an AD LDAP server.
v The domain is called puzzle.
v The usergroup filter checks that only the smadmin, smmgr, smuser, and smmon
groups exist.
v The users filter checks only for users that are members of the smadmin, smmgr,
smuser, and smmon groups.
Remember: If you authorize any new groups, you must modify the
com.ibm.lwi.rolemanager.ldap.filters.usergroup attribute and the
com.ibm.lwi.rolemanager.ldap.filters.users attribute to include the new groups.
For example, you authorize a new group called foogroup. To include foogroup, you
modify the settings as follows:
com.ibm.lwi.rolemanager.ldap.filters.usergroup =
(|(CN=smadmin)(CN=smmgr)(CN=smuser)(CN=smmon)(cn=foogroup))
com.ibm.lwi.rolemanager.ldap.filters.users =
(|(memberOf=CN=smadmin,DC=puzzle,DC=com)(memberOf=CN=smmgr,DC=puzzle,DC=com) \
(memberOf=CN=smuser,DC=puzzle,DC=com)(memberOf=CN=smmon,DC=puzzle,DC=com) \
(memberOf=CN=foogroup,DC=puzzle,DC=com))
Configuring the LDAP server

Configure the LDAP server so that IBM Systems Director can authenticate user
login requests.
To configure the LDAP server, complete the following steps:

1. Create a user account, or choose an existing user account, in the LDAP user
registry. For instructions about creating a user account, see the documentation
for your LDAP server.
Tip: To ease future troubleshooting, do not use the administrator user name
that you defined for the com.ibm.lwi.LDAPAdminUser attribute in this step.
2. Create the following user groups in the LDAP user registry to match the
groups that are predefined in IBM Systems Director:
v smadmin
v smmgr
v smmon
v smuser
Notes:
v Do not use nested groups. IBM Systems Director does not support nested
groupings of users. For example, do not assign users to group A, then assign
group A to group B, and then assign group B to the smadmin group. Nested
groups can cause User not found errors.
v After you enable the LDAP client of IBM Systems Director, IBM Systems
Director searches for these groups. The system assigns these groups the same
roles as the local groups of the same name. After the assignment, the system
no longer uses the local versions of these groups.
v Determine whether your environment includes both of the following
configurations:
– The registry is an AD LDAP user registry.
– IBM Systems Director is installed on a Linux system that uses the AD
LDAP registry.
In your environment includes both of these configurations, create the user
groups as local groups instead of default global groups.
3. Add the user as a member of one of the user groups that are defined for IBM
Systems Director at the user registry level.
4. If you must authorize more groups, complete the following steps:
a. Create the additional groups within the LDAP registry.
b. Authorize the additional groups by using the Authorize Groups wizard or
the authusergp command. For instructions, see “Authorizing IBM Systems
Director user groups” on page 665 or authusergp command.
c. Assign roles to the additional groups.
d. Add users to the additional groups.
Related reference:
chrole command
lsrole command
mkrole command
rmrole command
Editing the LDAP properties file

Rename and edit the LDAP properties file so that IBM Systems Director can
authenticate user login requests to the LDAP server.

To edit the LDAP properties file, complete the following steps:
1. Go to one of the following directories:
v Windows:
director_install\lwi\conf\overrides\
Where director_install is the installation directory of IBM Systems

Director.
v AIX or Linux:
director_install/lwi/conf/overrides

Director. The default installation directory is the /opt/ibm/director directory.
2. Rename the security.properties file to security.oldprop.
Tip: IBM Systems Director searches for any file with a .properties extension
and reads in the attributes. Thus, you must rename the security.properties
file to a different file extension.
3. Remove any other security files that have the .properties file extension.
4. Rename the security.ldap template properties file to
securityLDAP.properties.
Remember: Ensure that the file permissions for the newly renamed
securityLDAP.properties are correct. If not, change the permissions for the file
as necessary to reflect the intended permissions.
5. Open the securityLDAP.properties file in an editor.
6. Modify the contents of the securityLDAP.properties file according to your
completed worksheet. To complete the worksheet, see “Completing the LDAP
authentication worksheet” on page 640.
7. Save and exit the securityLDAP.properties file.
8. If you set the com.ibm.lwi.ldap.ssl.enable attribute to true, make sure that
the certificate that corresponds to LDAP is imported to the IBM Systems
Director truststore that is specified in the com.ibm.lwi.ldap.ssl.trustStore
attribute. To import the certificate, complete one of the following steps:
v Run the importcert command. For information about this command, see
importcert command.
v Run the IBM Key Management program. To run the program, run one of the
following commands:
a. Linux: director_install/jre/bin/ikeyman
b. Windows: director_install\jre\bin\ikeyman.exe
Where director_install is the installation directory of IBM Systems Director.
9. Encrypt the passwords and the truststore by completing the following steps:
a. Go to one of the following directories:
v Windows:
director_install\lwi\bin\

Director.
v AIX or Linux:
director_install/lwi/bin

Director. The default installation directory is the /opt/ibm/director
directory.
b. From this directory, run the following commands:
1) lwiencoder.sh -filename securityLDAP.properties -keylist
com.ibm.lwi.LDAPAdminPassword
Tip:
v If you do not encrypt this password, IBM Systems Director Server
does not start.
v If you think this password is already encrypted, run the command
anyway. The system automatically prevents you from encrypting this
password more than one time.
v Verify that the encrypted password looks similar to the following
password:
{aes:3C5SnKQL63SjkEy44Gs+vHF6nQzC+Dil1NzNvSiAzzk=}WlEqnBSFU4goMVKPszyZRg==
If the encrypted password looks different from this example,

something went wrong. Review your configuration and try again.
com.ibm.lwi.ldap.ssl.keyStorePassword
com.ibm.lwi.ldap.ssl.trustStorePassword
Validating the LDAP configuration

The final step of authenticating IBM Systems Director users that are stored in
LDAP is to validate that an LDAP user ID can log in to IBM Systems Director.
To validate the LDAP configuration for IBM Systems Director, complete the
following steps:
1. Verify the LDAP configuration by running the cfguserreg command on the
securityLDAP.properties file:
v For AIX or Linux, run the following command:
cfguserreg.sh -ldap -verify -f securityLDAP.properties
v For Windows, run the following command:
cfguserreg.bat -ldap -verify -f securityLDAP.properties
Resolve any errors and then run the command again. Repeat this step until you
resolve all of the errors.
2. Restart IBM Systems Director Server. For instructions, see Restarting IBM
3. Select an LDAP user ID that you can access to use for the login test.
4. Log in to IBM Systems Director by using the user ID and password that you
selected in the previous step.
5. If the login is successful, then LDAP authentication configuration is complete. If
the login is not successful, review the tasks in each of the configuration steps.
You can also see Handling LDAP authentication failures for troubleshooting
tips to common LDAP configuration problems.

Related reference:
cfguserreg command
Editing user properties

IBM Systems Director does not provide the capability to create, update, or delete
users or groups in a user registry regardless of where the registry resides. You can
create new users, user groups, and chassis roles from the management software
web interface or command-line interface.To manage users or groups in the user
registry, you must instead use the appropriate tool associated with the registry in
which the users or groups are stored. IBM Systems Director does, however, give
you the ability to enter and edit information for each user or group that describes
each in the context of IBM Systems Director. If the user registry has a value for the
fullname property, then the user registry will always get the higher precedence
than the IBM Systems Director database. If the fullname property in the registry is
set to empty, then you will be able to edit the fullname in the context of IBM
Systems Director. This will be displayed until the fullname property is modified
directly in the user registry.
To edit the properties that IBM Systems Director associates with each user or
group, complete the following steps:
1. In the IBM Systems Director Web interface navigation area, expand Security
and click Users.
2. Select the user or group that you want to edit.
3. Click Edit. The properties page is displayed.
4. Click Edit. The Edit Properties window is displayed.
5. Modify the properties as wanted.
6. Click OK.
Related concepts:
User authentication
Users and groups
Authorizing users to IBM Systems Director

Authorization is the process that determines whether an authenticated user or
group has the necessary privileges to access specific resources. With user
authorization, IBM Systems Director users can perform tasks on specific resources
by using IBM Systems Director Web interface. You must use IBM Systems Director
to configure the authorizations that provide access to IBM Systems Director tasks
and resources.
Using IBM Systems Director, you can create and manage the roles that control
authorization for IBM Systems Director users.

Related concepts:
Related tasks:
Managing auditing
Related reference:
User authorization
User authorization occurs when an authenticated user uses IBM Systems Director
to perform a task on a resource. The authorization mechanism compares the user
account, or the group to which the user belongs, to the role-based access control
(RBAC) settings for that user or group. If a role exists that contains the
authorizations necessary to complete that task on that specified resource, then the
task proceeds.
Users can access only the applications, tasks, and resources that their user accounts
are authorized to access. The authorities that you grant to a user determine the
console and resource information that the user can access, and the tasks that the
user can perform on those resources.
The authorization process that IBM Systems Director performs when accessing a
resource is independent of the authentication that is required to access that
resource. For example, a user might be able to authenticate to and therefore access
IBM Systems Director Web interface or another resource by using IBM Systems
Director Web interface, but to perform a task on that resource, both the task and
the resource must be authorized in the role settings that are assigned to that user
or the authorization group to which the user belongs.
After a user account is added to the applicable IBM Systems Director group to
provide access to IBM Systems Director Web interface, you can log in to IBM
Systems Director Web interface as an administrator and configure the authorization
policies and rules for IBM Systems Director tasks and resources for that user.
Related concepts:
Users and groups
Roles
Mappings
Related tasks:
Related reference:
Roles
You can assign roles to IBM Systems Director users to control their access to
resources and limit the tasks that they can perform on those resources. The
authorities that you configure for a role determine the level of access granted to
each user who is assigned to that role. All users or groups of users that access IBM
Systems Director must have a user role assignment.

The IBM Systems Director Server uses a role-based access control (RBAC) service
with which an administrator can create custom sets of permissions, known as roles,
and assign them to individual users or groups. A set of task, command-line
interface (CLI), and application permissions that is applied to one or more
resources defines an authorization role. Each role can be applied to many users,
and each user can have many roles. Regulating user roles is an effective way to
control security for your system as it enables you to control access to every task
and CLI command.
Note: By default, the only user ID that is assigned to the SMAdministrator role
(the only one that can take any action right after installation) is the user ID that
was used to install IBM Systems Director. Even if you have other administrators
defined on the management server, a role is not assigned to them and they are
unable to administer IBM Systems Director. They will instead receive a message
telling them to contact their system administrator. To ensure that you are using the
correct user ID, before logging on to the IBM Systems Director Web interface,
ensure that you can use that same user ID and password to successfully log on to
the operating system on the management server.
To allow users access to the IBM Systems Director Web interface, each user must
be assigned to a role. These user roles define the types of tasks that users or
groups can perform. To be assigned to a role, each user or group of users must
have a valid user ID or group ID in the user registry on the management server.
Both individual users and a group of users can be assigned to a role. All users in a
group are assigned the role of the group. If a user is assigned to one role as an
individual and a different role as a member of a group, the user has access to the
functions of the role that has greater access.
Role-based access control is functionality that was not available in versions of IBM
Systems Director prior to 6.1. In those versions, you could only edit the access
levels on each individual user or group, or you could modify the default access.
IBM Systems Director 6.1 and later provide reusable roles that you can assign more
than once and use to build other roles. IBM Systems Director 6.1 and 6.2 also
provide instance-based authorization. This gives you the ability to define, at a
more granular level than before, which tasks apply to which groups in a system.
The following system-defined user roles are preconfigured in IBM Systems

Director.
Note: The hierarchical order of the roles in this list is such that the
SMAdministrator role has the highest authority and the SMUser role has the
lowest authority. Roles with higher authority are permitted to run all operations
that roles with lower authority are permitted to run. For example, if the execution
of an operation is permitted for SMUser, then all the other roles with higher
privileges are also permitted to run the operation.
SMAdministrator (Administrator role)
The SMAdministrator role has full authority to perform all tasks and
functions, and has full control over permissions. A user assigned to this
role can perform all tasks (including security administration, product
installation, and configuration) with any resource.
Important: If you assign this role to a user, the user can modify or delete
all system-level resources and resources for all other users, including
operating-system and user files and processes. Before assigning this role to
a user, be sure that the user requires this level of authority.

SMManager (Manager role)
The SMManager role can perform management operations, which are a
subset of the functions that a member of the SMAdministrator role can
perform. Typically, system administration, system health management, and
system configuration tasks are available. This role cannot perform security
administration or security configuration tasks, but it has full access to all of
the IBM Systems Director functions included within a functional manager
or feature. The list of accessible functions include those within the status
manager and update manager.
SMMonitor (Monitor role)
The SMMonitor role can access those administrative functions that provide
read-only access, such as monitoring, notification, and status. With this
role, a user can complete such tasks as monitoring a process, viewing and
collecting inventory, and viewing hardware status. This role cannot, for
example, create virtual servers or reconfigure the IBM BladeCenter.
SMUser (User role)
The SMUser role includes any authenticated user and includes the ability
to perform only basic operations such as viewing resources and properties.
GroupRead (Group role)
The GroupRead role has a single permission, known as group read, that
defines the groups that are visible to each user. The administrator that
assigns this role to a user can assign the groups that the user can view. The
user then has access to see the groups but not necessarily to see the group
contents. For example, in a dynamic group, the visibility to users can vary
based on the assignments to which a user has read-only access.
These default user roles correspond directly with the groups that IBM Systems
Director installs at the operating system level. You cannot delete these roles, nor
can you modify the permissions associated with them. However, you can add
users and other groups to the system defined roles as needed, and you also can
copy the system defined roles or create new ones for your business needs.
Assigned role
This is the role which is directly assigned to user or group.
Implied role
This is the role acquired from the group to which the user has the
membership. In the case of nested groups, the group's implied role is a role
acquired from the parent group for which group has the membership.
For example, if the SMUser group has an assigned role of {'SMMonitor'
with Group By Access Resources}, all the users who are members of the
SMUser group will get this role as an implied role.
For information on viewing and editing the tasks available to each role, see
“Managing roles” on page 662. Tasks that require a role with greater permissions
than those of the role that you have will not appear in the IBM Systems Director
Web interface navigation area or on any of the pages.
Permissions and roles required to run smcli commands

A user ID must be authorized with certain permissions and roles to run the smcli
commands.
Important: A newly created user must run the smcli lsuser command before
running any other command.

Note: A user ID must have the AllPermission permission to run supported IBM
Director commands.
System commands
Command Required permission Predefined role
accesssys SecurityPermission SMAdministrator
chsys GeneralPermission SMAdministrator
lssys GeneralPermission SMUser
pingsys GeneralPermission SMAdministrator
rmsys GeneralPermission SMAdministrator
rpower PowerOnOffPermission SMAdministrator
Group commands
chgp GeneralPermission SMManager
lsgp GeneralPermission SMUser
mkgp GeneralPermission SMManager
rmgp GeneralPermission SMManager
Discovery and inventory commands

collectinv InventoryPermission SMAdministrator
discover InventoryPermission SMAdministrator
lsinv InventoryPermission SMMonitor
Configuration plan and template commands

lscfgplan SystemConfigurationPermission SMMonitor
lscfgtmpl SystemConfigurationPermission SMMonitor
mkcfgplan SystemConfigurationPermission SMManager
mkcfgtmpl SystemConfigurationPermission SMManager
rmcfgplan SystemConfigurationPermission SMManager
rmcfgtmpl SystemConfigurationPermission SMManager
Status commands
chled SystemStatusAndHealthPermission SMManager
lsled SystemStatusAndHealthPermission SMMonitor
lsstatus SystemStatusAndHealthPermission SMMonitor

Resource monitor commands
chresmonthresh SystemStatusAndHealthPermission SMManager
lsresmon SystemStatusAndHealthPermission SMMonitor
lsresmonrec SystemStatusAndHealthPermission SMMonitor
lsresmonthresh SystemStatusAndHealthPermission SMMonitor
mkresmonrec SystemStatusAndHealthPermission SMManager
mkresmonthresh SystemStatusAndHealthPermission SMManager
rmresmonrec SystemStatusAndHealthPermission SMManager
rmresmonthresh SystemStatusAndHealthPermission SMManager
runresmon SystemStatusAndHealthPermission SMManager
stopresmonrec SystemStatusAndHealthPermission SMManager
Process monitor commands

lsps SystemStatusAndHealthPermission SMMonitor
mkpmtask SystemStatusAndHealthPermission SMManager
rmpmtask SystemStatusAndHealthPermission SMManager
Event automation plan and event commands

chevtautopln AutomationPermission SMAdministrator
evtacthist AutomationPermission SMManager
evtautopln AutomationPermission SMAdministrator
evtlog AutomationPermission SMManager
lsevtact AutomationPermission SMMonitor
lsevtacthist AutomationPermission SMMonitor
lsevtautopln AutomationPermission SMMonitor
lsevtfltr AutomationPermission SMMonitor
lsevtlog AutomationPermission SMMonitor
lsevttype AutomationPermission SMMonitor
mkevtactemail AutomationPermission SMAdministrator
mkevtactstpgm AutomationPermission SMAdministrator
mkevtactsttask AutomationPermission SMAdministrator
mkevtautopln AutomationPermission SMAdministrator
rmevtact AutomationPermission SMAdministrator
rmevtautopln AutomationPermission SMAdministrator
rmevtfltr AutomationPermission SMAdministrator
rmevtlog AutomationPermission SMAdministrator
testevtact AutomationPermission SMAdministrator

Task and scheduled job commands
lsjob TaskManagementPermission SMUser
lsjobhistory TaskManagementPermission SMUser
lstask TaskManagementPermission SMUser
rmjob TaskManagementPermission SMAdministrator
rmjobhistory TaskManagementPermission SMAdministrator
runjob TaskManagementPermission SMUser
runtask TaskManagementPermission SMUser
Update commands
checkupd ReleaseManagementPermission SMMonitor
cleanupd ReleaseManagementPermission SMManager
importupd ReleaseManagementPermission SMManager
installupd ReleaseManagementPermission SMManager
lsupd ReleaseManagementPermission SMMonitor
uninstallupd ReleaseManagementPermission SMManager
Security commands
authusergp SecurityPermission SMAdministrator
chrole SecurityPermission SMAdministrator
chuser SecurityPermission SMAdministrator
chusergp SecurityPermission SMAdministrator
lsperm SecurityPermission SMAdministrator
lsrole SecurityPermission SMAdministrator
lsuser SecurityPermission SMAdministrator
lsusergp SecurityPermission SMAdministrator
mkrole SecurityPermission SMAdministrator
rmrole SecurityPermission SMAdministrator
rmusergp SecurityPermission SMAdministrator
SNMP devices
get SystemStatusAndHealthPermission SMMonitor
getbulk SystemStatusAndHealthPermission SMMonitor
getnext SystemStatusAndHealthPermission SMMonitor
inform SystemStatusAndHealthPermission SMManager
set SystemStatusAndHealthPermission SMManager

trap SystemStatusAndHealthPermission SMManager
walk SystemStatusAndHealthPermission SMMonitor
Storage commands
chnshost SystemConfigurationPermission SMManager
chnssys SystemConfigurationPermission SMManager
chnspath SystemConfigurationPermission SMManager
chnsvol SystemConfigurationPermission SMManager
lsnshost SystemConfigurationPermission SMMonitor
lsnspath SystemConfigurationPermission SMMonitor
lsnssys SystemConfigurationPermission SMMonitor
lsnsvol SystemConfigurationPermission SMMonitor
mknspath SystemConfigurationPermission SMManager
mknsvol SystemConfigurationPermission SMManager
rmnspath SystemConfigurationPermission SMManager
rmnsvol SystemConfigurationPermission SMManager
Virtualization commands
chvrtauth SystemConfigurationPermission SMAdministrator
chvrthost SystemConfigurationPermission SMAdministrator
chvs SystemConfigurationPermission SMAdministrator
chvsmauth SystemConfigurationPermission SMAdministrator
chvsmhost SystemConfigurationPermission SMAdministrator
chvsmvs SystemConfigurationPermission SMAdministrator
lsvrtsys SystemConfigurationPermission SMMonitor
lsvsm SystemConfigurationPermission SMMonitor
mkvs SystemConfigurationPermission SMAdministrator
mkvsmvs SystemConfigurationPermission SMAdministrator
Authorizing users to manage resources

To log in to IBM Systems Director Web interface and manage the resources that are
discovered by IBM Systems Director, a user must have a user account that is
associated with a role that has the appropriate authority.
The following steps are required to authorize an IBM Systems Director user to
manage resources:
1. If the user account that is needed does not exist, create it on the operating
system of the system that you want to manage or on the Lightweight Directory
Access Protocol (LDAP) server.

2. Log in to IBM Systems Director as a SMAdministrator.
3. Assign an appropriate role to the user account or group to which the user
account belongs and associate it with the resources that you want the account
to manage. You can use any of the existing initial role groups (smadmin,
smmgr, smmon, smuser) or you can create a role that includes the privileges
necessary to access the appropriate resource.
Note: Assigning a role other than smadmin, which is done with the operating
system, occurs within IBM Systems Director Web interface.
Related concepts:
Users and groups
User authorization
Roles
Related tasks:
Assigning a role to a user or user group
Assigning a role to a user or user group

The roles that are assigned to a user or user group determine the tasks that the
user has permission to access. From the Users page, you can assign one or more
roles to a user or user group. When you assign a role, you also associate specific
resources to which the role will apply for the selected user.
Before you can assign a role to a user, each user or group of users must have a
valid user ID or group ID in the local operating-system user registry on the
management server. Also, you must make sure that the role that you want to
assign to a user already exists. If it does not, you can create a new role from the
Roles page.
If you want to associate a role and user with only one resource group, you can
create a group that contains all the resources that you will assign to a specific user
and then pick that group when you work with the Assign Role wizard.
CAUTION:
When you assign a role or to a user or user group, the user or user group has the
permissions and authorization associated with that role. For example, if you
assign the role SMAdministrator to a user or user group, the user or user group
has SMAdministrator permissions, which includes full authority to all tasks and
commands, including security administration, product installation, and
configuration.
To assign a role to a user or group, complete the following steps:

and click Users and Groups.
2. From the Users tab, select the user or group to which you want to assign a role.
3. Click Assign Role. The Welcome page for the Assign Role wizard opens.
4. Click Next. The wizard lists the roles that have been created.
5. Select the role that you want to assign.
6. Click Next.
7. Select the resource groups that you want to associate with the role and the user.

Note: Selecting a parent group does not automatically assign access its
children.
9. Click Finish.
Related concepts:
Roles
Users and groups
User authorization
Copying a role to another user

The roles that are created in IBM Systems Director to control access to tasks and
resources can be applied to one or more users or groups. Use the Users page to
copy the task and resource assignments in an existing role from one user or group
to another user or group.
When you copy a role from one user to another, the task and resource assignments
in an existing role are copied and assigned to the new user in one step. As a result,
both the task permissions and the associated resources for the selected user are
copied to the new user.
Note: The Copy Role to User... action does not result in the creation of a new role
that matches the selected role. Instead, the task and resource assignments in the
selected role are copied to the user or group. In other words, it is the task and
resource assignments in the selected role, not the role itself, that are copied to the
user or group. If you instead want to copy a role, you can do so using the Roles
page.
To copy a role to another user, complete the following steps:

and click Users.
2. On the Users page, select the user that has the role that you want to copy, and
then click Copy Role to User.... The Copy Role to User page opens.
3. In the Copy to list, select the user to whom you want to copy the role.
4. In the Roles list box, select the roles that you want to copy.
Note: Both the task permissions and the associated resources for the selected
user are copied to the new user.
5. Click OK.
Related concepts:
Roles
Users and groups
User authorization
Creating a role
With the Roles page, you can create new roles on your system.
IBM Systems Director Server uses a role-based access control (RBAC) service with
which an administrator can create a set of task permissions that can be applied to
one or more resources. The permissions that are configured for a role determine

the resources that a user can access and what tasks the user can perform on those
resources. Each role can be applied to many users or groups, and each user can
have many roles.
To create a role, complete the following steps:

and click Roles.
2. On the Roles page, click Create. The Create Role wizard Welcome page is
displayed.
3. Click Next. The Name page is displayed.
4. In the Name field, type a name for the role that you want to create.
5. In the Description field, type an optional brief description for the role.
6. Click Next. The Permissions page is displayed.
7. In the Available permissions field, select a permission that you want to add
to the user role and then click Add. The selected permission is added to the
Selected permissions field. Continue adding permissions until you have
identified all permissions required for the role.
Note: The permissions are ordered and grouped under specific categories,
such as inventory and security, and subcategories within those categories.
Under each category, the permissions are sorted alphabetically by permission
type. The task permissions are first, followed by the cli permissions. The
different types of permissions are designated by different icons. You can either
select a category or subcategory name, which adds all the contained
permissions, or you can drill down to select and add an individual
permission.
8. Optional: To remove a permission from the role, select a permission in the
Selected permissions field and then click Remove. The selected permission is
added back to the Available permissions field.
10. Click Finish.
After you create a role, use the Assign Role wizard on the Users page to create role
and resource assignments for your users.
Related concepts:
Roles
Users and groups
User authorization
Removing a role from a user

You can remove an assigned role from a user.
Restriction:
You cannot remove an implied role from a user. You can only remove assigned
roles, which are directly assigned to user. You cannot remove implied roles, which
are acquired from the group to which the user has the membership.
To remove an assigned role from a user, complete the following steps:


2. From the Users tab, select the user from which you want to remove a role.
3. From the Roles tab, select the role you want to remove from the user.
4. Click Remove.
5. Click OK.
Removing a role from a group

You can remove a role from a user-created group on the properties page for the
group. For the system-defined groups - smadmin, smmgr, smmon, smuser - you
must use the Assign Role wizard to remove a role.
Restriction:
You cannot remove a system-defined user role (SMAdministrator, SMManager,

SMMonitor, SMUser) from its respective system-defined user group (smadmin,
smmgr, smmon, smuser). For example, you can’t remove the SMAdministrator
from the smadmin group.
To remove a role from a user-created group:

2. From the Group tab, select the group from which you want to remove a role.
3. From the Roles tab, select the role you want to remove from the group.
4. Click Remove.
5. Click OK.
To remove a role from a system-defined group (smadmin, smmgr, smmon,

smuser):
2. From the Groups tab, select the group from which you want to remove a role.
3. Click Assign Role. The Welcome page for the Assign Role wizard opens.
4. Click Next. The wizard lists the roles that have been created.
5. Select the role that you want to remove.
6. Click Remove.
8. Click Finish.
Managing roles
Use IBM Systems Director to work with roles and assign individual users and user
groups to those roles. From the Roles page, you can view, copy, edit, or delete a
role.
To view, copy, edit, or delete a role, the role must already exist. You can also use
this page to create a new role that you can then manage. See “Creating a role” for
instructions.
To view, copy, edit, or delete a role, complete the following steps:

and click Roles.
2. On the Roles page, select one of the following actions.

Table 51. Role actions
View details about an existing role 1. Select the role that you want to view.
2. Click View. The View page is displayed.
3. View the following details about the role:
v Name
v Description
v Permissions
4. Click OK.
Notes:
v When you view a role, you will see one of
two icons that designate the type of
permissions that the role has. One icon
indicates that the role applies to tasks in
the IBM Systems Director Web interface,
and the other indicates that it applies to
cli commands.
v To view a comprehensive list of role
permissions, use the lsrole command.
Copy an existing role 1. Select the role that you want to copy.
2. Click Create like. The Create Role Like
wizard is displayed. The role name
defaults to Copy of (original role name),
but the rest of the fields are populated
with the same entries and selections as is
in the original role.
3. Edit the fields as needed.
4. Click Finish. The new role based on the
original role will appear in the table on
the Roles page.
Edit an existing role Note: You cannot edit the roles that are
shipped with IBM Systems Director, which
are designated by the type of System
Defined.
1. Select the role that you want to edit.
2. Click Edit. The Create Role wizard is
displayed but with the fields already
filled out. You can select only certain
fields to edit.
3. Edit the role properties as needed,
wizard.
4. Click Finish.
Delete an existing role Note: You cannot delete the roles that are
shipped with IBM Systems Director, which
are designated by the type of System
Defined.
1. Select the role that you want to delete.
2. Click Delete. A confirmation message is
displayed.
3. Click Delete in the confirmation message
box to confirm the deletion or click
Cancel to retain the selected role. The
selected role is deleted and is no longer
displayed in the table on the Roles page.

Related concepts:
Roles
Users and groups
User authorization
Related tasks:
Creating a role
Ending the session for another user

You can choose to end the session for another active user if you have sufficient
authority to do so.
To end the session of another active user:

and click Users.
2. Right-click the user for whom the session is to be ended.
3. Click End Session. The End Session confirmation dialog is displayed. If the
user is logged in more than once, the list of sessions is displayed; select which
session to end. You can select multiple sessions.
4. In the End Session confirmation dialog, click End Session. The selected user is
logged out and must log in again.
Changing the time interval between consecutive

resynchronize calls
The default time interval between the two subsequent resynchronize calls is two
seconds (2000 ms). If you have hundreds or thousands of users and groups in the
user registry, the resynchronize call can take longer to complete. This topic
describes how to change the default time interval so the resynchronize call does
not occur as frequently.
In the IBM Systems Director's authorization service, the resynchronization of

authorized users and groups is carried out with the corresponding user registry,
such as the local operating system or LDAP. This resynchronization is called at
several places while using IBM Systems Director, including logging in to the server
and when loading the Security > Users page.
To change the time interval, do the following:

1. Edit the following file: ..\Director\lwi\conf\overrides\
USMIKernel.properties
2. Add the perf.security.resync.interval.delta property to the
USMIKernel.properties file and specify your desired time interval in
milliseconds. For example, if you want the time interval to be 30 seconds, add
the following line to the file:
perf.security.resync.interval.delta=30000
3. Save your changes to the USMIKernel.properties file.
4. Restart the server.
Managing user groups in IBM Systems Director

Use IBM Systems Director to manage user group access to the IBM Systems
Director Server. Authorization for existing user groups can be added or removed.

Related concepts:
Roles
Users and groups
User authorization
Authorizing IBM Systems Director user groups

IBM Systems Director can authorize user groups to access the IBM Systems
Director Server.
To authorize an existing user group to the IBM Systems Director Server, complete
to Security > Users. Authorized user groups are displayed in the list.
2. To authorize another user group, click Authorize Groups. The Authorize User
Groups wizard opens.
3. If the Welcome page is displayed, click Next. The User Groups page is
displayed.
4. Select or type the user groups that you want to authorize. You can select
multiple user groups from the list, type user group names in the User groups
field, or both.
Tip: A maximum of 10 user group names are displayed in the list. If user
groups are not listed, type the names in User groups. Separate the names by
commas.
6. Click Finish to authorize the specified user groups.
After user groups are authorized to the IBM Systems Director Server, you can
assign roles and users to them.
Related concepts:
User authorization
Roles
Related tasks:
Removing user group authorization
Related reference:
authusergp
Removing IBM Systems Director user group authorization

IBM Systems Director can remove user-group access to the IBM Systems Director
Server.
To remove a user group's access to the IBM Systems Director Server, complete the
following steps:
to Security > Users. Existing user groups are displayed in the list.
2. In the table, select the user group that you want to remove.
Note: The following user groups cannot be removed: smadmin, smmgr,

smmon, and smuser.
3. Click Remove Group Authorization or right-click the group name and select
Remove Group Authorization. A confirmation message is displayed.

4. Click OK to remove the user group's access to the IBM Systems Director Server.
Users assigned to the selected user group can no longer access the IBM Systems
Director Server. This action does not delete the user group; it only removes the
group's authorization.
Related tasks:
Authorizing user groups
Related reference:
rmusergp
Managing credentials in IBM Systems Director

IBM Systems Director uses credentials to implement single sign-on authentication.
Various forms of credentials are supported.
Single sign-on (SSO) is an authentication process in which a user can access more
than one system or application by entering a single user ID and password. It is
used to automate access to multiple resources by requiring a user to authenticate
only once. To implement single sign-on authentication, the IBM Systems Director
Server maps IBM Systems Director Web interface user credentials to the user
credentials needed for authenticating to the target managed system. These
credentials are saved in registries, which enables Web interface users who are
managing remote systems over various security domains or realms to authenticate
to and manage these remote systems and the resources hosted on them.
When credentials are configured in IBM Systems Director, users are not required to
type the user ID and password for the target system or resource each time that
they or a task access it. IBM Systems Director Server automatically logs in as
needed by retrieving the necessary credentials. You can view those systems for
which users do not automatically have access on the IBM Systems Director Web
interface Home page.
With IBM Systems Director, you can manage shared and targeted credentials:
Shared credentials
Shared credentials are those credentials that exist in an authentication
registry that is not specific to an access point. This enables the credentials
to be reused to access multiple console access points and systems. These
credentials must be of type user ID/password. After the credentials are
configured, the IBM Systems Director Server can use them to authenticate
to user interfaces and advanced system-management functions that are
hosted on the selected system.
Shared credentials are created on the local operating system, the domain
controller, or LDAP, and are then mapped to other credentials if necessary.
In IBM Systems Director, use the following pages to manage shared
credentials:
v To manually manage shared credentials and credential mappings for a
target managed system that you choose, use Security > Credentials.
v To manage single sign-on shared credentials from the selected system,
use Resource Explorer > All systems > (right-click a system) > Security
> Configure Single Sign-On Credentials.
Targeted credentials
Targeted credentials are each assigned to only one remote-service agent

access point and are located in an authentication registry that is specific to
that access point. These credentials cannot be reused to access other agent
access points. After the credentials are configured, the IBM Systems
Director Server can use them to manage the selected system.
In IBM Systems Director, use the following pages to manage targeted
credentials:
v To access general system-management capabilities for the selected
system, use Resource Explorer > All systems > (right-click a system) >
Security > Configure Access.
v To access advanced system-management capabilities for the selected
system, use Resource Explorer > All systems > (right-click a system) >
Security > Configure System Credentials.
Related tasks:
Managing mappings
Managing auditing
Related reference:
Managing shared credentials

Use IBM Systems Director to configure the shared credentials that are used to log
in to and manage console access points that are hosted on a managed system.
Shared credentials are those credentials that exist in an authentication registry that
is not specific to an access point. This enables the credentials to be reused to access
multiple console access points. These credentials must be of type user
ID/password. After the credentials are configured, the IBM Systems Director
Server can use them to launch user interfaces that are hosted on the selected
system.
Shared credentials are created on the local operating system, the domain controller,
or LDAP, and are then mapped to other credentials if necessary. To manage shared
credentials and credential mappings, use Security > Credentials. The Credential
wizard enables you to choose the target system for which to create the credentials.
Alternatively, you can configure single sign-on shared credentials for a selected
system by using the Create and Edit Single Sign-On Credentials wizard. See
“Managing single sign-on credentials.”
Related tasks:
Managing mappings
Creating shared credentials

Use the Credentials page to create shared credentials for a target managed system
that you specify in the Credential wizard.
To create a set of shared user ID / password credentials for a console access point
on a target system, complete the following steps:
and click Credentials.
2. On the Credentials page, click Create. The Credential wizard opens.

3. If the Welcome page is displayed, click Next. The Credential Details page is
displayed.
4. From the Authentication Registry Type list, select the type of authentication
registry that you want to create. The three authentication registry types are as
follows:
Local OS
Authenticates user login requests with the local operating system of the
target system. The target system must have a corresponding user
account in the operating-system registry.
LDAP Authenticates user login requests with a Lightweight Directory Access
Protocol (LDAP) server. Ensure that the LDAP server is configured in
your environment and available to the target system.
Domain
Authenticates user login requests with a specific domain server. Ensure
that the domain server is configured in your environment and available
to the target system.
5. From the Target system list, select the name of the target system. If your target
system does not appear in the list, click Browse to search for it.
6. Enter the appropriate user ID and password for the system. If you are creating
a credential for a resource that has defined a specific user ID that must be used
when authenticating, you cannot change the value in the User ID field.
8. Click Finish. The credentials are automatically used to authenticate to the
specified system.
For information about how to map a user's credentials in one user registry to
another user's credentials in another user registry, see “Managing mappings”.
Related concepts:
Related tasks:
Managing mappings
Editing shared credentials
Deleting shared credentials
Learn more about targets that define specific user IDs

For some systems, a specific user ID is required to access the system. When the
system requires the use of a specified user ID, the user ID fields on the Request
Access page are fixed. You cannot change the user ID. Instead, you must enter the
password for that user ID.
Editing shared credentials

Use the Credentials page to edit shared credentials.
With IBM Systems Director, you can edit existing shared credentials
To edit a set of shared user ID / password credentials, complete the following

steps:
2. On the Credentials page, select the shared credential that you want to edit.
3. Click Edit. The Edit Credential wizard opens.

4. If the Welcome page is displayed, click Next. The Credential Details page is
displayed.
5. Change the details that are available for changing and verify the password for
the credential.
7. Click Finish.
For information about how to map a user's credentials in one user registry to
another user's credentials in another user registry, see “Managing mappings”.
Related concepts:
Related tasks:
Managing mappings

Use the Credentials page to delete shared credentials that are no longer needed.
If you have created any automated tasks in IBM Systems Director, ensure that you
check the systems that are the targets of those tasks and the credentials that are
used to log in to those systems. Some tasks might be configured to use a set of
credentials to accomplish the procedures in the task. Deleting the set of credentials
that are used by one of these automated tasks will prevent the task from accessing
targeted systems that are secured.
Note: You will not receive a warning when deleting a credential that is associated
with an automated task, and the task will no longer be able to access the system.
To delete a set of shared credentials, complete the following steps:

2. On the Credentials page, select the credentials that you want to delete.
3. Click Delete. A confirmation message is displayed.
4. Click OK.
Related concepts:
Related tasks:

Use IBM Systems Director to manage single sign-on shared credentials for the
selected system. These credentials are mapped from specific user credentials on
that system to IBM Systems Director Web interface users.
Ensure that you have the correct authorization to access the resource and its access
points.
Like other shared credentials, single sign-on credentials are those credentials that
exist in an authentication registry that is not specific to an access point. This
enables the credentials to be reused to access multiple console access points and
systems. These credentials must be of type user ID/password. After the credentials

are configured, the IBM Systems Director Server can use them to launch user
interfaces that are hosted on the selected system.
Creating single sign-on credentials:
Use the Create and Edit Single Sign-On Credentials wizard to create single sign-on
shared credentials for the selected system.
Single sign-on credentials map user credentials on the selected system to specified
IBM Systems Director Web interface users. To create a single sign-on credential for
a console access point on the selected system, complete the following steps:
Explorer > group name > system name.
2. Click Actions > Security > Configure Single Sign-On Credentials. The
Configure Single Sign-On Credentials page is displayed.
3. Click a remote-service console access point. The credentials associated with
that access point are listed.
4. Click Create. The Create and Edit Single Sign-On Credentials wizard is
displayed.
Notes:
v If the Create button is disabled, all credential mappings that you have the
authority to create have been created for the configured authentication
registry on the selected system. A credential mapping can be created only
for those Web interface users who have logged in to IBM Systems Director
at least once. Existing credential mappings can still be edited or deleted.
v If the Create button is unavailable, the selected console access point is on
the IBM Systems Director Server. Single sign-on credentials for these access
points can only be displayed. You cannot create or edit these credentials
because they are automatically created when Web interface users log in to
registry that you want to create.
Note: If an authentication registry has already been configured for the

selected console access point, the value for the authentication registry type
cannot be changed. It is set to the previously configured authentication
registry type for the access point.
The three authentication registry types are as follows:
Local OS
Authenticates user login requests with the local operating system of
the target system. The target system must have a corresponding user
Domain
Authenticates user login requests with a specific domain server.
Ensure that the domain server is configured in your environment and
available to the target system.

a credential for a resource that has defined a specific user ID that must be
used when authenticating, you cannot change the value in the User ID field.
7. Click Next. The “Assign to IBM Systems Director User” page is displayed.
Note: This page lists only Web interface users who have logged in to IBM
Systems Director. These users must log in at least once before a credential
mapping can be created.
8. Select the IBM Systems Director Web interface user for whom the single
sign-on credential is being created. You can use the current user or choose
another user from the table.
Remember: Only one mapping can be created for each of the users on this
page.
selected console access point on the system.
Repeat the credential creation process for other console access points you plan to
access.
Related concepts:
Related tasks:
Configuring the authentication registry
Editing single sign-on credentials
Deleting single sign-on credentials
Editing single sign-on credentials:
Use the Create and Edit Single Sign-On Credentials wizard to edit single sign-on
shared credentials.
To edit a single sign-on credential, complete the following steps:

3. Click a remote-service console access point. The credentials associated with that
access point for the configured authentication registry are listed.
4. Select the credential that you want to edit.
5. Click Edit.
Note: If the Edit button is unavailable, the selected console access point is on
the IBM Systems Director Server. Single sign-on credentials for these access
points can only be displayed. You cannot create or edit these credentials
because they are automatically created when Web interface users log in to IBM
Systems Director.
The Create and Edit Single Sign-On Credentials wizard is displayed.
6. If the Welcome page is displayed, click Next. The Create Single Sign-On
Credential page is displayed.
7. Change the details that are available for changing.
9. Click Finish.
Related concepts:
Related tasks:
Deleting single sign-on credentials
Deleting single sign-on credentials:
Use the Configure Single Sign-On Credentials page to delete single sign-on shared
credentials that are no longer needed.
with an automated tasks, and the task will no longer be able to access the system.
To delete a single sign-on credential, complete the following steps:

3. Click a console access point. The credentials associated with that access point
are listed.
4. Select the credential that you want to delete.
6. Click OK.
Related concepts:
Related tasks:
Managing mappings
Use IBM Systems Director to map a user's credentials in one user registry to
another user's credentials in another user registry.
Mappings represent associations between a source credential in one security

domain and a target credential in another domain. For example, you can map
credentials from your local registry to various other types of authentication
registries, such as Lightweight Directory Access Protocol (LDAP).
Mappings
Mappings represent associations between a source credential in one security
domain and a target credential in another domain. For example, you can map
credentials from your local registry to various other types of authentication
registries, such as Lightweight Directory Access Protocol (LDAP).

Depending on the values used in the mapping and how the mapping is associated
with an access point, the following three types of mapping associations are
possible:
One-to-one mapping
This most basic type of mapping is used when a specific user wants to
request the services of an access point. A source credential and a target
credential are specified, and the target credential must be valid in the same
registry that the access point uses for validation. This mapping can be used
by any access point that happens to validate to the same registry.
One-to-one mapping with access point association
Use one-to-one mapping with access point association if you want to
restrict a mapping to a particular access point.
As with one-to-one mapping, a source credential and a target credential are
specified. The target credential must still be valid in the registry the access
point uses for validation. However, the mapping is associated with a
specific access point.
Many-to-one mapping with access point association
Use many-to-one mapping with access point association if you want to
have a mapping with which any user can request the services of a
particular access point. This method avoids the need to create many
one-to-one mappings when all users must use the same target credential
for an access point.
Note: Because this type of mapping can enable broad access, IBM Systems
Director requires that you associate this type of mapping with an access
point.
Creating mappings
Use the Credentials mapping page to map one credential to another to create a
one-to-one credential mapping.
To create a one-to-one mapping between two credentials, complete the following

steps:
2. On the Credentials page, select the target credential that you want to map.
3. Click Actions > Mapping.
4. On the Mapping page, click Create. The Credential Mapping wizard opens.
5. If the Welcome page is displayed, click Next. The Source credential page is
displayed.
6. Choose whether you would like to use the current console credential or a
credential that was previously created and is displayed in the credential table.
If you choose to select a credential from the table, select it.
Note: A credential mapping can be created only for those Web interface users
who have logged in to IBM Systems Director at least once. Existing credential
mappings can still be edited or deleted.
8. Click Finish.

Related concepts:
Mappings
Related tasks:
Editing mappings
Deleting mappings
Editing mappings
Use the Credentials mapping page to edit an existing one-to-one credential
mapping.
To edit a one-to-one credential mapping, complete the following steps:

2. On the Credentials page, select the target credential that you want to edit.
4. Select the mapping that you want to edit.
5. Click Edit. The Create Credential Mapping wizard is displayed.
6. If the Welcome page is displayed, click Next. The Source credential page is
displayed.
7. Select whether to use the current console credential or a credential that was
previously created and is displayed in the credential table.
8. If you choose to select a credential from the table, select it.
10. Click Finish.
Related concepts:
Mappings
Related tasks:
Deleting mappings
Creating mappings
Deleting mappings
Use the Credentials mapping page to delete one-to-one credential mappings that
are no longer needed.
To delete a one-to-one mapping between credentials, complete the following steps:

2. On the Credentials page, select the credential that contains the mapping that
you want to delete.
4. On the Mapping page, select the mapping that you want to delete.
6. Click OK.

Related concepts:
Mappings
Related tasks:
Creating mappings
Editing mappings

Use the Configure Authentication Registry wizard to configure the authentication
registry that the selected console access point on the managed system uses to
authenticate credentials. The authentication registry enables IBM Systems Director
to use the credentials and credential mappings that were configured through the
credentials or the configure single sign-on credentials tasks with other selected
console access points or managed systems.
To configure the authentication registry, complete the following steps:

3. Select a CONSOLE access type and then click Configure Authentication
Registry. The Configure Authentication Registry wizard is displayed.
4. If the Welcome page is displayed, click Next. The Authentication Registry Type
page is displayed.
registry that you want to identify. The three authentication registry types are as
follows:
Local OS
Authenticates user login requests with the local operating system of the
target system. The target system must have a corresponding user
Domain
Authenticates user login requests with a specific domain server. Ensure
that the domain server is configured in your environment and available
to the target system.
6. If you chose LDAP or Domain and previously used the credentials or
configure access tasks to identify LDAP or domain authentication registries,
you can select the one you want to use from the list. Alternatively, select Use
the entry from below in the list, and then type the IP address or host name of
the LDAP server or domain.
8. Click Finish.

Related tasks:
Managing targeted credentials

Use IBM Systems Director to configure the targeted credentials that are used to log
in to and access remote-service agent access points that are managed by IBM
Systems Director.
Targeted credentials are each assigned to only one remote-service agent access
point and are located in an authentication registry that is specific to that access
point. These credentials cannot be reused to access other agent access points. After
the credentials are configured, the IBM Systems Director Server can use them to
manage the selected system.
To access general system-management capabilities for the selected system, use

Resource Explorer > All systems > (right-click a system) > Security > Configure
Access.
Optionally, you can access advanced system-management capabilities for the

selected system by configuring system credentials. See “Managing system
credentials”.
Related tasks:
Managing system credentials
Creating targeted credentials

Use the Configure Credential wizard to create targeted credentials.
With IBM Systems Director, you can create targeted credentials that are specific to
an agent access point on a resource.
Note: Certain types of agent access points (for example, CAS or IPC) do not
support this credential creation process. Instead, the use of the Request Access task
is all that is required to obtain access to all the agent access points on the resource
when these types of access points are present. The Request Access task creates the
necessary credentials and mappings, but they cannot be viewed or managed. If
you need to create or manage credentials for other agent access points even when
access points such as CAS or IPC are present, you can follow this process, but the
overall system access will be determined by the Request Access request.
To create a set of targeted credentials, complete the following steps:

2. Click Actions > Security > Configure Access. The Configure Access page is
displayed.
3. Click an agent access type that supports the creation of targeted credentials
(for example, an access type other than CAS or IPC). The credentials
associated with that access point are listed.
4. Click Configure Credentials. The Configure Credential wizard is displayed.
5. If the Welcome page is displayed, click Next. The Credential Type page is
displayed.
6. Select the type of credential that you want to create. The following credential
types are available:

Key pair
Choose this credential type to specify a key pair file and password.
Restriction: Avoid creating a key pair credential on systems that do

not support a protocol using key pairs.
SNMP v1/v2c
Choose this credential type to use either SNMPv1 or SNMPv2c and
specify a community name.
SNMP v3
Choose this credential type to manage SNMPv3 profiles.
User ID and password
Choose this credential type to specify a user ID and password for the
credential.
X509 Choose this credential type to specify a keystore location and
password, and an alias for the credential.
Note:
v This list represents all available credential types. The list of credential types
that is displayed depends on the type of access point.
v Two credentials of the same type cannot exist simultaneously on an access
point. If one of these types of credentials is already created for this access
point, that credential type option will not be displayed. Your only option is
to edit the existing credential of that type or delete it before you can create
one of the same type.
7. Click Next. The Credential Details page that applies to the type of credential
that you chose is displayed.
8. Enter the values for the chosen credential type.
selected access point on the system.
Related concepts:
Related tasks:
Deleting targeted credentials
Editing targeted credentials
Editing targeted credentials

Use the Edit Credential wizard to edit targeted credentials.
To edit a targeted credential, complete the following steps:

displayed.
3. Click an agent access type that supports the creation of targeted credentials (for
example, an access type other than CAS or IPC). The credentials associated
with that access point are listed.
5. Click Edit. The Edit Credential wizard is displayed.

6. Change the details that are available for changing.
8. Click Finish.
Related concepts:
Related tasks:

Use the Configure Credential wizard to delete targeted credentials that are no
longer needed.
To delete a set of targeted credentials, complete the following steps:

displayed.
3. On the Configure Access page, select the credentials that you want to delete.
4. Click Delete.
Note: Deleting these credentials might affect the access state of the targeted
system.
A confirmation message is displayed.
5. Click OK.
Related concepts:
Related tasks:

Use IBM Systems Director to configure system credentials that are used to log in to
and access advanced system-management functions on target systems.
points.
For an IBM Systems Director Web interface user to do certain types of advanced
system-management tasks on a target system, system credentials must exist. These
credentials map IBM Systems Director Web interface users to user credentials on
the selected system.

Like other targeted credentials, system credentials are each assigned to only one
remote-service agent access point and are located in an authentication registry that
is specific to that access point. These credentials cannot be reused to access other
agent access points.
After the credentials are configured, the IBM Systems Director Server can use them
to do advanced system-management functions on the selected system. In IBM
Systems Director, use Resource Explorer > All systems > (right-click a system) >
Security > Configure System Credentials to manage system credentials.
Creating system credentials:
Use the Create and Edit System Credentials wizard to create system credentials
that provide access to advanced system-management functions on a selected
system. These credentials map IBM Systems Director Web interface users to user
credentials on the target system.
To create a system credential, complete the following steps:

displayed.
3. Click an access point. The credentials associated with that access point are
listed.
4. Click Create. The Create and Edit System Credentials wizard is displayed.
Note: If the Create button is disabled, all credential mappings that you have
the authority to create have been created for the configured authentication
registry on the selected system. A credential mapping can be created only for
those Web interface users who have logged in to IBM Systems Director at least
once. Existing credential mappings can still be edited or deleted.
5. If the Welcome page is displayed, click Next. The Create System Credential
page is displayed.
a credential for a resource that has defined a specific user ID that must be
used when authenticating, you cannot change the value in the User ID field.
7. Click Next. The Assign to IBM Systems Director User page is displayed.
Note: This page lists only Web interface users who have logged in to IBM
Systems Director. These users must log in at least once before a credential can
be created.
8. Select the IBM Systems Director Web interface user for whom the system
credential is being created. You can use the current user or choose another
user from the table.
Remember: Only one mapping can be created for each of the users on this
page.
selected access point on the system.
Repeat the credential creation process for each agent access point that you plan to
use.

Related concepts:
Related tasks:
Editing system credentials
Deleting system credentials
Editing system credentials:
Use the Create and Edit System Credentials wizard to edit existing system
credentials.
To edit a system credential, complete the following steps:

displayed.
3. Click an access point. The credentials associated with that access point are
listed.
5. Click Edit. The Edit Credential Wizard is displayed.
6. If the Welcome page is displayed, click Next. The Create System Credential
page is displayed.
7. Edit the credentials as needed.
9. Click Finish.
Related concepts:
Related tasks:
Deleting system credentials
Creating system credentials
Deleting system credentials:
Use the Configure System Credentials page to delete system credentials that are no
longer needed.
To delete a system credential, complete the following steps:

displayed.

3. Click a remote service agent access point. The credentials associated with that
access point are listed.
4. Select the credential that you want to delete.
6. Click OK.
Related concepts:
Related tasks:
Creating system credentials
Managing access
Use IBM Systems Director to configure credentials that are used to access managed
systems. These credentials enable IBM Systems Director to authenticate to and
manage target systems by using the protocols and access points available on the
managed system.
You can request access to and configure access options for systems in your
environment by using the request access task, the configure access task, or the
configure system credentials task. You can also revoke access to an accessed
system.
Related tasks:
Managing auditing

Use the Request Access page to request access to a secured system if the
management server to which you are connected has not yet authenticated to the
system. You must be able to access the system before you can perform tasks or
remotely access the system.
Before you start, complete the following prerequisite tasks:

v Ensure that you have the correct authorization to access the secured system.
v If you plan to request access to an agentless Windows system, ensure that the
following programs are enabled and disabled accordingly:
– Ensure that the Remote Registry (RR) is enabled.
– Ensure that the Microsoft User Account Control (UAC) is disabled.
For instructions about enabling RR and disabling UAC, see their product
documentation.
Note: Agent access points are all access points that have an access type other than
console. If certain types of agent access points (for example, CAS or IPC) exist on a
resource, you must use this process to access all agent access points on the system.
This process creates the necessary credentials and mappings, but they cannot be
viewed or managed. For other types of agent access points on the secured
resource, you have the option of using the Configure Access task to request access.
Secured systems are displayed in IBM Systems Director Web interface with a
padlock icon beside them in the Access field or column of the systems details.
After a system is accessed, the padlock disappears and additional tasks and status
information are available.

The Access attribute for each resource shows the current access status. You cannot
request access to the resources that have the following types of access status:
v Offline: Use verify access instead.
v OK: No further action is required. You already have access to these resources.
To request access to secured managed systems, complete the following steps.
Note: You can select more than one system at a time as long as each requires the
same user ID and password.
1. In IBM Systems Director Web interface, click Resource Explorer.
2. Navigate to the system that you want to access.
3. Right-click the system for which you want to request access and select Security
> Request Access.
Note: Alternatively, you can select Security > Configure Access and then click
Request Access on the Configure Access page.
4. On the Request Access page, type the user ID and password of a user that
belongs to the System group. Only certain users accounts can be used to
request access. The following table gives detailed requirements of what user
accounts can be used to request access.
Table 52. User accounts able to be used to access a system with request access
Common Agent Platform Agent Agentless
AIX 1. root 1. root 1. root
2. Users in the 2. Users in the 2. Users in the
system group system group system group
3. Users configured
with sudo
Linux 1. root 1. root 1. root
2. Users in the root 2. Users in the root
group (with root group
as primary group) 3. Users configured
with sudo
Windows 1. Administrator 1. Administrator 1. Administrator
2. Users in the Local 2. Users in the Local 2. Users in the Local
Administrators Administrators Administrators
Group Group Group
Notes:
v On AIX, only the root user or users in root group are supported for Common
Agent. Non-root, LDAP, NIS users can not access Common Agent.
v You can use the sudo utility to configure agentless managed systems running
AIX or Linux so that they are accessible by a user without administrator
privileges.
5. Click Request Access. Credentials are created and authenticated to the
managed system in an attempt to access it.
If the access request is successful, the access status for the managed system
changes to OK.

If the access status changes to Partial Access, then the access request was
unsuccessful for at least one access point. Click Configure Access to see the list of
access points and their access states. If necessary, to create additional credentials,
click an access point that does not have an access state of OK and repeat this
procedure.
Related tasks:
Configuring access to agentless managed systems

Related reference:
Request Access password length restriction

Use the Configure Access page to configure credentials for the agent access points
on a managed system. These credentials provide access to basic system
management functions on the target system for all authorized IBM Systems
Director users.
points.
To maximize the management capability of a resource, ensure that all access points
that are hosted on the resource are accessible. To do this, configure credentials that
are used to authenticate to each of those access points.
Note: Certain types of agent access points (for example, CAS or IPC) do not
support this credential configuration process. Instead, the use of the Request
Access task is all that is required to obtain access to all the agent access points on
the resource when these types of access points are present. The Request Access
task creates the necessary credentials and mappings, but they cannot be viewed or
managed. If you need to configure or manage credentials for other agent access
points even when access points such as CAS or IPC are present, you can follow
this process, but the overall system access will be determined by the Request
Access request.
To configure credentials to access secured managed systems, complete the

following steps:
1. In IBM Systems Director Web interface click Resource Explorer.
2. Navigate to the system for which you want to configure access.
3. Right-click the system and select Security > Configure Access. The Configure
Access page is displayed.
4. On the Configure Access page, right-click each listed access point and select
Credential.
5. Complete the task for creating the type of credential that you want. After the
credential is created, it is automatically used to authenticate to the selected
system.
6. Repeat the credential creation process for each access point that you plan to
use.
If you are successful in obtaining access to all access points on a resource, its
access state displays OK.

If the access status changes to Partial Access, then the access request was
unsuccessful for at least one access point. Click Configure Access to see the list of
access points and their access states. If necessary, to create additional credentials,
click an access point that does not have an access state of OK and repeat this
procedure.
Related tasks:
Configuring access to CIM using X509 certificates

You can configure access to the Common Information Model (CIM) server to use
X509 certificates to unlock CIM Remote Service Access Point (RSAP) from IBM
Systems Director. This is useful when you need access to the Platform Agent
without requiring any privileged user credentials. The IBM Systems Director X509
certificate must exist in the Platform Agent truststore. The certificate is associated
with a user and is used for authorization within the Platform Agent.
1. Obtain the IBM Systems Director X509 certificate from the keystore. For
example, on Linux the certificate is located in:
/opt/ibm/director/data/cim/keystore/ibmd_cert.jks
a. Extract the certificate on Linux using the command:
/opt/ibm/director/agent/_jvm/jre/bin/keytool -rfc -export
-alias secureclient -file directorcert.pem
-keystore /opt/ibm/director/data/cim/keystore/ibmd_cert.jks
-storepass iSBi06jA
This stores the certificate in the directorcert.pem file.

b. Copy the directorcert.pem file to the Platform Agent using your preferred
method.
2. Use the cimtrust command to install the IBM Systems Director X509 certificate
in the Platform Agent truststore. For example, use the following command to
create the self-signed X509 certificate in the Platform Agent truststore with
associated user root. The trustedclient.cert file should contain the X509
public key certificate of the trusted client.
cimtrust -a -U root -f trustedclient.cert -T s
For information on the cimtrust command, see the following web site:
http://linux.die.net/man/8/cimtrust.
3. Verify the X509 certificate is added to the agent truststore using the cimtrust
–l command.
4. Configure access for CIM using the X509 certificate to unlock the CIM RSAP.
a. Ensure the IBM Systems Director certificate exists in the Platform Agent
truststore.
b. Perform a system discovery to discover the managed end point.
c. In the IBM Systems Director navigation area, click Resource Explorer.
Navigate to the resource to ensure it was discovered successfully.
d. Right-click the resource then select Security > Configure Access.
e. Right-click the resource then select Credential.
f. Select the X509 credential then click Next.
g. Enter the credential details, including the keystore location, password, and
the certificate alias in the keystore.

h. Click Finish. The CIM RSAP should now be unlocked.
Related tasks:
“Performing a system discovery” on page 174

Use the Revoke Access action to revoke access to a system to which you previously
had access.
The Access attribute for each resource shows the current access status. A resource
must be accessible, with an access status of OK or Partial Access, before you can
revoke its access.
Note: The common agent services (CAS) and interprocess communication (IPC)
agent access point types do not support the revoke access action.
To revoke access to secured managed systems, complete the following steps:

1. In IBM Systems Director Web interface click Resource Explorer.
2. Navigate to the system from which you want to revoke access.
Tip: You can select more than one accessible system at a time.
3. Right-click the system and select Security > Revoke Access.
4. Click OK.
If access is successfully revoked, the access status changes to No access.
Managing access to agentless managed systems

When accessing agentless managed systems from IBM Systems Director, it is good
practice to configure access using a user account other than root. This way, you can
limit the functions that can be performed by the user account and increase the
detail of the audit records that display who has accessed the system.
IBM Systems Director must be configured to enable access to agentless managed

systems through user accounts other than root. After IBM Systems Director has
been configured using the sudo utility, you can request access to resources using
the request access task, the configure access task, or the configure system
credentials task. You can also revoke access to an agentless managed system.
Related tasks:
Configuring access to agentless managed systems
Accessing a managed system with configure system

credentials
In some cases, the request access and configure access tasks might not provide the
IBM Systems Director Server with all the necessary credentials to fully manage a
target system. Use the IBM Systems Director configure systems credentials task to
set up credentials that provide access to advanced system-management functions
for the selected system.
points.

To maximize the management capabilities for a resource, you can configure
additional credentials by using the Configure System Credentials page to ensure
that all agent access points for the resource are accessible. System credentials are
mapped from specific IBM Systems Director Web interface users to user credentials
on the target system.
Related tasks:
Configuring access to agentless managed systems using

sudo utility and key-pair authentication
You can configure access to an agentless managed system for a user account other
than root using key-pair authentication.
Using an account other than root to access an agentless management system

enforces the appropriate security for the system while enabling more detailed audit
records for access to the system. The following procedure illustrates how to
configure access to an agentless managed system for a user account other than root
with key-pair authentication.
1. Set the clock on the managed system to match the time of the management
server. If the managed system time is earlier than that of the management
server, the management server will be unable to unlock the managed system.
Note: <dirtest> is the sudo userid created above.

2. Access the agentless system withSSH key-pair:
a. Log in to the target Linux or AIX machine remotely as the sudo user.
b. Generate a key-pair on the Linux or AIX target machine:ssh-keygen -t rsa
Note: The passphrase can be different from the password of the sudo user,
but the passphrase cannot be blank.
c. Go to /home/<dirtest>/.ssh/ and cat <dirtest>_rsa.pub >>
authorized_keys .
d. chmod 600 authorized_keys
e. Check ssh -i /home/<dirtest>/.ssh/<dirtest>_rsa <dirtest>@localhost
and verify it is successful with the passphrase
f. Click Exit to close connection to localhost.
g. Copy <dirtest>_rsa to the management server.
h. On the management server, edit <install_root>\lwi\conf\overrides\
USMi.properties and add
com.ibm.usmi.server.security.cts.util.escalateUser=true
i. Restart the management server.
3. Find the target system on the IBM Systems Director Web interface Director
Console. Create the credential with
smcli cfgcred -S DirectorUser -W <DirectorUser_password> -r
https://ipaddr_of_target_machine:22/ -c RSA -U <dirtest>
-K "C:\temp\<dirtest>_rsa" -P "director"
4. Configure credentials on IBM Systems Director Web interface: Right-click OS
MEP > Security > Configure Access
5. Right-click SSH Access Type > Credential > Configure Credentials
6. Select Key Pair and enter the following information:
v Private Key File:c:\temp\<dirtest>_rsa
v User ID:<dirtest>
v Password:director
Note: If "Key Pair radio button cannot be found, close all the tabs on the IBM
Systems Director Web interface. Logout and then restart IBM Systems Director
Web interface. Try this process again.
Managing auditing
Audit infrastructure plays a pivotal role in helping organizations adhere to
compliance standards. IT administrators prepare for compliance audits by using
event log managers and robust change management software to allow tracking and
documenting authentication and controls in IT systems. With IBM Systems
Director's auditing capabilities, you can track what takes place on an IBM Systems
Director Server by viewing four categories of audit data : Security, Task, System
Configuration, and System Triggers. In addition, IBM Systems Director plug-ins
can use these existing categories or define new categories to audit their important
events. Use IBM Systems Director Server Auditing to enable and disable auditing
on IBM Systems Director Server, select which audit records to log (by choosing
which categories to enable), view and change the current audit settings, view audit
log events, and delete audit log events.
Tip: For your awareness, auditing can be managed using the following smcli
commands:
chaudit
Use the chaudit command to modify audit settings.
lsaudit
Use the lsaudit command to list audit settings and categories.
lsauditlogs
Use the lsauditlogs command to list a specific number of audit log
messages for one or more audit categories.
rmauditlogs
Use the rmauditlogs command to remove the audit log for one or more
audit categories.
Audit records
The audit records provide information that is necessary to track basic, important,
high-level actions. You can select from several categories of information to audit,
including security, task, system configuration and system triggers.
IBM Systems Director provides several categories of audit records.
Security audit records

This category enables auditing for security-related events in IBM Systems Director,
such as user authentication, authorization, access privileges, and user
administration.
Security audit records include the following data:

v Encryption turned on
v Encryption turned off
v Successful request access
v Unsuccessful request access
v Successful revoke access
v Unsuccessful revoke access

v User administration settings changed
v Successful login
v Successful logout
v Unsuccessful login
v Create role
v Remove role
v Add role to user
v Remove role from user
v Add permission to role
v Remove permission from role
v Modify user
v Modify group
v Create credential
v Modify credential
v Remove credential
v Create mapping
v Modify mapping
v Remove mapping
The following output is an example of security audit-log information:

Role "SMMonitor" successfully added to user "Diruser"
Task audit records

When this category is selected, audit records are logged when IBM Systems
Director tasks start or end.
The task audit records include the following data:

v Task activated
v Task deactivated
v Task scheduled
v CLI command successful
v CLI command not executed
v CLI command failed
v Create resource group
v Modify resource group
v Remove resource group
v Import resource group
v Export resource group
v Modify endpoint
v Remove endpoint
v Import Management Information Base
v Load Management Information Base
v Unload Management Information Base
v Schedule job
v Cancel job
v Delete job
The following output is an example of task audit-log information:

CLI command "lsbundle" succeeded
System Configuration audit records

This category captures all actions or events that a systems administrator performs
to configure the systems, such as deployment, install, and configuration actions on
server, storage, and network.

Audit records are displayed in this category when an IBM Systems Director
plug-in is installed.
The system configuration audit records include the following data:

v Enable auditing globally
v Disable auditing globally
v Enable audit category
v Disable audit category
v Delete audit logs
v Restore audit configuration
v Modify event log preferences
v Edit auto rename template
v Modify auto rename settings
v Modify server preferences
The following output is an example of system configuration audit-log information:

Auditing setting restored to default value
System Triggers audit records

This category captures the events that are automatically generated by the system to
indicate triggers such as status change, failure, or scheduling.
Audit records are displayed in this category when an IBM Systems Director
plug-in is installed.
The system triggers audit records include the following data:

v Job executed
The following output is an example of system triggers audit-log information:

Job "Collect Inventory" is running on "rev4.in.ibm.com"
Setting server-auditing preferences

You can customize your preferences for logging IBM Systems Director Server audit
information. These preferences include whether auditing is turned on and what
types of audit records to log. The audit records provide information that is
necessary to track basic, important, high-level actions. You can select from several
categories of information to audit, including security, task, system configuration
and system triggers.
Note: Server auditing is enabled by default for the Security category.
To set the server auditing preferences for IBM Systems Director Server, complete
and click Server Auditing.
2. On the Server Auditing page, if you want to disable auditing, clear the Enable
Auditing check box.
3. Select the categories of information that you want to audit. Use the Add and
Remove buttons to move items between the Available list and the Selected list.
You can select from the following auditing categories.

Security
This category enables auditing for security-related events in IBM
Systems Director, such as user authentication, authorization, access
privileges, and user administration.
Task When this category is selected, audit records are logged when IBM
Systems Director tasks start or end.
System configuration
This category captures all actions or events that a systems administrator
performs to configure the systems, such as deployment, install, and
configuration actions on server, storage, and network.
System triggers
This category captures the events that are automatically generated by
the system to indicate triggers such as status change, failure, or
scheduling.
For information about viewing audit logs, see “Viewing the audit log”.
Viewing the audit log

If you have enabled auditing for IBM Systems Director Server, you can view the
audit log.
Note: The audit log is in event format and can be viewed on the Event Log page.
To view the audit log when auditing is enabled, complete the following steps:
2. On the Server Auditing page, click View Audit Log. It will navigate to the
Event Log page.
Deleting the audit log

Use Server Auditing to delete the audit logs.
Attention: Deleting the audit log is a task that cannot be undone.
To delete the audit log, complete the following steps:

2. On the Server Auditing page, click Delete All Logs to delete all logged audit
events.
3. A confirmation window is displayed. Click Delete to confirm deleting all
logged audit events.

Communication protocols and supported encryption algorithms
The IBM Systems Director Server can communicate with target resources by using
a predetermined set of communication protocols. Depending on the type of
managed system, these communication protocols support various levels of
encryption.
The following combinations of communication protocols and encryption algorithms

are supported.
Table 53. Supported communication protocols and encryption algorithms
Managed system type Communication protocol Encryption algorithm
Agentless managed system Windows Distributed component object RC2.
model (DCOM)
Simple Network Management Protocol Not encrypted.
(SNMP) v1 and v2
SNMP v3 Encrypted. Advanced Encryption
Standard (AES) or Data Encryption
Standard (DES).
Secure Shell (SSH) Encryption algorithm is negotiated.
Notes:
v SSH is unsupported on managed
systems running the Windows
operating system.
v IBM Systems Director does not
include an SSH server. Use the SSH
server included with the operating
system or an SSH-compliant server
from a third party.
Platform Agent managed Agentless Supports the communication protocols
system and encryption algorithms listed for
Agentless managed system.
Common Information Model (CIM) If configured, encryption is enabled by
default using Secure Sockets Layer (SSL)
port 5989.
Common Agent managed IBM Director 5.x interprocess Encrypted (AES, DES, or Triple DES).
system communication (IPC)
Tivoli Common Agent Services 6.x Encrypted Web services (SSL).
Other Service Location Protocol (SLP) Not encrypted.

Appendix. Accessibility features for IBM Systems Director
Accessibility features help users who have a disability, such as restricted mobility
or limited vision, to use information technology products successfully.
Accessibility features
The following list includes the major accessibility features in IBM Systems Director:
v Uses accessibility support enabled by your Web browser
v Can be operated using only the keyboard
v Communicates all information independent of color
v Supports the attachment of alternate output devices
v Provides help information in an accessible format
v Supports alternatives to audio information
v (Microsoft Windows systems only) Supports interfaces commonly used by screen
readers and screen magnifiers
The IBM Systems Information Center, and its related publications, are
accessibility-enabled. The accessibility features of the information center are
described at Accessibility features in the information center.
Tip: For technical details about the accessibility support in IBM Systems Director,
see the Voluntary Product Accessibility Templates (VPATs). You can request VPATs
from the Web at www.ibm.com/research/accessibility/requests/accvpat.nsf/
bidxjs?OpenForm.
IBM and accessibility
See the IBM Human Ability and Accessibility Center for more information about
the commitment that IBM has to accessibility.
Accessibility options in IBM Systems Director

Set user preferences to improve accessibility settings in IBM Systems Director.
Accessibility settings: Interface information
The IBM Systems Director Web interface provides options that can improve
usability by simplifying tables and providing audio cues when dynamic pages
change. These options also improve screen reader enablement.
To enable accessibility options in the IBM Systems Director Web interface, follow
these steps:
1. Open Settings > Navigation Preferences.
2. Turn on the following options:
v Enable tables for accessibility. This option turns off table features that are not
accessible in the interface, such as fixed column width.
v Play sound when data on the page changes. This option enables an audio
alert for updates to the Web interface.

v Use resource table view as default view for topology perspectives. Topology
maps are not accessible. This option converts map data into an accessible
table format.
3. Click OK or Apply to save your settings.
Keyboard navigation in IBM Systems Director

Accessibility features help users who have a disability, such as restricted mobility
or limited vision, to use information technology products successfully.
Navigating the console using the keyboard
You can navigate the IBM Systems Director Web interface using keyboard shortcuts
that are provided by your Web browser. Refer to your Web browser documentation
for more information about keyboard shortcuts.
Use the following key combinations to navigate the console by keyboard:

v To move through the controls on a particular page, press Tab.
v To click a link or control on a page using the keyboard, navigate to the link or
control and press Enter.
v To open a combination box, press Alt+Down arrow. To then navigate in the
combination box, press the arrow keys.
Notes: Every table as a set of functions at the bottom of the table that you can use
to navigate through pages in the table. One function is the Go to page field. If you
enter a page number that is not valid in this field, the table stays on the current
page.
Navigating the help using the keyboard
Use the following key combinations to navigate the help system by keyboard:
v To bring the Topic pane (the right hand side) into focus, press Alt+K, and then
press Tab.
v In the Topic pane, to go to the next link, press the Tab key. To go to the
previous link, press Shift+Tab.
v To go directly to the Search Results view in the left hand side, press Alt+R, and
then press the Enter key or Up arrow to enter the view.
v To go directly to the Navigation (Table of Contents) view in the left hand side,
press Alt+C, and then press Enter or the Up arrow to enter the view.
v To navigate your browser history, press Alt+Left arrow to go back. If you have
navigated back to a previously view page, press Alt+Right arrow to navigate
forward again.
v To expand and collapse a node in the navigation tree, tab to the + or - icon next
to the node to bring the node into focus, and then press the Right arrow or Left
arrow.
v To go to the next frame in the help system, press F6. To go to the previous frame
in the help system, press Shift+F6.
v In the navigation, to move to the next topic node, press the Down arrow or Tab.
To move to the previous topic node, press the Up arrow or Shift+Tab.
v To go to the next link, button, or topic node from inside a view, press Tab.
v To scroll all the way up or down in a frame, press Home or End, respectively.
v To print the active pane, press Ctrl+P.

v To move to the search entry field, press Alt+S.
Note: Screen readers may override keyboard commands. Refer to the Using a
screen reader topic for more information.
Using a screen reader with IBM Systems Director

Recommendations and restrictions when using a screen reader for accessibility in
Screen reader accessibility:
IBM Systems Director supports screen readers in Microsoft Windows. The Web
interface is tested with Freedom Scientific JAWS for Windows screen reader
software. The following tips can help you successfully navigate the IBM Systems
Director Web interface with JAWS:
v Access IBM Systems Director Server using a supported Mozilla Firefox browser.
Certain functions, such as dynamic refresh, do not work correctly when using
Internet Explorer with JAWS screen reader.
v Turn on the accessibility options in IBM Systems Director. See “Accessibility
options in IBM Systems Director” on page 693 for instructions.
v Use the following JAWS key commands to navigate Actions menus when
working with resource tables:
– To move to the next menu item with focus and control, press and hold Shift
+ Ctrl keys while using the Up arrow and Down arrow keys.
– In the navigation pane, each node is a single list item. Press Insert+Tab to
read the selected node.
– To navigate to a sub-menu, navigate into a sub-menu list, press Alt + Right
arrow key.
– To navigate within Actions menus, press Insert + z to toggle the JAWS virtual
keyboard.
– If tables are difficult to understand with JAWS, press Insert + v to open the
Adjust JAWS Options page and change the table reading preferences.
– Other JAWS key commands are documented in the JAWS product. A quick
reference guide is available online: http://www.freedomscientific.com/
training/training-JAWS-keystrokes.htm
JAWS restrictions:
For detailed descriptions of accessibility limitations and techniques to work around

those limitations, refer to the Accessibility troubleshooting topic.
v In some cases, submitting a page where required fields have not been filled in
correctly will cause an error. The error message indicates that there are
incomplete required fields but will not automatically advance the user to the
field that caused the error. You must manually advance through the fields to
resolve the problem.
v The installation interface is not accessible. The alternative is to follow
instructions for silent install. See Accessible method for installing IBM Systems
Director.
v IBM Systems Director limits the amount of time a browser session can remain
inactive before the session is timed out. See Preventing session timeouts for
users with disabilities.
Appendix. Accessibility features 695

v The accessible alternative for viewing the topology map is the resource view or
relationship view. The content within these views is limited or enhanced by the
depth value, which defaults to 3 and can be set to any level from 1 to a variable
maximum level. Setting the depth to the maximum will list all of the endpoints
available, while lesser numbers will show fewer endpoints.

Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte character set (DBCS) information,

contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:
Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan, Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
Dept. LRAS/Bldg. 903
11501 Burnet Road
Austin, TX 78758-3400
U.S.A
Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.
The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,

modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and services names might be trademarks of IBM or other
companies. A current list of IBM trademarks is available on the Web at “Copyright
and trademark information” at www.ibm.com/legal/copytrade.shtml.
Adobe is either a registered trademark or trademark of Adobe Systems

Incorporated in the United States, and/or other countries.
Other product and services names might be trademarks of IBM or other

companies.
INFINIBAND, InfiniBand Trade Association, and the INFINIBAND design marks

are trademarks and/or service marks of the INFINIBAND Trade Association.
Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries

in the United States and other countries.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.
Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Other company, product, or service names may be trademarks or service marks of

others.
Notices 699
Glossary
This glossary includes terms and definitions for IBM Systems Director.
To view glossaries for other IBM products, go to information about the common agents
www.ibm.com/software/globalization/ and resource managers in a user's
terminology/. environment.
Agentless-managed system
A A system that does not have an agent
Advanced Encryption Standard (AES) installed but can be discovered by IBM
A data encryption technique that Systems Director using Secure Shell
improved upon and officially replaced the (SSH), Distributed Component Object
Data Encryption Standard (DES). AES is Model (DCOM), or Simple Network
sometimes referred to as Rijndael, which Management Protocol (SNMP).
is the algorithm on which the standard is
The function available to
based.
Agentless-managed systems is limited to
Advanced System Management interconnect the following tasks, and varies based on
(ASM interconnect) operating system and hardware: discover
A feature of IBM service processors that systems, collect limited operating-system
enables users to connect up to 24 servers inventory data, remotely deploy and
to one service processor, thus eliminating install Common Agent and Platform
the need for multiple modems, Agent, perform limited remote access, and
telephones, and LAN ports. It provides perform limited restart capabilities
such out-of-band management functions
alert A message or other indication that signals
as system power control,
an event or an impending event.
service-processor event-log management,
firmware updates, alert notification, and alert forwarding
user profile configuration. A function that ensures that alerts are
sent, even if a managed system
Advanced System Management processor (ASM
experiences a catastrophic failure, such as
processor)
an operating-system failure.
A service processor built into the
mid-range Netfinity® and early xSeries Alert Standard Format (ASF)
servers. IBM Systems Director can connect A protocol for the remote management of
out-of-band to an ASM processor located systems in environments without
on an ASM interconnect; an ASM PCI operating systems.
adapter, a Remote Supervisor Adapter, or
ASM interconnect
a Remote Supervisor II must serve as the
See Advanced System Management
gateway service processor.
interconnect.
AES See Advanced Encryption Standard.
ASM processor
agentless See Advanced System Management
Pertaining to a type of data collection that processor.
is accomplished without installing
Auto-Logical Drive Transfer
additional agents. Data is obtained by
See auto volume transfer/auto disk
using software that is already installed on
transfer.
the computer.
auto volume transfer/auto disk transfer
agent manager
(AVT/ADT)
A network service that provides
A function that provides automatic
authentication and authorization and that
failover in case of controller failure on a
maintains a registry of configuration
storage subsystem.

AVT/ADT management module name, network
See auto volume transfer/auto disk protocols, and static IP addresses. If
transfer. Remote Deployment Manager (RDM) is
installed on the management server, the
B chassis detect-and-deploy profile also can
include deployment policies.
Basic Input/Output System (BIOS)
The code that controls basic hardware CIM See Common Information Model.
operations, such as interactions with
cloning
diskette drives, hard disk drives, and the
In z/VM, a copying technique that
keyboard.
preserves the characteristics of the
Bash shell original but personalizes instance-specific
An sh-compatible shell that incorporates data. The result of a cloning operation is
the positive aspects of Korn shell and C new instance of an entity (for example, of
shell. It serves as the GNU operating a virtual disk, a virtual computer system,
system's command language interpreter. or an operating system) rather than a
backup of the original.
BIOS See Basic Input/Output System.
cluster
Blade slot connection
A collection of complete systems that
The connection between the SAS
work together to provide a single, unified
connectivity module and a BladeCenter
computing capability.
server blade.
Common Agent
Basic Zone Permission Table
Common Agent provides a rich set of
A table on the Manage Fabric page. Use it
security, deployment, and management
to map zone groups with hosts to zone
function. The function available for
groups that have storage that you want
Common-Agent managed systems varies
those hosts to have access to.
based on operating system and hardware,
BladeCenter chassis and includes the following tasks: discover
A BladeCenter unit that acts as an systems; collect comprehensive platform
enclosure. This 7-U modular chassis can and operating system inventory data;
contain up to 14 blade servers. It enables monitor health and status; manage alerts;
the individual blade servers to share remotely deploy and install Common
resources, such as the management, Agent; perform remote access, including
switch, power, and blower modules. transferring files; perform power
management function; additional event
blade server
support; monitor processes and resources,
A high-throughput, two-way, Intel
and set critical thresholds that send
Xeon-based server on a card that supports
notifications when triggered; manage
symmetric multiprocessors (SMPs).
operating system resources and processes.
browser system
Common Agent-managed system
A system that connects to the IBM
An IBM or non-IBM server, desktop
Systems Director Web interface on the
computer, workstation, or mobile
management server through a Web
computer that has Common Agent
browser.
installed. The function of a Common
Agent-managed system varies depending
C on the operating system and hardware.
chassis
Common Information Model (CIM)
The metal frame in which various
An implementation-neutral,
electronic components are mounted.
object-oriented schema for describing
chassis detect-and-deploy profile network management information. The
A profile that IBM Systems Director Distributed Management Task Force
automatically applies to all new (DMTF) develops and maintains CIM
BladeCenter chassis when they are specifications.
discovered. The profile settings include

configuration plan include disk spaces from multiple
A set of configuration templates used to physical disks. A disk pool corresponds to
configure a system. a z/VM Directory Maintenance Facility
allocation group.
configuration setting
Realtime definition of a system or device, distributed component object model (DCOM)
which can be saved as a configuration An extension of the Microsoft Component
template. You can save configuration Object Model (COM) to support objects
settings from a system and turn then into distributed across a network.
configuration templates, or you can create
Domain
configuration setting from scratch.
A group of IP addresses that corresponds
configuration template to a specific site, group, university,
A version of configuration settings that company, or other organization.
are not on a given system, but are stored
DSA See digital signature algorithm.
for future deployment. You can deploy a
configuration template on a system Dword
without having it as a member of a A sequence of four contiguous bytes or
configuration plan. characters which, together, are considered
one unit. When discussing the bits that
D are transmitted over a physical link, dword
represents four characters (or 40 bits).
database
When discussing the contents of a frame
The database that contains the data stored
after 10b8b decoding, dword represents
by IBM Systems Director Server.
four bytes (or 32 bits).
database server
Dword sync
The server on which the database
Dword synchronization. Detection of an
application and database are installed.
incoming stream of dwords from a
Data Encryption Standard (DES) physical link by a PHY.
A cryptographic algorithm designed to
encrypt and decrypt data using a private E
key.
ECM Expander connection manager. An object
DES See Data Encryption Standard. within an expander that manages routing.
Diffie-Hellman key exchange enclosure
A public, key-exchange algorithm that is A unit that houses the components of a
used for securely establishing a shared storage subsystem, such as a control unit,
secret over an insecure channel. disk drives, and power source.
digital signature algorithm (DSA) endpoint
A security protocol that uses a pair of The system that is the origin or
keys (one public and one private) and a destination of a session.
one-way encryption algorithm to provide
event An occurrence of significance to a task or
a robust way of authenticating users and
system. Events can include completion or
systems. If a public key can successfully
failure of an operation, a user action, or
decrypt a digital signature, a user can be
the change in state of a process.
sure that the signature was encrypted
using the private key. event action
The action that IBM Systems Director
discovery
takes in response to a specific event or
The process of finding resources within
events.
an enterprise, including finding the new
location of monitored resources that were event-automation plan
moved. A user-defined plan that determines how
IBM Systems Director will manage certain
disk pool
events. An event action plan comprises
In z/VM Center, a logical grouping of
contiguous disk spaces. A disk pool can
Glossary 703
one or more event filters and one or more worldwide port names (WWPNs) of the
customized event actions. host bus adapters (HBAs) that the cluster
has detected on the storage area network
event filter
(SAN).
A filter that specifies the event criteria for
an event action plan. Events must meet host system
the criteria specified in the event filter in A system that contains resources from
order to be processed by the event action which virtual servers are constructed.
plan to which the filter is assigned.
HT See Hyper-Threading.
Expander
Hyper-Threading (HT)
A device that enables quick aggregation
A technology with which a single
of several disk drives in a single SAS
processor can function as two virtual
domain. An expander can connect
processors and execute two threads
multiple hosts to multiple targets. A SAS
simultaneously.
connectivity module is an expander.
hypervisor
Extensible Markup Language (XML)
A program or a portion of Licensed
A standard metalanguage for defining
Internal Code (LIC) that allows multiple
markup languages that is based on
instances of operating systems to run
Standard Generalized Markup Language
simultaneously on the same hardware.
(SGML).
I
F
IBM Systems Director environment
fabric A complex network using hubs, switches,
The complex, heterogeneous environment
and gateways. Fibre channel uses a fabric
managed by IBM Systems Director. It
to connect devices.
includes systems, BladeCenter chassis,
field-replaceable unit (FRU) software, and SNMP devices.
An assembly that is replaced in its
IBM Systems Director plug-ins
entirety when any one of its components
A tool that extends the functionality of
fails.
IBM Systems Director (for example,
File Transfer Protocol (FTP) Electronic Service Agent).
In TCP/IP, an application layer protocol
IBM Systems Director Server
that uses TCP and Telnet services to
The main component of IBM Systems
transfer bulk-data files between machines
Director software. When installed on the
or hosts.
management server, it provides basic
FRU See field-replaceable unit. functions such as discovery of the
managed systems, persistent storage of
G configuration and management data, an
inventory database, event listening,
gateway
security and authentication, management
gigabyte (GB) console support, and administrative tasks.
In decimal notation, 1 073 741 824 when
IBM Systems Director Server service
referring to memory capacity; in all other
A service that runs automatically on the
cases, it is defined as 1 000 000 000.
management server, and provides the
group A logical set of managed objects. Groups server engine and application logic for
can be dynamic, static, or task-based. IBM Systems Director.
IBM Systems Director service account
H
The Windows operating-system account
HBA Host bus adapter. It plugs into a host so associated with the IBM Systems Director
that it can communicate with a SCSI service.
device.
image A bootable operating system and
host object additional software in the form of a single
A logical object that groups one or more raw image file. You can store, copy, and

customize system images to reuse them with each other within the same
for creating virtual servers. computer or over a network.
image repository IPC See interprocess communication.
A part of a local or shared file system that
ISMP See integrated system management
is used to store system images.
processor.
inband communication
iso image
Pertaining to events that are transmitted
A disk image for an ISO 9660 file system,
between IBM Systems Director Server and
containing the installable files for a
service processors in systems that are
particular update or upgrade.
running the required IBM Systems
Director agent inventory data
Information about physical, logical, and
Initiator
virtual hardware (such as virtual systems,
A SCSI device that asks another SCSI
virtual servers, and farms), software
device (the target) to perform an
applications, operating systems,
operation. Usually, a host computer acts
middleware, firmware and BIOS,
as an initiator and a peripheral device
diagnostics, and network.
acts as a target. With SAS zoning,
initiators and targets can see only parts of
J
a domain. These parts are called zone
groups. job A separately runnable unit of work.
instance job instance
An individual realization of the operating A specific occurrence of a job that is
system with a particular version, running or has completed running.
configuration, physical location, and
identifier. K
In object-oriented programming, an object keystore
of a particular class. In security, a storage object, either a file or
a hardware cryptographic card, where
integrated system management processor
identities and private keys are stored, for
(ISMP)
authentication and encryption purposes.
A service processor built into some
Some keystores also contain trusted, or
xSeries servers. ISMP is the successor to
public, keys.
the Advanced System Management (ASM)
processor.
L
Intelligent Peripheral Management Interface
launched task
(IPMI)
Tasks that start outside of the IBM
A standard for controlling intelligent
Systems Director Web interface.
devices that monitor a system. It provides
for dynamic discovery of sensors in the light path diagnostics
system and the ability to monitor the A technology that provides a lighted path
sensors and be informed when the to failed or failing components to
sensor's values change or go outside expedite hardware repairs.
certain boundaries.
logical unit number (LUN)
interprocess communication (IPC) In the Small Computer System Interface
1. The process by which programs send (SCSI) standard, a unique identifier used
messages to each other. Sockets, to differentiate devices, each of which is a
semaphores, signals, and internal logical unit (LU).
message queues are common methods Loss dword sync
of interprocess communication. An error that occurs when a PHY stops
2. A mechanism of an operating system detecting an incoming stream of dwords.
that allows processes to communicate
LUN See logical unit number.
Glossary 705
M nonvolatile random access memory (NVRAM)
Random access memory (storage) that
MAC address
retains its contents after the electrical
See Media Access Control address.
power to the machine is shut off.
management module
NVRAM
The BladeCenter component that handles
See nonvolatile random access memory.
system-management functions. It
configures the chassis and switch
O
modules, communicates with the blade
servers and all I/O modules, multiplexes out-of-band communication
the keyboard/video/mouse (KVM), and Pertaining to events that are transmitted
monitors critical information about the between the service processor and IBM
chassis and blade servers. Systems Director Server over a shared
connection. The type of service processor
MD5 A type of message algorithm that converts
present in a server determines which
a message of arbitrary length into a
paths out-of-band communication can
128-bit message digest. This algorithm is
take. These types of communication are
used for digital signature applications
known as out-of-band communication
where a large message must be
because they take place independent of an
compressed in a secure manner.
operating system.
management server
The server on which IBM Systems P
Director is installed.
PCI See Peripheral Component Interconnect.
Media Access Control address (MAC address) See also Peripheral Component
In a local area network, the protocol that Interconnect-X.
determines which device has access to the
PCI-X See Peripheral Component Interconnect-X.
transmission medium at a given time.
See also Peripheral Component
megabyte (MB) Interconnect.
For processor storage, real and virtual
Peripheral Component Interconnect (PCI)
storage, and channel volume, 2 to the
A local bus that provides a high-speed
20th power or 1 048 576 bytes.
data path between the processor and
For disk storage capacity and attached devices. See also Peripheral
communications volume, 1 000 000 bytes. Component Interconnect-X.
Peripheral Component Interconnect-X (PCI-X)
N
An enhancement to the Peripheral
network interface card Component Interconnect (PCI)
A printed circuit board that plugs into a architecture. PCI-X enhances the
personal computer, server, or workstation. Peripheral Component Interconnect (PCI)
It controls the exchange of data over a standard by doubling the throughput
network and provides the electronic capability and providing additional
functions for the data-link protocol or adapter-performance options while
access method, such as token ring or maintaining backward compatibility with
Ethernet. PCI adapters. See also Peripheral
Component Interconnect.
network interface controller (NIC)
Hardware that provides the interface persistent
control between system main storage and Pertaining to data that is maintained
external high-speed link (HSL) ports. across session boundaries, usually in
nonvolatile storage such as a database
Network News Transfer Protocol (NNTP)
system or a directory.
A protocol that is used to post messages
in, distribute messages to, and retrieve PFA See Predictive Failure Analysis.
messages from news groups and to
PHY Physical layer. A PHY is responsible for
transfer articles between news servers.
the transmission of signals between

computers. The function of each zone Predictive Failure Analysis (PFA)
group is determined by how you A scheduled evaluation of system data
configure each PHY port on an expander. that detects and signals parametric
degradation which might lead to
PHY reset
functional failures.
Any of several problems that can arise
during a PHY reset sequence that can private key
cause the sequence to fail. In secure communication, an algorithmic
pattern used to encrypt messages that
physical platform
only the corresponding public key can
An IBM Systems Director managed object
decrypt. The private key is also used to
that represents a single physical chassis or
decrypt messages that were encrypted by
server that has been discovered through
the corresponding public key. The private
the use of the Service Location Protocol
key is kept on the user's system and is
(SLP).
protected by a password. See also public
Platform Agent key.
Platform Agent provides a lighter
public key
footprint and fewer management
In secure communication, an algorithmic
functions than the Common Agent. The
pattern used to decrypt messages that
function available for Platform-Agent
were encrypted by the corresponding
managed systems is limited to the
private key. A public key is also used to
following tasks, and varies based on
encrypt messages that can be decrypted
only by the corresponding private key.
systems, collect limited platform
Users broadcast their public keys to
inventory data, monitor health and status,
everyone with whom they must exchange
manage alerts, remotely deploy and
encrypted messages. See also private key.
install Common Agent, perform limited
remote access, and perform limited restart
Q
capabilities.
Platform Agent-managed system R
An IBM or non-IBM server, desktop
remote I/O enclosure
computer, workstation, or mobile
An expansion enclosure of Peripheral
computer that has Platform Agent
Component Interconnect-X (PCI-X) slots,
installed.
for example, an RXE-100 Remote
Platform manager Expansion Enclosure. The enclosure
Software that manages one or more host consists of one or two expansion kits.
systems and their associated virtual
Remote Supervisor Adapter
servers and operating systems. Platform
An IBM service processor. It is built into
managers can be started from the IBM
some xSeries servers and available as an
Systems Director Web interface. For
optional adapter for use with others.
example, IBM BladeCenter Management
When used as a gateway service
Module, IBM Hardware Management
processor, the Remote Supervisor Adapter
Console (HMC), IBM Integrated
can communicate with all service
Virtualization Manager (IVM), and
processors on the Advanced System
VMware VirtualCenter are platform
Management (ASM) interconnect.
managers.
resource
plug-in
A generic term for anything that IBM
A software module that adds function to
Systems Director can manage. For
an existing program or application.
example, systems, groups, and updates
POST See power-on self-test. are all resources.
power-on self-test (POST) resource manager
A series of internal diagnostic tests In the Tivoli common agent services , the
activated each time the system power is server of a management application that
turned on. directly interacts with a managed
Glossary 707
resource. For example, a resource continuous memory space and access to
manager installs bundles on the agent all associated adapters. A scalable
and starts and stops a subagent. partition is the logical equivalent of a
physical platform. Scalable partitions are
resource-monitor threshold
associated with scalable systems and
The point at which a resource monitor
comprise only the scalable nodes from
generates an event.
their associated scalable systems.
root user
scalable system
1. In Linux and UNIX operating An IBM Systems Director managed object
systems, a user who has superuser that consists of scalable nodes and the
authority and root privileges. A root scalable partitions that are composed of
user's user identifier (UID) is 0. the scalable nodes in the scalable system.
2. A system user who operates without When a scalable system contains two or
restrictions. A root user has the special more scalable nodes, the servers that they
rights and privileges needed to represent must be interconnected through
perform administrative tasks. their SMP Expansion Modules to make a
multinode configuration, for example, a
RSA See Remote Supervisor Adapter.
16-way xSeries 455 server made from four
scalable nodes.
S
SCSI Small computer systems interface. A
SAN Storage area network. A network that
high-speed communications protocol that
attaches computer storage devices to
allows your computer to communicate
servers. (A disk array controller is an
with peripheral hardware.
example of a computer storage device.)
SCSI domain
SAS Serial attached SCSI. A mechanism for
An I/O system that consists of a set of
accessing computer peripheral devices.
SCSI devices that communicate with each
SAS employs a serial (one bit at a time)
other through a service delivery
means of digital data transfer over thin
subsystem.
cables.
secure copy (SCP)
SAS domain
A means of securely transferring
The I/O system that can also serve as a
computer files between a local and a
SCSI domain. Also known as a service
remote host or between two remote hosts
delivery subsystem.
using secure shell (ssh).
SATA Serial advanced technology attachment. A
Secure Hash Algorithm (SHA)
way to connect hard disk drives to
An encryption method in which data is
computer systems. SATA is based on
encrypted in a way that is mathematically
serial signaling technology, unlike current
impossible to reverse. Different data can
Integrated Drive Electronics (IDE) hard
possibly produce the same hash value,
disk drives that use parallel signaling.
but there is no way to use the hash value
scalable node to determine the original data.
A physical platform that has at least one
Secure Sockets Layer (SSL)
SMP Expansion Module. Additional
A security protocol that provides
attributes are assigned to a physical
communication privacy. With SSL,
platform when it is a scalable node. These
client/server applications can
additional attributes record the number of
communicate in a way that is designed to
SMP Expansion Modules, SMP Expansion
prevent eavesdropping, tampering, and
Ports, and RXE Expansion ports on the
message forgery.
physical chassis.
secure shell (ssh)
scalable partition
A Unix-based command interface and
An IBM Systems Director managed object
protocol for securely getting access to a
that defines the scalable nodes that can
remote computer.
run a single image of the operating
system. A scalable partition has a single,

server farm managed-system data. When installed on
A group of network servers that are a managed system, this feature enables
housed in one location. SNMP-based managers to poll the
managed system and receive its alerts. If
Service delivery subsystem
System Health Monitoring is installed on
A SAS domain.
the managed system also, hardware alerts
Service Location Protocol (SLP) can be forwarded as SNMP traps.
An Internet protocol that identifies and
SNMP device
uses network hosts without having to
An embedded device that uses SNMP to
designate a specific network host name.
monitor network-attached devices,
service processor printers, or computers for conditions that
A generic term for Remote Supervisor require system-management attention.
Adapters, Advanced System Management
SOAP See Simple Object Access Protocol.
processors, Advanced System
Management PCI adapters, integrated SQL See Structured Query Language.
management modules, and integrated
SSL See Secure Sockets Layer.
system management processors (ISMPs).
These hardware-based management SSP Serial SCSI protocol. Used to
processors used in IBM Netfinity and communicate with SAS devices and SCSI
xSeries servers work with IBM Systems software.
Director to provide hardware status and
static partition
alert notification.
A view-only scalable partition.
Simple Object Access Protocol (SOAP)
Storage Management Initiative Specification
A lightweight, XML-based protocol for
(SMI-S)
exchanging information in a
A design specification developed by the
decentralized, distributed environment.
Storage Networking Industry Association
SOAP can be used to query and return
(SNIA) that specifies a secure and reliable
information and invoke services across
interface with which storage management
the Internet.
systems (SMSs) can identify, classify,
SLP See Service Location Protocol. monitor, and control physical and logical
resources in a storage area network
SMBIOS
(SAN). The interface integrates the
See system management BIOS.
various devices to be managed in a
SMP SCSI management protocol. Used to storage area network (SAN) and the tools
manage SAS point-to-point topology. used to manage them.
SMP Expansion Module storage pool
An IBM xSeries hardware option. It is a Containers of virtual disks that reside on
single module that contains the Virtual I/O Server.
microprocessors, disk cache, random
storage subsystem
access memory, and three SMP Expansion
A storage control and its attached storage
Port connections. Two SMP Expansion
devices.
Modules can fit in a chassis.
storage volume
snap-in
A representation of a volume from the
A registered user exit program that is
standpoint of the storage system that
defined to be called from mail server
contains the volume.
framework user exit points. The mail
server framework user exit points are STP SCSI tunneling protocol. Used to identify
referred to as ports by the mail server and communicate with SATA devices.
framework. Systems will snap-in the
Structured Query Language (SQL)
programs that are needed to operate.
A standardized language for defining and
SNMP Access and Trap Forwarding manipulating data in a relational
An IBM Systems Director Agent feature database.
that enables SNMP to access
Glossary 709
Subtractive routing attribute are star (centralized), bus (decentralized),
The attribute of an expander PHY that and ring (decentralized).
indicates that it can be used by the ECM
triple Data Encryption Standard (triple DES)
to route connection requests to an
A block cipher algorithm that can be used
attached expander device.
to encrypt data transmitted between
Subtractive routing method managed systems and the management
The method the ECM uses to route server. Triple DES is a security
connection requests to an expander enhancement of DES that employs three
device. successive DES block operations.
switch module triple DES
The BladeCenter component that provides See triple Data Encryption Standard.
network connectivity for the BladeCenter
Trivial File Transfer Protocol (TFTP)
chassis and blade servers. It also provides
In Internet communications, a set of
interconnectivity between the
conventions that transfers files between
management module and blade servers.
hosts using minimal protocol.
system
trustore
Operating-system-based or
In security, a storage object, either a file or
hardware-based endpoint that has an IP
a hardware cryptographic card, where
address and host name and can be
public keys are stored in the form of
discovered and managed by IBM Systems
trusted certificates, for authentication
Director. For example, storage devices,
purposes in Web transactions. In some
network devices, physical servers, virtual
applications, these trusted certificates are
servers, and operating systems are
moved into the application keystore to
systems.
reside with the private keys.
system management BIOS (SMBIOS)
A specification that extends BIOS to U
support the retrieval of management data.
Universally Unique Identifier (UUID)
system variable The 128-bit numerical identifier that is
A user-defined keyword and value pair used to ensure that two components do
that can be used to test and track the not have the same identifier.
status of network resources. System
undoable disk
variables can be referred to wherever
A type of virtual disk that saves changes
event-data substitution is allowed.
to a temporary file instead of to the
virtual disk itself. Changes can be
T
committed when the virtual machine is
Target Another SCSI device that communicates powered off.
with the originating SCSI device.
UUID See Universal Unique Identifier.
target system
A managed system on which an IBM V
Systems Director task is performed.
viewport
terabyte (TB) 1. In the GDDM® function, a rectangular
For processor storage, real and virtual area within the picture space that
storage, and channel volume, 2 to the defines where the output of the
40th power or 1 099 511 627 776 bytes. current page appears on the work
For disk storage capacity and station.
communications volume, 1 000 000 000 2. In GL, the last transformation in the
000 bytes. graphics pipeline, which is used to
map from normalized device
Topology
coordinates to device coordinates. The
The geometric configuration of a
viewport maps the unit cube x/w =
computer network, or how the network is
physically laid out. Common topologies

+/-1, y/w = +/-1, z/w = +/-1 to the parameter list, such as a volume label or
screen space, as measured in pixels. input/output control.
3. That portion of a partition or usable VPD See vital product data.
area defined for display of data to the
operator. The viewport has a W
predefined size and position on the
screen and is related to a presentation Wake on LAN
space through a specified window. A technology that enables a user to
remotely turn on systems for off-hours
4. In BMS, that part of a screen that is
maintenance. A result of the Intel-IBM
allocated to a partition.
Advanced Manageability Alliance and
virtual farm part of the Wired for Management
A collection of host systems and their Baseline Specification, users of this
associated virtual servers. Virtual farms technology can remotely turn on a server
can represent farms that are defined in and control it across the network, thus
VMware VirtualCenter. Virtual farms can saving time on automated software
also be a collection of hosts in other installations, upgrades, disk backups, and
supported virtualization environments. virus scans.
virtualization environment walk An SNMP operation that is used to
Describes all of the components discover all object instances of
associated with a managed system and its management information implemented in
virtualized resources. The associated the SNMP agent that can be accessed by
components can include a platform the SNMP manager.
manager, host systems, virtual farms,
Web Services Description Language (WSDL)
virtual servers, and guest operating
An XML-based specification for
systems. The following are examples of
describing networked services as a set of
virtualization environments:
endpoints operating on messages
1. Power Systems that are under the containing either document-oriented or
control of a Hardware Management procedure-oriented information.
Console (HMC)
Windows Management Instrumentation (WMI)
2. Power Systems that are under the
An application programming interface
control of an Integrated Virtualization
(API) in the Windows operating system
Manager (IVM)
that enables devices and systems in a
3. VMware ESX Server network to be configured and managed.
4. VMware VirtualCenter WMI uses the Common Information
Model (CIM) to enable network
virtual server
administrators to access and share
A system composed of partitioned,
management information.
shared, or virtualized resources presented
from a host system. An operating system WMI See Windows Management
and other software can be installed on a Instrumentation.
virtual server. Terms also used for this
WMI Query Language (WQL)
concept are Virtual Machine, Hosted
A subset of the Structured Query
Computer, Child Partition, Logical Partition,
Language (SQL) with minor semantic
Domain Guest, Guest Domain, or domU.
changes to support Windows
vital product data (VPD) Management Instrumentation (WMI).
Information that uniquely defines system,
WQL See WMI Query Language.
hardware, software, and microcode
elements of a processing system. WSDL
See Web Services Description Language.
volume
A discrete unit of storage on disk, tape, or
X
other data recording medium that
supports some form of identifier and XML See Extensible Markup Language.
Glossary 711
Y Zone group
A part of a domain whose properties and
Z limits you specify on the Basic Zone
Permission Table. This table is on the
z/VM An IBM System z and zSeries operating
Manage Fabric page.
system that acts as virtualization software.
z/VM can virtualize all system resources,
Symbols and Numerics
including processors, memory, storage
devices, and communication devices. 10b8b decoding
z/VM supports the concurrent operation Decoding a 10-bit character (a control or
of hundreds of operating system data character) into an 8-bit byte (a
instances. control or data byte).
Zone configuration
A collection of information that describes
the zoning for a SAS domain.

Printed in USA

IBm System Director

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

IBm System Director

Caricato da

Copyright:

Formati disponibili

© Copyright IBM Corporation 1999, 2013.

© Copyright IBM Corp. 1999, 2013 iii

iv IBM Systems Director Systems Management Guide

vi IBM Systems Director Systems Management Guide

viii IBM Systems Director Systems Management Guide

This documentation also provides planning and implementation information for

Conventions and terminology

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

Attention: These notices indicate possible damage to programs, devices, or data.

Publications and related information

Information centers and topic collections

© Copyright IBM Corp. 1999, 2013 ix

x IBM Systems Director Systems Management Guide

IBM Redbooks® publications

About this publication xi

xii IBM Systems Director Systems Management Guide

How to send your comments

About this publication xiii

Deprecated terms New terms Description

The function available to

© Copyright IBM Corp. 1999, 2013 xv

xvi IBM Systems Director Systems Management Guide

To learn about IBM Systems Director accessibility of the information center

IBM Systems Director

The IBM Systems Director program contains Management Server (Manager)

Notwithstanding the foregoing, the IBM Systems Director program includes a

Authorization for IBM Systems Director for Power Systems

© Copyright IBM Corp. 1999, 2013 1

Authorization for IBM Systems Director for IBM x86 servers

Terms applicable to API use

Special terms for the Software Update component

2 IBM Systems Director Systems Management Guide

Software Updates Licensee receives are covered by this Agreement. If any

Supporting program details - IBM DB2®

The following applies to use of IBM DB2 Enterprise Server Edition.

Program details - IBM Systems Director Active Energy Manager

Program details - IBM Systems Director VMControl

4 IBM Systems Director Systems Management Guide

The web and command-line interfaces in IBM Systems Director provide a

IBM Systems Director is designed to manage simple and complex environments,

IBM Systems Director integrates with robust workgroup and enterprise

IBM Systems Director components

6 IBM Systems Director Systems Management Guide

Systems Director installed includes:

HTTPS TCP/IP Various protocols

Browser system SNMP devices

Platform managed systems

Common managed systems

Figure 1. Software in an IBM Systems Director environment

For a detailed list of functionality that is supported by Common Agent managed

8 IBM Systems Director Systems Management Guide

For a detailed list of function that is supported by Platform Agent managed

Agentless managed systems

When an Agentless managed system is discovered, it is locked by default. You can

Note: No persistent data is stored on Agentless managed system.

The function available to Agentless managed systems is limited to the following

Managed IBM DB2 database

Manageable resource types

10 IBM Systems Director Systems Management Guide

Manageable systems and system types

IBM Systems Director manages the following types of systems:

12 IBM Systems Director Systems Management Guide

The command-line interface follows the GN/POSIX conventions.

Base function and extensible plug-ins